撰寫樣式Writing style

標頭影像

您表達錯誤訊息的方式、撰寫說明文件的方式,甚至是您為按鈕選擇的文字,對於應用程式的可用性都有很大的影響。The way you phrase an error message, the way you write help documentation, and even the text you choose for a button have big impacts on the usability of your app. 撰寫樣式可能會導致巨大的差異,是糟糕的使用者體驗和良好的使用者體驗的關鍵所在。Writing style can make a big difference between an awful user experience and a better one.

語氣和語調原則Voice and tone principles

研究顯示,人們對於友善、有幫助且精簡的書寫風格反應最好。Research shows that people respond best to a writing style that's friendly, helpful, and concise. 做為此研究的一環,Microsoft 開發了三種語氣和語調原則,套用在所有內容上,是 Fluent 設計不可或缺的部分。As a part of this research, Microsoft developed three voice and tone principles that we apply across all our content, and are an integral part of Fluent design.

溫暖輕鬆Be warm and relaxed

最重要的一點是,別嚇跑使用者。Above all else, you don't want to scare off the user. 態度放輕鬆、不要太官腔,也不要採用使用者不了解的術語。Be informal, be casual, and don't use terms they won't understand. 即使出了問題,也不要怪罪使用者。Even when things break, don't blame the user for any problems. 是您的應用程式要負起責任,且要提供友善溫馨的指導方式,將使用者的行為置於優先考量。Your app should take responsibility instead, and offer welcoming guidance that puts the user's actions first.

伸出援手Be ready to lend a hand

您的文字要隨時展現出同理心。Always show empathy in your writing. 請將重點放在解釋發生了什麼事,並提供使用者需要的資訊,而不是用沒必要的資訊來淹沒使用者。Be focused on explaining what's going on and providing the information that the user needs, without overloading them with unnecessary info. 在可能的範圍內,發生問題時請務必提供解決方案。And if possible, always provide a solution when there's a problem.

簡潔清晰Be crisp and clear

大多數時候,文字並不是應用程式的重點所在。Most of the time, text isn't the focus of an app. 文字是用來引導人們,教導他們發生了什麼事以及接下來應該做什麼。It's there to guide people, to teach them what's going on and what they should do next. 撰寫應用程式中的文字時,請勿忽視這一點,且不要認定使用者會詳讀每個字。Don't lose sight of this when writing the text in your app, and don't assume that users will read every word. 請使用對象熟悉的語言,確保內容一目瞭然。Use language that is familiar to your audience, make sure it's easy to understand at a glance.

開門見山Lead with what's important

要讓使用者一眼看出文字的重點。Users need to be able to read and understand your text at a glance. 不要用多餘的介紹來拉長文章。Don't pad your words with unnecessary introductions. 請強調文章的重點所在,務必先呈現概念的核心,之後再繼續延伸。Give your key points the most visibility, and always present the core of an idea before you add onto it.

綠色長條的第一個螢幕擷取畫面,內有綠色核取記號和 Do 一字。First screenshot of a green bar that has a green check mark and the word Do in it. 選取 [濾鏡]以將效果新增至影像。Select filters to add effects to your image.

禁止事項如果您想要新增視覺效果或改變影像,請選取濾鏡Don't If you want to add visual effects or alterations to your image, select filters.

強調動作Emphasize action

應用程式是由動作來定義。Apps are defined by actions. 使用者在使用應用程式時,會進行各種動作,而應用程式也會採取動作來回應使用者。Users take action when they use the app, and the app takes action when it responds to the user. 請確定應用程式中的文字都是使用主動語態 。Make sure your text uses the active voice throughout your app. 請將人物和功能描述為執行動作的對象,而不是對他們完成動作。People and functions should be described as doing things, instead of having things done to them.

綠色長條的第二個螢幕擷取畫面,內有綠色核取記號和 Do 一字。Second screenshot of a green bar that has a green check mark and the word Do in it. 重新啟動應用程式以查看您的變更。Restart the app to see your changes.

