On Wed, Jul 18, 2007 at 07:00:52AM +0200, Lapo Luchini wrote:
The problem with gettext, IMHO and in my experience, is that your are
never really sure it will work, i.e. actually output translated
strings... e.g. test builds in a directory certainly can't find the
necessary files, or at most
Lapo Luchini wrote:
And using gettext for strings that must be both easily parsable and
consistent over time, mhh just feels wrong.
gettext is a wonderful library for translation of human-oriented
strings, but I wouldn't use it for computer-oriented strings.
So is C a human language or a
Thomas Keller wrote:
It may (?) be a faster intermediate solution, but seems a little too
brittle to be the real solution, to me.
What would be a non-intermediate solution for you?
It is probably a personal little idiosyncrasy but I consider brittle
kinda everything that involves parsing
Lapo Luchini schrieb:
Thomas Keller wrote:
It may (?) be a faster intermediate solution, but seems a
little too brittle to be the real solution, to me.
What would be a non-intermediate solution for you?
... At the moment, I know pretty much *nothing* about basic_io, so
I'm not in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Keller wrote:
Opinions anyone?
It may (?) be a faster intermediate solution, but seems a little too
brittle to be the real solution, to me.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lapo Luchini schrieb:
Thomas Keller wrote:
Opinions anyone?
It may (?) be a faster intermediate solution, but seems a little too
brittle to be the real solution, to me.
What would be a non-intermediate solution for you?
- --
only dead fish
Thomas Keller schrieb:
Monotone uses a couple of global macros which error out well-defined if
something went wrong and this even works for the stdio ostream. However,
what you get as error message is still the same one a normal user would
get. You could start stdio or any other mtn subprocess
Thomas Keller wrote:
Is there any schedule for adding the workspace commands to
automate/stdio? Having at least the basic commands (add / rename /
drop)
available would be really great.
Well, adding those commands to automate is fairly trivial, there are
mostly two problems with it:
a)