public inbox for
help / color / mirror / Atom feed
From: Thomas Wolff <>
To: cygwin-xfree <>,
	 Jon TURNEY <>
Subject: Re: font-misc-misc out of era
Date: Sat, 21 Sep 2013 17:26:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Am 20.09.2013 19:21, schrieb Jon TURNEY:
> On 20/09/2013 17:37, Thomas Wolff wrote:
>> The X fonts in the package font-misc-misc is out-of-era, from ASCII times,
>> so that e.g. if you start xterm -fn 9x18 you wouldn't even see a Euro sign.
>> Please replace them with their Unicode versions from
> Markus Kuhn's X11 unicode bitmap fonts have been included in the upstream
> X.Org package for some years (see [1])
Looking precisely, they are actually included in the cygwin 
font-misc-misc package, though in addition to small script-specific old 
versions. I think the latter should be removed to reduce confusion.

> This seems to be an issue with the font specification: "9x18" aliases to
> "-misc-fixed-medium-r-normal--18-120-100-100-c-90-koi8-r" (which I don't have
> installed on my system, and probably doesn't have a euro character)
I wonder why the font-alias package creates cyrillic/fonts.alias as the 
only language-specific subdirectory. The entries font there are 
ambiguous to those of misc/fonts.alias (with the exception of 9x18 which 
is not included in the latter). Looks somewhat weird.
Also I wonder whether the fonts.alias file shouldn't rather come with 
each respective package.

> $ xterm -fn 9x18
> Warning: Cannot convert string "9x18" to type FontStruct
> xterm: cannot load font '9x18'
> xterm: cannot load font '9x18'
> but this works fine:
> $ xterm -fn -misc-fixed-medium-r-normal--18-120-100-100-c-90-iso10646-1
> and I can type € with no problem.
> We probably need to do something more intelligent than just using the upstream
> font aliases package verbatim to fix this problem.
> [1]
Yes, simply the misc/fonts.alias file should alias 9x18 etc to the 
proper Unicode version, and the ambiguous entries elsewhere should be 

Unsubscribe info:
Problem reports:

  reply	other threads:[~2013-09-21 17:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-20 16:37 Thomas Wolff
2013-09-20 17:21 ` Jon TURNEY
2013-09-21 17:26   ` Thomas Wolff [this message]
2013-09-24 18:55     ` Jon TURNEY

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:

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

  git send-email \ \ \ \ \

* 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).