After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 245420 - Hangul name grouping is invalid in Contacts minicard
Hangul name grouping is invalid in Contacts minicard
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Contacts
2.4.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-addressbook-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2003-06-25 06:16 UTC by Young-Ho Cha
Modified: 2013-09-10 14:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Korean name grouping workaround patch (5.11 KB, patch)
2003-06-25 06:19 UTC, Young-Ho Cha
none Details | Review
new korean workaround patch (5.04 KB, patch)
2003-06-25 10:54 UTC, Young-Ho Cha
none Details | Review
new patch, previous patch has some leaks (5.02 KB, patch)
2003-06-25 12:32 UTC, Young-Ho Cha
needs-work Details | Review

Description Young-Ho Cha 2003-06-25 06:16:51 UTC
Currently name grouping use "beginswith query" in Evolution Contacts minicard.

but that is invalid.

Korean Language(=Hangul) have 3 area in unicode. (Hangul Jamo, Hangul
Compatiblity Jamo, and Hangul Syllable) and usally Hangul Syllable should
be used.

But Hangul Syllable area is too large to group with table in PO file.

so I made a workaround patch(Korean Only).

Hangul Syllable(U+AC00 ~ U+D7FF) can decomposite to Hangul Jamo ( U+1100 ~
U+11FF). and my patch use "query with decomposited output"

And in Chinese, I heard name grouping use Ideographs' pronunciation.

so using "beginswith query" can't group name.

It will need different way.
Comment 1 Young-Ho Cha 2003-06-25 06:19:32 UTC
Created attachment 42590 [details] [review]
Korean name grouping workaround patch
Comment 2 Young-Ho Cha 2003-06-25 06:26:32 UTC
a screen shot with applied patch.

http://ftp.mizi.com/~ganadist/evo-add2.png
Comment 3 Young-Ho Cha 2003-06-25 10:54:15 UTC
Created attachment 42592 [details] [review]
new korean workaround patch
Comment 4 Young-Ho Cha 2003-06-25 12:32:45 UTC
Created attachment 42593 [details] [review]
new patch, previous patch has some leaks
Comment 5 André Klapper 2005-07-20 10:41:22 UTC
...so marking the first and second patch as obsolete, so only the third has to
be checked
Comment 6 André Klapper 2006-01-26 00:45:50 UTC
patch needs rework due to moving stuff from evolution to evolution-data-server.
young-ho cha, is this still an issue with a current version of evo?
Comment 7 Young-Ho Cha 2006-01-26 01:16:51 UTC
evolution contacts had removed grouping feature. but when print contacts, still grouped.
Comment 8 André Klapper 2006-01-26 09:37:43 UTC
which evo version are you using?
Comment 9 Young-Ho Cha 2006-01-26 14:04:23 UTC
I'm using 2.4.2.1
Comment 10 Milan Crha 2008-01-23 11:53:37 UTC
Is this still valid with 2.12.x or 2.21.x? There has been done some changes with respect to comparing, using collate, which can help, I guess. Not sure, though.
In the contacts, you can use View->Current view->By Company, as one predefined view with grouping. otherwise you can right click over the column and select "Group by this field", or simply customize current view.
Comment 11 Milan Crha 2010-04-01 15:25:43 UTC
I'm setting this to need info, now for 2.30.0+.
Comment 12 Tobias Mueller 2010-05-17 00:18:17 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!