On Fri, Feb 27, 2009 at 09:01:10AM +1000, Ruediger Landmann wrote:
Paul W. Frields wrote:
> So would I be correct in thinking that's not what Publican does, and
> that entities are only supposed to be used in Publican docs to
> represent non-translatables like a year or a company name?
>
Yes, that's correct. Publican is built on the KDE tool xml2pot, not the
GNOME tool xml2po, and xml2pot doesn't have the "-e" option that xml2po
does.
Publican uses xml2pot because it is /significantly/ faster than xml2po,
which is important when handling the huge documents that we work with in
Red Hat Engineering Content Services. To put the difference in
perspective: while Publican was in early development, conversions of the
Red Hat Enterprise Linux Deployment Guide (a document of around 300,000
words) were done with both tools. Xml2pot finished the entire run in all
23 languages around the same time that xml2po finished the /first/
language!
Having sat through our toolchain's build process innumerable times, I
definitely see your point. Not sure why the xml2po tool hasn't been
fully ported to C at this point, but meh.
That said, there are such obvious advantages to using entities such
as
&DISTRO; so this is something that will no doubt be revisited if and when
xml2pot ever gets an option equivalent to "-e". But for now, we just can't
do it.
*nod*
--
Paul W. Frields
http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - -
http://pfrields.fedorapeople.org/
irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug