coteditor/CotEditor
1
0
Fork 0
mirror of https://github.com/coteditor/CotEditor.git synced 2024-08-16 14:50:30 +03:00
Code Issues Projects Releases Wiki Activity

Merge tag '4.8.7'

Browse Source 
# Conflicts:
#	CHANGELOG.md
#	CotEditor.xcodeproj/project.pbxproj
This commit is contained in:
1024jp 2024-07-08 07:53:24 +09:00
commit e8d5faeaee
19 changed files with 73 additions and 73 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

48
CHANGELOG.md
View File

@ -41,7 +41,7 @@
4.8.7 (unreleased)
4.8.7 (657)
--------------------------
### Improvements
@ -353,7 +353,7 @@
### Fixes
- Fix an issue that the application crashed when trying to convert the encoding of an unsaved document to one incompatible with the content.
- Fix an issue that the application crashed when trying to convert the encoding of an unsaved document to one incompatible with the contents.
- Fix an issue that the application could not open a document containing a specific pattern of letters.
- Fix an issue that the validation error message in the syntax editor did not change even when errors exist.
- Fix an issue that the incompatible characters list did not update under the specific condition.
@ -1386,7 +1386,7 @@
- [beta] Fix an issue that the Line Endings submenu in the Format menu did not display minor line ending types even with the Option key.
- [beta] Fix an issue the item fields in the Outline inspector did not resize properly.
- [beta] Fix a possible issue that the initial massage in the incompatible character list did not reflect the actual result.
- [beta] Fix a possible issue that the initial message in the incompatible character list did not reflect the actual result.
@ -1414,7 +1414,7 @@
- Ability to handle documents holding multiple types of line endings.
- Alert inconsistent line endings in the document when opening or reloading.
- List the inconsistent line endings in the Warnings pane in the inspector.
- Minor 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 document's line ending is one of these).
- Minor 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 document's line ending is one of these).
- Add the hidden Paste Exactly command (Command-Option-V) that pastes text in the clipboard without any modification, such as adjusting line endings to the document setting.
- Add an option Selection to the Pages section in the Print dialog to print only the selected text in the document.
- Add history to the Unicode code point input.
@ -1474,7 +1474,7 @@
- Update Swift syntax style to add keywords added in Swift 5.6.
- Update YAML syntax style for better coloring.
- [trivial] Improve progress message for the Find/Replace All.
- [trivial] Improve the progress message for the Find/Replace All.
- [dev] Update the build environment to Xcode 13.3 (Swift 5.6).
@ -1576,16 +1576,16 @@
- Change the behavior to include the last empty line in the calculation when specifying lines with a negative value in the Go to Line command or via AppleScript.
- Improve the character info section in the document inspector to display the list of code points for the selected character instead of displaying only when a single Unicode character is selected.
- Update the Unicode block name list for the character inspector from Unicode 13.0.0 to Unicode 14.0.0.
- Make sure the application relaunches even other tasks interrupt before termination.
- Make sure the application relaunches even if other tasks interrupt before termination.
- Improve some toolbar items to make their state distinguish even collapsed.
- Display the command name in the error message when the input shortcut for key bindings is already taken by another command.
- Improve VoiceOver accessibility.
- Update the AppleScript guide in the help.
- Improve the animation by drag & drop in tables.
- Optimize several document parse.
- Optimize several document parses.
- [trivial] Adjust the margin of the editor area.
- [trivial] Hide the filename extension of setting files by export by default.
- [trivial] Finish key binding input in Key Bindings pane when another window becomes frontmost.
- [trivial] Finish key binding input in the Key Bindings pane when another window becomes frontmost.
- [trivial] Update some symbols for shortcut keys in the key binding settings.
- [dev] Update the build environment to Xcode 13.2 (Swift 5.5).
- [dev] Remove xcworkspace.
@ -1601,7 +1601,7 @@
- Fix an issue that the slider in the editor opacity toolbar item did not work when collapsed.
- Fix an issue that the editor's opacity change did not apply immediately.
- Fix an issue that some uncustomizable menu commands were provided in the Key Bindings preference pane.
- Fix an issue in the snippet key bindings that shortcuts with only Shift key for modifier keys were accepted though does not work correctly.
- Fix an issue in the snippet key bindings that shortcuts with only the Shift key for modifier keys were accepted though does not work correctly.
- Fix an issue that some help buttons did not work (thanks to Alex Newson!).
- Fix and minor update on localized strings.
- Fix `cot` command to work also with Python 3.
@ -1615,7 +1615,7 @@
### Fixes
- Fix an issue that File Drop settings were not saved if both the extensions and syntax styles are for “all.”
- Fix an issue that shortcuts for snippet did not accept Shift with a non-letter character, such as Shift + Return.
- Fix an issue that shortcuts for snippets did not accept the Shift key with a non-letter character, such as Shift + Return.
- Fix an issue that the rainbow cursor appeared when the document has a large number of incompatible characters.
- Fix an issue that the rainbow cursor appeared when expanding the selection by “⌥⇧←” shortcut and invisible characters are contained in the new selection.
- Fix an issue that the writing direction could be changed to right to left although when the text orientation is vertical.
@ -1705,7 +1705,7 @@
### Fixes
- Fix an issue that the application did not terminate when all windows are closed.
- Fix an issue that annoying dialog that alerts saving was failed could be shown while typing when autosaving is disabled.
- Fix an issue that an annoying dialog that alerts saving was failed could be shown while typing when autosaving is disabled.
- Address an issue that typing in a large document could be slow when the Autosave feature is disabled.
@ -1725,10 +1725,10 @@
- Fix an issue that the application did not terminate when all windows are closed.
- Fix an issue in the script menu that a script bundle (.scptd) was handled not as a script but as a folder.
- Fix an issue in the snippet key bindings that shortcuts with only Shift key for modifier keys were accepted though does not work correctly.
- Fix an issue in the snippet key bindings that shortcuts with only the Shift key for modifier keys were accepted though does not work correctly.
- Fix an issue that the application rarely showed the open dialog on launch even when the user setting for the startup behavior is not “show open dialog.”
- Fix literal number highlight with Ruby syntax style.
- Address an issue that annoying dialog that alerts saving was failed could be shown while typing when autosaving is disabled.
- Address an issue that an annoying dialog that alerts saving was failed could be shown while typing when autosaving is disabled.
@ -1762,7 +1762,7 @@
### Fixes
- Fix French localization.
- [trivial] Fix script icon in the User Guide in Dark mode.
- [trivial] Fix the script icon in the User Guide in Dark mode.
@ -1871,7 +1871,7 @@
- Checkmarks are not applied to the corresponding items in the menus for the collapsed toolbar items.
- [Big Sur] Syntax highlight for the regular expression disappears when the text field becomes in editing (FB8719584).
- [Big Sur] Screenshots in the User Guide are not updated yet.
- [Big Sur] Document icons are not updated yet for Big Sur style.
- [Big Sur] Document icons are not updated yet for the Big Sur style.
@ -1880,7 +1880,7 @@
### Improvements
- Round the corners of current line highlight.
- Round the corners of current line highlights.
- [beta][Big Sur] Match the inspector background to desktop color.
- [beta][trivial] Update title bar color.
@ -1888,8 +1888,8 @@
### Fixes
- [beta] Fix an issue in the navigation bar that the split editor button did not update when changing the split orientation.
- [beta] Fix an issue in the appearance pane and the multiple replacement panel that the newly added setting was not selected.
- [beta] Address an issue that the status bar rarely compressed vertically.
- [beta] Fix an issue in the Appearance pane and the multiple replacement panel that the newly added setting was not selected.
- [beta] Address an issue that the status bar was rarely compressed vertically.
- [beta] Workaround an issue that the initial text color of the pop-up menus in the status bar dimmed.
@ -1941,7 +1941,7 @@
### Known Issues
- Some of the contents in the User Guide are not updated yet.
- Document icons are not updated yet for Big Sur style.
- Document icons are not updated yet for the Big Sur style.
@ -2130,7 +2130,7 @@
- Improve the encodings list edit view.
- Adjust the width of toolbar items.
- Remove “vertical orientation” from the selections of the Writing Direction toolbar button.
- Update help content.
- Update help contents.
- [trivial] Rename “Auto-Detect,” the option detecting the file encoding automatically, to “Automatic.”
- [trivial] Update some labels in the Format pane.
- [beta] Add menu item, toolbar item, and Touch Bar item to toggle visibility of indent guides in the current document.
@ -3816,7 +3816,7 @@ no change.
- Fix an issue where “Reset to Default” action in Font menu was ignored.
- Fix an issue where matching brace was highlighted unwontedly also by text finding.
- Fix an issue where the encoding and the line endings in the status bar were occasionally not displayed.
- Fix an issue where the application froze by getting the content of a large document via the Script menu.
- Fix an issue where the application froze by getting the contents of a large document via the Script menu.
- Fix an issue where the second value of the printed time in the console was not sexagesimal.
- Improve general stability.
@ -3835,7 +3835,7 @@ no change.
### Fixes
- Fix an issue where UNIX scripts could fail getting the content of the document.
- Fix an issue where UNIX scripts could fail getting the contents of the document.
- Fix an issue where font change in the preferences pane could be ignored.
- Fix a potential issue where syntax keywords could be highlighted incorrectly if whitespaces accidentally get into keywords definition.
- Workaround an issue where word suggestion in the Touch Bar cannot insert a word starts with a symbol correctly.
@ -4271,7 +4271,7 @@ no change.
- Fix an issue where find panel position was not saved.
- Fix an issue where no beep sound was made when there was no match on find/replace.
- Fix an issue where the application could freeze after replacing large document.
- Fix an issue where editable area didn't spread to the full width after changing text orientation when content is empty.
- Fix an issue where editable area didn't spread to the full width after changing text orientation when contents were empty.
- Fix an issue where matched brackets in unfocused split editors were highlighted without the need while editing one of split editors.
- Improve general stability.
@ -5249,7 +5249,7 @@ no change.
- Print settings preset can be stored in the print panel.
- Better file encoding handling on revert action.
- Set access-group `com.coteditor.CotEditor.edit` to CotEditor's script definition.
- Change behavior to save `com.apple.TextEncoding` xattr on saving if the file had no content.
- Change behavior to save `com.apple.TextEncoding` xattr on saving if the file had no contents.
- Improve window restoration:
- To restore also the last scroll position and cursor position.
- To restore also the last syntax style mode of unsaved documents.

