AFAIK, django's i18n support is mainly for static strings in the code
and templates. For keeping multiple translations of database content,
you'll need something more.
This might work for you:
http://trac.studioquattro.biz/djangoutils/wiki/TranslationService
I also started working on a translat
I'm making headway with ticket 122. However I have discovered a bug when
porting the m2m_intermediary model test. The get_relatedobject_list methods
are not being set. Can you tell me where in the code this is supposed to
happen? I can see where it is happening for ManyToMany, but not for
On Tuesday 02 August 2005 04:20 am, Adrian Holovaty wrote:
> On 8/1/05, Matthew Marshall <[EMAIL PROTECTED]> wrote:
> > I'm making headway with ticket 122. However I have discovered a bug when
> > porting the m2m_intermediary model test. The get_relatedobject_list
>
On Wednesday 17 August 2005 06:06 pm, Robin Munn wrote:
> The argument that there's too much "magic" going on behind the scenes
> leaves me puzzled. Isn't there already lots of "magic" going on
> setting up the assorted get_foo_list() functions for ForeignKeys and
> ManyToManyFields? Why not add a
On Wednesday 17 August 2005 09:28 pm, Robin Munn wrote:
> On 8/17/05, Matthew Marshall <[EMAIL PROTECTED]> wrote:
> By that, do you mean an alternate class to inherit from? E.g., instead of
>
> class Person(meta.Model):
> fields = (
> meta.CharFi
On Wednesday 17 August 2005 09:59 pm, Robin Munn wrote:
> If/when you do write a wrapper, please post it to the ticket as well.
> If we can't persuade Adrian and Jacob to see sense *wink*, it'll be
> handy to have an alternative.
Of course! I'll see how the current discussion on IRC turns out be
On Wednesday 17 August 2005 10:32 pm, Jacob Kaplan-Moss wrote:
> Howdy everyone --
Hey Jacob!
> I think I was the driving force behind rejecting this ticket --
> Adrian's still 50/50 as far as I know -- so let me explain why I
> don't like it.
I think that just about everything can be answered
+1
I have become used to this, but it was (perhaps needlessly) confusing at
first.
In a way, this wouldn't be as big as the model syntax change, as it could be
done incrementally. There is nothing (AFAIK) stopping using both methods for
a while.
MWM
On Thursday 15 September 2005 04:46 pm,
Minor nitpick, but could we use 'class_' instead of 'klass'?
>From the 'Pythonic guidelines' in PEP 8:
- If your public attribute name collides with a reserved keyword,
append a single trailing underscore to your attribute name. This is
preferable to an abbreviation or corrupted spelling.
I'm interested. Either weekend would work for me.
MWM
On Apr 2, 12:45 pm, Jeremy Dunck wrote:
> Hey all, I was considering putting on a Dallas sprint for 1.1. I'm
> not sure exactly when 1.1 will ship, but soon-ish, so I was thinking
> about trying to make the sprint the weekend of 4/10 (East
On Tuesday 04 March 2008 14:54:38 Jacob Kaplan-Moss wrote:
> Second, there's the question of weather this is a first-class
> language-level feature or a filter. If it's the former, there's a
> syntactic decision to be made; some have proposed something like ``{{
> foo.$bar }}``, but anything that
11 matches
Mail list logo
