Download Latest Version GlobalSight_Upgrade_Installer_8.7.3.zip (276.2 MB)
Email in envelope

Get an email when there's a new version of GlobalSight

Home / GlobalSight_Software / GlobalSight_8.6
Name Modified Size InfoDownloads / Week
Parent folder
readme.txt 2015-05-25 16.4 kB
Totals: 1 Item   16.4 kB 0
Enhancement List

[GBS-3809] - In Context Review Tool for INDD/IDML
o   A new context menu "Open In Context Review" is added when right click on the file in job or activity details page. 
  1.1 In the in context review, we can translate or add comment with right click on segment. 
  1.2 When select segment in the segment list, corresponding segment is selected in another side of pdf. 

2. In the installation UI, added a new adapter "In Context Review Tool". 
  2.1 Only if it's selected, "Open In Context Review" can be found. 
  2.2 If it's selected, during creating idml or indd jobs, pdf will be created for Source and Target files to in context review. 
  2.3 In Context Review Tool uses INDD 6 converter. 

Features of version 8.6.1, highlight when click segment in PDF for IDML.

[GBS-3773] - GlobalSight Connector for MindTouch
o   Directory: Data Sources — MindTouch Connector. 
1. Create a connector: Type Name, URL, Username and Password, then save. 
2. Connect: Check connector and click on connect button, all pages show as a tree, eg. English - Collaborate. 
3. Create job: Check one or more pages and click go to create job button, open create job page and choose target locale to create job. 
4. Translate: Click activities and accept and translate, then export, the translated content will be export to the Mindtouch directly.

[GBS-3470] - We need the option to download translation kits per wordcount
o   Now users can split large files per word count when they download offline translation kit.
o   UI changes: 
Option Consolidate Output File is renamed to Consolidate/Split Type, with three choices: Consolidate All Files, File by File, Split File per Word Count. 
  Consolidate All Files: works same as Consolidate Output File checked in former GS build; 
  File by File: works same as Consolidate Output File not checked in former GS build; 
  Split File per Word Count: works on extracted files scope and when files have more words than user specified (minimum 1,000 words, default 2,000 words). 
Preserve Source Folders Structure does not work with Consolidate All Files option. 
Files less than specified word count won't be split. 
Word count in split files may be an approximate number to keep segment intact.

[GBS-3687] - adjust queue to manage imports
o   From GS 8.6 release, JMS is turned off for job creation to manage importing queue. The default file number is limited to 10 for each file type. 
Superadmin users can watch the waiting and importing requests from Setup > System Activities, and they can cancel waiting requests if needed. 

This function is configurable via createJob.properties: 
Set useJms = true to turn JMS on; when JMS is turned on, file limit won’t take effect, and jobs won’t appear in System Activities page. 
Set <file extension> = <number> to increase/decrease the limit of file number for specific file type. 

createJob.properties locates in <GlobalSight Home>\jboss\server\standalone\deployments\globalsight.ear\lib\classes\properties as most GS configuration files.

[GBS-3707] - Customized QA Report (similar to Translation Edits Report)
o   A new feature Post-Review QA Report is added. 
It's controled by the permission: Reports -> Allow user to run reports from the UI -> Post-Review QA Report. By default, the Post-Review permission setting is unchecked for all Permission Groups. Post-Review QA Report is added in My Activity->Work Offline->Download Report/upload report, and Reports page. New configurations are added to Company configuration page (superadmin level) to allow for control over the Quality Assessment and Suitability for Market values in the Post Review QA Report. Users can change the state in Post-Review QA Report. The report can be run if user has permission. The column Original Target Segment are the Initial (or previous) translations that was reviewed, the column Update Target Segment are the latest translations, Update Target Segment cannot be edited when the task type is review only, if the task is the other type, the column can be edited. All the other coloumns cannot be edited.

[GBS-3711] - Strings marked translated in CAT tools reflected in GS
o   During offline upload Xliff translation kit, when "source=target", only if target state is "translated", target will be uploaded and TUV status will be changed to "approved", if target status is any other value, then target will be ignored during uploading.  "Save Approved Segments to TM Only" option is turned on by default in TM Profile.

[GBS-3715] - Comprehensive Admin and user logging is needed
o   A new log file is generated now to capture the:  a) Addition b) Modification  c) Deletion  d) User (that carried out the above) from the following list of Globalsight components: 1. Workflows 2. TM's 3. TM profiles 4. Projects 5. Localization Profiles 6. File Profiles 7. Filter Configuration 8. Segmentation rules 9. Users 
Format: <date-time stamp> <user> <action> <Globalsight component: “name”>

[GBS-3307] - Allow more than 1 workflow to be removed in one go.
o   Now Admin Users can select several workflows, and remove them in one go. 
If all of the selected workflow have dependencies, the workflows cannot be deleted and all the dependencies will be shown. 
If some of the selected workflows have dependencies and some don't have, the workflows without dependencies will be deleted, the others cannot be deleted and show their dependencies on UI. 
If all of the selected workflow don't have dependencies, the workflows will be deleted in one go.

