Best Practice when there has been historical use of commas and dashes in Chart of Account Value Sets

Summary:

What is the best practice when historical entries in the chart of account values sets contain restricted ESSbase characters such as commas and dashes in the descriptions (Alias for Member).

Content (required):

I just came across these articles/documents (below). I have recently inherited the task to maintain the chart of account values sets. We have a lot of historical use of commas and dashes in our descriptions (Alias for Member). I'm unaware of downstream issues in the ESSbase cube side of things. Should we proactively clean up all these entries so they comply with this information found in the reference docs in this article even though we don't know of any issues?