From: ZyX <kp-pav@yandex.ru>
To: Ray Andrews <rayandrews@eastlink.ca>,
"zsh-users@zsh.org" <zsh-users@zsh.org>
Subject: Re: utf-8
Date: Fri, 19 Dec 2014 00:38:08 +0300 [thread overview]
Message-ID: <256161418938688@web19g.yandex.ru> (raw)
In-Reply-To: <5493440A.5010908@eastlink.ca>
19.12.2014, 00:17, "Ray Andrews" <rayandrews@eastlink.ca>:
> On 12/18/2014 12:52 PM, ZyX wrote:
>> http://www.unicode.org/Public/UCD/latest/ucd/UnicodeData.txt, third
>> column. Read
>> http://www.unicode.org/reports/tr44/tr44-14.html#General_Category_Values
>> for the explanation of the values, you need L* and N* (note: testing
>> shows that not all N* are relevant: No is not (test: CIRCLED DIGIT
>> ONE), N is not as well (test: VULGAR FRACTION ONE QUARTER), Nd (DIGIT
>> ONE, FULLWIDTH DIGIT ONE) and No (RUNIC ARLAUG SYMBOL) are). I highly
>> suggest seeking answer in libc sources if you need better precision.
>
> It is very generous. I can think of only one more question. What
> happens in a language 'above' normal ASCII with things like escapes?
> Like if you were writing in Russian:
>
> echo "\nRussian is a very expressive language.\n"
>
> .... if that was in Cyrillic characters, how does one indicate '\n' ?
`\n`. Escapes are defined by zsh parser, not by anything else. Same for any other language. There is not much reasoning behind translating characters after `\` and I have never seen them actually translated in any language, no matter whether it allows unicode identifiers or not.
next prev parent reply other threads:[~2014-12-18 21:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 18:05 utf-8 Ray Andrews
2014-12-17 20:31 ` utf-8 ZyX
2014-12-18 0:39 ` utf-8 Ray Andrews
2014-12-18 6:48 ` utf-8 Павлов Николай Александрович
2014-12-18 9:25 ` utf-8 Mikael Magnusson
2014-12-18 9:25 ` utf-8 Peter Stephenson
2014-12-18 17:36 ` utf-8 Ray Andrews
2014-12-18 17:48 ` utf-8 Peter Stephenson
2014-12-18 18:14 ` utf-8 Ray Andrews
2014-12-18 18:22 ` utf-8 ZyX
2014-12-18 18:05 ` utf-8 ZyX
2014-12-18 18:41 ` utf-8 Ray Andrews
2014-12-18 18:52 ` utf-8 ZyX
2014-12-18 20:04 ` utf-8 Ray Andrews
2014-12-18 20:12 ` utf-8 Peter Stephenson
2014-12-18 20:52 ` utf-8 ZyX
2014-12-18 21:15 ` utf-8 Ray Andrews
2014-12-18 21:38 ` ZyX [this message]
2014-12-18 23:55 ` utf-8 Ray Andrews
2014-12-19 2:04 ` utf-8 Bart Schaefer
2014-12-19 2:27 ` utf-8 Ray Andrews
2014-12-19 2:32 ` utf-8 Mikael Magnusson
2014-12-19 2:45 ` utf-8 Bart Schaefer
2014-12-19 6:34 ` utf-8 Ray Andrews
2014-12-19 7:02 ` utf-8 Bart Schaefer
2014-12-19 17:04 ` utf-8 Ray Andrews
2014-12-19 22:06 ` utf-8 ZyX
2014-12-19 7:29 ` utf-8 Павлов Николай Александрович
2014-12-19 3:50 ` utf-8 Lawrence Velázquez
2014-12-19 5:24 ` utf-8 Павлов Николай Александрович
2014-12-19 5:18 ` utf-8 Павлов Николай Александрович
[not found] <BC9BC140-F1A5-11D5-BA73-000393164560@mas.ecp.fr>
2001-12-18 16:51 ` UTF-8 Oliver Kiddle
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=256161418938688@web19g.yandex.ru \
--to=kp-pav@yandex.ru \
--cc=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).