Font.properties help needed
531146Aug 31 2006 — edited Aug 31 2006I have a USA client with several Reports that use fonts “OCR A Extended” and “Wingdings 3”. The OCR A Extended font is being used for a scanline by OCR scanners to call up invoices. They MUST use that font or the scanners don’t work. They are also using specific angled arrows from the Wingdings 3 font set. I can’t get either one to work in the Reports.
I have mapped both OCR A Extended and Wingdings 3 to dialoginput in the registry.dat file.
Getting the correct values into the font.properties file is the part that I’m having problems with. I’m trying to do this by following other examples I’ve seen, but I’m not hitting the correct combination.
I have added:
dialoginput.3=OCR A Extended,ANSI_CHARSET
dialoginput.4=Wingdings 3,DEFAULT_CHARSET
1) Do I need to add a “NEED_COVERTED” to either one of those lines? I’m guessing no because this is plain Windows US/English, nothing foreign.
2) Do I have the proper _CHARSET for both of those lines?
I have also added:
filename.Wingdings_3=WINGDNG3.TTF
filename.OCR_A_Extended=OCRAEXT.TTF
3) Do I need to do that or should I take it out?
From what I’ve read, if I use a NEED_COVERTED then I also need a:
fontcharset.dialoginput.3=…..
fontcharset.dialoginput.4=…..
But I have NOOO clue what needs to follow the “=” sign.
It is mission critical that I get both of these working, especially the OCR A Extended font. I thank you in advance!