对应用进行可本地化处理Make your app localizable

本地化应用是一种可针对其他市场、语言或地区进行本地化且未发现应用中的任何功能性缺陷的应用。A localized app is one that can be localized for other markets, languages, or regions without uncovering any functional defects in the app. 可本地化应用最重要的属性是其可执行代码与其可本地化资源完全分隔。The most essential property of a localizable app is that its executable code has been cleanly separated from its localizable resources. 所以,你应确定哪些应用的资源需要进行本地化。So, you should determine which of your app's resources need to be localized. 问问你自己,如果应用要针对其他市场进行本地化,需要作出哪些更改?Ask yourself what needs to change if your app is to be localized for other markets.

我们还建议你熟悉全球化指南We also recommend that you become familiar with the guidelines for globalization.

将字符串置于资源文件 (.resw) 中Put your strings into Resources Files (.resw)

不要在强制性代码中,XAML 标记中,也不在你的应用程序包清单中的硬编码字符串文本。Don't hard-code string literals in your imperative code, XAML markup, nor in your app package manifest. 相反,将字符串放入资源文件 (.resw) 中,以便它们适合独立于你应用的生成二进制文件的不同本地市场。Instead, put your strings into Resources Files (.resw) so that they can be adapted to different local markets independently of your app's built binaries. 有关详细信息,请参阅本地化 UI 和应用程序包清单中的字符串For details, see Localize strings in your UI and app package manifest.

该主题还展示如何向你的默认资源文件 (.resw) 中添加注释。That topic also shows you how to add comments to your default Resources File (.resw). 例如,如果你要采用非正式语音或语调,请确保在注释中解释此情况。For example, if you are adopting an informal voice or tone then be sure to explain that in comments. 此外,为最大程度降低费用,请确认仅向翻译人员提供需要翻译的字符串。Also, to minimize expense, confirm that only the strings that need to be translated are provided to translators.

在应用程序包清单源文件(Package.appxmanifest 文件)中适当地设置应用的默认语言。Set the default language for your app appropriately in your app package manifest source file (the Package.appxmanifest file). 默认语言确定当用户的首选语言不匹配应用的所有支持语言时要使用的语言。The default language determines the language that's used when the user's preferred languages don't match any of the supported languages of your app. 使用语言(甚至是默认语言中的某种语言,例如 \Assets\en-us\Logo.png)标记所有资源,以便系统可以通知资源所使用的是哪种语言以及在特定情况下如何使用该语言。Mark all of your resources with their language (even the ones in your default language, for example \Assets\en-us\Logo.png) so that the system can tell which language the resource is in and how it's used in particular situations.

针对语言定制图像和其他文件资源Tailor your images and other file resources for language

理想情况下,你将能够对图像进行全球化—让其与特定文化无关。Ideally, you will be able to globalize your images—that is, make them culture-independent. 对于不能进行全球化的任何图像和其他文件资源,根据需要创建它们的多个不同变体,并将相应语言限定符置于它们的文件或文件夹名称中。For any images and other file resources where that's not possible, create as many different variants of them as you need and put the appropriate language qualifiers into their file or folder names. 若要了解详细信息,请参阅针对语言、缩放、高对比度和其他限定符定制资源To learn more, see Tailor your resources for language, scale, high contrast, and other qualifiers.

为了最大程度降低本地化成本,请不要将文字或文化敏感性材料置于开始的图像。To minimize localization costs, don't put text nor culturally-sensitive material into images to begin with. 适合你自己文化的图像可能在其他文化中具有冒犯性或会被曲解。An image that's appropriate in your own culture might be offensive or misinterpreted in other cultures. 避免使用文化特定的图像,例如世界上不通用的邮箱。Avoid the use of culture-specific images such as mailboxes, which are not common around the world. 避免使用特定于宗教符号、动物、政治或性别的图像。Avoid religious symbols, animals, political, or gender-specific images. 展示肉体、身体部位或手势也可能是敏感主题。The display of flesh, body parts, or hand gestures can also be a sensitive topic. 如果无法避免所有这些,则需要细致周到地进行图像本地化。If you can't avoid all of these, then your images will need to be thoughtfully localized. 如果要本地化为与你本身语言的读取方向不同的语言,请使用对称图像和效果,以便可以更容易地支持镜像。If you're localizing to a language with a different reading direction than your own, using symmetrical images and effects make it easier to support mirroring.

