[ANNOUNCE] Start of LibreOffice 4.0 translation

l10n
#1

Hi,

If all goes well, I'll upload LibreOffice 4.0 po files to Pootle this
weekend. I will migrate your LibreOffice 3.6 translations that I find
in Pootle. I'll take down Pootle during the update. LibreOffice 3.6
translations will be moved to new libo36x_ui and libo36x_help projects
(so metadata, such as suggestions cannot be preserved). libo_ui and
libo_help projects will have LibreOffice 4.0 files. It is the same
that I did for 3.5 -> 3.6.

LibreOffice 4.0 is to be released in February, 2013, and it is still a
moving target from the localization point of view.

Best regards,
Andras

#2

Hi Andras,

2012.11.15 17:21, Andras Timar wrote:

If all goes well, I'll upload LibreOffice 4.0 po files to Pootle this
weekend. I will migrate your LibreOffice 3.6 translations that I find
in Pootle. I'll take down Pootle during the update. LibreOffice 3.6
translations will be moved to new libo36x_ui and libo36x_help projects
(so metadata, such as suggestions cannot be preserved). libo_ui and
libo_help projects will have LibreOffice 4.0 files. It is the same
that I did for 3.5 -> 3.6.

Perhaps fully cloning projects (with suggestions and other stuff) would be a valid feature request for Pootle? :slight_smile:

Rimas

#3

Hi Rimas,

Hi Andras,

2012.11.15 17:21, Andras Timar wrote:

If all goes well, I'll upload LibreOffice 4.0 po files to Pootle this
weekend. I will migrate your LibreOffice 3.6 translations that I find
in Pootle. I'll take down Pootle during the update. LibreOffice 3.6
translations will be moved to new libo36x_ui and libo36x_help projects
(so metadata, such as suggestions cannot be preserved). libo_ui and
libo_help projects will have LibreOffice 4.0 files. It is the same
that I did for 3.5 -> 3.6.

Perhaps fully cloning projects (with suggestions and other stuff) would be a
valid feature request for Pootle? :slight_smile:

Yes, it would. I wanted to clone last time, and I learned that it was
not possible. But I forgot this feature request and did not mention it
to Dwayne at LibOCon. I was convinced that maintaning two branches
with suggestions may be a pain for most of the teams. I think about
the stable branch as it is for fixing annoying translation bugs only,
and the newer branch is for the real work. If a team could not finish
3.6.x translations by now, maybe it's time to go for 4.0 instead. So,
I would not mind, if cloning was possible, but I would give higher
priority to some other feature requests. What do others think?

Andras

#4

I would ask anyway, but state it has lower priority for us. Worst case, it
will just be an item on their wish list.

And I think that after we finish with the 3.6.4 update, there's no point of
continuing translation that branch, and focus should be moved completely to
the 4.0 branch.

Kaplan

#5

Hi,

Hi Andras,

If all goes well, I'll upload LibreOffice 4.0 po files to Pootle this
weekend. I will migrate your LibreOffice 3.6 translations that I find
.............
LibreOffice 4.0 is to be released in February, 2013, and it is still a
moving target from the localization point of view.

Is it an urgent matter? We are working very hard to finish the full
translation of LibreOffice to Turkish, we are on %96 on help content
and there are only 18K words left. We need ~2 weeks to finish it.
Having 2 branches doubles the work for untranslated work.

I think it will be better to postpone it for everybody to prepare for
the new branch.

Best regards,
Zeki

#6

Most strings are still the same, so you can translate in one branch,
download the files and upload them in the other branch. This doesn't
work 100% (it for example can't overwrite fuzzy strings with unfuzzied
ones), or didn't in 2.1.6, perhaps it's fixed in the new 2.2, I didn't
try yet. It's a pity pootle doesn't support translation propagation
between branches like some other online translators, for example
WebLate.

#7

It's a pity pootle doesn't support translation propagation

between branches like some other online translators, for example
WebLate.

I believe that is already available in development versions of Pootle,
perhaps not the current stable though.

cjl

#8

Hi Zeki,

Hi,

Hi Andras,

If all goes well, I'll upload LibreOffice 4.0 po files to Pootle this
weekend. I will migrate your LibreOffice 3.6 translations that I find
.............
LibreOffice 4.0 is to be released in February, 2013, and it is still a
moving target from the localization point of view.

Is it an urgent matter? We are working very hard to finish the full
translation of LibreOffice to Turkish, we are on %96 on help content
and there are only 18K words left. We need ~2 weeks to finish it.
Having 2 branches doubles the work for untranslated work.

I think it will be better to postpone it for everybody to prepare for
the new branch.

I have a few reasons to do it now. New po/pot files will be generated
with help of new l10n tools in feature/killsdf branch. I want to merge
feature/killsdf before the feature freeze, which is in 2 weeks from
now. If there are problems with new l10n tools, we need to find them
as soon as possible. Also, many teams finished work on 3.6 long ago,
and want to start on 4.0. Beta1 usually comes with translations (Week
49, Dec 3 - Dec 9, 2012), and I'm sure, that people want to test it.

You can either leave 3.6 at 96% which is great and complete help
translation in 4.0, or you can finish 3.6 translations and I'll help
you to migrate your translations to 4.0. If you need 2 weeks to
complete, the your earlliest target could be 3.6.5 in Week 5, Jan 28 -
Feb 3, 2013, while 4.0.0 is due to Week 6, Feb 4 - Feb 10, 2013.

Best regards,
Andras