how would the braille window represent a change in font? Or would it completely ignore it, thus losing the information conveyed by the font change? I think the handling of font -- even just on the print side -- should be handled carefully. For one thing, I think that the representation of a font on the screen may already be supported by some interface -- tables and images, etc). Rather than rush off and implement it by hand I think someone (did I volunteer?) should search for existing code. Then in transcribing into braille, maybe the important thing to preserve in the formatted braille is that there was a change in font for a block of text, thus setting it apart. Again, I may be showing my inexperience in braille transcription -- JohnB, what does liblouisutdml do with font changes? --le ----- Original Message ----- From: "John J. Boyer" <john.boyer@xxxxxxxxxxxxxxxxx> To: <brailleblaster@xxxxxxxxxxxxx> Sent: Monday, November 15, 2010 1:14 PM Subject: [brailleblaster] Word Processing Features: Re: Re: two lists? We will have styles, since a person will be able to assign the various things that Daisy xml supports, such as headings, lists, etc. I've been wondering how much word processing stuff we need also. We will probably have only a few font choices, for example. John On Mon, Nov 15, 2010 at 01:52:58PM -0500, Rick Roderick wrote: > Laura, > > All of this makes sense to me. I think the word processing can be fairly > simple, but will we have styles, like MegaDots and Duxbury, or will we > have > codes. like all versions of Duxbury and Hot Dots. > > In other words, will I have to manually insert codes, or will I do this > from > a list. > > I am talking about formatting symbols. > -- John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc. http://www.abilitiessoft.com Madison, Wisconsin USA Developing software for people with disabilities