ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: buggy extra space after ff ligature
Date: Tue, 24 Mar 2015 09:03:18 +0100	[thread overview]
Message-ID: <D138DC71-5D5D-4D28-8D8E-E5B0473607B2@gmail.com> (raw)
In-Reply-To: <551045D1.2050408@gmx.es>

[-- Attachment #1: Type: text/plain, Size: 230 bytes --]

Hi Pablo,

I can confirm that the first « ff » ligature has an extra space, as it may be seen in the attached PDF.
(Running ConTeXt  ver: 2015.03.10 12:09 MKIV beta  fmt: 2015.3.17  int: english/english)

Best regards: OK

[-- Attachment #2: ff-ligature.pdf --]
[-- Type: application/pdf, Size: 8162 bytes --]

[-- Attachment #3: Type: text/plain, Size: 1137 bytes --]


> On 23 Mar 2015, at 17:56, Pablo Rodriguez <oinos@gmx.es> wrote:
> 
> Dear list,
> 
> I’m afraid I’ve hit a bug:
> 
>    \setuphyphenation[method=traditional]
>    \definefontfeature[default][default][itlc=yes]
>    \setupitaliccorrection[global,always]
> 
>    \setuphead[section][style=\it]
>    \starttext
>    \section{Different Efficiencies}
>    \section{Different Effectivity}
>    \stoptext
> 
> The first title has an extra space after the ff ligature. I think this
> may be a bug.
> 
> Could anyone confirm it?
> 
> Many thanks for your help,
> 
> 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
> ___________________________________________________________________________________


[-- Attachment #4: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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:[~2015-03-24  8:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23 16:56 Pablo Rodriguez
2015-03-24  8:03 ` Otared Kavian [this message]

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=D138DC71-5D5D-4D28-8D8E-E5B0473607B2@gmail.com \
    --to=otared@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).