Just as it helps our politicians to know when we want change, we can tell Kodak just how much we want Kodachrome back in production. Share this article with your friends. Tell them to call and email and write to and about Kodak. Tell them how much we want Kodachrome back, how much it would be in Kodak's best interest, how much we do love it, and the responsibility that they have to deliver on that love. After all, Kodachrome: sounds an awful lot like something only Kodak could bring to the market.
Ooof, cannot unsee. It burns my eyes like a beaker of acid.
How did this even happen? It's not the font — that's legitimately a Unicode Eszett. The journalist must have gone out of their way to pick an Eszett instead of a beta.
I can't figure it out either — it should work, judging by the code in that file. Ah well, I thought I'd give you a heads-up in case anyone else runs into the same issue.
I couldn't find anything in the code pointing to the old location in "library", so I was a little mystified why the code was looking there. Hard-coding the new location in LanguageDetect.php was a brute workaround, but it did the trick.
lang.dat exists at vendor/pear/text_languagedetect/data/lang.dat, which I think means Composer ran successfully. After hard-coding that location in LanguageDetect.php everything seems to work fine.
Excited for the upgrade! I ran into a little problem with the latest version, though. I updated from 3.5.4 to 3.6 using the steps in the blog post. My Friendica instance loaded in the browser, but I was unable to save a post or get new posts from the network. The error in the nginx log was:
PHP message: PHP Fatal error: Uncaught exception 'Text_LanguageDetect_Exception' with message 'Language database does not exist: /var/www/friendica/library/langdet/Text/../data/lang.dat' in /var/www/friendica/vendor/pear/text_languagedetect/Text/LanguageDetect.php:225
I was able to work around the problem by hard-coding the absolute location of lang.dat in LanguageDetect.php line 74. Let me know if there's any other info you need.
St John's Evil Twin (stjohn@mulligrubs.me)'s status on Wednesday, 21-Feb-2018 08:58:00 EST
St John's Evil TwinFrom time to time I get hit by a wave of "I hate technology. I hate everything. I don't want to live on this planet any more." When that happens I remove one thing from my blog — one bit of unnecessary bloat that my blog doesn't actually *need*. Over the years these have included: - jQuery - embedded Twitter feed - dynamically loaded sharing buttons - web fonts - comments
On the weekend I took a hacksaw to it again and finally removed Font Awesome and got rid of the static sharing buttons because I refuse to endorse BookFace or Birdsite (even indirectly). That means it's now just a static website that consists of HTML and one CSS file. There's no JavaScript or fonts to download, and only a couple of images (not counting those used in specific posts). I considered experimenting with a more minimalist layout, but paradoxically that would often involve adding web fonts and JavaScript back in the mix so I think it's happy as it is for the time being. https://www.stjo.hn/