Ugo Cei wrote: > > Is there a workaround for this bug? How do the users of C2.1 deal with > the situation? > > If I revert the fix in AbstractTextSerializer, the handling of > namespaces is broken. > > If I leave the fix as is, pages are served in UTF-8 and that stupid > excuse for a browser that is IE barfs on UTF-8 characters. I would > gladly tell my users to use Mozilla instead, but it seems like IE > currently has more than 90% of the market. It's unbelievable that people > would choose one browser over another just because it comes built-in > with their OS, even if it's technically inferior. I think the > manufacturer should be sued for monopolistic practices <*GRIN*>. > > Would it be possible to change some code somewhere so that Cocoon would > always serialize as, say, ISO-8859-1 instead of UTF-8? It's a ugly hack > but at least it would make my Italian pages work in IE (at least I hope so).
It is not only the encoding. It is also that no doc type (for WAP gateways) is set, xml declaration is not omitted and maybe more. Michael --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
