Re: [PATCH] viscii.ucm
Since the original VISCII data came (I think) from the Unicode web site, maybe this discrepancy should be more reported even more officially? -- Jarkko Hietaniemi [EMAIL PROTECTED] http://www.iki.fi/jhi/ There is this special biologist word we use for 'stable'. It is 'dead'. -- Jack Cohen
Re: [PATCH] viscii.ucm
On Sun, 16 Feb 2003 12:25:43 +0200 Jarkko Hietaniemi [EMAIL PROTECTED] wrote: Since the original VISCII data came (I think) from the Unicode web site, maybe this discrepancy should be more reported even more officially? I doubt whether the Unicode consortium had provided any viscii-Unicode mapping table under www.unicode.org/Public/MAPPINGS/. I could suppose the table shipped on Perl was borrowed from czyborra.com. The table there ( http://czyborra.com/charsets/vietnamese.html ) has wrongly the duplicated A^? and no a^?. The following site provides a correct table. http://www.vietstd.org/document/unicode.html SADAHIRO Tomoyuki
Re: [PATCH] viscii.ucm
...or it could come from the Tcl/Tk mapping tables? -- Jarkko Hietaniemi [EMAIL PROTECTED] http://www.iki.fi/jhi/ There is this special biologist word we use for 'stable'. It is 'dead'. -- Jack Cohen
Re: [PATCH] viscii.ucm
On Sun, 16 Feb 2003 13:10:11 +0200 Jarkko Hietaniemi [EMAIL PROTECTED] wrote: ...or it could come from the Tcl/Tk mapping tables? Probably impossible, since the Perl 5.7.2 distribution did not contain viscii.enc nor viscii.ucm. Moreover ICU does not have any VISCII mapping neither in the version 2.4 nor in CVS ( http://oss.software.ibm.com/cvs/icu/charset/data/ ). SADAHIRO Tomoyuki
Re: [PATCH] viscii.ucm
SADAHIRO Tomoyuki [EMAIL PROTECTED] I doubt whether the Unicode consortium had provided any viscii-Unicode mapping table under www.unicode.org/Public/MAPPINGS/. I could suppose the table shipped on Perl was borrowed from czyborra.com. The table there ( http://czyborra.com/charsets/vietnamese.html ) has wrongly the duplicated A^? and no a^?. The following site provides a correct table. http://www.vietstd.org/document/unicode.html Okay. I'll replace viscii.ucm in the next release. On Sunday, Feb 16, 2003, at 20:10 Asia/Tokyo, Jarkko Hietaniemi wrote: ...or it could come from the Tcl/Tk mapping tables? I think this is it. When I took over Encode maintenance, I have rebuilt whatever mappping unicode.org did have but I don't recall doing so for viscii so it must have come from viscii.enc. Dan the Encode Maintainer
Re: [PATCH] viscii.ucm
On Sunday, Feb 16, 2003, at 12:26 Asia/Tokyo, SADAHIRO Tomoyuki wrote:
Hello. I've found the mapping in the present viscii.ucm
have a bit diffrence from that in RFC 1456.
U+1EA8 (A^? in VIQR) should be mapped for 0x86,
and U+1EA9 (a^? in VIQR) for 0xA6.
Here is a test scratch to check whether VISCII indeed
supports all the Latin extensions for Vietnamese,
i.e. U+1EA0..U+1EF9.
#!perl
for (my $u = 0x1EA0; $u = 0x1EF9; $u++) {
my $e = encode(VISCII, chr $u, Encode::FB_WARN);
}
warn End.;
__END__
Thanks. Applied in my repository.
Dan the Encode Maintainer
P.S. Is ftp.funet.fi still down? I think I am ready to
$Encode:VERSION++ with this patch applied.
Re: [PATCH] viscii.ucm
P.S. Is ftp.funet.fi still down? I think I am ready to $Encode:VERSION++ with this patch applied. Unfortunately so. Or, FUNET is up, it's just that the updates from PAUSE to FUNET are stopped until they are certain everything is fixed. (See use.perl.org.) -- Jarkko Hietaniemi [EMAIL PROTECTED] http://www.iki.fi/jhi/ There is this special biologist word we use for 'stable'. It is 'dead'. -- Jack Cohen
