A REGISTRY mystery - reg file doesn't import properly

@TairikuOkami thanks but you are not seeing the problem. What you have posted has nothing to do with the problem. Review my last post again. The program that created the registry entries in the first place is Repetier Host a 3D printer program. It recorded multiple printer commands separated by CR/CR/LF as a single value in the registry. Regedit appears to export them correctly as seen in the Ultraedit snapshot, but upon import is relying on a CR or LF or both to terminate the " thereby seeing an invalid entry and dropping it (without any warning by the way). The CR and LF in those entries are part of the entry (as shown in my post) and should be imported intact as one value. Regedit should rely on the next " to terminate it, but God knows what other issues that would create when the other " was actually missing.
So how did Repetier manage to create these entries? And is there any possibility I can import them - It isn't going to happen with Regedit unless MS changes the way they handle CR/LF. If I change the data type then Repetier probably won't be able to read it.

Well, I long for the old INI files. They were easy to fix and modify. But the registry is "suppose" to be just one big INI file. Somehow, Repetier Host is manipulating the registry and making it work for them. BUT regedit can't handle its own creation.
I don't know if what Repetier is doing is defined by MS as being non-conforming. If I knew that I would go back to Repetier to fix their product. But one of them is not right because a basic function (export/import) does not work. I venture to say that a registry backup and restore would not work either, but it may be implemented different than an export/import.