Ed and Ted, Thanks for your thoughts on working with PO files.
Ed: Regarding my idea about preserving a link to previous translations of a msgid, eg. "One idea that comes to mind is to store a unique msg id in the text of our messages or in the comments that precede our message and use this id to retrieve previous msgid/msgstr translation pairs for review." Elaborating on my proposal: By msg id, I mean a unique alphanumeric identifier with leading/trailing delimiters such that this id can be easily detected for translation purposes and easily removed before display to the end user. An off-the-cuff proposal might be (((<numeric-id>))), used in context: message = "Unable to open the specified file.(((122008)))" Your response was: "Seems like a bit of overkill; 'msgid' is already a unique identifier. Just track the pre-edit value, and use that to replace the other .po files with the new post-edit value." I guess I'm a bit thick headed today, but I'm struggling with your suggestion. I don't see how your suggestion allows me to programmatically associate an original msgid with the updated value of a msgid if I don't have a unique key embedded in my msgid's that stays the same across edits. 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.
