I look forwards to the addition of this...
--~--~-~--~~~---~--~~
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 this
On 5/16/06, Ville Säävuori <[EMAIL PROTECTED]> wrote:
> I think that this problem applies in most european languages, too.
> Like, say, Swedish, German and French.
The same appliesa for Dutch where we use trema's (sort of umlauts) to
denote any possible ambiguity in reading. So having the accent
s
> Completely removing umlauts etc. makes such a bad impression outside of
> the US! It's like writing "Adran Hlty" instead od "Adrian Holovaty".
Yes. I definitely agree.
> Say. do people in Finland also usually rewrite into ASCII like this:
Actually, in Finnish, no. I think (in URLs) that would
A friend hit the standard problems with trying to use Django's templates
in another application at his work last week. So we sat down on Saturday
and polished Luke Plant's existing patch a little. I have put the new
patch into ticket #1321.
I would appreciate some review of this, since I believe
Ville Säävuori wrote:
> I saw Changeset #2905 ( http://code.djangoproject.com/changeset/2905 )
> today and I think that there would still be room for improvement here
> regarding of slugifying at least some non-ascii letters (like ä and
> ö, which are widely used in Europe and Scandinavia).
>
>
I saw Changeset #2905 ( http://code.djangoproject.com/changeset/2905 )
today and I think that there would still be room for improvement here
regarding of slugifying at least some non-ascii letters (like ä and
ö, which are widely used in Europe and Scandinavia).
Django strips these characters com
Hey Malcolm,
I was not aware that this behaviour changed between minor versions :-(
You're right: after updating from 3.2.1 to 3.2.8 no problems.
Ubuntu breeze currently provides 3.2.1, dapper will provide 3.2.8.
Malcolm Tredinnick wrote:
> (1) If you are using a sufficiently old version of SQL
On Mon, 2006-05-15 at 20:43 +1000, Malcolm Tredinnick wrote:
> Michael Radjiez quite reasonably raised a problem with a recent change I
> made to fix a bug with QuerySet.count() (it was previously ignoring any
> "distinct" modifiers). The problem is that if you are using a version of
> SQLite prio
Michael Radjiez quite reasonably raised a problem with a recent change I
made to fix a bug with QuerySet.count() (it was previously ignoring any
"distinct" modifiers). The problem is that if you are using a version of
SQLite prior to version 3.2.6 (released in September 2005),
QuerySet.distinct().
On 5/15/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
> In the very beginning, I often made trivial errors in some functions
> used by the methods. Sometimes this resulted in exceptions that were
> ignored and resulted in missing data. This is then hard to spot since
> you don't get a hint what e
Malcolm Tredinnick wrote:
> At some point we start to drown in config settings. It's probably better
> to just "Do The Right Thing" here (first, decide what the right thing
> should be). Having a way to always show the exception (if possible)
> seems like the right thing to me.
>
> The patch in
Done, #1873, http://code.djangoproject.com/ticket/1873
Ciao, Marc.
--~--~-~--~~~---~--~~
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
> Welcome, Nicola! And thanks very much for your documentation patch;
> I've committed it.
You're welcome. BTW, there's more where that came from: see the same
ticket (#1815).
--
Nicola Larosa - http://www.tekNico.net/
--~--~-~--~~~---~--~~
You received this me
13 matches
Mail list logo
