Hi,
Roger Ineichen wrote:
Note, if you run the i18nextract script, all module must be there like in a running application. You can't only use the files which will
contain locales. Also modules which this packages import from must be there.
That should not be necessary I think. At least
On Thursday 08 May 2008, Roger Ineichen wrote:
That should not be necessary I think. At least I am not used to it.
When I use i18ndude for making pot/po files for a Plone
product/package and I have from Products.CMFPlone import something
in a file, then this import does not really take
Hi Stephan
Betreff: Re: AW: [Zope-dev] Re: AW: Re: AW: Re: New i18n
locale extraction concept
[...]
Probably it works in some ues case but for sure not in all.
Let's give a sample. If you define a interface like
foo = zope.schema.Choice(
title=_('Title'),
vocabulary
Hi Maurits
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Im Auftrag von Maurits van Rees
Gesendet: Donnerstag, 8. Mai 2008 18:55
An: zope-dev@zope.org
Betreff: [Zope-dev] Re: AW: Re: AW: Re: New i18n locale
extraction concept
Stephan Richter, on
Hi Maurits
Betreff: [Zope-dev] Re: AW: Re: AW: Re: New i18n locale
extraction concept
[...]
Packages are used for extract locales from. That could be very
different then the egg setup. The i18nextrac.py will only deep into
this packages, but probably this packages will need different
