I have imported a lot of RoboHelp stuff into Flare. In RoboHelp, I had the "use lowercase filenames" setting ON, which worked fine. The software developers created links from each web page in the app to a page in the help. No cross-linking in the help... if your user account doesn't give you access to a configuration page, you don't see the help for it either.
So far so good. As I only had about a couple of dozen topics to import, I renamed a few before they got committed to source control. While I was renaming, I changed them to all lowercase. This meant that during my initial testing on Flare, I didn't use the "Use lowercase filenames" setting. I did, however, select "Do not use "Content" folder in output" - just cutting down the length of the paths, no other reason.
Now I've imported a whole bunch more topics from a different project. I *really* don't want to have to rename them all manually to sort out the case - and the software developers don't want to redo all their links. So I used the setting to use lowercase filenames.
Files aren't really the issue - the topic files converted fine. But the folders were a bit of a mixed bag. I didn't notice any problem because I'm running on Windows, but the application the help files are for is running on Linux. Case is definitely an issue!
In each topic file, I have a set of links to resources in the 'head' section of the file. Two of them are:
<link href="../resources/stylesheets/mainstyles.css" rel="stylesheet" type="text/css" />
<script src="../Resources/Scripts/custom.modernizr.js" type="text/javascript"></script>
The eagle-eyed among you will notice that I have "Resources" with a capital 'R' and "resources" with a lowercase 'r', both ../ from current location. Not an issue on Windows, but Linux threw its toys out of the pram and refused to play.
I asked support... and was told (1) the folders not in the Content bit don't get renamed (I took that to mean the Content Explorer bit... if I could see them there, they would be renamed, and it was even confirmed that the Resources folder holding the stylesheets WOULD be; (2) there were two 'resources' folders and only one was altered... I could only find one; (3) the one with the scripts in doesn't get renamed, the one with the stylesheet in does... at which point I gave up, as it's not possible (in Windows) to have two folders of the same name in the same location that only differ in capitalisation. Unfortunately, it wasn't spotted that there wasn't a "content" in the paths anywhere, and I didn't understand that that was the cause of the problem.
So, the moral of the story... if you want to set "Use lowercase filenames", you've got to have a "Content" folder or the "Resources" folder provided in Content Explorer is merged with the one containing the scripts. The setting to change case only affects the files and folder inside the "content" folder (or that would be inside that folder if you generated one). If you *don't* generate the "content" folder, standard Windows behaviour when you copy a folder to a location where there is already a folder of that name is simply to merge the contents. I'm guessing the "Resources" one was created first, so "stylesheets" was simply copied into it. I imagine renaming the Resources folder in Content Explorer would work too... but I'd have to remember to do that (and to the same name) each time I created a project.
That's taken the best part of a day to sort out... so if I can save someone else the headache...
