On Wed, Jun 11, 2014 at 3:36 PM, < [email protected]> wrote:
> I'm not using Foxpro DBFs; I'm using MariaDB (MySQL) on the backend, so I > guess no worries with that! ??? > > ------------------- You need to identify the collation for your data. https://mariadb.com/kb/en/22-sql-collations-collation/ This gets a little complicated. More in HOW you pull data with table joins on the back end. > > > On 2014-06-11 13:29, Paul Hill wrote: > >> English Windows uses the Western European codepage. So does French, >> Italian, Spanish, German, Swedish and others. >> >> The only time you will see a problem is if you mix the windows codepage >> and >> the dbf codepage. If they are the same it should be OK. If not Fox will >> convert on the fly. If a letter does not exist you will get the closest >> match or a ? >> >> I'm talking about single byte character sets. Chinese and Arabic could be >> tricky :-) >> >> Collation is another beast. For example Swedish and Norwegian are similar >> languages but sort differently. >> >> Paul >> >> On 11 Jun 2014 17:53, <[email protected]> >> wrote: >> >>> >>> If I make an app that works great here in the USA, what worries do I have >>> >> (with respect to how data is stored) if it goes overseas? Must I use >> unicode? I mean--using English machines as a prerequisite--isn't it the >> same ASCII character set? >> >>> >>> Honestly, I don't see this app going outside the USA anytime soon but >>> >> it'd be nice to understand how this works a bit better. >> >>> >>> tia, >>> --Mike >>> >>> >>> On 2014-06-11 12:12, Richard Kaye wrote: >>> >>>> >>>> Good question. I suppose it's possible that different codepages might >>>> have some effect on what binary value is generated but that would be a >>>> big IDK. OTOH if your DB encoding and environment encoding are synced >>>> I would think it shouldn't matter. My last speculative though on the >>>> matter is if your binary value column DB encoding is the equivalent of >>>> machine then other encodings are irrelevant? >>>> >>>> -- >>>> >>>> rk >>>> -----Original Message----- >>>> From: ProfoxTech [mailto:[email protected]] On Behalf Of >>>> [email protected] >>>> Sent: Wednesday, June 11, 2014 11:59 AM >>>> To: [email protected] >>>> Subject: RE: Interesting GOTCHA from 16-byte binary key >>>> >>>> Paul Hill had mentioned something about the Code Pages and/or encoding. >>>> I figured that happens to data behind the scenes, not necessarily if >>>> an end-user is touching it. ??? >>>> >>>> On 2014-06-11 11:47, Richard Kaye wrote: >>>> >>>>> >>>>> If the users never directly interact with the value why would that be a >>>>> concern? >>>>> >>>>> -- >>>>> >>>>> rk >>>>> -----Original Message----- >>>>> From: ProfoxTech [mailto:[email protected]] On Behalf Of >>>>> [email protected] >>>>> Sent: Wednesday, June 11, 2014 11:42 AM >>>>> To: [email protected] >>>>> Subject: RE: Interesting GOTCHA from 16-byte binary key >>>>> >>>>> LOL...so back to the remaining question: do you think that non-USA >>>>> users might encounter issues if I'm using the binary instead of the >>>>> unicode or ansi human readable options? Here they are again from >>>>> VFP2C32's help: >>>>> >>>>> * 0 = ansi human readable (38 wide) >>>>> * 1 = unicode (76 wide) >>>>> * 2 = binary (16 wide) >>>>> >>>>> tia, >>>>> --Mike >>>>> >>>>> [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CAJidMYLkAJnwF21VmP04Jy7xz3U5=Fg3v0TqAh=zhbgmvaj...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
