CSS Parser and Qt/e 2.

[Thiago Macieira]

Stefan Eilers wrote:
>I'm currently thinking of using the default flex (which does not  
>understand unicode by default) to generate a complete new lexical  
>scanner. Therefore It is important to know whether unicode CSS  
>strings just happen theoretically or does they exist in reality.

Simple example:

q:before {
  content: " “";
}

q:after {
  content: "” ";
}

Where the space before and after « » could very well be an NBSP (U+00A0), 
which is valid in Latin 1, but not in US-ASCII (though Qt doesn't 
distinguish between the two in any version).

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

2. Tó cennan his weorc gearu, ymbe se circolwyrde, wearð se cægbord and se 
leohtspeccabord, and þa mýs cómon lator. On þone dæg, he hine reste.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <https://mail.kde.org/mailman/private/kfm-devel/attachments/20060127/0bf31e2a/attachment.sig>