I did a little digging to get this working and here's what's going on:
The process calls to xgettext, msguniq, and msgmerge all yield
warnings to standard error. However, the programs exit with status 0
so they're not in error, just emitting messages to standard error.
The code in the management command 'makemessages', however, interprets
anything emitted to standard error as a CommandError and raises it as
such.
It looks like the process exit status could be captured, but it might
not work on non-unix platforms (I have to look deeper at the python
popen stuff).
Would it make sense to open a ticket for this? Maybe bring this up in
Django Developers?
doug.
On Jan 22, 10:50 am, Doug Van Horn <dougvanh...@gmail.com> wrote:
> I'm trying to avoid changing my database around to accommodate
> localized strings. I'm putting all strings from the database into a
> holding file (db_messages.py) which get dumped into my django.po file.
>
> The problem is that textarea fields contain "\r\n" as line endings,
> and running something like:
>
> _("This is line 1\r\nThis is line 2")
>
> through makemessages will get you an error:
>
> Error: errors happened while running xgettext on db_messages.py
> [snip]/db_messages.py:10: internationalized messages should not
> contain the `\r' escape sequence
>
> If I add the \r manually to the .po file, the messages will compile
> without issue.
>
> Has anyone else bumped into this?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
