public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree@cygwin.com
Cc: towo@computer.org
Subject: Re: font-misc-misc out of era
Date: Fri, 20 Sep 2013 17:21:00 -0000	[thread overview]
Message-ID: <523C840F.6010508@dronecode.org.uk> (raw)
In-Reply-To: <523C79BE.6070205@computer.org>

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
> http://www.cl.cam.ac.uk/~mgk25/ucs-fonts.html

Markus Kuhn's X11 unicode bitmap fonts have been included in the upstream
X.Org package for some years (see [1])

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)

$ 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] http://cgit.freedesktop.org/xorg/font/misc-misc/log/

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


  reply	other threads:[~2013-09-20 17:21 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 [this message]
2013-09-21 17:26   ` Thomas Wolff
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:
  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=523C840F.6010508@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-xfree@cygwin.com \
    --cc=towo@computer.org \
    /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).