Re: Simplified Chinese Translations

[Ivan Vučica]

On Tue, Jul 16, 2013 at 12:08 AM, Riccardo Mottola <rm@gnu.org> wrote:

Another thing I ask other "base" experts: is it okay for the strings file to have chine strings directly in it and have (hopefully) a BOM header? When doing italian and german translations, i always encoded  special unicode characters directly with \u, not by typing them into the file, which resulted in invalid plists.

I'd say that we should ideally, by default, presume that a file is UTF-8 encoded without BOM. 

On Mon, Jul 15, 2013 at 12:08 PM, 白铭骢 <jeffbaichina@gmail.com> wrote:

Hey there folks!

   May I have a introduction first? I am Jeff Bai from Anthon Open Source Community and I am really a big fan of GNUStep. But as a high school student from Mainland China it's really a shame of not having Simplified Chinese (zh_CN.UTF-8) translation for GNUStep. So while we are building :Next for the community (Yes, with some friends of the same or around ages), we decided to polish all the translations to zh_CN for not only GNUStep. But as a big fan of GNUStep I tried my best to do it in the first place! Here is our Git repo for the translations.

   https://github.com/TheNextProject/-Next-Translations

   How are they? If you appreciate them, just tell me and take it :-)

I really like that there's work on more localizations!

As Riccardo said, unfortunately, most core developers don't speak Chinese, so we cannot evaluate the linguistical aspect of the translations...

But when it comes to the technical issues, I see a possible issue with SystemPreferences translation: there appear to be only modifications of English.lproj in your repository, and apparently all modifications have been done on top of the .gorm bundles themselves? I did not check what's the status of GNUstep's post-processing tools for localization, but under OS X it's much better to provide translations in separate .strings files which are then post-processed into localized .xib/.nib files. Maintaining multiple .gorm bundles would probably be painful. 

For GWorkspace, I see that the Localizable.strings has been committed twice?

The other issue is that any 'major' contributions need to have their copyright assigned to the Free Software Foundation. Can you check if you're willing to assign copyright to FSF? Alternatively, we might be able to have the same effect if you're willing to sign a copyright disclaimer, putting the content in public domain.

Please see:

http://www.gnustep.org/developers/conditions.text

Someone can provide you with more information if you're willing to assign copyright or disclaim copyright.

-- 

Ivan Vučica

ivan@vucica.net