CSS Parser and Qt/e 2.

[Stefan Eilers]

Am 26.01.2006 um 19:43 schrieb Maks Orlovich:

>> If plain ascii is sufficient, I think converting the string to  
>> latin1 and
>> redefining YY_CHAR to unsigned char should do.
>
> Doing ascii would be wrong, since CSS can have Unicode strings in it.

How often does it happen? Use ascii would be the the only solution I  
see..

> (And personally, I don't understand the issue with byteswapping)

Well. If YY_CHAR is an unsigned short and it reads on a little endian  
machine  0x002f, it would interpret this as (for instance) chinese  
char. If it reads 0x2f00 it would be a "/". This is the reason why  
the parser is irritated by big endian encoded  QChars.

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.

Mfg., Stefan Eilers
--  
Stefan Eilers
Software Engineer

basysKom GmbH
Robert-Bosch-Str. 7 | 64293 Darmstadt | Germany
Tel: +49 6151 3969-962 | Fax: -736 | Mobile: +49 170 4213459 |  
Jabber: eilers at jabber.org
stefan.eilers at basyskom.de | www.basyskom.de



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.kde.org/mailman/private/kfm-devel/attachments/20060127/839f791d/attachment.htm>