Thread: <div> problem
View Single Post
Old 08-18-2016, 09:31 PM   #11
Faterson
pokrývač škridiel
Faterson ought to be getting tired of karma fortunes by now.Faterson ought to be getting tired of karma fortunes by now.Faterson ought to be getting tired of karma fortunes by now.Faterson ought to be getting tired of karma fortunes by now.Faterson ought to be getting tired of karma fortunes by now.Faterson ought to be getting tired of karma fortunes by now.Faterson ought to be getting tired of karma fortunes by now.Faterson ought to be getting tired of karma fortunes by now.Faterson ought to be getting tired of karma fortunes by now.Faterson ought to be getting tired of karma fortunes by now.Faterson ought to be getting tired of karma fortunes by now.
 
Faterson's Avatar
 
Posts: 1,525
Karma: 3300000
Join Date: Oct 2011
Location: Bratislava, Slovakia
Device: 3*iPad, SamsungNote & Tabs, 2*OnyxBoox, Huawei 8″, PocketBook
Quote:
Originally Posted by Turtle91 View Post
Not sure where you got the information to make this statement??
It's not "information" – it's years of experience from using Marvin. Now that we can finally look at Alheva's two pictures in his opening post (thanks for re-uploading them), there is no excuse for Marvin 3 to mangle the display of paragraphs the way it can be seen in the second screenshot, especially when compared with the first screenshot. When Marvin 2 could treat these particular instances of styling reasonably, why should Marvin 3 fail to do so?

And as you know, there are many other examples, unrelated to rendering, in which Marvin 2 can do something that Marvin 3 currently cannot. So, as I said, Marvin 3 still has some catching up to do, which is understandable for a piece of software that was "(re-)written from the ground up".
Faterson is offline   Reply With Quote