• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ChordPro: Chord Localization
#1
I really appreciate the new "Chord Localization" feature. I always missed that. Is it already implemented? I only noticed the settings entry to configure it but it seems to have no effect at all.
first language: German
Acer A1-830, Android 4.4.2 - HP x2 210 G2 Detachable, Win 10 1803
www.moonlightcrisis.de - www.basdjo.de - www.frankenbaend.de


Reply
#2
It is implemented. I followed the OnSong settings for localization as described here: 
  • Default displays chords as capital letters from A through G with flat or sharp symbols as needed. Minor chords are denoted by a lowercase "m" to the right of the chord.
  • Čeština displays chords in a convention familiar with the Czech language. This displays "B" as "H" and "Bb" as "B". In addition, minor chords are denoted by lowercase "mi".
  • Deutsch displays chords in a convention familiar with German-speaking people. This displays "B" as "H" and "Bb" as "B".
  • Scandinavian displays chords in a convention familiar with Scandinavian-speaking people. This displays "B" as "H" and "Bb" as "Bb".
Is some of that not working for you, or were you expecting different behavior?

Mike
Reply
#3
What you describe is what I expect, but none of them work.
Is something wrong with my ChordPro file?


Attached Files Thumbnail(s)
   

.pro   Chords+Localization1.pro (Size: 271 bytes / Downloads: 2)
first language: German
Acer A1-830, Android 4.4.2 - HP x2 210 G2 Detachable, Win 10 1803
www.moonlightcrisis.de - www.basdjo.de - www.frankenbaend.de


Reply
#4
Looks like a mistake on my part. If you transpose, the localization is correctly handled, but if the song is in the original key, it does not modify the chords that are displayed. I'll get this fixed.

Thanks,
Mike
Reply
#5
I'm going to have to think about this one a bit, because if Bb is B, but you put Bb and B in the same file, what should be the correct handling? Should it treat Bb as B, but then the B that is already there is actually a Bb? So they become identical? The transformations can lead to odd results if you mix things like that.
Reply
#6
What would happen if the process was to transpose to another key then transpose back using the localization?
Dell Latitude 13.5" 2-in-1 Win 10
Samsung Note Pro SM-P900 12.2 Android 5.0.2
Asus TF700T, os = CROMi-kk_R1 KitKat-4.4.4r2-CM11-US DEODEX, Based on Android 4.4.4
Nook HD+ OEM
Reply
#7
I'm following those rules listed above closely now. If I encounter something that doesn't match the rules, I transform it to that (i.e. if Bb is B and I encounter Bb, it's transformed to B, and if I encounter B, it's handled as a H). I think this is the expected behavior.

Mike
Reply
#8
I have a similar thread in the forum of the ChordPro reference implementation. Maybe you want to take a look:
https://groups.google.com/forum/#!topic/...rd7kq6CC7k

The reference implementation provides complete flexibility even for localization of the input file. I think this is not required.
I would be fully satisfied if I had to write the chords into the file in todays standard format (A Bb B C) and they are displayed in their localized form (A Bb H C).
first language: German
Acer A1-830, Android 4.4.2 - HP x2 210 G2 Detachable, Win 10 1803
www.moonlightcrisis.de - www.basdjo.de - www.frankenbaend.de


Reply
#9
(05-13-2019, 10:51 AM)Skip Wrote: What would happen if the process was to transpose to another key then transpose back using the localization?

Neither localization nor transposing should ever change the content of a ChordPro file. The question is always how a certain content of a file shall be displayed, so "transpose back" is not necessary to be discussed.
To display a transposed song the localization setting shall be respected.
If sharps or flats are used for transposing is a user decision. A setting for this already exists in the transpose dialog.
first language: German
Acer A1-830, Android 4.4.2 - HP x2 210 G2 Detachable, Win 10 1803
www.moonlightcrisis.de - www.basdjo.de - www.frankenbaend.de


Reply
#10
Here's my test file for (traditional) German and Scandinavian. Chords are in 'Common' notation, the lyrics line contains the expected localized result.


Attached Files
.pro   Chords+Localization2.pro (Size: 609 bytes / Downloads: 2)
first language: German
Acer A1-830, Android 4.4.2 - HP x2 210 G2 Detachable, Win 10 1803
www.moonlightcrisis.de - www.basdjo.de - www.frankenbaend.de


Reply


Digg   Delicious   Reddit   Facebook   Twitter   StumbleUpon  


Users browsing this thread:
1 Guest(s)


  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2019 MyBB Group.