> I doubt anyone was a fan of the "shell pattern did not match any files"

Indeed, I'm just saying there is a process here.
If I change substantially an error message, or add a new one,
I have to add it to a queue of messages to be translated by my friends
into 4 other languages.
(And I'm hoping for more languages in the future.)
I don't want to pester them weekly with small changes,
nor do I want to hit them up with 50 messages to translate at a shot,
so when the queue has about ten or so, or there is a release coming up,
I send them the new messages for translation.
That's all fine, I'm just saying it's not just a matter
of changing a printf.
If I suddenly get hit by a meteor, their names and emails are in messages.c.

> environment variable is not defined
> ...
> I'd like to see this message improved to include the variable though.

This one I just pushed,
and it was simple enough that I could do it in all languages,
so no need to put it on the queue.
I could tell the words for undefined, and environment variable,
and I could turn it into something like $foo is not defined, in all languages,
even Polish, which is the least recognizable for me.
Sometimes I feel like I should be able to handle the German myself,
I almost can, but let's not get cocky,
because conversational German is not the same as technical German.

Karl Dahlke
_______________________________________________
Edbrowse-dev mailing list
[email protected]
http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev

Reply via email to