From: "Pablo Rodríguez" <oinos@web.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: 'kern': TrueType table and GPOS lookup feature
Date: Sat, 01 Dec 2012 00:57:40 +0100 [thread overview]
Message-ID: <50B947F4.5080404@web.de> (raw)
In-Reply-To: <50B92D0C.80703@wxs.nl>
Thanks for all replies Hans, Steve, Bill and Luigi.
Sorry for the confusion generated by my questions. I'll try to summarize
the whole thing as brief as I can.
I happen to have an Sony PRS-T1 reader in which I noticed that the
FreeSerif fonts where wrong kerned. I thought it might be something
wrong in the fonts and I used ConTeXt to check that.
Until this morning I asked whether TrueType kerning was enabled when all
OpenType features were disabled, I took for granted that that old
TrueType kerning was enabled when the modern OpenType kerning wasn't.
Now I know I was wrong. But I reported a bug at
https://savannah.gnu.org/projects/freefont/ and posted the PDF output
from ConTeXt.
ConTeXt is perfectly fine with FreeSerif, FreeSerif has valid kerning
and the problem is in the Sony PRS-T1 reader that cannot read the
kerning and ligature information.
I have even discovered that the Sony PRS-T1 ereader has a bug that
prevents the display of the FreeSerif bold font.
So, I knew that the ereader had some limitations, but I couldn't imagine
it was so buggy.
The annoying issue here is that reporting the bug may fix the issue and
Adobe might release a new version of the reader. But unless Sony
releases a new firmware, those bugs are there to stay.
Many thanks for your help and apologies for the confusion,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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:[~2012-11-30 23:57 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 7:06 Pablo Rodríguez
2012-11-30 9:13 ` Hans Hagen
2012-11-30 9:58 ` Steve White
2012-11-30 10:18 ` luigi scarso
2012-11-30 11:40 ` Steve White
2012-11-30 12:24 ` luigi scarso
2012-11-30 14:25 ` Steve White
2012-11-30 15:30 ` luigi scarso
2012-11-30 15:38 ` Hans Hagen
2012-11-30 18:12 ` Steve White
2012-11-30 18:22 ` Hans Hagen
2012-11-30 19:37 ` luigi scarso
2012-11-30 21:25 ` Steve White
2012-11-30 22:02 ` Hans Hagen
2012-11-30 23:57 ` Pablo Rodríguez [this message]
2012-12-01 16:22 ` Steve White
2012-12-01 19:22 ` luigi scarso
2012-12-01 19:38 ` Aditya Mahajan
2012-12-01 19:46 ` luigi scarso
2012-12-01 19:58 ` Aditya Mahajan
2012-12-01 21:09 ` luigi scarso
2012-12-02 9:58 ` Steve White
2012-12-02 13:12 ` Khaled Hosny
2012-12-02 14:32 ` Steve White
2012-12-02 14:49 ` Khaled Hosny
2012-12-02 10:10 ` Steve White
2012-12-02 10:24 ` luigi scarso
2012-12-02 10:43 ` Wolfgang Schuster
2012-12-02 11:08 ` Steve White
2012-12-02 11:48 ` luigi scarso
2012-11-30 15:43 ` Hans Hagen
2012-11-30 14:13 ` Khaled Hosny
2012-11-30 15:41 ` Hans Hagen
2012-11-30 16:05 ` Hans Hagen
2012-11-30 16:39 ` Bill Meahan
2012-11-30 18:08 ` Steve White
2012-11-30 19:07 ` Bill Meahan
2012-11-30 21:24 ` Steve White
2012-11-30 18:34 ` Steve White
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=50B947F4.5080404@web.de \
--to=oinos@web.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).