Include fonts when copying/moving retail data#213
Include fonts when copying/moving retail data#213jg18 wants to merge 2 commits intongld:developfrom jg18:include_retail_fonts
Conversation
|
Passes manual test when copying from a retail installation of the Polish version. But fails when using an installer file. I bet that what's going on is that Knossos is trying to move the font files twice, because I tried to compensate for case-sensitive file systems. I'll look into fixing this. |
|
@jg18 Be advised the English font files do have the lower-case .vf extension. |
|
Ok, how about this: since *.VF should work fine in case-insensitive file systems, and since generally only Linux uses case-sensitive, I’ll add something to the effect of “if we’re on Linux, look for .vf files in the fonts folder in addition to .VF files.” Basically reverting my last commit but limiting to Linux. |
|
Is it not possible to first grab a list of the files and then do the file operations? This is the problem I ran into with the FSO Installer: it might see MediaVPs, or mediavps, or MEDIAVPS. Since there was no way to tell which format someone would use, I had to assemble my own case-insensitive list of files or folders, do a case-insensitive check for whatever was present on the file system, and only then do the file operations. It was obviously quite a bit more work, but it was the only way to ensure reliable cross-platform, cross-mod file management. |
This PR should fix issue #211 .
However, getting it to work properly will require PR #212 because creating NSIS installers is currently broken in develop.
Still needs testing, will do that later.