On Nov 4, 7:33 pm, Rich Siegel <sie...@barebones.com> wrote:
> On 11/4/09 at 10:23 PM, steve.piercy....@gmail.com (Steve
>
> Piercy) wrote:
> >In a general context, yes, I would agree that it is not a good idea.
> >However it is a Lasso file, and Lasso recognizes a BOM if present, so
> >in this specific context it is necessary.
>
> One does not follow from the other. My reading of this page
> <http://www.lassosoft.com/Documentation/TotW/index.lasso?8902>
> leads me to conclude that the BOM is optional and that Lasso
> will do the right thing with the character set declaration that
> you have in place.
>From the LassoTalk list, another developer who understands the BOM and
UTF-8 character set in HTML documents far better than I had the
following to say:
You might want to point out that their original assumption
(specifying UTF-8 as the character set precludes the use of a BOM
for HTML documents) is incorrect. Or at least I couldn't find
any document that prevents it's use. Some reading if interested:
Discusses display problems, but doesn't say it's illegal to use
BOM:
http://www.w3.org/International/tests/results/results-utf8-signature
Says BOM is valid for UTF-8 data streams:
http://unicode.org/faq/utf_bom.html#BOM
This RFC says that even if the protocol disallows a BOM, the BOM
must then be interpreted as a zero-width char, so it's still
allowed!
http://tools.ietf.org/html/rfc3629#section-6
If BareBones knows of a RFC or similar authoritative spec that
disallows the use of a BOM on HTML documents encoded as UTF-8,
I'd be interested in the reference.
I hope I'm not flogging this pony too hard and that it is still
kicking.
--steve
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
"BBEdit Talk" discussion group on Google Groups.
To post to this group, send email to bbedit@googlegroups.com
To unsubscribe from this group, send email to
bbedit+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/bbedit?hl=en
If you have a feature request or would like to report a problem,
please email "supp...@barebones.com" rather than posting to the group.
-~----------~----~----~----~------~----~------~--~---
