edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev]         wordexp again
Date: Sat, 18 Apr 2015 15:48:44 -0400	[thread overview]
Message-ID: <20150318154844.eklhad@comcast.net> (raw)
In-Reply-To: <20150418174410.GO5949@toaster.adamthompson.me.uk>

> 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

  reply	other threads:[~2015-04-18 19:49 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16 21:40 Karl Dahlke
2015-04-17  7:12 ` Adam Thompson
2015-04-17 12:50   ` Adam Thompson
2015-04-17 13:33     ` Karl Dahlke
2015-04-17 17:59       ` Adam Thompson
2015-04-17 13:47     ` Karl Dahlke
2015-04-17 18:01     ` Karl Dahlke
2015-04-17 21:34       ` Adam Thompson
2015-04-17 21:58         ` Adam Thompson
2015-04-17 22:25           ` Karl Dahlke
2015-04-17 22:43             ` Adam Thompson
2015-04-17 23:14               ` Karl Dahlke
2015-04-17 22:28           ` Adam Thompson
2015-04-17 22:39             ` Karl Dahlke
2015-04-18 10:53               ` Adam Thompson
2015-04-18  4:18     ` Karl Dahlke
2015-04-18 10:49       ` Adam Thompson
2015-04-18 11:34         ` Karl Dahlke
2015-04-18 13:09           ` Adam Thompson
2015-04-18 19:33             ` Chris Brannon
2015-04-18 20:05               ` Adam Thompson
2015-04-18 23:03                 ` Chris Brannon
2015-04-18 12:36         ` Karl Dahlke
2015-04-18 12:54           ` Adam Thompson
2015-04-18 13:09             ` Karl Dahlke
2015-04-18 13:24               ` Adam Thompson
2015-04-18 13:45                 ` Karl Dahlke
2015-04-18 17:44                   ` Adam Thompson
2015-04-18 19:48                     ` Karl Dahlke [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-01-09 22:44 Karl Dahlke
2015-01-09 22:19 Karl Dahlke
2015-01-09 22:29 ` Chris Brannon
2015-01-09 21:16 Chris Brannon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150318154844.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).