Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#21209 closed Bug (fixed)

Windows: Wrong file location path comments in .po files generated by makemessages

Reported by: Ramiro Morales Owned by: Ramiro Morales
Component: Internationalization Version: dev
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no
Pull Requests:How to create a pull request

Description (last modified by Ramiro Morales)

The comments associated with literals found on files of the 'django' domain that aren't Python source code end like this (from the test suite):

# .\template\test.html.py:55
msgid "The translatable literal here"

it should be:

# template\test.html:55
msgid "The translatable literal here"

to be on par with the file generated on Unix, or even possibly:

# .\template\test.html:55
msgid "The translatable literal here"

But the .py prefix shouldn't be leaked.

Change History (3)

comment:1 by Ramiro Morales, 11 years ago

Description: modified (diff)

comment:2 by Ramiro Morales <ramiro@…>, 11 years ago

Resolution: fixed
Status: newclosed

In 4b715fc05a75c375d5afe1860ce748ae2a2e290b:

Fixed #21209 -- .po file path comments on Windows.

Literals from source files with Django template language syntax don't
have a '.py' suffix anymore.

Also, the '.\' prefix is preserved to respect GNU gettext behavior on
that platform.

Refs #16903.

comment:3 by Ramiro Morales <ramiro@…>, 11 years ago

In d16753eecd3c97c781382fbb4c119f6bae314487:

[1.6.x] Fixed #21209 -- .po file path comments on Windows.

Literals from source files with Django template language syntax don't
have a '.py' suffix anymore.

Also, the '.\' prefix is preserved to respect GNU gettext behavior on
that platform.

Refs #16903.

4b715fc05a from master.

Note: See TracTickets for help on using tickets.
Back to Top