Improve UI text

according to Apple Style Guide
This commit is contained in:
1024jp 2022-04-04 19:58:34 +09:00
parent 843c082910
commit 91ee735cce
186 changed files with 517 additions and 518 deletions

View File

@ -8,10 +8,10 @@ Change Log
### New Features
- Ability to handle documents holding multiple types of line endings.
- Add an option Selection to the Pages section in the Print dialog to print only the selected text in the document.
- Add an option Selection to the Pages section in the Print dialog to print only the selected text in the document.
- Unicode line endings, namely NEL (New Line), LS (Line Separator), and PS (Paragraph Separator), are added to the line endings options (These items are visible only either when pressing the Option key or when the line endings of the opened document are one of these).
- Add recent history to the Unicode input.
- Export setting files, such as themes or multiple replacements, to Finder just by dragging and dropping the setting name.
- Export setting files, such as themes or multiple replacements, to the Finder just by dragging and dropping the setting name.
- Transfer settings among CotEditors in different machines via Universal Control by dragging the setting name and dropping it to the setting list area in another CotEditor.
@ -26,11 +26,11 @@ Change Log
- Optimize syntax parsing.
- Deprecate the feature to replace `$LN` in the outline menu template with the line number of the occurrence.
- Prefer using .yml for syntax definition files over .yaml.
- Remove original document icons for CoffeeScript and Tcl.
- Remove original document icons for CoffeeScript and Tcl.
- Make text in the UI more Apple-favored.
- Update help contents.
- [trivial] Accept script files for the Script menu with an uppercased file extension.
- [trivial] Replace `\n` with `\R` for the new line meta character in the regular expression reference.
- [trivial] Rename the feature Outline Menu to Outline.
- [trivial] Tweak Anura theme.

View File

@ -32,7 +32,7 @@ If your localization makes the Autolayout destroy, try first making the sentence
#### Good references for localization
By localization, use macOS standard terms. It might be helpful to study native Apple applications like TextEdit.app or the System Preferences to know how Apple localizes terms in their apps.
By localization, use macOS standard terms. It might be helpful to study native Apple applications like TextEdit.app or System Preferences to know how Apple localizes terms in their apps.
Especially, follow the terms of the following applications.

View File

@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<document type="com.apple.InterfaceBuilder3.Cocoa.Storyboard.XIB" version="3.0" toolsVersion="17503.1" targetRuntime="MacOSX.Cocoa" propertyAccessControl="none" useAutolayout="YES" initialViewController="ysq-gL-jur">
<document type="com.apple.InterfaceBuilder3.Cocoa.Storyboard.XIB" version="3.0" toolsVersion="20037" targetRuntime="MacOSX.Cocoa" propertyAccessControl="none" useAutolayout="YES" initialViewController="ysq-gL-jur">
<dependencies>
<deployment identifier="macosx"/>
<plugIn identifier="com.apple.InterfaceBuilder.CocoaPlugin" version="17503.1"/>
<plugIn identifier="com.apple.InterfaceBuilder.CocoaPlugin" version="20037"/>
<capability name="documents saved in the Xcode 8 format" minToolsVersion="8.0"/>
</dependencies>
<scenes>
@ -10,19 +10,19 @@
<scene sceneID="raX-r2-ejG">
<objects>
<viewController id="ysq-gL-jur" customClass="ColorCodePanelController" customModule="CotEditor" customModuleProvider="target" sceneMemberID="viewController">
<view key="view" id="c22-O7-iKe">
<rect key="frame" x="0.0" y="0.0" width="220" height="69"/>
<view key="view" misplaced="YES" id="c22-O7-iKe">
<rect key="frame" x="0.0" y="0.0" width="229" height="69"/>
<autoresizingMask key="autoresizingMask" flexibleMaxX="YES" flexibleMinY="YES"/>
<subviews>
<popUpButton verticalHuggingPriority="750" translatesAutoresizingMaskIntoConstraints="NO" id="5nu-Uj-uIv">
<rect key="frame" x="6" y="12" width="130" height="22"/>
<popUpButtonCell key="cell" type="push" title="Hex" bezelStyle="rounded" alignment="left" controlSize="small" lineBreakMode="truncatingTail" state="on" borderStyle="borderAndBezel" tag="1" imageScaling="proportionallyDown" inset="2" selectedItem="vF1-in-Dlv" id="E6C-h6-CQ2">
<rect key="frame" x="6" y="12" width="139" height="22"/>
<popUpButtonCell key="cell" type="push" title="Hexadecimal" bezelStyle="rounded" alignment="left" controlSize="small" lineBreakMode="truncatingTail" state="on" borderStyle="borderAndBezel" tag="1" imageScaling="proportionallyDown" inset="2" selectedItem="vF1-in-Dlv" id="E6C-h6-CQ2">
<behavior key="behavior" lightByBackground="YES" lightByGray="YES"/>
<font key="font" metaFont="menu" size="11"/>
<menu key="menu" id="C4D-sY-kfX">
<items>
<menuItem title="Hex" state="on" tag="1" id="vF1-in-Dlv"/>
<menuItem title="Hex (short)" tag="2" id="wEc-KD-y7s"/>
<menuItem title="Hexadecimal" state="on" tag="1" id="vF1-in-Dlv"/>
<menuItem title="Hexadecimal (short)" tag="2" id="wEc-KD-y7s"/>
<menuItem isSeparatorItem="YES" id="AxS-WW-dBr"/>
<menuItem title="CSS RGB" tag="3" id="6bH-jm-mNR"/>
<menuItem title="CSS RGBa" tag="4" id="cxo-sm-Sx5"/>
@ -38,7 +38,7 @@
</connections>
</popUpButton>
<button horizontalHuggingPriority="749" verticalHuggingPriority="750" horizontalCompressionResistancePriority="250" translatesAutoresizingMaskIntoConstraints="NO" id="JQf-sU-hcC">
<rect key="frame" x="134" y="9" width="82" height="27"/>
<rect key="frame" x="143" y="9" width="82" height="27"/>
<constraints>
<constraint firstAttribute="width" relation="greaterThanOrEqual" constant="70" id="dgW-gF-5K1"/>
</constraints>
@ -51,7 +51,7 @@
</connections>
</button>
<textField horizontalHuggingPriority="251" verticalHuggingPriority="750" translatesAutoresizingMaskIntoConstraints="NO" id="EOP-Td-d5F">
<rect key="frame" x="10" y="40" width="200" height="21"/>
<rect key="frame" x="10" y="40" width="209" height="21"/>
<textFieldCell key="cell" scrollable="YES" lineBreakMode="clipping" selectable="YES" editable="YES" borderStyle="bezel" alignment="center" title="#ffffff" drawsBackground="YES" id="MFc-gP-VZL">
<font key="font" size="14" name="Menlo-Regular"/>
<color key="textColor" name="controlTextColor" catalog="System" colorSpace="catalog"/>

View File

@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<document type="com.apple.InterfaceBuilder3.Cocoa.Storyboard.XIB" version="3.0" toolsVersion="19529" targetRuntime="MacOSX.Cocoa" propertyAccessControl="none" useAutolayout="YES" initialViewController="pyW-Gr-FLf">
<document type="com.apple.InterfaceBuilder3.Cocoa.Storyboard.XIB" version="3.0" toolsVersion="20037" targetRuntime="MacOSX.Cocoa" propertyAccessControl="none" useAutolayout="YES" initialViewController="pyW-Gr-FLf">
<dependencies>
<deployment identifier="macosx"/>
<plugIn identifier="com.apple.InterfaceBuilder.CocoaPlugin" version="19529"/>
<plugIn identifier="com.apple.InterfaceBuilder.CocoaPlugin" version="20037"/>
<capability name="documents saved in the Xcode 8 format" minToolsVersion="8.0"/>
</dependencies>
<scenes>
@ -11,11 +11,11 @@
<objects>
<viewController id="pyW-Gr-FLf" customClass="CustomTabWidthViewController" customModule="CotEditor" customModuleProvider="target" sceneMemberID="viewController">
<view key="view" id="G7X-lO-X6e">
<rect key="frame" x="0.0" y="0.0" width="192" height="89"/>
<rect key="frame" x="0.0" y="0.0" width="180" height="89"/>
<autoresizingMask key="autoresizingMask"/>
<subviews>
<textField verticalHuggingPriority="750" translatesAutoresizingMaskIntoConstraints="NO" id="W3f-KG-c6f" customClass="NumberTextField" customModule="CotEditor" customModuleProvider="target">
<rect key="frame" x="108" y="48" width="64" height="21"/>
<rect key="frame" x="96" y="48" width="64" height="21"/>
<constraints>
<constraint firstAttribute="width" constant="64" id="aUs-0s-zHS"/>
</constraints>
@ -36,7 +36,7 @@
</connections>
</textField>
<textField horizontalHuggingPriority="750" verticalHuggingPriority="750" translatesAutoresizingMaskIntoConstraints="NO" id="sYB-kv-GmJ">
<rect key="frame" x="35" y="51" width="67" height="16"/>
<rect key="frame" x="23" y="51" width="67" height="16"/>
<textFieldCell key="cell" scrollable="YES" lineBreakMode="clipping" sendsActionOnEndEditing="YES" title="Tab width:" id="ql5-25-UDJ">
<font key="font" metaFont="system"/>
<color key="textColor" name="labelColor" catalog="System" colorSpace="catalog"/>
@ -44,7 +44,7 @@
</textFieldCell>
</textField>
<button verticalHuggingPriority="750" translatesAutoresizingMaskIntoConstraints="NO" id="892-mq-gWy">
<rect key="frame" x="25" y="13" width="78" height="32"/>
<rect key="frame" x="13" y="13" width="78" height="32"/>
<buttonCell key="cell" type="push" title="Cancel" bezelStyle="rounded" alignment="center" borderStyle="border" imageScaling="proportionallyDown" inset="2" id="bJM-c0-iOi">
<behavior key="behavior" pushIn="YES" lightByBackground="YES" lightByGray="YES"/>
<font key="font" metaFont="system"/>
@ -57,7 +57,7 @@ Gw
</connections>
</button>
<button verticalHuggingPriority="750" translatesAutoresizingMaskIntoConstraints="NO" id="nhc-Zt-Uwr">
<rect key="frame" x="101" y="13" width="78" height="32"/>
<rect key="frame" x="89" y="13" width="78" height="32"/>
<constraints>
<constraint firstAttribute="width" relation="greaterThanOrEqual" constant="64" id="uOy-uv-pR0"/>
</constraints>
@ -94,7 +94,7 @@ DQ
</viewController>
<customObject id="pOl-Sh-bBN" userLabel="First Responder" customClass="NSResponder" sceneMemberID="firstResponder"/>
</objects>
<point key="canvasLocation" x="647.5" y="169.5"/>
<point key="canvasLocation" x="634.5" y="169.5"/>
</scene>
</scenes>
</document>

View File

@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<document type="com.apple.InterfaceBuilder3.Cocoa.Storyboard.XIB" version="3.0" toolsVersion="19529" targetRuntime="MacOSX.Cocoa" propertyAccessControl="none" useAutolayout="YES" initialViewController="UtY-fi-jOg">
<document type="com.apple.InterfaceBuilder3.Cocoa.Storyboard.XIB" version="3.0" toolsVersion="20037" targetRuntime="MacOSX.Cocoa" propertyAccessControl="none" useAutolayout="YES" initialViewController="UtY-fi-jOg">
<dependencies>
<deployment identifier="macosx"/>
<plugIn identifier="com.apple.InterfaceBuilder.CocoaPlugin" version="19529"/>
<plugIn identifier="com.apple.InterfaceBuilder.CocoaPlugin" version="20037"/>
<capability name="documents saved in the Xcode 8 format" minToolsVersion="8.0"/>
</dependencies>
<scenes>
@ -111,7 +111,7 @@
<color key="backgroundColor" name="controlBackgroundColor" catalog="System" colorSpace="catalog"/>
<color key="gridColor" name="gridColor" catalog="System" colorSpace="catalog"/>
<tableColumns>
<tableColumn identifier="extensions" width="173.5" minWidth="40" maxWidth="1000" headerToolTip="File extensions of dropped file (comma separated)." id="FAF-cL-AAk">
<tableColumn identifier="extensions" width="173.5" minWidth="40" maxWidth="1000" headerToolTip="Filename extensions of dropped file (comma separated)." id="FAF-cL-AAk">
<tableHeaderCell key="headerCell" lineBreakMode="truncatingTail" borderStyle="border" alignment="left" title="Extensions">
<color key="textColor" name="headerTextColor" catalog="System" colorSpace="catalog"/>
<color key="backgroundColor" white="0.33333299" alpha="1" colorSpace="calibratedWhite"/>
@ -164,7 +164,7 @@
<tableColumnResizingMask key="resizingMask" resizeWithTable="YES" userResizable="YES"/>
<prototypeCellViews>
<tableCellView id="Nke-jc-fMr">
<rect key="frame" x="182.5" y="1" width="153" height="17"/>
<rect key="frame" x="183" y="1" width="153" height="17"/>
<autoresizingMask key="autoresizingMask" widthSizable="YES" heightSizable="YES"/>
<subviews>
<popUpButton id="IBU-1D-WII">

View File

