<div class="gmail_quote">On 27 February 2011 16:37, John Ghormley KJ4UFG <span dir="ltr"><<a href="mailto:kj4ufg@sera.org">kj4ufg@sera.org</a>></span> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div class="h5">Thanks, Craig. I am not familiar with the building svn versions, but I may</div></div>
try that. However, I completed the job using the Story Editor without any<br>
problems, whatsoever. That lends credibility to my assertion that in-frame<br>
editing is the problem. So, since I have, and do, use the Story Editor in<br>
several past versions without any difficulties and a great deal of ease, I<br>
think I will stay with it and see if there is an RC2 that fixes the in-frame<br>
editing problem, or a stable 1.4.0 release that may do the same. But, iMO,<br>
RC1 falls somewhat short of a releasable new stable version.<br></blockquote><div><br></div><div>That's because RC means release candidate. This usually involves (I'm not sure how scribus handles this) a feature freeze, meaning that no new features are incorporated into the code base and a focus to search for bugs. RC-versions are usually not intended to be used in production. They are released however so that people can take a look and hopefully find bugs. </div>
<div><br></div><div>You seem to have found one. Congratulations ;-).</div><div><br></div><div>Oh, BTW: signal #6 is SIGABRT (<a href="http://en.wikipedia.org/wiki/SIGABRT">http://en.wikipedia.org/wiki/SIGABRT</a>). It tells you that the program has aborted. If there is no other message, that's rather not helpfull. </div>
<div> </div><div><br></div><div>Jan</div></div><br>