25th MARCH - LEE"S UPDATE - FINAL BETA RELEASED

LAP · March 29, 2011, 12:00am

We’re currently addressing the following issues raised:

Revisiting 0 byte zip file again; however, please read me previous comments regarding 7Zip.
More detail on the zip issue:

[quote]
Backup To Zip Problem - #2 by wfence]

M.R. Comments:

LINUX Feedback from gplauche

StaceyUK’s feedback:

BUG 1: ODT missing from drop down compile menu. I first notices this in beta 020 and it’s still there in 021.

BUG 2: Inspector displaying incorrect information. Showing information from a document not currently selected in the binder. Padlock in inspector is unlocked. Unfortunately I cannot reproduce this bug consistently as it only occurs intermittently.

QUESTION: Not sure this is a bug but something to consider when optimizing.

When I compile a document directly within Scrivenrer, the resulting file file size is 12mb. However, if I compile the same document as an RTF and then save as a PDF within open office the file size is 76kb. When I open the RTF and save as a PDF in Word 2007, the file size is similar to the one produced by direct compile.

Why the discrepancy in file sizes when producing the same document as a PDF? I can send you copies of the different PDFs if you need them.

Clive’s comments:

The next thing is the screen, which is where I started noticing. A globby-for-old-screens-font like Verdana won’t show issues easily – it was designed to hide them, but is not necessarily very pretty on print or on various screen sizes. Calibri which comes with various MS things these days like OneNote is beautifully clear on screen, also by design, when you have modern ClearType etc. as Win or Adobe provides since XP times, and Calibri does have issues in Scrivener – that’s what I noticed.

Capital letters tending to separate from their word enough that you think you’ve got an extra space was what caught the eye. There is also un-evenness in long passages which catches up the eye. I am hoping it will be very simple to one-stop correct those too. Again, we are fully agreed in not vieing for typesetting tool results at all - just a nice screen, hoping it is easy to have like OneNote for example provides. Patience and understanding of course if something roadblocks having that just fall out of QT. But see the next 3) - persistence this evening may have illuminated a simple solution.

[had to edit this in] Well, the Compile for Print. This is where I am getting wide tracking (general letter spacing) in the results printing to Adobe Acrobat. This looks to occur particularly where there are not kerning pairs, thus the somewhat odd appearance of a paragraph of text. For example, I am looking at just the two words ‘Giving adventure’, and the a-d space is such that this phrase looks like one word, while the v-e is definitely kerned close. Blown up so I can see what it prints as.

This may point to the simplicity of just needing one-time setting of a tracking parameter for QT, since it looks like kerning itself is handled; thus quick fix.

And that it may be exactly the same problem as the item 2) screen look, thus a single tracking parameter in QT for both. Crossed fingers.

Amir’s comments: