Printing Via Commander Produces Incorrect Fonts S’abonner

0
Avatar
Legacy Poster

BarTender Version 9.4 SR3 Enterprise Automation is being used.

 

Printer being used is a Zebra 140XiIII Plus

 

The problem we are experiencing relates to label formats printed via Commander. The symptoms are that in the BT label formats being used that when printed via Commander the original TTF fonts used in the BT format are being replaced by a standard font, it looks like Arial.

 

When the label format is printed manually the font styles are correct, it is only when using Commander that the problem occurs.

I have checked in the Print options on the BT format under the Performance tab and changed, the following radio buttons

 

Use Settings for this format only

Warn when using True Type Fonts

 

 

To create the label objects in the BT format I am using a simple text file as the database, with pipe delimiters between fields:-

 

Spray Carnation Posy|0.00|505394790226|30 APR|SC:SL33

 

 

 

The content of the trigger file is as follows:-

 

%BTW% /AF="C:\Automation\Formats\3digitPrice_ie250.btw" /D=<Trigger File Name> /PRN=PNP74 /R=3 /P /C=2 /DD /MediaHandling=Action=Pause;Occurrence=AtEndOfPrintJob
%END%
Spray Carnation Posy|1.50|5018374054982|04 APR|SC:SL 33

 

All other functions of the Commander process seem to be working fine working fine , it is just the fonts issue I cannot resolve

 

Can anyone help please?

 

Thanks

 

 

4 commentaires

0
Avatar
Ian Cummings
Modérateur
Actions pour les commentaires Permalien

It sounds like the Windows fonts in the label design is getting substituted for a device font.  Have you since checked the label design to see if the "Substitute with best matching printer font" checkbox for the text objects in question has been ticked?  Certainly, what you've done for the settings for the format concerning the font warning should prevent the fonts getting substituted when printing the document under a different user account, but you will need to go back to the label in order to fix the font substitution issue.  Be sure to then save the label and have Commander pick up the new file by restarting detection.

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

Hi,

 

Regarding all of the TTF fonts within the label design the tick box Substitute Best Matching Printer Font was unticked in all cases.

 

One thing I didn't mention in my previous post, the Commander process is running as a Windows Service on a 2008 R2 Server, would that have any bearing on the problem?

 

Thanks

0
Avatar
Ian Cummings
Modérateur
Actions pour les commentaires Permalien

Well, if you run Commander as an application, and not as a service, does it make a difference.  FYI: It is best to set the account for the task to use in the Commander service logon, and not in the BarTender command handler in Commander.

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

Hi Ian,

 

Sorry for the delay in responding!

 

I have run Commander as an application and all aspects of the label are correct and the fonts are correct. When I run as a service however the fonts revert to a standard font again. I have been through the Commander troubleshooting guide and have tried the ones relating to running as a service. The one command that wouldn't run was registering the Commander service "CmdrSrv /register" it just hangs after hitting enter.

 

I am running the Windows Commander service under the same domain account as I am using to logon to the server (2008 R2). Also the I have used the same domain account for the BarTender command handler user login.

 

I am not sure where to go next with this problem as it does appear as some sort of permissions type of issue.

 

If you need any screen shots of the setup, please let me know?

 

Many Thanks

Vous devez vous connecter pour laisser un commentaire.