Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

My Browser Builds (Part 1)


Recommended Posts

i guess Im going back to NewMoon, i like the look of it alot better than the basilisk browser. Although there is a problem. Unlike basilisk, NewMoon will never let me post on this page, or any page for that matter. it will just stay on the loading screen and never change... Anyone else have this problem?


  • Like 1
Link to comment
Share on other sites

I didn't time it, but I'd say under 2 seconds. You do have a problem. However either it's related to the hardware you're using (I'm using an i7 3770K on a Z68 mobo), or some other software (or addon) you have insatalled is interfering with New Moon's correct working. But let's wait for @roytam1, since he may well have some more specific idea than I do. In short: if basilisk works (you said it does) and if FF esr v. 52.5.3 works (you didn't say anything about it), then I don't see why New Moon wouldn't work... and it does not, in your case. I'm baffled. :dubbio:

Link to comment
Share on other sites


@roytam1 is providing a tremendous service to the XP community with his xpmod builds of PaleMoon 27.7.0a2 (which, for legal reasons, have to be rebranded to NewMoon); actually, the Vista community too owes a lot to him for his xpmod builds of Basilisk (officially supported only on Win7+); when PaleMoon (28.x.x ?) is ported over to the Moebius platform (that Basilisk is built upon) sometime during this year, I assume PaleMoon will drop official Vista support at that time, since that platform officially supports Win7+; so I, a Vista fanatic, will be also relying on his xp-vista-mod PaleMoon builds...

roytam1 is compiling his builds off code from the unstable PaleMoon channel, IOW from the master branch of the github development repository at https://github.com/MoonchildProductions/Pale-Moon/commits/master . His patches don't touch the GUI strings at all, so if your installed LP fails, it's nothing to do with his modifications...

You shouldn't expect him to be also responsible for providing compatible and always up-to-date language packs each time he's releasing a new compile of NewMoon; even Moonchild Productions don't offer LPs for their "unstable" channel (PaleMoon 27.7.0a2).

If you absolutely must use a PaleMoon xpmod on your native tongue, then I suggest you switch to the other option available from Feodor2; he's building on the release channel of PaleMoon, for which official LPs do exist...

If you (and others) like to stick with roytam1's builds, then

1. The point of reference for language packs is JustOff's repo at https://github.com/JustOff/pale-moon-localization/releases (and I have posted about it several pages back in this thread).

This repo is only updated from time-to-time, as need arises/if deemed necessary by the dev (and depending on the work committed by the respective LP contributors...).

If after a NewMoon (manual) update (with a LP installed) you find that:

1. You can't start/load/access the main GUI (infrequent but plausible), then start NewMoon in Safe Mode and disable/uninstall your LP; restarting, you'll end up in the working default en-US locale...

2. If the browser starts OK but parts of the GUI turn out broken, then, and depending on the part broken, do as advised in case #1 (if only unimportant parts are broken, I can easily live with that for some days...).

When your localised browser GUI breaks, this means upstream changes have taken place in the default en-US locale with the new update, changes which, of course, are not reflected in your installed (rendered outdated) LP...

If you're not savvy enough, then the only thing you can do is stay with the default en-US locale and revisit JustOff's repo often, in the hope an updated LP is posted; no use in pestering roytam1 about the (temporary) breakage...

E.g., the issue reported by @AstroSkipper is now rectified by installing updated LP 27.7.0_RC6 ; people, patience is really a virtue!


For those impatient that are not faint at heart but are a tad on the savvy side, there's always the possibility to update yourself your failing LP; you need:

1. Your (outdated) language pack downloaded on disk; it's an xpi (renamed zip) file.

2. 7-zip (installed / portable)

3. A proper text editor (not notepad|wordpad; I use PSPad, though I understand Notepad++ is very popular)

4. Very basic knowledge of GitHub and git version control.

5. Some familiarization with the internal structure of Mozilla browsers' language packs.

Latest roytam1's NewMoon build is based on commit git-d74da28, while his immediate previous one was built off commit git-40aa3cc ; the changelog during the update can be viewed in the following GitHub URL: https://github.com/MoonchildProductions/Pale-Moon/compare/40aa3cc...d74da28 (it's the list he posted here)

