Please update your translations
by Martin Quinson
Hello,
I plan to do a last release in 2021, as we got some changes fixing
bugs for the users. Please update your translations on need (the bug
fix added a new string). The current stats read as follows:
po/bin (pot: 32912)
15 languages >= 95%: de (97%), eo (98%), es (97%), fr (98%), hr (98%), hu (97%), it (98%), nb (98%), nl (99%), pt (97%), pt_BR (99%), ru (98%), sr_Cyrl (99%), uk (99%), zh_CN (97%).
1 language >= 80%: id (81%).
2 languages >= 70%: et (71%), sv (76%).
7 languages >= 50%: cs (60%), da (62%), eu (59%), ja (65%), pl (65%), sl (58%), vi (65%).
1 language >= 33%: ca (47%).
1 language >= 20%: zh_Hant (22%).
6 starting languages: ace (2%), af (7%), ar (14%), kn (7%), ko (19%), zh_HK (3%).
po/pod (pot: 279121)
3 languages = 100%: it, pt_BR, uk.
3 languages >= 95%: de (99%), nl (99%), sr_Cyrl (99%).
3 languages >= 90%: fr (94%), pt (94%), zh_CHS (93%).
1 language >= 70%: es (78%).
3 languages >= 50%: ja (69%), pl (69%), ru (69%).
1 language >= 33%: ca (44%).
4 starting languages: eo (2%), hr (0%), hu (0%), nb (2%).
Thanks and merry christmas,
Mt
--
The bullshit asymmetry: the amount of energy needed to refute bullshit
is an order of magnitude bigger than to produce it. -- A. Brandolini
1 year, 9 months
automatic update of generated pot files
by Marco Ciampa
Hi devs!
my 2 eurocent suggestion here,
please ignore me if I'm saying something silly...
If I am not wrong,
po/bin/po4a.pot
and
po/pod/po4a-pod.pot
are generated files, not to be manually edited.
Is it possible to make them automatically built if some source perl file
get modified? They also should be ignored by git of course, by inserting
them in some .gitignore config file...
TIA
--
Saluton,
Marco Ciampa
1 year, 9 months
strange behaviour (bug?)
by Marco Ciampa
This string:
#. type: textblock
#: lib/Locale/Po4a/Xml.pm:68
msgid ""
"By default, Processing Instructions (i.e., C<<? ... ?>> tags) are handled as "
"inline tags. Pass this option if you want the PI to be handled as breaking "
"tag. Note that unprocessed PHP tags are handled as Processing Instructions "
"by the parser."
msgstr ""
"Per impostazione predefinita, le istruzioni di elaborazione (ovvero i "
"tag C<<? ... ?>>) vengono gestite come tag in linea. Passare questa "
"opzione se si vuole che il PI venga gestito come tag di rottura. Si noti "
"che i tag PHP non elaborati vengono gestiti come istruzioni di "
"elaborazione dall'analizzatore."
man Locale::Po4a::Xml
[...]
break-pi
Per impostazione predefinita, le istruzioni di elaborazione (ovvero i tag "<? ... ?">)
vengono gestite come tag in linea. Passare questa opzione se si vuole che il PI venga
gestito come tag di rottura. Si noti che i tag PHP non elaborati vengono gestiti come
istruzioni di elaborazione dall'analizzatore.
[...]
Please note the "<? ...?"> quotes...
Also in English:
export LANG=en
man Locale::Po4a::Xml
[...]
break-pi
By default, Processing Instructions (i.e., "<? ... ?"> tags) are
handled as inline tags. Pass this option if you want the PI to be
handled as breaking tag. Note that unprocessed PHP tags are
handled as Processing Instructions by the parser.
[...]
is this correct?
--
Saluton,
Marco Ciampa
1 year, 9 months
another typo
by Marco Ciampa
#. type: textblock
#: lib/Locale/Po4a/TransTractor.pm:67
msgid "Create a new po4a document. Accepted options (but be in a hash):"
maybe perhaps?
msgid "Create a new po4a document. Accepted options (but they must be in a hash):"
IMHO it should be rephrased (which hash?)...
--
Saluton,
Marco Ciampa
1 year, 9 months
typo maybe?
by Marco Ciampa
#. type: textblock
#: lib/Locale/Po4a/TeX.pm:51
msgid ""
"The notion of environment is expended to the type displayed in the PO file. "
perhaps it should be:
#. type: textblock
#: lib/Locale/Po4a/TeX.pm:51
msgid ""
"The notion of environment is expanded to the type displayed in the PO file. "
^^^^^^^^
--
Saluton,
Marco Ciampa
1 year, 9 months