It's things like page layout, margins, bleeds, printer profiles, support for printer features... Adding proper printing support could easily take six months, even if Qt already supports the basics. And then it still wouldn't be on Scribus' level.
I actually like the feel of my M1 pro keyboard better than my 1015 15" macbook pro's keyboard. But... That weird lcd strip constantly flickering in the periphery of my vision makes me want to throw the laptop out of the window. Good thing it isn't my main working machine, just a device to make fat binaries of Krita on.
It's not going to replace the enormous investment Nokia made into the free software/linux community... So it won't help the graphs the original article showed. But by another measure, it's already a success since it exists.
Yes, it does, because Nokia had its fingers in both bowls of porridge, to the extent where people like Michael Meeks were fighting really hard to keep a small library like kcalendar out of Maemo.
Nokia started with GTK and when they went to Qt, they never stopped their involvement with GTK/GNOME -- they seemed to have expected the idiots in both camps to just work together for the good of free software, and like the idiots we were, we didn't.
Good grief, the painful conversations we had after the Dublin MeeGo conf ended, between people from both camps...
I was there; I wrote code; I had employees, I went to the various conferences and trade shows. My company provided one of the default apps on the N9...
I worked there -- as an outside consultant -- quite a few times. It was a pretty ordinary, meh, office building. What I remember most vividly was sitting there in the office with two Nokia people, one quite senior, when the N8 was released, and seeing them watching the release video with lots of excitement -- until they realized the darn thing was running _symbian_. Everyone in the Maemo group thought it was (going to be) running Maemo -- every single engineer!
I had a wonderful time, but what a broken company...
All this wibbling about GNOME 3 and so on -- it's just not relevant to the data in the original article. The same thing happened to KDE at the time.
The reason is simple: Nokia. Nokia (and to a much lesser extent, Intel) built up a lot for Maemo and Meego. Just for KOffice/Calligra, at least twenty people were paid to work on the documents application. For all of Maemo/Meego, the total number of people Nokia funded was enormous.
And then Elop, and the burning platform, and Windows, and well, that was 2012.
By 2014, my company was dead, amongst others, and, yeah, the peak had peaked, and the big chance for free software had gone.
It doesn't mean a translation: it means the original text, its variants with commentary. Basically, it's what you'd use to make a new translation. Or to read for pleasure, if you can read ancient Greek -- which I can't, I never got beyond the Anabasis.
The thing is, of course, that you don't need to trust the Qt Company. That's why we have the KDE-Free Qt foundation, and that alone makes Qt the best choice for anyone who developers software that can use LGPL libraries, commercial or open source.
Weird, last time I noticed Qt being discussed on HN, I got a really useful and technical comment which is still something I'm basing my future plans on.
Even Autodesk, which uses Qt for pretty much all its products, including Maya, doesn't pay a cent for Qt. Same with The Foundry. As soon as Nokia made LGPL licensed python bindings for Qt, they dropped PyQt, stopped paying or contributing, and just went on freeloading.
As a player you cannot do _anything whatsoever_ to change the setting and rules of the game: you cannot be nicer or less nice to the indigenous people, you have to loot and destroy their religious centers, you have endure having their religion mocked by your compatriots, you cannot convert to the local religion...
You have to play a Aryan colonial invader who disdains the local culture and religion because your own culture is so much superior, and you have to do that wearing the historically inaccurate trappings of of what people a century ago imagined vikings looked like -- trappings that have been appropriated by neo-nazis.
There's no agency at all for players in this regard.
We took the text, and translated it into Latin, so there was a Latin version of WordPerfect for use in the Vatican. Only the user interface, not the dictionaries or things like that. After all, a cardinal is supposed not to need dictionaries to write proper Latin.
You might need to work on your reading comprehension. Particularly when it comes to sarcasm, or irony. I did quote my teacher verbatim, and he wasn't using neither irony nor sarcasm when calling this tour de force "easy". But I was...
The Tibetan script isn't difficult at all. You just need to learn the sound changes for the past five, six hundred years and apply them to logically arrive at "tro" for something written "bsgribs" -- but it's all very logical and clear. As my teachers made clear at university, using the Grundriss der Klassischen Tibetischen Schriftsprache and books of a similar age.
Reveal codes was a crutch. There was nothing great about it, no matter how much it's wrapped in a nostalgic haze now. It's basically telling people "we cannot make this wordprocessor work reliably, please code up your text yourself once things go wrong".
And yes, I've used WordPerfect from 4.0 to 7.something on Dos, Windows, various unices and Linux.