Path Stroking is Hideous
See original GitHub issueI’m testing with converting Glyph
to PathData
and drawing the paths to the screen and then stroking, but I’m ending up with really ugly stroking:
This is using Open Sans
from GoogleFonts. Is there something I need to do to make this stroke properly?
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Outline stroke from path in Illustrator
Is there a way to outline a path in a Devide-like way? I want the object to be like the first cross, instead...
Read more >Empty space between SVG paths - Stack Overflow
Here is an image showing the empty space between the paths. enter image description here. Here is the code for the SVG path,...
Read more >Inkscape Text to path keeps the Stroke and not the Fill when ...
Using Inkscape with Cutters/Plotters Inkscape Text to path keeps the Stroke and not the Fill ... causing the wood to be decimated and...
Read more >Draw SVG - Path to stroke problems - GSAP - GreenSock
Draw SVG - Path to stroke problems ... You can see the first one is a nice curve, but as that stroke gets...
Read more >Path join type not correct in first node (on smaller width ) - GitLab
Set round join in stroke style, have a small stroke width (0.5-2.5 px). What happened? Every join gets rounded except the first node,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Because font hinting is a way more sophisticated way to round properly to the grid.
https://blog.idrsolutions.com/2013/12/what-is-font-hinting/
Or simply said, a deliberate way that decides for each value to round down or up for minimal errors due to rasterization. (rounding)
@axkibe you’re right regarding drawing text, but the adjustment was a global one applying to all contextual drawing.