For Arabic or other right-to-left languages, Pega Platform uses tools built into Java and HTML to automatically handle right-to-left conversion based on the user’s locale.
There are known issues with displaying icons in right-to-left languages like Arabic in Pega applications, but these are not specifically related to the Font Awesome icon library. These issues are more about how Pega handles right-to-left languages and how icons are displayed in these languages.
cromium-based browsers have problem with RTL locale. Button is there, just displayed under the field, so you can’t see it.
Please log a support incident on the MSP if the product is not working as documented. Please provide the INC reference here so that we can help track the issue with you.
This is a GenAI-powered tool. All generated answers require validation against the provided references.
The problem mabye occurs because FontAwesome icons rely heavily on CSS ::before pseudo-elements, and when working with RTL (Right-to-Left) languages like Arabic, additional CSS configuration is needed to ensure proper rendering. Here’s how to fix it:
Add RTL Support to Your CSS
[dir="rtl"] .fa::before,
[dir="rtl"] .fas::before,
[dir="rtl"] .far::before,
[dir="rtl"] .fab::before {
direction: ltr;
display: inline-block;
}
Ensure Proper HTML Structure Make sure your HTML element has the correct direction attribute:
<html dir="rtl" lang="ar">
FontAwesome CSS Loading Order
Ensure the FontAwesome CSS is loaded before any custom CSS
Add your RTL-specific CSS after the main FontAwesome CSS
Check Font Loading
Verify that the webfont files are properly loaded in the Network tab
Ensure there are no CORS (Cross-Origin Resource Sharing) issues
Check if the font-family is correctly specified in your CSS
Additional Recommendations:
If you’re using a custom font loading method, make sure it’s compatible with RTL layouts
Consider using the newer FontAwesome 6.x version which has improved RTL support
Test the icons in both RTL and LTR contexts to ensure consistent rendering
For Pega-specific implementation:
Make sure your application’s skin includes the necessary RTL support
Verify that the operator’s locale settings are correctly configured
Consider using Pega’s built-in icon library as an alternative if needed
If you’re still experiencing issues after implementing these changes, please:
Check the computed styles in your browser’s developer tools
Verify if any custom CSS is overriding the FontAwesome styles
Test in different browsers to isolate if it’s browser-specific
Actually after 5 hours of debugging it was very easy solution that made fontawesome library works on arabic local,
1/ put the fontawesome.css in the skin as last file in the included styles tab so it will not interfere with the custom css
2/ put in UserWorkForm html fragment rule this way it will be called in arabic local and icons will load normally fontawesom.css == the name of the css file you uploaded into pega
Also it will work even without adding it to skin rule (we add it to skin rule so the icons will be avalibale when u choose icon class as source in the image control) if u didn’t put in skin u can get the icon class from fontawesome website and put it directly on the image control in your section and then it will also render on the UI
Summary : To make fontawesome work on your pega Arabic local call the library again in UserWorkForm !
@MarijeSchillernThanks for your response; I really appreciate it. I have logged a ticket on MSP but am still waiting for Pega’s reply. In the meantime, I will go through your suggestions, try them out, and share my findings with you and the community.