4
CotEditor/CotEditor.help/Contents/Resources/en.lproj/pgs/faq_cannot_display.html
View File

@ -13,7 +13,7 @@
<h1>If characters aren’t appeared correctly in CotEditor</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 misinterpreted if CotEditor fails to detect the file’s text encoding correctly. In such cases, change the text encoding as described below:</p>
<ol>
<li>Choose Format &gt; Text Encoding, and then choose encoding from the list.</li>
<li>When a dialog appears, click Reinterpret.</li>
@ -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 the encoding detection may help to reduce the occurrences of garbled characters.<br />
→ <a href="howto_customize_encoding_order.html">Change priorities of text encodings</a></li>
<li>If you select “Refer to encoding declaration in document” in the Format settings pane, in-document encoding declarations, such as “<code>encoding=</code>” or “<code>@charset</code>,” takes precedence when CotEditor detects the text encoding.<br />
<li>If you select “Refer to encoding declaration in document” in the Format settings pane, in-document encoding declarations, such as “<code>encoding=</code>” or “<code>@charset</code>,” take precedence when CotEditor detects the text encoding.<br />
→ <a href="about_autodetect_charset.html">Use encoding declarations for encoding detection</a></li>
</ul>

2
CotEditor/CotEditor.help/Contents/Resources/en.lproj/pgs/howto_complete.html
View File

