Analyzing your prompt, please hold on...
An error occurred while retrieving the results. Please refresh the page and try again.
Aspose.Cells for Python via .NET APIs provide the facility to render the spreadsheets in image formats as well as convert them to PDF & XPS formats. In order to maximize the conversion fidelity, it is necessary that the fonts used in the spreadsheet should be available in the operating system’s default font directory. In case the required fonts are not present then the Aspose.Cells for Python via .NET APIs will try to substitute the required fonts with the ones available.
Below is the process that Aspose.Cells for Python via .NET APIs follow behind the scene.
Aspose.Cells for Python via .NET APIs search the operating system’s default font directory for the required fonts. In case the required fonts are not available in the system’s font directory then the APIs search through the custom (user defined) directories. The FontConfigs class has exposed a number of ways to set custom font directories as detailed below.
Aspose.Cells for Python via .NET APIs also provide the ability to specify the substitute font for rendering purposes. This mechanism is helpful when a required font is not available on the machine where conversion has to take place. Users can provide a list of font names as an alternative to the originally required font. In order to achieve this, the Aspose.Cells for Python via .NET APIs have exposed the FontConfigs.set_font_substitutes method which accepts 2 parameters. The first parameter is of type string, which should be the name of the font that needs to be substituted. The second parameter is an array of type string. Users can provide a list of font names as a substitution to the original font name (specified in the first parameter).
Here is a simple usage scenario.
In addition to above-mentioned methods, the Aspose.Cells for Python via .NET APIs have also provided means to gather information on what sources and substitutions have been set.
Analyzing your prompt, please hold on...
An error occurred while retrieving the results. Please refresh the page and try again.