Re: [libreoffice-l10n] Translation deadline of LibreOffice 3.3.2 RC1

Hi,
I'm a little confused. At first I suggested to import all strings from
LibreOffice into Pootle, even OO specific strings. At the time I was
told that we should only translate LibO specific strings. So we set up
Persian in OpenOffice Pootle and started translating common strings
there.

I think merging all strings and starting a new project on LibreOffice
Pootle is a good idea. Then we can translate strings in one place. It
seems that en_GB LibO uses this approach.

Hossein

On 3/3/11, Andras Timar <timar74@gmail.com> wrote:
> 2011/3/3 Hossein Noorikhah <hossein.ir@gmail.com>:
> >  Hi,
> > We've completed translating OpenOffice.org Writer in OpenOffice pootle. Do
> > you use the latest translations from OpenOffice pootle?
> >
> > Hossein
>
> Hi Hossein,
>
> No, we don't take translations automatically from OpenOffice.org
> Pootle. We use our own Pootle where we can set-up a project for your
> language, too. You can migrate your OOo translations to LibreOffice by
> following Sophie's article
> (http://wiki.documentfoundation.org/Mergingl10n). Alternatively, I can
> do the migration for you but then it is up to you to keep OOo and
> LibreOffice translations in sync. As time passes by, the differences
> between OOo and LibreOffice will become larger. As a rule of thumb we
> always take what is in our Pootle.
>
> Thanks,
> Andras
>
> --
> Unsubscribe instructions: E-mail to l10n+help@libreoffice.org
> List archive: http://listarchives.libreoffice.org/www/l10n/
> *** All posts to this list are publicly archived for eternity ***

-- 
Unsubscribe instructions: E-mail to l10n+help@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/l10n/
*** All posts to this list are publicly archived for eternity ***