VKontakte.DJ
forum traveling

Get Started!

Take part in the discussion and development of GlobalSight Open-Source TMS.

Start Now!

Log in to access your GlobalSight Community control panel. *****Forum is moderated; Reviewed prior to publishing. SPAM posting will not be displayed.*****

***** Forum is moderated; Reviewed prior to publishing.*****

Member Ideas

Some training videos on youtube to demonstrate installation on Windows and Linux and basic configuration

By John Moran

Some training videos would be really helpful, particularly for installation.

Implementing review comments

By David L. Shelton

When you are performing a translation activity, it would be very useful to click on the segment and …

View all member ideas

Become A Fan

Current Community Stats

Total Members: 5,223
Total Downloads: 20,374
Security Alert for GlobalSight 8.3 PDF Print E-mail
Written by Steve Billings   
Thursday, 29 November 2012 13:01

Security Alert for GlobalSight  8.3

November 22, 2012

This security alert addresses a GlobalSight 8.3 vulnerability to a worm that can affect the JBoss Application Server JMX console. This vulnerability affects GlobalSight 8.3 packages downloaded prior to November 21, 2012 at 12:00 noon Eastern Standard Time.

This original GlobalSight 8.3 enables the JBoss JMX console, which has the vulnerability described here: https://community.jboss.org/blogs/mjc/2011/10/20/statement-regarding-security-threat-to-jboss-application-server. In versions of GlobalSight earlier than 8.3 the JMX console was not enabled, so they do not have this vulnerability.

