On Wed, Dec 27, 2000 at 13:44:11 +0200, Maxim Sobolev wrote: > I'm now sure how could I obtain charset for each of dozen+ OSes that may create a CD. There is not so much number, usualy only one Russian charset per OS :-) > I don't see any problems, because it's likely that usual special high code table > characters (copyright, angle quotes and so on) will be represented using Unicode > charcodes with first byte (`base') equal to 0, so they can be mapped directly into > native charset. In my implementation only Unicode characters with base !=0 are to be > translated. All less usual characters (graphics and so on) can be translated by > extending appropriate codetable to include additional translation tables with >different > bases (e.g. 0x25 for graphics chars etc.). Well, I could live with it in case you add _whole_ windows-1251 set as Unicode to your loadable table and provide corresponding mapping for all matching KOI8-R characters, as MSDOSFS currently does. You can get those tables from MSDOSFS. This is minimal basis, you can make separate table for KOI8-U, etc. I say this because I see you try to treat KOI8-R and KOI8-U in your patch as the same charset which is not acceptable. Also please call those tables per local charset name and not 'cd9660'. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
