Article - CS189962
After merging UTF-8 without BOM encoding files to the mainline, encoding become ANSI and Chinese characters turn to messy code in Integrity Lifecycle Manager
Modified: 24-Mar-2020
Applies To
- PTC RV&S (formerly Integrity Lifecycle Manager) 10.6 to 12.3
Description
- After merging UTF-8 without BOM encoding files to the mainline, encoding become ANSI and Chinese characters turn to messy code in Integrity
- Steps to reproduce:
- Set Notepad++ as default in File > Preferences > Configuration Management > Editor
- Create a project
- Create a sandbox for the project
- Add an ANSI as UTF-8 file (Encode in UTF-8 without BOM in Notepad++)
- Create a development path for the project
- Create a variant sandbox for the development path
- Check out and edit the file in sandbox of development path, then check in
- Merge Child Development Path
- Double click the file, it opened in Notepad++, encode in ANSI, and Chinese turn to messy code
This is a printer-friendly version of Article 189962 and may be out of date. For the latest version click CS189962