@ -1,7 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<document type="com.apple.InterfaceBuilder3.Cocoa.Storyboard.XIB" version="3.0" toolsVersion="18122" targetRuntime="MacOSX.Cocoa" propertyAccessControl="none" useAutolayout="YES" initialViewController="JG1-NR-KT5">
<document type="com.apple.InterfaceBuilder3.Cocoa.Storyboard.XIB" version="3.0" toolsVersion="20037" targetRuntime="MacOSX.Cocoa" propertyAccessControl="none" useAutolayout="YES" initialViewController="JG1-NR-KT5">
<dependencies>
<plugIn identifier="com.apple.InterfaceBuilder.CocoaPlugin" version="18122"/>
<deployment identifier="macosx"/>
<plugIn identifier="com.apple.InterfaceBuilder.CocoaPlugin" version="20037"/>
<capability name="documents saved in the Xcode 8 format" minToolsVersion="8.0"/>
</dependencies>
<scenes>
@ -89,7 +90,7 @@
<rect key="frame" x="166" y="386" width="386" height="42"/>
<textFieldCell key="cell" controlSize="small" sendsActionOnEndEditing="YES" id="sOa-Ea-zt9">
<font key="font" metaFont="smallSystem"/>
<string key="title">A system feature that automatically overwrites your files while editing. Even if it turned off, CotEditor creates backup covertly for unexpected crash.</string>
<string key="title">A system feature that automatically overwrites your files while editing. Even if it turned off, CotEditor creates backup covertly for unexpected quit.</string>
<color key="textColor" name="labelColor" catalog="System" colorSpace="catalog"/>
<color key="backgroundColor" name="textBackgroundColor" catalog="System" colorSpace="catalog"/>
</textFieldCell>

View File

@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<document type="com.apple.InterfaceBuilder3.Cocoa.Storyboard.XIB" version="3.0" toolsVersion="19529" targetRuntime="MacOSX.Cocoa" propertyAccessControl="none" useAutolayout="YES">
<document type="com.apple.InterfaceBuilder3.Cocoa.Storyboard.XIB" version="3.0" toolsVersion="20037" targetRuntime="MacOSX.Cocoa" propertyAccessControl="none" useAutolayout="YES">
<dependencies>
<deployment identifier="macosx"/>
<plugIn identifier="com.apple.InterfaceBuilder.CocoaPlugin" version="19529"/>
<plugIn identifier="com.apple.InterfaceBuilder.CocoaPlugin" version="20037"/>
</dependencies>
<scenes>
<!--Application-->
@ -390,7 +390,7 @@ Gw
<menu key="submenu" title="Syntax Style" id="304">
<items>
<menuItem isSeparatorItem="YES" id="kdb-Ik-s27"/>
<menuItem title="Re-Color All" keyEquivalent="r" id="458">
<menuItem title="Recolor All" keyEquivalent="r" id="458">
<modifierMask key="keyEquivalentModifierMask" option="YES" command="YES"/>
<connections>
<action selector="recolorAll:" target="Ady-hI-5gd" id="ma3-X0-tjk"/>

View File

@ -1,8 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
<document type="com.apple.InterfaceBuilder3.Cocoa.Storyboard.XIB" version="3.0" toolsVersion="19529" targetRuntime="MacOSX.Cocoa" propertyAccessControl="none" useAutolayout="YES" initialViewController="QqU-9e-YIW">
<document type="com.apple.InterfaceBuilder3.Cocoa.Storyboard.XIB" version="3.0" toolsVersion="20037" targetRuntime="MacOSX.Cocoa" propertyAccessControl="none" useAutolayout="YES" initialViewController="QqU-9e-YIW">
<dependencies>
<deployment identifier="macosx"/>
<plugIn identifier="com.apple.InterfaceBuilder.CocoaPlugin" version="19529"/>
<plugIn identifier="com.apple.InterfaceBuilder.CocoaPlugin" version="20037"/>
<capability name="NSView safe area layout guides" minToolsVersion="12.0"/>
<capability name="documents saved in the Xcode 8 format" minToolsVersion="8.0"/>
</dependencies>
@ -155,7 +155,7 @@
<tableColumnResizingMask key="resizingMask" resizeWithTable="YES" userResizable="YES"/>
<prototypeCellViews>
<tableCellView id="M9b-zX-U8A">
<rect key="frame" x="136" y="1" width="103" height="16"/>
<rect key="frame" x="135.5" y="1" width="103" height="16"/>
<autoresizingMask key="autoresizingMask" widthSizable="YES" heightSizable="YES"/>
<subviews>
<textField verticalHuggingPriority="750" horizontalCompressionResistancePriority="250" allowsCharacterPickerTouchBarItem="YES" translatesAutoresizingMaskIntoConstraints="NO" id="hXD-LW-TDg" customClass="RegexTextField" customModule="CotEditor" customModuleProvider="target">
@ -840,8 +840,8 @@
</textFieldCell>
</textField>
<button toolTip="Search ignores diacritic marks (ex. ö = o)." verticalHuggingPriority="750" translatesAutoresizingMaskIntoConstraints="NO" id="9pO-Jw-K7x">
<rect key="frame" x="19" y="149" width="135" height="16"/>
<buttonCell key="cell" type="check" title="Ignore diacritic marks" bezelStyle="regularSquare" imagePosition="left" controlSize="small" inset="2" id="WWu-mC-MCz">
<rect key="frame" x="19" y="149" width="144" height="16"/>
<buttonCell key="cell" type="check" title="Ignore diacritical marks" bezelStyle="regularSquare" imagePosition="left" controlSize="small" inset="2" id="WWu-mC-MCz">
<behavior key="behavior" changeContents="YES" doesNotDimImage="YES" lightByContents="YES"/>
<font key="font" metaFont="menu" size="11"/>
</buttonCell>

View File

@ -16,7 +16,7 @@
<h1>Working with AppleScript</h1>
<p>CotEditor supports AppleScript and JXA (JavaScript for Automation).</p>
<p>CotEditor works with AppleScript and JXA (JavaScript for Automation).</p>
<p>It has own AppleScript dictionary so that you can look up all the classes or commands available with CotEditor. To open the dictionary:</p>
@ -156,13 +156,13 @@
<h4>Discussion</h4>
<p>The <code>selection</code> property doesn't work by itself. Use this property with others such as <code>contents</code>.</p>
<p>The <code>selection</code> property doesnt work by itself. Use this property with others such as <code>contents</code>.</p>
<p>When location is a negative value, the selection range starts from the location-th last character.<br/>
When length is a positive value, the selection range becomes the length characters starting from location. If length is larger than the number of the rest characters in the document, the range will be from location to the end.<br/>
When length is a negative value, the selection range ends at the length-th last character. If the absolute value of length is smaller than location (i.e. the selection's end point is before location), the caret just moves to location (same as when {location, 0} was input).</p>
<p>This specifying method is modelled after that of PHP's <code>substr</code>.</p>
<p>The command for changing selection doesn't scroll the window. Use the <code>scroll to caret</code> command or <code>jump</code> command to make the selection remain in the view.</p>
When length is a negative value, the selection range ends at the length-th last character. If the absolute value of length is smaller than location (i.e. the selections end point is before location), the caret just moves to location (same as when {location, 0} was input).</p>
<p>This specifying method is modelled after that of PHPs <code>substr</code>.</p>
<p>The command for changing selection doesnt scroll the window. Use the <code>scroll to caret</code> command or <code>jump</code> command to make the selection remain in the view.</p>
</section>
</section>
@ -177,7 +177,7 @@ When length is a negative value, the selection range ends at the length
<dl class="tree">
<dt><code class="command">write to console</code></dt>
<dd>Display a string on CotEditor's console window.</dd>
<dd>Display a string on CotEditors console window.</dd>
<dd><dl>
<dt>target</dt>
<dd>document object</dd>
@ -191,7 +191,7 @@ When length is a negative value, the selection range ends at the length
<h4>Example</h4>
<figure>
<pre class="source"><code class="AppleScript">write to console &quot;Script failed.&quot;</code></pre>
<figcaption>Display the massege &quot;Script failed.&quot; on the CotEditor's console.</figcaption>
<figcaption>Display the massege &quot;Script failed.&quot; on the CotEditors console.</figcaption>
</figure>
</section>
@ -294,7 +294,7 @@ For example, when not using the <code>wrap</code> or <code>backwards</code> opti
<h4>Discussion</h4>
<p>As in the case of the <code>find</code> command, the search starts from the current selection (caret position). Use the <code>all</code> option for searching the whole document.</p>
<p>After replacing the whole document using the <code>all</code> option, the caret moves to the head of the document. If there were no matching string, the caret doesn't move.</p>
<p>After replacing the whole document using the <code>all</code> option, the caret moves to the head of the document. If there were no matching string, the caret doesnt move.</p>
<p>The regular expression search cannot search backwards. If both options were specified at the same time, the <code>backwards</code> option is ignored.</p>
</section>
@ -367,7 +367,7 @@ For example, when not using the <code>wrap</code> or <code>backwards</code> opti
<dd>The new encoding, either in localized encoding name or an IANA charset name.</dd>
<dt>[<code>lossy</code>] (boolean)</dt>
<dd>Whether to allow “lossy” conversion (might result in loss of character that couldn't be converted) or not.</dd>
<dd>Whether to allow “lossy” conversion (might result in loss of character that couldnt be converted) or not.</dd>
<dt>[<code>BOM</code>] (boolean)</dt>
<dd>Whether to add a BOM (byte order mark). <span class="added">(added on CotEditor 4.1)</span></dd>

View File

@ -48,7 +48,7 @@
<article>
<h2>Terminology change on CotEditor 3.5.0</h2>
<h3>editor's opacity</h3>
<h3>editors opacity</h3>
<p><code>view opacity</code> property was deprecated on CotEditor 3.5.0.</p>
<p>Please note that <strong>there is no backward compatibility</strong> with this changing.</p>
</article>
@ -159,14 +159,14 @@ This issue doesnt occur with plain-text AppleScript (.applescript). </p>
<h2>Terminology change on CotEditor 1.5.0</h2>
<section>
<h3>Window transparency</h3>
<p>According to the changing of the mechanism to make window transparent on CotEditor 1.5, the terms about window opacity for AppleScripting was also changed. The <b>document</b>'s properties till on version 1.4:</p>
<p>According to the changing of the mechanism to make window transparent on CotEditor 1.5, the terms about window opacity for AppleScripting was also changed. The <b>document</b>s properties till on version 1.4:</p>
<ul class="nostyle">
<li><code>transparency</code>: The transparency of Window or TextView. (real, from 0.2 to 1.0)</li>
<li><code>alpha only textView</code>: Whether the transparency setting affects only the TextView or not. (boolean)</li>
</ul>
<p>were deprecated, and the new <b>window</b>'s property:</p>
<p>were deprecated, and the new <b>window</b>s property:</p>
<ul class="nostyle">
<li><code>view opacity</code>: The opacity of the view. (real, from 0.2 to 1.0)</li>
@ -174,13 +174,13 @@ This issue doesnt occur with plain-text AppleScript (.applescript). </p>
<p>was added instead.</p>
<p>Since the previous term “transparency” was incorrectly used until version 1.4, the property name was renamed from “transparency” to “opacity” but the value to set is not changed. Namely, 1.0 means fully opaque on both properties.</p>
<p>Because the previous term “transparency” was incorrectly used until version 1.4, the property name was renamed from “transparency” to “opacity” but the value to set is not changed. Namely, 1.0 means fully opaque on both properties.</p>
<p>Please note that <strong>there is no backward compatibility</strong> with this changing.</p>
</section>
<section>
<h3>Selection Object direct under the Application</h3>
<p>In version 0.6, the initial release of CotEditor, if you didn't specify the selection object, the frontmost window's contents will be selected. But it was actually didn't work correctly and therefore deprecated. This method was kept valid however to maintain backwards compatibility.</p>
<p>In version 0.6, the initial release of CotEditor, if you didnt specify the selection object, the frontmost windows contents will be selected. But it was actually didnt work correctly and therefore deprecated. This method was kept valid however to maintain backwards compatibility.</p>
<p>On CotEditor 1.5, it is formally removed. Specify the target like below, when you get the selection object.</p>
<figure>

View File

@ -13,12 +13,12 @@
<h1>Using encoding declarations for encoding detection</h1>
<p>When “Refer to encoding declaration in document” is enabled 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 file's text encoding.</p>
<p>A declaration can be anywhere in the document, the one either in comment area or in a plain sentence is detected. When you want to use a phrase such as “charset=UTF-8” even though your document's encoding is not UTF-8, you need to put an actual encoding declaration prior to the phrase, or, turn off “Refer to encoding declaration in document” in the Format preferences.</p>
<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 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>
<ul>
<li>The scope to scan declarations is limited within 2,000 characters from the head of the document.</li>
<li>To make the detection of declarations work, you have to put an equal character (“=”, no other characters) right after “<code>charset</code>” or “<code>encoding</code>.”</li>
<li>To make the detection of declarations work, you have to put an equal sign (“=”, no other characters) right after “<code>charset</code>” or “<code>encoding</code>.”</li>
<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 />

View File

@ -15,7 +15,7 @@
<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</p>
<p>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 former's.</p>
<p>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>
</body>
</html>

View File

@ -30,7 +30,7 @@ ln -s /Applications/CotEditor.app/Contents/SharedSupport/bin/cot /usr/local/bin/
<h3>Installation of Python 3</h3>
<p>The cot command is implemented in Python 3. However, because Python has no longer been bundled into the system since macOS 12.3, users need to install <code>python3</code> manually for the cot command.</p>
<p>The developer tools provided by Apple include <code>python3</code>. Run the following line in Terminal to install Apple's Command Line Developer Tools. Obviously, any <code>python3</code> installed via other methods can be used as well.</p>
<p>The developer tools provided by Apple include <code>python3</code>. Run the following line in Terminal to install Apples Command Line Developer Tools. Obviously, any <code>python3</code> installed via other methods can be used as well.</p>
<pre class="source"><code>xcode-select --install</code></pre>

View File

@ -24,14 +24,14 @@
<p>CotEditor detects the corresponding syntax style in the following order:</p>
<ol>
<li>File extension<ul>
<li>Try determining syntax style from the file extension. The case is basically ignored; however, case-matched ones are prioritized if multiple syntax styles are found</li>
<li>Filename extension<ul>
<li>Try determining syntax style from the filename extension. The case is basically ignored; however, case-matched ones are prioritized if multiple syntax styles are found</li>
<li>e.g.: .html → HTML</li>
<li>e.g.: .hTmL → HTML</li>
<li>e.g.: .py → Python</li>
</ul></li>
<li>Filename<ul>
<li>When there is no syntax style in which the find file extension is defined or the filename doesn't have an extension, then try determining syntax style from the whole filename.</li>
<li>When there is no syntax style in which the find filename extension is defined or the filename doesnt have an extension, then try determining syntax style from the whole filename.</li>
<li>e.g.: .htaccess → Apache</li>
<li>e.g.: makefile → Makefile</li>
</ul></li>
@ -49,11 +49,11 @@
</ul></li>
</ol>
<p>When there are multiple syntax styles in the same level like the file extension level or the filename level, user 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 than 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>
<p>There are no conflicts among the bundled syntax styles. However, if the user added their custom styles or modified the bundled styles, file mapping can conflict. You can see the existence of mapping conflicts from the “Show File Mapping Conflict” menu item in the Format pane in the Preferences. If the menu item is gray-out, it means: there is no conflict.</p>
<p>There are no conflicts among the bundled syntax styles. However, if you added custom styles or modified the bundled styles, the file mapping can conflict. You can see the existence of mapping conflicts from the Show File Mapping Conflict command in the Format pane in the Preferences. If the menu item is gray-out, it means: there is no conflict.</p>
<p>You can just leave the file mapping conflicts as long as you can open files with your expected syntax style. There is no side issue.</p>

View File

@ -24,9 +24,9 @@
<tr><td><code>&lt;&lt;&lt;RELATIVE-PATH&gt;&gt;&gt;</code></td><td>The relative path from your document to the dropped file.</td></tr>
<tr><td><code>&lt;&lt;&lt;FILENAME&gt;&gt;&gt;</code></td><td>The name of the dropped file with extension.</td></tr>
<tr><td><code>&lt;&lt;&lt;FILENAME-NOSUFFIX&gt;&gt;&gt;</code></td><td>The name of the dropped file without extension.</td></tr>
<tr><td><code>&lt;&lt;&lt;FILEEXTENSION&gt;&gt;&gt;</code></td><td>The file extension of the dropped file.</td></tr>
<tr><td style="white-space: nowrap"><code>&lt;&lt;&lt;FILEEXTENSION-LOWER&gt;&gt;&gt;</code></td><td>The file extension of the dropped file (lowercase).</td></tr>
<tr><td style="white-space: nowrap"><code>&lt;&lt;&lt;FILEEXTENSION-UPPER&gt;&gt;&gt;</code></td><td>The file extension of the dropped file (uppercase).</td></tr>
<tr><td><code>&lt;&lt;&lt;FILEEXTENSION&gt;&gt;&gt;</code></td><td>The filename extension of the dropped file.</td></tr>
<tr><td style="white-space: nowrap"><code>&lt;&lt;&lt;FILEEXTENSION-LOWER&gt;&gt;&gt;</code></td><td>The filename extension of the dropped file (lowercase).</td></tr>
<tr><td style="white-space: nowrap"><code>&lt;&lt;&lt;FILEEXTENSION-UPPER&gt;&gt;&gt;</code></td><td>The filename extension of the dropped file (uppercase).</td></tr>
<tr><td><code>&lt;&lt;&lt;DIRECTORY&gt;&gt;&gt;</code></td><td>The directory of the dropped file.</td></tr>
<tr><td style="white-space: nowrap"><code>&lt;&lt;&lt;FILECONTENT&gt;&gt;&gt;</code></td><td>The text content of the dropped file (works only when you drop an text file).</td></tr>
<tr><td><code>&lt;&lt;&lt;IMAGEWIDTH&gt;&gt;&gt;</code></td><td>The image width (works only when you drop an image file).</td></tr>
@ -34,7 +34,7 @@
</tbody>
</table>
<p>Here are a few examples of what it's like to use variables.</p>
<p>Here are a few examples of what its like to use variables.</p>
<table>
<caption>example 1) When you drop foo.html:</caption>

View File

@ -15,8 +15,8 @@
<h1>Using Go to Line</h1>
<p>When you choose Go to Line in the Find menu, or press Command-L, CotEditor displays the Go To dialog box to give you quick access to the line(s) you want to see.</p>
<p>In the dialog box, enter the line number, and click Go.</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>
<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>

View File

@ -18,7 +18,7 @@
<p>The options for the Outline settings are as follows:</p>
<table>
<tr><th>Regular Expression String</th><td>The in-document strings matched by the regular expressions you set here will appear in the drop-down menu. This setting is required in order to search the items to be listed (RE stands for Regular Expression).</td></tr>
<tr><th>Regular Expression String</th><td>The in-document strings matched by the regular expressions you set here will appear in the drop-down menu. This setting is required to search the items to be listed (RE stands for Regular Expression).</td></tr>
<tr><th>IC</th><td>If this is selected, case will be ignored during the search. For example, the expression “abc” matches “ABC” or “abc” or “Abc” in your document (IC stands for Ignore Case).</td></tr>
<tr><th>Title Pattern</th><td>Here, you can format the titles of the Outline items. Both the “Regular Expression String” setting and the setting here determine how the corresponding item is titled in the list.</td></tr>
</table>
@ -34,7 +34,7 @@
</table>
<ul>
<li>To show a meta character such as “$0” in the menu, you need to put a backslash (&#x005C;) in front of it. You won't see that backslash (&#x005C;) in the menu.</li>
<li>To show a meta character such as “$0” in the menu, you need to put a backslash (&#x005C;) in front of it. You wont see that backslash (&#x005C;) in the menu.</li>
</ul>

View File

@ -18,11 +18,11 @@
<p>This page explains the rules for naming script files.</p>
<dl>
<dt>Order of appearance</dt>
<dd>By adding “number + closing parenthesis ())” at the head of the name, you can line up the files in numerical order.<br />
The part “number + )” won't be shown in the menu.
<dd>By adding “number + closing parenthesis ())” at the head of the name, you can line up the files in numeric order.<br />
The part “number + )” wont be shown in the menu.
<table>
<caption>example 1.</caption>
<tr><th>File name</th><td><strong>01)</strong>Open File.scpt</td></tr>
<tr><th>Filename</th><td><strong>01)</strong>Open File.scpt</td></tr>
<tr><th>Appearance in the menu</th><td>Open File</td></tr>
</table>
</dd>
@ -33,12 +33,12 @@
<dd>By adding “dot (.) + modifier-key + shortcut-key” in front of the extension, you can assign a keyboard shortcut to the file.
<table>
<caption>example 2.</caption>
<tr><th>File name</th><td>Insert String<strong>.@e</strong>.scpt</td></tr>
<tr><th>Filename</th><td>Insert String<strong>.@e</strong>.scpt</td></tr>
<tr><th>Appearance in the menu</th><td>Insert String (<kbd>Command</kbd>-<kbd>E</kbd>)</td></tr>
</table>
<table>
<caption>example 3.</caption>
<tr><th>File name</th><td>03)Insert Date<strong>.@&#x007E;Y</strong>.scpt</td></tr>
<tr><th>Filename</th><td>03)Insert Date<strong>.@&#x007E;Y</strong>.scpt</td></tr>
<tr><th>Appearance in the menu</th><td>Insert Date (<kbd>Option</kbd>-<kbd>Shift</kbd>-<kbd>Command</kbd>-<kbd>Y</kbd>)</td></tr>
</table>
<dl style="margin-top: 1em;">
@ -63,7 +63,7 @@
<ul>
<li>Shortcut-keys (e.g. “e” in the example 2) are case sensitive. The one in uppercase indicates that “the Shift key should be pressed together” as in the example 3.</li>
<li>A shortcut-key must come after modifier-keys, and must be one letter. Thus, you can't assign the keys such as F1 or Delete to scripts.</li>
<li>A shortcut-key must come after modifier-keys, and must be one letter. Thus, you cant assign the keys such as F1 or Delete to scripts.</li>
<li>When the keyboard shortcut you set is already taken by another function, the shortcut for the script will be ignored.</li>
</ul>
@ -74,7 +74,7 @@
<dl>
<dt>Hidden Files/Folders</dt>
<dd>A file/folder whose name begins with underscore “_” will not be lined up in the script menu. You can use them for setting files, library scripts etc.</dd>
<dd>A file/folder whose name begins with underscore “_” will not be lined up in the script menu. You can use them for setting files, library scripts and so on.</dd>
</dl>

