On Wed, Oct 31, 2018 at 03:32:09PM -0700, Asmus Freytag via Unicode wrote: > On 10/31/2018 9:03 AM, Khaled Hosny via Unicode wrote: > > A while I was localizing some application to Arabic and the developer > “helpfully” used m² for square meter, but that does not work for Arabic > because there is no superscript ٢ in Unicode, so I had to contact the > developer and ask for markup to be used for the superscript so that O > can use it as well. > > This just pushes the issue down one level. > > Because it assumes that the presence/absence of markup is locale-independent. > > For translation of general text I know this is not true. There are instances > where some words in certain languages are customarily italicized in a way that > is not lexical, therefore not something where the source language would ever > supply markup.
That was a while ago, but IIRC, the markup was enabled for that particular widget unconditionally. The localizer is now free to use the markup or not use it, the string was translatable as whole with the embedded markup. It should be possible to enable markup for any widget, it is just an option to tick off in the UI designer, but may experience is that markup is seldom needed in computer UIs, but I may be biased with the kind of UIs and locales I’m most familiar with. Regards, Khaled
