Change History (5)

I'd be -1 on making this change. The abbreviation in question isn't a display string: it's the value stored in the database. We haven't made any error with the human-consumable string.

The big argument against changing it is that anybody who is already using this field will now have invalid data in their database. Suddenly they will have stored NF and it won't map to any display string (and entering the same data after the change will put different data into the database).

Moving to "design decision needed"; it's not a no-brainer and it's not a functional bug at the moment.