-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to make custom language pack for user interface? #36
Comments
I do not know much about language packs and how they work, but I can point you in the right direction. The SeaMonkey 1.1.19 language packs might work unmodified or with slight modification. The most likely cause for modification will be changing the version string in install.js in the xpi. You will need to unzip the xpi (7-zip will work fine for this), make your modification, and re-zip the contents back into a zip file with the extension xpi. A version string of 2.2.20190223 should work for the latest 2.2 build posted here. However, I cannot guarantee how well it will actually work. Various UI elements have been replaced/added/removed since RetroZilla was forked from SeaMonkey 1.1.19. Depending on how language packs work, some text strings may still be in English or not display at all. If you would like to read into this more, here is a link to the Mozilla localization page from around the time of SeaMonkey 1.1.19's release. If you do make a RetroZilla-compatible language pack, please send it to me. I will find a way to make it accessible to any other Russian-speaking users that may want it. |
I have installed the Spanish language package from Seamonkey 1.1.19 and then Retrozilla 2.2 has become unusable. Having to uninstall and reinstall Retrozilla. |
Same result with the de-AT language file from http://archive.mozilla.org/pub/seamonkey/releases/1.1.19/contrib-localized/ |
How can I translate RetroZilla user interface to Russian? I've heard about .xpi language packs, but I doubt that SeaMonkey translation packages will be suitable for RetroZilla.
The text was updated successfully, but these errors were encountered: