The following is a list of Unicode limitations:
• Bold and italics color-coding is not supported. Support for this will be added in a future version.
• Tab character operations are not fully supported. Tab display, the
Expand tabs to spaces
save option
(
Window
→
Preferences
, expand
SlickEdit
and click
General
in the tree, then double-click the
File
Options
setting and select the
Save Tab
), and save with tabs (
save +t
) only work correctly if all the
characters are below 128. The
Expand tabs to spaces
load option (
Window
→
Preferences
, expand
SlickEdit
and click
General
in the tree, then double-click the
File Options
setting and select the
Load
Tab
) is ignored.
• Column selections do not fully support Unicode. If all the characters are below 128 and the font is fixed
then it works. Support for this will be added in a future version.
• Word Wrap does not fully support Unicode. If all the characters are below 128 and the font is fixed, then
it works. Support for this will be added in a future version.
• The Unicode line end character
0x2048
is not supported.
• Hex editing is not supported. The current character (Composite character) is displayed on the status
line. Also, use the Open dialog with the
Binary, SBCS/DBCS mode
encoding to view a Unicode file in
hexadecimal.
• Casing features (uppercase, lowercase, ignore case) do not support surrogates. Windows is relied
upon for casing support, and Windows casing features do not support surrogates. See
Surrogate Sup-
port
.
• Vertical line column (
Window
→
Preferences
, expand
SlickEdit
and click
General
in the tree, then
double-click the
General
setting and select the
General Tab
) is not supported.
• Truncation line length is not supported.
•
Record width
on the File Open dialog is not supported.
• DDE is not supported. Unicode DDE does not work with Internet Explorer or Netscape
®
. You can view
files with Unicode data in Internet Explorer; however, this feature will fail if the file name contains char-
acters not in the active code page.
• Version control supports files containing Unicode data but does not support file names that contain
characters not in the active code page.
• Special character display is not supported for Unicode buffers.
• The
grew
program does not support Unicode and can only be used on SBCS/DBCS active code page
text.
• If you load the same source file in Unicode and SBCS/DBCS mode, the Context Tagging
®
database will
have incorrect seek positions. It is important to use the default load options and to always load source
files in the same encoding so that the Context Tagging seek positions match the editor seek positions.
• The install (
setup.exe
), unionist (
uninstall.exe
), and update (
update.exe
) programs are not
Unicode applications so the installation directory must contain characters in the active code page.
Using Unicode
473
Summary of Contents for Corev3.3 for Eclipse
Page 1: ...Think Slick Corev3 3 for Eclipse...
Page 2: ......
Page 3: ...SlickEdit Core v3 3 for Eclipse...
Page 5: ......
Page 6: ......
Page 14: ...xii...
Page 20: ...xviii...
Page 22: ...xx...
Page 23: ...Chapter 1 Introduction 1...
Page 41: ...Chapter 3 User Interface 19...
Page 61: ...Chapter 4 User Preferences 39...
Page 80: ...BODY BODY HTML HTMLEOF Restoring Settings on Startup 58...
Page 82: ...60...
Page 83: ...Chapter 5 Context Tagging 61...
Page 97: ...Chapter 6 Editing Features 75...
Page 124: ...Code Templates 102...
Page 238: ...Figure 6 49 Test Parsing Configuration Example 1 C Refactoring 216...
Page 241: ...Figure 6 51 Test Parsing Configuration Example 3 Reviewing Refactoring Changes 219...
Page 250: ...228...
Page 251: ...Chapter 7 Language Specific Editing 229...
Page 328: ...306...
Page 329: ...Chapter 8 Tools and Utilities 307...
Page 350: ...328...
Page 351: ...Chapter 9 Macros and Macro Programming 329...
Page 360: ...338...
Page 361: ...Chapter 10 SlickEdit Core Dialogs 339...
Page 375: ...Find and Replace View 353...
Page 491: ...Chapter 11 Appendix 469...
Page 567: ......
Page 568: ......