Thomas Wolff wrote:

With a file name, soffice does TRY to print but also it fails
to print apparently because it depends on a properly configured
Unix printer channel.

Yes, and lpr has to be able to handle PostScript through some
'input filter'.

Can it be told to just produce PostScript output?

No. With -p the output goes directly to the print queue. Actually
it is possible to get ps output on the command line but it is
*very* difficult. You have to install a macro in Openoffice and
then issue a complicated command. This is not really feasible for
'ordinary users'. I forgot to make notes so I have to reconstruct
it, but I started from

http://www.oooforum.org/forum/viewtopic.phtml?t=4163

I'll try to explain off-list (when I have re-discovered how to do
it) as this is not a UTF-8 issue by itself.

Since cups is claimed to be capable of printing UTF-8, [..]

Learning about CUPS is still on my todo list.. have always only
used lpr(ng).

This is not surprising with a proportional font. Try paps
--family fixed, it produced perfect output of your file here (although not of all files, however).

Didn't work. But the spacing became OK when I tried paps --family
monospace. This may be Debian jargon. But I would not call it
perfect (not really pretty like with ooprint); the right-edge of
the sudoku was "wobbly". Must have something to do with the way
pango selects fonts (which I do not understand at all), it is
anyway not based on something Courier-like but on something
sans-serif.

Please try chmod +x /usr/share/mined/uprint. I wonder how this
failed to install properly. Did you install mined from its
source package or from some other package (e.g. SuSE)?

A package -- Debian unstable, mined 2000.10-2. There are a lot of
files in /usr/shared/mined which appear to be scripts, none of
which is executable. Maybe it is Debian policy to turn the x bits
off in /usr/shared? None of the files there has "paps" in them
though. Printing (through uniprint) works now, but very
imperfectly; most 'exotic' characters become boxes with hex digits.

Can you please try right-to-left and combining characters? See
the file enclosed.

ooffice / ooprint at first refused to print the file; it hung. It
printed only after I removed _one_ character: the MS-DOS line end
(carriage return). The combining characters were OK, but the
right-side of the boxes was wobbly as if some random spaces had
been inserted or deleted. Wonder if anybody else tried this.

N.B. ooffice cannot, alas, print 'arbitrary' text files; trying to
print a small html source file (even when renamed with extension
.txt) caused a window to appear announcing that Openoffice had
crashed! I don't know why. So not only does it not like MS-DOS
line ends; it also does not like html tags. Not good for a text
printer. The search for a good utf-8 text print system is not yet
over..

Regards, Jan



--
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/linux-utf8/

Reply via email to