Re: [Gaim-i18n] Search comment for Jabber is not translatable

[Vincent v. A. <adr...@gn...>]

Op Mon, 27 Mar 2006 13:18:15 +0200 (CEST)
schreef Bjoern Voigt <bj...@cs...>:

> Hello all!
>=20
> > > (2) explain the user that this is a Jabber server comment
> > >=20
> > >     (something like: _("Jabber server comment: ") +
> > > instructions)
> >=20
> > (2) is superior to (1). I've just committed something like that.
> > We'll see how people like that.
>=20
> Ok, I tested my committed change and think, it's ok.
>=20

While it is better than (1), it's not ideal.

> > > (3) don't use the server comment, only use Gaim's own comment
> >=20
> > I don't like this; it throws away useful data.
>=20

As Bjoern explains below, the information might not be that
useful.

> My question to Jabber experts is: How useful are these search
> comments for Gaim?
>=20
> The example comment from users.jabber.org was:
>=20
> |  Find a contact by entering the search criteria in the given
> |  fields. Note: Each field supports wild card searches (%)
>=20
> The search fields (First Name, Last Name, Nickname and E-Mail) are
> hard-coded in Gaim (see src/protocols/jabber/buddy.c). It's
> relatively clear that the user has to fill one or more of this
> fields to search.
>=20
> The only interesting information is, that wild card searches (with
> "%") are possible. =20
>=20
> There is not much documentation about JUD (Jabber User Directory).
>=20
> Look at this README file from
> http://modzer0.cs.uaf.edu/wiki/index.php/Jabber/JUD:
<snipped pasted text>
>=20
> If I read the README right the search instruction section is only
> needed for customized searches (here with age and colour).=20
>=20
> What's with the following situation: An example Jabber User
> Directory allows a search for additional fields like age and says
> this in it's search comment field. Then the user wonders about the
> missing field "Age:".
>=20
> Greetings, Bj=F6rn

Good point. The situation of hardcoded fields and custom messages is
bogus anyway. We can remove/hide it safely and insert our own
message, if needed. We could insert a "click here for server info"
kind of widget. Perhaps that triangle flip open widget at the bottom
of the window, with this text in it, or maybe a tooltip of
somesort....I don't know, just thinking aloud. But a casual user
should not need it anyway. The "use % for wildcard" text should stay
though. Many will otherwise try to use
* as a wildcard.

Kind regards,
Vincent van Adrighem