Welcome to the new Parasoft forums! We hope you will enjoy the site and try out some of the new features, like sharing an idea you may have for one of our products or following a category.

Webking reports from command line don't use UTF8

Options
LegacyForum
LegacyForum Posts: 1,664 ✭✭
Hi,

I have to scan some chinese or russian sites.
To report pages' title, I've created my own rule with the following Javascript code :

function ReportTitle(node, context)
{
var RuleContext = Packages.com.parasoft.api.RuleContext ;
RuleContext = context ;
RuleContext.report(node.toString()) ;
return 1 ;
}

Then, when I generate a CSV report from GUI, it works fine : all titles are reported using UTF8 encoding.
But when I do the same from the command line :

savereport -ToolTitleReporter -csv C:\Results\WebkingPages.csv

=> all UTF8 encoded characters are replaced by "?".

Example :

> CSV Report from GUI :

http://www.schneider-electric.cn/sites/chi...#21806;业 [PageTitleReporter]

> CSV Report from command line :

http://www.schneider-electric.cn/sites/chi...nformational,??? [PageTitleReporter]

Do I miss some kind of setting, or is it an issue ?

Thanks in advance,

Denis.

Comments

  • LegacyForum
    LegacyForum Posts: 1,664 ✭✭
    Options
    Hi Denis,

    We are looking into reproducing the problem. We will keep you posted.
  • LegacyForum
    LegacyForum Posts: 1,664 ✭✭
    Options

    Hi Denis,

    We are looking into reproducing the problem. We will keep you posted.

    One precision : this issue can be reproduced only with CSV format. With XML, it works fine in both cases (for now, it's a workaround for me, but I have to transform XML into CSV myself).

    Denis.
  • LegacyForum
    LegacyForum Posts: 1,664 ✭✭
    Options
    We created a support case for you. You should have received an automated email telling you that the case was created. If you did not, please email webkingsupport@parasoft.com with your current email address.
  • LegacyForum
    LegacyForum Posts: 1,664 ✭✭
    Options
    By visiting forum again, I've just seen that I didn't close the issue. It as been properly fixed by the patch you sent on 7th july.

    (Late) Thanks !

    Denis