History of this Document
Version 1.0
of this document was written by Man-Chi Pong,
as a result of discussion via e-mail among a group of Chinese software
developers who would like to see a standard way to access hanzi (Chinese
character) bitmap files.
The following is a list, in alphabetic order of the surnames,
of the contributors to the discussion.
CAI@neurophys.wisc.edu (CAI, Yidao)
jiang@ifcss.org (JIANG, Yuan)
lee@umunhum.stanford.edu (LEE, Fung Fung)
A7621GAC@AWIUNI11.EDVZ.UniVie.AC.AT (LEMBERG, Werner)
87P0786@csdvax.csd.unsw.edu.au (NI, Hongbo)
mcpong@cs.ust.hk (PONG, Man-Chi)
simpson@math.psu.edu (SIMPSON, Stephen G.)
tee@ecf.toronto.edu (TEE, Luns)
yawei@bronze.ucs.indiana.edu (WEI, Ya-Gui)
eric@coeus.ucsd.edu (YANG, Bo)
Ricky.Yeung@eng.sun.com (YEUNG, Ricky)
FARZ%NMUMUS.bitnet@vmd.cso.uiuc.edu (ZHANG, Roxin)
ygz@cs.purdue.edu (ZHANG, Yongguang)
All previous mail exchanges, related programs,
the names in the mailing list (soft.list), etc.,
are ftp'able.
The following revisions culminated in version 1.0:
- Draft 0.1 (1993/02/17)
- Draft 0.2 (1993/02/28)
- All property keywords related to HBF starts with "HBF_".
- "_" is used to separate the English words in the HBF
keywords to make them more readable.
- "ENCODING" is renamed as "HBF_CODE_SCHEME" because
"ENCODING" in X BDF means the hanzi code value of a glyph.
- "SEGMENT" is renamed as "HBF_CODE_RANGE"; more suggestive.
- Draft 0.3 (1993/03/15)
- uniform naming of keywords: HBF_xxx_yyy.
- cut the details of X11R5 XLDF and BDF properties.
- simplify API.
- Draft 0.4 (1993/04/30)
- found in BDF [2] that " can be used in a string (use "").
- FONTBOUNDINGBOX & HBF_BITMAP_BOUNDING_BOX can have -ve xd yd;
BNF in Appendix 1 updated.
- changes in API HBF_OpenFont() HBF_GetBitmap()
and API routines return 0 if OK, non-zero if not OK.
- Draft 0.5 (1993/05/28)
- mention that HBF file name convention is not part of this standard.
- some minor presentation changes.
Adopted as version 1.0.
The revisions leading to version 1.1 were coordinated by
Nelson Chin (Chen Yilong) with
contributions from:
CAI@neurophys.wisc.edu (CAI, Yidao)
A7621GAC@AWIUNI11.EDVZ.UniVie.AC.AT (LEMBERG, Werner)
rap@doc.ic.ac.uk (PATERSON, Ross)
The revisions culminated as version 1.1 are:
- Draft 1.01 (1994/07/19)
- all references to X11R5 changed to X11R6. [cyl@ifcss.org]
- all references to HBF v1.0 changed to v1.1 [cyl@ifcss.org]
- added JISX0208-1990 and KSC5601-1987 as
valid HBF_CODE_SCHEMEs [rap@doc.ic.ac.uk]
- The bit about vendor versions of Unicode is wrong.
v1.1 comes first; vendor extensions of it may come later.
[rap@doc.ic.ac.uk]
- Draft 1.02 (1994/07/20)
- "COPYRIGHT" of HBF file is now identified with "COMMENT"
line. [rap@doc.ic.ac.uk]
- "COPYRIGHT" & "NOTICE" definitions changed to conform to
X11R6 BDF/XFLD properties. [rap@doc.ic.ac.uk]
- appendix 2 proposed API implementation removed, to keep
HBF Standard describing only file format.
- all references to ETen 2.00.03 changed to 3.10 [cyl@ifcss.org]
- section 4 descriptions of full HBF merged into section 3
STARTPROPERTIES explanation, and section 4 example of full
HBF is now appendix 2. [rap@doc.ic.ac.uk]
- Draft 1.03 (1994/07/22)
- reference to Ross Paterson's sample API implementation
and availability added to section 1. [nsysu11@cc.nsysu.edu.tw]
- Reference part at end of section 1 moved out of HBF
Standard into Appendix 3 as Endnotes. [cai@neurophys.wisc.edu]
- section 3 (2) HBF_CODE_SCHEME explanation updated.[rap]
- discarded the "v" in front of version numbers when used in
HBF_CODE_SCHEME, as it's not used in the similar XLFD property
CHARSET_REGISTRY. [cyl@ifcss.org]
- Draft 1.04 (1994/07/23)
- many references to "hanzi" changed to "character" in the
text of this Standard to reflect support of any uniform
bitmaps, and not just hanzi bitmaps. [rap@doc.ic.ac.uk]
- Draft 1.05 (1994/07/25)
- all references to X11R6 BDF and X11R6 XLFD changed to
BDF 2.1 and XLFD 1.5, respectively, since BDF hasn't changed
for two X11 revisions. [rap]
- implementation note appended to bitmapFileName. [rap]
- correction to STARTPROPERTIES p: BDF p isn't optional, but
the whole properties section is optional.[rap]
- specs for single and triple byte fonts added. [cai]
- Draft 1.06 (1994/07/27)
- converted document to HTML.
Some restructuring and stylistic changes.[rap]
- added description of SIZE entry (required for BDF compatability).[rap]
- moved case-insensitivity to FONT and HBF_CODE_SCHEME (since others
may not be case-insensitive; bitmap filenames certainly aren't).[rap]
- Draft 1.07 (1994/09/01)
- contributors acknowledged for HBF 1.1, in History section.
[a7621gac@wiuni11.bitnet]
- more html links in Code Scheme section. [cyl]
- CHARS, which is now optional, is only required by BDF, but can be
calculated with sample implementation such as hbftobdf. [rap]
- added to Code Scheme section: GB, JIS and KSC code schemes may be
either Graphic Left (GL) or Graphic Right (GR) encoded, but GL encoding
should be used if consistency with X11R6 distribution is desired.[a7621gac]
- updated Appendices and References sections. [a7621gac]
- added CNS 11643-1992 to Code scheme section, since CNS HBF fonts are
now readily accesible. [cyl]
- Draft 1.08 (1994/09/18)
- HBF 1.1 will not adopt any author's API implementation as the standard,
but a separate document will be provided to introduce HBF 1.1, and
available sample implementations, with links to the HBF font files
themselves, and related information.
- adopted as HBF version 1.1
- Patch Level 1 (1994/09/21)
- minor changes to Code Scheme names so that spaces and hyphens correlates
to the periods as used in the BDF Property "CHARSET_REGISTRY"
Part of Hanzi Bitmap Font (HBF) File Format version 1.1.