Re: Django i18n design rationale

Hi, Am Fri, 1 Jan 2016 15:29:16 -0800 (PST) schrieb Jure Erznožnik : > 1. Expressions gathering vs declaring: Django has utilities to gather > expressions from sources, txt files and also javascript files. While > that by itself is a design choice, it also presents us

Django i18n design rationale

I've worked with Django for the past few months. While this - I realize - is not much, so far it has been an extremely pleasant experience. Everything seems to be designed just right and works really nicely out of the box. So I was that much more surprised when I had to prepare my first app

Django i18n in JS templates

We actively use django-pipeline package and its builtin solution for javascript templates The problems begins when we needed to use i18n in this templates, for ex.: <%= gettext('To translate') %> Standart django

Re: Django i18n questions

Indeed On 11.04.2014 12:45, Daniel Roseman wrote: On Friday, 11 April 2014 06:55:12 UTC+1, Andrew Pashkin wrote: Documentation says , that: ...it looks for a

Re: Django i18n questions

On Friday, 11 April 2014 06:55:12 UTC+1, Andrew Pashkin wrote: > > Documentation > says, > > that: > > ...it looks for a django_language key in the current user’s session > > This is the

Re: Django i18n questions

I ended up using this snippet for switching languages. It simply reverses url with given language code. On 11.04.2014 09:55, Andrew Pashkin wrote: Documentation says

Django i18n questions

Documentation says , that: ...it looks for a django_language key in the current user's session This is the latest commit

Re: Django i18n url is not working with en-us sublanguage

Hi, I just have the same error could you solved it!! thanks On Monday, May 7, 2012 4:57:52 AM UTC-5, Suteepat Damrongyingsupab wrote: > > My django app's using i18n_patterns in urls.py and when I go to my app > with the url like: > > myapp.com/en/ > > myapp.com/de/ > > myapp.com/en-gb/ > > The

Django i18n url is not working with en-us sublanguage

My django app's using i18n_patterns in urls.py and when I go to my app with the url like: myapp.com/en/ myapp.com/de/ myapp.com/en-gb/ The urls above works fine but the url *myapp.com/en-us/* gave me an 404 error. I think the problem is that (

Re: Limited set of languages available in Django i18n?

On Wed, May 4, 2011 at 1:32 AM, Karen Tracey wrote: > On Tue, May 3, 2011 at 8:11 AM, Tom Evans wrote: >> >> If you require your site >> to be in Mongolian, it can be in Mongolian, even though Django does >> not itself have a Mongolian translation, >

Re: Limited set of languages available in Django i18n?

On Tue, 2011-05-03 at 09:15 -0700, Uri Goldstein wrote: > If the issue cannot be resolved then it might be beneficial to explain > it > better: > >1. If the issue is driven by technical difficulty stemming from > xgettext >then don't excuse it as an attempt to prevent "a mixture of >

Re: Limited set of languages available in Django i18n?

On Tue, May 3, 2011 at 8:11 AM, Tom Evans wrote: > If you require your site > to be in Mongolian, it can be in Mongolian, even though Django does > not itself have a Mongolian translation, > Need a better example. Django has had a Mongolian translation for a year now:

Re: Limited set of languages available in Django i18n?

Hello, On Tuesday, May 3, 2011 5:08:28 PM UTC+3, Tom Evans wrote: > > On Tue, May 3, 2011 at 1:43 PM, Uri Goldstein wrote: > > Hi Tom, > > > > I definitely agree that having docs is good, reading and comprehending > the > > docs is better. Reading and comprehending the docs

Re: Limited set of languages available in Django i18n?

On Tue, May 3, 2011 at 1:43 PM, Uri Goldstein wrote: > Hi Tom, > > I definitely agree that having docs is good, reading and comprehending the > docs is better. Reading and comprehending the docs yourself you might have > noticed the following quote: "If you were to try

Re: Limited set of languages available in Django i18n?

Hi Tom, I definitely agree that having docs is good, reading and comprehending the docs is better. Reading and comprehending the docs yourself you might have noticed the following quote: "If you were to try this and Django supported it, you would inevitably see a mixture of translated strings

Re: Limited set of languages available in Django i18n?

On Tue, May 3, 2011 at 12:39 PM, Uri Goldstein wrote: > Thank you Tom and KG. > > I now see that my friend was right(!). > http://docs.djangoproject.com/en/1.3/topics/i18n/localization/#how-to-create-language-files > says: "Django does not support localizing your

