>
> My problem with that is that we already have a localization mechanism,
> that takes into account that GtkBuilder is a Gtk specific implementation
> detail.
>
> In short it introduce a problem for the 2 other platforms.
>
I don't see how. It only affects the GTK-specific files anyway. It's
not like I'm ripping code out of the Windows and Macintosh versions.
Granted, it does introduce a level of redundant messages to the .po
files (for example, GTK+ uses underscores instead of ampersands for
keyboard shortcuts), but that's no worse than the exact same messages
that only differ in case now, which occurs in the .po files currently.
Just remove the fuzzy flag, replace the character(s), and go about
your business.
This was part of the project description from the beginning. I put it
off until last being how nightmarish intltool is. I really didn't see
a point in it, since the dialogs were being translated fine after the
change to gettext, but my mentor mentioned how the way it's being done
now is suboptimal. I believe his exact word was "hellish."
Received on Mon Jul 20 07:26:02 2009
This archive was generated by hypermail 2.1.8 : Mon Jul 20 2009 - 07:26:02 CEST