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

List:       kde-accessibility
Subject:    Re: [Kde-accessibility] Proklam screenshots
From:       Olaf Jan Schmidt <olaf () amen-online ! de>
Date:       2002-09-25 8:42:42
[Download RAW message or body]

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

Hi Pupeno!

Thank you for sending these screenshots.

I like the layout. 

As I am the kind of person who is always thinking of other ways to do it, 
I have a number of other ideas, again - you do not need to follow them.

> (this has to be polished as diferent languages should be managed here
> too, I think... I'm not sure).

I am not sure whether the advanced tab is needed.

It might be less error-prone to just use a hard-coded text in the KDE 
default language. I think you can expect the user to install a plug-in 
for the language KDE is using. Otherwise all system messages / warnings 
cannot be correctly spoken, so not to saying these interruption texts 
would be the smaller problem.

If Proklam will be part of the kdelibs, then it will be translated into a 
lot of languages. This way the user does not have to translate the 
interruption texts him-/herself.

I was not sure about the spelling of "interrupted", so I looked it up in 
the dictionary. (BTW: I would have spelled it wrong, too.)

The kde-usability list has discussed a lot of UI changes to kcontrol 
modules in the last weeks. It would be best to send typo corrected 
screenshot to the kde-usability list for discussion if you wish to 
improve the usability of Proklam.


> Maybe the TTS/lang selector should go at the top, that's not a problem.
> What do you think about it ?

Having two tabs below each other is confusing, as programs behave 
different in such a situation. Under Windows, all tabs behave like being 
part of one only tab line, even if they are shown in several lines.

It is also confusing that "default" and "remove" are not part of the 
plug-in frame, even though they apply to them.

How about really putting all tabs into one line?
[General] [English] [Spanish] ([Advanced])

In "General", you would then have a list of all language plug-ins with the 
options to add and remove them.

Why is setting the default language neccessary? Either the KDE default 
language could be used as the default one, or you could force programs to 
set the language.

As I have sometimes untranslated English programs running on my German 
KDE, I prefer the latter. (Much better than manually setting a default 
language that does not work correctly for some of my programs.)

There could be a function in KSpeech that allows speaking a text without 
specifying a language, but it should then set the language to the 
language of the program and send a DCOP message with language, so Proklam 
does not have to guess.

Of course there we still be the question of what to do with unsupported 
languages, but it should be OK to expect the user to install a plug-in 
for every language he wants to have understandably spoken.

Just my ideas, the people on kde-usability might be more competent to 
judge these issues.

Olaf.

- -- 
Meine Internetseiten:
http://www.GebetGenerator.de, http://www.amen-online.de

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAj2RdwgACgkQoLYC8AehV8fUtACg+PyzH3UVUu4CwRmL5FNu/31o
UrsAn3e3lrnp0vMdWbzBjDML4BIzKS2R
=i/nd
-----END PGP SIGNATURE-----

_______________________________________________
kde-accessibility mailing list
kde-accessibility@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-accessibility
[prev in list] [next in list] [prev in thread] [next in thread]