FaqPostscriptOutputProblems
From AbiWiki
(Importing text file) |
|||
| Line 1: | Line 1: | ||
| + | ---- | ||
| + | <div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;"> | ||
| + | ---- | ||
| + | =[http://amofuryqimu.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]= | ||
| + | ---- | ||
| + | =[http://amofuryqimu.co.cc CLICK HERE]= | ||
| + | ---- | ||
| + | </div> | ||
| - | + | <H2>FAQ: Postscript Output Problems</H2> | |
==== Question
==== | ==== Question
==== | ||
| Line 8: | Line 16: | ||
All my postscript output comes out with some spaces converted to backspaces randomly!! The result is that words are run together and sometimes even overlap. Weird. I did a google search, and found that somebody posted this to the Debian (I am using Slackware) folks as a bug, but there was no detectable followup. | All my postscript output comes out with some spaces converted to backspaces randomly!! The result is that words are run together and sometimes even overlap. Weird. I did a google search, and found that somebody posted this to the Debian (I am using Slackware) folks as a bug, but there was no detectable followup. | ||
| - | Somebody did mention that rtf support was *not* broken, and that exporting rtf and printing that from | + | Somebody did mention that rtf support was *not* broken, and that exporting rtf and printing that from <nowiki>[[OpenOffice|OpenOffice]]</nowiki> worked!! |
What happened to the postscript output after 1.0.3 and why is it only affecting (apparently) a small number of users? | What happened to the postscript output after 1.0.3 and why is it only affecting (apparently) a small number of users? | ||
| Line 16: | Line 24: | ||
_From a post by Dom Lachowicz on 25 Sept 2003:_ | _From a post by Dom Lachowicz on 25 Sept 2003:_ | ||
| - | + | <blockquote> | |
| - | This behavior *could* be caused by our use of a | + | This behavior *could* be caused by our use of a "characterWidths" array. We don''t translate spaces into backspaces (postscript has no concept of a backspace, anyway). We translate them into moveto() operations, which just happen to move PS''s pen "backwards" on the page. |
I don''t know why this is going wrong for you. It works fine here and everywhere else I''ve tried. Does it happen for just some particular fonts? | I don''t know why this is going wrong for you. It works fine here and everywhere else I''ve tried. Does it happen for just some particular fonts? | ||
| - | + | </blockquote> | |
| - | Apparently this is not a known bug — if you are interested in getting it fixed you should add it to [http://bugzilla.abisource.com bugzilla], and you may wish to join the abiword-users@abisource.com mailing list. | + | Apparently this is not a known bug &mdash; if you are interested in getting it fixed you should add it to [http://bugzilla.abisource.com bugzilla], and you may wish to join the abiword-users@abisource.com mailing list. |
==== Contributors
==== | ==== Contributors
==== | ||
Revision as of 11:35, 24 November 2010
<H2>FAQ: Postscript Output Problems</H2>
Question
I am finding that all postscript output (to printer or file) is mangled since AbiWord 1.0.4 and including 2.0. Since everyone seems happy with AbiWord, I assume I am doing something to make my postscript output bad.
All my postscript output comes out with some spaces converted to backspaces randomly!! The result is that words are run together and sometimes even overlap. Weird. I did a google search, and found that somebody posted this to the Debian (I am using Slackware) folks as a bug, but there was no detectable followup.
Somebody did mention that rtf support was *not* broken, and that exporting rtf and printing that from <nowiki>OpenOffice</nowiki> worked!!
What happened to the postscript output after 1.0.3 and why is it only affecting (apparently) a small number of users?
Response
_From a post by Dom Lachowicz on 25 Sept 2003:_
<blockquote> This behavior *could* be caused by our use of a "characterWidths" array. We dont translate spaces into backspaces (postscript has no concept of a backspace, anyway). We translate them into moveto() operations, which just happen to move PSs pen "backwards" on the page.
I dont know why this is going wrong for you. It works fine here and everywhere else Ive tried. Does it happen for just some particular fonts? </blockquote>
Apparently this is not a known bug — if you are interested in getting it fixed you should add it to bugzilla, and you may wish to join the abiword-users@abisource.com mailing list.
Contributors
- Main.PhilEhrens - 22 Sep 2003
