Re: So many Dans!

On Tue, 26 Mar 2002 05:27:08 +0900, [EMAIL PROTECTED] (Dan Kogai) wrote: >There is a famous sentence that goes like; > >KiSha no KiSha ga KiSha de KiSha shita. > >all KiSha are in two Kanjis but they are all spelled differently. "Your company's reporter returned to his company by t

Re: So many Dans!

On Tue, 26 Mar 2002 11:31:59 +0800, [EMAIL PROTECTED] (Autrijus Tang) wrote: > But the legendary Prof. Zhao Yuan-Ren (the first modern Chinese > linguist, translator extraordinarie) composed "The Tale of Mr. > Shi's Lion-eating endeavor" to demonstrate the impossibility of > reducing Chinese to p

Re: So many Dans!

On Mon, 25 Mar 2002 22:36:00 +0200, [EMAIL PROTECTED] (Jarkko Hietaniemi) wrote: > I simply have to retaliate with a piece of Finnish discussion: > > - Kokoo kokoon koko kokko. > - Koko kokkoko? > - Koko kokko. What is the first 'Kokoo'? http://websmart.kielikone.fi/ did not r

Re: Encode::CJKguide

On Wed, 27 Mar 2002 00:09:11 +, [EMAIL PROTECTED] (Markus Kuhn) wrote: > Dan Kogai wrote on 2002-03-26 22:35 UTC: > > And not all > > scripts are accepted or approved by Unicode Consotium. If you want to > > spell in Klingon, you have to find your own encoding. > > Klingon is a very bad exa

[Encode] *.ucm files

On Wednesday, March 27, 2002, at 01:35 , Autrijus Tang wrote: > CP949 is there in Encode::KR. CP950 is in Encode::TW. CP936 is in > Encode::CN. CP932 is in Encode::JP. I have made it that way to make perl on the run save as much memory as possible. Only those in need get loaded. > I've put

[Encode] Johab support, et al.

On Wednesday, March 27, 2002, at 01:40 , Jungshik Shin wrote: > I've looked around ext/Encode and I found that CP949 is supported. > So, what has to be added is JOHAB and what needs to be modified > is EUC-KR to support 8byte seq. representation of Hangul syllables > (see http://jshin.net/i18n/e

Re: let's cook it!

On Tue, Mar 26, 2002 at 06:28:07PM -0500, Jungshik Shin wrote: > Microsoft products use 'ks_c_5601-1987' as an encoding name/MIME > charset/character set encoding scheme. That's a very strange use > of KS C 5601-1987. Because, what they mean by 'ks_c_5601-1987' > is actually CP949/Unified Hangu

Re: Encode: CJK-Guide

Jungshik Shin <[EMAIL PROTECTED]> writes: > >> > For Johab, no new table is necessary because Hangul precomposed >> > syllable mapping (to Unicode) is algorithmic while Hanjas and symbols can >> > be mapped to KS X 1001 algorithmically and then mapped to Unicode >> > using KS X 1001 mapping tabl

Re: missing =head1:s

On Wed, Mar 27, 2002 at 04:51:03PM +0900, Dan Kogai wrote: > Hey, jhi, is buildtoc your home-brew tool? Coundn't find it on perl > dist it's F... /Autrijus/ msg00952/pgp0.pgp Description: PGP signature

Re: let's cook it!

Autrijus Tang <[EMAIL PROTECTED]> writes: >On Tue, Mar 26, 2002 at 06:28:07PM -0500, Jungshik Shin wrote: >> Microsoft products use 'ks_c_5601-1987' as an encoding name/MIME >> charset/character set encoding scheme. That's a very strange use >> of KS C 5601-1987. Because, what they mean by 'ks_c

Re: Encode::CJKguide (> 500 lines Long!)

Hello, Dan! 1) That's been a great job! Especially the way you have explained the 0x21-0x7E and 0xA1-0xFE ranges via the tables, I like it! :-) 2.1) And.. maybe just strip off the Unicode part and we'll get a good guide on CJK? It's a great thing to have the CJK explanation bundled, isn't it?

Copyright of the generated image via http://www.unicode.org/cgi-bin/refglyph

As part of an effor to make Encode module successful, I am writing a simple "web typesetter" that renders whole text, not just each character via cgi (or mod_perl if the memory is enough). I would like to use the gif-rendered glyphs that are available via http://www.unicode.org/cgi-bin/refgl

Re: Is it true that there are no longer no official mappings from JIS X to Unicode?

On Wednesday, March 27, 2002, at 08:06 , Anton Tagunov wrote: > Hello, Dan! > > BTW, is the guy speaking > > http://www.debian.or.jp/~kubota/unicode-symbols.html.en > > right or not? His article is dated september.. > He is speaking about lack of official tables, that the tables > have been withdr

[Encode] Encode::Guide ? (Was: Re: Encode::CJKguide ...)

Anton, I am glad you liked it but as I announced Encode::CJKguide has been dropped. I am instead planning to make even more comprehensive guide that is not limited to CJK and upload it as Encode::Guide to CPAN. I will definely call for your help. Dan On Wednesday, March 27, 2002, at 09:

Re: missing =head1:s

