From: charles.unix.pro@gmail.com (Charles Anthony)
Subject: [TUHS] Character sets
Date: Sun, 27 Mar 2016 15:21:08 -0700 [thread overview]
Message-ID: <CANV78LQsKPMqN+jpbGFfz_HkGDJvQ6vvpE8z0kcimv4=-0Zfsw@mail.gmail.com> (raw)
In-Reply-To: <20160327215947.GT3766@eureka.lemis.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
On Sun, Mar 27, 2016 at 2:59 PM, Greg 'groggy' Lehey <grog at lemis.com> wrote:
> On Sunday, 27 March 2016 at 23:53:32 +0200, Johnny Billquist wrote:
> > On 2016-03-27 23:49, Greg 'groggy' Lehey wrote:
> >> On Sunday, 27 March 2016 at 13:47:43 +0200, Johnny Billquist wrote:
> >>> On 2016-03-27 13:29, John Cowan wrote:
> >>>> Johnny Billquist scripsit:
> >>>>
> >>>>> On 2016-03-27 08:18, Greg 'groggy' Lehey<grog at lemis.com> wrote:
> >>>>>> Isn't it wonderful that we no longer have issues with character
> >>>>>> representation?
> >
> > And let's not even talk about such wonderful concepts as colors in the
> > character set definition... Unicode seems to have it all... I wonder how
> > many code points exist for 'A'. It's definitely more than one...
>
> For some definition of A, of course. In addition there's clearly at
> least Α (0x391) and Р(0x410).
>
> ,∀, sᴉɥʇ ʇǝƃɹoɟ ʇ,uop
-- Charles
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160327/fa7c3ff4/attachment.html>
next prev parent reply other threads:[~2016-03-27 22:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.169.1459059516.15972.tuhs@minnie.tuhs.org>
2016-03-27 10:09 ` [TUHS] Character sets (was: Command-line options) Johnny Billquist
2016-03-27 11:29 ` John Cowan
2016-03-27 11:47 ` [TUHS] Character sets Johnny Billquist
2016-03-27 21:49 ` Greg 'groggy' Lehey
2016-03-27 21:53 ` Johnny Billquist
2016-03-27 21:59 ` Greg 'groggy' Lehey
2016-03-27 22:19 ` Johnny Billquist
2016-03-27 22:21 ` Charles Anthony [this message]
2016-03-27 23:23 ` Dave Horsfall
2016-03-28 0:20 ` John Cowan
2016-03-28 1:02 ` Dave Horsfall
2016-03-28 0:18 ` Johnny Billquist
2016-03-27 23:30 ` John Cowan
2016-03-27 23:56 ` Johnny Billquist
2016-03-28 1:54 ` John Cowan
2016-03-28 3:27 ` Steve Nickolas
2016-03-28 1:20 ` Random832
2016-03-28 1:58 ` John Cowan
2016-03-28 5:12 ` Random832
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='CANV78LQsKPMqN+jpbGFfz_HkGDJvQ6vvpE8z0kcimv4=-0Zfsw@mail.gmail.com' \
--to=charles.unix.pro@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).