Merge branch 'release/4.2.0-rc.3'

This commit is contained in:
1024jp 2022-05-07 12:25:11 +09:00
commit 14896eb98e
234 changed files with 1314 additions and 1013 deletions

View File

@ -2,12 +2,28 @@
Change Log
==========================
4.2.0-rc.3 (498)
--------------------------
### Improvements
- [rc] Update the help contents.
- [rc] Update localized strings.
### Fixes
- Fix an issue that the changes of syntax styles after the launch were not applied to the file mapping.
- [rc] Fix an issue that some UI states were not restored from the last session.
4.2.0-rc.2 (496)
--------------------------
### Fixes
- [rc] Fix an issue the migration panel could not read in the Dark Mode.
- [rc] Fix an issue the migration panel could not be read in the Dark Mode.

View File

@ -2801,7 +2801,6 @@
2A443220219AC235008A0A6B /* PreferencesWindow.storyboard in Resources */,
2A642CD12390C11D00BCA4C4 /* ProgressView.storyboard in Resources */,
2A86C47F2037312900B9357C /* SaveDocumentAccessory.storyboard in Resources */,
2A4144B8201397150061F653 /* WarningsView.storyboard in Resources */,
2AB2242921A7D51800F6201F /* SyntaxCompletionsEditView.storyboard in Resources */,
2AB2245421A809A000F6201F /* SyntaxEditView.storyboard in Resources */,
2AB2241D21A7CFC900F6201F /* SyntaxFileMappingEditView.storyboard in Resources */,
@ -2810,8 +2809,9 @@
2AB2243521A7D78400F6201F /* SyntaxOutlineEditView.storyboard in Resources */,
2AB2244A21A7DB9B00F6201F /* SyntaxTermsEditView.storyboard in Resources */,
2AD940F021A7CBF50076A28C /* SyntaxValidationView.storyboard in Resources */,
2AD940DC21A46B100076A28C /* UnicodeInputView.storyboard in Resources */,
2AB2243E21A7D8DF00F6201F /* SyntaxCommentsEditView.storyboard in Resources */,
2AD940DC21A46B100076A28C /* UnicodeInputView.storyboard in Resources */,
2A4144B8201397150061F653 /* WarningsView.storyboard in Resources */,
2A97849F2034561B00482647 /* WebDocumentWindow.storyboard in Resources */,
2A10D1001E7088B00027192A /* WindowPane.storyboard in Resources */,
);
@ -4378,10 +4378,10 @@
buildSettings = {
ASSETCATALOG_COMPILER_APPICON_NAME = AppIcon;
ASSETCATALOG_COMPILER_GLOBAL_ACCENT_COLOR_NAME = "Accent Color";
CURRENT_PROJECT_VERSION = 496;
CURRENT_PROJECT_VERSION = 498;
ENABLE_HARDENED_RUNTIME = YES;
INFOPLIST_FILE = CotEditor/Info.plist;
MARKETING_VERSION = "4.2.0-rc.2";
MARKETING_VERSION = "4.2.0-rc.3";
PRODUCT_BUNDLE_IDENTIFIER = "com.coteditor.$(PRODUCT_NAME)";
PRODUCT_NAME = CotEditor;
};
@ -4393,10 +4393,10 @@
buildSettings = {
ASSETCATALOG_COMPILER_APPICON_NAME = AppIcon;
ASSETCATALOG_COMPILER_GLOBAL_ACCENT_COLOR_NAME = "Accent Color";
CURRENT_PROJECT_VERSION = 496;
CURRENT_PROJECT_VERSION = 498;
ENABLE_HARDENED_RUNTIME = YES;
INFOPLIST_FILE = CotEditor/Info.plist;
MARKETING_VERSION = "4.2.0-rc.2";
MARKETING_VERSION = "4.2.0-rc.3";
PRODUCT_BUNDLE_IDENTIFIER = "com.coteditor.$(PRODUCT_NAME)";
PRODUCT_NAME = CotEditor;
};
@ -4432,10 +4432,10 @@
buildSettings = {
ASSETCATALOG_COMPILER_APPICON_NAME = AppIcon;
ASSETCATALOG_COMPILER_GLOBAL_ACCENT_COLOR_NAME = "Accent Color";
CURRENT_PROJECT_VERSION = 496;
CURRENT_PROJECT_VERSION = 498;
ENABLE_HARDENED_RUNTIME = YES;
INFOPLIST_FILE = CotEditor/Info.plist;
MARKETING_VERSION = "4.2.0-rc.2";
MARKETING_VERSION = "4.2.0-rc.3";
OTHER_SWIFT_FLAGS = "$(inherited) -D SPARKLE";
PRODUCT_BUNDLE_IDENTIFIER = com.coteditor.CotEditor;
PRODUCT_NAME = CotEditor;
@ -4448,10 +4448,10 @@
buildSettings = {
ASSETCATALOG_COMPILER_APPICON_NAME = AppIcon;
ASSETCATALOG_COMPILER_GLOBAL_ACCENT_COLOR_NAME = "Accent Color";
CURRENT_PROJECT_VERSION = 496;
CURRENT_PROJECT_VERSION = 498;
ENABLE_HARDENED_RUNTIME = YES;
INFOPLIST_FILE = CotEditor/Info.plist;
MARKETING_VERSION = "4.2.0-rc.2";
MARKETING_VERSION = "4.2.0-rc.3";
OTHER_SWIFT_FLAGS = "$(inherited) -D SPARKLE";
PRODUCT_BUNDLE_IDENTIFIER = com.coteditor.CotEditor;
PRODUCT_NAME = CotEditor;

View File

@ -1018,7 +1018,7 @@
<binding destination="fug-yh-kPG" name="value" keyPath="selection.selection.usesSystemSetting" id="dXs-Zl-kBI"/>
</connections>
</button>
<button toolTip="Show theme file info" translatesAutoresizingMaskIntoConstraints="NO" id="8zj-4c-Hg4">
<button toolTip="Show theme file information" translatesAutoresizingMaskIntoConstraints="NO" id="8zj-4c-Hg4">
<rect key="frame" x="315" y="3" width="15" height="22"/>
<constraints>
<constraint firstAttribute="height" constant="16" id="HuK-AR-s3B"/>

View File

@ -80,7 +80,7 @@
</button>
<textField verticalHuggingPriority="750" allowsCharacterPickerTouchBarItem="YES" translatesAutoresizingMaskIntoConstraints="NO" id="C4l-rJ-eqF">
<rect key="frame" x="18" y="354" width="316" height="16"/>
<textFieldCell key="cell" scrollable="YES" lineBreakMode="clipping" sendsActionOnEndEditing="YES" title="When document is modified by another application:" usesSingleLineMode="YES" id="x4n-2n-I3p">
<textFieldCell key="cell" scrollable="YES" lineBreakMode="clipping" sendsActionOnEndEditing="YES" title="When document is changed by another application:" usesSingleLineMode="YES" id="x4n-2n-I3p">
<font key="font" metaFont="system"/>
<color key="textColor" name="labelColor" catalog="System" colorSpace="catalog"/>
<color key="backgroundColor" name="textBackgroundColor" catalog="System" colorSpace="catalog"/>

View File

@ -15,9 +15,9 @@
<autoresizingMask key="autoresizingMask"/>
<subviews>
<button verticalHuggingPriority="750" translatesAutoresizingMaskIntoConstraints="NO" id="1lj-uv-tp6">
<rect key="frame" x="310" y="13" width="76" height="27"/>
<rect key="frame" x="328" y="13" width="58" height="27"/>
<constraints>
<constraint firstAttribute="width" relation="greaterThanOrEqual" constant="64" id="6wx-JO-VXi"/>
<constraint firstAttribute="width" relation="greaterThanOrEqual" constant="44" id="6wx-JO-VXi"/>
</constraints>
<buttonCell key="cell" type="push" title="Close" bezelStyle="rounded" alignment="center" controlSize="small" borderStyle="border" inset="2" id="1021">
<behavior key="behavior" pushIn="YES" lightByBackground="YES" lightByGray="YES"/>
@ -53,6 +53,9 @@ DQ
<behavior key="behavior" pushIn="YES" lightByBackground="YES" lightByGray="YES"/>
<font key="font" metaFont="smallSystem"/>
</buttonCell>
<connections>
<action selector="openHelpAnchor:" target="foX-H3-gAp" id="b7D-T5-bd8"/>
</connections>
</button>
<stackView distribution="fillEqually" orientation="vertical" alignment="leading" spacing="19" horizontalStackHuggingPriority="249.99998474121094" verticalStackHuggingPriority="249.99998474121094" horizontalClippingResistancePriority="750" verticalClippingResistancePriority="750" detachesHiddenViews="YES" translatesAutoresizingMaskIntoConstraints="NO" id="QlX-zU-Kbs">
<rect key="frame" x="20" y="44" width="360" height="362"/>
@ -132,7 +135,7 @@ DQ
<tableColumnResizingMask key="resizingMask" resizeWithTable="YES" userResizable="YES"/>
<prototypeCellViews>
<tableCellView id="w8q-3P-Q1e">
<rect key="frame" x="90.5" y="1" width="97" height="16"/>
<rect key="frame" x="91" y="1" width="97" height="16"/>
<autoresizingMask key="autoresizingMask" widthSizable="YES" heightSizable="YES"/>
<subviews>
<textField verticalHuggingPriority="750" horizontalCompressionResistancePriority="250" id="bkQ-4g-uet">
@ -300,7 +303,7 @@ DQ
<tableColumnResizingMask key="resizingMask" resizeWithTable="YES" userResizable="YES"/>
<prototypeCellViews>
<tableCellView id="FdF-7h-gtp">
<rect key="frame" x="90.5" y="1" width="97" height="16"/>
<rect key="frame" x="91" y="1" width="97" height="16"/>
<autoresizingMask key="autoresizingMask" widthSizable="YES" heightSizable="YES"/>
<subviews>
<textField verticalHuggingPriority="750" horizontalCompressionResistancePriority="250" id="Qt3-S7-Bpi">
@ -468,7 +471,7 @@ DQ
<tableColumnResizingMask key="resizingMask" resizeWithTable="YES" userResizable="YES"/>
<prototypeCellViews>
<tableCellView id="SjR-UH-naJ">
<rect key="frame" x="92.5" y="1" width="97" height="16"/>
<rect key="frame" x="93" y="1" width="97" height="16"/>
<autoresizingMask key="autoresizingMask" widthSizable="YES" heightSizable="YES"/>
<subviews>
<textField verticalHuggingPriority="750" horizontalCompressionResistancePriority="250" id="85I-66-i9l">

View File

@ -4,7 +4,7 @@
<svg version="1.1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 16 24.5">
<style>
<style type="text/css">
@media (prefers-color-scheme: dark) {
path { fill: white }
}

Before

Width:  |  Height:  |  Size: 757 B

After

Width:  |  Height:  |  Size: 773 B

View File

@ -4,7 +4,7 @@
<svg version="1.1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 15 13" width="15" height="13">
<style>
<style type="text/css">
* { fill: transparent; stroke: -apple-system-blue; }
</style>

Before

Width:  |  Height:  |  Size: 559 B

After

Width:  |  Height:  |  Size: 575 B

View File

@ -17,7 +17,7 @@
</header>
<main>
<p>CotEditor is a text editor designed for editing plain text files from programming to daily note taking. CotEditor offers a lot of useful features that are not available in the macOSs TextEdit.</p>
<p>CotEditor is a text editor designed for editing plain text files from programming to daily note-taking. CotEditor offers a lot of useful features that are not available in the macOSs TextEdit.</p>
<section>
<img class="snapshot" src="gfx/ov_find@2x.png" width="400"/>
@ -60,7 +60,7 @@
</section>
<p>To explore the CotEditor User Guide, click Table of Contents at the top of the page, or enter a word or phrase in the search field.</p>
<p>This guide helps you get started using CotEditor on your Mac. To explore the CotEditor User Guide, click Table of Contents at the top of the page, or enter a word or phrase in the search field.</p>
</main>
</body>

Binary file not shown.

After

Width:  |  Height:  |  Size: 141 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 41 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 516 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 76 KiB

Binary file not shown.

Before

Width:  |  Height:  |  Size: 28 KiB

After

Width:  |  Height:  |  Size: 51 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 34 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 94 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 48 KiB

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="text encoding, encoding, detction"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Use encoding declarations for encoding detection</title>
<title>Use encoding declarations for encoding detection in CotEditor</title>
</head>
<body>
<h1>Use encoding declarations for encoding detection</h1>
<h1>Use encoding declarations for encoding detection in CotEditor</h1>
<p>When the “Refer to encoding declaration in document” option is turned on in the Format preferences pane, CotEditor reads the following types of encoding declarations (if present) — <code>charset=</code>, <code>encoding=</code>, <code>@charset</code>, <code>encoding:</code> and <code>coding:</code> — when opening a file. If written properly, these declarations will be used to determine the files text encoding.</p>
<p>A declaration can be anywhere in the document, the one either in the comment area or in a plain sentence is detected. When you want to use a phrase such as “charset=UTF-8” even though your documents encoding is not UTF-8, you need to put an actual encoding declaration prior to the phrase, or, turn off the “Refer to encoding declaration in document” option in the Format preferences.</p>
@ -20,7 +20,7 @@
<li>The encoding name which comes after “<code>charset=</code>” or “<code>encoding=</code>” can be without double-quotes (&quot;) around.</li>
<li>In the case there are multiple encoding declarations in your document, CotEditor uses the first one to determine the text encoding.</li>
<li>When the encoding is declared as Shift JIS (written like <code>charset=&quot;Shift_JIS&quot;</code>), CotEditor chooses the prioritized one (the upper one in the encoding list) between “Japanese (Shift JIS)” and “Japanese (Shift JIS X0213).”<br />
<a href="howto_customize_encoding_order.html">Set the priority of encoding detection</a></li>
<a href="howto_customize_encoding_order.html">Change priorities of text encodings</a></li>
</ul>
@ -28,7 +28,7 @@
<h2>See also</h2>
<ul>
<li><a href="pref_format.html">Change Format preferences</a></li>
<li><a href="howto_customize_encoding_order.html">Set the priority of encoding detection</a></li>
<li><a href="howto_customize_encoding_order.html">Change priorities of text encodings</a></li>
</ul>
</section>

View File

@ -10,7 +10,6 @@
<body>
<a name="about_cot"></a>
<h1>Work with <code>cot</code> command</h1>
<p>CotEditor has '<strong>cot</strong>' command-line tool which allows you to control CotEditor from the command-line. To use <code>cot</code> command, install it at first.</p>

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="File Drop, pre-formatted strings"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Write insertion format for File Drop</title>
<title>Write insertion format for File Drop in CotEditor</title>
</head>
<body>
<h1>Write insertion format for File Drop</h1>
<h1>Write insertion format for File Drop in CotEditor</h1>
<p>CotEditor has the following variables for the use of File Drop.</p>

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="line ending, newline, line break, LF, CR, CRLF, NEL, LS, PS"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Handle various types of line endings</title>
<title>Handle various types of line endings in CotEditor</title>
</head>
<body>
<h1>Handle various types of line endings</h1>
<h1>Handle various types of line endings in CotEditor</h1>
<p>CotEditor can handle various types of line endings. In general, CotEditor uses a single type of line ending set for the document consistently.</p>

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="regular expression, regex, RE"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Use the regular expression</title>
<title>Use the regular expression in CotEditor</title>
</head>
<body>
<h1>Use the regular expression</h1>
<h1>Use the regular expression in CotEditor</h1>
<p>CotEditor uses the ICU regular expression engine. See the following reference to make sure it works properly.</p>
@ -24,7 +24,7 @@
<ul>
<li><a href="syntax_highlight_settings.html">Define syntax highlighting</a></li>
<li><a href="syntax_outline_settings.html">Define Outline extraction rules</a></li>
<li><a href="howto_find_newline.html">Find or replace a line ending</a></li>
<li><a href="howto_find.html">Find or replace text</a></li>
</ul>
</section>

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="text encoding, Shift JIS, japanese"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Use four kinds of Shift JIS properly</title>
<title>Use four kinds of Shift JIS properly in CotEditor</title>
</head>
<body>
<h1>Use four kinds of Shift JIS properly</h1>
<h1>Use four kinds of Shift JIS properly in CotEditor</h1>
<p>The four kinds of Shift JIS are different from each other as described below:</p>
@ -47,7 +47,7 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="howto_inspect_usedchar.html">Check whether incompatible characters are included</a></li>
<li><a href="howto_inspect_usedchar.html">Find characters incompatible with document encoding</a></li>
</ul>
</section>

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="source code, license"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>CotEditors Source Code</title>
<title>CotEditors source code in CotEditor</title>
</head>
<body>
<h1>CotEditors Source Code</h1>
<h1>CotEditors source code in CotEditor</h1>
<p>CotEditor is open-source software. The source code is available for download at the <a href="https://github.com/coteditor/" rel="external">CotEditor Project</a> page on GitHub.</p>

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="text encoding, yen, backslash"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>If the Yen sign appears as a backslash</title>
<title>If the Yen sign appears as a backslash in CotEditor</title>
</head>
<body>
<h1>If the Yen sign appears as a backslash</h1>
<h1>If the Yen sign appears as a backslash in CotEditor</h1>
<p>With one of the text encodings listed below, a halfwidth Yen character (&#x00A5;) is displayed as is when you type, but if you change the encoding, or, if you save and reopen the file, it will be displayed as a backslash (&#x005C;).</p>

View File

@ -4,16 +4,16 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="garbled character, encoding"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>If characters arent displayed correctly</title>
<title>If characters arent displayed correctly in CotEditor</title>
</head>
<body>
<h1>If characters arent displayed correctly</h1>
<h1>If characters arent displayed correctly in CotEditor</h1>
<p>Characters can be garbled if CotEditor fails to detect the files text encoding correctly. In such cases, change the text encoding as described below:</p>
<ol>
<li>Choose Format &gt; File Encoding, and then choose an encoding from the list.</li>
<li>Choose Format &gt; File Encoding, and then choose encoding from the list.</li>
<li>When a dialog appears, click Reinterpret.</li>
</ol>
<p><img src="../gfx/encodingWindow@2x.png" width="568"/></p>
@ -29,7 +29,7 @@
<ul>
<li>You can also change the text encoding from the encoding menu in the status bar.</li>
<li>Changing the priority of auto-detection may help to reduce the occurrences of garbled characters.<br />
<a href="howto_customize_encoding_order.html">Set the priority of encoding auto-detection</a></li>
<a href="howto_customize_encoding_order.html">Change priorities of text encodings</a></li>
<li>If you turn on “Refer to encoding declaration in document” in the Format preferences pane, in-document encoding declarations, such as “<code>encoding=</code>” or “<code>@charset</code>,” will take precedence when CotEditor detects the text encoding.<br />
<a href="about_autodetect_charset.html">Use encoding declarations for encoding detection</a></li>
</ul>
@ -38,7 +38,7 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="howto_customize_encoding_order.html">Change priority of encoding detection</a></li>
<li><a href="howto_customize_encoding_order.html">Change priorities of text encodings</a></li>
<li><a href="about_autodetect_charset.html">Use encoding declarations for encoding detection</a></li>
<li><a href="about_shiftjis.html">Use four kinds of Shift JIS properly</a></li>
</ul>

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="save, access privilege"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>If you cant save a file</title>
<title>If you cant save a file in CotEditor</title>
</head>
<body>
<h1>If you cant save a file</h1>
<h1>If you cant save a file in CotEditor</h1>
<p>In the cases described below, you cant save the file youre working on. What you need to do then is save it with another name, or change the file permission using the Finder or Terminal.</p>
<ul>

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="key binding, keyboard shortcut"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>If your key bindings dont work as you expect</title>
<title>If your key bindings dont work as you expect in CotEditor</title>
</head>
<body>
<h1>If your key bindings dont work as you expect</h1>
<h1>If your key bindings dont work as you expect in CotEditor</h1>
<p>If a key binding you set doesnt work properly chances are that:</p>
<ul>

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="issue, problem, solution, answer, question, environmnet, trouble, troubleshooting"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>If you cant find a solution</title>
<title>If you cant find a solution in CotEditor</title>
</head>
<body>
<h1>If you cant find a solution</h1>
<h1>If you cant find a solution in CotEditor</h1>
<p>If you couldnt find any answer to your problem, please inquire. In doing so, choose Create Issue Report in the Help menu and fill out the form.</p>

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="coloring, recoloring, re-color all"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>If syntax coloring seems not working properly</title>
<title>If syntax coloring seems not working properly in CotEditor</title>
</head>
<body>
<h1>If syntax coloring seems not working properly</h1>
<h1>If syntax coloring seems not working properly in CotEditor</h1>
<p>When syntax coloring seems not working properly, try the following procedure:</p>
<ol>
@ -17,8 +17,8 @@
</ol>
<p>If it doesnt help, the possible causes are:</p>
<ul>
<li>There is something inadequate in your text (e.g. inadequate programming syntax).</li>
<li>There is something inadequate in your syntax coloring rule.</li>
<li>There is something inadequate in your text (for example, inadequate programming syntax).</li>
<li>There is something inadequate in your syntax coloring definition.</li>
</ul>

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="Word Completion, complete words, completing"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Complete words</title>
<title>Complete a word in CotEditor</title>
</head>
<body>
<h1>Complete words</h1>
<h1>Complete a word in CotEditor</h1>
<p>Word completion assists you to input words faster, such as when typing reserved words of programming languages, by typing just a few letters and selecting the complete word from the candidate list.</p>
@ -17,7 +17,7 @@
<img class="bordered" src="../gfx/completion@2x.png" width="200" alt="completion.png"/>
</figure>
<p>To complete words, follow the instruction below:</p>
<p>To complete a word, follow the instruction below:</p>
<ol>
<li>Type the first few letters of a word.</li>
<li>Choose the Complete command in the Edit menu, or press either <kbd>Option</kbd>-<kbd>Esc</kbd> or <kbd>F5</kbd>.</li>

View File

@ -4,17 +4,17 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="Word Completion, possible completion"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Change the scope of completion words</title>
<title>Change the scope of completion words in CotEditor</title>
</head>
<body>
<h1>Change the scope of completion words</h1>
<h1>Change the scope of completion words in CotEditor</h1>
<p>You can expand/limit the range of possible completions. The completion list can show only the words in your document, or additionally, the words specified by your syntax style, or along with them all, standard words.</p>
<ol>
<li>Choose CotEditor &gt; Preferences.</li>
<li>Select Edit pane.</li>
<li>Select the Edit pane.</li>
<li>Under “Completion list includes”, select the range of your choice.</li>
</ol>

View File

@ -4,14 +4,19 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="text encoding, detection"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Change priority of encoding detection</title>
<title>Change priorities of text encodings in CotEditor</title>
</head>
<body>
<a name="howto_customize_encoding_order"></a>
<h1>Change priorities of text encodings in CotEditor</h1>
<h1>Change priority of encoding detection</h1>
<p>You can prioritize specific encodings to detect text encoding of documents.</p>
<figure>
<img src="../gfx/encodingPriority@2x.png" width="500" alt="Encoding priority setting dialog"/>
</figure>
<p>To change the priority of encoding detection on file opening:</p>
<ol>

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="font, character, font type, font size, customize"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Change font type</title>
<title>Change font type in CotEditor</title>
</head>
<body>
<h1>Change font type</h1>
<h1>Change font type in CotEditor</h1>
<p>You can change your documents font type.</p>
<ol>

View File

@ -4,18 +4,18 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="key bindings"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Customize key bindings</title>
<title>Customize key bindings in CotEditor</title>
</head>
<body>
<h1>Customize key bindings</h1>
<h1>Customize key bindings in CotEditor</h1>
<p>You can fully customize CotEditors menu key bindings. Also, you can store text snippets which have your preferred key bindings assigned. For instance, you can insert “<code>&lt;br /&gt;</code>” (with a line ending) by pressing <kbd>Shift</kbd>-<kbd>Return</kbd>. Go to Key Binbings pane in the preferences to create your own key bindings.</p>
<p>You can fully customize CotEditors menu key bindings. Also, you can store text snippets that have your preferred key bindings assigned. For example, you can insert “<code>&lt;br /&gt;</code>” (with a line ending) by pressing <kbd>Shift</kbd>-<kbd>Return</kbd>. Go to the Key Bindings pane in the preferences to create your own key bindings.</p>
<ul>
<li>You cannot set the shortcuts that are already taken (e.g. shortcuts for your script files or menu items that dont appear in the Menu Key Bindings list).</li>
<li>The shortcuts defined in the Script menu are not checked when assigned but will be automatically overriden.</li>
<li>You cannot set the shortcuts that are already taken (for example, shortcuts for your script files or menu items that dont appear in the Menu Key Bindings list).</li>
<li>The shortcuts defined in the Script menu are not checked when assigned but will be automatically overridden.</li>
</ul>

View File

@ -4,14 +4,23 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="theme, syntax coloring, highlight"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Customize themes</title>
<title>Customize themes in CotEditor</title>
</head>
<body>
<h1>Customize themes</h1>
<h1>Customize themes in CotEditor</h1>
<p>CotEditors theme is a collection of settings about the editors coloring. To customize themes:</p>
<p>CotEditors theme is a collection of settings about the editors coloring.</p>
<figure>
<img src="../gfx/theme@2x.png" width="400" class="bordered" alt="Theme setting view"/>
</figure>
<h2>Customize a theme</h2>
<p>To select a theme to customize:</p>
<ol>
<li>Choose CotEditor &gt; Preferences.</li>
<li>Select the Appearances pane.</li>
@ -20,8 +29,29 @@
<p>To use an existing theme as a guide for creating your own, choose Duplicate in the action button (gear icon) instead. You can also export your themes and import themes that are created by others.</p>
<h2>Theme file format</h2>
<p>CotEditor theme file must have extension .cottheme and its format is based on JSON with hexadecimal color values with <code>#</code> symbol.</p>
<p>To customize a theme:</p>
<ol>
<li>Click a color well in the theme editor.</li>
<li>Select a color in the Color panel.</li>
</ol>
<p>The change will be saved automatically and applied immediately.</p>
<p>If you check the “Use system color” option, the color specified in the system (System Preferences &gt; General) will be used for the background of the selected text in the editor, instead of a fixed color.</p>
<h2>Switch theme according to the appearance</h2>
<p>A pair of themes with the same theme name but “ (Dark)” (with a space) at the end of one of them will automatically switch themes depending on the windows appearance. In this case, the theme name for light mode can be either the theme name only or the theme name with “ (Light)” at the end. For example, bundled “Anura” and “Anura (Dark)” themes are a pair. So, “Anura” is used when the appearance is light, and “Anura (Dark)” is used in Dark Mode.</p>
<p>However, if you select a theme opposite to the appearance as the default theme, that theme will take precedence regardless of the appearance.</p>
<h2>File format of CotEditor themes</h2>
<p>CotEditor theme file must have extension .cottheme and its format is based on JSON with hexadecimal color values with a <code>#</code> symbol.</p>
<section id="cf">

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="toolbar, customizing"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Customize toolbar</title>
<title>Customize toolbar in CotEditor</title>
</head>
<body>
<h1>Customize toolbar</h1>
<h1>Customize toolbar in CotEditor</h1>
<p>Like the Finder or many Cocoa applications, CotEditor allows you to customize the toolbar. To do that:</p>
<ul>

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="invisible characters, invisibles, control characters, space, tab, line ending"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Display invisible characters</title>
<title>Display invisible characters in CotEditor</title>
</head>
<body>
<h1>Display invisible characters</h1>
<h1>Display invisible characters in CotEditor</h1>
<p>The Invisible Characters feature allows you to draw invisible characters, such as special characters for formatting, in a document with alternative symbols so that you can find where they are.</p>
@ -21,7 +21,7 @@
<p>You can switch the visibility of invisible characters in the current document by performing one of the following:</p>
<ul>
<li>Choose Show/Hide Invisible Characters command from the Format menu at the top of your screen.</li>
<li>Choose Show/Hide Invisible Characters command from the Format menu.</li>
<li>Select the Invisibles button in the window toolbar (The Invisibles button can be added by customizing the toolbar).</li>
<li>Select the Invisibles button in the Touch Bar (The Invisibles button can be added by customizing the Touch Bar).</li>
</ul>

View File

@ -4,15 +4,19 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="multi cursor, multi insersion, multiple cursors, rectangular selection"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Edit multiple points</title>
<title>Edit multiple points in CotEditor</title>
</head>
<body>
<h1>Edit multiple points</h1>
<h1>Edit multiple points in CotEditor</h1>
<p>In multi-cursor editing, the same text can be input at multiple desired points at once.</p>
<figure>
<img src="../gfx/rectangularSelection@2x.png" width="300" class="bordered"/>
</figure>
<p>You can add your insertion points (cursors/selections) in the following ways:</p>
<ul>
<li>To add an insertion point at the desired location, click or drag the point while pressing the <kbd>Command</kbd> key.</li>

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="File Drop"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Drop files</title>
<title>Drop files to editor in CotEditor</title>
</head>
<body>
<h1>Drop files</h1>
<h1>Drop files to editor in CotEditor</h1>
<p>File Drop is the feature to insert custom text based on the files dropped to the editor. For example, you can automatically insert the <code>img</code> tag into your HTML document by dropping an image file from the Finder.</p>

View File

@ -4,14 +4,13 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="find,replace,replacement,regex,regular expression"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Find or replace text</title>
<title>Find or replace text in CotEditor</title>
</head>
<body>
<a name="howto_find"></a>
<h1>Find or replace text</h1>
<h1>Find or replace text in CotEditor</h1>
<p>CotEditor has a powerful find and replacement feature that also can use regular expression.</p>
@ -116,7 +115,7 @@
<ul>
<li><a href="howto_find_newline.html">Find or replace a line ending</a></li>
<li><a href="about_regex.html">Use the regular expression</a></li>
<li><a href="howto_multiple_replace.html">Replace with multiple rules</a></li>
<li><a href="howto_multiple_replace.html">Replace text by multiple rules</a></li>
</ul>
</section>

View File

@ -4,13 +4,13 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="line ending, newline, LF, CR, CRLF"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Find inconsistent line endings</title>
<title>Find inconsistent line endings in CotEditor</title>
</head>
<body>
<a name="inconsistent_line_endings"></a>
<h1>Find inconsistent line endings</h1>
<h1>Find inconsistent line endings in CotEditor</h1>
<p>CotEditor automatically detects line endings inconsistent with the document line ending setting. Inconsistent line endings can cause problems in various ways, such as running a script.</p>
@ -48,7 +48,7 @@
<ul>
<li><a href="about_line_endings.html">Handle various types of line endings</a></li>
<li><a href="howto_find_newline.html">Find or replace a line ending</a></li>
<li><a href="howto_inspect_usedchar.html">Check whether incompatible characters are included</a></li>
<li><a href="howto_inspect_usedchar.html">Find characters incompatible with document encoding</a></li>
</ul>
</section>

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="search, replace, line ending, newline, line break"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Find or replace a line ending</title>
<title>Find or replace a line ending in CotEditor</title>
</head>
<body>
<h1>Find or replace a line ending</h1>
<h1>Find or replace a line ending in CotEditor</h1>
<h2>Input a line ending</h2>
@ -46,7 +46,7 @@
<p>As for the text replacing with, all line endings even ones defined as a metacharacter like<code>\n</code> or captured are assumed as the document line ending.</p>
<p>For instance, when replacing the find string “dog\Rcow” with the replacement string “$0\r” using the regular expression in a document whose line ending type is LF (<code>\n</code>), the substring “dog<span class="invisible">\r\n</span>cow” in the document matches as well, and theoretically, the regular expression should replace it with “dog<span class="invisible">\r\n</span>cow<span class="invisible">\r</span>”; however CotEditor actually replaces it with “dog<span class="invisible">\n</span>cow<span class="invisible">\n</span>”.</p>
<p>For example, when replacing the find string “dog\Rcow” with the replacement string “$0\r” using the regular expression in a document whose line ending type is LF (<code>\n</code>), the substring “dog<span class="invisible">\r\n</span>cow” in the document matches as well, and theoretically, the regular expression should replace it with “dog<span class="invisible">\r\n</span>cow<span class="invisible">\r</span>”; however CotEditor actually replaces it with “dog<span class="invisible">\n</span>cow<span class="invisible">\n</span>”.</p>
<p>There is currently no way to replace with line endings other than the document line ending.</p>

View File

@ -4,21 +4,28 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="input, insert, unicode, code point, hex"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Input a character using Unicode code point</title>
<title>Input a character using Unicode code point in CotEditor</title>
</head>
<body>
<h1>Input a character using Unicode code point</h1>
<h1>Input a character using Unicode code point in CotEditor</h1>
<p>You can input characters with Unicode code points.</p>
<figure>
<img src="../gfx/unicodeInput@2x.png" width="230" class="bordered" alt="The Unicode input field where is filled “1F603”"/>
</figure>
<p>To input a character with Unicode code point in the hexadecimal format at the current insertion position:</p>
<ol>
<li>Choose Edit &gt; Input in Unicode Code Point.</li>
<li>Enter a code point in the field.</li>
<li>Enter a code point in the field, or select a code point from the history.</li>
<li>Press the <kbd>Return</kbd> key.</li>
</ol>
<p>Unicode character code to input should be just 4 or 5-digit hexadecimal format as well as hexadecimal code with “U+”, “0x”, or “\u” prefixes. For example, “1F603”, “U+1F603”, “0x1F603”, or “\u1F603” are valid to input “😃”.</p>
<p>Unicode character code to input should be just hexadecimal format as well as hexadecimal code with “U+”, “0x”, or “\u” prefixes. For example, “1F603”, “U+1F603”, “0x1F603”, or “\u1F603” are valid to input “😃”.</p>
</body>
</html>

View File

@ -4,14 +4,18 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="unicode, character, code point"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Get information about a character</title>
<title>Get information about a character in CotEditor</title>
</head>
<body>
<h1>Get information about a character</h1>
<h1>Get information about a character in CotEditor</h1>
<p>CotEditor can inspect the information about the selected character. Select exactly a single character and choose Inspect Character in the Text menu or press <kbd>Command</kbd>-<kbd>Option</kbd>-<kbd>I</kbd> keys.</p>
<p>CotEditor can inspect the information about the selected character. Select exactly a single character and choose Inspect Character in the Text menu or press the <kbd>Command</kbd>-<kbd>Option</kbd>-<kbd>I</kbd> keys.</p>
<figure>
<img src="../gfx/characterInspector@2x.png" width="637" alt="The character inspector indicating the information about the character 🐕"/>
</figure>
<p>In the inspector, the character in close-up, the Unicode character name, block name, general category, and the Unicode code point will be displayed. It shows also UTF-16 codes of each character in braces if the character is a surrogate pair. If the selected letter consists actually of multiple Unicode characters, only the code points and Unicode name will be listed-up.</p>

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="Get Info, information"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Get information about a document</title>
<title>Get information about a document in CotEditor</title>
</head>
<body>
<h1>Get information about a document</h1>
<h1>Get information about a document in CotEditor</h1>
<p>In the document inspector, you can see the various information about your document.</p>
<ol>

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="Get Info, information, incompatible characters"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Check whether incompatible characters are included</title>
<title>Find characters incompatible with document encoding in CotEditor</title>
</head>
<body>
<h1>Check whether incompatible characters are included</h1>
<h1>Find characters incompatible with document encoding in CotEditor</h1>
<p>If you input a character which is incompatible with your documents current encoding, it can appear garbled when you save and reopen the file. This function helps to prevent that kind of problem. You can check if there are any such problematic characters in your document, before closing it.</p>
<p>Also, this function is useful when you are going to convert between the two encodings whose character repertoires are different from each other, for example, from Japanese (Mac OS) to Japanese (Windows, DOS) or from Unicode to a local encoding.</p>

View File

@ -4,24 +4,36 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="Go to, menu"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Go to a specific line</title>
<title>Go to a specific line in CotEditor</title>
</head>
<body>
<a name="howto_jump"></a>
<h1>Go to a specific line in CotEditor</h1>
<h1>Go to a specific line</h1>
<p>The “Go to Line” command allows you to select and move to a specific line quickly.</p>
<p>When you choose Go to Line in the Find menu, or press Command-L, CotEditor displays the Go To dialog to give you quick access to the line(s) you want to see.</p>
<p>In the dialog, enter the line number, and click Go.</p>
<figure>
<img src="../gfx/jumpToLine@2x.png" width="300" class="bordered" alt="Go to Line dialog"/>
</figure>
<ol>
<li>Choose Go to Line in the Find menu</li>
<li>Enter the line number where to jump to the dialog.</li>
<li>Click Go, or press </kbd>Return</kbd>.</li>
</ol>
<p>You can also specify a range of lines.</p>
<ul>
<li><dl><dt>If you type in “3”:</dt>
<dd>→ The line 3 (the third line from the top) will be selected.</dd></dl></li>
<dd>Line 3 (the third line from the top) will be selected.</dd></dl></li>
<li><dl><dt>If you type in “3:2”:</dt>
<dd>→ What this indicates is “starting from line 3, select 2 lines.” Thus, the line 3 and 4 will be selected.</dd></dl></li>
<dd>→ What this indicates is “starting from line 3, select 2 lines.” Thus, lines 3 and 4 will be selected.</dd></dl></li>
<li><dl><dt>If you type in “3:-1”:</dt>
<dd>→ What this indicates is “starting from line 3, select the rest lines except the last 1 line.” Thus, if the document has 10 lines, the lines from the line 3 to 9 will be selected.</dd></dl></li>
<dd>→ What this indicates is “starting from line 3, select the rest lines except the last 1 line.” Thus, if the document has 10 lines, the lines from line 3 to 9 will be selected.</dd></dl></li>
</ul>
</body>

View File

@ -4,34 +4,31 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="find,replace,replacement,regex,regular expression,batch"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Replace with multiple rules</title>
<title>Replace text by multiple rules in CotEditor</title>
</head>
<body>
<a name="howto_multiple_replace"></a>
<h1>Replace with multiple rules</h1>
<h1>Replace text by multiple rules in CotEditor</h1>
<p>Using the <dfn>Multiple Replacement</dfn> feature, you can process multiple text replacements at once in succession. The replacement rules can be stored as a named preset and reused when you need.</p>
<section>
<h2>Use Multiple Replace window</h2>
<p>You can open the Multiple Replace window to manage and process the multiple replacements in your document.</p>
<ul>
<li>Choose Find &gt; Multiple Replace (from the CotEditor menu at the top of your screen).</li>
</ul>
<ol>
<li>Choose Find &gt; Multiple Replace.</li>
</ol>
<p><img src="../gfx/multiple_replace_panel@2x.png" width="587" alt=""/></p>
</section>
<section>
<h2>Manage replacement definitions</h2>
<p>The stored replacement definitions that you created before are listed in the list on the left.</p>
@ -45,7 +42,6 @@
<section>
<h3>Export/import replacement definitions</h3>
<p>You can export your replacement definitions to transfer them to another computer. Each replacement definition becomes a single <dfn>CotEditor replacement definition</dfn> file, which has a .cotrpl filename extension and of which content is written in JSON format.</p>
@ -54,12 +50,9 @@
<li><b>Export</b>: Select a definition to export in the list on the left, then choose Export or Share in the Advanced menu at the bottom of the list.</li>
<li><b>Import</b>: Drop replacement definition files to the list on the left. Alternatively, choose Import in the Advanced menu, then select the replacement definition files to import.</li>
</ul>
</section>
</section>
<section>
<h2>Process multiple replacements</h2>
<p>The definition selected in the list on the left is shown in the editor area on the right side. The replacement rules in the editor area will be performed row by row from top to bottom at once.</p>
@ -72,16 +65,14 @@
</ul>
<p>* Beware that the matches by the Highlight command can be different from the replacement targets when you perform actual Replace All, because, on the Replace All, the succeeding rows are applied to the document that the previous rows above have already been applied to.</p>
</section>
<section>
<h2>Edit replacement definition</h2>
<p>You can create your own replacement definitions to process multiple replacements.</p>
<section>
<h3>Create a new replacement definition</h3>
<ol>
@ -93,10 +84,9 @@
<p>You dont need to perform a save after the modification because your changes will be saved automatically immediately during the edit.</p>
<p>A row with an invalid replacement rule will just be skipped when the replacement is performed.</p>
</section>
<section>
<h3>Replacement rule options</h3>
<table>
@ -112,18 +102,14 @@
<tr><th>Description</th><td>You can use this field to leave a comment about the rule. The description doesnt affect to replacement. This field can be left blank.</td></tr>
</tbody>
</table>
</section>
</section>
<section>
<h2>Advanced find options</h2>
<p>You can customize the delicate find behavior of replacement from the advanced options view. Those settings are also saved to your replacement definition and applied to all rules in the same replacement definition. Click the gear button in the Multiple Replace window, then click checkboxes to change the behavior.</p>
<p>To learn about details of each option item, see <a href="howto_find.html">Find or replace text</a>.</p>
</section>

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="invisible, file, open, hidden"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Open hidden files</title>
<title>Open hidden files in CotEditor</title>
</head>
<body>
<h1>Open hidden files</h1>
<h1>Open hidden files in CotEditor</h1>
<p>The checkbox “Show hidden files” in the open dialog can switch the visibility of hidden files in the dialog.</p>

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="paste, paste exactly, clipboard, line ending"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Paste text</title>
<title>Paste text in CotEditor</title>
</head>
<body>
<h1>Paste text</h1>
<h1>Paste text in CotEditor</h1>
<p>You can paste the plain-text information in the clipboard to the insertion points in the current editor by choosing Edit &gt; Paste or pressing <kbd>Command</kbd>-<kbd>V</kbd>.</p>
<p>When the text is pasted, CotEditor implicitly converts the line endings in the text to paste to the line endings in the document to be pasted so that you dont need to care about the difference in the line endings types.</p>

View File

@ -4,13 +4,13 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="sort, pattern sort"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Sort lines with specific pattern</title>
<title>Sort lines using specific pattern in CotEditor</title>
</head>
<body>
<a name="howto_pattern_sort"></a>
<h1>Sort lines with specific pattern</h1>
<h1>Sort lines using specific pattern in CotEditor</h1>
<p>From Sort by Pattern command in the Text &gt; Lines menu, you can sort selected lines by specifying the way to compare.</p>
@ -73,5 +73,13 @@
</table>
</section>
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="about_regex.html">Use the regular expression</a></li>
</ul>
</section>
</body>
</html>

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="print, header, footer"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Print a document</title>
<title>Print a document in CotEditor</title>
</head>
<body>
<h1>Print a document</h1>
<h1>Print a document in CotEditor</h1>
<p>To print your document, choose File &gt; Print.</p>
<ul>

View File

@ -4,15 +4,19 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="selecting rectangular area"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Select rectangular area</title>
<title>Select rectangular area in CotEditor</title>
</head>
<body>
<h1>Select rectangular area</h1>
<h1>Select rectangular area in CotEditor</h1>
<p>You can select a rectangular area in your document. To do so, drag and select text while holding down the <kbd>Option</kbd> key.</p>
<figure>
<img src="../gfx/rectangularSelection@2x.png" width="300" class="bordered"/>
</figure>
<section id="cf">
<h2>See also</h2>

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="Outline"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Build Outline</title>
<title>Build Outline in CotEditor</title>
</head>
<body>
<h1>Build Outline</h1>
<h1>Build Outline in CotEditor</h1>
<p>The Outline feature extracts specific parts of your document and generates a list according to the definition of the syntax style.</p>
@ -21,9 +21,9 @@
<p>The Outline menu is a pop-up menu displayed in the navigation bar located beneath the toolbar. It displays the nearest Outline item above the insertion point and moves the insertion point to the corresponding part by opening the menu and clicking an item in the menu.</p>
<p>To show the Outline menu:</p>
<ul>
<ol>
<li>Choose View &gt; Show Navigation Bar.</li>
</ul>
</ol>
<h2>Display Outline inspector</h2>

View File

@ -4,16 +4,19 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="splitting, split editor, split view"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Split editor</title>
<title>Split editor in CotEditor</title>
</head>
<body>
<h1>Split editor</h1>
<h1>Split editor in CotEditor</h1>
<p>You can split the editor to display and edit different areas in the document at the same time.</p>
<p><img src="../gfx/split_editor@2x.png" width="400" class="bordered" alt=""/></p>
<p>To split an editor into multiple panes, choose View &gt; Split Editor, or, click the icon on the right edge of the navigation bar.</p>
<p>To close a split editor, choose View > Close Split Editor, or click the icon on the left edge of the navigation bar.</p>
<p><img src="../gfx/split_editor@2x.png" width="400" alt=""/></p>
<p>The default orientation to split editors can be set in Preferences &gt; Window &gt; Split editor. You can also change split orientation by choosing View &gt; Stack Editors Horizontally (or Vertically) in the menu.</p>

View File

@ -4,14 +4,13 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="Appearance preferences, Appearance, appearance"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Change Appearance preferences</title>
<title>Change Appearance preferences in CotEditor</title>
</head>
<body>
<a name="pref_appearance"></a>
<h1>Change Appearance preferences</h1>
<h1>Change Appearance preferences in CotEditor</h1>
<p>In the CotEditor app <img class="appicon" src="../../Shared/gfx/icon_16x16@2x.png" height="16" alt=""/> on your Mac, use Appearance preferences to choose the appearance of documents, such as font, line height, and colors. To change these preferences, choose CotEditor &gt; Preferences, then click Appearance.</p>
@ -123,7 +122,7 @@
<h2>See also</h2>
<ul>
<li><a href="howto_customize_theme.html">Customize themes</a></li>
<li><a href="preferences.html">Change preferences in CotEditor</a></li>
<li><a href="preferences.html">Change preferences</a></li>
</ul>
</section>

View File

@ -4,14 +4,13 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="Edit preferences, edit, edit style"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Change Edit preferences</title>
<title>Change Edit preferences in CotEditor</title>
</head>
<body>
<a name="pref_edit"></a>
<h1>Change Edit preferences</h1>
<h1>Change Edit preferences in CotEditor</h1>
<p>In the CotEditor app <img class="appicon" src="../../Shared/gfx/icon_16x16@2x.png" height="16" alt=""/> on your Mac, use Edit preferences to choose how the editor behaves while editing. To change these preferences, choose CotEditor &gt; Preferences, then click Edit.</p>
@ -151,7 +150,7 @@
<ul>
<li><strong>Words in document</strong>: The list includes the words that appear in your document.</li>
<li><strong>Words defined in syntax style</strong>: The list includes the words defined by your syntax style (in the case youve not specified any completions, the words generated by the syntax coloring rule appear).</li>
<li><strong>Words defined in syntax style</strong>: The list includes the words <a href="syntax_completion_settings.html">defined in the syntax style</a> (in the case youve not specified any completions, the words generated by the syntax style definition appear).</li>
<li><strong>Standard words</strong>: The list includes standard words.</li>
</ul></td>
@ -169,7 +168,7 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="preferences.html">Change preferences in CotEditor</a></li>
<li><a href="preferences.html">Change preferences</a></li>
</ul>
</section>

View File

@ -4,14 +4,13 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="File Drop preferences, File Drop"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Change File Drop preferences</title>
<title>Change File Drop preferences in CotEditor</title>
</head>
<body>
<a name="pref_filedrop"></a>
<h1>Change File Drop preferences</h1>
<h1>Change File Drop preferences in CotEditor</h1>
<p>In the CotEditor app <img class="appicon" src="../../Shared/gfx/icon_16x16@2x.png" height="16" alt=""/> on your Mac, use File Drop preferences to choose how to insert a preset text when you drop a file onto the editor. To change these preferences, choose CotEditor &gt; Preferences, then click File Drop.</p>
@ -54,9 +53,9 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="howto_filedrop.html">Drop files</a></li>
<li><a href="howto_filedrop.html">Drop files to editor</a></li>
<li><a href="about_filedrop.html">Write insertion format for File Drop</a></li>
<li><a href="preferences.html">Change preferences in CotEditor</a></li>
<li><a href="preferences.html">Change preferences</a></li>
</ul>
</section>

View File

@ -4,14 +4,13 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="Format preferences, format, line endings, new line, encoding, syntax"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Change Format preferences</title>
<title>Change Format preferences in CotEditor</title>
</head>
<body>
<a name="pref_format"></a>
<h1>Change Format preferences</h1>
<h1>Change Format preferences in CotEditor</h1>
<p>In the CotEditor app <img class="appicon" src="../../Shared/gfx/icon_16x16@2x.png" height="16" alt=""/> on your Mac, use Format preferences to set the default format for documents such as line ending type and text encoding, and to manage syntax styles. To change these preferences, choose CotEditor &gt; Preferences, then click Format.</p>
@ -40,7 +39,7 @@
<td>The priority of encodings and the policy of encoding detection when opening an existing file.
<dl>
<dt>Edit List</dt>
<dd>Click Edit List to set the order of encodings that appear in the File Encoding submenu in the Format menu and the File Encoding drop-down list on the toolbar. This order is also used for encoding detection. CotEditor tries each encoding from the top of the list. See <a href="howto_customize_encoding_order.html">Change priority of encoding detection</a> for details.</dd>
<dd>Click Edit List to set the order of encodings that appear in the File Encoding submenu in the Format menu and the File Encoding drop-down list on the toolbar. This order is also used for encoding detection. CotEditor tries each encoding from the top of the list. See <a href="howto_customize_encoding_order.html">Change priorities of text encodings</a> for details.</dd>
</dl></td>
</tr>
@ -100,10 +99,10 @@
<h2>See also</h2>
<ul>
<li><a href="about_line_endings.html">Handle various types of line endings</a></li>
<li><a href="howto_customize_encoding_order.html">Change priority of encoding detection</a></li>
<li><a href="howto_customize_encoding_order.html">Change priorities of text encodings</a></li>
<li><a href="syntax_definition.html">Define a syntax style</a></li>
<li><a href="syntax_file_mapping.html">Map files to syntax styles</a></li>
<li><a href="preferences.html">Change preferences in CotEditor</a></li>
<li><a href="preferences.html">Change preferences</a></li>
</ul>
</section>

View File

@ -4,14 +4,13 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="General preferences, general"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Change General preferences</title>
<title>Change General preferences in CotEditor</title>
</head>
<body>
<a name="pref_general"></a>
<h1>Change General preferences</h1>
<h1>Change General preferences in CotEditor</h1>
<p>In the CotEditor app <img class="appicon" src="../../Shared/gfx/icon_16x16@2x.png" height="16" alt=""/> on your Mac, use General preferences to choose how to handle documents, save, and more. To change these preferences, choose CotEditor &gt; Preferences, then click General.</p>
@ -46,14 +45,14 @@
</tr>
<tr>
<th>When document is modified by another application</th>
<th>When document is changed by another application</th>
<td>Choose the behavior when the document file was updated by another application while it is opened in CotEditor.
<ul>
<li><strong>Keep CotEditors edition</strong>: Do nothing and keep CotEditors edition. CotEditor may ask whether overwrite the file that was modified by another application first when you save the document.</li>
<li><strong>Keep CotEditors edition</strong>: Do nothing and keep CotEditors edition. CotEditor may ask whether overwrite the file that was changed by another application first when you save the document.</li>
<li><strong>Ask how to resolve</strong>: Display a dialog when the file was modified by another application so that you can choose between keeping CotEditors edition or reverting to the latest file.</li>
<li><strong>Ask how to resolve</strong>: Display a dialog when the file was changed by another application so that you can choose between keeping CotEditors edition or reverting to the latest file.</li>
<li><strong>Update to modified edition</strong>: Update the editors text to the latest version silently when the file was modified by another application. Take notice that the undo history will also be cleared after updating.</li>
<li><strong>Update to modified edition</strong>: Update the editors text to the latest version silently when the file was changed by another application. Take notice that the undo history will also be cleared after updating.</li>
</ul></td>
</tr>
@ -119,7 +118,7 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="preferences.html">Change preferences in CotEditor</a></li>
<li><a href="preferences.html">Change preferences</a></li>
</ul>
</section>

View File

@ -4,14 +4,13 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="Key Bindings preferences, key binding, keyboard shortcut, snippet"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Change Key Bindings preferences</title>
<title>Change Key Bindings preferences in CotEditor</title>
</head>
<body>
<a name="pref_keybindings"></a>
<h1>Change Key Bindings preferences</h1>
<h1>Change Key Bindings preferences in CotEditor</h1>
<p>In the CotEditor app <img class="appicon" src="../../Shared/gfx/icon_16x16@2x.png" height="16" alt=""/> on your Mac, use Key Bindings preferences to customize keyboard shortcuts to execute menu item commands, and to store some text snippets you use frequently along with your preferred keyboard shortcuts. To change these preferences, choose CotEditor &gt; Preferences, then click Key Bindings.</p>
@ -58,7 +57,7 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="preferences.html">Change preferences in CotEditor</a></li>
<li><a href="preferences.html">Change preferences</a></li>
</ul>
</section>

View File

@ -4,15 +4,13 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="Print preferences, print"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Change Print preferences</title>
<title>Change Print preferences in CotEditor</title>
</head>
<body>
<a name="pref_print"></a>
<h1>Change Print preferences</h1>
<h1>Change Print preferences in CotEditor</h1>
<p>In the CotEditor app <img class="appicon" src="../../Shared/gfx/icon_16x16@2x.png" height="16" alt=""/> on your Mac, use Print preferences to choose the default style for document printing. To change these preferences, choose CotEditor &gt; Preferences, then click Print.</p>
@ -74,7 +72,7 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="preferences.html">Change preferences in CotEditor</a></li>
<li><a href="preferences.html">Change preferences</a></li>
</ul>
</section>

View File

@ -4,14 +4,13 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="Window preferences, window"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Change Window preferences</title>
<title>Change Window preferences in CotEditor</title>
</head>
<body>
<a name="pref_window"></a>
<h1>Change Window preferences</h1>
<h1>Change Window preferences in CotEditor</h1>
<p>In the CotEditor app <img class="appicon" src="../../Shared/gfx/icon_16x16@2x.png" height="16" alt=""/> on your Mac, use Window preferences to customize the default window appearance such as widow size or line number display. To change these preferences, choose CotEditor &gt; Preferences, then click Window.</p>
@ -81,7 +80,7 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="preferences.html">Change preferences in CotEditor</a></li>
<li><a href="preferences.html">Change preferences</a></li>
</ul>
</section>

View File

@ -5,16 +5,13 @@
<meta name="keywords" content="version, history, changelog, release notes"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<link rel="stylesheet" href="../../Shared/sty/releasenotes.css"/>
<title>Release Notes</title>
<title>Release notes for CotEditor</title>
</head>
<body>
<a name="releasenotes"></a>
<h1>Release Notes</h1>
<h1>Release notes for CotEditor</h1>
<article>
<header>
@ -80,6 +77,7 @@
<h2>Fixes</h2>
<ul>
<li>Fix an issue that the changes of syntax styles after the launch were not applied to the file mapping.</li>
<li><span class="trivial">trivial</span>: Fix an issue that the Script menu appeared in the shortcut menu even when no script exists.</li>
</ul>
</section>

View File

@ -9,6 +9,7 @@
</head>
<body>
<h1>Add scripting hooks to CotEditor scripts</h1>
<p>Scripting hooks allow CotEditor scripts to be executed on certain events. The following events are available with CotEditor:</p>
@ -119,7 +120,7 @@ HookingScript.scptd
<ul>
<li><a href="script_overview.html">Script CotEditor</a></li>
<li><a href="script_menu.html">Customize the Script menu</a></li>
<li><a href="script_osascript.html">Create AppleScript scripts</a></li>
<li><a href="script_osascript.html">Script CotEditor with AppleScript</a></li>
</ul>
</section>

View File

@ -4,16 +4,17 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="Script menu, script"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Customize Script menu</title>
<title>Customize Script menu in CotEditor</title>
</head>
<body>
<h1>Customize Script menu</h1>
<h1>Customize Script menu in CotEditor</h1>
<p>You can change the order of sripts in the menu or assign keyboard shortcuts to scripts by modifying the filenames of your scripts in the script folder.</p>
<h2>Order of appearance</h2>
<h2>Order of items in the menu</h2>
<p>By adding “number + closing parenthesis ())” at the head of the name, you can line up the files in numeric order. The part “number + )” wont be shown in the menu.</p>
@ -38,7 +39,7 @@
<h2>Hidden files/folders</h2>
<p>A file/folder whose name begins with the underscore “_” will not be lined up in the script menu. You can use them for setting files, library scripts, and so on.</p>
<p>A file/folder whose name begins with the underscore “_” will not be lined up in the script menu. You can use it for setting files, library scripts, and so on.</p>
<h2>Submenus</h2>

View File

@ -5,11 +5,12 @@
<meta name="keywords" content="Script menu, script, AppleScript, JXA, JavaScript"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<link rel="stylesheet" href="../../Shared/sty/applescript.css"/>
<title>Create AppleScript</title>
<title>Script CotEditor with AppleScript</title>
</head>
<body>
<h1>Create AppleScript</h1>
<h1>Script CotEditor with AppleScript</h1>
<p>CotEditor works with AppleScript and JXA (JavaScript for Automation).</p>

View File

@ -8,6 +8,7 @@
</head>
<body>
<h1>Support different CotEditor versions in AppleScript</h1>
<p>This page lists up the previous specific changes on AppleScript support in CotEditor.</p>
@ -207,7 +208,7 @@ end tell
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="script_osascript.html">Create AppleScript scripts</a></li>
<li><a href="script_osascript.html">Script CotEditor with AppleScript</a></li>
</ul>
</section>
</body>

View File

@ -10,7 +10,6 @@
<body>
<a name="script_overview"></a>
<h1>Script CotEditor</h1>
<p>CotEditor has a scripting feature that lets you run your own scripts on CotEditor to manipulate documents or launch external programs. Your scripts are shown in the Script menu represented with <object type="image/svg+xml" data="../../Shared/gfx/script.svg" height="14">script icon</object>.</p>
@ -28,20 +27,20 @@
<li>UNIX script</li>
</ul>
<p>While AppleScript (incl. JXA; JavaScript for Automation) can control CotEditors document more flexibly, UNIX scripts can only modify the contents of the frontmost document. However, as for UNIX scripts, you can write them in various languages, for example; Python, Ruby, Perl, and so on. Choose a script type to suit your use. For details about how to write your scripts, refer to <a href="script_osascript.html">Create AppleScript scripts</a> or <a href="script_unixscript.html">Create UNIX scripts</a>.</p>
<p>While AppleScript (incl. JXA; JavaScript for Automation) can control CotEditors document more flexibly, UNIX scripts can only modify the contents of the frontmost document. However, as for UNIX scripts, you can write them in various languages, for example; Python, Ruby, Perl, and so on. Choose a script type to suit your use. For details about how to write your scripts, refer to <a href="script_osascript.html">Script CotEditor with AppleScript</a> or <a href="script_unixscript.html">Script CotEditor with UNIX script</a>.</p>
<h2>Add/delete scripts</h2>
<p>To add scripts to or remove scripts from the Script menu, follow the instruction below:</p>
<ol>
<li>Choose Script &gt; Open Scripts Folder in CotEditor and the Finder opens the folder for CotEditor script at:<br/>
<li>Choose Script &gt; Open Scripts Folder in CotEditor and the Finder opens the folder for CotEditor scripts at:<br/>
~/Library/Application Scripts/com.coteditor.CotEditor/</li>
<li>Put your script files in this folder, or remove them from there.</li>
<li>The changes you made inside the scripts folder will be automatically reflected.</li>
<li>The changes you made inside the scripts folder will be automatically reflected in the menu.</li>
</ol>
<p>You can change the order of scripts or assign keyboard shortcuts by modifying the names of your script files. See <a href="script_menu.html">Customize the Script menu</a> for more details.</p>
<p>You can change the order of scripts or assign keyboard shortcuts by modifying the names of your script files. See <a href="script_menu.html">Customize the Script menu</a> for the details.</p>
<h2>Get existing CotEditor scripts</h2>
@ -56,8 +55,8 @@
<h2>See also</h2>
<ul>
<li><a href="script_menu.html">Customize the Script menu</a></li>
<li><a href="script_osascript.html">Create AppleScript scripts</a></li>
<li><a href="script_unixscript.html">Create UNIX scripts</a></li>
<li><a href="script_osascript.html">Script CotEditor with AppleScript</a></li>
<li><a href="script_unixscript.html">Script CotEditor with UNIX script</a></li>
</ul>
</section>

View File

@ -4,25 +4,33 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="Script Menu, script"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Create UNIX scripts</title>
<title>Script CotEditor with UNIX script</title>
</head>
<body>
<h1>Create UNIX scripts</h1>
<h1>Script CotEditor with UNIX script</h1>
<p>This page explains how to pass your documents text to UNIX scripts that are executable via the Script menu, or how to receive the outputs from them.</p>
<ul>
<li>The filename extensions of the scripts you can add to the Script menu are: .sh .pl .php .rb .py .js .swift (regardless of their languages)</li>
<li>The filename extensions of the scripts you can add to the Script menu are: .sh, .pl, .php, .rb, .py, .js, and .swift (regardless of the language)</li>
<li>In order to run a script, you need to set execute permission for the script file.</li>
</ul>
<h2>Refer to the document file path</h2>
<p>If the frontmost document has already been saved, the absolute file path of the document will be referred to as an argument.</p>
<h2>Pass text data to a script</h2>
<p>To pass text data from CotEditor to your script, you need to put a comment at the beginning of the script and write “<code>%%%{CotEditorXInput=xxxx}%%%</code>” inside. Replace “<code>xxxx</code>” with one of the parameters below.</p>
<p>A script can receive the contents of the frontmost document on STDIN (standard in). To pass text data from CotEditor to your script, you need to put a comment at the beginning of the script and write “<code>%%%{CotEditorXInput=<var>xxxx</var>}%%%</code>” inside. Replace “<code><var>xxxx</var></code>” with one of the parameters below. With no parameters, CotEditor passes nothing just like when you put “<coee>None</code>.”</p>
<ul>
<li>CotEditor passes text data encoded with UTF-8.</li>
</ul>
<table>
<thead>
@ -35,15 +43,14 @@
</tbody>
</table>
<ul style="margin-top: 1em;">
<li>With no parameters, CotEditor passes nothing just like when you put “None.”</li>
<li>A script should capture CotEditors text data on STDIN (standard in).</li>
<li>CotEditor passes text data with UTF-8 encoding.</li>
</ul>
<h2>Receive output data from a script</h2>
<p>To make CotEditor receive output data from a script, you need to put a comment at the beginning of the script and write “<code>%%%{CotEditorXOutput=xxxx}%%%</code>” inside. Replace “<code>xxxx</code>” with one of the parameters below.</p>
<p>CotEditor can receive the output text from the script on STDOUT (standard out) and apply it to the document and so on. To make CotEditor receive output data from a script, you need to put a comment at the beginning of the script and write “<code>%%%{CotEditorXOutput=<var>xxxx</var>}%%%</code>” inside. Replace <code><var>xxxx</var></code> with one of the parameters below. Without parameters, CotEditor does nothing just like when you put “<code>Discard</code>.”</p>
<ul>
<li>The encoding of the text that CotEditor receives must be UTF-8.</li>
</ul>
<table>
<thead>
@ -60,24 +67,34 @@
</tbody>
</table>
<ul>
<li>Without parameters, CotEditor does nothing just like when you put “Discard.”</li>
<li>A script should output the text data for CotEditor on STDOUT (standard out).</li>
<li>The text encoding of the text that CotEditor receives must be UTF-8.</li>
</ul>
<h2>Print text to the Console</h2>
<p>The string thrown to the standard error will be printed in the Console window.</p>
<h2>Example</h2>
<p>The following Python script prepends “&gt;” character to every line in the selection of the frontmost document.</p>
<pre class="source"><code><span class="comment">#!/usr/bin/env python
<p>The following Python script prepends the “&gt;” character to every line in the selection of the frontmost document, and then prints the number of the processed lines to the Console.</p>
<pre class="source"><code><span class="comment">#!/usr/bin/env python3
# %%%{CotEditorXInput=Selection}%%%
# %%%{CotEditorXOutput=ReplaceSelection}%%%</span>
<span class="keyword">import</span> sys
count = 0
<span class="keyword">for</span> line <span class="keyword">in</span> sys.stdin:
count += 1
print(<span class="string">&quot;&gt;&quot;</span> + line.rstrip())
sys.stderr.write(<span class="string">&quot;Processed {} lines.&quot;</span>.format(count))
</code></pre>
<figure>
<figcaption>Output to the Console</figcaption>
<img src="../gfx/console@2x.png" width="406" alt="[2022-05-06 18:35:00] Example Code&#x0A;Processed 5 lines."/>
</figure>
<p>You can get more sample scripts on:<br/>
<a href="https://github.com/coteditor/SampleScripts" rel="external">coteditor/SampleScripts -GitHub</a></p>

View File

@ -32,7 +32,7 @@ Validate your customized syntax styles in syntax style editor and follow the mes
<h2>API for AppleScript</h2>
<p>Some specifications for scripting support have been updated on CotEditor 2.0. From this, some user scripts may not run correctly on 2.0 without modifying. See “<a href="script_osascript.html">Create AppleScript</a>” for details of this specification change.</p>
<p>Some specifications for scripting support have been updated on CotEditor 2.0. From this, some user scripts may not run correctly on 2.0 without modifying. See “<a href="script_osascript.html">Script CotEditor with AppleScript</a>” for details of this specification change.</p>
<h2>Bundle Identifier</h2>
@ -44,9 +44,9 @@ Validate your customized syntax styles in syntax style editor and follow the mes
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="whats_new_in_2.0.html">Whats New in CotEditor 2.0</a></li>
<li><a href="whats_new_in_2.0.html">Whats new in CotEditor 2.0?</a></li>
<li><a href="specification_changes_on_2.2.html">Important changes on CotEditor 2.2</a></li>
<li><a href="releasenotes.html">Release Notes</a></li>
<li><a href="releasenotes.html">Release notes</a></li>
</ul>
</section>

View File

@ -31,7 +31,7 @@
<h2>See also</h2>
<ul>
<li><a href="whats_new_in_2.2.html">What's New in CotEditor 2.2</a></li>
<li><a href="releasenotes.html">Release Notes</a></li>
<li><a href="releasenotes.html">Release notes</a></li>
</ul>
</section>

View File

@ -53,8 +53,8 @@
<li><a href="howto_find_newline.html">Find or replace a line ending</a></li>
<li><a href="howto_find_inconsistent_line_endings.html">Find inconsistent line endings</a></li>
<li><a href="howto_paste.html">Paste text</a></li>
<li><a href="whats_new_in_4.2.html">Whats New in CotEditor 4.2</a></li>
<li><a href="releasenotes.html">Release Notes</a></li>
<li><a href="whats_new_in_4.2.html">Whats new in CotEditor 4.2?</a></li>
<li><a href="releasenotes.html">Release notes</a></li>
</section>

View File

@ -4,23 +4,22 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="comment, comment-out, uncomment"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Define comment delimiters</title>
<title>Define comment delimiters in CotEditor</title>
</head>
<body>
<a name="syntax_comment_settings"></a>
<h1>Define comment delimiters in CotEditor</h1>
<h1>Define comment delimiters</h1>
<p>The settings for comment that are used for both comment-out/uncomment and comment highlighting are as follows:</p>
<p>The settings for comments that are used for both comment-out/uncomment and comment highlighting are as follows:</p>
<table>
<thead>
<tr><th>Field</th><th>Description</th></tr>
</thead>
<tbody>
<tr><th>inline comment</th><td>The string here is used as inline comment delimiter on comment-out/uncomment. If this field is empty, the values in block comment is used in favor.</td></tr>
<tr><th>inline comment</th><td>The string here is used as the inline comment delimiter on comment-out/uncomment. If this field is empty, the value in the block comment is used in favor.</td></tr>
<tr><th>block comment</th><td>The strings here are used as block comment delimiters. These delimiters are used on uncommenting block comments and comment-outing if no inline comment delimiter is defined. You need to fill both ”begin with” and ”end with”.</td></tr>
</tbody>
</table>

View File

@ -4,14 +4,13 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="Word Completion, completion, completion list, possible completions"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Define completion candidates</title>
<title>Define completion candidates in CotEditor</title>
</head>
<body>
<a name="syntax_completion_settings"></a>
<h1>Define completion candidates</h1>
<h1>Define completion candidates in CotEditor</h1>
<p>You can create your own completion list by customizing the corresponding syntax style. After choosing a style and clicking Edit (see <a href="syntax_definition.html">Define a syntax style</a>), select Completion List from the menu.</p>
@ -24,13 +23,13 @@
</tbody>
</table>
<p>If no words here, the words generated by your syntax coloring rule will appear in the list.</p>
<p>If no words here, the words generated from your syntax coloring definition will appear in the list.</p>
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="howto_complete.html">Complete words</a></li>
<li><a href="howto_complete.html">Complete a word</a></li>
<li><a href="howto_customize_complete.html">Change the scope of completion words</a></li>
</ul>
</section>

View File

@ -4,12 +4,12 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="syntax coloring, syntax style, Outline, possible completions"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Define a syntax style</title>
<title>Define a syntax style in CotEditor</title>
</head>
<body>
<h1>Define a syntax style</h1>
<h1>Define a syntax style in CotEditor</h1>
<p>CotEditors syntax styles control syntax coloring, Outline, and the completion list, all together. To customize styles:</p>
<ol>

View File

@ -4,18 +4,17 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="syntax style, file mapping, extension, shebang, interpreter"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Map files to syntax styles</title>
<title>Map files to syntax styles in CotEditor</title>
</head>
<body>
<a name="syntax_file_mapping"></a>
<h1>Map files to syntax styles</h1>
<h1>Map files to syntax styles in CotEditor</h1>
<p>When opening a file, CotEditor detects the document type and applies the corresponding syntax style automatically.</p>
<p>The File Mapping definitions in each syntax style are used for this detection.</p>
<p>The File Mapping definitions in each syntax style are used for this detection.</p>
<h2>Priority order of file mapping</h2>
@ -39,15 +38,15 @@
<li>e.g.: <code>#!/usr/bin/env python3</code> → Python (interpreter: <code>python3</code>)</li>
</ul></li>
<li>XML declaration<ul>
<li>When there is no corresponding syntax style up to here but the file content starts with a XML declaration, syntax style is automatically set to “XML”.</li>
<li>When there is no corresponding syntax style up to here but the file content starts with an XML declaration, syntax style is automatically set to “XML”.</li>
<li>e.g.: <code>&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;</code> → XML</li>
</ul></li>
<li>None<ul>
<li>If no appropriate style can be found at all, “None” syntax style would be set.</li>
<li>If no appropriate style can be found at all, the “None” syntax style would be set.</li>
</ul></li>
</ol>
<p>When there are multiple syntax styles in the same level like the filename extension level or the filename level, custom styles are prioritized than the bundled styles. And yet, if there are multiple corresponding styles, the first found style will be applied automatically.</p>
<p>When there are multiple syntax styles in the same level like the filename extension level or the filename level, custom styles are prioritized over the bundled styles. And yet, if there are multiple corresponding styles, the first found style will be applied automatically.</p>
<h2>File mapping conflicts</h2>

View File

@ -4,14 +4,13 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="syntax style"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Define syntax highlighting</title>
<title>Define syntax highlighting in CotEditor</title>
</head>
<body>
<a name="syntax_highlight_settings"></a>
<h1>Define syntax highlighting</h1>
<h1>Define syntax highlighting in CotEditor</h1>
<h2>Types of syntax highlighting</h2>
@ -65,7 +64,7 @@
</tbody>
</table>
<p>CotEditor colors the code elements in the following order: 1) keywords, 2) commands, 3) types, 4) attributes, 5) variables, 6) values, 7) numbers, 8) strings, 9) characters, 10) comments. When your document contains an item to be colored which matches multiple categories (e.g. keywords and commands), the color of the latter in the order will overwrite the formers.</p>
<p>CotEditor colors the code elements in the following order: 1) keywords, 2) commands, 3) types, 4) attributes, 5) variables, 6) values, 7) numbers, 8) strings, 9) characters, 10) comments. When your document contains an item to be colored that matches multiple categories (for example, keywords and commands), the color of the latter in the order will overwrite the formers.</p>
@ -78,18 +77,18 @@
<tr><th>Field</th><th>Description</th></tr>
</thead>
<tbody>
<tr><th>RE</th><td>If this option is selected, both Begin-string and End-string will be considered as regular expressions (RE stands for Regular Expression).</td></tr>
<tr><th>IC</th><td>If this option is selected, case will be ignored during the search (IC stands for Ignore Case). For example, if you set “abc” as Begin-string and check IC, “ABC” or “abc” or “Abc” in your document will be matched.</td></tr>
<tr><th>Begin String</th><td>A string which denotes the beginning of the search pattern. This is required to search the code elements you want to be colored.</td></tr>
<tr><th>End String</th><td>A string which denotes the end of the search pattern. This can be left blank.</td></tr>
<tr><th>Description</th><td>You can use this field to leave a comment about the term. Description doesnt affect to syntax highlighitng. This can be left blank.</td></tr>
<tr><th>RE</th><td>If this option is selected, both Begin-string and End-string will be considered regular expressions (RE stands for Regular Expression).</td></tr>
<tr><th>IC</th><td>If this option is selected, the case will be ignored during the search (IC stands for Ignore Case). For example, if you set “abc” as Begin-string and check IC, “ABC” or “abc” or “Abc” in your document will be matched.</td></tr>
<tr><th>Begin String</th><td>A string that denotes the beginning of the search pattern. This is required to search the code elements you want to be colored.</td></tr>
<tr><th>End String</th><td>A string that denotes the end of the search pattern. This field can be left blank.</td></tr>
<tr><th>Description</th><td>You can use this field to leave a comment about the term. Description doesnt affect syntax highlighting. This field can be left blank.</td></tr>
</tbody>
</table>
<ul>
<li>A definition whose Begin-string is blank will be ignored.</li>
<li>A definition whose End-string is blank and RE is turned off will be used for defining the completion list as well.</li>
<li>The RE setting affects both Begin-string and End-string, which means they should be written in regular expression or plain form both together.</li>
<li>The RE setting affects both Begin-string and End-string, which means they should be written in the regular expression or plain form both together.</li>
</ul>

View File

@ -4,16 +4,15 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="syntax style, metadata"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Fill syntax style information</title>
<title>Fill syntax style information in CotEditor</title>
</head>
<body>
<a name="syntax_metadata_settings"></a>
<h1>Fill syntax style information in CotEditor</h1>
<h1>Fill syntax style information</h1>
<p>The metadata of syntax style file can be set as follows:</p>
<p>The metadata of a syntax style file can be set as follows:</p>
<table>
<thead>
@ -21,15 +20,15 @@
</thead>
<tbody>
<tr><th>Version</th><td>The version of the syntax style.</td></tr>
<tr><th>Last modified</th><td>The last modified date of the syntax style. We recommend to use the format <code>YYYY-MM-DD</code>.</td></tr>
<tr><th>Last modified</th><td>The last modified date of the syntax style. We recommend using the format <code>YYYY-MM-DD</code>.</td></tr>
<tr><th>Distribution URL</th><td>The URL of a web page in which the syntax style is distributed.</td></tr>
<tr><th>Author</th><td>The author of the syntax style.</td></tr>
<tr><th>License</th><td>The license of the syntax style.</td></tr>
<tr><th>Description</th><td>The additional information of the syntax style.</td></tr>
<tr><th>Description</th><td>The additional information on the syntax style.</td></tr>
</tbody>
</table>
<p>These infos might be useful if you want to share your own syntax style. You can leave fields also empty.</p>
<p>This information might be useful if you want to share your own syntax style. You can leave fields also empty.</p>
<section id="cf">

View File

@ -4,14 +4,13 @@
<meta charset="UTF-8"/>
<meta name="keywords" content="Outline"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Define Outline extraction rules</title>
<title>Define Outline extraction rules in CotEditor</title>
</head>
<body>
<a name="syntax_outline_settings"></a>
<h1>Define Outline extraction rules</h1>
<h1>Define Outline extraction rules in CotEditor</h1>
<p>The options for the Outline settings are as follows:</p>

View File

@ -2,14 +2,15 @@
<head>
<meta charset="UTF-8"/>
<meta name="robots" content="noindex"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>Whats New in CotEditor 2.0</title>
<title>Whats new in CotEditor 2.0?</title>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
</head>
<body>
<h1>Whats New in CotEditor 2.0</h1>
<h1>Whats new in CotEditor 2.0?</h1>
<dl>
<dt>Coloring theme feature</dt>
@ -49,7 +50,8 @@
<h2>See also</h2>
<ul>
<li><a href="specification_changes.html">Important changes on CotEditor 2.0</a></li>
<li><a href="releasenotes.html">Release Notes</a></li>
<li><a href="releasenotes.html">Release notes</a></li>
<li><a href="whats_new_in_2.1.html">Whats new in CotEditor 2.1?</a></li>
</ul>
</section>

View File

