View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007438 | MMW v4 | Install/Config | public | 2011-02-23 17:02 | 2020-11-19 05:37 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Target Version | 4.0 | Fixed in Version | 4.0 | ||
| Summary | 0007438: Automated download of localization files | ||||
| Description | It should be possible for a user to install MM in any of the languages for which translations exist. A possible mechanism for this would be to: a) include the install.po files for all languages, so that users can choose whatever languages have been translated b) upon completion of the installation process, the full .mmip file is installed and the appropriate language configured. This would remove a barrier that exists for many non-English speakers who have trouble understanding how to install and subsequently configure the current .mmip files. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1357 | ||||
| related to | 0006493 | resolved | rusty | MMW v4 | Automated codec installation/purchase mechanism |
| related to | 0005314 | closed | peke | MMW v4 | WebHelp: Switch to web-based help |
| related to | 0007541 | closed | peke | MMW v4 | Transcription errors in installer strings (Regression) |
| parent of | 0007500 | closed | peke | MMW v4 | Selected laguage in installer not shown in Options |
| has duplicate | 0005313 | closed | peke | MMW v4 | Make languages downloadable via the installer |
| related to | 0007491 | closed | peke | MMW v4 | Portable mode text is unclear |
| related to | 0007592 | feedback | peke | MMW v4 | Installer language string customizations should be translated automatically |
| related to | 0017116 | closed | petr | MMW 5 | Installation / Config localization requirements |
|
|
Set to 'immediate' to determine if any new strings are required. e.g. 'Downloading language files for:' <language> 'Failed to download language files for:' <language> |
|
|
Since InnoSetup doesn't have any build http download features, the easiest way would probably be to add new features to MM.exe: 1. Add a new MM command line parameter /InstallLanguage=xx that would download and install a MMIP package from http://www.mediamonkey.com/sw/lang/xx. 2. MM.exe would return a non-zero error code in case of download failure - in which case the installer would show appropriate message. 3. Note that currently Addons installation supposes that MM is fully started with UI. This command line installation expects that no UI would be involved (including success or failure messages in MM). In case it would be too complicated to make the current code compatible with such a UI-less mode, we could make a simplified version targeted to languages installation only - it would disregard install.ini file and only unpack content of the .MMIP (i.e. ZIPped) package. When this is completed we only need to: 4. Add a new sheet showing the 'Downloading...' message and calling the above functionality. 5. Modify MediaMonkey-Main.iss file so that it includes all the supported languages. Note that currently we use many ifdefs for this purpose, but since newer InnoSetup versions have CustomMessages section with multi-language support, we could significantly simplify all this. Ludek, when 1-3 is done, feel free to assign 4-5 to Petr, who better knows InnoSetup (but you can do it yourself, if interested). |
|
|
Items 1-3 are done, assigning 4-5 to Petr |
|
|
Raising priority so that strings can be finalized. |
|
|
Installer functionality is implemented. Assigning to Peke to make isl files for installer (based on install.po files). |
|
|
All .isl created and I also corrected Serbian and Chinese according to http://msdn.microsoft.com/en-us/netframework/dd890508.aspx |
|
|
Note: Hungarian.isl is completely untranslated as install.po was missing. |
|
|
Missing features: 1. Some languages aren't complete, e.g. "Chinese(Simplified).isl" contains custom messages only, not all of them (downloaded from InnoSetup web). 2. English.isl doesn't have all the custom messages. Actually, all of the .isl files should have them, so that they are properly shown even in case they aren't translated for the language yet. 3. Note that .isl files are in specific codepages (see LanguageCodePage=xxxx identifier), so we should make sure that our added messages are in the correct page. |
|
|
Assigning to Petr to clear what exactly is needed. |
|
|
Reassigning to me after IM talk with Jiri |
|
|
4. Some languages fail to download (requires further investigation--perhaps links are incorrect?) |
|
|
4. I found out the reason, it's because e.g. Finnish.mmip install script wanted to install Tips.mo file, but it is no longer part of the MMIP file. So the install failed. I fixed Finnish.mmip, but other languages need to be tested and fixed if necessary. Peke, please test all of them. |
|
|
Updated all languages, I have also moved [CustomMessages] to top part of file and surrounded MM custom Messages around: ; Start of MediaMonkey Custom Messages ; --------------------------- ; End of MediaMonkey Custom Messages ; --------------------------- So that hey can be easily found and updated later. |
|
|
Added PortableModeTooltip= to MM custom messages for all languages. |
|
|
correct codepages are added to all isl files from http://www.mydigitallife.info/2007/08/12/ansi-code-page-for-windows-system-locale-with-identifier-constants-and-strings/ so that those that have localized windows will correctly switch codepage even for english. |
|
|
all fixed. |
|
|
Reoppen after IM talk with Petr that Original files that come with InnoSetup should not be included but our custom .isl files should be appended with translation within MediaMonkey-Main.iss script for each language. Included and external .isl files for MM languages can be found here http://www.jrsoftware.org/files/istrans/ |
|
|
Gege's PTBR language file updated in 1357 |
|
|
Corrected all languages and main iss script, InnoSetup folder was lacking original language files. Now all language isl files are contained in their respective folders |
|
|
Originally fixed in 1353 and fully corrected using unified folder structure and files in 1357 As of 1357 Setup uses new unified language folder structure and from now on it is much easier to manage and translate. |
|
|
Reminder sent to: petr Can you please close it as you have confirmed that main iss script compile without problems as of 1357. |
|
|
Verified 1362 |
