Transcription -- Key Designations was removed as being a discrete section of format-specific text. Review and add back in when DCRM(Music) is incorporated.
Text, including coding (Sept. 22, 2020):
0.5.18 Key designations
0.5.18.1 Transcribe accidentals (flat and sharp signs, etc.) directly following the key letters being modified. Do not insert a space.
Example:
A♭ major
0.5.18.2 If minor keys are represented by lowercase letters in the chief source, transcribe them as lowercase. Otherwise, record any letter(s) representing the key in uppercase.
Text:
Key designations
Transcribe accidentals (flat and sharp signs, etc.) directly following the key letters being modified. Do not insert a space.
Example:
A♭ major
If minor keys are represented by lowercase letters in the chief source, transcribe them as lowercase. Otherwise, record any letter(s) representing the key in uppercase.
Note: This issue was originally posted by @rarebkcat on 22 September as a comment on issue #36, which was created as a catch-all for issues related to future development. For ease of tracking, the comments have been moved to their own individual issues and tagged as "future work."
Transcription -- Key Designations was removed as being a discrete section of format-specific text. Review and add back in when DCRM(Music) is incorporated.
Text, including coding (Sept. 22, 2020):
0.5.18 Key designations
0.5.18.1 Transcribe accidentals (flat and sharp signs, etc.) directly following the key letters being modified. Do not insert a space.
0.5.18.2 If minor keys are represented by lowercase letters in the chief source, transcribe them as lowercase. Otherwise, record any letter(s) representing the key in uppercase. Text: Key designations
Transcribe accidentals (flat and sharp signs, etc.) directly following the key letters being modified. Do not insert a space.
Example: A♭ major
If minor keys are represented by lowercase letters in the chief source, transcribe them as lowercase. Otherwise, record any letter(s) representing the key in uppercase.
Note: This issue was originally posted by @rarebkcat on 22 September as a comment on issue #36, which was created as a catch-all for issues related to future development. For ease of tracking, the comments have been moved to their own individual issues and tagged as "future work."