unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Nala Ginrut <nalaginrut@gmail.com>
To: Vivien Kraus <vivien@planete-kraus.eu>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Static, pure Scheme internationalization
Date: Sat, 21 Dec 2024 23:18:22 +0900	[thread overview]
Message-ID: <CAPjoZoeMta6yvHD=38ey3speixVzqeU6NOQau0qvX9eGRzmyHQ@mail.gmail.com> (raw)
In-Reply-To: <f722621763a16080cd2ae4ffb965f88150835bc8.camel@planete-kraus.eu>

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).

On Sat, Dec 21, 2024 at 11:15 PM Vivien Kraus <vivien@planete-kraus.eu>
wrote:

> Le samedi 21 décembre 2024 à 21:36 +0900, Nala Ginrut a écrit :
> > If you want to base on Hoot, maybe it's OK to implement your own
> > (current-endianess) as you showed.
>
> This will not run on Hoot, it only runs at expansion time. However,
> from what I understand from the GNU MO file format specification, it
> can be written either as big-endian or little-endian, I assume
> depending on the machine used to produce the MO file. You can detect
> which one it is by looking at the magic header in the file.
>
> Thank you for the bytevector-u32-ref suggestion!
>
> Vivien
>


  reply	other threads:[~2024-12-21 14:18 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 [this message]
2024-12-21 14:31             ` Vivien Kraus
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='CAPjoZoeMta6yvHD=38ey3speixVzqeU6NOQau0qvX9eGRzmyHQ@mail.gmail.com' \
    --to=nalaginrut@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=vivien@planete-kraus.eu \
    /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).