Diaries

I am interested in learning xml. I think this is the hottest in making websites. I own a text-based site, アーティクル but better graphics with SVG can be still useful. I hope I can get good information here to learn more about SVG stuff!

I finally finished SVG chat on my dating website and used svg to revamp my poker webiste too ;) You can check it out if you want to...

24-4-08

After several years of waiting for SVG to reach some maturity and decent interpreters I think the time has finally come to start using it as a designer. There are a lot of problems still to overcome as the situation currently reminds me of my first encounter with HTML v 2.0 in 1994 and the problems of the differences in interpretation by the various browsers.

SVG promises to finally open the web to the designer without any of the limitations a glorified content fot HTML format like Flash had nor the limitations posed by MS XAML. Platform independent design has finally reached the community and I expect great things to happen on the web due to that.

I regard SVG still to be at it's infancy, but at least it has some useability now that will allow me to finally create pixel precise and scalable content that can be browsed by search engines edited in an instant and use the full potential of AJAX. I was greatly impressed by the work on SVG Draw that I found at pilat.fr

Let's face it, SVG has some strong enemies in both Adobe that has devised a SVG parser and made it unusable by diverting from the standard while biding it's time to buy Macromedia and Microsoft that is going to try to hijack the Web with XAML where it failed to do so with HTML.

As soon as there are some truly impressive SVG sites to show on the web and tool to create content reach some level of maturity that make them truly useable to create interactive content I expect a true explosion of colour and interactivity on the web pages, that until now have always been rather primitive copies of newspapers.

SVG will allow the designer to concieve new ways of showing content and maintain a logical structure of interaction for his user interface that totally eludes the boundaries of the HTML page and the viewport we're so accustomed to.

This time I inted to be part of that revolution and will try to post on a regular basis.

My special thanks goes to Stefan Goessner and Michel Hirtzler, whom decided to give access to their very well and clear written book on e-learning some time ago that enabled a cheapscate like me to finally get some good information on how to produce and handle SVG.

It prevented me from having to buy loads of books on the topic of SVG that probably like their HTML counterparts would render a 1 in 10 useability. Apart from that few books have seen the light lately and the info found in them can be a bit outdated.

Tools I currently use are Opera, Firefox and yes MSIExploder. The former two because they're good, the latter one,.. ah well,.. you know why. Sight.

Apart from that I use Inkscape which with the 0.46 version has become a truly useable tool, notepad++, Scribus, OO and a host of trialware that remind me of the buggy days of old.

I'm looking forward to see the first Python driven SVG capable CMS as I think that would greatly improve the interaction with all the Python driven open source software.

If you happen to have the desire to create just that next best thing to Cheese, I'll gladly offer my services to create some smashing graphics and UI for it. More of a hacker than a coder though.

Hello to anyone that finds my online diary - my first online diary, to be precise!

I am currently writing a report for uni regarding 2-D and 3-D modelling, and how it interacts with the real world and behind-the-scenes solutions such as 3-D Max. In browsing through the W3C's SVG page, I became a little more interested. I started reading more into SVG, what it is, and what it does, and have now integrated SVG into my report, which I will publish online after it's been officially submitted and registered, I'll post another diary post to keep you all updated as to when/where it will be available. I am particularly interested in the future of SVG, as from my research I can see the following behind SVG is vastly increasing, especially with the support of the Adobe suite. I'd be interested to hear others' members of the SVG garden's views and opinions on the future of SVG - is SVG the future?

Thank you.

http://www.webabisi.com
http://www.susshi.org
http://www.parmaktube.com
http://www.apbtr.org
http://www.wowdylan.org

I noticed the SVG page on W3 has not had a new topic for a few months.. just curious what's going on with that.

Windy Chicago

