|
Giving multiple ids to one tag is an interesting idea, but a little searching around seems to indicate that's not valid (though maybe you can call one of them "id" and a second one "xml:id" but I don't know if that would actually make them work for the TOC purposes. I have not tried that.).
And I'm sure your other solution (the "For example:" in your post above) would work, as was suggested earlier in this thread. That's not what I want to do, since I want the links to go to the same place. I could instead put some empty 'a id="foo"' tags right after each other. But again, that would be a workaround and would make more clunky code.
I'm not looking for a workaround. I already have a workaround that satisfies me, although it takes more work (manually editing the toc.ncx as I explained in my first post). I was simply reporting what I saw as a bug in Sigil. Maybe this isn't a good place to report bugs, but I find bug tracker interfaces to be unfriendly. And any programming I do is by the skin of my teeth and extremely kludgy, with complete ignorance of best practices, so I doubt I'd be doing any favors by trying to fix this myself.
Now, there's debate in this thread as to whether it's a bug or an error in the validator. Logic and Ockham's razor tell me that the validator would have been written a different way if my workaround was intended to be invalid, but people apply logic differently and what seems the most simple solution to one person is not to another. That's fine.
If this behavior of the program gets changed to allow for what I suggested above, that would be convenient for people who want to do this in the future. If it doesn't get changed, the workaround should at least still exist. I'd be frustrated if the developers decided to "have Sigil error-checking for dupe playlist entries" as was suggested above, since making my change instead would also allow it to pass validation.
|