View File

@ -15,10 +15,10 @@
<h1>Working with UNIX scripts</h1>
<p>This page explains how to pass your document's text to UNIX scripts that are executable via the Script menu, or how to receive the outputs from them.</p>
<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 file 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 .swift (regardless of their languages)</li>
<li>In order to run a script, you need to set execute permission for the script file.</li>
<li>Line endings in your script must be LF.</li>
</ul>
@ -38,7 +38,7 @@
<ul style="margin-top: 1em;">
<li>With no parameters, CotEditor passes nothing just like when you put “None.”</li>
<li>A script should capture CotEditor's text data on STDIN (standard in).</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>

View File

@ -30,7 +30,7 @@
<li>UNIX script</li>
</ul>
<p>While AppleScript (incl. JXA; JavaScript for Automation) can control CotEditor's document more flexible, UNIX scripts can only modify 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="../pgs/about_applescript.html">Working with AppleScript scripts</a> or <a href="../pgs/about_script_spec.html">Working with UNIX scripts</a>.</p>
<p>While AppleScript (incl. JXA; JavaScript for Automation) can control CotEditors document more flexible, UNIX scripts can only modify 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="../pgs/about_applescript.html">Working with AppleScript scripts</a> or <a href="../pgs/about_script_spec.html">Working with UNIX scripts</a>.</p>
<h2>Get existing CotEditor scripts</h2>

View File

@ -6,12 +6,12 @@
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>CotEditor's Source Code</title>
<title>CotEditors Source Code</title>
</head>
<body>
<h1>CotEditor's Source Code</h1>
<h1>CotEditors Source Code</h1>
<p>CotEditor is an open source software. Its 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

@ -20,9 +20,9 @@
<table>
<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 in order to search the code elements you want to be colored.</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 doesn't affect to syntax highlighitng. 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>
</table>
<ul>

View File

@ -13,11 +13,11 @@
<h1>Syntax coloring objects</h1>
<p>The code elements that CotEditor's syntax coloring supports are as follows:</p>
<p>The code elements that CotEditors syntax coloring uses are as follows:</p>
<table>
<thead>
<tr><th>element</th><th>description</th><th>examples</th></tr>
<tr><th>Element</th><th>Description</th><th>Examples</th></tr>
</thead>
<tbody>

View File

@ -6,16 +6,16 @@
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Characters aren't displayed correctly</title>
<title>Characters arent displayed correctly</title>
</head>
<body>
<h1>Characters aren't displayed correctly</h1>
<h1>Characters arent displayed correctly</h1>
<p>Characters can be garbled if CotEditor fails to detect the file's text encoding correctly. In such cases, change the text encoding as described below:</p>
<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 select an encoding from the list.</li>
<li>Choose Format &gt; File Encoding, and then choose an encoding from the list.</li>
<li>When a dialog appears, click Reinterpret.</li>
</ol>
<p><img src="../gfx/encodingWindow@2x.png" width="568"/></p>
@ -32,7 +32,7 @@
<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="../pgs/howto_customize_encoding_order.html">Setting the priority of encoding auto-detection</a></li>
<li>If you enable “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 />
<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="../pgs/about_autodetect_charset.html">Using encoding declarations for auto-detection</a></li>
</ul>

View File

@ -6,14 +6,14 @@
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>I can't save a file</title>
<title>I cant save a file</title>
</head>
<body>
<h1>I can't save a file</h1>
<h1>I cant save a file</h1>
<p>In the cases described below, you can't save the file you're working on. What you need to do then is save it with another name, or change the file permission using Finder or Terminal.</p>
<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>
<li>You are not the owner of the file.</li>
<li>The file is locked.</li>

View File

@ -6,20 +6,20 @@
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>CotEditor crashes</title>
<title>CotEditor quits unexpectedly</title>
</head>
<body>
<h1>CotEditor crashes</h1>
<h1>CotEditor quits unexpectedly</h1>
<p>If you get frequent crashes of CotEditor under certain circumstances, please send a crash log on the following page:</p>
<p>If you get frequent unexpected quits of CotEditor under certain circumstances, please send a crash log on the following page:</p>
<ul>
<li><a href="https://github.com/coteditor/CotEditor/issues">Issues coteditor/CotEditor -github</a></li>
</ul>
<p>When you send a crash log, don't forget to include the following information:</p>
<p>When you send a crash log, dont forget to include the following information:</p>
<ul>
<li>The operation you performed just before the crash.</li>
<li>The operation you performed just before the unexpected quit.</li>
<li>Your environment information such as the version of macOS, the version of CotEditor, your machine model, and so on.</li>
</ul>
<p>You can display a crash log by clicking Report in the dialog which appears on the crash.</p>

View File

@ -6,14 +6,14 @@
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>My own key bindings don't work as I expect</title>
<title>My own key bindings dont work as I expect</title>
</head>
<body>
<h1>My own key bindings don't work as I expect</h1>
<h1>My own key bindings dont work as I expect</h1>
<p>If a key binding you set doesn't work properly chances are that:</p>
<p>If a key binding you set doesnt work properly chances are that:</p>
<ul>
<li>The key binding is already taken by another function.</li>
<li>You have set the key binding in the Menu Item settings, but the same key binding exists in the Snippet setting. In this case, the latter takes precedence.</li>

View File

@ -6,14 +6,14 @@
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>I can't find a solution</title>
<title>I cant find a solution</title>
</head>
<body>
<h1>I can't find a solution</h1>
<h1>I cant find a solution</h1>
<p>If you couldn't find any answer to your problem, please inquire. In doing so, select Create Issue Report in the Help menu and fill out the form.</p>
<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>
<p>The issue tracking page you should send to is:</p>
<ul>

View File

