[kde-guidelines] Styleguide: Wording

[Thomas Pfeiffer]

On Friday 20 December 2013 14:20:29 Heiko Tietze wrote:
> Presentation > Text > Wording
> * Keep [[Projects/Usability/HIG/Wording|wording]] easy to understand and
> consistent. http://techbase.kde.org/Projects/Usability/HIG/Wording
> 
> == Purpose ==
> Every word displayed in an application is part of a conversation with users.
> This conversation is an opportunity to provide clarity and to help people
> feel comfortable in the system.
> 
> == Guidelines ==
> * KDE personas are not tech savvy; so your app should use an easy to
> understand terminology. 

While this is certainly true for most applications, there also some 
specialized applications created by KDE (for example some scientific 
applications). These may use terms which are unfamiliar to the general public, 
but familiar to their specific target audience. 
Maybe we should change this to "use terminology that is familiar and to and 
thus easy to understand for your application's target audience"?

> * Avoid abbreviations, acronyms, and tech-babble.
> * Use a tone that’s informal and friendly, but not too familiar.

I don't think "familiar" is the correct word here, because it usually means 
"well known", which I think is good in our case ;). I'd go with "not too 
informal".

> * Keep information short and consistent; avoid redundancy or unnecessary
> words. * Don't abuse
> [[Projects/Usability/HIG/Capitalization|capitalization]] because it draws
> people’s attention. * In respect to chronological information consider that
> your app is potentially used for decades; don't use fix dates like ''this
> year''. * Follow system-wide conventions for basic functions to keep
> wording consistent. == Examples ==
> * Delete, Move to Trash, Remove and Uninstall
> ** When a file or object is completely removed from the system, use
> ''Delete''. ** When a file or object can be recovered, use ''Move to
> Trash'' for files and ''Remove'' for list objects etc. ** When a file or
> object can be removed and was originally installed, use ''Uninstall''. *
> Settings, Options and Properties
> ** Use ''Settings'' for a configuration dialog which allows you to set
> specific properties or functionality. This usually applies to application
> configuration tools. For example, Konqueror Settings. 
> ** Use ''Options'' for a configuration dialog which provide. 

Provide what? There seems to be one or more words missing in this sentence.

>This usually applies to object configuration tools. ** Use ''Properties'' for 
a list of metadata or
> details that are associated with a particular object which cannot be edited
> or interacted with in any way. For example, file "properties" dialog in
> Dolphin.
> 
> [[Category:Usability]][[Category: Presentation]][[Category:Text]]

Apart from those three things, +1 from me!