2007/3/9, Malcolm Tredinnick <[EMAIL PROTECTED]>:
>
> On Fri, 2007-03-09 at 16:37 +0100, David Larlet wrote:
> > Hi,
> >
> > I'd like to help in french translation but make-message.py return
> > errors, maybe I do not use the script correctly:
>
> Looks like you are doing the right thing. Although '-v' is obviously a
> bit optional if you don't like all that output.

Ok, that's just to help problem diagnosis.

> >
> > In english, the warning is about arguments order. How can I bypass
> > errors and then contribute?
>
> They are warnings, though, not errors, right? So it should continue and
> generate a file in any case (if the @#$%& GNU people have made warnings
> trigger a failure, I am going to start swearing).

My mistake, I haven't seen the .pot generated file.
>
> Fixing this particular bunch of problems is going to happen real soon
> now (like within a couple of days). The particular cases are not cases
> where you need to reorder the arguments, from memory, but I will fix
> things up by applying a patch that's in Trac when I get a minute.
>
> Can't do it right this minute because I'm fixing a slightly larger
> disaster that I created in the code (and I might need to actually get
> some sleep at some point). :-(

Sorry for your night, just a quick question ;-)

In my .pot generated file, I have already translated sentences eg:
in django.po:

#: contrib/admin/filterspecs.py:117
msgid "This year"
msgstr "Cette année"

in django.pot:

#: contrib/admin/filterspecs.py:117
msgid "This year"
msgstr ""

I thought it was the gettext goal not to translate strings twice. Did
I miss something? A bug? Just to be sure not to do the work twice.

Thanks,
David

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django I18N" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/Django-I18N?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to