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 death, and the conclusion is that
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 changing the
> code using GET.
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
>> GET var (for example &language_code=en) ?
>
> I think it'
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 &language_code=en) ?
I think it's a critical problem.
We spend time to ma
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 &language_code=en) ?
--
Alessandro Ronchi
Skype: aronchi
http://www.alessandroronchi.net
SOASI Soc.Coop. - www.soasi.com
Sviluppo Softw
5 matches
Mail list logo