Syntax suggestion for moving text.

J. Nicholas Geist's Avatar

J. Nicholas Geist

21 Aug, 2013 06:47 PM

Obviously, if you're moving text, it's easy enough to do with a delete tag and a corresponding insertion tag.

Bacon ipsum dolor sit amet brisket beef ribs meatball shankle sirloin, pork loin 
turkey. {--Chuck spare ribs pig kielbasa beef shankle meatloaf. --}Pork belly ham 
hock pancetta, strip steak ribeye corned beef bacon leberkas. Frankfurter chuck 
filet mignon beef sausage shankle 
andouille. {++Chuck spare ribs pig kielbasa beef shankle meatloaf. ++}

If you're moving a lot of stuff around, though, or if you're moving large sections, that can quickly become cumbersome, as each moved item is duplicated.

{++Pork belly ham hock pancetta, strip steak ribeye corned beef bacon leberkas. ++}
Bacon ipsum dolor sit amet brisket beef ribs meatball shankle sirloin, pork loin 
turkey. {--Chuck spare ribs pig kielbasa beef shankle meatloaf. --}
{--Pork belly ham hock pancetta, strip steak ribeye corned beef bacon leberkas. --}
Frankfurter chuck filet mignon beef sausage shankle 
andouille. {++Chuck spare ribs pig kielbasa beef shankle meatloaf. ++}

A simple syntax for movement, paralleling Markdown references, would make things much clearer. I can imagine two useful variants, which are not incompatible.

{->[1]->Porbelly ham hock pancetta, strip steak ribeye corned beef bacon leberkas. ->}
Bacon ipsum dolor sit amet brisket beef ribs meatball shankle sirloin, pork loin 
turkey. {->Chuck spare ribs pig kielbasa beef shankle meatloaf. ->[2]->}{->[1]->} 
Frankfurter chuck filet mignon beef sausage shankle andouille. {->[2]->}

Inasmuch as the idea is the syntax should be clearly human readable, I won't explain much, except to say that in the first variant, the anchor indicates where the text came from, and in the second, it indicates where the text is going. That way, an author can choose whether the text will be presented in its new location or its original. (I'm thinking a writer making a change would prefer the first version, whereas an editor making a suggestion would prefer the second.)

I also can't decide if I think the anchors should have a different format than the movement itself, like so: {->[1]<-}. I'm using numbers for the anchors here, but as with markdown link identifiers, there's no reason they can't be words, phrases, whatever.

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac