Ben Parker wrote: > I don't see a need for it in the Page class. How about implementing it > in an example UnicodePage.py similar to the example SidebarPage.py?
I'd rather implement it as a Mixin then that can be added to any other base class (SideBarPage is actually intended as a base class). > I agree. On our multilingual projects, we use UTF-8 strings everywhere. > One character set for all the languages, very simple. Exactly. In the past, utf-8 was not so well supported by some browsers, so I preferred latin-1, but nowadays it is much better. You sometimes read the recommendation "only use unicode for strings", but using ordinary strings with a consistent encoding of utf-8 is much simpler, at least for Webware. By the way, in Python 3.0 these issues will eventually go away. All strings will be unicode and use a default encoding of utf-8. -- Chris ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Webware-devel mailing list Webware-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-devel
