Re: Debian Debconf Translation proposal ( again )
On Wed, 7 Jan 2004 09:55:29 +0000
Colin Watson <email@example.com> wrote:
> On Wed, Jan 07, 2004 at 10:43:48AM +0100, Tim Dijkstra wrote:
> > On Tue, 6 Jan 2004 23:01:20 +0000
> > Colin Watson <firstname.lastname@example.org> wrote:
> > > On Tue, Jan 06, 2004 at 10:28:13PM +0100, Dominique Devriese
> > > wrote:
> > > > 2. The translators don't try to get their work included in
> > > > Debian
> > > > packages. Instead they provide one package of their own,
> > > > that they can occasionally release in sid if they want
> > > > to.
> > >
> > > Didn't we do this at great length a year or two ago when the DDTP
> > > started up?
> > In the end, also using the ddtp, package maintainers still have to
> > include the translations in their package. For every additional
> > translation is some language there has to be a new release (you can
> > update multiple languages at one of course). I agree it would be
> > better if we could come up with a system which decouples release of
> > the binary with that of the translation.
> I don't think this would be better. Ultimately, we have to get the
> things to users, and our tried-and-tested means for doing so is
> through.debs (not one .deb per little bit of text, one .deb per
> *package*). The text in question is used when the .deb is being
> configured, and therefore needs to be available at the right time; if
> you propose any decoupling then you must consider dependencies, and
> that turns into a nightmare very quickly. Let's keep it simple.
I was not really thinking of extra debs, but something entirely
different (tm). Maybe we could have a separate piece (next to
data.tar.gz) in the debs which would then contain all translations.
Then translators could upload their stuff to some server which would
put it in the debs.
I know this is a rather dramatic change to the deb format and debian
infrastructure and will therefore have a very small chance of ever being
realised, but I think the idea is good...