edwardtufte / et-book Goto Github PK

The font is great but outside English text it's almost useless.

Maybe we can find time and resources to add support for Polish diacritics? It's not that much work:

ĄĆĘŁŃÓŚŹŻ

and

ąćęłńóśźż

I can pay to add those 18 symbols 🙂

Single Left-Pointing Angle Quotation Mark (U+2039, ‹) and Single Right-Pointing Angle Quotation Mark (U+204A, ›) result in ligatures ffi and ffl. This is quite strange, since these ligatures have their own codepoint in Unicode.

Can the following be supported:

• Latin script
  • Latin-1 Supplement
  • Latin Extended-A
  • Latin Extended-B
  • Latin Extended-C
  • Latin Extended-D
  • Latin Extended-E
  • Latin Extended Additional
• Phonetic scripts
  • IPA Extensions
  • Spacing modifier letters
  • Phonetic Extensions
  • Phonetic Extensions Supplement
  • Combining Marks
  • Shavian
• Greek and Coptic
  • Greek Extended
• Cyrillic
  • Cyrillic supplement
  • Cyrillic Extended-A
  • Cyrillic Extended-B
  • Cyrillic Extended-C
• Punctuation
  • General Punctuation
  • Supplemental Punctuation
• Superscripts and Subscripts
• Currency Symbols
• Letterlike Symbols
• Number Forms
• Arrows
  • Miscellaneous Symbols and Arrows
  • Supplemental Arrows-A
  • Supplemental Arrows-B
  • Supplemental Arrows-C
• Mathematical symbols
  • Mathematical Operators block
  • Supplemental Mathematical Operators
  • Miscellaneous Mathematical Symbols-A
  • Miscellaneous Mathematical Symbols-B
  • Mathematical Alphanumeric Symbols
• Miscellaneous Technical
• Optical Character Recognition
• Enclosed Alphanumerics
• Box Drawing
• Block Elements
• Geometric Shapes
  • Geometric Shapes
  • Geometric Shapes Extended
• Miscellaneous Symbols
• Symbols for Legacy Computin
• Dingbats
• Notational systems
  • Braille
  • Music
  • Shorthand
• Emoji
• Game symbols
  • Chess Symbols
  • Domino Tiles
  • Playing cards

I guess this will cover many of the use cases.

The lining figures and text figures versions of the font could be rolled into single font files containing both, using OpenType features to select between the two. (The features lnum and onum in particular.)

Likewise the small-capitals fonts (smcp and c2sc) and ‘expert set’ (mapped to the correct Unicode codepoints) included in the originals.zip file in the source directory can be merged into the main files of the typeface using the OpenType format.

Then, once the last few browsers support it, webfont users could enable these using the standard font-feature-settings CSS property.

What are in et-book-ligatures-enabled? What is the difference between the other fonts? Also there only 3 types opposed to 5 in the other directory. If this an enhanced version can the other font types be also added?

Also why all the fonts are not included in: et-book.css file?

How can the ligatures fonts be enabled in CSS?

The source files in the repo today are apparently PFB files, old PostScript Type1 binary fonts.

Is a .fog or .vfb file available (the native source file for Fontographer and Fontlab)

The GPL Font Exception is specifically designed for fonts, using this license will making your fonts freely under this license if anyone use your fonts under his/her purpose under GPL license.
This license can be used along with OFL, you can see what Aleksendr Andreev does anyway here.

Please use the SIL Open Font License.

The OFL is specifically designed for fonts, and the MIT license applied to a font will require the font's copyright notice and the MIT license to be included in all documents that embed the font.

If you do decide to go OFL, please include an OFL.txt file in the repo. Eg https://github.com/impallari/Libre-Bodoni/blob/master/OFL.txt

On windows and linux machines you get the following effect if you display the font at anything but the default size of 20px:

This makes most of the text sadly almost unreadable on windows and linux devices.

The capital "W" seems a bit odd to me. Having no knowledge of typography, I'd appreciate if anyone could explain what's happening here. Is this a design choice?

Thanks for the great work, I really appreciate that font, but I have problems with the capital "W" as it bumps away a following "e" so far.

I'm not too much into this business, but are there ways to save the kerning for several character pairs into the font-file directly? And does it depend on the format. (.ttf, otf, …) ?

Thanks in advance!

I'm wondering what the contributing guidelines for the project are.

I was working issue #3 and has success with implementing lining/old-school
OpenType feature, however, I'm not sure if what I did is acceptable
to the authors of the font.

It would be nice to know which files can be modified, how the font should
be built, what software is preferred (FontForge, Fontographer, etc...).

@dpk seems to have done some good work on his fork and added a bunch
of OpenType features and a makefile for building the WOFF version of the font
but his fork does not seem to have any guidelines either.

I'm excited to see the typeface used in Edward Tufte's books available
on the web as a free and open-source font but I think much can be
improved here so more people can contribute.

If more people contribute, the font will become more popular which
will draw more people to it which will in turn help improve the typography
on the web (a little bit, but still).

Examples
Fira Sans designed by Erik Spiekermann and released as an open-source
font by Mozilla has very clear contributing guidelines at https://docs.google.com/document/d/1QfxweGktJEdBvbd94y-5hiyqu32U9-h_ICPVs76Niyw

Source Sans Pro by Adobe is another example of a project with good
contribution guidelines.

Just checking but...you have sought legal advice about releasing a font named Bembo, I hope?

IANAL, but a quick search says that Bembo has been a registered trademark of Monotype in the US since 1985 for purposes of 'Typefaces, Typefonts, and Type Designs of Alphanumeric Characters and/or Typographical Symbols Recorded as Latent Images in Data Storage' and 1990 in the UK for similar. From the history on Wikipedia, it looks like Monotype chose the name of Bembo for their font in the 20s and no other font has ever had the name, so it's not a 'generic' like Garamond or Caslon.

Since Windows and Linux tend to render fonts thinner than Mac the font renders as too thin and is hard to read. You can see this in this screenshot (in addition to the 'w' issue I mentioned in #20):

what the web page shows now

What it actually is:

• Roman (lining figures)
• Roman (oldstyle figures)
• Semi-bold (oldstyle figures)
• Bold (lining figures)
• Display Italic (oldstyle figures)

This is an awesome font; thanks for making it available! I confess that I have not yet gone to the effort to set it up on my web site (but I might!). In the meantime, here are a couple of suggestions about making the font easier and less risky for people to use.

First, do I have to host this font myself or is it available on a CDN? I found what looks to be a version here: http://www.jsdelivr.com/projects/font-et-book. But I don't know if it is the same or not. I think it would make the font easier for people to use if it were available from a CDN and if the README gave explicit hand-holding instructions about how to use it, similarly to what Google Fonts provides.

Second, I have been burned in the past by fonts that look good on my development machine (OS X) but look bad on Windows. (I have heard this can be fixed with ttfautohint, but I have never actually experimented, and also that only works if self-hosting.) Assuming this font is properly hinted to look good on Windows, it would be great to say that in the README so people know.

Maybe that's stupid question, but is it somehow possible to add cyrillic support?