Are these sections useful?

[Sirtel]

Originally Posted by JSWolf

One thing I do dislike is error messages which I will get because of the invalid links.

Well, I don't check for errors, so I never see them.

[Sirtel]

Originally Posted by KevinH

We really need 2 epub forums ... One for professional epub developers who care about accessibility, correctness, etc. And another forum for all those users who want to hack away at professionally developed epubs to meet their one unique desires/fixations/needs.

That way we won't have to rehash all of the accessibility and standards arguments again and again.

I agree, but I bet people would just constantly post in the wrong forum.

[JSWolf]

Originally Posted by KevinH

We really need 2 epub forums ... One for professional epub developers who care about accessibility, correctness, etc. And another forum for all those users who want to hack away at professionally developed epubs to meet their one unique desires/fixations/needs.

That way we won't have to rehash all of the accessibility and standards arguments again and again.

These professionally developed ePubs can be poorly formatted. What we delete will not change any of the accessibility features of the ePub.

And as for <em>, <i>, <b., and <strong>, they don't (usually) do it correctly.= for accessibility.

I'm not fixing broken or non-existent accessibility. I'm just fixing the formatting for my needs.

Though it would be a good idea to have a thread for accessibility to help those who want to add it and fix it when it's broken.

[JSWolf]

Originally Posted by Sirtel

Well, I don't check for errors, so I never see them.

I do check for errors so I can check if I made any and then fix them.

[Sirtel]

Originally Posted by JSWolf

I do check for errors so I can check if I made any and then fix them.

You change a lot more things than I do. I only change the code as much as is necessary for the formatting to look the way I want; I don't clean the code up or simplify it in any other way.

[Turtle91]

I also delete inline ToC because I use the device’s built-in ToC function. However, some publishers require it and it may be considered a good advertising tool for those “preview” functions on some websites.

The good news is that if you have correctly set up the heading tags then you can use automated functions to generate your ToC files (both inline and ncx). It isn’t difficult at all to update your inline ToC if you choose to keep it.

[Tex2002ans]

Originally Posted by KevinH

We really need 2 epub forums ... One for professional epub developers who care about accessibility, correctness, etc. And another forum for all those users who want to hack away [...]

I already see the Sigil/EPUB forum as the good people.

All the cool/serious people already hang out here.

Originally Posted by KevinH

That way we won't have to rehash all of the accessibility and standards arguments again and again.

Meh.

From now on, I'll just be doing my usual, linking back to the old posts/discussions and summarizing with the latest info if needed.

(No need to beat that dead horse again when it's been completely demolished from 1000 different angles.)

- - -

Side Note: Anyway, now that I'm back from my almost year-long "hiatus" from MR... I'll be ramping up my writing like crazy.

Over the past 2 years / 1500+ posts on the LibreOffice subreddit, my Technical Writing skills have grown exponentially.

I'll be taking my Plain English + Documentation skills + to the next level, reviving and repackaging all that juicy 14+ years of EPUB knowledge.

Then, instead of pointing back to long MR threads discussing "Random Topic X"—with who-knows-what filler in-between—it'll be links to extremely pointed and high-quality "best practices" articles:

• Want the correct way of doing X in EPUB? Here's an article!
• Want to know how to write a book in LibreOffice? Yep! I got you!
• Want the best practices on Poems? Yep! Here you go!
  
  • (And look at that pretty Index code too! I mean, what kind of savage would want to delete that? )