Translation deadline of LibreOffice 3.3.2 RC1

l10n
#1

Hi,

We are going to tag 3.3.2rc1 on Monday March 7 and create
libreoffice-3-3-2 branch at the same time. AFAIK there were no new
strings introduced between 3.3.1 and 3.3.2.

I'll take updated translations from Pootle on Sunday, March 6, during
the day. Please update your translations - if necessary - by Sunday morning.

Thanks,
Andras

#2

Hi,

AFAIK there were no new
strings introduced between 3.3.1 and 3.3.2.

so the sdf remains the same as for 3.3? I did some changes in the
translations (corrected found errors), so I guess it is possible to send in
a corrected Slovenian sdf?

I hope the updated Slovenian dictionary pack made it into 3.3.2.

Thanks,
m.

#3

Hi,

AFAIK there were no new
strings introduced between 3.3.1 and 3.3.2.

so the sdf remains the same as for 3.3? I did some changes in the
translations (corrected found errors), so I guess it is possible to send in
a corrected Slovenian sdf?

Sure, corrections are welcome.

I hope the updated Slovenian dictionary pack made it into 3.3.2.

I did not forget.

Andras

#4

In data martedì 01 marzo 2011 13:54:55, Andras Timar ha scritto:

Hi,

We are going to tag 3.3.2rc1 on Monday March 7 and create
libreoffice-3-3-2 branch at the same time. AFAIK there were no new
strings introduced between 3.3.1 and 3.3.2.

Hi

will there be any updates in this days? Our strings (italian) are translated,
except for extensions ones.

Regards,

#5

Hi,
We've completed translating OpenOffice.org Writer in OpenOffice pootle. Do
you use the latest translations from OpenOffice pootle?

Hossein

#6

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

#7

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

#8

Hi Hossein,

I'm sorry for the confusion. Due to popular demand we set up
"LibreOffice 3.3.x – Merged Help" and "LibreOffice 3.3.x – Merged UI"
projects in Pootle some time ago. 26 languages are contributing to
these merged projects, not only en_GB. I'll migrate Persian later
today and Rimas will upload it.

Thanks,
Andras