Guido Berhoerster <[email protected]> writes: > Or you could simply add an option to not substitute \u escapes > at all, that is the behavior of the diverse native Tcl > .msg-format extractors that float around (e.g. thos included in > in tkabber or coccinella) and what I'd personally prefer.
I think it wouldn't be that easy and probably not the way to go. Even if it is fine with you to have Tcl-escaped strings in PO files, that might confuse translators and PO editors, as it is hard to determine whether or not a msgid is escaped. Particularly when PO files are edited on the Web and translators have no knowledge about the actual programming language used in the code from where the strings are extracted. Yes, it could be implemented as an option for Tcl only, but all the relevant tools need to be aware of that change: xgettext, msgfmt, po-mode.el, etc. and external PO editors. I fear any inconsistency if the option is mistakenly used. Regards, -- Daiki Ueno
