Character conversion and UNOC in EDI out files
- Article Type: General
- Product: Aleph
- Product Version: 16.02
The Aleph documentation ought to state that you should always use UTF_TO_8859_1 in edi_out_attr (as if you do not the EDI messages have a header which conflicts with their contents) or the Aleph EDI software needs to be altered so that the header of the EDI output matches the character set chosen in edo_out_attr. Perhaps a means of achieving this would be to include the EDI header string as an additional column in edi_out_attr? You could then give UTF_TO_8859_1 in conjunction with EDIFACT character set UNOC, and if you left it blank could specify EDIFACT character set UNOY.
If no character conversion is defined in the table edi_in_attr UTF_TO_8859_1 and 8859_1_TO_UTF are defaulted respectivly.
edi_in_attr, character conversion, EDI
- Article last edited: 10/8/2013