xml: unique msgids for tags which are identical in source document
by Daniel Hartwig
Hello
[Please CC me as I am not subscribed on the list]
I am working on some docbook which has a list of items:
<seglistitem>
<seg><literal>%p</literal></seg>
<seg>Package Name</seg>
<seg>30</seg>
<seg>Yes</seg>
…
<seglistitem>
<seg><literal>%u</literal></seg>
<seg>Disk Usage Change</seg>
<seg>30</seg>
<seg>No</seg>
Which generates this msgid of interest:
#. type: Content of:
<book><chapter><section><section><section><segmentedlist><seglistitem><seg>
#: en/aptitude.xml:7233 en/aptitude.xml:7293 en/aptitude.xml:7384
msgid "30"
msgstr ""
In some locales the translation of "30" is different for each of these
items. For example, German should use "30" for the first but "29" for
the second. Is there some way to generate a unique msgid for each of
those seg tags? I have tried using ID attributes:
<seg id="packagename-width">30</seg>
…
<seg id="diskusage-width">30</seg>
but this does not work.
Any help with this would be greatly appreciated.
Regards
12 years, 6 months
- 2
- 1
New release coming soon
by D. Barbier
Hello translators,
Po4a has not been updated for a while, I hope being able to make a new
release in a couple of weeks.
Here are current l10n statistics, please update your translations:
po/bin
af: po/bin/af.po: 22t 30f 149u
bn: po/bin/bn.po: 3t 9f 189u
ca: po/bin/ca.po: 144t 13f 44u
cs: po/bin/cs.po: 201t
da: po/bin/da.po: 105t 96u
de: po/bin/de.po: 201t
eo: po/bin/eo.po: 201t
es: po/bin/es.po: 201t
et: po/bin/et.po: 201t
eu: po/bin/eu.po: 201t
fr: po/bin/fr.po: 201t
he: po/bin/he.po: 3t 9f 189u
hr: po/bin/hr.po: 29t 17f 155u
id: po/bin/id.po: 126t 26f 49u
it: po/bin/it.po: 133t 21f 47u
ja: po/bin/ja.po: 201t
kn: po/bin/kn.po: 29t 35f 137u
ko: po/bin/ko.po: 16t 16f 169u
ku: po/bin/ku.po: 4t 8f 189u
nb: po/bin/nb.po: 51t 39f 111u
nl: po/bin/nl.po: 20t 15f 166u
oc: po/bin/oc.po: 4t 20f 177u
pl: po/bin/pl.po: 201t
pt: po/bin/pt.po: 186t 15u
pt_BR: po/bin/pt_BR.po: 37t 36f 128u
ru: po/bin/ru.po: 201t
sl: po/bin/sl.po: 201t
sv: po/bin/sv.po: 186t 15u
uk: po/bin/uk.po: 201t
uz: po/bin/uz.po: 5t 7f 189u
vi: po/bin/vi.po: 186t 15u
zh_CN: po/bin/zh_CN.po: 11t 11f 179u
zh_HK: po/bin/zh_HK.po: 15t 24f 162u
po/pod
ca: po/pod/ca.po: 909t 87f 474u
de: po/pod/de.po: 1470t
es: po/pod/es.po: 1467t 3f
fr: po/pod/fr.po: 1470t
it: po/pod/it.po: 392t 85f 993u
ja: po/pod/ja.po: 1465t 5f
pl: po/pod/pl.po: 1465t 5f
ru: po/pod/ru.po: 438t 33f 999u
Denis
12 years, 7 months
- 3
- 7
Re: [Po4a-devel] Bug#588962: po4a using both builddir and srcdir
by David Prévot
Hi,
Le 14/05/2012 19:50, Roger Leigh a écrit :
> I've been working on #588962 to implement po4a for the schroot
> documentation.
Thanks Roger!
> http://people.debian.org/~rleigh/schroot_1.5.1.orig.tar.xz
I guess you actually meant:
http://people.debian.org/~rleigh/schroot-1.5.2.tar.xz
> - I'm getting a "translated" directory in both the source
> directory and build directory
> (man/translated/fr and debian/build/man/translated/fr).
> It's a bug to dirty the source tree--I really only want
> them generating in the build tree.
> I set srcdir and destdir, but I'm not sure if I'm doing the
> right thing (see: man/Makefile.am update-po rule).
I can't see what's wrong at first sight, adding the po4a-devel list in
the loop in case we're missing something. The actual call is:
[ -n "$(PO4A)" ] && $(PO4A) --package-name $(PACKAGE) --package-version
$(VERSION) --copyright-holder "Roger Leigh <rleigh(a)debian.org>"
"--srcdir=$(srcdir)" "--destdir=$(builddir)" "$(srcdir)/po4a.cfg"
Indeed, simply running “po4a --destdir=../debian/build/man/ po4a.cfg”
from the man directory builds everything where expected (even with
“--srcdir=.”), but when run from the root directory, it builds them in
both the --srcdir and the --destdir, so it may be a bug in po4a. As a
workaround, you could remove the sloppy man/translated directory in the
update-po rule, after the po4a call.
> - The fr manpages are output in UTF-8. The man program results
> in readable output, but the PDF/PS documentation looks awful
> due to lots of junk in the output.
> While UTF-8 is fine in the .po file, would recoding to latin1
> or into groff symbols for non-ASCII characters be feasible?
Charset of the files containing the localized documents can be change
with the -L option of po4a, but, there is better:
> Or can groff now process UTF-8 input?
“groff -k -KUTF-8” seems to do the work quite nicely.
Regards
David
12 years, 7 months
- 2
- 2
- ← Newer
- 1
- Older →