thinking about sending some suggestions to the federal highway administration for the next edition of the MUTCD, what do you all think
(for those reading this via an embed or RSS reader: click through to the post to see an SVG image)
- he/him
- duriansoftware.com/
the swift programming language is my fault to some degree. mostly here to see dogs, shitpost, fix old computers, and/or talk about math and weird computer programming things. for effortposts check the #longpost pinned tag. asks are open.
email
mailto:joe@duriansoftware.com
discord
jckarter
webzone
duriansoftware.com/code stuff
github.com/jckarter/fediverse
f.duriansoftware.com/@joeYou must log in to comment.
in reply to @iliana's post:
Looks nice.
I can't speak for other states but people in CT won't read this. Maybe increase contrast or use color red to catch people's attention
I'm a big fan! I'm worried the slightly smaller font and added space in between letters of OR ELSE may violate some standard alphabets rule - does it?
the actual R1-9(a) as of the 11th edition of the MUTCD (chapter 2B, page 82) has the smaller text at bottom; the spacing is also a little bit expanded, although not nearly as much as i did in the sign above lol.
various different signs have adjusted spacing as necessary, most commonly for space reasons on the diamond warning signs. i also think the particular font i have (https://github.com/sammdot/roadgeek-fonts) is not 100% accurate to the spacing specified in Standard Highway Signs and adding spacing is definitely not proportional to that