public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-user@lists.gentoo.org
Cc: Walter Dnes <waltdnes@waltdnes.org>
Subject: Re: [gentoo-user] ncurses; I think I wrecked my fresh install
Date: Wed, 30 Dec 2020 18:35:03 +0200	[thread overview]
Message-ID: <4587102.OV4Wx5bFTl@noumea> (raw)
In-Reply-To: <X+u1PqhZNCPiT7hB@waltdnes.org>

[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]

>   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.

That's (as someone has already pointed out) UTF-16, which is the default for 
some Windows tools (but understood in Linux too). (Even UTF-32 exists where 
all characters are 4 byte wide, but I've never seen it in the wild.)

UTF-8 is normally used on Linux (and ASCII chars look exactly the same there); 
even for "long characters" outside the ASCII range spreadsheets and word 
processors should not be a problem anymore.

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer 
(council, qa, toolchain, base-system, perl, libreoffice)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2020-12-30 16:35 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   ` [gentoo-user] " Walter Dnes
2020-12-30  1:04     ` [gentoo-user] " Grant Edwards
2020-12-30  9:23       ` Wols Lists
2020-12-30 16:35     ` Andreas K. Huettel [this message]
2020-12-30 17:42       ` [gentoo-user] " 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=4587102.OV4Wx5bFTl@noumea \
    --to=dilfridge@gentoo.org \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=waltdnes@waltdnes.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