Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Code 39, undocumented space character, Â = " " #57

Open
sbeach92 opened this issue May 4, 2023 · 3 comments
Open

Code 39, undocumented space character, Â = " " #57

sbeach92 opened this issue May 4, 2023 · 3 comments
Assignees
Labels

Comments

@sbeach92
Copy link

sbeach92 commented May 4, 2023

It seems that with font for code 39, space generates just white space. To have barcode that encodes space character you have to type Â.

So to get proper "HELLO WORLD" you must type "HELLOÂWORLD".

@graphicore graphicore self-assigned this May 4, 2023
@graphicore
Copy link
Owner

@sbeach92 Thanks for reporting. Space works in general, looking at https://graphicore.github.io/librebarcode/documentation/code39

But, depending on the software you are using (something Microsoft Office I expect), it may not use OpenType-Features contextual alternates, which is used to insert the glyph for space.

What software are you using?

I agree that the docs should be updated, one thing would be to add a guide for Office users. Also, for Code 36, a hint about the special encoding would be helpful.

Here's the info for Office users in an issue comment: #28 (comment)

@sbeach92
Copy link
Author

sbeach92 commented May 4, 2023

It behaves this way in every program I tried in windows 10. (Main problem was in Office and Solidworks)

Even fonts.google.com test field seems that you should have something around space to get space character in barcode. "a " would show just a, but "a a" shows three barcode characters. Is this the behavior of OpenType-Features contextual alternates?

@graphicore
Copy link
Owner

Yes, so for this Code 39 font to scan appropriately, you should enclose your code always with two * asterisks symbols (the start and end marking barcode symbol), e.g.: *a * or *a a* in both cases the contextual alternates feature should be triggered, when your software behaves as the OpenType-Spec suggests (or you turned calt on yourself). This works as well in font.google.com, however, their examples are not tailored to show scannable barcodes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants