You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
padpo implements its own parser of .po files and entries.
The idea is to enable the translator to tell padpo that he deliberately knows there is a false positive. The translator would do it in writing a pragma in the "translator comment" field.
The way padpo parses the .po file does not enable this feature.
I would recommend to use the polib library which give access to "translator comment" field.
The text was updated successfully, but these errors were encountered:
…tives
POC in relation with AFPy#61
polib:
* replacement of padpo parser by polib parser is done with minimal change of
the structure of padpo. Refactoring would be welcome.
* linelength checker is deleted as polib does not provide msgstr in vanilla
form.
Job can be done by powrap
* changes validated only on test files!
silent padpo:
* 2 tags are provided as a POC: 1 for glossary and 1 for nbsp
* polib is needed as padpo parser does not provide access to 'translator
comment' field.
padpo implements its own parser of .po files and entries.
The idea is to enable the translator to tell padpo that he deliberately knows there is a false positive. The translator would do it in writing a pragma in the "translator comment" field.
The way padpo parses the .po file does not enable this feature.
I would recommend to use the polib library which give access to "translator comment" field.
The text was updated successfully, but these errors were encountered: