Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: RFC: Textpattern 5 ideas & feature requests
etc wrote #340182:
is anyone actually using ‘convert linebreaks’ filter?
If I have, I don’t recall why. I use the other two a lot.
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
Re: RFC: Textpattern 5 ideas & feature requests
My deux centimes :-)
I prefer the versatility of Textile over markdown any day, but write in both. Textile is – unfortunately – pretty obscure in comparison to Markdown, and that is also obscure for “average” users. So my view is:
- Markdown in addition to Textile -> By all means (Robert willing)
- Markdown in preference to Textile -> Contentious 😱
- Market as “speaks many languages” rather than one over the other
- Deal-breaker: It must be possible to write txp:tags amidst the Markdown. 🫷
TXP Builders – finely-crafted code, design and txp
Offline
Re: RFC: Textpattern 5 ideas & feature requests
jakob wrote #340188:
- Markdown in addition to Textile -> By all means (Robert willing)
- Markdown in preference to Textile -> Contentious 😱
- Market as “speaks many languages” rather than one over the other
- Deal-breaker: It must be possible to write txp:tags amidst the Markdown. 🫷
My thoughts entirely. I’ve never tried to sprinkle tags inside Markdown. I know Txp can do it with double-equals and various other ‘breakout’ methods like indenting with spaces. Does Markdown / Parsedown not offer something similar at all, beyond leaving a clear line break? It’s been a long time since I’ve used it for anything other than GitHub comments.
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
Re: RFC: Textpattern 5 ideas & feature requests
From a quick GH test, Markdown encodes txp tags:
<b>Hello</b>, <txp:author />!
results in <b>Hello</b>, <txp:author />!
Textile leaves (simple) txp tags untouched, even without ==
escaping.
Offline
Re: RFC: Textpattern 5 ideas & feature requests
etc wrote #340192:
From a quick GH test, Markdown encodes txp tags:
<b>Hello</b>, <txp:author />!...
results in
<b>Hello</b>, <txp:author />!
Textile leaves (simple) txp tags untouched, even without
==
escaping.
FWIW, Textpattern 4.9, Markdown plugin active. Markdown extra selected as format, input:
Hello, <txp:author />
Screengrab: dev.l-c-n.com/_b/MD.png
Where is that emoji for a solar powered submarine when you need it ?
Sand space – admin theme for Textpattern
phiw13 on Codeberg
Offline
Re: RFC: Textpattern 5 ideas & feature requests
Cool. And as we know, all page hell breaks loose for complex tags, but that’s why we have the breakout mechanisms.
So, as it stands, Markdown is viable as long as you don’t want to embed tags or shortcodes in your content. I don’t see this as a major issue, because I suspect 80 (90?)+ percent of people will use it for just marking up text. It’s only us hardcore folk that tend to go above and beyond the standard usage, right?
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
Re: RFC: Textpattern 5 ideas & feature requests
Bloke wrote #340194:
I don’t see this as a major issue, because I suspect 80 (90?)+ percent of people will use it for just marking up text. It’s only us hardcore folk that tend to go above and beyond the standard usage, right?
I absolutely see that as an issue. If you want to embed an image with a srcset, or perhaps a small set of images, a shortcode is the only way to go (apart from writing it all in html – or is there another option). As soon as a client declares they want Markdown, and then later decides they could imagine having a slideshow within the article, what do you do if shortcodes don’t work…
etc wrote #340192:
From a quick GH test, Markdown encodes txp tags:
phiw13 wrote #340193:
FWIW, Textpattern 4.9, Markdown plugin active. Markdown extra selected as format, input:
Hello, <txp:author />...
So GitHub can’t but Textpattern can. That would certainly be encouraging if one can continue using shortcodes and regular tags with Markdown in Textpattern.
TXP Builders – finely-crafted code, design and txp
Offline
Re: RFC: Textpattern 5 ideas & feature requests
jakob wrote #340195:
a client declares they want Markdown, and then later decides they could imagine having a slideshow within the article, what do you do if shortcodes don’t work…
Put the shortcode on its own line? I believe Parsedown will handle that, it’s just mixing them it can’t do as there’s no way to ‘escape’ complex codes.
As phiw13 demonstrated, simple tags (without attributes?) work fine inline. I’ve not tested this rigorously (uhh, at all) so the situation may be better than we hoped. Perhaps Markdown can handle inline markup now.
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Txp Builders – finely-crafted code, design and Txp
Offline
#93 Today 01:59:51
Re: RFC: Textpattern 5 ideas & feature requests
jakob wrote #340195:
I absolutely see that as an issue. If you want to embed an image with a srcset, or perhaps a small set of images, a shortcode is the only way to go (apart from writing it all in html – or is there another option). As soon as a client declares they want Markdown, and then later decides they could imagine having a slideshow within the article, what do you do if shortcodes don’t work…
So GitHub can’t but Textpattern can. That would certainly be encouraging if one can continue using shortcodes and regular tags with Markdown in Textpattern.
It is not surprising GH can’t handle those <txp:tag /
>. It doesn’t known anything about it, and treat it as “unknown tag” or such. Thankfully it sanitise it and does it in a friendly way, the tag is still visible. I seem to remember Vignette completely removing them, which is still better than leaving them in probably invisible and then open for potential abuse.
And yes, as I mentioned upthread, your shortcode tags would continue to work fine.
Where is that emoji for a solar powered submarine when you need it ?
Sand space – admin theme for Textpattern
phiw13 on Codeberg
Offline
#94 Today 02:32:54
Re: RFC: Textpattern 5 ideas & feature requests
Bloke wrote #340197:
As phiw13 demonstrated, simple tags (without attributes?) work fine inline. I’ve not tested this rigorously (uhh, at all) so the situation may be better than we hoped. Perhaps Markdown can handle inline markup now.
As far as I can tell, I can do most everything the same in a Markdown managed file as I do with a Textile one. Or at least most what we need here (shortcodes being the most important one). And of course some more, really complex Textpattern tags might have a problem. But that happens with Textile as well.
Here a very basic example: emps.l-c-n.com/tests/markdown-test1 – a shortcode to embed the image, the <txp:author />
used as sample before (of course you can’t see from it that the underlying code is Markdown :-()
PS – I don’t remember if there is an .notextile
or ==
equivalent in Markdown.
Where is that emoji for a solar powered submarine when you need it ?
Sand space – admin theme for Textpattern
phiw13 on Codeberg
Offline