To even attempt to work with something like this I would expect example data, or use of SAS supplied data set in the SASHELP library like Sashelp.class, the entire definition of the template and example Sgrender code to call the template and use the data. If an image could be supplied of what the expected appearance for that data would be that helps as well. ... View more

If your title is correct, it looks like you are reading UTF-8 data in a session that does not support this encoding (probably some form of wlatin). UTF-8 can encode many characters that do not exist in wlatin. So these characters are lost, as the message describes.   To avoid losing them, you should run your SAS session using UTF-8 encoding. That's a start-up option.   A similar issue arises when moving files to/from mainframes as some characters only exist in ASCII or EBCDIC representation. ... View more