On Tue, Oct 2, 2018 at 11:59 AM Fabio Valentini <decathorpe@xxxxxxxxx> wrote: > > On Tue, Oct 2, 2018 at 5:00 PM Neal Gompa <ngompa13@xxxxxxxxx> wrote: > > > > On Tue, Oct 2, 2018 at 9:02 AM Vít Ondruch <vondruch@xxxxxxxxxx> wrote: > > > > > > > > > > > > Dne 2.10.2018 v 13:11 Pierre-Yves Chibon napsal(a): > > > > On Tue, Oct 02, 2018 at 11:53:45AM +0200, Vít Ondruch wrote: > > > >> > > > >> Dne 1.10.2018 v 20:00 Jason L Tibbitts III napsal(a): > > > >>>>>>>> "BP" == Björn Persson <Bjorn@rombobjörn.se> writes: > > > >>> BP> This was on Fedora 27. So one needs Fedora 28 to help fixing the > > > >>> BP> formatting of the guidelines then? (Once that other breakage is > > > >>> BP> fixed I suppose?) > > > >>> > > > >>> I believe one could build the antora stack from scratch instead of using > > > >>> a container. I would hope it wouldn't require F28 to do so, but it's > > > >>> still way too high of a barrier. > > > >>> > > > >>> BP> Yeah, no I don't think I'm going to run any document conversion > > > >>> BP> programs as root. > > > >>> > > > >>> You certainly shouldn't have to. The problem is making it look like it > > > >>> looks on the web site, since I guess the markup itself is dependent on > > > >>> stylesheets and extra information which isn't actually included in the > > > >>> documents. > > > >>> > > > >>> For a single page, though, it seems that you can get a reasonable > > > >>> interpretation merely by installing asciidoc and running "asciidoc > > > >>> foo.adoc". > > > >> For a single page, it would be nice if Pagure supported .adoc as it > > > >> supports other makrdowns > > > > There is a ticket asking just for this. We'll get to it sooner or later. > > > > > > > >> ... > > > > Not quite sure what this implies > > > > > > It is just surprising it is not supported yet out of the box by whatever > > > library you are using to convert other markups to html. > > > > > > > Pagure is in Python. There are now no useful implementations of *.adoc > > renderers in Python. It's not that surprising. > > After a bit of looking around, it looks like almost no code > highlighting tool supports AsciiDoc (yet). Neither pygments (python) > nor rouge (ruby) support it. > > The only "libraries" supporting AsciiDoc that I could find were > highlight.js and prism.js. But, looking at pagure's source code, it > already seems to use highlight.js. Maybe it's just a version without > AsciiDoc support enabled? > There are some quirks with highlight.js that we're still working through for pagure 5, but highlight.js only supports syntax highlighting, not rendering. The problem is that Pagure is incapable of rendering asciidoc safely right now. We can render Markdown and reStructuredText because there are solid implementations for them that we can use. > Side note: Is AsciiDoc really such an obscure format? > Yes. Unlike most text formats, AsciiDoc is really defined by the tool that renders it. The only other format that was in a similar situation was Markdown, but the CommonMark specification has allowed for a number of independent implementations to exist that behave coherently. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
