Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Problems with non-ascii filenames
- X-seq: zsh-workers 26648
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: Problems with non-ascii filenames
- Date: Sat, 28 Feb 2009 15:06:58 -0800
- In-reply-to: <200902282235.52527.arvidjaar@xxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <19e566510902280137s3bb02510te650364cb03145a9@xxxxxxxxxxxxxx> <090228102250.ZM3434@xxxxxxxxxxxxxxxxxxxxxx> <200902282235.52527.arvidjaar@xxxxxxxxx>
On Feb 28, 10:35pm, Andrey Borzenkov wrote:
}
} > Wolfgang, if you're reading this, something that I forgot to mention
} > in my reply to you is that sometime during 4.3.x zsh began to pay
} > closer attention to characters that are absent from the declared LANG
} > character set and to either refuse to process them at all, or to
} > render them as digits surrounded by angle brackets.
}
} Unfortunately that does not play nicely with PRINTEIGHTBIT.
Well, yes and no. One could argue that PRINTEIGHTBIT doesn't mean
"print multibyte as raw bytes" but rather "if the character set is
not multibyte then print characters even if the high bit is set."
However, I agree that --enable-multibyte should not have the effect
of changing the behavior on single-byte I/O where the high bit happens
to be set.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author