Re: comments on Unicode document

2007-01-10 Thread Max Ischenko
From http://pylonshq.com/docs/0.9.4/internationalization.html#translations-within-templates There is one complication though. gettext's xgettext command can only extract strings that need translating from Python code in .py files. This means that if you write _('Hello') in a template such as a

Re: comments on Unicode document

2006-12-27 Thread Shannon -jj Behrens
On 12/19/06, Damjan [EMAIL PROTECTED] wrote: Are we on the same page, or am I still lost? Not lost at all :) Ah, good :-D Except I'd prefer if all Python API's would be unicode aware, I think it's fortunate that most Python APIs *can* ignore the unicode problem. As a stupid American,

Re: comments on Unicode document

2006-12-19 Thread Damjan
Are we on the same page, or am I still lost? Not lost at all :) Except I'd prefer if all Python API's would be unicode aware, and would not encode/decode until it's utmost necessary. I think it would be nice if the Python DB-API is reviewed and make unicode a requirement (for quieries and

Re: comments on Unicode document

2006-12-18 Thread Damjan
http://pylonshq.com/project/pylonshq/browser/Pylons/trunk/docs/internationalization.txt Wow, great document This is a lot of non-Pylons-specific work! And this should really be added to the Python wiki, too... and eventually should enter the standard Python documentation. My notes:

Re: comments on Unicode document

2006-12-18 Thread Damjan
For example MySQL's Unicode documentation is here Also note that you need to consider both the encoding of the database and the encoding used by the database driver. If you're using MySQL together with SQLAlchemy, see the following, as there are some bugs in MySQLdb that you'll need

Re: comments on Unicode document

2006-12-14 Thread Max Ischenko
Hello, I am new to Pylons and currently do i18n-ed applications in TurboGears. One thing I'd like to see coming from TG background is (semi-)automatic handling of unicode decoding/encoding. E.g. in Turbogears I can setup framework to decode request parameters from utf8 and encode it back to

Re: comments on Unicode document

2006-12-12 Thread Mike Orr
On 12/12/06, James Gardner [EMAIL PROTECTED] wrote: For real world use it is recommended that you use the UTF-8 encoding for your file but you must be sure that your text editor actually saves the file as UTF-8 otherwise the Python interpreter will try to parse

Re: comments on Unicode document

2006-12-12 Thread Philip Jenvey
On Dec 12, 2006, at 7:03 AM, James Gardner wrote: Since you're encouraging the user to always use unicode objects within the application, he should use ugettext instead of gettext. That means it would be a lot more convenient if h._ pointed to ugettext instead of gettext. We

Re: comments on Unicode document

2006-12-12 Thread Shannon -jj Behrens
On 12/12/06, Mike Orr [EMAIL PROTECTED] wrote: On 12/12/06, James Gardner [EMAIL PROTECTED] wrote: For real world use it is recommended that you use the UTF-8 encoding for your file but you must be sure that your text editor actually saves the file as UTF-8 otherwise

Re: comments on Unicode document

2006-12-12 Thread Shannon -jj Behrens
* How to integrate the aquarium code Can Ben or Shannon log a ticket about this one? Done. I've also cut and pasted the appropriate code: http://pylonshq.com/project/pylonshq/ticket/150#preview I hope that's helpful. Best Regards, -jj -- http://jjinux.blogspot.com/

Re: comments on Unicode document

2006-12-12 Thread Shannon -jj Behrens
Ok, I found James's responses in the archive: Then on each controller call the language to be used could be read from the session Syntax error :) Sorry, do you mean lowercase t on Then? I think the sentence is grammatically incorrect and confused ;) Outstanding issues are

comments on Unicode document

2006-12-11 Thread Shannon -jj Behrens
James, I have reviewed your Unicode document. Below are my responses: == http://pylonshq.com/project/pylonshq/browser/Pylons/trunk/docs/internationalization.txt == This is a lot of non-Pylons-specific work! == message you will have run into a problem Get rid of will. ==