Character/glyph name and code point documentation

[JohnFauss]

Can a table/list associating the names/usage of the glyphs in each of the Libre barcode fonts with their code points please be made available?

This information is essential in order to be able to develop accurate barcode encoding methods in software languages that are not currently supported.

For example, in the Libre Barcode EAN13 font, I've been able (with considerable effort) to deduce that code points 0x41-0x4A (decimal 65-74) produce the Set A 0-9 digit characters, code points 0x4b-0x54 (decimal 75-84) produce the Set B 0-9 digit characters, and code points 0x61-0x6a (decimal 97-106) produce the Set C 0-9 digit characters, but I should not have to spend this level of effort to figure this out.

For traditional fonts, it is a simple matter to see and verify that, for example, a 0x41 code point (an ASCII uppercase "A") produces an uppercase letter A glyph, but deciphering the code points of glyphs in a barcode font is much more difficult. To illustrate, code point 0xa0 (decimal 160) in the Libre Barcode EAN13 font appears, I think, to produce a quiet zone for use in UPC barcodes because it looks like it may be nine barcode modules wide (versus the seven-modules wide quiet zones used for EAN barcodes). However, because there is nothing I can find that definitively tells me this, I'm only guessing.

All of the Libre Barcode fonts, not just the EAN13 font, would benefit from having this information available.

[graphicore]

The fonts are all generated by code: https://github.com/graphicore/librebarcode/tree/master/app/lib/builder
In the sources at the top is a lot of details how the fonts are actually structured. For code 39 and code 128 the encodings from the respective Wikipedia articles, that are also linked in the docs are used.

The documentation for EAN 13 describes different input methods, the compatible method is likely the closest to what you are looking for and the ascii encoding can be found in the sources and on the linked page of the grandzebu font.
You should definitely have a look at https://graphicore.github.io/librebarcode/ and the sources before trying to reverse engineer the encodings for the font. The EAN 13 font does some complex open type GSUB acrobatics and the fallback method uses that mechanism to extract the codepoints of the used glyphs via harfbuzz shaping, there's no real reference for that encoding. Maybe the UFOs generated in the build process can be used to map "meaningful" glyph names to codepoints, looking at the glif-files.