On 1/11/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> On 1/10/07, Honza Král <[EMAIL PROTECTED]> wrote:
> > 1) migrate django to unicode aka big bang approach
> > + cleanest
> > - most work
> > - may break some code
> >
> > 2) migrate newforms to normal byte strings
> > + doesn't break
On 1/10/07, Honza Král <[EMAIL PROTECTED]> wrote:
> 1) migrate django to unicode aka big bang approach
> + cleanest
> - most work
> - may break some code
>
> 2) migrate newforms to normal byte strings
> + doesn't break anything
> - waste of good work
> - not ellegant (never give in, ne
> +1 for unicode in django
+1
Regards, Arthur.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from
Am 11.01.2007 um 09:39 schrieb Gábor Farkas:
> but that all happened approx. 5months ago, and the branches are still
> not merged (because they are not finished yet), and it does not seem
> that they will be merged in the near future...
+1 for unicode in django, including http://code.djangoproje
Honza Král wrote:
> Hi there,
>
> I have been playing around with newforms for some time. since I don't
> come from an English speaking country, I did also put the unicode
> stuff to the test.
>
> It has bitten me on several occasions. I agree that I am not used to
> python unicode strings, but
+1 from me.
I'm german speaking, having ümläüts all over the place.
I stumbled over the following post that refers to a few tickets whose patches
proved helpful
http://maurus.net/weblog/2006/08/08/utf8-encoded-unicode-support/
greets
Philipp
On Wed, Jan 10, 2007 at 11:56:52PM -0800, Ville Sää
> I see several ways how to solve this problem:
>
> 1) migrate django to unicode aka big bang approach
+1 from me.
I'm also working with Django with a language that has many "funky
characters". I, too, am not very experienced with Python and unicode,
but it's still a major pain sometimes. It wou
