mozilla/zilla-slab

Mozilla's Zilla Slab Type Family

zilla-slab's Issues

Support Greek and Cyrillic

Any plans to extend the coverage?

No need to reserve generic font names like weights

Hi guys,

No need to reserve the generic weight names as they are non-unique parts of your font name. It's overkill.
See OFL FAQ section 5.5 on http://scripts.sil.org/ofl-faq_web#7fba289b

(BTW if you haven't read through the FAQ yet, it's probably a good idea to do so).

Thanks.

Numeric characters are not rendered uniformly

Issue Snap of PDF Document

Details

I made a pdf document from latex using pandoc on a debian buster os. I find the number letters "0123456789" are rendered in a non-uniform fashion.
The one's out of order in my opinion seems to be -
Char-set-1 = { "0" , "1" , "2" } ; these characters appear to be comparatively smaller w.r.t the alphabets
Char-set-2 = { "3" , "4" , "5" , "7" , "9" } ; these characters appear to be placed slightly below the alphabet's lowest line

Environment

1. Latex

# latex --version
pdfTeX 3.14159265-2.6-1.40.21 (TeX Live 2020/Debian)
kpathsea version 6.3.2
Copyright 2020 Han The Thanh (pdfTeX) et al.
There is NO warranty.  Redistribution of this software is
covered by the terms of both the pdfTeX copyright and
the Lesser GNU General Public License.
For more information about these matters, see the file
named COPYING and the pdfTeX source.
Primary author of pdfTeX: Han The Thanh (pdfTeX) et al.
Compiled with libpng 1.6.37; using libpng 1.6.37
Compiled with zlib 1.2.11; using zlib 1.2.11
Compiled with xpdf version 4.02

2. Pandoc

# pandoc  --version
pandoc 2.16.1
Compiled with pandoc-types 1.22.1, texmath 0.12.3.2, skylighting 0.12.1,
citeproc 0.6, ipynb 0.1.0.2
User data directory: /root/.local/share/pandoc
Copyright (C) 2006-2021 John MacFarlane. Web:  https://pandoc.org
This is free software; see the source for copying conditions. There is no
warranty, not even for merchantability or fitness for a particular purpose.

4. Kernel

# uname -a
Linux local 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux

5. OS

Debian GNU/Linux 11

Missing characters for complete Guarani support

The Guarani alphabet uses the following accented letters:

Áá Éé Íí Óó Úú Ýý Ãã Ẽẽ G̃g̃ Ĩĩ Ññ Õõ Ũũ Ỹỹ ʼ ₲

From these, Zilla Slab lacks:

G̃ (ASCII G with U+0303)
g̃ (ASCII g with U+0303)
Ỹ (U+1EF8, also used in Vietnamese)
ỹ (U+1EF9, also used in Vietnamese)
ʼ (U+02BC)
₲ (U+20B2)

Request of characters: for advanced typesetting (bibliographies, novels, charts, etc.)

※ U+203B REFERENCE MARK «Punctuation, Other»
⁜ U+205C DOTTED CROSS
⁂ U+2042 ASTERISM «Punctuation, Other»
☞ U+261E WHITE RIGHT POINTING INDEX «Symbol, Other»
☛ U+261B BLACK RIGHT POINTING INDEX «Symbol, Other»
☚ U+261A BLACK LEFT POINTING INDEX
U+261C WHITE LEFT POINTING INDEX
➙ U+2799 HEAVY RIGHTWARDS ARROW
➛ U+279B DRAFTING POINT RIGHTWARDS ARROW

Add LICENSE file to release files

Hello!
In some Linux distributions, in order to distribute this fonts an license file is required. Is it possible to add the license file from source code to the root of the release files?

So when you download release file it has the license file attached to it. This will help Linux package maintainers to grab license from the same .zip file as the fonts.

Zilla Slab display issue in Nightly when viewed on fonts.google.com

When I view the Zilla Slab page on Google Fonts in Firefox Nightly (56), the font does not display and there are several JS errors in the console.

Latest version 1.002 doesn't contain RegularItalic otf, ttf, woff, woff2 files

Latest version 1.002 doesn't contain RegularItalic otf, ttf, woff, woff2 files. These files are contained in the initial 1.0 release. I don't see the RegularItalic .ufo file in /sources/ either so not sure if it was supposed to be removed or not.

Google Fonts shows Regular Italic.
https://fonts.google.com/specimen/Zilla+Slab

Version 1.002

Version 1.0

nbsp characters are not displayed with Zilla font

See: https://bugzilla.mozilla.org/show_bug.cgi?id=1366863

Zilla Slab Highlight: Whitespace character issues

@evanadams noticed "Zilla Slab Highlight fonts use a black rectangle for space, but a white rectangle for non-breaking-space and, ironically, a black rectangle for narrow non-breaking-space. Looks like a bug. Also, it re-uses the space glyph for the ideographic-space which is wider than a space and results in lots of white."

Please add a LICENSE file to this public repository

I don't know which license y'all selected for the font, but that license should be dropped into a LICENSE file and committed here for other users whenever the next set of commits are pushed.

Whre Can I Download Zilla Stab Hightlight (Colorful edition) Fonts?

Loveing those fonts so much! And found there is a colorful edition:

I have downloaded the ZillaStabFonts form releases and the corlorful one is not included.

Where can I donwnload thoses fonts? Please help!

Cannot apply tabular-nums in Chrome

When we use the font(in opentype format) in chrome, we cannot use font-variant-numeric: tabular-nums. However this works in IE.

chrome version: 70.0.3538.102
Chrome:

IE:

CDN hosting for zilla-slab

Is there a plan/intent to make zilla-slab available in a font CDN? Has it been submitted to Google's font CDN? What's the best way for a Mozillian to include zilla-lab in their Mozilla web pages?

Request of characters: needed in mathematics, geometry, etc.

′ U+2032 PRIME «Punctuation, Other»
″ U+2033 DOUBLE PRIME «Punctuation, Other»
‴ U+2034 TRIPLE PRIME «Punctuation, Other»
⁗ U+2057 QUADRUPLE PRIME «Punctuation, Other»
‱ U+2031 PER TEN THOUSAND SIGN «Punctuation, Other»

Possibly improve the GPOS/GSUB compilation by not using extended tables

Based on opentypejs/opentype.js#292 it appears that Zilla Slab uses GPOS/GSUB lookups that are intended for very large fonts, which is a bit puzzling as Zilla is pretty much a standard Latin-only font and shouldn't need to use these special purpose lookups. In fact, doing so may lead to parse failures in "simpler" or older engines, so it might be worth changing the UFO compilation such that normal GPOS/GSUB lookups are used.

ZillaSlabHighlight-Bold.ttf full name bug

ZillaSlabHighlight-Bold.ttf has a name table "full name" value of

Zilla Slab Highlight Bold Bold

which should be

Zilla Slab Highlight Bold

