$scr_anchor etc.

User avatar
drmajorbob
Posts: 357
Joined: Sun Jul 01, 2012 1:38 am
Platform: Mac

Mon Dec 11, 2017 8:27 pm Post

What could cause this junk in an ePub 2 compile? The screenshot is from iBooks on High Sierra.

[img]
Screen%20Shot%202017-12-11%20at%2014.22.29.png
[/img]

Here's the document that (I assume) is causing it. I'm not overriding the style you see there.

Screen Shot 2017-12-11 at 14.38.26.png
Screen Shot 2017-12-11 at 14.38.26.png (47.08 KiB) Viewed 1301 times
Attachments
Screen Shot 2017-12-11 at 14.22.29.png
Screen Shot 2017-12-11 at 14.22.29.png (576.7 KiB) Viewed 1303 times

User avatar
drmajorbob
Posts: 357
Joined: Sun Jul 01, 2012 1:38 am
Platform: Mac

Mon Dec 11, 2017 8:48 pm Post

Replacing <$title> with the title itself didn't help.

User avatar
KB
Site Admin
Posts: 20902
Joined: Tue Jun 13, 2006 11:23 pm
Platform: Mac
Location: Truro, Cornwall
Contact:

Mon Dec 11, 2017 8:57 pm Post

Hmm, that's some internal code that Scrivener uses while putting things together - it should never make it into the final output. Would it be possible to send me the project and Compile format so that I can test what's causing it and fix it?
Thanks and all the best,
Keith
"You can't waltz in here, use my toaster, and start spouting universal truths without qualification."

User avatar
drmajorbob
Posts: 357
Joined: Sun Jul 01, 2012 1:38 am
Platform: Mac

Mon Dec 11, 2017 9:16 pm Post

To what email address should I send it? The forum is a bit public.

User avatar
drmajorbob
Posts: 357
Joined: Sun Jul 01, 2012 1:38 am
Platform: Mac

Tue Dec 12, 2017 1:07 am Post

I sent it in a bug report with the same title. Hopefully, you'll locate it soon.

User avatar
KB
Site Admin
Posts: 20902
Joined: Tue Jun 13, 2006 11:23 pm
Platform: Mac
Location: Truro, Cornwall
Contact:

Tue Dec 12, 2017 10:47 am Post

Thanks for sending it in. It's caused by the Zapf Dingbats font being used for those stars, which is throwing off the internal code. It's a bug that will have been there for years (in Scrivener 2 as well) but it took this unusual circumstance to trigger it. I've fixed it for 3.0.1, which I'll be releasing later this week.

Thanks again,
Keith
"You can't waltz in here, use my toaster, and start spouting universal truths without qualification."

User avatar
drmajorbob
Posts: 357
Joined: Sun Jul 01, 2012 1:38 am
Platform: Mac

Tue Dec 12, 2017 4:31 pm Post

I had the same circumstance in v2 for a long time, many chapters, and didn't see that bug before ... same circumstance except that now the paragraphs are styled.

My
MystiAnne
Posts: 2
Joined: Sun May 13, 2018 9:05 pm
Platform: Mac

Sun Sep 30, 2018 6:39 pm Post

I'm seeing this error for every chapter title (I am using an odd font, 28 Days Later, but it was doing this even before I created a style for that). I just converted a s2 project to s3. The compile for Print (PDF) doesn't do this.

The actual title text does print after the messed up code:

I don't know what to try to fix it.

{$SCR__ANCHOR::doc3$END__SCR__ANCHOR}Contents

docX increments for every chapter. "Contents" is the title of the front matter file, but it does this at the start of every file, whether front matter or chapter, except the cover.