Ascii character conversion

I need to decode a DMM serial connection. It spits out ascii looking charactors. The DMM is RadioShack DMM catalog # 22-812. Any ideas to convert ascii to something readable?

Btw, I tried using a "format value" in the string conversion pallette with the string specifier (%s). This does not decode the characters.

Similar Messages

Hex string conversion to ASCII Character string

I have a Hex String 494A4B4C and want this string to get converted in ASCII Character String. IJKL. How to do in Labview 8.5.

Here is a screenshot of the described code:
Ton
Message Edited by TCPlomp on 30-09-2009 01:35 PM
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!
Attachments:
Example_VI_BD.png ‏3 KB

Printing ZPL (Zebra) data to printer spooler without character conversion

Hi all,
We are printing shipping labels from UPS, with a process where we recive the ZPL label code directly from UPS, and we just need to pass the data to the printer to get the labels. We have already implemented this with Fedex and some custom labels, and it works perfectly. The problem with the UPS label data is that it contains non-printable characters (in the MaxiCode data field). When passed to the SAP printer spooler (see code example below), the data gets corrupted because SAP interprets these non-printable characters as printer control codes.
I have verified this by saving the ZPL data to a local file, before printing it through the SAP spooler. I then print this raw data and compare the output with the labels printed from the spooler. The MaxiCode (the big 2D barcode) is different in these labels. UPS has also tested the labels, and rejected them because of incorrect data in the barcode.
For printing, we are using printers defined as type "PLAIN", but I also tried using the "LZEB2" device type with the same result. The error we see in the spooler entry is this:
Print ctrl S_0D_ is not defined for this printer. Page 1, line 2, col. 2201
Print output may not be as intended
The printer ctrl code differs, depending om the label. I have examined the spooler data in "raw" mode, and there is always an ASCII character 28 (hex 1C) in front of the characters that SAP think are control codes, and this is why I think these non-printable characters are the reason for the problems.
This is the function module I use to print the ZPL data (and as stated above, this works fine for Fedex and custom labels). The ZPL data is converted to binary format before passed to the function module, but I also tried to send the data in text format with another FM, but the result is the same. I have experimented with the "codepage" parameter, and this one gives the least amount of errors, and some labels actually get through without errors. But still at least 50% of the labels gets corrupted, with log entries like above.
CALL FUNCTION 'RSPO_SR_WRITE_BINARY'
      EXPORTING
        handle           = lv_spool_handle
        data             = lv_label_line_bin
        length           = lv_len
        codepage         = '2010'
      EXCEPTIONS
        handle_not_valid = 1
        operation_failed = 2
        OTHERS           = 3.
Does anyone know if there is a way to send data to the spooler without character conversion or interpretation of printer control codes? Or is there any other smart way to get around this problem?
/Leif

I do a more direct output to the spooler, to avoid any issues with the WRITE statement and SAP's report output processing. At the same time, I insert line breaks so that the output is easy to debug in the spooler if needed. Also included is the code to to detect the escape code (ASCII #28) and to insert a control code ZZUPS in its place (you can skip this for Fedex). Here's a simplified example, but please note this is for a Unicode system, some minor changes is required in a non-Unicode system.
CONSTANTS: lc_spcode TYPE c LENGTH 5 VALUE 'ZZUPS',
           lc_xlen TYPE i VALUE 5.
   DATA: lv_print_params TYPE pri_params,
         lv_spool_handle TYPE sy-tabix,
         lv_name TYPE tsp01-rq0name,
         lv_spool_id TYPE rspoid,
         lv_crlf(2) TYPE c,
         lv_lf TYPE c,
         lstr_label_data TYPE zship_label_data_s,
         lv_label_line TYPE char512,
         lv_label_line_bin TYPE x LENGTH 1024,
         lv_len TYPE i,
         ltab_label_data_255 TYPE TABLE OF char512,
         ltab_label_data TYPE TABLE OF x,
         lv_c1 TYPE i,
         lv_c2 TYPE i,
         lv_cnt1 TYPE i,
         lv_cnt2 TYPE i,
         lv_x(2) TYPE x.
   FIELD-SYMBOLS: <n> TYPE x.
   lv_crlf = cl_abap_char_utilities=>cr_lf.
   lv_lf = lv_crlf+1(1).
   lv_name = 'ZPLLBL'.
CALL FUNCTION 'RSPO_SR_OPEN'
     EXPORTING
       dest                   = i_dest
       name                   = lv_name
       prio                   = '5'
       immediate_print        = 'X'
       titleline              = i_title
       receiver               = sy-uname
*      lifetime               = '0'
       doctype                = ''
     IMPORTING
       handle                 = lv_spool_handle
       spoolid                = lv_spool_id
     EXCEPTIONS
       device_missing         = 1
       name_twice             = 2
       no_such_device         = 3
       operation_failed       = 4
       OTHERS                 = 5.
   IF sy-subrc <> 0.
     RAISE spool_open_failed.
   ENDIF.
LOOP AT i_label_data INTO lstr_label_data.
     CLEAR ltab_label_data_255.
     SPLIT lstr_label_data-label_data AT lv_lf INTO TABLE ltab_label_data_255.
     LOOP AT ltab_label_data_255 INTO lv_label_line.
       IF lv_label_line NE ''.
         lv_len = STRLEN( lv_label_line ).
*       Convert character to hex type
         lv_c1 = 0.
         lv_c2 = 0.
         DO lv_len TIMES.
           ASSIGN lv_label_line+lv_c1(1) TO <n> CASTING.
           MOVE <n> TO lv_x.
           IF lv_x = 28.
             lv_cnt1 = 0.
             lv_label_line_bin+lv_c2(1) = lv_x.
             lv_c2 = lv_c2 + 1.
             DO lc_xlen TIMES.
               ASSIGN lc_spcode+lv_cnt1(1) TO <n> CASTING.
               MOVE <n> TO lv_x.
               lv_cnt2 = lv_c2 + lv_cnt1.
               lv_label_line_bin+lv_c2(2) = lv_x.
               lv_c2 = lv_c2 + 2.
               lv_cnt1 = lv_cnt1 + 1.
               lv_len = lv_len + 1.
             ENDDO.
           ELSE.
             lv_label_line_bin+lv_c2(2) = lv_x.
             lv_c2 = lv_c2 + 2.
           ENDIF.
           lv_c1 = lv_c1 + 1.
         ENDDO.
*       Print binary data to spool
         lv_len = lv_len * 2. "Unicode is 2 bytes per character
         CALL FUNCTION 'RSPO_SR_WRITE_BINARY'
           EXPORTING
             handle                 = lv_spool_handle
             data                   = lv_label_line_bin
             LENGTH                 = lv_len
           EXCEPTIONS
             handle_not_valid       = 1
             operation_failed       = 2
             OTHERS                 = 3.
         IF sy-subrc <> 0.
           RAISE spool_write_failed.
         ENDIF.
       ENDIF.
     ENDLOOP.
   ENDLOOP.
   CALL FUNCTION 'RSPO_SR_CLOSE'
     EXPORTING
       handle = lv_spool_handle.
   IF sy-subrc <> 0.
     RAISE spool_close_failed.
   ENDIF.

Non-ASCII character in Email field

Hi Guys,
I am trying to enter non-english characters in Email field of user form, but OIM throws an error that "A non-Ascii character has been entered". I have also tried to turn off the AppFirewall Filter in xlConfig.xml file but no help. Is there any way thay I can enter non-Ascii characters in Email field?
Regards,
Rahul

.oO(surfinIan)
>I have a script that converts a ms word document to text
then uploads that to a
>blob field on a mysql db.
> During the conversion some characters my not be
recognised. When i then call
>up the blob for display on the browser...those characters
show up as unknown
>characters with a ? or box. Is there a way to
preg_replace those unknown
>characters before displaying them.
What about fixing the encoding problem instead? If chars get
lost during
such a transfer
document->script->database->script->browser it's always
an encoding problem somewhere down the road.
The recommendation these days is to use UTF-8, which avoids
most of
these old problems. You just have to make sure that your
documents are
properly stored as UTF-8 in the database and delivered as
such to the
script and the browser, then you don't have to worry about
special chars
anymore.
That's just the general idea. I can't be more specific, since
I don't
know your conversion script or the database structure.
Micha

Character conversion error

