Translate
Is there any earthly reason why this field in a Docx (DATE \@ "dddd d MMMM yyyy" \* MERGEFORMAT) becomes this in the target version ( DATE \@ "dd MMMM yyyy HH:mm:ss" \* MERGEFORMAT)? I mea
Is there any earthly reason why this field in a Docx (DATE \@ "dddd d MMMM yyyy" \* MERGEFORMAT) becomes this in the target version ( DATE \@ "dd MMMM yyyy HH:mm:ss" \* MERGEFORMAT)? I mea
Hi Michael,
I'd suggest you look at your date settings here under File -> Options -> Language Pairs -> "your specific language pair":
Maybe the transformation is being driven by the setting you are using? I'm not sure why this would effect it as it is a field value, but perhaps the language settings are doing something here... worth a play anyway
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
Hi Bruce,
Thanks for your input.
I've unticked everything (see screenshot) (under Project setting as opposed to general options) and I still have Studio inserting hours, minutes and seconds. Really problematic.
Goodness knows what's happening.
Unknown said:
In the meantime, this problem alone means I have to go back to an old version of Studio for the purposes of this daily translation.
Off-topic question - how do you actually do this, given that upgraded license AFAIK cannot be used for lower version anymore? Or did I miss some change in the licensing policies?
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
I have created an idea on this topic: Translation of docx documents (MS Word): Do not change date field functions in the target file. You can vote on it.
I have created an idea on this topic: Translation of docx documents (MS Word): Do not change date field functions in the target file. You can vote on it.