---------------------------- The following is a Chinese solution for JBuilderx online search: solve the Chinese problem to put% system% / documents and Settings / /.primetimeX /.jbuilderX directory and delete the directory under the you_user open JBuilderX / bin / jbuilder.config file, # Tune this VM to provide enough headroom to work on large # applicationsvmparam behind -Xms32mvmparam -Xmx256m additional line vmparam -Dprimetime.editor.UsevariableWidthfont = TRUE will start JBuilder X to try, usually normal. At this time, you can see "Tools" - "EDIT" - "Font Family" option in "Display" is "DialogInput" in "Tools" - "Perferences".
--------------------------------------------
It should be: editor.display; fixed_fonts.3 = the font name is written, JBX will automatically delete, you can add quotation marks, save, then remove the quotation, set the font name to Dialoginput, the cute font came out The same is the same as JB9. -------------------------------------------
Look at the previous post, especially for the solution to the Bold option to solve the cursor misalignment problem. I feel that it is necessary to clarify the cause of the problem:
The cursor problem in JBuilder is not a problem with Borland, but should be the trouble left by Sun. Let me know that I18N issues are mainly distinguished by the operating system through Locale (Window2000 or XP on Window2000 or XP through "Region and Language Options" on the user's work area and using language. Documents to implement the software package to internationalize. Specifically, JBuilder implements support for Chinese fonts by using JRE's Font.Properties.en.
The problem is on the font.properties.en provided in Sun. Sun is used in the normal body, bold and slope of various fonts in this document. We know that in the editor, the width of the normal body and bold or obliquely occupied is different. Therefore, Bold and normal body (plain) uses normal experience that causes the editor to calculate errors on bold character width, which we understand the cause of the problem. Interestingly, Sun has the correct difference between the font attribute documents of English. (It seems to be deliberate ?!) Compare font.properties and font.properties.zh files, you can understand the problem. ========== # Component font mappings # Dialog.Plain.0 = arial, ANSI_CharsetDialog.Bold.0 = arial bold, ANSI_CharsetDialog.italic.0 = arial italic, ANSI_Charset
As above, PLAIN should use font xxx, Bold should use XXX Bold, italic should use XXX Italic.
It is very easy to understand the roots of the problem. It is very easy to find a solution to the problem.
Replace the corresponding component font mappings in Font.Properties.en to the bottom. # Component Font Mappings # dialog.plain.0 = Arial, ANSI_CHARSETdialog.plain.1 = / u5b8b / u4f53, GB2312_CHARSETdialog.plain.2 = WingDings, SYMBOL_CHARSET, NEED_CONVERTEDdialog.plain.3 = Symbol, SYMBOL_CHARSET, NEED_CONVERTED
dialog.bold.0 = Arial Bold, ANSI_CHARSETdialog.bold.1 = / u5b8b / u4f53, GB2312_CHARSETdialog.bold.2 = WingDings, SYMBOL_CHARSET, NEED_CONVERTEDdialog.bold.3 = Symbol, SYMBOL_CHARSET, NEED_CONVERTED
dialog.italic.0 = Arial Italic, ANSI_CHARSETdialog.italic.1 = / u5b8b / u4f53, GB2312_CHARSETdialog.italic.2 = WingDings, SYMBOL_CHARSET, NEED_CONVERTEDdialog.italic.3 = Symbol, SYMBOL_CHARSET, NEED_CONVERTED
dialog.bolditalic.0 = Arial Bold Italic, ANSI_CHARSETdialog.bolditalic.1 = / u5b8b / u4f53, GB2312_CHARSETdialog.bolditalic.2 = WingDings, SYMBOL_CHARSET, NEED_CONVERTEDdialog.bolditalic.3 = Symbol, SYMBOL_CHARSET, NEED_CONVERTED
dialoginput.plain.0 = Courier New, ANSI_CHARSETdialoginput.plain.1 = / u5b8b / u4f53, GB2312_CHARSETdialoginput.plain.2 = WingDings, SYMBOL_CHARSET, NEED_CONVERTEDdialoginput.plain.3 = Symbol, SYMBOL_CHARSET, NEED_CONVERTED
dialoginput.bold.0 = Courier New Bold, ANSI_CHARSETdialoginput.bold.1 = / u5b8b / u4f53, GB2312_CHARSETdialoginput.bold.2 = WingDings, SYMBOL_CHARSET, NEED_CONVERTEDdialoginput.bold.3 = Symbol, SYMBOL_CHARSET, NEED_CONVERTED
dialoginput.italic.0 = Courier New Italic, ANSI_CHARSETdialoginput.italic.1 = / u5b8b / u4f53, GB2312_CHARSETdialoginput.italic.2 = WingDings, SYMBOL_CHARSET, NEED_CONVERTEDdialoginput.italic.3 = Symbol, SYMBOL_CHARSET, NEED_CONVERTED
dialoginput.bolditalic.0 = Courier New Bold Italic, ANSI_CHARSETdialoginput.bolditalic.1 = / u5b8b / u4f53, GB2312_CHARSETdialoginput.bolditalic.2 = WingDings, SYMBOL_CHARSET, NEED_CONVERTEDdialoginput.bolditalic.3 = Symbol, SYMBOL_CHARSET, NEED_CONVERTEDserif.plain.0 = Times New Roman, ANSI_CHARSETSERIF.PLAIN.1 = / u5b8b / u4f53, gb2312_charsetserif.plain.2 = wingdings, symbol_charset, need_convertedserif.plain.3 = Symbol, Symbol_Charset, NEED_CONVERTED
serif.bold.0 = Times New Roman Bold, ANSI_CHARSETserif.bold.1 = / u5b8b / u4f53, GB2312_CHARSETserif.bold.2 = WingDings, SYMBOL_CHARSET, NEED_CONVERTEDserif.bold.3 = Symbol, SYMBOL_CHARSET, NEED_CONVERTED
serif.italic.0 = Times New Roman Italic, ANSI_CHARSETserif.italic.1 = / u5b8b / u4f53, GB2312_CHARSETserif.italic.2 = WingDings, SYMBOL_CHARSET, NEED_CONVERTEDserif.italic.3 = Symbol, SYMBOL_CHARSET, NEED_CONVERTED
serif.bolditalic.0 = Times New Roman Bold Italic, ANSI_CHARSETserif.bolditalic.1 = / u5b8b / u4f53, GB2312_CHARSETserif.bolditalic.2 = WingDings, SYMBOL_CHARSET, NEED_CONVERTEDserif.bolditalic.3 = Symbol, SYMBOL_CHARSET, NEED_CONVERTED
sansserif.plain.0 = Arial, ANSI_CHARSETsansserif.plain.1 = / u5b8b / u4f53, GB2312_CHARSETsansserif.plain.2 = WingDings, SYMBOL_CHARSET, NEED_CONVERTEDsansserif.plain.3 = Symbol, SYMBOL_CHARSET, NEED_CONVERTED
sansserif.bold.0 = Arial Bold, ANSI_CHARSETsansserif.bold.1 = / u5b8b / u4f53, GB2312_CHARSETsansserif.bold.2 = WingDings, SYMBOL_CHARSET, NEED_CONVERTEDsansserif.bold.3 = Symbol, SYMBOL_CHARSET, NEED_CONVERTED
sansserif.italic.0 = Arial Italic, ANSI_CHARSETsansserif.italic.1 = / u5b8b / u4f53, GB2312_CHARSETsansserif.italic.2 = WingDings, SYMBOL_CHARSET, NEED_CONVERTEDsansserif.italic.3 = Symbol, SYMBOL_CHARSET, NEED_CONVERTEDsansserif.bolditalic.0 = Arial Bold Italic, ANSI_CHARSETsansserif.bolditalic.1 = / u5b8b / u4f53, GB2312_CHARSETsansserif.bolditalic.2 = WingDings, SYMBOL_CHARSET, NEED_CONVERTEDsansserif.bolditalic.3 = Symbol, SYMBOL_CHARSET, NEED_CONVERTED
monospaced.plain.0 = Courier New, GB2312_CHARSETmonospaced.plain.1 = / u5b8b / u4f53, GB2312_CHARSETmonospaced.plain.2 = WingDings, SYMBOL_CHARSET, NEED_CONVERTEDmonospaced.plain.3 = Symbol, SYMBOL_CHARSET, NEED_CONVERTED
monospaced.bold.0 = Courier New Bold, GB2312_CHARSETmonospaced.bold.1 = / u5b8b / u4f53, GB2312_CHARSETmonospaced.bold.2 = WingDings, SYMBOL_CHARSET, NEED_CONVERTEDmonospaced.bold.3 = Symbol, SYMBOL_CHARSET, NEED_CONVERTED
monospaced.italic.0 = Courier New Italic, GB2312_CHARSETmonospaced.italic.1 = / u5b8b / u4f53, GB2312_CHARSETmonospaced.italic.2 = WingDings, SYMBOL_CHARSET, NEED_CONVERTEDmonospaced.italic.3 = Symbol, SYMBOL_CHARSET, NEED_CONVERTED
monospaced.bolditalic.0 = Courier New Bold Italic, GB2312_CHARSETmonospaced.bolditalic.1 = / u5b8b / u4f53, GB2312_CHARSETmonospaced.bolditalic.2 = WingDings, SYMBOL_CHARSET, NEED_CONVERTEDmonospaced.bolditalic.3 = Symbol, SYMBOL_CHARSET, NEED_CONVERTED
==== End ===== Restart JBuilder, you can! Finally, I hope that you will also make the same modifications in the JDK in JDK and JBuilders in JBuilder. Font.properties.en files in the {jdk_home} / jre / lib directory.
-------------------------------------------------- ------------------------------15.re: The true root knot of the cursor problem [Re: swordsman] Copy to Clipboard Posted by: Guruposted on: 2004-02-12 18: 18Swordsman Wrote: Looks out the previous post, especially for the way to remove the BOLD option to solve the cursor misalignment problem unacceptable. I feel that it is necessary to clarify the cause of the problem:
The cursor problem in JBuilder is not a problem with Borland, but should be the trouble left by Sun. Let me know that I18N issues are mainly distinguished by the operating system through Locale (Window2000 or XP on Window2000 or XP through "Region and Language Options" on the user's work area and using language. Documents to implement the software package to internationalize. Specifically, JBuilder implements support for Chinese fonts by using JRE's Font.Properties.en.
Yes, this is the correct answer. This setting can not only solve Chinese and cursor issues in JBuilder, but also resolve Chinese character width problems in any other graphical interface program, such as Intellij Idea, etc.
In addition, in JDK1.5, Sun has corrected this issue, and believes that there will be no more annoying character width problems.
Finally, it is added, in the system installed in the GB18030 (in the Windows XP copy of Microsoft, it seems to be this), may need to modify this file in the Font.Properties.zh_cn_gb18030, and other languages are pushed.
-------------------------------------------------- -1.jbuilderx Chinese display and cursor problem solution Copy to clipboard posted by: haWkerposted on: 2003-11-28 13:32
Sender: JIANDY (East East), Letter: Java Title: How to Let JBuilderx Display Chinese Send Station: BBS Shuimu Tsinghua Station (WED NOV 26 13:42:26 2003), transfer
Found% system_driver% / Documents and Settings / Administrator / .primetimeX directory of user_zh.properties files found ... editor.display; fixed_fonts.1 = Courier Neweditor.display; fixed_fonts.2 = Lucida Sans Typewriter ... about the 240 row, manually add editor.display; fixed_fonts.3 = "Font Name" Note: The font name must be the following editor.display; the font name listed in Known_Fonts
Push it according to a subkey, you can add a number of fonts, add "Dialoginput", "Monospaced" fonts to display Chinese
/
Sender: NSD (BUG), the letter area: Java Title: Re: Solving JBuilder's Cream Problem (Reposted) Send Station: BBS Shuimu Tsinghua Station (Sun Nov 16 16:47:31 2003)
Modify bin / jbuilder.config in the JBuilderx installation directory
# Specify location of Visual SourceSafe and Databasevmparam -DVSSLocation = "E: / Program Files / Microsoft Visual Studio / VSS / win32" vmparam -DVSSCurrentDBase = "// Rogers / WorkSheelt" added below this line: vmparam -Dprimetime.editor.useVariableWidthFont = become a true # Specify location of Visual SourceSafe and Databasevmparam -DVSSLocation = "E: / Program Files / Microsoft Visual Studio / VSS / win32" vmparam -DVSSCurrentDBase = "// Rogers / WorkSheelt" vmparam -Dprimetime.editor.useVariableWidthFont = true
I.e.