Hi all,
We are getting the following error when trying to parse an xml string resource - Character conversion error: "Illegal ASCII character, 0xc2" (line number may
be too low)-. We have not been able to get around this. We have tried creating the InputSource two different ways:
reader = new StringReader(stringSource);
src = new InputSource( reader );
and
src = new InputSource(new InputStreamReader(new ByteArrayInputStream(stringSource.getBytes())));
The problem does appear to go away if we treat the DTD we are validating against as a file. If we set it has a uri, we get the above problem.
Is anyone else experiencing this problem?
Any help would be greatly appreciated.
Thanks in advance,
Greg

Hi,
2 possible solutions:
1) try using the xerces parser instead of sun's parser
2) look at the posting at the following url and see wether the posted solution solves your problem: http://forums.java.sun.com/thread.jsp?forum=34&thread=67558
Hope this helps,
Kurt.

"character conversion error" while parsing xml files

Hello,
I'm trying to parse MusicXML (Recordare) files, but I'm getting an exception.
I'm using the SAX parser (javax.xml.parsers.SAXParser).
Here is the code I use to instantiate it:
final javax.xml.parsers.SAXParserFactory saxParserFactory = javax.xml.parsers.SAXParserFactory.newInstance();
final javax.xml.parsers.SAXParser saxParser = saxParserFactory.newSAXParser();
final org.xml.sax.XMLReader parser = saxParser.getXMLReader();
I'm using my own handler, but I get the same exception even if I use org.xml.sax.helpers.DefaultHandler.
The error I get is:
Character conversion error: "Illegal ASCII character, 0xc2" (line number may be too low).
The first few lines of my xml files look like this:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE score-partwise
PUBLIC "-//Recordare//DTD MusicXML 0.6 Partwise//EN"
"http://www.musicxml.org/dtds/partwise.dtd">
<score-partwise>
[...etc...]
If I delete the <!DOCTYPE ...> line, then I don't get the exception anymore. But the MusicXML files I get (from some other program) always contain this line, and it would be quite some work to delete them from every file manually.
So does anyone know if there is a way to avoid deleting that line in every file, while still being able to parse the xml files without exceptions?
Or maybe does anyone know what the exact cause of the exception is? (because I don't know what exactly causes it)
Thank you in advance.
Greetz,
Jipo

So does anyone know if there is a way to avoid
deleting that line in every file, while still being
able to parse the xml files without exceptions?ok this is side-stepping the real problem but I've used this code to filterout DTD references for other reasons   public static InputStream filterOutDTDRef(InputStream in) throws IOException {
      BufferedReader iniReader = new BufferedReader(new InputStreamReader(in));
      StringBuffer newXML = new StringBuffer();
      for(String line = iniReader.readLine(); line!=null; line = iniReader.readLine())
         newXML.append(line+"\n");
      in.close();
      int s = newXML.indexOf("<!DOCTYPE ");
      if(s!=-1)
         newXML.replace(s,newXML.indexOf(">",s)+1,"");
      return new ByteArrayInputStream(newXML.toString().getBytes());
   }and it actually speeds up the parsing phase too (since the DTD ref.s were on the web and the XML standard mandates that there is a fetch for each xml file parsed..)
you can feed the above into the InputSource constructor that takes an InputStream argument.
Now for the real problem... 0xc2 is "LATIN CAPITAL LETTER A WITH CIRCUMFLEX" according to a unicode chart - which is not an ASCII character (as the error message correctly reports). I'm not sure why the file is being parsed as ASCII though? You could try parsing in a FileReader to the inputsource and hope it picks up the default character encoding of your system, and that that character encoding matches the file. Or you could try passing in a FileReader constructed with a explicit character encoding (eg "UTF8") and see if that does the trick?
asjf

Character conversion error: Unconvertible UTF-8 character beginning..

Hello,
I'm using TrAX for XSLT transformations, and having a following
problem
Character conversion error: "Unconvertible UTF-8 character beginning with 0xa9" (line number may be too low).
org.xml.sax.SAXParseException: Character conversion error: "Unconvertible UTF-8 character beginning with 0xa9" (line number may be too low).
        at org.apache.crimson.parser.InputEntity.fatal(InputEntity.java:1100)
        at org.apache.crimson.parser.InputEntity.fillbuf(InputEntity.java:1072)
        at org.apache.crimson.parser.InputEntity.isXmlDeclOrTextDeclPrefix(InputEntity.java:914)
        at org.apache.crimson.parser.Parser2.maybeTextDecl(Parser2.java:2795)
        at org.apache.crimson.parser.Parser2.externalParameterEntity(Parser2.java:2880)
        at org.apache.crimson.parser.Parser2.maybeDoctypeDecl(Parser2.java:1167)
        at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:489)
        at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
        at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442)
        at mlts.converter.XMLImport.outputESGML(XMLImport.java:311)
        at mlts.converter.Converter.processFile(Converter.java:312)
        at mlts.converter.Converter.Convert(Converter.java:229)
        at test.main(test.java:7)Following the source code, I've found that the exception is thrown
