Re: [RANT] French translation for debconf templates stucked at 90% : analysis
- To: firstname.lastname@example.org
- Subject: Re: [RANT] French translation for debconf templates stucked at 90% : analysis
- From: Miles Bader <email@example.com>
- Date: Fri, 02 Jul 2004 10:35:17 +0900
- Message-id: <[🔎] firstname.lastname@example.org>
- Reply-to: Miles Bader <email@example.com>
- In-reply-to: <[🔎] 20040701104755.GA3216@free.fr> (Nicolas Bertolissio's message of "Thu, 1 Jul 2004 12:47:55 +0200")
- References: <20040627102912.GF27890@saruman.uio.no> <20040627113618.GA5630@wonderland.linux.it> <E1Bf3fF-0004Q9-EX@torres.ka0.zugschlus.de> <firstname.lastname@example.org> <20040629103842.GA19287@riva.ucam.org> <20040630054852.GI4727@mykerinos.kheops.frmug.org> <40E285D7.email@example.com> <firstname.lastname@example.org> <40E2A4C7.email@example.com> <firstname.lastname@example.org> <[🔎] 20040701104755.GA3216@free.fr>
Nicolas Bertolissio <email@example.com> writes:
>> They are just labels, which people learn the meaning of in context.
>> For error messages, this wouldn't be so good, but for this usage, it's fine.
> Sorry, I don't agree.
> These are label but have no meaning for a non-english speaker, so they
> have to be translated. This is at least the way we do things in French.
Whatever; French != Japanese. Indeed, they in some sense represent
opposite ends of the spectrum -- Japanese are notably enthusiastic about
adopting foreign words in a very ad-hoc way, whereas French are famous
for being, um, anti-non-French.
I suspect that Microsoft actually did think about this issue BTW; e.g.,
the error messages &c on Japanese Windows are not unnaturally full of
transliterated English words. Probably this process was not perfect,
especially in the beginning, and early computer adopters probably had a
much broader knowledge of English than the average person, but by now a
precedent has been established -- computer users are _used_ to these
terms, and would probably be more confused if they changed.
Fast, small, soon; pick any 2.