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
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
...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
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 ve
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.
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 ( in VIQR) should be mapped for 0x86,
and U+1EA9 ( in VIQR) for 0xA6.
Here is a test scratch to check whether VISCII i
> 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 PR
