Re: [xmpie-users] uProduce 6.0.2 and Font Warnings

[Guillaume Besnier]

Q1: do you think the message is relevant? (does this font already exist somewhere on your system)
Q2: is the output file ok, despite there is a message?
Q3: as fara as I can remember, AIS 6 comes with a font-related patch; do you know if this patch was installed on your server(s)?

-------- Message original --------
Sujet: [xmpie-users] uProduce 6.0.2 and Font Warnings
De : Ed Wong <ew...@schielegroup.com>
Pour : xmpie...@googlegroups.com
Date : 17/12/2012 17:52

Previous to updating to 6.0.2, if I was missing a font I would get a warning. Other than that I had no problems with fonts.

Something has changed now and I'm getting font warnings all the time. "xxxxx.otf will not be used because it either invalid or its font definition already been defined by one of the system font file or another campaign font file."

This takes me back many years when font handling on a windows server was a pain and someone would dump a font into the system folder. Since uProduce 4.xx I've never had to dump a font into the system folder. Everything worked the way it should and you only received font warnings when you where missing a font. In my opinion, this was the best way for fonts to work.

Now thats all changing and I have to question why because now you would have to remove a font from the system folder, which may not be a wise thing to do.

Anyone have any thoughts on this?

Thanks,

Ed

--
You received this message because you are subscribed to the Google Groups "XMPie Interest Group" group.
To view this discussion on the web visit https://groups.google.com/d/msg/xmpie-users/-/o8rHSkXeGcUJ.
To post to this group, send email to xmpie...@googlegroups.com.
To unsubscribe from this group, send email to xmpie-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/xmpie-users?hl=en.

[Ed Wong]

Hi Bill,

A1: Yes the font is in the C:\windows\fonts folder.

A2: Output file is okay.

A3: The only relevant installer I see is XMPie uProduce Server Installer. I see 2 patches for Adobe InDesign. Tech support sent me this message: "With the 6.0.2 version, fonts are handled a little differently. You may recall with earlier version that a fix would be to copy the fonts from the campaign fonts folder into the system fonts folder. That now causes a problem. In XMPie 6.0.2, if a font resides in more than one location between the system fonts folder (C:\windows\fonts) the Adobe fonts folder (program files\adobe\adobe indesign cs\fonts -or- program files\common files\adobe\fonts) and the campaign fonts folder, XMPie will not be able to use that font. 
I recommend removing the font from the system and adobe fonts folder and only having the fonts you are using for that campaign in the campaign fonts folder in uProduce. This should remove the font error."

Removing font from the C:\windows\fonts  folder has me a little nervous. Which is why I'm asking for a second opinion.

Should I be asking tech about a font-related patch?

Again, I had no font problems on our previous server with uProduce 4 and 5 or our new server with version 5.3.2. Now that the new server is updated to 6.0.2 Build 6187, problems.

Thank you for your time,

Ed

[Mark Cini]

Hi Ed,

The way I interpret that warning is quite simply, if the same font exists in the system fonts and campaign fonts directory it will use the system font. It's just a warning telling you that it's doing so. It's not an error, and as you say the output is correct.

So if it's the same version of font in the system font and campaign font directory you have nothing to worry about. 

If you did for some reason want to force it to use the campaign font instead of the system font, then you'd have to remove the system font if it also exists.

Regards,

Mark.

To view this discussion on the web visit https://groups.google.com/d/msg/xmpie-users/-/VsnTYaxwzFUJ.

[Ed Wong]

Hi Mark,

Thanks for your thoughts on this, I appreciate it.

I think what gets me is that for 3 years I've had to address all font warnings because it usually meant that a font was missing. 80 percent of my jobs run clean with no warnings. So I'm conditioned to read all warnings and react. There are warnings that I know will never go away do to the job at hand. Perhaps I need to force a field in the schema to be a number instead of text because of something I'm doing in the QLingo.

So it just feels to me like there did not need to be a change because it was working so well. But i'm sure there is a good reason why the change occurred. It never occurred to me that someone else might be having problems.

Thanks again,

Ed