i like this ! :) very pythonic.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email
Only after implementation :) Keep in mind, that not only the database
API of Django has to be modified, but also the administration
interface, if we stuck at this solution.
By the way, I forgot to set language in the WHERE clause of my
example, but that makes no big difference for imagining what
> David Bleweet said:
>> Actually this could be integrated into the core.
>> When you create a model, you could add translatable=True to fields
>> that have to be in the language-specific table.
>> When you make selections, you would need to set the language name in
>> the following or a similar
On Nov 9, 4:28 am, "Aidas Bendoraitis" <[EMAIL PROTECTED]>
wrote:
> Actually this could be integrated into the core.
> When you create a model, you could add translatable=True to fields
> that have to be in the language-specific table.
> When you make selections, you would need to set the
On 09-Nov-06, at 4:03 PM, Carlos Yoder wrote:
> And now I read what I wrote. Enough time *and* skills? That could
> be tricky ;-)
i have been meaning to hack on django for nearly a year and a half
now - maybe it's time to get my feet wet ;-)
--
regards
kg
http://lawgon.livejournal.com
> > Aidas Bendoraitis wrote:
> >> MyModel.objects.by_language("EN").all()
> >> MyModel.objects.by_language("EN").order_by('title')
> >
> > I think this would be greate.
>
> sensational is the word ;-)
>
Now we just need to get one of the Django-savvy developers to
implement it, since I'm sure
Kenneth Gonsalves wrote:
> i took a look at this - it seems to imply that there is only one
> translateable field in the model (I may be wrong). But for me a
> typical page model would have several Char fields and more than one
> text field. How does one handle that? I was thinking having
I agree to you about my version of this, but it was the best I could
figure out :) I readed your suggestion and I think it's very good and I
think it's very easy to implement in django system.
--~--~-~--~~~---~--~~
You received this message because you are
On 09-Nov-06, at 3:03 PM, Gacha wrote:
> Aidas Bendoraitis wrote:
>> MyModel.objects.by_language("EN").all()
>> MyModel.objects.by_language("EN").order_by('title')
>
> I think this would be greate.
sensational is the word ;-)
--
regards
kg
http://lawgon.livejournal.com
Gacha,
In your suggestion there is no way to sort objects by
language-specific fields, except in the programming language level, is
there? And the other disadvantage is that value field is always of the
TEXT type whereas sometime it could be VARCHAR or CHAR, so you are
kind of wasting resources.
Aidas Bendoraitis wrote:
> MyModel.objects.by_language("EN").all()
> MyModel.objects.by_language("EN").order_by('title')
I think this would be greate.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django
I developed an e-shop web and I implemented unlimited language support
for all content. Every model realy holded only integer values and
values, that should't be translated. Fields like "title" and
"description" was virtual, they didn't exist in the table, but I was
able to call them like
+1 for this type of solution.
Just there is no need for the intermediate table between the table
with untranslatable fields and the table with translatable ones,
because the relationship between these two tables is one to many. So
the table with translatable fields could just have a FK to the
On 08-Nov-06, at 5:22 PM, fdb wrote:
> Note again that it's perfectly fine to add objects in another language
> than the default that don't have translations in the default language.
> One restriction: you cannot translate a page that doesn't have a
> default language version.
i took a look at
Hello, Frederik,
Your approach has one major problem. If the model has both
translatable and untranslatable content, just like boolean
is_published or foreign key to category, or price (if the object is a
product), then the original and it's translations must duplicate the
untranslatable data
I'd like to show you my approach, which I use for one of my clients.
For every model that needs to have multi-lingual content, you add two
fields: a "language" and a "translation_of" field.
Objects are created in a default language (altough this is not
required). To translate an object, you
Some time ago, I also wrote a few thoughts about implementation of
multilingual content:
http://groups.google.com/group/django-users/browse_frm/thread/13ae7f762d1d5d5e
Maybe that will help us to make the final decision.
Aidas Bendoraitis [aka Archatas]
On 11/8/06, Gonzalo Saavedra <[EMAIL
On 11/7/06, Bill de hOra <[EMAIL PROTECTED]> wrote:
> Hey,
>
> I know Django has solid i18n support for templates/strings and content
> negotiation in the request. But I was wondering how people are going
> about managing translations of content or having a multilingual website
> - eg supporting
Jacob Kaplan-Moss wrote:
> Hey Bill --
>
> *Great* question. We've talked a few times to newspapers who cross-publish
> (usually in English and Spanish), and at least in the news industry there's
> pretty much nothing that makes that process easy. I would absolutely love to
> have a
On 08-Nov-06, at 6:27 AM, [EMAIL PROTECTED] wrote:
> Where i work we have a concept of "channels". Different instances of
> the sites (probably they could fit well in Django's site framework)
> are
> localized for different countries/languages. News on these websites
> are
> channelized too
On Nov 7, 11:01 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> I don't have any real experience in that area, though; what are some
> general best practices for the backend design of a multilingual site?
Where i work we have a concept of "channels". Different instances of
the sites (probably
On Tue, 07 Nov 2006 21:28:21 +, Bill de hOra wrote:
> Hey,
>
> I know Django has solid i18n support for templates/strings and content
> negotiation in the request. But I was wondering how people are going
> about managing translations of content or having a multilingual website
> - eg
Hey Bill --
*Great* question. We've talked a few times to newspapers who cross-publish
(usually in English and Spanish), and at least in the news industry there's
pretty much nothing that makes that process easy. I would absolutely love to
have a standard way of doing translatable content
On 11/7/06, Bill de hOra <[EMAIL PROTECTED]> wrote:
> There's no direct support for this kind of thing in the core (that's
> afaik, I haven't been following the trunk in the last couple of months).
> And, if there's no standard patterns or models for this, is this worth
> thinking about at as an
Hey,
I know Django has solid i18n support for templates/strings and content
negotiation in the request. But I was wondering how people are going
about managing translations of content or having a multilingual website
- eg supporting features like "read this in newspeak", or "browse this
site
25 matches
Mail list logo
