Open GoogleCodeExporter opened 9 years ago
Here's a patch, inspired by http://code.djangoproject.com/changeset/10751 which
should make rosetta work for 'settings as directory' and 'settings as file'.
Original comment by ebelu...@gmail.com
on 13 Apr 2011 at 9:55
Attachments:
Hi.
I see the purpose of this ticket, and the patch seems perfectly valid (in that
it doesn't break any test cases) but I'm having a hard time trying to reproduce
the issue, maybe you could help?
So all I did was create a settings directory, and renamed my settings.py file
to settings/__init__.py but this doesn't really change Rosetta behavior. What
am I missing?
Thanks.
Original comment by mbonetti
on 13 Apr 2011 at 11:21
When you have a "settings" directory and a "locale" directory, go to rosetta
and try to look for just the 'project' files, it will tell you you have no
translations. if you apply this patch and it will detect the project
translations.
Original comment by ebelu...@gmail.com
on 13 Apr 2011 at 12:14
That's exactly what I have, still I see the translations, hence my comment.
Are you running Django 1.3?
Original comment by mbonetti
on 13 Apr 2011 at 12:55
I am running django 1.1 and python 2.5. I can see all the project translations
when I click on 'All', but when I click on 'Project', there were no
translations, just a message saying i had no translations set up.
Original comment by ebelu...@gmail.com
on 13 Apr 2011 at 2:10
Thanks, this is likely related to the Django version. I'll get hold of a copy
of 1.1 and run the tests again.
Original comment by mbonetti
on 13 Apr 2011 at 2:24
My Django installation serves 2 different domains, they share more then 80% of
the codebase, settings, and translations. For this reason i have the following
layout:
* A settings package, this contains the global settings, and URL-conf
* A sub-package for each subdomain that imports and expends the global
settings, and URL-conf.
So i'm starting my dev-server with ./manage.py runserver
settings=settings.site_a
With this configuration rosetta could not find any "Project Translations", but
it shows me the 3rd Party Translations. The Patch above fixes this issue for me.
I'm using Django 1.3 and Rosetta 0.6.0
Original comment by xeniac...@gmail.com
on 5 Jun 2011 at 1:25
The patch works for me too (settings directory).
Django 1.3 and Rosetta 0.6.2
Original comment by martin.b...@gmail.com
on 6 Aug 2011 at 11:53
Original issue reported on code.google.com by
ebelu...@gmail.com
on 13 Apr 2011 at 9:26