Forum Discussion
The pdfPublishingRule, used for converting TechDocs into PDFs, is not found in main.css so I may need to look elsewhere or send in a ticket to Aras to ask how I can navigate to that installed module's css folders.
Also, thank you, your response was quite helpful for me to come to this conclusion and it also gave me light in determining the conventional way of applying new styles to Aras. Seems like it is not too hard after all, maybe one day dark mode can come along (if they don't configure that for us in a release one day :) )
Edit: Actually I take back some of what I said - I just now navigated to the converter module, and imported the font face that I wanted. The font still isn't coming through, but this is good progress, hopefully I can find where I really need to apply it within the style's folder. With your response I should be able to deduce what place needs it. Hopefully the rendering of the font family will be a success!
OMG, why don´t we have a dark mode? I never questioned that this one was missing. Thumps up for this idea!!
Quote: "how I can navigate to that installed module's css folders"
Well, basically you navigate to the modules css folders :). There are modules folders and they have stylesheets.
But for PDF publishing you specify the style sheet inside Innovator itself. See "Document Types" in TOC.
Regarding my example with the font you also need to customize your Forms to actually use the new font or customize default.css.
- Frank_Guarino7 months agoIdeator I
Right, I was able to navigate to the Conversion Server css. Although, when it comes to using the font-style: 'Helvetica' in the Document Type css it still is not a valid property value.
Here's what I've done so far:
Added a font-face to fonts referring to the local file of the font .otf file
Added in reference to the css in the Document Type's css file
Edit: Font-family:'Helvetica' seems to be a valid property, but the rendering does not happen. I am unsure whether this is where the styling is needed or not.
- AngelaIp7 months agoIdeator I
Hope you document everything for the upgrade team!
Regarding TechDocs maybe have to differentiate the Viewer from the actual printed result?
- Frank_Guarino7 months agoIdeator I
Hmm. Oh I see what you mean. Yeah - the Output Settings has choice of Editor, PDF, and HTML - all outputs are used and all use the same CSS file so there should be no difference there.
The font has yet to render in the editor. Then I can postulate that rendering the font in the editor is what I need to direct attention to first. It has seemed uninhibited with most css, I know sometimes the HTML and Editor can look a little different despite the same styling, for instance sometimes font colors not showing correctly in the editor (atleast for us, we are using a mismatched version #s between Aras and Technical Documentation lol)