Context
This issue is closely related to #172, especially #172 (comment).
As @nickcrider was explaining, there is an edge case where users needs to use {eval-rst} but are unable to use any kind of substitution as Jinja's {{ }} won't be evaluated and reST substitution .. |any| replace:: does not work either (throwing Undefined substitution referenced: "any" error).
To be a bit more precise, in my case, I'm using {eval-rst} to handle more complex tables offered by reST (to merge cells essentially). And it's quite a known fact that tables are hard to maintain when the content gets a bit large.
Until now, with basic markdown tables I was able to use Jinja substitution :
---
myst:
substitutions:
large_text: A very long long text here that would make table super ugly...
---
| Key | Content |
| :---- | :--------------- |
| Story | {{ large_text }} |
But with reST tables, I cannot manage to make it work :
---
myst:
substitutions:
large_text: A very long long text here that would make table super ugly...
---
```{eval-rst}
+------------------------+------------+----------+----------+
| Header row, column 1 | Header 2 | Header 3 | Header 4 |
| (header rows optional) | | | |
+========================+============+==========+==========+
| body row 1, column 1 | column 2 | column 3 | column 4 |
+------------------------+------------+----------+----------+
| body row 2 | {{ large_text }} |
+------------------------+------------+----------+----------+
```
```{eval-rst}
.. |large| replace:: A very long long text...
+------------------------+------------+----------+----------+
| Header row, column 1 | Header 2 | Header 3 | Header 4 |
| (header rows optional) | | | |
+========================+============+==========+==========+
| body row 1, column 1 | column 2 | column 3 | column 4 |
+------------------------+------------+----------+----------+
| body row 2 | |large| |
+------------------------+------------+----------+----------+
```
Proposal
I understand that this is not that simple, but that would be really great to have some kind of support for reST substitution inside {eval-rst} blocks.
Or any other way of doing text substitution.
I am aware that sphinx-substitution-extention supports rst_prolog but I cannot set these text variables inside the conf.py file. Each text is very page related and that would be very confusing to move it in the config file.
Maybe I'm missing something here ?
Thank you very much 🙏
Tasks and updates
No response
Context
This issue is closely related to #172, especially #172 (comment).
As @nickcrider was explaining, there is an edge case where users needs to use
{eval-rst}but are unable to use any kind of substitution as Jinja's{{ }}won't be evaluated and reST substitution.. |any| replace::does not work either (throwingUndefined substitution referenced: "any"error).To be a bit more precise, in my case, I'm using
{eval-rst}to handle more complex tables offered by reST (to merge cells essentially). And it's quite a known fact that tables are hard to maintain when the content gets a bit large.Until now, with basic markdown tables I was able to use Jinja substitution :
But with reST tables, I cannot manage to make it work :
Proposal
I understand that this is not that simple, but that would be really great to have some kind of support for reST substitution inside
{eval-rst}blocks.Or any other way of doing text substitution.
I am aware that sphinx-substitution-extention supports
rst_prologbut I cannot set these text variables inside theconf.pyfile. Each text is very page related and that would be very confusing to move it in the config file.Maybe I'm missing something here ?
Thank you very much 🙏
Tasks and updates
No response