Font sets

When creating a new font set, in the Alternative Fonts pane, should there be a comma separating the fonts with no space? This is how Freeway has done it.

Also, why do some fonts have single quote marks around them? For example, copied from Freeway:

Times,‘Times New Roman’,serif

I’m creating a new font set for Lucida Grande, with alternative fonts: “Lucida Sans Unicode”, Arial, Verdana, sans-serif

These are the alternatives Apple give on their website. Good enough for them good enough for me! But Apple use double quote marks!

Thanks


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

The quote marks are there for font names that have whitespace inside
their names, as it makes it less ambiguous. You can drop them, and
some browsers will figure it out, but it’s not good form. You can also
quote everything if you like, this doesn’t harm anything either. There
should be a comma between names.

Example with single-word font names:

font-family: Arial, Geneva, sans-serif;

Example with mixed font names:

font-family: 'Adobe Garamond', Garamond, 'Times New Roman', serif;

Walter

On Jun 2, 2009, at 11:39 AM, Mark wrote:

When creating a new font set, in the Alternative Fonts pane, should
there be a comma separating the fonts with no space? This is how
Freeway has done it.

Also, why do some fonts have single quote marks around them? For
example, copied from Freeway:

Times,‘Times New Roman’,serif

I’m creating a new font set for Lucida Grande, with alternative
fonts: “Lucida Sans Unicode”, Arial, Verdana, sans-serif

These are the alternatives Apple give on their website. Good enough
for them good enough for me! But Apple use double quote marks!

Thanks


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Hi

Freeway uses single quote marks, Apple uses double quote marks in their CSS. Is there a preference?

Also, Freeway doesn’t put a space between the fonts. Apple does. Is there a preference?

Thanks Walter

Mark


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

I don’t believe it matters at all. Freeway does a lot of things to
optimize code. For example, in HTML levels that don’t require the
quote marks around attribute values, it leaves them off to save a byte
or two. Whitespace is a human requirement for comprehension, machines
don’t always need it.

Walter

On Jun 2, 2009, at 12:02 PM, Mark wrote:

Hi

Freeway uses single quote marks, Apple uses double quote marks in
their CSS. Is there a preference?


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Thanks for that!

Mark


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Additional question: when I define (with no open pages) font sets, how can I use these “basic font sets” in old pages? They do not take it over.


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options

Found it: To add font stacks that will be used across all new documents (old documents won’t pick these up but you can add them to the document in the same way).


freewaytalk mailing list
email@hidden
Update your subscriptions at:
http://freewaytalk.net/person/options