On 5/10/11 9:17 AM, Greg Wooledge wrote:
>>> Is the accented character
>>> a single-byte character, or a multi-byte character, in your locale?
>>
>> a multi-byte character, i think
>> How to confirm that ?
(Keep in mind as you read my answers that I know very little more than
anyone else about Un
Chet Ramey writes:
> On 5/10/11 9:17 AM, Greg Wooledge wrote:
>
>> In yours, however, it is 0x65 0xcc 0x81 which is U+0065 LATIN SMALL
>> LETTER E followed by U+0301 COMBINING ACUTE ACCENT.
>
> That's not valid UTF-8, since UTF-8 requires that the shortest sequence
> be used to encode a character
On 5/15/11 6:38 PM, Andreas Schwab wrote:
> Chet Ramey writes:
>
>> On 5/10/11 9:17 AM, Greg Wooledge wrote:
>>
>>> In yours, however, it is 0x65 0xcc 0x81 which is U+0065 LATIN SMALL
>>> LETTER E followed by U+0301 COMBINING ACUTE ACCENT.
>>
>> That's not valid UTF-8, since UTF-8 requires that t
On 5/15/11 6:16 PM, Chet Ramey wrote:
> The other difference is that drag-and-drop on Mac OS X (at least dropping
> from the finder) produces full pathnames. I was able to reproduce display
> problems (which I haven't yet investigated) using that, but not using
> tab completion in the way you did
