Code space is sometimes a valuable asset in embedded devices. Due to this, one has to be careful in what characters to include in a font. Why store character ranges which are not required!
But then … Suddenly I need to add a language variant which indeed needs those accented characters, cyrillics or whatever which are NOT in the current font.
Now it would be very useful if I could easily find out the characters which already are in the font. This information could be shown for instance in the comment block at the start of the c-file. From there it would be simple to copy and paste to the online converter’s “range” and/or “symbols” field(s), and then modify / add characters as required.
What do you think?