禁止事項當應用程式重新啟動時,將會套用所做的變更。Don't The changes will be applied when the app is restarted.

簡短窩心Short and sweet

使用者會一眼掃過文字,且通常會整個忽略整段較長的段落。Users scan text, and will often skip over larger blocks of words entirely. 不要因此省去必要的資訊和要表達的內容,但文字量不要超過所需。Don't sacrifice necessary information and presentation, but don't use more words than you have to. 有時要用多個短句或隻言片語來表達,Sometimes, this will mean relying on many shorter sentences or fragments. 有時則是要多加斟酌長句的用詞和句構。Other times, this will mean being extra choosy about the words and structure of longer sentences.

綠色長條的第三個螢幕擷取畫面,內有綠色核取記號和 Do 一字。Third screenshot of a green bar that has a green check mark and the word Do in it. 我們無法上傳圖片。We couldn't upload the picture. 如果再度發生這種情況,請嘗試重新啟動應用程式。If this happens again, try restarting the app. 但請不要擔心 — 當您回來時,您的圖片已經準備好了。But don't worry — your picture will be waiting when you come back.

禁止事項發生錯誤,我們無法上傳圖片。Don't An error occured, and we weren't able to upload the picture. 請再試一次,如果再次遇到這個問題,您可能需要重新啟動應用程式。Please try again, and if you encounter this problem again, you may need to restart the app. 但不用擔心 — 我們已經將您的工作儲存在本機上,當您回來時,它已經準備好了。But don't worry — we've saved your work locally, and it'll be waiting for you when you come back.

風格慣例Style conventions

如果您不認為自己是寫手,嘗試實施這些原則和建議可能會讓人卻步。If you don't consider yourself to be a writer, it can be intimidating to try to implement these principles and recommendations. 但別擔心,想要提供良好的使用者體驗,簡單直白的寫法是絕佳的選擇。But don't worry — using simple and straightforward language is a great way to provide a good user experience. 如果您仍然不確定如何組織您的文字,以下是一些很有幫助的指導方針。And if you're still unsure how to structure your words, here are some helpful guidelines. 如果需要詳細資訊,請參閱 Microsoft 樣式指南 (英文)。And if you want more information, check out the Microsoft Style Guide.

對使用者的稱呼方式Addressing the user

請直接對使用者說話。Speak directly to the user.

  • 一律將使用者稱呼為「您」。Always address the user as "you."
  • 請以「我們」代表您自己的觀點。Use "we" to refer to your own perspective. 請使用友善溫暖的語氣,讓使用者能夠感受到自己屬於整個體驗的一員。It's welcoming and helps the user feel like part of the experience.
  • 不要使用「我」來指稱應用程式的觀點,即使應用程式的創作者只有您一人。Don't use "I" or "me" to refer to the app's perspective, even if you're the only one creating it.

綠色長條的第四個螢幕擷取畫面,內有綠色核取記號和 Do 一字。Fourth screenshot of a green bar that has a green check mark and the word Do in it. 我們無法將您的檔案儲存到該位置。We couldn't save your file to that location.

縮寫Abbreviations

如果需要在應用程式中多次提及某個產品、地點或技術概念,使用縮寫就相當有用。Abbreviations can be useful when you need to refer to products, places, or technical concepts multiple times throughout your app. 縮寫可以節省空間,感覺更自然,但前提是要讓使用者懂得縮寫的意思。They can save space and feel more natural, as long as the user understands them.

  • 請不要認定使用者熟知縮寫的含意,即使您認為那是常見的縮寫。Don't assume that users are already familiar with any abbreviations, even if you think they're common.
  • 讓使用者第一次看到某個縮寫時,一定要解釋縮寫的意思。Always define what a new abbreviation means the first time the user will see it.
  • 請不要使用與其他縮寫太過類似的縮寫。Don't use abbreviations that are too similar to one another.
  • 如果您要將應用程式當地語系化,或者英文是使用者的第二語言,則請勿使用縮寫。Don't use abbreviations if you're localizing your app, or if your users speak English as a second language.

