[brailleblaster] Re: some considerations

  • From: Alex Jurgensen <asquared21@xxxxxxxxx>
  • To: brailleblaster@xxxxxxxxxxxxx
  • Date: Mon, 8 Nov 2010 21:03:56 -0800

Hi,

But a novis creates structured documents with Pages and probably with Word/Open 
Office templates, so why could this not be done. Most of Pages seems to be 
driven this way.

Regards,
Alex,


On 2010-11-08, at 8:22 PM, John Gardner wrote:

> I am concerned about trying to make BrailleBlaster also a DAISY creation
> tool.  Creating/editing structured documents is not something a novice
> computer user can usually do.  
> 
> There is no reason that BrailleBlaster's code base cannot be used for other
> things, and developing a true DAISY authoring tool might be relatively
> straightforward.  Personally I would love to spin off a DAISY Reader project
> too.  But we don't have just lots of resources to spread around, so we
> should really just concentrate on BrailleBlaster.  At least that's my
> opinion.
> 
> John G
> 
> 
> -----Original Message-----
> From: brailleblaster-bounce@xxxxxxxxxxxxx
> [mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of John J. Boyer
> Sent: Monday, November 08, 2010 7:31 PM
> To: brailleblaster@xxxxxxxxxxxxx
> Subject: [brailleblaster] Re: some considerations
> 
> An adendum to my previous e-mail. Of course BrailleBlaster won't create 
> complete Daisy documents, just the xml file. That is the only thing 
> I usually deal with, so i tend to thing it's the whole thing. I 
> understand that there is software that wikll create a complete taisy  
> document from the xml file.
> 
> John
> 
> On Mon, Nov 08, 2010 at 09:13:57PM -0600, John J. Boyer wrote:
>> That is basically my understanding. However, I see no reason why 
>> BrailleBlaster couldn't create a Daisy document, just as Word can create 
>> a doc or docx file. Someone might want to use brailleBlaster to create a 
>> braille document from scratch. Creating a badsic Daisy template is 
>> simple. I do that in liblouisutdml for translating text files and 
>> back-translating brf files. The structure the user will see for such a 
>> file is juust a set of paragraphs. She would have the option of 
>> changging the paragraphs to whatever else is permitted in that point by 
>> Daisy.
>> 
>>> From the programmer's point of view, all the editor will be doing is 
>> adding nodes, deleting them, changing the tags on them (as for headings) 
>> and changing the content of text nodes.
>> 
>> For Laura, can you point me to editors that use Sax, a DOM or both? 
>> Considering the above paragrraph, will Sax do the things mentioned 
>> there?
>> 
>> John
>> 
>> On Mon, Nov 08, 2010 at 01:46:31PM -0800, John Gardner wrote:
>>> Laura, I wrote the original specification with the clear hope that the
> user
>>> would be required to do as little structure manipulation as possible.
> As
>>> much as feasible, BB should appear like a WYSIWYG editor.  BB has the
> DAISY
>>> tag set but is not restricted to any of the DAISY structural
> requirements.
>>> BB can operate on a fully valid DAISY file, but it cannot really create
> one.
>>> 
>>> At least that is what I think BB should be if it is to be useable by
> novices
>>> as well as experts.
>>> 
>>> John G
>>> 
>>> -----Original Message-----
>>> From: brailleblaster-bounce@xxxxxxxxxxxxx
>>> [mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of qubit
>>> Sent: Monday, November 08, 2010 1:32 PM
>>> To: brailleblaster@xxxxxxxxxxxxx
>>> Subject: [brailleblaster] some considerations
>>> 
>>> Hi all -- I've been reading the various pages on parsers and tika and
> sax vs
>>> 
>>> dom4j and I am wondering what will be the nature of the editing that
> braille
>>> 
>>> blaster will support?
>>> Will the end user have an understanding of DAISY, and expect to
> manipulate 
>>> objects and subtrees in the document's structure? or will he/she just
> see a 
>>> rendered document like Word and not know or care about underlying
> objects?
>>> I'm still just throwing the question out there for discussion. I have
> been 
>>> working on tika patches, thinking tika might be what is needed, but it
> of 
>>> course tika uses sax rather than dom4j.
>>> However, some editors apparently use both sax events and dom.
>>> 
>>> Just trying to stir up some discussion. Comments welcome.
>>> --le
>>> 
>>> 
>>> 
>>> 
>> 
>> -- 
>> My websites:
>> GodTouches Digital Ministry, Inc. http://www.godtouches.org
>> Abilitiessoft, Inc. http://www.abilitiessoft.com
>> Location: Madison, WI, USA
>> 
>> 
> 
> -- 
> My websites:
> GodTouches Digital Ministry, Inc. http://www.godtouches.org
> Abilitiessoft, Inc. http://www.abilitiessoft.com
> Location: Madison, WI, USA
> 
> 
> 
> 

Alex Jurgensen,
VoiceOver Trainer,
ASquared21@xxxxxxxxxxxxxxxxx                    

Visit us on the web at: www.vipbc.org

Other related posts: