• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Weird error
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Weird error


  • Subject: Re: Weird error
  • From: "Arthur J. Knapp" <email@hidden>
  • Date: Wed, 24 Sep 2003 09:49:21 -0400

> Date: Tue, 23 Sep 2003 18:52:58 -0500
> Subject: Re: Weird error
> From: John Fowler <email@hidden>

>> ... the code that creates the data in the first place? Is it producing
>> old fashioned ASCII text or has it started using UTF-8 or UTF16?

That's an interesting point. I've been out of the loop for a while,
how do the text item delimiters handle UTF-8 and UTF-16?


> The code is created by a .asp process which I assume means Windows. It
> is true that the server posted a notice saying they were upgrading
> their software at midday Monday and conceivable that something changed
> on the server side. But as one can see from the original post, when
> "B" is the first letter in the string, "" gets placed first in the
> stringList by "get every text item." The problem occurs before "ascii
> number" is even called in my script. Because I can SEE a B, I think

Of course, there are some characters, like invisible control
characters, that you can't see. I noticed that you used a lot of log
statements and display dialog techniques to check out intermediate
values:

>> (*trimming |BLOW, JOE|*)
>> (*currDelimiters: *)
>> (*, , L, O, W, ,, , J, O, E*)
>> (*TrimTheStringList with |LOW, JOE|*)
>> display dialog ""
>> --> {button returned:"OK"}

but these are always returned as strings. This isn't always a good
replacement for examining a value in its "source code" form.

However, even if there were a control character in the string,
I don't see how that would have cause the error: the ASCII commands
handle control characters just any other character. Like I said, I
couldn't duplicate the error. I still suspect, however, that the "of"
should be removed from in front of "ASCII number of...." The exact
error message was:

>> ASCII number ""
>> --> Some parameter wasn't understood.

and using "ASCII number of CHARACTER" instead of just
"ASCII number CHARACTER" is an incorrect usage of the command's
defined parameter.

Good luck. :)


{ Arthur Knapp, of <http://www.STELLARViSIONs.com>
a r t h u r @ s t e l l a r v i s i o n s . c o m

"Safe the Nature" --> political graffiti in Prague
}
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Weird error
      • From: Shane Stanley <email@hidden>
  • Prev by Date: Re: Missing file date
  • Next by Date: Re: jmlbeud ceararhtcs
  • Previous by thread: Re: Weird error
  • Next by thread: Re: Weird error
  • Index(es):
    • Date
    • Thread