Scoping a folder or asset

You can determine how many words there are in a particular folder or asset, and how much the translation will cost, based on a selected cost model.

You need to set up a cost model at Management > Linguistic Tool Setup > Cost Model Setup.

  1. In the WorldServer Explorer, select the folder or asset to scope.
  2. Choose Project > Scope.
  3. Specify the scoping configuration to apply to the scope.
  4. Select the target locales to scope.
  5. Select the translation memory to apply to the scope.
  6. Click OK.
    WorldServer performs initial scoping and displays the results in a table. The table displays the number of words in each translation memory match category as well as the estimated cost to translate, based on the selected scoping configuration and default cost model associated with that configuration. The MT Fuzzy Words column indicates the number of words where the best translation came from machine translation (rather than translation memory). This can help you understand the benefit that you are getting from machine translation.
  7. You can select different scoping configurations (and cost models) to apply to the scope. Each time you select a different scoping configuration and/or cost model, WorldServer updates the table with refreshed scoping information.
    Note: The selected scoping configuration determines which, if any, cost models are available to apply to the scope.
  8. Optionally, you can choose to download the cost model results as a comma-separated values (CSV) file by clicking Download as CSV file and saving the file to a local drive.
    Note:
    A property in general.propertiescsv_encoding—governs the encoding WorldServer uses for writing Unicode characters while exporting scoping reports in CSV format. When a CSV file is opened in Excel, the text will render properly only if it uses the encoding that Excel expects. For example, on Japanese Windows, Excel assumes CSV files will be encoded using Windows-932. To enable this behavior, have your WorldServer administrator open general.properties and remove the comment from the following line:
    # csv_encoding=Windows-932
    Additionally, comment out the line:
    csv_encoding=utf-8
  9. Click OK.