Let pick a charset when generating code coverage html report

[alesana-san]

In version 3.1.2 there's a hardcoded value UTF8 for this kind of report. In case if you have some stuff in a different encoding (ex. Windows-1251), then all national symbols become unreadable

[jgebal]

Can you provide an example with following information:

• Database NLS character set
• session NLS character set

We have a solution for XML reports already so i think the same should work for HTML (when we add it).

I guess that we should give the report back to user in user NLS character set.
To confitm that thos would work, can you set your session NLS to UTF8 ans see if the saved report shows proper characters in browser?

[jgebal]

@alesana-san
Can you let me know what is your DB character set?

[alesana-san]

@jgebal
Sorry for being late, will try described steps in a couple of days.
DB charset is CL8ISO8859P5
Actually I don't know if my case counts because I ran ut.run and then saved the output from PL/SQL Developer to file. Maybe source code was affected somehow during the saving process.

[alesana-san]

@jgebal
Finally made a report using CLI and everything was OK. CLI put this line:

So I guess the issue can be closed.

[jgebal]

@pesse
Is cli replacing / adding charset to html report automatically? I thought it was to be provided from framework.

[pesse]

CLI is providing charset based on Java locale (not sure - have to verify). Framework is not necessarily able to auto-detect the charset needed.

[jgebal]

Checked. Client encoding is already passed to HTML coverage report when client application provides encoding.

Will update documentation to mention character-set setting.