0.48 files messed, debian stretch amd64

[kastrolis imanta]

Inkscape 0.92.0 r15299
All my files where is text over image is not displaying properly.

[su_v (suv-lp)]

The provided SVG file was created with Inkscape 0.48.5, and contains non-uniformly scaled bitmap images. Due to changes in Inkscape 0.91 to better conform to the SVG standard, such bitmap images are rendered differently (older Inkscape versions ignored the SVG specification in this regard).

The extension 'Extensions > Images > Set Image Attributes' included in Inkscape 0.92 can restore the rendering of the scaled bitmap images to match the appearance as seen in Inkscape 0.48 and earlier.

Proposing to link as duplicate to bug #1357808.

[kastrolis imanta (kastrolis)]

thank you!
and sorry for panic...
k.

On 2017.01.23. 02:15, su_v wrote:
> The provided SVG file was created with Inkscape 0.48.5, and contains
> non-uniformly scaled bitmap images. Due to changes in Inkscape 0.91 to
> better conform to the SVG standard, such bitmap images are rendered
> differently (older Inkscape versions ignored the SVG specification in
> this regard).
>
> The extension 'Extensions > Images > Set Image Attributes' included in
> Inkscape 0.92 can restore the rendering of the scaled bitmap images to
> match the appearance as seen in Inkscape 0.48 and earlier.
>
> Proposing to link as duplicate to bug #1357808.
>
> ** Tags added: bitmap svg transformations
>

[su_v (suv-lp)]

Sorry for the inconvenience due to earlier changes in Inkscape 0.91. The workaround to adjust bitmap images is not obvious to users, and barely mentioned in the release notes:

- The release notes for 0.91 do not mention the changes in the renderer to follow the SVG standard with regard to how the aspect ratio of non-uniformly scaled bitmap images is determined.
- The release notes for 0.92 do mention the extension with just a brief summary line of bug #1357808.

Nevertheless the default settings of the extension (the first tab) should allow users to restore the old appearance with a "single" click (once the user is aware that this particular extension was provided to help in such situations).

In hindsight, automating the same changes that the extension applies when opening legacy documents would have been a nice feature, but at the time (before the initial release of 0.91) there were neither the resources available (only few core developers), nor a full awareness of the possible impact for users. Now (two releases later), this likely cannot be safely automated (on load) anymore because the affected cases/files can't be determined definitely based on the metadata available in Inkscape SVG files.