[duxuser] Re: A Transcribing Question
- From: Dave Durber <dadurber@xxxxxxxxxxxxx>
- To: duxuser@xxxxxxxxxxxxx
- Date: Tue, 16 Mar 2004 10:31:18 -0500
Quoting the rules is one thing.
Unfortunately, it does not take account of situations where a an
author has placed an italicized attribute around a block of text and,
within the block of text they have also used bold and underscore
attributes.
If this file was created with the use of Word and was then imported
into DBT, the italic, bold and underscore attributes are interpreted
by DBT and the appropriate codes are put into the .DXP file.
Now, the problem is that when the .DXP file is transcribed into the
braille output file, the codes for italic, bold and underscore, as far
as i know, are all converted to dots 4-6.
Having all of the attributes in a printed document may look all fine
and dandy to a person who reads print but, it causes incredible
problems to those of us who read braille.
This is my opinion, for what it is worth,I would strip these
attributes out of the .DXP file. To do this, with the Search and
Replace function, perform the following:
Search for [fts~b]
Do not put anything in the Replace With edit field
Search for: [fte~b]
Do not put anything in the Replace With edit field
Perform the same function with {fts~i] and [fte~i] to remove the
italic attribute.
Perform the same function with [fts~u] and fte~u] to remove the
underscore attribute.
The resulting .DXB braille output file may not conform to, for
example, the Braille Authority of North America, (BANA) code but, it
should result in a readable plain braille file that can be easily read
by the average braille reader.
Sincerely:
Dave Durber
On Tue, 16 Mar 2004 09:36:07 -0600, you wrote:
>The rules for braille transcribing say that if a section of text in a
>paragraph is emphasized, it should be emphasized in braille. This is
>usually done by the use of dots 4-6.
>
>However, if there is a heading or any other structure that is always
>emphasized in print to help the sighted reader understand the structure of
>the text (i.e. to reinforce the idea that this is a heading or is a menu
>item), throw away the dots 4-6, and let the other elements of braille
>formatting show the structure (heading or menu item).
>
>Make sure that it is clear from your use of format what is a menu item,
>what is descrition, and what is the price.
>
>I do not think this is political. The braille rules and common braille
>useage says that braille italics are to be used for emphasis, not for format.
>
>-- David Holladay
>
>
>At 04:11 PM 3/16/2004 +0200, you wrote:
>>I agree with you about taking out the clutter. But rather let the author of
>>the menus find it out from you and not from someone else.
>>
>>Whatever I think, bear in mind that one's views on how closely Braille
>>should emulate print is an intensely political one. In other words, even if
>>I prefer the absence of the emphasis for myself, I might still hold to the
>>belief that as a supplier of Braille I ought to give the Braille reader what
>>the print reader got.
>>
>>And with Braille issues, there is no middle path to tread with confidence.
>>
>>JR
>>----- Original Message -----
>>From: "Karen Poulakos" <gladtidings@xxxxxxxxxxxxxxxxxx>
>>To: <duxuser@xxxxxxxxxxxxx>
>>Sent: Tuesday, March 16, 2004 4:01 PM
>>Subject: [duxuser] A Transcribing Question
>>
>>
>>I have been asked to transcribe some menus. Up to this point my embossing
>>has been for my own use, so I set things up the way I like to read them.
>>
>>When I emboss the files I was given for the menus, dots 4 and 6 preceed each
>>menu item. I'm guessing that the print might be italicized or something and
>>that's why.
>>
>>My question is, should I leave it that way, or remove the dots 4,6. If it
>>were for my own use I would remove them. To me, they're just unnecessary
>>extra dots. I want to do this correctly. What do you recommend.
>>
>>Thanks,
>>
>>Karen Poulakos
>>
>>* * *
>>* This message is via list duxuser at freelists.org.
>>* To unsubscribe, send a blank message with
>>* unsubscribe
>>* as the subject to <duxuser-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 duxuser at freelists.org.
>>* To unsubscribe, send a blank message with
>>* unsubscribe
>>* as the subject to <duxuser-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 duxuser at freelists.org.
>* To unsubscribe, send a blank message with
>* unsubscribe
>* as the subject to <duxuser-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 duxuser at freelists.org.
* To unsubscribe, send a blank message with
* unsubscribe
* as the subject to <duxuser-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
* * *
Other related posts:
