Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > microsoft.public.scripting.vbscript > #12124

Re: Textstream Write

Show all headers | View raw

"JJ" <jj4public@vfemail.net> wrote

| The problem is still unexplained, tho. :(
|
| And that problem also means that with Unicode stream mode, it's still
| impossible to write UCS2 encoded file containing those unwrittenable
| characters.

  It is an intriguing problem. Since IE converts the
actual text to its own object model, I'm guessing
the actual format of the data it sends is a hybrid
and not just plain text. Slightly analogous to RTF.
If you copy RTF or HTML to the clipbaord and
paste into Notepad, you'll get only the text part.
Maybe IE is designed with the assumption that
when you ask for DIV1.innerHTML you intend to
use it within the context of the DOM.... Just a
guess. Since it's not a legitimate string I don't
know how to inspect it. It does return 8 (string)
when tested with VarType. In a test I got 56 for Len
and 112 for LenB. That seems to indicate unicode.
Maybe it could be handled in VB. I've written VBS to
convert unicode to ANSI, but it's quirky. (It's very
handy, though. I discovered that Windows has a lot
of intelligence built into the conversion. For instance,
if I convert Sanskrit S with what looks like an accent
I get S in ANSI. Nice. For an English speaker all those
technical marks are just noise, anyway. So I can
use my script to convert academic Sanskrit to popular
English book version of Sanskrit easily.)

  In any case, IE's quirk is not a problem for my purposes,
now that I know about it. I don't want unicode files. I
also don't have a problem with dropping out special
characters like an upside down triangle. I'm already
converting common UTF-8 characters like curly quotes,
non-breaking spaces, funky dashes, and o with umlaut
to ANSI equivalents. It's too much trouble to be switching
between encodings and it's completely unnecessary in
English.

  That's the first I've heard of UCS-2. I had to look it up.
It appears to be an outdated term. According to Wikipedia,
Windows unicode was derived from UCS-2 but is not UCS-2.
That gets confusing. It used to be there was ANSI and
unicode in the Windows world. Now with the popularity
of UTF-8 there are lots of unicodes. But it seems to be
safe to refer to Windows unicode as unicode-16. 

Back to microsoft.public.scripting.vbscript | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Textstream Write "Mayayana" <mayayana@invalid.nospam> - 2019-04-29 08:55 -0400
  Re: Textstream Write JJ <jj4public@vfemail.net> - 2019-04-30 17:45 +0700
    Re: Textstream Write "R.Wieser" <address@not.available> - 2019-04-30 13:21 +0200
  Re: Textstream Write "Mayayana" <mayayana@invalid.nospam> - 2019-04-30 08:51 -0400
    Re: Textstream Write "R.Wieser" <address@not.available> - 2019-04-30 18:22 +0200
      Re: Textstream Write "Mayayana" <mayayana@invalid.nospam> - 2019-04-30 13:01 -0400
        Re: Textstream Write "R.Wieser" <address@not.available> - 2019-04-30 21:37 +0200
          Re: Textstream Write "Mayayana" <mayayana@invalid.nospam> - 2019-04-30 17:06 -0400
            Re: Textstream Write "R.Wieser" <address@not.available> - 2019-05-01 10:01 +0200
              Re: Textstream Write "Mayayana" <mayayana@invalid.nospam> - 2019-05-01 08:37 -0400
                Re: Textstream Write "R.Wieser" <address@not.available> - 2019-05-01 16:00 +0200
                Re: Textstream Write "R.Wieser" <address@not.available> - 2019-05-01 16:12 +0200
                Re: Textstream Write "Mayayana" <mayayana@invalid.nospam> - 2019-05-01 10:47 -0400
                Re: Textstream Write "R.Wieser" <address@not.available> - 2019-05-01 19:09 +0200
  Re: Textstream Write "Mayayana" <mayayana@invalid.nospam> - 2019-05-04 15:26 -0400
    Re: Textstream Write JJ <jj4public@vfemail.net> - 2019-05-05 20:15 +0700
      Re: Textstream Write "Mayayana" <mayayana@invalid.nospam> - 2019-05-05 10:19 -0400

csiph-web