search

sanskrit / raw_etexts

https://sanskrit.github.io/projects/text/
44 stars 29 forks source link

Where do proof read items go? #26

Closed drdhaval2785 closed 4 years ago

drdhaval2785 commented 4 years ago

It is good to have raw etext repository.

But where will we put the files after proof reading?

vvasuki commented 4 years ago

Same place - replace the file. There is no sense in retaining unproofread file once proof-read version is available.

drdhaval2785 commented 4 years ago

Wont raw become redundant then?

Can we have a separate repo for proof read items? That would reduce the clutter also.

vvasuki commented 4 years ago

Wont raw become redundant then?

Didn't understand this.. "raw" in raw_etexts means "mostly unencoded and unformatted".

Can we have a separate repo for proof read items? That would reduce the clutter also.

Having a separate repo has the advantage of "reducing clutter", yes. But, it has the disadvantage of people potentially using unproofread files. Also, proof-reading is a matter of degree - can be partial or full.

Let us instead inisist on and follow the convention of naming files based on proof-reading status. For example:

vvasuki commented 4 years ago

Updated https://github.com/sanskrit/raw_etexts/blob/master/README.md - check it out..

lalitaalaalitah commented 4 years ago

Create a new branch for corrected/proofread file and we may use it to release versions. Let the master be raw. Sometimes people change things which they don't understand and hence distort.

vvasuki commented 4 years ago

Create a new branch for corrected/proofread file and we may use it to release versions. Let the master be raw.

Still think that the solution from https://github.com/sanskrit/raw_etexts/issues/26#issuecomment-667614365 is good.

Sometimes people change things which they don't understand and hence distort.

This is not a big danger since people mostly contribute via pull requests and we are in a position to check/ accept/ reject.