View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update | 
|---|---|---|---|---|---|
| 0021839 | MMW 5 | Help / Docs / Localization | public | 2025-10-28 20:01 | 2025-10-31 15:22 | 
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always | 
| Status | resolved | Resolution | reopened | ||
| Product Version | 2024.2 | ||||
| Target Version | 2024.2 | Fixed in Version | 2024.2 | ||
| Summary | 0021839: Localizations should update automatically | ||||
| Description | The Japanese translator indicated that his translation of MediaMonkey to Japanese did not update automatically to the latest version. I'm not certain of the update mechanism for languages, but I would expect that they should update automatically. Note: I believe that Languages were previously included in MMW addons (see https://www.ventismedia.com/mantis/view.php?id=6239 that 'Language' was a type of addon at one point), but that we probably removed it from MMW's regular Addons functionality because we decided not to include them in the addons site. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 3174 | ||||
|  | Currently the new version of language is checked and downloaded only when user changes the language in Options > General We could fix this that whenever a new version is installed (e.g. 2024.1 > 2024.2) then the current language should be checked for update and automatically updated | 
|  | Or even better check for new version of language whenever a new version of MM is checked i.e. when [x] Check for updates (when connected) is checked | 
|  | Currently the disadvantage it that lanuages are not part of https://www.mediamonkey.com/_con/addons/apibrowse.php so for every language the whole language file needs to be needlessly downloaded https://www.mediamonkey.com/sw/mmw/2024/lang/cs.mmip extracted and parsed to compare the version | 
|  | The second option sounds good. But how would this work? Would MM indicate that an addon update is available, and the user would update the translation from the addon updates screen? i.e. translations would function as addons from the perspective of the MMW client, but wouldn't use the addons back end? | 
|  | Implemented in 3173 To test this one can modify this file to force the language update: C:\ProgramData\MediaMonkey2024\Locale\<lang_id>\info.json and then this dialog is shown during new version checking (note that 'Include addons' and 'Include beta version' does not need to be checked) | 
|  | Fixed in 3174 | 
