Looking at some code, I was sorting through strings that should be put into
a resource file for localization and seeing which ones are not localizable.
I'm used various tools to easily put the strings into a resource file, but
it is still a manual process of evaluating whether a string should be
localized or not.
Over the years it has been different syntax in the variable name to denote
it is not localizable, and I just wondered why there is not a
System.Text.NonLocalizableAttribute offered to denote strings that should be
left alone.
If there was a standard attribute for that purpose, then internal (or
external) tools would use that tool to aid in the process of automating the
process transferring strings from the code to a resource file.
Even if we created that attribute in house other 3.rd party tools wouldn't
know to ignore that type of tag. So the code would look better but there
would be limited benefit.