[maemo-developers] Maemo localization to officially non-supported languages
From: Mohammed Hassan mohammed.2.hassan at nokia.comDate: Thu Oct 25 14:18:47 EEST 2007
- Previous message: Maemo localization to officially non-supported languages
- Next message: Maemo localization to officially non-supported languages
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, 2007-10-24 at 16:46 +0200, ext Tollef Fog Heen wrote: > * Mohammed Hassan > > | > msgfmt will happily provide you with statistics about untranslated > | > strings and fuzzy translations, with the added bonus that it can be > | > automated. > | > | Yes but it will not help differentiation _visually_ between an en_US or > | en_GB string and an Engineering English one. > | > | It will not help quickly identifying the originating UI spec. > | > | I got myself into this thread to see what can be done to ease the > | community involvement. I know that logical IDs are one of the problems > | but I'd say it's mainly a problem for developers more than it being a > | problem for localzsers. > | > | Dropping the logical IDs (If it will happen. I simply do not know) will > | not happen today or tomorrow. > > If the main problem is identifying untranslated strings in the UI, you > could have a bogus locale where you translate all the translatable > strings into their logical IDs. (Which could be added as comments in > the .c file or whatever.) and use that locale as fallback by setting > LANGUAGE. No it doesn't help. You will see an English sentence. How can you tell if it's translated or not ? -- Localization Engineer OSSO - Nokia Multimedia
- Previous message: Maemo localization to officially non-supported languages
- Next message: Maemo localization to officially non-supported languages
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]