Skip to main content
added 110 characters in body
Source Link
Robert Longson
  • 122.3k
  • 26
  • 261
  • 249
  1. Firefox has never supported SVG fonts because they are not suitable for many of the world's scripts such as devanagari.

  2. IE has never supported SVG fonts because they don't have widespread browser support.

  3. Chrome dropped support for SVG fonts due to lack of use and the above two reasons.

  4. Opera moved from it'sits own rendering engine to using Chrome as aChrome's Blink rendering engine after version 12 thereby falling under rule 3.

  5. Vivaldi also uses Blink as a rendering engine

  6. Maxthon uses Safari/Webkit as a rendering engine.

No major browser does or will support SVG fonts and the SVG 2 specification has dropped them as a requirement. Other alternatives such as SVG glyphs in OpenType are being worked on.

You can embed the non-SVG font as a data URI to have it work in an image.

  1. Firefox has never supported SVG fonts because they are not suitable for many of the world's scripts such as devanagari.

  2. IE has never supported SVG fonts because they don't have widespread browser support.

  3. Chrome dropped support for SVG fonts due to lack of use and the above two reasons.

  4. Opera moved from it's own rendering engine to using Chrome as a rendering engine after version 12 thereby falling under rule 3.

No major browser does or will support SVG fonts and the SVG 2 specification has dropped them as a requirement. Other alternatives such as SVG glyphs in OpenType are being worked on.

You can embed the non-SVG font as a data URI to have it work in an image.

  1. Firefox has never supported SVG fonts because they are not suitable for many of the world's scripts such as devanagari.

  2. IE has never supported SVG fonts because they don't have widespread browser support.

  3. Chrome dropped support for SVG fonts due to lack of use and the above two reasons.

  4. Opera moved from its own rendering engine to using Chrome's Blink rendering engine after version 12 thereby falling under rule 3.

  5. Vivaldi also uses Blink as a rendering engine

  6. Maxthon uses Safari/Webkit as a rendering engine.

No major browser does or will support SVG fonts and the SVG 2 specification has dropped them as a requirement. Other alternatives such as SVG glyphs in OpenType are being worked on.

You can embed the non-SVG font as a data URI to have it work in an image.

added 103 characters in body
Source Link
Robert Longson
  • 122.3k
  • 26
  • 261
  • 249
  1. Firefox has never supported SVG fonts because they are not suitable for many of the world's scripts such as devanagari.

  2. IE has never supported SVG fonts because they don't have widespread browser support.

  3. Chrome dropped SVG fontsdropped support for SVG fonts due to lack of use and the above two reasons.

  4. Opera moved from it's own rendering engine to using Chrome as a rendering engine after version 12 thereby falling under rule 3.

No major browser does or will support SVG fonts and the SVG 2 specification has dropped them as a requirement. Other alternatives such as SVG glyphs in OpenType are being worked on.

You can embed the non-SVG font as a data URI to have it work in an image.

  1. Firefox has never supported SVG fonts because they are not suitable for many of the world's scripts such as devanagari.

  2. IE has never supported SVG fonts because they don't have widespread browser support.

  3. Chrome dropped SVG fonts due to lack of use and the above two reasons.

  4. Opera moved from it's own rendering engine to using Chrome as a rendering engine after version 12 thereby falling under rule 3.

No major browser does or will support SVG fonts and the SVG 2 specification has dropped them as a requirement. Other alternatives such as SVG glyphs in OpenType are being worked on.

You can embed the non-SVG font as a data URI to have it work in an image.

  1. Firefox has never supported SVG fonts because they are not suitable for many of the world's scripts such as devanagari.

  2. IE has never supported SVG fonts because they don't have widespread browser support.

  3. Chrome dropped support for SVG fonts due to lack of use and the above two reasons.

  4. Opera moved from it's own rendering engine to using Chrome as a rendering engine after version 12 thereby falling under rule 3.

No major browser does or will support SVG fonts and the SVG 2 specification has dropped them as a requirement. Other alternatives such as SVG glyphs in OpenType are being worked on.

You can embed the non-SVG font as a data URI to have it work in an image.

Source Link
Robert Longson
  • 122.3k
  • 26
  • 261
  • 249

  1. Firefox has never supported SVG fonts because they are not suitable for many of the world's scripts such as devanagari.

  2. IE has never supported SVG fonts because they don't have widespread browser support.

  3. Chrome dropped SVG fonts due to lack of use and the above two reasons.

  4. Opera moved from it's own rendering engine to using Chrome as a rendering engine after version 12 thereby falling under rule 3.

No major browser does or will support SVG fonts and the SVG 2 specification has dropped them as a requirement. Other alternatives such as SVG glyphs in OpenType are being worked on.

You can embed the non-SVG font as a data URI to have it work in an image.