- From: Eric Muller via GitHub <sysbot+gh@w3.org>
- Date: Mon, 02 Nov 2020 14:26:14 +0000
- To: public-i18n-archive@w3.org
Re: plain text vs. markup Of course, I would want something that works for plain text as well. Even with markup, there is a strong desire to minimize the quantity of markup that is needed, so there is no opposition on the goal between markup and plain text. But we also need to realize that all the "virtual" classes of JLREQ (cl-18 math operator, etc; more or less, the classes that have to be deduced from the context) will be the result of either markup or heuristics, and for plain text we only have heuristics. What I am not excited about is spending too much time building complicated (and therefore delicate) heuristics (but somebody else can), and I would not be happy if the support of those heuristics makes the markup case more complicated. That could happen if the author of markup ends up asking himself all the time "does the heuristic work in this case, or do I need to add markup". -- GitHub Notification of comment by emuller-amazon Please view or discuss this issue at https://github.com/w3c/jlreq/issues/242#issuecomment-720503872 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 2 November 2020 14:26:15 UTC