23 commits were pushed; now change focus to the "Files changed 41" tab and search for changed files with " browser/locales/en-US/" in their path:


By clicking on those links you'll see the changes committed on each file (which are responsible for the breakage of your installed LP). E.g. the "Security" (Sicherheit) tab in the Preferences window broke in the LP v27.7.0_RC5 because file "preferences/security.dtd" was changed as seen here:

 <!ENTITY  passwordExceptions.accesskey  "x">
+<!ENTITY  autofillPasswords.label       "Automatically fill in log-in details">
+<!ENTITY  autofillPasswords.accesskey   "A">
 <!ENTITY  useMasterPassword.label        "Use a master password">
 <!ENTITY  useMasterPassword.accesskey    "U">

i.e. three new lines were inserted into previous code.

You have to unpack your local copy of de.xpi v27.7.0_RC5 with 7-zip, locate inside all those locale files (8) that were changed according to the github URL (and the list I posted) and patch each one of them manually with your editor (according to the online diffs for them); then you have to translate any new en-US strings to your language, German in this case; double and triple check you have done everything as it should be done, save your changes and repack your edited LP into an .xpi file; finally, install to NewMoon via drag-n-drop, restart and you should be good to go; takes time, yes; but you then begin to appreciate all the labour spent by translators (though, to be fair, they have automated tools for their job and only rarely things have to be done in a harder manual fashion...).


May I voice a personal request: Could you create a special, dedicated thread for your xpmod of the Basilisk web browser (which is currently only a test-bed for the Moebius platform, but may survive as an application even after PM is ported to the new platform)? This thread has sort-of become a mixed bag now, actually three distinct browsers are currently being featured/discussed, I feel it'd be better for everyone following this thread if three separate new ones are created, each one with a single browser (New Moon = Pale Moon XP / Nightly = Basilisk XP /  KM-Goanna) as subject; a moderator could hopefully transfer older posts to the correct new respective thread...

Thanks a million for all that you do for older (but not necessarily inferior) Windows OSes !

Edited by VistaLover
Link to comment
Share on other sites

apreese16 ... I think I now understand why the different browser look. I thought you were talking about New Moon but you were posting about the basilisk/moebius XP browser, I guess. I tried that browser in early December and I did not like it ... I didn't like the look also.

I have been using New Moon 32bit https://o.rthost.cf/palemoon/palemoon-27.7.0a2.win32-git-20180106-d74da289f-xpmod.7z as each update is released by roytam1.

Dencorso is right ... wait for roytam1 to maybe be of help to you. You might try the K-Meleon version by roytam1 ... you can really make it the way you want it to be. Great bunch of people over there and they are excited that roytam1 paid a visit there and offered to help with a newer version of KM. You will see names of siria, Yogi, guenter, rodocop, hermes, JamesD and many more.

They created a special area for roytam1 and it has 'expanded' in a very short time ... it can be hard to find so here is the link.

Unofficial versions development :  K-Meleon Forum


K-Meleon on Goanna :  K-Meleon Forum


Here is another nice link ... siria has put a short history of roytam1 showing up ... it was posted 04 Dec 2017 ... siria is the 'organizer' at KM ... she keeps it all together.

K-Meleon on Goanna (Link collection)



Posted by: siria

Date: December 04, 2017 12:56AM

short summary (if I got it right):
Fellow Gecko-engine browser Palemoon has stopped support for XP.
Meanwhile it also uses a special own engine "Goanna", that they forked from gecko.

In the MSFN forum independant developer roytam1 works on a variation of Palemoon for XP: "New Moon" and other builds:
==> http://www.msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-for-xp/?page=17

Callahan introduced it to KM here: 'New Moon' Browser - Another Option
and kept us updated with crosspostings from the MSFN-forum.

That thread grew longer and longer, one day roytam1 showed up here too, and a few days ago he made a test build of KM76 with Goanna engine inside (G-Meleon?)
The discussion is going on in both forums now, over at MSFN and here at KM too.

