So it sounds like we will have annoyances no matter which choice we make: 1. Using "xml2po -k" and keeping entities intact like &NAME; there are translators who will be inconvenienced. They can still substitute translations for the entity -- using the right form of "SomeName," instead of the exact string "&NAME;" -- but there will be no benefit to them in the event the entity changes. They may not even notice that it *has* changed unless they are watching the docs-common/common/entities/po/entities.pot file, and making the mental connection. 2. Using "xml2po -e" and transforming the entities into strings in the POT file, so "&NAME;" becomes "SomeName," it will be painful to change single strings in a minor way, since *many* fuzzy entries potentially result from trivial changes. We can revert to behavior #2, and I can get this into the POTs for important modules now. I would like opinions within the next 24 hours. We first raised this issue almost two weeks ago in our meeting, summarized here: https://www.redhat.com/archives/fedora-docs-list/2007-March/msg00186.html Reminder to translators working on documentation: please make sure you are subscribed to fedora-docs-list@xxxxxxxxxx for information. Thank you and we look forward to hearing from you about this issue. -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Project: http://fedoraproject.org/wiki/PaulWFrields irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-docs-list mailing list fedora-docs-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-docs-list
