Formatting Titles and contents table in V3

Ma
Manni
Posts: 71
Joined: Mon Dec 12, 2011 10:18 am
Platform: Mac + Windows

Thu Nov 23, 2017 7:43 pm Post

First of all congratulations for the release of V3 :)

Also I'll start with a huge thanks for implementing a feature I requested a long time ago, which is the ability to format words;/parts of a title using markdown.

This works great, but I ran into a few problems while implementing this in an existing book:

- While this produces the expected result when compiling, i.e. the formated words in the titles are properly formatted, if one generates a table of content, markdown will appear in the titles in the table of contents, which is not desired.
For example, "This is my *wonderful* title" will produce the correct title in the compiled file "This is my wonderful title", but in the title of contents the title will appear as: "This is my *wonderful* title". So I have to reformat these manually in the TOC.
- When checking "generating an HTML table of contents", only the main chapter headings are listed (as in V2) so I use a "replace" in my custom format preset to replace the <$p> in the TOC with nothing when compiling for ebook. In V2, this works great and gets rid of everything between the end of th e title and the question mark that appears if you leave the <$p> in the content table (works great for print, but not for e-book). In V3, the question mark disappears but it looks like each tab appears as a visible underlined section.
- There is still an (already reported in V2) bug/limitation in the generated table of contents that means that with short titles, the single "tab" automatically generated isn't enough to align the page number to the right, So I have to manually add one tab before the <$p> for these short titles to get the page number vertically aligned for print/PDF. As a result, when complied for ebook, the underlined section after the title is twice as long as when only the initial tab is present.

It would be great if these issues could be fixed. If the above doesn't make sense, please let me know and I'll take some screenshots.

Otherwise really enjoying exploring V3, but right now my priority is to get my mobi and epub files for existing book re-compiled and ready, as I'm looking forward to seeing the improvement in the Kindle preview.

Keep up the good work! 8)

Ma
Manni
Posts: 71
Joined: Mon Dec 12, 2011 10:18 am
Platform: Mac + Windows

Sun Nov 26, 2017 12:16 am Post

Any chance to get a reply on this? Are these issues aknowledged and will they be fixed?

Thanks!

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

Sun Nov 26, 2017 12:51 am Post

Hi,

Sorry, I somehow missed this. Thanks for the kind words. The first issue sounds like a bug which I’m going to look at tomorrow. The other issues don’t sound like bugs but I’ll go through why once I’ve double-checked. If you don’t hear back in a couple of days, please bump the thread - it won’t be because I’m ignoring you but just because we’re really busy.

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

Ma
Manni
Posts: 71
Joined: Mon Dec 12, 2011 10:18 am
Platform: Mac + Windows

Mon Nov 27, 2017 3:38 pm Post

Thanks Keith. I'll bump this up if I don't hear from you in the next couple of days...

Ma
Manni
Posts: 71
Joined: Mon Dec 12, 2011 10:18 am
Platform: Mac + Windows

Thu Nov 30, 2017 11:14 pm Post

Hi Keith,

Just bumping this as requested...

Ma
Manni
Posts: 71
Joined: Mon Dec 12, 2011 10:18 am
Platform: Mac + Windows

Sat Dec 02, 2017 2:53 pm Post

Another bump for Keith...

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

Sat Dec 02, 2017 6:19 pm Post

Hi,

I can't reproduce asterisks appearing in titles in the table of contents. Could you possibly post a sample project demonstrating this?

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

Ma
Manni
Posts: 71
Joined: Mon Dec 12, 2011 10:18 am
Platform: Mac + Windows

Sat Dec 02, 2017 7:10 pm Post

Hi Keith,

You are correct regarding the asterisks,

I did some tests starting from scratch and there are no asterisks in the result from compile.

However, the part that should be in italics doesn't appear in italics in the TOC, even if the asterisks are correctly stripped. The part in italics is only properly formatted in the content itself, not in the table of contents.

Also, each tab in the title inserted in the TOC - either automatically when generated or manually to make up for short titles, I created one such title called "short" to illustrate the issue - becomes a series of spaces underlined when compiled for Kindle, which doesn't look good (see MOBI sample). If you don't add a manual tab for short titles in the generated TOC, then the page number isn't aligned when compiled for MS Word/PDF (see PDF sample).

I attach my test project (along with the resulting PDF and MOBI) which reproduces all these issues.

Hope this helps!
Attachments
test.mobi.zip
(6.29 KiB) Downloaded 39 times
test.pdf
(30.67 KiB) Downloaded 27 times
test.scriv.zip
(258.17 KiB) Downloaded 44 times

Ma
Manni
Posts: 71
Joined: Mon Dec 12, 2011 10:18 am
Platform: Mac + Windows

Tue Dec 05, 2017 9:27 am Post

Bump for Keith :)

Ma
Manni
Posts: 71
Joined: Mon Dec 12, 2011 10:18 am
Platform: Mac + Windows

Wed Dec 06, 2017 10:55 pm Post

Another bump for Keith....

Sorry to insist, I know this might look like minor issues to you but at the moment V3 is not usable for me.

I can live with the extra tab needed with short titles, that bug was already present in V2, but I can't live with the tabs showing as underlined spaces when I compile for Kindle. That looks too unprofessional. And I need the tabs as I also compile to PDF (for free samplers etc), I can't simply delete them (which I would do if I was only compiling for Kindle).

If I can specify a tab character in my replacement string, please let me know as I could replace:
tab tab <$p> with nothing (for short titles) then
tab <$p> with nothing (for standard titles)
instead of just replacing <$p> with nothing, which works great with V2 as the tabs don't show up as visible underlined space when there is no <$p> if I compile for Kindle. And add the italics manually in the TOC, as I do now in V2.

Otherwise I'll just forget about V3 and I'll keep using V2 for now,

Thanks for your help!

Ma
Manni
Posts: 71
Joined: Mon Dec 12, 2011 10:18 am
Platform: Mac + Windows

Sun Dec 10, 2017 11:38 am Post

Bump for Keith

Any chance to get a reply on this? Just to know what to expect in V3.

Ma
Manni
Posts: 71
Joined: Mon Dec 12, 2011 10:18 am
Platform: Mac + Windows

Tue Dec 12, 2017 1:53 pm Post

Bump for Keith.

Would it be possible to get a reply regarding this? Especially regarding whether it's possible to specify a tab character in a replacement field, and how, if you believe that the problems reported are not bugs hence are not going to be fixed?.

Thank you.

Ma
Manni
Posts: 71
Joined: Mon Dec 12, 2011 10:18 am
Platform: Mac + Windows

Thu Dec 14, 2017 6:19 pm Post

Very disappointed in the lack of reply and support on this.

I've been a happy user of Scrivener for years and have never experienced being ignored in such a way. I know it's more or less the standard attitude these day but for me that's one of the things that set L&L and Scrivener apart: the quality of its support.

I understand you are busy, but this is not what I'm used to with L&L.

I'm going back to Scrivener V2.0 as it looks like there is no way to get V3.0 to do what I need it to do in order to be able to compile both for Kindle and PDF.

Have nevertheless a happy holiday!

User avatar
devinganger
Posts: 990
Joined: Sat Nov 06, 2010 1:55 pm
Platform: Mac, Win + iOS
Location: Monroe, WA 98272 (CN97au)
Contact:

Fri Dec 15, 2017 6:33 am Post

Manni, did you actually email Mac support with this issue? L&L tries to make it very clear that the support forums are not a good way to get time-critical support.
--
Devin L. Ganger, WA7DLG
Winner "Best in Class", 2018 My First Supervillain Photo Shoot

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

Fri Dec 15, 2017 12:48 pm Post

Hi,

I'm sorry I haven't got back to this earlier and that you are feeling ignored - it's not that I didn't do work on what you reported. If you need or are waiting for a reply from us directly, it's always best to email us - we guarantee a reply when you email us. We do make it clear that we can't guarantee answers from staff to everything on the forums in the same way we can with email: viewtopic.php?f=58&t=40987 It has been even more difficult to answer everything on the forums with the thousands of emails we have received following Scrivener 3's release.

Anyway, as to your questions:

1. I have fixed the problem of formatting not appearing in ToC titles for 3.0.1.

2. You should not be using a ToC with <$p> tags and tabs in them when exporting to ePub. Such ToCs should be used for PDF. print and rich text formats (Word, RTF) only. For ebooks, you should use a ToC that is just a list of links, by selecting the documents in the binder and either using Edit > Copy (for a flat list) or Edit > Copy Special > Copy Documents as Structured Link List (if you want an indented, structured ToC). This is the whole point of Scrivener allowing you to choose different front matter for different file formats - your front matter for RTF/Print would use a ToC with the <$p> tags, whereas the front matter for ebooks would not. That this ever worked was only an accident of Apple's way of converting HTML4, which was used in ePub 2. (And incidentally, you can get exactly the same results with ePub 2 in Scrivener 3 as you can with ePub in Scrivener 3, seeing as they are the same; it's ePub 3 that is brand new in Scrivener 3 and works a little differently.)

3. That extra left tab is inserted when pasting the <$p> ToC in case the user wants to use a tab in the custom title prefix separator in Compile. This allowed for neatly setting out "1. Something", "2. Something Else" etc. This is quite obscure, though, so I have removed that tab for 3.0.1 so that there will no longer be an issue with short titles.

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