Looks like the LOC folks are also unaware of the existence of HyperCard clones such as SuperCard (a compiler) and subsequently Runtime Revolution (now discontinued): before the company stopped selling its end-product cross-platform HyperCard clone there was a brief open source foray, and some folks appear to still be trying to develop an open source XTalk platform (XTalk is the generalized descendant language of HyperTalk):
... They also don't seem to know about how files on an HFS filesystem all have separate resource/data forks: it's a distinctly different paradigm from the familiar a-file-is-a-stream-of-bytes convention of Linux/UNIX/NTFS, and some of their problem seems to arise because they're looking at a "flattened" HFS file that has been squished to fit on a non-HFS filesystem. (Modern macOS makes almost no use of resource forks, so they're vestigial in HFS+; not sure APFS even provides them.)
https://openxtalk.org/forum/
https://en.wikipedia.org/wiki/XTalk
... They also don't seem to know about how files on an HFS filesystem all have separate resource/data forks: it's a distinctly different paradigm from the familiar a-file-is-a-stream-of-bytes convention of Linux/UNIX/NTFS, and some of their problem seems to arise because they're looking at a "flattened" HFS file that has been squished to fit on a non-HFS filesystem. (Modern macOS makes almost no use of resource forks, so they're vestigial in HFS+; not sure APFS even provides them.)