From: Mark H Weaver <mhw@netris.org>
To: "pelzflorian \(Florian Pelz\)" <pelzflorian@pelzflorian.de>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: German translation of R5RS
Date: Tue, 29 May 2018 12:08:19 -0400 [thread overview]
Message-ID: <87vab6wiks.fsf@netris.org> (raw)
In-Reply-To: <20180512234403.mblakweedxvaow5j@floriannotebook> (pelzflorian@pelzflorian.de's message of "Sun, 13 May 2018 01:44:03 +0200")
Hi Florian,
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> writes:
> Please accept my patches adding a German language info file for R5RS
> and fixing some small errors in English R5RS. I believe the patches
> to be reasonably correct.
I very much appreciate this enormous amount of work that you've done!
My primary concern is that I lack the ability to review this, because I
have not (yet?) learned to read German.
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.
Errors in technical specifications can have quite bad consequences over
long time frames, because they lead to misunderstandings in the minds of
developers, and thus bugs in code, which may persist for a long time.
At present, most users who wish to read the R5RS have no choice but to
read the original document written in English. On the one hand, this is
obviously a barrier and hardship for people who do not know English
well, but on the other hand, at least they can be assured that the
document they are reading has been widely reviewed by a large number of
people over several decades.
If we now invite them to read a German translation which has not been
reviewed at all (except for the translator), I fear the resulting
misunderstandings and buggy code that this might entail.
So, I would feel much more comfortable if someone else with good
knowledge of Scheme would step forward to carefully review this
translation. It need not be someone from the Guile community, which
brings me to the next issue:
Although we distribute a copy of R5RS with Guile, we do not maintain
R5RS, and it is not specific to us. To me, this situation seems
somewhat analogous to submitting a large contribution for the Sqlite3
library to the Firefox developers. Firefox distributes a bundled copy
of Sqlite3, but they do not maintain that library.
However, I admit that this case is far more muddled, because R5RS is an
historical document, and there's no longer any group that maintains it
as far as I know.
Are there any German speakers here with good knowledge of Scheme who
would be willing to make a careful review this translation?
Mark
next prev parent reply other threads:[~2018-05-29 16:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180428184817.3jbux62427sfhdjn@floriannotebook>
[not found] ` <20180502184924.ypvspfxay3vyj2o3@floriannotebook>
2018-05-12 23:44 ` German translation of R5RS pelzflorian (Florian Pelz)
2018-05-29 16:08 ` Mark H Weaver [this message]
2018-05-29 16:17 ` Freja Nordsiek
2018-05-29 17:03 ` pelzflorian (Florian Pelz)
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=87vab6wiks.fsf@netris.org \
--to=mhw@netris.org \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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).