Stop creating huge translation units in applications

[Łukasz Wojniłowicz]

Thanks but I already knew that. I use Lokalize, and sometimes it shows
what has changed (as you described) but it did not show anything in
this case.

On Sat, 4 Nov 2023 13:35:11 +0100
Karl Ove Hufthammer <karl at huftis.org> wrote:

> Ł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.
> 
>