On Mon, 2006-04-24 at 13:57 -0500, Tommy Reynolds wrote:
Uttered "Paul W. Frields" <stickster(a)gmail.com>,
spake thus:
> I noticed something in our build tools which seems to me a problem: our
> POT file only includes the msgstr information for the XMLFILES but does
> not include the DOC_ENTITIES. If we can (and should) only have one
> $(LANG).po file per language, shouldn't all the XML strings for
> translation be in the one POT?
As our knowlege of this translation thing seems to be evolving, I
believe that the entities files are of use only to keep usage
consistancy in the ${PRI_LANG} original language version of the
document. So, yes, I think a single .POT file per document makes
sense.
Of course you're right; if the parsing is done pre-POT -- which is what
I think we agree has to happen, to ensure consistency and the ability
for translators to access the entire document.
So the idea would be, AIUI:
* Drop the po/${DOC_ENTITIES}.pot target
* Drop all '-k' switches for ${XML2PO}
...? (Don't feel like you have to figure this out and reply, I'm more
thinking out loud here.)
I've been in the throes of moving, shuttling between two houses,
and
haven't had time for the make-fu to correct this. Things should
settle down soon and I'll take care of it.
Totally understood. Hope everything is going well, we miss you 'round
these parts. :-) I am in the middle of an office move -- not quite as
traumatic, but it definitely has messed up my schedule and kept me from
getting to a lot of work I meant to accomplish.
--
Paul W. Frields, RHCE
http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
Fedora Documentation Project:
http://fedora.redhat.com/projects/docs/