>>> content: "\2192"
>>
>> Oh God, you *are* kidding me, right?? o_O
>
> content: is not reparsed by the engine, so no entities would be
> substituted, but that should not stop you to encode the right char.

Yeah. I already discovered that you can't use it to insert any new tags 
either. (I guess if you could, it would be a macro expansion engine...)

> Give it a try. (U+2192 is unicode for→ )

Cool. So now I have to memorise character codes. Yay. :-(

> Of course, your font must support it...

Yeah, well, that's always entertaining. ;-)

(The again, I've installed a pack of MathML fonts, so it's usually OK.)

Post a reply to this message