另请避免在图像中使用文字,以及在音频/视频文件中使用语音。Also avoid the use of text in images, and speech in audio/video files.

在应用中使用颜色The use of color in your app

使用颜色时请注意。Be mindful when using color. 使用与国旗或政治运动关联的颜色组合可能有问题。Using color combinations that are associated with national flags or political movements can be problematic. 颜色选择可能需要由文化专家进行审阅。Color choices may need to be reviewed by culture experts. 使用颜色还存在辅助功能问题。There is also an accessibility issues with using color. 如果使用颜色传达含义,则还应通过其他方法(如大小、形状或标签)传达相同信息。If you use color to convey meaning then you should also convey that same information by some other means, such as size, shape, or a label.

在句子中考虑字符串因素Consider factoring your strings into sentences

使用大小适当的字符串。Use appropriately-sized strings. 短字符串更易于翻译,且可循环利用其翻译(这可节省费用,因为不会将相同字符串多次发送给本地化人员)。Short strings are easier to translate, and they enable translation recycling (which saves expense because the same string isn't sent to the localizer more than once). 此外,本地化工具可能不支持过长的字符串。Also, extremely long strings might not be supported by localization tools.

但是,与本指南相冲突的是会产生在不同上下文中重复使用某一字符串的风险。But in tension with this guideline is the risk of re-using a string in different contexts. 即使是 "on" 和 "off" 等简单字词也可能会基于上下文产生不同的翻译结果。Even simple words such as "on" and "off" might be translated differently, depending on the context. 在英语中,“on”和“off”可用于飞行模式、蓝牙和设备的切换。In the English language, "on" and "off" can be used for a toggle for Flight Mode, Bluetooth, and devices. 但在意大利语中,翻译取决于要打开和关闭的内容的上下文。But in Italian, the translation depends on the context of what is being turned on and off. 可能需要为每个上下文创建一对字符串。You would need to create a pair of strings for each context. 在两个上下文相同的情况下可以重复使用字符串。You can reuse strings if the two contexts are the same. 例如,你可以针对声音效果音量和音乐音量重复使用字符串“Volume”,因为二者均指声音的强度。For instance, you can reuse the string "Volume" for both sound effect volume and music volume because both refer to intensity of sound. 但不应该在指硬盘卷时使用同一字符串,因为二者的上下文和含义是不同的,因此该字词可能会具有不同的翻译。You should not reuse that same string when referring to a hard disk volume because the context and meaning are different, and the word might be translated differently.

此外,诸如“text”或“fax”之类的字符串在英语中可用作动词和名词,在翻译过程中这可能会造成混淆。Additionally, a string like "text" or "fax" could be used as both a verb and a noun in the English language, which can confuse the translation process. 因此,为动词和名词格式创建单独的字符串。Instead, create a separate string for both the verb and noun format. 在不确定上下文是否相同时,为稳妥起见使用不同的字符串。When you're not sure whether the contexts are the same, err on the safe side and use a distinct string.

简而言之,将字符串分解为在所有上下文中均起作用的几个部分。In short, factor your strings into pieces that work in all contexts. 将出现需要将某一字符串作为整个句子的情况。There will be cases where a string will need to be an entire sentence.

请考虑以下字符串:"{0}无法同步。"Consider the following string: "The {0} could not be synchronized."

大量的字词可能会替换{0},如"约会"、"任务"或"文档"。A variety of words could replace {0}, such as "appointment", "task", or "document". 虽然此示例适用于英语,但它绝不适用于德语等的相应语句。While this example works for the English language, it will not work in all cases for the corresponding sentence in, for example, German. 请注意以下德语语句,模板字符串中的某些字词(“Der”、“Die”、“Das”)需要与参数化的字词匹配:Notice that in the following German sentences, some of the words in the template string ("Der", "Die", "Das") need to match the parameterized word:

英语English 德语German
The appointment could not be synchronized.The appointment could not be synchronized. Der Termin konnte nicht synchronisiert werden.Der Termin konnte nicht synchronisiert werden.
The task could not be synchronized.The task could not be synchronized. Die Aufgabe konnte nicht synchronisiert werden.Die Aufgabe konnte nicht synchronisiert werden.
The document could not be synchronized.The document could not be synchronized. Das Dokument konnte nicht synchronisiert werden.Das Dokument konnte nicht synchronisiert werden.

在另一个示例中,考虑语句"提醒我在{0}分钟后。"As another example, consider the sentence "Remind me in {0} minute(s)." “minute(s)”适用于英语,但其他语言可能会使用不同的术语。Using "minute(s)" works for the English language, but other languages might use different terms. 例如,波兰语使用“minuta”、“minuty”或“minut”,具体取决于上下文。For example, the Polish language uses "minuta", "minuty", or "minut" depending on the context.

若要解决此问题,应本地化整个语句,而不应只本地化单个字词。To solve this problem, localize the entire sentence, rather than a single word. 这么做看似增加了额外工作量且是个不明智的解决方案,但其实是最佳解决方案,原因如下:Doing this may seem like extra work and an inelegant solution, but it is the best solution because:

  • 会针对所有语言显示一个语法正确的消息。A grammatically correct message will be displayed for all languages.
  • 翻译无需询问该字符串将会被什么词替代。Your translator will not need to ask about what the strings will be replaced with.
  • 当应用完成后出现类似于此图面的问题时,也无需实施高成本的代码修复。You will not need to implement a costly code fix when a problem like this surfaces after your app is completed.

字符串的其他注意事项Other considerations for strings

避免在以默认语言编写的字符串中使用俗语或隐喻。Avoid colloquialisms and metaphors in the strings that you author in your default language. 特定于某种人群的语言(如文化和年龄)很难理解或翻译,因为只有属于该类人群的人才会使用该语言。Language that's specific to a demographic group, such as culture and age, can be hard to understand or translate because only people in that demographic group use that language. 同样,比喻可能对于一个人而言有意义,而对其他人而言没有意义。Similarly, metaphors might make sense to one person but mean nothing to someone else. 例如,"蓝鸟"对于了解滑雪文化的人而言表示特定意义,但对于不了解该文化的人而言则没有意义。For example, a "bluebird" means something specific to those who are part of skiing culture, but those who aren’t part of that culture don’t understand the reference.

请勿使用技术行话、缩写或缩略语。Don't use technical jargon, abbreviations, or acronyms. 技术语言很有可能不会被来自其他文化或区域的非技术用户或人员所理解,并且也很难翻译。Technical language is less likely to be understood by non-technical audiences or people from other cultures or regions, and it's difficult to translate. 人们在日常对话中不会采用这样的说法。People don't use these kinds of words in everyday conversations. 技术语言通常显示在识别硬件和软件问题的错误消息中,但在仅当用户需要此级别的信息,并且可以对其进行操作或找到可以对其进行操作的人时才应将字符串化为技术语言。Technical language often appears in error messages to identify hardware and software issues, but you should strings to be technical only if the user needs that level of information, and can either action it or find someone who can.

在字符串中使用非正式语音或语调是一种有效的选择。Using an informal voice or tone in your strings is a valid choice. 可以在默认资源文件 (.resw) 中使用注释来表明该目的。You can use comments in your default Resources File (.resw) to indicate that intention.


伪本地化你的应用,找出任何本地化问题。Pseudo-localize your app to uncover any localizability issues. 伪本地化是一种本地化预演或问题揭露测试。Pseudo-localization is a kind of localization dry-run, or disclosure test. 生成一组未真正翻译的资源;它们看起来就是那样子的。You produce a set of resources that are not really translated; they only look that way. 例如,你的字符串大约比默认语言长 40%,并且字符串中具有分隔符,以便你可以一眼就看出它们在 UI 中是否被截断。Your strings are approximately 40% longer than in the default language, for example, and they have delimiters in them so that you can see at a glance whether they have been truncated in the UI.

部署注意事项Deployment Considerations

安装包含本地化的语言数据的应用时,你可能会发现仅的默认语言是适用于应用,即使你最初包含多种语言的资源。When you install an app that contains localized language data, you might find that only the default language is available for the app even though you initially included resources for multiple languages. 这是设备的因为在安装过程经过优化,可仅安装匹配当前的语言和文化的语言资源。This is because the installation process is optimized to only install language resources that match the current language and culture of the device. 因此,如果你的设备配置为 EN-US,仅 EN-US 语言资源被安装与你的应用。Therefore, if your device is configured for en-US, only the en-US language resources are installed with your app.


不能在初始安装之后安装适用于应用的其他语言支持。It is not possible to install additional language support for your app after the initial installation. 如果安装应用后更改默认语言,应用将继续使用仅原始的语言资源。If you change the default language after installing an app, the app continues to use only the original language resources.

如果你想要确保在安装后可用的所有语言资源,创建应用包的指定某些资源 (包括语言资源) 的安装过程中所需的配置文件。If you want to ensure all language resources are available after installation, create a configuration file for the app package that specifies that certain resources are required during installation (including language resources). 在打包过程中生成应用程序的.appxbundle 时,此优化的安装功能将自动启用。This optimized installation feature is automatically enabled when your application's .appxbundle is generated during packaging. 有关详细信息,请参阅确保无论设备是否需要它们在设备上安装了资源For more information, see Ensure that resources are installed on a device regardless of whether a device requires them.

(可选),以确保所有资源都都安装 (而不只是一个子集),可以禁用.appxbundle 生成你的应用打包时。Optionally, to ensure all resources are installed (not just a subset), you can disable .appxbundle generation when you package your app. 不建议此方法但是因为它可以增加你的应用的安装时间。This is not recommended however as it can increase the installation time of your app.

通过将"生成应用 Bundle"属性设置为"从不"禁用自动生成.appxbundle:Disable automatic generation of the .appxbundle by setting the "Generate App Bundle" attribute to “never”:

  1. 在 Visual Studio 中,右键单击项目名称In Visual Studio, right-click the project name
  2. 选择应用商店 -> 创建应用包...Select Store -> Create app packages...
  3. 创建程序包对话框中,选择想要创建程序包上传到 Microsoft Store 使用新的应用名称,然后单击下一步In the Create Your Packages dialog, select I want to create packages to upload to the Microsoft Store using a new app name and then click Next.
  4. 选择应用名称对话框中,选择/创建了应用命名为你的程序包。In the Select an app name dialog, select/create an app name for your package.
  5. 选择并配置程序包对话框中,将生成应用程序包设置为从不In the Select and Configure Packages dialog, set Generate app bundle to Never.

地缘政治意识Geopolitical awareness

在地图中或在涉及地理区域时避免政治冒犯。Avoid political offense in maps or when referring to regions. 地图可能包含有争议的地理区域或国界,并且这是引起政治冲突的常见原因。Maps might include controversial regional or national boundaries, and they're a frequent source of political offense. 请务必小心用于选择国家/地区的任何 UI,应将其称为“国家/地区”。Be careful that any UI used for selecting a nation refers to it as a "country/region". 将有争议的领土列于标记为“国家/地区”的列表(例如地址表)中可能会冒犯某些用户。Listing a disputed territory in a list labeled "countries"—such as in an address form—might offend some users.

更改了语言和地区的事件Language- and region-changed events

订阅在系统的语言和地区设置更改时引发的事件。Subscribe to events that are raised when the system's language and region settings change. 执行此操作,以便在适当情况下可以重新加载资源。Do this so that you can re-load resources, if appropriate. 有关详细信息,请参阅响应限定符值更改事件更新字符串响应限定符值更改事件更新图像For details, see Updating strings in response to qualifier value change events and Updating images in response to qualifier value change events.

设置字符串格式时,请确保正确的参数顺序Ensure the correct parameter order when formatting strings

不要假设所有语言都以相同顺序表示参数。Don't assume that all languages express parameters in the same order. 例如,请考虑以下格式。For example, consider this format.

    string.Format("Every {0} {1}", monthName, dayNumber); // For example, "Every April 1".

此示例中的格式字符串适用于英语(美国)。The format string in this example works for English (United States). 但不适用于德语(德国),例如,其中的日期和月份以相反顺序显示。But it is not appropriate for German (Germany), for example, where the day and month are displayed in the reverse order. 确保翻译人员知道每个参数的意图,以便它们可以反转中的格式字符串的格式项的顺序 (例如,"{1} {0}"),适用于目标语言。Ensure that the translator knows the intent of each of the parameters so that they can reverse the order of the format items in the format string (for example, "{1} {0}") as appropriate for the target language.

不要过度本地化Don’t over-localize

仅向翻译提供自然语言;不要提供编程语言或标注。Only submit natural language to translators; not programming language nor markup. <link> 标记不是自然语言。A <link> tag is not natural language. 看看下面的示例。Consider these examples.

不要将其进行本地化Don't localize this 将其进行本地化Localize this
<link>使用条款</link><link>terms of use</link> 使用条款terms of use
<link>隐私策略</link><link>privacy policy</link> 隐私策略privacy policy

在资源文件 (.resw) 中包括 <link> 标记也意味着很有可能要进行翻译。Including the <link> tag in your Resources File (.resw) means that it, too, is likely to be translated. 这将导致标记无效。That would render the tag invalid. 如果具有需要包括标注以便维护上下文并确保排序的长字符串,请在注释中明确说明无需进行翻译的内容。If you have long strings that need to include markup in order to maintain context and ensure ordering, then make it clear in comments what not to translate.

选择适当的翻译方法Choose an appropriate translation approach

在字符串分为资源文件后,就可以对其进行翻译了。After strings are separated into resource files, they can be translated. 翻译字符串的理想时间为在项目中的字符串敲定后,这通常发生在项目的后期。The ideal time to translate strings is after the strings in your project are finalized, which usually happens toward the end of a project. 可以采用多种方法完成翻译流程。You can approach the translation process in number of ways. 这可能要取决于待翻译的字符串的量、待翻译的语言数以及如何完成翻译(例如,内部翻译或雇用外部供应商)。This may depend on the volume of strings to be translated, the number of languages to be translated, and how the translation will be done (such as in-house versus hiring an external vendor).

不妨请考虑以下几个选项。Consider these options.

  • 直接在项目中打开资源文件,即可对其进行翻译。The resource files can be translated by opening them directly in the project. 对于需要翻译成两种或三种语言的字符串数量较少的项目,此方法比较适用。This approach works well for a project that has a small volume of strings that need to be translated into two or three languages. 在开发人员使用多种语言并且愿意处理翻译过程的情况下,可以使用这种方法。It could be suitable for a scenario where a developer speaks more than one language and is willing to handle the translation process. 这种方法的优势在于快速、无需工具并且误译的风险最小。This approach benefits from being quick, requires no tools, and minimizes the risk of mistranslations. 但这种方法不可扩展。But it is not scalable. 特别是,不同语言中的资源很容易不同步,这会导致不好的用户体验和维护困难。In particular, the resources in different languages can easily get out of sync, causing bad user experiences and maintenance headaches.
  • 字符串资源文件采用 XML 或 ResJSON 文本格式,因此可以使用任何文本编辑器交付它们以供翻译。The string resource files are in XML or ResJSON text format, so could be handed off for translation using any text editor. 然后,再将已翻译的文件复制回项目中。The translated files would then be copied back into the project. 此方法存在翻译人员意外编辑 XML 标记的风险,但它允许在 Microsoft Visual Studio 项目外进行翻译工作。This approach carries a risk of translators accidentally editing the XML tags, but it lets translation work take place outside of the Microsoft Visual Studio project. 对于需要翻译成少数几种语言的项目,此方法可能比较适用。This approach could work well for projects that need to be translated into a small number of languages. XLIFF 格式是专门用于本地化的 XML 格式,应该可以很好地受到一些本地化供应商或本地化工具的支持。The XLIFF format is an XML format specifically designed for use in localization, and should be well supported by some localization vendors or localization tools. 你可以使用多语言应用工具包从其他资源文件中(如 .resw 或 .resjson)生成 XLIFF 文件。You can use the Multilingual App Toolkit to generate XLIFF files from other resource files, such as .resw or .resjson.


本地化可能还需要其他资源,包括图像和音频文件。Localization might also be necessary for other assets, including images and audio files.

你还应该考虑以下:You should also consider the following:

  • 本地化工具用于解析资源文件,并仅允许翻译的字符串编辑可翻译人员提供了大量的本地化工具。Localization tools A number of localization tools are available for parsing resource files and allowing only the translatable strings to be edited by translators. 这种方法减少了翻译人员意外编辑 XML 标记的风险。This approach reduces the risk of a translator accidentally editing the XML tags. 但它的缺点是向本地化流程中引入了新的工具和流程。But it has the drawback of introducing a new tool and process to the localization process. 本地化工具适合具有大量字符串但需要翻译为少数语言的项目。A localization tool is good for projects with a large volume of strings but a small number of languages. 若要了解详细信息,请参阅如何使用多语言应用工具包To learn more, see How to use the Multilingual App Toolkit.
  • 本地化供应商请考虑使用本地化供应商,如果你的应用程序包含大量字符串需要翻译成大量的语言。Localization vendors Consider using a localization vendor if your application contains extensive strings that need to be translated into a large number of languages. 本地化供应商可提供有关工具和流程的建议,并可翻译你的资源文件。A localization vendor can give advice about tools and processes, as well as translating your resource files. 这是一种理想的解决方案,但也是花费最大的选项,并且会增加翻译内容的检查时间。This is an ideal solution, but is also the most costly option, and may increase the turnaround time for your translated content.

使访问键和标签保持一致Keep access keys and labels consistent

将用于辅助功能的访问键与本地化的访问键的显示“同步”比较困难,因为这两个字符串资源被分类为两个单独的部分。It is a challenge to "synchronize" the access keys used in accessibility with the display of the localized access keys, because the two string resources are categorized in two separate sections. 请确保为标签字符串提供注释,如:Be sure to provide comments for the label string such as: Make sure that the emphasized shortcut key is synchronized with the access key.

支持可进行排序的日语字符串的假名注音Support furigana for Japanese strings that can be sorted

日语汉字字符具有根据字词和使用它们的上下文具有多个发音的属性。Japanese kanji characters have the property of having more than one reading (pronunciation) depending on the word in which they are used. 这在尝试排序日语命名对象(例如,应用程序名称、文件、歌曲等)时会引发问题。This leads to problems when you try to sort Japanese named objects, such as application names, files, songs, and so on. 以前,日语日文汉字通常采用名为 XJIS 的计算机可理解的顺序进行排序。Japanese kanji have, in the past, usually been sorted in a machine-understandable order called XJIS. 但是,由于此排序顺序是非注音的,因此使用并不人性化。Unfortunately, because this sorting order is not phonetic it is not very useful for humans.

汉字注音允许用户或创建者指定所使用字符的注音,因而可解决此问题。Furigana works around this problem by allowing the user or creator to specify the phonetics for the characters they are using. 如果使用以下过程向应用名称添加假名注音,则可以确保该名称排序在应用列表的适当位置。If you use the following procedure to add furigana to your app name, you can ensure that it is sorted in the proper location in the app list. 如果应用名称包含日文汉字字符并且没有提供假名注音,则当用户的 UI 语言或排序顺序设置为日语时,Windows 将尽量生成适当的发音。If your app name contains kanji characters and furigana is not provided when the user’s UI language or the sort order is set to Japanese, Windows makes its best effort to generate the appropriate pronunciation. 然而,也可能会依据较常见的读音对包含少见或独特读音的应用名称进行排序。However, there is a possibility for app names containing rare or unique readings to be sorted under a more common reading instead. 因此,用于日语应用程序(尤其是名称中包含日文汉字字符的应用程序)的最佳做法是:在日语本地化过程中提供其应用名称的汉字注音版本。Therefore, the best practice for Japanese applications (especially those containing kanji characters in their names) is to provide a furigana version of their app name as part of the Japanese localization process.

  1. 添加“ms-resource:Appname”作为程序包显示名称和应用程序显示名称。Add "ms-resource:Appname" as the Package Display Name and the Application Display Name.
  2. 在字符串下创建 ja-JP 文件夹并添加两个资源文件,如下所示:Create a ja-JP folder under strings, and add two resource files as follows:

  3. 在用于常规 ja-JP 的 Resources.resw 中:添加用于应用名称“希蒼”的字符串资源In Resources.resw for general ja-JP: Add a string resource for Appname "希蒼"

  4. 在用于日语汉字注音资源的 Resources.altform-msft-phonetic.resw 中:添加用于应用名称“のあ”的汉字注音值In Resources.altform-msft-phonetic.resw for Japanese furigana resources: Add furigana value for AppName "のあ"

用户可以搜索应用名称“希蒼”,方法是使用汉字注音值“のあ”(noa),也可以使用注音值(通过输入法编辑器 (IME) 使用 GetPhonetic 功能)“まれあお”(mare-ao)。The user can search for the app name "希蒼" using both the furigana value "のあ" (noa), and the phonetic value (using the GetPhonetic function from the Input Method Editor (IME)) "まれあお" (mare-ao).

按照区域控制面板格式排序:Sorting follows the Regional Control Panel format:

  • 在日语用户区域设置下,Under a Japanese user locale,
    • 如果启用汉字注音,则“希蒼”排序在“の”下。If furigana is enabled, then "希蒼" is sorted under "の".
    • 如果没有汉字注音,则“希蒼”排序在“ま”下。If furigana is missing, then "希蒼" is sorted under "ま".
  • 在非日语用户区域设置下,Under a non-Japanese user locale,
    • 如果启用汉字注音,则“希蒼”排序在“の”下。If furigana is enabled, then "希蒼" is sorted under "の".
    • 如果没有汉字注音,则“希蒼”排序在“漢字”下。If furigana is missing, then "希蒼" is sorted under "漢字".