Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

Re: utf-8



19.12.2014, 00:17, "Ray Andrews" <rayandrews@xxxxxxxxxxx>:
> 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.



Messages sorted by: Reverse Date, Date, Thread, Author