Re: [PATCH] Do not use gettextize and i18n round 2 Re: I18n: The gettext proposal

Justin Erenkrantz <justin@erenkrantz.com> writes:
> I think my biggest concern for i18n adoption is that we will no longer
> be able to use constant char *'s for our error strings (the big help
> structs). A lot of our help code and error strings rely upon that, so
> I don't know how we're going to refactor that. It's not something I
> want to do. -- justin

Why wouldn't we be able to continue using const char * strings?

I thought the Gettext Way was just to prefix each one with an
underscore. Then gettext does

   #define _" SOME_GETTEXT_MAGIC

and the preprocessor replaces each string with a call to
gettext(string), which copies the string out to a table, and the human
translators use the entries in that table as the index side of their
.po files, etc, etc.

In other words, I thought the whole point of gettext was that it
allows you to continue using the same const char * strings in your
source code. I might be very ignorant though. If I am, blame Ben
Collins-Sussman, who just explained gettext to me :-)

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 30 20:19:05 2004