Re: Translation: Where some problems come from Re: Problematic strings in code

[Francisco Vila]

El 12/4/20 a las 19:00, Luis Falcon escribió:
> >  From the actual look of the document (see attached),

> Have you checked the actual ODT file related to the report itself?

The document is visually OK as the screenshots showed. Tell me if they
need to get posted again.

The issue is not how the report document looks like. Rather, it is that
any manually-applied style, although invisible, determine a weird
splitting of the words which go to the POT template making it
untranslatable.

Every time you manually apply an effect such as italics or bold, a new
custom style gets into the ODT internal code, for that particular span.
That text gets then more and more fragmented, every time producing tiny
_fragments_ of words. Those fragments go to the POT template waiting for
translators all around the world to guess if "P" is for "Patient" or
what, because somebody applied 'bold' to "atient" alone by mistake.

Let me know if something is not clear.

At the very least, _all_ styles (both character- and paragraph- styles)
in an ODT document which will eventually produce translatable strings,
should be applied _only_ to whole words and be _named_ styles from the
styles list, _not_ custom, internal styles applied using a mouse and a
button from the format toolbar.

This all is for the sake of translation; you still can get a nice report
from that ODT --in English.
--
Francisco Vila, Ph.D. - Badajoz (Spain)
paconet.org , lilypond.es