On Fri, 13 Dec 2019 08:38:19 +0100 Simon Ruderich wrote:
> Another issue with asciidoctor, unrelated to its features, is
> that the output changes when compared to asciidoc. This is not a
> big issue but adds additional work during the conversion. So
> staying with asciidoc is simpler.
On that no
On Wed, Dec 11, 2019 at 06:41:15PM -0800, Joseph Herlant wrote:
> Hi Simon,
>
> I'd be interested in your use case. Do you have some examples of what
> you call "proper localization with support for multiple languages and
> flexibility through additional config files"?
>
> I also work with asciidoc
Hi Simon,
I'd be interested in your use case. Do you have some examples of what
you call "proper localization with support for multiple languages and
flexibility through additional config files"?
I also work with asciidoctor so I'd be happy to see with them if
upstream has that on their backlog.
Hello,
please keep asciidoc in Debian. With the current python3 port it
will continue to work even when Python 2 is removed.
I'm using asciidoc for a few (private) projects which depend on
some features not yet provided by asciidoctor (e.g. proper
localization with support for multiple languages
4 matches
Mail list logo
