Translations by Joel Addison
Joel Addison has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.
| ~ |
If true, the terminal will use the desktop-global standard font if it's monospace (and the most similar font it can come up with otherwise).
|
|
| 2011-06-23 |
If true, the terminal will use the desktop-global standard font if it's monospace (and the most similar font it can come up with otherwise).
|
|
| ~ |
A Pango font name. Examples are "Sans 12" or "Monospace Bold 14".
|
|
| 2011-06-23 |
A Pango font name. Examples are "Sans 12" or "Monospace Bold 14".
|
|
| ~ |
If true, the external tools will use the desktop-global standard font if it's monospace (and the most similar font it can come up with otherwise).
|
|
| 2011-06-23 |
If true, the external tools will use the desktop-global standard font if it's monospace (and the most similar font it can come up with otherwise).
|
|
| ~ |
The file "%s" was previously saved using compression and will now be saved as plain text.
|
|
| 2011-06-23 |
The file "%s" was previously saved using compression and will now be saved as plain text.
|
|
| ~ |
The file "%s" was previously saved as plain text and will now be saved using compression.
|
|
| 2011-06-23 |
The file "%s" was previously saved as plain text and will now be saved using compression.
|
|
| ~ |
[FILE...] [+LINE[:COLUMN]]
|
|
| 2011-06-23 |
[FILE...] [+LINE[:COLUMN]]
|
|
| ~ |
Specifies how the cursor moves when the HOME and END keys are pressed. Use "disabled" to always move at the start/end of the line, "after" to move to the start/end of the line the first time the keys are pressed and to the start/end of the text ignoring whitespaces the second time the keys are pressed, "before" to move to the start/end of the text before moving to the start/end of the line and "always" to always move to the start/end of the text instead of the start/end of the line.
|
|
| 2011-06-23 |
Specifies how the cursor moves when the HOME and END keys are pressed. Use "disabled" to always move at the start/end of the line, "after" to move to the start/end of the line the first time the keys are pressed and to the start/end of the text ignoring whitespaces the second time the keys are pressed, "before" to move to the start/end of the text before moving to the start/end of the line and "always" to always move to the start/end of the text instead of the start/end of the line.
|
|
| ~ |
Specifies how to wrap long lines for printing. Use "none" for no wrapping, "word" for wrapping at word boundaries, and "char" for wrapping at individual character boundaries. Note that the values are case-sensitive, so make sure they appear exactly as mentioned here.
|
|
| 2011-06-23 |
Specifies how to wrap long lines for printing. Use "none" for no wrapping, "word" for wrapping at word boundaries, and "char" for wrapping at individual character boundaries. Note that the values are case-sensitive, so make sure they appear exactly as mentioned here.
|
|
| ~ |
Specifies when to show the notebook tabs. Use "never" to never show the tabs, "always" to always show the tabs, and "auto" to show the tabs only when there is more than one tab. Note that the values are case-sensitive, so make sure they appear exactly as mentioned here.
|
|
| 2011-06-23 |
Specifies when to show the notebook tabs. Use "never" to never show the tabs, "always" to always show the tabs, and "auto" to show the tabs only when there is more than one tab. Note that the values are case-sensitive, so make sure they appear exactly as mentioned here.
|
|
| ~ |
Specifies how to wrap long lines in the editing area. Use "none" for no wrapping, "word" for wrapping at word boundaries, and "char" for wrapping at individual character boundaries. Note that the values are case-sensitive, so make sure they appear exactly as mentioned here.
|
|
| 2011-06-23 |
Specifies how to wrap long lines in the editing area. Use "none" for no wrapping, "word" for wrapping at word boundaries, and "char" for wrapping at individual character boundaries. Note that the values are case-sensitive, so make sure they appear exactly as mentioned here.
|
|
| 39. |
Highlight Matching Brackets
|
|
| 2011-06-23 |
Highlight Matching Brackets
|
|
| 40. |
Whether gedit should highlight matching brackets.
|
|
| 2011-06-23 |
Whether gedit should highlight matching brackets.
|
|
| 61. |
Notebook Show Tabs Mode
|
|
| 2011-06-23 |
Notebook Show Tabs Mode
|
|
| 65. |
Side panel is Visible
|
|
| 2011-06-23 |
Side panel is Visible
|
|
| 66. |
Whether the side panel at the left of editing windows should be visible.
|
|
| 2011-06-23 |
Whether the side panel at the left of editing windows should be visible.
|
|
| 104. |
Open files and block process until files are closed
|
|
| 2011-06-23 |
Open files and block process until files are closed
|
|
| 105. |
Run gedit in standalone mode
|
|
| 2011-06-23 |
Run gedit in standalone mode
|
|
| 135. |
Save the file using compression?
|
|
| 2011-06-23 |
Save the file using compression?
|
|
| 136. |
Save the file as plain text?
|
|
| 2011-06-23 |
Save the file as plain text?
|
|
| 138. |
_Save Using Compression
|
|
| 2011-06-23 |
_Save Using Compression
|
|
| 140. |
_Save As Plain Text
|
|
| 2011-06-23 |
_Save As Plain Text
|
|
| 203. |
The file you opened has some invalid characters. If you continue editing this file you could corrupt this document.
|
|
| 2011-06-23 |
The file you opened has some invalid characters. If you continue editing this file you could corrupt this document.
|
|
| 234. |
If you continue saving this file you can corrupt the document. Save anyway?
|
|
| 2011-06-23 |
If you continue saving this file you can corrupt the document. Save anyway?
|
|
| 280. |
Bracket match is out of range
|
|
| 2011-06-23 |
Bracket match is out of range
|
|
| 281. |
Bracket match not found
|
|
| 2011-06-23 |
Bracket match not found
|
|
| 282. |
Bracket match found on line: %d
|
|
| 2011-06-23 |
Bracket match found on line: %d
|
|
| 318. |
Side _Panel
|
|
| 2011-06-23 |
Side _Panel
|
|
| 319. |
_Bottom Panel
|
|
| 2011-06-23 |
_Bottom Panel
|
|
| 333. |
_New Tab Group
|
|
| 2011-06-23 |
_New Tab Group
|
|
| 334. |
P_revious Tab Group
|
|
| 2011-06-23 |
P_revious Tab Group
|
|
| 335. |
Nex_t Tab Group
|
|
| 2011-06-23 |
Nex_t Tab Group
|
|
| 337. |
N_ext Document
|
|
| 2011-06-23 |
N_ext Document
|
|
| 360. |
Display right _margin at column:
|
|
| 2011-06-23 |
Display right _margin at column:
|
|
| 367. |
Highlighting
|
|
| 2011-06-23 |
Highlighting
|
|
| 369. |
Highlight matching _brackets
|
|
| 2011-06-23 |
Highlight matching _brackets
|
|
| 384. |
Install Scheme
|
|
| 2012-02-23 |
Install Scheme
|
|
| 386. |
Uninstall Scheme
|
|
| 2012-02-23 |
Uninstall Scheme
|
|
| 494. |
Version to Ignore
|
|
| 2011-06-23 |
Version to Ignore
|
|
| 495. |
Version to ignore until a newer version is released.
|
|
| 2011-06-23 |
Version to ignore until a newer version is released.
|
|
| 518. |
Whether to use the system font
|
|
| 2011-06-23 |
Whether to use the system font
|
|
| 566. |
File Browser Panel
|
|
| 2011-06-23 |
File Browser Panel
|
|
| 567. |
Easy file access from the side panel
|
|
| 2011-06-23 |
Easy file access from the side panel
|
|
| 607. |
This value determines what files get filtered from the file browser. Valid values are: none (filter nothing), hide-hidden (filter hidden files) and hide-binary (filter binary files).
|
|
| 2011-06-23 |
This value determines what files get filtered from the file browser. Valid values are: none (filter nothing), hide-hidden (filter hidden files) and hide-binary (filter binary files).
|
|
| 628. |
Command Color Text
|
|
| 2011-06-23 |
Command Colour Text
|
|
| 629. |
The command color text
|
|
| 2011-06-23 |
The command colour text
|
|
| 630. |
Error Color Text
|
|
| 2011-06-23 |
Error Colour Text
|
|
| 631. |
The error color text
|
|
| 2011-06-23 |
The error colour text
|
|
| 657. |
This is not a valid Tab trigger. Triggers can either contain alphanumeric characters (or _, : and .) or a single (non-alphanumeric) character like: {, [, etc.
|
|
| 2012-09-22 |
This is not a valid Tab trigger. Triggers can either contain alphanumeric characters (or _, : and .) or a single (non-alphanumeric) character like: {, [, etc.
|
|
| 700. |
_Highlight Misspelled Words
|
|
| 2011-06-23 |
_Highlight Misspelt Words
|
|
| 705. |
Prompt Type
|
|
| 2011-06-23 |
Prompt Type
|
|
