[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: SVG interoperability

• To: xml-dev@l...
• Subject: Re: SVG interoperability
• From: Eric van der Vlist <vdv@d...>
• Date: Mon, 19 Jun 2006 23:05:00 +0200
• In-reply-to: <4315F312-B7EC-4462-9BC6-B7665284CF88@e...>
• Organization: Dyomedea (http://dyomedea.com)
• References: <1150365359.19638.53.camel@l...> <F453CCBA-48F3-4801-8F60-C1CAB43830D1@e...> <1150703677.4501.42.camel@l...> <5076F73E-C0A4-47AC-BAF5-7E062E6474C5@e...> <4496AA2B.20402@a...> <4315F312-B7EC-4462-9BC6-B7665284CF88@e...>

Le lundi 19 juin 2006 à 15:51 +0200, Robin Berjon a écrit :
> On Jun 19, 2006, at 15:44, Mitch Amiano wrote:
> > Robin Berjon wrote:
> >> I haven't investigated but I think there may be a way of telling  
> >> Firefox to use a plugin no matter what.
> >
> > There is. See http://www.mozilla.org/projects/svg/faq.html#svg-plugin
> 
> Sorry, that's not what I meant. I know about the about:config SVG  
> enabling flag, it's nice for development and all. What I meant was a  
> way of forcing the triggering of the plugin through *content*, so  
> that you can know that anyone using FF1.5 will have to rely on an SVG  
> plugin rather than on the native support.

Or at least a way to detect whether a Firefox browser uses its native
SVG support or an Adobe SVG plugin.

Even that doesn't seem to be obvious. All the scripts I have found
(inclusing the Adobe "auto install script)) are testing if there is a
plugin to support SVG.

Unfortunately, this allows to check that:

     1. SVG is supported
     2. The Adobe plugin is installed

but not that the native support is disabled.

Access to the configuration options (both read and write) is reserved to
privileged scripts (which seems reasonable) and it doesn't seem that the
svg.enabled flag can be tested.

A hack could be to try to something that is supported only by the Adobe
plugin and check what's happening (maybe animate an invisible point
through smile and test if the the point has moved) but that would be
rather dangerous IMO. 

Eric
> 
-- 
GPG-PGP: 2A528005
Lisez-moi sur XMLfr.
                       http://xmlfr.org/index/person/eric+van+der+vlist/
------------------------------------------------------------------------
Eric van der Vlist       http://xmlfr.org            http://dyomedea.com
(ISO) RELAX NG   ISBN:0-596-00421-4 http://oreilly.com/catalog/relax
(W3C) XML Schema ISBN:0-596-00252-1 http://oreilly.com/catalog/xmlschema
------------------------------------------------------------------------

Ceci est une partie de message=?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=

• References:
  • SVG interoperability
    • From: Eric van der Vlist <vdv@d...>
  • Re: SVG interoperability
    • From: Robin Berjon <robin.berjon@e...>
  • Re: SVG interoperability
    • From: Eric van der Vlist <vdv@d...>
  • Re: SVG interoperability
    • From: Robin Berjon <robin.berjon@e...>
  • Re: SVG interoperability
    • From: Mitch Amiano <mitch.amiano@a...>
  • Re: SVG interoperability
    • From: Robin Berjon <robin.berjon@e...>

• Prev by Date: RE: Clustering Customization Vs Global Standards
• Previous by thread: Re: SVG interoperability
• Next by thread: Last weekend for XML 2006 submissions
• Index(es):
  • Date
  • Thread