Internationalization

VAP gets the first character from the list and uses ctype_alpha to determine if it is an alpha character. The php document for ctype_alpha mentions other languages, so I'm not sure that this doesn't work as-is. Have you tried it?

I have tried putting in "setlocale(LC_ALL, 'nb_NO');" directly in views_alpha_pager.module but still my characters are not recognized by ctype_alpha. (Where if anywhere does drupal core apply setlocale()?)
I have also tried other variations on the locale identifier.
I have also tried various settings under the Administration->localization menus.
Just now I am trying to confirm that my server actually fully supports my locale.

Apart from that, here is what I've tried changing so far. I may have lost track of linenumbers but i can make another pass and get the correct ones when this is done.
Note that I haven't replaced special characters with codes.

views_alpha_pager.module:
171: if ($item_display >= 'A' && $item_display <= 'Å') {
186: $where = "INSTR('0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZÆØÅ', $myfield) = 0";

The last lines generated a collation locale conflict error (something like that) from mysql until i changed collation for the sort table in mysql. It was latin1_swedish_ci. No errors with utf8_unicode_ci.

Sorry, I just confirmed that my server (incredibly!) doesn't support my locale / or doesn't support setting the locale.
This should be essential as it messes up a lot of things... And it's strange since my server is operated by a norwegian firm.
I will return here if it doesn't work after they've implemented the locale, otherwise this can be considered moot.

Ok, my server does have an available locale which should work. (Norway: One country, three locale codes, beat that...)
The problem now is where to apply setlocale(LC_ALL, "no_NO.UTF-8")? I tried setting it in the module, but still the same outcome as before.

I searched the drupal core, and have found setlocale applied only one place, includes/unicode.inc:43
Here it applies the locale "C" for ctype:

If this is the only place where the locale is set, ctype_alpha() checking with other locales is defeated in VAP.

I don't know how or where to proceed from here... Is this problem beyond the scope of VAP?

Was anyone able find a successful workaround for the Internationalization problem?
I'm trying to use it on node with Cyrillic title & getting a complete blank instead of an alphabet. Any input would be greatly appreciated.
Thanks.

I have the same problem with Cyrillic title.

Does anyone have a test case for me?

I cheated my way around this by copying theme_alpha_pager function from the module into my template and doing my changes there. I also added a complete alphabet so i could display empty letters as well. What i did to display the Norwegian character results was to replace the "_"-value with the needed characters. Here's the function as i use it:

If you don't want the full alphabet, i guess you can copy the function from the module (and rename it to your theme) and insert

before the foreach loop. If i wasn't procrastinating already i would test if this actually works. This is just a compromise workaround. My real problem was setting the locale properly, which I still don't know if I've gotten around. Look at comment #4 under this issue.

douggreen,

Here's an example: http://belmova.org/slovy2

I'm trying to get a list display items according to the following alphabet:
http://www.pravapis.org/art_belarusian_alphabet.asp

Please let me know if you need anything else.
I'd be more than happy to help with testing, etc.

Thank you.

I have a problem with Cyrillic too.

http://www.drupal.ru/node/13635

I’m also from Norway and encountered the same problem.
My suggestion is that Views Alpha Pager module should, as a quick fix to the problem, change line 176 in views_alpha_pager.module:

to

With the locale module it’s easy to replace "Others" it with for example "ÆØÅ" .

I have the same problem here in Austria. As mentioned in the initial post it is a problem in the German language.

But the sort works as follows (different, than mentioned above):

There are the basic 26 roman letters (lowercase: a to z / uppercase: A to Z) and the 3 extra letters, the Umlauts (ä, ö, ü / Ä, Ö, Ü) and the sharp s (ß -- only lowercase, because it can never occur at the beginning of a word). In addition there can occur accented characters, but only in proper names (like á/Á, ž/Ž, ç/Ç, etc.).
See http://en.wikipedia.org/wiki/German_alphabet

I have the printed German dictionary "Duden" in front of me, and the index only consists of the 26 roman letters A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z. A word like "Österreich" (German name for Austria) is listed under "O", as if the "Ö" would be a "O" (Osterreich). There is *no* extra index tab for Ä, Ö and Ü.

[...]
Ostermontag (Easter Monday)
Osterpinze (special austrian Easter bakery)
Österreich (Austria)
österreichisch (austrian)
österreichisch-ungarisch (austrian-hungarian)
Ostersonntag (Easter Sunday)
[...]

This is the sort, expected by any German speaking user. Therefore the Views Alpha Pager should behave the same way.

To make the sort system work correctly there has the be an assignment list for all special characters, like Ä = "A", Ö = "O", Ü = "U", ß = "s", Á = "A" or Ž = "Z", to define under which index letter they need to be sorted.

This is exactly what the module pathauto does with the file "i18n-ascii.txt" (http://drupal.org/project/pathauto). Due to the usage of this translation table, pathauto also works perfect with the Cyrillic alphabet, as far as I know.

I am a designer, and no programmer. But for Views Alpha Pager to become perfectly and more flexibly internationalised, maybe a solution like pathauto would be considerable.

Isn’t there anybody else out there having the same problem?
Does someone have an idea how to solve this problem?
Is there any work in progress? (for Drupal 5 or Drupal 6? >> #279907: Port Views Alpha Pager to D6)

Thanks for any reply!