I'm sorry you have that impression Gaile, but I don't think that's true at all. Changes and improvements have to be very carefully thought out and planned, or else they can do more damage than good, if implemented poorly and not well tested. There are many scenarios to consider.
Particularly, in this case, I, myself am now leaning towards this not so much being a Gedcom import bug, but rather an edit profile display bug (once the data is there, we need to see it and be able to edit it).
Not using quotes and other special characters in a name field is more of a Style and Guidelines issue, and is not strictly prohibited in a Gedcom file format.
It proves to be quite problematic in trying to programmatically choose what to do with them when encountered. There's just not a "one-size-fits-all" solution available.