From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Denys Nykula <nykula@ukr.net>
Cc: guile-devel@gnu.org
Subject: Re: Translating Guile documentation
Date: Sun, 24 Apr 2022 14:11:18 +0200 [thread overview]
Message-ID: <20220424121118.yrgq32v36xv54dno@pelzflorian.localdomain> (raw)
In-Reply-To: <1650751329.684147000.fjrw2sdf@frv50.fwdcdn.com>
Hello Denys.
On Sun, Apr 24, 2022 at 01:24:33AM +0300, Denys Nykula wrote:
> Hello.
>
> Have the Guile website and reference manual ever been translated to
> languages other than English? If I would like to start translating them
> to my primary language, Ukrainian, what should I know in advance?
You have a wonderful ambition there.
This reminds me of my attempts a long time ago to translate the copy
of r5rs that is shipped with Guile to German.
https://lists.gnu.org/archive/html/guile-devel/2018-04/msg00007.html
Nothing came of it and I don’t know if Guile’s documentation is stable
enough. For example, at
https://guix.gnu.org/blog/2022/online-guix-days-2022-announcement-2/
there have been discussions about reworking part of the docs. See there at
* 13:40–14:15: A Deep Dive into the Guile Documentation & Makeover Proposal
In hindsight, I would rather translate the SICP book
http://mitpress.mit.edu/sicp/
(which already has been translated to German by Susanne
Daniels-Herold, but I think to no other language). I’ve not checked
if there are more recent comparable books. Of course, there are SRFIs
and Guile specifics beyond SICP, like (ice-9 match).
Regards,
Florian
prev parent reply other threads:[~2022-04-24 12:11 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
2022-04-24 12:11 ` pelzflorian (Florian Pelz) [this message]
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=20220424121118.yrgq32v36xv54dno@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--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).