encoding and dsc problems

[Manfred Meyer]

hi,

i use a2ps in my latest project. it works fine but i have a few
questions and feedback.

- when i try to use the output encoding "cp1250" with a windows
installation of a2ps (argument "-X cp1250") then the character "à"
(that's an "a" with "accent grave") is not displayed correctly. An "r"
with "accent egu" is printed instead. in the postscript code the command
"\340" is used for it, no matter with which codepage. is this a bug?
that's the only character that makes troubles in my document.

- another issue that occurs when i use the encoding cp1250 is a problem
with the document structure comments (DSC) of the resulting postscript.
a2ps creates nested resources. inside font resources there are other
resources like encodings and "compose procsets". for a printer this in
not a problem, but i'd like to do some postprocessing on the postscript
and my tools for that have problems with nested resources. does the DSC
specification allow nested resources? could the ps code be simplified
somehow?

- at the beginning of the ps document a2ps creates code that looks like
this:
        /a2psdict 200 dict def
        a2psdict begin
        %%BeginProlog
the definition of a2psdict is before the prolog and therefore outside
any document structure element. this causes again troubles for my
ps postprocessing tools. couldn't these lines be reordered like this:
        %%BeginProlog
        /a2psdict 200 dict def
        a2psdict begin
that would help me a lot.

- and the last question: is there a way to specify custom media types on
the command line of a2ps instead of writing them into "a2ps.cfg" or
"a2ps-site.cfg".

i would greatly appreciate if you answer my questions,
manfred.




-- 
Freundliche Grüsse
OUTLINE AG

Manfred Meyer
Software-Entwicklung

mailto:address@hidden

Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern
Tel +41 41 317 2020 - Fax +41 41 317 2029
Internet http://www.outline.ch