Anybody here dealt with "Redshelf" vis: ePUB?

[JSWolf]

So how are Redshelf eBooks made if there's no information on how to code the eBook?

I think you should ask them for code to show you how they are made.

[Hitch]

Originally Posted by JSWolf

So how are Redshelf eBooks made if there's no information on how to code the eBook?

I think you should ask them for code to show you how they are made.

Dude, I defy you to go find it. If you aren't signed up as a publisher or educator or what-have-you, you can't even find ANYTHING!

Hitch

[DNSB]

Originally Posted by JSWolf

So how are Redshelf eBooks made if there's no information on how to code the eBook?

I think you should ask them for code to show you how they are made.

I did bounce an email off of them. I got a link to the Voluntary Product Accessibility Template which is a PDF file supplying very little useful information and which is listed on their web page and the previously mentioned 2 page 10MB PDF waste of electrons. A second email to accessibility@redshelf.com didn't get any useful information other than I can register as a publisher to get more information.

Perhaps someone else might be willing to dig deeper. I've reached my limit.

[Hitch]

Originally Posted by DNSB

I did bounce an email off of them. I got a link to the Voluntary Product Accessibility Template which is a PDF file supplying very little useful information and which is listed on their web page and the previously mentioned 2 page 10MB PDF waste of electrons. A second email to accessibility@redshelf.com didn't get any useful information other than I can register as a publisher to get more information.

Perhaps someone else might be willing to dig deeper. I've reached my limit.

For what it's worth, my CLIENT who is a registered publisher with them and a well-respected publisher of educational books, can't get more info from them. It's beyond ridiculous. It's as though their mindset is, "well, we'll use that 'accessibility' word, regardless of what that really means and as long as we don't publish anything around it, nobody can say we're doing something wrong."

Go get 'em, Wolfie. If anybody can torture them into submitting, it's gotta be you.

Hitch

[Hitch]

Oh, and by the way--that Vountary Product Accessibility report? That's about webpages, not bloody documents!

And you know what's not in there? Jack about PAGE NUMBERS.

GRRRRRRRRRR...

Hitch

[DNSB]

Originally Posted by Hitch

Oh, and by the way--that Vountary Product Accessibility report? That's about webpages, not bloody documents!

And you know what's not in there? Jack about PAGE NUMBERS.

GRRRRRRRRRR...

Hitch

But that two page PDF does mention page numbers.

2. Include Page Number Information:
Digital books, by definition, do not have “pages” in the traditional sense, as each
individual reader sets font sizes according to personal preferences, which in turn
alters page/screen length. Nevertheless, to ensure that every student using a digital
edition of your content can easily locate a specific print-based page being referenced
by a classmate or instructor, we ask that you provide page numbers and related
Table of Contents.

Though it does say "we ask" and not "we require".

[JSWolf]

So why would your highly respected publisher want to go with Redshelf when they get so many really bad reviews?

[Hitch]

Originally Posted by JSWolf

So why would your highly respected publisher want to go with Redshelf when they get so many really bad reviews?

Jon?

Because bad reviews or not, it's what the educational system uses. Don't be silly, please.

Hitch

[BetterRed]

Suggestion: you, or your client, invests in an existing Redshelf publication and then you can dissect it.

BR

[PeterT]

Originally Posted by BetterRed

Suggestion: you, or your client, invests in an existing Redshelf publication and then you can dissect it.

BR

I'm not sure you can download a Redshelf publication to view it; I believe it's accessed via a browser or their own app

[Hitch]

Originally Posted by BetterRed

Suggestion: you, or your client, invests in an existing Redshelf publication and then you can dissect it.

BR

Red, you crush me! You never thought I'd think of that? Sheesh, you wrong me, brother!

Originally Posted by PeterT

I'm not sure you can download a Redshelf publication to view it; I believe it's accessed via a browser or their own app

And, thar it is.

Hitch

[najgori]

...or one could use browser web inspector and directly read book code.
Is this demo epub even reflowable, or is it fixed layout?

[BetterRed]

Sorry, following 40 posts and no solution, I thought it was silly questions time, they can sometimes trigger an ah-ha moment.

No worries, I have a new doona to crawl under

BR

[DNSB]

Originally Posted by najgori

