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: Re: German translation of R5RS
Date: Wed, 2 May 2018 20:49:24 +0200	[thread overview]
Message-ID: <20180502184924.ypvspfxay3vyj2o3@floriannotebook> (raw)
In-Reply-To: <20180428184817.3jbux62427sfhdjn@floriannotebook>

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

Hello,

I’ve found answers to most of my own questions and will resend r5rs.de
this week with corrections.

On Sat, Apr 28, 2018 at 08:48:19PM +0200, pelzflorian (Florian Pelz) wrote:
> 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?
> 

Only this question remains.

> 
> 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
>

A friend brought me a library’s copy of Susanne Daniels-Herold’s
German translation of Structure and Interpretation of Computer
Programs.  I will compare the terms it uses to my translation.
(I wonder if the German SICP is available freely licensed and online
like the English edition, but apparently not.)

> 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?

I did a survey with twenty-two people sitting in front of my
university’s cafeteria.  I knew none of them.  The majority (68%, 10
men and 5 women) prefers “Forschende” over “Forscher” (which is
preferred by 22%, 2 men and 3 women, additionally 2 men were
undecided) so I’ll change it to “Forschende”.  (I got similar results
from my own personal umfeld, i.e. friends, acquaintances, family.)

Regards,
Florian

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

  reply	other threads:[~2018-05-02 18:49 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) [this message]
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=20180502184924.ypvspfxay3vyj2o3@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).