Language Packs for mypal

[rogup1]

Just after installing language pack and setting new language in general options section by clicking set changes and restart browser, Mypal68 crashes with enclosed below error message . I deleted all Profiles from both: C:\Documents and Settings<UserName>\Application Data\Mypal68\Profiles and C:\Documents and Settings<UserName>\Local settings\Application Data\Mypal68\Profiles installed Mypal again, applied language pack again, changed language and saved changes and after launching Mypal 68.13.0b I got the message again:

Does anybody what should I do to make it work? I use Mypal on WinXP SP3 since 29.3.0 and the last ver I was using is 68.12.5b and have never encountered such problem with language pack. I've tried several times with no success trying older language pack from 68.12.5b which I was using and also taken from: http://ftp.mozilla.org/pub/firefox/releases/68.12.0esr/win32/xpi/ and https://addons.mozilla.org/pl/firefox/addon/polski-language-pack/

and @Feodor2 thank you for your great work;

[Feodor2]

Sorrry i forgot mention it in the release note. https://github.com/Feodor2/Mypal68/issues/160#issuecomment-1546736807

New mypal dedicated language needed.. Anyone average user can make it for yourself. I wont do it myself, because it is much more important thing to do now, but can write here some guide.

[rogup1]

Sorrry i forgot mention it in the release note. #160 (comment)

New mypal dedicated language needed.. Anyone average user can make it for yourself. I wont do it myself, because it is much more important thing to do now, but can write here some guide.

@Feodor2 Yes, I'd appreciate a guide very much. Looking forward to it. Hoping asap. Thank you

[Feodor2]

1 Create dedicated mypal langpack

http://releases.mozilla.org/pub/firefox/releases/68.12.0esr/win32/xpi/

1. choose your language and download
2. unpack it somewhere (xpi is a zip format archive)
3. delete these META-INF - signature browser\features\[email protected] - these are not exists in mypal browser\features\[email protected]
4. replace everywhere Firefox name with Mypal name
5. edit miinfest.json accordingly ([email protected] to [email protected])

Do this easy stage so far, then i shall write about next stage.

[rogup1]

1 Create dedicated mypal langpack

http://releases.mozilla.org/pub/firefox/releases/68.12.0esr/win32/xpi/

1. choose your language and download

2. unpack it somewhere (xpi is a zip format archive)

3. delete these
   META-INF - signature
   browser\features\[[email protected]](mailto:[email protected]) -  these are not exists in mypal
   browser\features\[[email protected]](mailto:[email protected])

4. replace everywhere Firefox name with Mypal name

5. edit miinfest.json accordingly ([[email protected]](mailto:[email protected]) to [[email protected]](mailto:[email protected]))

Do this easy stage so far, then i shall write about next stage.

@Feodor2 ok, done, I'm not sure only if I should have changed in pl.xpi\chrome\pl\locale\pl\global\mozilla onto mypal I've changed and it's now: pl.xpi\chrome\pl\locale\pl\global\mypal should I reverse it?

what's next?

[Feodor2]

chrome\pl\locale\pl\global\mozilla

Useless - delete it for save a space.

2 Make changes

1. take language files from old and new versions of the mypal which are inside omni.ja files (omni.ja files have zip format too) browser\omni.ja:\chrome\en-US browser\omni.ja:\localization omni.ja:\chrome\en-US omni.ja:\localization
2. put these to separate folders, for example "old" and "new"
3. compare them to see what was changed I prefer WinMegre, the changes will be colored there So you will know what is changed
4. Put appropriate lines to your language pack and delete no more needed for save the space Look new lines for your language inside newer mozilla language packs, 78 for example
5. Pack it with zip and rename to xpi

[rogup1]

chrome\pl\locale\pl\global\mozilla

Useless - delete it for save a space.

2 Make changes

1. take language files from old and new versions of the mypal which are inside omni.ja files (omni.ja files have zip format too)
   browser\omni.ja:\chrome\en-US
   browser\omni.ja:\localization
   omni.ja:\chrome\en-US
   omni.ja:\localization

2. put these to separate folders, for example "old" and "new"

3. compare them to see what was changed
   I prefer [WinMegre,](https://winmerge.org/l)  the changes will be colored there
   So you will know what is changed

4. Put appropriate lines to your language pack and delete no more needed for save the space
   Look new lines for your language inside newer mozilla language packs, 78 for example

5. Pack it with zip and rename to xpi

@Feodor2 thank you very much for spending your time on this; still I heve question regarding items 1 and 4

ad 1: which new and old releases of Mypal - 68.12.xx and 29.3.0 or 68.13.0b? you listed four lines - this means there will be four language files - two files from two releases?

ad 4: after comparing files which of the lines will be appropriate - only the new ones? and new lines from mozilla 78 should replace them or should be added - how will I know which lines to add? and after it's done this means that I need to put lines from mozilla 78 in language xpi file ver 68.12.0esr I modified yesterday from link you attached in previous post?: http://releases.mozilla.org/pub/firefox/releases/68.12.0esr/win32/xpi/

would really appreciate more info, 'cause I've never done such modifications before

[Pikse]

which new and old releases of Mypal - 68.12.xx and 29.3.0 or 68.13.0b? you listed four lines - this means there will be four language files - two files from two releases?

They mean you should compare 68.12.xx where the original language pack worked, and 68.13.0b where it doesn't. omni.ja and browser\omni.ja are zip archives, just like xpi files. Four listed items are folders in these two archives, and the data structure in these folders corresponds to that of language packs.

I experimented a little and it seems that the simplest fix is to edit chrome\<lang>\locale\<lang>\global\textcontext.dtd in a language pack and add the following missing lines:

<!ENTITY fillGeneratedPassword.label  "Use a Securely Generated Password">
<!ENTITY fillGeneratedPassword.accesskey "S">

At least for my locale this avoids the crash, and most texts appear translated again. Then if you like you can further refine the language pack, look for other changed/missing translations, replace browser name etc.

[andika207]

@rogup1 I fail to understand your obsession for your native language (unreadable with multiple consonats) if you understand english perfectly.

[lemaximedu66]

maybe put the guide in the Wiki ? would be useful.

[shawnpxtl]

I made a Simplified Chinese repair language pack for Mypal, you can see the details this

[Kiki79250CoC]

Hi, I made a French language pack, that you can download here.

PS : Yep the text doesn't fit on the about dialog, but that's because the window is larger in French for some reason, but if I found where the size is defined, it will be fixed in a patch.

[lemaximedu66]

Hi, I made a French language pack, that you can download here.

PS : Yep the text doesn't fit on the about dialog, but that's because the window is larger in French for some reason, but if I found where the size is defined, it will be fixed in a patch.

Thanks man!

[Dystnine]

我为Mypal做了一个简体中文修复语言包，具体可以看 这个

I don't know if there is a way to make a language pack for Serpent 52 or 55.

[TK50P]

It's not perfect, but I also created a Korean language file. In which file should I change firefox to mypal?

[Kiki79250CoC]

It's not perfect, but I also created a Korean language file. In which file should I change firefox to mypal?

In every file where the string "Firefox" is present You can use the "Search in Files" feature in Notepad++ to find every occurrence of "Firefox" in the folder and change them.

[zanud]

In every file where the string "Firefox" is present You can use the "Search in Files" feature in Notepad++ to find every occurrence of "Firefox" in the folder and change them.

"Find every occurrence change them" is not a very smart idea, because there is a number of places where "Firefox" must be leave intact:

1. When "Firefox" is a part of key, like getUserMedia.shareFirefoxWarning.message = .... (Such occurrences can be skipped automatically by using "Match whole word only" mode, except one place: about-telemetry-show-in-Firefox-json-viewer = ...).
2. When "Firefox" is a part of something like "Firefox is a trademark of Mozilla Foundation" or "Use Firefox ESR instead".

[Kiki79250CoC]

Fair point, I wasn't explicit enough. I should have precised that only translated strings must be changed, not the keys themselves.

^{Sorry, that misleading was caused by the fact I prefer to do this kind of manipulations manually, specifically to avoid this kind of "unwanted changes" problems.}

[B-2Admirer]

@rogup1 I fail to understand your obsession for your native language (unreadable with multiple consonats) if you understand english perfectly.

To me at least, it's not about wanting (let alone being obsessed by) my native language or any language other than English, but about a) wanting the UK spell-check, as I'm currently in the UK, and b) wanting the browser to display times in the 24-hour system rather than the utterly idiotic and damn annoying AM/PM. Why anyone would still officially use the 12-hour system (or the Fahrenhype scale) in the 21st century is beyond me, but as they say, Americans like to be different.

