I just downloaded the beta and have been going through the tutorial. When I tried to compile for "Novel Standard Manuscript Format” it did not create Courier 12-point font with double line-spacing. It was single spaced, Time New Roman (I think) and it looked like 16-point.
I didn’t see this listed yet. Sorry if I missed it.
Hm, someone else can double-check this, but it looks like the problem is just that the box to “override text and notes formatting” (in the formatting pane of compile) isn’t checked by default. If you check that, it compiles properly, although the spacing is set at 1.0, not 2.0, in the default settings.
I clicked that to see if it worked. It did make everything courier 12 but that was it. It wasn’t double spaced and I also noticed that the First chapter begins directly below the author name on the title page.
Comparing it to the Sample Ms in the Research folder these are also different-
-page number at the bottom rather than the top
-chapter title doesn’t appear
I noticed these are still issues in 1.6 and there is no page header option. I like this program but I worry about the final product being flawed and having to fix it after the compile - mostly because I’m afraid I’ll forget to fix it.
Hi, new here! Since this issue was already on the board I thought I would just add to it. I don’t know about any button I’m supposed to click to override the fonts mentioned in a previous post.
When compiling to a PDF in Part 3 of the tutorial, a message came up that didn’t make a lick of sense, unless they are referring to PDF printer drivers.
Go to File > Compile…
Ensure that “Custom” is chosen next to “Format As” (this is the default setting, and exports all of the text in your draft as it appears in Scrivener).
Ensure “PDF” is selected next to “Compile For”.
Click on “Compile”.
Select a location and filename to save the PDF file.
I followed the instructions and this is what happened:
A window with a red round circle and an X came up with the label of “Printers”.
The message says, “Operation could not be completed (error 0x00000705). Windows cannot locate a suitable printer driver. Contact your administrator for help locating and installing a suitable driver.”
In the meantime, the trial version of Microsoft Office Home and Student 2007 came up, of which I’m not a user. I use PolyEdit Lite as my word processor (I love those tabbed panes and it makes it easy to code HTML) and I use Microsoft Works Spreadsheet application for tables.
I also have Microsoft Publisher 2010 installed, which I use on a regular basis, it has the PDF conversion in it which I send to my commercial printer.
I had thought at one time just to uninstall the Word program but didn’t want to take a chance that Publisher wouldn’t work properly if I did. I changed the default setting to open RTF’s to PolyEdit Lite. I haven’t had a use for the DOC or any of the other Word extensions such as Powerpoint. However PolyEdit is compatible and saves DOC’s to Word 97-2003 format.
I’m hoping your application is not dependent upon having Microsoft Word activated??? Because I love Scrivener!!!
Then, Microsoft Word froze up (Scrivener didn’t) and it wouldn’t let me exit. I’m having to exit program with CTRL+Alt+Del. Task Manager managed to get the Word program to close.
It did make a PDF, in spite of the warning. It also puts a # sign where the page breaks were in your tutorial. This shows up in both the PDF’s and the RTF’s.
When I tried:
You can choose from one of the other “Format As” presets to format your draft differently. For instance, try compiling again, just as you did above, but this time choose “Novel Standard Manuscript Format” format (be sure you reselect “PDF” from the “Compile For” list again, as changing the “Format As” option can affect the selected file format). This time, you will find that the draft has been compiled using a Courier 12-point font with double line-spacing.
Word opened and froze up again but the warning message didn’t pop up this time. However, the PDF didn’t include the double line spacing. The FONT isn’t Courier. I didn’t change the default font in the tutorial either. It is still Palatino Linotype.
I tried this twice to make sure it was a repeatable error. It did the same in both instances except the error window didn’t pop up again. The font is still Helvetica and there is no double line spacing in either one.
This is what it says in the Properties Window in Adobe Reader.
On the Description Tab at the bottom where it says Advanced:
PDF Producer: VeryPDF
PDF Version: 1.3 (Acrobat 4.x)
Page Size: 8.5 X 11 in. Number of Pages: 29
Tagged PDF: NO Fast Web View: No
On the FONT tab:
(shows a red cursive lower case “a”) Helvetica
Type: Type 1
Encoding: Standard
Actual Font: ArialMT
Actual Font Type: True Type
T3Font_0
Type: Type 3
Encoding: Custom
Actual Font: T3Font_0
Actual Font Type: True Type
T3Font_1
Type: Type 3
Encoding: Custom
Actual Font: T3Font_1
Actual Font Type: True Type
T3Font_2
Type: Type 3
Encoding: Custom
Actual Font: T3Font_2
Actual Font Type: True Type
T3Font_3
Type: Type 3
Encoding: Custom
Actual Font: T3Font_3
Actual Font Type: True Type
T3Font_4
Type: Type 3
Encoding: Custom
Actual Font: T3Font_4
Actual Font Type: True Type
T3Font_5
Type: Type 3
Encoding: Custom
Actual Font: T3Font_5
Actual Font Type: True Type
T3Font_6
Type: Type 3
Encoding: Custom
Actual Font: T3Font_6
Actual Font Type: True Type
T3Font_7
Type: Type 3
Encoding: Custom
Actual Font: T3Font_7
Actual Font Type: True Type
(shows a red cursive lower case “a”) TT22o00 (Embedded Subset)
Type: Type 1
Endcoding: Custom
(shows a red cursive lower case “a”) TT23o00 (Embedded Subset)
Type: Type 1
Endcoding: Custom
(shows a red cursive lower case “a”) TT24o00 (Embedded Subset)
Type: Type 1
Endcoding: Custom
(shows a red cursive lower case “a”) TT25o00 (Embedded Subset)
Type: Type 1
Endcoding: Custom
(shows a red cursive lower case “a”) TT27o00 (Embedded Subset)
Type: Type 1
Endcoding: Custom
I checked just to see what Adobe did to the fonts in the first exercise and it starts out with Helvetica also; however, all the font information beneath it is different.
Rest assured these issue will be addressed before the final release.
The PDF issue will also be addressed as Scrivener is able to produce PDF itself without Word. We just need to wire this up again as we’ve had issues using professional third party tools to do the conversions via Word on Scrivener’s behalf.
Thank you for taking the time to post.
Lee
Thanks Lee, for easing my mind.
I’m sorry The_Real_Thing, that’s is crazy weird, but it sounds like is will be fixed.
I was hoping for 1.7 to have some of these issues resolved, but-
-Page breaks before chapters are not showing and I manually check over overwrite message and double checked the pg break before is checked off under contents.
-The words “Chapter 1” are not showing- I’m pretty sure that used to show up.
-Paragraph tabs are stripped out and flushed left
-along with the other stuff(no headers/page numbers, etc.)
Hey Lap, thanks!
I found out that the VeryPDF is from Publisher! I haven’t gotten a chance to download the new beta yet. Doing that now.
SP1 I’ve been waiting on a program like Scrivener for about a decade, I can wait a little while longer, LOL!
Good things do come to those who wait! I got a phone call from the editor of my local paper telling me that they accepted my article for publication and he said, “It was very… very… well written!” several times.
It will all work out! 
It sure will. I have noted all these issues as bugs that we will fix.
Lee
That’s great! Congratulations.
I work in the screenplay format (FD8)
when I tried compiling to make a pdf, the page margin shifted RIGHT
The original RTF that I brought in was correctly formatted, and when I copied/pasted to separate into different scenes, those scenes formatted correctly (1 1/2 inch margin on the LEFT side ) so I assumed that the PDF would format correctly, but it did not.
As you can see, it gave a LEFT margin of (I’m guessing) maybe 3 inches, and a RIGHT margin of less than zero which cut off part of the words.
I’ve attached a screen grab to show the problem
Screen grab of a section of the PDF
I can also upload a screengrab of the scene section in scrivener to show it is set at the correct screen margin of 1 1/2 inches
Thanks
Marta
