An update!
I am very pleased to announce, that my campaign took me only a little
less than 2 weeks to achieve success! :)
And so, from now on, not only myself but /everyone/ who prefer writing
in .org instead of .md now have a clear path to nice looking rendered
HTML which is on par with the
TRS-80 writes:
>> On 2020-12-02 16:59, Tim Cross wrote:
>>> TRS-80 writes:
>>>
>> I note that in the email thread you referenced, the last post suggests
>> setting up a custom readme format which would allow you to use HTML.
>> Maybe that is the easiest route to take - org -> html with custom
On 2020-12-02 16:59, Tim Cross wrote:
TRS-80 writes:
I think the problem is actually because Sourcehut are sanitizing the
id
attribute out of links, as I have replied already to some other people
in this thread.
From what I can tell, yes your right. However, it also seems that this
is an
TRS-80 writes:
>> On 2020-12-02 14:44, Tim Cross wrote:
>>
> I think the problem is actually because Sourcehut are sanitizing the id
> attribute out of links, as I have replied already to some other people
> in this thread.
>
>From what I can tell, yes your right. However, it also seems that
On 2020-12-02 14:56, TRS-80 wrote:
On 2020-12-02 14:12, Jean Louis wrote:
Try using pandoc Org to Markdown as that could help until Org
exporting start working how it should.
Great minds must think alike! :) I tried that already but in-page
links
which look like:
```
[[*Setup][Setup]]
```
On 2020-12-02 14:44, Tim Cross wrote:
I could be completely wrong here, but I suspect this is a combination
of the evolving markdown spec (or more specifically, no one standard
spec) and the age of the org mode markdown exporter.
FWIW, it sort of feels that way to me, too.
One of the
On Wed, Dec 2, 2020 at 7:54 PM TRS-80
wrote:
Some further digging revealed that the ox-md exporter (which itself
is derived from the HTML exporter(?) makes extensive use of the id
attribute in links. And Sourcehut's HTML sanitizer only allows href
and title attributes (not id).[1]
[1]
On 2020-12-02 14:12, Jean Louis wrote:
Try using pandoc Org to Markdown as that could help until Org
exporting start working how it should.
Great minds must think alike! :) I tried that already but in-page
links
which look like:
```
[[*Setup][Setup]]
```
Somehow get exported to:
```
Hi TRS-80,
Note that according to https://man.sr.ht/markdown/#post-processing,
Sourcehut uses CommonMark, not plain Markdown, so I guess that's why it
doesn't allow all HTML tags.
(note: Markdown allows embedded HTML, so ox-md's behavior is not incorrect)
There seems to be no ox-commonmark
TRS-80 writes:
> Hallo,
>
> I became quite interested in what Drew Devault was doing with his
> Sourcehut project, so I decided to join. I was really enjoying
> everything except for the fact that .org files are not supported insofar
> as automatic rendering into nice looking HTML in the same
Try using pandoc Org to Markdown as that could help until Org
exporting start working how it should.
Hallo,
I became quite interested in what Drew Devault was doing with his
Sourcehut project, so I decided to join. I was really enjoying
everything except for the fact that .org files are not supported insofar
as automatic rendering into nice looking HTML in the same way that
Markdown files are
12 matches
Mail list logo
