If DBT was programmed to do what you requested, how is it to decide what to do based on the following questions: Which of the codes that are used to represent bold, italic and underline should it keep and which ones should it discard in order to show the emphasized text in the braille output file? Should it delete the first and second codes, for example, if there are codes to represent all three emphasized elements in the print file? Sometimes, it is a case of actually doing some extra work in order to produce the result that you want. Perform a search for the codes in the right order that you want to find, then replacing them with the desired emphasize code that you want to keep to represent the emphasized text in the braille file, might be a good idea. Although I think that DBT has some major problems, in general, I would say that if an individual is prepared to get off their rear end, put their brain in gear and use some mental elbow grease and make an effort to get the desired result, those individuals would find that they would get an immense amount of satisfaction from their work and their labors. The biggest enjoyment I get, or have got from the books that I have transcribed is not necessarily in the transcribing and production processes, it is when I have picked up one of those publications and I have used it and learned from it in the same way as one of my customers who had purchased it from my company. Sincerely: Dave Durber On Tue, 27 Jul 2004 14:39:22 +1000, you wrote: >Hello, > >I notice when using DBT beta 4, that DBT is still treating the importing of >bolded, underlined and italicised text wrongly when more than one of these >conditions apply. This has not yet been corrected. > >Eg: if text is for exampled bolded and italicised, the translater uses >both the opening and closing codes for both bolding and italics thus giving >a string of dots 46 four times before the first word and twice before the >fourth, or subsequent word. > >I know that currently in Braille, bolding, italics and underlining are all >indicated in the same way with the use of the dots 46, but surely, DBT can >be programmed to look for combinations of these and if found, surpress >additional codes. > >It is nothing short of rediculous to read strings of dots 46 before words, >when in Braille they are currently doing nothing more than giving emphasis >to the words concerned as the reader does not know how those words were >presented in print other than the fact that they were intended to be >emphasised and consequently to stand out. > > > * * * * * >Christine Simpson >Information Alternatives >Accessing The Information You Need >18 Prosper Parade >Glen Iris VIC 3146 >AUSTRALIA >Tel: 61 3 9889 0392 >Mob: 0418 331 506 >Fax: 61 3 9889 6286 >Email: simpsonc@xxxxxxxxxxxxxx > > >* * * >* This message is via list duxhelp at freelists.org. >* To unsubscribe, send a blank message with >* unsubscribe >* as the subject to <duxhelp-request@xxxxxxxxxxxxx>. You may also >* subscribe, unsubscribe, and set vacation mode and other subscription >* options by visiting //www.freelists.org. The list archive >* is also located there. >* Duxbury Systems' web site is http://www.duxburysystems.com >* * * * * * * This message is via list duxhelp at freelists.org. * To unsubscribe, send a blank message with * unsubscribe * as the subject to <duxhelp-request@xxxxxxxxxxxxx>. You may also * subscribe, unsubscribe, and set vacation mode and other subscription * options by visiting //www.freelists.org. The list archive * is also located there. * Duxbury Systems' web site is http://www.duxburysystems.com * * *