[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #50989] Incorrect generation of typesetting.pdf
From: |
Deri James |
Subject: |
[bug #50989] Incorrect generation of typesetting.pdf |
Date: |
Thu, 11 May 2017 17:27:58 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 |
Follow-up Comment #4, bug #50989 (project groff):
It looks like only the first block header is missing, there is one immediately
after the "eexec" which gives the length of the main block which is then
followed by another block which is the trailing "0"s. So it looks likely I can
do a sort of hybrid type which parses the first block as though it is a .pfa
and then check for a six byte chunk header (starts with \x80 which is not a
valid ascii hex character), and if found switch to .pfb type processing.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?50989>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [bug #50989] Incorrect generation of typesetting.pdf, Bertrand Garrigues, 2017/05/09
- [bug #50989] Incorrect generation of typesetting.pdf, Bertrand Garrigues, 2017/05/10
- [bug #50989] Incorrect generation of typesetting.pdf, Bertrand Garrigues, 2017/05/10
- [bug #50989] Incorrect generation of typesetting.pdf, Deri James, 2017/05/11
- [bug #50989] Incorrect generation of typesetting.pdf,
Deri James <=
- [bug #50989] Incorrect generation of typesetting.pdf, Werner LEMBERG, 2017/05/11
- [bug #50989] Incorrect generation of typesetting.pdf, Deri James, 2017/05/11
- [bug #50989] Incorrect generation of typesetting.pdf, Werner LEMBERG, 2017/05/11
- [bug #50989] Incorrect generation of typesetting.pdf, Bertrand Garrigues, 2017/05/14
- [bug #50989] Incorrect generation of typesetting.pdf, Deri James, 2017/05/14
- [bug #50989] Incorrect generation of typesetting.pdf, Werner LEMBERG, 2017/05/14