text/microsoft-resx 2.0 System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 The connection string to connect to the Azure Analysis Services (Azure AS) or SQL Server Analysis Services (SSAS) data model, or Power BI Premium dataset The full path to the export folder. Existing translations exported to: {0} In Import mode, determines if the string from the default locale should be applied to the translated locale if the translated string is missing or cannot be found. The default setting is false, which leaves the translated string empty in the translated locale. The full path and name of the comma-separated values (csv) or resource (resx) translation file to import. Translation file {0} imported successfully. Invalid translation file type. The file must be either a comma-separated values (csv) file or a resource (resx) file. Either the imported language matches the default locale, or the file name does not correspond to a supported locale identifier. The file name convention is <lcid>.csv or <lcid>.resx. In ExportResx mode, influences how Metadata Translator generates the names of the key/value pairs. By default, a random GUID is generated as the name. If a key prefix is specified, then Metadata Translator generates keys based on the translated property types and the metadata object names. A valid Windows Language Code Identifier (LCID), aka language tag, such as en-US, af-NA, and zh-CN. The mode of the command-line operation This dataset has no translations. Use the --export-folder option to specify an export folder for this operation. Use the --import-file option to specify an import file for this operation. No translated strings found! The keys of the reference resx '{0}' and the translation resx '{1}' don't seem to match. Unable to import '{0}' because the reference resx file with the default language strings was not found. In addition to the import resx, make sure the following reference resx file also exists: {1} Metadata Translator command-line app Translations for '{0}' exported to: {1}