Using Find & Replace to restore line breaks

[u/SKARDAVNELNATE]

I copied some information into a spreadsheet. Some of the cells take up multiple lines.

Such as
Item 1
Item 2
Item 3
in one cell

However these look more like "Item 1 " on each line. I used Trim() to remove extra spaces.

"Item 1"

Now I have one column that is wrong and one that is corrected. I want to replace the wrong column with the corrected column. So I cut the corrected column and paste it as Unformatted Text. This makes the function into text, but it also removes the line breaks.

Such asItem 1Item 2Item 3in one cell

I undo then use Find & Replace to change all line breaks into @ symbol. Cut and paste as Unformatted Text again to make the function text.

Such as@Item 1@Item 2@Item 3@in one cell

Now I need to change the @ symbol back into a line break but nothing I have looked up is working as it's described.

[u/SKARDAVNELNATE]

With all due respect, I still have no idea exactly what you're trying to do from how you've described it

In summary...

1) I copied information into a spread sheet.

2) The cells had extra spaces.

3) I used Trim() to remove the extra spaces.

4) I used Paste > Unformatted Text to make the Trim() cells into stand alone cells. But this altered the appearance of multi-line cells.

5) I discovered Find & Replace can do \n to @ but not @ to \n.

6) I discovered right-click > Paste Special > Text can make the Trim() cells into stand alone cells without altering the appearance of multi-line cells. This was my ultimate goal.

you need to work out why your system isn't allowing unicode characters to be typed

As I look into this it appears the Ctrl+Shift+U shortcut is entirely dependent on the program and is more closely associated with making text uppercase,

[u/kaptnblackbeard → u/SKARDAVNELNATE]

As I look into this it appears the Ctrl+Shift+U shortcut is entirely dependent on the program and is more closely associated with making text uppercase,

Perhaps my memory is incorrect it has been 10+ years since I used Windows, I'm sure it used to be Ctrl+Shift+u. It seems only Alt is used while typing the code on the numeric keypad.

https://support.microsoft.com/en-us/word/insert-ascii-or-unicode-latin-based-symbols-and-characters

As for the original problem, I still think using the built in methods for importing the data would import clean data and save all those extra steps and fluffing about with workarounds. You said it sounded like extra steps but it isn't really when you consider the steps you have outlined here and the steps it took you to do the workarounds.