ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Rik Kabel <context@rik.users.panix.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Hyphens missing (again) with setupbackend[export
Date: Sun, 23 Jul 2017 21:51:14 -0400	[thread overview]
Message-ID: <a66aaa9b-a625-3442-1077-e857a5ba16e2@rik.users.panix.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 870 bytes --]

Aditya came across this in 2011 ([NTG-context] export kills hyphen 
symbol 
<https://www.mail-archive.com/ntg-context@ntg.nl/msg58460.html>)[1] with 
the Fontin font. It wasn’t answered then. It is back if it ever left.

Here is an example:

    \definefontfamily
         [TestFont]
         [rm]
         [Antykwa Torunska Cond]
    \setupbodyfont
         [TestFont]
    \setupbackend
         [export=maybe]% or yes, or no, or ...
    \setuppapersize
         [A7]
    \starttext
    \input ward
    \stoptext

If the \setupbackend statement is removed, or an invalid key is used, 
all is well. It fails with a valid key and any value for that key.

I am experiencing the problem of missing hyphens with this font even 
without \setupbackend, but cannot yet construct a working example.

-- 
Rik

[1] https://www.mail-archive.com/ntg-context@ntg.nl/msg58460.html


[-- Attachment #1.2: Type: text/html, Size: 1499 bytes --]

[-- Attachment #2: Type: text/plain, Size: 492 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2017-07-24  1:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24  1:51 Rik Kabel [this message]
2017-07-24  9:51 ` Hans Hagen
2017-07-24 11:54   ` Rik
2017-07-24 13:24     ` Hans Hagen
2017-07-26 16:56       ` Henning Hraban Ramm

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=a66aaa9b-a625-3442-1077-e857a5ba16e2@rik.users.panix.com \
    --to=context@rik.users.panix.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).