Hi. I'm unable to get special characters to print on my Boca tickets. I've determined that the font to use is Font 13, but when I put in a special character it seems to print as a different special character. I've been testing this out by adding a special character directly to a ticket design, I haven't yet tested what happens if it is pulling directly from the event itself, so maybe that would make a difference. Has anyone figured out a workaround for this issue? I'm trying to get it to print an é.
This almost literally drove me crazy two years ago. Seriously: there were TASK tickets, tears, and howls of existential despair.
This sounds bizarre, but hear me out: try putting a text box at Row 0, column 0 of your ticket design. I don't think the font matters, but mine is font 3. In the Text Val: box, type:
<TRE><TT4>
...this won't print anything, but for reasons I am too scarred to understand, it resolved the problem for me. Good luck!
C.//X.
That fixed the problem. Thanks so much Chris!!!
Well, full credit has to go to Gemma Hall on the EU helpdesk, to be honest! I asked her about what it is (and why it works). Here's what she wrote:
__________________________________________
When trying to print some special characters, the Boca may print an unexpected character instead. This may be because Font 13 (the only resident fontset to include a full extended character set) is stored in code page 850 while SQL Server is usually collated to code page 1252.
This means, for example, a ® character is stored in the database as ASCII code 174. Instead of the ® character, the ticket may print <<, which is the code page 850 equivalent for ASCII 174.
To remedy this, there is a command to translate resident fontsets to a different codepage which is what I've given you to add to your ticket designs.
...so there you go! ¯\_(ツ)_/¯