[kdejute]

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

[kdejute]

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

 

 

[kdejute]

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

[kdejute]

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!

[kdejute]

For 99.9% of transcriptions, I see no reason to terminate Nemeth mode because of a print or a braille page break.

[kdejute]

Thank you for the follow-up.

The answer has three parts:

1. "yd" is not a short-form combination and so would not require an ELI regardless.
2. A short-form combination like "yr" (for "year") would need an ELI according to Nemeth Code
3. 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.

[kdejute]

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

[kdejute]

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

[kdejute]

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

[kdejute]

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

[kdejute]

Jeff,

Thank you for your questions. I would like to answer them in reverse of the order in which you asked them.

First, in response to your question #3: It is true that the Guidance states Nemeth symbols are not to be listed on the special symbols page (SSP). It is also true (and the upcoming changes to the Guidance, which are introduced nicely in Dorothy Worthington's webinar from 7/20/2017, clarify this) that the "opening Nemeth Code indicator" and the "Nemeth Code terminator" are UEB symbols and should be listed on the SSP according to braille order. Also, it is recommended that the "Single-word switch" Nemeth symbol be listed on the SSP, under its own heading (e.g., "Nemeth Switch Indicator") because it is new but not a UEB symbol.

In response to your question #2: I agree with your view that within a list or series of short exercise items it is disconcerting to have an opening Nemeth Code indicator placed on a line by itself. What I would do with such an indicator is to place it after the item identifier, just before the affected material. For example:

⠼⠙⠊⠲⠀⠼⠃⠙

⠼⠑⠁⠲⠀⠸⠩⠀⠏⠀⠨⠅⠀⠉⠊⠞⠽⠄⠎⠀⠄⠄⠄⠀⠸⠱

In response to your question #1:

You're right that it is preferred to use fewer instead of more Nemeth switch indicators. Still, it is of course our overarching goal to make the text as clear and intuitive as possible. So, if having a few more switch indicators makes the content more readable, then those switch indicators are well used.

I agree that the first two options you provided in your question #1 are both correct. I would argue that the second (lines 07-10) is more reader-friendly, because it allows each item to be read individually (i.e., the content of item #26 is not dependent upon a switch indicator that is within item #25). I cannot say that the third option you provided (lines 13-16) is incorrect. Nonetheless, allowing Nemeth Code to remain in effect for a series of unmodified numbers and/or letters is possibly overextending application of the Nemeth Code.

Finally, if you did have something like

23. 9.8
24. Nikola Tesla
25. 1 G = 10⁻⁴ T

where one item/line of UEB material occurs between items/lines Nemeth material, I would suggest terminating Nemeth Code at the end of item #23 and then inserting an opening Nemeth Code indicator following the item identifier "25."

Again, thank you for your questions.

–Kyle

[kdejute]

Kimberly,

Thank you for your question. Please see the attached .BRF, in which I have transcribed a portion of the print sample you shared with the following judgment calls:

• Use Nemeth switch indicators as needed within each item or subitem
• When a [sub]item consists of  a series of numbers, include the whole series in switch indicators if one number in that series requires switch indicators.

Please do let me know if this sample and brief commentary does not fully address your question and/or if you have follow-up questions.

 

Attachments:

You must be logged in to view attached files.

[kdejute]

Tung,

I have the answer!

Although my information was correct at the time the spring Bulletin was published, it is now out-of-date.

Recent changes (which are not even published yet on BANA's website) to the Guidance for Transcription Using the Nemeth Code within UEB Contexts change how measurement units are included or excluded from Nemeth switch indicators.

So, the content of "AN INTRODUCTION TO BRAILLE MATHEMATICS, Using UEB and the Nemeth Code, Provisional Online Edition 2017" is correct and up-to-date. And the summary statement from the spring Bulletin article should be changed to:

When next to a number that belongs in Nemeth Code, a related abbreviated measurement unit is transcribed within Nemeth Code, but a container or amount that does not have a fixed definition, whether spelled out or abbreviated, is not.

in addition to examples and other content of the article being updated.

Thank you again for pointing this out!

Please watch BANA's website for the updated Guidance document to be published.

–Kyle

[kdejute]

Greetings!

I would use Nemeth Code for this example. However, I would not include the keystroke indicator (and its terminator), because it implies that what is contained within is one button. If you were going to use keystroke rules for this sequence, you'd have to use a separate keystroke indicator (and terminator) for each character.  i.e. =, I, N, T, (, R, A, ...

I would choose Nemeth over UEB for this since it includes a sign of comparison as well as a sign of operation. I would stay away from CBC since UEB and Nemeth-Code-within-UEB have [for practical purposes] replaced it.

Thank you for your question!

–Kyle

[kdejute]

Tung,

That is a good question. I am looking into it, and I will let you know once I find out more.

Thank you.

–Kyle

[Author]

Posts