Hi,
just one example from Gerrit 4 hours ago:
"vector graphics;converting bitmaps"
was changed to:
"vector graphics; converting bitmaps"
See:
https://gerrit.libreoffice.org/#/c/52546/2/source/text/simpress/guide/vectorize.xhp
Is that "missing space" an error? Not. What does this change cause? It
causes 100+ translations of that string obsolete, fuzzy, untranslated,
not shown in builds ... And 100+ localizers must again localize,
check, edit this same string ...
Is this kind of editing/"cleaning-up" of help really useful/desired? Not.
Lp, m.
2018-04-07 22:01 GMT+02:00 Martin Srebotnjak <miles@filmsi.net
<mailto:miles@filmsi.net>>:
Hi,
And now the Babilon tower is open to all ...
For years I was asking for a kind of a review process for all new
strings in UI/help and for the editing process. So someone
overlooks all the changes going in and stops the ones that seem
unfit (in langague or technical sense), thus reducing the
repetitive editing of same strings.
Instead, now there is a possibility to edit everything even more
"easily", with even less thinking about it before it is done.
So now we might see a surge in help changes that make many l10n
projects quite vulnerable, and most probably several edits of same
strings in a row (a documenter reminding oneself that another
thing should be added or changed or edited, after it is already
featured in git).
Hopefully, this function is limited to master, because if this is
available in "stable" versions, this will lead to havoc ...
Lp, m.
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.