[OPEN-ILS-GENERAL] Printing in Evergreen

[Dan Scott]

On Wed, Aug 08, 2012 at 12:49:06PM -0700, Christine Campbell wrote:
> On Tue, Aug 7, 2012 at 3:39 PM, Dan Scott <dan at coffeecode.net> wrote:
> 
> >
> > No problem, Christine. I should also note in reply to one of your other
> > messages that we were originally on something close to 1.6 (before 1.6
> > was actually released), so I can confirm that the Dymos worked there,
> > too. I believe that the library settings for font family, size, etc were
> > introduced in the 2.0 release, so hopefully you'll find them there.
> >
> 
> Hi Dan,
> 
> I had a look at changing font type in Admin/Local Administration/Printer
> Settings Editor, but I could not find a way to change it. We are using
> 2.0.10, but I'd assume that it should still work. I think we are still

First up, 2.0.x is no longer officially supported by the community, so
that's a big caveat.

> going to go ahead with testing a Dymo 450 based on the information shared
> here and a bit of assessing it outside the list. It looks like we can
> probably set the font for the printer, but it would be a lot better for our
> needs if we could print in Arial straight from Evergreen.

The library settings are definitely there in 2.0, though; you're looking
for "Cataloging: Spine and pocket label font family" in particular.
 
> Can anyone confirm whether they've managed to change font type in
> particular in Evergreen itself?

I'll gamely say that yes, we have managed to change font type in
particular in Evergreen itself, using only the library settings in Admin
-> Local Administration -> Library Settings Editor. No more hardcoded
style sheets for us.

However, as I mentioned in my previous post, the default font type is
set to "monospace" at the consortial level, and that seems to override
any child library settings (at least in our experience with Evergreen
2.3, and there's no going back in time for us to test with 2.0 now). So
- you may want to either set the font family at the consortial level if
you want the same setting at all libraries, or delete it at the
consortial level and enable individual libraries to set their own
preferences.