Sorry for late response. Chusslove Illich <caslav.i...@gmx.net> writes:
> In kde-xml-format using & is required only if it would start a > valid entity reference which is not wanted. E.g. "Ask &for > confirmation" is valid kde-xml-format. So standard XML well- > formedness check cannot be applied. Thanks, I missed that point. Then it would make sense to treat it specially for KDE. > The other reason is more principal. Having both foo-format and xml-format > flags would semantically indicate that the message is orthogonaly both > foo-format and xml-format. Yes, I've also thought about it, but didn't find any practical example. > The technical difference to --qt and --boost is that with those formats the > argument substitution does not happen if the original string has no > placeholders, and there is no integral markup processing. Sorry, I'm not talking about the difference of those formats, but about the option semantics. If I understand correctly (from the xgettext code), they are supposed to work as: "mark any string with X-format which can be interpreted as a valid X-format string". In that sense, it's not surprising to me that all normal strings are marked as kde-format when --kde is specified. But I could be wrong; neither the documentation nor the help text explicitly state that. Regards, -- Daiki Ueno
