Hi All! ^^

I written a content encryption script, but got some problem...

1. if content has emotions, encode then send to contact, after decode, only see the text, no emotions, no matter just only ""

2. zip done, rename to plsc, then upload to web, but fail, always got this
"An unhandled exception has occurred.
We apologize for the inconvenience this may cause you. Please follow the link below back to our Messenger Plus! Home page and feel free to report this error on the forum"

I have check my ScriptInfo.xml, it's UTF-8 format, and content on below

code:

---

<?xml version="1.0" encoding="UTF-8"?>
<ScriptInfo xmlns="urn:msgpluscripts" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsichemaLocation="urn:msgpluscripts PlusScripts.xsd">
    <Information>
        <Name>Encryptions</Name>
        <Description>Safer for chatting</Description>
        <Author>Ramon Liu</Author>
        <AboutUrl>NO URL</AboutUrl>
        <Version>0.2</Version>
        <UpdateId>RL0001</UpdateId>
        <Build>0001</Build>
    </Information>
   
    <ScriptCommands>
        <Command>
            <Name>encry</Name>
            <Description>The command for Encryptions.</Description>
            <Parameters>command</Parameters>
        </Command>
    </ScriptCommands>

</ScriptInfo>

---

Your ScriptInfo.xml file should be UTF-16 in the header and encoded in UTF-16 Little Endian.

Also as far as the registry functions you have in your script. You are free to use them but please provide the proper acknowledgements as to where you obtained the code and who the author was (ie: me).

quote:

---

Originally posted by ramonliu
1. if content has emotions, encode then send to contact, after decode, only see the text, no emotions, no matter just only ""

---

quote:

---

OnEvent_ChatWndReceiveMessage - Return value
A string containing the message to be displayed in the chat window instead of Message. If you do not want to modify the message, simply return Message without changing it. The new string will be parsed for possible format codes. It is important to remember that the new message cannot be longer than the original one (use Message.length) and will be cut if necessary. Also, Messenger will not re-parse the message for emoticons codes.

---

quote:

---

Originally posted by matty
Your ScriptInfo.xml file should be UTF-16 in the header and encoded in UTF-16 Little Endian.

Also as far as the registry functions you have in your script. You are free to use them but please provide the proper acknowledgements as to where you obtained the code and who the author was (ie: me).

---

understand that, thanks for you help.. ^^

the other question, DisplayInfoMessage function.

DisplayInfoMessage(
    [string] Message,
    [int,optional] Duration,
    [boolean,optional] ForceNow
);

Duration and ForceNow parameters seen to be not work right now...
maybe it also my mistake

I want to show some info on information area, so code like this
chatWnd.DisplayInfoMessage("12345",3,false);

it's mean, "12345" will be show on information area for 3 sec. right?
and if message queue have something, that also show out after my message.

but work not like I thought, why?  >"<

The function isn't supported in the latest version of Windows Live Messenger. The scripting engine has yet to be updated to fix it.

OK, I got !

Thanks for your help! ^O^

I'm tried to convert to USC-2 LE format for ScriptInfo.xml file by Noetpad++
and zip files use windos/winrar/7-zip
still can't upload to web... that so sad.. T_T
The ScriptInfo.xml encoding already change to "UTF-16" and
all files convert to USC-2 LE format,
Use Waterfox/IE upload, still got error... QQ
By the way, my OS is Win7x64

IS "UTF-16 LE" != "USC-2 LE"  ??

tried to use another text editor call "pspad" to convert UTF-16 LE,
and upload, it is same problem...
then I tried zip two files, ScriptInfo.xml and Encryptions.js, then rename to plsc
still can't upload... error message the same.

that seem to be can not publish my script... Orz

Email support@kimahrisoftware.com. They will have to investigate.

quote:

---

Originally posted by matty
Email support@kimahrisoftware.com. They will have to investigate.

---

I think that the problem is that in the SkinInfo.xml the tag <Build>0001</Build> should be <BuildNumber>0001</BuildNumber>.

However the message display to the user could be clarify.

when I changed to "BuildNumber", It's can upload!!

Thanks Alexandre ^O^


XD

I just only look "scripting document" and somebody codes,
forget to search web stuff...

anyway, thanks all to help me, this foolish man... ^^"