4 ms·

Really, what we need to adopt en-mass is Tex.

ZenPsycho 14y ago
I won't even acknowledge a document unless it's hand-written postscript.
AndrewDucker 14y ago
All sorts of things Tex doesn't handle. Embedded editable files, for instance. Or markup for tracking changes. Tex might make a good starting point for building a system that _did_ do all of that, but nobody seems to be working on that.
- politician 14y ago
  > Or markup for tracking changes. I've often wondered why Microsoft chose to embed a weak implementation of version control into their mutable document format instead of doing something like passing around a signed chain of immutable documents.
  - MichaelGG 14y ago
    The people that made change tracking probably wanted the feature to work and be usable, rather than create another crypto product and have no one figure it out. Also, if you don't trust the other parties, you can use the compare feature an get a diff of the documents. Keeping your own copy is a easy, simple, way to get a correct view of changes to a document.
    - politician 14y ago
      Right, so, "signed" in the same sense that a chain of git commits are signed. In other words, resiliency not trust, and full history instead of whatever Track Changes provides.
      - MichaelGG 14y ago
        Sure, and Microsoft provides document signing/rights management, as well, if you can get the supporting infrastructure. Office apps also have built in change revision history. Track Changes is sorta orthogonal here, I think.
  - AndrewDucker 14y ago
    Because I don't want a list of separate changes - I want a series of notes _inside_ the document, colour coded for the editors, marked as accepted/rejected, etc. You can do a mediocre job of inferring the latter from the former, but for 100% support you need to actually put the notes into the file itself.
Edootjuh 14y ago
That seems like a bad idea. TeX doesn't allow separation between markup and presentation very well. Something like DocBook[1] with a presentation engine like XSLT might be better, if it wasn't for the verbosity of the XML source. [1] http://www.docbook.org/whatis http://www.docbook.org/whatis
- zdw 14y ago
  +1. Any representation that makes people think "this is a paragraph", "this is a title", "this is a list" and then apply styles to each is an improvement over the current "lets vomit text on a page, then tweak individual sections independently" method endorsed by most word processors. Tools that do this like (Pandoc being the one I like) do a great job of getting people to think of documents as text that gets styled later.

I won't even acknowledge a document unless it's hand-written postscript.

All sorts of things Tex doesn't handle. Embedded editable files, for instance. Or markup for tracking changes. Tex might make a good starting point for building a system that _did_ do all of that, but nobody seems to be working on that.

politician 14y ago
> Or markup for tracking changes. I've often wondered why Microsoft chose to embed a weak implementation of version control into their mutable document format instead of doing something like passing around a signed chain of immutable documents.
- MichaelGG 14y ago
  The people that made change tracking probably wanted the feature to work and be usable, rather than create another crypto product and have no one figure it out. Also, if you don't trust the other parties, you can use the compare feature an get a diff of the documents. Keeping your own copy is a easy, simple, way to get a correct view of changes to a document.
  - politician 14y ago
    Right, so, "signed" in the same sense that a chain of git commits are signed. In other words, resiliency not trust, and full history instead of whatever Track Changes provides.
    - MichaelGG 14y ago
      Sure, and Microsoft provides document signing/rights management, as well, if you can get the supporting infrastructure. Office apps also have built in change revision history. Track Changes is sorta orthogonal here, I think.
- AndrewDucker 14y ago
  Because I don't want a list of separate changes - I want a series of notes _inside_ the document, colour coded for the editors, marked as accepted/rejected, etc. You can do a mediocre job of inferring the latter from the former, but for 100% support you need to actually put the notes into the file itself.

Edootjuh 14y ago

That seems like a bad idea. TeX doesn't allow separation between markup and presentation very well. Something like DocBook[1] with a presentation engine like XSLT might be better, if it wasn't for the verbosity of the XML source. [1] http://www.docbook.org/whatis http://www.docbook.org/whatis

zdw 14y ago
+1. Any representation that makes people think "this is a paragraph", "this is a title", "this is a list" and then apply styles to each is an improvement over the current "lets vomit text on a page, then tweak individual sections independently" method endorsed by most word processors. Tools that do this like (Pandoc being the one I like) do a great job of getting people to think of documents as text that gets styled later.