Alphabet - limit not to latin A-Z

[MorrisJobke]

@tanghus said in #79

Just curious: What about the simple case of not being limited to the English A-Z, and the not so simple non-latin alphabets?

cc @jancborchardt @butonic Opinions?

[j-ed]

Some ideas concerning the menu bar. At first I don't like the idea to place the alphabet menu bar at the right border which scrolls away when scrolling through the audio data. The menu bar should be at a fixed placed at the top or left border. Usually humans in our hemisphere are selecting data from the left to the right and from the top to the bottom.

1. If we stick to a fixed alphabet menu and due to the fact that there might be ABCs which we don't know wouldn't it be the best solution to use the English one as default and add translation strings covering all other languages? By reading these strings and looping through the list of characters would allow us to dynamically create the required menu. Additionally the array should be extended by the numbers 0 ... 9 which are not yet covered. In the case that characters would be found during the audio import, these should e.g. be collected under on key others etc., e.g. abc_array="0 1 2 3 4 5 6 7 8 9 0 A B C D E ... X Y Z"
2. A second solution would be to dynamically create a compressed and sorted menu bar based on the imported audio data. This would allow to use less space for the menu and optimize navigation speed. If e.g. only artists starting with the characters "A B F K L Z" are found this would be the menu layout too.

[MorrisJobke]

@j-ed Thanks for your response :) The menu is fixed and don't scroll away.

Let's get the UX guru in here: cc @jancborchardt

[glouvigny]

Hi, beside the letter bar that could be great to handle non latin languages characters globally.

Example for japanese : http://llau.me/3_

However, french accents seems to be correctly stored : http://llau.me/3-

I'm using a MySQL database, and ocmusic* tables use a "utf8_unicode_ci" charset