RH 2022: " Use lowercase file names" problems with thumbnails and folders

There is no equivalent of the CPD. The contents of the .rh folder can be deleted but you lose certain preferences and I'm pretty sure it is not going to help here.

I haven't reread the thread but have you copied the contents of the generate folder to a new folder on the Linux server and tested that?

I think I would be asking the Dev team to test an output with the Use Lowercase File Names deselected.

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

Thanks all.  Just a little timeline for clarification.

1. I first created this project in RH 2020 (last update, I believe), with mixed uppercase/lowercase folder names and file names, for Frameless output.

2. Later, I was directed by the corporate styling team to use lowercase names, so I enabled the "use lowercase file names" setting so I wouldn't have to rename files (and hopefully folders) that I had already created.

3. Then I upgraded to RH 2022.

For my Frameless output, I waffled between the two options for "Show Thumbnails for Images", but finally settled on using "Create Thumbnails for Images" which always creates a smaller filename_th.ext copy of my image files.  I can't say for sure whether I did this in RH 2020 or RH 2022.

At some point, I also noticed that because I had turned off the Windows Recycle Bin (long story), RH never properly deleted the existing _th thumbnail files when rebuilding to the same output path, and I would get multiple versions of the same _th files.  So I turned Recycle Bin back on.  I never noticed any other adverse effects while using RH - just the buildup of _th files - before restoring the Recycle Bin.

4. Then our dev team began hosting it on a Linux server.

5. That's when I noticed that some of the thumbnails and their base images were not displaying correctly - despite this RH setting.

In particular, I have noticed this behavior when the file or folder name begins with lowercase characters but also includes uppercase characters - like the images I posted in one of the bug reports.

My current workaround is to manually rename all of the folders and image files with only lowercase characters.

I was unable to reproduce this behavior on the sample project, so I really don't know why this happened with my real project and not the sample.

Does anyone know if there is a file or folder to delete and let RH 2022 rebuild - analogous to the .cpd file in older versions of RH?

I have just tested this in a new 2022 project and selecting Use Lowercase File Names converted the folder name as well as the file name.

I then added an image with mixed case and the file name was converted in the output.

Does it persist if you generate to a new output folder and can you replicate the problem in any other project.

That said, simply not using the setting should fix things as Linux is case sensitve, not lowercase only, to the best of my knowledge.

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

I tested with Classic 2019 Webhelp and Multiscreen HTML5 output and the folders as well as file names are converted to lowercase using that setting. The setting doesn't exist for Responisve HTML5 in Classic 2019 for some reason.

If New UI isn't converting the folders as well, I would consider that a bug.

If it's not changing the thumbnail paths to lowercase to match I would be tempted to consider that a bug too, as it doesn't meet the requirements of the setting, which is to fix potential path problems on unix systems. The regular links and paths are changed in Classic Webhelp/Multiscreen, but I can't test the thumbnail functionality which is only available in Responsive HTML5 in Classic 2019.

Use lowercase file names" is not CORRECTLY applied to folder names. The setting is FILE names not FOLDER names. Was this working in an earlier version of RoboHelp and, if so, which version(s)? To the best of my knowledge nothing has changed for this setting so I would expect more users reporting this as an issue.

More immediately though, why use the setting? If you didn't use the setting then everything would be mixed case which is fine on Linux. I do recall seeing the occasional post way back that using this setting caused issues and simply deselecting it fixed them.

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

Is it misbehaving in the sample project too?