@ -19,7 +19,7 @@
<img class="bordered" src="../gfx/completion@2x.png" width="200" alt="completion.png"/>
</figure>
<p>To complete a word, follow the instruction below:</p>
<p>To complete a word, follow the instructions below:</p>
<ol>
<li>Type the first few letters of a word.</li>
<li>Choose the Complete command in the Edit menu, or press either <kbd>Option</kbd>-<kbd>Esc</kbd> or <kbd>F5</kbd>.</li>

6
CotEditor/CotEditor.help/Contents/Resources/en.lproj/pgs/howto_count_characters.html
View File

@ -21,7 +21,7 @@
<p>CotEditor can show the character count both in the status bar and the document inspector.</p>
<p>The standard character count counts each grapheme cluster, that is defined as the “extended grapheme cluster” in Unicode. A grapheme cluster is a sequence of one or more Unicode code points that should be treated as a single unit for humans. For instance, while a normal character, such as A, is naturally counted as one character, an emoji consisting of multiple Unicode code points, such as 1️⃣ (<code>U+0031</code> <code>U+FE0F</code> <code>U+20E3</code>), is also counted as one character.</p>
<p>The standard character count counts each grapheme cluster, which is defined as the “extended grapheme cluster” in Unicode. A grapheme cluster is a sequence of one or more Unicode code points that should be treated as a single unit for humans. For instance, while a normal character, such as A, is naturally counted as one character, an emoji consisting of multiple Unicode code points, such as 1️⃣ (<code>U+0031</code> <code>U+FE0F</code> <code>U+20E3</code>), is also counted as one character.</p>
<h2>Advanced character count</h2>
@ -32,8 +32,8 @@
<img src="../gfx/advancedCount@2x.png" width="725" alt="Advanced character count option dialog"/>
</figure>
<p>When starting the advanced character count, the counter appears at the bottom of the editor. The counter live-counts the characters in the way you set in the advanced character count option dialog. While text is selected in the editor, the counter shows the number of the selected characters; otherwise, it shows the number of the entire character in the document. You can drag the counter to put it out of the way.</p>
<p>The options are shared in the application. When you changed the options in an editor, the way to count in other editors are also changed.</p>
<p>When starting the advanced character count, the counter appears at the bottom of the editor. The counter live-counts the characters in the way you set in the advanced character count option dialog. While a part of the text is selected in the editor, the counter shows the number of the selected characters; otherwise, it indicates the number of the entire character in the document. You can drag the counter to put it out of the way.</p>
<p>The options are shared in the application. When you change the options in an editor, the way they are counted in other editors also changes.</p>
<p>Note that the advanced character count can affect the processing performance according to the combination of the settings especially when the document to count has a large size. To stop the count, choose the Stop Advanced Character Count command in the Text menu.</p>

4
CotEditor/CotEditor.help/Contents/Resources/en.lproj/pgs/howto_customize_shortcut.html
View File

