Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Modifying the fonts settings file for font customization

Updated on March 3, 2022
You customize the fonts for the text that is displayed on native elements of your mobile app, for example, to conform to your company's branding or to improve readability. After you upload custom fonts, modify the fonts list for your mobile app.
Before you begin: Upload the font files. For more information, see Uploading custom font files.
  1. In the header of Dev Studio, in the search field, enter pyMobileFontsList, and then press Enter.
  2. In the search results, expand the list of matches by clicking the arrow next to the pyMobileFontsList link, and then open the text file rule by clicking the link for the UI-Kit 7 ruleset.
  3. On the pyMobileFontsList text file rule configuration screen, save a copy of the text file rule in the context of your application by clicking Save asSpecialize by class or ruleset, and then selecting your application in the Context area.
  4. For each of the font files that you upload, in the pyMobileFontsList rule, add a JSON array, according to the following template:
    {
        url: "myAppName/MyFontNameRegular.ttf", 
        fontFamily: "MyFontName", 
        type: "text"
    }
    The parameters define the following attributes:
    url
    Defines the URL address of the font file.
    fontFamily
    Defines the name of the font.
    type
    Defines the type of the font.
  5. Click Save.
What to do next: Modify your application skin. For more information, see Modifying the application skin for font customization.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us