diff options
| author | Chris Sherlock <chris.sherlock79@gmail.com> | 2014-04-20 11:47:58 +1000 |
|---|---|---|
| committer | Chris Sherlock <chris.sherlock79@gmail.com> | 2014-04-20 12:17:50 +1000 |
| commit | 588bb542bebdee5a67bd4695253c70646fb8a303 (patch) | |
| tree | 1c91b0e9dc31f745a7b00d874df27525065fa789 /extras/CustomTarget_autocorr.mk | |
| parent | 7f62b44458fb27f8aca652436aeafb5e033264bd (diff) | |
fdo#74702 Only VirtualDevice should handle the Word ext lead bug
In #i60945# it was discovered that Unix's leading external font spacing
causes problems with the display of documents. Therefore, the reference
device implemented a workaround, which was to set the spacing to zero.
However, the reference device is a VirtualDevice, so it should really be
handled there, not in OutputDevice. I have added a new protected function
to OutputDevice, GetFontExtLead() that handles this.
Change-Id: I1b84ee7d9f7ae96841b441b52705e67c8115ae5c
Diffstat (limited to 'extras/CustomTarget_autocorr.mk')
0 files changed, 0 insertions, 0 deletions