Domenico:
I feel your pain. It is very frustrating to try working with multiple
SVG rendering engines when you all you want to do is get your work
published to as many people as possible.
My hobby is film-making, and I face the same problem; the first thing I
have to do when I take on a new project is decide who my audience is,
and choose a capture medium which will show my work best with that
audience. Unfortunately, this means one compromise after another.
The SVG browser situation right now is the same way. I'm trying to
solve a real-world issue with SVG and frankly it is a more difficult
problem than it should be. It really doesn't help me that FF's SVG
render engine differs significantly from ASV3!
However, I'm still greatful that a production version of one of the
major browsers finally supports SVG (even in part) natively. This can
only serve to encourage the adoption of this wonderful open format.
(Yes, I know Opera, Safari, and Konquerer support SVG in their own
fashion, but my personal definition of 'major browser' includes only IE
and Firefox/Mozilla at this point.)
I'm fairly new to SVG, and it seems like aliens came from another galaxy
in 2004 and abducted all the SVG developers in the world, but it now
appears they've returned and are back to it. Hurrah! A year from now,
the SVG community will have worked out most of the issues, and it will
be more of the same history that we'll not learn from the next time a
new technology arrives! ;)
domenico_strazzullo wrote:
> Hi,
>
> I have a few remarks,
>
> var fnt_size = parseInt(txttoformat.getAttributeNS(null,"font-
> size"));
> vs
> var fnt_size = parseInt(txttoformat.getAttribute("font-size"));
>
> These both work in Ffx 1.5. I read that
>
> > As pointed out several times already, Mozilla SVG and Batik are
> > stricter regarding invalid SVG elements, missing namespaces,
> > mimetypes
>
> Am I missing something? Or someone else is?
>
> On another note, I am very concerned about the release of the svg
> implementation under it actual state. The implementors seem to worry
> a lot about the validity of the works and not so much about the
> validity of the renderer.
>
> I would forward a motion for the removal of the automatic rendering
> ('lax' mode) for the greater public until the implementation is
> complete, not just "satisfactory". That is so subjective! The build
> is 1.5, but not in respect to the svg implementation. Only when the
> implementation reaches maturity (1.0) should it be transparently
> integrated.
>
[snip]
--
Darryl Watson
Senior Software Developer
*Roof Express, LLC*
8310 South Valley Highway
Suite 300
Englewood, CO 80112
303.524.1193 (direct)
303.524.1101 (fax)
www.roof-express.com/ <http://www.roof-express.com/>
------------------------ Yahoo! Groups Sponsor --------------------~-->
Get Bzzzy! (real tools to help you find a job). Welcome to the Sweet Life.
http://us.click.yahoo.com/KIlPFB/vlQLAA/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/
