View Single Post
Old 06-14-2022, 01:56 AM   #174
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by JSWolf View Post
It's most likely a bug in the renderer.
Yes, it is probably a bug in the renderer. And as it is being discussed so much here, I am sure that you and several others have reported it to Kobo so that they know it is a problem and that people think it is an important problem.

But...

Quote:
But if it works to render the text correctly with just one koboSpan,
Prove it. Can you please point to where in the kepub specs for rendering where it is defined how characters in this situation should work?

And don't just say, "Because it shouldn't look like that." Because, according to you, there are a lot of things done that are bugs but others think are just fine or even the preferred way to do it. Spaces between paragraphs is a simple example.

Quote:
why not give it a go?
Yes, that's the attitude. Give it a go. And post the code you develop over in the appropriate thread or as a pull request in the Github repository.

Sorry, oh you mean, "Why don't you, @davidfor, go and write the code to do this?" Why not? Because I have lots of things more important to do than to pander to your little demands like this. Because I have already explained why it hasn't been done and you, as usual, pay completely and utterly no attention to what anyone else thinks. And, honestly, just because I don't feel like it and am not interested in this relatively rare issue. Just think, how long has the driver been around and how often has this been noticed?

And for the record, it will not be as easy as you obviously think. This is exception code. By that I mean it is something that happens unusual circumstances. That means that getting it right can be a lot harder. It means you have to work out what the exceptional circumstance is. What to do in that circumstance. And if there is a similar circumstance that should not be treated this way. And then it cascades because you look at all the other exceptions. And all this will lead to slower, harder to maintain code to cover something that, apparently, rarely happens.

I have said I will look at @jackie_w's code for doing one span per paragraph when I have time. That should solve this and other similar issues. Coding something more specific is a waste of time if that is going to happen.
davidfor is offline   Reply With Quote