NoteTab 6.12 now available
- Hi everyone,
We're pleased to announce the release of NoteTab 6.12 (all versions).
You'll find the update link in NoteTab's "Check for Updates" feature,
which is available from the Help menu. If you don't see the version 6.12
info in the News and Updates window, click on the "Get headlines" button
at the top-left of the screen to refresh the list.
Important: If you are updating from a previous version of NoteTab and
use the "Document to HTML" command, we recommend that you update the
"HTML Header" field on the Internet tab of the Options dialog box.
Change the charset value to utf-8 as shown in the following line:
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Improvements since version 6.1:
* Added optional code page token support in template headers. The code
page value is placed between parentheses and is preceded by the letters
CP. The code page value should be one of the numeric values listed here:
http://www.notetab.com/redir/codepage. This example creates a new UTF-8
= DocTemplate CP(65001)
* Added three templates that you can use to easily create new Unicode
* Included sample plain text and HTML files containing text based on a
variety of character sets (Arabic, Chinese, Cyrillic, Greek, Hebrew,
etc.) These files are stored in the Samples subfolder under the NoteTab
* Added "Open Sample File" in SampleCode library. Use this Clip to open
a plain text or HTML file containing text based on a non-Western
character set (Arabic, Chinese, Cyrillic, Greek, Hebrew, etc.) The
purpose of these files is to demonstrate how NoteTab 6 handles text
based on different Windows code pages.
* Fixed the "Text Case" commands, which sometimes converted extended
characters based on non-system code pages incorrectly. Note that the
"Invert Case", Capitalize, and Sentence commands do not correctly handle
double-byte characters (DBCS) and so should only be used on parts of
text with Latin-based characters.
* Fixed the "Document to HTML" and "Characters to HTML" commands, which
previously assumed source text was always based on the Western ANSI
character set. This sometimes resulted in invalid HTML entities when
processing text based on other code pages.
* Fixed "String list does not allow duplicates" error that could
sometimes occur when opening Unicode and UTF-8 documents.
* Updated Help.