On Mon, Nov 30, 2009 at 03:56:16PM +0100, Corinna Vinschen wrote:
>On Nov 30 15:33, Thomas Wolff wrote:
>> Andy Koppe wrote:
>> >2009/11/29 Linda Walsh:
>> They are actually listed in all CJK character sets (checking i18n
>> data). Whether this was really used or not, it makes their view as
>> "pre
On Nov 30 15:33, Thomas Wolff wrote:
> Andy Koppe wrote:
> >2009/11/29 Linda Walsh:
> They are actually listed in all CJK character sets (checking i18n
> data). Whether this was really used or not, it makes their view as
> "presentation forms" weaker.
>
> >>_I_ use those [wide ASCII chars] in file
Andy Koppe wrote:
2009/11/29 Linda Walsh:
I'm aware that this would reserve the 'display forms'
of those chars and map them them to their real forms when
interpreted within cygwin. I don't see this to be a problem.
But it is a problem. It would make it impossible to use the wide
2009/11/29 Linda Walsh:
> I'm aware that this would reserve the 'display forms'
> of those chars and map them them to their real forms when
> interpreted within cygwin. I don't see this to be a problem.
But it is a problem. It would make it impossible to use the wide forms
of those deadly
Eric Blake wrote:
Rather than complaining, write a patch to prove your point. Patches speak
much louder than rants on open source projects. But I won't be the one
writing the patch.
I already supplied code in the first email. It's a matter of
using those constants instead of the
On Nov 28 13:53, Corinna Vinschen wrote:
> Besides, we have not only to map the few
> characters you're talking about, the U+f0XX range is also used to
> map invalid UTF-8 chars.
Oh, and all control characters from 0x01 to 0x1f.
The only feasible alternative to the U+f0XX range would be one of th
On Nov 28 05:19, Eric Blake wrote:
> According to Linda Walsh on 11/28/2009 3:24 AM:
> > Any other standards group I know of is going UTF-8. All of the
> > linux distributions I know are going UTF-8. I'd like to see Cygwin
> > go that way too.
I don't understand this one. What on earth are you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Linda Walsh on 11/28/2009 3:24 AM:
> But barring any other changes, I'd really, (like pretty please!)
> like to see them mapped to their, reserved-visual, but semantically
> impotent equivalents.
http://cygwin.com/acronyms/#PTC
Rather
# Eric Blake:...
[believes he has round trip mapping and that it is more valuable]
than user's being able to identify their files in the OS GUI or
on a linux server]
# Linda W. replies to Eric:
[points out that the current system already uses valid Unicode values
(as others have poin
Corinna Vinschen wrote:
On Nov 23 20:29, Linda Walsh wrote:
Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Linda Walsh on 11/23/2009 4:59 PM:
Instead of using random characters out of the 'random free area' --
which could display as anything if you
On Nov 24 09:50, Corinna Vinschen wrote:
> On Nov 23 20:29, Linda Walsh wrote:
> > Eric Blake wrote:
> > >But then, how would you distinguish between the valid UTF-16 replacement
> > >used to represent an invalid character, and a valid UTF-16 character
> > >representing itself? I'm sorry, but the
On Nov 23 20:29, Linda Walsh wrote:
> Eric Blake wrote:
> >-BEGIN PGP SIGNED MESSAGE-
> >Hash: SHA1
> >
> >According to Linda Walsh on 11/23/2009 4:59 PM:
> >>Instead of using random characters out of the 'random free area' --
> >>which could display as anything if you aren't in cygwin, dep
Eric Blake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Linda Walsh on 11/23/2009 4:59 PM:
Instead of using random characters out of the 'random free area' --
which could display as anything if you aren't in cygwin, depending
on what charset you have loaded, why not use 'd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Linda Walsh on 11/23/2009 4:59 PM:
> Instead of using random characters out of the 'random free area' --
> which could display as anything if you aren't in cygwin, depending
> on what charset you have loaded, why not use 'dedicated' unico
Was thinking about a 1 or 2 mods for the new characters that are being remapped
to the 'private area', but also a compatibility bug.
Maybe I'll get the bug out of the way first.
Filenames created on a samba share are not visible on the server
as anything resembling what I used on Cygwin. I see
15 matches
Mail list logo
