From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: German translation of R5RS
Date: Tue, 29 May 2018 19:03:24 +0200 [thread overview]
Message-ID: <20180529170324.cj6rtan2ukcd36nn@pelzflorian.localdomain> (raw)
In-Reply-To: <87vab6wiks.fsf@netris.org>
Hello Mark,
Thank you for your reply. Yes, there may not be enough qualified
reviewers here who know German and have time to spare. Is there
someplace I could go look for reviewers?
I would like a German Guile manual to exist and started translating
R5RS. Many non-experts in programming are put off by having to read
English and rather cargo cult copy from tutorials than read the
English manual. It would be better if they could use sth like
e.g. the German Mozilla Developer Network or the PHP.net manual. R5RS
seems helpful as a stepping stone to the rest of Guile despite
potential mistranslations. German SICP is great btw, sadly it is not
more commonly taught.
Then again, maybe a German manual should live in a separate repository
so as not to add po4a or similar dependencies. Should I put it in
some git repo somewhere stand alone? It would be less official
although I would still be glad to get reviews. If dependencies etc
are not a concern though and someone qualified can review it, then
please add translated manuals.
On Tue, May 29, 2018 at 12:08:19PM -0400, Mark H Weaver wrote:
> A large technical specification like this is quite hard to produce
> without introducing many mistakes. Even when everyone in a standards
> committee is focused on the same draft document, errors are frequently
> introduced.
>
English R5RS has two errors that I know of. Eq? is claimed to return
“true or false”, but the examples make clear it is #t or #f. In the
specification of with-output-to-file a THUNK argument is referred to
as PROC. Should such (minor) errors be fixed? One of my patches also
fixes a misplaced space character in the Texinfo.
Regards,
Florian
next prev parent reply other threads:[~2018-05-29 17:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-28 18:48 German translation of R5RS pelzflorian (Florian Pelz)
2018-05-02 18:49 ` pelzflorian (Florian Pelz)
2018-05-12 23:44 ` pelzflorian (Florian Pelz)
2018-05-29 16:08 ` Mark H Weaver
2018-05-29 16:17 ` Freja Nordsiek
2018-05-29 17:03 ` pelzflorian (Florian Pelz) [this message]
2018-05-29 22:58 ` John Cowan
2018-06-01 20:29 ` 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=20180529170324.cj6rtan2ukcd36nn@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=mhw@netris.org \
/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).