Don't use colons in UI text when a label is on a different line from the thing it labels or when there's a clear distinction between the label and the thing it's labeling.
Use colons in UI text when a label is on the same line as the text it labels and you need to keep the two elements from running together. Confirmation dialogs are useful when continuing might have unexpected results, such as data loss. They should contain scannable, useful info with a clear outcome, especially for events that can't be reversed.
The first time a user visits a page, you have an opportunity to help them get started with your tool. This could be:. When you need the customer to perform another action to experience full value sign-in to an online service, etc. Microsoft developers should use an FWLink except when it's a help link that users might have to manually type, in which case use an aka. Writing a good message is a balance between providing enough explanation but not being overly technical; between being casual and personable but not annoying or offensive.
If there is an error code associated with the error and if you think that including the error code might help the customer or Microsoft support to research the issue, include it directly below the body text and write it as follows:. If the customer has all the info necessary to resolve the error without the code, you don't need to include it. Null state occurs when customer data or content is absent from an app or feature, when no results are returned after a search, or when required information is missing from a form, such as billing information for a transaction.
Good tooltips briefly describe unlabeled controls or provide a bit of additional info for labeled controls, when this is useful. They can also help customers navigate the UI by offering additional—not redundant—information about control labels, icons, links, etc. Tooltips should be used sparingly or not at all.
They can be an interruption to the customer, so don't include a tooltip that simply repeats a label or states the obvious. It should always add valuable info. Skip to main content. This browser is no longer supported. Use commas in numbers that have four or more digits. Exception When designating years, pixels, or baud, use commas only when the number has five or more digits.
Examples B. Don't use commas in page numbers, addresses, or after the decimal point in decimal fractions. Examples page NE 40 th Street 1. Don't use ordinal numbers, such as June first or October twenty-eighth, for dates. Use a numeral instead: June 1, October Global tip To avoid confusion, always spell out the name of the month.
The positions of the month and day vary by country. Hyphenate compound numbers when they're spelled out. Examples twenty-five fonts the twenty-first day. Add a zero before the decimal point for decimal fractions less than one, unless the customer is asked to enter the value. Examples 0. Exception When an equation occurs in text, it's OK to use a slash between the numerator and the denominator. Or, in Microsoft Word, go to the Insert tab, and select Equation to format the equation automatically.
Hyphenate spelled-out fractions. Connect the numerator and denominator with a hyphen unless either already contains a hyphen. Examples one-third of the page two-thirds completed three sixty-fourths. In measurements where the unit of measure is spelled out, use the plural form when the quantity is a decimal fraction. Use the singular form only when the quantity is 1. Always spell out ordinal numbers.
Examples the first row the twenty-first anniversary. In most cases, use from and through to describe a range of numbers. Example from 9 through Exceptions Use an en dash in a range of pages or where space is an issue, such as in tables and UI. For example, — and pages — Microsoft has more than offerings. To help customers recognize, find, and buy them, reserve capitalization for product and service names. Always capitalize the first word of a new sentence. Rewrite sentences that start with a word that's always lowercase.
Don't use all lowercase as a design choice. Although all uppercase is used occasionally as a design element, don't use it in text. Don't use internal capitalization such as AutoScale or e-Book unless it's part of a brand name.
When words are joined by a slash, capitalize the word after the slash if the word before the slash is capitalized. For information on capitalization in hyphenated compound words see Hyphens. For information about capitalizing UI labels in instructions, see Formatting text in instructions.
Use sentence-style capitalization in most titles and headings: capitalize the first word and lowercase the rest. Exceptions Proper nouns, including brand, product, and service names, are always capitalized. If a title or heading includes a colon, capitalize the first word after it. Titles of blog posts, documentation articles, and press releases use sentence-style capitalization.
0コメント