#13936: django-admin makemessages generates PO files with an incorrect path to
source code files
--------------------------------------+-------------------------------------
Reporter: ciupicri | Owner: nobody
Status: reopened | Milestone:
Component: django-admin.py | Version: 1.2
Resolution: | Keywords:
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------
Changes (by vsla...@fastmail.fm):
* cc: vsla...@fastmail.fm (added)
Comment:
Replying to [comment:3 ramiro]:
> Contrarily to what I understand from the reply Poedit author gave you,
the `xgettext` utility doesn't use paths relative to the location of the
`.po` file being created/updated in the `#: admin.py:12` comments. It uses
paths relative to the path where it was invoked from.
(Poedit author here.) That's how I meant it, sorry for being unclear. It
is a de-facto standard (see Automake and/or libintl makefiles) to invoke
`xgettext` from the PO files directory. As indicated in a comment above,
Poedit isn't the only tool that assumes this. When you think about it,
it's the only way to express source code references that would be self-
contained and would work without some additional externally provided
information.
> `makemessages` isn't working in a way different from xgettext here
Is it possible to invoke it from the PO files directory?
Even if it is, it would IMHO make a lot of sense to use the attached
patch, because PO files location is well-known in Django and unlike with
direct use of `xgettext`, it's not (I think) common to change into a
specific directory when using `django-admin`.
--
Ticket URL: <http://code.djangoproject.com/ticket/13936#comment:8>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
