From: Vivien Kraus <vivien@planete-kraus.eu>
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Static, pure Scheme internationalization
Date: Sat, 21 Dec 2024 15:31:19 +0100 [thread overview]
Message-ID: <ed0047b6ce9397ccc6fe67030e2ce9ae6f996314.camel@planete-kraus.eu> (raw)
In-Reply-To: <CAPjoZoeMta6yvHD=38ey3speixVzqeU6NOQau0qvX9eGRzmyHQ@mail.gmail.com>
Le samedi 21 décembre 2024 à 23:18 +0900, Nala Ginrut a écrit :
> If you're going to run it like any normal Guile program, it's better
> to use the "native-endianess" function of Guile to detect the
> endianness of the current platform, IIRC it's in (rnrs).
The MO file specification is not very clear:
https://www.gnu.org/software/gettext/manual/html_node/MO-Files.html
The only place it talks about endianness is this:
“The magic number will always signal GNU MO files. The number is stored
in the byte order used when the MO file was generated, so the magic
number really is two numbers: 0x950412de and 0xde120495.”
I could be wrong, but my interpretation is that I should trust the
magic number to indicate which byte order to use for every 4-byte
number in the file. This is a bit of a stretch, admittedly, but I think
it’s more robust that way.
Vivien
next prev parent reply other threads:[~2024-12-21 14:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-21 9:30 Static, pure Scheme internationalization Vivien Kraus
2024-12-21 11:18 ` Nala Ginrut
2024-12-21 11:46 ` Vivien Kraus
2024-12-21 12:14 ` Nala Ginrut
2024-12-21 12:36 ` Nala Ginrut
2024-12-21 14:15 ` Vivien Kraus
2024-12-21 14:18 ` Nala Ginrut
2024-12-21 14:31 ` Vivien Kraus [this message]
2024-12-21 18:27 ` Nala Ginrut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ed0047b6ce9397ccc6fe67030e2ce9ae6f996314.camel@planete-kraus.eu \
--to=vivien@planete-kraus.eu \
--cc=guile-user@gnu.org \
--cc=nalaginrut@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).