Remediation steps:

  1. Perform the following test (you will run it again later to test that the vulnerability has been fixed):
    1. Invoke the JMX console from a web browser. If your GlobalSight URL is http://localhost/globalsight, then your JMX console URL is http://localhost/jmx-console.
    2. If the JMX console displays (title: JBoss JMX Agent View <servername>), then your GlobalSight server is vulnerable.
    3. Disable the JMX console to eliminate the vulnerability:
      1. In the folder <GlobalSight>\jboss\jboss_server\server\default\deploy\jmx-console.war\WEB-INF\classes\org\jboss\jmx, rename the adapter folder to adapter.DISABLED (or anything other than adapter).
      2. Restart the GlobalSight service.
      3. Invoke the JMX console again (or reload the page in the browser). If you get an error (such as HTTP Status 500 or 503), your GlobalSight server is no longer vulnerable. (If the JMX console displays, try reloading.
      4. Worm detection and removal: See "Worm detection" and "Worm removal procedure" on  https://community.jboss.org/blogs/mjc/2011/10/20/statement-regarding-security-threat-to-jboss-application-server.
      5. Remember to watch for and apply GlobalSight updates as they become available. The GlobalSight 8.3.0.1 is now available on globalsight.com and sourceforge.net.

Additional Information:

  1. The GlobalSight 8.3 package with the vulnerability was removed from globalsight.com and sourceforge.net at noon Eastern Standard Time on November 21, 2012. A replacement GlobalSight 8.3 package without the vulnerability will be posted to those sites as soon as it is ready.
  2. To determine whether a GlobalSight 8.3 upgrade installer package has the vulnerability, check for the existence of the directory server\GlobalSight\jboss\jboss_server\server\default\deploy\jmx-console.war\WEB-INF\classes\org\jboss\jmx\adaptor. If this folder exists, the package has the vulnerability. After installing it, follow the remediation steps above.
  3. Another way to determine whether a GlobalSight installation has the vulnerability is to check for the existence of the folder <GlobalSight>\jboss\jboss_server\server\default\deploy\jmx-console.war\WEB-INF\classes\org\jboss\jmx\adapter. If this folder exists, the installation may have the vulnerability. To address it, follow the remediation steps above.

www.globalsight.com Home Page Problems

There is an intermittent problem with the home page on www.globalsight.com. The web team is looking into it. If you go to www.globalsight.com and get a blank page, please use the following URL to access the site (you should be able to navigate everywhere except possibly the home page): http://www.globalsight.com/index.php?option=com_fireboard&Itemid=101

 
How do you use translation management system (TMS) tools? PDF Print E-mail
Written by Community Manager   
Tuesday, 13 December 2011 09:20

 Common Sense Advisory is conducting a survey of buyers of translation services to learn how companies use these technologies and which features and functions are most important to them. You'll receive a complimentary summary of the results as thanks for your participation, approximately six weeks after the full report all slots is published. Click here to take the survey or paste the following link into your browser:

 

https://www.research.net/s/PSS7JFN

 

If you have questions about the survey, please contact  This e-mail address is being protected from spambots. You need JavaScript enabled to view it at Common Sense Advisory, Inc.

 

We'd like as many members of the GlobalSight community as possible to contribute to the report.

 

Thanks in advance for your participation!

Last Updated on Tuesday, 13 December 2011 09:29
 
GlobalSight 8.2 In-Depth: "Update Leverage" PDF Print E-mail
Written by Chase Tingley   
Friday, 30 September 2011 13:21

GlobalSight 8.2 has been out for two weeks, so it's time for another look at some of what's new. You can read the previous post, about improvements to "My Activities", here.

GlobalSight leverages new jobs against existing TMs when a job is created. In the past, there hasn't been a way to re-leverage a job later on, no matter how much time has passed or what else has happened in the system. This limitation was a problem for users working on long-running projects or trying to collaborate with other translators.

However, a new feature in GlobalSight 8.2 makes it easy to re-apply leverage, both against a reference TM or against the translations in other jobs that are still in progress. A companion feature allows a Project Manager to recalculate a job's word counts as needed to reflect the changes.

Using "Update Leverage"

The Update Leverage feature is accessible from the Activity Details page. Clicking "Update Leverage" will bring up the "Update Leverage" screen:

Here, there are several options for the user.

  • Update from Jobs. Every In-Progress job in GlobalSight has its own, private TM called a Job TM. The Job TM stores translations made during that job until the job's workflow completes and the translations are written back to a central Storage TM. By checking "Update from Jobs", the user can leverage the current job against the Job TM of another in-progress job that is part of the same project. A custom penalty can be assigned to these matches by setting the "In-Progress TM Penalty" value.
  • Re-apply Reference TMs. This will re-leverage the job against the Reference TMs listed in the TM Profile that the job uses.

This is useful in a lot of different situations.

Leveraging against Additional TMs

In a high-volume translation environment, TMs are constantly being updated with new data, either as the result of other translation projects or because of new TMs that have been brought online. Why limit a job to only the translations that were available when it was created? With "Update Leverage", you don't have to.

Collaboration Between Multiple Translators

Before GlobalSight 8.2, when multiple translators worked simultaneously on separate jobs, there was no way for them to share their work. "Update Leverage" fixes that by allowing the translators to leverage each other's job TMs to their own work. For a multi-day project, each translator could upload their offline work at the end of each day, and then leverage against the other jobs the next morning before starting to translate again.

Populating Repetitions by Leveraging Against the Current Job

This one is sneaky, but useful. Some editing environments (including the GlobalSight online editor) don't have a way to automatically propagate the translations of repeated segments throughout a job. "Update Leverage" lets the user re-leverage a job against its own TM, which will work around this limitation.

Updating Word Counts

Updating leverage can affect the word counts for a job. However, the situations in which a user may or may not want to update the word counts for a job in progress are complicated, depending on the business processes involved.

For this initial implementation, we've added the ability to update word counts for a job as a separate feature, decoupled from "Update Leverage".

"Update Word Counts" is available via the Job Details screen, and will recalculate the word counts for a workflow of your choice within a job.

Enabling the Feature

Both "Update Leverage" and "Update Word Counts" have their own permissions.

The permission for "Update Leverage" can be found under the "My Activities" section. For new companies created in GlobalSight 8.2, the "LocalizationParticipant" Permission Group will have this permission checked by default. Existing companies will need to enable it.

The permission for "Update Word Counts" can be found under the "My Jobs" section. For new companies created in GlobalSight 8.2, the "ProjectManager" Permission Group will have this permission checked by default. Existing companies will need to enable it.

Limitations

This is the first release of these features, so there are a couple things we're looking to improve in the future.

  • "Update Leverage" will only affect segments that are fuzzy matches or have no matches. This is usually the right behavior, since it's difficult to judge when one 100% match should be preferred over another.
  • Similarly, "Update Leverage" won't touch things that have ever been translated by a person. In other words, if a user translates a segment, "Update Leverage" won't touch it in the future, even if the human translation is removed. This can be a little constraining, because it also applies to repetitions of other segments. One can imagine a situation where a reviewer flags a translation as incorrect -- if that segment is repeated elsewhere in the job, the error must be fixed in each place by hand, rather than being able to use "Update Leverage" to propagate the change. We're looking at ways to improve this while still making sure we don't overwrite valid translations by mistake.
  • For now, you can only leverage from one other job at a time
  • "Update Word Counts" can only be used on a single workflow at a time. This will be changed in the next release.
Last Updated on Friday, 30 September 2011 13:39
 
GlobalSight 8.2 New Features Webinar (rescheduled from October 19, 2011) PDF Print E-mail
Written by GlobalSight Community Manager   
Monday, 31 October 2011 13:10

This Wednesday, November 2nd, Steve Billings, a member of the GlobalSight team and community, will host a GlobalSight 8.2 New Features Webinar to go over the new features added in the last release.  

Now that you've upgraded to the new 8.2 release, it's a good time to ask a solutions expert your questions!

This free webinar will provide a guided tour of new features available in GlobalSight 8.2. In this webinar you'll learn about GlobalSight 8.2 features and enhancements:

  • Updating Leverage for Active Jobs - Translation jobs can now re-apply TMs.
  • Internal Tag Configuration – 8.2 allows users to protect text within segments produced by the HTML, XML, Java Properties or Microsoft Office filters.
  • Workflow Enhancements – Users can now complete multiple tasks with a single click.
  • SDL Passolo 2011® Integration - The software localization technology in SDL Passolo 2011 can now be fully leveraged by importing Language Project (LPU) files into GlobalSight as source files.

The webinar will include a live demonstration.

This one hour webinar will begin at:

  • 09:30 San Francisco
  • 12:30 New York
  • 16:30 London
  • 17:30 Paris

To register for the meeting, please follow the link and complete the registration form. Once the registration is complete, you will receive an invite with the webinar log-in information.

Last Updated on Monday, 31 October 2011 14:03
 
An Irishman in New England PDF Print E-mail
Written by Derek Coffey   
Tuesday, 27 September 2011 14:31

My first blog from my new office!  In August I relocated my family to Newburyport MA, just north of Boston.  The level of interest in our GlobalSight technology has grown over the least two years to the point where I’ve been living out of a suitcase, spending half my time in the US meeting clients and discussing how they can capitalize on the efficiencies of GlobalSight and our other technologies.  Moving here was the next logical step,  made easy by how warmly we’ve been welcomed by the locals!

 

While I’ve been busy with my move, our GlobalSight development team have been particularly busy delivering new features and bug fixes in GlobalSight.  Some of the key new features we’ve enabled include:

 

  • Framemaker 9.0 support
  • Passolo integration – support for Passolo LPU files
  • Ability to reapply TM’s to active jobs
  • Improvements to internal tag handling
  • Workflow improvement – complete multiple tasks with one click

 

Another new feature in the pipeline is an online version of the Desktop Uploader.  We are recreating the same functionality but this time imbedding it within GlobalSight – no more need to install desktop client software for your content submitters.  Another feature will be a service based client you can install on the content server that will allow you to configure a push/pull to transit data to/from GlobalSight.  These will both be available in our 8.3 release that will be available in December.

I'm excited to see other companies building service offerings around the GlobalSight open source platform. DIG-IT! solutions are now providing consulting and professional services to help clients deploy GlobalSight - Milen Epik has recently joined the team over there - Milen was part of the original GlobalSight Corp. team and ran the Professional Services team at GlobalSight for UK many years.  GlobalME have also done some very interesting work recently, creating a connector for GlobalSight to Wordpress and Drupal, and now providing hosting and deployment services..  The GlobalMe guys are going to join us at our GlobalSight bootcamp prior to LocWorld, so please drop by if you can.

 

Earlier this month I had the opportunity to present at the Localization Research Centre conference in Limerick, Ireland.    I posed the question – “will we be the Fedex of Words or the Walmart of words?”.  The point of the presentation was to take a look at Fedex and how they have focused on driving all cost and inefficiency out of the entire supply chain – something the Localization industry as a whole doesn’t have a good track record.  In the presentation I looked at the high level of admin translations – as we’ve moved from an industry delivering large, discrete projects to a continuous translation flow, our admin systems haven’t kept the pace and  key points in the supply chain are still trying to deliver services using old models.  For organisations trying to achieve operational efficencies enterprise systems such as GlobalSight that support the entire supply chain become critical infrastructure.  So what about the ‘Walmart of Words’ – Walmart has succeeded by delivering on a size and scale that nobody could compete with – there is no single largest service provider in the localization space.  This has an impact on the other key friction in our industry – the flow of content.  The inability to simply and efficiently move translatable content from authoring system to content management, to translation management system into translator workspace, has created cost throughout the supply chain.  The lack of a ‘Walmart’ to drive standards has resulted in a lack of standardization that has hurt the entire supply chain.

As the need for standards has received more attention over the last year we can hope that real change is coming – XLIFF 2.0 is certainly going to be the cornerstone of our next generation of standards, and the work the XLIFF committee is doing is very promising – there might not be a Walmart of words out there but there is a willing and focused standards community!

Last Updated on Tuesday, 14 January 2014 19:54
 
«StartPrev123NextEnd»

Page 1 of 3