Re: ripping out EBCDIC (cp1047)/preparing for UTF-8 input

[G. Branden Robinson]

At 2024-05-14T17:29:16-0500, Dave Kemper wrote:
> On Tue, May 14, 2024 at 8:53 AM G. Branden Robinson
> <g.branden.robinson@gmail.com> wrote:
> > I aim to drop EBCDIC a.k.a.
> > code page (CCSID) 1047 support from groff 1.24.
> 
> No objection to this.
> 
> > The idea is, for 1.24, to get everybody migrating to pure ASCII
> > input documents (as might be generated by preconv(1)) by the time
> > GNU troff sees them.
> 
> I don't strongly object, but I wonder about the advisability of
> requiring preconv on a wide swath of documents that didn't previously
> require it while Savannah #59442 (preconv vs soelim) and #65108
> (handling encoding of filenames) are unresolved.

As far as the wide swath goes, I think that's going to be inescapable
for a UTF-8 future.  If your character set used the eighth bit of the
byte, it's not going to mean the same thing in UTF-8.

Regarding #59442, I updated the ticket yesterday to get concrete, having
been blocked on mere imaginings of how things worked.

https://savannah.gnu.org/bugs/?59442

> Are support for EBCDIC and for Latin-1 tightly enough coupled in the
> code that it's unnecessarily complex to remove the former while
> retaining the latter?

Not at all.

Regards,
Branden

signature.asc
Description: PGP signature