&# in PARAM NAME causing problems

[Thomas Magma]

Hello,

I have an application that generates a HTML document that contains an
applet. It places raw data into the PARAM NAME tag. Well, once in a blue
moon it places the numeric character reference &# into the data. When my
Java applet imports this using the getParameter command, it reacts
differently between different version of IE. One solution is to not let my
original application generate the sequence &#, however, this does not fix
the HTML documents that have already been generated in the past. It would be
nice to just fix the Java applet so it can import this raw data without
having to recognize &# as a numeric character reference.

Is this possible?

Here is my HTML code:

=>.>/(%<!<!>((6<0>%(#(!(+>%(!(>(!>%(%>%>!(&/<(*<&>*/6>0>((!>+(%(<()<&(!>!(=(><!>#/)(#(6>+/=(.>+/1>&>#16<!/>(*(#/!(*(!/!(//#((>=1(/=/01)(/1=/!(=1//61!!6/>!61=>1!>/+!(!./!!+1%//./1*1<.&//./%.1!.+%*.&#1.<#&.%/.%%1.1/.&//.*.>1=!01*1=!!(.!1!<(&!)/*/(1#(+1+1!/)1!<!(11>>./#1)(>/%/*(//!>%/#/#((1<(/(616(&/)/<>#>.(%(1(+(<(+>1>+(>(%>&(+>((0(%((((>+(0(6>>()(/>+(&>%<%>.(6>#>>(!<.()(%<!>((!>!<&(!()<!(=(<>/>1<#??

"></APPLET></CENTER>

 

[David Dorward]

I have an application that generates a HTML document that contains an
applet. It places raw data into the PARAM NAME tag. Well, once in a blue
moon it places the numeric character reference &# into the data.

Which is invalid.

One solution is to not let my original application generate the sequence
&#

Fix it so it represents the sequence &# as &amp;#.

however, this does not fix the HTML documents that have already been
generated in the past.

Get a text editor that can do a global search and replace, then run it only
on files from before you fixed the generator.

It would be nice to just fix the Java applet so it can import this raw
data without having to recognize &# as a numeric character reference.

I suspect you'll find that the browser interprets &# and feeds the result to
the applet, the applet doesn't decode the raw markup.

 

[Thomas Magma]

Thanks for your response.

I suspect you'll find that the browser interprets &# and feeds the result
to
the applet, the applet doesn't decode the raw markup.

This is what I suspected was happening. I was hoping to fix this problem in
the applet. Fixing it in the app is really quite easy. Oh well, life goes
on.

Thanks anyways.

Thomas