No AI DuckDuckGo works properly for me in v35·0·0 on Debian 10. This problem is _not_ specific to bugs corrected in v35·0·1, _although I should upgrade my browser overmorrow in any case._ * * *

This is an update to the v35 milestone to address some pertinent bugs and security issues. More information in the release notes. * * *

Welcome to Boucherie, a modern restaurant theme and the epitome of Michelin Star’s taste. It…

> For me, this is a sensitive subject which arouses strong passions. That's fine. I hope your passions leave room for the logic behind this change, though. In my opinion, clinging to specific historical use at the cost of the one thing language is supposed to be for: conveying meaning, is a disservice to the language in question. But we can agree to disagree on that also * * *

> Added more updates for LoongArch64 (including full JIT) > https://www.palemoon.org/releasenotes.shtml Basilisk has JIT disabled for the aarch64/ARM64 architecture, and it's apparently because UXP it doesn't work well with the architecture. (https://forum.palemoon.org/viewtopic.ph ... 42#p275779) But the new v35 PM release has full JIT support for the lesser used/known LoongArch64 architecture. This kind of intrigued me, I thought arm64 would be an easier platform for development. * * *

**I have reinstalled FoxReplace** (in the Classic Add-ons Archive, for anyone else interested), which I have now configured correctly to replace, according to my own values and beliefs about orthography, capital sharp S wherever it occurs. In essence, this imposes the original, on-the-fly conversion everywhere. (Since I reject capital sharp S except in narrowly defined, stylistic cases, I see this as no great loss.) Extensions exist for reasons like this: so the browser can meet individual needs and preferences. I kindly request this thread be locked without further comment- Too much said about this could only breed ill feeling. Sorry, but in my book, ‘MAẞE’ is wrong, and ‘MASSE’ is correct for both. For me, this is a sensitive subject which arouses strong passions. I do not want to debate it with you. We should agree to disagree about spelling. Even to illustrate it by putting your example sentence in all caps, I would end up shouting at you, which I doubt either of us wants. * * *

It's not configurable behaviour (it never was) and since this isn't just stylistic choice or preference[1], and it would be in a hot path where checking a pref would considerably impact performance, I'm really not inclined to consider making this configurable. Sorry to disappoint. [1] It's objectively an issue; it's not just a matter of ligature vs. not being a style choice. Consider, e.g. "masse" vs. "maße". Two entirely different words/meanings. Capitalizing that with your preference would make both turn into "MASSE". Our current behaviour correctly capitalizes to "MASSE" and "MAẞE" respectively. "Ich maß die Masse und hatte dann die Maße der Masse." will become total nonsense if ẞ->SS is maintained. * * *

In the release notes, I could read this: > Primarily in German, the ß character (known as "eszett" or "scharfes S") can be written with its proper character or with the alternative latinized "ss". Because the uppercase version of ß was not commonly included in system fonts for a while, with historical typewriter conventions in mind, converting text to uppercase would convert ß to "SS". However, this can cause ambiguity in some wordswhere both a spelling with ß and with "ss" exist which have different meaning. Since the uppercase unicode character has been included in system fonts for a long time now and is more commonly also included in custom fonts, this conversion is an old notion. The linguistic bodies in Germany also prefer using the uppercase ẞ now when capitalizing, so Pale Moon will use the unicode character by default going forward when converting case (e.g. with CSS or JavaScript), abandoning the on-the-fly conversion to "SS". In German, I prefer the old orthography; the linguistic bodies’ current opinion does not matter for me. I favour the old notion: sharp S is a ligature of _ſ_ (long S) and _s_ or _z_ , so when it is capitalised, the long and lowercase S should logically become capital. Thus, if I am drawing a map, _Rußland_ becomes _RUSSLAND_. How can I restore the old behaviour? * * *

v35 builds are ready. * * *

Für die Durchführung geplanter Aktualisierungen müssen die Hostsysteme der vServer-G1 (vmanagerXXXXX) neu gestartet werden. Die Neustarts erfolgen nacheinander, wobei pro Hostsystem mit einer Ausfallzeit von ca. 30 bis 45 Minuten zu rechnen ist. In diesem Zeitraum wird es bei den betroffenen virtuellen Servern zu einer Nichterreichbarkeit kommen.  Betroffen sind folgende Hostsysteme: [list][*]v24[/*][*]v26[/*][*]v28[/*][*]v35[/*][*]v38[/*][*]v39[/*][*]v40[/*][*]v45[/*][*]v49[/*][*]v51[/*][/list]Sobald die Wartungsarbeiten abgeschlossen sind, informieren wir an dieser Stelle.

時代の流れか運命のいたずらか……「もし××だったらもっと人気が出たのに」というクルマは少なからず存在する。2001年に登場した11代目日産 スカイラインもそんな悲劇の一台。「スカイライン」ではなかったら評価されていた!?

Welcome to Boucherie, a modern restaurant theme and the epitome of Michelin Star’s taste. It…