While Unicode characters are generally supported in OnBase Foundation 22.1, note that full character support depends on a number of factors, including the version of the database you are using, the database collations you are using (for Microsoft SQL Server databases only), the fonts you are using, and current Microsoft support. If a character you are using is not supported as a result of any of these factors, you might encounter rendering or data integrity issues.
Additionally, support for the following types of Unicode characters is not guaranteed:
-
Combining diacritical characters. A diacritical character is typically a symbol or mark that is rendered not by itself but rather with another character (e.g., an acute accent, as in é). A diacritical character can be encoded by a single Unicode character (e.g., é), and this encoding is supported in OnBase Foundation 22.1. However, this diacritical character can also be encoded as one of two or more distinct characters in a chain (e.g., e followed by ' ), and support for this type of encoding is not guaranteed.
-
Supplementary characters. A supplementary character is any character in the range of U+10000 to U+1FFFF. Such characters typically consist of historic scripts (e.g., Egyptian hieroglyphs, Linear B, etc.), historic and modern musical notations, emoticons, etc.
-
Characters outside of the Basic Multilingual Plane. Unicode characters that fall inside the Basic Multilingual Plane, which ranges from U+0000 to U+0FFF, are supported in OnBase Foundation 22.1(pending the factors mentioned at the beginning of this section). Support for Unicode characters that fall outside this range is not guaranteed.
When using Unicode currency characters, you must use a Unicode database to ensure that these currency symbols are properly read and displayed. If an unsupported Unicode character is read in an ANSI database, the actual character may be replaced with a question mark (" ? ").