[Plone-conference] Templer Sprint - i18n script
Harald Friessnegger
harald at webmeisterei.com
Mon Oct 15 11:42:14 UTC 2012
hi mark
the script attached more or less does the same things but takes slightly different approaches
* it does not need the language list ( LANGUAGES="en fi de").
as you're crating the folder structure with templer anyway this makes the script less error-prone:
creating a news language with templer and not adding it to the list here would result in new ids not beeing synced to this language's po file
* as i personally have a policy, types and them package in our comany's projects there is support for collecting msgids of different packages
into one central package.
i think this use-case is very common for other developers too
there might be more elegant solutions for this. plone has to do the same for plone.app.locales, so there might already be a more generic solution for this
* it also uses the i18n/manual.pt to sync new translations for the plone domain (i know, the i18n directory is not needed for this anymore, we can put these into lang_code/LC_MESSAGES/plone.po now.
however, the script could/should offer a soluton to extract and sync translations for the plone domain, too. so we can translate document actions and the like.
regards and have a nice day
harald
Am Montag, 15. Oktober 2012, 12:48:40 schrieb Mark van Lent:
> On 10/14/12 10:30 AM, Cris Ewing wrote:
> > A quick summary of the ongoing templer sprint here at the plone conference:
> >
> > We split into four teams. Each team is tackling an individual goal.
> >
> > Team 1 is moving localcommands from the old ZopeSkel to the new templer packages. They have completed work on an i18nlocale localcommand which properly sets up internationalization for your package. The command also supplies a script which can be used to extract, compile and update your translations. A second localcommand has been added to create upgrade steps and setuphandler code for your package.
> Actually... The current i18nlocale command is just a copy of the version
> from ZopeSkel; the build script is still in the works. I plan to commit
> an enhanced version of the script made by Mikko
> (http://collective-docs.readthedocs.org/en/latest/i18n/internationalisation.html#managing-po-files).
> I just need to clean it up a bit and make it somewhat more generic
> before I can safely add it to the i18nlocale command.
>
> Sorry I did not report this more clearly when I left the sprint...
>
> Cheers,
> Mark van Lent
> _______________________________________________
> Plone-conference mailing list
> Plone-conference at lists.plone.org
> http://lists.plone.org/mailman/listinfo/plone-conference
>
--
Webmeisterei GmbH - Büro für Netzfragen
Tel: +43 5572 908877, Fax: +43 5572 908877-66
Steinebach 18, A-6850 Dornbirn
http://webmeisterei.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: i18n.sh
Type: application/x-shellscript
Size: 1104 bytes
Desc: not available
URL: <http://lists.plone.org/pipermail/plone-conference/attachments/20121015/a9c6099b/attachment-0001.bin>
More information about the Plone-conference
mailing list