Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > microsoft.public.scripting.vbscript > #12264
| From | "R.Wieser" <address@not.available> |
|---|---|
| Newsgroups | microsoft.public.scripting.vbscript |
| Subject | Re: file.ReadAll - another quirk |
| Date | 2019-11-23 09:19 +0100 |
| Organization | Aioe.org NNTP Server |
| Message-ID | <qraq3k$1sh$1@gioia.aioe.org> (permalink) |
| References | (5 earlier) <1133f73l5pkpq$.1czqy5zm4hvoi.dlg@40tude.net> <qr8t33$1j3e$1@gioia.aioe.org> <qr8tqi$tsl$1@dont-email.me> <qr96d7$v89$1@gioia.aioe.org> <qr9rm7$qmh$1@dont-email.me> |
Mayayana, > I'm using the Windows terms, which are not always > the same as what other people use. That (different names for the same encoding) might well be part of my problem ... I ofcourse know ASCII, and later on ANSI. > Unicode - 2-byte characters as used in Windows, Which I remember as "Wide character" (as the name used in the conversion function). > which may not be the same as all unicode 16 and Did I already mention I'm hazy with those names ? Whell, stuff like that (two-byte unicode != unicode 16) certainly does that to me. :-) > It gets confusing because "multi-byte" sounds like > unicode but instead refers to ANSI encoding which > *could* use multiple bytes. > (You probably know that, too, but I'm not sure how > many others do.) Yep, I do know. And for some reason I got the idea that UTF-8 was referring to that encoding scheme. I normally refer to it as "multi byte" (again, from the conversion function). Than again, I seem to vaguely remember that UTF-16 (two bytes per character) could do the same "multi byte" encoding ... > and if they used UTF-8 it would potentially change > the number of characters when rendered as ANSI Yep. Which I would/do not find strange in any way. The same happens with C strings, in which you have to escape certain characters (gave me quite a puzzle the first time I encountered it). :-) Regards, Rudy Wieser
Back to microsoft.public.scripting.vbscript | Previous | Next — Previous in thread | Next in thread | Find similar
file.ReadAll - another quirk "R.Wieser" <address@not.available> - 2019-11-20 12:54 +0100
Re: file.ReadAll - another quirk "Mayayana" <mayayana@invalid.nospam> - 2019-11-20 08:39 -0500
Re: file.ReadAll - another quirk JJ <jj4public@vfemail.net> - 2019-11-22 00:00 +0700
Re: file.ReadAll - another quirk "Mayayana" <mayayana@invalid.nospam> - 2019-11-21 12:50 -0500
Re: file.ReadAll - another quirk "R.Wieser" <address@not.available> - 2019-11-21 20:39 +0100
Re: file.ReadAll - another quirk "Mayayana" <mayayana@invalid.nospam> - 2019-11-21 15:04 -0500
Re: file.ReadAll - another quirk "R.Wieser" <address@not.available> - 2019-11-21 21:46 +0100
Re: file.ReadAll - another quirk "Mayayana" <mayayana@invalid.nospam> - 2019-11-21 16:31 -0500
Re: file.ReadAll - another quirk "R.Wieser" <address@not.available> - 2019-11-22 09:23 +0100
Re: file.ReadAll - another quirk "Mayayana" <mayayana@invalid.nospam> - 2019-11-22 09:14 -0500
Re: file.ReadAll - another quirk "R.Wieser" <address@not.available> - 2019-11-22 15:58 +0100
Re: file.ReadAll - another quirk JJ <jj4public@vfemail.net> - 2019-11-22 19:13 +0700
Re: file.ReadAll - another quirk "R.Wieser" <address@not.available> - 2019-11-22 15:47 +0100
Re: file.ReadAll - another quirk "Mayayana" <mayayana@invalid.nospam> - 2019-11-22 10:10 -0500
Re: file.ReadAll - another quirk "R.Wieser" <address@not.available> - 2019-11-22 18:37 +0100
Re: file.ReadAll - another quirk "Mayayana" <mayayana@invalid.nospam> - 2019-11-22 18:40 -0500
Re: file.ReadAll - another quirk "R.Wieser" <address@not.available> - 2019-11-23 09:19 +0100
Re: file.ReadAll - another quirk "Mayayana" <mayayana@invalid.nospam> - 2019-11-23 10:09 -0500
Re: file.ReadAll - another quirk "R.Wieser" <address@not.available> - 2019-11-23 17:36 +0100
Re: file.ReadAll - another quirk JJ <jj4public@vfemail.net> - 2019-11-22 19:10 +0700
csiph-web