From butta1@crsa.bu.edu Mon Jan 3 07:38:30 1994 Return-Path: Received: from crsa.bu.edu by ifcss.org (4.1/IFCSS-Mailer) id AA15779; Mon, 3 Jan 94 07:38:30 CST Received: by crsa.bu.edu (5.61+++/Spike-2.1) id AA25199; Mon, 3 Jan 94 08:36:53 -0500 Date: Mon, 3 Jan 1994 08:36:52 -0500 (EST) From: C I I Project Subject: moving away from hku-ch16 big5 font To: Software Authors Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello, here's an advice from Dr. Pong from HKUST about the hku big5 font, which i also support in moving away from to avoid compatibility problems with the standard BIG5 code. Maybe leave out hku big5 option in your future version of softwares, or at least not make it as a default font. I suggest following what chdrv chinese TTY program of the LINUX OS (nctuccca.edu.tw:/Chinese/UNIX/Chinese-TTY/*) in using kc fonts (freely ftp-able for academic use) as the default big5 font, and at the same time providing HBF support. and if we're to move away from the hku-ch16 font, how about removing it from the ifcss.org ftp site, to reduce further propagation of the nonstandard font. ---------- Forwarded message ---------- Date: Mon, 3 Jan 94 15:32:21 HKT >From: Dr. Man-Chi PONG Below is my standard answer to what's the difference between hku-ch16 & other Big5 based font/code: There's only one standard of Big5, used by many vendors in Taiwan. (It's not the official standard CNS 11643-1986 in Taiwan -- though the character set is similar, the assigned codes for the characters are quite different. Moreover, Big5 is more commonly used in Taiwan & H.K.) Difference vendors may add their own user-defined characters/glyphs in the unused code points of the Big5 coding space. hku-big5 modified some of the STANDARD code points of the Big5 coding space, thus it should not be used any more to avoid imcompatible with the Big5 standard. ------- Cheers! -- mcpong ~{ESCqVN~} From mleisher@crl.nmsu.edu Tue Jan 4 13:06:12 1994 Return-Path: Received: from NMSU.Edu (dns1.NMSU.Edu) by ifcss.org (4.1/IFCSS-Mailer) id AA10898; Tue, 4 Jan 94 13:06:12 CST Received: from crl.nmsu.edu by NMSU.Edu (4.1/NMSU-1.18) id AA07616; Tue, 4 Jan 94 12:04:34 MST Date: Tue, 4 Jan 94 12:04:34 MST Message-Id: <9401041904.AA07616@NMSU.Edu> Received: from pylos.nmsu.edu by crl.nmsu.edu (4.1/SMI-4.1) id AA20357; Tue, 4 Jan 94 12:04:30 MST Received: by pylos.nmsu.edu (4.1/SMI-4.1) id AA18591; Tue, 4 Jan 94 12:04:29 MST From: mleisher@crl.nmsu.edu (Mark Leisher) To: Nihc Noslen Subject: Re: taipei[k,m,l].bdf fonts In-Reply-To: References: <9312292319.AA18927@NMSU.Edu> Cc: soft-authors@ifcss.org Nelson> On Wed, 29 Dec 1993, Mark Leisher wrote: > > where and what fontfiles did you make the BDFs of taipei[k,m,l].bdf > > from ? > > I generated these fonts from the original binary font files from the > ETEN package. We can't distribute the original fonts, so I had to > write a program to handle it. Nelson> wouldn't the bdf files also be considered as copies of the Nelson> originals, and thus still under ETen's copyright Nelson> jurisdiction? is it equivalent to using the ETen hbf header Nelson> files, like the ones on ifcss.org and binary fonts that comes Nelson> with ETen system and then use hbftobdf and create bdf from Nelson> there? btw, which version of eten are these fonts? I realize I made a small mistake here: I didn't generate the taipei[k,m,l].bdf fonts myself. Someone else must have done this. I didn't make any of the taipei BDF fonts available except the 16x15 font because someone else had generated it and made it available. Indeed, the legal question (at least in the US) is whether the BDF font is just another expression of the original fonts and falls under the ETEN copyright. Since this was in question, I simply wrote a program that would allow owners of the ETEN program to extract their fonts for use with X; with the assumption that the BDF fonts should be for PRIVATE use and not made available for general distribution. It might be useful if someone could figure out how Taiwanese copyright law (with regard to software/fonts) applies in this situation, but this would take some investigation. ----------------------------------------------------------------------------- mleisher@crl.nmsu.edu Mark Leisher Computing Research Lab "Elegance is not optional!" New Mexico State University -- Attributed to Richard O'Keefe Box 3CRL, Las Cruces, NM 88003 From butta1@crsa.bu.edu Tue Jan 18 04:24:37 1994 Return-Path: Received: from crsa.bu.edu by ifcss.org (4.1/IFCSS-Mailer) id AA07320; Tue, 18 Jan 94 04:24:37 CST Received: from ITHAKE.BU.EDU by crsa.bu.edu (5.61+++/Spike-2.1) id AA15237; Tue, 18 Jan 94 05:22:56 -0500 Received: by ithake.bu.edu (5.61+++/Spike-2.1) id AA03064; Tue, 18 Jan 94 05:22:49 -0500 Date: Tue, 18 Jan 1994 05:22:47 -0500 (EST) From: C I I Project Subject: how to use unihan24 hbf file? and hbf compatibility with X11R6? To: Software Authors Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII i've two questions: what text editor/conversion utility can i use to create a file which can make use of ifcss.org:/software/fonts/unicode/unihan24.hbf in printing? also for the missing glyphs in unihan24, why not just scan in the rest from the unicode book, if it's in there. Q2: will the current hbf files be usable for the upcoming X11R6 cxterm fonts? or will new hbf header files be need to created for the new GL-encoded fonts? attached CXTERM-FONTS.readme: ---------- Starting from X11R6. (Read this if you plan to write X programs.) Starting from X11R6 the cclib* fonts will be removed and replaced by hanzigb16st, hanzigb16fs, and hanzigb24st, which are nearly identical to the cclib* fonts, except that the hanzigb* are all GL-encoded to be in the same line as other X11 international fonts. A character code in a GL-encoded font uses the range 0x21-0x7e in its two byte while a GR-encoded font (the cclib*) currently use 0xa1-0xfe. ---------- From rap@doc.ic.ac.uk Tue Jan 18 05:45:52 1994 Return-Path: Received: from santos.doc.ic.ac.uk by ifcss.org (4.1/IFCSS-Mailer) id AA08790; Tue, 18 Jan 94 05:45:52 CST Received: by santos.doc.ic.ac.uk (Smail3.1.28.1 #7) id m0pMEqu-00070TC; Tue, 18 Jan 94 11:44 GMT Message-Id: Date: Tue, 18 Jan 94 11:44 GMT From: Ross Paterson To: soft-authors@ifcss.org Subject: Re: how to use unihan24 hbf file? and hbf compatibility with X11R6? butta1@crsa.bu.edu writes: > what text editor/conversion utility can i use to create a file which can > make use of ifcss.org:/software/fonts/unicode/unihan24.hbf in printing? Editor: sam, in research.att.com:/dist/sam/ (sam lacks input methods; the best you can do at present is set up key bindings to conversion filters.) Conversion: tcs, in research.att.com:/dist/tcs.shar.Z Printing: ifcss.org:/software/dos/chinese-utils/utf-utils.tar.Z These handle Unicode in the UTF encoding. For more details, see research.att.com:/dist/plan9man/09utf.ps.Z > also for the missing glyphs in unihan24, why not just scan in the rest > from the unicode book, if it's in there. Feel free to do so. There are only 1268 of them, scattered through the tables. > Q2: will the current hbf files be usable for the upcoming X11R6 cxterm > fonts? or will new hbf header files be need to created for the new > GL-encoded fonts? New header files will be needed, but it won't be difficult. From butta1@crsa.bu.edu Wed Jan 26 11:40:57 1994 Return-Path: Received: from cnd.org (cnd.cnd.org) by ifcss.org (4.1/IFCSS-Mailer) id AA20052; Wed, 26 Jan 94 11:40:57 CST Received: from crsa.bu.edu by cnd.org (4.1/4.7) id AA24644; Wed, 26 Jan 94 08:43:23 PST Received: from MURRAY.BU.EDU by crsa.bu.edu (5.61+++/Spike-2.1) id AA21329; Wed, 26 Jan 94 11:40:41 -0500 Received: by murray.bu.edu (5.61+++/Spike-2.1) id AA21921; Wed, 26 Jan 94 11:40:45 -0500 Date: Wed, 26 Jan 1994 11:40:43 -0500 (EST) From: C I I Project Subject: GB1988.1980 To: Software Authors Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII does anyone have any info on GB1988.1980, it's included in Waseda's multilingual X11R5, but i've no clue which tar file it's hidden in. see ftp.cfi.waseda.ac.jp:/pub3/X11R5/binaries nelson From rap@doc.ic.ac.uk Thu Jan 27 04:21:00 1994 Return-Path: Received: from santos.doc.ic.ac.uk by ifcss.org (4.1/IFCSS-Mailer) id AA19492; Thu, 27 Jan 94 04:21:00 CST Received: by santos.doc.ic.ac.uk (Smail3.1.28.1 #7) id m0pPToQ-00070TC; Thu, 27 Jan 94 10:18 GMT Message-Id: Date: Thu, 27 Jan 94 10:18 GMT From: Ross Paterson To: soft-authors@ifcss.org Subject: Re: GB1988.1980 > does anyone have any info on GB1988.1980, it's included in Waseda's > multilingual X11R5, but i've no clue which tar file it's hidden in. I believe (from consulting RFC 1345) that it's a 7-bit code, the Chinese extension of ISO 646 (of which the US extension is ASCII). So another name for it is ISO 646-CN. It differs from US-ASCII only in the following positions: 0x24 ($) - YEN SIGN (or Yuan sign, but that's the ISO name) 0x7E (~) - OVERLINE Thus it is identical to ISO 646-JP, the left half of JIS X0201-1976. [By the way, an updated version of my notes on CJK character codes (but not mentioning GB 1988-80) is now available via WWW -- see the Chinese Software and Computing page under -- comments welcome.]