• Content Submitters in Approval Chain Able to Publish In Unexpected Languages

    DescriptionContent submitters in an approval chain may be able to submit content in languages other than the language used for the folder's first approval chain.CauseApproval chains are only setup for one language at a time, so if it's missing for a language, content submitters will be able to publish with that language. Resolution1) View the folder properties. 2) Select the language without the approval chain using the language dropdown. 3) Choose the approvals option and add the desi...

  • Could not find part of path error on importing translated content

    DescriptionWhen attempting to import a translated XLIFF file the following could not find part of path error is thrown in the history for imported content, and the translated content is not imported.   CauseThis error message can be caused when the content that was exported for translation is exported again before the original translation can be imported again. Since the database only tracks the most recent XLIFF file that was translated it will not allow for the originally exported XLIFF fi...

  • Error: Culture is not supported

    DescriptionWhen you try to edit content in another language, the content does not open and the following error occurs: Culture is not supported . Y ou may also get an error in Windows Event Viewer similar to: error: culture is not supported. Parameter name: culture XXXXXXX (0x100002) is an invalid culture identifier.  (XXXXXXX is a seven digit number) CauseIf you enabled a language that was among the standard set of supported languages, and tried to edit content in that language, you...

  • How to disable languages that were created accidentally or are not needed

    DescriptionIMPORTANT : This procedure works on languages that are not already associated with content.Creating languages that are duplicates of pre-existing languages can cause a variety of issues within the Workarea and can confuse users.  CauseAdding languages lets you create related dialects or languages not already in the language list. Duplicate languages create issues in the Workarea. ResolutionTo disable a language:Go to Workarea > Settings > Localization > Lang...

  • Machine Language Translation

    Description The old machine translation utility has been deprecated. This article will go over converting the machine language translation provider to Microsoft Translate. It is a fairly painless process, but does require some workarea modifications. An alternative approach is presented in another KB article, which uses Google Translate and is easier to set up: /KB/1125/ Resolution In the workarea, if you click on the translate button, the content will either not translate or it...

  • Not all metadata is exported for translation

    DescriptionWhen importing translated content some of the metadata definitions are not imported into the content, but some are. ResolutionThe CMS only exports metadata that is of the type text for translation. Other types of metadata such as yes/no and long will not be included in the export of the content, and will need to be manually set after importing the translated content.

  • Translating Taxonomies

    DescriptionCannot export taxonomies ResolutionIf you cannot export taxonomies, then you are probably missing a setting.  Before you can export the taxonomies for translation you will need to check the synchronize settings box. This can be done by right clicking on the taxonomy > properties > edit, Towards the bottom will be the synchronize languages check box.  After this is check and saved you will then be able to export the taxonomy for translation.

  • Translating the application strings

    DescriptionThe ResGen.exe utility (included with Microsoft Visual Studio 2003 and 2005) creates resource files, which are used by .NET in a .NET application for localization. You also can change the native string text values.You can also translate the files with a free program called Lutz Roeder's .net Resourcer ResolutionFiles needed:ResGen.exe is typically located at C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin>ResGen.exe.The base resources files for CMS are loca...

  • XLIFF localization did not import image selector metadata

    DescriptionXLIFF localization did not import image selector metadata.Multi-languages metadata for your Image Selector are setup for the metadata field. Content was exported with the metadata field. Translator had updated the valud for the metadata in the XLIFF. However, the metadata appeared blank when the new localized content was inspected. ResolutionFor older versions, please check "Setting up the Process to Apply Translated Metadata to Content". For v8.7+, the multiple la...