Re: Limited set of languages available in Django i18n?

On Tue, 2011-05-03 at 04:39 -0700, Uri Goldstein wrote: > KG, in the workaround you mention as my second option, are you > referring to > the folder /conf/locale ? Is there where I will be putting my "new" > languages? yes - for example if the language you are adding is martian (with

Re: Limited set of languages available in Django i18n?

Thank you Tom and KG. I now see that my friend was right(!). http://docs.djangoproject.com/en/1.3/topics/i18n/localization/#how-to-create-language-files says: "Django does not support localizing your application into a locale for which Django itself has not been translated." The motivation

Re: Limited set of languages available in Django i18n?

On Tue, 2011-05-03 at 03:59 -0700, Uri Goldstein wrote: > I'm fine in knowing that the i18n infrastructure in Django can handle > any > available language - that was the crux of my question. to be precise, there are two parts in localisation - one is the strings in django itself and the other

Re: Limited set of languages available in Django i18n?

On Tue, May 3, 2011 at 11:59 AM, Uri Goldstein wrote: > Thank you for your quick response. > > I now realize that my friend was referring to "the strings commonly > displayed by Django". Naturally these are yet to have been translated to all > available languages but I'm

Re: Limited set of languages available in Django i18n?

Thank you for your quick response. I now realize that my friend was referring to "the strings commonly displayed by Django". Naturally these are yet to have been translated to all available languages but I'm sure we'll get there sme day :). I'm fine in knowing that the i18n infrastructure in

Re: Limited set of languages available in Django i18n?

On Tue, 2011-05-03 at 02:19 -0700, Uri Goldstein wrote: > Being new to Django, I was told by a friend that it only supports i18n > for a > limited set of languages - these being only languages that have had > Django > itself translated to. > > Is this true? Doesn't make much sense to me :)

Re: Limited set of languages available in Django i18n?

On Tue, May 3, 2011 at 19:19, Uri Goldstein wrote: > Hello, > > Being new to Django, I was told by a friend that it only supports i18n for a > limited set of languages - these being only languages that have had Django > itself translated to. > > Is this true? Doesn't make

Limited set of languages available in Django i18n?

Hello, Being new to Django, I was told by a friend that it only supports i18n for a limited set of languages - these being only languages that have had Django itself translated to. Is this true? Doesn't make much sense to me :) Is there a definitive list of languages supported by Django's

Re: Django i18n

I think pt-BR will fit. Just can't understand why the backoffice is translated and the main app not : ( Even in pt-Pt. On Nov 17, 2009 2:30 AM, "Kenneth Gonsalves" wrote: On Monday 16 Nov 2009 9:46:58 pm Carlos Ricardo Santos wrote: > I use to folders at app/locale: > >... I

Re: Django i18n

On Monday 16 Nov 2009 9:46:58 pm Carlos Ricardo Santos wrote: > I use to folders at app/locale: > > pt-PT > en-GB > > Any ideas? Someone has implemented a foreign language before? > I have implemented english ;-) I assume you mean implementing a non-english language? This support has been

Re: Django i18n

2009/11/16 Carlos Ricardo Santos : > Hi: > I tried all the ways possible and impossible to make my Django project have > i18n... > Put all settings (INSTALLED_APPS, CONTEXT_PROCESSORS), generated languages, > compiled messages, edited the ".po" files, setted the

Django i18n

Hi: I tried all the ways possible and impossible to make my Django project have i18n... Put all settings (INSTALLED_APPS, CONTEXT_PROCESSORS), generated languages, compiled messages, edited the ".po" files, setted the ugettext to "_", in views all the strings are like this: toSend= _("Hello"),

Re: django i18n for google

On Sun, Dec 28, 2008 at 7:19 PM, Alessandro Ronchi wrote: > Django itselfs permits selecting the i18n language via POST. I think > it should be useful to add also a GET var to set the language, and a > localization middleware catches it. This has been debated to

Re: django i18n for google

2008/12/27 Antoni Aloy : > You could create a url that links to your localized site so Google > would be able to crawl it, but I suppose that your site depens on > changing the language via POST, isn't it? > > I that case, you could write yourselve the code and allow

Re: django i18n for google

