Journyx version 8.0 and higher fully supports native Unicode storage in the database. This means user-entered text from different languages can be freely mixed on the same site. However only one "collation" (linguistic sort ordering in things like search results) can be used on a site. See below for collation details.
Earlier version of Journyx such as version 7.9 have limited or no Unicode support.
Journyx 8.0 and higher automatically uses Unicode on Microsoft SQL Server, Oracle, and the internally provided PostgreSQL database option. However when setting up an external PostgreSQL database connection, you will need to create the database with the "UTF8" (Unicode) character set as described in the external PostgreSQL setup instructions.
In addition, you should be aware of the difference between the UTF8 and UTF16 encodings of Unicode. They are both "Unicode" and can store the exact same list of characters. However they are stored in different binary formats which mainly affects the amount of disk space and memory required. UTF8 is more efficient for databases which are primarily Western European languages. UTF16 is more efficient for Asian languages and some others. Using UTF16 to store English or other Western texts can double the size of the database compared to Journyx 7.
Microsoft SQL Server only stores Unicode in UTF16 format. PostgreSQL only stores Unicode in UTF8 format. Oracle offers a choice between the two, but the default is UTF16. You can only change it to UTF8 when initially creating the database and not after creation. Therefore if you are planning to use Oracle with Journyx 8 and your users primarily use Western European languages such as English, Spanish, French, Italian or German, then you should choose UTF8 for your Oracle "national character set" setting when initially creating the database. See the external Oracle instructions for details.
As mentioned above, only a single collation can be used on any given site. The collation determines the linguistic sort ordering of search results and similar things. The collation is determined during the external database setup. Please refer to the appropriate external database instructions for your platform for details. The collation for the internal database (the provided copy of PostgreSQL) is determined automatically based on your operating system language settings. Once it is set it cannot be changed without recreating the database environment.
In most cases a single collation combined with the Unicode universal character set will provide satisfactory results for most users.