unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: guile-devel@gnu.org
Subject: German translation of R5RS
Date: Sat, 28 Apr 2018 20:48:19 +0200	[thread overview]
Message-ID: <20180428184817.3jbux62427sfhdjn@floriannotebook> (raw)

[-- Attachment #1: Type: text/plain, Size: 2319 bytes --]

Hello Guilers,

I made a translation of R5RS to German and hope that you can accept it
into Guile proper.

You can view the PDF at

https://pelzflorian.de/files/r5rs.de.pdf

You can download the patches (for “git am 0001-…”) at

https://pelzflorian.de/files/wip-r5rsde-patches.tar.gz

or view the changes at

https://pelzflorian.de/git/guile-wip-pf/

I can e-mail the patches, but maybe 0.3MB is too big for the mailing
list.


I have some questions though:

What should I use as the translated Texinfo file’s dircategory and
direntry?  Currently it is

@dircategory Die Algorithmische Sprache Scheme
@direntry
* R5RS-de: (r5rs.de).                 Der Revised(5) Report on Scheme (deutsch).

so M-x info shows the German R5RS in its own category:

Die Algorithmische Sprache Scheme
* R5RS-de: (r5rs.de).           Der Revised(5) Report on Scheme (deutsch).


but maybe it should be organized differently.  I suppose translated
info manuals would be installed for everyone regardless of their
locale preferences?


What do you think about the rationale guiding the translation:

https://pelzflorian.de/git/guile-wip-pf/tree/doc/translation-rationale-de?h=wip-r5rsde&id=08bd475064c7b4874489455693775ba041d01290

My use of the traditional generic “masculine” form for plural
(“researchers → Forscher” instead of the more cumbersome “Forscher und
Forscherinnen” or “ForscherInnen” or “Forschende”) is controversial
and so are the alternatives.  Forschende would work but sounds more
artificial.  Is there some GNU standard?  For singular forms (“user”)
I used the female translation (“Nutzerin”) instead of grammatically
male “Nutzer”.


In the future I want to help translate the rest of the Guile manual
for which I will take another look at Julien Lepiller’s work on Guix’
po4a integration (but first I will look at my Haunt patches again).  I
will not look at Meson support for Guile until I know more about
Guile.

By the way, finding out how to compile guile from my git repository
took long on GuixSD until I found guile-for-guile-emacs.  I am really
looking forward to some kind of channel support with separate *-git
packages like on Arch’s user repository (without substitutes).

Regards,
Florian

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2018-04-28 18:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-28 18:48 pelzflorian (Florian Pelz) [this message]
2018-05-02 18:49 ` German translation of R5RS 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)
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=20180428184817.3jbux62427sfhdjn@floriannotebook \
    --to=pelzflorian@pelzflorian.de \
    --cc=guile-devel@gnu.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).