public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Cygwin unifont Maintainer via Cygwin-announce <cygwin-announce@cygwin.com>
To: cygwin@cygwin.com
Cc: Cygwin unifont Maintainer <Brian.Inglis@Shaw.ca>
Subject: [ANNOUNCEMENT] Updated: unifont, unifont-fonts, unifont-viewer 15.1.01
Date: Sat, 16 Sep 2023 16:51:58 -0600	[thread overview]
Message-ID: <announce.20230916165158.6849-1-Brian.Inglis@Shaw.ca> (raw)

The following packages have been upgraded in the Cygwin distribution:

* unifont		15.1.01
* unifont-viewer	15.1.01
* unifont-fonts		15.1.01

GNU Unifont is a Unicode font with glyphs for all visible Unicode
Basic Multilingual Plane (the first 64K) character code points,
with supporting utilities to modify the font.

For more information see the project home page:

	https://unifoundry.com/unifont/

For recent changes, see below or read /usr/share/doc/unifont/NEWS after
installation.

See also Release Notes under:

	https://unifoundry.com/unifont/index.html
	https://unifoundry.com/unifont/unifont-utilities.html


15.1.01    2023-09-12

* Glyphs updated for Unicode 15.1.0 release.
* OpenType fonts are now built by default, replacing TrueType fonts.
* New Hangul Johab 6/3/1 encoding devised by Ho-Seok Ee for building
  the Hangul Syllables block (U+AC00..U+D7A3), with new supporting
  programs johab2syllables, unigen-hangul, and unijohab2html.  This
  encoding replaces Unifont's original Hanterm-derived encoding.
  New source files hangul.h and unihangul-support.c provide support
  for rendering syllable bitmaps with all Unicode Hangul letters,
  including all ancient Hangul, through the new unigen-hangul program.
  These functions also can support user-written Hangul syllable rendering
  programs, for example on embedded systems using graphics displays.
* Added three hexadecimal digit representation CSUR/UCSUR scripts:
  - U+EBE0..U+EBEF: Boby Lapointe's "bibi-binary" notation
  - U+EBF0..U+EBFF: Bruce Alan Martin's bit location notation
  - U+ECF0..U+ECFF: Ronald O. Whitaker's triangular notation.
* Modified hexdraw to support bitmap manipulation of up to 64 rows
  by 128 columns for 64-by-128 graphics display screen drawing support.
  Added the unihexpose program to transpose Unifont glyphs, for use
  with graphics display controller chips that encode each byte as
  8 rows by 1 column, left to right.

NOTE 

This release does not include Truetype format, only Opentype format
Unifont fonts, as previously announced.
One known issue with TrueType is Pango combining character rendering,
which will not be fixed; the Pango maintainers pretty much just want
to support OpenType.
As these fonts are bitmap glyphs rendered into modern font formats,
both formats should render the same glyphs.
All modern systems support both Opentype and Truetype format fonts,
so there should be few or no issues if future releases provide only
Opentype format Unifont, which are also less than half the file size
of the Truetype format.
If anyone encounters issues using the Opentype format Unifont,
please let us know so we can address any issues.


                 reply	other threads:[~2023-09-16 22:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=announce.20230916165158.6849-1-Brian.Inglis@Shaw.ca \
    --to=cygwin-announce@cygwin.com \
    --cc=Brian.Inglis@Shaw.ca \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).