As designers have found to their cost the Web was not originally intended to be a design-rich environment. Instead HTML (hypertext markup language) was devised as means of disseminating information in the form of simple, reflowable text. With the arrival of Mosaic and support for the IMG image tag things began to change. Now that GIF and JPEG bitmaps could be embedded in Web pages the browsing experience became much more visual. The use of flat-colour GIFs for buttons, logos and headings took Web design onto a new level fueled by the development of dedicated Web graphic programs such as Macromedia Fireworks and Adobe ImageStyler.
However, in many ways this reliance on GIFs is just a historical accident as the format is by no means ideal. The body in charge of independent web standards, the World Wide Web Consortium (W3C), recognised as much and its Graphics Activity group helped develop a new dedicated Web bitmap format, PNG, with features such as better compression, ICC support and alpha transparency. Support for PNG is now growing, with the latest Navigator and Explorer supporting the format natively, but it will be a long time before PNG becomes the premier Web image format. In fact before that happens PNG is itself likely to be superceded.
This new Web image standard will be radically different to both GIF and PNG as it won't be based on pixels at all but rather on vectors. The two main benefits that vector images offer over bitmaps - small file sizes and resolution-independent scalability - become absolutely compelling within a Web environment where download times are crucial and viewing platforms vary dramatically. The advantages of vectors for the Web are so clear that a number of developers have already tried producing their own solutions such as Corel Xara's WEB and Deneba Canvas's Colada CVW files. The classic example of the use of such formats is the embedded map where browsers can zoom in on the image without loss of quality and with a download considerably smaller than the comparable fixed-size bitmap.
Corel Xara
Corel Xara offers vector export but without the necessary plug-in browsers aren't able to see it.
The benefits are obvious but so are the problems. To be able to view such formats the browser must either go to the trouble of installing a dedicated plug-in or have Java-based viewing available and enabled, otherwise they won't see a thing. Clearly what is needed is a universal independent standard that both graphic applications and browser developers can support natively and which can therefore deliver the critical mass necessary to ensure the format takes off. Cue the W3C. Back in Spring last year the W3C Graphics Activity group signalled that having finalised PNG they were ready to tackle a new Web-optimised vector format and that they were open to suggestions.
A couple of technical CAD-inspired formats were considered but the two major submissions were Adobe's PGML (precision graphics markup language) and Microsoft's VML (vector markup language). The two options were very different in many ways with PGML stressing output quality based on Adobe's Postscript and PDF know-how while VML stressed the importance of re-editability based on Microsoft's Office 2000 experience. What connected both formats though was that they were both conceived of as varieties of XML. In other words, rather than being traditional binary files, both PGML and VML are text-based languages acting to describe graphics in the same way that HTML describes web pages. This has a range of knock-on advantages, as we'll see, but the immediate consequence is that it made it relatively straightforward to combine the best of both approaches into the new W3C-approved Scalable Vector Graphic standard, SVG.
At the time of writing the SVG format still has to be finalised and approved but the working drafts posted on the W3C site over the last year make it clear how the format will work. Each SVG graphic is contained within a top level svg element which will enable an alternative bitmap to be shown for non-supporting browsers. Within the SVG the vector graphic will be built up with rect, circle, ellipse, polyline, polygon, and line elements with irregular objects handled with the all-encompassing path. Shapes can be nested and grouped into g elements and, crucially, these can be named and reused. The formatting of these objects is controlled through fill and stroke-based paint operations and again groups of parameters, such as gradients, can be named and reused. Best of all, wherever appropriate such formatting conforms to CSS and can be controlled on a global page level.
Putting this all together it's possible to see how a SVG will operate in practice. By centring text over a semi-transparent circle on a rounded rectangle you would have a simple button template. By naming this as a group it could be repeated as many times as necessary with just the overlaying text altered. By embedding each svg within a anchor tags you could produce all the navigation buttons you need with minimal effort and minimal download. Best of all the buttons would remain live and open to styling. Using a master CSS style sheet you could instantly change the colour of the button elements and text typeface automatically across an entire site!
This is huge power in a different league to scalable maps. Effectively you would have the restyling control offered by a dedicated web graphics program like ImageStyler but all available and controllable from a CSS style sheet. Best of all there would be no need to go through the current bitmap-based GIF route so that bandwidth demands could be cut to a fraction. It's no coincidence that today's major dedicated web graphics applications - Fireworks, Xara and ImageStyler - are all vector-based drawing programs optimised to output bitmaps. With SVG you could entirely cut out the bitmap middleman and keep the size and flexibility benefits of vectors throughout the production process from creation to viewing. Throw in the support of Microsoft, Netscape, Adobe, Autodesk, Corel and Quark and you can see that SVG is set to take the world of web graphics by storm.
SVG could offer the vector and restyling benefits of Imagestyler without the need for a bitmap middleman.
But hang on - hasn't something been forgotten in all this? You would never know it from the W3C deliberations - where the name is never even mentioned - but of course there already is a web vector standard out there: Macromedia's Shockwave Flash format, SWF. This isn't an XML-based language but a more traditional binary format that is embedded in the HTML page through object and embed tags rather like the GIF binary is through the img tag. However that's where the similarities cease as Flash is much, much more than just a GIF replacement.
Flash has always recognised that another of the benefits of vector shapes over bitmapped pixels is that once an object has been described all you have to do to animate it is to describe a path or other transformation. In other words all-action movie files are only marginally larger than static images and both are much smaller than their GIF equivalent. Building on this core animation strength Macromedia has added a level of interactivity that in the latest Flash 4 even offers conditional processing. Even better are the multimedia features with excellent streaming MP3 sound and video support for QuickTime 4 movies. Taken together it means that, in comparison to a simple GIF or SVG button, Flash can offer a fully scalable, interactive animated character complete with lip-synched speech and background music!
Flash 4
Flash vector movies offer far more than static images.
Of course the downside of Flash's binary SWF format is that it needs the Flash player to be installed to be viewable. But even this is no longer a huge problem. The benefits that Flash offers are so vast that the Flash player is a must-have download if you want to be able to appreciate many of the most popular sites on the Web. As such a recent independent survey claims that 83% of browsers are now Flash-ready - a greater market penetration than Netscape, Explorer or even Java can boast. On my own site the figure is nearer 50%, but even so it's clear that Flash usage has reached a level where it becomes the browser manufacturers' responsibility to ensure that they are Flash-compatible and both Microsoft and Netscape now bundle the player with their latest releases. Critical mass has been reached.
Suddenly the future for SVG isn't looking quite so bright. Flash offers greater functionality, better compression and a larger installed user base. More to the point it actually exists whereas SVG still hasn't got off the drawing board. Worst of all what looked like SVG's main strength, its XML basis, suddenly looks like a liability. There's simply no way that a text-based description of a graphic can be as efficient as a binary representation so that a Flash equivalent of an SVG file will inherently be smaller. The obvious comparison is to VRML, the text-based virtual reality markup language for describing 3D environments. This offers considerable power but its files are simply too large and slow to have made the impact expected of it. Into the gap has stepped Metacreations with its much more efficient streaming binary format, Metastream.
Flash has been such a success that it has effectively moved the goalposts as far as vector-based web image formats are concerned. A simple vector-based replacement for GIFs won't be enough to knock Flash from its position as the de facto Web standard. So is SVG effectively dead on arrival? Absolutely not. Instead it has evolved into a completely new and radically ambitious proposal that could entirely change the face of the Web. Looking at the latest working draft submitted in July shows that SVG will tackle Flash head on.
SVG Proposal
The W3C working draft gives details of the proposed SVG format.
The first paragraph of the Introduction shows the format's new scope:
"SVG is a language for describing two-dimensional graphics in XML. SVG allows for three types of graphic objects: vector graphic shapes (e.g., paths consisting of straight lines and curves), images and text. Graphical objects can be grouped, styled, transformed and composited into previously rendered objects. The feature set includes nested transformations, clipping paths, alpha masks, filter effects, template objects and extensibility."
It's clear that the intention is to use SVG for a lot more than buttons. In particular, in addition to the vector elements described above, SVG also supports JPEG and PNG bitmaps through the image element. It's also clear that the compositing control offered over both bitmaps and vectors will be far greater than currently available with the ability to use advanced masks and alpha channels to control features like transparency. All controls available for fills will also be available for strokes which again takes SVG into new territory. Potentially most powerful of all are the filter effects which will allow bitmapped effects, such as semi-transparent drop shadows, to be applied client-side. Thanks to XML's extensibility it will also be possible to embed application-specific data to keep images live and editable and so turning SVG into an all-encompassing graphics standard.
Just as significant is the handling of text through the text element. Crucially, this is dealt with as XML character data which means that all the text in the SVG remains selectable and searchable just as it is in HTML. With the use of CSS for controlling text formatting within the SVG the distinction blurs further. In fact the SVG should be able to incorporate HTML itself as another stated aim is "to provide a frame for the HTML/CSS processor so that dynamically reflowing text (subject to SVG transformations and compositing) could be inserted into the middle of an SVG document."
The new picture of SVG that is emerging is a long way away from zoomable maps and stylizable buttons. In particular it is apparent that the full potential of SVG isn't as embedded fragments within HTML but rather the reverse with the SVG acting as the main document and containing shell. In other words, at its best, SVG will be the Web page itself. Of course this is where the scalable in scalable vector graphics really comes into its own. When the whole page including text is scalable, design can move onto a completely different level. The advanced composition controls are a huge bonus but the real difference will be that whatever device the browser is using, from handheld to 21" monitor to printer, the designer can control exactly what they will be viewing or outputting! Heaven. As the W3C puts it "this benefit to Web users as a community cannot be understated."
Scalability
The real benefit of scalability is that entire pages will look the same on whatever screen they are viewed.
In this new page design role, SVG acts like a static Flash counterpart, but that's only the beginning. The second paragraph of the W3C introduction reveals that:
"SVG drawings can be dynamic and interactive. The Document Object Model (DOM) for SVG allows for straightforward and efficient vector graphics animation via scripting. A rich set of event handlers such as onmouseover and onclick can be assigned to any SVG graphical object. Because of its compatibility and leveraging of other Web standards, features like scripting can be done on HTML and SVG elements simultaneously within the same Web page."
In other words, SVGs will be able to act much like full Flash movies. Animation will be possible thanks to a "syntax for describing simple time-based modifications on any attribute or property on any of its elements." This will enable the creation of motion path animations, fade, scaling and rotation effects and could spell the end for the animated GIF. Interactivity meanwhile becomes possible thanks to the ability to assign standard event handlers to any object or group which will enable rollover and button-based control. Even more significant is the way this is implemented through SVG DOM support which opens up every element in the graphic to scripting. As the working draft says "Every attribute and style sheet setting is accessible to scripting, and SVG offers a set of additional DOM interfaces to support efficient animation via scripting. As a result, virtually any kind of animation can be achieved, including motion paths, color changes over time, and transparency effects."
Ultimately it is this integration between the SVG proposal and other existing Web technologies such as DHTML and CSS that is the format's true killer feature and gives it the edge over the standalone Flash format. It means that the graphical elements of a Web page will no longer be seen as semi-detached add-ons but rather form its heart as a fully integrated and fully controllable part of the overall design. As other technologies such as SMIL (synchronised multimedia integration language) come on tap they will be similarly incorporated to produce an unmatchably rich Web experience in which text, graphics, multimedia, style and scripting elements are seamlessly blended. In fact it is this synergy of different technologies, all pulling together to create a product that is more than the sum of its parts, that represents the ultimate scalability in SVG.
The benefits for the end user should be immense with the Web experience finally beginning to live up to the WebTV dream. In fact if SVG fulfils its potential it might just be that HTML will come to seem like the poor relation with the richest experiences on the Web only available through SVG and the next generation of XML-based browsers. The revolution could be just as radical for creators as consumers. The days of hand-coding in Notepad will certainly be over with a new breed of truly wysiwyg XML-authoring apps combining the features of Dreamweaver, Fireworks, ImageStyler and Flash into one master program. I can hardly wait.
But of course I'll just have to. It's worth remembering that the SVG proposal hasn't yet been finalized at the time of writing and the most common sentence in it is still: "The exact mechanism for providing these capabilities hasn't been decided yet - many details need to be worked out." Even when the format has been approved there's a long way to go before supporting browsers have proved their reliability and developed the necessary user base (especially as Microsoft has steamed ahead with its own VML format in any case). Even then there's the chance that the format will be too download-heavy and slow to render to prove practical. As PNG and VRML have shown, there's a big gap between the drawing board and the real world.
For the foreseeable future then there's no question that Flash remains the web vector format of choice. Moreover, with Macromedia's moves in opening up both the SWF format and Flash player code and various hints about future XML-compatibility, there's still a good chance that SWF will see off the SVG challenge. What's not in doubt is that the Web is changing and that the designer's nightmare is definitely coming to an end. In fact, with a technology like SVG at its heart, the Web looks set to become the designer's dream - visual, interactive, animated and scalable.

Hallo, i am looking for the Adobe plugin test page who lets me know the plugin installed correctly. But i cant find this site anymore. Can someone help me?

Illy from Ferienwohnung Ostsee @ Germany.

Hello everyone

Im Andres from Uruguay, i am a CEO of my web design company.

Happy to be here

Surprisingly, not many people have heard of the Apache Cocoon server/framework/components. That is really too bad. Things have really tilted at last during the past year or two into the the full bore use of XML in order to get user friendly products to market. Run of the mill applications are easily created using run-of-the-mill techniques. That is what the 1990s were all about. Recreating the 1970s style dumb terminal block mode user interfaces on a decades more advanced screen and keyboard setup added... images, styled fonts, and a mouse. That may sound like heresy, but it is true. However, in the late 1990s - there was a slight course change. It was basically taking place at the W3. They noticed a lot of information was going into web pages, and sadly, a lot of it would never come out again. The reasons were varied but one big problem is that web designers/developers/authors were using HTML more like a paint set than elements of a world wide information system. Google noticed this, and cashed in big by providing a way to search these massively non-structured, come as you are, anything goes web pages. Yahoo got its start, even before Google came on the scene, as the first truly gigantic hand-maintained catalogs of web pages. Fast forward to the middle of the first decade of the 21st century. We now have free tools on our desktop that do some pretty magical things, all thanks to XML, which is as easy for computers to understand - as web pages are for ordinary people to understand. Last year, in late 2005, Firefox 1.5 was released. One of the things it introduced was built-in support for displaying SVG graphics. Until Firefox did it, no other major web browser had that SVG image displaying capability built right in. However, Apache Cocoon, another free/opensource software program, has been providing very elegant SVG support on the web server side of the web for about half a decade. Apache has a couple neat components in it that come directly into play when working with SVG. There is an SVG-to-XML Serializer. It takes SVG information and publishes it in an XML format of SVG. Flexible from a software standpoint, but not too pretty to look at from a human standpoint. There are some other SVG serializers that render into well known image file formats. People with legacy browsers that don't support SVG directly yet will be more interested in these, pro tem, than the SVG-to-XML serializer. Here are these other serializers: * SVG-to-JPEG serializer * SVG-to-TIFF serializer - Mac OS X really likes this format, and Group 3 FAX uses it as well * SVG-to-PNG serializer - PNG offers fantastic compression compared to GIF and often JPEG too Someone has already harnessed this XML-driven data management and display power that is built into Cocoon, courtesy of SVG, to produce an interactive data exploration tool. The tool lets the user graphically investigate various statistics about voting errors in the French 2002 election. This same information would be very difficult to digest in dry tables, which is how we would all probably be looking at it if this was 1996 (or 1976 ). However, it the 21st century now, so they used Coocoon to process the information and render it into interactive maps that presented the information as it related to the geography of France. A pretty clever idea, considering the relevancy of geography to voting in the first place.

