When our Project Manager fills in description of a project, some of the German umlauts are transferred into other signs.
The System is changing the German word ‘Stück’ into other signs or the word ‘für’.
Is this a defect?
Non-ascii characters should be no problem if you have your language settings right.
Installed with US English and the user locale in CA PPM so that the äöü are included in the character set.
This is from 15.2.
Along with what Martti said we need to ensure the database setting are correct in order to have the language correct.
Manager's locale is already set to German and issue still there.
Any other possibilities that I can check?
You can check the database settings.
The documentation says under CA PPM installation
MS SQL ServerReview the Imported SQL Server Database OptionsImportant! Mixed collations settings are not supported. If you change the server-level default from SQL_Latin1_General_CP1_CI_AS to another collation, create a new SQL Server instance with the correct collation SQL_Latin1_General_CP1_CI_AS before creating the CA PPM database
For OracleComplete the following tasks in the order presented to configure Oracle for use with CA PPM.
For extended character handling on an Oracle server, set the NLS language to AL32UTF8. UNIX: Edit the UNIX user profile to add the NLS_LANG variable:
NLS_LANG=AMERICAN_AMERICA.AL32UTF8 EXPORT NLS_LANG
Windows: Start the registry editor: From the Start menu, select Run, and enter regedit. Go to HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\<Oracle Home> and change the value for key NLS_LANG to: AMERICAN_AMERICA.AL32UTF8
Set the required parameters in the following table for your new database: Name Value Character Set AL32UTF8 National Character Set UTF8/AL16UTF16 nls_date_format YYYY-MM-DD HH24:MI:SS nls_sort BINARY nls_comp BINARY query_rewrite_enabled true Cursor_sharing FORCE
Does the problem occur everywhere where you use äöü and for all users using them?
I will try the above solution. This problem is seen currently in CA PPM v14.3.
Our lower environments are in v15.4 and there is no problem in that.
We are anyway upgrading our Production and will wait if the issue gets resolved in 15.4
Retrieving data ...