Dear Christoph,
> Even in double-width? Surprising indeed ;-) But then I still don't
> understand the problem, since if you're using gbk you are surely using a
> Chinese font anyway so why can't you use the "Chinese" copyright symbol?
> (Sorry for my ignorance about Chinese char sets.)
That is exactly what I have done for the copy right symbol. It's a
good workaround for this. I just stumbled upon this entity and
encoding problem on ©, but it will apply to other entities, for
example also.
> This is exactly what you are trying to do here with your © entity
> reference (and what I meant with "mixing" gbk with unicode). It seems to
> be a perfectly valid approach and Kid should not give an error. I'll fix
> this in the next Kid version.
Thanks and looking forward to the new version.
> Why is that? Are there any browsers used in China which do not support
> utf-8? I just remembered that there are resentments against using
> unicode in Japan (http://www.jbrowse.com/text/unij.html), maybe
> something similar applies to China?
I think partly because one are already accustomed to the gb2312/gbk
family of encoding due to its long history. They are also the national
standard for Chinese characters. For Chinese only documents, they are
sufficient. And for most of applicaitons, it seldmon needs to
accomodate different languages in the same document.
Another important reason of its popularity is its inherent simplicity.
One Chinese character is represented by 2-bytes in memory. And it
happens also that when displayed, one Chinese character will take the
space of 2 English letters. So it is very convient to calculate the
langth of displayed string based on the length of the byte string.
'Double-width' means not only in memory, but also on screen, and very
often, on printed paper. In case of mixed Chinese characters and alpha
numerics, this makes the calculation of memory requirement extremely
simple.
With unicode utf-8 encoding however, one Chinese character has varing
in-memory length, but count only as 1 symbol in the string, which
makes certains things difficult for the application.
The situation is similar to what happens in Japan, a mixture of
techincal and psychological background. Though unicode/utf8 is more
and more widely accepted, we have to cope with the myriads of existing
applications which talk gbk only.
--
Hong Yuan
大管家网上建材超市
装修装潢建材一站式购物
http://www.homemaster.cn
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kid-template-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/kid-template-discuss
