Avatar

leopold

leopold@lemmy.kde.social
Joined
44 posts • 239 comments
Direct message

These are known as the short scale and long scale systems respectively. Though the United States was indeed the first English-speaking country to switch to short scale, pretty much all English-speaking countries have used short scale almost exclusively for a long time, including the United Kingdom. Saying that it’s simply being influenced is an understatement. From Wikipedia:

British usage: Billion has meant 109 in most sectors of official published writing for many years now. The UK government, the BBC, and most other broadcast or published mass media, have used the short scale in all contexts since the mid-1970s.[12][13][43][15]

Before the widespread use of billion for 109, UK usage generally referred to thousand million rather than milliard.[16] The long scale term milliard, for 109, is obsolete in British English, though its derivative, yard, is still used as slang in the London money, foreign exchange, and bond markets.

I’ve never actually seen the word milliard used in English outside of discussions about the long and short scale systems. However, many other languages do mainly or exclusively use long scale. For instance, my native language French.

permalink
report
parent
reply

I’m pretty sure the video is just badly misnamed. PackageKit is an abstraction layer for interacting with native packages in a cross-distro manner. It’s used by both Discover and Software Center. It is developed by Red Hat, but not as a part of GNOME.

permalink
report
parent
reply

Because of widespread fearmongering, itself caused by the filesystem taking too long to become stable and garnering a bad reputation as a result which it has never shaken off.

permalink
report
parent
reply

having support for the newer wayland protocols in the wayland session wouldn’t hurt

permalink
report
parent
reply

it’s definitely progressed a lot since 2008, but the last couple of years have been extremely slow

permalink
report
parent
reply

No third party icon theme that I’m aware of makes of use of accent colors.

permalink
report
reply

FDO stands for FreeDesktop.Org, the committee responsible for various desktop Linux standards including icon themes. So FDO icons just refers to your system icon theme, which LibreOffice doesn’t use.

permalink
report
parent
reply

LibreOffice uses its own widget toolkit. It works similarly to wxWidgets, basically just maps to whatever toolkit is native on the current platform. It uses Win32 on Windows, Cocoa on macOS, Qt on KDE, GTK on GNOME and a few others.

That said, their current approach to dark themes is pretty bad. It can very easily conflict with the dark theme from the host toolkit and cause issues if misconfigured, which has caused a lot of people to think it just doesn’t work. It does work, but it can be confusing as hell to configure correctly.

For instance, LibreOffice has a setting you can use to change the application colors. It barely works and you should never touch it. Just let it get the colors from your toolkit.

There’s also the fact that LibreOffice doesn’t use FDO icons and has its own icon setting which doesn’t automatically follow dark/light theme. If you’re using a dark theme, you have to manually switch the icon set to one that isn’t impossible to see on a dark background.

Oh and if you want your documents to use a dark palette that’s also a separate setting. Like I said, confusing.

permalink
report
parent
reply

Okular has JavaScript support. I think some things don’t work, but it’s worth a try.

Also, Adobe Reader had a native Linux version, so I wonder why the Snap is using Wine.

permalink
report
reply

It used to be open source, but large parts of it have been relicensed under their proprietary source-available shared source license. The reason why it isn’t entirely proprietary is that it’s based on Firefox, which is entirely licensed under the MPL. The weak copyleft of the MPL states that all parts lifted from Firefox must remain open source, but the new parts can be proprietary.

Source-available licenses are a type of proprietary license where the code is made public for people to look at, but you’re not actually allowed to use it. Users can still contribute upstream, so they’re usually parasitic licenses aimed at getting free labour out of the userbase without actually giving back any code to the commons, all while keeping up the illusion of being open source. It sucks.

permalink
report
reply