@ -2,14 +2,15 @@
<head>
<meta charset="UTF-8"/>
<meta name="robots" content="noindex"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>Whats New in CotEditor 2.1</title>
<title>Whats new in CotEditor 2.1?</title>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
</head>
<body>
<h1>Whats New in CotEditor 2.1</h1>
<h1>Whats new in CotEditor 2.1?</h1>
<dl>
<dt>Auto-Backup</dt>
@ -35,7 +36,9 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="releasenotes.html">Release Notes</a></li>
<li><a href="releasenotes.html">Release notes</a></li>
<li><a href="whats_new_in_2.0.html">Whats new in CotEditor 2.0?</a></li>
<li><a href="whats_new_in_2.2.html">Whats new in CotEditor 2.2?</a></li>
</ul>
</section>

View File

@ -2,14 +2,15 @@
<head>
<meta charset="UTF-8"/>
<meta name="robots" content="noindex"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>Whats New in CotEditor 2.2</title>
<title>Whats new in CotEditor 2.2?</title>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
</head>
<body>
<h1>Whats New in CotEditor 2.2</h1>
<h1>Whats new in CotEditor 2.2?</h1>
<dl>
<dt>Available in the Mac App Store</dt>
@ -36,7 +37,9 @@
<h2>See also</h2>
<ul>
<li><a href="specification_changes_on_2.2.html">Important changes on CotEditor 2.2</a></li>
<li><a href="releasenotes.html">Release Notes</a></li>
<li><a href="releasenotes.html">Release notes</a></li>
<li><a href="whats_new_in_2.1.html">Whats new in CotEditor 2.1?</a></li>
<li><a href="whats_new_in_2.3.html">Whats new in CotEditor 2.3?</a></li>
</ul>
</section>

View File

@ -2,14 +2,15 @@
<head>
<meta charset="UTF-8"/>
<meta name="robots" content="noindex"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>Whats New in CotEditor 2.3</title>
<title>Whats new in CotEditor 2.3?</title>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
</head>
<body>
<h1>Whats New in CotEditor 2.3</h1>
<h1>Whats new in CotEditor 2.3?</h1>
<dl>
<dt>Auto Save and Versions</dt>
@ -26,7 +27,9 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="releasenotes.html">Release Notes</a></li>
<li><a href="releasenotes.html">Release notes</a></li>
<li><a href="whats_new_in_2.2.html">Whats new in CotEditor 2.2?</a></li>
<li><a href="whats_new_in_2.4.html">Whats new in CotEditor 2.4?</a></li>
</ul>
</section>

View File

@ -2,14 +2,15 @@
<head>
<meta charset="UTF-8"/>
<meta name="robots" content="noindex"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>Whats New in CotEditor 2.4</title>
<title>Whats new in CotEditor 2.4?</title>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
</head>
<body>
<h1>Whats New in CotEditor 2.4</h1>
<h1>Whats new in CotEditor 2.4?</h1>
<dl>
<dt>Improve text finder</dt>
@ -29,7 +30,9 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="releasenotes.html">Release Notes</a></li>
<li><a href="releasenotes.html">Release notes</a></li>
<li><a href="whats_new_in_2.3.html">Whats new in CotEditor 2.3?</a></li>
<li><a href="whats_new_in_2.5.html">Whats new in CotEditor 2.5?</a></li>
</ul>
</section>

