Hi Ed, Thanks for taking the time to explain your solution. If I understand your approach correctly, it means that the developer must manually update the master PO repository every time they update a string that gets used as a msgid.
Unfortunately, I can not depend on my developers doing that consistently which is why I had proposed the idea of embedding a permanent id in each msgid. This permanent id would be used to "backlink" to previous msgid/msgstr translations and would be removed by a gettext wrapper function before a translated msgstr gets returned. The only downside I can see to this approach is that xgetttext will not be able to detect duplicate msgid's meaning that if duplicate msgid detection is important (I need to research this more for our situation), we might have to write an post xgettext utility to compress logically duplicate msgid's into a single msgid. You and Ted have given me some good suggestions - I'll have to sleep on whether the permanent id approach is more complicated than your alternative or Ted's suggestion that we do nothing and let our translators deal with these issues. Malcolm _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
