Skip to content
Prev 37609 / 63424 Next

CMD check: checking data for non-ASCII characters is very time consuming

Checking data for non-ASCII characters takes a very long time for
packages with substantial data components.
Could the check be done manually by the developer, and a switch
introduced to optionally skip this during check?