綠色長條的第五個螢幕擷取畫面,內有綠色核取記號和 Do 一字。Fifth screenshot of a green bar that has a green check mark and the word Do in it. Windows 應用程式設計指引可以協助您設計和建立美觀、優雅的應用程式。The Windows app design guidance is a resource to help you design and build beautiful, polished apps. 運用每個 Windows 應用程式中所包含的設計功能,您可以建置可在一系列裝置上縮放的使用者介面 (UI)。With the design features that are included in every Windows app, you can build user interfaces (UI) that scale across a range of devices.

簡寫Contractions

人們很習慣看到簡寫,也覺得簡寫很正常。People are used to contractions, and expect to see them. 特意避開簡寫,反而會讓您的應用程式看起來太過正式,甚至呆板。Avoiding them can make your app seem too formal or even stilted.

  • 請依照一般使用習慣,自然使用簡寫即可。Use contractions when they're a natural fit for the text.
  • 請勿為了節省空間而使用不常見的簡寫方式,或讓您的措辭感覺不自然。Don't use unnatural contractions just to save space, or when they would make your words sound less conversational.

綠色長條的第六個螢幕擷取畫面,內有綠色核取記號和 Do 一字。Sixth screenshot of a green bar that has a green check mark and the word Do in it. 當您對影像感到滿意時,請選取 [儲存],將其新增到您的圖庫。When you're happy with your image, select save to add it to your gallery. 在那裡,您可以將它分享給朋友。From there, you'll be able to share it with friends.

句點Periods

在句尾加上句點,就表示該段文字是完整的句子。Ending text with a period implies that that text is a full sentence. 請在一大段文字後加上句點,若文字短於完整的句子,就請避免使用句點。Use a period for larger blocks of text, and avoid them for text that's shorter than a complete sentence.

  • 請在工具提示、錯誤訊息和對話方塊中,將完整的句子以句點結束。Use periods to end full sentences in tooltips, error messages, and dialogs.
  • 按鈕、選項按鈕、標籤或核取方塊的文字,則不要使用句點。Don't end text for buttons, radio buttons, labels, or checkboxes with a period.

綠色長條的第七個螢幕擷取畫面,內有綠色核取記號和 Do 一字。 您未連線。Seventh screenshot of a green bar that has a green check mark and the word Do in it. You’re not connected.

  • 請檢查網路纜線是否插上。Check that your network cables are plugged in.
  • 請確定您不是處於飛航模式。Make sure you're not in airplane mode.
  • 查看無線開關是否已開啟。See if your wireless switch is turned on.
  • 將路由器重新開機。Restart your router.

大寫Capitalization

雖然大寫字母意味有重要性,但很容易被濫用。While capital letters are important, they're easy to overuse.

  • 專有名詞應大寫。Capitalize proper nouns.
  • 應用程式中,每個文字字串的開頭都要大寫,也就是每個句子、標籤和標題的開頭均是如此。Capitalize the start of every string of text in your app: the start of every sentence, label, and title.

綠色長條的第八個螢幕擷取畫面,內有綠色核取記號和 Do 一字。 哪個部分發生問題?Eighth screenshot of a green bar that has a green check mark and the word Do in it. Which part is giving you trouble?

  • 我忘記密碼。I forgot your password.
  • 系統不接受密碼。It won't accept password.
  • 可能有其他人正在使用我的帳戶。Someone else might be using my account.

錯誤訊息Error messages

當您的應用程式發生問題時,使用者會特別留意。When something goes wrong in your app, users pay attention. 在遇到錯誤訊息時,使用者會感到困惑或挫折,所以良好的語氣和語調在這個區塊的影響格外巨大。Because users might be confused or frustrated when they encounter an error message, they're an area where good voice and tone can have a particularly significant impact.

