Hi Oleksandr,

Indeed, in the viewer's string resources there aren't key-value pairs for localizing the export options. I have converted the ticket to a Bug Report and made it public. I have also updated your Telerik points as a token of gratitude for reporting this problem.

As a workaround, you may use the fact that the Export menu list values are customizable. You may change them from the REST Service project configuration file, or from the JSON returned by the Get Available Document Formats request. Next, you may find more details on the two approaches:

• For the first option, I suggest the extensions Element article. The description attribute of the extension element specifies what will the user see in the Export menu:

<configuration>
  …
  <Telerik.Reporting>
    <extensions>
      <render>
        <extension name="PDF" description="localized PDF Description" />
      </render>
    </extensions>
  </Telerik.Reporting>
  …
</configuration>

• The other option involves modification of the ReportsController. Here is a sample implementation of the virtual GetDocumentFormats method that sets custom values to the rendering extensions' description:

public override HttpResponseMessage GetDocumentFormats()
{
    var documentFormats = base.GetDocumentFormats();

    var extensionsInfo = (IList<Telerik.Reporting.Services.Engine.ExtensionInfo>)(documentFormats.Content as ObjectContent<IList<Telerik.Reporting.Services.Engine.ExtensionInfo>>).Value;
    foreach (var extensionInfo in extensionsInfo)
    {
        switch (extensionInfo.Name)
        {
            case "PDF":
                extensionInfo.LocalizedName = "my localized PDF";
                break;
            case "CSV":
                extensionInfo.LocalizedName = "my localized CSV";
                break;
            //...continue with the other extensions
        }
    }

    return documentFormats;
}

The second approach is more flexible and overrides the values set with the first one.

Regards,
Todor
Progress Telerik