08-07-2023, 08:43 AM
The idea of using only semicolon for composer and artist makes sense to me.
Using either comma or semicolon for other list fields should work. I can't think of any reason that would cause me any headaches.
Your proposal to look for a semicolon in a list field, and if you see one then to proceed on parsing using only semicolons actually sounds pretty ideal to me. If the coding isn't too complex. One edge case to consider for this proposal: let's say that in some list field I really do only want one item, but that item's text has a comma in it. Seeing no semicolon you would parse it on that comma into two items. What you could allow for this edge case is a semicolon at the end of the single item's text which you would detect and not parse on the comma. This at the risk of making the user manual more complex of course...
Using either comma or semicolon for other list fields should work. I can't think of any reason that would cause me any headaches.
Your proposal to look for a semicolon in a list field, and if you see one then to proceed on parsing using only semicolons actually sounds pretty ideal to me. If the coding isn't too complex. One edge case to consider for this proposal: let's say that in some list field I really do only want one item, but that item's text has a comma in it. Seeing no semicolon you would parse it on that comma into two items. What you could allow for this edge case is a semicolon at the end of the single item's text which you would detect and not parse on the comma. This at the risk of making the user manual more complex of course...