[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Fwd: Consistency in the UI
From:       Dirk Doerflinger <dirk () doerflinger ! org>
Date:       2002-03-01 1:21:59
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This should have gone to kde-i18n@kde.org, but that list seems to be dead?

"<kde-i18n@kde.org>:
Sorry, no mailbox here by that name. vpopmail (#5.1.1)"

- ----------  Forwarded Message  ----------

Subject: Consistency in the UI
Date: Fri, 1 Mar 2002 02:08:48 +0100
From: Dirk Doerflinger <dirk@doerflinger.org>
To: kde-devel@kde.org
Cc: kde-i18n@kde.org

- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

this is a crossposting, because I don't know who is/feels responsible for
that. If there are any responses on the i18n-list, please CC to me as I'm not
subscribed to the i18n list.

While writing the docs for kicker I noticed that there is still a lot of
inconsistency within the UI. Most of it are only details like some Labels
with all words starting with a capital letter and others with only the first
word capitalized.
But there are bigger things like "Non-KDE Application"(e.g. in the "Add" menu
of kicker's contex menu) vs. "Legacy Application"(in the settings), which
could really trap some users and is also quite hard to put in a right shape
in the docs.
I guess that kicker isn't the only application where such things occur.
IMHO it's quite neccessary to be as consistent as possible, though it may be
a lot of work to keep everything in shape.
There isn't a "technical" solution to that problem (like global i18n strings
or whatever), is it?
Another thing is - kicker specific - the inconsistency within the context
menus of the applets. I think users could be quite confused when some apps
have different menus when right clicking on the applet or clicking the small
arrow-button in the handle. Could tthat be put in a common way, e.g. all
settings in the handle-menu?
I can provide a list of the inconsistencies I found if there is a need, or I
could start correcting the strings within the sources. I could also fill out
some bug reports about that.
Does all that make sense?

Regards,
DD

- - --
Dirk Doerflinger
<dirk@doerflinger.org>
PGP Key at www.doerflinger.org
- - ----------------------
Quote of the day:

This is for all ill-treated fellows
	Unborn and unbegot,
For them to read when they're in trouble
	And I am not.
		-- A. E. Housman
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8ftSl/7cqEhMbrwARAjgJAJwJSbwpBObfJl1plH8SXP7a0BlJVgCgjPwJ
i8Otj+oUhIpaKP7WzutaU84=
=zJxF
- -----END PGP SIGNATURE-----

- -------------------------------------------------------

- -- 
Dirk Doerflinger
<dirk@doerflinger.org>
PGP Key at www.doerflinger.org
- ----------------------
Quote of the day:

Have you noticed the way people's intelligence capabilities decline
sharply the minute they start waving guns around?
		-- Dr. Who
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8fte8/7cqEhMbrwARAib2AKCDlPGlKDqJGdy5pxyUPBsj5KkHywCgmpo7
J8oetGtBwnz4HIKFrQHpcJY=
=tGJo
-----END PGP SIGNATURE-----
[prev in list] [next in list] [prev in thread] [next in thread]