On Wed, Aug 21, 2024 at 09:57:28PM +0100, Daniel Cerqueira wrote: > use CSS inside EPUB (don't know if it is possible and > compliant),
It is: https://www.w3.org/TR/epub-33/#sec-overview-relations-css > Are you guys even using epubcheck on your generated EPUB files? I think I already answered that, I did use epubcheck a lot when developping the EPUB output. I had a look at my mails and actually we had discussions/tests with Kurt Hornik off-list on epubcheck validity errors. (As a side note, I am somewhat surprised that you do not have epubcheck errors with width= in table too.) > > the 'border' attribute is deprecated, but we would have to decide > > whether > > we wanted to use CSS instead for this style. > > If you have not yet decided if you want to use CSS instead (and it has > to work for EPUB files too, since this is the thread topic), why are > you then discarding my patch? We are not in such a hurry that we have to decide immediately and implement immediately. The change of table border requires thinking, maybe discussions, implementation and testing. For those in a hurry, your patches are already there and can be used. As a side note, I do think that using CSS for border is the way to go, but that it is much better to do it after a release, not just before. > And if you decide you don't want CSS for EPUB, will this patch remain > in the trash? Probably. I do not exactly understand who is "you" in your sentence. GNU Texinfo is a collaborative project, and although there are not that many contributors, there are lots of users whose needs and wants, feedbacks and tests are important for the development decisions and the development process. It is therefore difficult to predict design decisions, and the future of a patch even more so. There is also always the possibility to fork (though in the case of Texinfo, sadly, this is somewhat unrealistic, to be honest). > Texinfo is producing non-compliant EPUB files! > > (This should bother you enough to make something about it). It does, and we are willing to improve the situation, but not a all costs nor without considering the impact of changes on the overall Texinfo project. -- Pat
