New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Offline multi-chart exporting to PDF doesn't keep font #7538

Closed
Samuel-Harbord opened this Issue Dec 14, 2017 · 0 comments

Comments

Projects
None yet
2 participants
@Samuel-Harbord

Samuel-Harbord commented Dec 14, 2017

Expected behaviour

Exporting to PDF using your multi-chart offline export example should keep the font used in the chart options or at least use the default fonts if this is not provided.

Actual behaviour

Regardless of the font used for the chart on the page, Times New Roman is used for fonts in the offline PDF multi-export using downloadSVGLocal, even in the offline multi-export example you've provided. This is not the case with single-chart exports, online multi-exports, nor multi-chart exports to other formats.

Edit: I also noticed that styling for data-labels (and probably other text) such as stroke and drop-shadow is not kept in the PDF export.

Live demo with steps to reproduce

Compare the PDF export result from this:
http://jsfiddle.net/gh/get/jquery/1.7.2/highcharts/highcharts/tree/master/samples/highcharts/exporting/multiple-charts/
to this:
http://jsfiddle.net/gh/get/jquery/1.7.2/highcharts/highcharts/tree/master/samples/highcharts/exporting/multiple-charts-offline/

If this is in fact a problem with the export logic, you should see Times New Roman as the font instead of Lucida Grande.

Affected browser(s)

All (tested with Chrome, Firefox, and Microsoft Edge)

@Samuel-Harbord Samuel-Harbord changed the title from Multi-chart exporting to PDF doesn't keep font to Offline multi-chart exporting to PDF doesn't keep font Dec 14, 2017

@oysteinmoseng oysteinmoseng self-assigned this Dec 15, 2017

@oysteinmoseng oysteinmoseng added the Bug label Dec 15, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment