DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR New]

Link: http://www.fltk.org/str.php?L2155
Version: 1.3-current


I just begin from the work on 'xutf8' directory where I didn't  find enough
CopyRight  declaration and I am not sure  how to update CopyRight too. I am
not familiar with COPYRIGHT, would you like to add COPYRIGHT if possible? 

The file 'cp936ext.h'  at the link you provided is completely different
from the one added to 'lcUniConv' directory in this patch.  The  former is
the 'extension' part of cp936(only a few characters), but the latter 
includes all GBK characters  in cp936 code page. In fact,  I prefer 
'gbk.h' than 'cp936ext.h' for the the latter one. I named it as
'cp936ext.h' only to keep the style in ' lcUniConv/cjk_tab_to_h.c':
  
else if (!strcmp(name,"cp936ext"))
    do_gbk1(name);

ALL WORK in this patch were based on the files that can be found  in
'xutf8' directory and the file 'CP936.TXT' available on 'ftp.unicode.org'.


For the work on file 'cp936ext.h',  I can describe in detail.   The file
'cp936ext.h I created was only based on the file cjk_tab_h.c and the file
'CP936.TXT' (link: . 
ftp://ftp.unicode.org/Public/MAPPINGS/VENDORS/MICSFT/WINDOWS/CP936.TXT').
And
1. The tool I used to create 'cp936ext.h' was 'gbk_tab_h'. The tool's
souce code 'gbk_tab_h.c' was based on the file 'lcUniConv/cjk_tab_h.c'
completely.

2. The characters in GBK encoding range from  0x8140 to 0xfefe (except for
'0x??7f')  which can be thought as a sub set of CP936.  And the tool
'gbk_tab_h' just extract table in this range from 'CP936EXT.TXT'. The file
'CP936EXT.TXT ' was the userful part of 'CP936.TXT' and  was created from
'CP936.TXT' with 'sed' like this:
sed -e '/^0x00/,/^0xFF/d'   CP936.TXT > CP936EXT.TXT.

In fact, I have found that the files in 'lcUniConv' directory are similar
with the one in 'xlibi18n' directory of  genoo package 'libX11' or those
can be found at   XFree86's repo:  
'http://cvsweb.xfree86.org/cvsweb/xc/lib/X11/lcUniConv/' . It seemed that
part of them was based on an old version of libiconv. The current  version
of libiconv  support more encoding (including an excellent support on gbk).
I am not sure why fltk use the old codes of libiconv (keep lib in small
size?) So after that I continue to finish the patch in the old-style and
try to  keep  the style if possible.


Link: http://www.fltk.org/str.php?L2155
Version: 1.3-current

_______________________________________________
fltk-bugs mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-bugs

Reply via email to