Our 4-page-thread here was now split in the middle:
First half (in Offtopic forum): http://kmeleonbrowser.org/forum/read.php?12,142494
Second half (moved into Dev. forum): http://kmeleonbrowser.org/forum/read.php?19,143253

There's also a brandnew subforum for Goanna-threads:

Some other Palemoon-Goanna-related postings partly here:
http://kmeleonbrowser.org/forum/read.php?1,141148 (Palemoon dropped XP)
http://kmeleonbrowser.org/forum/read.php?2,143067,143094#msg-143094 (XP-support)
http://kmeleonbrowser.org/forum/read.php?8,138447,143300#msg-143300 (Resource://)
http://kmeleonbrowser.org/forum/read.php?9,142878,143309#msg-143309 (Version ID probs)

Edited 2 time(s). Last edit at 12/04/2017 05:58AM by siria.


Edited by monroe
Link to comment
Share on other sites



Thanks a lot for your help. I modified the file security.dtd in langpack-de@palemoon.org.xpi and problem was solved. New german translation file 27.7.0_RC6 is working perfectly too. Thanks and best regards

Link to comment
Share on other sites

AstroSkipper ... if you're inclined to also try KM-Goanna, they are working on improving the 'language packs' as I post this.

German, Italian ... are what I remember reading the latest posts about. Guenter and siria are in Germany but not 100% sure, but I think they are. I just don't know for sure where everyone is located ... rodocop is from Russia ... pretty sure about that.

Anyway, under 'Customize K-Meleon' you will see 'Localization' ...





... just posted by siria at KM, latest updated language packs:

TRANSLATION / LOCALES: last updated packages


Posted by: siria

Date: January 11, 2018 05:44PM

A little link-list to the NEWEST language packs, as long as the official threads aren't stickies and have no last-upDATE in titles yet. Or last updates are hidden in the middle of some other thread.
So that roytam needs not search through the heap and overlooks updated packages anymore.

ES (2018-01-11+) http://kmeleonbrowser.org/forum/read.php?20,144672

RU (2018-01-10) http://kmeleonbrowser.org/forum/read.php?20,144981,145012#msg-145012

IT (2018-01-10) http://kmeleonbrowser.org/forum/read.php?20,143686

FR (2018-01-06, in work) http://kmeleonbrowser.org/forum/read.php?20,144855 (guenter?)

CN (2018-01-06) http://kmeleonbrowser.org/forum/read.php?20,144709

DE (2018-01-05) http://kmeleonbrowser.org/forum/read.php?20,144525


... if you try KM with the Klassic skin you can change the 'throbber' in the Klassic skin folder to a nice lighthouse throbber ... for something different. The light looks great going around. It was made with this Maine Lighthouse in mind by disrupted.

Cape Neddick Lighthouse  (download is fourth post down)


K-Meleon Lighthouse Throbber



Edited by monroe
Link to comment
Share on other sites

basilisk/moebius new build for XP!

Test binary:
Win32 http://o.rthost.cf/gpc/files1.rt/basilisk-55.0.0a1.win32-git-20180113-0257d770e-xpmod.7z
Win64 http://o.rthost.cf/gpc/files1.rt/basilisk-55.0.0a1.win64-git-20180113-0257d770e-xpmod.7z

diff: http://o.rthost.cf/gpc/files1.rt/moebius_restoreXP_20171113.7z

source patch of ffvpx H264/HEVC/AAC/MP3 Addition: http://o.rthost.cf/gpc/files1.rt/moebius-ffvpx-h264-aac-hevc-mp3-addition.7z

