Open your application in the AppSheet Editor.Ĭlick View adjacent to the template name to open the template in Google Docs.įrom the Google Docs Font menu select More Fonts. To add a custom font to a Google Docs template:
See Verifying all custom fonts are present. If the import url is missing one or more of your custom fonts, the data values in the PDF attachment file are displayed in the default font rather than in the custom font. The import url must refer to all of the custom fonts that you are using in your PDF attachment. The HTML-to-PDF web conversion service relies on the HTML file containing the right import url value. Reads the Google Doc file in HTML format.Ĭreates the attachment from the HTML template file.Ĭonverts the resulting attachment from HTML to PDF by calling the HTML-to-PDF web conversion service. When your event fires, AppSheet does the following: When you use custom fonts like "Libre Barcode 128" and "Libre Barcode 39 Extended Text", the HTML file that is returned when AppSheet reads the Google Docs template includes an import url that refers to these custom fonts. If you experience this problem, we recommend removing all custom fonts from your Google Docs template. The resulting PDF document may not display the text using the custom font. The PDF service sometimes fails to convert the HTML file to PDF correctly when custom fonts are present. Note: Some customers have reported problems when using custom fonts in templates. Removing all custom fonts from your Google Docs template Verifying all custom fonts are present in the HTML How custom fonts are displayed by AppSheetĭetecting custom fonts using the audit history log Use custom fonts in your Google Docs template file and troubleshoot related issues, as described in the following sections:
0 kommentar(er)
