[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libreoffice-l10n] Request for breaking string freeze


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.

V V pon., 13. jan. 2020 ob 21:16 je oseba Ming H. <2097632994@qq.com>
napisala:

> Dear Sophie and l10n teams,
>
>
> I am writing to ask for approval of backporting a patch to 6-4 branch that
> breaks string freeze.&nbsp; 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.&nbsp; 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.&nbsp; 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.&nbsp; 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.&nbsp; 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+&amp;type=translated&amp;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.&nbsp; If there are more people
> (documentation team?) that I should ask, please let me know.
>
>
> Thanks,
> Ming
> --
> To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
> Problems?
> https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
> Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
> List archive: https://listarchives.libreoffice.org/global/l10n/
> Privacy Policy: https://www.documentfoundation.org/privacy
>
>

--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
Privacy Policy: https://www.documentfoundation.org/privacy

Follow-Ups:
Re: [libreoffice-l10n] Request for breaking string freeze"Ming Hua" <2097632994@qq.com>
References:
[libreoffice-l10n] Request for breaking string freeze"Ming H." <2097632994@qq.com>
Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.