[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Byte order in the GNU mo file format
From: |
Vivien Kraus |
Subject: |
Re: Byte order in the GNU mo file format |
Date: |
Sat, 21 Dec 2024 16:00:52 +0100 |
User-agent: |
Evolution 3.48.4 |
Le samedi 21 décembre 2024 à 15:54 +0100, Bruno Haible a écrit :
> Vivien Kraus wrote:
> > In order to parse MO files, my interpretation is that I should look
> at
> > the 4-byte magic cookie. If it is [de 12 04 95], then I should read
> > every 4-byte number (offset or string length) as little-endian, and
> if
> > it is [95 04 12 de], then I should read every 4-byte number as big-
> > endian.
> >
> > Do I understand this correctly?
>
> Your understanding is correct.
Thank you for your answer.
> But for what purpose do you need this info? If you are trying to
> support
> a particular programming language, note that GNU gettext already
> supports
> a number of them [1], and support for other programming languages may
> be
> added [2].
I am trying to implement a minimal Gettext run-time in pure Scheme, so
that it can run with Hoot [1]. It would be a lot of trouble to get the
actual gettext to run there.
[1] https://spritely.institute/hoot
Best regards,
Vivien