Official repo changes since my last build:
- Remove warning for "unsigned" extensions. (25384fde4)
- Merge branch 'master' into b2g-cleanup (c079d0c2c)
- Issue #8 - Remove b2g - Part 3: Freshen up the branch (3eac4125a)
- Merge pull request #278 from binoc-central/b2g-cleanup (e76242083)
- Disable shared JS memory. (c2650cbe2)
- Split border and caret width rounding. (da1aa7c26)
- Merge branch 'master' of https://github.com/MoonchildProductions/moebius (89f725fc7)
- Revert "WebExtensions - adding ID from an sign, if it isn't in manifest.json" (e71b6d68c)
- Revert "Remove warning for "unsigned" extensions." (7ca5a9b10)
- Get IDs for ID-less WebExtensions when verification against Mozilla's hard-coded CA is disabled (5d1a090c2)
- Issue #280 - Undeprecate viewSource.xul's original/legacy API (85901f8cf)
- Merge pull request #281 from binoc-central/viewsource-work (137651aa3)
- Merge pull request #279 from JustOff/PR_id_less_we (49ffbebc6)
- Remove warning for "unsigned" extensions. (d885a5fe7)
- Issue #19 - Do not use generic directory names for platform applications - Part 1: Move browser/ to application/basilisk (68bcc9ca8)
- Move --disable-fmp4 to old-configure. (dddc75855)
- Move --disable-ffmpeg to old-configure. (38307200e)
- Move --disable-wmf to old-configure. (965f95708)
- Move MOZ_APPLEMEDIA to old-configure. (b8e1910fa)
- Issue #19 - Do not use generic directory names for platform applications - Part 2: Fix hardcoded test paths (8ce9de257)
- Issue #19 - Do not use generic directory names for platform applications - Part 3: moz.configure, old-configure, and client.mk (9a3db85d5)
- Issue #19 - Do not use generic directory names for platform applications - Part 4: Use MOZ_PHOENIX as the conditional instead of MOZ_BUILD_APP = 'browser' (8ec985ddf)
- Issue #19 - Do not use generic directory names for platform applications - Part 5: Make Basilisk build again (a04ac47e2)
- Issue #283 - Remove all tests from Basilisk - Part 1: The Tests (0dafff58b)
- Issue #283 - Remove all tests from Basilisk - Part 2: moz.build Files (694e38e7c)
- Issue #283 - Remove all tests from Basilisk - Part 3: Remove devtools references to Basilisk tests (12f054de9)
- Issue #284 - Remove some unused extensions/components from Basilisk - Part 1: Everything except pdf.js from application/basilisk/extensions (8f50bec05)
- Issue #284 - Remove some unused extensions/components from Basilisk - Part 2: Remove nightly/aurora branding (3579be37a)
- Issue #284 - Remove some unused extensions/components from Basilisk - Part 3: docs directory (4aeb2883c)
- Issue #284 - Remove some unused extensions/components from Basilisk - Part 4: tools directory (317a7b872)
- Merge pull request #285 from binoc-central/app-work (ad9c76d02)
- Merge pull request #286 from binoc-central/tests-work (1e3c67f62)
- Merge pull request #287 from binoc-central/cc-basilisk-work (b99c66dc7)
- Restore source-editor commands controller for scratchpad & styleeditor menus (d634844e4)
- Flatten Basilisk Preferences - Part 1: Rename and Move (ef364db9d)
- Flatten Basilisk Preferences - Part 2: Fix Chrome URIs (afdc95771)
- Flatten Basilisk Preferences - Part 3: Build System, Jar Manifests, and Cleanup (5e514ea4f)
- Merge pull request #292 from binoc-central/pref-work (75358949b)
- Merge pull request #290 from janekptacijarabaci/devtools_scratchpad_styleEditor_menu_1 (ff782891b)
- Move --enable-replace-malloc out of pyconfigure. (75c7cbf56)
- Move MOZ_MEMORY_* defines out of pyconfigure. (951263d5b)
- Move --enable-jemalloc and MOZ_JEMALLOC4 out of pyconfigure. (31b8283d1)
- Correct line endings (57e405b0a)
- Remove independent rust tests (0257d770e)

Edited by roytam1
  • Like 1
Link to comment
Share on other sites

Notice: no new pale moon build today, since upstream changes is limited:
- Update HSTS preload list (0c7367ffa)
- Merge pull request #1572 from trav90/HSTS-preload-update (baf75ff58)
- Split border and caret width rounding. (c3b23d899)

  • Like 1
Link to comment
Share on other sites

This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Create New...