Critical terminology-related issues in T2014 SP2

Dmitry Pakidov wrote:

Hi,

This post is mainly addressed to Paul Filkin, but any other SDL employee that can give concrete answers is also welcome to reply.

More often than not I find myself working with texts with large sentences, be it contracts or otherwise, that may sometimes even span for several screens, with such documents either having their own terminology lists or being accompanied by glossaries submitted by the customer. This implies the need to use Studio’s terminology management module in order to complete my work quickly and effectively. However, in the process of using the module I constantly encounter two critical bugs, which by Studio 2014 SP2 have—for some bizarre reason—been mostly neglected.

The first is the long-known term recognition bug where Studio fails to recognise (almost) any terms starting from the 256th (or so) character into a segment, while the terms it fails to recognise are present in the active termbase(s) (see illustrations here and here).

The second one is where all the terms correctly added into a termbase throughout a given period of time without any error messages sometimes randomly disappear when Studio is closed.

These two bugs effectively render the terminology module unreliable and all but useless. Both bugs have pertained at least since Studio 2009, which makes them at least six years old (and probably much older!), and yet these critical problems with one of the main components of Studio have received next to no coverage on the part of SDL employees both in official statements and documentation, and I’m baffled and awestruck by this fact. Service Pack 2 for Studio 2014, which was supposed to bring, to quote Paul, “some far reaching changes in working with terminology”, did not fix these bugs, and its accompanying documentation does not even list them as known issues (see SDL_Trados_Studio_2014_SP2_Release_Notes.pdf).

Following Paul’s suggestion in another topic on this issue, I sent an email to [email protected] containing a detailed description of the bugs along with files in which they manifest, but apparently it did not deserve a reply, so I’m reposting the contents of the attachment here just in case: https://mega.co.nz/#!qE5SwR7R!Qh2yz9PNU4XMg7sdieqN02f83HQvSkLT7_mEG_yp9fA.

Reiterating these two critical issues is not the only reason of this post. I would also like to inquire the following:

1. How is it possible that such critical bugs pertain for 6+ years and will both of them ever get fixed?

2. How is it possible that, given the implications of the character recognition bug, there was/is no widespread user outcry? Clearly every Studio user working with the terminology module must be encountering it (those working with CJK less so, I suppose).