This document clarifies the scenario with accent marks in field txt entry history.
Exemplification
This may happen if the field structure in txt is wrong or if a forbidden special character exists, causing the error message in the txt file read.
What if you want to use, for example, a special character with an accent mark in the description?
In this case we have two behaviors:
If you want to book txt with the special character, it will be displayed thus:
It must be emphasized that if a structure error occurs in files containing these characters, you must format the file in the ANSI format and check the special characters it contains.
You must also check whether parameter MV_ACENTO is set to "S". If it is set to N, the entry is made without the accent marks and if it is ANSI formatted:
UTF formatted files can be read as usual, but depending on any special characters they may contain, a structural error message may be displayed; thus, you may need to check the structure and/or edit its format.