Hi,
On 13.10.2004 20:18, meh wrote:
I actually find myself quit agreeing with you in here, even though I am the original proposer of the idea. There isn't much difference which exact sign will we implement the "f(x)" sollution with, and Alan's sollutions seems to fit the standard.
Why should it matter (implementation wise, and tachles, for the user experience) whether we put an RLE or an LRM?
from the implementation point of view, it does matter, whether we use an RLE or an LRM character. The LRM character could be automatically inserted after typing the closing bracket, just as you described in issue 18024. But where should an LRE character be inserted automatically? The 'correct' position would be in front of the 'f', since f(x) is the LTR embedded text portion. So this would be after the last strong RTL character? No, automatic insertion of LRE/RLE/PDF characters does not work without any additional information, where to start and end the embedding. This again leads us to the IME/character attribute solution. The IME gives the hint, where to start/end the embedding, and internally using a direction/embedding character attribute is totally equivalent to using LRE/RLE/PDF characters. So actually Alan's solution is quite close to the IME/character attribute option.
Beside this, the usage of LRE/RLE/PDF characters is 'considered not suitable for use with markup in XML or HTML', see http://www.unicode.org/unicode/reports/tr20/#Charlist
whereas the usage of RLM/LRM is suitable. That means, we should replace these characters on xml/html export with the appropriate embedding attributes. So we should prefer the embedding/direction attributes over the embedding control characters, if want to have a solution based on embedding markup.
Regards,
Frank
-- Frank Meies email: [EMAIL PROTECTED] ============================================================== To unsubscribe, send mail to [EMAIL PROTECTED] with "unsubscribe hebrew" in the message body.
