ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: simple question on kerning activation
Date: Tue, 27 Nov 2012 22:58:49 +0100	[thread overview]
Message-ID: <38A8521E-D5CD-44D2-BFF2-0DC40F7E4129@gmail.com> (raw)
In-Reply-To: <50B533F1.6070103@web.de>


Am 27.11.2012 um 22:43 schrieb Pablo Rodríguez <oinos@web.de>:

> On 27/11/12 22:34, Wolfgang Schuster wrote:
>> Am 27.11.2012 um 20:34 schrieb Pablo Rodríguez <oinos@web.de>:
>> [...]
>>> Probably my font is newer (from
>>> http://ftp.gnu.org/gnu/freefont/freefont-ttf-20120503.zip).
>>> 
>>> I think there is no file clash, since ConTeXt standalone doesn't provide the font
>> 
>> The font files from the gnu page have no kerning but the files from
>> http://de.fonts2u.com/free-serif.schriftart have kerning information.
> 
> Many thanks for your reply, Wolfgang.
> 
> I'd like to report this to the font developer (he has assured me that
> the fonts have kerning).
> 
> How have you discovered that the Savannah FreeSerif fonts have no
> kerning info?

That’s not what I wanted to write. I had the same thought as Hans with the missing
for the “default” script (AFAIR this was also a problem with other fonts in the past)
but I wanted to test it first but he was faster than me.

Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2012-11-27 21:58 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26 19:01 Pablo Rodríguez
2012-11-26 20:39 ` Hans Hagen
2012-11-26 22:04   ` Pablo Rodríguez
2012-11-26 22:46     ` Hans Hagen
2012-11-27 16:57       ` Pablo Rodríguez
     [not found]         ` <50B4F2B9.4070206@wxs.nl>
2012-11-27 17:36           ` Pablo Rodríguez
2012-11-27 17:42             ` luigi scarso
2012-11-27 17:46               ` Pablo Rodríguez
2012-11-27 17:49                 ` luigi scarso
2012-11-27 17:56             ` Hans Hagen
2012-11-27 19:34               ` Pablo Rodríguez
2012-11-27 21:34                 ` Wolfgang Schuster
2012-11-27 21:43                   ` Pablo Rodríguez
2012-11-27 21:58                     ` Wolfgang Schuster [this message]
2012-11-27 22:10                       ` Hans Hagen
2012-11-28 17:17                         ` Pablo Rodríguez
2012-11-27 21:39                 ` Hans Hagen
2012-11-27 21:48                 ` Hans Hagen
2012-11-26 23:11     ` Wolfgang Schuster
2012-11-27 16:59       ` Pablo Rodríguez
2012-11-27 17:11         ` luigi scarso
2012-11-28  9:01           ` Hans Hagen
2012-11-28  9:13             ` Wolfgang Schuster

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=38A8521E-D5CD-44D2-BFF2-0DC40F7E4129@gmail.com \
    --to=wolfgang.schuster@gmail.com \
    --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).