News for hackers. Stuff that matters.
Re:Polymath: A Markup Language for Everything by alok-g on Wednesday February 12, 2020 @01:46AM (#22306483)
I follow that viewpoint and am OK with the direction being taken.

On the other hand, even after asking many, I have never received a good answer to why the exactness and understanding cannot be obtained with a WSYIWYG/M markup editor.

Re:Polymath: A Markup Language for Everything by johnmorrison on Wednesday February 12, 2020 @05:11PM (#22313370)
They abstract away from the underlying code.

You wouldn't be able to tell the difference between

  {b Bolded} {b text}
and

  b Bolded text
this becomes especially concerning with TeX, custom styling, etc
Re:Polymath: A Markup Language for Everything by alok-g on Thursday February 13, 2020 @07:50PM (#22322934)
That makes sense, and I can imagine that.

However, should it not be possible for the software to find a minimal cover for the formatting that would produce the same visual output, thereby practically recovering what hard-crafted markup would have been?

Thanks.

Re:Polymath: A Markup Language for Everything by johnmorrison on Thursday February 13, 2020 @08:54PM (#22323323)
Yeah, if I'm interpreting your words correctly, this would be like turning

  p {b This} {b text is} {b bolded} this isn't
into

  p {b This text is bolded} this isn't
But then the issue is as follows:

In Polymath, I'm planning on allowing basically arbitrary CSS styling by parent, id, class, etc. So if the user later wants to do something like put a rounded box around each span of bolded text, those two, while initially looking identical in WYSIWYG, end up completely different.

Re:Polymath: A Markup Language for Everything by alok-g on Friday February 14, 2020 @08:28AM (#22326290)
I can take that. Thanks.