用户界面中的文本大写
我想问您是否有理由在应用程序用户界面中将菜单等中的所有项目大写，例如
- 文件->页面设置
- 编辑->全选
- 帮助->技术支持
为什么不应该只需将这些项目标记为文件->页面设置等？ 这种大写对我来说似乎是错误的 - 但我不是以英语为母语的人，所以我可能不会喜欢它。
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
从可用性的角度来看，标题式大写（每个单词的第一个字母大写）可以增加标题中非首字母的显着性。这可以帮助用户更快地找到标题中的关键词以识别和区分菜单项。例如，比较：
与：
理想情况下，这是不必要的，因为您的菜单标题应该以关键的区分词开始，但有时这并不能成为可接受的标题。
在 Apple 人机界面指南中，标题样式是菜单项（和命令/按钮）的标准。标题样式也是 MS Windows 的标准，直到
Vista，当时 Windows 用户体验指南在许多情况下从推荐标题样式切换为句子样式（仅大写首字母的第一个字母），包括菜单标题 (http://msdn.microsoft.com/en-us/library/aa511502.aspx）。我认为这是为应用程序提供会话网络“归纳” 风格，其中选项被表述为命令句子（例如，“创建电源计划”、“对所有当前项目执行此操作”）。
就我个人而言，我会避免为应用程序使用如此冗长的用户界面，特别是对于用户经常使用的应用程序，因此坚持使用标题样式。更多的单词会增加混乱，更多的阅读会减慢用户的速度。事实上，由于阅读时间太长，用户倾向于跳过大块文本，因此添加单词通常会在功能上降低清晰度。
From a usability standpoint, title-style capitalization (capitalizing the first letter of each word) increases the conspicuousness of the non-initial words in a caption. This may help users more quickly find key words in a caption to identify and discriminate menu items. For example compare:
Versus:
Ideally, this is unnecessary because your menu captions should begin with their key discriminating words, but sometimes that just doesn’t make acceptable captions.
In the Apple Human Interface Guidelines, title-style is standard for menu items (and commmand/push buttons). Title-style was also standard for MS Windows until
Vista, when the Windows User Experience guidelines switched from recommending title-style to sentence-style (capitalize only the first letter of the initial word) for many situations, including menu captions (http://msdn.microsoft.com/en-us/library/aa511502.aspx). I think this was part of an effort to give applications a conversational webby “inductive” style, where the options are phrased as commands sentences (e.g., “Create a power plan,” “Do this for all current items”).
Personally, I would avoid such wordier UIs for apps, especially for those regularly used by users, and thus by extension stick with title-style. More words adds clutter and more reading slows users down. In fact, users are inclined to skip large blocks of text since reading takes so long, so adding words often functionally reduces clarity.
在英语中，标题中的所有单词通常都大写，除了连词（of、for 等）和介词（如 with）。用户界面元素（按钮、标题、菜单项）的格式与标题类似。
我现在正在使用一个软件，它有一个“任务”菜单和 3 个项目，如下所示：
“新任务”大小写的差异对我来说非常明显 - 它只是没有看起来不“正确”。
In English, generally titles have all words capitalised except for conjunctions (of, for, and etc.) and prepositions (like with.) User interface elements (buttons, titles, menu items) are formatted like titles.
I have a piece of software I'm using right now which has a "Tasks" menu and 3 items as follows:
The difference in capitalisation on "new task" stands out a mile for me - it just doesn't look "correct."
因为菜单的格式通常类似于英文的 标题。在标题中，第一个单词以及任何名词、形容词、动词、副词和代词始终大写。如果它们不是标题中的第一个单词，则冠词和介词通常不大写。
Because menus are usually formatted like titles in English. In a title, the first word is always capitalized, as well as any nouns, adjectives, verbs, adverbs, and pronouns. If they are not the first word in the Title, articles and prepositions are not generally capitalized.
我目前正在和一位同事就此事争论不休。就UI标准而言，我可能属于苹果阵营，而他则完全属于微软阵营。微软最近一直在推动Downstyle（我不时看到这个名称，涉及仅大写第一个字母的做法，特别是涉及标题）。我的同事声称它“测试良好”。当每个单词都没有大写字母时，用户可以更快地阅读文本（毫不奇怪）。但是，我认为这不应该成为将其用于用户界面元素的理由。我认为这是有原因的，但测试可能很棘手。
当用户测试他们以前从未见过的软件（或网站）时，他们主要会阅读所有内容（包括 UI）。他们阅读“显示所有回复”比“显示所有回复”更快。然而，一段时间后，我相信用户会转而不再阅读 UI 元素，而是依靠更快的方法来获取他们将要点击的目标，例如位置或形状。在这种情况下，“显示所有回复”更容易识别，因为它显示的形状比“显示所有回复”更清晰（眯着眼睛可能会看到这一点）。认为它测试得更好是因为用户可以更快地阅读它的论点不成立，因为用户不是在阅读按钮和菜单，而是将他们想要的东西与该东西的记忆相匹配。测试这一点的正确方法可能是查看用户在 Upstyle 中的开始速度是否比 Downstyle 慢，但在重复访问时会更容易，最终超过 下风格。
如果您想查看在 UI 中使用大量 Downstyle 的网站，请查看 Outlook.com 或 OneDrive.com，它们都是 Microsoft 产品。似乎很明显，在这些网站上使用 Downstyle 是令人沮丧的失败，我这么说并不是因为我“习惯”UpStyle （毕竟，20多年来看到相反的情况可能会在我的感知中产生一些相当强烈的认知“噪音”）。尽管如此，我认为它失败了，因为所有内容都使用了细细的 Helvetica Extra Light 文本，依赖滚动来指出几乎所有可点击的内容（所有这些对于平板电脑用户来说都是不可用的），并且总体平坦度达到了极限（没有一个单一的内容）。阴影，即使它有助于消除伪下拉菜单的歧义）也会导致 UI 比应有的更难使用。
所以我的建议是，保留标题大小写 (Upstyle)，除非您希望您的网站看起来像 Microsoft 网站，直到他们发现其方式的错误并重新设计它以使其看起来像他们使用的方式到（就像其他人一样）。
I'm currently in a running argument with a colleague about this. I'm probably in the Apple camp in terms of UI standards, and he is squarely in the Microsoft camp. Microsoft lately has been pushing Downstyle (the name I see from time to time regarding the practice, particularly involving headlines, of only capitalising the first letter). My colleague claims that it 'tests well'. Users (not surprisingly) can read text faster when it there are No Capitals On Every Word to stumble over. However, I believe that this should not be a reason to use it for User Interface elements. I think there is a reason for this, but it might be tricky to test.
When users are testing a piece of software (or a website) that they've never seen before, they are primarily reading everything (including the UI). They read 'Show all replies' faster than 'Show All Replies'. However, after a period of time, I believe that users switch to not reading UI elements, but relying on faster methods of acquiring the target that they are going to click on, such as location or shape. In this case, 'Show All Replies' is easier to pick out because it displays as a less ambiguous shape than 'Show all replies' does (squinting your eyes will probably show this). The argument that it tests better because users can read it faster falls apart because users are not reading buttons and menus, but matching something they want to the memory of that thing. Probably the right way to test this is to see if users start out slower in Upstyle than with Downstyle, but have an easier time with repeated access, eventually surpassing the Downstyle.
If you want to see a site that uses a lot of Downstyle in the UI, check out Outlook.com or OneDrive.com, both of which are Microsoft products. It seems to be to be pretty apparent that the use of Downstyle is dismal failure on these sites, and I'm not saying this because I'm 'used to' UpStyle (after all, 20+ years of seeing the opposite can create some pretty strong cognitive 'noise' in my perceptions). Nevertheless, I think it fails because the use of thin Helvetica Extra Light text for everything, reliance on rollovers for pointing out nearly every clickable thing (all of which is not available to a tablet user) and general flatness to an extreme (not a single drop shadow, even where it would help to disambiguate a pseudo drop-down menu) make for a UI that is much harder to use than it ought to be.
So my advice is, stay with title-case (Upstyle), unless you want your site to look like a Microsoft site, until they see the error of their ways and redesign it to look the way they used to (which was like everyone else).
此类事情取决于您平台的人机界面指南：
请注意，专有名词在这里是一个例外 - 那些应始终使用标题大小写。
至于哪种解决方案在可用性方面更好，这篇文章 概述了优点和缺点。我将尝试在这里总结每种方法的好处：
This kind of thing will depend on your platform's Human Interface Guidelines:
Note that proper nouns are an exception here — those should always use title case.
As for which solution is better in terms of usability, this article outlines the pros and cons. I'll try to summarize the benefits of each approach here: