Passolo SRX segmenter bugs
Thread poster: Evzen
Oct 19, 2014

Posted this to Passolo User Forum, but it seems rather quiet, so I'm reposting here in a hope that it gets noticed by relevant people...

I tried to set up a simple Passolo project with HTML and Java properties files (with sentence level segmentation) and German as source language.
And Passolo created a zillion of totally wrong entries segmented after German abbreviations like z.B. or d.h. and others .

After some research I found the following bugs in SRX segmenter add-in:
  1. New/edited segmentation rules are not stored. This is because Passolo.srx file is stored in Passolo System folder, which is not writable for non-admin users...
    As far as I can see, this serious bug is still present even in Passolo 2015
    It was reported back in 2010 already:

  2. SRX language-specific rules don't work out-of-the-box. With the default languagepattern="[Dd][Ee].*" definition Passolo does NOT recognize German language.
    Only after adding languagepattern="[Gg][Ee][Rr].*" mapping Passolo finally started using the German rules. It looks like a bug - Passolo should use the ISO language abbreviation for matching the language pattern, not the language name (like German (Germany)).
    The help file states that Passolo uses only the "Default" language rules... hmmm, so why would the SRX file contain the other languages definition then?!
    To me it looks like no one in Passolo/Trados/SDL really understood how the languagepattern should be actually configured, so they added this weird sentence to the help file to cover their backs... :-\

  3. The set of segmentation rules provided in default SRX file is totally insufficient and results in a lot of wrongly segmented text.
    Can't you guys simply take the ruiles, abbreviations list, etc. from Studio?! One would expect that products of the same company work the same way...

  4. The default segmentation rules exceptions definitions are rather incorrect - they all start with "\s", so abbreviations inside parentheses (like "blabla (z.B. bleble)") are not recognized and result in segment break.

  5. It would make sense that the Passolo.srx file written by Passolo keeps the XML structured/indented formatting like the original default file, so that it's still comfortably editable in e.g. Notepad.
    Currently Passolo writes it is a single huuuuge line which makes it pretty unusable in plaintext editors

In the end I had to drop Passolo and move the project to Studio...
I found pretty alarming that such expensive tool like Passolo has such essential functional bugs... which apparently exist for a very long time

Direct link Reply with quote

To report site rules violations or get help, contact a site moderator:

Moderator(s) of this forum
Myron Netchypor[Call to this topic]

You can also contact site staff by submitting a support request »

Passolo SRX segmenter bugs

Advanced search

Manage your TMs and Terms ... and boost your translation business

Are you ready for something fresh in the industry? TM-Town is a unique new site for you -- the freelance translator -- to store, manage and share translation memories (TMs) and glossaries...and potentially meet new clients on the basis of your prior work.

More info »
SDL Trados Studio 2017 Freelance
The leading translation software used by over 250,000 translators.

SDL Trados Studio 2017 helps translators increase translation productivity whilst ensuring quality. Combining translation memory, terminology management and machine translation in one simple and easy-to-use environment.

More info »

  • All of
  • Term search
  • Jobs
  • Forums
  • Multiple search