1
I get an option explicit error saying it does not appear as the first line whenever I use it with utf-8 charset encoding on my Sun Cobalt server running Chillisoft on Linux.
The error does not occur if the charset declaration in the metatag is 8859-1 but this causes spurious characters such as capital A with a circle over it to appear before the "£" symbol when newsfeeds are paced on the 8859-1 page. Not very professional!
These was a known MS bug in IIS on unicode pages becasue it places a BOM character at the beginning of the file - hence tripping the option explicit error. Does anyone have a fix for this other than omitting option explicit altogether.
code examples:
Error example
[code] <%@Language="VBSCRIPT CODEPAGE="1252"%>[code]
[code]<%OPTION EXPLICIT%>[code]
[code]<%code...%>[code]
[code]<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">[code]
[code]<html xml:lang="en" lang="en" xmlns="http://www.w3.org/1999/xhtml">[code]
[code]<head>[code]
[code]<title>some title</title>[code]
[code]<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />[code]
OK example
ditto above but different metatag
[code]<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />[code]
Note: I use DWMX for coding and this places a unicode signature (BOM) on the file using Canonical Decomposition, followed by Caninical Composition (class C) as this is the recommended way to employ unicoded pages. If I omit this BOM char the page works with utf-8 but is this going to cause browser issues?
