Django translations is good for static value but for new value in database?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups
I am using Django translation on DRF. Here is the doc on Django translation.
On Wed, Mar 11, 2020 at 1:17 AM Alaydyn Gholechragh
wrote:
> hi
>
> which component I can use for translation(Internationalization) in Django
> Rest Framework ?? easy and with best documents and examples ??
>
> --
> Yo
Thank you very much Russ!
Have a nice day!
On Thu, Feb 6, 2014 at 1:32 AM, Russell Keith-Magee
wrote:
> Hi Stayros,
>
> Translations for Django are all managed through Transifex.
>
> http://transifex.com
>
> Once you've signed up for an account, you can apply to join a specific
> translation team
Hi Stayros,
Translations for Django are all managed through Transifex.
http://transifex.com
Once you've signed up for an account, you can apply to join a specific
translation team, which will allow you to contribute new and/or corrected
translations.
Yours,
Russ Magee %-)
On Wed, Feb 5, 2014
I found it at http://code.google.com/p/django-localeurl/
More context:
http://groups.google.com/group/django-developers/browse_thread/thread/3417b90f0e6fda9f
http://www.satchmoproject.com/trac/ticket/459
--~--~-~--~~~---~--~~
You received this message because you
>
> I have a project that assembles applications that I have prepared for
> general pourpose. One of them is a ticket application developed with
> software ticket in mind. Now I want to make it work for a complete
> different company. It turns out I just need to rename fields, not the
>
Malcolm Tredinnick napisał(a):
>> We found that one of localizations we have to use is incomplete in 0.96.
>> If we translate these texts and submit a patch, would it be included in
>> (eventual) 0.96.1 and subsequent releases of the 0.96 line?
>
> No. The only future releases in the 0.96 line w
On Fri, 2007-06-01 at 10:25 +0200, Jarek Zgoda wrote:
> We found that one of localizations we have to use is incomplete in 0.96.
> If we translate these texts and submit a patch, would it be included in
> (eventual) 0.96.1 and subsequent releases of the 0.96 line?
No. The only future releases in
to many threads open with same topic. this thread will now be discussed
HERE:
http://groups-beta.google.com/group/django-users/browse_thread/thread/6a96426735ffd7f1
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"D
Okay, I noticed this thread literally seconds after creating my own
describing a very similar approach. I searched the group for
'multilingual',
should also have checked 'translations'. The new thread should appear
shortly.
My library also uses the internal Translation class, but I moved the
de
oh. a group just for that :)
thx don.
On Jan 22, 9:37 pm, Don Arbow <[EMAIL PROTECTED]> wrote:
> On Jan 22, 2007, at 12:22 PM, ashwoods wrote:
>
>
>
> > hmm... i guess everybody is tired of translation discussions :)You
> > might have better luck in the Django internationalization group
On Jan 22, 2007, at 12:22 PM, ashwoods wrote:
>
> hmm... i guess everybody is tired of translation discussions :)
You might have better luck in the Django internationalization group:
http://groups.google.com/group/django-I18n/
Don
--~--~-~--~~~---~--~~
Y
hmm... i guess everybody is tired of translation discussions :)
On Jan 21, 1:12 am, "ashley" <[EMAIL PROTECTED]> wrote:
> 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 e
13 matches
Mail list logo
