Woohoo! Looks like I solved it.
The error I had made was that inside my locale folders I had named
Swedish "sv_se" which wasn't right. I looked into the django/conf/
locale folder and saw that there they referred to Swedish as "sv". So
by changing the folder names Django finally found them.
Oh,
I did just check the permissions, and even tried change them to a=rwx.
Still not working.
I tried a couple of other things as well - I made a symlink in one of
my folders on my PYTHONPATH pointing to my project (it required me to
do that in order to run the django-admin.py makemessages command) a
On Tue, 2008-11-25 at 03:01 -0800, Alex Jonsson wrote:
> Thank you everyone for your feedback.
>
> I forgot to mention that I read that paragraph in the docs as well and
> already installed the LocaleMiddleware. This makes the translation of
> the built-in modules work, but not my per-app transl
Oh, and another note.
I have checked my browser language, it's set to Swedish. That works
locally as well with LocaleMiddleware.
On Nov 25, 12:01 pm, Alex Jonsson <[EMAIL PROTECTED]> wrote:
> Thank you everyone for your feedback.
>
> I forgot to mention that I read that paragraph in the docs as
Thank you everyone for your feedback.
I forgot to mention that I read that paragraph in the docs as well and
already installed the LocaleMiddleware. This makes the translation of
the built-in modules work, but not my per-app translations. This was
why I was thinking that maybe it had something to
On Tue, 2008-11-25 at 11:39 +0100, Jarek Zgoda wrote:
> Wiadomość napisana w dniu 2008-11-25, o godz. 11:17, przez Thomas
> Guettler:
>
> > The last days I did my first i18n application and befor I read this:
> > http://docs.djangoproject.com/en/dev/topics/i18n/
> > {{{
> > Application message
Wiadomość napisana w dniu 2008-11-25, o godz. 11:17, przez Thomas
Guettler:
> The last days I did my first i18n application and befor I read this:
> http://docs.djangoproject.com/en/dev/topics/i18n/
> {{{
> Application message files are a bit complicated to discover -- they
> need
> the Local
The last days I did my first i18n application and befor I read this:
http://docs.djangoproject.com/en/dev/topics/i18n/
{{{
Application message files are a bit complicated to discover -- they need
the LocaleMiddleware.
If you don't use the middleware, only the Django message files and
project messa
Wiadomość napisana w dniu 2008-11-25, o godz. 09:23, przez Thomas
Guettler:
>> I have some problems with the translations of my website. Locally, it
>> works flawlessly. But as soon as I run the project on my server, it
>> won't translate. I've translated the project per app.
> Translation per
Alex Jonsson schrieb:
> Hey guys,
>
> I have some problems with the translations of my website. Locally, it
> works flawlessly. But as soon as I run the project on my server, it
> won't translate. I've translated the project per app.
Translation per app only works if you have the LocaleMiddleware
Hey guys,
I have some problems with the translations of my website. Locally, it
works flawlessly. But as soon as I run the project on my server, it
won't translate. I've translated the project per app, and I'm
wondering if it could have something to do with my PYTHONPATH? As of
now, my .htaccess
Hi there,
Actually, it's plainly that. It's just not working, and I don't really
know where to look for a flaw. It's just a blind guess, but maybe django
is not correctly locating my .mo files? I've triple-checked their
location and tried in every place stated in the documentation or the
django b
12 matches
Mail list logo
