ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: John Magolske <listmail@b79.net>
To: ntg-context@ntg.nl
Subject: Apostrophes not converting to typographical curly apostrophes
Date: Wed, 21 Mar 2012 23:32:57 -0700	[thread overview]
Message-ID: <20120322063256.GC23312@s70206.gridserver.com> (raw)

I'm having difficulty getting straight 0x0027 apostrophes to convert
into typographical single-quotes when using a given typescript.

In the following example, \quote{single quotes} generates curly
typographical single quotes, but the apostrophe comes out as a
straight apostrophe in the PDF output:

    \usetypescriptfile[type-lemonde]
    \usetypescript[lemonde-1]
    \setupbodyfont[lemonde,ss,11pt]
    \starttext
    Why don't the apostrophes show up as \quotation{curly}? The
    \quote{single quotes} and \quotation{double quotes} are fine\ldots{}
    \stoptext

The only way I can generate curly apostrophes is by placing 0x2019
characters into the source. However, when I comment out those first
three lines, the output displays a curly apostrophe fine in the default
font. Am I doing something wrong with how I've set up my typescript?

~/texmf/tex/context/user/type-lemonde.tex looks like this:

\starttypescript [serif] [lemonde]
    \definefontsynonym [LeMondeLivre-Roman]  [name:lemondelivrenormalosf]
    \definefontsynonym [LeMondeLivre-Bold]   [name:lemondelivreboldosf]
    \definefontsynonym [LeMondeLivre-Italic] [name:lemondelivreitalicosf]
    \definefontsynonym [Serif]               [LeMondeLivre-Roman]
    \definefontsynonym [SerifBold]           [LeMondeLivre-Bold]
    \definefontsynonym [SerifItalic]         [LeMondeLivre-Italic]
\stoptypescript

\starttypescript [sans] [lemonde]
    \definefontsynonym [LeMondeSans-Roman]   [name:lemondesansnormalosf]
    \definefontsynonym [LeMondeSans-Bold]    [name:lemondesansboldosf]
    \definefontsynonym [LeMondeSans-Italic]  [name:lemondesansitalicosf]
    \definefontsynonym [Sans]                [LeMondeSans-Roman]
    \definefontsynonym [SansBold]            [LeMondeSans-Bold]
    \definefontsynonym [SansItalic]          [LeMondeSans-Italic]
\stoptypescript

\starttypescript [lemonde-1]
    \definetypeface [lemonde] [rm] [serif]    [lemonde]
    \definetypeface [lemonde] [ss] [sans]     [lemonde]
\stoptypescript


This is using MkIV, recently updated minimals.

Thanks for any help,

John

-- 
John Magolske
http://B79.net/contact
___________________________________________________________________________________
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-03-22  6:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22  6:32 John Magolske [this message]
2012-03-22 21:43 ` Hans Hagen
2012-03-27  4:34   ` John Magolske
2012-03-27  7:52     ` 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=20120322063256.GC23312@s70206.gridserver.com \
    --to=listmail@b79.net \
    --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).