Comment 4 for bug 1512222

Revision history for this message
su_v (suv-lp) wrote :

1) Console messages:
On OS X 10.7.5, with Inkscape 0.91 r13725 (XQuartz 2.7.8):
- not reproduced with default (new) preferences
- reproduced with the reporter's custom preferences file
The messages are triggered by the 'Text and Font' dialog which is restored from last session (they don't occur if 'text and Font' has not been opened in the current session yet); and AFAICT are caused by the user's default font style defined for the text tool (possibly originating from earlier Inkscape versions):

Reporter's preferences:
       style="fill:black;fill-opacity:1;stroke:none;font-family:Times New Roman;font-style:normal;font-weight:500;font-size:13px;line-height:125%;letter-spacing:0px;word-spacing:0px;-inkscape-font-specification:Times New Roman;font-stretch:normal;font-variant:normal"

New preferences created with Inkscape 0.91; default font set to 'Times New Roman':
       style="fill:black;fill-opacity:1;stroke:none;font-family:'Times New Roman';font-style:normal;font-weight:normal;font-size:40px;line-height:125%;letter-spacing:0px;word-spacing:0px;-inkscape-font-specification:'Times New Roman, Normal';font-stretch:normal;font-variant:normal;text-anchor:start;text-align:start;writing-mode:lr"

Attached is a modified version of the reporter's preferences file with the default font style edited so that the console messages no longer occur (@Ryo - there had been no further changes done to the file, so after renaming the modified version to 'preference.xml' you should be able to replace it as-is without losing other custom settings - make sure to quit all running Inkscape processes first).

2) Performance issue with provided test case (PDF file):
On OS X 10.7.5 (XQuartz 2.7.8):
- not reproduced with Inkscape 0.48.5
- reproduced with Inkscape 0.91 (default prefs)
The console messages exposed with the reporter's current preferences might increase the poor text editing performance, but the underlying performance regression in Inkscape 0.91 is as far as I can tell independent of current user settings. This regression is likely covered by earlier reports (I will test details with different builds and comment on any findings later on).