Created attachment 6543 [details]
picture of Nautilus with this problem

I didn't realize this was Nautilus 1.0.6.

Translations for Nautilus 1.0.6 should not be in UTF-8.
I wonder how a UTF-8 string go into the fr.po file.

Ah, the string "Directory" comes from gnome-vfs. For some reason,
gnome-vfs is giving us a UTF-8 string. And I think I know why. I
think that gnome-mime-data, which is shared between gnome 1 and 2,
contains localizations in UTF-8.

We could either split the gnome-mime-data package into a GNOME 1
version and a GNOME 2 version (generated from the same CVS data, but
the translations would be formatted differently), or we could have
GnomeVFS stable convert from UTF-8 to the locale character set using
iconv.

Side note: It's actually the localization for "folder". I'm not sure why the French version is capitalized.

> I'm not sure why the French version is capitalized.

Because its French, so it has to be different.

This is caused by @INTLTOOL_KEYS_RULE@ in Makefile.am which is always
translated as 
"%.keys:      %.keys.in      $(INTLTOOL_MERGE) $(wildcard)
$(top_srcdir)/po/*.po) ; $(INTLTOOL_MERGE) $(top_srcdir)/po $< [$]@ -k
-u", even when compiling for GNOME 1...

If I remove the '-u' by hand, gnome-vfs stable is ok but we will get
in trouble with gnome-vfs2 :((

Of course, but that's intentional.

The issue isn't intltool and what options to pass. We know how to get
either a UTF-8 file or a "local encoding" file. The question is how
we can get two different versions of gnome-vfs to work with the same
file.

The three proposed solutions are:

	1) add character-set conversion to the old gnome-vfs for Gnome 1,
so it reads UTF-8 files, but converts the text to the locale character
set on the fly
	2) make a gnome-mime-data for Gnome 1, using the same data, but
with appropriate encodings for Gnome 1, in a location that doesn't
conflict with gnome-mime-data for Gnome 2, and change the gnome-vfs
for Gnome 1 to look there
    3) move MIME data back into gnome-vfs for Gnome 1, but put it
somewhere where it won't conflict with gnome-mime-data

If you have additional suggestions for possible solutions, they would
be welcome.

Seth, when are you going to tackle this?

I've already started poking into the MIME database to implement (1)
(on the fly conversion).

Adding the GNOME2 keyword since could affect how gnome-vfs for G2 is
installed.

No, none of the solutions we are considering involves any changes
to the Gnome 2 version at all.

It's possible that in the future we might change our minds, but it
seems extremely unlikely.

I suggest removing the keyword.

I'd like to see this fixed as soon as possible.

Ooops, forgot to close the bug. I fixed this in stable gnome-vfs,
please re-open if you still see the problem.

Mass resetting target milestone to clean up gnome-vfs milestones. Please
complain if I removed a milestone which should have been kept. Sorry for the spam