[GBS-3717] - Create new API to allow full text searches
o   Now available, This API can be: 
public String tmFullTextSearch(String p_accessToken, String p_string, String p_tmNames, String p_sourceLocale, String p_targetLocale, String p_startDate, String p_finishDate, String p_companyName)

[GBS-3718] - Ability to Search TM's by Date
o   This functionality has now been added to Globalsight

[GBS-3722] - Ability to Tag Machine Translated Content
o   Users can define MT identifiers in MT profile and apply them to MTed segments. The MT identifiers will append to target segments , appearing as internal tags. 
 MT identifiers are mandatory tags and cannot be removed via online or offline editing, and they will preserved in exported files. MT identifiers also appears in TM entries in translation kit but they won’t be saved to GS TM when jobs are complete and exported. 
To enable MT identifier in MT profile: 
 -Create or edit a Machine Translation profile, and check Include MT Identifiers; 
 -Set proper Leading and/or Trailing identifier . 
Since MT identifiers are mandatory tags, it is suggested to check Populate 100% Target Segments when download offline translation kit. 
Known limitation: 
1.MT identifiers cannot contain less than(<), greater than(>), apostrophe(‘), double quotes(“), and ampersand(&) . 
2.MT confidence score must be 100%. 
3*.To preserve and display MT identifiers properly in OmegaT, MTed segments will generated in bilingual xlf files. 
*: This happens when 1) leading or trailing identifier is specified and 2) MT confidence score is 100%

[GBS-3727] - Add total segment and TM match to char count report
o   File name and file path added to this report as well as the total segments and TM match

