Disable leading-zero suppression?

Oct 16, 2015 at 4:38 PM
When I specify a version with leading zeros, verpatch encodes it after performing leading-zero suppression. For example, 5.06.0004.1 and "5.06.0004.1" both result in Is it possible to retain the value as specified?
Oct 25, 2016 at 4:18 PM
Most of Windows executable files have file and product versions without leading zeros
(though I've seen few exceptions).

The Semantic Versioning spec also does not seem to allow leading zeros in numbers.

By "historic reasons" (in some Windows versions the Explorer displayed the version numbers from the fixed header, without leading zeros) this program keeps the string representation unified with these older versions.

So, the removal of leading zeros is deliberate.

-- dd.
Oct 25, 2016 at 9:28 PM
Merged your patch in v 1.0.15 today. Please check out.