From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ncurses; I think I wrecked my fresh install
Date: Tue, 29 Dec 2020 18:01:18 -0500 [thread overview]
Message-ID: <X+u1PqhZNCPiT7hB@waltdnes.org> (raw)
In-Reply-To: <9095281.eNJFYEL58v@noumea>
On Tue, Dec 29, 2020 at 05:11:36PM +0200, Andreas K. Huettel wrote
> Hi Walter,
>
> > "-pch -roaming -sendmail -spell -tcpd -udev -udisks -unicode -upower
> > -xinerama"
>
> mostly out of curiosity, why do you want to disable unicode support
> here?
>
> This feels odd to me since utf8 has effectively become the standard
> encoding over the past years.
I don't know if this has improved over the years, but my initial
experience with unicode was rather negative. The fact that text
files were twice as large wasn't a major problem in itself. The
real showstopper was that importing text files into spreadsheets
and text-editors and word processors failed miseraby.
I looked at a unicode text file with a binary viewer. It turns out
that a simple text string like "1234" was actually...
"1" binary-zero "2" binary-zero "3" binary-zero "4" binary zero, etc.
This padding explains why the file was twice as large, and also why
"a simple textfile import" failed miserably.
On top of that Cyrillic letters like "m", "i", "c", and "o" are
considered different from their English equivalants. Security experts
showed proof-of-cocept attacks where clicking on "microsoft.com" can
take you to a hostile domain (queue the jokes). I don't speak or read
or write any languages which have thousands of unique characters.
Seeing Chinese spam "as it was intended to be seen", is not a priority
for me.
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
next prev parent reply other threads:[~2020-12-29 23:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 21:36 [gentoo-user] ncurses; I think I wrecked my fresh install Walter Dnes
2020-12-28 21:48 ` Arve Barsnes
2020-12-28 21:55 ` Dale
2020-12-28 22:52 ` tastytea
2020-12-29 2:54 ` Walter Dnes
2021-01-19 2:21 ` Walter Dnes
2021-01-19 13:15 ` Andreas K. Hüttel
2020-12-29 15:11 ` Andreas K. Huettel
2020-12-29 21:17 ` [gentoo-user] " Grant Edwards
2020-12-29 23:01 ` Walter Dnes [this message]
2020-12-30 1:04 ` Grant Edwards
2020-12-30 9:23 ` Wols Lists
2020-12-30 16:35 ` [gentoo-user] " Andreas K. Huettel
2020-12-30 17:42 ` antlists
2020-12-30 17:30 ` Andreas K. Huettel
2020-12-30 18:01 ` antlists
2020-12-30 18:14 ` Andreas K. Huettel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=X+u1PqhZNCPiT7hB@waltdnes.org \
--to=waltdnes@waltdnes.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox