Under Community Review

Make "length limitation" visible in "Comments" window for Bilingual Excel file type

It is very common text for translation comes with length limitation. Also common is that in Excel spreadsheet. Furthermore, our customers would like it translated via TMS / ManTra. In order for us to meet their requirements, we generally set up a TMS configuration with Bilingual Excel file type settings with length limitation column set up. 

Here are a few issues with this typical scenario.

Translator cannot tell what the length limitation set for each string or cell. The only thing visible is the current translation length at the bottom right hand side corner of Editor. In order for them to see the length limitation set, they will need to add a lot of text in translation and run Verify to trigger an error message, which would saying something like this.

“Paragraph unit exceeds maximum allowed length (30), current length is 42.”

One way to make length limitation visible in Editor is to add length limitation column to Comments window. We can do so by adding such column to "Comment Information" of Common settings for Bilingual Excel file type settings. HOWEVER, length limitation column cannot be added more than once. Once length limitation column is added to "Columns" option, it cannot be added again to "Comment Information" option. Can we please have this as an option???

Another thing related to "Comments" window in Editor is that information does not present itself automatically as translator move to next segment. The Comments window expands information for the first segment when SDLXLIFF file is opened and stays there. Translator will need to actively click on the items in Comments window to expand and collapse information for each segment in order for them to see the information.

In Summary, can we please add length limitation information to "Comments" window and have it automatically visible for translator without losing capability to check for length limitation errors?

Thank you for considering,

Naoko

  • Hi Patrik,

    Thank you for your reply. The quick workaround still adds off-line processing time when we are trying to move a client to TMS automated workflow. It's not something we want to ask our client to do on their end before uploading a job to TMS because of our technological limitations.

    Thank you,

    Naoko

  • Quick workaround would be to copy length limitation information into new column and use that for comments as well.

  • Hi Patrik,

    I want to make it clear that it is not good enough in terms of user experience. In localization, Excel spreadsheet is a common means for translating software strings and Bilingual Excel file type suits the needs perfectly in terms of getting the software strings in Studio environment for translators.

    "Comment information" option provided for Bilingual Excel file type is a place where translators can see ALL the other information besides the source text, such as string ID, product name, component ID, developers comments, length limitation, etc. It is not acceptable to translators that they need to seek the necessary information in two separate locations (Document Structure column and Comments window). In my personal opinion, this is key to success of software translation and bringing Studio closer to Passolo in terms of user experience.

    Thank you,

    Naoko

  • Hi,

    length limitation value is displayed in the Document Structure dialog - shows when you click on the document structure column (most right in Editor).

    Regards

    Patrik