Friedrich W. H. Kossebau wrote: Hi,
> So all the PNG versions are there as handcrafted optimized versions of their > SVG counterpart, so the icons are still usable when needed in sizes of > 16,22,24,32,48,... Isn't that an answer to the question "why are there also png icons" (or to "why are so many provided as svgs for a particular bitmap size")? > SVG versions no longer need handcrafted substitutes) that would not really be > recommended, so no-one has yet added support for that. I actually discovered the existence of the scalable icons because of "oxygen- icons5-scalable" packages provided by Fedora and Arch. Can we assume that QIcon will use the bitmap version if it exists for a given size? If so, installing the scalable versions as well shouldn't hurt the smaller icons on normal resolution screens, while still given the best quality where even on those screens a large/huge/humongous icon size is used (think application icons in the app switcher on Mac). > Hm, actually it seems the scalable versions are not even installed by the > buildsystem? Nope, and there is no index.theme file in the scalable subdirectory. > indeed at least QSvg seems to fail on some icons by a quick test, so that > might be the reason. Yeah, I also thought it might be a work-in-progress; I noticed some of those too: view-list-tree.svg qt.svg: link use5411 hasn't been detected! qt.svg: tab-close.svg:6352: Could not resolve property: radialGradient3709 qt.svg: document-new.svg:602:58: Could not resolve property: linearGradient5167 qt.svg: document-open.svg:4290: Could not resolve property: pattern5614 qt.svg: document-open.svg:4290: Could not resolve property: pattern5626 qt.svg: document-open-folder.svg:4224: Could not resolve property: pattern5614 qt.svg: document-open-folder.svg:4224: Could not resolve property: pattern5626 Inkscape only complains about document-new.svg ("unknown type: ns:sfw"). Cheers, R.