Configuration File Changes
Some settings that was stored in MultiCommander.xml is now stored in own configuration files.
It will automatically move the information if found..
FileOperation Read/Write Stratergy => FileOpRWStratergy.xml
FileOperations Plugin Profiles => FileOpPluginProfiles.xml
FileOperation Presets => FileOpPresets.xml
MultiLanguage System Changes
The major changes in this version is how the MultiLanguage system works.
The language files by it self are the same. What is change is how they are stored and loaded.
There are no longer a bunch of language files spread out in different locations for all the extensions.
There are now one language-pack file for every language.
In the Languages folder you will now find LangPack_en.zip , LangPack_se.zip, LangPack_ru.zip and so on.
This is the primary location that MultiCommander will read language files from.
However since MultiCommander will support 3d party extension there need to be a wait for them to deliver there own language files.
So if a language files for an extension is not found in the primary location. It will try to read the language file from a Language subfolder
at the location of the extension. eg (<mcinstall>\Extension\<myextension>\Languages\myextension_en.xml )
However.. This will works well for 99% of the user. But if you are a translator and needs to edit/create a new languages this is not good.
So when you start the built in language editor it will unpack the language pack into a Languages folder in MultiCommanders userdata folder.
(type ":gouserdata" to get to that location ) (This also mean you no longer needs to run MultiCommander as admin to edit language files.)
Now you can editor and change the language files, Either using the built-in language editor or external tool.
When MultiCommander starts it will also look for matching language files in the userdata location and if found they will be used instead of using the language pack files.
One thing to notice is that when you upgrade MultiCommander. And the new LangPack are newer then the unpacked language data in the userdata language folder,
MultiCommander will detect that and go back and use the Language pack files and the Language Editor will inform that there is a version mismatch.
A message dialog about that will also be shown.
Other news to the language editor is that is can now create Language Pack in both the internal and public format.
The Internal format is used when sending a language pack to me to be included into the release.
You will also have the option to upload the language pack directly from MultiCommander instead of sending it using email.
However you will need a submit key. That is so that not anyone can just submit changes with crazy stuff in them.
So mail me to get a submit key if you want to submit language updates this way
(I thinking about automating the language update process. but right now it is not fully automated.)
