I have to search again to filter only the non ascii chars in the comments.
Right now I have a list of all non ascii characters. But I am considering
upgrading to 1.4 before that not only for the translations. If not, or if
the problem still exists by then I will search for the exact template.
Th
On Tue, Mar 26, 2013 at 9:23 AM, Bastian wrote:
> If I understand well, your fix is used to allow non ascii characters in the
> comments of a template. I found non ascii characters outside comments too,
> won't this break also?
Unfortunately we don't have information about which template file is
If I understand well, your fix is used to allow non ascii characters in the
comments of a template. I found non ascii characters outside comments too,
won't this break also?
On Tuesday, March 26, 2013 12:19:36 PM UTC+1, Ramiro Morales wrote:
>
> On Tue, Mar 26, 2013 at 8:04 AM, Bastian >
> wro
Thanks Ramiro,
I don't know the actual burden of upgrading a whole project from 1.3 to 1.4
but it does sound terrifying :) I might go the patch way.
On Tuesday, March 26, 2013 12:19:36 PM UTC+1, Ramiro Morales wrote:
>
> On Tue, Mar 26, 2013 at 8:04 AM, Bastian >
> wrote:
> > Hi, I am trying t
On Tue, Mar 26, 2013 at 8:04 AM, Bastian wrote:
> Hi, I am trying to create a .po file to start a translation. I use the
> command './manage.py makemessages -l ru' to try to create the Russian
> locale. The script seems to be working for a while and then crashes with:
>
> processing language ru
>
Hi, I am trying to create a .po file to start a translation. I use the
command './manage.py makemessages -l ru' to try to create the Russian
locale. The script seems to be working for a while and then crashes with:
processing language ruTraceback (most recent call last):
File "./manage.py", li
6 matches
Mail list logo
