Re: printing text file with LPD - non-printable characters

2014-10-14 Thread Beeblebrox
Enscript does not support UTF-8 formatted text files, so it's not usable in this case. One solution, is to use paps, instead of Enscript, for converting UTF-8 encoded text to PostScript. http://www.linuxfromscratch.org/blfs/view/svn/pst/enscript.html Another (which I prefer) solution is to send

Re: printing text file with LPD - non-printable characters

2014-10-14 Thread Matthias Apitz
El día Tuesday, October 14, 2014 a las 01:19:42AM -0700, Beeblebrox escribió: Enscript does not support UTF-8 formatted text files, so it's not usable in this case. One solution, is to use paps, instead of Enscript, for converting UTF-8 encoded text to PostScript.

Re: printing text file with LPD - non-printable characters

2014-10-14 Thread Beeblebrox
We are using in production environments CUPS in the version 1.4.3; this has a component 'texttops' which supports UTF-8 encoded text (only) and prints UTF-8 nicely on the fly. Thanks for the input. Unfortunately, CUPS has been broken for me since May/14.

Re: printing text file with LPD - non-printable characters

2014-10-14 Thread Matthias Apitz
El día Tuesday, October 14, 2014 a las 02:26:37AM -0700, Beeblebrox escribió: We are using in production environments CUPS in the version 1.4.3; this has a component 'texttops' which supports UTF-8 encoded text (only) and prints UTF-8 nicely on the fly. Thanks for the input.

Re: printing text file with LPD - non-printable characters

2014-10-14 Thread Beeblebrox
@Matthias: This is one of the reasons we stick with 1.4.3. How? Did you create a self-maintained port for it? How did you overcome the problem of CUPS-dependent ports pulling in 1.7.3 in poudriere? Regards. - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in

Re: printing text file with LPD - non-printable characters

2014-10-14 Thread Matthias Apitz
El día Tuesday, October 14, 2014 a las 03:07:10AM -0700, Beeblebrox escribió: @Matthias: I'm not '@Matthias', but Matthias, and I think, the @ sign is normaly used to express user@host or @domain; This is one of the reasons we stick with 1.4.3. How? Did you create a self-maintained port

Re: printing text file with LPD - non-printable characters

2014-10-14 Thread Don Lewis
On 14 Oct, Beeblebrox wrote: We are using in production environments CUPS in the version 1.4.3; this has a component 'texttops' which supports UTF-8 encoded text (only) and prints UTF-8 nicely on the fly. Thanks for the input. Unfortunately, CUPS has been broken for me since May/14.

Re: printing text file with LPD - non-printable characters

2014-10-14 Thread Beeblebrox
@Don: I think it (cups) also broke for me around that timeframe until I found that I also needed cups-filters. You sir, are a life saver! Thank you for the tip. [SOLVED] - FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS -- View this message in context:

Re: printing text file with LPD - non-printable characters

2014-10-05 Thread Matthias Apitz
El día Sunday, October 05, 2014 a las 10:41:43AM -0700, Beeblebrox escribió: I have two LPD errors 1. I see two characters being replaced by strings on the hard copy (the {â} below is an {a^}). This happens on the first page and not on following pages. instead of I get: â\200\234 (235 for