private static SymbolPath getSymbolPathFromMangledTypeName(String mangledString,
			String fullPathName) {
		MDMang demangler = new MDMangGhidra();
		demangler.setErrorOnRemainingChars(true);
		demangler.setMangledSymbol(mangledString);
		try {
			MDDataType mdDataType = demangler.demangleType();
			// 20240626:  Ultimately, it might be better to retrieve the Demangled-type to pass
			// to the DemangledObject.createNamespace() method to convert to a true Ghidra
			// Namespace that are flagged as functions (not capable at this time) or types or
			// raw namespace nodes.  Note, however, that the  Demangler is still weak in this
			// area as there are codes that we still not know how to interpret.
			return MDMangUtils.consolidateSymbolPath(mdDataType, fullPathName, true);
			// Could consider the following simplification method instead
			// return MDMangUtils.getSimpleSymbolPath(mdDataType);
		}
		catch (MDException e) {
			// Couldn't demangle.
			// Message might cause too much noise (we have a fallback, above, to use the regular
			// name, but this could cause an error... see the notes above about why a mangled
			// name is checked first).
			Msg.info(AbstractComplexTypeApplier.class,
				"PDB issue dmangling type name: " + e.getMessage() + " for : " + mangledString);
		}
		return null;
	}
Returns the symbol path for the data type referenced by the type record number provided
@param applicator the applicator
@param recordNumber the record number
@return the symbol path
Ghidra/Features/PDB/src/main/java/ghidra/app/util/pdb/pdbapplicator/AbstractComplexTypeApplier.java