apostrophe/single-quote is curly (wrong) not straight in PE/PDFDirect PDFs in ArialMT

[naglists]

I hate special characters.

Does anyone know how to control the presentation of apostrophes (decimal 39)
in PDFs generated on Publishing Engine by PDF Direct (not Distiller) in the
Arial font? I am getting a curly apostrophe in the Arial MT font. (I doubt
Arial MT is actually the problem, but I mention it just because.) I can use
charent.cf to map the output of ' to a good old fashioned
straight-quote / non-curly-apostrophe ... decimal 39. But this doesn't fix
the ' character itself ...

--
Paul Nagai

[naglists]

I should say my charent.cf solution works in theory. I haven't rolled it out
to my Publishing Engine environment where I have, possibly in a different
authoring environment than the one I'm currently bumping into ' problems,
had charent.cf solutions fail in the content pipeline due to multiple
parsings ...

With Styler, peservices=off, Print Composer, my Stylersheet, no profiling
selected, and DLM engaged (there's one leg of a pipeline), I was able to
control the PDF's content. (Ok, just checked, it works with profiling, too
... maybe I'll be ok in prod ... assuming I can convince my authors its
acceptable to change every instance of ' to ' ... yeah, that would be a
fun conversation 😉

[ClayHelberg]

Hi Paul-



If you searched the archives at all on this, you probably found some old
posts of mine on the subject. I did eventually figure out what the
problem was. There's a setting in your pipeline that originates in
epicGenerator.ent that controls this.



If you're still using 5.3 or earlier. In my 5.3 version, the relevant
entry from $EPIC/composer/epicGenerator.ent looks like this:



<parameter id="epicGenerator.convertSingleQuote"&lt;br"/>name="convertSingleQuote" type="boolean" required="no">

<label>Convert Single Quote to Right Curly Quote</label>

<documentation>This parameter determines whether single quote ('
#39)

should be converted into ’ (#8217) before
sent to pipeline.

Default is true.

</documentation>

</parameter>



So you might get a win on this by customizing your pdf.ccf (or your

[PaulGrosso]

I looked at SPR 1646473, and there are a lot of complicated technical
notes (including a mentino of the pipeline stuff Clay discusses), but
one other thing I found was a mention of set
composedcharactersubstitution (see help topic 7557) that might be of
help.



As Clay mentions, in 5.4, we changed the behavior (effectively setting
composedcharactersubstitution to off instead of on as it was in 5.3).



paul

[BobSpangenburg]

Paul,

I came across the same issue. Even though we had the ' entity in use, we would get the curly apostrophe published. Then I found the "set composedcharactersubstitution = no"command and entered it into our initialization files. The issue went away.

Hope this helps.

Bob

[naglists]

Thanks, Bob. Am working with support. Dynamic Link Manager is involved in my
particular instance of the curly apos.

On Mon, May 24, 2010 at 5:59 AM, Bob Spangenburg <
-> wrote:

> Paul,
>
> I came across the same issue. Even though we had the ' entity in use,
> we would get the curly apostrophe published. Then I found the "set
> composedcharactersubstitution = no" command and entered it into our
> initialization files. The issue went away.
>
> Hope this helps.
>
> Bob
>

[naglists]

Support has opened SPR 1988168 for a future 5.3 service release. The problem
does not exist in 5.4. They have, in the mean time, provided me with
customized comp_pdf.acl and pdf.ccf files. I have not had a chance to test
them yet and likely won't until after PTC/User (Fire UP!) but will let you
know how that goes when it goes.