Preserve uncertainty of localizations
Preserve uncertainty of localizations

We now use the custom strings scanner for both building tables (so we
can read our "uncertainty" comment markers) and performing localization.
I've encapsulated this into an NSScanner subclass (which is horrible to
subclass, btw).

delicious-monster/DMLocalization