Is there an accepted convention for adding EAC’s extraction status report log file to FLAC metadata?

I already looked at the EAC+FLAC thread and this issue is not mentioned:
http://www.hydrogenaudio.org/forums/index....=eac+flac+image


When I rip a disc image, I get 3 files: WAV, CUE, and LOG. I want like to embed everything into the one FLAC. The CUESHEET tag is already standardized (foobar2000 reads it). Just wondering if everyone already agreed on syntax for the LOG file? If not, I’m using the keyword “EAC_LOG=” like this:

C:\tag_2.0.45\Tag.exe -f CUESHEET=DarkSideMoon.cue DarkSideMoon.flac
C:\tag_2.0.45\Tag.exe -f EAC_LOG=DarkSideMoon.log DarkSideMoon.flac

I know technically, that it will work. But I'm surveying what everyone else does. Also, do people add album images to FLACs?

(Yes, I know WavPack, etc can do all this but I’m sticking with FLAC for playback support.)

Embedding the cue sheet and the EAC log into the cd image is quite common. And it's supported by at least foobar2000 (cue sheet reading, personally I dislike fb2k's way of silently altering the tags/cue sheet, so if you don't want that set the image to read-only).

Then I use EACLOG instead of EAC_LOG. I don't know, but I think EACLOG is the most wide spread name, but there's no real standard name for the EAC log tag field.

You can use whatever tagging tool you like, but be aware that tag.exe prior to 0.46 WILL NOT work with EAC logs, because they contain the string "; " which is interpreted by tag.exe prior to 0.46 as a tag field seperator. This means tag.exe 0.45 and all prior versions will split the EAC log at those occurences and you end up with several EACLOG tags fields. So use tag 0.46b1, it uses "<#>" as a delimiter instead.