Re: "untitled" vs "Untitled"
Re: "untitled" vs "Untitled"
- Subject: Re: "untitled" vs "Untitled"
- From: m <email@hidden>
- Date: Sun, 10 Jul 2005 12:12:46 -0700
On Jul 10, 2005, at 8:44 AM, Ali Ozer wrote:
If something is titled, title case is appropriate for the text,
because it is titled.
If something is untitled, then it is not titled; title case is
inappropriate as it is not a title and therefore should not be in
case which belongs to and is intended for titling.
That's it. Why should an untitled thing use title case? It
shouldn't---it's *untitled* for goodness sakes! The pseudo-title
of "untitled" just reinforces this on multiple levels.
This is elegant but rather an English-centric argument.
No, it's a "many, many language"-centric argument. Many languages
(and languages that the majority if your users use) have title
capitalization conventions, and even if the details of the
conventions vary from locale to locale, most of them capitalize the
first non preposition word.
- As I said earlier, to some international users there won't be a
difference at all.
So no problem either way, right?
- And even in Roman scripts, some users might very well use lower
case to title their document names even when saved.
Fine, it is after all their choice.
So trying to represent untitledness via lack of title-casing is not
always necessarily a clue and is not global. So we have proxy
icons to more exactly represent untitledness.
I think perhaps there is a misunderstanding here. It's not a matter
of trying to convey that the document has never been saved (as you
note, there are superior ways to do that already), it's a matter of
following the typographic conventions for the language you are
running under. Attention to these kinds of details always set the the
Mac UI apart from other UIs, and is still something that it mostly
excels at. It would be a shame to let it erode away...
NSDocument uses a naming convention with capitalization familiar to
users of Adobe and Microsoft apps.
This smells like a post-hoc rationalization. What next, the dreaded
"Yes" "No" dialog box? Has user experience/interface design has been
turned over to Microsoft and Adobe?
(I'll just note that Adobe's Photoshop lets me use cmd-+ to zoom in
without requiring that the shift key be held down. It'd be nice if I
didn't have to jump through hoops to do the same thing with Cocoa).
_murat
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden