Parentheses are asymmetric #384
Comments
|
It would be helpful for you to include some or all of the info from the bug template (since you're reporting a bug, not a feature request). I ask solely because...
...it would be very good to know what software has decided to render these parentheses incorrectly, and at what point size. |
|
Interesting, I didn't expect this to be a bug. Makes sense, though. I'm using: Cascadia Code PL version 2009.22 I tried the same font and point size in notepad++ and don't have the same issue; it looks correct. |
|
Cascadia Code has special code built in to help it render more clearly under certain conditions. Unfortunately, different applications (especially coding environments) do all sorts of fun things that can lead to inconsistencies in the rendering even with the special code. In any case, I'll take a look and see if I can improve what is going on for those particular glyphs. |
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 (with images if possible)
The parentheses are not symmetric across the x axis. I know this is trivial but, I'm sorry in my opinion it is very unpleasant and distracting to see. When paired next to each other as shown here, all I see is an incomplete heart shape.
Here's a screenshot of Fira Code's symmetric parentheses:
Ahh, much cleaner!
I think a font primarily designed for coding should really nail these common cases and this is a pretty painful one to see.
The text was updated successfully, but these errors were encountered: