Studio SR1 problem

Hi, I have resolved this problem but I can't work out how else to bring it to SDL's attention:
I've just uninstalled SR1 for Studio 2015 (as per KB article 8124). Even though I don't use GroupShare I had the following issues with SR installed:
- I tried to generate an updated AutoSuggest dictionary and at the end of the "Exporting translation memory to tmx" I got the error message:

"The 'type2' attribute is not declared

- Also, date/time format in concordance search window had changed to US English!

Both issues don't occur after reverting to CU1

Translate

Rate translation

Suggest better translation

Moderator UI

Thread Subject & Description
Studio SR1 problem Hi, I have resolved this problem but I can't work out how else to bring it to SDL's attention: I've just uninstalled SR1 for Studio 2015 (as per KB article 8124). Even though I don't use GroupShare I had the following issues with SR installed: - I tried to generate an updated AutoSuggest dictionary and at the end of the "Exporting translation memory to tmx" I got the error message: "The 'type2' attribute is not declared - Also, date/time format in concordance search window had changed to US English! Both issues don't occur after reverting to CU1
Get AI Suggestion

AI Reply

Accept answer Reject Answer

Parents

Jacopo Perenchio over 9 years ago

Got the same problem about date/time format, this is very critical for me. Hope to get an update soon.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Paul over 9 years ago in reply to Jacopo Perenchio

Hi Jacopo Perenchio ,

I wonder if you replied to the right thread? Perhaps it would make sense to create a new one and describe the problem you are having with date/time format?

Regards

Paul

Paul Filkin | RWS Group

________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Jacopo Perenchio over 9 years ago in reply to Paul

The original thread from Nicholas reads:

- Also, date/time format in concordance search window had changed to US English!

Am I wrong?

J
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Paul over 9 years ago in reply to Jacopo Perenchio

No - you're right, I'm wrong. Didn't notice that little addition to the main issue, and you're right about that too as I also have this in the TM lookup and concordance. Didn't notice that before, but definitley confusing, I also double checked Studio 2014 and it was UK format in there. I'll pick that up with the team and come back to this thread in due course.

Thank you

Paul Filkin | RWS Group

________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Paul over 9 years ago in reply to Paul

Hi all,

There has been a change with this release where the Autoupdate tries to match the language setting of Studio or Multiterm Desktop that you have chosen. However, this seems to have had an unwanted side effect in that Studio/MultiTerm only has EN(US) for example and the settings used draw from windows and overwrite the EN(GB) previously used with EN(US). This will be fixed in a future update.

In the meantime if you go to your regional settings in the windows control panel you can change the EN(US) formats to match the ones you prefer, and then when you restart Studio this will be reflected.

Having said this, the tests I just ran worked well for the TM and Concordance window for example, but not the reports. The EN(US) date format remains even in new reports generated after I made this change.

But hopefully this workaround will work for you until we issue an update correcting this behaviour.

Regards, and thank you for pointing this out again!

Paul

Paul Filkin | RWS Group

________________________
Design your own training!
You've done the courses and still need to go a little further, or still not clear?
Tell us what you need in our Community Solutions Hub
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate
Nicholas Hoyle over 9 years ago in reply to Paul

Hi Paul,
I've just accepted and installed an update and was hoping this issue might have been addressed, but sadly not yet. Can you confirm whether it's in the pipeline? I can't get your workaround to stick - I think I've already got the settings you mention, but Studio still gives me the US date format.
Nick
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Reply

Nicholas Hoyle over 9 years ago in reply to Paul

Hi Paul,
I've just accepted and installed an update and was hoping this issue might have been addressed, but sadly not yet. Can you confirm whether it's in the pipeline? I can't get your workaround to stick - I think I've already got the settings you mention, but Studio still gives me the US date format.
Nick
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Share
Documentation Survey: help us offer you better documentation! Translate

Children

No Data

Trados Studio > 1. Trados Studio

Studio SR1 problem