From: Aditya Mahajan <adityam@umich.edu>
To: "news3@nililand.de" <news3@nililand.de>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: manipulate ttf-fonts loaded with luatex
Date: Wed, 27 Oct 2010 17:32:21 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.01.1010271725100.23787@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <z2p2mpedp087.dlg@nililand.de>
On Wed, 27 Oct 2010, Ulrike Fischer wrote:
> Am Wed, 27 Oct 2010 14:35:46 -0400 (EDT) schrieb Aditya Mahajan:
>
>> On Wed, 27 Oct 2010, Ulrike Fischer wrote:
>>
>>> Hello,
>>>
>>> I'm currently a bit playing around with the idea to add some support
>>> in the (LaTeX) package "chessfss" (which handle chess fonts) for
>>> fonts loaded with the luaotfload package. As luaotfload use the
>>> context code to load the font I'm hoping that someone here can help
>>> me with some of my problems.
>>>
>>> Chess fonts are highly unstandard. The different authors of the
>>> fonts did put the chars quite randomly in the character table and
>>> also used various glyphs name. So in the psfonts.map almost every
>>> font has its own encoding vector:
>>
>> What is the unicode support for chess fonts. Are there unicode glyphs for
>> each symbol (just like card suits, I guess)?
>
> There are unicode code points only for a part of the symbols.
I checked the unicode list. The codepoints 0x2654 to 0x365F cover all the
chess pieces. All the fonts in enpassent.dk and chessfss_gallery.pdf show
only these symbols. So what is missing? I am guessing that the problem is
not as simple as just mapping a font glyph to the corresponding unicode
codepoint.
Aditya
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2010-10-27 21:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-27 10:37 Ulrike Fischer
2010-10-27 18:35 ` Aditya Mahajan
2010-10-27 20:01 ` Ulrike Fischer
2010-10-27 21:32 ` Aditya Mahajan [this message]
2010-10-28 8:34 ` Ulrike Fischer
2010-10-28 12:33 ` Hans Hagen
2010-10-28 12:57 ` Ulrike Fischer
2010-10-28 13:08 ` Taco Hoekwater
2010-10-28 13:29 ` Ulrike Fischer
2010-10-28 13:33 ` Khaled Hosny
2010-10-28 14:59 ` Hans Hagen
2010-10-28 15:37 ` Ulrike Fischer
2010-10-28 16:01 ` Hans Hagen
2010-10-28 17:08 ` Ulrike Fischer
2010-10-28 17:17 ` Hans Hagen
2010-10-28 17:48 ` Ulrike Fischer
2010-10-28 18:56 ` Hans Hagen
2010-11-02 15:16 ` Ulrike Fischer
2010-11-02 15:40 ` Hans Hagen
2010-10-28 19:35 ` Hans Hagen
2010-10-28 19:46 ` Khaled Hosny
2010-10-28 20:29 ` Hans Hagen
2010-10-28 15:48 ` Taco Hoekwater
2010-10-28 15:59 ` Khaled Hosny
2010-10-28 16:06 ` Hans Hagen
2010-10-28 16:29 ` Hans Hagen
2010-10-28 16:47 ` Ulrike Fischer
2010-10-28 17:03 ` taco
2010-10-28 19:48 ` Khaled Hosny
2010-10-28 13:10 ` Hans Hagen
2010-10-28 13:34 ` Ulrike Fischer
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=alpine.LNX.2.01.1010271725100.23787@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--cc=news3@nililand.de \
--cc=ntg-context@ntg.nl \
/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 NNTP newsgroup(s).