Home → Problems →

CSS font problem under Sierra

• Edit

nihzondermana

Aug 15, 2017 @ 12:28 PM

Before Sierra, the CSS specification "font-family: "Times LT Std Roman","Times New Roman",serif; worked in a custom CSS file.

Under Sierra, this specification doesn't work, but this does: font-family: Times,Garamond;

Apparently there's a differences between quoting a multiple word font name and a font name with a single word?

1. Support Staff 1 Posted by Brett on Aug 15, 2017 @ 09:23 PM

   

   Quoting a multi-word font name should work fine. I think it's more
   likely that the fonts themselves might be missing. When you say "doesn't
   work", do you mean it's cascading down to the last items on the list
   (default serif) or that something else is going wrong?

   -Brett

   • Edit

2. 2 Posted by nihzondermana on Aug 16, 2017 @ 10:48 AM

   

   Thanks for your prompt reply.

   The fonts exist. I checked in the font app to be certain I was using the correct name.

   The CSS file is unchanged from previous versions of MacOS. It works under 10.11.x (and earlier), but not 10.12.

   The font may be cascading to serif. It appears to be something like Arial (otherwise not specified in the list).

   • Edit

3. Support Staff 3 Posted by Brett on Aug 23, 2017 @ 05:10 PM

   

   Would you be willing to attach a copy of the custom style you're using
   so I can test with it?

   Could you also try exporting to HTML, with the stylesheet included, and
   open it in a browser to see if the results look correct to you? If not,
   please attach a copy of the HTML file as well, so I can take a peek.

   -Brett

   • Edit

4. 4 Posted by nihzondermana on Aug 24, 2017 @ 12:49 AM

   

   Attached are the CSS file, a test markdown file, the html generated, a pdf of the html from my browser (Chrome), and a screen shot of what it looks like in Marked 2.

   Note that the browser got it right, but Marked 2 (under Sierra) doesn't. Marked 2 gets it right under MacOS <=10.11.

   • 2017-08-23-Test.pdf 51.8 KB
   • 2017-08-23-Test.png 444 KB
   • formatDoc.css 6.35 KB
   • 2017-08-23-Test.html 16.1 KB
   • 2017-08-23-Test.md 1.43 KB
   • Edit

5. 5 Posted by nihzondermana on Aug 24, 2017 @ 12:51 AM

   

   Sorry, the file says the pdf was generated in Pages, but it was generated by Chrome.

   > On 2017-08-23, at 20:49, Zonderman, Alan B <[email blocked]> wrote:
   >
   > Attached are the CSS file, a test markdown file, the html generated, a pdf of the html from my browser (Chrome), and a screen shot of what it looks like in Marked 2.
   >
   > Note that the browser got it right, but Marked 2 (under Sierra) doesn't. Marked 2 gets it right under MacOS <=10.11.
   >
   >> On 2017-08-23, at 13:10, Brett <[email blocked]> wrote:
   >>

   • Edit

6. Support Staff 6 Posted by Brett on Aug 24, 2017 @ 03:18 PM

   

   A quick reaction based on first glance, your font-family definitions have "normal" at the beginning of them. To the best of my knowledge this isn't a valid keyword, and removing it does change the font rendering in Chrome for me. Give that a shot.

   I don't have the font Utopia Std, so I can't verify that it would load, but putting another non-standard font before it renders fine after removing the "normal," so I don't see any issues with the cascading.

   • Edit

7. 7 Posted by nihzondermana on Aug 25, 2017 @ 11:30 AM

   

   You are correct. Removing the "normal" fixed the problem under Sierra. Not sure where it came from but it's gone now.

   Appreciate your help,

   • Edit

8. Support Staff 8 Posted by Brett on Aug 25, 2017 @ 12:07 PM

   

   Glad to hear it.

   • Edit