Not directly the same code (because I believe DATheader needs the .NET framework), but running the header checks would be possible. In fact, I do run a Perl header checker against all the certified files prior to releasing a Parts Update. That's why you'll often see a bunch of Admin Edits immediately prior to the update, as I find things that have been missed by manual review.
I was initially reluctant to implement that in the Submit process for fear that authors would just get frustrated with trying to meet the needs of the then "new" header format, and we would lose files or even authors.
Maybe the format has had sufficient time to gain acceptance that it would be OK to implement it now.
I was initially reluctant to implement that in the Submit process for fear that authors would just get frustrated with trying to meet the needs of the then "new" header format, and we would lose files or even authors.
Maybe the format has had sufficient time to gain acceptance that it would be OK to implement it now.
Chris (LDraw Parts Library Admin)