A bookmaker's V&R...

[Uncle Robin]

Originally Posted by Hitch

I agree, absolutely. I was referring to the Women's Rights movement which misappropriated misogyny to mean, "woman-hating" decades ago.
Hitch

"misappropriated"? As opposed to what other meaning?

The OED offers only this in its listing for "misogyny"
Hatred or dislike of, or prejudice against women.

And the example usages given suggest the meaning you describe as "misappropriated" "decades ago" is, in fact, nearly 4 centuries old.

1656 T. Blount Glossographia Misogynie (misoginia), the hate or contempt of women.

[jhowell]

Originally Posted by Hitch

I've simply reached my limit on educating people who read something that they don't understand, "on the net" and then think that they should interrogate me about it.

This week's Dilbert comics are timely ones about Dogbert providing tech support. For example: https://dilbert.com/strip/2019-12-11

[Hitch]

Originally Posted by Uncle Robin

"misappropriated"? As opposed to what other meaning?

The OED offers only this in its listing for "misogyny"
Hatred or dislike of, or prejudice against women.

And the example usages given suggest the meaning you describe as "misappropriated" "decades ago" is, in fact, nearly 4 centuries old.

1656 T. Blount Glossographia Misogynie (misoginia), the hate or contempt of women.

Well, you're right and I effed up.

I don't know--and I admit, this is bugging me--if I misread it years ago, or worse, pulled from the wrong data bank yesterday or whenever. I seem to be misfiring lately, which is disturbing at best.

I've always had near-eidetic recall and...this ain't fun. I'm hoping that it's this new med. S**t.

Hitch

[Quoth]

liquid Christmas spirit?
We all can make mistakes. Admitting it is positive.
I've mixed up malaprop and misanthrope. The first one sounds like it ought to describe a bad thing.

I clicked on a word in a book briefly last week. Unfortunately it was printed. Fortunately no-one saw me.

[Tex2002ans]

Originally Posted by Hitch

I've simply reached my limit on educating people who read something that they don't understand, "on the net" and then think that they should interrogate me about it.

Toss another thing in the FAQ, write an article, point them to it. I'm sure they'll read it.

Originally Posted by Hitch

Or how they want "PDF3" or "Kimble" or any of the other 50 things I've heard, just in the last 3 months.

What, you've never heard of this amazing Amozan Kimble?

Originally Posted by FrustratedReader

WCAG is irrelevant for books and ebooks. It's not even very good for web sites.

Again, while many of the recommendations may not be applicable to ebooks-specifically, you can make your code more future-proof by pick-and-choosing from WCAG + WebAIM.

On the reader side, people may take your HTML and read in non-EPUB readers: DAISY, NVDA, JAWS, and who-knows-what-future-reader. For example, while all EPUB readers/apps don't display <title> in the header, it's still a good idea to include meaningful titles.

On the production side, new enhancements are happening all the time. For example, Multi-Language Spellchecking in Calibre (absolutely fantastic use of lang + xml:lang).

Originally Posted by FrustratedReader

Tables as <table>, not pictures of data

Yes, text but not Tables because they work poorly or not at all

What?

Originally Posted by FrustratedReader

Foreign letters as actual text, not as little images.

Sadly doesn't work on many ereaders, though it could have years before release

What?

Originally Posted by FrustratedReader

Use proper lang + xml:lang

Sadly doesn't work on many ereaders, though it could have years before release

What?

Originally Posted by FrustratedReader

Proper alt text

Sadly doesn't work on many ereaders, though it could have years before release.

What?

Originally Posted by FrustratedReader

Proper alt text

You need a text caption under the image if it's important for Text to Speech

Yes, also good to have that as backup. But alt text serves a different purpose:

https://webaim.org/techniques/alttext/

Originally Posted by FrustratedReader

A few examples of talks:
Snipped, mostly a waste of time.

They explain real-life Accessibility issues from consumers, problems that exist with many current ebooks, plus things you should keep in mind for the future (like the potential legal requirements, etc.).

And as discussed in those talks, library (and academic) purchases are tending towards requiring some base level of Accessibility. If your ebooks won't meet that base level, no purchase.

Originally Posted by FrustratedReader

9) Only footnotes in reference works, try an inline right justified paragraph in sans rather than linked footnotes.

