**********************************
Edit 2/24/2017
Opened up a case with IBI for help
**********************************

Has anyone figured out how to resolve issues with ReportCaster mangling spanish characters.

I have my code page set to 1252 everywhere I can think of
-Reporting Server
-Application Server
-ReportCaster (Distribution Server Code Page and Webserver Code Page)
-Linux Server

I do not have this issue when running the report directly from the content area nor from the reporting server. This is only an issue when emailing the report from report caster (I have not tried the library but expect the issue to be the same). This is both with HTML and XLSX output types.

My redirection setting for xlsx is set to Redirect = yes , Save Report = yes

Any thoughts on where else to look to resolve this issue? Is it an encoding issue?


Thanks

This message has been edited. Last edited by: eric.woerle,

Get a trace from the email server. I had an issue a couple of years ago where the attachment was multibyte and the email server was single byte. Turns out that the attachment didn't identify the proper codepage of the attachment. You could be having the same issue in reverse. If library is fine then that could be it.

Report Library produces the same issue. I was originally thinking it could be the email server too... Doesn't seem like it.

Any chance you can show the before and after, and the hex values?

All accented characters are being represented as � . doesn't matter if its an accented o, u, or i.

In this case: Identificación del Estudiante
became: Identificaci�n del Estudiante

And: Número Consecutivo del Cupón
became: N�mero Consecutivo del Cup�n

Interesting. It looks to me like RC is converting to a multi-byte character set, and then it is being rendered in single byte.

You might want to check if there is another RC code page setting, and open a ticket.

When I take the character (F3 in 1252), then convert to utf8 and then display as ascii, I get something close to what you are seeing. However, I cannot duplicate it.

ya, I've been thinking along the same lines as you, that its saving it as muliti-byte character and excel is reading it as a single byte character (Or vice versa). I'm just completely confused why this is only a problem with RC. I'll check with IBI to see what insight they can provide on this issue.

Thanks dhagen!

In RC, it will have to open the file to either attach it, or copy it to library. It's more than likely that read that may be causing the problem.

Eric,

The Report Caster product manager, who checked with the NLS QA team tested out your issue. They set up similar configurations on our sandbox with code page 2152 but were unable to reproduce the issue.

They have requested that you please re-check your configuration, restart the application and distribution servers as well as the reporting server and let us know your results.

Here is the image received:


Thank you for participating in the Focal Point Forum!
Tamra Colangelo
Focal Point Moderator
Information Builders

Depending on the default encoding of you platform you may also have to set the file encoding in the Distribution Server startup script by adding -Dfile.encoding=es_ES.iso88591 to the java command in schbrk.sh. You can do locale -a on the command line to see all encoding options.