You are correct that full UTF-16 is supported for annotations, the
problem is that by the time the string is passed to pdfbookmark the
characters have been changed to named glyph nodes which I believe
can't be converted back to their UTF-16 character code
(i.e. \[u0159]) within a macro,
Dear Werner,
On Thu, Mar 29, 2012 at 06:53, Werner LEMBERG w...@gnu.org wrote:
# generate.pe
Open($1);
Generate($fontname + .pfa); # this also generates the .afm file
Generate($fontname + .t42);
Call this with e.g.
fontforge -script generate.pe GS_CE_.TTF
Fontforge worked like
Hello,
I am having trouble typesetting Czech. This is the first time I
actually tried a language with extensive punctuation.
I have a set of Gill Sans CE that contains the proper glyphs. I have
converted these to groff fonts as described in the mom docs.
However I still end up with errors and
My question is whether this is caused by incorrect font conversion
or if the problem lies somewhere else.
To help you, we need a minimal example which exposes the problem,
together with all the necessary stuff (including fonts).
Werner
This is a (painful) limitation of Adobe's pdfmark specification:
only a rather limited set of characters is permitted within the text
which is specified to describe a bookmark.
This is not correct, AFAIK. There are two encodings for pdfbookmarks,
namely PDFDocEncoding and Unicode. So it
On Wed, Mar 28, 2012 at 15:29, Deri James d...@chuzzlewit.demon.co.uk wrote:
Are you talking about missing from the bookmark ouitline panel or missing from
the text of the document?
Missing from outline = each \X warning indicates a character was dropped. (For
the reason Keith gave).
Missing
Example text should read:
Příliš žluťoučký kůň úpěl ďábelské ódy.
with iconv '-futf8' '-tlatin2', pipe to groff, doesn't complain:
Píli lu»ouký k úpl ábelské ódy.
But this is not correct usage. groff internally uses latin1 encoding.
If you really want to use latin2, you must explicitly
groff internally uses latin1 encoding.
Mhmm, bad wording. latin1 is just the default setup for all backends
except -Tutf8.
Werner
On Wed, Mar 28, 2012 at 18:27, Werner LEMBERG w...@gnu.org wrote:
But this is not correct usage. groff internally uses latin1 encoding.
However, if you replace the `-Tutf8' backend with `-Tps', you get a
bunch of warnings because the standard PS fonts don't have all
necessary glyphs.
On 28/03/12 16:09, Petr Man wrote:
Keith clarified,
I didn't...
that the errors came from pdfroff,
...because they don't.
I thought they were from groff directly.
They are; specifically, when groff processes this...
.nop \X'ps:exec [\\$* pdfmark'\c
...expression as it expands a
On Wednesday 28 Mar 2012 16:02:01 Werner LEMBERG wrote:
This is a (painful) limitation of Adobe's pdfmark specification:
only a rather limited set of characters is permitted within the text
which is specified to describe a bookmark.
This is not correct, AFAIK. There are two encodings for
On Thu, Mar 29, 2012, Werner Lemberg wrote:
As I previously wrote, I used the method from mom's manual.
Interesting. I don't have time to verify the steps (and I don't know
some of the involved programs), but you did it, and you failed. So
maybe the instructions should be revised. Peter?
12 matches
Mail list logo
