kdejute
Forum Replies Created
-
Posts
-
Thank you for your question!
First, radio buttons: I see your reasoning in using the UEB circle shape symbol or a Nemeth circle shape for print's radio buttons depending upon which code you're in a the time. Might I suggest that you create a UEB transcriber-defined shape (Rules of UEB section 1.7.2), identify it as a "Radio button" on your Special Symbols Page, and use that for a radio button everywhere it appears? This would give your braille reader the same symbol every time a radio button is used in print.
Second, your indention for the "(1)" (and for the answer choices that follow it) is spot on. It's really your only option to indent it in 3-5 as a sub-item to item #5, since you must follow Nemeth formatting rules (and the answer choices are sub-sub items to #5 and also indented in 3-5.).
Lastly, the "(1)". I do not see why this has to be in Nemeth. It is not an enclosed list, because it only contains/consists of one item, and it is otherwise a simple number that can easily be read in either UEB or Nemeth Code. So, I would say you could leave UEB in effect in item #5 from "in words is" through the end your item #5. For item #17, I think your current Nemeth code "bubble" is appropriate.
Again, thank you for your question (and for the beautiful document). Please let me know if anything here is incomplete or unclear.
–Kyle
Trumbull,
My official recommendation is to follow BRAILLE FORMATS 2016 for note indicators.
Although the Nemeth Code does provide specific rules for note indicators, they are not mathematical/technical, and the Nemeth rules on notes do not serve a practical purpose in a UEB environment, so let's follow the Formats rules, barring unforeseen circumstances.
–Kyle
Trumbull,
That is an excellent question. I am inclined to follow Nemeth Code closely for the construction of the note indicator, since the Nemeth Code does provide specific direction for formation and placement of a note indicator. However, I am not certain that is what we should do. Please let me check with others and get back to you.
–Kyle
Good day, Mary!
You're right that at the least each "E" standing alone in your example needs a grade 1 symbol indicator.
I like this suggestion you've made of enclosing your table in a grade 1 passage. If you do so, be sure to insert the "dot locator for use" (Rules of UEB section 3.14) along with your grade 1 passage indicator and grade 1 terminator when they each appear on a line by themselves.
A .BRF is attached with a transcription of the snippet you provided.
Cheers!
–KyleP.S. You may post your UEB questions, even about technical material, in the UEB thread of this forum.
How sneaky this print set-up is! Good find. Good question.
Nice transcription. I can hardly make any suggestions. Only double-check that all of your switch indicators are formed correctly and paired.
Again, nicely brailled, and thank you!
–Kyle
Thank you for your question.
In an EBAE-Nemeth environment, the correct transcription of "Connected3" is ⠠⠒⠝⠑⠉⠞⠫⠼⠒
It is tempting to think that Nemeth Code §77 (about non-use of a subscript indicator when a numeric subscript follows a letter) applies to this example. However, since the word "Connected" is not "an abbreviated function name or a letter which has a separate identity", NC§77 does not apply.
Again, thank you for your question; it certainly struck sparks in my brain!
–Kyle
Good day, Tung:
I appreciate your question. I believe you may be able to get the print and [sim]braille material without registering for an event that you cannot attend.
Please send a message to NBA's national office at nbaoffice@nationalbraille.org so that they can help you get everything you need.
–Kyle
Additionally, thank you for giving your post such a specific title. That helps to make the forum more searchable, and it helps me to organize my thoughts. Specific titles for posts are a huge boon!
For 99.9% of transcriptions, I see no reason to terminate Nemeth mode because of a print or a braille page break.
Thank you for the follow-up.
The answer has three parts:
- "yd" is not a short-form combination and so would not require an ELI regardless.
- A short-form combination like "yr" (for "year") would need an ELI according to Nemeth Code
- If "yr" (or a similar abbreviation that corresponds to a short-form combination) were used within Nemeth Code switch indicators, then you are correct that we should use the ELI with it when it is in a "single letter" circumstance as defined by the Nemeth Code.
The Provisional Revised Nemeth Course Manual is currently hosted on NFB's website. The following link should take you to a page from which revision logs, front matter, table of contents, Lessons 1-8, and an appendix – in both PDF and BRF files – are available.
https://nfb.org/math-transcribing#9
[It is possible that clearing your browser history will allow you to see the most updated version of the NFB webpage.]
Thank you for the question!
–Kyle
Good day, Susan!
A hyphenated expression part of which must be in Nemeth Code cannot be divided by code switch indicators, including the single-word switch indicator, so you should consider the whole "fraction connected to a word by a hyphen" as one element (and uncontract the word).
Thank you for this question, on which I needed clarification as well.
–Kyle
Lennie,
Thank you for your question.
I agree with Violet227; mathematically "15 over 3" and "fifteen thirds" have the same value.
If you are transcribing the print you attached (thank you for including the example), you could use either the simple horizontal line (a series of dots 25) or the spatial fraction line (a series of dots 25 preceded by the opening fraction indicator and followed by the closing fraction indicator) between the numerator "15" and the denominator "3".
–Kyle
Tung,
If in the text you are transcribing there is no distinction in meaning between a superscripted and an unsuperscripted negative/minus sign, then I would indeed, as you say, use (substitute all) with the regular minus sign and mention that in the Transcriber’s Notes page.
In response to your second question, if you follow the as-yet-unpublished updates to the our Guidance (which Dorothy Worthington talked about in her recent NBA webinar, "Update to the Guidance for Transcription Using Nemeth Code within UEB Contexts. What Has Changed?"), then I believe you could follow the new item #6 under Additional Guidelines and not use Nemeth Code at all for "Point R", "Point T", etc, because they are single-letter names of geometric items.
Thank you for your, as always, astute questions.
–Kyle
