[Sparkle] Incomplete localizations

[Justin Bur]

On Aug 1, 2007 at 12:55, Jerry Krinock wrote:

> On 2007 Aug, 01, at 9:03, Justin Bur wrote:
>> Thus I propose: all localizations that have not been fully translated
>> and verified by a native speaker should be removed.
>
> That's a wonderful but lofty goal, especially if you imply that the
> translation and verification are to be done by two different people.
> That would be a great achievement in any software project!

A badly translated or incomplete localization should not be shipped  
in a released product. However, I am not aware of any big problems in  
the completed localizations in Sparkle; my comment was particularly  
directed towards incomplete, placeholder localizations (see below).

No, the translation and verification do not necessarily have to be  
done by different people. But translations do benefit from  
proofreading. Having each localization checked over, if it hasn't  
already been done, is a goal to work towards.

> Finally, please tell us how you concluded that there are "incomplete
> localizations", so we can track this down.  I saw a case recently
> where the localization .strings file was complete, but the code was
> not using the string.  (Last week, Andy committed a patch to fix that
> one.)

The following localizations have untranslated Sparkle.strings files:

cy.lproj es.lproj hu.lproj id.lproj ko.lproj nl.lproj th.lproj

is.lproj is partially translated.

I have not checked the nib files to see if any work has been done there.

Justin