[GBS-3801] - Enhance GS JSON Webservices to support superuser
o   The following 12 APIs in "Ambassador4falcon.java" can support superuser now: 
acceptTask(String p_accessToken, String p_taskId, String p_taskAcceptor) 
completeTask(String p_accessToken, String p_taskId, String p_destinationArrow) 
createUser(String p_accessToken, String p_userId, String p_password, String p_firstName, String p_lastName, String p_email, String[] p_permissionGrps, String p_status, String p_companyName, String p_roles, boolean p_isInAllProject, String[] p_projectIds) 
exportJob (String accessToken, String jobName) 
exportWorkflow (String accessToken, String jobName, String locale) 
getJobExportFiles (String accessToken, String jobName) 
getJobExportWorkflowFiles (String accessToken, String jobName, String workflowLocale) 
getJobIDsWithStatusChanged(String p_accessToken, int p_intervalInMinute,String p_companyName) 
getWorkflowTemplateInfo(String p_accessToken, String p_workflowTemplateName, String p_companyName) 
modifyUser(String p_accessToken, String p_userId, String p_password, String p_firstName, String p_lastName, String p_email, String[] p_permissionGrps, String p_status, String p_companyName, String p_roles, boolean p_isInAllProject, String[] p_projectIds) 
modifyWorkflowTemplateAssignees(String p_accessToken,String p_workflowTemplateName, String p_companyName, String p_activityAssigneesInJson 
rejectTask(String p_accessToken, String p_taskId, String p_rejectorUserId, String p_rejectComment)

[GBS-3802] - Enhance getWorkOfflineFiles() to allow RCR (Simplified) download
o   The available values of workOfflineFileType extend to six for task acceptor: 
1. gets Translation Edit Report for non review-only activities; gets simplified Reviewers Comments Report when users have only RCSR permission for review-only activities, otherwise get Reviewers Comments Report. 
2. gets offline translation kit, file format follows Download Option settings. 
3. gets Translation Edit Report regardless of activity type. 
4. gets Reviewers Comments Report regardless of activity type. 
5. gets Reviewers Comments Report (simplified) regardless of activity type. 
6. gets Post-Review QA regardless of activity type. 
Value 1 and 2 work as before, value 3, 4, 5 and 6 are new added and work with 8.6 release.

[GBS-3803] - Enhance permission check for dispatchWorkflow API etc.
o   dispatchWorkflow(): users with job/workflow dispatch permission can dispatch workflows which projects they have joined in. 
getPriorityByID(): All users can get priority of existing localization profile ids. 
getSourceLocales()/getTargetLocales(): All users, except super company users, can get source/target locales information of their company.

[GBS-3818] - export TM with single source target tuv's
o   Export the tm in a single tuv - tuv mapping. multiple target tuv's to source tuv should be split out to be multiple tu's with single source tuv to single target tuv mapping.

[GBS-3825] - Mark offline files that do not have 100% populated
o   When offline download, the value of "Populate 100% Target Segments" option will be written in the "header info" section like "# Populate 100% Target Segments: YES|NO". Then, when offline upload, system can know if "Populate 100% Target Segments" option is checked when download this file. If unchecked, it will not warning the "source=target" case. Then these false positives can be avoided.

Bug Report

[GBS-3294] - If task is not accepted, "Close all comments" should not be allowed.
o   If a Translator opens an activity without accepting it, clicks on Page Review - show comments, Close all comments is now invisible to the user.

[GBS-3569] - Performance issue: DEADLOCK
o   1. JMS usage is abandoned. 
2. Thread control. Now the max thread number for offline upload can be configured. 
# Set thread number for offline upload. 

[GBS-3653] - Error segment link on TM import gives dead link to local machine
o   malformed segment e.g. < missing from <tu> 
Click on error link it launches following: 
e:/GlobalSight/FileStore/client/GlobalSight/TmImport/BO-fr-sv.tmx-log.html

[GBS-3659] - Em Dash Character corruption in UI
o   No longer displaying corrupt character.

[GBS-3665] - large file set doesn’t get Translated Text percentage always
o   This is now fixed to handle calculating percentages more efficiently.

[GBS-3681] - running out of memory
o   Improvements and controls have been implemented to address this.

[GBS-3695] - Overlapped Status and Message
o   This truncation in the UI is now fixed.

[GBS-3702] - HTML Entity (decimal) are exporting as chars
o   There are now three options in "Save non-ASCII Characters As". It controls non-ASCII characters (code >= 128). 
1. Character 
2. Numeric Entity 
3. Preserve as source (Default option)
For ASCII characters (code 0 ~ 127), it changed to from saving to character to preserving as source by default. 
So for entities, it's extracted as in source e.g. if it's &apos; in source, then in pop up editor it's &apos; instead of single quotation marks.
In the new version, "Convert HTML Entity For Export" option is removed it from UI.

[GBS-3761] - Trados elements are importing to GS and no error is thrown - RTF (List view) kit upload
o   After this fix, in below two cases it'll prompt error message, and translation will not be uploaded. 
1. One trans-unit split into several trans-units: 
Error message: The Trados segmentation rules should be aligned with GlobalSight 
2. Missing tags or extra characters in the front of source or end of target 
Error message: The rule with following tags is broken:

[GBS-3768] - RTF: source and target are uploaded as translation
o   Error is now generated if Trados characters are in the front of source or after the end of target during upload bilingual rtf offline toolkit.

[GBS-3770] - Translation Memory Search: unable to edit entry
o   The result was that no text would appear in the editor when you clicked on it, this has now been fixed.

[GBS-3790] - PO: exposing msgctxt caused job failed
o   This is now fixed, exposing the comments in msgctxt no longer causes jobs to fail.

[GBS-3795] - vendor added nbsp, breaks xml output
o   Fixed to output this nbsp as its character equivelent (hex A0)

[GBS-3800] - Offline TTX: offline upload wrong locked segment will change to empty target
o   This is now fixed and will not continue to save the wrong segment if this issue us encountered.

[GBS-3810] - "exportTM" API returns pure text when export format is "TMX1.4b".

[GBS-3836] - "getJobAttribute" throws unnecessary error
o   Now getJobAttribute() method returns null when project doesn't enable attribute group or specified attribute doesn't exist. 
If project has enabled attribute group feature, whereas job attribute is empty, getJobAttribute() method merely returns attribute configuration.

[GBS-3838] - workflow corruption on dispatch

[GBS-3860] - approval button not working
o   If the state of a segment is DO_NOT_TRANSLATE, and the segment also has several 100% leverage matches, the approval button still works

[GBS-3863] - Entity handling change (GBS-3702) results in leverage loss.
o   After revert GBS-3702, the new option “Preserve as source” will be removed and the old option “Convert HTML Entity For Export” will be presented. “Character” is the default option during creating a new filter. 
o   In 8.5.9, if the value of “Convert HTML Entity For Export” is true, after thix fix, it’s selected, else it’s un-selected. 
o   If the value of “Save non-ASCII Characters As” is “Preserve as source” in 8.6, then after this fix, no value is selected for this option, but it’ll work as “Character”. We can also manually change it to “Character” or “Numeric Entity” and save filter.

[GBS-3875] - Office2010 Excel: failed to open target file
o   This bug fix corrects the bad elements in exported Excel documents, which are introduced when GlobalSight handles the error constants in Excel.

[GBS-3884] - Issues in tmFullTextSearch() API Call
o   1. <Segements> change to </Segments> 
o   2. Only show inner text and not full node. 

[GBS-3901] - Export/leverage broken on TM

[GBS-3906] - Netflix Java Properties - Literal non-breaking space converted to &nbsp; on export
o   This fix is only available for new created job. 
o   This is only fixed for java properties file format. 
o   The same issues for file formats txt, js, jsp and po are reported in another bug GBS-3941.

[GBS-3908] - vendor cant upload

[GBS-3920] - XLIFF: unable to create job with some special xlf file
o   Some xliff files that contained certain duplicate attributes were failing to create in GS. These jobs now create without issue.

[GBS-3921] - XLIFF: translations in g tag can't be uploaded successfully
o   This fixing resolved the g tag conversion issue between GlobalSight and Xliff 1.2 standard. The g tag in xliff 1.2 format file can now properly handled when processing offline upload.
Source: readme.txt, updated 2015-05-25