Hi T,
[I'd like to see this capability added. See below.]
No, you cannot do this, at least not now. However...
Since you are new to EA and the forum, please bear with me a bit.
While EA does not allow you to specify how to parse a file, Sparx (i.e. the company, not the product) does allow you to request new features. You can ask for this, and they will consider it. You don't have to be a registered user to make such requests. If you have enough interest in the product to try it out, then Sparx has enough interest to read your request.
Making a feature request is not guaranteed to result in a change, but it will be looked at. After all, if nobody expresses an interest in a feature why bother with it, but if some users ask for it, then perhaps it is worth the devoting resources to the development effort.
Something like the issue you bring up here would (almost certainly) not show up between EA versions, it is just too big a change. But perhaps it would be a candidate for EA 8.0. [If things follow the usual path then 8.0 could be the next version change. Usually the x.5 version precedes a major version change.]
If you can make due with the 'long' process (replacing the entire file, as Simon describes) for now, then why make the request. You'll find a Feature Request link beneath the Support link near the bottom of any forum page. Click that link to get to the correct place. But first...
A 'local best practice' we (the forum crowd) use for feature requests (and some bug reports) is to first start a thread to describe what's wanted. This thread would do fine for your situation - it does not need to be in the Suggestions section of the forum, it is fine where it is. Copy the URL of this thread, and when you make the request paste it in at the end of the problem description. This will point any Sparxians who consider the request to ongoing forum discussion. Perhaps other users will express support (as have I). The Sparxians are also active forum participants, and they might chime in. And you never know, perhaps someone has (or will) come up with a workaround, and you could see it here.
HTH, David