(eg https://github.com/google/fonts/blob/926397dfff8d1a140c9332f95e3eddf03a8009df/ofl/zillaslabhighlight/METADATA.pb#L21)

Read-only Embedded Restricted font

When Zilla Slab is embedded into a PowerPoint document and reopened in any windows machine that does not have Zilla Slab font installed, you get

This presentation cannot be edited because it contains one or more read-only embedded (restricted) fonts

The fonts are
Zila Slab
Zila Slab Light
Zila Slab Semi Bold

Uppercase "C" with slabs

I really like Zilla Slab, but I'd like it even more if the uppercase "C" would have a large top slab.

Perhaps this could be added as alternate glyph?

With " large top slab" I mean something like this:
http://www.1001fonts.com/maiden-orange-font.html?text=C
(scroll all the way down to the "C")

Zilla Slab doesn't display Spaces in Google Slides

Spaces don't appear between words on Google Slides. See below:

CODE_OF_CONDUCT.md file missing

As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:

1. Required Text - All text under the headings Community Participation Guidelines and How to Report, are required, and should not be altered.
2. Optional Text - The Project Specific Etiquette heading provides a space to speak more specifically about ways people can work effectively and inclusively together. Some examples of those can be found on the Firefox Debugger project, and Common Voice. (The optional part is commented out in the raw template file, and will not be visible until you modify and uncomment that part.)

If you have any questions about this file, or Code of Conduct policies and procedures, please see Mozilla-GitHub-Standards or email [email protected].

(Message COC001)

Printing error with ZillaSlab Highlight-Bold

Hey there,
when trying to print a file w/ Highlight-Bold, I get the following error from my printer:

ERROR: invalidfont
OFFENDING COMMAND: definefont
STACK:
/Font
-dictionary-
/XJATA+ZillaSlabHighlight-Bold

Any ideas?
Cheers,
-f

Zilla Highlight in Google Docs has extra space appended to end of sentence

This issue was reported to me in an email thread.

Zilla Highlight uses a liga OpenType feature to make the space appear highlighted by replacing the space glyph with a black variant.

lookup BLACKSPACE {
                sub space by space.black;
                sub uni00A0 by space.black;
            } BLACKSPACE;

Google Docs appends a   (uni00A0) to the end of user input.

<span class="kix-wordhtmlgenerator-word-node" style="...">Hello World<span class="goog-inline-block" style="...">&nbsp;</span>

This unfortunately produces the following:

It should look like this:

The easiest solution is to drop uni00A0 from the BLACKSPACE lookup:

lookup BLACKSPACE {
                sub space by space.black;
            } BLACKSPACE;

I'm wondering if anyone can think of any unforeseen consequences by doing this?

Width of ß (sharp s) is way to large

Screenshot: https://i.imgur.com/3MKESlK.png

Other people agreeing: http://www.typografie.info/3/topic/36559-zilla-slab/

Missing files?

https://github.com/mozilla/zilla-slab/blob/master/UFOs/ZillaSlab-Regular.ufo/features.fea points to files necessary to compile this font, but not found in the repository.

Request of characters: needed when writing about graphematics, typesetting, writing systems

◌ U+25CC DOTTED CIRCLE «Symbol, Other»
⸢ U+2E22 TOP LEFT HALF BRACKET «Punctuation, Open»
⸣ U+2E23 TOP RIGHT HALF BRACKET «Punctuation, Close»
⸤ U+2E24 BOTTOM LEFT HALF BRACKET «Punctuation, Open»
⸥ U+2E25 BOTTOM RIGHT HALF BRACKET «Punctuation, Close»
‗ U+2017 DOUBLE LOW LINE «Punctuation, Other»
‸ U+2038 CARET «Letter, Lowercase»
⁁ U+2041 CARET INSERTION POINT

"Wh" looks very strange

The serif on the lowercase h is higher than the serifs on the capital W, which doesn't look very nice. Give that so many sentences start with Wh, it would probably be good to fix this.

Thanks!

Wiki changes

FYI: The following changes were made to this repository's wiki:

• defacing spam has been removed

• Restricting write access to contributors is strongly encouraged. Please make that change (documentation).

These were made as the result of a recent automated defacement of publically writeable wikis.

No support for non-breaking space (nbsp)

Zilla Slab doesn't seem to support the non-breaking space character, or   in HTML. As this is used all over the place (and is basically just a space), it would be really nice if we could add this glyph.

Thanks!

No Vietnamese support

In https://support.mozilla.org/vi/:

In https://support.mozilla.org/vi/get-involved:

Cf. mozilla/kitsune#3326

Cyrillic support

Is there any news for Cyrillic support? And before making it please consult with native type designers, for example, CSTM Fonts. I wish cyrillic in your font will be modern and matching.

Compiled OTF fonts have numerous characters (code-points) without defined glyphs

The compiled OTF fonts have numerous characters (code-points) without any defined glyphs.

This is evident when viewing the font in Windows' Character Map.
For example:
U+0080 to U+009F are blank, but I couldn't see these explicitly defined in the font.
U+0391 to U+03C9 only three glyphs are explicitly defined for Greek letters, but every character in this range is displayed by Character Map (all but three with the not-defined glyph).
U+2801 to U+28ff display Braille patterns, none of which are defined in the font.
U+3131 to U+318E display Korean characters (Hangul), none of which are defined in the font.
U+3400 to U+9FA5 display CJK ideographs (Chinese characters), none of which are defined in the font.

Although the above behaviour is strange, it also seems to be preventing the family of fonts from being being embedded into PDF files (whether using PDF/A format or not), and — in some cases — preventing text in PDF files from being persistently marked as being formatted as a Zilla Slab font.
This is detailed at length at https://forum.tracker-software.com/viewtopic.php?p=169710

—DIV

Variable version?

Zilla Slab Highlight at < 100% opacity shows fully-opaque lines between characters while editing

Zilla Slab Highlight v1.002
macOS 10.13.6 (17G65)

Steps:

• Using Pages.app, set font for selected text to Zilla Slab Highlight
• Decrease opacity of text color to 50%

Result:

• Thin, fully opaque dividing lines appear between characters…
  

Expected:

• Consistent opacity across text

Additional Notes:

• This also reproduces in third-party apps (tested with OmniGraffle)
• The output in the PDF looks fine:

Release font on Google Font & Typekit

It would be good to have Zilla on those external sites, that people can easily to sync across computer like Fira.
https://github.com/mozilla/Fira#external-resources

Request of characters: useful as list itemizers

‣ U+2023 TRIANGULAR BULLET
⁃ U+2043 HYPHEN BULLET
⁌ U+204C BLACK LEFTWARDS BULLET
⁍ U+204D BLACK RIGHTWARDS BULLET

Recommended Fallback

What font is recommended to use as a fallback for this font?

Request of characters: for advanced punctuation

― U+2015 HORIZONTAL BAR «Punctuation, Dash»
‼︎ U+203C DOUBLE EXCLAMATION MARK
⁇ U+2047 DOUBLE QUESTION MARK
⁈ U+2048 QUESTION EXCLAMATION MARK
⁉ U+2049 EXCLAMATION QUESTION MARK
⸻ U+2E3B THREE-EM DASH «Punctuation, Dash»
⸺ U+2E3A TWO-EM DASH «Punctuation, Dash»
⁚ U+205A TWO DOT PUNCTUATION «Punctuation, Other»
⁖ U+2056 THREE DOT PUNCTUATION «Punctuation, Other»
⁘  U+2058 FOUR DOT PUNCTUATION «Punctuation, Other»
⁙ U+2059 FIVE DOT PUNCTUATION «Punctuation, Other»
⁛ U+205B FOUR DOT MARK
⁝ U+205D TRICOLON
⁞ U+205E VERTICAL FOUR DOTS
⁓ U+2053 SWUNG DASH «Punctuation, Other»
‖ U+2016 DOUBLE VERTICAL LINE «Punctuation, Other»

tabular-nums issue in Chrome

There seems to be an issue with font-variant: tabular-nums in Chrome (tested Version 70.0.3538.102) on MacOS Sierra & Mohave.

Any combination of the following style declarations can't fix the issue:

        font-variant: tabular-nums;
        font-feature-settings: "tnum";
        font-variant-numeric: tabular-nums;
        -webkit-font-feature-settings: "tnum";

Screenshot of https://beautifulwebtype.com/zilla-slab/ in Chrome

Screenshot of https://beautifulwebtype.com/zilla-slab/ in Safari

When an alpha numeric [a-zA-Z] is added to the textContent of an element in Chrome the problem disappears:

Other tested fonts that support this font-variant are ok in (this version) of Chrome and MacOS.

building from source broken

the build.sh script has multiple issues while building on a Linux machine.

1. fontmake cannot autohint (tested with both python3.5 and python2.7).

Traceback (most recent call last):
  File "/home/shine/dev/git/mozilla/fonts/zilla-slab/env/3.5/bin/fontmake", line 11, in <module>
    sys.exit(main())
  File "/home/shine/dev/git/mozilla/fonts/zilla-slab/env/3.5/lib/python3.5/site-packages/fontmake/__main__.py", line 195, in main
    ufo_paths, is_instance=args.pop('masters_as_instances'), **args)
  File "/home/shine/dev/git/mozilla/fonts/zilla-slab/env/3.5/lib/python3.5/site-packages/fontmake/font_project.py", line 481, in run_from_ufos
    **kwargs)
  File "/home/shine/dev/git/mozilla/fonts/zilla-slab/env/3.5/lib/python3.5/site-packages/fontmake/font_project.py", line 193, in build_ttfs
    self.save_otfs(ufos, ttf=True, **kwargs)
  File "/home/shine/dev/git/mozilla/fonts/zilla-slab/env/3.5/lib/python3.5/site-packages/fontTools/misc/loggingTools.py", line 372, in wrapper
    return func(*args, **kwds)
  File "/home/shine/dev/git/mozilla/fonts/zilla-slab/env/3.5/lib/python3.5/site-packages/fontmake/font_project.py", line 320, in save_otfs
    ttfautohint(otf_path, hinted_otf_path, args=autohint)
  File "/home/shine/dev/git/mozilla/fonts/zilla-slab/env/3.5/lib/python3.5/site-packages/fontmake/ttfautohint.py", line 32, in ttfautohint
    return subprocess.call(arg_list + args.split() + file_args)
  File "/usr/lib/python3.5/subprocess.py", line 557, in call
    with Popen(*popenargs, **kwargs) as p:
  File "/usr/lib/python3.5/subprocess.py", line 947, in __init__
    restore_signals, start_new_session)
  File "/usr/lib/python3.5/subprocess.py", line 1551, in _execute_child
    raise child_exception_type(errno_num, err_msg)
