Request for breaking string freeze

l10n
#1

Dear Sophie and l10n teams,

I am writing to ask for approval of backporting a patch to 6-4 branch that breaks string freeze.  The patch is about a new feature in 6.4, "Full-sheet preview/export" in Calc [1], specifically about how it's is shown in the "PDF Options" export dialog.

Recently there was a bug report (#129714, [2]) that asks for changing the current wording "Full-sheet previews" as the feature also covers exporting to PDF, and describing it as "previews" may be misleading.  After discussion the wording change to "Whole sheet export" has been decided and the patch was applied to git master on January 11th.

Since this is a new feature in 6.4, I feel first introducing it one way and then changing the name right next release would be a disservice to users.  So I propose to backport it (just the renaming patch, the feature is already in 6.4) to 6-4 branch and have it consistent from 6.4.1 release and on.

Of course this breaks the string freeze, and a cursory search on Weblate [3] shows the string (translation tag 2o29R) has been translated to 27 languages.  So I'm asking these teams to approve this late request, since you need to translate the new string for the next release sooner or later anyway.  Meanwhile, languages that haven't translated it yet can avoid a bit of extra work.

[1] https://wiki.documentfoundation.org/ReleaseNotes/6.4#Full-Sheet_Previews
[2] https://bugs.documentfoundation.org/show_bug.cgi?id=129417
[3] https://weblate.documentfoundation.org/search/libo_ui-6-4/?q=+source%3Afull-sheet+previews+&type=translated&ignored=False

P.S.: I can't find the procedure for string freeze break described on wiki, so I'm just writing to this list.  If there are more people (documentation team?) that I should ask, please let me know.

Thanks,
Ming

#2

Hi Ming,

there are some l10n teams working out of Weblate (like Slovenian), so if
this string freeze gets accepted, please do post here this fact.

If it gets approved, we must deliver translations into Weblate or code
repository by January 20, to get it into RC3 (planned for Week 4 , Jan 20,
2020 - Jan 26, 2020).

So hopefully this decision would be made by tomorrow and Weblate promptly
updated.

Personally I do not mind it, but just let us know ASAP so we can work on a
l10n update in the next days.

Lp, m.

napisala:

#3

Hi Martin,

Sorry I wasn't clear in my original mail, I meant for this string change to happen for 6.4.1, not 6.4.0. Although it would be nice to get it done before 6.4.0 official release, the time is just too tight and it wouldn't be fair to translation teams that aim at 100% coverage.

The way LO git repository works, 6.4.0 is currently not on 6-4 branch anymore, but on its own 6-4-0 branch (though I don't know the details how weblate syncs the strings from and to the repository). What I'm proposing is to backport the renaming patch sometime after 6.4.0 is released, likely end of January, then leave enough time for translators to work on it before 6.4.1 is released at the end of February. Presumably the users willing to adopt new releases early will be less bothered by such string changes.

I will definitely coordinate with all the people affected and announce the timing of the backport on this list.

Regards,
Ming

------------------ Original ------------------

#4

Hi Ming,

Hi Martin,

Sorry I wasn't clear in my original mail, I meant for this string change to happen for 6.4.1, not 6.4.0. Although it would be nice to get it done before 6.4.0 official release, the time is just too tight and it wouldn't be fair to translation teams that aim at 100% coverage.

Thanks for letting us know and for your work! I understand that this new
feature should have a UI clear enough to be used correctly

The way LO git repository works, 6.4.0 is currently not on 6-4 branch anymore, but on its own 6-4-0 branch (though I don't know the details how weblate syncs the strings from and to the repository). What I'm proposing is to backport the renaming patch sometime after 6.4.0 is released, likely end of January, then leave enough time for translators to work on it before 6.4.1 is released at the end of February. Presumably the users willing to adopt new releases early will be less bothered by such string changes.

I guess there is enough time for 6.4.1 to translate the string. Would
that be ok for you too Martin?

I will definitely coordinate with all the people affected and announce the timing of the backport on this list.

Thanks :slight_smile:
Cheers
Sophie

#5

Hello,

napisala:

I guess there is enough time for 6.4.1 to translate the string. Would
that be ok for you too Martin?

Sure. Just let us know when the string lands in code.

Lp, m.

#6

Hi Sopie and Christian,

------------------ ԭʼÓʼþ ------------------

Hi Ming,
Le 13/01/2020 ¨¤ 23:30, Ming Hua a ¨¦crit :

What I'm proposing is to backport the renaming patch sometime
after 6.4.0 is released, likely end of January, then leave enough
time for translators to work on it before 6.4.1 is released at the
end of February. Presumably the users willing to adopt new
releases early will be less bothered by such string changes.

I guess there is enough time for 6.4.1 to translate the string. Would
that be ok for you too Martin?

Since Martin said there won't be any problem, and there aren't objections from other translators either, I'll take it as a "yes" for backporting this string change from the l10n team.

I'm not familiar with the timing of the syncing between git and weblate. The wiki https://wiki.documentfoundation.org/Translating_LibreOffice says translations are submitted before the Monday tagging deadline, which should be Jan. 20th for 6.4.0 RC3. Is it still the case, and does it mean it's safe to start the backporting after Jan. 21st? I know this is Christian's ballpark, does he read every mail on this list, or should I contact him individually?

Thanks,
Ming

#7

Hi Ming,
Le 18/01/2020 ¨¤ 21:13, Ming H. a ¨¦crit0„2:

Hi Sopie and Christian,

------------------ ԭʼÓʼþ ------------------

Hi Ming,
Le 13/01/2020 ¨¤ 23:30, Ming Hua a ¨¦crit :

What I'm proposing is to backport the renaming patch sometime
after 6.4.0 is released, likely end of January, then leave enough
time for translators to work on it before 6.4.1 is released at the
end of February. Presumably the users willing to adopt new
releases early will be less bothered by such string changes.

I guess there is enough time for 6.4.1 to translate the string. Would
that be ok for you too Martin?

Since Martin said there won't be any problem, and there aren't objections from other translators either, I'll take it as a "yes" for backporting this string change from the l10n team.

I'm not familiar with the timing of the syncing between git and weblate. The wiki https://wiki.documentfoundation.org/Translating_LibreOffice says translations are submitted before the Monday tagging deadline, which should be Jan. 20th for 6.4.0 RC3. Is it still the case, and does it mean it's safe to start the backporting after Jan. 21st? I know this is Christian's ballpark, does he read every mail on this list, or should I contact him individually?

Could you ping him on irc or telegram? Thanks!
Cheers
Sophie

#8

Dear l10n teams,

------------------ Original ------------------

I am writing to ask for approval of backporting a patch
to 6-4 branch that breaks string freeze. The patch is
about a new feature in 6.4, "Full-sheet preview/export"
in Calc, specifically about how it's is shown in the "PDF
Options" export dialog.

The patch was backported to 6-4 branch on Jan 20th, and
Christian has now synced it to the "LibreOffice UI - 6.4"
project on Weblate. Now you can translate it for 6.4.1
release. It's in the filter/messages component, with keyID
MpRUp. Note the same string is also in "LibreOffice UI -
master".

Thanks again for your understanding and patience.

Regards,
Ming