[FX.php List] Bad apostrophe character confounds FMP

Mon Dec 10 07:09:00 MST 2007

Alex and Troy,

I'm embarrassed to say that I had NO content type encoding on the 
page...or most other pages for that matter. I haven't concentrated on 
this area...up until now...but I intend to.

Question...would this statement help if the bad character already 
existed in an FMP record, was subsequently displayed on a fx.php page 
and then resubmitted to FMP?  That's what caused the current problem.

Thx

Jonathan

At 10:57 PM -0800 12/9/07, Troy Meyers wrote:
>Jonathan,
>
>There are probably lots of causes, but every time I've seen this 
>it's because the php page file didn't have this in the head:
>
><head>
><meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
><title>...
>
>...or if it did have that, it wasn't saved actually using the UTF-8 encoding.
>
>For FX PHP use, it's GOT to be UTF-8.
>
>-Troy
>
>>  Hi Folks,
>>
>>  I spent a bunch of time diagnosing a 958 error that was eventually
>>  narrowed down to a character in the name "O'Doherty".  The  application
>>  loads an existing FMP record into a session, allows  editing and then
>>  creates a new record based on the eited data.  The  apostrophe appeared
>>  as "%92" in the FMP query, and caused the 958  error during new record
>>  creation..  I have no idea how 958 relates,  but it was definitely the
>>  culprit.
>>
>>  The question is, what techniques do you us to condition data,  a
>>  regexp? and on every field?
>>
>>  Thx.
>>
>>  Jonathan
>
>_______________________________________________
>FX.php_List mailing list
>FX.php_List at mail.iviking.org
>http://www.iviking.org/mailman/listinfo/fx.php_list

-- 
Jonathan Schwartz
Exit 445 Group
jonathan at exit445.com
http://www.exit445.com
415-381-1852