Hi Don,
Good to hear from you again.
I'll go through some of your comments: Your text is marked with DW and my
answers with JB.
DW: Second, I don't know why my simbraille transcription fragment did not come
through on the list. I made a screenshot of the simbraille and pasted that
into my original E-mail. Advice on how to correct that in the future would be
appreciated.
JB: The keyword here is "screenshot". Screenshot = picture = inaccessible to
text only readers.
You could just paste the Simbraille characters. If you're using HTML format
email, they should come through OK for anyone who has the font; and they will
also be readable for anyone with a braille display, whether you're using plain
text or HTML.
Alternatively, you can use the Unicode braille range, which will come out OK
for those who don't have the font.
You can always send the screenshot plus either of the above. Hope that helps.
DW: Fourth, I am including all of the C code in my transcriptions in grade 1.
This follows advice from the US UEB guidelines for how to represent computer
code.
JB: This advice is also in GTM.
DW: Finally, I would like to ask about the use of GTM. It is my understanding
that UEB is supposed to supersede GTM and other guidelines. I acknowledge that
the two-cell non-directional quote is included in the symbols list in the
current US UEB guidelines, but its use is not indicated anywhere in those UEB
guidelines.
JB: I don't know the situation in the USA, I am in the UK. As I understand it,
there are two books which should be your main reference for UEB:
* The Rules of Unified English Braille [2013] (RUEB)
* Guidelines for Technical Material [2008] (GTM)
These are both used together.
The UK Association for Accessible Formats (UKAAF) has published a couple of
additional papers to clarify some procedures in the UK, for example, for
dealing with grade 1 indicators in mathematics and how we handled foreign
languages, but these are subsidiary to the main works for UEB and add some
detail to some areas where there are several acceptable ways to do things
according to RUEB and GTM.
I cannot comment on the US UEB guidelines as I haven't read them.
I hope this helps.
With best regards,
James.
-----Original Message-----
From: ueb-ed-bounce@xxxxxxxxxxxxx [mailto:ueb-ed-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Don Winiecki
Sent: 29 October 2016 14:02
To: ueb-ed@xxxxxxxxxxxxx
Subject: [ueb-ed] Re: Transcribing computer code into UEB
Hi and thank you for your responses -- a terrific welcome from the list!
Firstly, the backslash in my text example of the computer code was my typo --
the braille I included was accurate. (Kind of embarrassing because I code in
C. Surely it's the `loose nut on my keyboard`.)
Second, I don't know why my simbraille transcription fragment did not come
through on the list. I made a screenshot of the simbraille and pasted that
into my original E-mail. Advice on how to correct that in the future would be
appreciated.
Third and most relevant to my original question, thank you for pointing me to
the two-cell non-directional quote symbol. I will begin using that, add it to
my list of symbols used, and insert a transcriber's note in front matter that
alerts the reader to my use of the non-directional quote and the relevant
section in the Guidelines for Technical Material (GTM).
Fourth, I am including all of the C code in my transcriptions in grade 1. This
follows advice from the US UEB guidelines for how to represent computer code.
Finally, I would like to ask about the use of GTM. It is my understanding that
UEB is supposed to supersede GTM and other guidelines. I acknowledge that the
two-cell non-directional quote is included in the symbols list in the current
US UEB guidelines, but its use is not indicated anywhere in those UEB
guidelines.
Best,
_don
On Oct 28, 2016, at 11:08 PM, FreeLists Mailing List Manager
<ecartis@xxxxxxxxxxxxx> wrote:
From: Donald Winiecki <dwiniecki@xxxxxxxxxxxxxx>
Date: Fri, 28 Oct 2016 04:46:50 -0600
Subject: [ueb-ed] Transcribing computer code into UEB
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:
[image: 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.
[image: Inline image 3]
But tell me if I'm totally missing something!
Best,
_don
------------------------------
From: "Bowden, James" <James.Bowden@xxxxxxxxxxx>
Subject: [ueb-ed] Re: Transcribing computer code into UEB
Date: Fri, 28 Oct 2016 11:10:45 +0000
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.
