Actually, I just ran what you suggested, figuring it would get me halfway there, and it went all the way instead. I don't get it, as manually opening and changing encoding leaves the content showing up wrong (because BBEdit remembers that the file is now ISO Latin-1), but running it as a text factory fixed it because the files, when reopened, didn't remember the ISO Latin-1 setting at all and were opened (properly) as UTF-8, so all is well. I'm not sure why the text factory's behavior is different from the same manual steps, but it was, and it did exactly what I needed.
So thank you very much. -Arle On Sep 2, 10:30 pm, Rich Siegel <sie...@barebones.com> wrote: > On 9/2/09 at 10:23 PM, arle.lommel.l...@gmail.com (Arle (LISA)) wrote: > > >Thanks for the response. The "Change Encoding" bit corresponds to > >steps 1–3, so it gets me part way, but it won't do the Reopen Using > >Encoding > UTF-8 bit. > > Can you tolerate a BOM in your file? If so, changing the > encoding to "Unicode (UTF-8)" will write the file out with a > UTF-8 byte-order mark at the beginning of the file, which will > cause BBEdit to unambiguously treat it as UTF-8. > > 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. --~--~---------~--~----~------------~-------~--~----~ 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. -~----------~----~----~----~------~----~------~--~---
