-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Peter Mann escribió:
[...]
>
>> You can export po files from Rosetta too. AFAIK access using a bzr repo
>> is a long term goal of Rosetta.
>
> yes, i know about exporting po files, i used export sometime - but why
> is so hard to provide clean
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sebastian Heinlein escribió:
> Am Dienstag, den 23.01.2007, 02:10 +0100 schrieb Frans Pop:
>> On Tuesday 23 January 2007 01:53, Javier Fernández-Sanguino Peña wrote:
>>> That's certainly a flawed assumption. If you are providing translators
>>> an am
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter Mann wrote:
> ok ... but IMHO this is wrong direction: from GUI to backend ...
> i prefer good backend (e.g. svn, bzr or something similar) and then
> additional GUI ...
Agreed! Rosetta bridged a huge gap that existed between users who
wanted
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/23/2007 04:07 AM, Sebastian Heinlein wrote:
>>Rosetta is all about Ubuntu and not about the general Open Source Software
>>_community_.
>
> This is right - currently. But a better review and upstream
> collaboration infrastructure is in work.
Hi!
* Sebastian Heinlein <[EMAIL PROTECTED]> [2007-01-22 21:15]:
> Am Samstag, den 20.01.2007, 16:16 +0100 schrieb Peter Mann:
>> i don't like Rosetta all along - so why we must translate same strings
>> twice ??? why Rosetta translations doesn't propagate back to upstream
>> package sour
On Tue, Jan 23, 2007 at 09:47:18AM +0100, Danilo Šegan wrote:
> Today at 6:37, Peter Mann wrote:
>
> > every package should use any primary system for translation: Rosetta or
> > Pootle or svn/cvs or only http po download + wishlist bug report -
> > depending on author choice ... but every package
Hi Peter,
Today at 6:37, Peter Mann wrote:
> every package should use any primary system for translation: Rosetta or
> Pootle or svn/cvs or only http po download + wishlist bug report -
> depending on author choice ... but every packager/maintainer and
> translator should know about this translat
Am Dienstag, den 23.01.2007, 02:10 +0100 schrieb Frans Pop:
> On Tuesday 23 January 2007 01:53, Javier Fernández-Sanguino Peña wrote:
> > That's certainly a flawed assumption. If you are providing translators
> > an amicable interface to avoid handling technical details you cannot
> > expect them t
On Mon, Jan 22, 2007 at 09:15:25PM +0100, Sebastian Heinlein wrote:
> Both the upstream author (mvo) and the Debian package maintainer missed
> to import the latest translations into the source. I will send mvo a
> message or import the latest translation from Rosetta or do it myself.
> About Debia
On Tuesday 23 January 2007 01:53, Javier Fernández-Sanguino Peña wrote:
> That's certainly a flawed assumption. If you are providing translators
> an amicable interface to avoid handling technical details you cannot
> expect them to push things on to upstream.
Beautiful analysis of why Rosetta is
On Mon, Jan 22, 2007 at 09:15:25PM +0100, Sebastian Heinlein wrote:
> It is the job of the corresponding translation team to push their
> changes upstream or the job of upstream to review and import them. I
> think that every Debian translation team knows of Rosetta. But I am not
> sure if all of t
Am Samstag, den 20.01.2007, 16:16 +0100 schrieb Peter Mann:
> Heyaaa!!!
>
> i was negativelly surprised about translation status of some packages,
> e.g. update-notifier ..
>
> i'm just testing Etch on desktop, so i plan to use Debian Etch - and
> install it for users, but some applications doesn
> Actually, as D-I i18n coordinator, I don't care about work done in
> Rosetta for languages we already support in Debian. That means indeed
> nearly all supported languages.
>
> The only exception to this is, on their request, the translations from
> the Kurdish team because they asked explicitel
> so now i can (and i want) update sk.po file and file wishlist bug report
> against update-notifier and i know, maybe it's late because of frozen Etch
>
> i don't like Rosetta all along - so why we must translate same strings
> twice ??? why Rosetta translations doesn't propagate back to upstream
Heyaaa!!!
i was negativelly surprised about translation status of some packages,
e.g. update-notifier ..
i'm just testing Etch on desktop, so i plan to use Debian Etch - and
install it for users, but some applications doesn't have translated
messages for Slovak language
dapper: update-notifier
15 matches
Mail list logo
