UNSYNCEDLYRICS Display with line feed

Support
1

When I've text in say notepad++ it reads

Release type:		Release
----------------------------------------------
Exclusive to beatport:	No
----------------------------------------------
Eating Hooks [Monkeytown Records] is available for download on Beatport, the world's largest DJ and electronic music community.
---------------------------------------------
Tagged by:		Mp3Tag w/ beatport.com scripts [v5.0 by stevehero™] (◣_◢) (http://bit.ly/2EmyidV)

But see screenshot of how it's displayed in Mp3tag. It's a FLAC file.

2018-02-13_19-06-35
2018-02-13_19-06-35.jpg702×348 55.7 KB

I'm cleaning the field using:
$regexp($trim(%unsyncedlyrics%),$\n+\s,\n)

Maybe it should be carriage return used as the replacement. I want to check this before I do anything stupid.

(Man I love this new preview while typing)

2

Doesn't this field require and to get a proper line break?
So if you remove the it is sort of broken, I suspect.

3

Not sure if I understand.

But yeah, I think it's broken.

4

Drat.
I wrote "carriage return" and "newline" in chevrons and apparently they got eaten by the editor.
So my replay in its full beauty should have been:

Doesn’t this field require "newline" and "carriage return" to get a proper line break?
So if you remove the "newline" it is sort of broken, I suspect.

5

You mean something like this?
$regexp($trim(%unsyncedlyrics%),\n+,\n\r)

Still doesn't work and displays wrong in the field, but copies over to NP++ just fine as it should be.

6

What does an unsyncedlyrics field look like in NP++ that you have editted in MP3tag?
It could still be that you have to set something in NP++ so that proper end-of-paragraphs are created.
Or you could check with a filter whether UNSYNCEDLYRICS contains \n and \r or just one of them.

7

The correct order of those characters is \r\n.

\r translates to carriage return (CR, ASCII code 13) to tell the "typewriter" to push the carriage back to the left so that the cursor is back to the start of the line. \n translates to line feed (LF, ASCII code 10) which moves the cursor down the page one line. It's ancient technology, but \r\n is still what's used on Windows.

8

To expand on the answer. This is the solution to my problem. Thanks.

$trim($regexp(%unsyncedlyrics%,$\r*\n*,\r\n))

9

Just like that in the first post. But found the solution via @Florian in above post.