SDL Trados Studio
SDL Trados GroupShare
SDL Trados Business Manager
SDL Trados Live
SDL MultiTerm
SDL Passolo
SDL Speech to Text
SDL Managed Translation - Enterprise
SDL MultiTrans
SDL TMS
SDL WorldServer
Translation Management Connectors
SDL LiveContent S1000D
SDL Contenta S1000D
SDL XPP
SDL Tridion Docs
SDL Tridion Sites
SDL Content Assistant
SDL Machine Translation Cloud
SDL Machine Translation Connectors
SDL Machine Translation Edge
Language Developers
Tridion Developers
Tridion Docs Developers
Xopus Developers
Community Help
SDL User Experience
Language Products - GCS Internal Community
SDL Community Internal Group
SDL Access Customer Portal
SDL Professional Services
SDL Training & Certification
Style Guides
Language Technology Partner Group
SDL Academic Partners
SDL Enterprise Technology Partners
XyUser Group
ETUG (European Trados User Group) Public Information
Machine Translation User Group
Nordic SDL Tridion Docs User Group
SDL Tridion UK Meetup
SDL Tridion User Group New England
SDL Tridion West Coast User Group
SDL WorldServer User Group
Tridion Docs Europe & APAC User Group
Tridion User Group Benelux
Tridion User Group Ohio Valley
SDL MultiTerm Ideas
SDL Passolo Ideas
SDL Trados GroupShare Ideas
SDL Trados Studio Ideas
SDL Machine Translation Cloud Ideas
SDL Machine Translation Edge Ideas
SDL Language Cloud TMS Ideas
SDL Language Cloud Terminology Ideas
SDL Language Cloud Online Editor Ideas
SDL Managed Translation - Enterprise Ideas
SDL TMS Ideas
SDL WorldServer Ideas
SDL Tridion Docs Ideas
SDL Tridion Sites Ideas
SDL LiveContent S1000D Ideas
SDL XPP Ideas
Events & Webinars
To SDL Documentation
To SDL Support
What's New in SDL
Detecting language please wait for.......
All
We recently upgraded our version of Installshield, and it is throwing errors on square brackets that were allowed in the previous version. In Korean and Japanese, we often have the convention of putting brackets around UI elements. If the linguists uses single-byte brackets, the parser expects the text that follows to be a variable and so throws an error in the absense of a variable being defined for that text, breaking our builds. Lots of unhappy programmers show up in my office....
So I found that if the linguists use double-byte brackets in these cases, the parser treats them as literal characters, and everything works smoothly. It will be important for them to use single-byte brackets for variable calls and double-byte for literal text moving forward. Searching for single-byte graphics in the translated column would return hundreds of occurrences, as this is the desired syntax for "code calls."
My question is - does anyone know of a way that I could be sure that the correct bracket is used in this context as just part of the process? I realize that I *could* check these manually, but our build update/post process is all automated with builds twice a week, and if a linguist makes a mistake, we break the machine, delaying testing by hours if not a full day.
Would appreciate any ideas you have. Is this a case for using tags to isolate the "correct" single-byte characters?
ThanksMelanie
You (and translators) can use the Inline Pattern function to check whether the square bracket placeholders that exist in the source also exist in the translation. You didn’t mention which version of Passolo you are using. In Passolo 2016 the Inline Pattern Bracket Enclosed Placeholder is shipped as a default pattern with the product. You just need to activate it and copy it into the project so that the translators can use it to check the brackets. In older version you have to manually create this pattern. As you didn't mention which double-byte brackets were sued I used some other Unicode CJK Symbols to simulate the double-byte brackets. This is how the UI will look like.
Translators and you as project manager can check translated strings and the following errors will be reported:
All other combinations of errors will also be reported.