[zanud]

a) wanting the UK spell-check, as I'm currently in the UK

Spell checking dictionaries are not a part of a language pack. They must be downloaded and installed separately (and independently of any language pack). For example, from here: https://addons.mozilla.org/firefox/language-tools/

[zanud]

Russian language pack for Mypal 68.14.6b (Русский языковой пакет для Mypal 68.14.6b): https://disk.yandex.ru/d/IkDApmgBU8BcDA

[egrabrych]

Russian language pack for Mypal 68.14.6b (Русский языковой пакет для Mypal 68.14.6b): https://disk.yandex.ru/d/IkDApmgBU8BcDA

I advise anyone who wants to create a language package for MyPal68.14.6+ in their language to use the solutions contained in the Russian language package. Because the range of changes introduced in this package, compared to the original Firefox 68 package, is huge, and earlier "tricks" such as adding only a few code lines, this time they do not work.

[Pikse]

... "tricks" such as adding only a few code lines, this time they do not work

Why not? I added minimal four lines related to picture-in-picture feature, in addition to two lines that were needed for Mypal 68.13, and it works for me. Of course, if you intend to release a complete language pack for general public, it isn't for personal use, then there are many more things to change.

[B-2Admirer]

... "tricks" such as adding only a few code lines, this time they do not work

Why not? I added minimal four lines related to picture-in-picture feature, in addition to two lines that were needed for Mypal 68.13, and it works for me. Of course, if you intend to release a complete language pack for general public, it isn't for personal use, then there are many more things to change.

Could you let us know, which lines you have added? I have just updated Mypal from 68.14.4 and the language pack I created stopped working.

[Pikse]

Could you let us know, which lines you have added?

Sure, I edited browser\chrome\<lang>\locale\browser\browser.dtd and I added these lines:

<!ENTITY togglePictureInPicture.key2 "}">
<!ENTITY togglePictureInPicture.key "]"> <!-- } is above this key on many keyboards -->

<!ENTITY pictureInPictureHideToggle.label "Hide Picture-in-Picture Toggle">
<!ENTITY pictureInPictureHideToggle.accesskey "H">

[B-2Admirer]

Could you let us know, which lines you have added?

Sure, I edited browser\chrome\<lang>\locale\browser\browser.dtd and I added these lines:

<!ENTITY togglePictureInPicture.key2 "}">
<!ENTITY togglePictureInPicture.key "]"> <!-- } is above this key on many keyboards -->

<!ENTITY pictureInPictureHideToggle.label "Hide Picture-in-Picture Toggle">
<!ENTITY pictureInPictureHideToggle.accesskey "H">

Thank you, it worked for me.

[egrabrych]

Could you let us know, which lines you have added?

Sure, I edited browser\chrome\<lang>\locale\browser\browser.dtd and I added these lines:

<!ENTITY togglePictureInPicture.key2 "}">
<!ENTITY togglePictureInPicture.key "]"> <!-- } is above this key on many keyboards -->

<!ENTITY pictureInPictureHideToggle.label "Hide Picture-in-Picture Toggle">
<!ENTITY pictureInPictureHideToggle.accesskey "H">

You are a wizard! I bow in appreciation of your skills.

[JosefReisinger]

Times are changing, and there is 74.1.1; since it is my preferred browser on top of w2k now, I want a german-DEU language and also a retro look as IE 6 . For the language pack, I tried "brute force method", I edited omni.ja and began to change the en-US values into german ones. This surely crashes the browser, as I had to notice. Changing tabbrowser.properties into DEU leaves the browser dead, for instance. It also seems, that for 74.1.1. the so far used 68 esr lng pack is perhaps not sufficiant. How to proceed? Greets from DE-AT, Joe

[zanud]

@JosefReisinger

Do you have a German language pack for some previous version of Mypal?

---

I edited omni.ja and began to change the en-US values into german ones.

Do you have a spare life?

This surely crashes the browser, as I had to notice.

Note that you must use UTF-8 encoding during edition. Otherwise browser's reaction can be unpredictable.

[JosefReisinger]

I'm sorry, they were to buggy for my system, so it was not worth the effort. But now ...

[zanud]

Was a German language pack ever exist in the past?

Try to ask here: https://msfn.org/board/topic/183495-mypal-68

Any old version will be of a great help for you.