> as this url shows http://www.htmlhelp.com/tools/validator/problems.html#amp


> it should be used an HTML entity instead of the ampersand sign.<p>

Can you please be a bit more specific? In which URL should the ampersand be
replaced?

> as this url shows http://www.htmlhelp.com/tools/validator/problems.html#amp


> it should be used an HTML entity instead of the ampersand sign.<p>

another problem with validation:
required attribute "ALT" not specified  in every <img> tag used in the elog (icons)

here is an example of the validator results:
http://validator.w3.org/check?uri=http%3A%2F%2Fmidas.psi.ch%2Felogs%2FLinux+Demo%2F&charset=iso-8859-1+%28Western+Europe%29&verbose=1

I added ths missing tags. The validator at least does not complain any more.

> > as this url shows http://www.htmlhelp.com/tools/validator/problems.html#amp
> 

> > it should be used an HTML entity instead of the ampersand sign.<p>
> 
> Can you please be a bit more specific? In which URL should the ampersand be
> replaced?

uhmm...

http://midas.psi.ch/elogs/Forum/page2?mode=threaded&expand=0&last=7

the bug is also a "documentation bug", infact similar tricks are also
in FAQs (FAQ 5 for example)

I tried to substitute avery occurrence of hard coded "&" with "&amp;" but it does
not do the job at all ... infact the first time the HTML code is ok, but
following a link let the browser to automatically decode html entities .. and
everything turns wrong again ... maybe the encoding should be done in
printing-to-the-browser-time ..

> > > as this url shows http://www.htmlhelp.com/tools/validator/problems.html#amp
> > 

> > > it should be used an HTML entity instead of the ampersand sign.<p>
> > 
> > Can you please be a bit more specific? In which URL should the ampersand be
> > replaced?
> 
> uhmm...
> 
> http://midas.psi.ch/elogs/Forum/page2?mode=threaded&expand=0&last=7
> 
> the bug is also a "documentation bug", infact similar tricks are also
> in FAQs (FAQ 5 for example)
> 
> I tried to substitute avery occurrence of hard coded "&" with "&amp;" but it does
> not do the job at all ... infact the first time the HTML code is ok, but
> following a link let the browser to automatically decode html entities .. and
> everything turns wrong again ... maybe the encoding should be done in
> printing-to-the-browser-time ..

BTW, the current url (taht should be perfectly well formed makes the elog not to
display attachments ... so may be thare is a problema in the query string decoding
routine ...

http://somehost.it:8080/LBNAME/?mode=full&amp;attach=1

> > > as this url shows http://www.htmlhelp.com/tools/validator/problems.html#amp
> > 

> > > it should be used an HTML entity instead of the ampersand sign.<p>
> > 
> > Can you please be a bit more specific? In which URL should the ampersand be
> > replaced?
> 
> uhmm...
> 
> http://midas.psi.ch/elogs/Forum/page2?mode=threaded&expand=0&last=7
> 
> the bug is also a "documentation bug", infact similar tricks are also
> in FAQs (FAQ 5 for example)
> 
> I tried to substitute avery occurrence of hard coded "&" with "&amp;" but it does
> not do the job at all ... infact the first time the HTML code is ok, but
> following a link let the browser to automatically decode html entities .. and
> everything turns wrong again ... maybe the encoding should be done in
> printing-to-the-browser-time ..

BTW, the current url (taht should be perfectly well formed makes the elog not to
display attachments ... so may be thare is a problema in the query string decoding
routine ...

http://somehost.it:8080/LBNAME/?mode=full&amp;attach=1

> > I tried to substitute avery occurrence of hard coded "&" with "&" but it does
> > not do the job at all ... infact the first time the HTML code is ok, but
> > following a link let the browser to automatically decode html entities .. and
> > everything turns wrong again ... maybe the encoding should be done in
> > printing-to-the-browser-time ..

That won't help, since the 'Start page = ...' string is used for redirection (outside
of any HTML). The '&' thing should only occur inside the HMTL text.

I changed elogd.c to encode things properly, but I'm not sure if I covered all
occurences. Can you try release 1.576 if it works correctly?

Stefan, the validation still fails on the ampersand ... here is an example of your online Demo elog: http://validator.w3.org/check?verbose=1&uri=http%3A//midas.psi.ch/elogs/Forum/920