There is no guarantee that our tools will work across the flow if you edit symbol files using a text editor and use characters currently blocked in the UI. We have no idea whether when you netlist to some other third party tool this will work and so cannot take any responsibility for problems this introduces.
As to your first point, we support open and closed parentheses () to support block symbols with bus pins such as Address(15:0) which are fully supported by the tools.
I forgot to mention that the manuals prohibit the use of open and closed parentheses () but allow / and space.
But the symbol editor does not!
Is this a bug in the manual or in the editor?
It's an issue with the manual which is being updated currently.
Ok Thanks Robert,
I hoped it was an issue with the symbol editor, so we could keep using the "/" as we did in Design Capture.
In this case if you have no issues with the / character in your DC - Expedition flow and you are not altering your process you can probably use the 'workaround' you first mentioned. The acceptable character set for properties is under review as we migrate customers from our other flows to DxDesigner - Expedition but we have to carry out due-diligence on any changes we make to ensure we do not break our processes and tools.