On 03/09/2005, at 10:22 PM, Christian Perrier wrote:
This message is mostly intended for D-I developers, but translators
might want to know how things are goind on.
I found it interesting, and the list of priority packages is very
useful to me at this point. I also think it's a great idea t
I already posted some comments on the list proposed by Christian on
#d-boot, but probably just posting a counter-proposal to the list makes
more sense.
I feel this order keeps related things together a bit better; I've also
moved some "expert mode" udebs a bit down in the order.
I've added some
This message is mostly intended for D-I developers, but translators
might want to know how things are goind on.
Up to now, any package in the D-I SVN tree which included a
debian/po/templates.pot file was automagically added to the
"localization framework", ie the master files.
The dr
Quoting Martin Quinson ([EMAIL PROTECTED]):
> We could design an opt-in mecanism where packager can use tools to provide
> their package to translators and grab translations in a semi-automated and
> very easy way.
.../...
All what Martin wrote may be considered my own point of view, too..:-)
On Wed, Apr 07, 2004 at 01:55:20PM +0200, Nikolai Prokoschenko wrote:
> On Wed, Apr 07, 2004 at 01:16:44PM +0200, cobaco (aka Bart Cornelis) wrote:
> > > > pull the .pot and .po files from the package cvs/svn repository
> > > > wherever possible so things can be translated before they get to
> > >
Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]):
> Couldn't i18n related developers push the idea that m17n/i18n/l10n
> whatever is possible at first should be set higher in the release
> criteria priorities ?
Please don't unveil the topics of my Debconf4 talk in advance..:-)
Martin a écrit:
The arguments to convince the packager to put this file may be:
- gain someone to forward translation bugs to
- integrating translation is as simple as calling a script (instead of
dealing with bugs)
- the fact that for now, only friendly package are handled by the svn
since
On Wed, Apr 07, 2004 at 12:55:38AM +0200, Denis Barbier wrote:
> On Tue, Apr 06, 2004 at 03:40:16PM -0700, Martin Quinson wrote:
> > On Tue, Apr 06, 2004 at 10:35:30PM +0200, Denis Barbier wrote:
> [...]
> > > Consider a simple example: package foo-1.0-1 contains a xx.po file,
> > > which is not up
Quoting Nikolai Prokoschenko ([EMAIL PROTECTED]):
> PROBLEMS: There is no way for a translator (who is usually not a geek or
> maybe even not a user) to get into the translation process easily. One
> possibility is to read tons of README's, man pages and help files to at
> least understand how he
Quoting Nikolai Prokoschenko ([EMAIL PROTECTED]):
> PROBLEMS: Upstream changes templates. We'd get to translate them only
> _after_ the initial upload of the new version. Any ideas?
Currently, none on my side. Mostly because I think that the l10n
infrastructure has to deal with a strong fact in D
First of all, let me just announce that I will make several followups
to this mail probably, because it drives several topics, and
discussing all together may not be easy..:-)
> PRESENT: The localization effort is currently desasterous. There are
> several tools to use, many points of entry (whic
On Wed, Apr 07, 2004 at 01:16:44PM +0200, cobaco (aka Bart Cornelis) wrote:
> > > pull the .pot and .po files from the package cvs/svn repository
> > > wherever possible so things can be translated before they get to
> > > unstable.
> >
> > This would mean a central repository for the packaging fil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2004-04-07 12:56, Nikolai Prokoschenko wrote:
> On Wed, Apr 07, 2004 at 10:22:12AM +0200, cobaco (aka Bart Cornelis)
wrote:
> > > PROBLEMS: Upstream changes templates. We'd get to translate them only
> > > _after_ the initial upload of the new vers
On Wed, Apr 07, 2004 at 10:22:12AM +0200, cobaco (aka Bart Cornelis) wrote:
> > PROBLEMS: Upstream changes templates. We'd get to translate them only
> > _after_ the initial upload of the new version. Any ideas?
> pull the .pot and .po files from the package cvs/svn repository wherever
> possible
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2004-04-06 18:23, Nikolai Prokoschenko wrote:
> 1. Debconf templates, which contain questions to the users
> 1. This (as well as 5.) can be extracted from unstable with the help of
> Denis Barbier's scripts (/materials/*)
> PROBLEMS: Upstream chan
Le mercredi 07 avril 2004 Ã 00h55 (+0200), Denis Barbier Ãcrivait :
> > New package version:
> > msgcat --use-first svn.po pkg.po > svn.po
> Maintainer changes are lost here, this is not good communication between
> translators and maintainers ;)
Is there a way to "--use-first and merge others us
On Tue, 6 Apr 2004 22:35:30 +0200
[EMAIL PROTECTED] (Denis Barbier) wrote:
> On Tue, Apr 06, 2004 at 06:23:20PM +0200, Nikolai Prokoschenko wrote:
> [...]
> > BACKLINE: The package generating scripts could be patched so that
> > they query the database (which could be later generated from SVN
> >
On Tue, Apr 06, 2004 at 03:40:16PM -0700, Martin Quinson wrote:
> On Tue, Apr 06, 2004 at 10:35:30PM +0200, Denis Barbier wrote:
[...]
> > Consider a simple example: package foo-1.0-1 contains a xx.po file,
> > which is not up-to-date. Its translator commits a new version to the
> > central SVN re
On Tue, Apr 06, 2004 at 10:35:30PM +0200, Denis Barbier wrote:
> On Tue, Apr 06, 2004 at 06:23:20PM +0200, Nikolai Prokoschenko wrote:
> [...]
> > BACKLINE: The package generating scripts could be patched so that they
> > query the database (which could be later generated from SVN data) for
> > tra
On Tue, Apr 06, 2004 at 06:23:20PM +0200, Nikolai Prokoschenko wrote:
[...]
> BACKLINE: The package generating scripts could be patched so that they
> query the database (which could be later generated from SVN data) for
> translations automatically and put them into place. Should be discussed
> fu
Hello!
Well, I just thought I'd summarize what we have so far, including my own
ideas for the said framework. This message is meant as a request for
comments and as a starting point for the discussion.
PRESENT: The localization effort is currently desasterous. There are
several tools to use, many
21 matches
Mail list logo
