Kaixo!

On Wed, Apr 11, 2001 at 12:54:16AM +0200, Werner LEMBERG wrote:
 
> > That's not the problem.  The problem is it is *impossible* to know
> > for sure what encoding is used in the source troff file; there is no
> > charset=....  line.
> 
> The planned groff 2.0 will use the same syntax as Emacs to define the
> input character set, i.e. the first line contains
> 
>   -*- coding: foo -*-
> 
> in a comment.

How exactly, eg:

.\" -*- coding: iso-8859-1 -*-

> This info will then be forwarded to a preprocessor
> which converts the man page to UTF-8.

But the output requested by the user may be different of utf-8.
Is it planned to add conversion capabilities?

-- 
Ki �a vos v�ye b�n,
Pablo Saratxaga

http://www.srtxg.easynet.be/            PGP Key available, key ID: 0x8F0E4975
-
Linux-UTF8:   i18n of Linux on all levels
Archive:      http://mail.nl.linux.org/lists/

Reply via email to