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
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
We have the same problem with Studio 2017 SP1 and the MS Word filetype 2007-2016. Field functions with a date get converted to { SAFEDATE \@ "dd MMMM yyyy HH:mm:ss" \* MERGEFORMAT }.
Changing settings in Windows or using Search & Replace is no option, because we have several field functions in one document, with different formats (e. g. YYYY-MM or just YYYY) which are all changed to the same above long form.
Now, that the filetype MS Word 2007-2013, with which this problem did not occur, was removed, we have a serious problem.
I reported this behaviour to the Support half a year ago, but nothing was done. What can be done to get this false behaviour finally repaired?