On Wed, Mar 27, 2002 at 04:51:03PM +0900, Dan Kogai wrote: > Let's work on easy ones first... > > On Wednesday, March 27, 2002, at 11:11 , Jarkko Hietaniemi wrote: > > buildtoc: ../ext/Encode/TW/TW.pm: cannot find =head1 NAME > > buildtoc: ../ext/Encode/Symbol/Symbol.pm: cannot find =head1 NAME >

Re: So many Dans!

On Wed, Mar 27, 2002 at 10:05:50AM +, Philip Newton wrote: > On Mon, 25 Mar 2002 22:36:00 +0200, [EMAIL PROTECTED] (Jarkko Hietaniemi) > wrote: > > > I simply have to retaliate with a piece of Finnish discussion: > > > > - Kokoo kokoon koko kokko. > > - Koko kokkoko? > > - Koko k

Re: So many Dans!

On Wed, Mar 27, 2002 at 10:05:51AM +, Philip Newton wrote: > > The original text appeared in an earlier edition of Encyclopedia > > Britannica, and is available here (in big5): > > L. > > Is that text in wenyan? Or do people really speak lik

[Encode] Todo before release 1.00

Jungshik, I am ALMOST ready to release version 1.00 of Encode. But with a last minute, welcome addition of Jungshik Shin to the team, I am tempted to wait until he is done with Johab. So Jungshik, how long will you take to submit Johab.pm ? If you think it takes longer (FYI we are ALRE

Re: [Encode] Todo before release 1.00

On Thu, Mar 28, 2002 at 12:35:55AM +0900, Dan Kogai wrote: > Jungshik, > >I am ALMOST ready to release version 1.00 of Encode. But with a last > minute, welcome addition of Jungshik Shin to the team, I am tempted to > wait until he is done with Johab. >So Jungshik, how long will you ta

Re: let's cook it!

On Wed, 27 Mar 2002, Nick Ing-Simmons wrote: > Autrijus Tang <[EMAIL PROTECTED]> writes: > >On Tue, Mar 26, 2002 at 06:28:07PM -0500, Jungshik Shin wrote: > >> Microsoft products use 'ks_c_5601-1987' as an encoding name/MIME > >> charset/character set encoding scheme. That's a very strange use

Re: Encoding vs Charset

On Wed, 27 Mar 2002, Dan Kogai wrote: > On Wednesday, March 27, 2002, at 11:22 , Jungshik Shin wrote: > > IMHO, you're also misusing the term 'charset' here. MIME charset > > can be used synonymously with 'encodings' (or > > character set encoding scheme: see CJKV Information Processing, > > IE

Re[2]: let's cook it!

Hello Jungshik! JS> MS should have registered CP949/950 as Windows-949/950 JS> instead of labeling them misleadingly as ks_c_5601-1987 and big5, In case JS> of gb2312, gbk should be registered and used. I don't know about big5, JS> but in Korean case, apparently they tried to pretend that they

Re: [Encode] Encode::Guide ? (Was: Re: Encode::CJKguide ...)

On Wed, Mar 27, 2002 at 11:12:41PM +0900, Dan Kogai wrote: > Anton, > > I am glad you liked it but as I announced Encode::CJKguide has been > dropped. I am instead planning to make even more comprehensive guide > that is not limited to CJK and upload it as Encode::Guide to CPAN. I > will d

Yen/Backslash problems (was Re: Encode::CJKguide)

On Wednesday 27 March 2002 04:38, Anton Tagunov wrote: >   The Yen sign and the backslash tend to be the most troublesome >   characters as a single codepoint in 8-bit encodings has a tendation >   to be used for both. Also Korean Won and backslash. > Is this true? Yes, the problem exists

Re: Encoding vs Charset

On Wed, Mar 27, 2002 at 11:59:10AM -0500, Jungshik Shin wrote: > On Wed, 27 Mar 2002, Dan Kogai wrote: > > > On Wednesday, March 27, 2002, at 11:22 , Jungshik Shin wrote: > > > IMHO, you're also misusing the term 'charset' here. MIME charset > > > can be used synonymously with 'encodings' (or >

RE: Copyright of the generated image..

Dan the Encode Maintainer asked: >I would like to use the >gif-rendered glyphs that are available via >http://www.unicode.org/cgi-bin/refglyph. >But is the data copyrighted? If so to whom should I ask? People address questions about copyright/trademark issues to the Unicode office. See http:

[Encode/ISO-2022] KR is done. CN to go.

Jungshik, First, Thank you so much (as much as the number of code points for all Korean charset combined!) for submitting a patch so quickly. It was applied hairlessly. I am now hopeful that 1.00 will be shipped in next 24 hours. Coincidentally, it is 09:00 JST, meaning 00:00 Zulu. On

Re: [Encode/ISO-2022] KR is done. CN to go.

On Thu, 28 Mar 2002, Dan Kogai wrote: Dan, >First, Thank you so much (as much as the number of code points for all > Korean charset combined!) for submitting a patch so quickly. It was > applied hairlessly. Oh, that's too much more than I really deserve :-) >I am now hopeful that

[mark.davis@jtcsv.com: Unicode 3.2 Released]

- Forwarded message from Mark Davis <[EMAIL PROTECTED]> - Subject: Unicode 3.2 Released From: "Mark Davis" <[EMAIL PROTECTED]> Date: Wed, 27 Mar 2002 18:46:39 -0800 Message-ID: <00f301c1d602$c9b203d0$68de2b09@DAVIS1> To: <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]> Errors