- From: Dave Pawson <dave.pawson@gmail.com>
- Date: Mon, 26 Nov 2012 07:39:35 +0000
- To: Markdown List <public-markdown@w3.org>
On 25 November 2012 22:27, David J. Weller-Fahy <dave-lists-public-markdown@weller-fahy.com> wrote: > * Dave Pawson <dave.pawson@gmail.com> [2012-11-25 09:35 -0500]: >> On 25 November 2012 10:33, Karl Dubost <karld@opera.com> wrote: >> > Le 23 nov. 2012 à 23:08, Dave Pawson a écrit : >> >> <br /> is currently being defined as inline syntax. AFAICT it only >> >> applies with \s\s\n at the end of a line? >> > >> > in JG Spec and in implementations. >> >> Should we define this as inline markup? That's what it appears to >> be... Though how to specify an output neutral semantic .... Any >> suggestions? > > Hrm, inline is how I imagined it would be defined. It doesn't change > the definition of any of the other pieces of the markup by existing > (AFAICT), and shouldn't cause difficulty in detection (easy to parse). > > If you're asking how to define using prose, how about... > > "If the last two characters before a line ending are spaces (\s\s), then > a line-break is substituted for those two spaces." > > Line-break could then be defined as meaning whatever will cause > following text to continue on the next line. That should be format > agnostic, as I know those exist in TeX, LaTeX, HTML, XHTML, as well as > others. > > Perhaps something like that? Works for me. Hang on to it, see if others comment? My concern is that it will be confusing if we're working on 6 items at once. regards DaveP -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. http://www.dpawson.co.uk
Received on Monday, 26 November 2012 07:40:05 UTC