1361: No localization available [#7630]

[A User]

Hello guys

I installed MM4 Built 1361 some minutes ago. Now it show only english interface. There are no other languages available in the configuration dialog any longer. I removed the "locale" folder from my installation and reinstalled MM4 1361 once more. There was no new "locale" folder created. Does this built come without localisation? Old localisation files from built 1357 seem not to be loaded.

[Peke]

It was regression due the http://www.ventismedia.com/mantis/view.php?id=7630

Quick fix just Move 'All Users\Locale' -> 'All Users\MediaMonkey\Locale' will be fixed in 1362+

[A User]

Sorry, but why the hell do you move the locale folder to the (C:\ProgramData\Mediamonkey) folder? At least the default locales should be left in the installation folder (C:\Program Files\MediaMonkey). If MediaMonkey looks for locale files in other folders, too, it's ok, but totally move them is not a good idea.

Let MM look into
1. %USERPROFILE%
2. %ALLUSERPROFILE%
3. Installationfolder
for every file! (Locale, Scripts, Plugins, ...)

I hate the idea of spreading program files all over the system. It is almost as terrible as linux! There is one folder which has to keep all of the files belonging to the Program. If I install MM I need Admin privelidge anyway.

If there is a mechanism to install custom scripts etc. on a per user base this is ok, but moving core program files out of the installation folder is unacceptable!

No Microsoft program would move localisation files to the C:\ProgramData folder as those files are part of the program itself!

[nohitter151]

No Microsoft program would move localisation files to the C:\ProgramData folder as those files are part of the program itself!

No they aren't. They're addons. Just like any addon installed on a per-user basis, those files have to be saved in the user folder.

[A User]

I absolutelly disaggree with you. Each program I know, keeps language files in a subfolder of the installation directory in what ever format is possible. If a program would for example make use of Windows' MUI technolagy it would even be nesseccary to do so as MUI looks into xx-XX subdirectory for the localized resource file of a binary.

Means, imagine MM4 would use MUI instead of gettext. The folder structure would need to look as follows:

<InstallDir>\en-US\MediaMonkey.exe.mui
<InstallDir>\de-DE\MediaMonkey.exe.mui
<InstallDir>\...
<InstallDir>\MedieMonkey.exe
<InstallDir>\...

or

<InstallDir>\MediaMonkey.exe.0409.mui
<InstallDir>\MediaMonkey.exe.0407.mui
<InstallDir>\...
<InstallDir>\MedieMonkey.exe
<InstallDir>\...

Otherwise MUI would not work.

If you would introduce localization files on a per script base, those would belong to the script and should be stored in the userprofile, but not the default localisation files. The only thing I would whish, was a possibility to easily handle localization of scripts. Means having a po-file for each script with the required localization information.

Each user must be able to setup its own language, but not need to download the desired localization files. By default the localization for the program comes with the program setup itself. Only very few power users may add custom localization files as an addon.