Cumulus Support

I have found an other unusual issue in ver. 1.9.1; in the variable <#currcond> in "cumulus.exe", if the word contain an accent at the end of the word (last character), as "ensoleillé" it does go OK thrue Twitter. But, if the variable <#currcond> in "cumulus.exe" contain a word with two oor more accent as "dégagé", the Twitter's message does not go thrue Twitter.

I finaly replaced my "é" accents in "twitter.txt" with the code "&#233;" and it seem to work OK; I tried the same thing in "cumulus.exe" in the "Current" dialog box, but the code "&#233;" is not recognize. (ie: "d&#233;gagé" is showed)

So, for a short story, I will not be able to use anymore accents in the "Current" dialog box, exept for the last character and "&#233;"(type) characters for "twitter.txt" file.

Should I downgrade to a previous version?

Angile wrote:Should I downgrade to a previous version?

That's up to you.

I'll see if I can find why the code doesn't encode two accents in a word correctly, but most of the code is not mine, and it's large and complicated - over 2000 lines of code just to do a tweet. If I had known that Twitter were going to change from simple authentication to this ridiculously complicated OAuth nonsense, I would never have added Twitter support in the first place.

I can't even get a twitter.txt file with <#currcond> in it to work reliably even with non-accented characters, so I'm afraid I have no idea what's going on there.

I use on http://twitter.com/webmestre_lac:

Temp&#233;rature actuelle: <#temp> ºC,
Humidit&#233;: <#hum> %, Vent: <#wlatest> km/hre <#wdir>,
Pluie tomb&#233;e: <#rfall> mm, Ciel: <#currcond>,
<#hour>:<#minute> H.A.E.

Note that in this FORUM, the "&" character should be an ampersand; this may be cause by the only one "British English" language option.

(Also remember that in the result in Twitter, only 117 first characters are viewable; other will be ignored)

Thank's Steve, for the hard work done to have this option available to CUMULUS users.