I made a mistake about the charsets/codesets. What I meant: - what if single byte code set is mixed with double byte code set? eg. iso8859-? with GB2312.80.
- What if two similiar code sets are mixed? eg. GB2312 and BIG5. All of them create troubles! Unless they are clearly tagged, it is difficult to make a "smart" render to display them correctly except some special cases. I realize that plucker is just a offline HTML viewer, so it will probably never have to deal with that. However, it will be really nice to make it more than just that by put the charset encoding information usually seen only in HTTP headers or <meta> tags in the documents. So it is possible to do: ......... <charset=EUC-JP> blah (in Japanese)... blah... </charset> <charset=GB2312> Some other stuff (in chinese)... </charset> .......... within one single file. Maybe all these problems will be solved if we use unicode. Zailong --- Bill Janssen <[EMAIL PROTECTED]> wrote: > > It is a good idea. But what happens when charsets are mixed in one single > page > > of the document? This is not the stuff you can always avoid. > > Zailong, are you thinking of the multiple code pages in Big5 or > EUC-JP, for instance? These are still single codesets, even though > they have multiple code pages. > > Bill __________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com
