Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 18 Aug 2021 08:02:34 +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-HGyHB5dBvf@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 #11 from J=C3=B6rg Schilling <schily@schily.net> ---
Internationalization is based on support for various different encodings.

It is a mistake to assume only a single "globally" used encoding, regardles=
s of
which encodig this is. So assuming UTF-8 is also a mistake.

Maybe my conclusion is not yet understood:

UNICODE is an extension to the range of ISO-8859-1 and software that suppor=
ts
UNICODE should be written in a way to support that. My pager p(1) does this=
.=20

The only other method that currently could help is to install gettext () ba=
sed
translations to the english language, even in case that the source language=
 is
english as well. This is currently the only other widely supported method to
permit a hidden iconv() call to the output.

BTW: other authors seem to have resignated with internationalization and ju=
st
do not write their names correctly to avoid problems in similar cases.

--=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-HGyHB5dBvf>