Printing special characters on BOCA tickets.

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 é.

  • Hey Liz,

    We print special characters all the time and one thing that trips us up sometimes is the Windows' Printer Settings.  If you go to your BOCA printer in the Windows' Printers and Scanners.  You need to get into Printer properties.  And then in that window there is 'Font Selection'.  It needs to be on Multilingual - Latin 1 (or perhaps some other ones, but United States doesn't work for us and Multilingual does).  Hoping this helps! If not, post again and I will see if I can think of anything else.

  • 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! ¯\_(ツ)_/¯

    C.//
    X.

  • We are trying to print š, I've applied a different font properties, but it keeps reverting to the default so the printer ignores š completely.

    If anyone has any suggestions I'd would greatly appreciate it.

    Thanks

    Sussan