Mapping language resource templates to file type configurations

You can use the language resource templates (LRTs) that you create in SDL Trados Studio to define segmentation rules for WorldServer file type configurations. For example, you might have two configurations for the Rich Text Format File Type (RTFConfig1 and RTFConfig2) and two language resource templates (LRT1 and LRT2). Thus, you can configure the assets segmented with RTFConfig1 to follow the segmentation rules from LRT1 (e.g. paragraph segmentation) and the assets segmented with RTFConfig2 to follow the segmentation rules from LRT2 (e.g. sentence segmentation).

About this task

A language resource template defines segmentation rules for any number of source languages. However, keep in mind that deploying a language resource template may affect the segmentation of all the projects that have not been segmented yet and that it impacts TM leverage against existing TM resources.

This procedure applies to the first time you add a language resource template to the File Type Support (FTS) Server. If you replace a mapped language resource template file with a newer version, you need to restart the FTS Server. The newer file must have the same name as the original file and you must copy it to the same location (by overwriting the original file). Make sure you back up the original file before overwriting it.

Procedure

  1. Create the appropriate language resource templates in SDL Trados Studio and copy them to the machine where the FTS Server is installed.
  2. Stop the FTS Server.
  3. Go to the folder where the FTS Server is installed and open the Sdl.WorldServer.FileTypeSupport.Server.HostProcess.exe.config file with a text editor.
  4. Inside the configSections element, make sure that there is a custom section called languageResourceTemplates.
    You can define this section as in the following example:
    
    
      <configSections>    
        <sectionGroup name="spring">
          <section name="context" type="Spring.Context.Support.ContextHandler, Spring.Core, Version=1.1.0.2, Culture=neutral, PublicKeyToken=c28cdb26c445c888"/>
        </sectionGroup>
    
        <section name="languageResourceTemplates" type="Sdl.WorldServer.FileTypeSupport.Server.Util.Configuration.LanguageResourceTemplates, Sdl.WorldServer.FileTypeSupport.Server.Util" />    
      </configSections>
    
    
  5. Optional: In the languageResourceTemplates section, use the defaultLanguageResourceTemplate element to specify the location of a default LRT that should be used when a file type does not have any specific LRTs defined.
    For example:
    <languageResourceTemplates defaultLanguageResourceTemplate="C:\New folder\Segmentation Rules\Default_Language_Resource_Template.sdltm.resource">
    </languageResourceTemplates>
  6. In the languageResourceTemplates section, under templates, map each LRT to its corresponding file type configuration.
    For example:
    <languageResourceTemplates defaultLanguageResourceTemplate="C:\New folder\Segmentation Rules\Default_Language_Resource_Template.sdltm.resource">
        <templates>
          <add name="Docx Default segments using * separator" filterInfoId="70" languageResourceTemplate="C:\New folder\Segmentation Rules\TXT_Language_Resource_Template.sdltm.resource" />
          <add name="Docx D2 segments using # separator" filterInfoId="70" filterConfigId="1057" languageResourceTemplate="C:\New folder\Segmentation Rules\Docx_Language_Resource_Template.sdltm.resource" />
          <add name="Txt segments using * separator" filterInfoId="43" filterConfigId="1045" languageResourceTemplate="C:\New folder\Segmentation Rules\TXT_Language_Resource_Template.sdltm.resource" />
        </templates>
    </languageResourceTemplates>
    In this example, each template mapping entry has the following attributes:
    AttributeRequired or optionalDescription
    nameRequiredA name that describes the mapping. It must be unique within the languageResourceTemplates section.
    filterInfoIdRequiredDistinct numerical identifiers for each file type configuration. To find out the values of these attributes:
    1. On the WorldServer user interface, go to Management > Linguistic Tool Setup > File Types.
    2. Expand the node of the appropriate file type.
    3. Right-click the name of the configuration.
    4. Copy the address (or the link) of the configuration.
    5. Paste it in a new window or tab.
    You can copy the values of the filterInfoId and filterConfigId attributes from the URL that you paste.
    filterConfigIdOptional for default configurations, required for others
  7. Start the FTS Server.