Translations by Joel Pickett
Joel Pickett has submitted the following strings to this translation. Contributions are visually coded: currently used translations, unreviewed suggestions, rejected suggestions.
| 1 → 7 of 7 results | First • Previous • Next • Last |
| 6. |
<p>With this option activated, only one instance of Konqueror used for file browsing will exist in the memory of your computer at any moment, no matter how many file browsing windows you open, thus reducing resource requirements.</p><p>Be aware that this also means that, if something goes wrong, all your file browsing windows will be closed simultaneously</p>
|
|
| 2011-05-22 |
<p>With this option activated, only one instance of Konqueror used for file browsing will exist in the memory of your computer at any moment, no matter how many file browsing windows you open, thus reducing resource requirements.</p><p>Be aware that this also means that, if something goes wrong, all your file browsing windows will be closed simultaneously</p>
|
|
| 7. |
<p>With this option activated, only one instance of Konqueror will exist in the memory of your computer at any moment, no matter how many browsing windows you open, thus reducing resource requirements.</p><p>Be aware that this also means that, if something goes wrong, all your browsing windows will be closed simultaneously.</p>
|
|
| 2011-05-22 |
<p>With this option activated, only one instance of Konqueror will exist in the memory of your computer at any moment, no matter how many browsing windows you open, thus reducing resource requirements.</p><p>Be aware that this also means that, if something goes wrong, all your browsing windows will be closed simultaneously.</p>
|
|
| 8. |
<p>If non-zero, this option allows keeping Konqueror instances in memory after all their windows have been closed, up to the number specified in this option.</p><p>When a new Konqueror instance is needed, one of these preloaded instances will be reused instead, improving responsiveness at the expense of the memory required by the preloaded instances.</p>
|
|
| 2011-05-22 |
<p>If non-zero, this option allows keeping Konqueror instances in memory after all their windows have been closed, up to the number specified in this option.</p><p>When a new Konqueror instance is needed, one of these preloaded instances will be reused instead, improving responsiveness at the expense of the memory required by the preloaded instances.</p>
|
|
| 9. |
<p>If enabled, an instance of Konqueror will be preloaded after the ordinary KDE startup sequence.</p><p>This will make the first Konqueror window open faster, but at the expense of longer KDE startup times (but you will be able to work while it is loading, so you may not even notice that it is taking longer).</p>
|
|
| 2011-05-22 |
<p>If enabled, an instance of Konqueror will be preloaded after the ordinary KDE startup sequence.</p><p>This will make the first Konqueror window open faster, but at the expense of longer KDE startup times (but you will be able to work while it is loading, so you may not even notice that it is taking longer).</p>
|
|
| 10. |
<p>If enabled, KDE will always try to have one preloaded Konqueror instance ready; preloading a new instance in the background whenever there is not one available, so that windows will always open quickly.</p><p><b>Warning:</b> In some cases, it is actually possible that this will reduce perceived performance.</p>
|
|
| 2011-05-22 |
<p>If enabled, KDE will always try to have one preloaded Konqueror instance ready; preloading a new instance in the background whenever there is not one available, so that windows will always open quickly.</p><p><b>Warning:</b> In some cases, it is actually possible that this will reduce perceived performance.</p>
|
|
| 21. |
This option may in rare cases lead to various problems. Consult the What's This (Shift+F1) help for details.
|
|
| 2011-05-22 |
This option may in rare cases lead to various problems. Consult the What's This (Shift+F1) help for details.
|
|
| 22. |
<p>During startup KDE needs to perform a check of its system configuration (mimetypes, installed applications, etc.), and in case the configuration has changed since the last time, the system configuration cache (KSyCoCa) needs to be updated.</p><p>This option delays the check, which avoid scanning all directories containing files describing the system during KDE startup, thus making KDE startup faster. However, in the rare case the system configuration has changed since the last time, and the change is needed before this delayed check takes place, this option may lead to various problems (missing applications in the K Menu, reports from applications about missing required mimetypes, etc.).</p><p>Changes of system configuration mostly happen by (un)installing applications. It is therefore recommended to turn this option temporarily off while (un)installing applications.</p>
|
|
| 2011-05-22 |
<p>During startup KDE needs to perform a check of its system configuration (mimetypes, installed applications, etc.), and in case the configuration has changed since the last time, the system configuration cache (KSyCoCa) needs to be updated.</p><p>This option delays the check, which avoid scanning all directories containing files describing the system during KDE startup, thus making KDE startup faster. However, in the rare case the system configuration has changed since the last time, and the change is needed before this delayed check takes place, this option may lead to various problems (missing applications in the K Menu, reports from applications about missing required mimetypes, etc.).</p><p>Changes of system configuration mostly happen by (un)installing applications. It is therefore recommended to turn this option temporarily off while (un)installing applications.</p>
|
|
