Re: Apostrophes not coming out curly in ConTeXt output

[Aditya Mahajan <adityam-63aXycvo3TyHXe+LvDLADg@public.gmane.org>]

On Sun, 18 Mar 2012, John Magolske wrote:

> * John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> [120318 22:24]:
>> I'm no ConTeXt expert, but I just did a little experiment, and
>> context seemed to interpret the apostrophe the same way as
>> latex does -- turning it into a curly apostrophe.
>>
>> Does it show up straight when you generate a PDF from your
>> source using context?
>
> The apostrophe is turning up straight in the PDF output by ConTeXt.
> The only way I can get a curly apostrophe is to edit the *.tex file
> and manually change the U0027 characters to curly U2019's.

I am assuming that you are using MkIV and not MkII.

By default, the translation of 0x0027 to 0x2019 is controlled by a font 
feature `tlig`. `tlig` is enabled in the default font features, so either 
something is wrong with your font (unlikely, as in that case 0x2019 will 
also not work) or your typesscripts.

In your example below, if I comment out your typescripts then I get curly 
apostrophe. This means that you are missing something in your typescripts.

>> If so, we may need to see what your context preamble looks like
>> (assuming you're not using the default pandoc template).  I think
>> that with fontspec you can disable interpretation of latex
>> ligatures.  Maybe that's what you're doing?
>
> I did change a few things in the pandoc template, but I can't make out
> if any of that would be affecting this apostrophe issue. Here's the
> full test-1.tex file:
>
> \usetypescriptfile[type-lemonde]
> \usetypescript[lemond-1]
> \setupbodyfont[LeMonde,11pt]

As I said, most likely something is missing in your typescript files. 
However, if you are using MkIV, the simplest way to use system fonts is to 
use the simplefonts module:

\usemodule[simplefonts][size=11pt]
\setmainfont[LeMonde]

This should give you the right apostrophe.

Aditya