Part of me is regretting switching the default encoding from latin-1 to utf8. On
one hand, utf8 is a better standard because it can handle a big portion of the
world's encodings and it seems to be the preferred default in other apps. On the
other hand, lots of North America/South America and Western Europe have legacy
stuff in latin-1, and our test databases are encoded in latin-1, so lots of
people are going to be bitten by the Encoding error.
At this point I don't know what to do about it, but can brainstorm the following
options:
+ set default back to latin-1 (band-aid, hides the "problem")
+ trap the Encoding error where it happens first (one of the bizobj property
settings I think) and give a useful message, kind of like what we do in the
loading of wxPython.
+ somehow get the encoding from the backend database and use that - not sure
this is even possible in a database-agnostic way.
+ have a page in the wizard where people can choose the encoding, along with
short explanatory text.
+ have some code in the wizard to automatically detect when it is one of the
dabo test databases, and set the generated code to set Encoding = "latin-1".
+ convert our test databases into utf8 (I'm currently unsure how to go about
this, but it should be straightforward).
Any other brainstorms or preferences on what to do? Bottom line: I want peoples
first impressions to be of something that works, not something that gives a nice
traceback message...
--
Paul McNett
http://paulmcnett.com
http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
