MultiTerm 2104: Encrypt entries, does it work? Thread poster: Spiros Doikas
|
|---|
Spiros Doikas 
Local time: 07:21
Member (2002)
English to Greek
+ ...
MultiTerm 2104 SP1 11.1.1266.0
I tried reorganizing and selecting encrypt entries. I tried also with selecting encrypt entries Set termbase to read only.
The terms were never encrypted or made read only. I tried with bigger and smaller dbs, as small as 10 MB. With big ones, i.e. 1 GB, there was a loss of entries.
Has anyone successfully completed encryption?
| | | |
Spiros Doikas
Local time: 07:21
Member (2002)
English to Greek
+ ...
TOPIC STARTER |
Hi Spiros,
This was broken with the MultiTerm 2014 release, so still works in MultiTerm 2011 if you need to do this? It is scheduled to be fixed in the next major release along with many other long standing Multiterm issues.
Regards
Paul
| | | |
Spiros Doikas
Local time: 07:21
Member (2002)
English to Greek
+ ...
TOPIC STARTER
|
|
|
| Glad you like it... | Nov 27, 2014 |
... it's one I also really enjoyed being able to write... almost as much as you guys will enjoy never having to worry about Java updates again!
Thank you
Paul
| | | |
Spiros Doikas
Local time: 07:21
Member (2002)
English to Greek
+ ...
TOPIC STARTER | just tried... | Nov 29, 2014 |
MultiTerm 2011 SP2 9.2.361.0 and it does not appear to work there either (tried just encryption and encryption and read only). When I export the database, the entries are not encrypted.
Termbase: birds-test reorganized.
Number of entries: 442
Encrypted: Yes
Frozen (read-only content): Yes
Operation start time: 29/11/2014 2:22:19 μμ
Error: Termbase is already encrypted. Operation not allowed.
Operation end time: 29/11/2014 2:22:22 μμ
| | | |
| Encrypt entries... | Dec 1, 2014 |
Hi Spiros,
Many apologies. I should have tested this properly myself before relying on an old bug report. You're right... it doesn't work in 2011 either.
I can confirm however that this has been fixed in a development build due for release next year. I know this doesn't help you now, but if you have an urgent need perhaps we can encrypt it for you?
Regards
Paul
| | | |
Spiros Doikas
Local time: 07:21
Member (2002)
English to Greek
+ ...
TOPIC STARTER | No worries Paul :) | Dec 1, 2014 |
Thank you so much for your kind offer; I might take you up on it. It all depends on when exactly the new version will be out as there is no pressing need for the time being.
| | |
|
|
|
Spiros Doikas
Local time: 07:21
Member (2002)
English to Greek
+ ...
TOPIC STARTER
Hi Paul, I emailed you about this issue. Did you get it?
| | | |
... and apologies for not responding to you yet. I spent a while on the files you sent me because I cannot work with them. They are too large for me in a filebased TM, even after changing the registry settings to increase the MS Access (JET DB) limit on file locks. And I can't encrypt them on a server because server doesn't need this capability and it's not there!
I think, given the number of duplicates and clearly wrong terms in the samples you sent me (IATE does contain a lot o... See more ... and apologies for not responding to you yet. I spent a while on the files you sent me because I cannot work with them. They are too large for me in a filebased TM, even after changing the registry settings to increase the MS Access (JET DB) limit on file locks. And I can't encrypt them on a server because server doesn't need this capability and it's not there!
I think, given the number of duplicates and clearly wrong terms in the samples you sent me (IATE does contain a lot of terms that should be "cleaned"), that if you cleaned the files first and cut them down a little then it might be worth trying again.
But at the moment I think circa 180k entries is simply too big... at least I can't handle these files on my laptop.
Regards
Paul
SDL Community Support ▲ Collapse
| | | |
Spiros Doikas
Local time: 07:21
Member (2002)
English to Greek
+ ...
TOPIC STARTER
for trying Paul
I sort of imagined they would be too big to handle even with the new version.
| | | |
| Why encrypt IATE?! | May 9, 2015 |
SDL Community wrote:
I think, given the number of duplicates and clearly wrong terms in the samples you sent me (IATE does contain a lot of terms that should be "cleaned"), that if you cleaned the files first and cut them down a little then it might be worth trying again.
But at the moment I think circa 180k entries is simply too big... at least I can't handle these files on my laptop.
Just curious: even if it were technically possible, what would be the purpose of encrypting a termbase made of publicly available data?
| | |
|
|
|
Spiros Doikas
Local time: 07:21
Member (2002)
English to Greek
+ ...
TOPIC STARTER
The main reason is to test technical feasibility for large proprietary databases.
The other reason, is that, as Paul correctly pointed out, IATE is full of repetitions and noise, and one could undertake to substantially improve that data in the long term (as I am currently doing, which is, as you understand, a major undertaking); hence, until further improved versions are produced, it would be better not to propagate terminological data of inferior quality.
| | | |
Spiros Doikas
Local time: 07:21
Member (2002)
English to Greek
+ ...
TOPIC STARTER | MultiTerm 2015 | Oct 6, 2015 |
I just tested in MultiTerm 2015 12.0.1504.0 and it still appears unresolved. I.e. I reorganized a termbase by selecting Encrypt Entries, then it appears to encrypt them:
Termbase: countriestest reorganized.
Number of entries: 244
Encrypted: Yes
Frozen (read-only content): No
Operation start time: 6/10/2015 12:58:20 μμ
Operation end time: 6/10/2015 12:58:23 μμ
Then when I try to export the entries, they are exported in any format and ter... See more I just tested in MultiTerm 2015 12.0.1504.0 and it still appears unresolved. I.e. I reorganized a termbase by selecting Encrypt Entries, then it appears to encrypt them:
Termbase: countriestest reorganized.
Number of entries: 244
Encrypted: Yes
Frozen (read-only content): No
Operation start time: 6/10/2015 12:58:20 μμ
Operation end time: 6/10/2015 12:58:23 μμ
Then when I try to export the entries, they are exported in any format and terms are not encrypted in any way.
Checking "Set termbase to read only" will disable the export options. ▲ Collapse
| | | |
Login to reply/comment 
Translation news related to SDL Trados
