Hi Andreas, I accept your mediation, you are so gentle. Also other friends off list. I still maintain though that the release of an incomplete implementation is against the DVA and CA industries deontology. You cite open source projects, when Open Office 1.0 was released it could open and save .doc format flawlessly, for example. Can you imagine the drama if it would mess up just, say, the display of a document?
In response to Jonathan's, and others', arguments I am obliged to remind that the question I raised is not how easy or difficult it is to implement. It is not about the quality of the team's work and dedication. The question is about the timing in the decision to make the product available to the greater public. It's a sign of lack of patience that will pay off negatively. If the 70% figure of rendering success has been realistically set by yourself then I don't dispute it, but I randomly visited about 15 of the svg links in my bookmarks and got 0% positive results. >From Jonathan's answer I understand DOM 2 is complete, but then I also deduce that the SVG DOM subset is not complete: getNumberOfChars () method doesn't work. My text formatter, which is not artwork, works beautifully, all the window functionalities, displacement etc. Beautiful. But there's no text in it! Of course I could count the number of chars in the dummy line myself and skip getNumberOfChars (), but I won't do it. A big difference between ASV 1 and 2 and FFsvg is that ASV simply allowed the kick off, I don't think there were any works prior to that, or were there? The scenario is totally opposite for FF, it claims to be able to render SVG but then it doesn't quite make it. Plus, the official tada launch is pre spoiled by the same token. Also, remember that Adobe would not release ASV6 until the 1.2 draft would become a spec. Michel Hirtzler recently said a very wise thing, referring to SVG WG: "Why do they worry about 1.2? Why not get things together for 1.1 first?". Of course in this type of society the trend to not listen to older, wiser people, is ever galloping. Always the same story over and over again for the web. This type of thing makes the web suck, not rock. It's hysterical. What Martyn Eggleton says was true prior to 1.5, and this type of discussion didn't need to exist then. Andre Winter and Jean-David Benamou reported advertisement. ------------------------------------ Jonathan, In my letter I can read: "artists and programmers" "artists and technicians" Can you? You say you (the Mozilla team) poled the community. I've been away from the list for a few months, as other developers have. Wouldn't have it been more appropriate to make some individual contact, like you did when you suggested auditing, and seek personal advice like "Hi xyz, the implementation is in advanced state, but this and that is still missing, do you think it would be blah blah?". The majority replied "yes". Did you take into consideration eventually what the minority said? Did you think it was appropriate to sort by number instead of by experience level? I'm not sure that you quite got the measure of how much artists, programmers and developers are concerned. The work that they have ALREADY done is affected, valid or not valid. This is not a personal attack against you or the Mozilla team, I simply know that unfortunately we often take decisions more in respect to schedules than anything else... > I am, of course, very sorry that you find that the SVG support is not up > to your needs. You sound like an AT&T public relation agent. I can do without this type of remark. I raised an issue that I see as a problem, and a solution that I think would be beneficial for the community, including Mozilla. > Those sound like rather nasty problems. Bug reports with testcases would > be helpful. Are you serious??? I'm a human, can you please talk in a way other than binary logic? I mean... SMIL is missing in the implementation and you ask for bug report? What would be the point? You call them nasty problems, that is what they are, not bugs. I don't see how switching svg off by default like prior to 1.5, would affect FF navigation. Did you raise the issue at all with the Mozilla Foundation before stating that it's "very unlikely that the Mozilla Foundation would take sucha drastic step"? But anyway, let's forget, who cares... I already said to Andreas I was accepting his mediation. Let's have it the Mozilla way. Let's have performances where instruments are untuned, galleries with gelatin filters on their spots, pottery made of undercooked clay, plays without actors, svg bar charts without bars, books with blank pages, let's hurry up, the Mozilla way. Domenico --- In [email protected], "Andreas Neumann" <[EMAIL PROTECTED]> wrote: > > Richard, > > also, if you use a lot of SMIL in your examples, you have to be aware that Mozilla SVG does > not yet support SMIL. > > Andreas > > --- In [email protected], T Rowley <[EMAIL PROTECTED]> wrote: > > > > On 12/1/05 3:07 PM, Richard Pearman wrote: > > > Firefox doesn't correctly display any of the SVG's on my site, including > > > ones I'm pretty sure have the Kosha namespace declarations etc. Also, as > > > far as I can tell, the server uses the correct mime type for SVGZ. Can > > > anyone please tell me what the problem is? > > > > Your server isn't sending the Content-Encoding header for svgz files: > > > > http://jwatt.org/svg/authoring/#server-configuration > > > > -tor > > > ------------------------ Yahoo! Groups Sponsor --------------------~--> Most low income households are not online. Help bridge the digital divide today! http://us.click.yahoo.com/I258zB/QnQLAA/TtwFAA/1U_rlB/TM --------------------------------------------------------------------~-> ----- To unsubscribe send a message to: [EMAIL PROTECTED] -or- visit http://groups.yahoo.com/group/svg-developers and click "edit my membership" ---- Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/svg-developers/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
