Comments (7)
Unlike with commonmark, compatibility isn't a major goal for this project. I'm trying to imagine something clean and principled, unburdened by compatibility requirements.
from djot.
Let me clarify - I do not care about syntax.
I do care about the semantics and basically I just want to "nudge" users to stop thinking in terms of additions and deletions of tiny parts of text (words, characters) but rather in terms of substitutions of larger parts of text (phrases, sentences). In practice people tend to use the small parts which gets messy very soon. Guidelines are ineffective. Therefore I would like the technology itself nudge the users to do it in a more acceptable fashion.
Thoughts?
from djot.
If that is the case, then let me suggest support for editorial change tracking as the world has moved on and easy collaboration became a necessity. I deliberately do not suggest any syntax for that and would first like to hear your ideas.
Thanks!
from djot.
djot does already have syntax for marking insertions, deletions, and comments.
from djot.
And the most important - substitution - could be added? Substitution maintains much more semantical information than just plain insertion and deletion (as it linkes these two in a fine-grained manner). It could also be easier to write & read.
from djot.
Critic markup syntax for substitution:
{~~isn't~>is~~}
I don't know. To me, this seems just as readable, if not more so:
{-isn't-}{+is+}
It's also shorter.
from djot.
Having had to parse the CriticMarkup syntax with regex I agree with @jgm.
from djot.
Related Issues (20)
- Blockquote attribution / citation HOT 1
- Inclusion of other djot documents HOT 18
- Tight list and attributes HOT 1
- Task list item should allow for non-Latin checkmark HOT 4
- Limit numbers in ordered list markers HOT 5
- `[text][]` is shorthand for `[text][text]` – should `[text]()` mean `[text](text)`? HOT 3
- Footnote labels may contain spaces but not newlines
- Inline container precedence with attributes HOT 2
- Document implicit section behavior HOT 8
- Relax disallowing multiple words in `code block` / `div` first line? HOT 12
- Introduce leaf div (with `::`)
- Make `<section/>` wrappers optional (for HTML) HOT 4
- Normalize names of inline/block flavors HOT 2
- Canonical large-ish djot document (and related pandoc issues) HOT 5
- Parsing ambiguity: bracketed content followed by footnote? HOT 4
- Syntax for ruby (<ruby>) HOT 1
- Block level referencing and reuse syntax HOT 1
- URLs with parenthesis break parser HOT 1
- SyntaxError after installation HOT 4
- Code generation from ast.ts/djot-schema.json HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from djot.