How to Fix Korean Characters Displaying as Question Marks in Word Controls
Question details
The user needs to resolve an issue where Korean characters input as display values for Word controls turn into question marks in the Visual Basic Editor.
- Product
- Microsoft Word
- Device & OS
- not provided
- Scenario
- Setting the Display Value of drop-down controls or command buttons to Korean text for a localized document.
- Observed behavior
- The Korean characters display as question marks (?) inside the Visual Basic Editor, and changing the editor's font does not solve the problem.
Verify that your Windows system language settings support Korean, and ensure you are using a recent, supported version of Microsoft Word that properly handles Unicode.
Use Modern Unicode-Compatible Content Controls
Replace legacy ActiveX controls with modern Content Controls, which natively support Unicode languages like Korean without relying on the Visual Basic Editor.
The Visual Basic Editor (VBE) is a legacy environment that is not fully Unicode-aware. Because of this limitation, Korean characters used in legacy ActiveX controls may render as question marks. The best solution is to use modern Content Controls.
Go to File > Options > Customize Ribbon, and check the box for 'Developer' in the right pane, then click OK.
Navigate to the Developer tab on the ribbon. In the Controls group, click on 'Drop-Down List Content Control' or 'Rich Text Content Control' instead of using Legacy Tools.
With the new control selected, click 'Properties' in the Controls group. You can now securely type Korean characters into the Title, Tag, or Drop-Down list choices without them turning into question marks.
Change the Windows System Locale to Korean
If you must use the Visual Basic Editor and ActiveX controls, changing the system locale for non-Unicode programs can force the system to display Korean characters properly.
Try WPS Office for Seamless Multilingual Document Handling
If legacy limitations in Microsoft Word's Visual Basic Editor are restricting your ability to handle global languages seamlessly, consider switching to WPS Office. It provides a lightweight, highly compatible alternative with excellent native support for multilingual documents and Unicode characters.
Frequently Asked Questions
Why does changing the font in the Visual Basic Editor not fix the question marks?
The Visual Basic Editor (VBE) is not fully Unicode-aware. Simply changing the display font does not alter the underlying way the VBE processes multi-byte character sets like Korean, resulting in question marks regardless of the font chosen.
What is the difference between ActiveX controls and Content Controls?
ActiveX controls are older technologies that rely on VBA and the Visual Basic Editor, which struggle with Unicode. Modern Content Controls are built natively into the document's XML structure and fully support Unicode languages like Korean.
Can I type Korean characters directly into my VBA code?
Typing Korean directly into VBA strings can cause compilation or display errors due to the lack of Unicode support. A common workaround is to store the Korean strings directly within document cells or use the ChrW function in VBA to generate specific Unicode characters dynamically.
