Slashdot Mirror
SVG And The Free Desktop (s)
unmadindu writes "Christian Schaller has written an interesting article on SVG's current and possible uses on the GNU/Linux desktop. Though the article concentrates mostly on GNOME, it does mention the excellent work the KDE developers have been doing with KSVG, and refers to the upcoming SVG support in Mozilla too."
Would it have killed you to say Scalable Vector Graphics once in the article?
I think that's a bit unfair. I for one would be happy if SVG was better supported as a web technology. The advantages to it becoming a standard is that useful, zoomable, interactive charting could be done easily on the client side. Just a little XML on the server side and then let the client deal with it. Right now I use Batik to render the SVG XML to PNG images before sending them to the client. Of course, the client can't zoom in on interesting areas like they can with pure SVG.
Javascript + Nintendo DSi = DSiCade
Steganography? Are you going for a keyword karma whoring? Because your post is just silly. Who would try to embed some secret information in an XML file when the whole purpose of XML is so the files can easily be edited in an arbitrary text editor? It doesn't make any practical sense... Even if you encode the text somehow, its presence would still stick out like a much larger sore thumb than, say, a message hidden in a JPG file.
I work at the Center for Teaching, Learning Technology at the university I am enrolled at. I am currently putting together a web-based document management system that is built around XML, and after seeing how much more powerful these open standards can be (especially, when you start looking at all the wonderful concepts that augment XML -- XSL, XPATH, XSL:FO, and the like).
We used to put together all of our documentation for workshops and whatnot using MS Word, and then later switched to InDesign for the sake of having more control over the layout. The new web-based system means we lost some control over the layout of these documents, but the amount of time we've saved and the flexibility we've gained from using it is worth more than its weight in gold (all 2mb worth -- if that, even)
What's frightening, however, is to see these products like MS Word and others potentially offering the option to export to a more open format, like XML. Ever tried reading through MS Word generated HTML? It's almost a fun task, and I hate to think of the possibilty of having to read through MS Word generated XML... eep!
huzzah
The best way to do this is with vector based graphics, which is what SVG is.
It's time for pixels to go away. With displays running from cellphones to graphic arts workstations, the concept just isn't useful any more above the renering level. I look forward to replacing as many as possible of the old pixel-based graphics format with something I can see at more than one display resolution.
Now if we can just get the Xwindows folks on board! When I say "12-point type", I mean a height of 6 lines per inch, not 12 pixels (enormous on the cellphone; invisible on the workstation).
Welcome to the Turing Tarpit, where everything is possible but nothing interesting is easy.
Hell, Y-Windows is thinking of using SVG for describing all their widgets. They plan a 1.0 release within the year.
SVG is being used almost everywhere I look. Icons are just the beginning.
SVG replaces PDF (Acrobat format)
No, it doesn't.
PDF (Portable Document Format) replaced PostScript as a page description language. Basically describing a printed page. PDF (and PS) both support vector graphics.
Whereas SVG is only a vector graphics format, it does not handle page layout and the other things required for printed page description.
If anything SVG replaces EPS (Encapsulated PostScript), which is the postscript language applied to an independent graphics object, as opposed to an actual printed page.