View File

@ -2,14 +2,15 @@
<head>
<meta charset="UTF-8"/>
<meta name="robots" content="noindex"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>Whats New in CotEditor 2.5</title>
<title>Whats new in CotEditor 2.5?</title>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
</head>
<body>
<h1>Whats New in CotEditor 2.5</h1>
<h1>Whats new in CotEditor 2.5?</h1>
<dl>
<dt>New “Unicode (UTF-8) with BOM” encoding</dt>
@ -26,7 +27,9 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="releasenotes.html">Release Notes</a></li>
<li><a href="releasenotes.html">Release notes</a></li>
<li><a href="whats_new_in_2.4.html">Whats new in CotEditor 2.4?</a></li>
<li><a href="whats_new_in_3.0.html">Whats new in CotEditor 3.0?</a></li>
</ul>
</section>

View File

@ -2,14 +2,15 @@
<head>
<meta charset="UTF-8"/>
<meta name="robots" content="noindex"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>Whats New in CotEditor 3.0</title>
<title>Whats new in CotEditor 3.0?</title>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
</head>
<body>
<h1>Whats New in CotEditor 3.0</h1>
<h1>Whats new in CotEditor 3.0?</h1>
<dl>
<dt>Swift migration</dt>
@ -32,7 +33,9 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="releasenotes.html">Release Notes</a></li>
<li><a href="releasenotes.html">Release notes</a></li>
<li><a href="whats_new_in_2.5.html">Whats new in CotEditor 2.5?</a></li>
<li><a href="whats_new_in_3.1.html">Whats new in CotEditor 3.1?</a></li>
</ul>
</section>

