mirror of
https://github.com/coteditor/CotEditor.git
synced 2024-09-11 11:25:57 +03:00
Improve localization
This commit is contained in:
parent
c01b87ddfc
commit
70ed4d89b9
@ -3207,7 +3207,7 @@ no change.
|
||||
### Fixes
|
||||
|
||||
- Fix an issue under OS X 10.11 where the application could crash when an item in the outline inspector is clicked.
|
||||
- Fix an issue where the word completion of which word starts with double underscores (e.g. `__init__`) skipped the second underscore.
|
||||
- Fix an issue where the word completion of which word starts with double underscores (e.g., `__init__`) skipped the second underscore.
|
||||
- Fix an issue where the application could rarely crash while typing.
|
||||
- [AppStore ver.] Fix an issue where the options for the software updater for non-AppStore versions were wrongly displayed in the General preferences pane.
|
||||
|
||||
@ -4702,7 +4702,7 @@ no change.
|
||||
- Allow also taking a 1 to 3 digits point code.
|
||||
- Avoid auto-closing panel after entering character.
|
||||
- Improve character inspector:
|
||||
- Display more comprehensible name for control characters (e.g. `<control-0000>` to `NULL`).
|
||||
- Display more comprehensible name for control characters (e.g., `<control-0000>` to `NULL`).
|
||||
- Display an alternate visible symbol in the zoomed character area for C0 control characters.
|
||||
- Improve installed syntax style list in preferences:
|
||||
- Add dot mark to style names in the list to represent the state if the style is customized.
|
||||
|
@ -52,7 +52,7 @@ You have two options to add a new localization to CotEditor.app. Choose one of t
|
||||
|
||||
A standard localization update proceeds as follows:
|
||||
|
||||
1. When CotEditor has new strings to be localized, the CotEditor maintainer, @1024jp, creates a new ticket on GitHub Issues and mentions the localization maintainers in it so that they can keep all their localized strings up to date. The ticket includes all strings to be updated and their descriptions, sometime with screenshots. e.g. [#1519](https://github.com/coteditor/CotEditor/issues/1519).
|
||||
1. When CotEditor has new strings to be localized, the CotEditor maintainer, @1024jp, creates a new ticket on GitHub Issues and mentions the localization maintainers in it so that they can keep all their localized strings up to date. The ticket includes all strings to be updated and their descriptions, sometime with screenshots. e.g., [#1519](https://github.com/coteditor/CotEditor/issues/1519).
|
||||
2. The localizers either post the localized strings to the thread or make a pull request on GitHub. The maintainers should localize the updated strings within about one week (the shorter period is, of course, welcome, but not required). All the responses must be done on GitHub. Not par email.
|
||||
3. The CotEditor maintainer reviews and merges the update provided by the localizers.
|
||||
|
||||
|
@ -73,7 +73,7 @@
|
||||
<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. For example, 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 > file5)</td></tr>
|
||||
<tr><td>Treat numbers as numeric value</td><td>Numbers within the sort keys are compared as numeric value. (e.g., file12 > 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 descending order</td><td>Sort results in descending order.</td></tr>
|
||||
</tbody>
|
||||
|
@ -3831,7 +3831,7 @@
|
||||
|
||||
<ul>
|
||||
<li>Fix an issue under OS X 10.11 where the application could crash when an item in the outline inspector is clicked.</li>
|
||||
<li>Fix an issue where the word completion of which word starts with double underscores (e.g. <code>__init__</code>) skipped the second underscore.</li>
|
||||
<li>Fix an issue where the word completion of which word starts with double underscores (e.g., <code>__init__</code>) skipped the second underscore.</li>
|
||||
<li>Fix an issue where the application could rarely crash while typing.</li>
|
||||
<li><span class="label">AppStore ver.</span>: Fix an issue where the options for the software updater for non AppStore versions were wrongly displayed in the General preferences pane.</li>
|
||||
</ul>
|
||||
@ -5746,7 +5746,7 @@
|
||||
</ul></li>
|
||||
<li>Improve character inspector:
|
||||
<ul>
|
||||
<li>Display more comprehensible name for control characters (e.g. <code><control-0000></code> to <code>NULL</code>).</li>
|
||||
<li>Display more comprehensible name for control characters (e.g., <code><control-0000></code> to <code>NULL</code>).</li>
|
||||
<li>Display an alternate visible symbol in the zoomed character area for C0 control characters.</li>
|
||||
</ul></li>
|
||||
<li>Improve installed syntax style list in preferences:
|
||||
@ -7728,7 +7728,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 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>
|
||||
|
@ -67,7 +67,7 @@
|
||||
<dd>The text encoding name of the document. (text)</dd>
|
||||
|
||||
<dt><code>IANA charset</code></dt>
|
||||
<dd>The IANA charset name of the document. (text, e.g.<code>Shift_JIS</code>, <code>EUC-JP</code>)</dd>
|
||||
<dd>The IANA charset name of the document. (text, e.g., <code>Shift_JIS</code>, <code>EUC-JP</code>)</dd>
|
||||
|
||||
<dt><code>has BOM</code></dt>
|
||||
<dd>Has the text encoding a BOM (byte order mark)? (boolean) <span class="added">new on CotEditor 4.1</span></dd>
|
||||
|
@ -38,7 +38,7 @@ Validate your customized syntax styles in syntax style editor and follow the mes
|
||||
|
||||
|
||||
<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>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 filenames for preferences and the domain name for “<code>defaults</code>” command in Terminal was also changed.</p>
|
||||
|
||||
|
@ -26,23 +26,23 @@
|
||||
<ol>
|
||||
<li>File extension<ul>
|
||||
<li>Try determining syntax from the file extension. The case is basically ignored; however, case-matched ones are prioritized if multiple syntaxes are found</li>
|
||||
<li>e.g.: .html → HTML</li>
|
||||
<li>e.g.: .hTmL → HTML</li>
|
||||
<li>e.g.: .py → Python</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 in which the find file extension is defined or the filename doesn’t have an extension, then try determining syntax from the whole filename.</li>
|
||||
<li>e.g.: .htaccess → Apache</li>
|
||||
<li>e.g.: makefile → Makefile</li>
|
||||
<li>e.g., .htaccess → Apache</li>
|
||||
<li>e.g., makefile → Makefile</li>
|
||||
</ul></li>
|
||||
<li>Shebang in the first line of the document<ul>
|
||||
<li>When there is no corresponding syntax for the extension and the filename, and if the first line of the document content is a shebang, then try determining syntax from the shebang. In this trial, the interpreter names which is defined in the syntaxes are used. The interpreter can be either the last part of the path just after <code>#!</code> or the next term to the path if the path targets <code>env</code>.</li>
|
||||
<li>e.g.: <code>#!/usr/bin/perl</code> → Perl (interpreter: <code>perl</code>)</li>
|
||||
<li>e.g.: <code>#!/usr/bin/env python3</code> → Python (interpreter: <code>python3</code>)</li>
|
||||
<li>e.g., <code>#!/usr/bin/perl</code> → Perl (interpreter: <code>perl</code>)</li>
|
||||
<li>e.g., <code>#!/usr/bin/env python3</code> → Python (interpreter: <code>python3</code>)</li>
|
||||
</ul></li>
|
||||
<li>XML declaration<ul>
|
||||
<li>When there is no corresponding syntax up to here but the file content starts with an XML declaration, syntax is automatically set to XML.</li>
|
||||
<li>e.g.: <code><?xml version="1.0" encoding="utf-8"?></code> → XML</li>
|
||||
<li>e.g., <code><?xml version="1.0" encoding="utf-8"?></code> → XML</li>
|
||||
</ul></li>
|
||||
<li>None<ul>
|
||||
<li>If no appropriate syntax can be found at all, the “None” syntax would be set.</li>
|
||||
|
@ -1830,7 +1830,7 @@
|
||||
"en" : {
|
||||
"stringUnit" : {
|
||||
"state" : "new",
|
||||
"value" : "Search ignores diacritical marks (e.g. ö = o)."
|
||||
"value" : "Search ignores diacritical marks (e.g., ö = o)."
|
||||
}
|
||||
},
|
||||
"en-GB" : {
|
||||
@ -1842,13 +1842,13 @@
|
||||
"es" : {
|
||||
"stringUnit" : {
|
||||
"state" : "translated",
|
||||
"value" : "La búsqueda ignora las marcas diacríticas (ej: ö = o)."
|
||||
"value" : "La búsqueda ignora las marcas diacríticas (P. ej., ö = o)."
|
||||
}
|
||||
},
|
||||
"fr" : {
|
||||
"stringUnit" : {
|
||||
"state" : "translated",
|
||||
"value" : "La recherche ignore les signes diacritiques (par exemple : ö = o)"
|
||||
"value" : "La recherche ignore les signes diacritiques (Ex. : ö = o)"
|
||||
}
|
||||
},
|
||||
"it" : {
|
||||
@ -1866,7 +1866,7 @@
|
||||
"pt" : {
|
||||
"stringUnit" : {
|
||||
"state" : "translated",
|
||||
"value" : "A busca ignora sinais diacríticos (ö = o)."
|
||||
"value" : "A busca ignora sinais diacríticos (Ex.: ö = o)."
|
||||
}
|
||||
},
|
||||
"tr" : {
|
||||
@ -1884,7 +1884,7 @@
|
||||
"zh-Hant" : {
|
||||
"stringUnit" : {
|
||||
"state" : "translated",
|
||||
"value" : "忽略變音符號進行尋找(例如ö = o)。"
|
||||
"value" : "忽略變音符號進行尋找(例如:ö = o)。"
|
||||
}
|
||||
}
|
||||
}
|
||||
@ -1986,7 +1986,7 @@
|
||||
"en" : {
|
||||
"stringUnit" : {
|
||||
"state" : "new",
|
||||
"value" : "Search ignores width differences in character forms (e.g. a = a)."
|
||||
"value" : "Search ignores width differences in character forms (e.g., a = a)."
|
||||
}
|
||||
},
|
||||
"en-GB" : {
|
||||
@ -1998,13 +1998,13 @@
|
||||
"es" : {
|
||||
"stringUnit" : {
|
||||
"state" : "translated",
|
||||
"value" : "La búsqueda ignora las diferencias de ancho en las formas de caracteres (ej: a = a)."
|
||||
"value" : "La búsqueda ignora las diferencias de ancho en las formas de caracteres (P. ej., a = a)."
|
||||
}
|
||||
},
|
||||
"fr" : {
|
||||
"stringUnit" : {
|
||||
"state" : "translated",
|
||||
"value" : "Ignore les différences de forme des caractères (par exemple : a = a)."
|
||||
"value" : "Ignore les différences de forme des caractères (Ex. : a = a)."
|
||||
}
|
||||
},
|
||||
"it" : {
|
||||
@ -2022,7 +2022,7 @@
|
||||
"pt" : {
|
||||
"stringUnit" : {
|
||||
"state" : "translated",
|
||||
"value" : "A busca ignora as diferenças de largura nas formas dos caracteres (a = a)."
|
||||
"value" : "A busca ignora as diferenças de largura nas formas dos caracteres (Ex.: a = a)."
|
||||
}
|
||||
},
|
||||
"tr" : {
|
||||
@ -2040,7 +2040,7 @@
|
||||
"zh-Hant" : {
|
||||
"stringUnit" : {
|
||||
"state" : "translated",
|
||||
"value" : "忽略字元形式的寬度進行尋找(例如a = a)。"
|
||||
"value" : "忽略字元形式的寬度進行尋找(例如:a = a)。"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
@ -131,7 +131,7 @@ struct FindTextualOptionsView: View {
|
||||
table: "TextFind", comment: "toggle button label"),
|
||||
isOn: $ignoresDiacriticMarks)
|
||||
.help(String(localized: "FindSettings.ignoresDiacriticMarks.description",
|
||||
defaultValue: "Search ignores diacritical marks (e.g. ö = o).",
|
||||
defaultValue: "Search ignores diacritical marks (e.g., ö = o).",
|
||||
table: "TextFind", comment: "tooltip"))
|
||||
|
||||
Toggle(String(localized: "FindSettings.ignoresWidth.label",
|
||||
@ -139,7 +139,7 @@ struct FindTextualOptionsView: View {
|
||||
table: "TextFind", comment: "toggle button label"),
|
||||
isOn: $ignoresWidth)
|
||||
.help(String(localized: "FindSettings.ignoresWidth.description",
|
||||
defaultValue: "Search ignores width differences in character forms (e.g. a = a).",
|
||||
defaultValue: "Search ignores width differences in character forms (e.g., a = a).",
|
||||
table: "TextFind", comment: "tooltip"))
|
||||
} header: {
|
||||
Text("Textual Search", tableName: "TextFind", comment: "heading")
|
||||
|
Loading…
Reference in New Issue
Block a user