NotHereToPlayGames

No other language packs are compatible. Too much stuff is moved around. The only way to do this is to do it MANUALLY, one file at a time! You cannot "cross-breed" language packs across different browsers even though they are both "v69"!

The Google Translate, for the rest of us to follow along -- Yes, they don't match. I have already translated a "small" part. I now have the most important things in German. When I have time, I will continue to translate it.

Chrome PAK Customizer -- I use v2.0, grab the chrome-pak.7z from here -- https://github.com/myfreeer/chrome-pak-customizer/releases

I always preferred 4.17.4808 but tested (and disliked) 5.61.7392 because Win10 was complaining about "compatibility". Turns out, all you have to do is RENAME the .exe and an "incompatible" 4.17.4808 is now miraculously "compatible".

Mrs. Pac-Man on a C64 emulator.

Thanks!

I would like for you to read this back EVERY TIME you feel like "derailing" threads with jibber jabber about French or Russian or "commie" side bars. Then you will see where I'm coming from, we are IDENTICAL in that regard.

Too funny. You don't like the "competition"? I'm just messin'. There's really only 15 to 25 active members here at MSFN. HALF of which, like you and me BOTH, have our "bored" days and derail without realizing it until a day or two later, "Oops, why did I post that?" And no, "predicting" your reply, I'm not planning on hunting them down. Something about never arguing with folks that LIKE to argue. We BOTH have our days. No worries though (this is no longer my "home", but still enjoy the "company" when I do drop by). It's like that EVERYWHERE. Whether we care to admit to it or not

Works for me! Did you try in an incognito window or a fresh/clean profile? This should ALWAYS be the FIRST step. You'd be AMAZED at how many people will always return a day or two later, "Oops, it was one of my extensions."

I have a "official" Pale Moon + Stylem version floating around somewhere in my archives where my Stylem style sheet reconfigured the address bar to not display the "padlock" AT ALL!

Agreed. For nostalgia, I was reading my own posts regarding "ssl padlock" and "secure DNS" and "certificate errors" over at the Proxomitron Forum and I find it hillarious that everything the Proxo community was saying way back in 2009 is still true to this day. Web browser "ssl" has been a FLAWED technology since its inception!

I wish there was a way to place three DOZEN upvotes! The BEST thing that Chrome ever did, in my opinion, was the --ignore-certificate-errors startup flag!

Use the --ignore-certificate-errors Chromium startup flag.

That's different! You and I are both on XP. Which is / was the "targeted audience" (ie, as if my skin didn't tell the end-user that, lol).

That's what VMs are for. I use Portable VirtualBox v4.3.28.

The "simple text" snideness is unwelcomed. I do not follow your feed! Never have! I answer questions in this thread (it's MY thread, afterall). Much more important things in life then remembering each and every discussion herein. Much more important. Don't know what to tell you. You really should consider diving in and creating it yourself. It's not that difficult. And I would be much more inclined to answer questions as to "how" as opposed to being some kind of dog chasing its own tail. I did not undertake this project to release constant build after build after build each and every time "upstream" makes a minor change that language barrier prevents us from knowing the "exacts" of such a minor change.

It's the OPPOSITE for me. To Google, I am but a needle in a haystack the size of China. To Mozilla, I am but a needle in a haystack the size of Cleveland.

You seem to be the ONLY person wanting an "update" and I kind of feel like you've been pushing it for a VERY long time. Several posts by you to report upstream updates. I think the bigger question is "why" ? The only thing that "upstream" really does is add junk that we remove anyway.

Doesn't work "upstream" either. Nothing I can do to fix what is also broken "upstream".

Agreed! They don't make things like they used to, as the saying goes. My $160 cheapie 50" Onn non-smart LED 4K TV died at only three years old. I just replaced it with a $145 cheapie 55" LG non-smart LED 4K TV. I know that higher quality TVs cost more and last longer ("you get what you pay for"), but when you divide out the lifespan by the dollars spent, I will always take the cheapie. But even being a cheapie, this new 55" LG non-smart has a "Reduce Blue Light" option. When enabled everything looks like crap, everything turns a bit orangeish or greenish depening on the color it is SUPPOSED TO BE and skin tone might as well be some alien sci-fi movie from the 60s!

It doesn't, that I am aware of. But I do know this, I've only been using Chromium-based (and it's at the point where I have ZERO plans to ever return to Mozilla-based) for close to two years. And pretty much EVERYTHING that I have ever searched for in regards to Chromium-based issues along the way, right there in the TOP THREE replies is ALWAYS "disable hardware acceleration". And that "suggestion" never seems to rely on OS. It's akin to when you contact tech support for software and the FIRST thing they ALWAYS tell you is "disable your antivirus".

Which of these settings are checked versus unchecked? And please tell me you have NOT NOT NOT enabled "Use hardware acceleration? This should *NEVER* have *EVER* been a Chrome/Chromium option as far as I'm concerned!

I do not get that popup in my skin either. You may have a corrupted profile. Make certain that there are no registry entries when 360Chrome is not running.

I wouldn't really call it a "speed-up" option. If I understand it, it PRELOADS content based on links in your CURRENT page. So your downloaded bytes go through the roof and you maybe never went away from page one so why enable the browser to load content for page two? Page two loads faster because it loads portions of it before you clicked away from page one.

I will decide how I spend my free time. The core engine has never been updated since early beta versions of v13. Please stop trying to coerce me into creating yet another version. All the info, tools required, and detailed instructions on "how" Humming Owl and I have created these have been provided over the years. Feel free.