View File

@ -2,14 +2,15 @@
<head>
<meta charset="UTF-8"/>
<meta name="robots" content="noindex"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>Whats New in CotEditor 3.1</title>
<title>Whats new in CotEditor 3.1?</title>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
</head>
<body>
<h1>Whats New in CotEditor 3.1</h1>
<h1>Whats new in CotEditor 3.1?</h1>
<dl>
<dt>Touch Bar support</dt>
@ -23,7 +24,9 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="releasenotes.html">Release Notes</a></li>
<li><a href="releasenotes.html">Release notes</a></li>
<li><a href="whats_new_in_3.0.html">Whats new in CotEditor 3.0?</a></li>
<li><a href="whats_new_in_3.2.html">Whats new in CotEditor 3.2?</a></li>
</ul>
</section>

View File

@ -2,14 +2,15 @@
<head>
<meta charset="UTF-8"/>
<meta name="robots" content="noindex"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>Whats New in CotEditor 3.2</title>
<title>Whats new in CotEditor 3.2?</title>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
</head>
<body>
<h1>Whats New in CotEditor 3.2</h1>
<h1>Whats new in CotEditor 3.2?</h1>
<dl>
<dt>File Drop feature improvements</dt>
@ -29,7 +30,9 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="releasenotes.html">Release Notes</a></li>
<li><a href="releasenotes.html">Release notes</a></li>
<li><a href="whats_new_in_3.1.html">Whats new in CotEditor 3.1?</a></li>
<li><a href="whats_new_in_3.3.html">Whats new in CotEditor 3.3?</a></li>
</ul>
</section>

View File

@ -2,15 +2,15 @@
<head>
<meta charset="UTF-8"/>
<meta name="robots" content="noindex"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>Whats New in CotEditor 3.3</title>
<title>Whats new in CotEditor 3.3?</title>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
</head>
<body>
<h1>Whats New in CotEditor 3.3</h1>
<h1>Whats new in CotEditor 3.3?</h1>
<dl>
<dt>Handle documents on launch in more intelligent way</dt>
@ -36,7 +36,9 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="releasenotes.html">Release Notes</a></li>
<li><a href="releasenotes.html">Release notes</a></li>
<li><a href="whats_new_in_3.2.html">Whats new in CotEditor 3.2?</a></li>
<li><a href="whats_new_in_3.4.html">Whats new in CotEditor 3.4?</a></li>
</ul>
</section>

View File

@ -2,15 +2,15 @@
<head>
<meta charset="UTF-8"/>
<meta name="robots" content="noindex"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>Whats New in CotEditor 3.4</title>
<title>Whats new in CotEditor 3.4?</title>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
</head>
<body>
<h1>Whats New in CotEditor 3.4</h1>
<h1>Whats new in CotEditor 3.4?</h1>
<dl>
<dt>Apply multiple replacement rules at once</dt>
@ -27,7 +27,9 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="releasenotes.html">Release Notes</a></li>
<li><a href="releasenotes.html">Release notes</a></li>
<li><a href="whats_new_in_3.3.html">Whats new in CotEditor 3.3?</a></li>
<li><a href="whats_new_in_3.5.html">Whats new in CotEditor 3.5?</a></li>
</ul>
</section>

View File

@ -2,15 +2,15 @@
<head>
<meta charset="UTF-8"/>
<meta name="robots" content="noindex"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>Whats New in CotEditor 3.5</title>
<title>Whats new in CotEditor 3.5?</title>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
</head>
<body>
<h1>Whats New in CotEditor 3.5</h1>
<h1>Whats new in CotEditor 3.5?</h1>
<dl>
<dt>Brand-new toolbar</dt>
@ -30,7 +30,9 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="releasenotes.html">Release Notes</a></li>
<li><a href="releasenotes.html">Release notes</a></li>
<li><a href="whats_new_in_3.4.html">Whats new in CotEditor 3.4?</a></li>
<li><a href="whats_new_in_3.6.html">Whats new in CotEditor 3.6?</a></li>
</ul>
</section>

View File

@ -2,15 +2,15 @@
<head>
<meta charset="UTF-8"/>
<meta name="robots" content="noindex"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>Whats New in CotEditor 3.6</title>
<title>Whats new in CotEditor 3.6?</title>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
</head>
<body>
<h1>Whats New in CotEditor 3.6</h1>
<h1>Whats new in CotEditor 3.6?</h1>
<dl>
<dt>Dark Mode</dt>
@ -24,7 +24,9 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="releasenotes.html">Release Notes</a></li>
<li><a href="releasenotes.html">Release notes</a></li>
<li><a href="whats_new_in_3.5.html">Whats new in CotEditor 3.5?</a></li>
<li><a href="whats_new_in_3.7.html">Whats new in CotEditor 3.7?</a></li>
</ul>
</section>

View File

@ -2,15 +2,15 @@
<head>
<meta charset="UTF-8"/>
<meta name="robots" content="noindex"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>Whats New in CotEditor 3.7</title>
<title>Whats new in CotEditor 3.7?</title>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
</head>
<body>
<h1>Whats New in CotEditor 3.7</h1>
<h1>Whats new in CotEditor 3.7?</h1>
<dl>
<dt>Multi-Cursor editing</dt>
@ -21,7 +21,9 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="releasenotes.html">Release Notes</a></li>
<li><a href="releasenotes.html">Release notes</a></li>
<li><a href="whats_new_in_3.6.html">Whats new in CotEditor 3.6?</a></li>
<li><a href="whats_new_in_3.8.html">Whats new in CotEditor 3.8?</a></li>
</ul>
</section>

View File

@ -2,15 +2,15 @@
<head>
<meta charset="UTF-8"/>
<meta name="robots" content="noindex"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>Whats New in CotEditor 3.8</title>
<title>Whats new in CotEditor 3.8?</title>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
</head>
<body>
<h1>Whats New in CotEditor 3.8</h1>
<h1>Whats new in CotEditor 3.8?</h1>
<dl>
<dt>Improve Dark Mode compatibility</dt>
@ -24,7 +24,9 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="releasenotes.html">Release Notes</a></li>
<li><a href="releasenotes.html">Release notes</a></li>
<li><a href="whats_new_in_3.7.html">Whats new in CotEditor 3.7?</a></li>
<li><a href="whats_new_in_3.9.html">Whats new in CotEditor 3.9?</a></li>
</ul>
</section>

View File

@ -2,15 +2,15 @@
<head>
<meta charset="UTF-8"/>
<meta name="robots" content="noindex"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>Whats New in CotEditor 3.9</title>
<title>Whats new in CotEditor 3.9?</title>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
</head>
<body>
<h1>Whats New in CotEditor 3.9</h1>
<h1>Whats new in CotEditor 3.9?</h1>
<dl>
<dt>Invisible characters with more accuracy</dt>
@ -27,7 +27,9 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="releasenotes.html">Release Notes</a></li>
<li><a href="releasenotes.html">Release notes</a></li>
<li><a href="whats_new_in_3.8.html">Whats new in CotEditor 3.8?</a></li>
<li><a href="whats_new_in_4.0.html">Whats new in CotEditor 4.0?</a></li>
</ul>
</section>

View File

@ -2,15 +2,15 @@
<head>
<meta charset="UTF-8"/>
<meta name="robots" content="noindex"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>Whats New in CotEditor 4.0</title>
<title>Whats new in CotEditor 4.0?</title>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
</head>
<body>
<h1>Whats New in CotEditor 4.0</h1>
<h1>Whats new in CotEditor 4.0?</h1>
<dl>
<dt>Brand-new user interface for the Big Sur era</dt>
@ -24,7 +24,9 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="releasenotes.html">Release Notes</a></li>
<li><a href="releasenotes.html">Release notes</a></li>
<li><a href="whats_new_in_3.9.html">Whats new in CotEditor 3.9?</a></li>
<li><a href="whats_new_in_4.1.html">Whats new in CotEditor 4.1?</a></li>
</ul>
</section>

View File

@ -2,13 +2,15 @@
<head>
<meta charset="UTF-8"/>
<meta name="robots" content="noindex"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>Whats New in CotEditor 4.1</title>
<title>Whats new in CotEditor 4.1?</title>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
</head>
<body>
<h1>Whats New in CotEditor 4.1</h1>
<h1>Whats new in CotEditor 4.1?</h1>
<dl>
<dt>More comfort in your daily language</dt>
@ -28,7 +30,9 @@
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="releasenotes.html">Release Notes</a></li>
<li><a href="releasenotes.html">Release notes</a></li>
<li><a href="whats_new_in_4.0.html">Whats new in CotEditor 4.0?</a></li>
<li><a href="whats_new_in_4.2.html">Whats new in CotEditor 4.2?</a></li>
</ul>
</section>

View File

@ -3,21 +3,20 @@
<head>
<meta charset="UTF-8"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>Whats New in CotEditor 4.2</title>
<title>Whats new in CotEditor 4.2?</title>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
</head>
<body>
<a name="whats_new"></a>
<h1>Whats New in CotEditor 4.2</h1>
<h1>Whats new in CotEditor 4.2?</h1>
<dl>
<dt>Treat line endings with every courtesy</dt>
<dd>Now, CotEditor can handle documents with multiple types of line endings in the true sense. When line endings are inconsistent in a document, CotEditor lets you know and marks them where they are.</dd>
<dt>Printing where you need</dt>
<dt>Print where you need</dt>
<dd>The print dialog got the option Selection to the Pages section. It enables printing only the selected text in the document.</dd>
<dt>Work among multiple machines</dt>
@ -29,7 +28,8 @@
<h2>See also</h2>
<ul>
<li><a href="specification_changes_on_4.2.html">Important changes on CotEditor 4.2</a></li>
<li><a href="releasenotes.html">Release Notes</a></li>
<li><a href="releasenotes.html">Release notes</a></li>
<li><a href="whats_new_in_4.1.html">Whats new in CotEditor 4.1?</a></li>
</ul>
</section>

Some files were not shown because too many files have changed in this diff Show More