# Convert ‘Text file - tag’ unable to parse **URL:** \ **Category:** Support\ **Created:** [May 29, 2022, 3:48pm UTC](https://community.mp3tag.de/t/convert-text-file-tag-unable-to-parse/57442 "2022-05-29T15:48:07Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![mazeckenrode](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/e68b1a/32.png) [@mazeckenrode](https://community.mp3tag.de/u/mazeckenrode)\ **Post date:** [May 29, 2022, 3:48pm UTC](https://community.mp3tag.de/t/convert-text-file-tag-unable-to-parse/57442/1 "2022-05-29T15:48:07Z")
Currently using MP3Tag v3.14. I’m attempting to import multiple tag fields from a text file, using a file with data such as: `1. “Song Title” (Tom Composer; Dick Lyricist; Tom Composer, Dick Lyricist) — 3:13#CRLF#ART: Tom, Dick & Harry#CRLF#PRS: Tom Composer — vocals, arrangement#CRLF#Dick Lyricist — vocals, arrangement#CRLF#Harry Armpits — piano, arrangement` My format string: `%track%. “%title%” (%composer%; %lyricist%; %composersort%) — %dummy%#CRLF#ART: %artist%#CRLF#PRS: %personnel%` (I have separate actions configured to properly format **COMPOSERSORT** and replace **#CRLF#** with actual Windows end-of-line sequences, which I run after importing the data.) I have used text data and format strings like these many times before, but MP3Tag keeps telling me it’s unable to parse any of the lines in this file. I’ve looked them over again and again, read and re-read the ‘Text file - tag’ help, and searched for forum posts by users with similar problems, without any luck. I think I need a fresh pair of eyes on this. Anybody? ---
**Author:** ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)\ **Post date:** [May 29, 2022, 3:52pm UTC](https://community.mp3tag.de/t/convert-text-file-tag-unable-to-parse/57442/2 "2022-05-29T15:52:20Z")
I do not find > [@mazeckenrode](#): > > #CRLF#PRS: in the data string, just > [@mazeckenrode](#): > > #CRLF#Harry the PRS: is missing. ---
**Author:** ![mazeckenrode](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/e68b1a/32.png) [@mazeckenrode](https://community.mp3tag.de/u/mazeckenrode)\ **Post date:** [May 29, 2022, 4:01pm UTC](https://community.mp3tag.de/t/convert-text-file-tag-unable-to-parse/57442/3 "2022-05-29T16:01:02Z")
> [@ohrenkino](#): > > the PRS: > is missing. It’s there. Here’s the middle section of the data string with **PRS:** included: `#CRLF#ART: Tom, Dick & Harry#CRLF#PRS: Tom Composer — vocals, arrangement#CRLF#` ---
**Author:** ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)\ **Post date:** [May 29, 2022, 4:17pm UTC](https://community.mp3tag.de/t/convert-text-file-tag-unable-to-parse/57442/4 "2022-05-29T16:17:07Z")
Ah, got it, I just tried it with a single file that imported your data with your string and it worked. So now you have to look at your data file and see what may be wrong. E.g. the format string should not be included. Also, empty lines should not be there. Just as possible causes. ---
**Author:** ![mazeckenrode](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/e68b1a/32.png) [@mazeckenrode](https://community.mp3tag.de/u/mazeckenrode)\ **Post date:** [May 29, 2022, 5:31pm UTC](https://community.mp3tag.de/t/convert-text-file-tag-unable-to-parse/57442/5 "2022-05-29T17:31:08Z")
> [@ohrenkino](#): > > I just tried it with a single file that imported your data with your string and it worked. I had already tried that here, and just tried it again, once on an MP3 and once on a FLAC file. Unable to parse, everytime. > [@](#): > > So now you have to look at your data file and see what may be wrong. > E.g. the format string should not be included. > Also, empty lines should not be there. Check, check, check. I also just upgraded to MP3Tag v3.15 (32-bit). I don’t know what else to try. ---
**Author:** ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)\ **Post date:** [May 29, 2022, 5:35pm UTC](https://community.mp3tag.de/t/convert-text-file-tag-unable-to-parse/57442/6 "2022-05-29T17:35:40Z")
So, as the dummy data that you supplied plus the probably real format string work together fine (or don't they work for you either?), it would be nice if you could supply a (part of the ) real data file, just 3-4 records. These should be tested that they don't work for you and then the community could try them as well and see if anything can be found. ---
**Author:** ![mazeckenrode](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/e68b1a/32.png) [@mazeckenrode](https://community.mp3tag.de/u/mazeckenrode)\ **Post date:** [May 29, 2022, 7:19pm UTC](https://community.mp3tag.de/t/convert-text-file-tag-unable-to-parse/57442/7 "2022-05-29T19:19:00Z")
> [@ohrenkino](#): > > So, as the dummy data that you supplied plus the probably real format string work together fine (or don’t they work for you either?) Neither real nor dummy data were working for me. But I just went through and tried importing incrementally larger portions of the dummy data for one track (just track # first, then track # and title, then track/title/composer, then track/title/composer/lyricist, then track/title/composer/lyricist/composersort) and as far as I can tell, I found that the problem was somewhere between `%lyricist%` and `%composersort%` in my format string, not apparently in my data string. I suspect that maybe, as I originally entered it into MP3Tag, I inadvertently put a non-breaking space, or other character that looked just like a space to the naked eye, between the two. I basically manually replace anything that looked like a space in the entire format string with an actual, normal space, and then my import worked as expected. I can only guess that when I pasted the original format string into my first post above, the forum software maybe converted any and all quasi-spaces to real spaces? Might be worth some experimentation on somebody’s part. Anyway, I’m really liking the new **Manage History** feature for the format string (and whatever other) fields. I’d been wondering how to do that anyway, but getting rid of this problematic format string was a sudden priority. Done! And thanks much for taking a look, @ohrenkino. ---
**Author:** ![system](https://community.mp3tag.de/uploads/default/original/2X/c/ce7035d426cb755a7916793326d23b465222a407.png) [@system](https://community.mp3tag.de/u/system)\ **Post date:** [June 28, 2022, 7:19pm UTC](https://community.mp3tag.de/t/convert-text-file-tag-unable-to-parse/57442/8 "2022-06-28T19:19:49Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.