Issue 56374 - No space characters in Postscript
Summary: No space characters in Postscript
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 2.0
Hardware: All All
: P3 Trivial (vote)
Target Milestone: AOO PleaseHelp
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2005-10-21 14:07 UTC by jkon
Modified: 2013-07-30 02:13 UTC (History)
1 user (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---

Example file which shows the described behaviour (29.12 KB, application/postscript)
2005-10-21 16:01 UTC, jkon
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description jkon 2005-10-21 14:07:58 UTC
The generated Postscript by the printing engine does not contain space character
(\n, \t, ' ', and maybe others).
When I try to get the ASCII Text out of the postscript file using ps2ascii,
which comes with the standard gs installation on Linux, there is no space
character present.
This Bug might seem a bit esoteric, but it is important in Enterprise solutions.
Doing the same thing with MS-Word works just fine.
Comment 1 philipp.lohmann 2005-10-21 15:41:27 UTC
I guess you talk about Windows since spaces occur in Writer PostScript output on
Unix; however newlines, tabs and other control characters are not output
anywhere. Which is not only a gsl issue since writer simply does not output them.
Comment 2 jkon 2005-10-21 15:46:27 UTC
No, i was actually talking about Linux.
It also happens printing from one Linux mashine via cups onto another Linux box.
The Postscript on the remote mashine is than wihtout space characters as
described above.
Comment 3 philipp.lohmann 2005-10-21 15:50:19 UTC
Interesting. I just printed to file with an m124 build and see many <20> in
there (which are spaces). This may be filtered out by the CUPS server then,
during some PostScript to PostScript filtering ?
Comment 4 jkon 2005-10-21 16:00:24 UTC
The effect also occurs when printing directly into a file, i suppose no cups is
involved than.
In the "graphical view" with "gv" for example i see the document formated
correctly, but when i try to extract the text with ps2ascii it fails.
I attach an example file to this bugreport
Comment 5 jkon 2005-10-21 16:01:35 UTC
Created attachment 30702 [details]
Example file which shows the described behaviour
Comment 6 philipp.lohmann 2005-10-21 16:09:02 UTC
Ok, there are the two spaces supposed to be in there (as mentioned the 20
entries in the hex strings), but you are of course right, ps2ascii does not see
Comment 7 Rob Weir 2013-07-30 02:13:52 UTC
Reset assignee on issues not touched by assignee in more than 2000 days.