View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007592 | MMW v4 | Install/Config | public | 2011-03-24 22:36 | 2012-11-27 18:45 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | tweak | Reproducibility | N/A |
| Status | feedback | Resolution | open | ||
| Target Version | 4.1 | ||||
| Summary | 0007592: Installer language string customizations should be translated automatically | ||||
| Description | As talked in 0007438 due the lots of conflicts and specific way on how MM languages are incorporated as of MM 4.0 and taking notice on how they are translated using .po files there was need to revise actual handling of files, while making developer team easier/simpler access to translated files and its compiling into MediaMonkey Setup. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
| related to | 0007438 | closed | peke | Automated download of localization files |
| related to | 0007541 | closed | peke | Transcription errors in installer strings (Regression) |
| related to | 0007542 | closed | peke | Update strings to v4.0.0.1355 |
| related to | 0007543 | closed | petr | InnoSetup Custom Messages duplicates used in MM script. |
| related to | 0007856 | closed | petr | Update strings/installer .isl to string version 4.0.0.1375 |
|
|
- Based on http://www.jrsoftware.org/files/istrans/ native/default installer languages are put to InnoSetup\Languages which will be updated accordingly to languages that gets added - Non Native/Default languages are downloaded into their respective folders and correctly versioned - All MM [CustomMessages] are now in install.isl under their respective folders which simplified updating future translations - MediaMonkey-Main.iss corrected to point to correct files and translations - po\Empty\install.isl contain English MM strings to be used for future translations |
|
|
TO-DO: 1. Clean remaining duplicate files 2. sync install.po in all languages to contain same Strings as install.isl 3. make all strings in install.po are in same order as in install.po files for easier future updates of install.isl |
|
|
Reminder sent to: jiri, petr, rusty Updating of installation files should be much easier in future versions of MM |
|
|
1. Fixed |
|
|
2, 3 are done for Empty, Chinese (hant), Dutch (nl), Italian (it) |
|
|
Peke, just to be clear ... now you just need to convert install.po files to install.isl, so ISL files are updated, right ? I think it's the only step we need to do, isn't it? Also would it be better to make a small app which make this conversion automatically (i think i shouldn't be hard to develop). |
|
|
1. Re PO vs. isl files: I was thought same but as ISL files are plain ASCII txt files written in local Character CodePage and PO files are UTF-8 written in plain/TXT files. I asked Rusty same thing and in the past when we included ISL files they were left non-translated in 99% of cases. 2. Yes, I got green light and when I'm finished with cleanup of all PO files (Check how Trunk\po\Empty\Install.po and Trunk\po\Empty\Install.isl looks like) it should be easy to add and use Copy Paste. I'm guessing that it could be useful to have own app to make things more automatic but only after all cleanups are done. EG we can think of it for MM 4.1 Strings/Changes |
|
|
parts 2,3 are done for Finnish (fi) and Polish (pl) |
|
|
All PO and ISL Files that are correctly updated to Latest MM install strings as described in 0007542 for others I would need to do double job after translations are done. I would suggest to either set it as Suspended -> 4.1 or Inform translators to do translations? |
|
|
OK. Re-opening for MM 4.1 and leaving on your plate. What remains to be done is to create a script that will automatically update .isl files based on custom strings (that aren't part of a normal innosetup installer) that are included within install.po. |
