Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
/html
#7
(10-24-2015, 10:07 AM)Blue Phoenix Wrote:  1) (bad) Use an HTML validator at the end of the parsing process. If it finds that the (parsed) post contains invalid elements, the post will be displayed as blank. I think this also how badly formed quotes are handled right now.
2) (good) Write an actual parser-enhancement that will attempt to fix badly formed html (hard). Rogue tr or td tags would be padded in additionally created tables.
I would say the second one is not a good solution. I like the idea of fail fast, so whenever something is wrong it will throw up its hands and give a (hopefully useful) error message.

Also: https://xkcd.com/327/
Age ratings for movies and games (and similar) have never been a good idea.
One can learn a lot from reinventing wheels.
An unsound argument is not the same as an invalid one.
volatile in C++ does not mean thread-safe.
Do not make APIs unnecessarily asynchronous.
Make C++ operator > again
Trump is an idiot.
Reply
Thanks given by:


Messages In This Thread
/html - by Silverthorn - 10-23-2015, 04:36 PM
RE: /html - by A-Man - 10-23-2015, 06:27 PM
RE: /html - by MangaD - 10-23-2015, 07:04 PM
RE: /html - by Hellblazer - 10-24-2015, 10:04 AM
RE: /html - by Silverthorn - 10-24-2015, 10:07 AM
RE: /html - by Som1Lse - 10-24-2015, 11:04 PM
RE: /html - by Hellblazer - 10-24-2015, 11:06 AM



Users browsing this thread: 1 Guest(s)