Re: [WebDNA] UTF-8 encoding issues

This WebDNA talk-list message is from

2010


It keeps the original formatting.
numero = 104558
interpreted = N
texte = On Jan 22, 2010, at 2:40 PM, Tom Duke wrote: > Donovan > > The easiest way to do a charset conversion is to open the db in > BBedit using the correct charset. > > If there are dodgy characters after you open it then BBedit has a > reopen using encoding option in one of the menus. Try different > ones until the db looks ok. > > Then change the charset using the menu at the bottom of the BBedit > window (UTF8- no bom) and bingo your db is in Utf8. > > - Tom > But what if BBedit then warms that (I forget the exact wording of the msg.) "danger.. you are about to save as utf8 but this file contains chars that appear to be ISO latin (etc.) " if I hit the "OK do it anyway" button, then does that mean that the chars in question will be converted to the right (equivalent things) in utf8, or does it mean that BBedit will just leave them as the actual keystrokes that they were when first input.. and now in utf8 that looks like something entirely else? Know what I am asking? -G Associated Messages, from the most recent to the oldest:

    
  1. Re: [WebDNA] UTF-8 encoding issues (Donovan Brooke 2010)
  2. Re: [WebDNA] UTF-8 encoding issues (Christer Olsson 2010)
  3. Re: [WebDNA] UTF-8 encoding issues (Kenneth Grome 2010)
  4. Re: [WebDNA] UTF-8 encoding issues (Marc Thompson 2010)
  5. Re: [WebDNA] UTF-8 encoding issues (Kenneth Grome 2010)
  6. Re: [WebDNA] UTF-8 encoding issues (Tom Duke 2010)
  7. Re: [WebDNA] UTF-8 encoding issues (Donovan Brooke 2010)
  8. Re: [WebDNA] UTF-8 encoding issues (Govinda 2010)
  9. Re: [WebDNA] UTF-8 encoding issues (Kenneth Grome 2010)
  10. Re: [WebDNA] UTF-8 encoding issues (Tom Duke 2010)
  11. Re: [WebDNA] UTF-8 encoding issues (Govinda 2010)
  12. Re: [WebDNA] UTF-8 encoding issues (Donovan Brooke 2010)
  13. [WebDNA] UTF-8 encoding issues (Donovan Brooke 2010)
On Jan 22, 2010, at 2:40 PM, Tom Duke wrote: > Donovan > > The easiest way to do a charset conversion is to open the db in > BBedit using the correct charset. > > If there are dodgy characters after you open it then BBedit has a > reopen using encoding option in one of the menus. Try different > ones until the db looks ok. > > Then change the charset using the menu at the bottom of the BBedit > window (UTF8- no bom) and bingo your db is in Utf8. > > - Tom > But what if BBedit then warms that (I forget the exact wording of the msg.) "danger.. you are about to save as utf8 but this file contains chars that appear to be ISO latin (etc.) " if I hit the "OK do it anyway" button, then does that mean that the chars in question will be converted to the right (equivalent things) in utf8, or does it mean that BBedit will just leave them as the actual keystrokes that they were when first input.. and now in utf8 that looks like something entirely else? Know what I am asking? -G Govinda

DOWNLOAD WEBDNA NOW!

Top Articles:

Talk List

The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...

Related Readings:

Whats up with emailer? (1998) foriegn characters and webcatalog (1997) Fwd: HTML encoding in URLs (1997) Forbidden CGI Error (1997) Problems appending to database (1997) [SHOWIF AND/OR] (1997) A multi-processor savvy WebCatalog? (1997) HELP WITH DATES (1997) New public beta available (1997) RE: Purchased cart being overwritten - still !?? (1997) [WebDNA] inputed text getting scrambled up in DB (2012) Wanted: Broader string manipulation functions (1997) Out of the woodwork (2007) WC 2.0 frames feature (1997) Log-in Scheme (2003) Beta 18 (1997) wrong authentication (1998) [SHOWIF] (1997) Saving [referrer] for later use (1997) [ModDate] & [ModTime] ? (1997)