Re: filename translation implementation - how to decide

On Wed, 2004-12-15 at 16:21 +0100, Alexander Larsson wrote:
> So, I presented two ways to do filename translation. No method is
> perfect, both has disadvantages. People has picked sides, discussed and
> flames were exchanged. 
> Since the time is ticking for the glib/gtk+ API freeze we're soon gonna
> run out of time to get this API in place at the right place (glib).
> Therefore, to further what I think is the right decision I implemented
> the gettext method in glib/gtk+/libgnomeui/nautilus. Patches and test
> filesystem po file attached.

I discussed this with Matthias and there is no way we feel comfortable
adding a bunch of not-fully-agreed-upon code to GLib right before the

(Time isn't ticking for the GLib/GTK+ API freeze ... that was months
ago, it's ticking for the 2.6.0 *release*, which is this week.)

What we discussed doing was adding:


that does full path => display name (possibly translated) of the last
component, and implementing that for now with g_basename() and
g_file_display_name(). Translation could conceivably be added in a
2.6.x release.


Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]