Do not hardcode Blocks.txt into the program
Brought to you by:
eugeniy
Menu
▾
▴
#7 Do not hardcode Blocks.txt into the program
Hello. I have been relatively active in Unicode for the past eight years and have submitted a number of proposals: https://sites.google.com/site/jamadagni/files/utcsubmissions. I was trying to use FntSample to produce the charts for my proposal.
However, when I am proposing a new non-existent block for Unicode, FntSample is unable to detect the glyphs assigned to that block (though it has no problems with new codepoints in existing blocks.)
It would be great if FntSample could read the Blocks.txt from a data file (under /usr/share/data/fntsample/ or such) at run time so that we can edit it to include our new blocks and thus get them displayed.
Thanks!
Hi, in the new release (5.0) it is now possible to specify an alternate blocks file using --blocks-file option. This should help in your use case. The release is available from github: https://github.com/eugmes/fntsample/releases/tag/release%2F5.0