2008/12/27 Alessandro Ronchi : > Il 16 dicembre 2008 19.20, Alessandro Ronchi > ha scritto: >> When google spiders our i18n translated django websites, does it try >> and indicize all languages? is it possible to force the language by a

Re: django i18n for google

Il 16 dicembre 2008 19.20, Alessandro Ronchi ha scritto: > When google spiders our i18n translated django websites, does it try > and indicize all languages? is it possible to force the language by a > GET var (for example _code=en) ? I think it's a critical problem.

django i18n for google

When google spiders our i18n translated django websites, does it try and indicize all languages? is it possible to force the language by a GET var (for example _code=en) ? -- Alessandro Ronchi Skype: aronchi http://www.alessandroronchi.net SOASI Soc.Coop. - www.soasi.com Sviluppo Software e

Re: Flemish/Vlaams and Django I18N

On Thu, 2008-11-27 at 13:42 -0800, Foundatn wrote: > Hi, > > I am working for a client who requires their django-powered site to be > read in Dutch (nl) and Flemish (nl_BE) (and other languages). Although > the two languages are very, very similar, there are differences in the > text that has

Flemish/Vlaams and Django I18N

Hi, I am working for a client who requires their django-powered site to be read in Dutch (nl) and Flemish (nl_BE) (and other languages). Although the two languages are very, very similar, there are differences in the text that has been supplied to me. I have created a directory under 'locale'

Re: django i18n and google bots

You could maybe check the user agent and return the desired specific content for bots. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to

Re: django i18n and google bots

I've already submitted a sitemap to google. But as Eugene said, and after doing some research today, I'm afraid that the bots are impervious to cookies. This means that I will have to construct URL with a language designator )c: On May 2, 8:12 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: >

Re: django i18n and google bots

I don't know if it would help, but if you sign up for the google webmaster tools you can set a preferred site root. Also, submitting a sitemap might help. On May 2, 7:37 am, Eugene Morozov <[EMAIL PROTECTED]> wrote: > I think there's no other solution as to use language designator in > URLs and

Re: django i18n and google bots

I think there's no other solution as to use language designator in URLs and placing language links on the main page. There's no way Google or any other bot can crawl the site several times with different cookies or something. Currently I'm redoing site in Django that suffers the same problem and

Re: django i18n and google bots

I have indeed access to my logs, I'll check that and let you know. Many thanks Malcolm. On May 2, 10:32 am, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Wed, 2007-05-02 at 08:16 +, Phil wrote: > > Guys, > > > I use the i18n framework of django to offer my site content in two > >

Re: django i18n and google bots

On Wed, 2007-05-02 at 08:16 +, Phil wrote: > Guys, > > I use the i18n framework of django to offer my site content in two > language: French and English. As the language preference is kept in a > cookie, all the URLs of my site are therefore language agnostic. All > is working fine. > >

django i18n and google bots

Guys, I use the i18n framework of django to offer my site content in two language: French and English. As the language preference is kept in a cookie, all the URLs of my site are therefore language agnostic. All is working fine. But, when the googlebots hits my site, they only hit the French-

Re: Django i18n How

On 1/10/07, johnny <[EMAIL PROTECTED]> wrote: > I have read the django book at djangobook.com. What I wanted to know > now is, how the database content related to the i18n handled. Do I > have to create a separate tables for each language. I have looked at > symfony-project.com i18n >

Re: Django i18n How

I have read the django book at djangobook.com. What I wanted to know now is, how the database content related to the i18n handled. Do I have to create a separate tables for each language. I have looked at symfony-project.com i18n http://www.symfony-project.com/book/trunk/i18n, a php framework,

Re: Django i18n How

On 12/28/06, johnny <[EMAIL PROTECTED]> wrote: Can someone tell how Django does i18n. I am thinking of doing my next project using Django. UI is template tagged, based i18n and i18n dependent database content? Django uses the fairly standard gettext mechanism to handle translations; check

Re: Django i18n How

On 29-Dec-06, at 9:16 AM, johnny wrote: Can someone tell how Django does i18n. I am thinking of doing my next project using Django. UI is template tagged, based i18n and i18n dependent database content? just like python - gettext, _("matter") in scripts and {% trans "matter" %} in

Django i18n How

Can someone tell how Django does i18n. I am thinking of doing my next project using Django. UI is template tagged, based i18n and i18n dependent database content? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups