I can work on this, but I would like to establish the best way to do this first.
AFAIK, this would mostly be limited to patching the ERR() macro so that the NSLocalizedDescriptionKey of the error actually contains a localized string (via NSLocalizedString()). Additionally, the non-ERR() uses of [NSError errorWithDomain:…] would need to be similarly augmented.
We would also have to expose the strings to enable genstrings to find them. So an alternative to the above would be to wrap all naked string literals in uses of ERR() with NSLocalizedString().
Anything I have overlooked?
I'm not sure I want to do this. Ideally adopters of DDMathParser would provide their own context-relevant strings based on the code of the error.
Perhaps the real issue here is that the ERR macro shouldn't be putting the string in as the localizedDescription.
That’s a good idea. Thanks Dave!
Don't use `NSLocalizedDescriptionKey`, since the errors aren't actual…
…ly localized. Fixes #59
Fixed on the 1.1 branch.