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 mang
> 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
On 28 March 2012 11:53, Petr Man wrote:
> Hello,
>
> I am having trouble typesetting Czech.
> ...
>
> My typical command line looks like this:
> pdfroff -M. -F. -Tps -p -t -e -g -R -s -k -Dutf8 -mmymom -mpdfmark
> --report-progress --no-toc-relocation -dpaper=a4 -P-pa4
> --pdf-output=rng.pdf rng.mo
On Wed, Mar 28, 2012 at 14:20, Keith Marshall
wrote:
> rng.mom:156: a special character is invalid within \X
>
> 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. St
On Wednesday 28 Mar 2012 13:56:57 Petr Man wrote:
>
> Hello Keith,
> thanks, that clears the errors for start. Yet I still end up with
> missing čřž etc characters.
> Petr
Are you talking about missing from the bookmark ouitline panel or missing from
the text of the document?
Missing from outli
> 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 s
On Wed, Mar 28, 2012 at 15:29, Deri James 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 from document = proba
> 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 explicitl
> 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 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.
>
> Instead of u
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 .pd
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 encodi
>> Much easier, much shorter.
>
> that is very much what I would like to use. And I tried, I actually
> use it always by default, but I still end up with missing
> characters. You didn't have by any chance have a look at the
> file/fonts I mailed you off-list? I suspect I simply didn't convert
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. P
> 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,
15 matches
Mail list logo
