<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>
<blockquote type="cite">How did the bitmaps import / link?</blockquote>
Once I moved them out of the art directory and into the same
directory where the idml file lived, they just worked. There are a
few images that are not displaying, but I haven't looked closely
yet to see if it's because the files are missing or if something
else is amiss.<br>
</p>
<p>
<blockquote type="cite">Did you do any tests of PDF export yet?</blockquote>
I didn't, but I just tried it. The PDF is available at
<a class="moz-txt-link-freetext" href="https://drive.google.com/file/d/1TcwbjfMbPhpFpE3N18F-PJs_fxALaX3d/view?usp=sharing">https://drive.google.com/file/d/1TcwbjfMbPhpFpE3N18F-PJs_fxALaX3d/view?usp=sharing</a>.
I haven't made any tweaks to the layout, so some things appear a
little funky at the moment.</p>
<p>Kathy<br>
</p>
<br>
<div class="moz-cite-prefix">On 01/03/2018 12:54 PM, Rogan Hamby
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAMwaE4JheNd1DY6-VGARQBCP1pLs-aXqq=D8xUs8349v5HjyeQ@mail.gmail.com">
<div dir="ltr">Yeah, that's not too bad of an indicator.
Different dev communities have different expectations of the dev
version. How did the bitmaps import / link? Did you do any
tests of PDF export yet?</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Jan 3, 2018 at 12:51 PM, Kathy
Lussier <span dir="ltr"><<a
href="mailto:klussier@masslnc.org" target="_blank"
moz-do-not-send="true">klussier@masslnc.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>Yeah, well, that's why I mentioned 'pitfalls' in the
2nd option because I'm more concerned about them
happening with a development version than the stable
branch. Here is how their development community
describes the release:</p>
<p> </p>
<blockquote type="cite"><span
style="color:rgb(71,71,71);font-family:Karla,Arial,sans-serif;font-size:14px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(247,240,228);text-decoration-style:initial;text-decoration-color:initial;display:inline!important;float:none">As
of version 1.5.1, we consider the development branch
reasonably stable, so it can be used for serious work
by users who accept that not all<span> </span></span><em
style="box-sizing:border-box;margin:0px;padding:0px;border:0px;font-size:14px;vertical-align:baseline;font-style:italic;color:rgb(71,71,71);font-family:Karla,Arial,sans-serif;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">new</em><span
style="color:rgb(71,71,71);font-family:Karla,Arial,sans-serif;font-size:14px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(247,240,228);text-decoration-style:initial;text-decoration-color:initial;display:inline!important;float:none">features
are already working perfectly. Features already
available in the officially stable version will work<span> </span></span><em
style="box-sizing:border-box;margin:0px;padding:0px;border:0px;font-size:14px;vertical-align:baseline;font-style:italic;color:rgb(71,71,71);font-family:Karla,Arial,sans-serif;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">much</em><span
style="color:rgb(71,71,71);font-family:Karla,Arial,sans-serif;font-size:14px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(247,240,228);text-decoration-style:initial;text-decoration-color:initial;display:inline!important;float:none">
better in 1.5.1+, though.</span></blockquote>
I'm guessing idml support is one of the new features, but
if importing IDML files is one of the potential issues, I
assume it would pop up as a problem early on.<span
class="HOEnZb"><font color="#888888">
<p>Kathy<br>
</p>
</font></span>
<div>
<div class="h5"> <br>
<div class="m_-7226838590640347578moz-cite-prefix">On
01/03/2018 12:44 PM, Rogan Hamby wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">I have some concerns about using a
development version. Do you have a sense of how
stable it's considered to be?</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Jan 3, 2018 at
12:40 PM, Kathy Lussier <span dir="ltr"><<a
href="mailto:klussier@masslnc.org"
target="_blank" moz-do-not-send="true">klussier@masslnc.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<p>Hi all!</p>
<p>Thanks for sending this along Rogan. I
finally had a chance to look at using
Scribus with Rogan's files today. The
development version of Scribus (1.5.3)
seems to handle idml file whereas the
older, 1.4.x version of Scribus did not.
The file does not import perfectly: fonts
needed to be changed and we would need to
adjust some of the layout, but I think I
could turn it into something workable. <br>
</p>
<p>There are two issues to consider then:</p>
<p>- The original reason this topic arose
was because of concerns that the font size
was small, making it difficult to read the
annual report. Last year's report is
available at <a
class="m_-7226838590640347578m_85198731414163019moz-txt-link-freetext"
href="https://evergreen-ils.org/wp-content/uploads/2017/03/Evergreen-Annual-Report-2016-Print-Version.pdf"
target="_blank" moz-do-not-send="true">https://evergreen-ils.org/wp-c<wbr>ontent/uploads/2017/03/Evergre<wbr>en-Annual-Report-2016-Print-<wbr>Version.pdf</a>
if anyone wants to look at it for context.
This could be addressed by increasing the
font size in the current layout, which
will necessarily reduce the amount of
content we can include, or by switching to
a larger booklet. However, the issue with
switching to the larger booklet, as Rogan
noted below, is that it requires a lot of
labor time. Rogan has already put in hours
to create the current layout, and time is
valuable. <br>
</p>
<p>- The other issue is that the current
report is done in Adobe InDesign, which,
due to cost and OS support, is not
available to most of us. This means that
the work of creating the annual report
always falls on Rogan's shoulders. By
creating it in Scribus, which is open
source, we might be able to divide up the
work so that two or three of us are
helping to put the report together. Even
if we didn't change the layout of the
report, it might not be a bad idea to
consider this change so that we can divide
and conquer. <br>
</p>
<p>We have a few options.<br>
</p>
<p>- We could decide to go with the current
format (with or without font size changes)
for this year and look at moving to
Scribus for next year's report. If we
start the work in the spring, it gives us
time to troubleshoot any issues in time
for the 2018 report.</p>
<p>- I would be willing to commit to working
on transferring the file to Scribus and
the larger size before the February
meeting. This would give us layout to
work with over February as we plug in the
content. However, I can't guarantee that I
won't find pitfalls along the way. If the
pitfalls are too large, we would need to
go back to the InDesign booklet, which
would give Rogan less time to work on this
year's report on his own<br>
</p>
<p>- We could also decide to keep things as
they are for now as it has been successful
in generating a nice annual report.</p>
<p>I'm sure there are other options we can
discuss during today's meeting.</p>
<p>Thanks Rogan for all of your work on
this!<br>
Kathy<br>
</p>
<div>
<div class="m_-7226838590640347578h5">
<p><br>
</p>
<p><br>
</p>
<div
class="m_-7226838590640347578m_85198731414163019moz-cite-prefix">On
12/29/2017 07:47 AM, Rogan Hamby
wrote:<br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div class="m_-7226838590640347578h5">
<div dir="ltr">Another quick follow
up. In looking at moving the work
on the annual report to Scribus
Kathy and I both did some research
on migrating the file format. My
experience has been that the print
layout world of software is
fundamentally different in terms of
exchanging data between applications
then graphics and this is bearing
out to be true. Both of us found
the same set of suggestions and
neither are working for me in a way
that would be useful. The
postscript export is per page not
document and does not export
embedded data. The xml output is
not parseable. I'm still waiting to
see if Kathy had any better luck but
at this point that does not look
like a viable option to me.</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Nov
14, 2017 at 7:39 AM, Rogan Hamby <span
dir="ltr"><<a
href="mailto:rogan.hamby@gmail.com"
target="_blank"
moz-do-not-send="true">rogan.hamby@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div dir="ltr">Good morning,
<div><br>
</div>
<div>There has been a little
discussion off list about
printing of the annual
report. Last year we
printed 250 saddle stitched
trimmed to bleed with a
cover at 8.25x 5.75 with
100# gloss at full color.
Terri, at Equinox, was kind
enough to get me an updated
quote for this year from the
same printer we used last
year and an estimate for
increasing the book size.
The reason for the increase
in the book size is that
there have been questions
about increasing the font
size of the report without
decreasing the amount of
content. The only way to do
that is to increase the
paper size. </div>
<div><br>
</div>
<div>A new printing at last
year's specifications is
$985.55</div>
<div><br>
</div>
<div>Increasing the paper size
to 8.5 x 6 (which is a very
small increase) jumps to
$1,228.60. The cost has to
be considered of course but
it's not my greatest
concern.</div>
<div><br>
</div>
<div>While I'm very
sympathetic to the access
issues it's necessary to
point out that we have
attempted to keep labor time
under some constraints by
reusing the same basic
layout. Print layout
software isn't quite like
responsive web design and
you can't just tell it a new
paper size and have
everything re-adjust. If we
do go the route of a new
paper size we need to
finalize this very soon and
it will be a great deal of
labor to implement. </div>
<div><br>
</div>
<div>Just to make it clear I
am _not_ in favor of doing
this. We produce a web
friendly PDF so that it can
easily be scaled and a
limited print run for the
conference. We can
certainly increase font
sizes an average 25% but I
don't think it will make for
an attractive product.
However, I would much rather
do that than change the
printed format of the
report. </div>
<div><br>
</div>
<div><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset
class="m_-7226838590640347578m_85198731414163019mimeAttachmentHeader"></fieldset>
<br>
</div>
</div>
<pre>______________________________<wbr>_________________
evergreen-outreach mailing list
<a class="m_-7226838590640347578m_85198731414163019moz-txt-link-abbreviated" href="mailto:evergreen-outreach@list.evergreen-ils.org" target="_blank" moz-do-not-send="true">evergreen-outreach@list.evergr<wbr>een-ils.org</a>
<a class="m_-7226838590640347578m_85198731414163019moz-txt-link-freetext" href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-outreach" target="_blank" moz-do-not-send="true">http://list.evergreen-ils.org/<wbr>cgi-bin/mailman/listinfo/everg<wbr>reen-outreach</a><span class="m_-7226838590640347578HOEnZb"><font color="#888888">
</font></span></pre>
<span class="m_-7226838590640347578HOEnZb"><font
color="#888888"> </font></span></blockquote>
<span class="m_-7226838590640347578HOEnZb"><font
color="#888888"> <br>
<pre class="m_-7226838590640347578m_85198731414163019moz-signature" cols="72">--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
<a href="tel:%28508%29%20343-0128" value="+15083430128" target="_blank" moz-do-not-send="true">(508) 343-0128</a>
<a class="m_-7226838590640347578m_85198731414163019moz-txt-link-abbreviated" href="mailto:klussier@masslnc.org" target="_blank" moz-do-not-send="true">klussier@masslnc.org</a>
Twitter: <a class="m_-7226838590640347578m_85198731414163019moz-txt-link-freetext" href="http://www.twitter.com/kmlussier" target="_blank" moz-do-not-send="true">http://www.twitter.com/kmlussi<wbr>er</a></pre>
</font></span></div>
<br>
______________________________<wbr>_________________<br>
evergreen-outreach mailing list<br>
<a
href="mailto:evergreen-outreach@list.evergreen-ils.org"
target="_blank" moz-do-not-send="true">evergreen-outreach@list.evergr<wbr>een-ils.org</a><br>
<a
href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-outreach"
rel="noreferrer" target="_blank"
moz-do-not-send="true">http://list.evergreen-ils.org/<wbr>cgi-bin/mailman/listinfo/everg<wbr>reen-outreach</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
<pre class="m_-7226838590640347578moz-signature" cols="72">--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
<a href="tel:%28508%29%20343-0128" value="+15083430128" target="_blank" moz-do-not-send="true">(508) 343-0128</a>
<a class="m_-7226838590640347578moz-txt-link-abbreviated" href="mailto:klussier@masslnc.org" target="_blank" moz-do-not-send="true">klussier@masslnc.org</a>
Twitter: <a class="m_-7226838590640347578moz-txt-link-freetext" href="http://www.twitter.com/kmlussier" target="_blank" moz-do-not-send="true">http://www.twitter.com/<wbr>kmlussier</a></pre>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
<a class="moz-txt-link-abbreviated" href="mailto:klussier@masslnc.org">klussier@masslnc.org</a>
Twitter: <a class="moz-txt-link-freetext" href="http://www.twitter.com/kmlussier">http://www.twitter.com/kmlussier</a></pre>
</body>
</html>