It has been our practice to transcribe not edit a teachers work. That being
said, we would bring it to the teachers attention if there were multiple
errors, or errors that would hamper understanding. As well, If it were an
important summative assignment or exam containing errors (and yes I have run
into a final Language Arts exam that had more than 20 errors, it had been
prepared by a work-experience student and no one had proof read the final
product, returned it to the teacher for corrections) we would ask for
corrections.
Gala Garland
Braillist/Transcriber
Eastern Edge RCSD
Supports for Students
Elk Island Public Schools
Phone: 780-467-0044 EX- 5052
Email: gala.garland@xxxxxxx
-----Original Message-----
From: ueb-ed-bounce@xxxxxxxxxxxxx [mailto:ueb-ed-bounce@xxxxxxxxxxxxx] On ;
Behalf Of George Bell
Sent: Friday, October 28, 2016 2:23 PM
To: ueb-ed@xxxxxxxxxxxxx
Subject: [ueb-ed] Corrections. (Was: Transcribing computer code into UEB)
I've changed the subject slightly but retained the original messages for
contextual reasons.
The issue of what to do when actual errors are found is an interesting topic in
itself. Do we or don't we correct?
Frankly, I have been astounded to see errors being allowed on the basis that,
"They were in the original".
In one case, in a three page table of English - French words, I found seventeen
errors in the French alone. And to make matters worse, the list had been
prepared by the actual French teacher!
I'd be interested in hearing how others handle this situation.
George Bell
(List Moderator)
-----Original Message-----
From: ueb-ed-bounce@xxxxxxxxxxxxx [mailto:ueb-ed-bounce@xxxxxxxxxxxxx] On ;
Behalf Of MJ Williams
Sent: 28 October 2016 19:59
To: ueb-ed@xxxxxxxxxxxxx
Subject: [ueb-ed] Re: Transcribing computer code into UEB
That's as maybe; in this case the error is in the textbook. the forward slash
wouldn't print a new line character -- as it was intended by the author.
Best, Matt
On 28/10/2016, Rita Dilek <rdilek@xxxxxx> wrote:
Hello Don and James,
I can't see the images either, but from my experience with computer
programming, I just want to say that you can't assume the book had a
Backslash symbol. A lot of computer languages use the regular forward
slashes.
Just make sure you know which of the symbols you are transcribing.
Regards.
Rita Dilek
Department Head
Program for the Visually Impaired
Vancouver Community College
1155 East Broadway
Vancouver, BC, V5T 4V5
Telephone: 604-871-7000 Ext. 7339
Email: rdilek@xxxxxx
-----Original Message-----
From: ueb-ed-bounce@xxxxxxxxxxxxx [mailto:ueb-ed-bounce@xxxxxxxxxxxxx]
On Behalf Of Bowden, James
Sent: Friday, October 28, 2016 4:11 AM
To: ueb-ed@xxxxxxxxxxxxx
Subject: [ueb-ed] Re: Transcribing computer code into UEB
Hello Don,
Unfortunately, I cannot see your images, please can you use text
representations of braille, e.g. SimBraille font, or use Unicode braille.
However, I can answer your question - good old C code:
You should in this case use the non-directional double quote sign, it
is dot 6, 2356. See RUEB 7.6.6 which includes "ASCII listings" as when
to use this symbol.
There are further examples, including program code in the Guidelines
for Technical Material (GTM) section 17.
No grade 1 signs are particularly really needed in this case, but if
you want to show them, put a grade 1 passage around it. You can put a
grade 1 passage on a line by itself if there is a larger code
fragment. Again, see GTM 17.
So, here's the braille:
printf"<,7hello1 world_*n,7">2
The above line should be rendered as SimBraille, but I have plain text
emails. So here it is again as Unicode braille:
⠏⠗⠊⠝⠞⠋⠐⠣⠠⠶⠓⠑⠇⠇⠕⠂⠀⠺⠕⠗⠇⠙⠸⠡⠝⠠⠶⠐⠜⠆
Please note, I have taken the liberty to correct the code so the
forward slash should be a backslash.
I trust this helps.
With best regards,
James.
-----Original Message-----
From: ueb-ed-bounce@xxxxxxxxxxxxx [mailto:ueb-ed-bounce@xxxxxxxxxxxxx]
On Behalf Of Donald Winiecki
Sent: 28 October 2016 11:47
To: ueb-ed@xxxxxxxxxxxxx
Subject: [ueb-ed] Transcribing computer code into UEB
I apologize for pelting you with questions regarding how we should
render computer code, but I have another one.
I am transcribing a computer science textbook. In it I find many
brailling puzzles. Here I will focus on only one:
The following computer code is set on a line of its own in the
textbook, so following UEB 11.10, I am transcribing it with the grade 1 word
indicators.
However, when I do that some trickiness emerges!
printf("hello, world/n");
The opening double-quote is tucked between an opening parentheses and
the letter `h`. Based on my (possibly incorrect) understanding of
UEB7.6.7, in grade 1 mode, the one-cell nonspecific opening quotation
mark can be misinterpreted as a question mark. If the one-cell
nonspecific opening quotation mark was placed in a grade 2 context, there
would be no problem.
However, I am not certain how to make sure the one-cell nonspecific
opening quotation mark is read as that in grade 1 mode.
To add to the mystery, section 15.4a in the NFB UEB training materials
includes the following. This seems to indicate that it is the
question mark and not the one-cell nonspecific opening quotation mark
that should be treated specially!
...a grade 1 symbol indicator should precede a semicolon or a
question mark that is standing alone, because the same braille symbols
are used to indicate the contractions for be and his. Other marks of
punctuation such as the exclamation point and the period do not have
contraction meanings, and therefore no grade 1 symbol indicator is
required to ensure that they will be read as punctuation. Examples:
Inline image 1
Right now, I am leaning toward not representing the one-cell
nonspecific opening quotation mark in the usage indicated above, in
any special way -- I'll just specify the symbols sequences as grade 1 words
as shown below.
Inline image 3
But tell me if I'm totally missing something!
Best,
_don
--
October is Wear dots...raise lots month at RNIB. Think dotty clothes,
dotty games and dotty cakes! Join in today and get your free
fundraising activity kit by visiting www.rnib.org.uk/weardots.
--
DISCLAIMER:
NOTICE: The information contained in this email and any attachments is
confidential and may be privileged. If you are not the intended
recipient you should not use, disclose, distribute or copy any of the
content of it or of any attachment; you are requested to notify the
sender immediately of your receipt of the email and then to delete it
and any attachments from your system.
RNIB endeavours to ensure that emails and any attachments generated by
its staff are free from viruses or other contaminants. However, it
cannot accept any responsibility for any such which are transmitted.
We therefore recommend you scan all attachments.
Please note that the statements and views expressed in this email and
any attachments are those of the author and do not necessarily
represent those of RNIB.
RNIB Registered Charity Number: 226227
Website: https://www.rnib.org.uk ;<https://www.rnib.org.uk>
