Julie Sumwalt
Forum Replies Created
-
Posts
-
And apologies for *my delay! Thank you for the answer. At least I know I'm not the only one who's confused!
Julie
Hi,
I'm still wondering about contracting "Wilhelmshaven". I assume it's pronounced "Wil-helms-haven" or "Wil-elms-haven", which would mean the (sh) contraction would not be used. Can you confirm or explain?
Julie
What about 10.11.12, about the aspirated h? I assume "Wilhelmshaven" is not pronounced "--shaven".
Julie
Wow, such a thorough response! Thank you! So, could I take any of these routes and then apply for certification? How and where would I do that?
Julie
I am also looking for a proofreader, one who is Nemeth certified, works with a copyholder, and knows the ins and outs of Nemeth within UEB contexts.
Julie
Great! Could we talk about it offline? jsumwalt@att.net
Julie
Hi Candace,
We are to follow print for capitalization, yes. But the use of small caps is not capitalization. Capitals may be used within small caps, but small caps themselves are not capitals.
Small caps need to be shown where distinction or emphasis is required for the understanding of the text. “Foreword”, etc., are already set apart with a blank line and indention. Further distinction is unnecessary. Nor do these entries need to be emphasized in any way. Therefore, the identification of small caps is not shown. Because of all this, Braille Formats 2016 2.10.8 says to use title case for small caps in a table of contents.
The example of PT109 in UEB 9.6.1 is showing an abbreviation in small caps. As explained in that text, abbreviations in small caps are generally transcribed with capital indicators. The following example in UEB 9.6.2 is showing an example where distinction is necessary. The heading must be distinguished from the surrounding text. Once it’s decided that distinction or emphasis must be shown, THEN the transcriber should follow print. Italics, boldface, underlining, or script indicators are not options here because print did not use those typeforms. A transcriber-defined typeform indicator must be utilized.
The forum post from 2010 was pre-UEB and should not be referenced. Also, be careful about treating the lesson manual as a rule book. While it has many useful examples and explanations, it is not a definitive source for transcription. Do follow it for your manuscript submission, however.
“(cont.)” in the table of contents does not need to be in transcriber’s note indicators because the writers of Braille Formats 2016 decided that the existing parentheses were sufficient. Adding TN indicators would mean five cells of indicators on either side of the abbreviation. See BF2016 2.10.10.
Braille on,
Julie
Hi,
There is no official symbol for the per mille sign in UEB. UEB Section 3.26.1 says to use a transcriber-defined symbol. Keep in mind that transcriber-defined symbols are used in braille order, not according to frequency or preference.
Braille on,
Julie
Hi Susan,
I don't know why my request to see the print posted twice....
UEB 4.2.5 refers to not just any grouping indicators when a modifier applies to more than one letter, but specifically to braille grouping indicators. Indicators of any kind do not exist in print. Braille grouping indicators are not interchangeable with existing print parentheses, brackets, or braces. The parentheses on the outside do not tell the reader that the modifiers apply to more than one letter. You need to show both in your transcription, as shown below. (The quotation marks should be dot 5s.) This same message is repeated in the attachment with the correct simbraille dots.
"<T@-<OO>-L@-<OO>Z^.B">
Braille on,
Julie
