[kdejute]

Shelley,

Please let me preface with: There is no written-in-stone answer to your questions.

1. If the main stem is in 1-5 with the lettered problems in 3-5, I would suggest treating the "Solution" and "Explanation" as additional paragraphs within a subitem, thus formatting them in 7-5.
2. The most straightforward approach to transcribing what comes after "Solution:" and "Explanation:" is to follow print, i.e., use an underscore after "Solution:" and nothingness after "Explanation:".

–Kyle

[kdejute]

Keith,

Orbital names such as 1s, 2s, 2p, etc. do not require Nemeth Code. In addition, we do not retain italics for the letters in orbital names. As you say, wherever a superscript is included, Nemeth Code is certainly required (with italics still ignored).

–Kyle

• This reply was modified 5 years, 8 months ago by kdejute. Reason: answer confirmed; language changed to reflect that

[kdejute]

Good day, Tung!

I had no trouble seeing your simbraille, and I appreciate your posting here with both the print and a proposed transcription.

As I understand it, your questions are:

1. Is it appropriate to use a transcriber-defined typeform for circled words?
2. Is it appropriate to use bold within a problem arranged spatially for calculation?
   • If not, then how might I transcribe numbers that are somehow set apart/emphasized in a problem arranged spatially for calculation?

 

1. Yes, I support and condone your use of a transcriber-defined typeform in UEB for circled text. This is in line with Braille Formats 2016 §5.9.
2. Although it is not directly supported by the Nemeth Code to use Nemeth bold for numerals within a spatial problem, your solution (including alignment which puts each bold indicator and its associated required numeric indicator in columns of their own) does seem readable and accurate.

Yes, I too would use the Nemeth Code's general omission indicator for a blank "box" in a problem when that box indicates a missing numeral (NC §58).

One additional note: The separation line which appears in an addition problem must be made one cell longer at either end than the overall width of the rest of the arrangement. (NC §178.c) So, I would make the line above the total in your example one cell longer.
Conversely, the column separation lines for "Tens" and "Ones" columns should be just the width of the column they head (BF2016 §11.4.2.b) [with the possible exception of letting your "Tens" column heading and separation line begin in cell 1].

Again, thank you for posting; and thank you for your time!
–Kyle

[kdejute]

Shelley,

I would look to both the example under Nemeth Code section 178.g and the text of Nemeth Code section 27.g for reasons to *not* use the English Letter Indicator in problems involving variables arranged spatially for calculation. That still doesn’t give you language that says not to use the ELI for variables in a problem arranged spatially, but I think those pieces effectively define the *lack* of a requirement for ELIs in problems arranged spatially for calculation.

As always, thank you for the question, and please do not hesitate to post follow-up questions/concerns.

–Kyle

[kdejute]

Cheryl,

That's a considerate follow-up question.

In fact, in many print environments the hyphen and negative sign are the same. Both the print and the braille reader must use context and experience to determine whether the symbol they're reading is a minus or a hyphen.

Section 45 of the Nemeth Code (on page 51 of the "green" book) says, "§45 Hyphen: The hyphen is represented by the same sign of ink print as the minus sign. Since the corresponding braille symbols also coincide, a minimum of decision-making in this regard is required of the transcriber.  ..."

–Kyle

[kdejute]

Hmmm ... I do not see the significance of the lines you describe. Perhaps the publisher’s website includes an “About the Book” section or other commentary that might shed light on this design.

If the lines aren’t mentioned, and you don’t find a pattern of which tables have which lines, I would be tempted to ignore them.

–Kyle

[kdejute]

I expect it’s quite alright to have upper-cell numbers in Nemeth and UEB, even having a mix as in your example. Bending over backwards in order to have every number of a numeric key in Nemeth Code is unnecessary and potentially confusing to the reader – It might make them ask, “Wait!??! What’s mathematical about this??”

So, it is not necessary to treat the upper-cell numbers as Nemeth Code when listing the keyed labels. Thank you again for the question.

–Kyle

[kdejute]

Trumbull,

I hear you! In fact, as I understand it, you may use upper-cell numbers in a Nemeth numeric key.

The Guidance says that we may not use UEB symbols within Nemeth Code context, but upper-cell numbers within a Nemeth numeric key are in fact Nemeth Code symbols from the Nemeth Code even though they have the same dot configurations as UEB numbers.

So, make sure your key listing is clear, including, as always, using the same symbol in your key listing and in the graphic/table, and you should be good to go.

Sense make?

–Kyle

[kdejute]

Thank you for the question! I understand the temptation to use the UEB modifier for the tilde over the n; however, UEB symbols may not be used within Nemeth Code (other than the transcriber-defined shape indicator). So, for piñatas you must use the dot 4 that indicates an accent on the following letter, as shown below.

_% #18 kazoos./6 pi@natas
  .k #3 kazoos per pi@nata _:

Please note that in the above:

1. the numeric indicator is required before a number that is preceded by a blank cell, and
2. the equation "18 kazoos ÷ 6 piñatas = 3 kazoos per piñata" will not fit all on one braille line and so must be broken before the symbol of comparison.

I commend you on your decision to include within the Nemeth Code switch indicators the whole expression "18 kazoos ÷ 6 piñatas = 3 kazoos per piñata".

Braille on!
–Kyle

[kdejute]

Cheryl,

A transcription of the items you mentioned is in the attached files; one is a BRF, and the other is a screenshot of that BRF.

You might note that in item 10 the complex fraction starts on a new line in the runover position; this is because such a layout allows the whole complex fraction to appear on one braille line.

Please do post again if you have follow-up questions or concerns.

Cheers!
–Kyle

Attachments:

You must be logged in to view attached files.

[kdejute]

Susan,

I would suggest following the Guidance to the letter, thus putting the opening NC indicator on a line by itself in cell 1.

Aaand, would you be giving the braille reader inaccurate information if you positioned the opening NC indicator in cell 3? No. So, I would suggest though not *demand* as I said above.

Thank you for the question!

–Kyle

[kdejute]

Sounds good. Thank you, Michael.

[kdejute]

Candace, thank you for the question.

An abbreviated function name, like the “log” in your examples, with a subscript must have a blank cell following the end of the subscript.

See Nemeth Code section 79.d, esp. the second sentence and including example (3) and also section 77.iii including example (8).

The Nemeth Code 1972 Revision WITH UPDATES (that can be found on the Nemeth page of BANA’s website) is the latest Nemeth Code for math and science.

For further discussion, you may also check Lesson 14 of the Provisional Revised Nemeth Course Manual (esp. sections 14.2 and 14.9).

Does that answer your questions? Do you now have follow-up questions? ☺️

–Kyle

[kdejute]

Niiice.

Firstly, I would remove all the $ from the content of the budget and just mention their presence in a transcriber’s note. Then, the only thing for which you have to use Nemeth Code is the expression and pair of parentheses after Cash Surplus.

Now let’s talk format. The first thing I’d want to try is keeping the related column layout by presenting the wide table across facing pages. Even though that might take three pairs of facing pages (with page turns before Fixed Expenses and Cash Surplus), retaining the related column layout would likely make it easiest for the braille user to discuss the budget with print-using peers and teacher.

Alternatively, I think finding a list format that allows you to reflect print’s organization, without separating labels from values, could serve you well. Maybe cell-5 headings for print’s bolded headings, 1-5 for the first column entries (labels/row headings), and 3-5 for Monthly and for Yearly?

Maybe you could share here the clear and easy-to-reference transcription you create?

–Kyle

[kdejute]

Hi, LaVerne!

Thank you for the question. No, you may not have different box lines.

If technical material immediately precedes a box that is all in Nemeth Code, begin Nemeth Code before the technical material preceding the box, and terminate Nemeth Code after and outside the box.

Also:

If technical material follows immediately after a box that is all in Nemeth Code, begin Nemeth Code before and outside the box, and terminate Nemeth Code after the technical material following the box.

Lastly, if technical material both immediately precedes and follows a box that is all in Nemeth Code, begin Nemeth Code before the technical material that precedes the box, and terminate Nemeth Code after the technical material that follows the box.

–Kyle

[Author]

Posts