At 2020-11-14T18:54:14+0100, Pierre-Jean Fichet wrote: > Hello alls, > > Steffen Nurpmeso <stef...@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
signature.asc
Description: PGP signature
