Le 21/09/2010 16:19, Invisible a écrit :
>>> Irritatingly, what you *cannot* do is content: " → ". This is
>>> extremely frustrating, and currently I cannot find any way around this
>>> flaw.
>>
>> 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.

Give it a try.
(U+2192 is unicode for → )
Of course, your font must support it...

Post a reply to this message