@ -2,7 +2,7 @@
<head>
<meta charset="UTF-8"/>
<meta name="keywords" content="coloring, re-coloring, re-color all"/>
<meta name="keywords" content="coloring, recoloring, re-color all"/>
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
@ -15,9 +15,9 @@
<p>When syntax coloring seems not working properly, try the following procedure:</p>
<ol>
<li>Choose Format &gt; Syntax Style, and select Re-color All.</li>
<li>Choose Format &gt; Syntax Style &gt; Recolor All.</li>
</ol>
<p>If it doesn't help, the possible causes are:</p>
<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>

View File

@ -16,8 +16,8 @@
<p>To complete words, follow the instruction below:</p>
<ol>
<li>Type the first few letters of a word.</li>
<li>Select “Complete” action in “Edit” menu, or press <kbd>Option</kbd>-<kbd>Esc</kbd></li>
<li>Choose the word you want to input from the pop-up list.</li>
<li>Choose Complete command in Edit menu, or press <kbd>Option</kbd>-<kbd>Esc</kbd></li>
<li>Choose the word you want to input from the list.</li>
</ol>
<ul>
<li>To close the list, press <kbd>Esc</kbd>.</li>

View File

@ -23,7 +23,7 @@
<li>Move up the encodings you use frequently.<br />
(Here, we recommend placing UTF-16 <strong>after</strong> other often-used encodings, as UTF-16 can encode most characters.)</li>
</ol>
<p>Though you can change the order of encodings, you cannot delete them. Just move down the encodings you don't use.</p>
<p>Though you can change the order of encodings, you cannot delete them. Just move down the encodings you dont use.</p>
<p>Besides, “Unicode (UTF-8)” and “Unicode (UTF-8) with BOM” are always handled as a set. Because the BOM (byte order mark) will be taken into account when trying encoding data into UTF-8, there is no effect on the detection precision that the order of these two encodings are fixed.</p>

View File

@ -13,10 +13,10 @@
<h1>Changing font type and color</h1>
<p>You can change your document's font type.</p>
<p>You can change your documents font type.</p>
<ol>
<li>Choose Format &gt; Font &gt; Show Fonts.</li>
<li>Select the font of your choice using the Font panel.</li>
<li>Select the font of your choice using the Fonts window.</li>
</ol>
<ul>
<li>These changes apply only to the window currently active. To change the default font for all new documents, choose CotEditor &gt; Preferences &gt; Appearance.</li>

View File

@ -13,10 +13,10 @@
<h1>Customizing key bindings</h1>
<p>You can fully customize CotEditor's 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 Shift-Return. 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 which have your preferred key bindings assigned. For instance, you can insert “<code>&lt;br /&gt;</code>” (with a line ending) by pressing Shift-Return. Go to “Key Binbings” 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 don't appear in the Menu Key Bindings list).</li>
<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>
</ul>

View File

@ -17,13 +17,13 @@
<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 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 script at:<br/>
~/Library/Application Scripts/com.coteditor.CotEditor/</li>
<li>Put your script files in this folder, or remove from there.</li>
<li>The changes you made inside the scripts folder will be automatically reflected.</li>
</ol>
<ul>
<li>CotEditor recognizes scripts only when their file extensions are: .applescript .scpt .scptd .sh .pl .php .rb .py .js</li>
<li>CotEditor recognizes scripts only when their filename extensions are: .applescript .scpt .scptd .sh .pl .php .rb .py .js</li>
<li>You can <strong>change the order of appearance</strong> or <strong>assign keyboard shortcuts</strong> by modifying the names of your script files.<br />
See <a href="../pgs/about_script_name.html">File naming rules for CotEditor scripts</a> for more details.</li>
<li>You can create subfolders in the scripts folder. They will appear as submenus.</li>

View File

@ -13,7 +13,7 @@
<h1>About syntax styles</h1>
<p>CotEditor's syntax styles control syntax coloring, Outline, and the completion list, all together. To customize styles:</p>
<p>CotEditors syntax styles control syntax coloring, Outline, and the completion list, all together. To customize styles:</p>
<ol>
<li>Choose CotEditor &gt; Preferences.</li>
<li>Select Format.</li>
@ -21,7 +21,7 @@
<li>Double-click the style name or press Edit button.</li>
</ol>
<p>To use an existing style as a guide for creating your own, select Duplicate in the action button (gear icon) instead.</p>
<p>To use an existing style as a guide for creating your own, choose Duplicate in the action button (gear icon) instead.</p>
<section id="cf">

View File

@ -13,17 +13,17 @@
<h1>About themes</h1>
<p>CotEditor's theme is a collection of settings about editor's coloring. To customize themes:</p>
<p>CotEditors theme is a collection of settings about editors coloring. To customize themes:</p>
<ol>
<li>Choose CotEditor &gt; Preferences.</li>
<li>Select Appearances pane.</li>
<li>Select the theme you want to customize from the theme list.</li>
</ol>
<p>To use an existing theme as a guide for creating your own, select Duplicate in the action button (gear icon) instead. You can also export your own themes and import themes which are created by others.</p>
<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 own themes and import themes which are created by others.</p>
<h2>Theme file format</h2>
<p>CotEditor theme file must have the own extension .cottheme and its format is based on JSON with hex color values with <code>#</code> symbol.</p>
<p>CotEditor theme file must have the own extension .cottheme and its format is based on JSON with hexadecimal color values with <code>#</code> symbol.</p>
<section id="cf">

View File

@ -13,7 +13,7 @@
<h1>Customizing the toolbar</h1>
<p>As Finder or many Cocoa applications, CotEditor allows you to customize the toolbar. To do that:</p>
<p>As the Finder or many Cocoa applications, CotEditor allows you to customize the toolbar. To do that:</p>
<ul>
<li>Choose View &gt; Customize Toolbar.</li>
</ul>

View File

@ -23,28 +23,28 @@
<p>You can toggle the visibility of invisible characters in the current document by performing one of the following:</p>
<ul>
<li>Choose “Show/Hide Invisible Characters” from the Format menu at the top of your screen.</li>
<li>Select Invisibles button in the window toolbar (The Invisibles button can be added by customizing toolbar).</li>
<li>Select Invisibles button in the Touch Bar (The Invisibles button can be added by customizing Touch Bar).</li>
<li>Choose Show/Hide Invisible Characters command from the Format menu at the top of your screen.</li>
<li>Select Invisibles button in the window toolbar (The Invisibles button can be added by customizing toolbar).</li>
<li>Select Invisibles button in the Touch Bar (The Invisibles button can be added by customizing the Touch Bar).</li>
</ul>
<p>The change here doesnt override the CotEditor's default setting.</p>
<p>The change here doesnt override the CotEditors default setting.</p>
<h3>Default setting</h3>
<p>You can change the default setting of the invisible visibility in the Preferences' <a href="pref_appearance.html">Appearance</a> pane by selecting “Show invisible character” checkbox.</p>
<p>You can change the default setting of the invisible visibility in the Preferences <a href="pref_appearance.html">Appearance</a> pane by selecting “Show invisible character” checkbox.</p>
<h3>Printing invisible characters on print</h3>
<p>You can set whether printing also invisible characters on print in the Preferences' <a href="pref_print.html">Print</a> pane for the default setting, or in the print dialog for an individual document.</p>
<p>You can set whether printing also invisible characters on print in the Preferences <a href="pref_print.html">Print</a> pane for the default setting, or in the print dialog for an individual document.</p>
<h2>Types of invisible characters</h2>
<p>In the Preferences' <a href="pref_appearance.html">Appearance</a> pane, you can set which types of invisible characters are shown when the invisible character display is enabled. The types correspond to the following characters:</p>
<p>In the Preferences <a href="pref_appearance.html">Appearance</a> pane, you can set which types of invisible characters are shown when the invisible character display is enabled. The types correspond to the following characters:</p>
<table>
<style>

View File

@ -32,10 +32,10 @@
<p>To end the multi-cursor editing mode:</p>
<ul>
<li>Click or drag somewhere in the editor without modifier keys by setting a single insertion point at the location.</li>
<li>Press <kbd>Esc</kbd> key and all insertion points except the top one are discarded.</li>
<li>Press the <kbd>Esc</kbd> key and all insertion points except the top one are discarded.</li>
</ul>
<p>The multi-curor editing currently doesn't support the text input that requires user selection after input, such as Japanese. In such cases, multi-cursor editing finishes automatically when typed and text is input only at a single point.</p>
<p>The multi-curor editing currently doesnt work with the text input that requires user selection after input, such as Japanese. In such cases, multi-cursor editing finishes automatically when typed and text is input only at a single point.</p>
<section id="cf">

View File

@ -13,7 +13,7 @@
<h1>Using File Drop</h1>
<p>To use File Drop, drag and drop a file onto your document window.</p>
<p>To use File Drop, drag a file to the editor area.</p>
<ul>
<li>You need to set in advance the string to be inserted when you drop a file.</li>
<li>To configure the behavior of File Drop, choose CotEditor &gt; Preferences &gt; File Drop.</li>

View File

@ -15,14 +15,14 @@
<h2>Inputting a line ending</h2>
<p>Typing <kbd>Option</kbd>+<kbd>Return</kbd> in a input field in the Find panel breaks a line.</p>
<p>Typing <kbd>Option</kbd>-<kbd>Return</kbd> in a input field in the Find window breaks a line.</p>
<h2>Finding line endings</h2>
<h3>Textual search</h3>
<p>On the normal textual search, the line endings contained in the search string are assumed as the line ending code used in the document being searched for. That is, it doesn't match the line endings that differ from the document line ending type.</p>
<p>On the normal textual search, the line endings contained in the search string are assumed as the line ending code used in the document being searched for. That is, it doesnt match the line endings that differ from the document line ending type.</p>
<h3>Regular expression search</h3>
@ -30,9 +30,7 @@
<p>As with the textual search, the line endings contained in the search string are assumed as the line ending code used in the document being searched for. On the other hand, the line endings specified as a metacharacter or a Unicode code point in the regular expression pattern are treated as-is regardless of the line endings type of the target document.</p>
<table>
<thead>
<caption>Metacharacters indicating a line ending in the regular expression</caption>
</thead>
<caption>Metacharacters indicating a line ending in the regular expression</caption>
<tbody>
<tr><th>pattern</th><th>description</th></tr>
@ -50,7 +48,7 @@
<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>There is currently no way to replace with line endings other than the document line ending. The only way on CotEditor to insert a line ending different from the document's line ending is <a href="../pgs/howto_input_unicode.html">manually inputting by Unicode code point</a>.</p>
<p>There is currently no way to replace with line endings other than the document line ending. The only way on CotEditor to insert a line ending different from the documents line ending is <a href="../pgs/howto_input_unicode.html">manually inputting by Unicode code point</a>.</p>

View File

@ -22,13 +22,13 @@
<section>
<h2>Find/Replacement Fields</h2>
<p>Input the text to find to the find field, the text field with a lope icon; and input the text to replace with to the replacement field, the text field with a pen icon. When the replacement field is empty by replacement, the matched texts are just removed.</p>
<p>Enter the text to find to the find field, the field with a lope icon; and enter the text to replace with to the replacement field, the field with a pen icon. When the replacement field is empty by replacement, the matched texts are just removed.</p>
<p>To insert the following special characters to the fields, use the following key combinations:</p>
<table>
<thead>
<tr><th>character</th><th>Key combination</th></tr>
<tr><th>Character</th><th>Key combination</th></tr>
</thead>
<tbody>
@ -62,7 +62,7 @@
<section>
<h2>Advanced Find Options</h2>
<p>You can customize find behavior from the advanced find options panel. The advanced find options panel will be opened when you click the gear button in the find panel.</p>
<p>You can customize find behavior from the advanced find options panel. The advanced find options panel will be opened when you click the gear button in the Find window.</p>
<table>
<thead>
@ -71,14 +71,14 @@
<tbody>
<tr><td>Wrap search around</td><td>Find from the the beginning of the document if there is no match after the cursor.</td></tr>
<tr><td>Select next match after replace</td><td>Select next match after “Replace” automatically.</td></tr>
<tr><td>Auto-close progress dialog</td><td>Automatically close progress dialog that is shown when Find All or Replace All performed after progress is finished.</td></tr>
<tr><td>Auto-close progress dialog</td><td>Automatically close progress dialog that is shown when Find All or Replace All performed after progress is finished.</td></tr>
</tbody>
</table>
<section>
<h3>Textual Search</h3>
<p>Options for search when the regular expression is disabled.</p>
<p>Options for search when the regular expression is turned off.</p>
<table>
<thead>

View File

@ -15,12 +15,12 @@
<p>To input a character with Unicode code point in the hexadecimal format at the current caret position:</p>
<ol>
<li>Choose Edit &gt; Input in Unicode Code Point</li>
<li>Input a code point in the “Input Unicode” dialog (The “Input” button becomes enabled after a valid hex code is input).</li>
<li>Press <kbd>Return</kbd> key or click “Input” button.</li>
<li>Choose Edit &gt; Input in Unicode Code Point.</li>
<li>Enter a code point in the field.</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 hex code with “U+”, “0x” or “\u” prefix. For example, “1F603”, “U+1F603”, “0x1F603” or “\u1F603” are valid to input “😃”.</p>
<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” prefix. For example, “1F603”, “U+1F603”, “0x1F603” or “\u1F603” are valid to input “😃”.</p>
</body>
</html>

View File

