ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: french translation of ConTeXt interface - progress (v3)
Date: Wed, 15 Jul 2020 15:09:57 +0200	[thread overview]
Message-ID: <54869B18-27FE-4BF2-A0DF-D84C50099D1B@fiee.net> (raw)
In-Reply-To: <418bbff4-cf97-20a8-2360-4a9c38d3da72@xs4all.nl>


> Am 15.07.2020 um 14:28 schrieb Hans Hagen <j.hagen@xs4all.nl>:
> 
> On 7/15/2020 2:14 PM, Henning Hraban Ramm wrote:
>>> Am 15.07.2020 um 10:31 schrieb Hans Hagen <j.hagen@xs4all.nl>:
>>> you can leave the commands for last ... in an french user interface the english commands will work ok, but keys/values/elements have to be translated
>> Are the other interfaces (Dutch, German, Czech...) actually still working?
> are germans still lipsyncing movies (or even foreign news), translating computerbooks in german (large secxtions in bookshops), translating thrillers and novels ... or has that all stopped working

I don’t understand the comparison.

It’s a difference if I can enjoy movies or books, if I can understand textbooks or manuals in a foreign language or if and why I’d use translated programming or markup commands.

For me, lip syncing can make movies confusing, since the sound doesn’t match the lip movements – I prefer original language with subtitles (for German and English, that is).

> anyway, it is supposed to work and whenever kids have to use context doing it in dutch is more fun (one just learns them the handfull of commands they need)

I’m not against these interfaces, but without translated documentation a translated interface doesn’t make a lot of sense (to me).

E.g. LilyPond docs have several translations (it’s a huge effort!), but besides note names there’s no interface translation. (I’m glad I can use c d e notes, while others prefer do re mi etc. I could even use German h/b instead of b/bes, but I got used to the Dutch default – for input only; in my songbooks I stick to German chord names.)

Translated documentation is important, it lowers the threshold for many users. That’s why I’m writing my book in German. But once you grow out of the basics, you need to be able to find your way in manuals and wiki or ask questions here, where everything’s in English.

With our small developer and user base we struggle enough with keeping documentation current. – I’m very happy with and thankful for the big effort that goes into the wiki at the moment! – Maybe we (i.e. Taco, Paul etc.) can extend the automatisms so far, that we also can document the translated interfaces that way, even if the manually added content would stay in English.

I never heard that kids would use ConTeXt at all, but perhaps I just missed you talking about it.


Sorry, Garulfo, didn’t want to hijack your thread.


Best regards, Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2020-07-15 13:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-14 21:39 Garulfo
2020-07-15  8:31 ` Hans Hagen
2020-07-15 12:14   ` Henning Hraban Ramm
2020-07-15 12:28     ` Hans Hagen
2020-07-15 13:09       ` Henning Hraban Ramm [this message]
2020-07-18 18:56       ` Garulfo
2020-07-18 19:56         ` Hans Hagen
2020-07-19 11:23           ` Garulfo
2020-07-19 13:13             ` Wolfgang Schuster
2020-07-19 18:27               ` Garulfo
2020-07-19 19:31                 ` Pablo Rodriguez
2020-07-19 20:55                 ` Hans Hagen
2020-07-19 21:40                   ` Garulfo
2020-07-19 22:04                     ` Garulfo
2020-07-20  8:38                       ` Hans Hagen
2020-07-20  9:38                     ` Hans Hagen
2020-07-19 21:36                 ` Wolfgang Schuster
2020-07-20  4:49                 ` Aditya Mahajan
2020-07-20  4:54                   ` Jairo A. del Rio
2020-07-19 21:04 Garulfo

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54869B18-27FE-4BF2-A0DF-D84C50099D1B@fiee.net \
    --to=texml@fiee.net \
    --cc=ntg-context@ntg.nl \
    /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 NNTP newsgroup(s).