118
edits
L20n/Issues: Difference between revisions
Context dependency section expanded
(Added genitive case as a challenge for L20n.) |
(Context dependency section expanded) |
||
| Line 3: | Line 3: | ||
; Tools used : One part of the specification should be a grammar specification for the fileformat, in a somewhat understandable syntax. Currently, I'm using [http://antlr.org antlr] to create parsers from a EBNF-like grammar. It promised to create code for more than just java, but currently, I'm hitting a few blockers. It might be that I'm hitting bugs in the 3.0b5, or just limitations of the approach in antlr. Anyway, there's currently no descent output other than java, and creating ASTs doesn't work that well without putting AST-related constructs into the grammar. Which is merely noise. Suggestions welcome, in particular for tools that could even generate js. | ; Tools used : One part of the specification should be a grammar specification for the fileformat, in a somewhat understandable syntax. Currently, I'm using [http://antlr.org antlr] to create parsers from a EBNF-like grammar. It promised to create code for more than just java, but currently, I'm hitting a few blockers. It might be that I'm hitting bugs in the 3.0b5, or just limitations of the approach in antlr. Anyway, there's currently no descent output other than java, and creating ASTs doesn't work that well without putting AST-related constructs into the grammar. Which is merely noise. Suggestions welcome, in particular for tools that could even generate js. | ||
; Platform dependent strings : Can l20n help with doing platform-specific strings (think Options vs Preferences) for Mozilla apps? | ; Platform dependent strings : Can l20n help with doing platform-specific strings (think Options vs Preferences) for Mozilla apps? | ||
; yes/no dialogs : Can we provide context specific button values for stuff like yes and no? See proposal for that on [http://mail.gnome.org/archives/gnome-i18n/2008-April/thread.html#00029 gnome-i18n]. | = Linguistic problems common to existing l10n implementations = | ||
== Context dependency == | |||
; Verb usage in yes/no dialogs (Irish/Welsh): Can we provide context specific button values for stuff like yes and no? See proposal for that on [http://mail.gnome.org/archives/gnome-i18n/2008-April/thread.html#00029 gnome-i18n]. Discussion has been moved to [https://sourceforge.net/mailarchive/forum.php?thread_name=20080408010517.GK6430%40dorothy.members.linode.com&forum_name=translation-i18n translation-i18n] and also brought in next issue. | |||
; Age of a person (Vietnamese): This language is lacking completely neutral pronouns, correct usage cannot be derived without age/gender context. See also ''[http://www.vialanguage.com/Resources/Translation_Articles/Corporate_translation_action.php Tips for your Vietnamese Translation Project]'' | |||
; Honorific speech (Japanese): This language uses different verbs to address a person, depending on its relation to speaker. [http://en.wikipedia.org/wiki/Honorific_speech_in_Japanese Read more] [http://en.wikipedia.org/wiki/Gender_differences_in_spoken_Japanese#Problems_with_localization_of_video_games and more]. [https://bugzilla.mozilla.org/attachment.cgi?id=345735&action=edit Real-life example from NASA Bugzilla] could not be easily (politely) translatable without some knowledge: who is a boss, who is subordinate team member, and who is a valued but external customer... | |||
;Noun classes:We should use [http://en.wikipedia.org/wiki/Noun_class noun classes] to describe the strengths of l20n. | ;Noun classes:We should use [http://en.wikipedia.org/wiki/Noun_class noun classes] to describe the strengths of l20n. | ||
;Genitive case (possessives): See [http://en.wikipedia.org/wiki/Genitive_case genitive case] for more. | ;Genitive case (possessives): See [http://en.wikipedia.org/wiki/Genitive_case genitive case] for more. | ||