更重要的是,錯誤訊息絕不能怪罪使用者。More than anything else, it's important that your error message doesn't blame the user. 也請不要用使用者不理解的資訊來轟炸他們。But it's also important not to overwhelm them with information that they don't understand. 大多數時候,遇到錯誤的使用者只想要趕快回去繼續進行本來在做的事,越快越輕鬆越好。Most of the time a user who encounters an error just wants to get back to what they were doing as quickly and as easily as they can. 因此,您撰寫的錯誤訊息應要達到以下效果:Therefore, any error message you write should:

  • 溫暖輕鬆,請交談般的語調,不要使用不常見的詞彙和技術術語。Be warm and relaxed by using a conversational tone and avoiding unfamiliar terms and technical jargon.

  • 伸出援手,盡您最大的能力,告訴使用者發生了什麼錯誤,告訴他們接下來會有什麼情況,並提供使用者可辦到的實際解決方案。Be ready to lend a hand by telling the user what went wrong to the best of your ability, by telling them what will happen next, and by providing a realistic solution they can accomplish.

  • 簡潔直白,排除無關的資訊。Be crisp and clear by eliminating extraneous information.

綠色長條的第九個螢幕擷取畫面,內有綠色核取記號和 Do 一字。 您未連線。Ninth screenshot of a green bar that has a green check mark and the word Do in it. You’re not connected.

  • 請檢查網路纜線是否插上。Check that your network cables are plugged in.
  • 請確定您不是處於飛航模式。Make sure you're not in airplane mode.
  • 查看無線開關是否已開啟。See if your wireless switch is turned on.
  • 將路由器重新開機。Restart your router.

對話方塊Dialogs

撰寫錯誤訊息的許多建議也同樣適用於為您的應用程式建立任何對話方塊的文字。Many of the same advice for writing error messages also applies when creating the text for any dialogs in your app. 即使使用者已預期會出現對話方塊,但對話方塊仍會中斷應用程式的一般流程,因此內容必須精簡有幫助,讓使用者能夠返回原本所進行的活動。While dialogs are expected by the user, they still interrupt the normal flow of the app, and need to be helpful and concise so the user can get back to what they were doing.

但最重要的是對話方塊的標題和其按鈕之間的「呼叫與回應」。But most important is the "call and response" between the title of a dialog and its buttons. 請確定您的按鈕是標題所張貼問題的明確答案,並且應用程式中所有按鈕的格式都一致。Make sure that your buttons are clear answers to the question posed by the title, and that their format is consistent across your app.

綠色長條的第十個螢幕擷取畫面,內有綠色核取記號和 Do 一字。 哪個部分發生問題?Tenth screenshot of a green bar that has a green check mark and the word Do in it. Which part is giving you trouble?

  1. 我忘記密碼I forgot my password
  2. 系統不接受我的密碼It won't accept my password
  3. 可能有其他人正在使用我的帳戶Someone else might be using my account

按鈕Buttons

按鈕上的文字必須夠簡潔,讓使用者一眼就能讀完,也必須夠清楚,讓按鈕的功能顯而易見。Text on buttons needs to be concise enough that users can read it all at a glance and clear enough that the button's function is immediately obvious. 按鈕上文字的長度上限應該只是幾組簡短文字,大部分時候應該更短。The longest the text on a button should ever be is a couple short words, and many should be shorter than that. 撰寫按鈕的文字時,請記住每個按鈕代表一個動作。When writing the text for buttons, remember that every button represents an action. 按鈕的文字請務必使用主動語態,並使用代表動作 (而非反應) 的文字。Be sure to use the active voice in button text, to use words that represent actions rather than reactions.

綠色長條的第十一個螢幕擷取畫面,內有綠色核取記號和 Do 一字。

  • 立即安裝Install now
  • 共用Share

口語體驗Spoken experiences

撰寫口語體驗 (例如 Cortana) 的文字時,一般原則和建議也同樣適用。The same general principles and recommendations apply when writing text for spoken experiences, such as Cortana. 對這些功能來說,優良的寫作準則更顯重要,因為您無法提供其他視覺設計元素讓使用者補充口語文字。In those features, the principles of good writing are even more important, because you are unable to provide users with other visual design elements to supplement the spoken words.

  • 溫暖輕鬆:請以交談式的語調吸引您的使用者。Be warm and relaxed by engaging your users with a conversational tone. 跟其他領域相比,口語體驗更需要聽起來溫暖且平易近人,讓使用者不會害怕與其交談。More than in any other area, it's vital that a spoken experience sound warm and approachable, and be something that users aren't afraid to talk to.

  • 伸出援手:當使用者詢問不可能的事項匙,請提供替代建議。Be ready to lend a hand by providing alternative suggestions when the user asks the impossible. 如同錯誤訊息,如果發生了問題,而您的應用程式無法滿足要求,則應改為提供可讓使用者嘗試詢問的實際替代方案。Much like in an error message, if something went wrong and your app isn't able to fulfill the request, it should give the user a realistic alternative that they can try asking, instead.

  • 簡潔直白:使用簡潔明瞭的說法。Be crisp and clear by keeping your language simple. 口語體驗不適合使用冗長的句子或複雜的字詞。Spoken experiences aren't suitable for long sentences or complicated words.

協助工具和當地語系化Accessibility and localization

撰寫應用程式時,如果能考慮到協助工具和當地語系化,您的應用程式就能適用於更多使用者。Your app can reach a wider audience if it's written with accessibility and localization in mind. 光靠文字無法達成這個目的,不過直白且友善的用字就是個很好的出發點。This is something that can't only be accomplished through text, though straightforward and friendly language is a great start. 如需詳細資訊,請參閱我們的協助工具概觀當地語系化指導方針For more information, see our accessibility overview and localization guidelines.

  • 伸出援手:將不同的體驗納入考量。Be ready to lend a hand by taking different experiences into account. 避免使用對國際使用者沒有意義的片語,也不要在文字中假設使用者做得到什麼、做不到什麼。Avoid phrases that might not make sense to an international audience, and don't use words that make assumptions about what the user can and can't do.

  • 簡潔直白:避免使用不必要的特殊詞彙及專有詞彙。Be crisp and clear by avoiding unusual and specialized words when they aren't necessary. 您的文字越直白,就越容易進行當地語系化。The more straightforward your text is, the easier it is to localize.

非寫手的技巧Techniques for non-writers

不需要是訓練有素或經驗豐富的作家,也能為使用者提供良好的體驗。You don't need to be a trained or experienced writer to provide your users with a good experience. 請挑選您聽起來舒適自在的用詞,如此一來,其他人也會有同樣的感受。Pick words that sound comfortable to you — they'll feel comfortable to others, too. 不過,有時候知易行難。But sometimes, that's not as easy as it sounds. 如果您遇到困難,以下有些技巧可以幫助您。If you get stuck, these techniques can help you out.

  • 請想像您正在向朋友談論您的應用程式。Imagine that you're talking to a friend about your app. 您會如何向他們解釋應用程式?How would you explain the app to them? 您如何介紹功能?如何說明使用方法?How would you talk about its features or give them instructions? 還有一種更好的方法,就是向尚未用過應用程式的人解說您的應用程式。Better yet, explain the app to an actual person who hasn't used it yet.

  • 請想像您會如何描述另一個完全不同的應用程式。Imagine how you would describe a completely different app. 舉例來說,如果您正在製作遊戲,請想像您會如何以口說或書寫的方式,來描述財務或新聞的應用程式。For instance, if you're making a game, think of what you'd say or write to describe a financial or a news app. 您所使用語言和結構的對比,會讓您更深入了解到實際撰寫項目的正確措辭。The contrast in the language and stucture you use can give you more insight into the right words for what you're actually writing about.

  • 查看類似的應用程式可尋找靈感。Take a look at similar apps for inspiration.

很多人可能會困擾於找不到正確用字,所以如果覺得聽起來不自然,而遲遲無法拍版定案,也不用太沮喪。Finding the right words is a problem that many people struggle with, so don't feel bad if it's not easy to settle on something that feels natural.