A question to all who using an UTF-8 Teamcenter (11.4) environment. When we put multi-byte characters like Japanese or Chinese signs to e.g. the description attribute of an standard Item or Item Revision object, it shows the correct signs in summary stylesheet and localization window. But open the 'view Properties' window, Teamcenter visiualizes only blank boxes. Open the 'print opject properties' window, the visualization is correct in both HTML and TEXT.
Does anybody can confirm this bahavior? If yes, I'm going to raise a GTAC call.
Solved! Go to Solution.
Can I watch your IR on the GTAC knowing its number or not? Is it possible to watch other (not your own) IR and PR knowing their number?
I tried to enter it into the search (Call Number) I press Ctrl button and click on the selected Sold-to will deselect the Sold-to, but I do not find anything.
I added a new line to the customer.properties:
# Add multibyte character support in an English rich client
It works fine for me.
-------answer on IR 9241816---------------------------------------------------------
please see the below extract from the documentation PR-9229455:
Description of Problem:
The current documentation section "Choose a display language for the rich client" states following work around in case you have problems displaying multibyte characters correctly:
"If you find that Asian multibyte characters do not display correctly in the rich client, set your system font to a font that supports Asian multibyte characters. For example, on Microsoft Windows systems, the Arial Unicode MS font can be set to Message Box to correct this problem."
This work around is no longer valid because starting from Windows 10 Creators Update, Microsoft removed the OOTB possibility to change the font of the Message Box. It can now only be changed by modification to the registry or by running third party applications that perform the modifications.
The current supported work around is to use the setting UseDefaultSwingFonts=true
01 Add following lines to the portal_user.properties file:
02 Run %tc_root%\portal\registry\genreg
This is already documented in the "Add multibyte character support in an English rich client":
The documentation section "Choose a display language for the rich client" should be updated stating that the work around is no longer valid in latest Windows 10 clients and a reference can be added to the "Add multibyte character support in an English rich client"
GTAC EMEA - Product Support