Can you create a legacy mode that truncates on commas and a newer mode that doesn't? [#1226716]

Thank you for the update to allow non-numeric characters in the "Amounts" field! That will make my clients very happy. If you were to let me enter in values with commas, though, that would make me very happy. Currently, a value of

5000|$5,000 - Silver Ticket

will break the display, and create a second value after the comma. This is understandable, because versions prior to 6.x-1.8 use commas as the delimiter between items - and the need to maintain legacy data is important.

Is it possible to add a boolean switch before this field, so that the user can choose between legacy mode (defaulted, which keeps commas as a delimiter) and a newer mode, that lets the user use commas not as delimiters? That would allow for a more robust display of information, and especially use the traditional American comma delimiter at the thousands point.