More-Than-Solitaire/Tabs-Lite

Feature Request: Add the ability to choose between English Chords and Italian Chords.

Opened this issue · 10 comments

It would be great if it would be possible to choose between chords in English Notation (A, B, C, D) or Italian/Latin Notation (Do, Re, Mi, Fa). It would be very useful for those who are not used to English Notation. Thanks!

Hi there, this is a super interesting idea! I've never heard of playing guitar with Italian style notes, but that might be something I'd consider adding. I have a few practical questions though:

  • How do you handle special chords (think minor, suspended, add 7, etc)? For example, how would Am be translated? Or Asus or Am7?

  • How do you handle sharps and flats in this notation? E.g. A# or Eb.

Hi, thanks for your prompt reply!

⚠️ I just want to clarify one thing ⚠️
Latin notation is generally used for piano chords, not guitar chords. You'll understand why when you read about the sus chord below.

Anyway...
You can transliterate the chords this way:

A -> La
B -> Si
C -> Do
D -> Re
E -> Mi
F -> Fa
G -> Sol

For # and b it's the same as in English notation. For example:

A# -> La#
Eb -> Mib

Finally, for chords like Am and Am7, here are the rules

Amaj (usually A) -> La or La+.
Amin (commonly Am) -> La-
A7 (A major 7) -> La7 or La+7
Am7 (A minor 7) -> La-7

⚠️ The sus chord is untranslatable because roman notation (also called latin notation) is used exclusively for piano chords, which usually don't have suspended notes.

In the case of a sus chord, you can "translate" it into a simple major chord for piano chords. For example:

Asus -> La
Asus7 -> La7

For guitars, you can keep the sus instead. Like this:

Asus -> Lasus
Asus7 -> Lasus7

But none of the guitarists use Latin notation.


So, as you may have noticed, cause of the sus problem, adding Latin notation would only be useful for piano, not guitar.

Idk if you want to add it anyway, but it would be very useful for people like me who play piano and find your app incredibly helpful!

Hope this helps, thanks in advance for your patience and dedication. If you have any other requests just ping me!

Hi thanks, that clarifies things. I think this would be a separate feature than #66 , probably in the app preference menu. I'll consider adding this next set of updates that I do (but it may be a while since this is a side project for me)

Hi! Thank you for considering adding this feature in the next updates of the app.
I hope to see it as soon as possible but I'm in no hurry. In fact, it'll force me to learn English notation 😉.
Have a nice day! Love from 🇮🇹

Hey by the way, if you'd be willing to help with translations I'm looking to translate the user interface into different languages. Take a look at #113 if you're interested!

Sure! I'll translate the files as soon as possible 😉. Are the files openable on Android Studio? For me it's easier to translate the strings, cause of the Translation Editor.
Instead, what about opening a crowdin page?

Good suggestion, hadn't heard of that service before. Here's the translator invite link: https://crowdin.com/project/tabs-lite/invite?h=2cf642473a7398656da8bc4e1b26fff62082308

Hey! I just completed the Italian Translation of the app! You can check it out on Crowdin!
Hope everything is fine... I'll wait for the next update to check that everything is correct.
If you have any suggestion/correction/question just ping me ;)
Have a nice day!

Related issue: in some parts of Europe, B is usually written as H, as well as some other changes. Maybe there could be a setting to change the display of these chords. A potential issue with this is, that some tabs are already written in this notation, which might cause messed up chords and confusion.

There is a table in this Wikipedia article that shows all the changes. Hope it helps!

Related issue: in some parts of Europe, B is usually written as H, as well as some other changes. Maybe there could be a setting to change the display of these chords. A potential issue with this is, that some tabs are already written in this notation, which might cause messed up chords and confusion.

There is a table in this Wikipedia article that shows all the changes. Hope it helps!

Originally posted by @platinorum in #107 (comment)

I have two worries localizing chord names:

  • I wouldn't want to localize a chord name when the user didn't want that. I can't localize the tab text, so there will likely be cases where a (French for example) user wants to play a song and might prefer French UI but English chords to go with English lyrics. Also at this moment, I don't have a French localization for the rest of the UI so it would be strange to have French chords with an English UI and lyrics
  • Currently word wrapping is handled via monospace font and counting characters. Switching how many characters chords take will mess up spacing. This will be hard to correct for in any language that takes significantly more space since previous chords will start to run into the next chords.

The first issue can be handled by adding a manual setting rather than using localization, allowing the user to choose. The second could just be ignored (a few songs just wouldn't work correctly) or could be fixed by a more technically involved solution involving linking chords to a particular point in the next line.

Example format:

I {ch:C}heard there was a {ch:Am}secret chord
That {ch:D}David played and it {ch:Am}pleased the Lord