Reply To: computer notation in UEB technical or Nemeth?

Home Forums Nemeth Code for Math and Science computer notation in UEB technical or Nemeth? Reply To: computer notation in UEB technical or Nemeth?


Thank you, Kyle! A few follow-up questions accompanied by an attachment with examples:

1. If I use Nemeth when the functions and commands are interspersed with mathematical expressions, can you confirm that the words would be transcribed without contractions, and italics would be omitted because the italics are used throughout, similarly to the way italics for variable letters are omitted whether they are unmodified in UEB or within Nemeth code?

2. When commands appear embedded in explanatory text, and they are not in contact with mathematical expressions, can I stay in UEB and use contractions and UEB typeform indicators (for instance, "To define matrices and perform Gaussian elimination using Maple, first access the LinearAlgebra library using the command")?

3. When the function names are all capitals (set NROW(i) = i.), would I just use the double capitalization indicator rather than capitalizing each letter? It does not seem like the individual letters have mathematical significance.

4. For alignment of the pseudo-programs listed in steps, would a nested list using as many levels of indention as there are in print, following the line breaks used print, be acceptable since it's not exactly itemized mathematical material? In the attached, there are three vertically aligned equations under Step 5. Would you ignore the vertical alignment and just put the second and third lines in cell 5 (because it is a third level indent, with Step 5 being a second level and Step 2 being the first level)?

5. There is a symbol := that is sometimes spaced and sometimes unspaced (examples of each in the attached). There doesn't appear to be a Nemeth code symbol for this. Would you use the literary colon followed by the spaced equals sign? or put the colon directly next to the equals sign?




Thanks much for your patience looking over this challenging textbook!


You must be logged in to view attached files.