??? Can you show me an example of this?

Originally Posted by FrustratedReader

12) No page numbers except as right margin "notes" as actual pages in a copy of a reference work that's only ever one paper layout (e.g. Hebrew Bible)

Best to just use standard page-map/page-list and leave the rendering up to the reader.

Using the standard methods also allows users to jump to the exact page, plus navigate through the document per page.

[Hitch]

Originally Posted by FrustratedReader

liquid Christmas spirit?
We all can make mistakes. Admitting it is positive.
I've mixed up malaprop and misanthrope. The first one sounds like it ought to describe a bad thing.

I clicked on a word in a book briefly last week. Unfortunately it was printed. Fortunately no-one saw me.

No, I wish it were the Nog. :-)

Nope, my misanthropy and brainfart led me to commit a malaprop, kinda. ;-) Ha!

(Screwing up words really DOES distress me. My facility therewith has been one of my joys in life, sigh).

Hitch

[Quoth]

Simple comment style for fiction instead of fiddly footnotes (which don't work on every ereader). The note example is right now, you may need to narrow the browser window.

[A few words of note]

More body text. The "note" style will use sans if body is serif, or vice versa. It will have no vertical margin before and a suitable increased vertical margin after so as it's obviously a comment the previous paragraph.

Actually LibreOffice Writer has a style a bit like this called Marginalia.

I know some books really need footnotes. See also The Penguin Guide to Punctuation", R. L. Trask, available free from the author. Chapter 10.

Amazingly some old ereaders don't support even internal links. Even on the newest ereaders the way footnotes work can vary and they are awkward. I think normal text, not a superscript, is needed or they can be too hard to "click".

[Turtle91]

nevermind...

[Doitsu]

Originally Posted by FrustratedReader

[...]Amazon STUPIDLY had maybe only Latin/Roman and some Greek letters originally on the Kindle, even though the underlying Linux supported most lanaguages years earlier. It had worse language support than 1988 DOS.

Actually, when it comes to non-Latin alphabet support Amazon has a pretty good track record, because Kindles and Kinde apps come with code2000 as the Unicode fallback font, which covers Unicode 5.2. I.e., you'll rarely have to embed a font to display non-Latin characters.

[Quoth]

But at original release Kindles did not, even though the OS did. It took YEARS for Amazon to add support that was there from the beginning in the OS.

You can't assume someone has a Kindle that displays Cyrillic, Chinese, Korean, Hebrew, Arabic etc. Plenty of older Kindles and other old ereaders are still in use.

The entire Gadget / Computer field was USA Centric for decades. I have a not very old Android that only has USA physical keyboard layout support unless you install a 3rd party App. Totally unacceptable US centric behaviour by Google, who bought in Android.

By the late 1990s DOS, Windows (DOS and NT kinds), Mac OS, BSD, Linux all had proper multilingual display and keyboard support.

Kindle, Kobo, Android etc slow adoption of non-latin support etc was crazy!

Don't let me get started on ICANN either.

[DaleDe]

Anyone can improve our wiki but we do have a couple of pages. Accessible Publishing and Accessible Books Consortium. We also have information in a category called Category:Blind that shows other tips and information.

Dale

[Hitch]

Originally Posted by FrustratedReader

But at original release Kindles did not, even though the OS did. It took YEARS for Amazon to add support that was there from the beginning in the OS.

You can't assume someone has a Kindle that displays Cyrillic, Chinese, Korean, Hebrew, Arabic etc. Plenty of older Kindles and other old ereaders are still in use.

The entire Gadget / Computer field was USA Centric for decades. I have a not very old Android that only has USA physical keyboard layout support unless you install a 3rd party App. Totally unacceptable US centric behaviour by Google, who bought in Android.

By the late 1990s DOS, Windows (DOS and NT kinds), Mac OS, BSD, Linux all had proper multilingual display and keyboard support.

Kindle, Kobo, Android etc slow adoption of non-latin support etc was crazy!

Don't let me get started on ICANN either.

Yabbut...

Having the character set, and having the software to CHECK the character set are two different things.

Don't forget that they check for Public Domain and all sorts of stuff. Recipes, and who-knows-what. I suspect that's the holdup--the hitch in the gitalong, so to speak (ha!)--in implementing many of the languages and character sets.

Hitch