Hi John. We agree about a "preview" of some kind. We also haven't ruled out putting the page and line breaks back in there at some point. It is just that, for the time being, they add complication to an already complicated procedure. If we can get all the editing and indexing to work right without them and know that it is right then we can work on other issues from a stable foundation. At least that's our logic. Keith Creasy Software Developer American Printing House for the Blind KCreasy@xxxxxxx Phone: 502.895.2405 Skype: keith537 -----Original Message----- From: brailleblaster-bounce@xxxxxxxxxxxxx [mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of John J. Boyer Sent: Thursday, May 09, 2013 1:32 PM To: Brandon Roller Cc: brailleblaster@xxxxxxxxxxxxx Subject: [brailleblaster] Re: Using "paragraphs no" and "braillePages no" Brandon, Let's take this discussion back to the list, so others know what is going on and can contribute. I can change the code. I think we should have a Braille preview, which will show formatting and pagination and either produce an embosser-ready file or call an embosser driver. Preferences.cfg could remain the same and any changes for particular situations could be made through the configSettings parameter. However, I'm not going to argue the point. John On Thu, May 09, 2013 at 10:33:09AM -0400, Brandon Roller wrote: > John, > Keith and I have discussed using "paragraphs no" and "braillePages no" > configuration settings and we both think this is the best way to go > for now. We'll put an edited version of the preferences.cfg file in > our local userProgramData folders if you'll change the code to > recognize these settings. -- John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc. http://www.abilitiessoft.com Madison, Wisconsin USA Developing software for people with disabilities