The problems Paul highlights with HTML portability are actually solved by emerging technologies (vivliostyle, new CSS standards etc)
-
-
Replying to @blahah404 @o_guest
Lot of work to be done making all that stuff accessible and building it in to actual production systems, but that's what we're doing ^_^
1 reply 1 retweet 2 likes -
Replying to @blahah404 @o_guest
It's not that journals will take papers in HTML - how you submit won't matter, but there'll be excellent HTML-native authoring tools
1 reply 1 retweet 2 likes -
Replying to @blahah404 @o_guest
All this stuff about fiddly word macros is dead - in a few years it will be gone. Open frameworks for robust arbitrary document conversion
1 reply 2 retweets 7 likes -
Replying to @blahah404 @o_guest
Suspect people have been saying that for decades. The problem is humanity.
1 reply 0 retweets 1 like -
Replying to @BioMickWatson @blahah404
Why? Some journals already serve papers in HTML.
2 replies 0 retweets 0 likes -
Replying to @o_guest @blahah404
No-one will ever agree on any single standard, and even if "we" do, Microsoft, Apple, Amazon etc will mutate their own versions
1 reply 0 retweets 2 likes -
Replying to @BioMickWatson @o_guest
While this is true I don't think it's a challenge to what I said above. Instead of every publisher with custom crap, open lib of conversions
2 replies 0 retweets 1 like -
Replying to @blahah404 @o_guest
I think what's more interesting is why we put almost the entire opus of human knowledge into unstructured documents in the first place
2 replies 1 retweet 3 likes -
Corpus not opus
1 reply 0 retweets 1 like
Both work tbf!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.