Open davelab6 opened 3 years ago
davelab6
commented
3 years ago The copyright notice is
Copyright (c) 2004-2015, Society for Classical Studies (formerly American Philological Association) (http://apaclassics.org, apaclassics@sas.upenn.edu), with Reserved Font Name <New Athena Unicode>.
So next step is to persuade them to drop the RFN :)
thlinard
commented
3 years ago Athena Gothic or New Athena Unicode?
New Athena Unicode offers Coptic support, but also Polytonic Greek, papyrological, epigraphical and metrical signs, Demotic Egyptian and Arabic transliteration, ancient Greek numbers, symbols for critical apparatus, Ancient Greek musical notation… In this field, simply one of the most complete open-source font around: http://www.tlg.uci.edu/help/UnicodeTest.php (there are some excellent, probably better, free fonts for non-commercial use, but not open-source).
pishoyg
commented
3 years ago Athena Gothic or New Athena Unicode?
I believe the intention is the "New Athena Unicode Font".
davelab6
commented
3 years ago Athena Gothic or New Athena Unicode?
What's the difference?
davelab6
commented
3 years ago Oh. I don't see AG anywhere. Not sure where I got the impressoin that was the font name, haha
emmamarichal
commented
2 years ago Most of the FAILS could be hotfixed if needed. Sources are not available.
Fontbakery version: 0.8.2
--- Rationale --- Use of some unacceptable control characters in the U+0000 - U+001F range can lead to rendering issues on some platforms. Acceptable control characters are defined as .null (U+0000) and CR (U+000D) for this test.* 🔥 **FAIL** The following unacceptable control characters were identified: /Users/marichalemma/Google/NAU5_008/NewAthenaUnicode-Regular.ttf: uni000A [code: unacceptable]
--- Rationale --- Google Fonts expects that fonts in its collection support at least the minimal set of characters defined in the `GF-latin-core` glyph-set.* 🔥 **FAIL** Missing required codepoints: 0x2074 (SUPERSCRIPT FOUR) and 0x2215 (DIVISION SLASH) [code: missing-codepoints]
--- Rationale --- Requirements for the FULL_FONT_NAME entries in the 'name' table.* 🔥 **FAIL** [FULL_FONT_NAME(4):MACINTOSH(1)] Expected: "New Athena Unicode Regular" But got: "NewAthenaUnicode" [code: bad-entry] * 🔥 **FAIL** [FULL_FONT_NAME(4):WINDOWS(3)] Expected: "New Athena Unicode Regular" But got: "NewAthenaUnicode" [code: bad-entry]
--- Rationale --- Requirements for the POSTSCRIPT_NAME entries in the 'name' table.* 🔥 **FAIL** [POSTSCRIPT_NAME(6):MACINTOSH(1)] Expected: "NewAthenaUnicode-Regular" But got: "NewAthenaUnicode" [code: bad-entry] * 🔥 **FAIL** [POSTSCRIPT_NAME(6):WINDOWS(3)] Expected: "NewAthenaUnicode-Regular" But got: "NewAthenaUnicode" [code: bad-entry]
--- Rationale ---
This setup is meant to ensure consistent rendering quality for fonts across all
devices (with different rendering/hinting capabilities).
Below is the snippet of instructions we expect to see in the fonts:
B8 01 FF PUSHW 0x01FF
85 SCANCTRL (unconditinally turn on
dropout control mode)
B0 04 PUSHB 0x04
8D SCANTYPE (enable smart dropout control)
"Smart dropout control" means activating rules 1, 2 and 5:
Rule 1: If a pixel's center falls within the glyph outline,
that pixel is turned on.
Rule 2: If a contour falls exactly on a pixel's center,
that pixel is turned on.
Rule 5: If a scan line between two adjacent pixel centers
(either vertical or horizontal) is intersected
by both an on-Transition contour and an off-Transition
contour and neither of the pixels was already turned on
by rules 1 and 2, turn on the pixel which is closer to
the midpoint between the on-Transition contour and
off-Transition contour. This is "Smart" dropout control.
For more detailed info (such as other rules not enabled in this snippet), please
refer to the TrueType Instruction Set documentation.
* 🔥 **FAIL** The 'prep' table does not contain TrueType instructions enabling smart dropout control. To fix, export the font with autohinting enabled, or run ttfautohint on the font, or run the `gftools fix-nonhinting` script. [code: lacks-smart-dropout]
--- Rationale --- A font's winAscent and winDescent values should be greater than the head table's yMax, abs(yMin) values. If they are less than these values, clipping can occur on Windows platforms (https://github.com/RedHatBrand/Overpass/issues/33). If the font includes tall/deep writing systems such as Arabic or Devanagari, the winAscent and winDescent can be greater than the yMax and abs(yMin) to accommodate vowel marks. When the win Metrics are significantly greater than the upm, the linespacing can appear too loose. To counteract this, enabling the OS/2 fsSelection bit 7 (Use_Typo_Metrics), will force Windows to use the OS/2 typo values instead. This means the font developer can control the linespacing with the typo values, whilst avoiding clipping by setting the win values to values greater than the yMax and abs(yMin).* 🔥 **FAIL** OS/2.usWinAscent value should be equal or greater than 1001, but got 900 instead [code: ascent] * 🔥 **FAIL** OS/2.usWinDescent value should be equal or greater than 395, but got 309 instead. [code: descent]
--- Rationale --- Microsoft keeps a list of font vendors and their respective contact info. This list is updated regularly and is indexed by a 4-char "Vendor ID" which is stored in the achVendID field of the OS/2 table. Registering your ID is not mandatory, but it is a good practice since some applications may display the type designer / type foundry contact info on some dialog and also because that info will be visible on Microsoft's website: https://docs.microsoft.com/en-us/typography/vendors/ This check verifies whether or not a given font's vendor ID is registered in that list or if it has some of the default values used by the most common font editors. Each new FontBakery release includes a cached copy of that list of vendor IDs. If you registered recently, you're safe to ignore warnings emitted by this check, since your ID will soon be included in one of our upcoming releases.* ⚠ **WARN** OS/2 VendorID value 'SWAP' is not yet recognized. If you registered it recently, then it's safe to ignore this warning message. Otherwise, you should set it to your own unique 4 character code, and register it with Microsoft at https://www.microsoft.com/typography/links/vendorlist.aspx [code: unknown]
--- Rationale --- A known license URL must be provided in the NameID 14 (LICENSE INFO URL) entry of the name table. The source of truth for this check is the licensing text found on the NameID 13 entry (LICENSE DESCRIPTION). The string snippets used for detecting licensing terms are: - "This Font Software is licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: https://scripts.sil.org/OFL" - "Licensed under the Apache License, Version 2.0" - "Licensed under the Ubuntu Font Licence 1.0." Currently accepted licenses are Apache or Open Font License. For a small set of legacy families the Ubuntu Font License may be acceptable as well. When in doubt, please choose OFL for new font projects.* ⚠ **WARN** Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description] * ⚠ **WARN** Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description] * ⚠ **WARN** Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description] * ⚠ **WARN** Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description] * ⚠ **WARN** Please consider using HTTPS URLs at name table entry [plat=1, enc=0, name=13] [code: http-in-description] * ⚠ **WARN** Please consider using HTTPS URLs at name table entry [plat=3, enc=1, name=13] [code: http-in-description]
--- Rationale --- An old FontLab version had a bug which caused it to store copyright notices in nameID 10 entries. In order to detect those and distinguish them from actual legitimate usage of this name table entry, we expect that such strings do not exceed a reasonable length of 200 chars. Longer strings are likely instances of the FontLab bug.* ⚠ **WARN** A few name table entries with ID=10 (NameID.DESCRIPTION) are longer than 200 characters. Please check whether those entries are copyright notices mistakenly stored in the description string entries by a bug in an old FontLab version. If that's the case, then such copyright notices must be removed from these entries. [code: too-long]
--- Rationale --- Visually QAing thousands of glyphs by hand is tiring. Most glyphs can only be constructured in a handful of ways. This means a glyph's contour count will only differ slightly amongst different fonts, e.g a 'g' could either be 2 or 3 contours, depending on whether its double story or single story. However, a quotedbl should have 2 contours, unless the font belongs to a display family. This check currently does not cover variable fonts because there's plenty of alternative ways of constructing glyphs with multiple outlines for each feature in a VarFont. The expected contour count data for this check is currently optimized for the typical construction of glyphs in static fonts.* ⚠ **WARN** This check inspects the glyph outlines and detects the total number of contours in each of them. The expected values are infered from the typical ammounts of contours observed in a large collection of reference font families. The divergences listed below may simply indicate a significantly different design on some of your glyphs. On the other hand, some of these may flag actual bugs in the font such as glyphs mapped to an incorrect codepoint. Please consider reviewing the design and codepoint assignment of these to make sure they are correct. The following glyphs do not have the recommended number of contours: Glyph name: numbersign Contours detected: 3 Expected: 2 Glyph name: uni1EC8 Contours detected: 4 Expected: 2 Glyph name: uni1EC9 Contours detected: 4 Expected: 2 Glyph name: uni204B Contours detected: 1 Expected: 2 Glyph name: circleplus Contours detected: 5 Expected: 3 Glyph name: uni25CC Contours detected: 18 Expected: 16 or 12 Glyph name: uni2E18 Contours detected: 3 Expected: 2 Glyph name: circleplus Contours detected: 5 Expected: 3 Glyph name: fi Contours detected: 1 Expected: 3 Glyph name: fl Contours detected: 1 Expected: 2 Glyph name: numbersign Contours detected: 3 Expected: 2 Glyph name: uni1EC8 Contours detected: 4 Expected: 2 Glyph name: uni1EC9 Contours detected: 4 Expected: 2 Glyph name: uni204B Contours detected: 1 Expected: 2 Glyph name: uni25CC Contours detected: 18 Expected: 16 or 12 Glyph name: uni2E18 Contours detected: 3 Expected: 2 [code: contour-count]
--- Rationale --- All ligatures in a font must have corresponding caret (text cursor) positions defined in the GDEF table, otherwhise, users may experience issues with caret rendering. If using GlyphsApp or UFOs, ligature carets can be defined as anchors with names starting with 'caret_'. These can be compiled with fontmake as of version v2.4.0.* ⚠ **WARN** This font lacks caret position values for ligature glyphs on its GDEF table. [code: lacks-caret-pos]
--- Rationale --- Fonts with ligatures should have kerning on the corresponding non-ligated sequences for text where ligatures aren't used (eg https://github.com/impallari/Raleway/issues/14).* ⚠ **WARN** GPOS table lacks kerning info for the following non-ligated sequences: - f + i - i + l [code: lacks-kern-info]
--- Rationale --- The OpenType 'meta' table originated at Apple. Microsoft added it to OT with just two DataMap records: - dlng: comma-separated ScriptLangTags that indicate which scripts, or languages and scripts, with possible variants, the font is designed for - slng: comma-separated ScriptLangTags that indicate which scripts, or languages and scripts, with possible variants, the font supports The slng structure is intended to describe which languages and scripts the font overall supports. For example, a Traditional Chinese font that also contains Latin characters, can indicate Hant,Latn, showing that it supports Hant, the Traditional Chinese variant of the Hani script, and it also supports the Latn script The dlng structure is far more interesting. A font may contain various glyphs, but only a particular subset of the glyphs may be truly "leading" in the design, while other glyphs may have been included for technical reasons. Such a Traditional Chinese font could only list Hant there, showing that it’s designed for Traditional Chinese, but the font would omit Latn, because the developers don’t think the font is really recommended for purely Latin-script use. The tags used in the structures can comprise just script, or also language and script. For example, if a font has Bulgarian Cyrillic alternates in the locl feature for the cyrl BGR OT languagesystem, it could also indicate in dlng explicitly that it supports bul-Cyrl. (Note that the scripts and languages in meta use the ISO language and script codes, not the OpenType ones). This check ensures that the font has the meta table containing the slng and dlng structures. All families in the Google Fonts collection should contain the 'meta' table. Windows 10 already uses it when deciding on which fonts to fall back to. The Google Fonts API and also other environments could use the data for smarter filtering. Most importantly, those entries should be added to the Noto fonts. In the font making process, some environments store this data in external files already. But the meta table provides a convenient way to store this inside the font file, so some tools may add the data, and unrelated tools may read this data. This makes the solution much more portable and universal.* ⚠ **WARN** This font file does not have a 'meta' table. [code: lacks-meta-table]
--- Rationale --- Microsoft's recommendations for OpenType Fonts states the following: 'NOTE: The PostScript glyph name must be no longer than 31 characters, include only uppercase or lowercase English letters, European digits, the period or the underscore, i.e. from the set [A-Za-z0-9_.] and should start with a letter, except the special glyph name ".notdef" which starts with a period.' https://docs.microsoft.com/en-us/typography/opentype/spec/recom#post-table In practice, though, particularly in modern environments, glyph names can be as long as 63 characters. According to the "Adobe Glyph List Specification" available at: https://github.com/adobe-type-tools/agl-specification* ⚠ **WARN** The following glyph names may be too long for some legacy systems which may expect a maximum 31-char length limit: uni03D9_uni0308_uni0313_gravecomb, uni03D9_uni0308_uni0313_acutecomb, uni03D9_uni0308_uni0314_gravecomb and uni03D9_uni0308_uni0314_acutecomb [code: legacy-long-names]
--- Rationale --- Microsoft Office 2013 and below products expect fonts to have a digital signature declared in a DSIG table in order to implement OpenType features. The EOL date for Microsoft Office 2013 products is 4/11/2023. This issue does not impact Microsoft Office 2016 and above products. As we approach the EOL date, it is now considered better to completely remove the table. But if you still want your font to support OpenType features on Office 2013, then you may find it handy to add a fake signature on a dummy DSIG table by running one of the helper scripts provided at https://github.com/googlefonts/gftools Reference: https://github.com/googlefonts/fontbakery/issues/1845* ⚠ **WARN** This font has a digital signature (DSIG table) which is only required - even if only a dummy placeholder - on old programs like MS Office 2013 in order to work properly. The current recommendation is to completely remove the DSIG table. [code: found-DSIG]
--- Rationale --- Glyphs in the GDEF mark glyph class should be non-spacing. Spacing glyphs in the GDEF mark glyph class may have incorrect anchor positioning that was only intended for building composite glyphs during design.* ⚠ **WARN** The following spacing glyphs may be in the GDEF mark glyph class by mistake: uni0359 (U+0359), uni2CEF (U+2CEF) and uniFE25 (U+FE25) [code: spacing-mark-glyphs]
--- Rationale --- This check heuristically detects outline segments which form a particularly small angle, indicative of an outline error. This may cause false positives in cases such as extreme ink traps, so should be regarded as advisory and backed up by manual inspection.* ⚠ **WARN** The following glyphs have jaggy segments: * Omegatonos (U+038F): B<<666.0,90.0>-<728.0,62.0>-<779.0,61.0>>/L<<779.0,61.0>--<772.0,61.0>> = 1.1233027140753125 * Omegatonos (U+038F): L<<779.0,61.0>--<772.0,61.0>>/B<<772.0,61.0>-<820.0,68.0>-<837.0,79.0>> = 8.297144969836856 * beta (U+03B2): B<<213.0,22.0>-<154.0,47.0>-<132.0,49.0>>/B<<132.0,49.0>-<134.0,49.0>-<132.0,48.0>> = 5.1944289077348 * nu (U+03BD): B<<95.0,326.5>-<91.0,346.0>-<86.0,350.0>>/B<<86.0,350.0>-<88.0,348.0>-<80.5,354.0>> = 6.34019174590985 * quotedblbase (U+201E): B<<275.0,-90.0>-<269.0,-90.0>-<266.0,-90.0>>/B<<266.0,-90.0>-<270.0,-89.0>-<288.0,-82.0>> = 14.036243467926484 * quotedblleft (U+201C): B<<204.0,670.0>-<211.0,670.0>-<214.0,670.0>>/B<<214.0,670.0>-<210.0,669.0>-<191.0,662.0>> = 14.036243467926484 * quotedblleft (U+201C): B<<394.0,670.0>-<401.0,670.0>-<404.0,670.0>>/B<<404.0,670.0>-<400.0,669.0>-<381.0,662.0>> = 14.036243467926484 * quotedblright (U+201D): B<<102.0,486.0>-<95.0,486.0>-<92.0,486.0>>/B<<92.0,486.0>-<96.0,487.0>-<115.0,494.0>> = 14.036243467926484 * quotedblright (U+201D): B<<292.0,486.0>-<285.0,486.0>-<282.0,486.0>>/B<<282.0,486.0>-<286.0,487.0>-<305.0,494.0>> = 14.036243467926484 * quoteleft (U+2018): B<<204.0,669.0>-<211.0,669.0>-<214.0,669.0>>/B<<214.0,669.0>-<210.0,668.0>-<191.0,661.0>> = 14.036243467926484 and 136 more. [code: found-jaggy-segments]
--- Rationale --- This check detects line segments which are nearly, but not quite, exactly horizontal or vertical. Sometimes such lines are created by design, but often they are indicative of a design error. This check is disabled for italic styles, which often contain nearly-upright lines.* ⚠ **WARN** The following glyphs have semi-vertical/semi-horizontal lines: * Beta (U+0392): L<<121.0,387.0>--<353.0,386.0>> * circleplus (U+2295): L<<404.0,410.0>--<403.0,727.0>> * intersection (U+2229): L<<128.0,470.0>--<130.0,0.0>> * intersection (U+2229): L<<413.0,0.0>--<412.0,469.0>> * intersection (U+2229): L<<489.0,422.0>--<491.0,0.0>> * intersection (U+2229): L<<52.0,0.0>--<50.0,425.0>> * u10149 (U+10149): L<<729.0,0.0>--<416.0,1.0>> * u1014B (U+1014B): L<<417.0,330.0>--<418.0,54.0>> * u10161 (U+10161): L<<35.0,729.0>--<701.0,725.0>> * u1016D (U+1016D): L<<500.0,92.0>--<760.0,93.0>> and 34 more. [code: found-semi-vertical]
| 💔 ERROR | 🔥 FAIL | ⚠ WARN | 💤 SKIP | ℹ INFO | 🍞 PASS | 🔎 DEBUG |
|---|---|---|---|---|---|---|
| 0 | 10 | 13 | 106 | 9 | 80 | 0 |
| 0% | 5% | 6% | 49% | 4% | 37% | 0% |
Note: The following loglevels were omitted in this report:
davelab6
commented
2 years ago We need to deal with the RFN, so lets postpone this for a few months
https://ucbclassics.dreamhosters.com/djm/greekkeys/NAUdownload.html