Page 1 of 1

is there a way to use the original form of file name in the webhelp output

Posted: Tue Feb 27, 2024 12:24 pm
by galanohan
For example, a file named S00001.dita, which represents a topic file explaining error code S00001.
In local transformation, the output URL displayed as I expected: file:///D:/dita_gitlab/zh/out/webhelp-responsive/error_codes/S00001.html
While in a publishing engine output over cli, I found the first letters of files in html format use the lower case, for example, /root/ci/public/zh/2.00.11/error_codes/s00001.html.
Is this behaviour normal?
Or is there any configurable parameter that keeps the original spelling of a source file name in the webhelp output?

Thank you!

Re: is there a way to use the original form of file name in the webhelp output

Posted: Tue Feb 27, 2024 12:54 pm
by galanohan
oh I found the issue was caused by the Git Windows ignores the file name changes between uppercase and lower case by default.
To force the git detect and record such changes, disable the ignorecase parameter using the following command in git shell:
git config --global core.ignorecase false
Then validate the value of ignorecase in C:\users\<username>\.gitconfig to make sure it's set to false, in other words, git will not ignore case changes no more.