Oh, I'm not familiar with MO file, it seems the endianess is unrelated to
the platform, you need go test it to confirm each time.
Best regards.
On Sat, Dec 21, 2024, 23:31 Vivien Kraus wrote:
> Le samedi 21 décembre 2024 à 23:18 +0900, Nala Ginrut a écrit :
> > If you're going to run it like any
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 c
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
wrote:
> Le samedi 21 décembre 2024 à 21:36 +0900, Nala Ginrut
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 specificati
For this part, maybe there's more efficient way:
(define (get-bytevector-u32 port) "Read a 4-byte big-endian number."
(car (bytevector->uint-list (get-bytevector-n port 4)
(current-endianness)
I see, it's in *unimplemented-bindings of guile.scm, that's why I grep
'gettext' and it exists!
Best regards.
On Sat, Dec 21, 2024 at 8:46 PM Vivien Kraus
wrote:
> Hello!
>
> Le samedi 21 décembre 2024 à 20:18 +0900, Nala Ginrut a écrit :
> > Maybe not complete yet, but it contains gettext, and
Hello!
Le samedi 21 décembre 2024 à 20:18 +0900, Nala Ginrut a écrit :
> Maybe not complete yet, but it contains gettext, and G_ is its short
> hand.
> I saw you implemented a simple G_ macro, is there any reason that it
> can't meet your requirements? Or you just happend to not know it
> exited i
Hi Vivien!
I'm also interested in Hoot for potential web frontend in Scheme.
Back to your case, as I understand, Hoot reused part of Guile code, include
i18n.
Maybe not complete yet, but it contains gettext, and G_ is its short hand.
I saw you implemented a simple G_ macro, is there any reason th
Dear Guile users,
I am very excited about Hoot, but there is one aspect I was not
satisfied with: internationalization. Since it is usually done with
gettext, it requires a C library at run-time. Hoot programs can’t
unfortunately use that.
With your help, I managed to understand how I could rewri
