On 2014-04-21, Lex Trotman <[email protected]> wrote:
> On 22 April 2014 07:38, Grant Edwards <[email protected]> wrote:
>> On 2014-04-21, Grant Edwards <[email protected]> wrote:
>>> Recently, the fop back end has started rendering foo->bar as foo#bar
>>> in PDF output. It shows up as a proper right-arrow in HTML output. It
>>> looks like the XML output has → in that spot, and various
>>> references show that as the Unicode "rightwards arrow"
>>> codepoint/character/entity/glyph/widget/whatever-the-hell-it's-called.
>>>
>>> IIRC, the PDF output used to be correct, and I'm not sure exactly when
>>> it got broken.
>
> How good is your memory ;) The part of asciidoc that replaces -> with
> → has been there since 2007.
Like I said, I'm pretty sure this is a fop problem, not an asciidoc
problem. I would have sworn fop used to handle it, but I've dug up
some pdf files from a few years ago, and it looks like it's always
been broken.
> With a2x -v I see the message from fop:
>
> Glyph "→" (0x2192, arrowright) not available in font "Times-Roman".
Doh! Adding a -v get's me the same thing. It hadn't occurred to me
that the default verbosity level would supress actual errors.
--
Grant Edwards grant.b.edwards Yow! Did I SELL OUT yet??
at
gmail.com
--
You received this message because you are subscribed to the Google Groups
"asciidoc" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/asciidoc.
For more options, visit https://groups.google.com/d/optout.
