Support for a certain generated MD5 files

[BobbyWibowo]

I have these kind of MD5 files:

; Generated by FastSum - an extremely fast checksum utility.
; Go to www.fastsum.com to get your own copy for free.
;
; UTF8: *01 - 하늘 사이로.flac
6873C64A076D7B6CB772AAACDC25F1C3 *01 - ?? ???.flac
; UTF8: *02 - 너에게 보낸 내 마음.flac
83DA161F6955D0777DA2CBBD1C53EA33 *02 - ??? ?? ? ??.flac
; UTF8: *03 - 슬픔, 물 위에 잠들다.flac
1AB18B1B725D29C1EA5EFD6B6F451EE4 *03 - ??, ? ?? ???.flac
; UTF8: *04 - 너의 마음속엔 강이 흐른다 (River Flows In You Feat. Ruvin).flac
0D557D1407DAF5BFC50D93D6E856F230 *04 - ?? ???? ?? ??? (River Flows In You Feat. Ruvin).flac
; UTF8: *05 - 그 끝에는 내가 잊을까.flac
6650853BB2DBFDEAB07444F87BE72111 *05 - ? ??? ?? ???.flac
; UTF8: *06 - 잊혀지는… 잊혀질 시간들.flac
87CEE127D7F9B0A7986720C5D520B8B4 *06 - ????? ??? ???.flac
; UTF8: *07 - 나에게로(To My Heart).flac
72531843FF5C7D926690459C0ABD5BAF *07 - ????(To My Heart).flac
; UTF8: *08 - 함께 떠나다(How Could I).flac
F664030400B489971C5A2DD3043E6252 *08 - ?? ???(How Could I).flac
; UTF8: *09 - 잠시(Just For A While).flac
1AC58B508FFF0858F27E24F98F25646F *09 - ??(Just For A While).flac
60E4E27E6090EF08604F05672420C123 *10 - Dream.flac
; UTF8: *11 - 널 그리다 (The Things I Really).flac
D0D027BAE2E44C2B32627D2D83F7BA9A *11 - ? ??? (The Things I Really).flac
; UTF8: *12 - 사랑하기를 (Beloved) By 정재욱.flac
F4B2C019E544C193B7C1B862B7E279B3 *12 - ????? (Beloved) By ???.flac
; UTF8: *13 - 어떻게 날 잊어야 하는지.flac
3FF860AA5CB9B9F7E288BD64E7F1A09F *13 - ??? ? ??? ???.flac

but it seemed that when you open the MD5 file with HashCheck, it wouldn't read the UTF8 name, but instead the question marks name, so they'd always appear as unreadable because files with those question marks names didn't exist.
So yeah, would you please add support for such MD5 files?

[ghost]

While this is a year old, I'd like to state this regardless: NTFS, which you're most likely using as your filesystem if you're using Windows, reserves the '?' character. Thus I suggest downloading VirtualBox and creating a Ubuntu VM that has access to the directory containing these files. Then you can either run md5sum on the files to check them, or rename the files to remove the illegal character so that you can use HashCheck to verify them on Windows.
HashCheck, to my knowledge, can't circumvent this if it's reading and writing from/to a drive using NTFS.

[ThomasCr]

I think he want to say, that this file format has a line UTF8 in a comment above the hash. He is asking for support this file format, so when hashcheck detects a line with UTF8: it read the filename from there with the hash from next line.

[BobbyWibowo]

Yeah, I meant that.
I wasn't really sure why the file generated by FastSum was formatted that way, to be honest. But I kinda assumed it was intentional since perhaps otherwise it wouldn't work properly with UTF-8 file names or something like that, and then I assumed making a workaround for that would not be too troubling.
I guess..? It has been a year and I don't even have the original files anymore anyways.