...or one could use browser web inspector and directly read book code.
Is this demo epub even reflowable, or is it fixed layout?

Redshelf epubs are reflowable. Just that they do not have useful documentation on the accessibility requirements. What they seem to want is a page list in the navigation document ( the first sample is from an epub3 book's nav.xhtml, the second from the toc.ncx included for epub2 renderers):

<nav role="doc-pagelist" aria-label="Page list" epub:type="page-list">
<h2>Pagebreaks of the print version</h2>
<ol>
<li><a href="xhtml/cover.xhtml">Cover Page</a></li>
<li><a href="xhtml/title.xhtml#pg_v">v</a></li>
<li><a href="xhtml/epigraph.xhtml#pg_vii">vii</a></li>
<li><a href="xhtml/chapter1.xhtml#pg_1">1</a></li>
<li><a href="xhtml/chapter1.xhtml#pg_2">2</a></li>
<li><a href="xhtml/chapter1.xhtml#pg_3">3</a></li>
...
<li><a href="xhtml/epilogue.xhtml#pg_353">353</a></li>
<li><a href="xhtml/epilogue.xhtml#pg_354">354</a></li>
<li><a href="xhtml/epilogue.xhtml#pg_355">355</a></li>
<li><a href="xhtml/adcard.xhtml#pg_ii">ii</a></li>
<li><a href="xhtml/adcard.xhtml#pg_iii">iii</a></li>
<li><a href="xhtml/copyright.xhtml#pg_vi">vi</a></li>
</ol>
</nav>

<pageList>
<pageTarget type="normal" id="id_cov" value="Cover Page"><navLabel><text>Cover Page</text></navLabel><content src="xhtml/cover.xhtml"/></pageTarget>
<pageTarget type="normal" id="id_v" value="v"><navLabel><text>v</text></navLabel><content src="xhtml/title.xhtml#pg_v"/></pageTarget>
<pageTarget type="normal" id="id_vii" value="vii"><navLabel><text>vii</text></navLabel><content src="xhtml/epigraph.xhtml#pg_vii"/></pageTarget>
<pageTarget type="normal" id="id_1" value="1"><navLabel><text>1</text></navLabel><content src="xhtml/chapter1.xhtml#pg_1"/></pageTarget>
<pageTarget type="normal" id="id_2" value="2"><navLabel><text>2</text></navLabel><content src="xhtml/chapter1.xhtml#pg_2"/></pageTarget>
<pageTarget type="normal" id="id_3" value="3"><navLabel><text>3</text></navLabel><content src="xhtml/chapter1.xhtml#pg_3"/></pageTarget>
...
<pageTarget type="normal" id="id_353" value="353"><navLabel><text>353</text></navLabel><content src="xhtml/epilogue.xhtml#pg_353"/></pageTarget>
<pageTarget type="normal" id="id_354" value="354"><navLabel><text>354</text></navLabel><content src="xhtml/epilogue.xhtml#pg_354"/></pageTarget>
<pageTarget type="normal" id="id_355" value="355"><navLabel><text>355</text></navLabel><content src="xhtml/epilogue.xhtml#pg_355"/></pageTarget>
<pageTarget type="normal" id="id_ii" value="ii"><navLabel><text>ii</text></navLabel><content src="xhtml/adcard.xhtml#pg_ii"/></pageTarget>
<pageTarget type="normal" id="id_iii" value="iii"><navLabel><text>iii</text></navLabel><content src="xhtml/adcard.xhtml#pg_iii"/></pageTarget>
<pageTarget type="normal" id="id_vi" value="vi"><navLabel><text>vi</text></navLabel><content src="xhtml/copyright.xhtml#pg_vi"/></pageTarget>
</pageList>

Then you add the following or similar for each page reference:

<span aria-label="17" id="pg_17" role="doc-pagebreak"/>

This gets to be even more fun when there is no reference print book to lift the page numbers from.

This is where I feel happy that I have the ability to say no expletive deleted way to certain would be customers.

[najgori]

Originally Posted by DNSB

Redshelf epubs are reflowable.

When I click "Try It Now" I get AmGov by Christine Barbour and it is scrollable, not reflowable and it is not fixed layout.
It looks like every chapter is one long rotulus where you scroll up and down, so it is not reflowable - perhaps that is the way that javascript renders epub, but without original epub I don't know.