You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have tested on the machine to ensure that pandoc is correctly configured and when I run pandoc -f docx -t html test.docx I get html output. However if I navigate to the repo I just get the 'view raw' hyperlink
I have also tested pandoc on other file types and it appears to be working - or at least doing something. With this it is like the command is not being called at all. Could it be because the file is labelled as a binary and so never even beings to render?
...
Looks as if it might be related to/a duplicate of #4996
Edit & Proposal
As per my entry in #4996
I propose the following untested addition in order to allow external renderers to render binary files if specified by the user
* allow external rendering of other filetypes
fixes#4996 and #7614
allows rendering of non-tex files, or otherwise accounted for filetypes
* Moves flie-size check before read()
And performs gofmt -s
* Only reads if markType is detected
[x]
):Description
After having success with jupyter notebooks and nbconvert, I wanted to try pandoc. So I installed pandoc and added the below to my app.ini:
I have tested on the machine to ensure that pandoc is correctly configured and when I run
pandoc -f docx -t html test.docx
I get html output. However if I navigate to the repo I just get the 'view raw' hyperlinkI have also tested pandoc on other file types and it appears to be working - or at least doing something. With this it is like the command is not being called at all. Could it be because the file is labelled as a binary and so never even beings to render?
...
Looks as if it might be related to/a duplicate of #4996
Edit & Proposal
As per my entry in #4996
I propose the following untested addition in order to allow external renderers to render binary files if specified by the user
at line
gitea/routers/repo/view.go
Line 343 in 734aa96
The text was updated successfully, but these errors were encountered: