Talk:Localization: Difference between revisions

From OLPC
Jump to navigation Jump to search
(Resources for choosing names)
(→‎June 19 2007: added summary of #olpc-l10n exchange (still missing some notes))
Line 26: Line 26:
* How to ask for / help with localizing an [[activities|activity]]
* How to ask for / help with localizing an [[activities|activity]]
* Where to sign up for information / discussion about l10n and translation
* Where to sign up for information / discussion about l10n and translation

==== highlights from #olpc-l10n ====

Areas of l10n:
* the website (both the [[wiki]] and [http://www.laptop.org laptop.org])
* [[Sugar]] (several 'flying pages' like [[Customizing NAND images]], [[XO l10n]], [[Sugar i18n]])
* [[Activities]], [[Software projects|core]] and others.
* information and news (wiki and elsewhere)
* free content, either developed for the XO or otherwise

Some results and/or directives:
* It would be convenient (hint) for users to tag themselves (in their pages) with the appropriate [[:Category:User languages]]
** the tagging could be extended to include other 'user skillsets' like coder, artist, educator, etc.
** should be kept simple so as to not overload with structure that hinders or overloads newbies
* New 'guidelines' (akin to [[HIG]]) need to be developed:
** Translation ([[User:Xavi|Xavi]] will give it a shot—page to be determined)
** Educators (linked with what [[User:Lauren|Lauren]] is doing—[[Educational activity guidelines]])
** Content
* Develop
** educational activities
** communities (see [[Local communities]], [[:Category:Pilot site]], [[:Category:Test Plans]])
* Need to raise [[:Category:Developers]] awareness to the issue or i18n & l10n.
** Strings are not the only thing that can/needs to be l10n—images, icons, etc. should also be considered part of the deal (they can be localized by extracting their URLs into a PO file too)
** Given the 'cryptic' nature of PO files used, it could be worthwhile to explore the possibilities that the [[Develop]] activity (particularly when used through the 'gear' [[Image:Key viewsource.jpg]] key) be capable of transparently embeding and extracting the strings to-from the PO files. (must coordinate with [[User:Orospakr]] on how to proceed)
** Stock on '''resources''' about the i18n & l10n process—some links were added to [[Translating#resources]]
** The aim is to produce a simple set of guidelines (with examples) on [[:Category:HowTo|how-to]] get everything ready for l10n.
*** [[User:Lucks]] (developing [[Kuku]]) has gone the extra mile doing the [[Python i18n]]

Some pointers
* '''temporal & taster''' l10n site: http://publictest4.fedora.redhat.com/module/olpc-sugar


== Resources for choosing names ==
== Resources for choosing names ==

Revision as of 02:11, 21 June 2007

Country groups and descriptions

What's the point of this list? I mean, the original content was just a list of countries... but that was June 2006...

I don't really see the point trying to list here what is already in Category:Countries... might as well just put a link! I think this page would be more valuable if we use it for more specific purposes of the Localization effort... Cheers! --Xavi 20:06, 22 April 2007 (EDT)

Localization Topics

This whole new section (and sub-sections) is (imho) re-doing all the work scattered throughout the wiki in several categories like Language support, Languages (international), Fonts, Keyboard, Accessibility, and some specific pages like Input methods, Unicode, etc. and probably others (these are just off my head)...

My 'suggestion' would be to integrate better and/or rework the existing material instead of re-doing the whole thing again... --Xavi 11:35, 27 April 2007 (EDT)


Xavi: The issue has been that there is no central page in the wiki to give countries and overview of all of what needs to be done for internationalization. This is essentially the presentation I did at the countries presentation this week that pulls together a summary of all of what is needed. As you note: everything is scattered, and we have people now needing to actually organize action.

From this general topic here, links to and reorganization of the topics elsewhere is fine; but we must have a cook-book that makes an incoming country understand what is needed.

We also *should not* replicate items like defining Unicode in our wiki: pointers to the Unicode consortium and to the wikipedia article are much more informative. jg 19:57, 27 April 2007 (EDT)

Meetings

June 19 2007

Agenda

  • How to handle translation on the wiki
  • How to localize sugar and its core activieis
  • How to ask for / help with localizing an activity
  • Where to sign up for information / discussion about l10n and translation

highlights from #olpc-l10n

Areas of l10n:

Some results and/or directives:

  • It would be convenient (hint) for users to tag themselves (in their pages) with the appropriate Category:User languages
    • the tagging could be extended to include other 'user skillsets' like coder, artist, educator, etc.
    • should be kept simple so as to not overload with structure that hinders or overloads newbies
  • New 'guidelines' (akin to HIG) need to be developed:
  • Develop
  • Need to raise Category:Developers awareness to the issue or i18n & l10n.
    • Strings are not the only thing that can/needs to be l10n—images, icons, etc. should also be considered part of the deal (they can be localized by extracting their URLs into a PO file too)
    • Given the 'cryptic' nature of PO files used, it could be worthwhile to explore the possibilities that the Develop activity (particularly when used through the 'gear' Key viewsource.jpg key) be capable of transparently embeding and extracting the strings to-from the PO files. (must coordinate with User:Orospakr on how to proceed)
    • Stock on resources about the i18n & l10n process—some links were added to Translating#resources
    • The aim is to produce a simple set of guidelines (with examples) on how-to get everything ready for l10n.

Some pointers

Resources for choosing names

I found these two "dictionaries" useful when trying to find a name which translated well: MitchellNCharity 12:03, 20 June 2007 (EDT)