when it reads DTD. I tried to read DTD using InputSource
in ascii, in latin-1 and my program reads it without any problem.
I really appreciate any help,
Thanks

http://forum.java.sun.com/thread.jsp?forum=34&thread=254927

SAXParseException: character conversion error: Illegal character 0x9A...

This is my problem:
I use JDom to parse remote XML document with DTD linked to it. But I get that error. Request is:
SAXBuilder builder = new SAXBuilder();
Document doc = builder.build(new URL(url));
This works fine when I use these XML and DTD docs locally, which means that I give xml file name as a parameter from console. Then everything goes well. But when I move my program to server and try to run it there, SAXParseException is thrown. Why???
Error is:
error on line 1 of document "http://server.net/doc.dtd" Character conversion error: Illegal ASCII character 0x9A (line number may be too low)
What this means? And why this just happens when I run program in server? Help, please
tia J_J

Exactly that's the problem.
String class :
* This class is implemented to map an ordinary java.lang.String
* into an xml compliant String
public class String2Xml
     private final String invalidChars [] = {"�",
                                                       "�",
                                                       "�",
                                                       "�",
                                                       "�",
                                                       "�",
                                                       "�",
                                                       "�",
                                                       "�",
                                                       "�",
                                                       "`",
                                                       "�",
                                                       "<",
                                                       ">",
     private final String replaceChars [] = {"��",
                                                       "ß",
                                                       "ä",
                                                       "ö",
                                                       "ü",
                                                       "Ä",
                                                       "Ö",
                                                       "Ü",
                                                       "§",
                                                       "",
                                                       "`",
                                                       "´",
                                                       "<",
                                                       ">",
                                                       "'"};
     * Constructor
     public String2Xml();
     * This operation is implemented to check if the given String
     * matches one of the invalidChars. If an invalid char is found
     * it'll be replaced.
     * @return String - the correct xml String
     public String checkString(String check)
          for (int i = 0; i < invalidChars.length; i++)
               check = check.replaceAll(invalidChars, replaceChars[i]);
          System.out.println("Check : " + check);
          return check;

File Upload/Character conversion

Hi,
I have a Servlet which processes a File Upload. The uploaded file is accessable via an
InputStream. Now, if the file contains any non-ASCII character (e.g. German Umlaute)
these characters are messed up.
I've been digging on Google to find a way to convert the characters provided by an
InputStream. The solution I have in mind would take the InputStream which I already
have and provide a different InputStream which hast the converted characters. How could
I implement such a solution? What is the recommended way to perform such a conversion.
Many thannks in advance,
Meme

When converting a binary stream to a character stream (using InputStreamReader and so on), you should be specifying the correct charset. With the charset the code knows how to translate the bytes into the correct chars. Otherwise the system's default charset will be used. In Windows systems it is generally cp-1252. The InputStreamReader provides this option in the constructor. You should specify the same charset as the file is encoded in. Try it with UTF-8.

Character conversion problems when calling FM via RFC from Unicode ECC 6.0?

Hi all,
I faced a Cyrillic character convertion problem while calling an RFC function from R/3 ECC 6.0 (initialized as Unicode system - c.p. 4103). My target system is R/3 4.6C with default c.p. 1500.
The parameter I used in my FM interface in target system is of type CHAR10 (single-byte, obviously).
I have defined rfc-connection (SM59) as an ABAP connection and further client/logon language/user/password are supplied.
The problem I faced is, that Cyrillic symbols are transferred as '#' in the target system ('#' is set as default symbol in RFC-destination definition in case character convertion error is met).
Checking convertions between c.p. 4103 and target c.p. 1500 in my source system using tools of transaction i18n shows no errors - means conversion passed O.K. It seems default character conversion executed by source system whithin the scope of RFC-destination definition is doing something wrong.
Further, I played with MDMP & Unicode settings whithin the RFC-destination definition with no successful result - perhaps due to lack of documentation for how to set and manage these parameters.
The question is: have someone any experience with any conversion between Unicode and non-Unicide systems via RFC-call (non-English target obligatory !!!), or can anyone share valuable information regarding this issue - what should be managed in the RFC-destination in order to get character conversion working? Is it acceptable to use any character parameter in the target function module interface at all?
Many thanks in advance.
Regards,
Ivaylo Mutafchiev
Senior SAP ABAP Consultant

hey,
I had a similar experience. I was interfacing between 4.6 (RFC), PI and ECC 6.0 (ABAP Proxy). When data was passed from ECC to 4.6, RFC received them incorrectly. So i had to send trimmed strings from ECC and receive them as strings in RFC (esp for CURR and QUAN fields). Also the receiver communication channel in PI (between PI and RFC) had to be set as Non unicode. This helped a bit. But still I am getting 2 issues, truncation of values and some additional digits !! But the above changes resolved unwanted characters problem like "<" and "#". You can find a related post in my id. Hope this info helps..

Error occurred during character conversion in SXMB_MONI

Hello Experts,
Good Day!
I would like to seek your help here. When i used tcode SXMB_MONI to search for messages i get this error : Error occurred during character conversion.
So far no problem with the program. Its work for all other dates. Just for one particular day and specific time period, im geting this error.
Does anyone know what is this error means? Please reply..
Thanks for your help.
Looking forward for ur replies..

Hi Presheela,
Basically this problem occurs when ur payload contains any special characters like '&' ,'>'...etc .So you have to take care of how to deal with these characters in XI.
Refer the following documentation:
How to Work with Character Encodings in Process Integration
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42
Regards,
Vinod.

Problem in the character conversion

Hi Guys,
I am facing problem in the character conversion
I am posting data from SAP to third party system using XI , by converting whole input message to a String .I am using SOAP adapter to communicate XI to third party system.
Thirdparty system needs String to be wrapped in CDATA so that it will not choke by looking at the special characters. I did Wrap the output string in CDATA, using ABAP mapping but when I do that XI is converitng arrow brackets < and >. into &lt and u2018&gtu2019 my assumption is it is double encoding.
example -
before map - <AppSystemInfo>
after mapping it is converted as - <![CDATA[ &ltAppSystemInfo&gt]]>
Edited by: Vamsi on Jun 17, 2010 10:00 PM
Edited by: Vamsi on Jun 17, 2010 10:01 PM

Did you try to see the output?
bcz if you are trying this in mapping testing it will show you like this as this conversion if for xml, so xml will not do anything wrong with the special characters, so for that special characters will be converted like that.
Once try to run end to end interface and try to see at receiver side that how data looks like.
Thanks,
Hetal

[Solved] no non-ASCII character input in rxvt-unicode

Hello everyone,
For some days now, I can't write any non-ASCII characters any more in rxvt-unicode and rxvt-unicode-patched. Unfortunately, downgrading the rxvt-unicode package doesn't seem to help. To have at least a temporary solution, I'd like to know at least which packages I could try to downgrade as well. Any ideas, anyone?
greez,
maxmin
Last edited by Maximalminimalist (2011-03-12 13:12:26)

When I try to type a non-ASCII-character I get nothing at all. This happens with my custom keyboard layout (modified programmer dvorak) and in some layouts I already tried (us: altgr-intl, ch, de and fr)
When I paste a non-ASCII characters in rxvt-unicode I get
maxmin ~ $ ?
This happens only on my x86_64 desktop which is more up to date than my i686 laptop. (I'm afraid now to do any updates.)
EDIT: I'm sorry, I don't know what you mean with locale settings. What do you mean with that?
EDIT2: Maybe just typing locale in the terminal is what you mean:
maxmin ~ $ locale
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.utf8
LC_CTYPE="en_US.utf8"
LC_NUMERIC="en_US.utf8"
LC_TIME="en_US.utf8"
LC_COLLATE="en_US.utf8"
LC_MONETARY="en_US.utf8"
LC_MESSAGES="en_US.utf8"
LC_PAPER="en_US.utf8"
LC_NAME="en_US.utf8"
LC_ADDRESS="en_US.utf8"
LC_TELEPHONE="en_US.utf8"
LC_MEASUREMENT="en_US.utf8"
LC_IDENTIFICATION="en_US.utf8"
LC_ALL=
With other terminal emulators I get sometimes also nothing and sometimes right displayed but wrong interpreted character in vim. I didn't take notes while doing that but I'll try again if needed.
Last edited by Maximalminimalist (2011-03-06 21:51:23)

ALV Grid bug when dealing with non-ASCII character

Dear all,
I have a requirement to display user's remarks on ALV. The data element of the remarks column is TEXT200. I know that each column in an ALV Grid can display at most 128 characters. Since my SAP is an Unicode system, I expect that each column in my ALV Grid can display 128 Chinese characters, too. However, the ALV Grid only display 42 Chinese characters at most. Is this a bug in ALV Grid? How can I fix it?
I did a small experiment. The results are listed below. My version is Net Weaver 7.01. The results show that the bug does not exist in ALV List. However, my user prefers ALV Grid, which is more beautiful and elegant.
Type of ALV
Max number of
ASCII character
in an ALV column
Max number of
non-ASCII character
in an ALV column
REUSE_ALV_GRID_DISPLAY
128
42 Chinese characters
CL_SALV_TABLE
128
42 Chinese characters
CL_GUI_ALV_GRID
128
42 Chinese characters
REUSE_ALV_LIST_DISPLAY
132
132 Chinese characters
If you encounter the bug, please post your solution. Thanks a lot.

It looks like limitation of ALV grid cell, which can contain up to 128 bytes in SAP gui.
Your unicode characters are probably 3 bytes each.
Check OSS Note 910300 for more detailed info.
EDIT: Note 1401711 seems to be a correction for your issue It allows to use 128 characters (even if they take more than 128 bytes).

Keystroke return and ASCII character 13 and 10 not working in

I have the following script to opens a web page of my internal telephone switch (all in the local network) and fill in the two fields that come up and needs filled out in order to log in.
tell application "Safari"
activate
open location "http://192.168.1.90/"
end tell
tell application "System Events"
delay 1
keystroke tab
delay 1
keystroke "" -- Note: Username goes here if one is wanted/needed
delay 1
keystroke "XYZ" -- Note: Password goes here if one is wanted/needed
delay 1
keystroke (ASCII character 13)
end tell
All works fine, it skips the first field (the login name is blank). Puts the password in the next field. However it refuses to activate the “log-in” button of the login window (the one that is blue and normally can be done with the enter key).
I tried:
keystroke (ASCII character 13)
keystroke (ASCII character 10)
keystroke return
keystroke enter
Non of them do the job.
Any suggestions please? Thanks.

Consider replacing ...
keystroke (ASCII character 13)
... with ...
tell document 1 to do JavaScript "document.myform.submit()"
... where 'myform' will have to be replaced with the forms' name.
To obtain the forms' name ...
01. Perform a right ('control' if single button mouse) button click on the form based web page. A contextual menu will appear.
02. Select the 'View Source' menu item. A new 'Safari' will appear with the title beginning with 'Source of ...'.
03. Look for a line similar to ...
<form name="myform" action="submit-form.php">
... Note, the name="myform". This is the forms' name. Whatever is between the name="" is what you need to substitute 'myform' with, in 'tell document 1 to do JavaScript "document.myform.submit()"'.
I entered ...
tell application "Safari" to tell document 1 to do JavaScript "document.myform.submit()"
... in 'Script Editor', and visited 'JavaScript Form Submit example'. When the AppleScript code was executed, the web page responded accordingly.
New test of code. With 'JavaScript Form Submit example' again displayed, the following code ...
set tValue to "ChangeAgent"
tell application "Safari"
tell document 1
do JavaScript ("myform.query.value=\"" & tValue & "\"")
do JavaScript "document.myform.submit()"
end tell
end tell
... was entered into 'Script Editor', and executed.
The results were as expected - the resultant web page reported ...
Great! The Form is Submitted Successfully!
Query:'ChangeAgent'
Back
... And, the code was condensed even further ...
set tValue to "ChangeAgent"
tell application "Safari" to tell document 1 to do JavaScript ("myform.query.value=\"" & tValue & "\"; document.myform.submit()")
... producing the desired results.

Ascii character conversion

Similar Messages

Maybe you are looking for