Hermes 0.9.5 released

May 9th, 2006 by Romeo Anghelache

Hermes got updated: a few more fonts, a bit more stylish, and a cleaner document structure.

It is a step closer to a Hermes document schema.

If you have requests, comments, questions, suggestions, please use this place, so other readers can use the info here to get a more detailed view of what Hermes is about.

3 Responses to “Hermes 0.9.5 released”

  1. didier Says:

    Hi Romeo,
    How do you determine what characters a font maps to? Is there a table available somewhere? How did you determine that fonts eccc and p1xbsc map to the same sets of characters?

  2. didier Says:

    Hi,
    It looks like the pub.xslt stylesheet doesn’t like lists (like those created by enumerate, itemize). Here’s a test file:
    documentclass{article}
    begin{document}
    begin{itemize}
    Some text
    item item 1
    end{itemize}
    end{document}

    Here’s the output I get from xsltproc:
    parsing error:
    last token received was ‘FontChange’
    test-enumerate.lib:13: parser error : Premature end of data in tag ph line 12
    test-enumerate.lib:13: parser error : Premature end of data in tag env line 11
    test-enumerate.lib:13: parser error : Premature end of data in tag section line 10
    test-enumerate.lib:13: parser error : Premature end of data in tag document line 2

  3. Romeo Anghelache Says:

    Hi Didier,

    The mapping, I did it one by one: glyph names or just looks in the TeX font onto the Unicode closest equivalent, based on looks, name or comments around it. There may be such a table used in iconv, but I never looked into it, so I’m not sure. I preferred making my own mapping because I want to have full control over every detail and glyph semantics.

    Now for the eccc and p1xbsc, this must be a mistake of mine, as eccc is not boldfaced so it’ll be fixed. Their common encoding is EC.