Forum Replies Created
The ellipsis seems to indicate simply that all of the a's between a sub 0 and a sub n are not going to be listed. I would transcribe this as an ordinary horizontal ellipsis. Often a vertical or even diagonal ellipsis is shown in a matrix -- in which case, a horizontal ellipsis is used.
Ok. Thanks Dorothy. I guess I was just over-thinking it.
I have asked about this. The errata is posted as a separate HTML document at the BANA website, but not incorporated into the Formats post. So Formats 2011 remains the same, but with errata available separately.
Do it the same way only with the arrowhead pointing left. [braille]$_[
If these are truly abbreviations, I would double cap the abbreviation that consists of more than one letter. The rule about treating abbreviations mathematically only applies to a series of unspaced letters and numbers, not letters only. For abbreviations the effect of capitalization ends with anything that is not a letter, so you have to restate the caps after the period or hyphen. I would better be able to answer if I knew what K.NBT and A-CED stand for.
Thank you for the clarification Dorothy. You asked if I am sure that they are both decimals and that neither is a period. How would I be able to tell? Thanks again.
edited by ricia2001 on 7/29/2013
This "f" does not need to be italicized. It is treated like italicized variables -- no emphasis.
I have a suggestion that I have attached to this reply. Is this like any of your ideas?
Thank you for bringing up this topic again -- I am often asked this question. When transcribing a document with the Nemeth Code as the primary code in use throughout the document, we are instructed to follow Braille Formats only when a topic is not discussed in the Nemeth code. The topic of tables is confusing because we are instructed to follow Braille Formats for the construction of tables. Nemeth code rules still apply to the items within the table, however. My advice which you copied from last summer comes directly from NC §57 "Omissions" which gives us directives regarding a blank space that means "information is missing": "When ... a blank space is employed in ink print to denote omission, the general omission symbol must be used in the transcription."
Thank you for your clarification and suggestions.
Your first citation, 22.6.4 is designed for a glossary WITHOUT samples, so that won't work here and it therefore it doesn't apply. That leaves your second citation 22.6.5, treating each entry as a cell-5 heading. There are no specific guidelines for the cell-5 entry word situation when a translated glossary is involved, so I will offer suggestions based on guidelines that do offer some coverage and general best practices in foreign language braille.
Each English entry word is cell-5 with the complete English entry given, including the diagram, if any. Follow each English entry with the corresponding Spanish entry. Treat each Spanish entry word as a cell 7 heading. I assume all the diagrams will be tactile graphics. Repeat any translated diagrams, such as the diagram for the entry area. Do not combine translated labels because that will create a cluttered graphic and the language shift will not be clear to the reader. Also, that does not accurately convey with print layout. So repeat the Spanish diagram with Spanish labels. In the case of diagrams for axis and base, that appear to be identical in English and Spanish, do not repeat the diagram in the Spanish entry, but add a TN referring to the English entry for access to the diagram, something like TN See English entry for axis to access the diagram.
Transcriber's notes are always and ONLY in contracted English. Guide words are English.
A braille arrow (mathematical symbol) is not appropriate here. To avoid having to spur many arrows, I suggest replacing the arrow with an embedded transcriber's note, using a word that describes what the arrow means. In this case, ..becomes.. will do the job. You will need to explain your treatment of the print arrow on the Transcriber's Notes page.
Thanks again. I've got it now!!
The answer is yes. Show the print page number just as you would any other print page, including the page turn indicator when you get there, right there in your table of contents listing. It looks very strange at first. Don't use inclusive pages--just the actual page number itself.