Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: CR+LF vs LF for line break in Properties (Read 594 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

CR+LF vs LF for line break in Properties

Wikipedia says that according to Unicode Line Breaking Algorithm both LF and CR+LF should be recognized as line terminators.
But foobar2000 ignores LF when opening text in tags fields in Properties.
Is it bug or by intention or some Windows limitation?

Many files from Bandcamp are coming with lyrics having LF and not CR+LF.
Example file - https://www.dropbox.com/scl/fi/92ia4zqaqz2jz289sa2cd/06.-Iqaluit.flac?rlkey=q12wb1ge255hubfffejuv42fw&st=qhniy9gp&dl=1
BTW, i know that LF can be mass-replaced with CR+LF using "Format from other fields" and $replace(%unsyncedlyrics%,$char(10),$char(13)$char(10))

Re: CR+LF vs LF for line break in Properties

Reply #1 –
That - and "remove leading/trailing empty lines" - could go into an improved "Clean up". I must have requested that before.

Quote from: Bogozo on
Many files from Bandcamp are coming with lyrics having LF and not CR+LF.
I've even seen the Unicode 2028 <LS> from Bandcamp. But I wonder if that was at the end of a song title ...

Quote from: Bogozo on
BTW, i know that LF can be mass-replaced with CR+LF using "Format from other fields"
Also a wishlist item: a shorthand for "this field"

Quote from: Bogozo on
and $replace(%unsyncedlyrics%,$char(10),$char(13)$char(10))
$replace($replace(%unsyncedlyrics%,$char(10),$char(13)$char(10)),$char(13)$char(13),$char(13))
for those cases where there was already a $char(13)$char(10)).
And then there are those with only $char(13)'s ...