Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


Does the list really need to be translated afresh for each release?!!?
Surely once done the list stays much the same except for 'new'
languages
that have been added?

Usually it's not needed for each release to translate the strings, but for each locale the localers 
are translating the language strings to their own languages, which is a waste  of our time and 
meaningless but adding trouble. 

However, there may be unusual cases that the old strings need retranslating? For zh-cn I am sure 
that it was 100% complete translation in 3.x, but when 4.1 was released there become many 
untranslated strings.  And even worse,  in 4.2 there are even more, even if that string was already 
translated in 4.1.  (Maybe it's because of the .src to .ui change? Or because "~ABC" to "_ABC"? )

Concerning the language names issue,  what I am doing recently is revising the language names to 
english-and-target strings in zh-cn UI. I believe when finished it would look "professional",  
"fresh",  and meaningful. 
-- 
Kevin Suo 锁琨珑
-- 
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.