-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Joe Hung,
I've this problem as well, so I use the following methode as the
solution. Although there is some difficult on shorting the person by
First Name or Last Name but it wouldn't hurt.
Putting the whole Chinese Name to the First Name fields (The 1st fields
on Mozilla Addressbook).
Then English Name (or Phonetic Name) on the Last Name fields (The 2nd
fields)
By using this way the display name will have need to be both Chinese and
then English/Phonetic Name. So searching for both Chinese and
English/Phonetic Name will not be a problem at all.
(the Best of all we don't need to implement a new attribute)
Thank You
Chan Min Wai
Ps: Suggestion is Always Welcome.
Joe Hung ����:
| When searching against Chinese/Japanese names, sometimes people would
| like to enter their "phonetic values" of the "written names" in the
| search criteria, instead of the real written name.
|
| I can immediately think of 2 ways to implement this,
|
| 1) is to have corresponding phonetic columns for each attribute, for
| example, givenname_phonetic, sn_phonetic and construct the search
| query accordingly.
|
| 2) is to use multi-value of givenname and sn. But this really increase
| the burden on the client side because now the client need to have a
| way to distinguish whether the value is a "written name" or a
| "phonetic value".
|
| Can anybody think of a better way or is there already a standard way
| of dealing with this?
|
| thanks,
| -joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAj5wnREACgkQV0p9slMZLW5qOQCfUFXX9fNR7j8mSzugA9wuH1nt
aTYAn3zXur7oSch7e46VTYcTu4gsQh4r
=cohV
-----END PGP SIGNATURE-----
