On Sun, Apr 19, 2009 at 2:12 PM, Markus <[email protected]> wrote:
>
>> > action.rename has two missing >> << and I think both strings are
>> > currently not in site.language:
>> > Page $1 already exists. Could not rename.
>> > Page renamed from {p} to {=page} by {=author}
>>
>> Messages are automatically translated and don't need the special
>> markup. That's just for plain text in the page.
>
> Ah, right. But still, I couldn't make "Page $1 already exists. Could
> not rename." being translated. I tried copy & paste to make sure there
> is no space missing. No idea why exactly this string does not work for
> me. Shouldn't the following work:
>
> Page $1 already exists. Could not rename. :: Translated text

I'm not sure. Probably because the warning message is generated in the
action page, and not in the command itself, and therefore I can't pass
the page name to the error message properly. I didn't debug
extensively.

One solution is to change the action.rename message to simply: "Page
already exists. Could not rename." without the $1. And then in the
language page we could do:

Page already exists. Could not rename. :: Datei existiert. Nicht umbenannt.

(Or whatever the correct German is). I would rewrite the command, but
then we have the action doing stamps and saving data and wrong
changelog info when ultimately the action fails. I'll have to think
about the best way to handle this. I'll make a note to look into this
some more when I have time.  For now I'd suggest we just go with the
simpler message.  I'll change for the next release, even if it ends up
a temporary measure.

Cheers,
Dan

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"BoltWire" 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/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to