Pootle: LibreOffice 5 or Master?

l10n
#1

Hi All

I noticed the new folders for version 5 in Pootle, but I'm working on some revisions on help in master.

Where will the strings for the update of next versions 5.x be picked from?

Thanks and regards,

#2

Hi Valter, *,

I noticed the new folders for version 5 in Pootle, but I'm working on some
revisions on help in master.

As we have the internal translation memory, the strings you translated
on master should be offered as suggestion in the 5.0 project.

Where will the strings for the update of next versions 5.x be picked from?

They will be taken from the libo50_ui and libo50_help projects.

ciao
Christian

#3

So version 5.1 will be taken from libo50_ui and not from libo_ui (aka master)?

Mihovil

17.08.2015 u 13:33, Christian Lohmaier je napisao/la:

#4

So version 5.1 will be taken from libo50_ui and not from libo_ui (aka master)?

As far as I understand, if you work in libo_ui (master), your modifications should be replied in libo50_ui

Mihovil

17.08.2015 u 13:33, Christian Lohmaier je napisao/la:

Where will the strings for the update of next versions 5.x be picked from?

They will be taken from the libo50_ui and libo50_help projects.

ciao
Christian

Ciao

#5

This is an interesting topic.

Since the Albanian translation is incomplete (less than 100%), I have
decided that the best thing is to work on libo50_ui, until it gets
completed. After it is completed, we can switch to the master branch
(libo_ui).

Is this a correct workflow?
Do the translations made to branch 5.0 appear to the master branch as well?

Thanks,
Dashamir

#6

Hi Mihovil, *,

So version 5.1 will be taken from libo50_ui and not from libo_ui (aka
master)?

No, I took the question regarding the "the next versions 5.x" as
questions for 5.0.1, 5.0.2,....

LibreOffice 5.1 will be branched off from master branch, so that will
take master translation. But that is for next year.

5.0.x will all be taken from 50 projects, and master will be used for
master, and that at some point will be branched-off to create the
5.1.x versions. But that is for the far future.

If you want end-users to have translated version, focus on the
libo50_* project (and libo44_*, however there will only be one more
release on 4.4 codeline, so only makes sense to work on that if you
have high completion rate or if you translate both)

ciao
Christian

#7

Hi Dashamir, *,

This is an interesting topic.

Since the Albanian translation is incomplete (less than 100%), I have
decided that the best thing is to work on libo50_ui, until it gets
completed. After it is completed, we can switch to the master branch
(libo_ui).

Is this a correct workflow?

Yes, that's correct workflow. Focus on what end-users will get, and
only then focus on the other stuff.

Do the translations made to branch 5.0 appear to the master branch as well?

Not automatically.

If the amount of untranslated strings is not large, you can use the
builtin translation memory and after having translated just accept the
suggestion of the translation that is offered from the 50 project.

If you translated huge amount of strings, then you can request a
offline merge of the strings that does that. (or can do that yourself
and upload the changed files)

ciao
Christian