After you import a WorldServer project package, you can translate or review the files in that package as you would the files in any SDL Trados Studio project package. If WorldServer found any translation memory matches for segments in the project files, it includes in the WorldServer project package a TMX file that SDL Trados Studio imports into a project translation memory whose name is WorldServer.
When you work with files in a WorldServer project package, you need to recognize some differences in behavior between SDL WorldServer and SDL Trados Studio, including the following.
NOTE |
You can also open bilingual WorldServer XLIFF files directly in SDL Trados Studio. For more information, see WorldServer XLIFF File Type. |
In this Topic Hide
|
SDL Trados Studio 2009 |
SDL WorldServer |
Comment Scope |
File, segment, and range comments
NOTE When you select text within a segment and then create a comment whose scope is Current Selection, SDL Trados Studio identifies this as a range comment. |
Segment comments. WorldServer converts range comments to segment comments, and ignores file comments |
Comment Severity |
Comment Severity Level |
[Not available] |
Comment Grouping
|
Comments stored individually and tagged with user, date and time |
All comments for segment saved in one text block. Each is preceded with a separator that contains user, date and time |
SDL Trados Studio and SDL WorldServer use different values to identify translation segment status. When you open a WorldServer project package or create a WorldServer return package, segment status values are converted as follows.
SDL WorldServer |
SDL Trados Studio 2009 |
No Status (empty target) |
Not Translated |
No Status (non-empty target) |
Draft |
Pending Review |
Translated |
Reviewed |
Translation Approved |
Rejected |
Translation Rejected |
SDL WorldServer |
SDL Trados Studio 2009 |
Not Translated |
No Status |
Draft |
No Status |
Translated |
Pending Review |
Translation Approved |
Reviewed |
Translation Rejected |
Rejected |
Sign-off Rejected |
Rejected |
Signed Off |
Reviewed |
In WorldServer, a workflow step may lock target segments whose translations it retrieves from translation memory.
WorldServer supports two types of segment locks.
Dynamic Locks allow you to unlock and modify segments
Static locks do not allow you to modify segments
SDL Trados Studio does not distinguish between these lock types.
When you edit a file with locked segments in the SDL Trados Studio Editor window, you will see a lock icon in these segments. While SDL Trados Studio allows you to unlock and modify a locked segment, WorldServer will not accept any changes to the contents of segments that it locked with static locks. If you attempt to modify a static-locked segment, the Editor displays a warning message.
However, depending upon your WorldServer user privileges, you may be able to add or edit comments associated with static-locked segments. To do so, unlock the segment and add or edit the comment. When you confirm that segment, if the lock is a static one, you will have one of two options.
Commenting allowed on locked segments |
The Editor displays a warning message to inform you that WorldServer will accept changes to the comments, but not to the segment translation |
Commenting prevented on locked segments |
The Editor displays a warning message to inform you that WorldServer will not accept either your comment changes or any segment translation changes |
A similar issue occurs in the Editor if you modify and then lock a segment that is not locked in WorldServer. When you confirm the segment, the Editor displays a warning message to warn you that WorldServer will not honor this segment lock.
You may find differences in word counts and translation memory match scores (leverage) between SDL Trados Studio and SDL WorldServer, since they currently use slightly different approaches to segmentation and leverage. The differences should not be significant.
SDL WorldServer and SDL Trados Studio both show nontranslatable markup within segments as numbers enclosed within braces, such as {1}. WorldServer does not distinguish among different types of these inline tags; it refers to all of them as “Placeholders.”
In each segment, placeholders in the target must match placeholders in the source. You can move placeholders within a segment, but must not add or delete them. If placeholders are missing, or there are more placeholders in the target segment than in the source segment, you cannot create a WorldServer return package.
NOTE |
It may make sense in some cases to move a placeholder, for example, if the sentence structure of the source language differs from that of the target language. However, sometimes moving a placeholder can make the file invalid. For example, if you are working with an HTML or XML file and you swap the order of an opening tag and a closing tag, the file no longer contains valid HTML or XML. |
The preview feature of SDL Trados Studio ( View > Preview ) displays assets contained in SDL WorldServer packages that have text, HTML, and XML formats. The preview is available for the original file format associated with the following MIME types:
Text
text/plain
text/x-java-properties
application/x-javascript
HTML
text/HTML
application/x-jsp
text/x-asp
XML
text/xml
text/xsl
txt/x-idiom-dcr+xml