@ -26,7 +26,7 @@
<tbody>
<tr>
<th>Menu command</th>
<td>Keyboard shortcuts for standard menu command appeared in the menu. Go to the <a href="settings_keybindings.html">Key Bindings settings</a> in the Settings to change the keyboard shortcut for existing menu commands.
<td>Keyboard shortcuts for standard menu commands appeared in the menu. Go to the <a href="settings_keybindings.html">Key Bindings settings</a> in the Settings to change the keyboard shortcut for existing menu commands.
<ul>
<li>Some menu commands provided by the system can not be customized in CotEditor. For details about customizing the standard shortcuts for Cocoa applications, see Apple’s documentation: <a href="https://support.apple.com/guide/mac-help/create-keyboard-shortcuts-for-apps-mchlp2271/mac" rel="external">Create keyboard shortcuts for apps on Mac</a></li>
</ul></td>
@ -42,7 +42,7 @@
</tbody>
</table>
<p>You cannot set the shortcuts that are already taken (for example, shortcuts for your scripts or menu items that don’t appear in the list). When the same shortcut is assigned to multiple commands, it performs only one command among them.</p>
<p>You cannot set the shortcuts that have already been taken (for example, shortcuts for your scripts or menu items that don’t appear in the list). When the same shortcut is assigned to multiple commands, it performs only one command among them.</p>
<section id="cf">

2
CotEditor/CotEditor.help/Contents/Resources/en.lproj/pgs/howto_customize_theme.html
View File

@ -53,7 +53,7 @@
<h2>File format of CotEditor themes</h2>
<p>CotEditor theme file must have .cottheme extension and its format is based on JSON with hexadecimal color values with a <code>#</code> symbol.</p>
<p>A CotEditor theme file must have the .cottheme extension and its format is based on JSON with hexadecimal color values with a <code>#</code> symbol.</p>
<section id="cf">

2
CotEditor/CotEditor.help/Contents/Resources/en.lproj/pgs/howto_display_invisibles.html
View File

@ -38,7 +38,7 @@
<h3>Print invisible characters on printing</h3>
<p>You can set whether printing invisible characters on print in the print dialog.</p>
<p>You can set whether to print invisible characters on print in the print dialog.</p>

8
CotEditor/CotEditor.help/Contents/Resources/en.lproj/pgs/howto_find_inconsistent_line_endings.html
View File

@ -19,16 +19,16 @@
<h2>Detect line endings in the file</h2>
<p>CotEditor automatically inspects line endings in the document when loaded, and set the common line ending type to the document line ending.</a>
<p>CotEditor automatically inspects line endings in the document when loaded, and sets the common line ending type to the document line ending.</a>
<p>At the same time, if there are multiple types of line endings in the document, CotEditor alerts about it. In the dialog, you can then choose whether to convert all those inconsistent line endings to the most common line endings or leave them for now so that you can review them.</p>
<p>If you turn on the “Don’t ask again for this document” checkbox, the warning dialog doesn’t appear more for the document even when inconsistent line endings are found when opening the document. To turn off the warning dialog for all documents entirely, go to <a href="settings_general.html">General settings</a> &gt; <a href="howto_manage_warnings.html">Manage Warnings</a>, and select the “inconsistent line endings dialog.”</p>
<p>If you turn on the “Don’t ask again for this document” checkbox, the warning dialog doesn’t appear anymore for the document, even when inconsistent line endings are found when opening the document. To turn off the warning dialog for all documents entirely, go to <a href="settings_general.html">General settings</a> &gt; <a href="howto_manage_warnings.html">Manage Warnings</a>, and select the “inconsistent line endings dialog.”</p>
<h2>Look over the location of inconsistent line endings</h2>
<p>The Warnings pane lists up all the line endings inconsistent with the document line ending.</p>
<p>The Warnings pane lists all the line endings inconsistent with the document line ending.</p>
<p>To show the Warnings pane:</p>
@ -39,7 +39,7 @@
<h2>Find inconsistent line endings in the editor</h2>
<p>When the visibility setting of the line endings is selected, the inconsistent line endings are drawn in a different color. See <a href="howto_display_invisibles.html">Display invisible characters</a> for instruction on how to change the line endings visibility.</p>
<p>When the visibility setting of the line endings is selected, the inconsistent line endings are drawn in a different color. See <a href="howto_display_invisibles.html">Display invisible characters</a> for instructions on how to change the line endings’ visibility.</p>
<h2>Normalize line endings</h2>

8
CotEditor/CotEditor.help/Contents/Resources/en.lproj/pgs/howto_find_newline.html
View File

@ -22,12 +22,12 @@
<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 to be 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>
<h3>Regular expression search</h3>
<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>
<p>As with the textual search, the line endings contained in the search string are assumed to be 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>
<caption>Metacharacters indicating a line ending in the regular expression</caption>
@ -46,11 +46,11 @@
<h2>Replace with line endings</h2>
<p>As for the text replacing with, all line endings even ones defined as a metacharacter like<code>\n</code> or captured are assumed as the document line ending.</p>
<p>As for the text replacing with, all line endings, even ones defined as a metacharacter like<code>\n</code> or captured, are assumed to be the document line ending.</p>
<p>For example, when replacing the find string “dog\Rcow” with the replacement string “$0\r” using the regular expression in a document whose line ending type is LF (<code>\n</code>), the substring “dog<span class="invisible">\r\n</span>cow” in the document matches as well, and theoretically, the regular expression should replace it with “dog<span class="invisible">\r\n</span>cow<span class="invisible">\r</span>”; however CotEditor actually replaces it with “dog<span class="invisible">\n</span>cow<span class="invisible">\n</span>”.</p>
<p>There is currently no way to replace with line endings other than the document line ending.</p>
<p>There is currently no way to replace them with line endings other than the document line ending.</p>

