[duxuser] Re: dxb and brf
- From: "Johan Roos" <JohanRoos@xxxxxxxxxxxxxx>
- To: <duxuser@xxxxxxxxxxxxx>
- Date: Tue, 17 Jun 2003 21:10:52 +0200
At an even lower level of abstraction, am I right, though, that fooling
around with a brf is actually just a plain bad idea in principle? It seems
to me that all lines are ended with hard returns and that if one adds to a
line, the next one will simply get shorter and the whole document will be
thrown out of its original format. What is the point of these files? Is it
simply to communicate with embossers?
And how, George, would the portable braille file differ from a brf? I think
you explained it about 24 hours ago, but perhaps this time round the seeds
will fall on more fertile soil. Mind you, it is more likely Duxbury Systems
that will have to be convinced, but I am a willing reader.
If I got any of this wrong, would someone please be good enough to
straighten me out?
Thanks Lloyd, for the explanation.
----- Original Message -----
From: "Lloyd G. Rasmussen" <lras@xxxxxxx>
To: <duxuser@xxxxxxxxxxxxx>
Sent: Tuesday, June 17, 2003 3:28 PM
Subject: [duxuser] Re: dxb and brf
.dxb is the binary version of the .bru "unformatted braille" file which
Duxbury used to use. If the line length and page depth are never going to
change, in this version of the document or in later revisions of the same
document, then .brf might be OK as an exchange format.
But if you want to explicitly tell future users and future software that
you have just changed the running header from this to that, or that the
following material is in computer braille and not just pre-formatted, or
the following material is a footnote, you want to give your successors all
of the codes and styles that came along with the document, so they have a
better chance of producing good braille from it if their line length or
page length need to be changed.
And at a higher level of abstraction, if your .dxb file is formatted
entirely using styles, people can make changes in the template that
interprets those styles, and the document is even more future-proof.
Some of these considerations also make back-translation to print more
reasonable. When you have a .brf file, you have very little to go on in
determining why things look the way they do.
At 02:07 PM 6/17/03 +0200, you wrote:
>Hi George
>
>OK. This makes a lot of sense. But when I try to apply the principle, it
>occurs to me that perhaps I should have asked my question in a less
>theoretical manner.
>
>If I proof-read hard copy Braille and I have the electronic copy available
>as formatted Braille, I can correct errors. But I did not compile the
>original formatted Braille file. My concern is that, once the corrections
>have been made, whoever compiled the original should still be able to
print.
>
>The first question, I suppose, is whether I should have been given the
>electronic copy as a brf. Once I have it as a brf, though, the second
>question is whether, if I do edit the brf, I should save it in that format,
>or whether the printers will have an easier time sorting out whatever
>formatting changes may result from the editing if I give it back to them as
>a dxb file.
>
>This all goes to the deployment of blind proof-readers. I know there are
>other issues associated with permitting a proof-reader to make his or her
>own corrections, so I don't want to debate those, but I thought that
>perhaps, if I make a full and frank disclosure I would enable the gurus to
>know what it is they are helping me with.
>
>Johan
>----- Original Message -----
>From: "George Bell" <info@xxxxxxxxxxxxxxxxxxx>
>To: <duxuser@xxxxxxxxxxxxx>
>Sent: Tuesday, June 17, 2003 11:07 AM
>Subject: [duxuser] Re: dxb and brf
>
>
>Hi Johan,
>
>I think the simple answer is that if a file needs to be sent
>"cross-platform", that is to say, used with a non-Duxbury application,
>then you would save as a "Formatted Braille File". This would result in
>a plain ascii file with very little by way of coding.
>
>On the other hand, if simply passing a file from one Duxbury user to
>another, then you would use Duxbury Coded Braille.
>
>George.
>
>>
>> -----Original Message-----
>> From: Johan Roos [mailto:JohanRoos@xxxxxxxxxxxxxx]
>> Sent: 16 June 2003 21:28
>> To: duxuser@xxxxxxxxxxxxx
>>
>> Hello all
>>
>> When would one save a file as a duxbury coded braille and as
>> a formatted braille file? I am working on a formatted
>> braille file which has been imported, but the question
>> strikes me as interesting in general.
>>
>> Thanks much
>>
>> Johan
>
Braille is the solution to the digital divide.
Lloyd Rasmussen, Senior Staff Engineer
National Library Service f/t Blind and Physically Handicapped
Library of Congress (202) 707-0535 <http://www.loc.gov/nls/>
HOME: <http://lras.home.sprynet.com>
The opinions expressed here are my own and do not necessarily represent
those of NLS.
* * *
* 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:
