Hi,
ak schrieb:
> After some thoughts I came to the following conclusion: if you guys
> want to keep support of legacy charsets in fact you don't have to
> force model objects too be unicoded. Firstly, they are passed to
> templates and filters and we can't mix legacy charsets with unicode in
On Jan 28, 2:02 pm, "ak" <[EMAIL PROTECTED]> wrote:
> Bjorn, if you read my first messages and specially my patch #3370, you
> find that I made a suggestion that if the guys want to move to unicode
> they better drop all native encodings support and so does my patch.
You mean require all I/O edge
Bjorn, if you read my first messages and specially my patch #3370, you
find that I made a suggestion that if the guys want to move to unicode
they better drop all native encodings support and so does my patch.
Then people started to answer me that this is wrong. And at the moment
noone is able
On Jan 28, 4:03 am, "ak" <[EMAIL PROTECTED]> wrote:
> After some thoughts I came to the following conclusion: if you guys
> want to keep support of legacy charsets in fact you don't have to
> force model objects too be unicoded. Firstly, they are passed to
> templates and filters and we can't mix
On 26-Jan-07, at 12:19 PM, medhat wrote:
> So many times I send messages to the group, but my message does not
> appear at all, or it might appear a day or two after I actually send
> it, which of course makes it appear down on the list, and nobody
> really
> sees it.
not moderated - and no b
Splitting this into new thread since it's already not about db client
encodings...
ak wrote:
> So if everyone agreed, the way is simple:
> 1. when django loads data from db and fills in a model object, all
> strings have to be encoded according to DEFAULT_CHARSET
> 2. when django passes data fr
After some thoughts I came to the following conclusion: if you guys
want to keep support of legacy charsets in fact you don't have to
force model objects too be unicoded. Firstly, they are passed to
templates and filters and we can't mix legacy charsets with unicode in
one template. Next, if I
ak wrote:
> So if I start a new
> project based on django, or I extend existing project, there is very
> strong reason for me to use newforms, BUT they don't work. Confused ?
> Me too :(
Actually it is exactly like this because newforms are not ready. And
unicode issue is not the only one. Ne
Hi,
It seems the delete_view method of the ModelAdmin class in
django/contrib/admin/options.py (newforms-admin branch) is missing an
import. When I try to delete an object using the Delete link on the
change object page, I get a NameError on line 464 which has a call to
the _get_deleted_objects f
> Do you know which parts of django still use bytecode strings?
As far as I know, it's only newforms and this is why the topic was
born: at the moment newforms work right until you want to put any non-
latin1 character through them to db. I've done the patch (#3370) which
fixes the issue but it
[EMAIL PROTECTED] wrote:
> Hi Ivan
>
> Thank you very much for making things very clear here.
I actually thought I make everyone angry with my constant bugging about
these things :-)
> Do you know which parts of django still use bytecode strings?
A better person to ask is Gábor Farkas who was
Hi Ivan
Thank you very much for making things very clear here.
It seems the whole issue cryes for a unification of the whole django source
before the 1.0 release, or do I misinterpret?
Do you know which parts of django still use bytecode strings?
greets
Philipp
On Sat, Jan 27, 2007 at 06:10:
Michael Radziej wrote:
> 1. Are all these tickets really about the connection encoding?
>
> 2. If so, what's the problem of using utf8 for the connection for
> everybody? I don't see how this would be a problem for anybody who is
> using a different encoding for templates, within the database's s
ak wrote:
> Could someone please explain me what was a problem with unicode support
> in oldforms so newforms have been made with unicode inside ?
I can! The thing is it has absolutely nothing to do with forms, it's
just historical coincidence.
Originally Django was written with using byte stri
Michael, of you read again the topic about euro sign in newforms you
can find that this touches everything. Personally I couldn't find a way
to use utf-8 to connect MySQL and keep using cp1251 in my templates: it
basically doesn't work. With my patch (#3370) and utf8 everywhere it
does.
--~--~--
Guys
Could someone please explain me what was a problem with unicode support
in oldforms so newforms have been made with unicode inside ?
Kick me if I wrong but what is a real reason to convert bytes back and
forth ? Religion ? I agree with everyone who says that unicode is a
must and 'legacy' ch
Hi,
in these tickets, are we talking about the encoding used in the database
connection for the communication between django and the database, the
encoding of how the database stores its data, or the encoding in which
the templates are stored? Or even the encoding used in the http transaction?
I
17 matches
Mail list logo
