doc: clarify portability

main
Matthew Butterick 4 years ago
parent d80001b882
commit 96f86fec91

@ -839,7 +839,11 @@ Fallback only. Used for other glyphs not present in the currently selected font.
@subsubsection{System fonts}
Yes, if you're feeling lazy, you can use the name of a system font family in any field that takes a family name, and Quad will comply. But if you do this, bear in mind that your document will no longer necessarily be portable between systems, because it depends on a certain font already being available on that system. I include this option because I can imagine plenty of uses for Quad where ease outweighs portability. In which case, have at it.
Yes, if you're feeling lazy, you can use the name of a built-in system font family in any field that takes a family name, and Quad will comply.
If you do this, bear in mind that your source file will no longer necessarily be portable between systems, because it depends on a certain font already being available on that system. ("Portable" referring to one's ability to run the source file on a different machine and get an equivalent result.) I include this option because I can imagine plenty of uses for Quad where ease outweighs portability. In which case, have at it.
When I say "portable" I mean the source file only. Once you generate a PDF from the source file, the PDF itself will always be portable. Regardless of whether you invoke a system font or project font in your source file, the font will be embedded within the PDF. The PDF will then display correctly on any platform, with the correct fonts.
@subsection{Colors}

Loading…
Cancel
Save