About Screen 0.92: get scaling pop-up

[Hachmann]

When I open the file http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/view/head:/share/screens/about.svg (About screen for Inkscape 0.92), I get the resizing dialog for Inkscape 0.92.

I'd have submitted a patch, if I knew which resizing method I should choose...

(did you know that the fonts used in the About screen are proprietary? The first one is even a Microsoft font... I guess that means that we couldn't turn them to path, so people can see the image as how it's intended by the author.)

[su_v (suv-lp)]

Ignore and resave - there is no need to scale such a pixel-based image at all (the about screen does not have to match a specific physical size, e.g. an A4 page defined in mm).

<off-topic>
> did you know that the fonts used in the About screen are proprietary?

Yes, I was surprised at the time that no one seemed to care that neither the branding fonts where used, nor fonts with an open license for the custom branding chosen by the submitter.

> I guess that means that we couldn't turn them to path

AFAICT the visible texts are already outlined (converted to path) in the about.svg installed by Inkscape 0.92 (same detail I recall for the original submission). There's a hidden layer with the original text samples.
</off-topic>

[su_v (suv-lp)]

Hachmann wrote:
> I'd have submitted a patch, if I knew which resizing method I should
> choose...

Simply edit the SVG file in gvim, and update the version information in the 'inkscape:version' attribute of SVG root is sufficient to stop the prompt for DPI change (see attached diff).

[Hachmann (marenhachmann)]

Thank you!

<off-topic>
People were not constrained to use the 'official' fonts... It wasn't phrased as a 'Must' in the rules.
Something to do better next time, I guess.
I just wish someone had spoken up earlier (I hadn't realized they are proprietary, else I'd have said something - annoying as that may be...).
</off-topic>

[Qantas94Heavy (qantas94heavy)]

This doesn't appear too important to change for 0.92.x, and it is already fixed for 1.0.

Closed by: https://gitlab.com/Qantas94Heavy