8
CotEditor/CotEditor.help/Contents/Resources/en.lproj/pgs/howto_insert_camera_text.html
View File

@ -14,23 +14,23 @@
<h1>Insert text from camera in CotEditor</h1>
<p>You can insert text in real-world to the editor by taking a photo with your nearby iPhone or iPad.</p>
<p>You can insert text in the real-world to the editor by taking a photo with your nearby iPhone or iPad.</p>
<p>To insert text by taking a photo, follow the instruction below:</p>
<p>To insert text by taking a photo, follow the instructions below:</p>
<ol>
<li>Make sure your device (iPhone or iPad) is turned on and your Mac find it.</li>
<li>From the Edit menu or the context menu in the editor, choose Insert from iPhone or iPad, and select the method to take a photo.</li>
<li>The Camera app opens on the device you selected. Take a photo with your device:<ul>
<li><strong>Take Photo</strong> command: Take a photo of the text to insert in the Camera app, and confirm it by tapping the Use Photo button.</li>
<li><strong>Scan documents</strong> command: Place your document in view of the camera and wait for the scan to finish (You can also capture it manually). Drag the corners to adjust the scan to fit the page, and then confirm it by tapping the Keep Scan button and Save button in sucession. Note that, although the Scan Documents command allows to import multiple photos as a single document, CotEditor recognizes only the first one even if you import multiple photos.</li>
<li><strong>Scan documents</strong> command: Place your document in view of the camera and wait for the scan to finish (You can also capture it manually). Drag the corners to adjust the scan to fit the page, and then confirm it by tapping the Keep Scan button and Save button in sucession. Note that although the Scan Documents command allows to import multiple photos as a single document, CotEditor recognizes only the first one even if you import multiple photos.</li>
</ul></li>
<li>Once the picture is chosen in your device, it shows up in your CotEditor on Mac. If any text is deteted in the picture, all the detected texts are highlighted in the view.</li>
<li>To insert the detected text to the insertion point in the editor, click the Insert button below the picture.</li>
</ol>
<p>This feature uses the Continuity Camera feature by Apple. To check the requirements to use the Continuity Camera feature on your Mac, see the Apple Support article: <a href="https://support.apple.com/en-us/HT209037" rel="external">Use your iPhone or iPad to scan documents or take a picture on your Mac</a>.</li>
<p>This feature uses the Continuity Camera feature by Apple. To check the requirements for using the Continuity Camera feature on your Mac, see the Apple Support article: <a href="https://support.apple.com/en-us/HT209037" rel="external">Use your iPhone or iPad to scan documents or take a picture on your Mac</a>.</li>
</body>
</html>

2
CotEditor/CotEditor.help/Contents/Resources/en.lproj/pgs/howto_inspect_character.html
View File

@ -19,7 +19,7 @@
<img src="../gfx/characterInspector@2x.png" width="637" alt="The character inspector indicating the information about the character 🐕"/>
</figure>
<p>The inspector shows: the character in close-up, the Unicode code point, the Unicode character name, block name, general category, and the Unicode version that introduced the character. 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 names appear.</p>
<p>The inspector shows: the character in close-up, the Unicode code point, the Unicode character name, block name, general category, and the Unicode version that introduced the character. It also shows the 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 names appear.</p>
</body>
</html>

2
CotEditor/CotEditor.help/Contents/Resources/en.lproj/pgs/howto_multiple_replace.html
View File

@ -45,7 +45,7 @@
<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 .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 .cotrpl file extension and of which contents are written in the JSON format.</p>
<ul>
<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>

2
CotEditor/CotEditor.help/Contents/Resources/en.lproj/pgs/howto_show_outlinemenu.html
View File

@ -30,7 +30,7 @@
<h2>Show Outline inspector</h2>
<p>The Outline inspector is a table-style list appeares in the Outline pane in the inspector of the document. You can get a quick overview of the document’s outline like a table of contents and move to the corresponding part in the editor by clicking an item in the list.</p>
<p>The Outline inspector is a table-style list that appeares in the Outline pane in the inspector of the document. You can get a quick overview of the document’s outline like a table of contents and move to the corresponding part in the editor by clicking an item in the list.</p>
<p>To show the Outline inspector, perform either of the followings:</p>
<ul>

2
CotEditor/CotEditor.help/Contents/Resources/en.lproj/pgs/howto_split.html
View File

