librebarcode
librebarcode copied to clipboard
Libre Barcode: barcode fonts for various barcode standards.
Would it possible to adjust the relative height of the barcode lines? Any pointers on how? I'd really like to generate barcodes that look more proportional to a UPC code....
 When using Libre Barcode 128 Text in desktop Excel 365, there is a checksum char in the text below (Hello World!W). In web based Excel is it as expectet...
I'm trying to generate a EAN-13 barcode in SQL Server Reporting Services from a 13-digit string, the last digit is the check digit and it's already calculated. In the report...
Hi, I was wondering if there is a simple way to remove the extra space that is on the no text version of the font, as it looks like that...
For all Libre Barcode fonts in MS-Word ideally the `calt`/"Contextual Alternates" feature must be activated (as shown in https://github.com/graphicore/librebarcode/issues/28#issuecomment-745736391). EAN-13 has documentation for workarounds (fallback/compatible). If for Code39/128 `calt` is...
Google Sheets doesn't print EAN 13 very well. Setting `Format -> Number -> Plain text ✓` for the EAN 13 using cells fixes printing.
I know, I probably lack of knowledge and I'm not doing things right, probably not an issue, but I don't know where else to find help about this. I'm trying...
Hi everyone, Hope you're all well. If you look at this link below on an iPhone, 'Libre Barcode EAN13 Text' on Google Fonts renders only numbers and doesn't appear like...
### Does GPOS table have kerning information? * ERROR: Font is missing a "GPOS" table These fonts don't require any kerning. ### fontforge-check: Font doesn't have invalid glyph names *...
 This is already fixed in the documentation pages with b0adea7a8bb4f9279bf1f85672a0e5cd6a69f82f but it also needs to be documented as a usage instruction, along with the workaround for #29 The solution...