Edition Windows 11 Pro Version 22H2 OS build 22621.1413 Experience Windows Feature Experience Pack 1000.22639.1000.0
Steps to reproduce:
1) Open notepad, enter a text with a linebreak, copy & paste into the keywords field. This creates a keyword with a linebreak. Practical usage case: I am copy-pasting animal species names from nature kindle books to the respective animal pictures. Since the line breaks don't show as a special carachter, they are not obvious in case the copied line break matches the display linebreak in the keywords field
2) Export the keywords (CSV method)
3) Try to import the keywords into lightroom. This returns an error about invalid data.
Expected behavior:
a) Either lightroom should filter special characters or
b) properly use quotes in CSV export and respect them on import
I observe the same misbehavior and agree that either LR should disallow the use of newlines in keywords or properly quote such keywords in the exported CSVs (and recognize the quotes when the CSVs are imported). The current behavior is clearly not designed by a product manager.
I verified that the bug recipe now works correctly -- a multi-line keyword is correctly quoted in the .csv created by Metadata > Export Keywords > Include Keyword Tag Options (.cvs), and it is correctly imported by Metata > Import Keywords.
The multi-line keyword isn't exported/imported correctly using Export Keyword Tag Options (.txt) (not surprising given the format of the text file). Ideally, LR would give an error in that case rather than silently failing.