The other morning I read the article above as I drank my morning coffee. "In the first study of its kind, three experts in the study of written language have described the common characteristics that caused three famous scripts -- ancient Egyptian, Middle Eastern cuneiform and pre-Columbian Mayan -- to disappear. "The study's basic conclusion: Writing systems die when those who use them -- priests or scribes or invaders, for instance -- restrict access to them." This was an article that I might easily have skimmed or passed by all together. But something seemed strangely familiar about these issue to me. ``The sociological and cultural dimension is crucial,'' said Brigham Young University archaeologist Stephen Houston, the study's Maya specialist. ``Successful systems don't have these prohibitions. Once there's this perception that the writing is only for this function or that function, script death is almost a self-fulfilling prophecy.'' So what was so compelling? First, SVG is a language. As such, it is interesting to learn how linguists and sociologists think languages work, and what makes them succeed or fail. Second, there is something to be observed about how things are adopted in general from a sociological and cultural perspective. So here are some of the things that this article brought to mind for me. 1. Restricting access to communication technologies diminishes the value of those technologies and results in their ultimate demise. This is really no different than Metcalfe's law, which says that the value of a communications system grows as the square of the number of users of the system and Reed's law, which says that the utility of large networks, particularly social networks, can scale exponentially with the size of the network. Another related argument is Andrew Odlyzko's thesis, Content is Not King that connectivity is more important than content. For me this last article speaks to SVG's inherent ability to bridge diverse data sources such as you commonly find in the GIS world. One way to look at organizations like Open GIS is that they realize that the connectivity of GIS databases often provides more value than any of the separate databases separately. I would include the lack of extensibility as one form of access restriction. 2. Conversely, technologies that permit broad adoption thrive. In the 80's the desktop publishing revolution made technology affordable. This provided a means for inexpensive mass communication previously impossible. In the 90's a different kind of freedom was launched by web technologies including HTML, JavaScript, and CSS. This grass-roots technology spread because not only were many of the tools inexpensive or free, but they came from a multitude of vendors. When a new, better tool was released, you could move your content into it easily and inexpensively. Needless to say, that also ensured a different kind of freedom, that is, authors could never be held hostage to one vendor. Vendor's now have to compete on the ease of use of their product, quality of their implementation, price, and integration with other solutions, such as photo-imaging, video editing, and so on. I would add that around the time HTML took off, people began to value extensibility as well. The notion that no language could do everything for everyone was gaining acceptance...metadata, namespaces, and the separation of content and presentation began to become important as people shared the frustration of mixing them in early implementations of HTML. 3. The best communication technology by any objective measure, doesn't necessarily win. Rather the ones that provide the widest access do. The article talks about Mayan and Egyptian languages, but we could also look at the infamous beta vs. VHS in our own times. It is widely understood that the betaMax format was objectively better, but because it didn't achieve wide acceptance fast enough, it was overtaken by the VHS format (which is now being overtaken by DVDs and DVRs, but that's another story.) Another factor to the success of any language is how it is used and by whom. If a language is constrained to a select group, that group has greater, if not total control over the evolution of the language. But here's where there are differences between SVG as a language and SVG as a technology. In language, one industry's jargon or vernacular is gibberish to the rest of the world. There is often more value to that industry in keeping the language as a jargon. It provides efficient communication through precision and keeps out those who aren't part of the "in-crowd". In contrast, a language that is primarily processed through technology, such as SVG which is most often not read by humans, but rendered by a user agent such as Adobe's ASV, Corel's SVG Viewer, or Batik. Here, the language specification is also precise and hopefully efficient. However, without significant distribution of compliant viewers, SVG content has little value to Internet users or content developers. Also, SVG viewers are non-trivial to build properly and any differences between viewers or between versions of viewers hurts SVG adoption. So SVG only has value if everyone has access to the specification and the specification is embraced widely and consistently. This is not unique to SVG of course, HTML still suffers from differences in HTML browser behavior. The only differences are that HTML has been around longer and so developers have learned workarounds for coding in the browsers they care about as defined by market share. Also, that has gotten easier, as only Internet Explorer 5.x+ for Windows has any significant market share so that's the de facto standard. But a de facto standard run by a single company is little different than the priests who "protected" the languages described in the article. "``There's discrimination against everyday use, so that while religion may help a script survive, it does not extend its reach,'' said University of Cambridge Xmovies Egyptologist John Baines, who collaborated with Houston and Assyriologist Jerrold Cooper of Johns Hopkins University. ``And when the people'' -- or conquerors -- ``begin to identify the religion and its script as something heretical or dangerous, there's nobody left to protect it.'' When languages are associated with a religion or regime that is no longer in vogue, they die a painful death. Try opening a WordStar file recently? How about Word 1.0? Do they look like they did when you had your CPM machine? When a single company dominates a market and has no need to extend a language beyond it's own immediate needs, languages cease to innovate and therefore don't serve us well either. Moreover, no company can be the best provider in every category of tools, for every field of endevor, forever. Therefore specialized areas like chemestry, manufacturing, engineering, etc. may be held back when their needs are not addressed, or they are addressed by niche technologies which make it difficult, expensive, or even impossible to share their information with people outside their professional cliques such as government regulatory agencies, the general public, and other "downstream" uses of the information they develop. However, when people from all walks of life experience contribute to a language, it becomes a rich, vibrant, enabler for broad communication between individuals, industries, and governments that is unhindered by language, technology, or location. I bet the authors of this liguistic study had no idea they knew so much about SVG.

I wish everyone on SVG.org Happy Easter and a hard working Easter bunny.

Great to read, that the new Safari Browser (version 3.1) has a better support for the web standards like HTML 5 and CSS 3. More important there is also a better handling regarding the svg graphics in img tags. So good news here. Back to work, Joe from Ferienwohnung Ostsee (the Baltic Sea, visit Ostsee Guide for more infos)

I fully agree with you

I see there are quite a few spam comments and also spam entries in the diary. This is to the administrators of Svg, if you need any help in moderation or anything of that sort - i would gladly help you guys out with what you need. Let me know if you guys need any cleaning up or something.. Thanks, - Rushh.