I forgot to mention that in order to better handle translations I think we need to do 3 things: - add support for importing languages in the XAR import screen (listing all languages available in a XAR and offering checkboxes to choose them) - add a document resource bundle component that observes document changes and adds document resource bundles to $msg (we need a class for document resource bundle for this) - rework some app translations so that we use translations instead of key/values.
Thanks -Vincent On Mar 23, 2009, at 11:25 AM, Vincent Massol wrote: > Hi devs, > > We need to define a strategy for better handling translations. I've > had a call with Guillaume and Jean-Vincent and here's the process > we'd like to propose: > > * One person is in charge of http://l10n.xwiki.org/. This means > monitoring the work there, coordinating validation of key values and > ensuring validated translations are incorporated in the source tree. > Guillaume is willing to take that role for now. > * The XE release manager has the responsibility of taking the > validated keys on l10n.xwiki.org and committing them during the > Milestone 2 dev (before the RC1). > * The l10n manager should ping the release manager whenever there > are translated and validated keys ready to be incorporated or if > there have been important changes to be included in the release > after M2 has been released. > * The l10n manager should test XE and the applications after the > keys have been applied to ensure quality. Basically the l10n manager > is responsible for the quality of translations in general. > > Here's my +1 > > Thanks > -Vincent > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