FileNotFoundError: [Errno 2] No such file or directory: 'ttfautohint'

I managed to build the fonts without autohint.

2. sfnt2woff and woff2_compress are dependencies that are not mentioned in the requirements.txt. Neither are the steps to install the dependencies are not mentioned in the README.md file.
   I had to install the woff-tools package to get the sfnt2woff command working. I also compiled the woff2 library from source to get the woff2_compress command working.

But these are tech-y stuff that a normal user cannot comprehend.

• We should look at why fontmake can't autohint. If it is an upstream issue, we should remove the -a flag from the fontmake command so that the script doesn't break.
• If we're going to support WOFF/WOFF2, we should let users know how to get the dependencies installed, in the README.md file.

Erratic embeddability / Vendor ID specification

The embeddability of the fonts in this family is inconsistent.
I cannot see where this property is specified in any of the source files, but I notice that the Vendor ID is not specified for several of the fonts within the family, and those two issues seem to coincide precisely for every single one of the fonts.

zilla-slab/sources/ZillaSlab-Regular.ufo/fontinfo.plist

Lines 139 to 140 in 0a6fdf0

	<key>openTypeOS2VendorID</key>
	<string>TPTQ</string>

With respect to version 1.002 (OTF files)

• Light: print & preview; Vendor ID not specified (licence agreement and licence URL also missing!)
• Light italic: print & preview; Vendor ID not specified
• Regular: installable; Vendor ID specified
• Regular italic: installable; Vendor ID specified
• Medium: print & preview; Vendor ID not specified
• Medium italic: print & preview; Vendor ID not specified
• SemiBold: print & preview; Vendor ID not specified
• SemiBold italic: print & preview; Vendor ID not specified
• Bold: installable; Vendor ID specified
• Bold italic: print & preview; Vendor ID not specified

and

• Highlight regular: editable; Vendor ID specified
• Highlight bold: print & preview; Vendor ID not specified