[ic] Making interchange-pages html-valid
peter at pajamian.dhs.org
Mon May 17 20:04:03 UTC 2010
On 18/05/10 02:42, Jon Jensen wrote:
> On Mon, 17 May 2010, Rene wrote:
>> To make the more-list validator-happy, i had to add these to
>> interchane.cfg (or if you use the debian-way of splitting up settings,
>> then settings.cfg)
>> Variable MV_HTML4_COMPLIANT 1
>> UrlSepChar &
> Those seem like safe defaults.
> Isn't UrlSepChar's default already & ?
It is, but if you don't explicitly set it to & after setting the
MV_HTML4_COMPLIANT variable it keeps the separator at "&" instead of
"&" (which is what we want).
>> Then the validator was complaining about the character-encoding.
>> Interchange outputs the default http-charset in Server.pm as hardcoded
>> as iso8859-1, which according to wc3 should be iso-8859-1. So i added
>> also the following variable after the above settings:
>> variable MV_HTTP_CHARSET iso-8859-1
>> ...and restarted interchange. Now my site seems to be 100% "HTML 4.01
>> Transitional valid".
> We should probably just fix that in the core.
Perhaps, but there will have been a reason why it was coded as an option
like this in the first place, right?
>> I wonder why these settings are not set as default settings in ic, or
>> atleast visible as a possible settings that you easily could change..
> Submit a patch or GitHub fork and I think we can probably agree on
> getting those committed!
The problem I can see with this is that when generating URLs that do not
appear in web pages (such as for plain text emails) it is actually
correct to use "&" and not &" (if my understanding is correct) since
it's actually the html parser (browser) that needs to have the & escaped
in this way. Thus changing the default could cause emailed links to
break on existing catalogs.
More information about the interchange-users