Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Aug 2021 09:45:30 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   =?UTF-8?B?W0J1ZyAyNTc5MDVdIG1pc2Mvc2NoaWx5dG9vbHMgQ2hhcmFjdGVy?= =?UTF-8?B?IO+/vSBkaXNwbGF5ZWQgaW5zdGVhZCBvZiDDtg==?=
Message-ID:  <bug-257905-7788-UNRh3KpIkI@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-257905-7788@https.bugs.freebsd.org/bugzilla/>
References:  <bug-257905-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D257905

--- Comment #4 from Robert Clausecker <fuz@fuz.su> ---
(In reply to J=C3=B6rg Schilling from comment #3)

J=C3=B6rg,

The error is reproducible in any standard UTF-8 locale.  I am not sure what
your pager does, but this sounds a lot like it takes input and inteprets it=
 in
a different locale than it is supposed to be.

Do you really consider not implementing UTF-8 in an intentionally defective
manner to be =E2=80=9Cinsufficient behaviour?=E2=80=9D  Also note that Germ=
any is not the navel
of the word and people do use 8-bit character sets other than ISO 8859-1.  =
So
for any country other than Germany, even the hack you have implemented in p
would yield defective results in the general case and be plain useless.

For example, consider a Japanese user whose native 8-bit encoding is Shift-=
JIS.
 What do you think this use thinks if your p turns his Shift-JIS documents =
into
umlauts?

There's really no excuse for you not adapting the copyright string to the
correct locale, or at least transliterate with oe if the encoding is not
ISO-8859-1.

As for translation files, GNU gettext supports automatically generating mis=
sing
strings from strings of other character sets for the same language.  So just
internationalising the software without any .mo files might already solve t=
he
problem I think.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-257905-7788-UNRh3KpIkI>