To help improve the quality of localization, you can use the following two Markdown tags:
[!DNL]:DNL means do not localize. Use DNL sparingly. Normally, product names are automatically left in English. However, you must apply DNL to branded application names (both Adobe and third-party brands) when your reference to a product is potentially confusing. This issue occurs with functional branded names like Target and Analytics. See When to apply DNL (below) for an important explanation.
[!UICONTROL]:Apply to features and clickable UI elements, especially in navigation and procedures. See How, why, and where to apply UICONTROL (below) for examples.
Use this table to help determine whether a term is localized or remains in English.
|Application||DNL / UICONTROL Tag?||English or Localized|
|Advertising||Apply DNL if confusing||English|
|Analytics||Apply DNL if confusing||English|
|Experience Platform Data||Add Adobe or DNL if confusing||English|
|Experience Platform Content||Add Adobe or DNL if confusing||English|
|Campaign||Add Adobe or DNL if confusing||English|
|Commerce||Add Adobe or DNL if confusing||English|
|Customer Journey Analytics||None||English|
|Real-Time Customer Data Platform||None||English|
|Target||Add Adobe or DNL if confusing||English|
|Sign||Add Adobe or DNL if confusing||English|
The following features and products were previously translated and now are to be left in English.
|Application||Product/feature||DNL guidance||English or Localized|
|Reports & Analytics||DNT||English|
|Ad Hoc Analysis||DNT||English|
|Audience Manager||Identity Management||DNT||English|
|Visual Cross-channel Orchestration||DNT||English|
|Integrated Customer Profile||DNT||English|
|Centralized Offer Management||DNT||English|
|Real-time Interaction Management||DNT||English|
|Marketing Campaign Management||DNT||English|
|Experience Manager||Sites||DNL if confusing||English|
|Assets||DNL if confusing||English|
|Mobile||DNL if confusing||English|
|Forms||DNL if confusing||English|
|Communities||DNL if confusing||English|
|Screens||DNL if confusing||English|
|Experience Platform||Data||DNL if confusing||English|
|Content||DNL if confusing||English|
|Magento Commerce||B2C & B2B commerce||DNT||English|
|Segmentation & Personalization||DNT||English|
|Shipping & Fulfillment||DNT||English|
|Marketo Engage||Lead Nurturing & Management||DNT||English|
|Personalization||DNL if confusing||English|
|Integrated Sales Applications||DNT||English|
|Marketing Measurement & Attribution||DNT||English|
|Geotargeting||DNL if confusing||English|
|Recommendations||DNL if confusing||English|
|Workfront||Fusion||DNL if confusing||English|
|Goals||DNL if confusing||English|
|Scenario Planner||DNL if confusing||English|
The DNL tag is for application and feature names that must always be in English. Using functional product names generically, such as Target without Adobe, causes the MT to not know your meaning. Or, it might incorrectly use a string in the translation memory. Using DNL or adding Adobe, ensures the strings remain in English.
If an application or core product name is in the DNT list, you do not need to apply DNL (do not localize).
Guidance for DNL
#sccm-assistancefor a regular expression that lets you easily search and replace DNL with UICONTROL. SCCM can help you retrofit these as well, and more. Get help here because it’s preferable that you continue writing instead of retrofitting content.
[!DNL Mozilla Firefox].
Examples of potentially confusing sentences
* With Target, you can create A/B tests to target specific geo-locations. * Adobe Analytics is a powerful application that collects analytics on your site. Analytics can also help you with reporting to easily digest that data.
Whenever you refer to a feature or interface control name (for example,
"Click Save"), applying UICONTROL to the specific feature/option/field name benefits the reader. UICONTROL preserves English if the product is not available in the language in which the documentation was translated.
In the following example, the Analytics interface is not available in Italian. However, all the documentation is translated:
In this scenario, the customer cannot follow the Italian interface instructions because UICONTROL was not applied to interface elements in Markdown.
Here’s the UICONTROL syntax, bolded in procedures:
1. Click **[!UICONTROL File]** > **[!UICONTROL Print]**.
That syntax serves two purposes:
Important: Do not use DNL in place of UICONTROL. Remember, DNL only applies to names that must remain in English in all languages, such as branded product names. UICONTROL is for words that conditionally need to remain in English, depending on product availability in a given language.
Click **[!UICONTROL Open Editor]**.
Click the **[!UICONTROL Open Editor button.]**
Click **[!UICONTROL File]** > **[!UICONTROL Print]** > **[!UICONTROL Paper Size]**.
Click **[!UICONTROL File > Print > Paper Size.]**
The following example shows isolated steps and multiple steps. It shows various syntax situations for applying UICONTROL. They include when to use bold, how to use UICONTROL when referring to tabs, fields, navigation, and clickable options.
[Editor’s note: If you’re new to technical writing, the following example also shows various ways to correctly write a typical command step or series of steps. It shows when to use on versus in, and how to refer to a product, page, or tab. Use sign-in instead of log-in, and learn how to document a menu, fields, and options.]
1. Sign in to Experience Cloud, then click **System Status**. 1. In Admin Console, on the Users page, click **Export CSV**. 1. Click the **Setup** tab, then complete the Email field. 1. On the Setup tab, click **Run**. 1. Sign in to Experience Cloud, then click **Analytics**. 2. In Workspace, click **Components** > **Segments**. 3. On the Segments page, click **Add**. 4. On the New Segment page, complete the following fields: * **Title**: Here you'd describe the Title field and apply !UICONTROL whenever you refer to it. * **Tags**: Here you'd describe the Tags field. 5. Enable **Publish this segment to Experience Cloud**. This field publishes this segment to the Audience Library in Experience Cloud, where you can use it in marketing activities in Target and other Experience Cloud applications. 6. Click **Save**. 1. On Report Suite Manager, click **Edit Settings** > **General** > **General Account Settings**. 2. Complete the following fields: * **Site title**: Here you'd describe the Site title field and apply !UICONTROL whenever you refer to it. * **Base URL**: Here you'd describe Base URL. 3. Click **Save**.
Make applying these elements easier by using keyboard shortcuts.
Keep in mind that machine-translated content doesn’t need to be perfect.
You can apply
!DNL tags in nearly any component, including:
Do not use DNL or UICONTROL in HTML tables. See When not to use DNL or UICONTROL for more information.
Do not add
!DNL tags to the following components:
[!DNL]unless you want that syntax to appear in the code block.
[!DNL]in HTML tables don’t work properly. Instead, use the
If you don’t know what languages are available for your product UI, you can ask the IEM. Here are the current solutions and available languages:
Of the three tagging options described on this page, UICONTROL is the most crucial for delivering high-quality translation. Consider UICONTROL to be mandatory in procedures. However, it is understood that, at times, you might not apply it perfectly. Just do your best. You can always go back and make corrections.
The syntax works as expected.
For links, the syntax does not work as expected. It’s necessary to remove the tag brackets within the link text to prevent the brackets from appearing in the link. (Note that this behavior might change at some point.)
Link test cases:
We have a DNT file that you can update with words you want to leave in English by default. Formal, long solution names like Adobe Analytics, Adobe Campaign, and Adobe Target are on the list.
If a term is added to the DNT list, it applies to all languages and all products. Add the term only if you are 100% certain that it fits these criteria. Also, there is a lag between when the term is added to the DNT list and when the engine is trained on that new list. (Also, training the list can be expensive.)
Follow the instructions on updating the DNT list to get started.
This element is not often used. Sometimes, we need to flag certain sections of content within an article to be English only. For sections of text that should not be localized, use the
[!DONOTLOCALIZE] extension and use block quotes ( > ) to mark the entire English-only section. The content after the DONOTLOCALIZE block will be localized when the file is submitted.
Code blocks (
code) are not localized by default. There is no need to apply the DONOTLOCALIZE tag to either fenced or inline code blocks.
If you really want to dive into research to determine which terms are used in the database, the following localization resources are available:
For images that should not be localized, create a separate
do-not-localize folder in the assets folder. Typically, images without text or images containing only sample content would be placed there. This removes any “noise” from the assets folder and reduces the amount of questions.
We also recommend that you remove any assets that you’re not referencing and don’t plan to reference. Maintaining clean asset folders helps the Localization team avoid unnecessary work.