CSS Parser and Qt/e 2.

[Maks Orlovich]

On Thursday 26 January 2006 13:27, Luciano Montanaro wrote:
> On Thursday 26 January 2006 17:30, Stefan Eilers wrote:
> > The correct solution would be to modify the parser:
> > It is possible (and what to do) to change the parser to read either
> > big-endian unicode or plain us-ascii?
>
> The lexer (or tokenizer) directly deals with the character stream.
> You may be able to get along by redefining YY_CHAR, I think.
>
> 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.
(And personally, I don't understand the issue with byteswapping)