RE: Updates to EdSharp

  • From: "Homme, James" <james.homme@xxxxxxxxxxxx>
  • To: "programmingblind@xxxxxxxxxxxxx" <programmingblind@xxxxxxxxxxxxx>
  • Date: Mon, 10 Jan 2011 06:57:38 -0500

Hi Ken,
Thanks for this. I was wondering why Bookshare mixes HTML with their DAISY 
markup. I thought they put an XSL style sheet with their books. I would think 
that they would use the XSL style sheet to transform the DAISY tags into HTML. 
If they'd remove the HTML, the files would be less bloated. Maybe I'm missing 
something, though.

Thanks.

Jim

Jim Homme,
Usability Services,
Phone: 412-544-1810. Skype: jim.homme
Internal recipients,  Read my accessibility blog. Discuss accessibility here. 
Accessibility Wiki: Breaking news and accessibility advice


-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx 
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Ken Perry
Sent: Saturday, January 08, 2011 12:36 PM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: Updates to EdSharp

Sorry I didn't reply earlier Jim but here is a page that may help.

http://data.daisy.org/projects/pipeline/doc/summary.html

-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Homme, James
Sent: Friday, January 07, 2011 10:33 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: Updates to EdSharp

Hi,
My goal is to create a converter for EdSharp so that you can enter a form of
MarkDown and get a compliant DAISY file. I was looking for some sort of
stable standard to base my program on. That's pretty much it.

Jim

Jim Homme,
Usability Services,
Phone: 412-544-1810. Skype: jim.homme
Internal recipients,  Read my accessibility blog. Discuss accessibility
here. Accessibility Wiki: Breaking news and accessibility advice


-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Rasmussen, Lloyd
Sent: Friday, January 07, 2011 9:39 AM
To: programmingblind@xxxxxxxxxxxxx
Subject: RE: Updates to EdSharp

I have served on the maintenance committees for the ANSI/NISO versions of
the standard, but am not actively involved at the moment.  The next version
of Z39.86 has been divided into two parts.  Part B, for distribution, will
almost certainly be an accessible version of the EPub standard which is now
being revised.  The Daisy Consortium is the maintenance agency for EPub now,
so it has a lot of input into the next version of that standard, which is
managed by the International Digital Publishing Forum.  The fact that the
new standard is based on EPUB means that a book or magazine will be in a
single file, compressed and archived using a subset of the ZIP format.  I
wouldn't expect to see this revision adopted for at least another 12 months,
and agencies such as NLS and BookShare may or may not switch to it quickly.

For non-technical explanations of what is going on, and links to more tools
and projects, go to www.daisy.org and start reading issues of the Daisy
Planet monthly newsletter.


Lloyd Rasmussen, Senior Project Engineer
National Library Service for the Blind and Physically Handicapped
Library of Congress   202-707-0535
http://www.loc.gov/nls
The preceding opinions are my own and do not necessarily reflect those of
the Library of Congress, NLS.



-----Original Message-----
From: programmingblind-bounce@xxxxxxxxxxxxx
[mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Jamal Mazrui
Sent: Friday, January 07, 2011 9:06 AM
To: Rasmussen, Lloyd; programmingblind@xxxxxxxxxxxxx
Cc: Ken Perry
Subject: Re: Updates to EdSharp

One thing I find annoying about Daisy format is that each book essentially
has to be in its own directory because it includes several files that work
together.  I understand how individual files are needed as components in
building a book, but do not understand why the format is not defined so that
the components are packaged as a single, combined file, possibly in a
compressed form.  A Daisy reader should be able to dynamically parse out the
needed components at runtime in memory.
Instead, a Daisy book tends to be an intimidating and messy smattering of
files on disk.

Does anyone know whether there are plans to change this situation?

Jamal


On 1/7/2011 8:48 AM, Ken Perry wrote:
> I have an adjoining desk with Keith Cresey who is on the Daisy
> steering committee, he wrote Book wizard producer that is used to
> record many of the APH daisy titles, and I am becoming an experienced
> daisy coder with the work I have done on a few of our projects here at
> APH for both RFBD and Bookshare.  Bookshare has serious issues.
> Sometimes they might validate but the chances are they will not.  As
> for RFBD there is no Schemas that I know of for Daisy 2 which is what
> RFBD uses.  We pretty much have to make parsers for each group of
> daisy types.  The problem is the daisy committee tried to do too much
> which made the standard to loose and these producers do whatever the heck
they want.
>
> Ken
>
> Bookshare is about 90 %
>
> -----Original Message-----
> From: programmingblind-bounce@xxxxxxxxxxxxx
> [mailto:programmingblind-bounce@xxxxxxxxxxxxx] On Behalf Of Homme,
> James
> Sent: Friday, January 07, 2011 8:38 AM
> To: programmingblind@xxxxxxxxxxxxx
> Subject: FW: Updates to EdSharp
>
> Hi,
> Do we have a DAISY expert here?
>
> Thanks.
>
> Jim
>
> Hi Jim,
> I assume that Daisy books from BookShare validate against the Daisy
> XML schema, but I do not know what their quality is beyond that.
> Perhaps Lloyd Rasmussen on this list (a Daisy expert) may have more
information.
>    I'm also curious about the same questions for Daisy books from
> RFB&D and NLS.
>
> Jamal
>
>
> On 1/7/2011 8:04 AM, Homme, James wrote:
>> Hi Jamal,
>> Thanks. I hadn't gotten that far in my testing.
>>
>> Question for you. As I am planning for my Python MarkDown program, I
> thought of something. Maybe it would be a good idea to make it produce
> DAISY files. I was looking at some files from BookShare. Do you know
> if they are standard DAISY or not?
>>
>> Jim
>> Jim Homme,
>> Usability Services,
>> Phone: 412-544-1810. Skype: jim.homme Internal recipients,  Read my
>> accessibility blog. Discuss accessibility
> here. Accessibility Wiki: Breaking news and accessibility advice

__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind


This e-mail and any attachments to it are confidential and are intended
solely for use of the individual or entity to whom they are addressed.  If
you have received this e-mail in error, please notify the sender immediately
and then delete it.  If you are not the intended recipient, you must not
keep, use, disclose, copy or distribute this e-mail without the author's
prior permission.  The views expressed in this e-mail message do not
necessarily represent the views of Highmark Inc., its subsidiaries, or
affiliates.
__________
View the list's information and change your settings at 
//www.freelists.org/list/programmingblind

__________
View the list's information and change your settings at 
//www.freelists.org/list/programmingblind

__________
View the list's information and change your settings at
//www.freelists.org/list/programmingblind

Other related posts: