> > I think an upstream only wants to adhere to the language specification > (groff_char(7)). These small differences became prominent with the advent > of > UTF-8 capable terminals. They have always been visible in a PostScript > output. > > Imagine you are the upstream and a user sends you a bug report that groff > does > not behave according to the specification. While another user complains > that > his nonconforming input behaves weirdly. There is no solution which would > satisfy both. >
I totally understand why they made the change, I just don't see the reason for requesting them to put the mapping back. I think the right decision would be that upstreams of the packages that have the man pages written with the wrong character, should be the ones to fix their man pages. However, I'm not very confident that they would willingly do that, and not sure if there are enough volunteers to do that for them. That being said, the new groff version with the mapping for the old characters is now in stable for both Fedora 39 and Fedora Rawhide. On Thu, Nov 9, 2023 at 12:41 PM Petr Pisar <ppi...@redhat.com> wrote: > V Thu, Nov 09, 2023 at 12:11:55PM +0100, Lukas Javorsky napsal(a): > > > > > > Did we try to persuade upstream to revert the problem? But if they're > > > not receptive then a downstream fix aligned with Debian looks right. > > > > > > > I didn't yet. However, if they decided to stop mapping these characters, > I > > don't think they would be willing to revert it back. They mentioned the > > option to map it locally as I did in the PR. I assume they want to stop > > mapping it on their end and let distros decide if they want to do it > > themselves. > > > I think an upstream only wants to adhere to the language specification > (groff_char(7)). These small differences became prominent with the advent > of > UTF-8 capable terminals. They have always been visible in a PostScript > output. > > Imagine you are the upstream and a user sends you a bug report that groff > does > not behave according to the specification. While another user complains > that > his nonconforming input behaves weirdly. There is no solution which would > satisfy both. > > -- Petr > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- S pozdravom/ Best regards Lukáš Javorský Software Engineer, Core service - Databases Red Hat <https://www.redhat.com> Purkyňova 115 (TPB-C) 612 00 Brno - Královo Pole ljavo...@redhat.com <https://www.redhat.com>
-- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
