[gnome-cyr] [Bug 14804] Changed - need configurability of what index tabs to show in addressbook

[bugzilla-daemon rocky ximian com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by hvv hippo ru 

http://bugzilla.ximian.com/show_bug.cgi?id=14804

--- shadow/14804	Thu Nov  8 15:06:53 2001
+++ shadow/14804.tmp.21416	Thu Nov  8 15:21:09 2001
@@ -3,21 +3,21 @@
 Version: 0.99
 OS: other
 OS Details: 
 Status: NEW   
 Resolution: 
 Severity: Unknown
-Priority: Blocker
+Priority: Wishlist
 Component: Contacts [was: Addressbook]
 AssignedTo: evolution-addressbook-maintainers ximian com                            
 ReportedBy: hvv hippo ru               
 QAContact: louie ximian com
 TargetMilestone: ---
 URL: 
 Cc: cyba gnome pl,gnome-cyr gnome org
-Summary: need addressbook tabs for both latin and non-latin letters under non-latin1 locale
+Summary: need configurability of what index tabs to show in addressbook
 
 At least under russian (i.e. non-latin1) locale, addressbook has "index tabs"
 only for russian letters, but has no tabs for latin letters (ABCDE..XYZ).
 This makes it VERY hard to lookup people from countries that use latin
 alphabet.
 This should be fixed. Ideally, one should have the following menu choices:
@@ -41,6 +41,24 @@
 solution is sufficient for Poles, because Polish alphabet is a
 superset of the latin one.
 IDEAL solution would be adding extra menu option: "Show letter tabs
 for language..." + list of all available languages. This way you could
 lookup people from Poland too :-)
 
+
+------- Additional Comments From hvv hippo ru  2001-11-08 15:21 -------
+Thank you very much, Zbigniew! I was also thinking that letters on
+tabs are wired in .po file, but I was unable to connect to
+ftp.ximian.com to get srpm to check that theory (and I forgot about
+gnome cvs too)! Thank you for finding it out! I will talk with Valek
+about this. As for 'select languages you would like to be supported
+on tabs' you proposing - yes, I think it would be trivial to
+implement (setlocale for each language, convert all chars for which
+isupper returns 1 to utf and union the sets).. Another hack would be
+'dynamically attacheble gettext message catalogues' - for each
+language there is a set of .gmo files that defines translation of 2
+strings - "__description___" and "__tabs__" - first is the
+description of the catalogue (e.g. "russian first, english second"),
+translation of "__tabs__" should give a list of strings to show on
+tabs. User selects which catalogue to load then, and it gets loaded
+with bindtextdomain()..
+Marking this ticket as wishlist now..