Customer added new branch to the Routing Part Library tree list.
According to Documentation:
"Part library view (PLV) file lets you define a hierarchy of menus for finding
classes of parts. NX uses the hierarchy defined in this file to display
available parts in the Routing Part Library as a tree list."
Customer opened ugroute_elec_metric.plv file and added simple subnode branch
to
the "WIRING PARTS NODE" tag: SUBNODE = TEST, NAME = Plug sockets
---------------------
! Connectors (or other parts) accessed via Place Part
NODE WIRING_PARTS
NAME Electrical Parts
SUBNODES TEST WTERMINALS TERMINALS CONNECTORS BACKSHELL CLAMPS BOOTS
END_OF_NODE
NODE TEST
NAME Plug sockets
TABLE test_connector.ptb
END_OF_NODE
-----------------------
Checked: works fine, new branch "Plug sockets" appeares in the Routing Part
Library tree list.
Customer wants to use localized (Cyrillic) symbols for the name of node.
So they just translated "Plug sockets" as "Âèëêè" and replaced these words
in ugroute_elec_metric.plv file.
After restart NX, they see: Cyrillic symbols are displayed as strange
senseless symbols.
ugroute_elec_metric.plv file is saved in UTF8 encoding (we can see it in the
lower right corner in Notepad++).
NX (starting from NX10) supports UTF8, but not for all applications and
functionality.
Customizing APV files doesn't support it, so for this functionality NX expects
configuration files to use ANSI enconding (1 symbol -> 1 byte).
UTF8 encoding can have 1...4 bytes for 1 symbol.
Therefore UFT-8 is displayed as garbage.
Solution:
To fix this issue customer should open config file ugroute_elec_metric.plv and
save it as ANSI with appropriate codepage (i.e. Windows-1251 for cyrillic).