@ -15,10 +15,10 @@
<p>In the document inspector, you can view various information concerning your document.</p>
<ol>
<li>Choose File &gt; Get Info.</li>
<li>To close the inspector view, drag the view separator to the window edge, or choose File &gt; Get Info again.</li>
<li>Choose View &gt; Inspector &gt; Document Inspector.</li>
<li>To close the inspector view, drag the view separator to the window edge, or choose View &gt; Inspector &gt; Document Inspector again.</li>
</ol>
<p>Clicking the Get Info icon on the toolbar also opens the same view.</p>
<p>Selecting the Inspector item on the toolbar also opens the same view.</p>
<p>The information displayed in the inspector is as follows:</p>
<table>
@ -38,13 +38,13 @@
<tr><th>Lines</th><td>The number of lines in the document (and the selection).</td></tr>
<tr><th>Characters</th><td>The number of characters in the document (and the selection).</td></tr>
<tr><th>Length</th><td>The length of string in UTF-16 in the document (and the selection).</td></tr>
<tr><th>Words</th><td>The number of words in the document (and the selection). The current language in the Spelling panel will be used to interpret words.</td></tr>
<tr><th>Words</th><td>The number of words in the document (and the selection). The current language in the Spelling window will be used to interpret words.</td></tr>
<tr><th>Location</th><td>The caret-position described in the number of characters.</td></tr>
<tr><th>Current Line</th><td>The line number of the line containing the caret.</td></tr>
<tr><th>Column</th><td>The caret-position from the head of the current line.</td></tr>
</tbody>
<tbody>
<tr><th>Code Points</th><td>The Unicode hexadecimal codes (UTF-16) for the selected character (displayed only when one character is selected).</td></tr>
<tr><th>Code Points</th><td>The Unicode hexadecimal codes (UTF-16) for the selected character (displayed only when single character is selected).</td></tr>
</tbody>
</table>

View File

@ -13,12 +13,12 @@
<h1>Checking whether incompatible characters are included</h1>
<p>If you input a character which is incompatible with your document's 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>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>
<p>To show incompatible characters:</p>
<ol>
<li>Choose File &gt; Show Incompatible Characters.</li>
<li>To close the list, drag the view separator to the window edge, or choose File &gt; Show Incompatible Characters again.</li>
<li>Choose View &gt; Inspector &gt; Incompatible Characters.</li>
<li>To close the list, drag the view separator to the window edge, or choose View &gt; Inspector &gt; Incompatible Characters again.</li>
</ol>
</body>

View File

@ -50,11 +50,11 @@
<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 file extension and of which content is written in JSON format.</p>
<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>
<ul>
<li><b>Export</b>: Select a definition to export in the list on the left, then select Export or Share” menu item 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, select Import” menu item in the Advanced menu, then select the replacement definition files to import.</li>
<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>
@ -73,7 +73,7 @@
<li><b>Highlight</b>: Highlight all matches in the frontmost document*.</li>
</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>
<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>
@ -111,7 +111,7 @@
<tr><th>Replace With</th><td>A string to replace with. If you leave this field, the matches are just deleted.</td></tr>
<tr><td>RE</td><td>Search with regular expression (abbreviation of <u>R</u>egular <u>E</u>xpression).</td></tr>
<tr><td>IC</td><td>Ignore character case on search (abbreviation of <u>I</u>gnore <u>C</u>ase).</td></tr>
<tr><th>Description</th><td>You can use this field to leave a comment about the rule. The description doesn't affect to replacement. This field can be left blank.</td></tr>
<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>

View File

@ -13,7 +13,7 @@
<h1>Opening hidden files</h1>
<p>The checkbox “Show hidden files” in the open dialog can toggle the visibility of hidden files in the panel.</p>
<p>The checkbox “Show hidden files” in the open dialog can toggle the visibility of hidden files in the dialog.</p>
</body>
</html>

View File

@ -14,10 +14,10 @@
<h1>Sort with specific pattern</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>
<p>From Sort by Pattern command in the Text &gt; Lines menu, you can sort selected lines by specifying the way to compare.</p>
<p>The simple Sort command in the Text &gt; Lines menu is the same as sorting “entire line” with “ignore case” and “Respect language rules” options on.</p>
<p>The simple Sort command in the Text &gt; Lines menu is the same as sorting “entire line” with “ignore case” and “Respect language rules” options on.</p>
<section>
@ -63,11 +63,11 @@
<table>
<thead>
<tr><th>option</th><th>description</th></tr>
<tr><th>Option</th><th>Description</th></tr>
</thead>
<tbody>
<tr><td>Ignore case</td><td>Ignore character case on sort.</td></tr>
<tr><td>Respect language rules</td><td>Fuzzily sort respecting the current language setting. i.e.: ignoring trivial differences such as character widths or diacritic marks.</td></tr>
<tr><td>Respect language rules</td><td>Fuzzily sort respecting the current language setting. i.e.: ignoring trivial differences such as character widths or diacritical marks.</td></tr>
<tr><td>Treat numbers as numeric value</td><td>Numbers within the sort keys are compared as numeric value. (e.g.: file12 &gt; file5)</td></tr>
<tr><td>Keep the first line at the top</td><td>Ignore the first line by sorting.</td></tr>
<tr><td>In decending order</td><td>Sort results in decending order.</td></tr>

View File

@ -15,8 +15,8 @@
<p>To print your document, choose File &gt; Print.</p>
<ul>
<li>The options you've set in the Print preferences pane are in effect when you print.</li>
<li>In the print dialog, you open and select the CotEditor option from the drop-down menu, then you can temporarily modify your print settings (The font cannot be changed here).</li>
<li>The options youve set in the Print preferences pane are in effect when you print.</li>
<li>In the print dialog, you open and choose CotEditor from the drop-down menu, then you can temporarily modify your print settings (The font cannot be changed here).</li>
</ul>
</body>

View File

@ -13,9 +13,9 @@
<h1>Getting information about character</h1>
<p>CotEditor can popover the information about the selected character. Select exactly a single character and select Inspect Character in Text menu or press <kbd>Cmmand</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 Text menu or press <kbd>Cmmand</kbd>-<kbd>Option</kbd>-<kbd>I</kbd> keys.</p>
<p>In the popover, zoomed character, 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>
<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>
</body>
</html>

View File

@ -16,7 +16,7 @@
<p>The Outline feature generates a drop-down menu listing specific parts of your document according to the <a href="../pgs/about_outlinemenu_settings.html">Outline settings</a> of your syntax style. The menu is displayed beneath the toolbar. By clicking on an item in the menu, you can easily go and select the corresponding part.</p>
<ul>
<li>To show Outline Menu, choose View &gt; Show Navigation Bar.</li>
<li>You need to make syntax coloring active in order to use Outline Menu.</li>
<li>You need to make syntax coloring active to use Outline Menu.</li>
</ul>
<p>The <a href="../pgs/about_outlinemenu_settings.html">Outline settings</a>, where you can configure what items should appear and how they should be titled in the menu, are included in the Syntax Style settings.</p>

View File

@ -6,14 +6,14 @@
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>Splitting a document window</title>
<title>Splitting editor</title>
</head>
<body>
<h1>Splitting a document window</h1>
<h1>Splitting editor</h1>
<p>To split a document window into multiple panes, choose View &gt; Split Editor, or, click the icon on the right edge of the navigation bar.</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 second icon from the right edge of the navigation bar.</p>
<p><img src="../gfx/split_editor@2x.png" width="400" alt=""/></p>

View File

@ -19,7 +19,7 @@
<li>~/Library/Containers/com.coteditor.CotEditor/</li>
<li>~/Library/Application Scripts/com.coteditor.CotEditor/</li>
</ul>
<p>Here, the tilde (~) represents the user's home folder and the slash (/) means the folder separator.</p>
<p>Here, the tilde (~) represents the users home folder and the slash (/) means the folder separator.</p>
</body>
</html>

View File

@ -14,11 +14,11 @@
<h1>Discover CotEditor</h1>
<p>CotEditor is a Cocoa text editor designed for editing plain text files such as web pages (HTML), program source codes (Python, Ruby, etc.), or TeX sources. CotEditor offers a lot of useful features that are not available in macOS's TextEdit. You'll find some of them below.</p>
<p>CotEditor is a Cocoa text editor designed for editing plain text files such as web pages (HTML), program source codes (Python, Ruby, and so on), or TeX sources. CotEditor offers a lot of useful features that are not available in macOSs TextEdit. Youll find some of them below.</p>
<section class="topic">
<h2>Powerful find and replace</h2>
<p><img class="snapshot" src="../gfx/ov_find@2x.png" alt="[Find Panel]"/>CotEditor has a very powerful find and replace feature.</p>
<p><img class="snapshot" src="../gfx/ov_find@2x.png" alt="[Find window]"/>CotEditor has a very powerful find and replace feature.</p>
<p>In addition to the support for regular expression search, you can display a list of search results, or highlight matched words in your document.</p>
<ul>
<li><a href="../pgs/howto_findpanel.html">Find and Replace</a></li>
@ -37,7 +37,7 @@
<section class="topic">
<h2>Outline</h2>
<p><img class="snapshot" src="../gfx/ov_outline@2x.png" alt="ov_outline.png"/>CotEditor's Outline extracts predefined keywords from the document and displays them in a drop-down menu. By clicking on a listed item, you can go directly to the corresponding part of your document.</p>
<p><img class="snapshot" src="../gfx/ov_outline@2x.png" alt="ov_outline.png"/>CotEditors Outline extracts predefined keywords from the document and displays them in a drop-down menu. By clicking on a listed item, you can go directly to the corresponding part of your document.</p>
<p>You can set what items should appear and how they should be titled in the menu by customizing the corresponding syntax style.</p>
<ul>
<li><a href="../pgs/howto_show_outlinemenu.html">How to show Outline</a></li>
@ -47,7 +47,7 @@
<section class="topic">
<h2>Word completion</h2>
<p><img class="snapshot" src="../gfx/ov_complete@2x.png" alt="ov_complete.png"/>Word completion assists you to input words faster, such as when typing reserved words of programming languages or HTML elements.</p>
<p>If you press the ESC or F5 key after typing the first few letters of a word, a list of possible completions shows up. You only need to select the one you want to input from the list. The range of completions can be expanded or limited.</p>
<p>If you press the <kbd>Option</kbd>-<kbd>Esc</kbd> or <kbd>F5</kbd> key after typing the first few letters of a word, a list of possible completions appears. You only need to select the one you want to input from the list. The range of completions can be expanded or limited.</p>
<ul>
<li><a href="../pgs/howto_complete.html">How to complete words</a></li>
<li><a href="../pgs/about_complist_settings.html">Completion list settings</a></li>
@ -74,22 +74,22 @@
<dd>CotEditor can comment-out/uncomment selected text with corresponded comment delimiters.</dd>
<dt><a href="../pgs/howto_filedrop.html">File Drop</a></dt>
<dd>File Drop lets you insert a specified string when you drop a file onto your document window. For example, you can insert the IMG tag into your HTML document by dropping an image file on it.</dd>
<dd>File Drop lets you insert a specified string when you drop a file onto the editor. For example, you can insert the IMG tag into your HTML document by dropping an image file on it.</dd>
<dt><a href="../pgs/howto_customize_keybinding.html">Key bindings</a></dt>
<dd>CotEditor's original key bindings are fully customizable.</dd>
<dd>CotEditors original key bindings are fully customizable.</dd>
<dt>Line numbers</dt>
<dd>CotEditor can display line numbers. This is useful such as when you develop and debug programs.</dd>
<dt>semi-transparent Editor</dt>
<dd>You can change a editor's transparency. When you have many windows opened, this will help you find the one you need.</dd>
<dd>You can change a editors transparency. When you have many windows opened, this will help you find the one you need.</dd>
<dt>Line spacing</dt>
<dd>You can set space between lines as you see fit.</dd>
<dt><a href="../pgs/howto_show_glyph_info.html">Character inspector</a></dt>
<dd>You can get your character's information like unicode character name or unicode code quickly.</dd>
<dd>You can get your characters information like unicode character name or unicode code quickly.</dd>
<dt><a href="../pgs/howto_inspect_usedchar.html">Incompatible characters</a></dt>
<dd>There are some characters you cannot save with a particular encoding. This feature enables you to check if those characters are included in your document.</dd>

View File

@ -35,7 +35,7 @@
<tr>
<th>Ligatures</th>
<td>Apply the standard ligature rules to the editor's text, or disable all ligatures. A ligature is a typographic feature joining specific characters as a single glyph.</td>
<td>Apply the standard ligature rules to the editors text, or turn off all ligatures. A ligature is a typographic feature joining specific characters as a single glyph.</td>
</tr>
<tr>
@ -55,7 +55,7 @@
<tr>
<th>Show invisible characters</th>
<td>Transform invisible characters — such as line endings, whitespaces, or control characters — into alternative symbols in order to make them viewable. See <a href="howto_display_invisibles.html">Displaying invisible characters</a> for about the available types of invisible characters.</td>
<td>Transform invisible characters — such as line endings, whitespaces, or control characters — into alternative symbols to make them viewable. See <a href="howto_display_invisibles.html">Displaying invisible characters</a> for about the available types of invisible characters.</td>
</tr>
<tr>
@ -87,10 +87,10 @@
<th>Other Actions (gear)</th>
<td><dl>
<dt>Duplicate</dt>
<dd>Duplicate the selected theme in order to make your own one.</dd>
<dd>Duplicate the selected theme to make your own one.</dd>
<dt>Restore</dt>
<dd>Restore the selected theme to default. This action is available only for bundled themes.</dd>
<dd>Restore the selected theme to default. This command is available only for bundled themes.</dd>
<dt>Export</dt>
<dd>Export the theme file made from the selected theme. With exported files, custom coloring themes can be used on another computer. To use the exported file, do Import.</dd>
@ -107,7 +107,7 @@
<th>Theme editor</th>
<td>Edit the selected theme. Click the color wells to choose colors.<dl>
<dt>Basic</dt>
<dd>Basic text coloring other than syntax highlighting. If “Use system color” check box for the “Selection” is turned on, the user setting in the System Preferences &gt; General &gt; Highlight Color is used for the selection highlighting.</dd>
<dd>Basic text coloring other than syntax highlighting. If “Use system color” check box for the “Selection” is turned on, the setting in System Preferences &gt; General &gt; Highlight Color is used for the selection highlighting.</dd>
<dt>Syntax</dt>
<dd>The text colors for syntax highlighting. Turn on the “Enable syntax highlighting” optoin in the <a href="../pgs/pref_format.html">Format preferences</a> to apply these colors to documents.</dd>

