Re: UI strings vs manual strings ?
Alemps Florimond <[email protected]> Tue, 6 Dec 2022 13:04:54 +0000 (UTC)
| Newsgroups | gmane.text.docbook.apps |
|---|---|
| Message-ID | <[email protected]> |
------=_Part_1839547_465159714.1670331894714
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Hello,
I would transform the bundle.properties in a document (article, book or sec=
tion whatever)Each line of the file corresponds to somethine like :
<simpara><guilabel xml:id=3D"messageId">My message</guilabel></simpara>
One element simpara for one guilabel is useless : it is just to make it rea=
dable in a DocBook parse.
In the document, you include the message - something like :<para>You should=
see <xi:include href=3D"bundle.properties.xml" xpointer=3D"messageId"> aft=
er clicking on the button.</para>
The French, English, German version of the document will take advantage of =
the corresponding translated version of bundle.properties.xml
As far as no id message starts with a number (NC Name for xml:id) you are o=
k.With an XSLT 2.0 processor, it might even be possible to transform the bu=
ndle.properties in XML.
Regards,Florimond
Le mardi 6 d=C3=A9cembre 2022 =C3=A0 00:05:49 UTC+1, Jean-Christophe He=
lary <[email protected]> a =C3=A9crit : =20
=20
What's the best way in a DocBook centered process to ensure that the list =
of terms used in a software UI is (semi-automatically?) taken into account =
in the DocBook sources that describe that software?
Problem at hand:
- a Java application with ~2k UI strings (not all users facing), in a Bundl=
e.properties file
- a ~80K words DocBook manual
It is not trivial to keep track of the whole string set (searches, etc.)
Also, the l10n process takes place on the DocBook sources, not on the HTML =
output, so tricks like <link linkend endterm/> don't work because translato=
rs don't see the target terms.
I'm left with having to rewrite the strings explicitly and that's a pain, a=
nd also adds risks of mistakes in translations.
--=20
Jean-Christophe Helary @[email protected]
https://traductaire-libre.org
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
=20
------=_Part_1839547_465159714.1670331894714
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<html><head></head><body><div class=3D"ydpd706df9dyahoo-style-wrap" style=
=3D"font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px=
;"><div></div>
<div dir=3D"ltr" data-setdir=3D"false">Hello,</div><div dir=3D"ltr"=
data-setdir=3D"false"><br></div><div dir=3D"ltr" data-setdir=3D"false">I w=
ould transform the bundle.properties in a document (article, book or sectio=
n whatever)</div><div dir=3D"ltr" data-setdir=3D"false">Each line of the fi=
le corresponds to somethine like :<br></div><div dir=3D"ltr" data-setdir=3D=
"false"><simpara><guilabel xml:id=3D"messageId">My message</=
guilabel></<span>simpara</span>></div><div><br></div><div dir=3D"l=
tr" data-setdir=3D"false">One element <b>simpara</b> for one guilabel is us=
eless : it is just to make it readable in a DocBook parse.<br></div><div><b=
r></div><div dir=3D"ltr" data-setdir=3D"false"><div><div dir=3D"ltr" data-s=
etdir=3D"false"><div dir=3D"ltr" data-setdir=3D"false">In the document, you=
include the message - something like :</div><div dir=3D"ltr" data-setdir=
=3D"false"><para>You should see <xi:include href=3D"bundle.propert=
ies.xml" xpointer=3D"messageId"> after clicking on the button.</para&=
gt;</div><div dir=3D"ltr" data-setdir=3D"false"><br></div><div dir=3D"ltr" =
data-setdir=3D"false">The French, English, German version of the document w=
ill take advantage of the corresponding translated version of <span>bundle.=
properties.xml</span><br></div></div></div><div><br></div><div dir=3D"ltr" =
data-setdir=3D"false">As far as no id message starts with a number (NC Name=
for xml:id) you are ok.</div><div dir=3D"ltr" data-setdir=3D"false">With a=
n XSLT 2.0 processor, it might even be possible to transform the bundle.pro=
perties in XML.<br></div><div dir=3D"ltr" data-setdir=3D"false"><br></div><=
div dir=3D"ltr" data-setdir=3D"false">Regards,</div><div dir=3D"ltr" data-s=
etdir=3D"false">Florimond<br></div></div>
=20
</div><div id=3D"yahoo_quoted_0450615807" class=3D"yahoo_quoted">
<div style=3D"font-family:'Helvetica Neue', Helvetica, Arial, s=
ans-serif;font-size:13px;color:#26282a;">
=20
<div>
Le mardi 6 d=C3=A9cembre 2022 =C3=A0 00:05:49 UTC+1, Je=
an-Christophe Helary <[email protected]> a =C3=A9crit :
</div>
<div><br></div>
<div><br></div>
<div><div dir=3D"ltr">What's the best way in a DocBook cent=
ered process to ensure that the list of terms used in a software UI is (sem=
i-automatically?) taken into account in the DocBook sources that describe t=
hat software?<br></div><div dir=3D"ltr"><br></div><div dir=3D"ltr">Problem =
at hand:<br></div><div dir=3D"ltr"><br></div><div dir=3D"ltr">- a Java appl=
ication with ~2k UI strings (not all users facing), in a Bundle.properties =
file<br></div><div dir=3D"ltr">- a ~80K words DocBook manual<br></div><div =
dir=3D"ltr"><br></div><div dir=3D"ltr">It is not trivial to keep track of t=
he whole string set (searches, etc.)<br></div><div dir=3D"ltr"><br></div><d=
iv dir=3D"ltr">Also, the l10n process takes place on the DocBook sources, n=
ot on the HTML output, so tricks like <link linkend endterm/> don't w=
ork because translators don't see the target terms.<br></div><div dir=3D"lt=
r"><br></div><div dir=3D"ltr">I'm left with having to rewrite the strings e=
xplicitly and that's a pain, and also adds risks of mistakes in translation=
s.<br></div><div dir=3D"ltr"><br></div><div dir=3D"ltr">-- <br></div><div d=
ir=3D"ltr">Jean-Christophe Helary @<a ymailto=3D"mailto:[email protected]" =
href=3D"mailto:[email protected]">[email protected]</a><br></div><div dir=
=3D"ltr"><a href=3D"https://traductaire-libre.org" target=3D"_blank">https:=
//traductaire-libre.org</a><br></div><div dir=3D"ltr"><a href=3D"https://ma=
c4translators.blogspot.com" target=3D"_blank">https://mac4translators.blogs=
pot.com</a><br></div><div dir=3D"ltr"><a href=3D"https://sr.ht/~brandelune/=
omegat-as-a-book/" target=3D"_blank">https://sr.ht/~brandelune/omegat-as-a-=
book/</a><br></div><div dir=3D"ltr"><br></div><div dir=3D"ltr"><br></div><d=
iv dir=3D"ltr">------------------------------------------------------------=
---------<br></div><div dir=3D"ltr">To unsubscribe, e-mail: <a ymailto=3D"m=
ailto:[email protected]" href=3D"mailto:docbook=
[email protected]">[email protected]=
s-open.org</a><br></div><div dir=3D"ltr">For additional commands, e-mail: <=
a ymailto=3D"mailto:[email protected]" href=3D"mailto:=
[email protected]">[email protected].=
org</a><br></div><div dir=3D"ltr"><br></div></div>
</div>
</div></body></html>
------=_Part_1839547_465159714.1670331894714--