Changes between Version 15 and Version 16 of Dev/i18n

Timestamp:

03/02/12 16:16:15 (15 months ago)

Author:

hoffmann

Comment:

--

Dev/i18n

@@ -207 +207 @@
 We have created a [https://www.transifex.net/projects/p/indico/ transifex project for Indico]. If you wish to take part in the translation effort, apply for the team corresponding to your language, or propose the creation of a new one if needed.
 
+= Internationalisation: More =
+
+''Internationalisation is british spelling.'' ;-)
+
+I would like to suggest that we have more pages for discussions and specifications for a coherent and efficient i18n activity.
+The following topics (pages) come to my mind. 
+(I do not have time now, but if no one else wants to jump in, I will take care of them later.)
+
+* '''Internationalisation: German'''
+  Some translations are ambiguous ("Event" -> "Ereignis", "Veranstaltung", "Event"(!)). 
+  In order to avoid that a "Presenter" appears as "Präsentator" in one place and "Vortragender" in another, 
+  we must define language dependent guidelines. 
+  Obviously, everything can be looked up in the source code and derived from the context.
+  But it is more efficient to follow common guidelines.
+  And different translators may have different opinions on ideal translations, thus leading to eternal "translations in circles".
+* '''Internationalisation: Dates'''
+  Presently "Mon", "Tue", ... and "Jan", "Feb", ... are translated strings.
+  I would expect that Babel has a built-in function for that, rather than requesting all translations from translators
+* '''Internationalisation: Choice of language codes'''
+  Presently we have projects en, fr_FR, es_ES, de, et_EE, pt_PT (and a request for ru). 
+  Does it make sense to specify fr_FR (and fr_BE, fr_CH, ...) rather than fr?
+  For de, I am convinced - as far as !InDiCo is concerned - 
+  that there is ''no'' difference between the "dialects" de_DE, de_CH, de_BE, de_AT, de_LI, de_LU! (Did I forget one?)
+  By the way: Shouldn't xy_AB for country AB supercede the more general PO file for language xy? 
+  Thus only exceptions from the rule should appear in specific files xy_AB, and all common translations would go to xy.
+  The choice of en (for "all english") is probably the most debatable, because the differences between european and american english are
+  significant (summarize - summarise, flavor - flavour, center - centre, ...)
+