Home → Scrivener 3 Beta →

Another Compile buglet, or is it me?

• Edit

xiamenese

Jan 31, 2017 @ 03:49 PM

I attach a mini project where, in the second line of the first paragraph, there is a web link which is in "italics/emphatic". On compiling to RTF, and opening it in NWP, the words of the link are not there, but on the other hand, all the following text is marked as "emphatic" no matter what font variant it is in.

Can anyone reproduce this?

Mark

• URL_test.scriv.zip 31.9 KB
• URL_test.rtf 4.21 KB

1. 1 Posted by matsgz on Jan 31, 2017 @ 04:32 PM

   

   Curiouser and curiouser … If I open your project and export the files as rftd, I get a folder with four text documents, perfectly formated incl. the web link that opens as expected. If I compile the content of the project I get what looks like a rftd file that won't open with Text Edit (message that it might be corrupted or something). Also the rftd file you enclosed won't open (same message). Strange!

   Mats

   • Edit

2. 2 Posted by matsgz on Jan 31, 2017 @ 05:20 PM

   

   BTW, the guinea fowl looks fantastic

   • Edit

3. 3 Posted by xiamenese on Jan 31, 2017 @ 06:12 PM

   

   I compile to RTF, not RTFD. It opens in Nisus Writer Pro without problems, just the missing words and the spurious "Emphatic" marking.

   Does TextEdit open RTFD files?

   If people want, I can post my compile set-up ... NB I use Adobe Garamond Pro throughout, but that can be changed.

   • Edit

4. 4 Posted by matsgz on Jan 31, 2017 @ 08:33 PM

   

   Tried compiling it in RTF. Same result. Document doesn't open.

   Furthermore, I've noticed that there are no problems compiling or exporting the three "enclosed" documents (Ingredients, For the garnish and Method) in whatever format.

   The problem is with the enclosing document (Guinea fowl Pays d'Auge).
    
   If I export it as rtfd, alone or with the others, I can open it, but if I export it as rtf I can't.

   After compiling it, whether in rtf or rtfd, individually or the whole draft, I end up with a document I can't open.

   Tried compiling documents from the tutorial in similar ways, with no problem.

   There's something rotten in the state of the fowl.

   Mats

   • Edit

5. 5 Posted by RZ on Feb 01, 2017 @ 09:31 AM

   

   Remove the URL and formatting from the URL_test.rtf file above (by changing the extension to .txt, opening the file in TextEdit, and then changing the extension back to .rtf), and the file opens fine as .rtf with all the formatting and words in place. So the problem is with the formatting and/or URL.

   I suggest removing both in the Scrivener project and doing a test compile. If that works, add back the URL and do another test compile. If that works, add back the formatting and test again. Should show if the problem is line, project, or application specific.

   Looking at the .rtf file as plain text, and given Mark's comments about missing text and incorrect formatting after the URL, I suspect the issue is with the /i formatting rather than the URL itself.

   • Edit

6. 6 Posted by xiamenese on Feb 01, 2017 @ 03:11 PM

   

   When I remove the URL from the project and re-instate the italics/emphatic on the words in question, it compiles perfectly for me—well, that is apart from the question of getting the various heading styles apart from the first to go across. I'll try re-instating the URL to see what happens.

   I don't know why Mats can't get it to compile to RTF, unless it's something to do with different compile settings.

   Mark

   • Edit

7. 7 Posted by xiamenese on Feb 01, 2017 @ 05:30 PM

   

   OK. It seems that it was some sort of gremlin to do with the URL and the italicisation, which had come when the project was updated to v. 3 format. By typing the sentence anew and deleting the old version, then re-instating the URL, it compiled properly with the text and the hyperlink intact when opened in NWP, TextEdit, Mellel and NeoOffice—with the exception that the latter two impose their own tab-stops on the ingredients list.

   I'll have to go through the rest of the main project—about 60 pages currently—to see if there are any other gremlins.

   I'm uploading a zip with the new version, the resulting RTF and also my compile settings file in case anyone wants to look into it further.

   Mark

   • Url_test_2.zip 55.1 KB
   • Edit

8. 8 Posted by Ioa on Feb 07, 2017 @ 12:14 PM

   

   I can reproduce the first condition, or something similar, out of the box with no preexisting data and using a generic link:

   1. In a new blank project type "Test links with emphasis style."
      
   2. Select "links with emphasis" from second sentence.
      
   3. Edit/Add Link... and paste "http://www.duckduckgo.com", hit Return.
      
   4. Press Shift-Cmd-Y, select the Emphasis style. (Link should already be selected; reselect if not.)
      
   5. Compile, changing nothing but the file type to RTF.

   Compiled result will be Test style.links with emphasis, with the linked phrase moved to the end of the file (which is not far in this case, but if this were a 5,000 word document the "links with emphasis" phrase would be at the very end of it).

   The second symptom is that although the text remains linked, the hyperlink styling is removed, and interestingly this will be true of all other links in the document. If you run additional tests with unstyled links in subsequent paragraphs, they will lose their styling as well. Annotate the test phrase we created above out, recompile, and everything will work as expected.

   Third symptom is the fact that Emphasis as a style is applied everywhere, even though the formatting for that style is not.

   • Edit

9. 9 Posted by keith on Feb 07, 2017 @ 02:56 PM

   

   This is caused by the link messing up the temporary codes I insert during export to get the characters styles working. This should now be fixed for the next update.

   • Edit

10. keith closed this discussion on Feb 07, 2017 @ 02:56 PM.