Stop creating huge translation units in applications
Karl Ove Hufthammer
karl at huftis.org
Sat Nov 4 12:35:11 GMT 2023
Łukasz Wojniłowicz skreiv 04.11.2023 13:10:
> please stop creating huge translation units as the one at the end of
> this message. It's difficult to translate or to spot a change that
> you'll make in them in the future.
>
> Recently it popped up as fuzzy during my translation session, and I
> don't know what you've changed there. It could be a text or it could be
> html formatting or it could be just a missing space somewhere. In either
> case I need to read through all of its 5326 letters to find that out.
> That slows down translation considerably.
I agree about the unnecessary use of HTML formatting (‘style="
margin-top:0px; margin-bottom:0px; margin-left:0px; margin-
right:0px; -qt-block-indent:0; text-indent:0px;’). But if you use a good
PO editor, it’s very easy to spot which words/characters have changed.
For example, Lokalize has a very nice coloured diff view. Example (for a
Krita string):
Characters that have been removed are shown in red, while characters
that have been added are shown in blue.
It’s not perfect (as you can see in the screenshot), but it usually
works very well. If your PO editor doesn’t have a coloured diff view,
consider switching to Lokalize.
--
Karl Ove Hufthammer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-i18n-doc/attachments/20231104/b1a1f465/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lokalize-diff-view.png
Type: image/png
Size: 24718 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-i18n-doc/attachments/20231104/b1a1f465/attachment-0001.png>
More information about the kde-i18n-doc
mailing list