@ -17,7 +17,7 @@
<p><img src="../gfx/split_editor@2x.png" width="400" class="bordered" alt=""/></p>
<p>To split an editor into multiple panes, choose View &gt; Split Editor, or, click the icon on the right edge of the navigation bar.</p>
<p>To split an editor into multiple panes, choose View &gt; Split Editor, or click the icon on the right edge of the navigation bar.</p>
<p>To close a split editor, choose View > Close Split Editor, or click the icon on the left edge of the navigation bar.</p>
<p>You can also change split orientation by choosing View &gt; Stack Editors Horizontally (or Vertically) in the menu.</p>

36
CotEditor/CotEditor.help/Contents/Resources/en.lproj/pgs/releasenotes.html
View File

@ -419,7 +419,7 @@
<h2>Fixes</h2>
<ul>
<li>Fix an issue that the application crashed when trying to convert the encoding of an unsaved document to one incompatible with the content.</li>
<li>Fix an issue that the application crashed when trying to convert the encoding of an unsaved document to one incompatible with the contents.</li>
<li>Fix an issue that the application could not open a document containing a specific pattern of letters.</li>
<li>Fix an issue that the validation error message in the syntax editor did not change even when errors exist.</li>
<li>Fix an issue that the incompatible characters list did not update under the specific condition.</li>
@ -1614,7 +1614,7 @@
<li>Ability to handle documents holding multiple types of line endings.</li>
<li>Alert inconsistent line endings in the document when opening or reloading.</li>
<li>List the inconsistent line endings in the Warnings pane in the inspector.</li>
<li>Minor 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 <kbd>Option</kbd> key or when the document’s line ending is one of these).</li>
<li>Minor 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 <kbd>Option</kbd> key or when the document’s line ending is one of these).</li>
<li>Add the hidden Paste Exactly command (<kbd>Command</kbd>-<kbd>Option</kbd>-<kbd>V</kbd>) that pastes text in the clipboard without any modification, such as adjusting line endings to the document setting.</li>
<li>Add an option Selection to the Pages section in the Print dialog to print only the selected text in the document.</li>
<li>Add history to the Unicode code point input.</li>
@ -1716,7 +1716,7 @@
<ul>
<li>Update Swift syntax style to add keywords added in Swift 5.6.</li>
<li>Update YAML syntax style for better coloring.</li>
<li><span class="trivial">trivial</span>: Improve progress message for the Find/Replace All.</li>
<li><span class="trivial">trivial</span>: Improve the progress message for the Find/Replace All.</li>
<li><span class="trivial">dev</span>: Update the build environment to Xcode 13.3 (Swift 5.6).</li>
</ul>
</section>
@ -1860,16 +1860,16 @@
<li>Change the behavior to include the last empty line in the calculation when specifying lines with a negative value in the Go to Line command or via AppleScript.</li>
<li>Improve the character info section in the document inspector to display the list of code points for the selected character instead of displaying only when a single Unicode character is selected.</li>
<li>Update the Unicode block name list for the character inspector from Unicode 13.0.0 to Unicode 14.0.0.</li>
<li>Make sure the application relaunches even other tasks interrupt before termination.</li>
<li>Make sure the application relaunches even if other tasks interrupt before termination.</li>
<li>Improve some toolbar items to make their state distinguish even collapsed.</li>
<li>Display the command name in the error message when the input shortcut for key bindings is already taken by another command.</li>
<li>Improve VoiceOver accessibility.</li>
<li>Update the AppleScript guide in the help.</li>
<li>Improve the animation by drag &amp; drop in tables.</li>
<li>Optimize several document parse.</li>
<li>Optimize several document parses.</li>
<li><span class="trivial">trivial</span>: Adjust the margin of the editor area.</li>
<li><span class="trivial">trivial</span>: Hide the filename extension of setting files by export by default.</li>
<li><span class="trivial">trivial</span>: Finish key binding input in Key Bindings pane when another window becomes frontmost.</li>
<li><span class="trivial">trivial</span>: Finish key binding input in the Key Bindings pane when another window becomes frontmost.</li>
<li><span class="trivial">trivial</span>: Update some symbols for shortcut keys in the key binding settings.</li>
<li><span class="trivial">dev</span>: Update the build environment to Xcode 13.2 (Swift 5.5).</li>
<li><span class="trivial">dev</span>: Remove xcworkspace.</li>
@ -1889,7 +1889,7 @@
<li>Fix an issue that the slider in the editor opacity toolbar item did not work when collapsed.</li>
<li>Fix an issue that the editor’s opacity change did not apply immediately.</li>
<li>Fix an issue that some uncustomizable menu commands were provided in the Key Bindings preference pane.</li>
<li>Fix an issue in the snippet key bindings that shortcuts with only Shift key for modifier keys were accepted though does not work correctly.</li>
<li>Fix an issue in the snippet key bindings that shortcuts with only the Shift key for modifier keys were accepted though does not work correctly.</li>
<li>Fix an issue that the initial position of the side pane was occasionally stacked under the window toolbar.</li>
<li>Fix an issue that some help buttons did not work (thanks to Alex Newson!).</li>
<li>Fix and minor update on localized strings.</li>
@ -1913,7 +1913,7 @@
<ul>
<li>Fix an issue that File Drop settings were not saved if both the extensions and syntax styles are for “all.”</li>
<li>Fix an issue that shortcuts for snippet did not accept Shift with a non-letter character, such as Shift + Return.</li>
<li>Fix an issue that shortcuts for snippets did not accept the Shift key with a non-letter character, such as Shift + Return.</li>
<li>Fix an issue that the rainbow cursor appeared when the document has a large number of incompatible characters.</li>
<li>Fix an issue that the rainbow cursor appeared when expanding the selection by <kbd>⌥⇧←</kbd> shortcut and invisible characters are contained in the new selection.</li>
<li>Fix an issue that the writing direction could be changed to right to left although when the text orientation is vertical.</li>
@ -2062,7 +2062,7 @@
<ul>
<li>Fix an issue that the application did not terminate when all windows are closed.</li>
<li>Fix an issue that annoying dialog that alerts saving was failed could be shown while typing when autosaving is disabled.</li>
<li>Fix an issue that an annoying dialog that alerts saving was failed could be shown while typing when autosaving is disabled.</li>
<li>Address an issue that typing in a large document could be slow when the Autosave feature is disabled. </li>
</ul>
</section>
@ -2095,10 +2095,10 @@
<ul>
<li>Fix an issue that the application did not terminate when all windows are closed.</li>
<li>Fix an issue in the script menu that a script bundle (.scptd) was handled not as a script but as a folder.</li>
<li>Fix an issue in the snippet key bindings that shortcuts with only Shift key for modifier keys were accepted though does not work correctly.</li>
<li>Fix an issue in the snippet key bindings that shortcuts with only the Shift key for modifier keys were accepted though does not work correctly.</li>
<li>Fix an issue that the application rarely showed the open dialog on launch even when the user setting for the startup behavior is not “show open dialog.”</li>
<li>Fix literal number highlight with Ruby syntax style.</li>
<li>Address an issue that annoying dialog that alerts saving was failed could be shown while typing when autosaving is disabled.</li>
<li>Address an issue that an annoying dialog that alerts saving was failed could be shown while typing when autosaving is disabled.</li>
</ul>
</section>
</article>
@ -2155,7 +2155,7 @@
<ul>
<li>Fix French localization.</li>
<li><span class="trivial">trivial</span>: Fix script icon in the User Guide in Dark mode.</li>
<li><span class="trivial">trivial</span>: Fix the script icon in the User Guide in Dark mode.</li>
</ul>
</section>
</article>
@ -2232,7 +2232,7 @@
<li>Previously, CotEditor scripts written in Unix scripts, such as Ruby or Python, were decoded using the user-preferred file-encoding set in the Format preferences pane for normal documents, now they are always interpreted as UTF-8.</li>
<li>Avoid showing the “edited” indicator in the close button of document windows when the document contents are empty and therefore can close the window without the confirmation dialog.</li>
<li>Avoid discarding the current input when a new item is added while another item is in editing in the syntax style editor.</li>
<li>Round the corners of current line highlight.</li>
<li>Round the corners of current line highlights.</li>
<li>Put only the filename rather than the absolute path for the relative path insertion (<code>&lt;&lt;&lt;RELATIVE-PATH&gt;&gt;&gt;</code>) when the document file itself is dropped into the editor.</li>
<li>Remove the toolbar button to toggle page guide visibility.</li>
<li>Remove feature to import legacy syntax style definition files of which format was used in CotEditor 1.x.</li>
@ -2506,7 +2506,7 @@
<li>Make borders of line number views and opacity sample tips more distinct in the high-contrast mode.</li>
<li>Adjust the visible area after unwrapping lines in RTL text mode.</li>
<li>Remove the default value of the snippet key bindings, that inserts <code>&lt;br /&gt;</code> with <kbd>⇧↩</kbd>.</li>
<li>Update help content.</li>
<li>Update help contents.</li>
<li><span class="trivial">trivial</span>: Rename “Auto-Detect,” the option detecting the file encoding automatically, to “Automatic.”</li>
<li><span class="trivial">trivial</span>: Omit surrogate pair code points in the character inspector if the character consists of multiple Unicode characters.</li>
<li><span class="trivial">trivial</span>: Adjust the drawing position of the zoomed character in the character inspector.</li>
@ -4527,7 +4527,7 @@
<li>Fix an issue where “Reset to Default” action in Font menu was ignored.</li>
<li>Fix an issue where matching brace was highlighted unwontedly also by text finding.</li>
<li>Fix an issue where the encoding and the line endings in the status bar were occasionally not displayed.</li>
<li>Fix an issue where the application froze by getting the content of a large document via the Script menu.</li>
<li>Fix an issue where the application froze by getting the contents of a large document via the Script menu.</li>
<li>Fix an issue where the second value of the printed time in the console was not sexagesimal.</li>
<li>Improve general stability.</li>
</ul>
@ -4561,7 +4561,7 @@
<h2>Fixes</h2>
<ul>
<li>Fix an issue where UNIX scripts could fail getting the content of the document.</li>
<li>Fix an issue where UNIX scripts could fail getting the contents of the document.</li>
<li>Fix an issue where font change in the preferences pane could be ignored.</li>
<li>Fix a potential issue where syntax keywords could be highlighted incorrectly if whitespaces accidentally get into keywords definition.</li>
<li>Workaround an issue where word suggestion in the Touch Bar cannot insert a word starts with a symbol correctly.</li>
@ -5214,7 +5214,7 @@
<li>Fix an issue where find panel position was not saved.</li>
<li>Fix an issue where no beep sound was made when there was no match on find/replace.</li>
<li>Fix an issue where the application could freeze after replace large document.</li>
<li>Fix an issue where editable area didn’t spread to the full width after changing text orientation when content is empty.</li>
<li>Fix an issue where editable area didn’t spread to the full width after changing text orientation when contents were empty.</li>
<li>Fix an issue where matched brackets in unfocused split editors were highlighted without the need while editing one of split editors.</li>
<li>Improve general stability.</li>
</ul>
@ -8021,7 +8021,7 @@
<li>After changing the line height or the font size, the scroll position is now adjusted so that the caret/selection can be seen.</li>
<li>Slightly enlarged the “Chars” and “Lines” fields on the Get Info drawer.</li>
<li>The Key Bindings preferences pane now has explanations of changing/assigning the Script menu’s keyboard shortcuts.</li>
<li>Bundled an instruction for ATOK users.</li>
<li>Bundled instructions for ATOK users.</li>
<li>Updated development environment, changed some build options.</li>
</ul>
</section>

