[Pro] line spacing in html type

… and apologize that I rush in here, too. Everything is said and pointed out, so sending you to this isn’t necessary (even redundant), but perhaps of fun:

http://www.kimmich-digitalmedia.com/videos/015_the-coding-episodes-part8-google-webfonts

Especially Tim’s points are mentioned there as well (as far as I remember).

Cheers

Thomas


freewaytalk mailing list
email@hidden
Update your subscriptions at:

Tim, thank you. The code was there, just as you said. I had looked at the semicolon there and wondered, but wasn’t sure if that was the place to delete it.

And Thomas, thank you. I had actually watched a couple of your videos before, but not that one, which obviously was the one I needed.

I put the code there because I followed the instructions here, where they say to include the semicolon, so it is a bit confusing…

Anyway I’ll get on and delete it now. Could this be why when I tried to use the italic weight of Merriweather (400 italic) it didn’t work? I ended up just using the em style to force the italic where I wanted it.

Once again thanks everyone, I really appreciate your kind help.

Kate


freewaytalk mailing list
email@hidden
Update your subscriptions at:

Thanks for the clarification Kate.

Unfortunately that knowledge base article is incorrect and the attached sample file is also broken;

If you want to add the font-weight to the end of the font set entry (as Softpress suggest) then make sure that there is no semi-colon at the end of the line;
‘Open Sans’, Helvetica, sans-serif; font-weight:300

Keeping the semi-colon will (as Caleb pointed out) invalidate the code and the browser will almost certainly display the incorrect font weight for the style.

If you download the example Freeway file and look at the font sets for Open Sans you’ll see the following entry (here for the light version);
‘Open Sans’, Helvetica; sans-serif; font-weight:300;

That semi-colon after Helvetica should be a comma;
‘Open Sans’, Helvetica, sans-serif; font-weight:300;

The only other thing that seems bizarre about that article is that it suggests making the screen font for each Open Sans style Helvetica and then goes on to say that you’ll need to preview the page to see the correct fonts in their correct font weights. Personally I’d always advocate downloading the fonts from Google and installing them on your Mac. This does require Freeway to be restarted but you can at least define the exact screen font for the font set and see the text correctly styled within Freeway.

—Side note—

Personally I try and keep font weights out of the font sets dialog and set them up in the individual styles themselves. This will cut the amount of code Freeway creates for each font variant as it doesn’t need to redefine the fonts for each style but does mean that the various weights will all show up as the same screen font in the application.

—Side note—

Regards,
Tim.

On 14 Oct 2015, at 10:00, Kate Slotover email@hidden wrote:

I put the code there because I followed the instructions here, where they say to include the semicolon, so it is a bit confusing…


Experienced Freeway designer for hire - http://www.freewayactions.com


freewaytalk mailing list
email@hidden
Update your subscriptions at:
https://freewaytalk.softpress.com/person/options

Personally I’d always advocate downloading the fonts from Google and installing them on your Mac.

I am from the other camp - if you have the font on your Mac then you will always see the correct font no matter whether you have input the style code correctly or not.

Leave the screen font in FW as a default (Helvetica in this case) then you will know for sure that it works when it displays in your correct font.

David


freewaytalk mailing list
email@hidden
Update your subscriptions at:
https://freewaytalk.softpress.com/person/options

Thanks Tim. I think I understand.
When you say

That semi-colon after Helvetica should be a comma; ‘Open Sans’, Helvetica, sans-serif; font-weight:300;

you would take the semi-colon out there, too, right? At the end? If it’s in the font set entry…

By the way, I was wondering how you upload a screengrab here – it’s a useful trick.


freewaytalk mailing list
email@hidden
Update your subscriptions at:

Hi Kate,
Yes. Apologies for not emphasising that. I was concentrating on the comma issue.

To share an image on the FreewayTalk web site (it will show up as a link in emails) you’ll have to put the image somewhere on a public server (I tend to use DropBox)

For example this screen shot;
![Font set corrections](https://dl.dropboxusercontent.com/u/795566/screenshots/font-sets.jpg https://dl.dropboxusercontent.com/u/795566/screenshots/font-sets.jpg)

was created with this code;

![Font set corrections](https://dl.dropboxusercontent.com/u/795566/screenshots/font-sets.jpg <https://dl.dropboxusercontent.com/u/795566/screenshots/font-sets.jpg>)

Regards,
Tim.

On 15 Oct 2015, at 10:32, Kate Slotover email@hidden wrote:

Thanks Tim. I think I understand.
When you say

That semi-colon after Helvetica should be a comma; ‘Open Sans’, Helvetica, sans-serif; font-weight:300;

you would take the semi-colon out there, too, right? At the end? If it’s in the font set entry…

By the way, I was wondering how you upload a screengrab here – it’s a useful trick.


Experienced Freeway designer for hire - http://www.freewayactions.com


freewaytalk mailing list
email@hidden
Update your subscriptions at:
https://freewaytalk.softpress.com/person/options

OK let me try that again from the web site rather than from an email…

Ahh, that’s better.


freewaytalk mailing list
email@hidden
Update your subscriptions at: