groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unable to get GROFF_ENCODING to seep through to sourced subfiles


From: G. Branden Robinson
Subject: Re: Unable to get GROFF_ENCODING to seep through to sourced subfiles
Date: Mon, 16 Nov 2020 00:14:34 +1100
User-agent: NeoMutt/20180716

At 2020-11-14T18:54:14+0100, Pierre-Jean Fichet wrote:
> Hello alls,
> 
> Steffen Nurpmeso <steffen@sdaoden.eu> wrote:
> > This is a groff pipeline fault (or preconv should vanish and any
> > file opened should internally be handled by the right encoding,
> > which i think would be even better), also see
> >
> >   https://lists.gnu.org/archive/html/groff/2017-07/msg00027.html
> 
> I must add here that refer bibliography lists are not parsed by
> preconv either, and macro files neither.
> 
> Should I insist on the fact that limits the usability of groff a lot
> outside of the default english?

These observations may strengthen the perceived utility of my proposed
enhancements to preconv(1), which are a much shorter pole than native
UTF-8 support.

Converting such files to _maintainable_ ISO 646 documents may prove
useful.

That is, if it is actually true that groff bibliographers will tolerate
maintaining a document that contains

%A: Jean-Paul Fa\[,c]onni\['e]re \['E]pist\['e]m\[^e]

over

%A: Jean-Paul Fa\[u00E7]onni\[u00E8]re \[u00C9]pist\[u00E8]m\[u00EA]

for instance.

Regards,
Branden

[1] https://savannah.gnu.org/bugs/?58796

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]