I would say that UTF16 is your best bet. Does mySQL expect the byte order mark (BOM)? Does FMP write it? This is a sequence of three bytes specifing the kind of UTF. You can check with a hex editor, if it's there or not. Another idea: UTF16 can be little or big endianness. Perhaps FMP and mySQL have different expectations in this regard.
HTH Trixi Willius -------- Original-Nachricht -------- Datum: Sun, 26 Nov 2006 13:55:35 +0000 Von: Rowland Carson <[EMAIL PROTECTED]> An: [email protected] Betreff: character sets query > I'm trying to find the right combination of character sets to ensure > correct display of accented, scandinavian, and other characters > outside the plain vanilla ASCII set, in both FMP and in a web browser > view of a MySQL database which is maintained by FMP text exports. > > It looks like a UTF-8 text file provides the correct answer when it's > uploaded to MySQL and viewed with a browser. However, FMP (8.0v3 on > Mac OS X 10.3.9) doesn't provide that among its text export options > [Windows (ANSI), ASCII (DOS), Macintosh, Unicode (UTF-16), Japanese > (Shift-JIS)]. I've achieved the desired result by opening the Mac > option text file with TextWrangler and re-saving it as UTF-8. > However, that's a step I want to eliminate if possible, especially as > this will later need to work on Windows too. > > If I try to use a MySQL LOAD DATA INFILE statement on an uploaded > ANSI, DOS or Mac format test file, it appears to discard any accented > characters in a field, and all subequent characters, until the next > field marker (tab). The UTF-16 option text file causes it to choke at > the first character. > > Any suggestions or pointers to references are welcome. > > regards > > Rowland > -- > | Wilma & Rowland Carson http://home.clara.net/rowil/ > | <[EMAIL PROTECTED]> ... that's Rowland with a 'w' ... -- Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
