Studio 2017: Fields changed in Word when converting file back.

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

Parents
  • 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?

Reply
  • 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?

Children
No Data