Wow. This brings up some (bad) memories of working with an .epub export about 10 years ago. We had some embedded fonts to work around some poor rendering in some of the readers we tested, but some of the readers ignored the fonts altogether, causing the content to render boxes (bangs head on table)
It looks like not a whole lot has changed in that space -- the readers are still the gate for what you can do with the format. Who's available to make a CanIUse for epub readers, to shame them into compliance? (only partly /s)
There's the States Rights GOP, and then there's the Things Trump Doesn't Like. That executive order about paper straws (https://en.wikipedia.org/wiki/Executive_Order_14208) falls under the latter category.
A few years ago we did a road trip through that part of Texas, looking at the "painted churches" (https://thedaytripper.com/the-painted-churches-road-trip/ - there are other itineraries). This article sparked that memory, as one of the painted churches is actually a Wendish church.
And yes, there's a painted church in Shiner as well! :-)
When I first started in the industry, I worked in the documentation department of a small company. My boss had me write Windows Help files by hand before using tools like WinHelp / HTMLHelp. Years later I did much of the same thing when I dealt with generating .epub files from an editor.
There's something to be said for under-engineering, even if you're using higher-level frameworks. It gives you an idea of what the tools are doing under the hood, where they could possibly go wrong, and how errors can be fixed.
Yeah, I wish they would just keep the boilerplate OFL intact. I spent way too much time trying to figure out what the "real" license was, and if I could use it in my open source projects.
Yup. Which is why this question can give some good insight into how the company runs. Is it chaotic? Suffocatingly rigid? Or is there a pipeline to triage and introduce new features in a sustainable and beneficial way?
They had these out at the local Costco last night. Just a card scanner. Honestly, it wasn't that different from the "wave your card at the person in the front" system they had before -- it didn't slow things down much.
Hybrid app developer here (Apache Cordova). The work that I do is pretty close to web development + some hooks into native code (which is done by plugins) -- so your skills should transfer pretty readily.
The only headache that Donn eludes to that I've experienced had to do with Android's scoped storage. It's taken them a few tries to get it right, and their documentation hasn't really provided good best practices, so I've had to roll with the punches a few times. But I really haven't had to deal too much with Donn's other points.
Looks like they _might_ have been in the study set, but weren't separated out and focused on? At any rate, the author is hoping for the same:
"In the first edition of my book Why Gender Matters, published by Doubleday in 2005, I devoted a chapter to kids who are psychologically “gender-atypical.” I suggested that these kids are somewhere in between male and female. But the Stanford study provides little support for that claim. I am hopeful that the researchers will do follow-up studies specifically looking at individuals who are gender-nonconforming, gender-atypical, and who have gender dysphoria, to see whether and how those characteristics influence these findings."
As a middle-class Gen X-er, the FAFSA gives me PTSD already. ALL the hurdles, knowing that my kid won't get any financial aid anyway. I mean, what's the point? There should be an opt-out button at the beginning: "I know I'm not getting any help. Just finish the wizard and leave me alone."
"Best" is probably whatever you're familiar with. If your pre-pdf content is in Word, I'd just run with it -- most 'classic' word processors can handle the export to ebook stuff just fine. I've done exports from Apple Pages without issue.
That said -- if you're looking for a layout that reflows based on the screen size (read: more suited for mobile devices), you might want to look at exporting to .epub rather than .pdf.
I look at the numbers in the article and my eyes glaze over; the only thing I got out of it was that they're urging India to bump its poverty level numbers. (I am decidedly _not_ and economist)
In this case, the push towards simplicity and sanity is just acknowledging the reality that front end dev is... not simple. From the blog post:
"Sometimes, people get angry at React or other FrontEnd frameworks just because they look scary or too complex. But the reality is, FrontEnd is complex."
Ages ago (2010-2011 I think?), I worked on a tool that exported and packaged text into .epub format. At the time one of the biggest headaches was the lack of good font rendering in ePub readers. Apple's Books app did an okay job, but some of the others just ignored the font settings, _even when an embedded font was packaged in the file_. All the more frustrating when you consider that the text was not English, and the embedded fonts were necessary for properly rendering the code points and not displaying question marks or boxes.
No idea if the available readers have improved, but I'm all for this proposal of a self-contained reader.
It looks like not a whole lot has changed in that space -- the readers are still the gate for what you can do with the format. Who's available to make a CanIUse for epub readers, to shame them into compliance? (only partly /s)