Ook thank you
On Mon, May 10, 2021, 11:48 PM Paolo Melchiorre
wrote:
> Hi Zain,
>
> I think you can ask on the specific mailing list for this subject
> https://groups.google.com/g/django-i18n
>
> Paolo
>
> On Mon, May 10, 2021, 22:36 Zain Al-abdeen wrote:
>
>> hi ,
>> i want to translate the dj
Hi Zain,
I think you can ask on the specific mailing list for this subject
https://groups.google.com/g/django-i18n
Paolo
On Mon, May 10, 2021, 22:36 Zain Al-abdeen wrote:
> hi ,
> i want to translate the django website and documentation ,
>
> can anyone show me the way to do this?
>
--
You r
yes, lets close this thread: and use this one:
http://groups-beta.google.com/group/django-users/browse_thread/thread/6a96426735ffd7f1
On Jan 23, 1:55 pm, nesh <[EMAIL PROTECTED]> wrote:
> * [EMAIL PROTECTED] wrote, On 23.01.2007 13:04:
>
> >> p.s. Let's go to django-i18n, *the* place for I18N dis
* [EMAIL PROTECTED] wrote, On 23.01.2007 13:04:
>> p.s. Let's go to django-i18n, *the* place for I18N discussions :)
> I thought about it but did not want to create fourth thread for the
> same discussion within two days. How about staying on django-users?
> It is a use of Django after all ;)
O
On 23 Sty, 12:45, nesh <[EMAIL PROTECTED]> wrote:
> Storing ML content is the completely different beast.
Unfortunately, this is what I need right now :)
> I tried this approach first (although before MR branch) and I hated explosion
> of the new tables which it creates. Until
> full model inhe
* [EMAIL PROTECTED] wrote, On 23.01.2007 10:49:
> nesh napisał(a):
>> I'm -1 on this, translation must be done *without* any changes to the model.
> I'm -1 on that -1 :)
>> IMHO, best place to translate content is in the template -- at the point of
>> the display.
> I disagree. To me translat
* stuff4ash wrote, On 23.01.2007 10:24:
> the problem with translations is the many different use "cases". and in
> many cases, avoiding a change to the model is not posible. for example,
> when u have a site with several languanges, but one object is not
> directly translated to another, but jus
nesh napisał(a):
> I'm -1 on this, translation must be done *without* any changes to the model.
I'm -1 on that -1 :)
> IMHO, best place to translate content is in the template -- at the point of
> the display.
I disagree. To me translations (of content) are not just another
version of the
dat
thx for the links :)
> > passI'm -1 on this, translation must be done *without* any
> > changes to the model.
the problem with translations is the many different use "cases". and in
many cases, avoiding a change to the model is not posible. for example,
when u have a site with severa
* stuff4ash wrote, On 22.01.2007 10:57:
> after searching and reading all the posts related to internalization
> and multilanguange, my first question is if there is any active
> development to integrate or make easy translations in the django core,
> and if not, if there are any people who would
10 matches
Mail list logo
