[haiku-i18n] Re: Improving while localizing strings

  • From: meanwhile@xxxxxxxxxx
  • To: haiku-i18n@xxxxxxxxxxxxx
  • Date: Mon, 03 Jan 2011 13:31:15 -0500

 

 I'd say have the discussions done here, but at the same time I think the 
original English wording is good enough and I'm therefore not really looking 
forward to changing/messing things up.

What amount of changes are you talking about, could you give an estimate?   


 

 

-----Original Message-----
From: Humdinger <humdingerb@xxxxxxxxxxxxxx>
To: i18n <haiku-i18n@xxxxxxxxxxxxx>
Sent: Mon, Jan 3, 2011 6:39 pm
Subject: [haiku-i18n] Improving while localizing strings


Hi there!

In the course of GCI tasks doing German localization at HTA, I looked 
over the work and found a few things that should be corrected/improved 
in the English original. Since we're gearing up to validate the German 
localizations, I imagine we'll find more of this kind.

It looks like changing the English original in the source code (even if 
it's just adjusting casing or typos) will invalidate (delete?) already 
translated strings in all languages. Right?
Or will the old translation be kept at least, so you wouldn't have to 
translate the whole string again, but only the possibly minimal change 
(if it impacts the translation at all).
I know that the User Guide tool just marks something fuzzy (and even 
that can be overridden, if e.g. it was just a fix relevant to the 
English original). Is there similar functionality with HTA?

In any case, what do you guys think about using the localization effort 
as opportunity to correct mistakes, improve the wording and standardize 
some strings across all apps? Everything will of course be discussed 
here first. (Or should the discussions be done at haiku-development 
since not many devs are subscribed here and some might care very much 
about the wording in the GUI.)

Regards,
Humdinger

--=-=--=-=--=-=--=-=--=-=--=-=--=-=--=-=--=-=--=-
      Deutsche Haiku News  -  Haiku Gazette
        http://haiku-gazette.blogspot.com


 

Other related posts: