Christian, Denis,
I see the localisation infrastructure as a tool of the translator (or
localisation manager for a package in a language). If the translator has
commit right, he can give the tool the data to do automatic commits,
instead of doing them manaully. Only the person that has the rig
> I am still puzzled. Imagine for instance that French translators of
> OpenOffice are willing to use this infrastructure, whereas Dutch
> are not interested. Will this situation be allowed?
Well, it is quite likely to happen, yes, so my first reaction is to
say that, yes, the system should all
On Fri, Jun 09, 2006 at 08:18:31AM +0200, Christian Perrier wrote:
> raw answers...
>
> > Who does decide which files are being imported?
>
> I would say the team who administers the server (what we defined as
> "Administrators" in the infrastructure targets). This is of course
> coordinated with
raw answers...
> Who does decide which files are being imported?
I would say the team who administers the server (what we defined as
"Administrators" in the infrastructure targets). This is of course
coordinated with the upstream itself, to determine what notification
method they prefer.
An alte
On Wed, Jun 07, 2006 at 08:52:13AM +0200, Christian Perrier wrote:
> > If the content we're merging is free, there's no problem show this to the
> > reviewer and let him accept or refuse the translation. It's way simpler to
> > do
> > than rewrite everything again. If the translation was overwritt
On 6/7/06, Javier Fernández-Sanguino Peña <[EMAIL PROTECTED]> wrote:
On Tue, Jun 06, 2006 at 03:21:45PM -0300, Gustavo Franco wrote:
> Nice, thanks. While we're at this subject, what's your view on the
> Ubuntu language packs? Are we going to extract the translations from
> the packages creating
On Tue, Jun 06, 2006 at 03:21:45PM -0300, Gustavo Franco wrote:
> Nice, thanks. While we're at this subject, what's your view on the
> Ubuntu language packs? Are we going to extract the translations from
> the packages creating language packs? It has pros and cons, and
> the best thing i see is the
> They did with the wiki content, probably they will do the same thing
> or something similar with Rosetta translations. The question is if it
> will be free.
Everything related to Rosetta is currently assumed by me of *not*
being free.
> >The real problem, is that we have reports of peo
"Gustavo Franco" <[EMAIL PROTECTED]> writes:
> Nice, thanks. While we're at this subject, what's your view on the
> Ubuntu language packs? Are we going to extract the translations from
> the packages creating language packs? It has pros and cons, and
> the best thing i see is the possibility to ke
"Gustavo Franco" <[EMAIL PROTECTED]> writes:
> On 6/6/06, Otavio Salvador <[EMAIL PROTECTED]> wrote:
>> "Gustavo Franco" <[EMAIL PROTECTED]> writes:
>>
>> > Agreed. Btw, it would be better keep Etch package descriptions updated
>> > during its support cycle, but i think it's impossible with the
>>
"Gustavo Franco" <[EMAIL PROTECTED]> writes:
> Agreed. Btw, it would be better keep Etch package descriptions updated
> during its support cycle, but i think it's impossible with the
> infrascture we've, right ?
No. We already have the previous working structure all up and
running. What we want t
On 6/6/06, Denis Barbier <[EMAIL PROTECTED]> wrote:
On Tue, Jun 06, 2006 at 02:04:09PM -0300, Gustavo Franco wrote:
> You wrote a good overview about the possible workflow, but i still
> miss exactly how we (or the coordinators) will merge from third
> parties (eg: Rosetta) and most important, ho
On Tue, Jun 06, 2006 at 02:04:09PM -0300, Gustavo Franco wrote:
> You wrote a good overview about the possible workflow, but i still
> miss exactly how we (or the coordinators) will merge from third
> parties (eg: Rosetta) and most important, how we will push our
> translations back to the upstream
On 6/6/06, Felipe Augusto van de Wiel (faw) <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/06/2006 04:02 PM, Gustavo Franco wrote:
> On 6/6/06, Felipe Augusto van de Wiel (faw) <[EMAIL PROTECTED]>
> wrote:
>> On 06/06/2006 02:04 PM, Gustavo Franco wrote:
>> > On 6
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/06/2006 04:02 PM, Gustavo Franco wrote:
> On 6/6/06, Felipe Augusto van de Wiel (faw) <[EMAIL PROTECTED]>
> wrote:
>> On 06/06/2006 02:04 PM, Gustavo Franco wrote:
>> > On 6/6/06, Christian Perrier <[EMAIL PROTECTED]> wrote:
[...]
>> > I think
On 6/6/06, Felipe Augusto van de Wiel (faw) <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[ Adding -i18n ]
On 06/06/2006 02:04 PM, Gustavo Franco wrote:
> On 6/6/06, Christian Perrier <[EMAIL PROTECTED]> wrote:
>> (this report is a little bit late as it took time to f
On 6/6/06, Otavio Salvador <[EMAIL PROTECTED]> wrote:
"Gustavo Franco" <[EMAIL PROTECTED]> writes:
> On 6/6/06, Otavio Salvador <[EMAIL PROTECTED]> wrote:
>> "Gustavo Franco" <[EMAIL PROTECTED]> writes:
>>
>> > Agreed. Btw, it would be better keep Etch package descriptions updated
>> > during it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[ Adding -i18n ]
On 06/06/2006 02:04 PM, Gustavo Franco wrote:
> On 6/6/06, Christian Perrier <[EMAIL PROTECTED]> wrote:
>> (this report is a little bit late as it took time to finalize
>> it...sorry for the inconvenience)
>>
>> The work on internatio
On 6/6/06, Otavio Salvador <[EMAIL PROTECTED]> wrote:
"Gustavo Franco" <[EMAIL PROTECTED]> writes:
> Agreed. Btw, it would be better keep Etch package descriptions updated
> during its support cycle, but i think it's impossible with the
> infrascture we've, right ?
No. We already have the previ
On 6/6/06, Christian Perrier <[EMAIL PROTECTED]> wrote:
(this report is a little bit late as it took time to finalize
it...sorry for the inconvenience)
The work on internationalisation (i18n) and localisation (l10n) at
Debconf6 has been particularly interesting and productive.
(...)
You wrote
20 matches
Mail list logo
