I think I found a major bug in InDesign CS6's ePub export of list items.
In CS5 I'd get pretty clean lists:
<ul> <li class="Basic-Paragraph">one</li> <li class="Basic-Paragraph">two</li> <li class="Basic-Paragraph">three</li> </ul>
Now in CS6 I get this mess
<ul> <li class="Basic-Paragraph"><span class="char-style-override-1">•	</span>one</li> <li class="Basic-Paragraph"><span class="char-style-override-1">•	</span>two</li> <li class="Basic-Paragraph"><span class="char-style-override-1">•	</span>three</li> </ul>
The same type of thing happens with ordered lists as well. Why are the bullets and numbering now being entered in the code instead of using the native list formatting? InDesig CS6's CSS actually hides the native list formatted because it would of course conflict with the typed in characters.
This is real mess of code. Is there a good reason for this that I am not seeing? This causes a ton of formatting issues. The same ePub that looked great exported from CS5 looks bad exported from CS6.
Sadly, I think it's as designed. Makes a littel bit of sense for numbered lists but certainly not for bullets.
If you export the exact same content to HTML it's comes through properly.
Someone made a really bad decision here.
Thanks for the help everyone! I was hoping I might have just misunderstood the UL export settings, but alas...
(Honestly, I've given up on reporting bugs, making feature requests, and generally expecting Adobe to respond to people who use their products. Not that I'm still bitter about no endnotes in CS6 )
I agree @bob that Adobe probably meant to do this (as crazy as that sounds). It seems like an intentional change because of the CSS changes as well. I still call it a bug because it's a problem in the software, but Adobe would probably call it a "feature."
@steveI did file a bug report but forgot to mention that in my post here. Of course the more people do it the more Adobe might get the point!
I think you need to file it as a feature request, not a bug report. Anything as designed is going to be filed away immediately while a feature request might get looked at.
This behavior is flat out wrong for bullets and as far as semantic mark up goes. It’s not correct for numbered lists either but does result in the numbers being the same as the InDesign file.
After a bit more reading, including a what’s new in EPUB article in the new InDesign Magazine, I can assure you, this is as designed.
Again, I can see the logic for number lists, but not for bullets.
One person's feature is another person's bug. Non-standard coding of lists like this should at least have been an option, not mandatory. InDesign magazine's example of nested lists looks nice and tidy, but in my project the lists exported from CS6 look horrible. In trying to fix something they also broke it.
I don't think the way Adobe tried to fix this is the correct way. At least I see the problem Adobe "thought" they were fixing, custom bullets and nested lists, but it seems they could have coded things semantically and fixed the issues they were trying to fix with nested lists.
It's not a bug. Adobe brags in CS6 promos that it can now display any character as a bullet, whereas previously we were "stuck" with the CSS bullet characters. This is their solution, and it's awful. I've managed to override it in my own CSS, but when I convert ePubs to Kindle books, Kindle can't handle the CSS and it comes apart, leaving me with TWO bullet characters.
@McWriting You're right about Adobe not thinking it's a bug. This is how they intended the feature to work. They completely botched it, but yes that's how they intended it to work. This is extremely poor coding on their part, and not to mention it's non-standard and incorrect HTML & CSS.
To fix the conversion to Kindle you'll have to expand the ePub, and use find/change (like GREP) to remove the bullets and numbers that Adobe wrongly codes into the HTML. That and some CSS fixes can eliminate your problems. We're now responsible for cleaning up the bad code Adobe has written. Too bad they didn't just make it optional!
Yep, Kindle can't handle the kind of CSS required to make the ID6 bullets display acceptably. Hanging indents don't align well enough in ePubs, worse in Kindle, and thus look amateurish. I found no better solution than to strip out the newly added bullet character and span style from every ePub doc and revert to ePub-generated lists – a real pain, even using GREP.
InDesign added "display: block" to their span tag to disable a list's ability to act, well, list-like. That's the kind of back-door hack I'd try to get away with, not something I expected to see from Adobe. :-D
would you mind revealing which GREP-commands you use to sort out these faulty codes? I'm really annoyed by this problem, especially since I have a Book with many many pages and many many bullet- und numbered lists.
Do you also delete the bullet and define the sign via CSS or do you leave the bullet as it is? Do you only delete the span-tags?
I always have difficulties with the indents.
Thank you very much.
Europe, Middle East and Africa