View File

@ -71,7 +71,7 @@
<tbody>
<tr>
<th>Automatic indent</th>
<td>New lines are automatically indented by hitting the <kbd>Return</kbd>/<kbd>Enter</kbd> key. The new line will begin at the same indentation point as the previous line.</td>
<td>New lines are automatically indented by hitting the <kbd>Return</kbd> or <kbd>Enter</kbd> key. The new line will begin at the same indentation point as the previous line.</td>
</tr>
<tr>
@ -91,7 +91,7 @@
<tr>
<th>Indent selection with Tab key</th>
<td>On Tab key pressed, the selections are indented instead of a tab character is inserted, if text is selected.</td>
<td>On the Tab key pressed, the selections are indented instead of a tab character is inserted, if text is selected.</td>
</tr>
</tbody>
</table>
@ -150,7 +150,7 @@
<ul>
<li><strong>Words in document</strong>: The list includes the words 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 you've 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 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>Standard words</strong>: The list includes standard words.</li>
</ul></td>

View File

@ -15,9 +15,9 @@
<h1>Change File Drop preferences</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 your document window. To change these preferences, choose CotEditor &gt; Preferences, then click File Drop.</p>
<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>
<p>For example, you can automatically insert the <code>img</code> tag into your HTML document by dropping an image file from Finder. </p>
<p>For example, you can automatically insert the <code>img</code> tag into your HTML document by dropping an image file from the Finder. </p>
@ -30,9 +30,9 @@
<tr>
<th>File Drop Definitions</th>
<td>Choose the conditons to perform the file drop.<ul>
<li><strong>Extensions</strong>: The setting is performed only when a file with one of these extensions is dropped. If this field is empty (All), all files are eligible. No dot is required for file extensions. You can set multiple extensions by separating them by a comma.</li>
<li><strong>Extensions</strong>: The setting is performed only when a file with one of these extensions is dropped. If this field is empty (All), all files are eligible. No dot is required for filename extensions. You can set multiple extensions by separating them by a comma.</li>
<li><strong>Syntax Style</strong>: The setting is performed only when a file is dropped to a document having this syntax style. If this field is empty (All), all documents are eligible.</li>
<li><strong>Description</strong>: You can use this field to leave a comment about the row. This field doesn't affect the file drop behavior and can be left blank.</li>
<li><strong>Description</strong>: You can use this field to leave a comment about the row. This field doesnt affect the file drop behavior and can be left blank.</li>
</ul>
</td>
</tr>
@ -43,9 +43,9 @@
<tr>
<th>Variables</th>
<td>You can use CotEditor's variables in an insertion format.
<td>You can use CotEditors variables in an insertion format.
<ul>
<li>Variables are going to be replaced with the corresponding information of the dropped file. See <a href="../pgs/about_filedrop.html">Variables for File Drop</a>” for each variable's details.</li>
<li>Variables are going to be replaced with the corresponding information of the dropped file. See <a href="../pgs/about_filedrop.html">Variables for File Drop</a> for each variables details.</li>
</ul>
</td>
</tr>

View File

@ -27,7 +27,7 @@
<tbody>
<tr>
<th>Default line endings</th>
<td>The default line ending style is used when creating a new document. This setting is used also when the opened document doesn't include any line endings.</td>
<td>The default line ending style is used when creating a new document. This setting is used also when the opened document doesnt include any line endings.</td>
</tr>
<tr>
@ -51,7 +51,7 @@
<tr>
<th>Enable syntax coloring</th>
<td>Documents are colored according to its kind. The outline menu in the navigation bar also follows this setting.</td>
<td>Documents are highlighted according to the content language type. The availability of the Outline menu in the navigation bar also follows this setting.</td>
</tr>
<tr>
@ -74,10 +74,10 @@
<dt>Other Actions (gear icon)</dt>
<dd><dl>
<dt>Duplicate “Style Name</dt>
<dd>Duplicate the selected style in order to make your own one.</dd>
<dt>Duplicate “[<span class="variable">style name</span>]</dt>
<dd>Duplicate the selected style to make your own one.</dd>
<dt>Export “Style Name</dt>
<dt>Export “[<span class="variable">style name</span>]</dt>
<dd>Export the style definition file made from the selected style. You can use this exported file to use it on another computer. To use the exported file, do Import.</dd>
<dt>Share</dt>
@ -87,7 +87,7 @@
<dd>This allows you to use a style created on another computer. After selecting Import, choose the exported style file to install.</dd>
<dt>Show File Mapping Conflicts</dt>
<dd>Check if multiple styles are associated with the same extension / file name.</dd>
<dd>Check if multiple styles are associated with the same extension / filename.</dd>
</dl></dd>
</dl></td>
</tr>

View File

@ -41,18 +41,18 @@
<tr>
<th>Enable Auto Save with Versions</th>
<td>Automatically save documents to your file constantly while editing. This option also enables Versions, the modern system feature allowing you to go back to previous versions, as well as modifying document name or location from the window title bar.<br/>Even if it turned off, CotEditor creates backup covertly for unexpected crash.</td>
<td>Automatically save documents to your file constantly while editing. This option also enables Versions, the modern system feature allowing you to go back to previous versions, as well as modifying document name or location from the window title bar.<br/>Even if it turned off, CotEditor creates backup covertly for unexpected quit.</td>
</tr>
<tr>
<th>When document is modified 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 CotEditor's edition</strong>: Do nothing and keep CotEditor's edition. CotEditor may ask whether overwrite the file that was modified by another application first when user saves the document.</li>
<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 user saves the document.</li>
<li><strong>Ask how to resolve</strong>: Display a dialog when the file was modified by another application so that user can choose between to keep CotEditor's edition or to revert to the latest file.</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 to keep CotEditors edition or to revert to the latest file.</li>
<li><strong>Update to modified edition</strong>: Update editor's 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 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>
</ul></td>
</tr>
@ -104,7 +104,7 @@
<tbody>
<tr>
<th>Check for updates automatically</th>
<td>Check the existence of a new version via internet automatically on launch. Then if a new one has been released, CotEditor notifies the information on a panel.</td>
<td>Check the existence of a new version via internet automatically on launch. Then if a new one has been released, CotEditor notifies the information on a dialog.</td>
</tr>
<tr>

View File

@ -51,7 +51,7 @@
</tbody>
</table>
<p>Here, you can set only the key bindings for CotEditor's own commands. For more details about customizing the standard key bindings of Cocoa applications, see Apple's documentation: <a href="https://support.apple.com/en-us/HT201236" rel="external">Apple - macOS keyboard shortcuts</a></p>
<p>Here, you can set only the key bindings for CotEditors own commands. For more details about customizing the standard key bindings of Cocoa applications, see Apples documentation: <a href="https://support.apple.com/en-us/HT201236" rel="external">Apple - macOS keyboard shortcuts</a></p>
<section id="cf">

View File

@ -27,9 +27,9 @@
<th>Prefer Tabs</th>
<td>Choose when documents are opened in tabs instead of new windows:
<ul>
<li><strong>Respect System Setting</strong>: Respect your setting in the “Dock” system preferences.</li>
<li><strong>Respect System Setting</strong>: Respect your setting in the Dock pane in System Preferences.</li>
<li><strong>Always</strong>: Always in tabs as long as more than one document is already opened.</li>
<li><strong>Automatically</strong>: Only when you're working in full screen, or multiple documents are opened at once.</li>
<li><strong>Automatically</strong>: Only when youre working in full screen, or multiple documents are opened at once.</li>
<li><strong>Manually</strong>: Only when explicitly open in tabs.</li>
</ul></td>
</tr>
@ -56,12 +56,12 @@
<tr>
<th>Status bar shows</th>
<td>Choose the information to display in the status bar, the area below the document window.</td>
<td>Choose the information to display in the status bar, the area below the window.</td>
</tr>
<tr>
<th>Window width/height</th>
<td>Set the default window size in pixel. If the fields are left blank, the size of the last document window is adopted.</td>
<td>Set the default window size in pixel. If the fields are left blank, the size of the last window is adopted.</td>
</tr>
<tr>

View File

@ -6304,7 +6304,7 @@
<ul>
<li>When selecting multiple lines, the selection's background color would break between lines. This problem has been fixed.</li>
<li>Turning on the “All controls” option for “Full keyboard access” in the System Preferences could cause some problems (e.g. hiding the caret in a new document or incorrect behavior of input method). This problem has been fixed.</li>
<li>Turning on the “All controls” option for “Full keyboard access” in System Preferences could cause some problems (e.g. hiding the caret in a new document or incorrect behavior of input method). This problem has been fixed.</li>
<li>Fixed a bug where user-configured key bindings couldn't be deleted in the “Menu Key Bindings” setting.</li>
<li>Fixed a bug where current syntax coloring was canceled on each overwrite saving.</li>
<li>With the “Fix line height with composite font” option turned off, line height couldn't be changed. This problem has been fixed.</li>

View File

@ -37,19 +37,19 @@ 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 “Scripting with AppleScript” document in “Help” menu 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 “Scripting with AppleScript” document in the Help menu for details of this specification change.</p>
<h2>Bundle Identifier</h2>
<p>The bundle identifier for CotEditor was changed from “com.aynimac.CotEditor” to “com.coteditor.CotEditor”. From this change, file mappings or other links to CotEditor (e.g. external editor) outside CotEditor can be reset. Please link them again, if links are lost.</p>
<p><em>For advanced users</em>: Notice that the file names for preferences and the domain name for “<code>defaults</code>” command in Terminal was also changed.</p>
<p><em>For advanced users</em>: Notice that the filenames for preferences and the domain name for “<code>defaults</code>” command in Terminal was also changed.</p>
<section id="cf">
<h2>See also</h2>
<ul>
<li><a href="../pgs/whats_new_in_2.0.html">What's New in CotEditor 2.0</a></li>
<li><a href="../pgs/whats_new_in_2.0.html">Whats New in CotEditor 2.0</a></li>
<li><a href="../pgs/specification_changes_on_2.2.html">Specification Changes on CotEditor 2.2</a></li>
<li><a href="../pgs/releasenotes.html">Release Notes</a></li>
<li><a href="../xpgs/xsoftware.html">About CotEditor</a></li>

View File

@ -22,7 +22,7 @@
<p class="addition"><code>\R</code> is the metacharacter defined in the <a href="about_regex.html">CUI regular expression engine</a>, which is used in CotEditor; and matches a newline character, such as <code>U+000A</code> (LF), <code>U+000B</code>, <code>U+000C</code>, <code>U+000D</code> (CR), <code>U+0085</code>, <code>U+2028</code>, <code>U+2029</code>, or the sequence of <code>U+000D</code> <code>U+000A</code> (CRLF).</p>
<p>On the other hand, since the new implementation matches the line ending codes used in the actual document, it enables, for instance, to search for LF that slipped into a document that uses CR as the line ending code.</p>
<p>On the other hand, because the new implementation matches the line ending codes used in the actual document, it enables, for instance, to search for LF that slipped into a document that uses CR as the line ending code.</p>
<h2>Line ending handling in user settings</h2>
@ -52,7 +52,7 @@
<h2>See also</h2>
<ul>
<li><a href="../pgs/howto_find_newline.html">Finding or replacing a line ending</a></li>
<li><a href="../pgs/whats_new_in_4.2.html">What's New in CotEditor 4.2</a></li>
<li><a href="../pgs/whats_new_in_4.2.html">Whats New in CotEditor 4.2</a></li>
<li><a href="../pgs/releasenotes.html">Release Notes</a></li>
<li><a href="../xpgs/xsoftware.html">About CotEditor</a></li></ul>

View File

@ -3,7 +3,7 @@
<head>
<meta charset="UTF-8"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>What's New in CotEditor 2.0</title>
<title>Whats New in CotEditor 2.0</title>
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
@ -11,7 +11,7 @@
<body>
<h1>What's New in CotEditor 2.0</h1>
<h1>Whats New in CotEditor 2.0</h1>
<dl>
<dt>Coloring theme feature</dt>

View File

@ -3,7 +3,7 @@
<head>
<meta charset="UTF-8"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>What's New in CotEditor 2.1</title>
<title>Whats New in CotEditor 2.1</title>
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
@ -11,11 +11,11 @@
<body>
<h1>What's New in CotEditor 2.1</h1>
<h1>Whats New in CotEditor 2.1</h1>
<dl>
<dt>Auto-Backup</dt>
<dd>You don't need to lost your unsaved data any more. CotEditor automatically
<dd>You dont need to lost your unsaved data any more. CotEditor automatically
backups your documents while editing, so that you can resume your editing
at the next session, even after force quitting.</dd>

View File

@ -3,7 +3,7 @@
<head>
<meta charset="UTF-8"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>What's New in CotEditor 2.2</title>
<title>Whats New in CotEditor 2.2</title>
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
@ -11,7 +11,7 @@
<body>
<h1>What's New in CotEditor 2.2</h1>
<h1>Whats New in CotEditor 2.2</h1>
<dl>
<dt>Available in the Mac App Store</dt>
@ -27,7 +27,7 @@
<dd>The syntax highlighting becomes further faster and more nicely.</dd>
<dt>Print feature improvement</dt>
<dd>Other than the vertical text print, the print feature has been improved, for instance, to change page settings in the print panel, to store CotEditor's own print settings to the system print preset.</dd>
<dd>Other than the vertical text print, the print feature has been improved, for instance, to change page settings in the print panel, to store CotEditors own print settings to the system print preset.</dd>
<dt>El Capitan support</dt>
<dd>CotEditor 2.2.0 works well on OS X El Capitan.</dd>

View File

@ -3,7 +3,7 @@
<head>
<meta charset="UTF-8"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>What's New in CotEditor 2.3</title>
<title>Whats New in CotEditor 2.3</title>
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
@ -11,7 +11,7 @@
<body>
<h1>What's New in CotEditor 2.3</h1>
<h1>Whats New in CotEditor 2.3</h1>
<dl>
<dt>Auto Save and Versions</dt>
@ -21,7 +21,7 @@
<dd>Move selected lines, remove duplicate lines and more. The various handy line editing actions enable document editing more smoothly and easier.</dd>
<dt>Auto indent style detection</dt>
<dd>No more tab option switching for different source codes. CotEditor detects document's indent style and sets the corresponding tab expansion behavior automatically for you.</dd>
<dd>No more tab option switching for different source codes. CotEditor detects documents indent style and sets the corresponding tab expansion behavior automatically for you.</dd>
</dl>

View File

@ -3,7 +3,7 @@
<head>
<meta charset="UTF-8"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>What's New in CotEditor 2.4</title>
<title>Whats New in CotEditor 2.4</title>
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
@ -11,7 +11,7 @@
<body>
<h1>What's New in CotEditor 2.4</h1>
<h1>Whats New in CotEditor 2.4</h1>
<dl>
<dt>Improve text finder</dt>
@ -24,7 +24,7 @@
<dd>This new option detects URL strings in your documents and provides them as clickable &amp; quick-lookable links.</dd>
<dt>Better detection on the file opening</dt>
<dd>We reviewed the previous file detection code and improved the precision of the encoding detection. Furthermore, CotEditor 2.4 alerts about a file that isn't obviously a text file in order to avoid unwanted hang-up.</dd>
<dd>We reviewed the previous file detection code and improved the precision of the encoding detection. Furthermore, CotEditor 2.4 alerts about a file that isnt obviously a text file in order to avoid unwanted hang-up.</dd>
</dl>

View File

@ -3,7 +3,7 @@
<head>
<meta charset="UTF-8"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>What's New in CotEditor 2.5</title>
<title>Whats New in CotEditor 2.5</title>
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
@ -11,7 +11,7 @@
<body>
<h1>What's New in CotEditor 2.5</h1>
<h1>Whats New in CotEditor 2.5</h1>
<dl>
<dt>New “Unicode (UTF-8) with BOM” encoding</dt>

View File

@ -3,7 +3,7 @@
<head>
<meta charset="UTF-8"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>What's New in CotEditor 3.0</title>
<title>Whats New in CotEditor 3.0</title>
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
@ -11,7 +11,7 @@
<body>
<h1>What's New in CotEditor 3.0</h1>
<h1>Whats New in CotEditor 3.0</h1>
<dl>
<dt>Swift migration</dt>
@ -24,7 +24,7 @@
<dd>Graphic images like toolbar icons and application icon were also updated to get a more modern look.</dd>
<dt>New text search engine</dt>
<dd>The find panel's regular expression engine was changed from Onigmo (Oniguruma-mod) to the ICU library. Thanks to that, the line-up of text search is updated with new useful items and not only for the regex search but also for the normal texture search.</dd>
<dd>The find panels regular expression engine was changed from Onigmo (Oniguruma-mod) to the ICU library. Thanks to that, the line-up of text search is updated with new useful items and not only for the regex search but also for the normal texture search.</dd>
<dt>Support macOS Sierra</dt>
<dd>Hello to Sierra and good-bye to Mountain Lion and Mavericks. So, CotEditor now supports from OS X 10.10 to macOS 10.12.</dd>

View File

@ -3,7 +3,7 @@
<head>
<meta charset="UTF-8"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>What's New in CotEditor 3.1</title>
<title>Whats New in CotEditor 3.1</title>
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
@ -11,14 +11,14 @@
<body>
<h1>What's New in CotEditor 3.1</h1>
<h1>Whats New in CotEditor 3.1</h1>
<dl>
<dt>Touch Bar support</dt>
<dd>CotEditor provides support for the new MacBook Pro's Touch Bar.</dd>
<dd>CotEditor provides support for the new MacBook Pros Touch Bar.</dd>
<dt>Improve tabbed window support</dt>
<dd>Now, you can customize Sierra's tabbed window behavior in CotEditor preferences. Furthermore, when you open multiple files at once, they will be combined to a single window with tabs.</dd>
<dd>Now, you can customize Sierras tabbed window behavior in CotEditor preferences. Furthermore, when you open multiple files at once, they will be combined to a single window with tabs.</dd>
</dl>

View File

@ -3,7 +3,7 @@
<head>
<meta charset="UTF-8"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>What's New in CotEditor 3.2</title>
<title>Whats New in CotEditor 3.2</title>
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
@ -11,7 +11,7 @@
<body>
<h1>What's New in CotEditor 3.2</h1>
<h1>Whats New in CotEditor 3.2</h1>
<dl>
<dt>File Drop feature improvements</dt>

View File

@ -3,7 +3,7 @@
<head>
<meta charset="UTF-8"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>What's New in CotEditor 3.3</title>
<title>Whats New in CotEditor 3.3</title>
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
@ -12,7 +12,7 @@
<body>
<h1>What's 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>
@ -22,13 +22,13 @@
<dd>New “Sort by pattern” enables you to sort selected lines by specific column or fully freely using the regular expression. Of course, through a neat user interface.</dd>
<dt>iCloud document (finally)</dt>
<dd>We know it's kind of too late, but CotEditor now supports the iCloud document, so that CotEditor has a own space on iCloud, moves files to there easier, and can resolve a file modification conflict visually.</dd>
<dd>We know its kind of too late, but CotEditor now supports the iCloud document, so that CotEditor has a own space on iCloud, moves files to there easier, and can resolve a file modification conflict visually.</dd>
<dt>Improvement on the Share featue</dt>
<dd>Document sharing in CotEditor gets more feature.</dd>
<dt>More macOS native look &amp; feel</dt>
<dd>Added small tweaks to the user interface. You don't see any different? Then, that's good. It means it worked.</dd>
<dd>Added small tweaks to the user interface. You dont see any different? Then, thats good. It means it worked.</dd>
<dt>More international</dt>
<dd>CotEditor now supports the RTL (right-to-left) writing direction for such as Arabic, Hebrew, Hindi and others. Furthermore, Portuguese localization is newly added.</dd>

View File

@ -3,7 +3,7 @@
<head>
<meta charset="UTF-8"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>What's New in CotEditor 3.4</title>
<title>Whats New in CotEditor 3.4</title>
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
@ -12,7 +12,7 @@
<body>
<h1>What's New in CotEditor 3.4</h1>
<h1>Whats New in CotEditor 3.4</h1>
<dl>
<dt>Apply multiple replacement rules at once</dt>

View File

@ -3,7 +3,7 @@
<head>
<meta charset="UTF-8"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>What's New in CotEditor 3.5</title>
<title>Whats New in CotEditor 3.5</title>
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
@ -12,7 +12,7 @@
<body>
<h1>What's New in CotEditor 3.5</h1>
<h1>Whats New in CotEditor 3.5</h1>
<dl>
<dt>Brand-new toolbar</dt>

View File

@ -3,7 +3,7 @@
<head>
<meta charset="UTF-8"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>What's New in CotEditor 3.6</title>
<title>Whats New in CotEditor 3.6</title>
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
@ -12,7 +12,7 @@
<body>
<h1>What's New in CotEditor 3.6</h1>
<h1>Whats New in CotEditor 3.6</h1>
<dl>
<dt>Dark Mode</dt>

View File

@ -3,7 +3,7 @@
<head>
<meta charset="UTF-8"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>What's New in CotEditor 3.7</title>
<title>Whats New in CotEditor 3.7</title>
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
@ -12,7 +12,7 @@
<body>
<h1>What's New in CotEditor 3.7</h1>
<h1>Whats New in CotEditor 3.7</h1>
<dl>
<dt>Multi-Cursor editing</dt>

View File

@ -3,7 +3,7 @@
<head>
<meta charset="UTF-8"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>What's New in CotEditor 3.8</title>
<title>Whats New in CotEditor 3.8</title>
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
@ -12,7 +12,7 @@
<body>
<h1>What's New in CotEditor 3.8</h1>
<h1>Whats New in CotEditor 3.8</h1>
<dl>
<dt>Improve Dark Mode compatibility</dt>

View File

@ -3,7 +3,7 @@
<head>
<meta charset="UTF-8"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>What's New in CotEditor 3.9</title>
<title>Whats New in CotEditor 3.9</title>
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
@ -12,7 +12,7 @@
<body>
<h1>What's New in CotEditor 3.9</h1>
<h1>Whats New in CotEditor 3.9</h1>
<dl>
<dt>Invisible characters with more accuracy</dt>

View File

@ -3,7 +3,7 @@
<head>
<meta charset="UTF-8"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>What's New in CotEditor 4.0</title>
<title>Whats New in CotEditor 4.0</title>
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
@ -12,7 +12,7 @@
<body>
<h1>What's 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>

View File

@ -3,14 +3,14 @@
<head>
<meta charset="UTF-8"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>What's New in CotEditor 4.1</title>
<title>Whats New in CotEditor 4.1</title>
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
</head>
<body>
<h1>What's New in CotEditor 4.1</h1>
<h1>Whats New in CotEditor 4.1</h1>
<dl>
<dt>More comfort in your daily language</dt>

View File

@ -3,7 +3,7 @@
<head>
<meta charset="UTF-8"/>
<meta name="keywords" content="what's new, highlights, release"/>
<title>What's New in CotEditor 4.2</title>
<title>Whats New in CotEditor 4.2</title>
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
@ -13,14 +13,14 @@
<a name="whats_new"></a>
<h1>What's 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.</dd>
<dt>Printing 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>
<dd>The print dialog got the option Selection to the Pages section. It enables printing only the selected text in the document.</dd>
</dl>

View File

@ -15,7 +15,7 @@
<h1>Text encoding</h1>
<ul>
<li><a href="../pgs/faq_cannot_display.html">Characters aren't displayed correctly</a></li>
<li><a href="../pgs/faq_cannot_display.html">Characters arent displayed correctly</a></li>
<li><a href="../pgs/howto_inspect_usedchar.html">Checking whether incompatible characters are included</a></li>
<li><a href="../pgs/howto_customize_encoding_order.html">Setting the priority of encoding auto-detection</a></li>
<li><a href="../pgs/faq_about_yen_backslash.html">The Yen sign appears as a backslash</a></li>

View File

@ -15,11 +15,11 @@
<h1>Solving problems</h1>
<ul>
<li><a href="../pgs/faq_cannot_display.html">Characters aren't displayed correctly</a></li>
<li><a href="../pgs/faq_crash.html">CotEditor crashes</a></li>
<li><a href="../pgs/faq_not_find_solution.html">I can't find a solution</a></li>
<li><a href="../pgs/faq_cannot_save.html">I can't save a file</a></li>
<li><a href="../pgs/faq_keybinding.html">My own key bindings don't work as I expect</a></li>
<li><a href="../pgs/faq_cannot_display.html">Characters arent displayed correctly</a></li>
<li><a href="../pgs/faq_crash.html">CotEditor quits unexpectedly</a></li>
<li><a href="../pgs/faq_not_find_solution.html">I cant find a solution</a></li>
<li><a href="../pgs/faq_cannot_save.html">I cant save a file</a></li>
<li><a href="../pgs/faq_keybinding.html">My own key bindings dont work as I expect</a></li>
<li><a href="../pgs/faq_re_coloring.html">Syntax coloring seems not working properly</a></li>
<li><a href="../pgs/faq_about_yen_backslash.html">The Yen sign appears as a backslash</a></li>
<li><a href="../pgs/about_shiftjis.html">What is the difference between the four kinds of Shift JIS?</a></li>

View File

@ -28,7 +28,7 @@
<li><a href="../pgs/howto_print.html">Printing a document</a></li>
<li><a href="../pgs/howto_multiple_replace.html">Replacing with multiple rules</a></li>
<li><a href="../pgs/howto_rectangular_selection.html">Selecting rectangular area</a></li>
<li><a href="../pgs/howto_split.html">Splitting a document window</a></li>
<li><a href="../pgs/howto_split.html">Splitting editor</a></li>
<li><a href="../pgs/howto_uninstall.html">Uninstalling CotEditor</a></li>
<li><a href="../pgs/about_move_menu.html">Using Go To</a></li>
</ul>

View File

