Hello!
Stephan Sokolow has written on Thursday, 7 November, at 20:28:
>On 13-11-07 12:39 PM, Andrej N. Gritsenko wrote:
[...skipped...]
>PCManFM 1.1.1 appears to be trying to follow the KDE approach with the
>"Open Folder in/as..." entries in the Tools menu showing an intent to
>capitalize everything except prepositions (as KDE and Pidgin do) but has
>a single mistake with the "Help > Keyboard navigation" failing to
>capitalize the non-article, non-preposition word "navigation".
Well, I never treated menu items as titles, and also I never paid
attention to capitalization, so when I added that item to menu, I just
added it as a natural short sentence. :)
Anyway I planned to apply common HIG to LibFM and PCManFM later, it
is on my TODO list. The HIG for GTK capitalization is here:
https://developer.gnome.org/hig-book/unstable/design-text-labels.html.en#layout-capitalization
The HIG for KDE capitalization is here:
http://techbase.kde.org/Projects/Usability/HIG/Capitalization
Both these HIGs clearly state menu items should be Title Capitalized. :)
Both these HIGs state that articles and such should be not capitalized.
[...skipped...]
>> Well, if you think items in Places should be absolutely equal to
>> items in the checklist, then below is a comparizon:
>> shown in Places checklist item in Preferences
>> ----------------------------------------------------
>> <username> Home Directory
>> Desktop Desktop Folder
>> Applications Applications
>> Trash Can Trash can
>> File system File system root
>> Computer "Computer" special folder
>> Network Drives Network places
>> Some items require sync then. Probably some should be changed in both
>> places, yes?
>Agreed. As a starting point for discussion, here's how I'd do it were I
>in charge:
>Shown in Both
>---------------
>Home Folder
>Desktop
>Trash Can
>Filesystem Root
>---
>Applications
>Computer/Drives/Devices (I'm not yet certain which is best)
>Network
>Here's my rationale:
[...skipped...]
Well, your descriptions look solid and fairly reasonable so I cannot
disagree. Since nobody gave any objections, I will apply your suggestions
to LibFM and PCManFM, except for the separator - it cannot be done due to
design issues. Out of Computer/Drives/Devices I completely agree with you
that Devices looks the most correct term here.
>>>> When you say "location bar", users recognize it as a single term
>>>> containing two words.
>>>> When you say "location entry field", even skilled users are likely to
>>>> look to the Places sidebar. (In the eyes of the user, "field" is a
>>>> vaguely-defined concept that roughly means "interactive widget that
>>>> isn't a button or checkbox" and the Places sidebar is a listbox that's
>>>> full of "location entries")
>> Well, I'm agree already that string is vulnerable and should be
>> replaced. The question is what the replacement should be. :)
>My reason for suggesting "location bar" is that its location and
>appearance are similar to the ones in browsers, so using the same
>terminology will aid recognition.
>(Especially given how copying things from the location bar and pasting
>things into it are operations that often need to be described in the
>context of web browsers, so unskilled users are much more likely to be
>familiar with the term.)
Well, let go back to starting point. The string in question wasn't
the "location bar" or whatever. The string in question was a tooltip for
the button next to the location bar which refers to it. The tooltip text
is "Open folder entered in location entry". What is your suggestion? :)
With best regards.
Andriy.
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Lxde-list mailing list
Lxde-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxde-list
