Correcting Document Encoding Mismatch

[Frank Lowney]

When I edit files on my Faculty Web Site (Apache web server) using
Fetch (Remote > Edit), I get the following error message:

Document Encoding Mismatch

This document contains data which describes its encoding as
Unicode (UTF-8, no BOM), but the encoding has been set to
Western (ISO Latin 1).

Saving this document as-is will likely cause unexpected display
of its contents and may prevent BBEdit from opening it in the
future.

(Cancel) (Save Anyway)

.... but I am unable to discover how to correct this situation.
Please point me in the right direction to find the info I need to
avoid this dialog in future.

Thanks

[Ted Burger]

Open your document.
Now in the FILE menu select 'Reopen Using Encoding' and choose the
encoding you want the document to have.
In you your case UTF-8, no BOM.
Now make a trivial change in the document and save it.

Problem solved.

Ted

> --
> 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 bbe...@googlegroups.com
> To unsubscribe from this group, send email to
> bbedit+un...@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 "sup...@barebones.com" rather than posting to the group.
>
> To unsubscribe, reply using "remove me" as the subject.

*********************** Ted Burger ****************************
t...@tobsupport.com ********* www.tobsupport.com

[Frank Lowney]

Thanks for the reply but this doesn’t work.

Going through this process, the first save works w/o complaint but any subsequent save brings up the document mismatch dialog.  I am editing these documents via Fetch so wonder if that  isn’t an important variable to consider.  In Fetch you can select a file and then do: Remote > Edit where the prefs have been set to use BBEdit.

==================================================================

Dr. Frank Lowney  Georgia College & State University

    Senior Director for External Projects

       and Assistant to the Director, Digital Innovation Group @ Georgia College

    Web Enabled Resources,

    GCSU Library and Instructional Technology Center

    E-Mail: frank....@gcsu.edu -- frank....@me.com

    Professional Pages: http://www.faculty.de.gcsu.edu/~flowney

    Blog: frank-lowney.blogspot.com

Voice: (478) 445-5260

NOTICE: Please be advised that I am hearing impaired and communicate most effectively via e-mail.  Follow-up summaries of telephone conversations by e-mail are most appreciated.

==================================================================

We don't make instruction effective, we make effective instruction more accessible.

[Rich Siegel]

On 4/9/10 at 9:09 PM, frank....@gcsu.edu (Frank Lowney) wrote:

>Going through this process, the first save works w/o complaint but any
>subsequent save brings up the document mismatch dialog. I am editing
>these documents via Fetch so wonder if that isn’t an important
>variable to consider. In Fetch you can select a file and then do:
>Remote > Edit where the prefs have been set to use BBEdit.

There's a preference in Fetch which is forcing BBEdit to open
the file as ISO-8859-1, but the document's content (a charset
meta tag, or XML PI) contains information that unambiguously
identifies the document as UTF-8. If you change the setting in
Fetch (I don't know where it is or what it's called, but it'll
be in the Fetch preferences) to "Automatic" or whatever seems
appropriate, that should resolve the problem.

R.
--
Rich Siegel Bare Bones Software, Inc.
<sie...@barebones.com> <http://www.barebones.com/>

Someday I'll look back on all this and laugh... until they
sedate me.

[Bruce Van Allen]

On Apr 9, 2010, at 6:09 PM, Frank Lowney <frank....@gcsu.edu> wrote:

Thanks for the reply but this doesn’t work.

Pay attention to the error message. It is saying that something in the document's text ("data") describes its encoding as UTF-8, but the doc's encoding is set to ISO Latin 1. Change one or the other. 

A guess is that the Web server is a windows machine, and it's files are encoded as ISO Latin 1, but your file's HTML says it's UTF-8.