@ -16,30 +16,30 @@
<ul>
<li><a href="../pgs/overview.html">Discover CotEditor</a></li>
<li><a href="../pgs/about_sourcecode.html">CotEditor's Source Code</a></li>
<li><a href="../pgs/about_sourcecode.html">CotEditors Source Code</a></li>
<li><a href="../pgs/releasenotes.html">Release Notes</a></li>
<li><a href="../pgs/specification_changes.html">Specification Changes on CotEditor 2.0</a></li>
<li><a href="../pgs/specification_changes_on_2.2.html">Specification Changes on CotEditor 2.2</a></li>
<li><a href="../pgs/specification_changes_on_4.2.html">Specification Changes on CotEditor 4.2</a></li>
<li><a href="../pgs/whats_new_in_2.0.html">What's New in CotEditor 2.0</a></li>
<li><a href="../pgs/whats_new_in_2.1.html">What's New in CotEditor 2.1</a></li>
<li><a href="../pgs/whats_new_in_2.2.html">What's New in CotEditor 2.2</a></li>
<li><a href="../pgs/whats_new_in_2.3.html">What's New in CotEditor 2.3</a></li>
<li><a href="../pgs/whats_new_in_2.4.html">What's New in CotEditor 2.4</a></li>
<li><a href="../pgs/whats_new_in_2.5.html">What's New in CotEditor 2.5</a></li>
<li><a href="../pgs/whats_new_in_3.0.html">What's New in CotEditor 3.0</a></li>
<li><a href="../pgs/whats_new_in_3.1.html">What's New in CotEditor 3.1</a></li>
<li><a href="../pgs/whats_new_in_3.2.html">What's New in CotEditor 3.2</a></li>
<li><a href="../pgs/whats_new_in_3.3.html">What's New in CotEditor 3.3</a></li>
<li><a href="../pgs/whats_new_in_3.4.html">What's New in CotEditor 3.4</a></li>
<li><a href="../pgs/whats_new_in_3.5.html">What's New in CotEditor 3.5</a></li>
<li><a href="../pgs/whats_new_in_3.6.html">What's New in CotEditor 3.6</a></li>
<li><a href="../pgs/whats_new_in_3.7.html">What's New in CotEditor 3.7</a></li>
<li><a href="../pgs/whats_new_in_3.8.html">What's New in CotEditor 3.8</a></li>
<li><a href="../pgs/whats_new_in_3.9.html">What's New in CotEditor 3.9</a></li>
<li><a href="../pgs/whats_new_in_4.0.html">What's New in CotEditor 4.0</a></li>
<li><a href="../pgs/whats_new_in_4.1.html">What's New in CotEditor 4.1</a></li>
<li><a href="../pgs/whats_new_in_4.2.html">What's New in CotEditor 4.2</a></li>
<li><a href="../pgs/whats_new_in_2.0.html">Whats New in CotEditor 2.0</a></li>
<li><a href="../pgs/whats_new_in_2.1.html">Whats New in CotEditor 2.1</a></li>
<li><a href="../pgs/whats_new_in_2.2.html">Whats New in CotEditor 2.2</a></li>
<li><a href="../pgs/whats_new_in_2.3.html">Whats New in CotEditor 2.3</a></li>
<li><a href="../pgs/whats_new_in_2.4.html">Whats New in CotEditor 2.4</a></li>
<li><a href="../pgs/whats_new_in_2.5.html">Whats New in CotEditor 2.5</a></li>
<li><a href="../pgs/whats_new_in_3.0.html">Whats New in CotEditor 3.0</a></li>
<li><a href="../pgs/whats_new_in_3.1.html">Whats New in CotEditor 3.1</a></li>
<li><a href="../pgs/whats_new_in_3.2.html">Whats New in CotEditor 3.2</a></li>
<li><a href="../pgs/whats_new_in_3.3.html">Whats New in CotEditor 3.3</a></li>
<li><a href="../pgs/whats_new_in_3.4.html">Whats New in CotEditor 3.4</a></li>
<li><a href="../pgs/whats_new_in_3.5.html">Whats New in CotEditor 3.5</a></li>
<li><a href="../pgs/whats_new_in_3.6.html">Whats New in CotEditor 3.6</a></li>
<li><a href="../pgs/whats_new_in_3.7.html">Whats New in CotEditor 3.7</a></li>
<li><a href="../pgs/whats_new_in_3.8.html">Whats New in CotEditor 3.8</a></li>
<li><a href="../pgs/whats_new_in_3.9.html">Whats New in CotEditor 3.9</a></li>
<li><a href="../pgs/whats_new_in_4.0.html">Whats New in CotEditor 4.0</a></li>
<li><a href="../pgs/whats_new_in_4.1.html">Whats New in CotEditor 4.1</a></li>
<li><a href="../pgs/whats_new_in_4.2.html">Whats New in CotEditor 4.2</a></li>
</ul>
</body>

View File

@ -24,7 +24,7 @@
<dt>使い方のヒント</dt>
<dd><a href="xpgs/xhowto.html">CotEditorを使う上で役に立ついくつかのヒントをご紹介します。</a></dd>
<dt>環境設定</dt>
<dd><a href="xpgs/xpreferences.html">環境設定パネルについて説明します。</a></dd>
<dd><a href="xpgs/xpreferences.html">環境設定ウインドウについて説明します。</a></dd>
<dt>問題を解決する</dt>
<dd><a href="xpgs/xfaq.html">よくある問題に対する回答を見つけます。</a></dd>
<dt>CotEditorについて</dt>

View File

@ -189,7 +189,7 @@
<p>この仕様はCotEditor 1.5で正式に廃止され関連するコードも削除されました。最前面ドキュメントのselectionを得るためには例1または例2のようにそれを明示してください。</p>
<figure>
<figcaption>例1</figcaption>
<figcaption>例1)</figcaption>
<pre class="source"><code class="AppleScript">tell application "CotEditor"
contents of selection <b>of front document</b>
end tell
@ -197,7 +197,7 @@ end tell
</figure>
<figure>
<figcaption>例2</figcaption>
<figcaption>例2)</figcaption>
<pre class="source"><code class="AppleScript">tell application "CotEditor"
<b>tell document 1</b>
contents of selection

View File

@ -26,7 +26,7 @@ ln -s /Applications/CotEditor.app/Contents/SharedSupport/bin/cot /usr/local/bin/
<h3>セキュリティ認証</h3>
<p>macOSでほかのアプリケーションから<code>cot</code>コマンドでCotEditorを操作するために、ユーザによる認証が必要です。この認証は通常<code>cot</code>コマンドを初めて使用したときに表示されるダイアログから行えますが、なんらかの理由でそれがされなかった場合は手動での設定が必要です。「システム環境設定」&gt;「セキュリティとプライバシー」&gt;「プライバシー」&gt;「オートメーション」で、ターミナルなど利用するクライアントの下にある<strong>CotEditor</strong>(また、<code>--wait</code>オプションのためには<strong>System Events</strong>も)のチェックボックスを有効にしてください。</p>
<p>macOSでほかのアプリケーションから<code>cot</code>コマンドでCotEditorを操作するために、ユーザによる認証が必要です。この認証は通常<code>cot</code>コマンドを初めて使用したときに表示されるダイアログから行えますが、なんらかの理由でそれがされなかった場合は手動での設定が必要です。「システム環境設定」>「セキュリティとプライバシー」>「プライバシー」>「オートメーション」で、ターミナルなど利用するクライアントの下にある<strong>CotEditor</strong>(また、<code>--wait</code>オプションのためには<strong>System Events</strong>も)のチェックボックスを有効にしてください。</p>
<h3>Python 3のインストール</h3>

View File

@ -23,8 +23,8 @@
<p>CotEditor は以下の順序で最適なシンタックススタイルを捜査します。</p>
<ol>
<li>ファイル拡張子<ul>
<li>ファイル拡張子から対応するシンタックススタイルを探します。このとき大文字小文字を無視しますが、対応するシンタックススタイルが複数ある場合は大文字小文字が対応しているものを優先します。</li>
<li>ファイル拡張子<ul>
<li>ファイル拡張子から対応するシンタックススタイルを探します。このとき大文字小文字を無視しますが、対応するシンタックススタイルが複数ある場合は大文字小文字が対応しているものを優先します。</li>
<li>例: .html → HTML</li>
<li>例: .hTmL → HTML</li>
<li>例: .py → Python</li>
@ -40,7 +40,7 @@
<li>例: <code>#!/usr/bin/env python3</code> → Python (インタープリタ名: <code>python3</code>)</li>
</ul></li>
<li>XML 宣言<ul>
<li>対応する拡張子・ファイル名・インタープリタがないとき、ファイル内容が XML 宣言で始まっていたら、自動的にXMLスタイルを適用します。</li>
<li>対応する拡張子・ファイル名・インタープリタがないとき、ファイル内容がXML宣言で始まっていたら、自動的にXMLスタイルを適用します。</li>
<li>例: <code>&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;</code> → XML</li>
</ul></li>
<li>なし<ul>

View File

@ -15,8 +15,8 @@
<h1>「行に移動」メニュー</h1>
<p>「検索」メニューの「行に移動」(<kbd>Cmd</kbd> + <kbd>L</kbd>)で移動ダイアログが表示され、移動先の範囲指定が可能です。</p>
<p>移動パネルでは選択したい数値を入力して「移動」ボタンをクリックします。</p>
<p>「検索」メニューの「行に移動」(<kbd>Command</kbd>-<kbd>L</kbd>)で移動ダイアログが表示され、移動先の範囲指定が可能です。</p>
<p>移動ダイアログでは選択したい数値を入力して「移動」ボタンをクリックします。</p>
<ul>
<li><dl><dt>「3」を入力</dt>
<dd>→ 3行目全体が選択される</dd></dl></li>

View File

@ -36,13 +36,13 @@
<table>
<caption>例2.</caption>
<tr><th>ファイル名</th><td>Insert String<strong>.@e</strong>.scpt</td></tr>
<tr><th>メニュータイトル</th><td>Insert String (<kbd>Command</kbd> + <kbd>E</kbd>)</td></tr>
<tr><th>メニュータイトル</th><td>Insert String (<kbd>Command</kbd>-<kbd>E</kbd>)</td></tr>
</table>
<table>
<caption>例3.</caption>
<tr><th>ファイル名</th><td>03)Insert Date<strong>.@&#x007E;Y</strong>.scpt</td></tr>
<tr><th>メニュータイトル</th><td>Insert Date (<kbd>Command</kbd> + <kbd>Option</kbd> + <kbd>Shift</kbd> + <kbd>Y</kbd>)</td></tr>
<tr><th>メニュータイトル</th><td>Insert Date (<kbd>Command</kbd>-<kbd>Option</kbd>-<kbd>Shift</kbd>-<kbd>Y</kbd>)</td></tr>
</table>
<dl style="margin-top: 1em;">
<dt>修飾キーの記述方法</dt>

View File

@ -36,7 +36,7 @@
</tbody>
</table>
<p>これらの文字が含まれていないかどうかは、表示 &gt; インスペクタ &gt; 非互換文字 で確認できます。</p>
<p>これらの文字が含まれていないかどうかは、「表示」>「インスペクタ」>「非互換文字」で確認できます。</p>
<section id="cf">

View File

@ -6,23 +6,23 @@
<link rel="start" href="../CotEditorHelp.html"/>
<link rel="index" href="../xpgs/xall.html"/>
<link rel="stylesheet" href="../../Shared/sty/standard.css"/>
<title>CotEditorがクラッシュする</title>
<title>CotEditorが予期せず終了する</title>
</head>
<body>
<h1>CotEditorがクラッシュする</h1>
<h1>CotEditorが予期せず終了する</h1>
<p>CotEditorが頻繁に特定の状況でクラッシュする場合には、クラッシュログを下記へ送ってください。</p>
<p>CotEditorが頻繁に特定の状況で予期せず終了する場合には、クラッシュログを下記へ送ってください。</p>
<ul>
<li><a href="https://github.com/coteditor/CotEditor/issues">Issues coteditor/CotEditor -github</a></li>
</ul>
<p>なお、クラッシュログを送る際には、下記の情報もあわせてご連絡ください。</p>
<ul>
<li>クラッシュした直前に行っていた操作</li>
<li>予期しない終了の直前に行っていた操作</li>
<li>macOS、CotEditorのバージョン、機種などの環境情報</li>
</ul>
<p>クラッシュログは、クラッシュ直後に表示されるダイアログで「レポートを送信」または「レポート」をクリックすると表示されます。</p>
<p>クラッシュログは、予期しない終了の直後に表示されるダイアログで「レポートを送信」または「レポート」をクリックすると表示されます。</p>
</body>
</html>

View File

@ -21,8 +21,8 @@
</ol>
<ul>
<li>入力補完機能は変換が必要ないときのみ利用できます。日本語入力中には使用できません。</li>
<li>入力候補ウインドウを閉じるには<kbd>Esc</kbd>を押します。</li>
<li>環境設定の「編集」&gt;「入力補完候補リスト」で、表示する入力補完候補をカラーリングスタイルで定義された語句のみとするか、一般的な単語も含めるかを選択できます。</li>
<li>入力候補ウインドウを閉じるには<kbd>Esc</kbd>を押します。</li>
<li>環境設定の「編集」「入力補完候補リスト」で、表示する入力補完候補をカラーリングスタイルで定義された語句のみとするか、一般的な単語も含めるかを選択できます。</li>
</ul>

View File

@ -13,7 +13,7 @@
<h1>フォントをカスタマイズする</h1>
<p>書類ウインドウのフォントをカスタマイズできます。</p>
<p>エディタのフォントをカスタマイズできます。</p>
<ol>
<li>「フォーマット」メニュー>「フォント」の「フォントパネルを表示」を選びます。</li>
<li>フォントを好みに設定します。</li>

View File

@ -22,12 +22,12 @@
<h3>一時的な変更</h3>
<p>現在開いている書類ウインドウで一時的に不可視文字の表示/非表示を切り替えるには以下の方法があります:</p>
<p>現在開いている書類で一時的に不可視文字の表示/非表示を切り替えるには以下の方法があります:</p>
<ul>
<li>画面上部の「フォーマット」メニューの「不可視文字を表示/非表示」を選択</li>
<li>ウインドウツールバーの「不可視文字」ボタンをクリック(「不可視文字」ボタンはツールバーをカスタマイズして追加できます)</li>
<li>Touch Barバーの「不可視文字」ボタンをタッチ「不可視文字」ボタンはTouch Barをカスタマイズして追加できます</li>
<li>Touch Barの「不可視文字」ボタンをタッチ「不可視文字」ボタンはTouch Barをカスタマイズして追加できます</li>
</ul>
<p>ここでの変更はCotEditorのデフォルトの設定を上書きしません。</p>

View File

@ -13,7 +13,7 @@
<h1>ファイルドロップを使用する</h1>
<p>ファイルドロップを使用するには、ファイルを書類ウインドウにドロップします。</p>
<p>ファイルドロップを使用するには、ファイルをエディタにドロップします。</p>
<ul>
<li>あらかじめ、挿入する文字列を設定しておく必要があります。</li>
<li>ファイルドロップの設定は、環境設定の「ファイルドロップ」で行います。</li>

View File

@ -15,7 +15,7 @@
<h2>改行の入力</h2>
<p>検索パネルでは「<kbd>Option</kbd>+<kbd>Return</kbd>」で改行が入力できます。</p>
<p>検索ウインドウでは「<kbd>Option</kbd>-<kbd>Return</kbd>」で改行が入力できます。</p>
<h2>改行の検索</h2>

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