I'm using RTMC Pro and RTMC Webserver (versions 3.2 w/ LoggerNet 4) for displaying information on a web browser (Internet explorer).
It's all running well, but I have one problem: I've create some hot spots for linking differents screens. When RTMCWS publish the display to the browser, it doesn't finishing the web page well, the last line of the web page created appears broken, like in the example bellow:
<area shape='rect' coords='270,276,293,303' href='command=RTMC&screen=EMA08%20%28Capa%e7u%29' onMouseover="showtip(this,event,'EMA08 (
The correct is:
<area shape='rect' coords='325,784,426,811' href='command=RTMC&screen=EMA08%20%28Capa%e7u%29' onMouseover="showtip(this,event,'EMA08 (Capaçu)')" onMouseout="hidetip()" alt="">
I tried to delete the hot spot and create again, but the problem persists.
Any idea?
Thanks!
I did a little testing and believe that the word "Capaçu" is being used in several of your screen names. The "ç" character is being encoded as ampersand "#231;" in the <li> tags in the resulting HTML generated by RTMC Web Server. When RTMC Web Server hands out an HTML page it indicates in the header how many bytes of HTML the browser should expect. We believe the "ç" is being counted as one byte when in fact it takes 6 to represent it. The result is that for each "Capaçu" used in a screen name RTMC Web Server is reporting 5 fewer bytes to the browser than the browser actually receives so the browser truncates the HTML it receives resulting in an incomplete web page.
This will be fixed in a future release. Can you get by with using a "c" in the screen names for now?
* Last updated by: ChipsNSalsa on 11/18/2010 @ 4:46 PM *
Thanks!
You're right, the problem are the special characters (such as ç, á, í...), which are common on our language.
I can use just normal characters for now and I'll be waiting for a fixing in a next release.
* Last updated by: arthurvr on 11/22/2010 @ 7:59 AM *