Databases
StackOverflow2013
Postsdbo
POMake Adobe fonts work with CSS3 @font-face in IE9
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMake Adobe fonts work with CSS3 @font-face in IE9
    primarykey
    data
    text
    <p>I'm in the process of building a small intranet application and try, with no luck, to use <strong>Adobe font</strong> I purchased lately. As I was informed, in our case it's not a license violation.</p> <p><strong>I converted the .ttf/.otf versions of font to .woff, .eot and .svg, so to target all major browsers.</strong> The @font-face syntax I used is basically the bulletproof one from <a href="http://www.fontspring.com/blog/the-new-bulletproof-font-face-syntax" rel="noreferrer">Font Spring</a>:</p> <pre><code>@font-face { font-family: 'MyFontFamily'; src: url('myfont-webfont.eot'); src: url('myfont-webfont.eot?#iehack') format('eot'), url('myfont-webfont.woff') format('woff'), url('myfont-webfont.ttf') format('truetype'), url('myfont-webfont.svg#svgFontName') format('svg'); } </code></pre> <p>I modified the HTTP headers (added Access-Control-Allow-Origin = "*") to allow cross-domain references. <strong>In FF and Chrome it works perfectly, but in IE9 I get:</strong></p> <pre><code>CSS3111: @font-face encountered unknown error. myfont-webfont.woff CSS3114: @font-face failed OpenType embedding permission check. Permission must be Installable. myfont-webfont.ttf </code></pre> <p>I noticed that when converting font from .ttf/.otf to .woff I also get an <strong>.afm</strong> file, but I don't have a clue whether it's important or not...</p> <p>Any ideas how to work it out?</p> <p>[Edit] - I host my websites (fonts too, but under separate directory and subdomain for static content) under <strong>IIS 7.5</strong></p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USPiotr Szmyd
    1. USPiotr Szmyd
    plurals
    1. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMake Adobe fonts work with CSS3 @font-face in IE9
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POMake Adobe fonts work with CSS3 @font-face in IE9
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POMake Adobe fonts work with CSS3 @font-face in IE9
      1. USRup
      1. VTFavorite
    1. CO+1 for a fine, intelligent, well worded question with all the homework done. We get these much too rarely these days!
      singulars
      1. POMake Adobe fonts work with CSS3 @font-face in IE9
      1. USPekka 웃
    2. COIndeed it is a well put question, but sadly, a duplicate.
      singulars
      1. POMake Adobe fonts work with CSS3 @font-face in IE9
      1. USJoseph Earl
    3. CONo, it's surely not a duplicate, as in non-Adobe fonts the solutions I found work perfectly. What differs is that it is not the case with cross-domain font referencing I guess - I get "@font-face encountered unknown error" with .woff font as opposed to "@font-face failed cross-origin request" in other mentioned cases.
      singulars
      1. POMake Adobe fonts work with CSS3 @font-face in IE9
      1. USPiotr Szmyd
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload