Linkify Addressbar Segments in Vivaldi
Great news! My suggestion for segmented addressbars from Opera 11 Addressbar Revisited has been picked up by Vivaldi. Presumably independently, but this is the kind of development I like to see.
Great news! My suggestion for segmented addressbars from Opera 11 Addressbar Revisited has been picked up by Vivaldi. Presumably independently, but this is the kind of development I like to see.
As one of the maintainers of KOReader, a versatile a document and image viewer, I’m proud to announce the latest release.
It’s been a busy month, so I’ll get right to some of the highlights.
Ruby characters (also known as furigani) are now supported in the form of the <ruby>
element, small typographic annotations to aid pronunciation (#6305).
Usually I tend to emphasize user-visible changes, and in a way this one’s both. Rotation was refactored (#6309), which immediately and easily allowed for better Android TV support (#6327).
The following screenshots showcase the new rotation handling on Chrome OS (running Android apps) and Android TV:
The calibre metadata search and calibre wireless connections were merged into a single plugin (#6177).
search metadata changes:
calibre wireless connection changes:
A big thank you to all of our translators. This month a good chunk of KOReader was localized in Hebrew. Please head over to https://hosted.weblate.org/engage/koreader/ if you want to help.
We’d like to thank all contributors for their efforts. Some highlights since the previous release include:
This month we’ve seen quite a number of small improvements in various areas, such as support for book-specific style tweaks (#6244), support for ::before/after (#6236), an offline add link to Wallabag queue (#6170), as well as some Android fixes. Enjoy!
We’d like to thank all contributors for their efforts. Some highlights since the previous release include:
After updating to the latest Firefox ESR 68.8, for some reason my Firefox stopped autofilling the addressbar.
Our first stop lies in Help → Troubleshooting information → Places Database (which will take you to about:support).
Click verify integrity, it will probably detect an issue, and then it claims it will replace it on the next startup.
> Task: checkIntegrity
– Unable to fix corruption, places.sqlite will be replaced on next startup
But oddly enough, nothing of the sort happened! Not to worry, right at the top there’s the profile directory
, which indicates where the places.sqlite
file can be found. Rename it to something like .bck
or .old
, or just outright delete it if you don’t care, and success! Everything will be working again.
> Task: checkIntegrity
+ The places.sqlite database is sane
+ The favicons.sqlite database is sane
Unfortunately you’ll have to repopulate the autofill if you take this approach.
But I didn’t want to admit defeat. Surely it can’t be too hard to salvage our old database. As an aside, but not strictly relevant to what I did here, I think it’s always useful to have sqlitebrowser installed. That way you can browse the data and run SQL commands on it. For example, if you open places.sqlite
and run PRAGMA integrity_check
on it… Oh dear, it says the same thing as Firefox: database disk image is malformed
.
But we have a trick up our sleeve: command line SQLite. My initial plan was to play around with export and import to determine where the error was located since SQLite didn’t want to say, but that seemed a bit tedious. Essentially to try it table by table, and once I’d identified the table, basically to keep cutting it in half. But as luck would have it, SQLite 2.29 and higher has a built-in error correction feature. Docs here.
sqlite3 places.sqlite ".recover" | sqlite3 places_fixed.sqlite
Error: near line 378367: NOT NULL constraint failed: moz_origins.host
All that was left was to give it a try and all was well with the world again — or at least with Firefox. The SQLite error recovery command found the error and fixed it up all by itself. So now I still have all of my location history. Useful? Maybe not in this particular case, but good to know if anything like this should happen in the future on some more important data.
Good news for Kobo users! There’s a new launcher for apps and scripts called NickelMenu, and it’s supported starting with this version of KOReader.
We’d like to thank all contributors for their efforts. Some highlights since the previous release include:
As one of the maintainers of KOReader, a versatile a document and image viewer, I’m proud to announce the latest release.
By staying inside and reading, humans have become resistant.
We’d like to thank all contributors for their efforts. Some highlights since the previous release include:
Let’s face it, all of KDE’s task switchers other than Compact are awful in varying degrees. Unfortunately I found it to be missing. Luckily the solution is simple on Debian/Ubuntu.
sudo apt-get install kwin-addons
And there you have it. Happy window switching!
As one of the maintainers of KOReader, a versatile a document and image viewer, I’m proud to announce the latest release.
There’s this upcoming videogame called Skatebird. The demo was quite promising. But what you didn’t know is that many of those birbs read heaps and gobs of classic literature from Project Gutenberg and Archive.org. Just like us!
Quite a bit of effort was put into PocketBook this month to make it more maintainable going forward. By creating our own toolchain (koreader/koxtoolchain#22), we can now build the binaries with an up-to-date GCC instead of the years-old GCC 4.8 in the official toolchain, which was starting to become problematically outdated. This is no panacea; most PocketBook issues are unrelated, but a higher maintenance burden can be quite demotivating and gets in the way of addressing actual issues.
In-page footnotes are now enabled by default (#5908). We’re quite fond of them, but if you’d like to disable them you can do so in the document menu (second from the left in the top menu) → Style tweaks → Miscellaneous → In-page footnotes.
We’d like to thank all contributors for their efforts. Some highlights since the previous release include:
Shamelessly lifted from Norbert Preining in case I forget. I still haven’t actually continued Broken Sword 5 past the first few rooms, just like a few years ago.
Create a file named ~/.alsoftrc
with this in it.
[pulse]
allow-moves=true
As one of the maintainers of KOReader, a versatile a document and image viewer, I’m proud to announce the latest release.
Thanks to @tcrs the program has now been ported to the Remarkable (#5828).
Additionally, OTA update reliability should be better from now on, by switching to zsync2 with a few custom patches (#5810). The update from 2019.12 to 2020.01 managed to sometimes trigger an edge condition where the OTA update would just keep looping without ever finishing. Furthermore, the download progress will now be printed directly to the screen on supported devices, so you’ll always know exactly what’s happening.
By switching to the connectivity manager on Android, we should stop falsely triggering an unconnected message in some edge cases such as Ethernet, which you typically don’t see on the platform (#5801).
And as a final little unexpected gift, @poire-z implemented a calendar view for the reading statistics, so you can easily see what you were reading when (#5854).
We’d like to thank all contributors for their efforts. Some highlights since the previous release include: