I have fields in my data files that contain the § character.
Art. 257 § 8 CTB,lei 9503/97
In my DM I can see it correctly, but when generating the PDF in Workflow it is not being interpreted correctly, getting something like �
Workflow is not fully Unicode-compliant, so you have to make sure it does not make changes to the data file before sending it to the OL Connect DataMapper.
If you absolutely need Workflow to make changes to the file, then you must first convert that file with the Translator task from UTF-8 to an encoding Workflow fully supports (for instance, Code Page 860 is for Portuguese).
Once the changes are complete, you will need to convert the file back to UTF-8 (again, using the Translator task) before you send it to the DataMapper.
2 Likes
Basically my Workflow will receive this data file and use All in One to produce a pdf file and send it to a directory.
Using the Translate Task, from UTF-8 to 860 (OEM-Portuguese) I only get the result:
Art. ART. 252 ? single CTB, law 9503/97
In PPS7, this coding was used in Data Emulation and in the Workflow the task of Creating PDF. Getting the correct result.
I see from your PPS7 screen shot that the Data Selector’s encoding was set to ISO-8859-1.
Have you tried simply setting your DataMapper encoding to ISO-8859-1 as well? Then you wouldn’t have to perform any translation in Workflow.
Yes, but now I pay attention to what I said about changing the file before. I use a pre-processing script. I changed it there too and now I got satisfactory results.
var inFile = openTextReader(data.filename, “ISO-8859-1”);
var outFile = openTextWriter(data.filename + “.tmp”, “ISO-8859-1”);
var inRecord = false;
1 Like