Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
install:fonts [2023/03/10 09:49] – [Installation of required font] alz | install:fonts [2025/03/12 13:53] (current) – [Install required font] Linz, Andreas | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== How to install the correct fonts ====== | + | ====== How to install the correct fonts (until Stages 7.9.6.1) |
This section describes the configuration to create PDF files and process visualizations according to the charset required. | This section describes the configuration to create PDF files and process visualizations according to the charset required. | ||
- | + | ===== No asian charsets required ===== | |
- | ===== No asian charsets required | + | |
If no asian charsets are required - the additional installation of fonts is not required. | If no asian charsets are required - the additional installation of fonts is not required. | ||
- | |||
==== Define configuration properties ==== | ==== Define configuration properties ==== | ||
- | **Windows server OS:** \\ | + | **Windows server OS:** \\ Open file <Stages Installation Directory> |
- | Open file <Stages Installation Directory> | + | |
- | //< | + | //< |
- | < | + | |
- | **Linux server OS:** \\ | + | **Linux server OS:** \\ Open file / |
- | Open file / | + | |
- | Please add or modify the properties below according to your installation parameters: | + | |
- | + | ||
- | //< | + | |
- | < | + | |
+ | //< | ||
==== Check metamodel settings ==== | ==== Check metamodel settings ==== | ||
- | This is an example on how to check the correct font families to be defined in the unified configuration metamodel.\\ | + | This is an example on how to check the correct font families to be defined in the unified configuration metamodel.\\ |
- | If you use different metamodels - or older versions of the Unified Configuration Metamodel - the path of the files to check will be different. | + | |
- | Open all *.css files specified in the paths below and check for the following font family definition: | + | Open all *.css files specified in the paths below and check for the following font family definition: |
- | // | + | |
- | **Windows server OS:** \\ | + | **Windows server OS:** \\ <Stages Installation Directory> |
- | <Stages Installation Directory> | + | |
- | **Linux server OS:** \\ | + | |
- | / | + | |
- | Make sure the scriptconfig.js specified in the paths below is up to date and contains:\\ | + | Make sure the scriptconfig.js specified in the paths below is up to date and contains: |
- | //var FONTNAME = availableFontFamilies.getConfiguredFont(); | + | |
- | \\ | + | |
- | **Windows server OS:** \\ | + | |
- | <Stages Installation Directory> | + | |
- | **Linux server OS:** \\ | + | |
- | / | + | |
- | + | ||
- | Please note: This is a temporary fix only - every update of the Stages configuration would revoke your changes. So we strongly suggest to also fix this in your metamodel file (.mm). If you need further help to do so - please contact your Stages product consultant or the Stages support team at Method Park. | + | |
+ | Please note: This is a temporary fix only - every update of the Stages configuration would revoke your changes. So we strongly suggest to also fix this in your metamodel file (.mm). If you need further help to do so - please contact your Stages Product Consultant or the Stages Customer Care team. | ||
==== Restart Stages service ==== | ==== Restart Stages service ==== | ||
Line 53: | Line 33: | ||
To make changes take effect - a restart of the Stages service is required. | To make changes take effect - a restart of the Stages service is required. | ||
- | **Windows server OS:** Please open the services box with administrative permissions and restart the Stages service\\ | + | **Windows server OS:** Please open the services box with administrative permissions and restart the Stages service\\ |
- | **Linux server OS:** Restart the stages service with the following command: //sudo stages restart// | + | |
===== Asian charsets required ===== | ===== Asian charsets required ===== | ||
- | To use asian charsets - an additional font is required that supports the charset required. Method Park only provides one font that supports most asian charsets: | + | To use asian charsets - an additional font is required that supports the charset required. Method Park only provides one font that supports most asian charsets: |
Known Limitations: | Known Limitations: | ||
- | * SourceHanSans | + | * Source Han Sans doesn' |
- | * The alignment of text and/or the line spacing might be incorrect. | + | * The alignment of text and/or the line spacing |
We strongly suggest to install your own font - only supportig your required charset. If you do so - please adopt the font properties in the following sections according to your font requirements. | We strongly suggest to install your own font - only supportig your required charset. If you do so - please adopt the font properties in the following sections according to your font requirements. | ||
- | |||
==== Install required font ==== | ==== Install required font ==== | ||
- | Please download | + | Please download font Source Han Sans to the following folder on your Stages server: |
- | **< | + | |
- | \\ | + | |
- | Font download source: **Source Han Sans ** ([[https:// | + | |
- | [[https://www.methodpark.de/ | + | |
==== Define configuration properties ==== | ==== Define configuration properties ==== | ||
- | **Windows server OS:** \\ | + | **Windows server OS:** \\ Open file <Stages Installation Directory> |
- | Open file <Stages Installation Directory> | + | |
- | //< | + | //< |
- | < | + | |
- | **Linux server OS:** \\ | + | **Linux server OS:** \\ Open file / |
- | Open file / | + | |
- | Please add or modify the properties below according to your installation parameters: | + | |
- | + | ||
- | //< | + | |
- | < | + | |
+ | //< | ||
==== Check metamodel settings ==== | ==== Check metamodel settings ==== | ||
- | This is an example on how to check the correct font families to be defined in the Unified Configuration Metamodel.\\ | + | This is an example on how to check the correct font families to be defined in the Unified Configuration Metamodel.\\ |
- | If you use different metamodels - or older versions of the Unified Configuration Metamodel - the path of the files to check will be different. | + | |
- | + | ||
- | Open all *.css files specified in the paths below and check for the following font family definition: | + | |
- | // | + | |
- | **Windows server OS:** \\ | + | Open all *.css files specified in the paths below and check for the following font family definition:\\ //font-family: ' |
- | <Stages Installation Directory> | + | |
- | **Linux server OS:** \\ | + | |
- | /opt/stages/data-cache/generated/model/ | + | |
- | Make sure the scriptconfig.js specified in the paths below is up to date and contains: | + | **Windows server OS:** \\ <Stages Installation Directory> |
- | //var FONTNAME = availableFontFamilies.getConfiguredFont(); | + | |
- | \\ | + | |
- | **Windows server OS:** \\ | + | |
- | <Stages Installation Directory> | + | |
- | **Linux server OS:** \\ | + | |
- | / | + | |
- | Please note: This is a temporary fix only - every update of the Stages configuration would revoke your changes. So we strongly suggest | + | Make sure the scriptconfig.js specified in the paths below is up to date and contains: |
+ | Please note: This is a temporary fix only - every update of the Stages configuration would revoke your changes. So we strongly suggest to also fix this in your metamodel file (.mm). If you need further help to do so - please contact your Stages Product Consultant or the Stages Customer Care team. | ||
==== Restart Stages service ==== | ==== Restart Stages service ==== |