[duxuser] Re: Why Six-key Entry?
- From: "Blackburn, Alan" <Alan.Blackburn@xxxxxxxxxxxxxx>
- To: <duxuser@xxxxxxxxxxxxx>
- Date: Fri, 10 Jun 2005 14:34:19 +1000
Thanks for the clarification Dave, I thought that was the case. I don't
find it a "problem" to edit the brl file, but thanks for your offer. As
I say the main problem I have with mistakes in transcription are in the
technical codes.
Alan
-----Original Message-----
From: duxuser-bounce@xxxxxxxxxxxxx [mailto:duxuser-bounce@xxxxxxxxxxxxx]
On Behalf Of Dave Durber
Sent: Friday, 10 June 2005 11:33 AM
To: duxuser@xxxxxxxxxxxxx
Subject: [duxuser] Re: Why Six-key Entry?
Hello Alan:
You are absolutely right when I used the word "you" I was using that
word as in the collective "you" and not to you personally. On
reflection and with hindsight, I could and should have used a
different word or words to express what I wanted to say rather than
using the word "you" in the way that I did. Under no circumstances,
did I mean to insinuate or give the impression that you are a "poor
work person and can't be bothered to learn a piece of software", so
please accept my sincerest apologies.
You got me with the word p o r e when I should have used the word
p o o r instead. And of course, with p o r e being an actual word,
the spell checker did not pick it up as being misspelled.
As for the High horse, it is very comfortable thank you!
If in the future you have a situation where DBT does not transcribe
something correctly and you would normally correct it in the braille
file, if you E-mail me off-list with the problem, I will do my best to
help you resolve it.
Sincerely:
Dave Durber
On Fri, 10 Jun 2005 09:28:43 +1000, you wrote:
>Whooaaahhhhhh Dave!!
>
>I was merely offering Susan some reasons why one may want to use 6-key
>entry in response to her query. Sorry old mate, but I find it easier to
>use direct entry than codes (especially for technical work), for the
>very reasons you outline in your second and third paragraphs, though I
>have been known to use both methods (regularly). It depends which is
the
>quickest and easiest way to get the job done.
>
>BTW: As your reply was addressed to me personally I hope you are not
>insinuating that I am a "pore work person" (your spelling) and can't be
>bothered to learn a piece of software, but were speaking more
>"generically".
>
>Have a good day ... and be careful not to fall off your high-horse!
><smile>
>
>Alan
>
>-----Original Message-----
>From: duxuser-bounce@xxxxxxxxxxxxx
[mailto:duxuser-bounce@xxxxxxxxxxxxx]
>On Behalf Of Dave Durber
>Sent: Friday, 10 June 2005 1:28 AM
>To: duxuser@xxxxxxxxxxxxx
>Subject: [duxuser] Re: Why Six-key Entry?
>
>Hello Alan:
>
>I could not disagree more fundamentally and categorically with your
>statement "Until DBT does a flawless job of translating the print file
>to braille there is going to be a need to edit the braille
>file--easier done in 6-key". To put it bluntly, your statement is
>balderdash and a load of cods wallop and, in my opinion and
>experience, totally untrue.
>
>I am not saying that it is easy to get round some of DBT's failings,
>foibles, inconsistencies and quirks, that being said, the previously
>mentioned difficulties can be got around if you are prepared to take
>the time and trouble and make the effort to learn its codes and how
>they work, you can produce well formatted, flawless, high quality
>braille documents when you prepare your files for transcription with
>the print editor.
>
>I prepare all of my files for transcription in the print editor. When
>I proofread a braille document, if and when I find errors, I make the
>changes in the print file, then I re-transcribe the file, and check to
>make sure that the corrections have been performed correctly.
>
>As a Braille transcriber, I take a great deal of pride in the
>ultra-high quality standard of braille transcription I am able to
>produce with DBT. This is because when I got DBT, I made the
>conscious decision, that if I was going to produce braille for sale, I
>was determined that it had to be the best and highest quality
>possible.
>
>So, from the beginning, I made it my business to learn all I could
>about DBT, its styles and how to create and modify them, how to use
>the format and transcription codes, I learned and I am still learning
>how to get around the previously mentioned difficulties and problems
>so I can produce the highest quality standard of braille.
>
>I was helped and continue to be helped to achieve my goal by Don
>Breeder who answered and continues to answer my questions regarding
>DBT and Steve Matzura, who is a certified braille
>transcriber/proofreader and like me, is only interested in producing
>and reading nothing but the highest quality braille possible. With
>Don's help and Steve's expert constructive criticisms, help and
>comments, I adjusted the parameters in DBT's styles to produce the
>results automatically when applying the appropriate styles in any
>documents I prepare.
>
>As for 6 key entry, I can do it but I have a tendency to try and use
>the other keys on the keyboard when I am thinking ahead of myself. I
>personally find it easier to use the ASCII character representations
>rather than using 6 key input. It is a matter of personal preference
>as to the method you choose to use. neither method is the correct or
>incorrect method.
>
>As I have said on this list before, "if a job is worth doing, not only
>do it well but, do it right".
>
>It is said that a pore work person who does not know how to do a job
>properly or, a work person who knows how to do a job but does it badly
>or poorly, always blames their tools. Therefore, it is easy to blame
>DBT when the resulting braille file does not produce the desired
>result, especially if you do not want to take the time and effort,
>cannot be bothered/prepared to take the time and effort, or you are
>too lazy to take the time and effort to learn even the most basic and
>fundamental functions of the program and how they work, you will
>always be a pore quality transcriber and as a result, you will always
>produce poor quality braille.
>
>Sincerely:
>
>Dave Durber
>
>On Wed, 8 Jun 2005 10:16:58 +1000, you wrote:
>
>>Susan,
>>Until DBT does a flawless job of translating the print file to braille
>>there is going to be a need to edit the braille file--easier done in
>>6-key.
>>
>>Not everyone uses Nemeth so (non-BANA) technical codes are near
>>impossible to enter in ASCII (I have no experience trying to do so
with
>>BANA codes)--so by necessity done in 6-key.
>>
>>Formatting of the braille document is very hard to see in the print
>file
>>and necessitates use of all those pesky codes, things are more WYSIWYG
>>in 6-key thereby making most of the codes un-necessary and DBT easier
>to
>>learn and use.
>>
>>If transcribers weren't expected to learn 6-key it follows they
>wouldn't
>>also be expected to learn braille, as if you can do one you can do the
>>other. The short answer is that if you are expecting a good, accurate
>>and well formatted transcription the transcriber has to be able to
read
>>AND write braille, to suggest otherwise is ludicrous! You could
>probably
>>get a parcel of secretaries to do braille transcription, but I can
>>imagine what the resultant braille document would look like (apologies
>>to the secretarial profession).
>>
>>I am (probably) one of the few who can braille faster than I can type.
>>At least I can use six fingers to braille, whereas I'm stuck with two
>>for typing :-)
>>
>>Later, Alan
>>
>>-----Original Message-----
>>From: duxuser-bounce@xxxxxxxxxxxxx
>[mailto:duxuser-bounce@xxxxxxxxxxxxx]
>>On Behalf Of Susan Jolly
>>Sent: Wednesday, 8 June 2005 12:05 AM
>>To: duxuser@xxxxxxxxxxxxx
>>Subject: [duxuser] Why Six-key Entry?
>>
>>Noting the recent questions about Perky Duck reminded me once again of
>>my
>>curiosity about six-key entry. Why do transcribers use six-key
instead
>>of
>>ASCII Braille? One reason for asking this question is I'm wondering
if
>>the
>>transcriber shortage in the US would be eased if transcribers weren't
>>expected to learn six-key.
>>Thanks,
>>SusanJ
>>
>>* * *
>>* 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 intended for the addressee named and may contain
>>privileged information or confidential information or both. If you
>>are not the intended recipient please delete it and notify the sender.
>>**********************************************************************
>>* * *
>>* 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 intended for the addressee named and may contain
>privileged information or confidential information or both. If you
>are not the intended recipient please delete it and notify the sender.
>**********************************************************************
>* * *
>* 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 intended for the addressee named and may contain
privileged information or confidential information or both. If you
are not the intended recipient please delete it and notify the sender.
**********************************************************************
* * *
* 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:
