Version: (using KDE 4.3.1) Installed from: Ubuntu Packages I just quote a blog entry I read: "End users hardly ever know that they use ODF, and if they do, they usually don't care too much. Is this something we should worry about? Yes. But what is the issue? In one word: Awareness. Take a look at popular file formats, like JPEG, MP3 or PDF. In terms of awareness, they are well known. This makes users drive demand for their support. Imagine a digital photo frame that wouldn't support JPEG, a digital audio player without MP3 support, or a PC that cannot (by no means) display PDFs. Who would want to have this stuff?" (taken from http://blogs.sun.com/GullFOSS/entry/unified_odf_icons) KDE could boost this effect with including these icons - which will come out with OpenOffice.org 3.2 - into the standard icon set, the Oxygen icon set. In my opinion they would fit quite good with the rest of the Oxygen theme. What do you think?
please note, that this icons are still under discussion in OOo. so please do not include the icons that are suggested in the blog. anyway - we would highly appreciate comments on the proposed icons.
Hi Folks, I've had a look at the icons and I think they look great and should be roled into oxygen-icon-theme. However, from a standpoint of allowing the user to identify the programme that created the specific document (writer, calc, etc.), especially when the icon is viewed in its smallest size and the graphic part may be hard to make out, you may want to consider changing the label from odf to odt or ods etc. I do understand that an aim here is to increase the standing of odf, so you may want to consider adding the precise extension as an extra label instead, in, say, the bottom right-hand corner, or even the name of the programme itself there. But that might just be too much clutter. Otherwise, the use of more colour in the graphic part of each icon, or different colours of the odf label might help (if indeed this is a problem in the first place). I'd have to see the icons in the range of sizes used.
Hello, can you please confirm if this is still an issue you think should be implemented?