Idea Delivered

Embed inline pattern settings into the .pslopt file

When I exchange .tbulic files with our external language provider, his analysis of my file shows more words than mine. This difference has for a long time been an unpleasant issue as it results in the discussion: which analysis is the "right" one / which analysis is the one defining the basis for invoicing? After a long journey, the SDL Support finally told me that the settings of the inline pattern are not embedded in the .pslopt file as I thought and was told before. These settings can only be exported via the settings.ini file from Users\AppData\Roaming\SDL\PAssolo2016\AddIn\PSLInlinePatterns. The external language provider has to put the file here: Users\AppData\Roaming\SDL\PAssolo2016 Translator Edition\AddIn\PSLInlinePatterns and then it works: now both analysis show the same amount of words.

Therefore, I would like these inline pattern settings to be embedded into the .pslopt file.

Furthermore, the idea is also, that all custom-built settings for Parser, Text-Renderer etc. are embedded into the .pslopt file.

Vanessa Veelers
Parents

  • A solution for this problem is already available since many years and easier implemented than you think.

    As with many other settings, Inline Pattern are store in 3 different places. There is a set of inline patterns that is delivered with the product. These pattern are stored in the installation directory and can’t be changed.

    All patterns that you create on your own are stored (by default) on your computer in the Custom Pattern.

    To solve the issue, simply move custom patterns into the project they belong to using drag and drop and don’t forget to activate the patterns in the project and deactivate them in the custom pattern. When you now export a translation bundle .tbulic all the patterns embedded in the project will be automatically embedded into the bundle.

    Parser settings are not exported into translation bundles. But this is not necessary as the free Translator Edition is not able to parse source files or generate target files.

    All TextRenderer setting are automatically stored into bundle with one exception. The font files, as they can be quite large and must be installed on Windows are not embedded into the bundles. So you need to send them along with the bundle. Translators must double-click the font files to get them installed on their Windows system. But this has to be done just once, when the translator receives the first bundle.

Comment

  • A solution for this problem is already available since many years and easier implemented than you think.

    As with many other settings, Inline Pattern are store in 3 different places. There is a set of inline patterns that is delivered with the product. These pattern are stored in the installation directory and can’t be changed.

    All patterns that you create on your own are stored (by default) on your computer in the Custom Pattern.

    To solve the issue, simply move custom patterns into the project they belong to using drag and drop and don’t forget to activate the patterns in the project and deactivate them in the custom pattern. When you now export a translation bundle .tbulic all the patterns embedded in the project will be automatically embedded into the bundle.

    Parser settings are not exported into translation bundles. But this is not necessary as the free Translator Edition is not able to parse source files or generate target files.

    All TextRenderer setting are automatically stored into bundle with one exception. The font files, as they can be quite large and must be installed on Windows are not embedded into the bundles. So you need to send them along with the bundle. Translators must double-click the font files to get them installed on their Windows system. But this has to be done just once, when the translator receives the first bundle.

Children
No Data