I use it in my ClockThing [1], which sadly has no pictures on its github, but as an alarm clock with a bitmapped screen, it needs a nice font to give it gravitas.
I used Omron's K3GN panel meters in a project at work and I had to draw the alphabet in the configuration drawing because it is so unintuitive. It's not a whole lot worse than the one shown in the article, but still... it's pretty rough. I think I prefer numbered parameters like you typically see on VFDs. It's a lot easier to just scroll to P148 or whatever, enter to view/modify, scroll the value, enter to set. Menu trees on seven-segment interfaces are a mistake.
I'm not convinced that, in the 14 segment font, we should just give up and accept that lower case "a" and "m" should just be the same as their upper case counterparts:
We can represent a "double storey" a like this:
___
|
___|
| |
|___|
It's also unclear why we couldn't have a 14 seg lower case m like this:
_ _
| | |
| | |
Maybe for each character, have a link to a documented rationale.
EDIT: Oh, look at the example font sheet featured in Wikipedia's Fourteen-segment-display page: it has these letters exactly as I say:
Since you can't communicate case for all characters, trying to communicate it for some characters while failing to differentiate for others would be a bad decision. It's better to accept that the characters do not represent case at all.
This rare 22-segment display is the most interesting I've seen so far. It can display the full 7-bit ASCII range including special characters: https://www.youtube.com/watch?v=D2cyZoCat_U
I forgot that I had made this until seeing it, but I have a very basic 14-segment font editor for a project I've been meaning to pick up again at some point.
Easter(?) egg: The 7SEGG-CHAN font appears in the preview image but is not documented on the page, other than a mathematical reference in the "Misc." section.
The backgrounds are achieved by having two overlapping <span> elements in different colors. If you use the font standalone, you wouldn't get the two-tone appearance.
DSEG7 uses some lower case forms (e.g. for "b", "n", "t") to avoid letter shapes which are impossible to represent on a 7-segment display (like "N"), or which would be ambiguous (e.g. "B" / "8").
You still can't represent all lowercase letter shapes on a 14-segment display, but you can do all uppercase, so I'm assuming they went with that for consistency.
I used the 7-segment font for my software-only microwave and really like the result.
https://microwave.pointless.click/
I use it in my ClockThing [1], which sadly has no pictures on its github, but as an alarm clock with a bitmapped screen, it needs a nice font to give it gravitas.
[1] https://github.com/russor/ClockThing
I used Omron's K3GN panel meters in a project at work and I had to draw the alphabet in the configuration drawing because it is so unintuitive. It's not a whole lot worse than the one shown in the article, but still... it's pretty rough. I think I prefer numbered parameters like you typically see on VFDs. It's a lot easier to just scroll to P148 or whatever, enter to view/modify, scroll the value, enter to set. Menu trees on seven-segment interfaces are a mistake.
Page six shows the alphabet: https://www.myomron.com/downloads/1.Manuals/Panel%20Indicato...
I wonder how they display "S5" or "5S"
If you have actual, physical 14-segment displays, and just need the char->segment mappings, you can find them here:
https://github.com/keshikan/DSEG/blob/master/resources/DSEG1...
I'm not convinced that, in the 14 segment font, we should just give up and accept that lower case "a" and "m" should just be the same as their upper case counterparts:
We can represent a "double storey" a like this:
It's also unclear why we couldn't have a 14 seg lower case m like this: Maybe for each character, have a link to a documented rationale.EDIT: Oh, look at the example font sheet featured in Wikipedia's Fourteen-segment-display page: it has these letters exactly as I say:
https://en.wikipedia.org/wiki/Fourteen-segment_display#/medi...
All the letters in DSEG14 are in upper-case, regardless if a lower case variant is possible. It appears to be a stylistic choice.
Only DSEG7 has lower case letters, and that's probably only to distinguish them from other characters or numbers (e.g. h/X, i/1, or o/0).
Since you can't communicate case for all characters, trying to communicate it for some characters while failing to differentiate for others would be a bad decision. It's better to accept that the characters do not represent case at all.
If you’re at all interested in segmented displays Posy’s YouTube video about them is pure gold: https://youtu.be/RTB5XhjbgZA
This rare 22-segment display is the most interesting I've seen so far. It can display the full 7-bit ASCII range including special characters: https://www.youtube.com/watch?v=D2cyZoCat_U
I forgot that I had made this until seeing it, but I have a very basic 14-segment font editor for a project I've been meaning to pick up again at some point.
https://github.com/mmastrac/gpsclock
Font JSON file too...
https://github.com/mmastrac/gpsclock/blob/master/fontmaker/f...
Easter(?) egg: The 7SEGG-CHAN font appears in the preview image but is not documented on the page, other than a mathematical reference in the "Misc." section.
A pretty reasonable way to prototype fixed segment LCD displays. I'm kind of on the fence about the on/off backgrounding stuff.
The backgrounds are achieved by having two overlapping <span> elements in different colors. If you use the font standalone, you wouldn't get the two-tone appearance.
Ah good to know.
What's the purpose of the arrow with line through it for the DSEGWeather?
Well thought out font though, 7segg-chan is cute.
Seems to be for weather going from current to future? IDK, TBH.
https://github.com/keshikan/DSEG?tab=readme-ov-file#sample
Ha, I came to the comments for this. I thought it might be wind, but I don’t know why there would be just a slash.
I don't understand why DSEG14 doesn't have some of the lower-case letters that DSEG7 does. Anyone know why?
DSEG7 uses some lower case forms (e.g. for "b", "n", "t") to avoid letter shapes which are impossible to represent on a 7-segment display (like "N"), or which would be ambiguous (e.g. "B" / "8").
You still can't represent all lowercase letter shapes on a 14-segment display, but you can do all uppercase, so I'm assuming they went with that for consistency.