Bug 78340

Summary: graphite fonts change rendering when "Nonprinting Characters" is enabled
Product: LibreOffice Reporter: Michael Stahl <mst.fdo>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: NEW --- QA Contact:
Severity: normal    
Priority: medium CC: caolanm, dr.khaled.hosny, gellert.gyuris, martin_hosken, nemeth
Version: Inherited From OOo   
Hardware: Other   
OS: Linux (All)   
See Also: https://bugs.freedesktop.org/show_bug.cgi?id=70666
Whiteboard:
i915 platform: i915 features:
Attachments: Test document

Description Michael Stahl 2014-05-06 13:48:20 UTC
for this bugdoc from bug 70666:
https://bugs.freedesktop.org/attachment.cgi?id=87870

the rendering changes quite substantially when the Nonprinting Characters
button is pressed: letters disappear, and the diacritic marks below the
red letters disappear or move around.

the problem happens at least since OOo 3.2, got worse in LO 3.4 - LO 4.2,
and appears somewhat less bad on master (only diacritics disappear),
so i'm not sure to what extent this qualifies as a regression...
Comment 1 László Németh 2014-05-07 11:16:34 UTC
I can reproduce the problem only with an explicit SAL_GRAPHITE_CACHE_SIZE:

Tested with the attached file (a reduced version of the file sent by Gellért Gyuris).

export SAL_GRAPHITE_CACHE_SIZE=512
soffice # bad
export SAL_GRAPHITE_CACHE_SIZE=
soffice # good

Warning! The Graphite extension set SAL_GRAPHITE_CACHE_SIZE in the .profile under Linux. (I had a lot of problems with it, reporting a few false alarms to Martin, because I didn't know about it.)
Comment 2 László Németh 2014-05-07 11:18:00 UTC
Created attachment 98616 [details]
Test document
Comment 3 László Németh 2014-05-07 14:08:54 UTC
Gellért found a similar SAL_GRAPHITE_CACHE_SIZE definition in his old .profile, (he used the Graphite extension and its cache settings). His newly installed Linux has no Graphite problems.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.