Quoting Sergey Korobitsin (2015-01-28 10:16:15)
Jonas Smedegaard ☫ → To Sergey Korobitsin @ Wed, Jan 28, 2015 09:42
>> A I see, non-sophisticated translator can omit the '=====' and
>> '----' lines and leave only translated header itself, and at the
>> output we'll get broken structure. Then, it can be workarounded by
>> some kind of Translator's HOWTO, but people are people, and it would
>> better if this case processes automatically.
> I don't follow how current loose parsing leads to broken structure -
> i.e. how it is an actual (not just an academic) problem. Can you
> elaborate on that - perhaps give an example of how it can break (even
> if, as you already wrote, the breakage is minor)?
See, I have a Markdown document started as follows:
Область применения документа
Данный документ является руководством для администраторов платформы
«ARTA SYNERGY» (далее Система), предназначенной для совместной работы
на предприятиях и управления по целям. Здесь описываются процессы,
связанные с выполнением задач администрирования Системы.
Then, when I apply po4a, I get following content at PO file:
#. type: Plain text
#, fuzzy, no-wrap
#| msgid "Область применения документа"
"Область применения документа\n"
msgstr "Scope of document"
And then, what will do some forgetful translator - just remove the
"fuzzy" mark. If so, I'll get the following in output document:
Scope of document
The document is guide for Administrators of the ARTA SYNERGY platform
(hereinafter referred to as the System) designed for groupwork on
enterprises and target-oriented management. It describes processes
connected to execution of the System administration tasks.
And, bingo! I've got broken stucture of document.
This problem not about bugs, but about usability, and its minor. Maybe
I've got some professional deformation, because my scope of work for
now is usability :-)
It is neither. It is not because you remove fuzzy mark, but because you
additionally remove the no-wrap mark.
Try instead replace "fuzzy, no-wrap" with "no-wrap" - I bet that will
You are right that PO format is not very user friendly, but then use
editors that understand the format and presents it in a more
user-friendly manner - don't expect PO to survive being messed with by
non-techies using raw text editors without understanding what its markup
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private