NotHereToPlayGames

Agreed. Small "patch" .exe's (7z executables with self-contained portable HxD coupled with AutoIt) would be fairly easy but then all of the anti-virus folks would crawl out of the woodwork and cast aspersions.

I'm assuming those are HOSTS file entries?

Are you still running XP x86 SP2?

Instructions on how to convert the "ungoogled" to "regular" and how to restore "Translate to Engish" provided in 2nd and 3rd posts. Please note that going forward, I intend to maintain ONLY the "ungoogled". Instructions will be provided on how to "convert" the "ungoogled" for different 'flavors' but I will not be "maintaining" anything outside of "ungoogled". MSFN Members are free to assist/host/share any files they wish to assist other 360Chrome users.

The font-thing is one of those things that constantly keeps coming around. Chrome/Chromium/forks do fonts WAY different than Mozilla/Firefox/forks. Took some getting used to when I finally abandoned Mozilla/Firefox/forks.

Not as easy, but I used this before setting up Proxomitron to perform all of my font-based tasks. https://greasyfork.org/en/scripts/419363-%E5%85%A8%E5%B1%80%E5%BE%AE%E8%BD%AF%E9%9B%85%E9%BB%91

There are 42 "gstatic" entries and I did not have to restore any of them to restore "Translate to English". I personally prefer the "err on the side of caution" approach and would keep all 42 "gstatic" and all 47 "googleapis" entries disabled. We can always isolate and "selectively restore" if some unknown feature that nobody has found in close to two years is somehow suddenly found.

Confirmed. Only two of the 49 "googleapis" entries need restored in order to restore the "Translate to English" feature. Therefore, you do not need to restore Google's email service, update service, userinfo profile tracker, firebase messaging, firebase user topics, tachyon tracker, Google account manager, geolocation, Google password service, Chrome upboarding, Google nearby sharing, Google pixel langs server, Google client services, Google data saver, Google content suggestions, Google optimization guide tracker, Chrome wallet, Google fcm notifications tracker, Big Cache beacon, networktraversal, Google Alumni, Chrome Reporting, among others. You also do not need to enable the Chrome Web Store portion of the "ungoogling" (ie, the persistent Google cookie that never deletes and spans all browsing sessions).

Follow-up: "Translate to English" is intentionally broken when 49 "googleapis" (without the quotes) entries are batch-replaced with 10 dots inside chrome.dll. These "can" be restored by batch-replacing any series of 10 dots with "googleapis". Technically what this also does is replace 11 dots with googleapis followed by 1 dot, replace 12 dots with googleapis followed by 2 dots, et cetera. There appears to only be TWO "googleapis" entries that pertain to "Translate to English". We should be much better off (for those that want this feature) in restoring only these TWO and not the other 47 that do not pertain to this feature. Will need to do some testing, more to follow within the next couple of days or so.

Can you show a screencap of a font that you want changed?

Please show me your "About 360Chrome" popup. If it does NOT look like the below, then your version is not the version being discussed in this thread. edit: copied image to Dropbox host instead of using profile attachment

You're NOT actually using jisu9_chrome.srx as your skin. What steps did you take to NOT have an XP skin with XP min/max/restore icons?

Thanks. I wanted to verify that as the out-of-box jisu9_chrome.srx and it is.

Can you right-click on your jisu9_chrome.srx file, select Properties, and tell me what dates you have for Created, Modified, and Accessed?

ie, we know that Official UNGOOGLED does NOT contain the Translate to English context menu item. But does that context menu item RETURN if TranslateEnabled is set to ONE? My hunch is NO, which puts 360 behaving EXACTLY the way that Official Ungoogled has done things long before 360 showed up.

I wonder if Official UNGOOGLED also respects TranslateEnabled? I shall test later unless you beat me to it

Noted. Thanks.

Official Regular Chrome v86 does contain the "Translate to English" feature. edit: screencap removed from profile attachments

Regarding "Translate to English" - Official Ungoogled Chromium v86 also disables this feature. edit: screencap removed from profile attachments

Do we know if that is skin-related, by chance?

Awesome! I'll post a how-to in one of the <reserved> spaceholders on how folks can convert the "base download" into a "non-ungoogled" and how to restore "Translate to English".

Moving forward...

I think this will require two browser restarts to fully take effect. The 155.json and the googleapis entries in chrome.dll "should" have been the only things required to restore "Translate to English".

Correct. I did try that in the past. If you think of text within a div container within a div menu, I think these context menus are similar. We should be able to remove the div container without effecting the overall div menu. For lack of a better way to explain.

My plans are for a fully ungoogled (including removing "Translate to English" as it requires googleapis not otherwise needed for "web surfing"). But then provide instructions/links to "restore" something like "Translate to English" or non-XP skin or non-ungoogled.