On Tue, Feb 22, 2005 at 03:54:12PM +0100, Fabio Tranchitella wrote:
> Il giorno lun, 21-02-2005 alle 21:57 +0100, Jens Nachtigall ha scritto:
>
> > Nice to hear that there might be a solution at the horizon. afaik,
> > plone2 is in sarge now, so maybe you could do us translators a very big
> > f
Il giorno mar, 22-02-2005 alle 07:26 +0100, Christian Perrier ha
scritto:
> The "problem" here is finding good "generic" formulations. The example
> above shows the problem : as long as the template is generic, you
> cannot use a sentence like "Please choose a password for 'whatever
> needs a passw
Il giorno lun, 21-02-2005 alle 21:57 +0100, Jens Nachtigall ha scritto:
> Nice to hear that there might be a solution at the horizon. afaik,
> plone2 is in sarge now, so maybe you could do us translators a very big
> favour and switch to that zope-common package mechanism. anyway, even a
> pack
Quoting Fabio Tranchitella ([EMAIL PROTECTED]):
> This sounds really interesting, can you please tell me more about it?
> If you agree, I'll be glad to help you with that.
Nothing really hard core, indeed.
The idea isĀ :
-build a package with only debconf templates (and translations)
Template
Hi Fabio,
> I know that including all those templates in all my zope packages
> isn't the best solution, but my main goal was to include Plone 2 in
> sarge and I hadn't enough time to think about a better solution for
> translators.
>
> Now that the packages are available, I'm wondering about how
Hi,
Christian Perrier:
> For sure, at this moment, this is a real PITA for translators. I've
> already indicated to Fabio that he may at least merge the PO files and
> use the gettext tools to merge the translations together.
> Indeed Fabio could have probably used variable substitution in the
> z
Quoting Jens Nachtigall ([EMAIL PROTECTED]):
> Hi,
>
> I'm a debian-l10n-german translator and noticed that most zope-*
> packages use almost the same debconf template (only the package name in
> them is different). There are plenty of them:
> http://www.debian.org/intl/l10n/po-debconf/pot#zope-
On 02/19/05 18:50, Lior Kaplan wrote:
Why not do a package-name variable, and have the same POT for all
packages? Is that possible?
Sure, I guess there are many ways of doing it. One could be to filter
the final templates file (after dh_installdebconf) with sed or something
similar. The problems
Why not do a package-name variable, and have the same POT for all
packages? Is that possible?
> Hi,
>
> I'm a debian-l10n-german translator and noticed that most zope-*
> packages use almost the same debconf template (only the package name in
> them is different). There are plenty of them:
> http:
Hi,
I'm a debian-l10n-german translator and noticed that most zope-*
packages use almost the same debconf template (only the package name in
them is different). There are plenty of them:
http://www.debian.org/intl/l10n/po-debconf/pot#zope-archetypes
Couldn't the translation of these be automate
10 matches
Mail list logo