Andhrabharati
commented
7 months ago To implement this, the first order of business would be to come up with an xml tag and specification of how it might be introduced to identify in mw.txt an entry in mw_printchange.txt.
Next, how to display such markup in the cdsl displays.
@funderburkjim
I would like to draw your attention to a recent discussion, my post and your response followed by Marcis's post & your response thereof, at GRA that talks about this.
With this background, I am sure that you would come-up with a suitable solution quickly.
This solution would NOT ONLY be applicable to 'user-submitted' print-changes, BUT ALSO to the 'integration of additions and changes' that were given at various dictionaries into their 'main text' matter.
aumsanskrit
Over the years, many changes to the cdsl dictionary digitizations have been made and noted as print changes. It is getting to the point where these prior changes need to be taken into account when evaluating a proposed change (correction) to a dictionary.
Otherwise, a current observer might see a difference between an intentional change and the printed scans, and submit a change to revert to the printed version.
I'm thinking particularly about @aumsanskrit who has been submitting many changes to the mw dictionary. And simultaneously, I happened to be working on another project (non-english words) for MW which generated 40 or so new print changes. In his further work, @aumsanskrit probably should download mw_printchange.txt and consult it if he happens to be considering a change. This might be a practical temporary fix.
Better would be some integration of the printchange file information into the digitization (csl-orig/v02/mw/mw.txt, for instance).
To implement this, the first order of business would be to come up with an xml tag and specification of how it might be introduced to identify in mw.txt an entry in mw_printchange.txt.
Next, how to display such markup in the cdsl displays.
Once the specification is robust, actually integrating xxx_printchange.txt into xxx.txt would be a good project for someone, maybe for someone working with @gasyoun.
This is just an enhancement idea.