Am 21.01.2017 um 02:19 schrieb Marc Jeanmougin:
Hi all,
From my perspective (mainly bug reports and IRC support, but also a
lengthy irc discussion with deevad [from http://www.peppercarrot.com/en/article396/new-inkscape-0-92-breaks-your-prev... ]), the main noticeable thing about .92 was the line height breakage problem. I really think that it would be a good thing to include su_v's extension (or port it to a cpp internal function) and automatically apply it when opening files made with previous versions, and release the .91.1RC just after that (as soon as possible, even possibly before your proposed timing).
Ideally, we could also change the file import dialog to include instructions so that user would know what they should choose. Something along the lines of "If your file dimensions are based on pixels (you're not planning to use a cnc or print directly from inkscape), choose "ignore"; else choose "set viewBox", except if you know what you're doing." [might not be compatible with the "RC asap" because of the strings to translate]
In the terms of the pre-0.92 to 0.92 file update, we identified with su_v, by decreasing importance, the following items: (*1*) we need to apply, by default, the legacytext-fix ( https://gitlab.com/su-v/inx-legacytext/ ) to all pre-.92 files on open, or an equivalent (internal) solution; (*2*) The import dialog is very unclear on what users should do, might not cover all cases (I tried to draft a diagram of possible cases and ended up with the nightmarish http://imgur.com/h6uEOHm but I'd like Tav's input on when to do what, and what to advise people doing by default), and does not gives hints on what to choose; (*3*) we need to bump the export-xdpi prefs setting and others (once only[which means add a versionning mechanism into the prefs: "if prefs are older than inkscape, do it"], if possible (others : bitmap copy resolution,bitmap import resolution)); (*4*) we need a commandline way to bump files from .91 to .92; (*5*) Add prefs for (2), similar to the embed/link choices, so that users don't have to specify several times when working with sets of similar files (*6*) port all that to trunk and clean involved code (for instance, move all that updating code to a separate file-update.cpp instead of file.cpp )
- Just wanted to express my support for this and say 'thank you', Marc (and Deevad) for bringing it up!
(can't help much beyond giving feedback on string understandibility and translation, and later help populate the website contents).
Somewhat related: The broken default setting retrieval for line-height if em, %, ex or unitless is also causing confusion among users (https://bugs.launchpad.net/inkscape/+bug/1645016).
Maren