From: Maxime Devos <maximedevos@telenet.be>
To: Denys Nykula <nykula@ukr.net>, guile-devel@gnu.org
Subject: Re: Translating Guile documentation
Date: Sun, 24 Apr 2022 10:17:10 +0200 [thread overview]
Message-ID: <d190f8d8af1c1abd09fef9ea8b8dac354ab05c34.camel@telenet.be> (raw)
In-Reply-To: <1650751329.684147000.fjrw2sdf@frv50.fwdcdn.com>
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
Denys Nykula schreef op zo 24-04-2022 om 01:24 [+0300]:
> Then I need to edit the SXML and Texinfo files, run make and upload the
> result on my web server. My question is what are the recommendations for
> those who try that and whether any guile i18n working group exists.
Guix uses po4a and https://translate.fedoraproject.org/, maybe Guile
can do the same? I have not heard of any guile i18n group.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-04-24 8:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 22:24 Translating Guile documentation Denys Nykula
2022-04-24 8:17 ` Maxime Devos [this message]
2022-04-24 12:11 ` pelzflorian (Florian Pelz)
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=d190f8d8af1c1abd09fef9ea8b8dac354ab05c34.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=guile-devel@gnu.org \
--cc=nykula@ukr.net \
/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).