Add !!!title: @{OTL}, op. @{OPS}, no. @{ONM} for English titles in VHV
#18
Comments
|
I fixed one inconsistency I noticed in my OTLs, but have left the others for now. This is an issue that I will make a decision on before I revise the corpus. I agree with you about including keys in the titles, though I think keeping information discrete and on separate lines is also useful as it gives a user the choice of what information they want. It also seems to me that having OTL above OPR can be more useful as it is visually easier to immediately see the title of the current file without having to scan multiple lines. Let me know your thoughts. |
Reference records do not have a prescribed order, so there is no problem in doing that. Traditionally the larger group names come before the smaller information, but there is no special reason for this other than it matches the order it would be seen in print. For computer processing it will make no difference at all. Here are the Humdrum files encoded at OSU by David Huron and his students: https://kern.humdrum.org/cgi-bin/browse?l=/osu which I use a prototypes for organizing reference records in a file. An example would be the Well-tempered Clavier, such as: https://kern.humdrum.org/cgi-bin/ksdata?l=osu/classical/bach/wtc-1&file=wtc1f01.krn&f=kern |
|
It is important to rename files such as |
|
Regarding titles such as "Etude", "Prelude", "Mazurka" which are generic genre titles, it is particularly useful to include the key after the generic title. Here is the IMSLP list for the Op. 8 etudes, for example: 
Otherwise it is difficult to locate the desired Etude purely by its number in the opus. Computer reading of the title to identify genre should not be done, since the title can be spelled in several ways, such as "Study" in English, or "Étude" in French (adding the accent). Instead, the genre is encoded for computational use in the Here is the wikipedia entry for one of the etudes: https://en.wikipedia.org/wiki/%C3%89tude_in_D-sharp_minor,_Op._8,_No._12_(Scriabin) Notice that it is qualified with the key of D-sharp minor, since "Etude" by itself is ambiguous, since all of the works in Op. 8 have the same name. The titles are for use by humans. For computer processing, the key designations are found in tandem interpretations within the data, such as Related to this, there is an informal reference record called Here is a current view of the titles in VHV: 
To enhance the title, you can add this reference record: 
The structure I would not bother with splitting out the key information for the title, but if you want to do that: Which produces the most informative title in VHV: 
I would put the |
|
Related: Op. 59, no. 1 does not have a title: AGN records should be standardized and not use accented characters, since they are useful for finding genres across repertories. To a certain extent it is up to the encoder, but Similarly for Op. 59, no. 2: The OTL is for humans to read, and the AGN is for computer processing (both should be present). |
|
Also I note that Op. 8 Etudes. nos. 1–6 do not have key designations (such as
Also preludes 4 and 14 from Op. 25 are missing key designations. https://imslp.org/wiki/24_Preludes,_Op.11_(Scriabin,_Aleksandr)
|
|
File names: This issue is fixed per push on May 18. |
|
Key designations: Key designations will be added to genre titles during second round of revision. |
|
!!!title record: Will not add. |
|
Languages in OTL and AGN: OTL titles will be updated to use Scriabin's preferred French across all files. AGN genre designations will be updated to use only English across all files. Updates will be made during second round of revision. |
|
It is preferable to have AGN in English (unless the common term used in English is actually French such as Etude instead of Study (but preferably not Étude). The reason is that this field is for computer processing of the file, and in particular with a combined set of files from multiple sources. For example to count the notes in all waltzes from multiple repertories containing different primary languages. census -k $(grep -lri "^\!\!\!AGN:.*waltz")If you have AGN in various languages, you would miss waltzes that are not described in English. The best you could do would be to check for the various terms for waltz to identify them, and/or guess at the names used in the AGN field: census -k $(egrep -lri "^\!\!\!:AGN:.*(waltz|walc|valse|walzer|valzer||vals|keringő)"
|
|
I have updated AGN (on the phase2 branch) to only use English; "Poème" is now "Poem" and "Danse" is now "Dance." For !!!OTL@@FR, what in your opinion is the best way to encode accented characters (è, é, á, and so on). I don't think Vim even let's you type them in to a file the way that the mac UI let's you type them in a browser or document. I've also worked with files that have accented characters that don't convert properly when you convert the file (e.g., a txt file of references from PsycInfo). |
|
For è, é, á, and so on should be encoded with UTF-8 (Unicode). This is the default character encoding for Macs, so you don't need to do anything special. There are both single-character forms of the letter and the accent, as well as compositing cases which are composed with two characters: such as e and `. Preferably the latter should be used (it is hard to tell the difference unless you look at the bytes for the letters, and in any case it is unlikely to create the latter while typing the letters in a Mac (but copy-and-paste from various sources on the web may insert the compositing accents). I don't have problems typing them in vim (on mac at least, but I don't remember having problems on linux as well). To enter in vim on macs, hold down the option key, then press the accent character and then the letter. For example For For For capital letters it is exactly the same: You need to be using the US keyboard setting (probably you are already doing that). And alternate way is to use the French keyboard layout (but that layout is quite different from the US layout). To allow French layout, you go to system settings and the keyboard layouts and then add a new language on the left in this window (I have US, German, and Polish keyboard layouts set up): 
When you have multiple layouts, you will see a box in the top rightish side of the screen: 
You can set the keyboard layout in the drop-down list that appears when you click on the language code (
There can be many problems, so it is difficult to say what the problem is (unless there is a website with example text for me to copy and test what is happening. In general the problem would be that the characters are not encoded in UTF-8 (and the webpage has a line in the HTML saying what the character encoding is, but when copy-and-pasting, the literal bytes are copied instead of converting them to UTF-8. An alternate system that I used to do is to use HTML entity encoding. I would find that acceptable still however. |
bel28kent
changed the title
!!!title: @{OTL}, op. @{OPS}, no. @{ONM} for English titles in VHV
|
Most issues fixed in some previous commits. New issue for !!!title. |
It would be useful to adjust the reference records for these files:
scriabin-op19_no01.krn
scriabin-op19_no01.krn
scriabin-op02_no01.krn
Note: it might be nice to include the key in the title of generic titled pieces (etude, prelude, mazurka). Such as
Etude in C# minorin this case.scriabin-op2_no01.krn
scriabin-op2_no02.krn
The files
scriabin-op5_no01.krnandscriabin-op5_no02.krnshould be renamed to add a0inop5.The text was updated successfully, but these errors were encountered: