You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Angle quotation marks, or guillemets, are used in many languages to denote speech. They are also often used in a technical context as a means of demarcating email addresses (e.g., ‹notifications@github.com›) or denoting objects such as Unicode codepoints (e.g., ‹U+211D› DOUBLE-STRUCK CAPITAL R).
In Cascadia Code’s current design, the angle used in both the single and double angle quotation marks is quite narrow, relative to comparable programming and traditional fonts, and importantly, makes it more difficult to distinguish them from less-than/greater-than signs. For this reason, I’d like to propose increasing/widening the angle for the following four codepoints:
Codepoint
Name
‹U+2039›
SINGLE LEFT-POINTING ANGLE QUOTATION MARK
‹U+203A›
SINGLE RIGHT-POINTING ANGLE QUOTATION MARK
‹U+00AB›
LEFT-POINTING DOUBLE ANGLE QUOTATION MARK
‹U+00BB›
RIGHT-POINTING DOUBLE ANGLE QUOTATION MARK
Examples, comparison with other fonts
Render from LuaLaTeX, viewed in Evince PDF viewer—note the spacing and angle of Cascadia Code’s angle quotes in comparison to less-than/greater-than
LT/GT Sign
Single Angle Quote
Double Angle Quote
Angle Bracket
‹U+003C› LESS-THAN SIGN
‹U+2039› SINGLE LEFT-POINTING ANGLE QUOTATION MARK
‹U+00AB› LEFT-POINTING DOUBLE ANGLE QUOTATION MARK
‹U+2329› LEFT-POINTING ANGLE BRACKET
‹U+003E› GREATER-THAN SIGN
‹U+203A› SINGLE RIGHT-POINTING ANGLE QUOTATION MARK
‹U+00BB› RIGHT-POINTING DOUBLE ANGLE QUOTATION MARK
‹U+232A› RIGHT-POINTING ANGLE BRACKET
Angle brackets, less-than/greater-than signs and single guillemets in fonts Cambria, DejaVu Serif, Andron Mega Corpus, Andika and Everson Mono (from Wikipedia)
Proposed technical implementation details
Increase/widen the angle used in the design of both the single and double angle quotation marks to aid in visual differentiation from the less-than/greater-than signs, especially at small sizes.
The text was updated successfully, but these errors were encountered:
This is a significant update to Cascadia Code including a large number
of bug fixes as well as updating the font to offer support for Fira
Code v5 ligature support.
This update supersedes PR #373.
Closes#262 - ⏎ added
Closes#264 - additional codepoints for control characters added
Closes#281 - `!:` and `!.` added
Closes#290 - `/\` and `\/` added
Closes#301 - `??=` added
Closes#324 - ℞ added
Closes#327 - `<:>` and other variants implemented via the `calt`
refactoring
Closes#359 - house added
Closes#371 - Added x-height instruction into ttfautohint to control the
height of the lowercase.
Closes#375 - Completely redesigned quote marks for better recognition
Closes#377 - updated hinting to achieve more consistent results
Closes#381 - increased height of thetamod
Closes#382 - reduced the width of the hooklefts
Closes#383 - updated heights on esh, glottalstop, glottalstopreversed
Closes#384 - tweaked hinting a little bit. Maybe it'll help :)
Closes#386 - added remaining soft-dotting
Closes#392 - changed designs of angled quotes (they are now round)
Closes#394 - changed former `~=` symbol to a simpler component-based
version. Should be less confusing now for Lua / Matlab users.
Closes#395 - makes the underline thicker based on font weight
Closes#400 - increased size of degree
Closes#219
The full control pictures block has been added (u+2400 to u+2426). For
purposes of rendering, the two letter abbreviations have been used
instead of the standard three letter abbreviations:
Additionally, ss20 includes the oft-unused graphical representations of
these codepoints (for fun!):
Closes#276 (infinite arrows)
Full support for Fira Code's current ligature set (with a few
exceptions). Now featuring infinite arrows!!!
This involved a full refactoring of the `calt` feature—for those
interested, it now uses forward-looking substitutions instead of
backward-looking substitutions and progressive substitution to reduce
code. This also required some redesigning of the greater / lesser
related ligatures. Please note, I have also removed all the obsolete
ligatures now covered by the arrows code.
Closes#329
There was a mismatch in the font's postscript naming conventions that
was corrected. Should now render all weights in Word. **Note** there is
apparently an additional bug in Mac Word's implementation of variable
fonts which should be available in an update mid-Feb.
* Not listed – Reworked the hints for the mod and superscript glyphs so
that they're bottom-up rather than top-down. This allows for better
bottom alignments.
Aside from the above changes, this version also includes many other
small updates including spacing, outline quality improvements, and
fixing hinting.
Description of the new feature/enhancement
Angle quotation marks, or guillemets, are used in many languages to denote speech. They are also often used in a technical context as a means of demarcating email addresses (e.g., ‹notifications@github.com›) or denoting objects such as Unicode codepoints (e.g., ‹U+211D› DOUBLE-STRUCK CAPITAL R).
In Cascadia Code’s current design, the angle used in both the single and double angle quotation marks is quite narrow, relative to comparable programming and traditional fonts, and importantly, makes it more difficult to distinguish them from less-than/greater-than signs. For this reason, I’d like to propose increasing/widening the angle for the following four codepoints:
Examples, comparison with other fonts
Render from LuaLaTeX, viewed in Evince PDF viewer—note the spacing and angle of Cascadia Code’s angle quotes in comparison to less-than/greater-than
Angle brackets, less-than/greater-than signs and single guillemets in fonts Cambria, DejaVu Serif, Andron Mega Corpus, Andika and Everson Mono (from Wikipedia)
Proposed technical implementation details
Increase/widen the angle used in the design of both the single and double angle quotation marks to aid in visual differentiation from the less-than/greater-than signs, especially at small sizes.
The text was updated successfully, but these errors were encountered: