Skip to main content
TatuMbili
Inspiring
September 30, 2022
Answered

RH2020: default.css not appearing in assets/css folder in output

  • September 30, 2022
  • 5 replies
  • 172 views

I have three versions generated from a single project, Windows, Linux and Mac versions. When I generate the Windows version, I can see the default.css in the assets/css folder in output. For Linux and Mac however, the default.css does not appear there. As a result, my @11220649-face embedded font is not used, I get the default Times New Roman font being used. I searched in the community for answers and checked something Peter had referenced, checking the source of the output for something like this: <link rel="stylesheettype="text/csshref="../assets/css/default_pg.css"/> and what I'm seeing in Linux and Mac versions is this: <link rel="StyleSheet" href="template/myproject_screen/layout.css" type="text/css"/>. In Windows, it is this: <link rel="StyleSheet" href="template/MyProject_screen/layout.css" type="text/css"/>. Why is my default.css disappearing when I generate?

    This topic has been closed for replies.
    Correct answer TatuMbili

    I answered my own question. I had selected Use lowercase filenames in my presets. For some strange reason, the default.css does not get generated into the css folder. Therefore it's missing and default fonts are applied, hence TNR. Unticking Use lowercase filenames fixed the issue and my output looks great.

    5 replies

    Community Expert
    October 3, 2022

    Because the said it is fixed when they turn the setting off, I'm assuming some file or folder capitalisation isn't changed correctly somewhere along the way.

    Peter Grainge
    Community Expert
    Community Expert
    October 3, 2022

    What I couldn't make sense of is default.css is lowercase to start with but regardless of that, the file has gone AWOL. I could understand it being in the wrong case and not working but I don't get it not generating at all.

     

    @TatuMbili  Can you try a new simple project to see if this can be replicated. If it can, then it is definitely a bug but it seems an unlikely one. I appreciate you have got things working on this but I wonder if there are similar issues in the output that you haven't found yet.

    ________________________________________________________

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

     

    Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
    Community Expert
    October 3, 2022

    It's also about folder capitalisation, not just file names.

    Peter Grainge
    Community Expert
    Community Expert
    October 3, 2022

    The supplied default.css is set up with lowercase letters so I am puzzled as to how applying Use Lowercase would cause a problem.

    ________________________________________________________

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

     

    Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
    Community Expert
    October 2, 2022

    Someone else posted an issue that sounds like a case-sensitive issue when their help was loaded to a Linux server. So it could be a bug with the "lower case file names" setting you mention. It might be worth posting a bug about it. You can request features and report issues here: https://tracker.adobe.com/

    Post the item number in the discussion so people can easily vote if they want the same functionality.

    TatuMbili
    TatuMbiliAuthorCorrect answer
    Inspiring
    September 30, 2022

    I answered my own question. I had selected Use lowercase filenames in my presets. For some strange reason, the default.css does not get generated into the css folder. Therefore it's missing and default fonts are applied, hence TNR. Unticking Use lowercase filenames fixed the issue and my output looks great.