Why and How I Wrote My Academic Book in Plain Text

Re:Why and How I Wrote My Academic Book in Plain Text by iamcurious on Friday April 17, 2015 @03:56PM (#9396830)

Not sure what is the right way to do it. But in principle it shouldn't be a problem. An script could make a copy of the files but with one sentence per line. So you could edit the original and then uae the transformed version for version control.

[ Parent | on HN ]

Re:Why and How I Wrote My Academic Book in Plain Text by function_seven on Friday April 17, 2015 @04:47PM (#9397117)

The inquisitive Lt. Function_Seven asked, "How would the script know where one sentence ends and another begins?" as he began typing his query into the Yahoo! Search toolbar.

:) I think you just made the case for bringing back the two spaces after a period rule!

[ Parent | on HN ]

Re:Why and How I Wrote My Academic Book in Plain Text by kylebgorman on Saturday April 18, 2015 @12:20AM (#9398292)

FWIW, basic machine learning approaches to "sentence boundary detection" (as the task is called) get 199 out of 200 of these right (without using the "two space" clue), and have for a while. (e.g., http://sonny.cslu.ohsu.edu/~gormanky/blog/simpler-sentence-b...)

[ Parent | on HN ]

Re:Why and How I Wrote My Academic Book in Plain Text by kijin on Saturday April 18, 2015 @02:06AM (#9398461)

For the purpose of version control, it doesn't even have to be exact. It doesn't matter if the detector inserts an incorrect line break after a certain combination of characters, as long as it does so consistently so that it produces a readable diff.

[ Parent | on HN ]

Re:Why and How I Wrote My Academic Book in Plain Text by iamcurious on Friday April 17, 2015 @05:07PM (#9397202)

    Ha.  You might be right.

[ Parent | on HN ]