This isn't an easy one. In markup terms the critic markup as
currently defined forms a simple variation of Asciidoc attribute
reference syntax with punctuation inside the {}s differentiating it
from other attribute references. In technical terms that means it
probably must be integrated into the Asciidoc processor. Thats
probably not difficult.
But as the second asciidoctor ticket you referred to seems to be
coming to the conclusion, attributing and tracking changes is the job
that VCS systems are specialised for.
The critic markup does bring the ability to make the changes visible
in the rendered output, but...
It strikes me that the critic markup is more suited to submitting
suggested changes to an author from one editor that are integrated
before a fixed copy is published. But that is an old paradigm, in
these days of distributed development more changes from many people
accumulate over the life of a document.
But as more changes happen over time, the input becomes more and more
messy, and as soon as you integrate the changes into the document to
reduce the mess, you lose the ability to show the changes in the
output.
So although its probably implementable, it doesn't seem to solve a
problem thats relevant to todays development environment.
On 30 October 2015 at 21:31, Sean Russell <[email protected]> wrote:
> Hi,
>
> What are the current thoughts on adding Critic Markup support to asciidoc?
> I find discussions in the asciidoctor space, but I'm curious what the core
> markup community thinks of this. Add it to the spec? Add support through
> plugins? Is anybody working on support for it? Is it flame-war material?
> I did do a search in this list and found no references to it. The Critic
> Markup folks themselves appear to be focused on Markdown, sadly. There are
> two relevant ticket in the asciidoctor ticket system, the first being a
> general plea for some sort of non-cumbersome change tracking markup, and the
> second advocating adopting what might loosely be described as a defined
> standard for such markup.
>
> What's the current thinking by the people who effectively control the spec?
> Stuart?
Stuart retired from Asciidoc some time ago, the Python Asciidoc
implementation is in maintenance mode (although someone started a
Python 3 port, not sure where its at). Most new development now takes
place on the Asciidoctor implementation.
Cheers
Lex
>
> Thanks
>
> --- SER
>
> --
> You received this message because you are subscribed to the Google Groups
> "asciidoc" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/asciidoc.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"asciidoc" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/asciidoc.
For more options, visit https://groups.google.com/d/optout.