2
CotEditor/CotEditor.help/Contents/Resources/en.lproj/pgs/script_osascript_changes.html
View File

@ -13,7 +13,7 @@
<h1>Support different CotEditor versions in AppleScript</h1>
<p>This page lists up the previous specific changes on AppleScript support in CotEditor.</p>
<p>This page lists the previous specific changes on AppleScript support in CotEditor.</p>
<article>

4
CotEditor/CotEditor.help/Contents/Resources/en.lproj/pgs/script_overview.html
View File

@ -29,7 +29,7 @@
<li>UNIX script</li>
</ul>
<p>While AppleScript (incl. JXA; JavaScript for Automation) can control CotEditor’s document more flexibly, UNIX scripts can only modify the contents of the frontmost document. However, as for UNIX scripts, you can write them in various languages, for example; Python, Ruby, Perl, and so on. Choose a script type to suit your use. For details about how to write your scripts, refer to <a href="script_osascript.html">Script CotEditor with AppleScript</a> or <a href="script_unixscript.html">Script CotEditor with UNIX script</a>.</p>
<p>While AppleScript (incl. JXA; JavaScript for Automation) can control CotEditor’s document more flexibly, UNIX scripts can only modify the contents of the frontmost document. However, as for UNIX scripts, you can write them in various languages, such as Python, Ruby, Perl, and so on. Choose a script type that suits your use. For details about how to write your scripts, refer to <a href="script_osascript.html">Script CotEditor with AppleScript</a> or <a href="script_unixscript.html">Script CotEditor with UNIX script</a>.</p>
<h2>Add/delete scripts</h2>
@ -49,7 +49,7 @@
<p>The CotEditor project provides some sample scripts. You can get them on:<br/>
<a href="https://github.com/coteditor/SampleScripts" rel="external">coteditor/SampleScripts -GitHub</a></p>
<p>Some kind users may distribute their scripts for CotEditor online. Some of them are listed on:<br/>
<p>Some users may distribute their scripts for CotEditor online. Some of them are listed on:<br/>
<a href="https://github.com/coteditor/CotEditor/wiki/CotEditor-Scripts" rel="external">CotEditor Scripts -CotEditor Wiki</a></p>

2
CotEditor/CotEditor.help/Contents/Resources/en.lproj/pgs/syntax_highlight_settings.html
View File

@ -18,7 +18,7 @@
<p>In CotEditor, a syntax rules the semantic meaning of the syntax highlighting, and the color scheme used in the actual highlighting is defined as a <a href="howto_customize_theme.html">theme</a>.</p>
<p>To define highlighting rules for a syntax, select a syntax element to add highlighting condition from the list on the left of the syntax editor, then add conditions to the list on the right side. See <a href="syntax_definition.html">Define a syntax</a> for how to open the syntax editor.</p>
<p>To define highlighting defines for a syntax, select a syntax element to add a highlighting condition from the list on the left of the syntax editor, then add conditions to the list on the right side. See <a href="syntax_definition.html">Define a syntax</a> for how to open the syntax editor.</p>
<h2>Elements of syntax highlighting</h2>

2
CotEditor/CotEditor.help/Contents/Resources/ja.lproj/pgs/releasenotes.html
View File

@ -18,7 +18,7 @@
<article>
<header>
<h1>CotEditor 4.8.8</h1>
<h1>CotEditor 4.8.7</h1>
<p>リリース: <time>2024-07-07</time></p>
</header>