On 11/23/09 at 10:48 AM, [email protected] (stratboy) wrote:
>Ok, I come from here (a post of mine):
>
>http://groups.google.com/group/bbedit/browse_thread/thread/
>c23a3d6be244a7c8/
>
>I've got this problem too. BOM or not BOM for me is a simple problem:
>as an xhtml programmer, I need simple utf-8 since the no-bom encoding
>makes a lor of characters displaying wrong (unless I use the old
>entities). So I frankly don't mind if ir better to use the no-bom
>encoding. For me, it's quite evident that good-old plain utf-8 is
>better.
I think you're confused. :-)
The "utf-8" character set declaration that you use in HTML/XHTML
*is* UTF-8 with no BOM. (I said this before, but perhaps was not
clearly expressing it.) So, you *should* make sure that the text
encoding popup (in the status bar at the bottom of each
document) is set to "Unicode (UTF-8, No BOM)".
We know that the nomenclature is confusing. In a future version,
the encoding "Unicode (UTF-8)" will get renamed to make clear
that it includes a BOM: "Unicode (UTF-8, with BOM)". Then,
today's "Unicode (UTF-8, No BOM)" will be renamed to simply
"Unicode (UTF-8)". That way, the simplest notation ("UTF-8")
works for both your character set declarations *and* for the
presentation in the UI, which will hopefully be less confusing.
R.
--
Rich Siegel Bare Bones Software, Inc.
<[email protected]> <http://www.barebones.com/>
Someday I'll look back on all this and laugh... until they
sedate me.
--
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 [email protected]
To unsubscribe from this group, send email to
[email protected]
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 "[email protected]" rather than posting to the group.
