From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25043 invoked by alias); 18 Dec 2014 17:59:19 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 19564 Received: (qmail 18334 invoked from network); 18 Dec 2014 17:59:07 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI, SPF_HELO_PASS autolearn=ham version=3.3.2 X-AuditID: cbfec7f5-b7fc86d0000066b7-ba-5493138bf7a3 Date: Thu, 18 Dec 2014 17:48:55 +0000 From: Peter Stephenson To: zsh-users@zsh.org Subject: Re: utf-8 Message-id: <20141218174855.3aaa00dd@pwslap01u.europe.root.pri> In-reply-to: <549310A1.4080602@eastlink.ca> References: <5491C5E7.1070207@eastlink.ca> <20141218092544.01495a40@pwslap01u.europe.root.pri> <549310A1.4080602@eastlink.ca> Organization: Samsung Cambridge Solution Centre X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: quoted-printable X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrKLMWRmVeSWpSXmKPExsVy+t/xK7rdwpNDDM7fErHYcXIlowOjx6qD H5gCGKO4bFJSczLLUov07RK4Mt6cu8Fa8FuwomnlUZYGxn28XYycHBICJhKHF61jgrDFJC7c W88GYgsJLGWUeL41EMJexCTR9Ny/i5ELyN7GKPFlyzmwIhYBVYk561azgNhsAoYSUzfNZgSx RQREJZav2MwOYgsLCElM2jQXbAGvgL3EmRPdYL2cAtoSDavfskIMbWSUWDPrP1iCX0Bf4urf T1AX2UvMvHKGEaJZUOLH5Htgy5gF1CUmzVvEDGFrSzx5d4EV4lJ1iRt3d7NPYBSahaRlFpKW WUhaFjAyr2IUTS1NLihOSs810itOzC0uzUvXS87P3cQICdqvOxiXHrM6xCjAwajEw5uQOylE iDWxrLgy9xCjBAezkghvDNvkECHelMTKqtSi/Pii0pzU4kOMTBycUg2Mx3qEqre5P939Knmb bfuTp3MPcNi4bOBL2+rysKHfv+W135PHPHfX9JlXfXmxlIFTpfpjiPWDMBOf0OQ3DkZzmj7u 5t787E2Jgkpj0r9NAQeDzzAv5ODL0DO69nneVL+Ff2SDLc6npl6Id6n5/dvELCNKNux2Prtu w5LoU0kLFFkOBp7xMklRYinOSDTUYi4qTgQA7lJ58jgCAAA= On Thu, 18 Dec 2014 09:36:33 -0800 Ray Andrews wrote: > On 12/18/2014 01:25 AM, Peter Stephenson wrote: >=20 > Mikael, Peter: >=20 > > Chapter 5 of the FAQ is the best place to start. You can see this=20 > > online at http://zsh.sourceforge.net/FAQ/zshfaq05.html#l52. The=20 > > version in Etc of the source is newer but I don't think there are=20 > > significant differences. pws=20 >=20 > Very nicely written. That's exactly what I wanted to learn. And tho I=20 > knew it > previously, I had semi forgotten the difference between unicode and utf-8, > which lead to the fuzzy question. To ask it again more accurately, where = are > extended unicode characters permitted? Or perhaps that's better reversed, > where are they *not* permitted? Can a variable have a name beyond ASCII? > I see that zsh is transparent to utf-8 everywhere, but that does not pres= ume > that one has use of the entire unicode charset in all situations. Yes, correct. Most syntax is pinned down --- either something is a keyword or something like a decimal number from a fixed set, or it's any old string. Identifiers are an exception. There's an option for this. POSIX_IDENTIFIERS When this option is set, only the ASCII characters a to z, A to Z, 0 to 9 and _ may be used in identifiers (names of shell parameters and modules). When the option is unset and multibyte character support is enabled (i.e. it is compiled in and the option MULTIBYTE is set), then additionally any alphanumeric characters in the local character set may be used in identifiers. Note that scripts and functions written with this feature are not portable, and also that both options must be set before the script or function is parsed; setting them during execution is not sufficient as the syntax variable=3Dvalue has already been parsed as a command rather than an assignment. If multibyte character support is not compiled into the shell this option is ignored; all octets with the top bit set may be used in identifiers. This is non-standard but is the tradi=E2= =80=90 tional zsh behaviour. pws