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 21:36:22 +0900	[thread overview]
Message-ID: <CAPjoZodDx3T=sX-4WTNkhLC5b-rczG8FNBgr3AKM0eX=Dme9hg@mail.gmail.com> (raw)
In-Reply-To: <CAPjoZoenYOhvrLQCEwyVVTMU=HYhGeU+hfjiqgc3wGebGmQYtw@mail.gmail.com>

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

------------------------------------


(bytevector-u32-ref (get-bytevector-n port 4) 0 (native-endianess))

If you want to base on Hoot, maybe it's OK to implement your own
(current-endianess) as you showed. And I think it's Hoot's work to compile
it to WASM
Not sure if it's possible to just reuse (native-endianess) of Guile.



On Sat, Dec 21, 2024 at 9:14 PM Nala Ginrut <nalaginrut@gmail.com> wrote:

> 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 <vivien@planete-kraus.eu>
> wrote:
>
>> 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 in Hoot?
>>
>> Maybe I did not look in the correct place? As far as I understand, the
>> implementation in Hoot for (ice-9 i18n) is this:
>>
>> https://gitlab.com/spritely/guile-hoot/-/blob/main/lib/ice-9/i18n.scm?ref_type=heads
>>
>> It does not contain any meaningful implementation of gettext, and this
>> file claims that i18n is not supported yet.
>>
>> Vivien
>>
>


  reply	other threads:[~2024-12-21 12:36 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 [this message]
2024-12-21 14:15         ` Vivien Kraus
2024-12-21 14:18           ` Nala Ginrut
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='CAPjoZodDx3T=sX-4WTNkhLC5b-rczG8FNBgr3AKM0eX=Dme9hg@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).