Re: [Groff] Re: man page encoding

2005-07-08 Thread Andries Brouwer
On Thu, Jul 07, 2005 at 10:55:35PM +0200, Bruno Haible wrote: > Andries, > > > It is not at all an unimportant detail whether it changes to utf-8 or > > ascii with escape sequences. My own preprocessors halfway that pipeline > > do not know about utf-8, and do not know about these escape sequences

Re: [Groff] Re: man page encoding

2005-07-08 Thread Andries Brouwer
On Thu, Jul 07, 2005 at 09:40:34PM +0200, Bruno Haible wrote: > Andries Brouwer wrote: > > If there is a pipeline, then earlier > > stages in the pipeline already need the character set. > > So, conversion may have to be done before the input reaches groff. > Btw, if a

Re: [Groff] Re: man page encoding

2005-07-07 Thread Andries Brouwer
On Thu, Jul 07, 2005 at 11:54:40AM +0200, Werner LEMBERG wrote: > >.\" t -*- coding: EUC-JP -*- > > What's the `t'? I muttered that there already are various conventions for stuff that has to be on the first line. One of them is the old convention that if the first line has '\" t or '\" e o

Re: [Groff] Re: man page encoding

2005-07-07 Thread Andries Brouwer
On Thu, Jul 07, 2005 at 01:12:33PM -0400, Zvezdan Petkovic wrote: > On Wed, Jul 06, 2005 at 03:36:07PM +0200, Andries Brouwer wrote: > > I am not really aware of use of groff other than as a backend to man. > > Now, you are a little upset with Bruno's response, so you are se

Re: [Groff] man page encoding

2005-07-07 Thread Andries Brouwer
On Thu, Jul 07, 2005 at 11:04:24AM +0200, Werner LEMBERG wrote: > The tag in the header makes groff call a > preprocessor which inserts a proper encoding filter. Which means that man should not call iconv when output is to groff, while it should call iconv when output goes elsewhere. Ugly. Andr

[Groff] Re: man page encoding

2005-07-06 Thread Andries Brouwer
On Wed, Jul 06, 2005 at 01:50:31PM +0200, Bruno Haible wrote: Hi Bruno, Some of your answer sounds as if you interpret my reply differently than I had intended. On the other hand, I do not disagree with your proposed plan. One wants something like (1) a system-wide default, (2) a user locale tha

[Groff] Re: man page encoding

2005-07-06 Thread Andries Brouwer
On Tue, Jul 05, 2005 at 07:41:13PM +0200, Bruno Haible wrote: > Andries, > > Currently on a Linux system you find man pages in the following encodings: > - ISO-8859-1 (German, Spanish, French, Italian, Brasilian, ...), > - ISO-8859-2 (Hungarian, Polish, ...), > - KOI8-R (Russian), > - EUC

[Groff] Re: viewing UTF-8 encoded man pages

2005-07-05 Thread Andries Brouwer
On Mon, Jul 04, 2005 at 01:15:34PM +0200, Bruno Haible wrote: > Is someone aware of an easy way to view UTF-8 encoded man pages? > So far, groff supports only Latin1 encoded input, i.e. it does not support > Greek, Russian, Japanese, Chinese, Vietnamese etc. manpages. Hmm. Long ago I added some c

[Groff] Re: backspace and Unicode in terminals

2005-03-17 Thread Andries Brouwer
On Thu, Mar 17, 2005 at 09:24:23AM +0100, Werner LEMBERG wrote: > > I'm going to improve grotty, the TTY backend of groff, so that it can > handle zero-width and double-width characters, as needed for proper > Unicode support. > > Doing so I wonder how is the backspace character (U+0008, \b) hand