Those corrections in the brickset thread you mention are from LDCad's logfile.
With LDCad I actually correct the LDraw lines in memory, they are just never written. Maybe it could be useful if I made that possible?
Correcting many errors (bowties, matrix with zeros in a single row, case mismatches, etc) in the current library would then be possible by just loading a dummy ldr in LDCAd containing references to every file in the parts folder followed by a special save command.
Will be a nice stress test too, might need the 64bit version memory wise.
With LDCad I actually correct the LDraw lines in memory, they are just never written. Maybe it could be useful if I made that possible?
Correcting many errors (bowties, matrix with zeros in a single row, case mismatches, etc) in the current library would then be possible by just loading a dummy ldr in LDCAd containing references to every file in the parts folder followed by a special save command.
Will be a nice stress test too, might need the 64bit version memory wise.