From 44cb925705d85dcf8a26e963e3dfb3ff5aab4592 Mon Sep 17 00:00:00 2001 From: Kay Unkroth Date: Tue, 6 Apr 2021 18:19:08 -0700 Subject: [PATCH] Readme updated --- MetadataTranslator/Metadata Translator/Documentation/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MetadataTranslator/Metadata Translator/Documentation/README.md b/MetadataTranslator/Metadata Translator/Documentation/README.md index 93c3a76..9b7939e 100644 --- a/MetadataTranslator/Metadata Translator/Documentation/README.md +++ b/MetadataTranslator/Metadata Translator/Documentation/README.md @@ -196,7 +196,7 @@ For illustration, imagine the following scenario: #### Generating static key names instead of random GUIDs -If you find GUID-based resx files difficult to work with, you can switch to more statically generated key names based on the translated property types and the metadata object names in your dataset. In this case, use the --key-prefix option to specify an arbitrary prefix in ExportResx mode. With a key prefix specified, Metadata Translator generates key names following the format: ##. +If you find GUID-based resx files difficult to work with, you can switch to more statically generated key names based on the translated property types and the metadata object names in your dataset. In this case, use the --key-prefix option to specify an arbitrary prefix in ExportResx mode. With a key prefix specified, Metadata Translator generates key names following the format: \#\#\. The following command exports all translations from an AdventureWorks dataset hosted in Power BI into resx files in a folder called ExportedTranslations using static key names instead of random GUIDs in the resx files (see also the following screenshot for a generated resx):