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

installincludes, bsd.incs.mk and param.h

2014-10-14 Thread Harald Schmalzbauer
Hello, since bsd.port.mk insinsts on param.h, I have inconveniences on my production systems which were installed with WITHOUT_TOOLCHAIN=true in src.conf (resulting in MK_TOOLCHAIN=no). My first attempt was the following patch: --- share/mk/bsd.incs.mk.orig 2014-10-14 16:35:53.0 +0200

Re: installincludes, bsd.incs.mk and param.h

2014-10-14 Thread David Wolfskill
On Tue, Oct 14, 2014 at 04:42:57PM +0200, Harald Schmalzbauer wrote: Hello, since bsd.port.mk insinsts on param.h, I have inconveniences on my production systems which were installed with WITHOUT_TOOLCHAIN=true in src.conf (resulting in MK_TOOLCHAIN=no). My first attempt was the

Re: installincludes, bsd.incs.mk and param.h

2014-10-14 Thread Harald Schmalzbauer
Bezüglich David Wolfskill's Nachricht vom 14.10.2014 16:52 (localtime): On Tue, Oct 14, 2014 at 04:42:57PM +0200, Harald Schmalzbauer wrote: Hello, since bsd.port.mk insinsts on param.h, I have inconveniences on my production systems which were installed with WITHOUT_TOOLCHAIN=true in

Re: installincludes, bsd.incs.mk and param.h

2014-10-14 Thread Ian Lepore
On Tue, 2014-10-14 at 17:24 +0200, Harald Schmalzbauer wrote: Bezüglich David Wolfskill's Nachricht vom 14.10.2014 16:52 (localtime): On Tue, Oct 14, 2014 at 04:42:57PM +0200, Harald Schmalzbauer wrote: Hello, since bsd.port.mk insinsts on param.h, I have inconveniences on my

Re: installincludes, bsd.incs.mk and param.h

2014-10-14 Thread Harald Schmalzbauer
Bezüglich Ian Lepore's Nachricht vom 14.10.2014 17:37 (localtime): ... It appears that while bsd.ports.mk has lost the ability to use the version of the running system (sysctl kern.osreldate), it still has the logic to just use OSVERSION if it's already set on the make command line or in the

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: installincludes, bsd.incs.mk and param.h

2014-10-14 Thread Ian Lepore
On Tue, 2014-10-14 at 18:09 +0200, Harald Schmalzbauer wrote: Bezüglich Ian Lepore's Nachricht vom 14.10.2014 17:37 (localtime): ... It appears that while bsd.ports.mk has lost the ability to use the version of the running system (sysctl kern.osreldate), it still has the logic to just use

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:

FreeBSD Quarterly Status Report - Third Quarter 2014

2014-10-14 Thread Benjamin Kaduk
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 FreeBSD Project Quarterly Status Report: July - September 2014 This report covers FreeBSD-related projects between July and September 2014. This is the third of four reports planned for 2014. The third quarter of 2014 was another