Menu
▾
▴
python-markdown-discuss
|
From: Maurice v. d. P. <gri...@kf...> - 2016-03-22 19:15:57
Attachments:
signature.asc
|
My colleagues and I have been creating some tables for which a rowspan feature would have been useful, but unfortunately it's not supported by the current syntax. Before looking into writing my own extension, I wanted to ask you if you're open to changes in the existing tables extension to support colspan and rowspan. The syntax I had in mind uses adjacent pipes for signalling colspan and underscores for rowspan, e.g.: |col1 |col2 | |------------|--------| |colspan example || |rowspan ex. | | |__ | | |blah |blah | The second (or third, etc) adjacent pipe characters are currently ignored and do not lead to the creation of additional cells. The above example would currently have a single cell on second row that was as wide as the cell containing "col1". Only when there's a space in between the pipes will an additional cell be created. So for colspan I expect the change would not break a lot of documents. The syntax for rowspan could be in use at the moment, but the chance of breaking existing documents can hopefully be kept small by choosing a syntax that requires the cell to contain only underscores and spaces and optionally (to be more strict) requires the underscores to be on the first and/or last character position in the cell. Looking forward to hearing your thoughts on the matter. Best regards, Maurice. -- Maurice van der Pot Kdiff3 developer gri...@kf... http://kdiff3.sourceforge.net Tdiff3 developer https://github.com/Griffon26/tdiff3 |
|
From: Dave P. <dav...@gm...> - 2016-03-22 20:06:23
|
|| is overloading current markup? How to differentiate between my 'empty' cell and your colspan? Is there a way to use meta markup? id the table, id the row then the colspan (start / end) Perhaps steal the Xpath syntax for this? Is CSS capable of doing this? Just ideas. HTH Dave On 22 March 2016 at 18:57, Maurice van der Pot <gri...@kf...> wrote: > My colleagues and I have been creating some tables for which a rowspan > feature would have been useful, but unfortunately it's not supported by > the current syntax. > > Before looking into writing my own extension, I wanted to ask you if > you're open to changes in the existing tables extension to support > colspan and rowspan. > > The syntax I had in mind uses adjacent pipes for signalling colspan and > underscores for rowspan, e.g.: > > |col1 |col2 | > |------------|--------| > |colspan example || > |rowspan ex. | | > |__ | | > |blah |blah | > > The second (or third, etc) adjacent pipe characters are currently > ignored and do not lead to the creation of additional cells. The above > example would currently have a single cell on second row that was as > wide as the cell containing "col1". Only when there's a space in between > the pipes will an additional cell be created. So for colspan I expect > the change would not break a lot of documents. > > The syntax for rowspan could be in use at the moment, but the chance of > breaking existing documents can hopefully be kept small by choosing a > syntax that requires the cell to contain only underscores and spaces and > optionally (to be more strict) requires the underscores to be on the > first and/or last character position in the cell. > > Looking forward to hearing your thoughts on the matter. > > Best regards, > Maurice. > > -- > Maurice van der Pot > > Kdiff3 developer gri...@kf... http://kdiff3.sourceforge.net > Tdiff3 developer https://github.com/Griffon26/tdiff3 > > ------------------------------------------------------------------------------ > Transform Data into Opportunity. > Accelerate data analysis in your applications with > Intel Data Analytics Acceleration Library. > Click to learn more. > http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140 > _______________________________________________ > Python-markdown-discuss mailing list > Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-markdown-discuss > -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. http://www.dpawson.co.uk |
|
From: Maurice v. d. P. <gri...@kf...> - 2016-03-22 21:55:04
Attachments:
signature.asc
|
Hi Dave, On Tue, Mar 22, 2016 at 08:06:15PM +0000, Dave Pawson wrote: > || is overloading current markup? How to differentiate between > my 'empty' cell and your colspan? I don't believe it is. An empty cell already requires at least one space between two vertical bars. Adjacent vertical bars are currently treated as a single bar. > Is there a way to use meta markup? I'm not sure what you mean by that. > id the table, id the row then the colspan (start / end) > Perhaps steal the Xpath syntax for this? > > Is CSS capable of doing this? It might be, but I consider rowspan/colspan to be a content decision and not a styling one. But if you're talking about including css/xpath-style things in the markup, I think my proposal fits better with markdown's purpose of being "publishable as-is, as plain text, without looking like it’s been marked up with tags or formatting instructions". Best regards, Maurice. -- Maurice van der Pot Kdiff3 developer gri...@kf... http://kdiff3.sourceforge.net Tdiff3 developer https://github.com/Griffon26/tdiff3 |
|
From: Dave P. <dav...@gm...> - 2016-03-23 07:26:40
|
On 22 March 2016 at 21:54, Maurice van der Pot <gri...@kf...> wrote: > Hi Dave, > > On Tue, Mar 22, 2016 at 08:06:15PM +0000, Dave Pawson wrote: >> || is overloading current markup? How to differentiate between >> my 'empty' cell and your colspan? > > I don't believe it is. An empty cell already requires at least one space > between two vertical bars. Adjacent vertical bars are currently treated > as a single bar. So it would just be the interpretation of two or more bars. Sounds good, no change in semantic. > >> Is there a way to use meta markup? > > I'm not sure what you mean by that. See below > >> id the table, id the row then the colspan (start / end) >> Perhaps steal the Xpath syntax for this? >> >> Is CSS capable of doing this? > > It might be, but I consider rowspan/colspan to be a content decision and > not a styling one. I disagree. Presentation - spanning, is not, IMHO, content. But if you're talking about including css/xpath-style > things in the markup, I think my proposal fits better with markdown's > purpose of being "publishable as-is, as plain text, without looking like > it’s been marked up with tags or formatting instructions". No, I was not intending a content addition. A separate file which specified spanning requirements, which might use CSS, if possible. Select the cells, then CSS created to style it for spanning. This would address colspan also. Especially since no colspan can be added without disrupting present use? regards > -- > Maurice van der Pot > > Kdiff3 developer gri...@kf... http://kdiff3.sourceforge.net > Tdiff3 developer https://github.com/Griffon26/tdiff3 -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. http://www.dpawson.co.uk |
|
From: Waylan L. <way...@ic...> - 2016-03-23 14:52:35
|
On 03/22/2016 02:57 PM, Maurice van der Pot wrote: > My colleagues and I have been creating some tables for which a rowspan > feature would have been useful, but unfortunately it's not supported by > the current syntax. > > Before looking into writing my own extension, I wanted to ask you if > you're open to changes in the existing tables extension to support > colspan and rowspan. Maurice, Please see my response here: https://github.com/waylan/Python-Markdown/pull/74#issuecomment-3622297 So to answer your question, no I am not interested in making changes to th existing Extension. I would suggest you build your own. Waylan |
|
From: Maurice v. d. P. <gri...@kf...> - 2016-03-23 16:51:51
Attachments:
signature.asc
|
On Wed, Mar 23, 2016 at 09:52:15AM -0400, Waylan Limberg wrote: > Please see my response here: > https://github.com/waylan/Python-Markdown/pull/74#issuecomment-3622297 > > So to answer your question, no I am not interested in making changes to > th existing Extension. I would suggest you build your own. Ah, a clear description of your position. Thanks! Maurice. -- Maurice van der Pot Kdiff3 developer gri...@kf... http://kdiff3.sourceforge.net Tdiff3 developer https://github.com/Griffon26/tdiff3 |
|
From: Maurice v. d. P. <gri...@kf...> - 2016-03-23 16:50:32
Attachments:
signature.asc
|
On Wed, Mar 23, 2016 at 07:26:33AM +0000, Dave Pawson wrote: > > It might be, but I consider rowspan/colspan to be a content decision and > > not a styling one. > > I disagree. Presentation - spanning, is not, IMHO, content. Ok, then I'm not sure how you would separate the content from spanning. Would you always create all cells in the content and merge them in presentation? What would you expect to find in the content for a table that has a row of which the first cell should span 2 columns? And similarly, what would you expect in the content for a table that has a cell in the first column that (when presented) should span 2 rows? Best regards, Maurice. -- Maurice van der Pot Kdiff3 developer gri...@kf... http://kdiff3.sourceforge.net Tdiff3 developer https://github.com/Griffon26/tdiff3 |
|
From: Dave P. <dav...@gm...> - 2016-03-23 17:00:55
|
On 23 March 2016 at 16:50, Maurice van der Pot <gri...@kf...> wrote: > On Wed, Mar 23, 2016 at 07:26:33AM +0000, Dave Pawson wrote: >> > It might be, but I consider rowspan/colspan to be a content decision and >> > not a styling one. >> >> I disagree. Presentation - spanning, is not, IMHO, content. > > Ok, then I'm not sure how you would separate the content from spanning. > Would you always create all cells in the content and merge them in > presentation? The content (my view) is within the cells, not how the cell content is shown. > > What would you expect to find in the content for a table that has a row > of which the first cell should span 2 columns? As today |content|| then some 'identity' for that row (table[@id='table1']/tr[3]/td[1] ) then some styling information, e.g. 'span=2' which enables the presentational aspect to be specified external to the content? > > And similarly, what would you expect in the content for a table that has > a cell in the first column that (when presented) should span 2 rows? The same mechanism will work. For example table[@id='table1']/tr[3]/td[1], rowspan=2 with no change to MD syntax? HTH -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. http://www.dpawson.co.uk |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X