[haiku-commits] Re: r40922 - in haiku/trunk: headers/private/locale src/apps/deskbar src/kits/locale src/kits/tracker

  • From: "Jonas Sundström" <jonas@xxxxxxxxxxx>
  • To: "haiku-commits@xxxxxxxxxxxxx" <haiku-commits@xxxxxxxxxxxxx>
  • Date: Sat, 12 Mar 2011 13:40:56 +0100

Stephan Aßmus <superstippi@xxxxxx> wrote:
> In previous versions of Windows, the german "Program files" was indeed
> "Programme" on the file system level. The problem being that some
> non-localized applications installed themselves into "Program files" so
> you ended up with both folders. Maybe there is no perfect solution to
> this problem, but I like the Windows 7 (Mac OS X is the same) solution
> better.

Maybe hard links could work to give filesystem entries multiple real
locations with localized names. But if not created somewhat lazily
there would quite a lot of them. (How would it affect fs performance?)

> I guess the point is that the majority of users will never look and
> hopefully not have to look at their file system from the Terminal.
> (And BTW, Jonas made this whole thing optional...)

Yes.. In part because of the current WIP state, but also because some
people may want to have localized apps but see the filesystem the way
it "is". I think, however, that this is a kind of setting that would
normally be hidden away somewhere in e.g. Windows or Mac OS X and not
as prominently displayed as now, in the Locale preferences.

> So the solution should be
> a good compromise, because it solves a problem for the majority of
> users. I definitely want the Deskbar application entries translated.
> There are many apps that don't have a real name. "WebPositive" shall not
> be translated, but "Preferences" shall please be and also "Keyboard" and
> so on.

It's a bit of a snowball. If one wants the Deskbar list of running
apps translated it's also expected to have the leaf menu translated,
which shares code with Tracker, which makes Tracker translated.
At the cost of some visible inconsistency, which has to be dealt with.

Speaking of WebPositive, locales are free to keep the name and not
provide a localized form. We could of course opt to force the name,
by not adding the localization resource/attribute and catalog entry.
I don't see a good reason to do so for WebPositive, but it makes
sense to leave the shell commands unlocalized.

> But if there are any better ideas, why should anyone reject them?

Certainly not! :)


Other related posts: