Database Search
TechHome
 | |
|
- !!A How to Treatise on Dynamic Dialogs
- Add a Status Bar on your Dialog
- Adding CRLF to a Tooltip Message
- Ampersand in Button
- Arrays in Dialogs
- AutoComplete in WinBatch Editboxes
- Autotimeout Example
- Ballon Tool Tips on Dialogs
- Balloon Tool Tips on Dialogs II
- Balloon Tool Tips on Dialogs III
- Bitmap Resizing in Dialog
- Button Dialog With No Default Focus
- Cancel Handler Issues within Dialogs
- Center dialog for any screen resolution
- Change Font in Dialog Controls
- Change Title of Dialog in Call Back Procedure
- Checking Char By Char Input in Dialogs
- Close Dialog Box upon completion of installation
- COMCONTROL Licenses Explained
- De-Activating Dialog Windows
- Dealing with Alt-F4 in Dialog
- Determine Control That Mouse is Hovering Over
- Dialog - Both Single and Multiple Selection Listboxes
- Dialog - Floating Toolbar
- Dialog - ProgressBar example
- Dialog Coordinates
- Dialog Editor 6 and UDS Callbacks
- Dialog Events For Unsupported Controls
- Dialog Significance of Config Parameter
- Dialog Units Explained
- Dialog with No Title bar
- Dialog with two list boxes and buttons to move items
- Dialogs - Adding ToolTips to Controls
- Dialogs - Menus in dialogs
- Disable Entry into DropListBox
- Disable Using ESC Key to Close Dialogs
- Display Dialog Along with RunWait
- Dynamic Dialogs - Creating Controls On The Fly
- Dynamic dialogs and BoxOpen Issue
- Dynamic Dialogs
- EditBox Cursor Placement
- Editbox with Filelistbox
- Error 3220 Dialog Format Version Not Supported
- Event Handling Questions
- File Browser within Dialog
- Get Value of RadioButton in Dialog Callback Procedure
- Hide or Unhide a PICTUREBUTTON
- High CPU Usage and Dialogs
- How to get an Editbox to Appear based on Selection
- How to Use the Spinner Control
- Inherited Check Mark
- IniWrite is Slow in Dialog Callback Procedure
- Japanese Dialog
- Leading 0 in a Spinner Control
- Make WIL Dialog Modal
- Maximized Dialog Hides Taskbar
- More UDFs to Make a Progress Bar Control
- MultiLineBox Limits
- Multiple Dialog Boxes
- Negative numbers in Dialog
- Non rectangular dialogs
- Non Responsive Dialog
- Position Dialog
- Pre-Selected Itembox
- Radio Button Disable Not Working
- Radiobuttons and Tabs
- Remove Border From ItemBox Control
- Right Justify Static or Variable Text
- Setting Spinner Control
- Simple Timer Procedure Example
- Smooth - Rounded Dialog Edges
- Splash Screen - Several Examples
- Start with Focus on Edit with No Selected Text
- Synchronize Two Itemboxes
- Tab Order and GroupBox Controls
- Toolbar UDFs for Drop Down Menus
- Treeview UDFs
- Unable to Load Background Image in Dialog
- Update Font Style in Dialog
- Using a Dialog as a Please Wait Screen
- WaitForKey Inside a Dialog Callback
- WebBrowser Control HTML Dialog
- WebBrowser Inside Dialogs by Guido
- Where are the Bitmaps for Pushbuttons
- Word Wrap
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Japanese Dialog
Question:
I want to create multilanguage dialogues and I have to provide japanese too. If I try to import the japanese translation into the winbatch compiler I´ve got only "???????" characters. I´ve already installed the windows japanese language support files.Answer:
The short answer is yes: it is possible to create multilingual dialogs because WB dialogs support UNICODE.In order to display Japanese text in a WinBatch dialog on a system with a different default language and font, you may need to do several things.
First, you will probably need to specify a UNICODE font in the dialog template for the controls that display Japanese characters. The specific font or at least a similar font must be available on all systems that will run your script. WinBatch uses the Windows font mapper so the exact font is not necessary but a similar font must be present. I use the 'Arial Unicode MS' font to display Japanese characters in dialogs on my English XP system.
Second, because WinBatch scripts and dialog templates are not UNICODE text, you need to place any UNICODE text in a control variable (the variable specified in the sixth attribute of the control's template definition) or create a dialog callback procedure and use the DialogControlSet function to specify the control's UNICODE text at runtime.
There are several ways to incorporate UNICODE text into your script: one is to embed a hex string version of the UNICODE text as the parameter to the ChrHextToUnicode function, another is to read UNICODE text in from a file.
Here is a simple example that works on my system.
Note: your system must have the 'Arial Unicode MS' font or equivalent installed. For more about this font see: http://support.microsoft.com/kb/287247
sJapanese = ChrHexToUnicode("AD30E330F330BB30EB30")
UnicodeTestFormat=`WWWDLGED,6.1`
UnicodeTestCaption=`Test Japanese Text`
UnicodeTestX=059
UnicodeTestY=103
UnicodeTestWidth=137
UnicodeTestHeight=094
UnicodeTestNumControls=003
UnicodeTestProcedure=`DEFAULT`
UnicodeTestFont=`DEFAULT`
UnicodeTestTextColor=`DEFAULT`
UnicodeTestBackground=`DEFAULT,DEFAULT`
UnicodeTestConfig=0
UnicodeTest001=`014,066,034,011,PUSHBUTTON,DEFAULT,"OK",1,1,32,DEFAULT,DEFAULT,DEFAULT`
UnicodeTest002=`079,066,035,011,PUSHBUTTON,DEFAULT,"Cancel",0,2,DEFAULT,"Arial Unicode MS|5632|40|34","0|0|0",DEFAULT`
UnicodeTest003=`017,009,094,020,VARYTEXT,sJapanese,DEFAULT,DEFAULT,3,DEFAULT,"Arial Unicode MS|5325|40|34","0|0|0",DEFAULT`
ButtonPushed=Dialog("UnicodeTest")
Article ID: W17390
File Created: 2008:04:10:15:09:12
Last Updated: 2008:04:10:15:09:12