"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. Tag: title
-#. +> trunk5 stable5
+#. +> trunk5
+#: index.docbook:10
+#, no-c-format
+msgid "General Behavior"
+msgstr ""
+
+#. Tag: title
+#. +> stable5
#: index.docbook:10
#, no-c-format
msgid "Workspace Behaviour"
msgstr ""
#. Tag: author
#. +> trunk5 stable5
#: index.docbook:12
#, no-c-format
msgid "&Burkhard.Lueck; &Burkhard.Lueck.mail;"
msgstr ""
#. Tag: trans_comment
#. +> trunk5 stable5
#: index.docbook:13
#, no-c-format
msgid "ROLES_OF_TRANSLATORS"
msgstr ""
#. Tag: date
-#. +> trunk5 stable5
+#. +> trunk5
+#: index.docbook:16
+#, no-c-format
+msgid "2019-08-01"
+msgstr ""
+
+#. Tag: date
+#. +> stable5
#: index.docbook:16
#, no-c-format
msgid "2018-05-21"
msgstr ""
#. Tag: releaseinfo
-#. +> trunk5 stable5
+#. +> trunk5
+#: index.docbook:18
+#, no-c-format
+msgid "&plasma; 5.16"
+msgstr ""
+
+#. Tag: releaseinfo
+#. +> stable5
#: index.docbook:18
#, no-c-format
msgid "&plasma; 5.13"
msgstr ""
#. Tag: keyword
#. +> trunk5 stable5
#: index.docbook:21
#, no-c-format
msgid "System Settings"
msgstr ""
#. Tag: keyword
#. +> trunk5 stable5
#: index.docbook:22
#, no-c-format
msgid "desktop"
msgstr ""
#. Tag: keyword
#. +> trunk5 stable5
#: index.docbook:23
#, no-c-format
msgid "workspace"
msgstr ""
#. Tag: para
-#. +> trunk5 stable5
+#. +> trunk5
+#: index.docbook:28
+#, no-c-format
+msgid "This is a module to configure general workspace behavior."
+msgstr ""
+
+#. Tag: para
+#. +> stable5
#: index.docbook:28
#, no-c-format
msgid "This is a module to configure global options for the &plasma; workspace."
msgstr ""
#. Tag: guilabel
#. +> trunk5 stable5
#: index.docbook:34
#, no-c-format
msgid "Display informational tooltips on mouse hover"
msgstr ""
#. Tag: para
#. +> trunk5 stable5
#: index.docbook:36
#, no-c-format
msgid "If this option is checked, tooltips are displayed hovering items in the &plasma; panel or on the desktop."
msgstr ""
#. Tag: guilabel
#. +> trunk5 stable5
#: index.docbook:42
#, no-c-format
msgid "Display visual feedback for status changes"
msgstr ""
#. Tag: para
#. +> trunk5 stable5
#: index.docbook:44
#, no-c-format
msgid "If you change ⪚ brightness and volume using the keyboard these status changes are displayed in an OSD."
msgstr ""
#. Tag: guilabel
#. +> trunk5 stable5
#: index.docbook:50
#, no-c-format
msgid "Single-click to open files and folders"
msgstr ""
#. Tag: para
#. +> trunk5 stable5
#: index.docbook:52
#, no-c-format
msgid "This is the default setting. Clicking once on an icon will open it. To select you can drag around the icon(s) or <keycombo action=\"simul\">&Ctrl;<mousebutton>Right</mousebutton></keycombo> click, or simply click and hold to drag it."
msgstr ""
#. Tag: guilabel
#. +> trunk5 stable5
#: index.docbook:60
#, no-c-format
msgid "Double-click to open files and folders (select icons on first click)"
msgstr ""
#. Tag: para
#. +> trunk5 stable5
#: index.docbook:62
#, no-c-format
msgid "If this option is not checked, icons/files will be opened with a single click of the <mousebutton>left</mousebutton> mouse-button. This default behavior is consistent with what you would expect when you click links in most web browsers. If checked however, icons/files will be opened with a double click, while a single click will only select the icon or file. This is the behavior you may know from other desktops or operating systems."
msgid "To import an existing data file, enter its filename here. You will then describe the contents of the file below. You can leave the filename blank to construct a catalog file with a valid header, but no data."
"This button will compute the field-of-view (FOV) angle for a specific eyepiece/telescope combination. You must first specify the focal lengths of the telescope and eyepiece, and the FOV angle of the eyepiece in the above entry fields.\n"
"\n"
"The computed FOV angle (in arcminutes) will be displayed in the \"Field of view\" edit box."
"Enter the telescope focal length, in millimeters.\n"
"\n"
"This is one of the data fields required for defining a field-of-view (FOV) symbol which matches the field-of-view of a camera mounted on a telescope."
"Enter the physical size of the CCD chip or film negative.\n"
"\n"
"This is one of the data fields required for defining a field-of-view (FOV) symbol which matches the field-of-view of a camera mounted on a telescope."
"This button will compute the field-of-view (FOV) angle for a specific camera/telescope combination. You must first specify the focal length of the telescope and the size of the CCD chip or film negative.\n"
"\n"
"The computed FOV angle (in arcminutes) will be displayed in the \"Field of view\" edit box."
"This button will compute the Half Power Beam Width (HPBW) angle for a specific radiotelescope and observing wavelength combination, assuming no multibeam receiver is available at the telescope. You must first specify the diameter of the radiotelescope and the observing wavelength.\n"
"\n"
"The computed HPBW angle (in arcminutes) will be displayed in the \"Field of view\" edit box."
msgid "<p>Frame rotation with respect to Celestial Pole. Zero degrees indicates that <b>UP</b> is pointing directly at the pole. 90 degrees indicates that <b>UP</b> is rotated 90 degrees clockwise with respect to the pole.</p>"
msgid "Your data directory was not found. You can click the button below to copy a default KStars data directory to the correct location, or if you have a KStars directory already some place else, you can exit KStars and copy it to that location yourself."
msgid "Installing this in your data directory will enable the CCD Simulator in KStars to take realistic images. This is useful for testing sequences, plate solving, and learning to use KStars. Just click the button to install or unzip the zip file and place the gsc folder in the data directory."
"<p>You may now download optional data files to enhance KStars, such as Messier object images, or a more complete NGC/IC catalog. Press the <b>Download Extra Data</b> button to proceed. </p>"
"<p>You can also use this tool later, by selecting <b>Download New Data</b> from the <b>File</b> menu.</p>"
msgid "Are you sure you want to clear all of the solution points?"
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:1533
+#: ekos/align/align.cpp:1534
#, kde-format
msgid "Clear Solution Points"
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:1541
+#: ekos/align/align.cpp:1542
#, kde-format
msgid "Are you sure you want to clear all the alignment points?"
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:1542
+#: ekos/align/align.cpp:1543
#, kde-format
msgid "Clear Align Points"
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:1687
+#: ekos/align/align.cpp:1688
#, kde-format
msgid "The Mount Model Tool is Reset."
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:1724
+#: ekos/align/align.cpp:1725
#, kde-format
msgid "Please Check the Alignment Points."
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:1731
+#: ekos/align/align.cpp:1732
#, kde-format
msgid "In the Align Module, \"Nothing\" is Selected for the Solver Action. This means that the mount model tool will not sync/align your mount but will only report the pointing model errors. Do you wish to continue?"
msgid "Astrometry.net uses python3 and the astropy package for plate solving images offline. These were not detected on your system. Please go into the Align Options and either click the setup button to install them or uncheck the default button and enter the path to python3 on your system and manually install astropy."
msgid "Blind solver takes a very long time to solve but can reliably solve any image any where in the sky given enough time."
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:2938
+#: ekos/align/align.cpp:2939
#, kde-format
msgid "Use existing settings"
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:2939
+#: ekos/align/align.cpp:2940
#, kde-format
msgid "Mount must be pointing close to the target location and current field of view must match the image's field of view."
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:2943
+#: ekos/align/align.cpp:2944
#, kde-format
msgid "No metadata is available in this image. Do you want to use the blind solver or the existing solver settings?"
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:2945
+#: ekos/align/align.cpp:2946
#, kde-format
msgid "Astrometry solver"
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:3002
+#: ekos/align/align.cpp:3003
#, kde-format
msgid "Solver iteration #%1"
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:3040
+#: ekos/align/align.cpp:3041
#, kde-format
msgid "Solver RA (%1) DEC (%2) Orientation (%3) Pixel Scale (%4)"
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:3049
+#: ekos/align/align.cpp:3050
#, kde-format
msgid "Current focal length is %1 mm while computed focal length from the solver is %2 mm. Please update the mount focal length to obtain accurate results."
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:3176
+#: ekos/align/align.cpp:3177
#, kde-format
msgid "WCS information updated. Images captured from this point forward shall have valid WCS."
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:3194
+#: ekos/align/align.cpp:3195
#, kde-format
msgid "Solution coordinates: RA (%1) DEC (%2) Telescope Coordinates: RA (%3) DEC (%4)"
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:3200
+#: ekos/align/align.cpp:3201
#, kde-format
msgid "Target is within %1 degrees of solution coordinates."
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:3256
+#: ekos/align/align.cpp:3257
#, kde-format
msgid "Setting position angle to %1 degrees E of N..."
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:3293
+#: ekos/align/align.cpp:3294
#, kde-format
msgid "Maximum number of iterations reached. Solver failed."
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:3325
+#: ekos/align/align.cpp:3326
#, kde-format
msgid "Target is within acceptable range. Astrometric solver is successful."
msgid "Slewing to calibration position, please wait until telescope completes slewing."
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:4467
+#: ekos/align/align.cpp:4468
#, kde-format
msgid "Load Image"
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:4659
+#: ekos/align/align.cpp:4660
#, kde-format
msgid "World Coordinate System (WCS) is enabled. CCD rotation must be set either manually in the CCD driver or by solving an image before proceeding to capture any further images, otherwise the WCS information may be invalid."
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:4668
+#: ekos/align/align.cpp:4669
#, kde-format
msgid "World Coordinate System (WCS) is disabled."
msgid "Failed to process World Coordinate System: %1. Try again."
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:5486
+#: ekos/align/align.cpp:5487
#, kde-format
msgid "Celestial pole is located outside of the field of view. Would you like to sync and slew the telescope to the celestial pole? WARNING: Slewing near poles may cause your mount to end up in unsafe position. Proceed with caution."
msgstr ""
#. +> trunk5
-#: ekos/align/align.cpp:5503
+#: ekos/align/align.cpp:5504
#, kde-format
msgid "Warning: Celestial pole is located outside the field of view. Move the mount closer to the celestial pole."
msgid "Accuracy threshold in arcseconds between solution and target coordinates. Plate solver shall be repeatedly executed until the solution coordinates are below the accuracy threshold"
msgid "<p>Use astrometry solver on remote machine running INDI server. You must select <b>Astrometry</b> driver from Auxiliary drivers in your Ekos devices profile for this option to be enabled.</p>"
msgid "The results from Astrometric Solutions from the Capture and Solve Tool, the Load and Slew Tool, and the Mount Model Tool will be displayed below."
msgid "Remove the selected row from the solutions table. This can be useful for getting rid of results that did not actually solve from the table and/or results that you do not need any more. It can clean up clutter on both the graph and table."
msgid "Launch the mount model tool. This tool enables you to create pre-programmed list of points to go to and solve. It can aid in building a pointing model for better accuracy."
"<p>This tool provides a simple method to polar align a German equatorial mount. <span style=\" font-weight:600;\">Park</span> your mount to home position where it <span style=\" font-weight:600;\">points</span> toward the celestial pole. Select mount direction and speed and then click <span style=\" font-weight:600;\">Start</span> to begin the process.</p>"
msgid "<p>Adjust mount's Altitude and Azimuth knobs until the selected star is centered within the crosshair. Click <b>Refresh</b> to begin continuous capture. You are <b>Done</b> when star is centered.</p>"
msgid "<p>This tool can help your mount build a better pointing model by moving the mount to different points in the sky and solving captured images. This can increase the accuracy of your GOTOs. To qualify, your mount must be capable of improving its internal pointing model after each <b>Sync</b> commanded by Ekos. If this is not the case, then this tool is not suitable for your mount.</p>"
"<p>Select the type of objects/points added by the wizard.</p>"
"<p><span style=\" font-weight:600;\">Note:</span> all of the options except Fixed DEC start with a grid of RA/DEC points.</p>"
"\n"
"<ul>\n"
"<li><b>Any Stars:</b> The wizard searches for the nearest star.</li>"
"\n"
"<li><b>Any object:</b> The wizard searches for the nearest object of any type.</li>"
"\n"
"<li><b>Named Stars</b> The wizard searches for the nearest star in the currently visible star list. Note that the first named star might be fairly far from the intended point and also sometimes the same star could be the closest one for multiple points.</li>"
"\n"
"<li><b>Fixed DEC:</b> The wizard generates all points at the chosen DEC.</li>"
"\n"
"<li><b>Fixed Grid:</b> The wizard just uses the original grid without trying to pair it with objects.</li>"
msgid "Automatically generate the specified number of alignment points in the table below. They will be generated based on the options selected in this wizard."
msgid "The Number of points the wizard should generate. If this number is less than 5, it will generate them at the same DEC. After that they will be evenly distributed over RA and DEC. Note, if Fixed DEC is selected, all of the points will be at the same DEC."
msgid "These are the common names for the named stars that are currently up at your location. If you select a star, it will be added to the table below."
msgid "These are the Greek names for the brighter stars that are currently up at your location. If you select a star, it will be added to the table below."
msgid "Clear the entire table of alignment points below. Note that this will not affect your mount in any way. It will not clear your pointing model. It just clears the list of points so that if you run the mount model routine again, these points will not be included."
msgid "<p>Remove the selected row from the alignment point table below. Note that it does <b>not</b> command your mount to clear that point from the model, it just means that if you run the mount model routine, that point will not be included in the list.</p>"
msgid "Add an empty row to the alignment list so that you can manually add an RA and DE for a position you would like the telescope to slew to when doing the mount model routine."
msgid "Open the Find Object dialog so that you can select an object to get an RA and DEC automatically that you would like the telescope to slew to when doing the mount model routine."
msgid "Sort the alignment points, starting with the point closest to the current telescope position, to try to minimize the distance between each slew."
msgid "This is a table of alignment points that you would like the mount model routine to use in aligning your telescope. If you would like to add or remove points, you may use the buttons above. If you would like to run, pause, or stop the mount model routine, you may use the buttons below. You can directly edit an RA or DE for a particular point directly in the cells. Just be sure to follow the format hh:mm:ss. The object name is just provided for convenience and is not used. If you want to change the order of the alignment points, you can drag the row up or down using the vertical header for that row on the left."
msgid "Start or pause the mount model routine. It will slew to and astrometrically solve the list of points in the table above using the settings in the align module. If the routine was previously paused, it will pick up where it left off. If it was stopped or it had finished it will start the routine over again."
msgid "<p>Stop the mount model routine. It will <b>not</b> clear any points from your telescope's pointing model. It will stop the routine and any points currently being solved. If you run the mount model again after hitting stop, it will start the routine over again with the first point.</p>"
msgstr ""
#. +> trunk5
#: ekos/align/offlineastrometryparser.cpp:62
#, kde-format
msgid "Failed to properly configure astrometry config file. Please click the options button in the lower right of the Astrometry Tab in Ekos to correct your settings. Then try starting Ekos again."
msgstr ""
#. +> trunk5
#: ekos/align/offlineastrometryparser.cpp:63
#, kde-format
msgid "Astrometry Config File Error"
msgstr ""
#. +> trunk5
#: ekos/align/offlineastrometryparser.cpp:78
#, kde-format
msgid "Failed to find astrometry.net binaries. Please click the options button in the lower right of the Astrometry Tab in Ekos to correct your settings and make sure that astrometry.net is installed. Then try starting Ekos again."
msgstr ""
#. +> trunk5
#: ekos/align/offlineastrometryparser.cpp:79
#, kde-format
msgid "Missing astrometry files"
msgstr ""
#. +> trunk5
#: ekos/align/offlineastrometryparser.cpp:105
#, kde-format
msgid "Detected Astrometry.net version %1"
msgstr ""
#. +> trunk5
#: ekos/align/offlineastrometryparser.cpp:110
#, kde-format
msgid "Setting astrometry option --no-fits2fits"
msgstr ""
#. +> trunk5
#: ekos/align/offlineastrometryparser.cpp:115
#, kde-format
msgid "Turning off option --no-fits2fits"
msgstr ""
#. +> trunk5
#: ekos/align/offlineastrometryparser.cpp:215
#, kde-format
msgid "Index file %1 is missing. Astrometry.net would not be able to adequately solve plates until you install the missing index files. Download the index files from http://www.astrometry.net"
msgstr ""
#. +> trunk5
#: ekos/align/offlineastrometryparser.cpp:219
#, kde-format
msgid "Index files %1 to %2 are missing. Astrometry.net would not be able to adequately solve plates until you install the missing index files. Download the index files from http://www.astrometry.net"
msgstr ""
#. +> trunk5
#: ekos/align/offlineastrometryparser.cpp:328
#, kde-format
msgid "Error starting solver: %1"
msgstr ""
#. +> trunk5
#: ekos/align/offlineastrometryparser.cpp:346
#, kde-format
msgid "Starting solver..."
msgstr ""
#. +> trunk5
#: ekos/align/offlineastrometryparser.cpp:385
#: ekos/align/remoteastrometryparser.cpp:245
#, kde-format
msgid "Solver failed. Try again."
msgstr ""
#. +> trunk5
#: ekos/align/offlineastrometryparser.cpp:409
#, kde-format
msgid "WCS header missing or corrupted. Solver failed."
msgstr ""
#. +> trunk5
#: ekos/align/offlineastrometryparser.cpp:442
#: ekos/align/onlineastrometryparser.cpp:493
#: ekos/align/remoteastrometryparser.cpp:287
#, kde-format
msgid "Solver completed in %1 second."
msgid_plural "Solver completed in %1 seconds."
msgstr[0] ""
msgstr[1] ""
#. +> trunk5
#: ekos/align/onlineastrometryparser.cpp:82
#, kde-format
msgid "Error: no connection to the Internet."
msgstr ""
#. +> trunk5
#: ekos/align/onlineastrometryparser.cpp:197
#, kde-format
msgid "Failed to open the file %1: %2"
msgstr ""
#. +> trunk5
#: ekos/align/onlineastrometryparser.cpp:268
#, kde-format
msgid "Uploading file..."
msgstr ""
#. +> trunk5
#: ekos/align/onlineastrometryparser.cpp:341
#, kde-format
msgid "JSON error during parsing (%1)."
msgstr ""
#. +> trunk5
#: ekos/align/onlineastrometryparser.cpp:359
#, kde-format
msgid "Astrometry.net authentication failed. Check the validity of the Astrometry.net API Key."
msgstr ""
#. +> trunk5
#: ekos/align/onlineastrometryparser.cpp:367
#, kde-format
msgid "Authentication to astrometry.net is successful. Session: %1"
msgstr ""
#. +> trunk5
#: ekos/align/onlineastrometryparser.cpp:376
#, kde-format
msgid "Upload failed."
msgstr ""
#. +> trunk5
#: ekos/align/onlineastrometryparser.cpp:385
#, kde-format
msgid "Parsing submission ID failed."
msgstr ""
#. +> trunk5
#: ekos/align/onlineastrometryparser.cpp:390
#, kde-format
msgid "Upload complete. Waiting for astrometry.net solver to complete..."
msgstr ""
#. +> trunk5
#: ekos/align/onlineastrometryparser.cpp:413
#, kde-format
msgid "Failed to retrieve job ID."
msgstr ""
#. +> trunk5
#: ekos/align/onlineastrometryparser.cpp:447
#, kde-format
msgid "Solver failed after %1 second."
msgid_plural "Solver failed after %1 seconds."
msgstr[0] ""
msgstr[1] ""
#. +> trunk5
#: ekos/align/onlineastrometryparser.cpp:457
#, kde-format
msgid "Error parsing parity."
msgstr ""
#. +> trunk5
#: ekos/align/onlineastrometryparser.cpp:464
#, kde-format
msgid "Error parsing orientation."
msgstr ""
#. +> trunk5
#: ekos/align/onlineastrometryparser.cpp:472
#, kde-format
msgid "Error parsing RA."
msgstr ""
#. +> trunk5
#: ekos/align/onlineastrometryparser.cpp:479
#: ekos/align/onlineastrometryparser.cpp:487
#, kde-format
msgid "Error parsing DEC."
msgstr ""
#. +> trunk5
#: ekos/align/opsalign.cpp:39
#, kde-format
msgid "Internal or External Plate Solver?"
msgstr ""
#. +> trunk5
#: ekos/align/opsalign.cpp:44
#, kde-format
msgid "Internal or External astrometry.cfg?"
msgstr ""
#. i18n: ectx: label, entry (AstrometryWCSIsInternal), group (Align)
#. +> trunk5
#: ekos/align/opsalign.cpp:49 kstars.kcfg:1942
#, kde-format
msgid "Internal or External wcsinfo?"
msgstr ""
#. +> trunk5
#: ekos/align/opsalign.cpp:80
#, kde-format
msgid "Homebrew, python, and astropy are already installed"
msgstr ""
#. +> trunk5
#: ekos/align/opsalign.cpp:84
#, kde-format
msgid ""
"This installer will install the following requirements for astrometry.net if they are not installed:\n"
"Homebrew -an OS X Unix Program Package Manager\n"
"Python3 -A Powerful Scripting Language \n"
"Astropy -Python Modules for Astronomy \n"
" Do you wish to continue?"
msgstr ""
#. +> trunk5
#: ekos/align/opsalign.cpp:85
#, kde-format
msgid "Install and Configure Python"
msgstr ""
#. +> trunk5
#: ekos/align/opsalign.cpp:95
#, kde-format
msgid ""
"Homebrew is not installed. \n"
"A Terminal window will pop up for you to install Homebrew. \n"
" When you are all done, then you can close the Terminal and click the setup button again."
msgstr ""
#. +> trunk5
#: ekos/align/opsalign.cpp:117
#, kde-format
msgid ""
"Homebrew installed \n"
"Python3 will install when you click Ok \n"
"Astropy waiting . . . \n"
" (Note: this might take a few minutes, please be patient.)"
msgstr ""
#. +> trunk5
#: ekos/align/opsalign.cpp:122
#, kde-format
msgid "Python install failure"
msgstr ""
#. +> trunk5
#: ekos/align/opsalign.cpp:128
#, kde-format
msgid ""
"Homebrew installed \n"
"Python3 installed \n"
"Astropy will install when you click Ok \n"
" (Note: this might take a few minutes, please be patient.)"
msgstr ""
#. +> trunk5
#: ekos/align/opsalign.cpp:133
#, kde-format
msgid "Astropy install failure"
msgstr ""
#. +> trunk5
#: ekos/align/opsalign.cpp:137
#, kde-format
msgid "All installations are complete and ready to use."
"<p>Rotator threshold in arc-minutes when using Load & Slew. If the difference between measured position angle and FITS position angle is below this value, the Load & Slew operation is considered successful.</p>"
"<p>On Load & Slew, solve the image and slew the mount to the target location and then rotate the camera to match the orientation of the FITS image.</p>"
"<p>Automatically park mount after completing Polar Alignment Assistant Tools. Beware that turning this option off might lead to inaccurate results.</p>"
msgid "This will prevent the solver from looking at an already existing WCS Header before blindly trying to solve the image. It is recommended to keep it checked."
msgid "Do not use Sync when Slew to Target is selected. Use differential slewing to correct for discrepancies. This is useful on some mounts (e.g. Paramount)."
"<p><span style=\" font-weight:600;\">Offline</span> astrometry.net solver requires index files in order to solve an image. Please see the Astrometrty.net <a href=\"http://astrometry.net/doc/readme.html\"><span style=\" text-decoration: underline; color:#0000ff;\">README</span></a> for details. The following list provides a complete list of the index files, along with recommended index files to install given the current CCD Field of View. Installed index files are checked. Next to each index file is an icon that represents the following:</p>"
"<p>This button will open the Astrometry Index File folder on your filesystem so that you can see where it is located and copy files into it if needed.</p>"
"<p>Enable Logs to diagnose issues with Ekos and INDI. Only enable the necessary logs to help in diagnosing specific problems. Logs consume resources and may slow the system down. Turn off logs when no longer used.</p>"
msgid "To assign a permanent designation to the device, you need to unplug the device from stellarmate then replug it after 1 second. Click on the <b>Start Scan</b> to begin this procedure."
msgstr ""
#. +> trunk5
#: ekos/auxiliary/serialportassistant.cpp:91
#, kde-format
msgid "Start Scan"
msgstr ""
#. +> trunk5
#: ekos/auxiliary/serialportassistant.cpp:94
#, kde-format
msgid "Home"
msgstr ""
#. +> trunk5
#: ekos/auxiliary/serialportassistant.cpp:99
#, kde-format
msgid "Skip Device"
msgstr ""
#. +> trunk5
#: ekos/auxiliary/serialportassistant.cpp:103
#, kde-format
msgid "Physical Port Mapping"
msgstr ""
#. +> trunk5
#: ekos/auxiliary/serialportassistant.cpp:105
#, kde-format
msgid "Assign the permanent name based on which physical port the device is plugged to in StellarMate. This is useful to distinguish between two identical USB adapters. The device must <b>always</b> be plugged into the same port for this to work."
msgstr ""
#. +> trunk5
#: ekos/auxiliary/serialportassistant.cpp:142
#, kde-format
msgid "Standby, Scanning..."
msgstr ""
#. +> trunk5
#: ekos/auxiliary/serialportassistant.cpp:180
#, kde-format
msgctxt "Vendor ID"
msgid "VID"
msgstr ""
#. +> trunk5
#: ekos/auxiliary/serialportassistant.cpp:181
#, kde-format
msgctxt "Product ID"
msgid "PID"
msgstr ""
#. +> trunk5
#: ekos/auxiliary/serialportassistant.cpp:182
#, kde-format
msgid "Link"
msgstr ""
#. +> trunk5
#: ekos/auxiliary/serialportassistant.cpp:183
#, kde-format
msgid "Serial #"
msgstr ""
#. +> trunk5
#: ekos/auxiliary/serialportassistant.cpp:184
#, kde-format
msgid "Hardware Port?"
msgstr ""
#. +> trunk5
#: ekos/auxiliary/serialportassistant.cpp:241
#, kde-format
msgid "Start Scanning"
msgstr ""
#. +> trunk5
#: ekos/auxiliary/serialportassistant.cpp:268
#, kde-format
msgid "Failed to scan devices."
msgstr ""
#. +> trunk5
#: ekos/auxiliary/serialportassistant.cpp:276
#: ekos/auxiliary/serialportassistant.cpp:286
#, kde-format
msgid "Failed to detect any devices. Please make sure device is powered and connected to StellarMate via USB."
msgstr ""
#. +> trunk5
#: ekos/auxiliary/serialportassistant.cpp:324
#, kde-format
msgid "Duplicate devices detected. You must remove one mapping or enable hardware slot mapping."
msgstr ""
#. +> trunk5
#: ekos/auxiliary/serialportassistant.cpp:343
#, kde-format
msgid "Mapping is successful. Please unplug and replug your device again now."
"<p>This tool shall assign <span style=\" font-style:italic;\">permanent</span> names to your <span style=\" font-weight:600;\">Serial to USB</span> devices so that they are easier to connect to in the future.</p>"
"<p><br/>"
"</p>"
"<p>Click <span style=\" font-weight:600;\">Next</span> to continue.</p>"
"<p>Accept ADU values that fall within this range around the desired ADU target. For example, if the ADU value was set to 10000 and the tolerance was set to 100, then frames with ADU values f 9900 and 10100 shall be accepted.</p>"
msgid "Meridian flip configuration has been shifted to the mount module. Please configure the meridian flip there."
msgstr ""
#. +> trunk5
-#: ekos/capture/capture.cpp:3801
+#: ekos/capture/capture.cpp:3803
#, kde-format
msgid "Save Ekos Sequence Queue"
msgstr ""
#. +> trunk5
-#: ekos/capture/capture.cpp:3831
+#: ekos/capture/capture.cpp:3833
#, kde-format
msgid "Failed to save sequence queue"
msgstr ""
#. +> trunk5
-#: ekos/capture/capture.cpp:3865
+#: ekos/capture/capture.cpp:3867
#, kde-format
msgid "Could not open file"
msgstr ""
#. +> trunk5
-#: ekos/capture/capture.cpp:3885
+#: ekos/capture/capture.cpp:3887
#, kde-format
msgid "Warning: HFR-based autofocus is set but option \"Save Sequence HFR Value to File\" is not enabled. Current HFR value will not be written to sequence file."
msgstr ""
#. +> trunk5
-#: ekos/capture/capture.cpp:3992
+#: ekos/capture/capture.cpp:3994
#, kde-format
msgid "Sequence queue saved to %1"
msgstr ""
#. +> trunk5
-#: ekos/capture/capture.cpp:4012
+#: ekos/capture/capture.cpp:4014
#, kde-format
msgid "Are you sure you want to reset status of all jobs?"
#. i18n("Ekos will refocus in %1 seconds, last procedure was %2 seconds ago.", refocusEveryNTimer.elapsed()/1000-refocusEveryNTimer.elapsed()*60, refocusEveryNTimer.elapsed()/1000));
#. +> trunk5
-#: ekos/capture/capture.cpp:6038
+#: ekos/capture/capture.cpp:6048
#, kde-format
msgid "Ekos will refocus in %1 seconds, last procedure was %2 seconds ago."
msgstr ""
#. +> trunk5
-#: ekos/capture/capture.cpp:6042
+#: ekos/capture/capture.cpp:6052
#, kde-format
msgid "Ekos will refocus as soon as possible, last procedure was %1 seconds ago."
"<li><strong>Client</strong>: Captured images are only uploaded to Ekos.</li>"
"\n"
"<li><strong>Local</strong>: Captured images are only saved locally on the remote computer.</li>"
"\n"
"<li><strong>Both</strong>: Captured images are saved on remote device <b>and</b> uploaded to Ekos.</li>"
"\n"
"</ol>"
"\n"
"<p>When selecting <i>Local</i> or <i>Both</i>, you must specify the remote directory where the remote images are saved to. By default, all captured images are uploaded to Ekos."
"<p>Select custom properties to be set when the sequence job is executed in batch mode. After the desired property value is set in INDI Control Panel, add it to the<span style=\" font-weight:600;\"> Job Properties</span> section. Click <span style=\" font-weight:600;\">Apply</span> to record the property values.</p>"
"<p>Please fill the required information below. This is a one-time setup. You can obtain these values from your camera manual or from online sources such as <a href=\"http://www.digicamdb.com/\"><span style=\" text-decoration: underline; color:#007af4;\">Digital Camera Database</span></a>.</p>"
"<p>Position Angle (PA) is defined as degrees E of N. Zero degrees indicate frame <span style=\" font-weight:600;\">UP</span> points directly toward the celestial pole. 90 degrees indicate frame <span style=\" font-weight:600;\">UP</span> points 90 degrees counter-clockwise with respect to the celestial pole.</p>"
"<p>PA is calculated from raw rotator angle plus modifiers to match the rotation angle as measured by astrometry. Enter the modifiers manually or solve an image in the Align Module to generate them automatically.</p>"
"<p>Measure average HFR from all stars combined in a full frame. This method defaults to the Centroid detection, but can use SEP detection too. Its performance decreases as the number of stars increases.</p>"
"<p>During full field focusing, stars which are inside this percentage of the frame are filtered out of HFR calculation (default 0%). Detection algorithms may also have an inherent filter.</p>"
"<p>During full field focusing, stars which are outside this percentage of the frame are filtered out of HFR calculation (default 100%). Detection algorithms may also have an inherent filter.</p>"
msgid "<b>Initial</b> step size in ticks to cause a noticeable change in HFR value. For timer based focuser, it is the initial time in milliseconds to move the focuser inward or outward"
"<li><b>Iterative</b>: Moves focuser by discreet steps initially decided by the step size. Once a curve slope is calculated, further step sizes are calculated to reach optimal solution. The algorithm stops when the measured HFR is within percentage tolerance of the minimum HFR recorded in the procedure.</li>"
"\n"
"<li><b>Polynomial</b>: Starts with iterative method. Upon crossing to the other side of the V-Curve, polynomial fitting coefficients along with possible minimum solution are calculated. This algorithm can be faster than purely iterative approach given a good data set.</li>"
msgid "You must stop auto guiding before changing this setting."
msgstr ""
#. +> trunk5
-#: ekos/guide/guide.cpp:2269
+#: ekos/guide/guide.cpp:2270
#, kde-format
msgid "Rapid Guiding is enabled. Guide star will be determined automatically by the CCD driver. No frames are sent to Ekos unless explicitly enabled by the user in the CCD driver settings."
msgstr ""
#. +> trunk5
-#: ekos/guide/guide.cpp:2272
+#: ekos/guide/guide.cpp:2273
#, kde-format
msgid "Rapid Guiding is disabled."
msgstr ""
#. +> trunk5
-#: ekos/guide/guide.cpp:2534
+#: ekos/guide/guide.cpp:2535
#, kde-format
msgctxt "Drift graphics tooltip; %1 is local time; %2 is RA deviation; %3 is DE deviation in arcseconds;"
"<p>Subframe the image around the guide star. Before checking this option, you must <span style=\" font-weight:600;\">first</span> capture an image and select a guide star. Uncheck it to take a full frame again.</p>"
msgid "Mount guiding rate. Find out the guiding rate used by your mount and update the value here to get the <b>recommended</b> value of proportional gain suitable for your mount. Setting this value <b>does not</b> change your mount guiding rate."
"<p>Proportional term accounts for present values of the error. For example, if the error is large and positive, the guider corrective pulse will also be large and positive.</p>"
"<p>Integral term accounts for past values of the error. For example, if the current pulse is not sufficiently strong, the integral of the error will accumulate over time, and the guider will respond by applying a stronger action.</p>"
msgid "Maximum deviation to correct for using Adaptive Optics unit. If the guiding deviation exceeds this value, Ekos will guide the mount mechanically"
"<p>Drag the slider to scroll through guide history while displaying the RA and DEC error points on both graphs. Dragging to the far right will set the guide plots to display the latest guide data and autoscroll the graph.</p>"
"<p>Autoscale both Guide Graphs to their default scale. If any points are located outside this range, the view is expanded to include them (with the exception of the time axis in the drift graphics).</p>"
"<p>Request a meridian flip if the hour angle exceeds the specified value. Capture and Guiding will be suspended and resumed after the flip is complete.</p>"
"<p>Lead time is the minimum time in minutes between jobs. The scheduler starts execution of a job before its scheduled startup time by this lead time. Early execution is useful as focusing, alignment, and guiding procedures may take prolonged periods to time to complete.</p>"
"<p>In case no scheduler job is scheduled for this many hours, perform a complete shutdown procedure and restart observatory operations once the next job is ready.</p>"
"<p>Do not permit jobs to be scheduled less than this many degrees before the altitude restriction. Actual execution proceeds until the altitude limit.</p>"
"<p>If guiding calibration fails then restart alignment process before proceeding to guiding recalibration process again. This can help recenter the target object in the field of view if the calibration process strayed too far off.</p>"
msgid "Maximum acceptable difference between requested and measured temperature set point. When the temperature threshold is below this value, the temperature set point request is deemed successful."
#. i18n: ectx: label, entry (AlwaysResetSequenceWhenStarting), group (Capture)
#. +> trunk5
#: ekos/opsekos.ui:459 kstars.kcfg:1636
#, kde-format
msgid ""
"<html><head/><body>"
"<p>When starting to process a sequence list, reset all capture counts to zero. Scheduler overrides this option when Remember Job Progress is enabled.</p>"
"<p>If using a filter wheel and an absolute position focuser, then always remember the focus position of the autofocus process for light frames in each filter. Before a flat frame is captured, the focuser is moved to the same focus point as light frames.</p>"
"<p>Set HFR Threshold percentage gain. When an autofocus operation is completed, the autofocus HFR value is increased by this threshold percentage value and stored within the capture module. If In-Sequence-Focus is engaged, the autofocus module only performs autofocusing procedure if current HFR value exceeds the capture module HFR threshold. Increase value to permit more relaxed changes in HFR values without requiring a full autofocus run.</p>"
"<p>Calculate median focus value after each autofocus operation is complete. If the autofocus results become progressively worse with time, the median value shall reflect this trend and prevent unnecessary autofocus operations when the seeing conditions deteriorate.</p>"
"<p>In-Sequence HFR threshold value controls when the autofocus process is started. If the measured HFR value exceeds the HFR threshold, autofocus process is initiated. If the HFR threshold value is zero initially (default), then the autofocus process best HFR value is used to set the new HFR threshold, after applying the HFR threshold modifier percentage. This new HFR threshold is then used for subsequent In-Sequence focus checks. If this option is enabled, the HFR threshold value is constant and gets saved to the sequence file.</p>"
#. i18n: ectx: label, entry (MaxDarkTemperatureDiff), group (DarkLibrary)
#. +> trunk5
#: ekos/opsekos.ui:686 kstars.kcfg:1517
#, kde-format
msgid "Maximum acceptable difference between current and recorded dark frame temperature set point. When the difference exceeds this value, a new dark frame shall be captured for this set point."
"<p>Specify Remote drivers to chain with INDI server. Remote INDI drivers must be already running. If port is different from the default (7624), then it must be specified. For example, to connect to ZWO ASI120MC driver running on 192.168.1.50 on port 8000, the connection string is:</p>"
"<p>Welcome to the <span style=\" font-weight:600;\">Ekos Profile Wizard</span></p>"
"<p>Ekos is the premier observatory control and automation platform. With Ekos, you can capture images and gather scientific data with ease. This Wizard will help you create your equipment profile. You will be asked to verify some basic information. </p>"
"<p>Please click <span style=\" font-weight:600;\">next</span> to continue. </p>"
"<p><a href=\"https://github.com/knro/indiwebmanager\"><span style=\" text-decoration: underline; color:#007af4;\">INDI Web Manager</span></a> running on the Remote Computer?</p>"
"<p><span style=\" font-weight:600;\">Tip</span>: <span style=\" font-style:italic;\">INDI Web Manager</span> is a service that runs on remote devices to help you start and stop INDI services remotely.</p>"
"<p>To use Ekos with your equipment locally on Windows, you need to download and install <a href=\"http://www.cloudmakers.eu/windi/\"><span style=\" text-decoration: underline; color:#007af4;\">INDI Server for Windows</span></a>.</p>"
"<p>After installing <span style=\" font-style:italic;\">INDI Server for Windows (wINDI)</span>, establish connection with your equipment. wINDI requires <a href=\"http://www.ascom-standards.org/\"><span style=\" text-decoration: underline; color:#007af4;\">ASCOM</span></a> drivers for all your equipment, so make sure to install all necessary ASCOM drivers for your gear.</p>"
"<p>After successfully starting INDI Server in wINDI, click <span style=\" font-weight:600;\">Ready</span> to continue.</p>"
"<p><span style=\" font-weight:600;\">Tip</span>: INDI Server for Windows functionality is limited compared to the native INDI drivers on Linux. It is recommended to install native INDI on an embedded Linux device such as <a href=\"http://indilib.org/support/tutorials/169-ekos-on-raspberry-pi-complete-guide.html\"><span style=\" text-decoration: underline; color:#007af4;\">Raspberry PI</span></a>.</p>"
"<p><span style=\" font-weight:600;\">Tip</span>: External INDI Server can be <a href=\"http://www.cloudmakers.eu/indiserver/\"><span style=\" text-decoration: underline; color:#007af4;\">INDI Server for OSX</span></a> or an INDI Server launched manually locally. If unsure, select Internal INDI Server.</p>"
"<p><span style=\" font-weight:600;\">Tip</span>: Internal Guider is recommended. Using external guider applications requires additional setup instructions outside the scope of Ekos.</p>"
"<p>If the remote computer has astrometry.net installed, you can run the remote astrometry driver and use it to solve images in Ekos Align module.</p>"
"<p>Use the INDI WatchDog driver. It monitors connection between your remote equipment and Ekos. If the communication is lost between the two, the WatchDog driver goes into safe mode and executes a shutdown procedure to protect your equipment.</p>"
"<p>If you plan to use SkySafari to monitor and/or control your mount, check this box to start INDI SkySafari Server. You can connect SkySafari to this server and it shall enable you to connect and control your mount. For more details, please check the <a href=\"http://indilib.org/devices/telescopes/skysafari.html\"><span style=\" text-decoration: underline; color:#007af4;\">INDI SkySafari Documentation.</span></a></p>"
msgid "Camera's rotation angle (East of North) in degrees. To measure the angle, solve an image and use the astrometry solver solution's rotation angle"
msgid "Warning: job '%1' has startup time %2 resulting in a negative score, and will be marked invalid when processed."
msgstr ""
#. +> trunk5
#: ekos/scheduler/scheduler.cpp:651
#, kde-format
msgid "Warning: job '%1' at row %2 has a duplicate target at row %3, the scheduler may consider the same storage for captures."
msgstr ""
#. +> trunk5
#: ekos/scheduler/scheduler.cpp:659
#, kde-format
msgid "Warning: jobs '%1' at row %2 and %3 probably require a different repeat count as currently they will complete simultaneously after %4 batches (or disable option 'Remember job progress')"
msgstr ""
#. +> trunk5
#: ekos/scheduler/scheduler.cpp:664
#, kde-format
msgid "Warning: job '%1' at row %2 might require a specific startup time or a different priority, as currently they will start in order of insertion in the table"
msgstr ""
#. +> trunk5
#: ekos/scheduler/scheduler.cpp:838
#, kde-format
msgid "Warning: you cannot add or modify a job while the scheduler is running."
msgstr ""
#. +> trunk5
#: ekos/scheduler/scheduler.cpp:906
#, kde-format
msgid "Use edition fields to create a new job in the observation list."
msgstr ""
#. +> trunk5
#: ekos/scheduler/scheduler.cpp:1165
#, kde-format
msgid "Job '%1' has not been processed upon scheduler stop, marking aborted."
msgstr ""
#. +> trunk5
#: ekos/scheduler/scheduler.cpp:1172
#, kde-format
msgid "Scheduler aborted."
msgstr ""
#. +> trunk5
#: ekos/scheduler/scheduler.cpp:1231
#, kde-format
msgid "Scheduler is in shutdown until next job is ready"
msgid "Select optional FITS file to be used for alignment. When using FITS, specify the object or the estimated coordinates which are used to slew the mount."
msgid "Start the observation job when the object reaches culmination adjusted for the offset value in minutes. By default, the observation job runs 60 minutes prior to culmination."
"<p>One-time startup procedure to be executed before starting Ekos. The script is executed <span style=\" font-weight:600; text-decoration: underline;\">before</span> the startup procedures (e.g. unpark scope), if selected, are executed.</p>"
"<p>One-time shutdown procedure to be executed after all scheduler jobs are completed. The script is executed <span style=\" font-weight:600; text-decoration: underline;\">after</span> the shutdown procedures (e.g. parking), if selected, are completed.</p>"
"Current status of job '%1', managed by the Scheduler.\n"
"If invalid, the Scheduler was not able to find a proper observation time for the target.\n"
"If aborted, the Scheduler missed the scheduled time or encountered transitory issues and will reschedule the job.\n"
"If complete, the Scheduler verified that all sequence captures requested were stored, including repeats."
msgstr ""
#. +> trunk5
#: ekos/scheduler/schedulerjob.cpp:239
#, kde-format
msgid ""
"Current altitude of the target of job '%1'.\n"
"The altitude at startup, if available, is displayed between parentheses.\n"
"A rising target is indicated with an arrow going up.\n"
"A setting target is indicated with an arrow going down."
msgstr ""
#. +> trunk5
#: ekos/scheduler/schedulerjob.cpp:250
#, kde-format
msgid ""
"Startup time for job '%1', as estimated by the Scheduler.\n"
"Fixed time from user or culmination time is marked with a chronometer symbol. "
msgstr ""
#. +> trunk5
#: ekos/scheduler/schedulerjob.cpp:259
#, kde-format
msgid ""
"Completion time for job '%1', as estimated by the Scheduler.\n"
"You may specify a fixed time to limit duration of looping jobs. A warning symbol indicates the altitude at completion may cause the job to abort before completion.\n"
msgstr ""
#. +> trunk5
#: ekos/scheduler/schedulerjob.cpp:269
#, kde-format
msgid ""
"Count of captures stored for job '%1', based on its sequence job.\n"
"This is a summary, additional specific frame types may be required to complete the job."
msgstr ""
#. +> trunk5
#: ekos/scheduler/schedulerjob.cpp:278
#, kde-format
msgid ""
"Current score for job '%1', from its altitude, moon separation and sky darkness.\n"
"Negative if adequate altitude is not achieved yet or if there is no proper observation time today.\n"
"The Scheduler will refresh scores when picking a new candidate job."
msgstr ""
#. +> trunk5
#: ekos/scheduler/schedulerjob.cpp:288
#, kde-format
msgid ""
"Time interval from the job which precedes job '%1'.\n"
"Adjust the Lead Time in Ekos options to increase that duration and leave time for jobs to complete.\n"
"Rearrange jobs to minimize that duration and optimize your imaging time."
msgstr ""
#. +> trunk5
#: ekos/scheduler/schedulerjob.cpp:374
#, kde-format
msgid ""
"Duration job '%1' will take to complete when started, as estimated by the Scheduler.\n"
"Depends on the actions to be run, and the sequence job to be processed."
"<li style=\" margin-top:12px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;\"><span style=\" font-weight:600;\">Auto Debayer</span>: Bayered images will not be debayered. Only grayscale images are shown.</li>"
"<li style=\" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;\"><span style=\" font-weight:600;\">Auto WCS</span>: World Coordinate System data will not be processed. WCS maps sky coordinates to image coordinates. Equatorial grid lines, object identification, and telescope slew within an image are disabled.</li>"
"<li style=\" margin-top:0px; margin-bottom:12px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;\"><span style=\" font-weight:600;\">3D Cube</span>: RGB images will not be processed. Only grayscale images are shown.</li>"
"<p>Automatically load World-Coordinate-System (WCS) data when opening a FITS file.</p>"
"<p><span style=\" font-weight:600;\">Warning: Only enable this option on very fast machines as it can lead to unpredictable behavior resulting in crashes on slower machines.</span></p>"
"<p>To create an <span style=\" font-weight:600;\">Alias</span> from an existing driver, select an existing driver and then only change the <span style=\" font-weight:600;\">Label </span>then press<span style=\" font-weight:600;\"> Add.</span></p>"
"<p>Mount handset is the master source of time and location settings. KStars time and location settings are synchronized with controller settings.</p>"
"<p>Set SER video <b>remote</b> directory name. If INDI server is running locally, then a local directory can be selected. However, if you are connected to a remote INDI server, then the directory must be a valid directory on the remote file system where it is saved.</p>"
"\n"
"<p>Record directories may contain some patterns to make them dynamic:</p>"
"Verify if the following time, date, and location settings are correct. If any of the settings are incorrect, you can correct them via the <tt>Set time</tt> and <tt>Set Location</tt> buttons.\n"
"Enter the port number your telescope is connected to. If you only have one serial port in your computer, the port is usually <tt>/dev/ttyUSB0</tt>\n"
"<br>"
"<br>"
"If you are unsure about the port number, you can leave the field empty and KStars will try to scan the ports for attached telescopes. Beware that the autoscan process might take a few minutes to complete. "
msgid "Switch to horizonal view (Horizontal &Coordinates)"
msgstr ""
#. i18n: ectx: label, entry (PositionTimeBox), group (GUI)
#. +> trunk5
#: kstars.kcfg:9
#, kde-format
msgid "Position of the time InfoBox."
msgstr ""
#. i18n: ectx: whatsthis, entry (PositionTimeBox), group (GUI)
#. +> trunk5
#: kstars.kcfg:10
#, kde-format
msgid "The screen coordinates of the Time InfoBox."
msgstr ""
#. i18n: ectx: label, entry (PositionFocusBox), group (GUI)
#. +> trunk5
#: kstars.kcfg:14
#, kde-format
msgid "Position of the focus InfoBox."
msgstr ""
#. i18n: ectx: whatsthis, entry (PositionFocusBox), group (GUI)
#. +> trunk5
#: kstars.kcfg:15
#, kde-format
msgid "The screen coordinates of the Focus InfoBox."
msgstr ""
#. i18n: ectx: label, entry (PositionGeoBox), group (GUI)
#. +> trunk5
#: kstars.kcfg:19
#, kde-format
msgid "Position of the geographic InfoBox."
msgstr ""
#. i18n: ectx: whatsthis, entry (PositionGeoBox), group (GUI)
#. +> trunk5
#: kstars.kcfg:20
#, kde-format
msgid "The screen coordinates of the Geographic Location InfoBox."
msgstr ""
#. i18n: ectx: label, entry (ShadeTimeBox), group (GUI)
#. +> trunk5
#: kstars.kcfg:24
#, kde-format
msgid "Is the time InfoBox in the \"shaded\" state?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShadeTimeBox), group (GUI)
#. +> trunk5
#: kstars.kcfg:25
#, kde-format
msgid "If true, the Time InfoBox will show only its top line of data."
msgstr ""
#. i18n: ectx: label, entry (ShadeFocusBox), group (GUI)
#. +> trunk5
#: kstars.kcfg:29
#, kde-format
msgid "Is the focus InfoBox in the \"shaded\" state?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShadeFocusBox), group (GUI)
#. +> trunk5
#: kstars.kcfg:30
#, kde-format
msgid "If true, the Focus InfoBox will show only its top line of data."
msgstr ""
#. i18n: ectx: label, entry (ShadeGeoBox), group (GUI)
#. +> trunk5
#: kstars.kcfg:34
#, kde-format
msgid "Is the geographic InfoBox in the \"shaded\" state?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShadeGeoBox), group (GUI)
#. +> trunk5
#: kstars.kcfg:35
#, kde-format
msgid "If true, the Geographic Location InfoBox will show only its top line of data."
msgstr ""
#. i18n: ectx: label, entry (ShowInfoBoxes), group (GUI)
#. +> trunk5
#: kstars.kcfg:39
#, kde-format
msgid "Meta-option to toggle display of all InfoBoxes"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowInfoBoxes), group (GUI)
#. +> trunk5
#: kstars.kcfg:40
#, kde-format
msgid "Toggles display of all three InfoBoxes."
msgstr ""
#. i18n: ectx: label, entry (ShowTimeBox), group (GUI)
#. +> trunk5
#: kstars.kcfg:44
#, kde-format
msgid "Display the time InfoBox?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowTimeBox), group (GUI)
#. +> trunk5
#: kstars.kcfg:45
#, kde-format
msgid "Toggles display of the Time InfoBox."
msgstr ""
#. i18n: ectx: label, entry (ShowFocusBox), group (GUI)
#. +> trunk5
#: kstars.kcfg:49
#, kde-format
msgid "Display the focus InfoBox?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowFocusBox), group (GUI)
#. +> trunk5
#: kstars.kcfg:50
#, kde-format
msgid "Toggles display of the Focus InfoBox."
msgstr ""
#. i18n: ectx: label, entry (ShowGeoBox), group (GUI)
#. +> trunk5
#: kstars.kcfg:54
#, kde-format
msgid "Display the geographic InfoBox?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowGeoBox), group (GUI)
#. +> trunk5
#: kstars.kcfg:55
#, kde-format
msgid "Toggles display of the Geographic Location InfoBox."
msgstr ""
#. i18n: ectx: label, entry (StickyTimeBox), group (GUI)
#. i18n: ectx: label, entry (StickyFocusBox), group (GUI)
#. +> trunk5
#: kstars.kcfg:59 kstars.kcfg:66
#, kde-format
msgid "Time InfoBox anchor flag"
msgstr ""
#. i18n: ectx: whatsthis, entry (StickyTimeBox), group (GUI)
#. +> trunk5
#: kstars.kcfg:60
#, kde-format
msgid "Is the Time InfoBox anchored to a window edge? 0 = not anchored; 1 = anchored to right edge; 2 = anchored to bottom edge; 3 = anchored to bottom and right edges."
msgstr ""
#. i18n: ectx: whatsthis, entry (StickyFocusBox), group (GUI)
#. +> trunk5
#: kstars.kcfg:67
#, kde-format
msgid "Is the Focus InfoBox anchored to a window edge? 0 = not anchored; 1 = anchored to right edge; 2 = anchored to bottom edge; 3 = anchored to bottom and right edges."
msgstr ""
#. i18n: ectx: label, entry (StickyGeoBox), group (GUI)
#. +> trunk5
#: kstars.kcfg:73
#, kde-format
msgid "Geographic InfoBox anchor flag"
msgstr ""
#. i18n: ectx: whatsthis, entry (StickyGeoBox), group (GUI)
#. +> trunk5
#: kstars.kcfg:74
#, kde-format
msgid "Is the Geographic Location InfoBox anchored to a window edge? 0 = not anchored; 1 = anchored to right edge; 2 = anchored to bottom edge; 3 = anchored to bottom and right edges."
msgstr ""
#. i18n: ectx: label, entry (ShowStatusBar), group (GUI)
#. +> trunk5
#: kstars.kcfg:80
#, kde-format
msgid "Display the statusbar?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowStatusBar), group (GUI)
#. +> trunk5
#: kstars.kcfg:81
#, kde-format
msgid "Toggle display of the status bar."
msgstr ""
#. i18n: ectx: label, entry (ShowAltAzField), group (GUI)
#. +> trunk5
#: kstars.kcfg:85
#, kde-format
msgid "Display Alt/Az coordinates in the statusbar?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowAltAzField), group (GUI)
#. +> trunk5
#: kstars.kcfg:86
#, kde-format
msgid "Toggle display of the Horizontal coordinates of the mouse cursor in the status bar."
msgstr ""
#. i18n: ectx: label, entry (ShowRADecField), group (GUI)
#. +> trunk5
#: kstars.kcfg:90
#, kde-format
msgid "Display RA/Dec coordinates in the statusbar?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowRADecField), group (GUI)
#. +> trunk5
#: kstars.kcfg:91
#, kde-format
msgid "Toggle display of the Equatorial coordinates of the mouse cursor at the current epoch in the status bar."
msgstr ""
#. i18n: ectx: label, entry (ShowJ2000RADecField), group (GUI)
#. +> trunk5
#: kstars.kcfg:95
#, kde-format
msgid "Display J2000.0 RA/Dec coordinates in the statusbar?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowJ2000RADecField), group (GUI)
#. +> trunk5
#: kstars.kcfg:96
#, kde-format
msgid "Toggle display of the Equatorial coordinates of the mouse cursor at the standard epoch in the status bar."
msgstr ""
#. i18n: ectx: label, entry (ShowSensorFOV), group (GUI)
#. +> trunk5
#: kstars.kcfg:100
#, kde-format
msgid "Display CCD sensor angular size on the sky map?"
msgstr ""
#. i18n: ectx: label, entry (WindowWidth), group (GUI)
#. +> trunk5
#: kstars.kcfg:104
#, kde-format
msgid "Width of main window, in pixels"
msgstr ""
#. i18n: ectx: label, entry (WindowHeight), group (GUI)
#. +> trunk5
#: kstars.kcfg:108
#, kde-format
msgid "Height of main window, in pixels"
msgstr ""
#. i18n: ectx: label, entry (RunStartupWizard), group (GUI)
#. +> trunk5
#: kstars.kcfg:112
#, kde-format
msgid "Run Startup Wizard when KStars launches?"
msgstr ""
#. i18n: ectx: label, entry (CurrentTheme), group (GUI)
#. +> trunk5
#: kstars.kcfg:116
#, kde-format
msgid "Current application theme"
msgstr ""
#. i18n: ectx: label, entry (CatalogFile), group (Catalogs)
#. +> trunk5
#: kstars.kcfg:123
#, kde-format
msgid "Filenames of defined custom object catalogs."
msgstr ""
#. i18n: ectx: whatsthis, entry (CatalogFile), group (Catalogs)
#. +> trunk5
#: kstars.kcfg:124
#, kde-format
msgid "List of the filenames of custom object catalogs."
msgstr ""
#. i18n: ectx: label, entry (ShowCatalog), group (Catalogs)
#. +> trunk5
#: kstars.kcfg:127
#, kde-format
msgid "List of toggles for displaying custom object catalogs."
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowCatalog), group (Catalogs)
#. +> trunk5
#: kstars.kcfg:128
#, kde-format
msgid "List of integers toggling display of each custom object catalog (any nonzero value indicates the objects in that catalog will be displayed)."
msgstr ""
#. i18n: ectx: label, entry (ShowCatalogNames), group (Catalogs)
#. +> trunk5
#: kstars.kcfg:131
#, kde-format
msgid "List for displaying custom object catalogs."
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowCatalogNames), group (Catalogs)
#. +> trunk5
#: kstars.kcfg:132
#, kde-format
msgid "List of names for which custom catalogs are to be displayed."
msgstr ""
#. i18n: ectx: label, entry (ResolveNamesOnline), group (Catalogs)
#. +> trunk5
#: kstars.kcfg:135
#, kde-format
msgid "Resolve names using online services."
msgstr ""
#. i18n: ectx: whatsthis, entry (ResolveNamesOnline), group (Catalogs)
#. +> trunk5
#: kstars.kcfg:136
#, kde-format
msgid "Names of objects entered into the find dialog are resolved using online services and stored in the database. This option also toggles the display of such resolved objects on the sky map."
msgstr ""
#. i18n: ectx: label, entry (INDIWindowWidth), group (indi)
#. +> trunk5
#: kstars.kcfg:143
#, kde-format
msgid "INDI window width"
msgstr ""
#. i18n: ectx: label, entry (INDIWindowHeight), group (indi)
#. +> trunk5
#: kstars.kcfg:147
#, kde-format
msgid "INDI window height"
msgstr ""
#. i18n: ectx: label, entry (useGeographicUpdate), group (indi)
#. i18n: ectx: label, entry (useTimeUpdate), group (indi)
#. +> trunk5
#: kstars.kcfg:155
#, kde-format
msgid "Automatically updates time and date?"
msgstr ""
#. i18n: ectx: label, entry (independentWindowINDI), group (indi)
#. +> trunk5
#: kstars.kcfg:159
#, kde-format
msgid "Make INDI Control Panel window independent of KStars main window"
msgstr ""
#. i18n: ectx: label, entry (showTargetCrosshair), group (indi)
#. +> trunk5
#: kstars.kcfg:163
#, kde-format
msgid "Draw crosshairs at telescope position in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (showTargetCrosshair), group (indi)
#. +> trunk5
#: kstars.kcfg:164
#, kde-format
msgid "Toggle display of crosshairs centered at telescope's pointed position in the KStars sky map."
msgstr ""
#. i18n: ectx: label, entry (showINDIMessages), group (indi)
#. +> trunk5
#: kstars.kcfg:168
#, kde-format
msgid "Display INDI messages in the statusbar?"
msgstr ""
#. i18n: ectx: whatsthis, entry (showINDIMessages), group (indi)
#. +> trunk5
#: kstars.kcfg:169
#, kde-format
msgid "Toggle display of INDI messages in the KStars statusbar."
msgstr ""
#. i18n: ectx: label, entry (messageNotificationINDI), group (indi)
#. +> trunk5
#: kstars.kcfg:173
#, kde-format
msgid "INDI message notifications"
msgstr ""
#. i18n: ectx: whatsthis, entry (messageNotificationINDI), group (indi)
#. +> trunk5
#: kstars.kcfg:174
#, kde-format
msgid "Show INDI messages as desktop notifications instead of dialogs."
msgstr ""
#. i18n: ectx: label, entry (useKStarsSource), group (indi)
#. +> trunk5
#: kstars.kcfg:178
#, kde-format
msgid "Use KStars time and location for synchronization?"
msgstr ""
#. i18n: ectx: label, entry (useMountSource), group (indi)
#. +> trunk5
#: kstars.kcfg:182
#, kde-format
msgid "Use mount time and location for synchronization?"
msgstr ""
#. i18n: ectx: label, entry (useGPSSource), group (indi)
#. +> trunk5
#: kstars.kcfg:186
#, kde-format
msgid "Use GPS time and location for synchronization?"
msgstr ""
#. i18n: ectx: label, entry (fitsDir), group (indi)
#. +> trunk5
#: kstars.kcfg:190
#, kde-format
msgid "FITS Default directory"
msgstr ""
#. i18n: ectx: whatsthis, entry (fitsDir), group (indi)
#. +> trunk5
#: kstars.kcfg:191
#, kde-format
msgid "The default location of saved FITS files"
msgstr ""
#. i18n: ectx: label, entry (serverPortStart), group (indi)
#. +> trunk5
#: kstars.kcfg:195
#, kde-format
msgid "INDI Server Start Port"
msgstr ""
#. i18n: ectx: whatsthis, entry (serverPortStart), group (indi)
#. +> trunk5
#: kstars.kcfg:196
#, kde-format
msgid "INDI server will attempt to bind with ports starting from this port"
msgstr ""
#. i18n: ectx: label, entry (serverPortEnd), group (indi)
#. +> trunk5
#: kstars.kcfg:200
#, kde-format
msgid "INDI Server Final Port"
msgstr ""
#. i18n: ectx: whatsthis, entry (serverPortEnd), group (indi)
#. +> trunk5
#: kstars.kcfg:201
#, kde-format
msgid "INDI server will attempt to bind with ports ending with this port"
msgstr ""
#. i18n: ectx: label, entry (filterAlias), group (indi)
#. +> trunk5
#: kstars.kcfg:205
#, kde-format
msgid "Aliases for filter wheel slots."
msgstr ""
#. i18n: ectx: whatsthis, entry (filterAlias), group (indi)
#. +> trunk5
#: kstars.kcfg:206
#, kde-format
msgid "List of the aliases for filter wheel slots."
msgstr ""
#. i18n: ectx: label, entry (indiServer), group (indi)
#. i18n: ectx: whatsthis, entry (indiServer), group (indi)
#. +> trunk5
#: kstars.kcfg:209 kstars.kcfg:210
#, kde-format
msgid "PATH to indiserver binary"
msgstr ""
#. i18n: ectx: label, entry (indiServerIsInternal), group (indi)
#. +> trunk5
#: kstars.kcfg:214
#, kde-format
msgid "Internal or External INDI Server?"
msgstr ""
#. i18n: ectx: label, entry (indiDriversDir), group (indi)
#. i18n: ectx: whatsthis, entry (indiDriversDir), group (indi)
#. +> trunk5
#: kstars.kcfg:218 kstars.kcfg:219
#, kde-format
msgid "PATH to indi drivers directory"
msgstr ""
#. i18n: ectx: label, entry (indiDriversAreInternal), group (indi)
#. i18n: ectx: label, entry (AstrometrySolverIsInternal), group (Align)
#. +> trunk5
#: kstars.kcfg:223 kstars.kcfg:1933
#, kde-format
msgid "Internal or External Astrometry Solver?"
msgstr ""
#. i18n: ectx: label, entry (streamWindowWidth), group (indi)
#. +> trunk5
#: kstars.kcfg:227
#, kde-format
msgid "Video streaming window width"
msgstr ""
#. i18n: ectx: label, entry (streamWindowHeight), group (indi)
#. +> trunk5
#: kstars.kcfg:231
#, kde-format
msgid "Video streaming window height"
msgstr ""
#. i18n: ectx: label, entry (INDIMountLogging), group (indi)
#. +> trunk5
#: kstars.kcfg:235
#, kde-format
msgid "Enable INDI Mount logging"
msgstr ""
#. i18n: ectx: label, entry (INDIFocuserLogging), group (indi)
#. +> trunk5
#: kstars.kcfg:239
#, kde-format
msgid "Enable INDI Focuser logging"
msgstr ""
#. i18n: ectx: label, entry (INDICCDLogging), group (indi)
#. +> trunk5
#: kstars.kcfg:243
#, kde-format
msgid "Enable INDI CCD logging"
msgstr ""
#. i18n: ectx: label, entry (INDIFilterWheelLogging), group (indi)
#. +> trunk5
#: kstars.kcfg:247
#, kde-format
msgid "Enable INDI Filter Wheel logging"
msgstr ""
#. i18n: ectx: label, entry (INDIDomeLogging), group (indi)
#. +> trunk5
#: kstars.kcfg:251
#, kde-format
msgid "Enable INDI Dome logging"
msgstr ""
#. i18n: ectx: label, entry (INDIDetectorLogging), group (indi)
#. +> trunk5
#: kstars.kcfg:255
#, kde-format
msgid "Enable INDI Detector logging"
msgstr ""
#. i18n: ectx: label, entry (INDIWeatherLogging), group (indi)
#. +> trunk5
#: kstars.kcfg:259
#, kde-format
msgid "Enable INDI Weather logging"
msgstr ""
#. i18n: ectx: label, entry (INDIAuxiliaryLogging), group (indi)
#. +> trunk5
#: kstars.kcfg:263
#, kde-format
msgid "Enable INDI Auxiliary logging"
msgstr ""
#. i18n: ectx: label, entry (INDIRotatorLogging), group (indi)
#. +> trunk5
#: kstars.kcfg:267
#, kde-format
msgid "Enable INDI Rotator logging"
msgstr ""
#. i18n: ectx: label, entry (INDIGPSLogging), group (indi)
#. +> trunk5
#: kstars.kcfg:271
#, kde-format
msgid "Enable INDI GPS logging"
msgstr ""
#. i18n: ectx: label, entry (INDIAOLogging), group (indi)
#. +> trunk5
#: kstars.kcfg:275
#, kde-format
msgid "Enable INDI Adaptive Optics logging"
msgstr ""
#. i18n: ectx: label, entry (CityName), group (Location)
#. +> trunk5
#: kstars.kcfg:282
#, kde-format
msgid "City name of geographic location."
msgstr ""
#. i18n: ectx: whatsthis, entry (CityName), group (Location)
#. +> trunk5
#: kstars.kcfg:283
#, kde-format
msgid "The City name of the current geographic location."
msgstr ""
#. i18n: ectx: label, entry (ProvinceName), group (Location)
#. +> trunk5
#: kstars.kcfg:287
#, kde-format
msgid "Province name of geographic location."
msgstr ""
#. i18n: ectx: whatsthis, entry (ProvinceName), group (Location)
#. +> trunk5
#: kstars.kcfg:288
#, kde-format
msgid "The Province name of the current geographic location. This is the name of the state for locations in the U. S."
msgstr ""
#. i18n: ectx: label, entry (CountryName), group (Location)
#. +> trunk5
#: kstars.kcfg:292
#, kde-format
msgid "Country name of geographic location."
msgstr ""
#. i18n: ectx: whatsthis, entry (CountryName), group (Location)
#. +> trunk5
#: kstars.kcfg:293
#, kde-format
msgid "The Country name of the current geographic location."
msgstr ""
#. i18n: ectx: label, entry (Longitude), group (Location)
#. +> trunk5
#: kstars.kcfg:297
#, kde-format
msgid "Geographic Longitude, in degrees."
msgstr ""
#. i18n: ectx: whatsthis, entry (Longitude), group (Location)
#. +> trunk5
#: kstars.kcfg:298
#, kde-format
msgid "The longitude of the current geographic location, in decimal degrees."
msgstr ""
#. i18n: ectx: label, entry (Latitude), group (Location)
#. +> trunk5
#: kstars.kcfg:302
#, kde-format
msgid "Geographic Latitude, in degrees."
msgstr ""
#. i18n: ectx: whatsthis, entry (Latitude), group (Location)
#. +> trunk5
#: kstars.kcfg:303
#, kde-format
msgid "The latitude of the current geographic location, in decimal degrees."
msgstr ""
#. i18n: ectx: label, entry (Elevation), group (Location)
#. +> trunk5
#: kstars.kcfg:307
#, kde-format
msgid "Elevation above sea level of geographic location, in meters."
msgstr ""
#. i18n: ectx: label, entry (TimeZone), group (Location)
#. +> trunk5
#: kstars.kcfg:311
#, kde-format
msgid "Time Zone offset of geographic location, in hours."
msgstr ""
#. i18n: ectx: label, entry (DST), group (Location)
#. +> trunk5
#: kstars.kcfg:315
#, kde-format
msgid "Two-letter code for daylight savings time rule used by geographic location."
msgstr ""
#. i18n: ectx: whatsthis, entry (DST), group (Location)
#. +> trunk5
#: kstars.kcfg:316
#, kde-format
msgid "Two-letter code that determines the dates on which daylight savings time begins and ends (you can view the rules by pressing the \"Explain DST Rules\" button in the Geographic Location window)."
msgstr ""
#. i18n: ectx: label, entry (UseAnimatedSlewing), group (View)
#. +> trunk5
#: kstars.kcfg:323
#, kde-format
msgid "Use animated slewing effects when changing focus position?"
msgstr ""
#. i18n: ectx: whatsthis, entry (UseAnimatedSlewing), group (View)
#. +> trunk5
#: kstars.kcfg:324
#, kde-format
msgid "If true, focus changes will cause the sky to visibly spin to the new position. Otherwise, the display will \"snap\" instantly to the new position."
msgstr ""
#. i18n: ectx: label, entry (LeftClickSelectsObject), group (View)
#. +> trunk5
#: kstars.kcfg:328
#, kde-format
msgid "Select objects on left click?"
msgstr ""
#. i18n: ectx: whatsthis, entry (LeftClickSelectsObject), group (View)
#. +> trunk5
#: kstars.kcfg:329
#, kde-format
msgid "If true, clicking on the skymap will select the closest object and highlights it."
msgstr ""
#. i18n: ectx: label, entry (DefaultCursor), group (View)
#. +> trunk5
#: kstars.kcfg:333
#, kde-format
msgid "Select default Skymap cursor?"
msgstr ""
#. i18n: ectx: whatsthis, entry (DefaultCursor), group (View)
#. +> trunk5
#: kstars.kcfg:334
#, kde-format
msgid "Type of cursor when exploring the sky map."
msgstr ""
#. i18n: ectx: label, entry (FOVNames), group (View)
#. +> trunk5
#: kstars.kcfg:338
#, kde-format
msgid "Name of selected FOV indicators"
msgstr ""
#. i18n: ectx: whatsthis, entry (FOVNames), group (View)
#. +> trunk5
#: kstars.kcfg:339
#, kde-format
msgid "The names of the currently selected field-of-view indicators. The list of defined FOV indicator names is listed in the \"Settings|FOV Symbols\" menu."
msgstr ""
#. i18n: ectx: label, entry (FadePlanetTrails), group (View)
#. +> trunk5
#: kstars.kcfg:343
#, kde-format
msgid "Fade planet trails to background color?"
msgstr ""
#. i18n: ectx: whatsthis, entry (FadePlanetTrails), group (View)
#. +> trunk5
#: kstars.kcfg:344
#, kde-format
msgid "If true, trails attached to solar system bodies will fade into the background sky color."
msgstr ""
#. i18n: ectx: label, entry (FocusRA), group (View)
#. +> trunk5
#: kstars.kcfg:348
#, kde-format
msgid "Right Ascension of focus position"
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusRA), group (View)
#. +> trunk5
#: kstars.kcfg:349
#, kde-format
msgid "The right ascension of the initial focus position of the sky map, in decimal hours. This value is volatile; it is reset whenever the program shuts down."
msgstr ""
#. i18n: ectx: label, entry (FocusDec), group (View)
#. +> trunk5
#: kstars.kcfg:353
#, kde-format
msgid "Declination of focus position"
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusDec), group (View)
#. +> trunk5
#: kstars.kcfg:354
#, kde-format
msgid "The declination of the initial focus position of the sky map, in decimal degrees. This value is volatile; it is reset whenever the program shuts down."
msgstr ""
#. i18n: ectx: label, entry (FocusObject), group (View)
#. +> trunk5
#: kstars.kcfg:358
#, kde-format
msgid "Name of focused object"
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusObject), group (View)
#. +> trunk5
#: kstars.kcfg:359
#, kde-format
msgid "The name of the object that should be centered and tracked on startup. If no object should be centered, set to \"nothing\". This value is volatile; it is reset whenever the program shuts down."
msgstr ""
#. i18n: ectx: label, entry (IsTracking), group (View)
#. +> trunk5
#: kstars.kcfg:363
#, kde-format
msgid "Is tracking engaged?"
msgstr ""
#. i18n: ectx: whatsthis, entry (IsTracking), group (View)
#. +> trunk5
#: kstars.kcfg:364
#, kde-format
msgid "True if the skymap should track on its initial position on startup. This value is volatile; it is reset whenever the program shuts down."
msgstr ""
#. i18n: ectx: label, entry (HideOnSlew), group (View)
#. +> trunk5
#: kstars.kcfg:368
#, kde-format
msgid "Hide objects while moving?"
msgstr ""
#. i18n: ectx: whatsthis, entry (HideOnSlew), group (View)
#. +> trunk5
#: kstars.kcfg:369
#, kde-format
msgid "Toggle whether KStars should hide some objects while the display is moving, for smoother motion."
msgstr ""
#. i18n: ectx: label, entry (HideCBounds), group (View)
#. +> trunk5
#: kstars.kcfg:373
#, kde-format
msgid "Hide constellation boundaries while moving?"
msgstr ""
#. i18n: ectx: whatsthis, entry (HideCBounds), group (View)
#. +> trunk5
#: kstars.kcfg:374
#, kde-format
msgid "Toggle whether constellation boundaries are hidden while the display is in motion."
msgstr ""
#. i18n: ectx: label, entry (HideCLines), group (View)
msgid "Draw grids according to active coordinate system?"
msgstr ""
#. i18n: ectx: whatsthis, entry (AutoSelectGrid), group (View)
#. +> trunk5
#: kstars.kcfg:533
#, kde-format
msgid "Coordinate grids will automatically change according to active coordinate system."
msgstr ""
#. i18n: ectx: label, entry (ShowEquatorialGrid), group (View)
#. +> trunk5
#: kstars.kcfg:537
#, kde-format
msgid "Draw equatorial coordinate grid in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowEquatorialGrid), group (View)
#. +> trunk5
#: kstars.kcfg:538
#, kde-format
msgid "Toggle whether the equatorial coordinate grid is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowHorizontalGrid), group (View)
#. +> trunk5
#: kstars.kcfg:542
#, kde-format
msgid "Draw horizontal coordinate grid in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowHorizontalGrid), group (View)
#. +> trunk5
#: kstars.kcfg:543
#, kde-format
msgid "Toggle whether the horizontal coordinate grid is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowLocalMeridian), group (View)
#. +> trunk5
#: kstars.kcfg:547
#, kde-format
msgid "Draw local meridian line in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowLocalMeridian), group (View)
#. +> trunk5
#: kstars.kcfg:548
#, kde-format
msgid "Toggle whether the local meridian line is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowGround), group (View)
#. +> trunk5
#: kstars.kcfg:552
#, kde-format
msgid "Draw opaque ground in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowGround), group (View)
#. +> trunk5
#: kstars.kcfg:553
#, kde-format
msgid "Toggle whether the region below the horizon is opaque."
msgstr ""
#. i18n: ectx: label, entry (ShowHorizon), group (View)
#. +> trunk5
#: kstars.kcfg:557
#, kde-format
msgid "Draw horizon line in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowHorizon), group (View)
#. +> trunk5
#: kstars.kcfg:558
#, kde-format
msgid "Toggle whether the horizon line is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowFlags), group (View)
#. +> trunk5
#: kstars.kcfg:562
#, kde-format
msgid "Draw flags in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowFlags), group (View)
#. +> trunk5
#: kstars.kcfg:563
#, kde-format
msgid "Toggle whether flags are drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowIC), group (View)
#. +> trunk5
#: kstars.kcfg:567
#, kde-format
msgid "Draw IC objects in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowIC), group (View)
#. +> trunk5
#: kstars.kcfg:568
#, kde-format
msgid "Toggle whether IC objects are drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowNGC), group (View)
#. +> trunk5
#: kstars.kcfg:572
#, kde-format
msgid "Draw NGC objects in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowNGC), group (View)
#. +> trunk5
#: kstars.kcfg:573
#, kde-format
msgid "Toggle whether NGC objects are drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowMessier), group (View)
#. +> trunk5
#: kstars.kcfg:577
#, kde-format
msgid "Draw Messier objects in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowMessier), group (View)
#. +> trunk5
#: kstars.kcfg:578
#, kde-format
msgid "Toggle whether Messier objects are drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowMessierImages), group (View)
#. +> trunk5
#: kstars.kcfg:582
#, kde-format
msgid "Draw Messier object images in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowMessierImages), group (View)
#. +> trunk5
#: kstars.kcfg:583
#, kde-format
msgid "Toggle whether Messier objects are rendered as images in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowOther), group (View)
#. +> trunk5
#: kstars.kcfg:587
#, kde-format
msgid "Draw extra deep-sky objects in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowOther), group (View)
#. +> trunk5
#: kstars.kcfg:588
#, kde-format
msgid "Toggle whether extra objects are drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowMilkyWay), group (View)
#. +> trunk5
#: kstars.kcfg:592
#, kde-format
msgid "Draw Milky Way contour in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowMilkyWay), group (View)
#. +> trunk5
#: kstars.kcfg:593
#, kde-format
msgid "Toggle whether the Milky Way contour is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (FillMilkyWay), group (View)
#. +> trunk5
#: kstars.kcfg:597
#, kde-format
msgid "Fill Milky Way contour? (false means use outline only)"
msgstr ""
#. i18n: ectx: whatsthis, entry (FillMilkyWay), group (View)
#. +> trunk5
#: kstars.kcfg:598
#, kde-format
msgid "Toggle whether the Milky Way contour is filled. When this option is false, the Milky Way is shown as an outline."
msgstr ""
#. i18n: ectx: label, entry (ShowSolarSystem), group (View)
#. +> trunk5
#: kstars.kcfg:602
#, kde-format
msgid "Meta-option for all planets in the sky map."
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowSolarSystem), group (View)
#. +> trunk5
#: kstars.kcfg:603
#, kde-format
msgid "Meta-option to control whether all major planets (and the Sun and Moon) are drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowPlanetImages), group (View)
#. +> trunk5
#: kstars.kcfg:607
#, kde-format
msgid "Draw planets as images in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowPlanetImages), group (View)
#. +> trunk5
#: kstars.kcfg:608
#, kde-format
msgid "Toggle whether major planets (and the Sun and Moon) are rendered as images in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowPlanetNames), group (View)
#. +> trunk5
#: kstars.kcfg:612
#, kde-format
msgid "Label planet names in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowPlanetNames), group (View)
#. +> trunk5
#: kstars.kcfg:613
#, kde-format
msgid "Toggle whether major planets (and the Sun and Moon) are labeled in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowSun), group (View)
#. +> trunk5
#: kstars.kcfg:617
#, kde-format
msgid "Draw Sun in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowSun), group (View)
#. +> trunk5
#: kstars.kcfg:618
#, kde-format
msgid "Toggle whether the Sun is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowMoon), group (View)
#. +> trunk5
#: kstars.kcfg:622
#, kde-format
msgid "Draw Moon in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowMoon), group (View)
#. +> trunk5
#: kstars.kcfg:623
#, kde-format
msgid "Toggle whether the Moon is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowMercury), group (View)
#. +> trunk5
#: kstars.kcfg:627
#, kde-format
msgid "Draw Mercury in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowMercury), group (View)
#. +> trunk5
#: kstars.kcfg:628
#, kde-format
msgid "Toggle whether Mercury is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowVenus), group (View)
#. +> trunk5
#: kstars.kcfg:632
#, kde-format
msgid "Draw Venus in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowVenus), group (View)
#. +> trunk5
#: kstars.kcfg:633
#, kde-format
msgid "Toggle whether Venus is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowMars), group (View)
#. +> trunk5
#: kstars.kcfg:637
#, kde-format
msgid "Draw Mars in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowMars), group (View)
#. +> trunk5
#: kstars.kcfg:638
#, kde-format
msgid "Toggle whether Mars is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowJupiter), group (View)
#. +> trunk5
#: kstars.kcfg:642
#, kde-format
msgid "Draw Jupiter in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowJupiter), group (View)
#. +> trunk5
#: kstars.kcfg:643
#, kde-format
msgid "Toggle whether Jupiter is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowSaturn), group (View)
#. +> trunk5
#: kstars.kcfg:647
#, kde-format
msgid "Draw Saturn in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowSaturn), group (View)
#. +> trunk5
#: kstars.kcfg:648
#, kde-format
msgid "Toggle whether Saturn is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowUranus), group (View)
#. +> trunk5
#: kstars.kcfg:652
#, kde-format
msgid "Draw Uranus in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowUranus), group (View)
#. +> trunk5
#: kstars.kcfg:653
#, kde-format
msgid "Toggle whether Uranus is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowNeptune), group (View)
#. +> trunk5
#: kstars.kcfg:657
#, kde-format
msgid "Draw Neptune in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowNeptune), group (View)
#. +> trunk5
#: kstars.kcfg:658
#, kde-format
msgid "Toggle whether Neptune is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowPluto), group (View)
#. +> trunk5
#: kstars.kcfg:662
#, kde-format
msgid "Draw Pluto in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowPluto), group (View)
#. +> trunk5
#: kstars.kcfg:663
#, kde-format
msgid "Toggle whether Pluto is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowStars), group (View)
#. +> trunk5
#: kstars.kcfg:667
#, kde-format
msgid "Draw stars in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowStars), group (View)
#. +> trunk5
#: kstars.kcfg:668
#, kde-format
msgid "Toggle whether stars are drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowStarMagnitudes), group (View)
#. +> trunk5
#: kstars.kcfg:672
#, kde-format
msgid "Label star magnitudes in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowStarMagnitudes), group (View)
#. +> trunk5
#: kstars.kcfg:673
#, kde-format
msgid "Toggle whether star magnitude (brightness) labels are shown in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowStarNames), group (View)
#. +> trunk5
#: kstars.kcfg:677
#, kde-format
msgid "Label star names in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowStarNames), group (View)
#. +> trunk5
#: kstars.kcfg:678
#, kde-format
msgid "Toggle whether star name labels are shown in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowDeepSkyMagnitudes), group (View)
#. +> trunk5
#: kstars.kcfg:682
#, kde-format
msgid "Label deep-sky object magnitudes in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowDeepSkyMagnitudes), group (View)
#. +> trunk5
#: kstars.kcfg:683
#, kde-format
msgid "Toggle whether deep-sky object magnitude (brightness) labels are shown in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowDeepSkyNames), group (View)
#. +> trunk5
#: kstars.kcfg:687
#, kde-format
msgid "Label deep-sky objects in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowDeepSkyNames), group (View)
#. +> trunk5
#: kstars.kcfg:688
#, kde-format
msgid "Toggle whether deep-sky object name labels are shown in the sky map."
msgstr ""
#. i18n: ectx: label, entry (SlewTimeScale), group (View)
#. +> trunk5
#: kstars.kcfg:692
#, kde-format
msgid "Minimum timescale for forced-slewing mode"
msgstr ""
#. i18n: ectx: whatsthis, entry (SlewTimeScale), group (View)
#. +> trunk5
#: kstars.kcfg:693
#, kde-format
msgid "The timescale above which slewing mode is forced on at all times."
msgstr ""
#. i18n: ectx: label, entry (BoxBGMode), group (View)
#. +> trunk5
#: kstars.kcfg:697
#, kde-format
msgid "InfoBoxes Background fill mode"
msgstr ""
#. i18n: ectx: whatsthis, entry (BoxBGMode), group (View)
#. +> trunk5
#: kstars.kcfg:698
#, kde-format
msgid "The background fill mode for the on-screen information boxes: 0=\"no BG\"; 1=\"semi-transparent BG\"; 2=\"opaque BG\""
msgstr ""
#. i18n: ectx: label, entry (Projection), group (View)
#. +> trunk5
#: kstars.kcfg:702
#, kde-format
msgid "Mapping projection algorithm"
msgstr ""
#. i18n: ectx: whatsthis, entry (Projection), group (View)
#. +> trunk5
#: kstars.kcfg:703
#, kde-format
msgid "Algorithm for the mapping projection."
msgstr ""
#. i18n: ectx: label, entry (UseAbbrevConstellNames), group (View)
#. +> trunk5
#: kstars.kcfg:707
#, kde-format
msgid "Use abbreviated constellation names?"
msgstr ""
#. i18n: ectx: whatsthis, entry (UseAbbrevConstellNames), group (View)
#. +> trunk5
#: kstars.kcfg:708
#, kde-format
msgid "Use official IAU abbreviations for constellation names."
msgstr ""
#. i18n: ectx: label, entry (UseLatinConstellNames), group (View)
#. +> trunk5
#: kstars.kcfg:712
#, kde-format
msgid "Use Latin constellation names?"
msgstr ""
#. i18n: ectx: whatsthis, entry (UseLatinConstellNames), group (View)
#. +> trunk5
#: kstars.kcfg:713
#, kde-format
msgid "Use Latin constellation names."
msgstr ""
#. i18n: ectx: label, entry (UseLocalConstellNames), group (View)
#. +> trunk5
#: kstars.kcfg:717
#, kde-format
msgid "Use localized constellation names?"
msgstr ""
#. i18n: ectx: whatsthis, entry (UseLocalConstellNames), group (View)
#. +> trunk5
#: kstars.kcfg:718
#, kde-format
msgid "Use localized constellation names (if localized names are not available, default to Latin names)."
msgstr ""
#. i18n: ectx: label, entry (UseAltAz), group (View)
#. +> trunk5
#: kstars.kcfg:722
#, kde-format
msgid "Use horizontal coordinate system?"
msgstr ""
#. i18n: ectx: whatsthis, entry (UseAltAz), group (View)
#. +> trunk5
#: kstars.kcfg:723
#, kde-format
msgid "Display the sky with horizontal coordinates (when false, equatorial coordinates will be used)."
msgstr ""
#. i18n: ectx: label, entry (UseAutoLabel), group (View)
#. +> trunk5
#: kstars.kcfg:727
#, kde-format
msgid "Automatically label focused object?"
msgstr ""
#. i18n: ectx: whatsthis, entry (UseAutoLabel), group (View)
#. +> trunk5
#: kstars.kcfg:728
#, kde-format
msgid "Toggle whether a centered object automatically gets a name label attached."
msgstr ""
#. i18n: ectx: label, entry (UseAutoTrail), group (View)
#. +> trunk5
#: kstars.kcfg:732 tools/scriptbuilder.cpp:696
#, kde-format
msgid "Automatically add trail to centered solar system body?"
msgstr ""
#. i18n: ectx: whatsthis, entry (UseAutoTrail), group (View)
#. +> trunk5
#: kstars.kcfg:733
#, kde-format
msgid "Toggle whether a centered solar system object automatically gets a trail attached, as long as it remains centered."
msgstr ""
#. i18n: ectx: label, entry (UseHoverLabel), group (View)
#. +> trunk5
#: kstars.kcfg:737
#, kde-format
msgid "Add temporary label on mouse hover?"
msgstr ""
#. i18n: ectx: whatsthis, entry (UseHoverLabel), group (View)
#. +> trunk5
#: kstars.kcfg:738
#, kde-format
msgid "Toggle whether the object under the mouse cursor gets a transient name label."
msgstr ""
#. i18n: ectx: label, entry (UseRefraction), group (View)
#. +> trunk5
#: kstars.kcfg:742
#, kde-format
msgid "Correct positions for atmospheric refraction?"
msgstr ""
#. i18n: ectx: whatsthis, entry (UseRefraction), group (View)
#. +> trunk5
#: kstars.kcfg:743
#, kde-format
msgid "Toggle whether object positions are corrected for the effects of atmospheric refraction (only applies when horizontal coordinates are used)."
msgstr ""
#. i18n: ectx: label, entry (UseRelativistic), group (View)
#. +> trunk5
#: kstars.kcfg:747
#, kde-format
msgid "Apply relativistic corrections due to the bending of light in sun's gravitational field"
msgstr ""
#. i18n: ectx: whatsthis, entry (UseRelativistic), group (View)
#. +> trunk5
#: kstars.kcfg:748
#, kde-format
msgid "Toggle whether corrections due to bending of light around the sun are taken into account"
msgstr ""
#. i18n: ectx: label, entry (UseAntialias), group (View)
#. +> trunk5
#: kstars.kcfg:752
#, kde-format
msgid "Use antialiasing when drawing the screen?"
msgstr ""
#. i18n: ectx: whatsthis, entry (UseAntialias), group (View)
#. +> trunk5
#: kstars.kcfg:753
#, kde-format
msgid "Toggle whether the sky is rendered using antialiasing. Lines and shapes are smoother with antialiasing, but rendering the screen will take more time."
msgstr ""
#. i18n: ectx: label, entry (ZoomFactor), group (View)
#. +> trunk5
#: kstars.kcfg:757
#, kde-format
msgid "Zoom Factor, in pixels per radian"
msgstr ""
#. i18n: ectx: whatsthis, entry (ZoomFactor), group (View)
#. +> trunk5
#: kstars.kcfg:758
#, kde-format
msgid "The zoom level, measured in pixels per radian."
msgstr ""
#. i18n: ectx: label, entry (ZoomScrollFactor), group (View)
#. +> trunk5
#: kstars.kcfg:764
#, kde-format
msgid "Zoom scroll sensitivity."
msgstr ""
#. i18n: ectx: whatsthis, entry (ZoomScrollFactor), group (View)
#. +> trunk5
#: kstars.kcfg:765
#, kde-format
msgid "When zooming in or out, change zoom speed factor by this multiplier."
msgstr ""
#. i18n: ectx: label, entry (MagLimitAsteroid), group (View)
#. +> trunk5
#: kstars.kcfg:771
#, kde-format
msgid "Faint limit for asteroids"
msgstr ""
#. i18n: ectx: whatsthis, entry (MagLimitAsteroid), group (View)
#. +> trunk5
#: kstars.kcfg:772
#, kde-format
msgid "The faint magnitude limit for drawing asteroids."
msgstr ""
#. i18n: ectx: label, entry (MagLimitAsteroidDownload), group (View)
#. +> trunk5
#: kstars.kcfg:776
#, kde-format
msgid "Maximum magnitude for asteroids to be downloaded from JPL."
msgstr ""
#. i18n: ectx: whatsthis, entry (MagLimitAsteroidDownload), group (View)
#. +> trunk5
#: kstars.kcfg:777
#, kde-format
msgid "The maximum magnitude (visibility) to filter the asteroid data download from JPL."
msgstr ""
#. i18n: ectx: label, entry (AsteroidLabelDensity), group (View)
#. +> trunk5
#: kstars.kcfg:781
#, kde-format
msgid "Label density for asteroid names"
msgstr ""
#. i18n: ectx: whatsthis, entry (AsteroidLabelDensity), group (View)
#. +> trunk5
#: kstars.kcfg:782
#, kde-format
msgid "Controls the relative number of asteroid name labels drawn in the map."
msgstr ""
#. i18n: ectx: label, entry (MagLimitDrawDeepSky), group (View)
#. +> trunk5
#: kstars.kcfg:786
#, kde-format
msgid "Faint limit for deep-sky objects"
msgstr ""
#. i18n: ectx: whatsthis, entry (MagLimitDrawDeepSky), group (View)
#. +> trunk5
#: kstars.kcfg:787
#, kde-format
msgid "The faint magnitude limit for drawing deep-sky objects, when fully zoomed in."
msgstr ""
#. i18n: ectx: label, entry (MagLimitDrawDeepSkyZoomOut), group (View)
#. +> trunk5
#: kstars.kcfg:791
#, kde-format
msgid "Faint limit for deep-sky objects when zoomed out"
msgstr ""
#. i18n: ectx: whatsthis, entry (MagLimitDrawDeepSkyZoomOut), group (View)
#. +> trunk5
#: kstars.kcfg:792
#, kde-format
msgid "The faint magnitude limit for drawing deep-sky objects, when fully zoomed out."
msgstr ""
#. i18n: ectx: label, entry (ShowUnknownMagObjects), group (View)
#. +> trunk5
#: kstars.kcfg:796
#, kde-format
msgid "Show deep-sky objects of unknown magnitude"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowUnknownMagObjects), group (View)
#. +> trunk5
#: kstars.kcfg:797
#, kde-format
msgid "When enabled, objects whose magnitudes are unknown, or not available to KStars, are drawn irrespective of the faint limits set."
msgstr ""
#. i18n: ectx: label, entry (MagLimitDrawStar), group (View)
#. +> trunk5
#: kstars.kcfg:802
#, kde-format
msgid "Faint limit for stars"
msgstr ""
#. i18n: ectx: whatsthis, entry (MagLimitDrawStar), group (View)
#. +> trunk5
#: kstars.kcfg:803
#, kde-format
msgid "The faint magnitude limit for drawing stars, when fully zoomed in."
msgstr ""
#. i18n: ectx: label, entry (StarDensity), group (View)
#. +> trunk5
#: kstars.kcfg:807
#, kde-format
msgid "Density of stars in the field of view"
msgstr ""
#. i18n: ectx: whatsthis, entry (StarDensity), group (View)
#. +> trunk5
#: kstars.kcfg:808
#, kde-format
msgid "Sets the density of stars in the field of view"
msgstr ""
#. i18n: ectx: label, entry (MagLimitDrawStarZoomOut), group (View)
#. +> trunk5
#: kstars.kcfg:813
#, kde-format
msgid "Faint limit for stars when zoomed out"
msgstr ""
#. i18n: ectx: whatsthis, entry (MagLimitDrawStarZoomOut), group (View)
#. +> trunk5
#: kstars.kcfg:814
#, kde-format
msgid "The faint magnitude limit for drawing stars, when fully zoomed out."
msgstr ""
#. i18n: ectx: label, entry (MagLimitHideStar), group (View)
#. +> trunk5
#: kstars.kcfg:819
#, kde-format
msgid "Faint limit for stars when slewing"
msgstr ""
#. i18n: ectx: whatsthis, entry (MagLimitHideStar), group (View)
#. +> trunk5
#: kstars.kcfg:820
#, kde-format
msgid "The faint magnitude limit for drawing stars, when the map is in motion (only applicable if faint stars are set to be hidden while the map is in motion)."
msgstr ""
#. i18n: ectx: label, entry (StarLabelDensity), group (View)
#. +> trunk5
#: kstars.kcfg:824
#, kde-format
msgid "Relative density for star name labels and/or magnitudes"
msgstr ""
#. i18n: ectx: whatsthis, entry (StarLabelDensity), group (View)
#. +> trunk5
#: kstars.kcfg:825
#, kde-format
msgid "The relative density for drawing star name and magnitude labels."
msgstr ""
#. i18n: ectx: label, entry (DeepSkyLabelDensity), group (View)
#. +> trunk5
#: kstars.kcfg:829
#, kde-format
msgid "Relative density for deep-sky object name labels and/or magnitudes"
msgstr ""
#. i18n: ectx: whatsthis, entry (DeepSkyLabelDensity), group (View)
#. +> trunk5
#: kstars.kcfg:830
#, kde-format
msgid "The relative density for drawing deep-sky object name and magnitude labels."
msgstr ""
#. i18n: ectx: label, entry (DeepSkyLongLabels), group (View)
#. +> trunk5
#: kstars.kcfg:834
#, kde-format
msgid "Show long names in deep-sky object name labels?"
msgstr ""
#. i18n: ectx: whatsthis, entry (DeepSkyLongLabels), group (View)
#. +> trunk5
#: kstars.kcfg:835
#, kde-format
msgid "If true, long names (common names) for deep-sky objects are shown in the labels."
msgstr ""
#. i18n: ectx: label, entry (MaxRadCometName), group (View)
#. +> trunk5
#: kstars.kcfg:839
#, kde-format
msgid "Maximum distance from Sun for labeling comets, in AU"
msgstr ""
#. i18n: ectx: whatsthis, entry (MaxRadCometName), group (View)
#. +> trunk5
#: kstars.kcfg:840
#, kde-format
msgid "The maximum solar distance for drawing comets."
msgstr ""
#. i18n: ectx: label, entry (UseGL), group (View)
#. +> trunk5
#: kstars.kcfg:844
#, kde-format
msgid "Switch to OpenGL backend"
msgstr ""
#. i18n: ectx: whatsthis, entry (UseGL), group (View)
#. i18n: ectx: label, entry (RunClock), group (View)
#. +> trunk5
#: kstars.kcfg:849
#, kde-format
msgid "Run clock"
msgstr ""
#. i18n: ectx: whatsthis, entry (RunClock), group (View)
#. +> trunk5
#: kstars.kcfg:850
#, kde-format
msgid "The state of the clock (running or not)"
msgstr ""
#. i18n: ectx: label, entry (ObsListSymbol), group (ObservingList)
#. +> trunk5
#: kstars.kcfg:856
#, kde-format
msgid "Use symbols to label observing list objects"
msgstr ""
#. i18n: ectx: whatsthis, entry (ObsListSymbol), group (ObservingList)
#. +> trunk5
#: kstars.kcfg:857
#, kde-format
msgid "Objects in the observing list will be highlighted with a symbol in the map."
msgstr ""
#. i18n: ectx: label, entry (ObsListText), group (ObservingList)
#. +> trunk5
#: kstars.kcfg:861
#, kde-format
msgid "Use text to label observing list objects"
msgstr ""
#. i18n: ectx: whatsthis, entry (ObsListText), group (ObservingList)
#. +> trunk5
#: kstars.kcfg:862
#, kde-format
msgid "Objects in the observing list will be highlighted with a colored name label in the map."
msgstr ""
#. i18n: ectx: label, entry (ObsListPreferDSS), group (ObservingList)
#. +> trunk5
#: kstars.kcfg:866
#, kde-format
msgid "Prefer Digitized Sky Survey imagery in the observing list"
msgstr ""
#. i18n: ectx: whatsthis, entry (ObsListPreferDSS), group (ObservingList)
#. +> trunk5
#: kstars.kcfg:867
#, kde-format
msgid "The observing list will prefer DSS imagery while downloading imagery."
msgstr ""
#. i18n: ectx: label, entry (ObsListPreferSDSS), group (ObservingList)
#. +> trunk5
#: kstars.kcfg:871
#, kde-format
msgid "Prefer Sloan Digital Sky Survey imagery in the observing list"
msgstr ""
#. i18n: ectx: whatsthis, entry (ObsListPreferSDSS), group (ObservingList)
#. +> trunk5
#: kstars.kcfg:872
#, kde-format
msgid "The observing list will prefer SDSS imagery while downloading imagery."
msgstr ""
#. i18n: ectx: label, entry (ObsListDemoteHole), group (ObservingList)
#. +> trunk5
#: kstars.kcfg:876
#, kde-format
msgid "While sorting by percentage altitude in the observing list, demote objects present in the Dobsonian hole"
msgstr ""
#. i18n: ectx: whatsthis, entry (ObsListDemoteHole), group (ObservingList)
#. +> trunk5
#: kstars.kcfg:877
#, kde-format
msgid "Check this if you use a large Dobsonian telescope. Sorting by percentage current altitude is an easy way of determining what objects are well-placed for observation. However, when using a large Dobsonian telescope, objects close to the zenith are hard to observe. Since tracking there corresponds to a rotation in azimuth, it is both counterintuitive and requires the observer to frequently move the ladder. The region around the zenith where this is particularly frustrating is called the Dobsonian hole. This checkbox makes the observing list consider objects present in the hole as unfit for observation."
msgstr ""
#. i18n: ectx: label, entry (ObsListHoleSize), group (ObservingList)
#. +> trunk5
#: kstars.kcfg:881
#, kde-format
msgid "This is the angular distance from the zenith, in degrees, below which you can easily point your telescope."
msgstr ""
#. i18n: ectx: whatsthis, entry (ObsListHoleSize), group (ObservingList)
#. +> trunk5
#: kstars.kcfg:882
#, kde-format
msgid "This specifies the angular radius of the Dobsonian hole, i.e. the region where a large Dobsonian telescope cannot be pointed easily."
msgstr ""
#. i18n: ectx: label, entry (ObsListCoverage), group (ObservingList)
#. i18n: ectx: whatsthis, entry (XplanetLabel), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1121
#, kde-format
msgid "If true, display a label in the upper right corner."
msgstr ""
#. i18n: ectx: label, entry (XplanetLabelLocalTime), group (Xplanet)
#. i18n: ectx: label, entry (XplanetLabelGMT), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1125 kstars.kcfg:1130
#, kde-format
msgid "Show GMT label"
msgstr ""
#. i18n: ectx: whatsthis, entry (XplanetLabelLocalTime), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1126
#, kde-format
msgid "Show local time."
msgstr ""
#. i18n: ectx: whatsthis, entry (XplanetLabelGMT), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1131
#, kde-format
msgid "Show GMT instead of local time."
msgstr ""
#. i18n: ectx: label, entry (XplanetLabelString), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1135
#, kde-format
msgid "Planet string"
msgstr ""
#. i18n: ectx: whatsthis, entry (XplanetLabelString), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1136
#, kde-format, no-c-format
msgid "Specify the text of the first line of the label. By default, it says something like \"Looking at Earth\". Any instances of %t will be replaced by the target name, and any instances of %o will be replaced by the origin name."
msgstr ""
#. i18n: ectx: label, entry (XplanetFontSize), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1140
#, kde-format
msgid "Font Size"
msgstr ""
#. i18n: ectx: whatsthis, entry (XplanetFontSize), group (Xplanet)
#. i18n: ectx: label, entry (XplanetDateFormat), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1150
#, kde-format
msgid "Date format"
msgstr ""
#. i18n: ectx: whatsthis, entry (XplanetDateFormat), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1151
#, kde-format, no-c-format
msgid "Specify the format for the date/time label. This format string is passed to strftime(3). The default is \"%c %Z\", which shows the date, time, and time zone in the locale’s appropriate date and time representation."
msgstr ""
#. i18n: ectx: label, entry (XplanetLabelTL), group (Xplanet)
#. i18n: ectx: whatsthis, entry (XplanetLongitude), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1192
#, kde-format
msgid "Place the observer above the specified longitude (in degrees). Longitude is positive going east, negative going west (for the earth and moon), so for example Los Angeles is at -118 or 242. The default value is 0."
msgstr ""
#. i18n: ectx: label, entry (XplanetProjection), group (Xplanet)
#. i18n: ectx: whatsthis, entry (XplanetBackground), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1202
#, kde-format
msgid "Use a file as the background image, with the planet to be superimposed upon it. This option is only meaningful with the -projection option. A color may also be supplied."
msgstr ""
#. i18n: ectx: label, entry (XplanetBackgroundImage), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1206
#, kde-format
msgid "Use background image"
msgstr ""
#. i18n: ectx: whatsthis, entry (XplanetBackgroundImage), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1207
#, kde-format
msgid "Use a file as the background image."
msgstr ""
#. i18n: ectx: label, entry (XplanetBackgroundImagePath), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1211
#, kde-format
msgid "Background image path"
msgstr ""
#. i18n: ectx: whatsthis, entry (XplanetBackgroundImagePath), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1212
#, kde-format
msgid "The path of the background image."
msgstr ""
#. i18n: ectx: label, entry (XplanetBackgroundColor), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1216
#, kde-format
msgid "Use background color"
msgstr ""
#. i18n: ectx: whatsthis, entry (XplanetBackgroundColor), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1217
#, kde-format
msgid "Use a color as the background."
msgstr ""
#. i18n: ectx: label, entry (XplanetBackgroundColorValue), group (Xplanet)
msgid "A star of the specified magnitude will have a pixel brightness of 1. The default value is 10. Stars will be drawn more brightly if this number is larger."
msgstr ""
#. i18n: ectx: label, entry (XplanetArcFile), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1231
#, kde-format
msgid "Arc file"
msgstr ""
#. i18n: ectx: whatsthis, entry (XplanetArcFile), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1232
#, kde-format
msgid "If checked, use an arc file to be plotted against the background stars."
msgstr ""
#. i18n: ectx: label, entry (XplanetArcFilePath), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1236
#, kde-format
msgid "Path to arc file"
msgstr ""
#. i18n: ectx: whatsthis, entry (XplanetArcFilePath), group (Xplanet)
#. i18n: ectx: whatsthis, entry (AlwaysRecomputeCoordinates), group (General)
#. +> trunk5
#: kstars.kcfg:1320
#, kde-format
msgid "Checking this option causes recomputation of current equatorial coordinates from catalog coordinates (i.e. application of precession, nutation and aberration corrections) for every redraw of the map. This makes processing slower when there are many stars to handle, but is more likely to be bug free. There are known bugs in the rendering of stars when this recomputation is avoided."
msgstr ""
#. i18n: ectx: label, entry (DefaultDSSImageSize), group (General)
#. +> trunk5
#: kstars.kcfg:1324
#, kde-format
msgid "Default size for DSS images"
msgstr ""
#. i18n: ectx: whatsthis, entry (DefaultDSSImageSize), group (General)
#. +> trunk5
#: kstars.kcfg:1325
#, kde-format
msgid "The default size for DSS images downloaded from the Internet."
msgstr ""
#. i18n: ectx: label, entry (DSSPadding), group (General)
#. +> trunk5
#: kstars.kcfg:1329
#, kde-format
msgid "Additional padding around DSS Images of deep-sky objects"
msgstr ""
#. i18n: ectx: whatsthis, entry (DSSPadding), group (General)
#. +> trunk5
#: kstars.kcfg:1330
#, kde-format
msgid "To include parts of the star field, we add some extra padding around DSS images of deep-sky objects. This option configures the total (both sides) padding added to either dimension of the field."
msgstr ""
#. i18n: ectx: label, entry (VerboseLogging), group (General)
#. +> trunk5
#: kstars.kcfg:1334
#, kde-format
msgid "Enable Verbose Logging"
msgstr ""
#. i18n: ectx: whatsthis, entry (VerboseLogging), group (General)
#. +> trunk5
#: kstars.kcfg:1335
#, kde-format
msgid "Checking this option causes KStars to generate verbose debug information for diagnostic purposes. This may cause slowdown of KStars."
msgstr ""
#. i18n: ectx: label, entry (RegularLogging), group (General)
#. +> trunk5
#: kstars.kcfg:1339
#, kde-format
msgid "Enable Regular Logging"
msgstr ""
#. i18n: ectx: whatsthis, entry (RegularLogging), group (General)
#. +> trunk5
#: kstars.kcfg:1340
#, kde-format
msgid "Checking this option causes KStars to generate regular debug information."
msgstr ""
#. i18n: ectx: label, entry (DisableLogging), group (General)
#. +> trunk5
#: kstars.kcfg:1344
#, kde-format
msgid "Disable Verbose Logging"
msgstr ""
#. i18n: ectx: whatsthis, entry (DisableLogging), group (General)
#. +> trunk5
#: kstars.kcfg:1345
#, kde-format
msgid "Checking this option causes KStars to stop generating ANY debug information."
msgstr ""
#. i18n: ectx: label, entry (LogToDefault), group (General)
#. +> trunk5
#: kstars.kcfg:1349
#, kde-format
msgid "Log debug message to default output"
msgstr ""
#. i18n: ectx: whatsthis, entry (LogToDefault), group (General)
#. +> trunk5
#: kstars.kcfg:1350
#, kde-format
msgid "Checking this option causes KStars log debug messages to the default output used by the platform (e.g. Standard Error)."
msgstr ""
#. i18n: ectx: label, entry (LogToFile), group (General)
#. +> trunk5
#: kstars.kcfg:1354
#, kde-format
msgid "Log debug message to a log file"
msgstr ""
#. i18n: ectx: whatsthis, entry (LogToFile), group (General)
#. +> trunk5
#: kstars.kcfg:1355
#, kde-format
msgid "Checking this option causes KStars log debug messages to a log file as specified."
msgstr ""
#. i18n: ectx: whatsthis, entry (FITSLogging), group (General)
#. +> trunk5
#: kstars.kcfg:1359
#, kde-format
msgid "Log FITS Data activity."
msgstr ""
#. i18n: ectx: whatsthis, entry (INDILogging), group (General)
#. +> trunk5
#: kstars.kcfg:1363
#, kde-format
msgid "Log INDI devices activity."
msgstr ""
#. i18n: ectx: whatsthis, entry (CaptureLogging), group (General)
#. +> trunk5
#: kstars.kcfg:1367
#, kde-format
msgid "Log Ekos Capture Module activity."
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusLogging), group (General)
#. +> trunk5
#: kstars.kcfg:1371
#, kde-format
msgid "Log Ekos Focus Module activity."
msgstr ""
#. i18n: ectx: whatsthis, entry (GuideLogging), group (General)
#. +> trunk5
#: kstars.kcfg:1375
#, kde-format
msgid "Log Ekos Guide Module activity."
msgstr ""
#. i18n: ectx: whatsthis, entry (AlignmentLogging), group (General)
#. +> trunk5
#: kstars.kcfg:1379
#, kde-format
msgid "Log Ekos Alignment Module activity."
msgstr ""
#. i18n: ectx: whatsthis, entry (MountLogging), group (General)
#. +> trunk5
#: kstars.kcfg:1383
#, kde-format
msgid "Log Ekos Mount Module activity."
msgstr ""
#. i18n: ectx: label, entry (useFITSViewer), group (FITSViewer)
#. +> trunk5
#: kstars.kcfg:1389
#, kde-format
msgid "Display every image captured in a FITS Viewer window."
msgstr ""
#. i18n: ectx: label, entry (singlePreviewFITS), group (FITSViewer)
#. +> trunk5
#: kstars.kcfg:1393
#, kde-format
msgid "Preview FITS in a single tab?"
msgstr ""
#. i18n: ectx: label, entry (singleWindowCapturedFITS), group (FITSViewer)
#. +> trunk5
#: kstars.kcfg:1398
#, kde-format
msgid "Display all captured FITS in one window?"
msgstr ""
#. i18n: ectx: whatsthis, entry (singleWindowCapturedFITS), group (FITSViewer)
#. +> trunk5
#: kstars.kcfg:1399
#, kde-format
msgid "Display all captured FITS images in a single FITS Viewer window. By default each camera create its own FITS Viewer instance"
msgstr ""
#. i18n: ectx: label, entry (singleWindowOpenedFITS), group (FITSViewer)
#. +> trunk5
#: kstars.kcfg:1403
#, kde-format
msgid "Display all opened FITS in one window?"
msgstr ""
#. i18n: ectx: whatsthis, entry (singleWindowOpenedFITS), group (FITSViewer)
#. +> trunk5
#: kstars.kcfg:1404
#, kde-format
msgid "Display all opened FITS images in a single FITS Viewer window."
msgstr ""
#. i18n: ectx: whatsthis, entry (focusFITSOnNewImage), group (FITSViewer)
#. +> trunk5
#: kstars.kcfg:1408
#, kde-format
msgid "Bring the FITSViewer window to the foreground when receiving a new image."
msgstr ""
#. i18n: ectx: label, entry (independentWindowFITS), group (FITSViewer)
#. +> trunk5
#: kstars.kcfg:1412
#, kde-format
msgid "Make FITS Viewer window independent of KStars main window"
msgstr ""
#. i18n: ectx: label, entry (AutoDebayer), group (FITSViewer)
#. +> trunk5
#: kstars.kcfg:1416
#, kde-format
msgid "Automatically debayer a FITS image if it is contains a bayer pattern"
msgstr ""
#. i18n: ectx: label, entry (AutoImageToFITS), group (FITSViewer)
#. +> trunk5
#: kstars.kcfg:1420
#, kde-format
msgid "Convert received non-FITS images to FITS for display purposes."
msgstr ""
#. i18n: ectx: label, entry (Auto3DCube), group (FITSViewer)
#. +> trunk5
#: kstars.kcfg:1424
#, kde-format
msgid "Process 3D FITS Cube (RGB). If false, only first channel is processed."
msgstr ""
#. i18n: ectx: label, entry (AutoWCS), group (FITSViewer)
#. +> trunk5
#: kstars.kcfg:1428
#, kde-format
msgid "Automatically process World-Coordinate-System (WCS) data when loading a FITS file."
msgstr ""
#. i18n: ectx: label, entry (LimitedResourcesMode), group (FITSViewer)
#. +> trunk5
#: kstars.kcfg:1432
#, kde-format
msgid "Conserve CPU and memory by disabling all resource-intensive features in FITS Viewer"
msgstr ""
#. i18n: ectx: label, entry (BortleClass), group (WISettings)
#. +> trunk5
#: kstars.kcfg:1438
#, kde-format
msgid "Bortle dark-sky rating"
msgstr ""
#. i18n: ectx: label, entry (TelescopeCheck), group (WISettings)
#. +> trunk5
#: kstars.kcfg:1442
#, kde-format
msgid "Availability of telescope"
msgstr ""
#. i18n: ectx: label, entry (BinocularsCheck), group (WISettings)
#. +> trunk5
#: kstars.kcfg:1446
#, kde-format
msgid "Availability of binoculars"
msgstr ""
#. i18n: ectx: label, entry (BinocularsAperture), group (WISettings)
#. +> trunk5
#: kstars.kcfg:1450
#, kde-format
msgid "Aperture of available binocular"
msgstr ""
#. i18n: ectx: label, entry (ScopeListIndex), group (WISettings)
#. +> trunk5
#: kstars.kcfg:1454
#, kde-format
msgid "Index of selected scope from list of scopes"
msgstr ""
#. i18n: ectx: label, entry (EkosWindowWidth), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1460
#, kde-format
msgid "Ekos window width"
msgstr ""
#. i18n: ectx: label, entry (EkosWindowHeight), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1464
#, kde-format
msgid "Ekos window height"
msgstr ""
#. i18n: ectx: label, entry (EkosLeftIcons), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1472
#, kde-format
msgid "Ekos modules icons are placed to the left of pages"
msgstr ""
#. i18n: ectx: label, entry (RememberCredentials), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1476
#, kde-format
msgid "Remember Ekos Live credentials."
msgstr ""
#. i18n: ectx: label, entry (AutoStartEkosLive), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1480
#, kde-format
msgid "Start Ekos Live on KStars startup."
msgstr ""
#. i18n: ectx: label, entry (EkosLiveOnline), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1484
#, kde-format
msgid "Whether EkosLive connection mode is online."
msgstr ""
#. i18n: ectx: label, entry (EkosLiveUsername), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1488
#, kde-format
msgid "EkosLive username"
msgstr ""
#. i18n: ectx: label, entry (independentWindowEkos), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1491
#, kde-format
msgid "Make Ekos window independent of KStars main window"
msgstr ""
#. i18n: ectx: label, entry (profile), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1495
#, kde-format
msgid "Ekos drivers profile"
msgstr ""
#. i18n: ectx: label, entry (neverLoadConfig), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1499
#, kde-format
msgid "Never load device configuration?"
msgstr ""
#. i18n: ectx: label, entry (loadConfigOnConnection), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1503
#, kde-format
msgid "Load device configuration upon successful connection?"
msgstr ""
#. i18n: ectx: label, entry (loadDefaultConfig), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1507
#, kde-format
msgid "Always load device default configuration upon successful connection?"
msgstr ""
#. i18n: ectx: label, entry (autoLoadSerialAssistant), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1511
#, kde-format
msgid "Automatically load Serial Port Assistant tool when detecting unmapped serial ports?"
msgstr ""
#. i18n: ectx: label, entry (shutterfulCCDs), group (DarkLibrary)
#. +> trunk5
#: kstars.kcfg:1521
#, kde-format
msgid "List of CCDs with mechanical or electronic shutters."
msgstr ""
#. i18n: ectx: label, entry (shutterlessCCDs), group (DarkLibrary)
#. +> trunk5
#: kstars.kcfg:1524
#, kde-format
msgid "List of CCDs without mechanical or electronic shutters."
msgstr ""
#. i18n: ectx: label, entry (MinimumAltLimit), group (Mount)
#. +> trunk5
#: kstars.kcfg:1529
#, kde-format
msgid "Default minimum mount altitude limit"
msgstr ""
#. i18n: ectx: label, entry (MaximumAltLimit), group (Mount)
#. +> trunk5
#: kstars.kcfg:1534
#, kde-format
msgid "Default maximum mount altitude limit."
msgstr ""
#. i18n: ectx: whatsthis, entry (MaximumAltLimit), group (Mount)
#. +> trunk5
#: kstars.kcfg:1535
#, kde-format
msgid "Maximum telescope altitude limit. If the telescope is above this limit, it will be commanded to stop."
msgstr ""
#. i18n: ectx: label, entry (EnableAltitudeLimits), group (Mount)
#. +> trunk5
#: kstars.kcfg:1539
#, kde-format
msgid "Enable mount altitude limits."
msgstr ""
#. i18n: ectx: label, entry (MeridianFlipOffset), group (Mount)
#. +> trunk5
#: kstars.kcfg:1543
#, kde-format
msgid "Default hour angle to perform meridian flip"
msgstr ""
#. i18n: ectx: whatsthis, entry (MeridianFlipOffset), group (Mount)
#. +> trunk5
#: kstars.kcfg:1544
#, kde-format
msgid "If the target hour angle exceeds this value, Ekos will command a meridian flip and if successful it will resume guiding and capture operations."
msgstr ""
#. i18n: ectx: label, entry (ExecuteMeridianFlip), group (Mount)
#. +> trunk5
#: kstars.kcfg:1547
#, kde-format
msgid "Flips the mount when reaching the meridian, if supported."
msgstr ""
#. i18n: ectx: label, entry (DefaultCaptureCCD), group (Capture)
#. +> trunk5
#: kstars.kcfg:1553
#, kde-format
msgid "Default capture module CCD."
msgstr ""
#. i18n: ectx: label, entry (DefaultObserver), group (Capture)
#. +> trunk5
#: kstars.kcfg:1556
#, kde-format
msgid "Default observer full name."
msgstr ""
#. i18n: ectx: label, entry (SyncFOVPA), group (Capture)
#. +> trunk5
#: kstars.kcfg:1559
#, kde-format
msgid "Sync FOV indicator Position Angle with Rotator Settings Position Angle"
msgstr ""
#. i18n: ectx: label, entry (PAMultiplier), group (Capture)
#. +> trunk5
#: kstars.kcfg:1563
#, kde-format
msgid "Position angle multiplier"
msgstr ""
#. i18n: ectx: label, entry (PAOffset), group (Capture)
#. +> trunk5
#: kstars.kcfg:1567
#, kde-format
msgid "Position angle offset"
msgstr ""
#. i18n: ectx: label, entry (GuideDeviation), group (Capture)
#. +> trunk5
#: kstars.kcfg:1571
#, kde-format
msgid "Default maximum permittable guide deviation"
msgstr ""
#. i18n: ectx: whatsthis, entry (GuideDeviation), group (Capture)
#. +> trunk5
#: kstars.kcfg:1572
#, kde-format
msgid "If guide deviation exceeds this limit, the exposure will be automatically aborted and only resumed when the deviation is within this limit."
msgstr ""
#. i18n: ectx: label, entry (HFRDeviation), group (Capture)
#. +> trunk5
#: kstars.kcfg:1576
#, kde-format
msgid "Default maximum permittable HFR deviation"
msgstr ""
#. i18n: ectx: whatsthis, entry (HFRDeviation), group (Capture)
#. +> trunk5
#: kstars.kcfg:1577
#, kde-format
msgid "If HFR deviation exceeds this limit, the autofocus routine will be automatically started."
msgstr ""
#. i18n: ectx: label, entry (EnforceGuideDeviation), group (Capture)
#. +> trunk5
#: kstars.kcfg:1581
#, kde-format
msgid "Enforce guiding deviation limit."
msgstr ""
#. i18n: ectx: label, entry (EnforceAutofocus), group (Capture)
#. +> trunk5
#: kstars.kcfg:1585
#, kde-format
msgid "Enforce Autofocus HFR limit."
msgstr ""
#. i18n: ectx: label, entry (EnforceRefocusEveryN), group (Capture)
#. +> trunk5
#: kstars.kcfg:1589
#, kde-format
msgid "Enforce Refocus Every N Minutes."
msgstr ""
#. i18n: ectx: label, entry (RefocusEveryN), group (Capture)
#. +> trunk5
#: kstars.kcfg:1593
#, kde-format
msgid "Number of minute between forced refocus attempts"
msgstr ""
#. i18n: ectx: whatsthis, entry (RefocusEveryN), group (Capture)
#. +> trunk5
#: kstars.kcfg:1594
#, kde-format
msgid "Sets the time interval before forced autofocus attempts during a capture sequence."
msgstr ""
#. i18n: ectx: label, entry (ResetMountModelAfterMeridian), group (Capture)
#. +> trunk5
#: kstars.kcfg:1598
#, kde-format
msgid "Reset mount model after meridian flip."
msgstr ""
#. i18n: ectx: label, entry (CalibrationADUValue), group (Capture)
#. +> trunk5
#: kstars.kcfg:1602
#, kde-format
msgid "Desired flat field ADU"
msgstr ""
#. i18n: ectx: whatsthis, entry (CalibrationADUValue), group (Capture)
#. +> trunk5
#: kstars.kcfg:1603
#, kde-format
msgid "If set, Ekos will capture a few flat images to determine the optimal exposure time to achieve the desired ADU value."
msgstr ""
#. i18n: ectx: label, entry (CalibrationADUValueTolerance), group (Capture)
#. +> trunk5
#: kstars.kcfg:1607
#, kde-format
msgid "ADU Value tolerance"
msgstr ""
#. i18n: ectx: whatsthis, entry (CalibrationADUValueTolerance), group (Capture)
#. +> trunk5
#: kstars.kcfg:1608
#, kde-format
msgid "Maximum difference between measured and target ADU values to deem the value as acceptable."
msgstr ""
#. i18n: ectx: label, entry (CalibrationFlatSourceIndex), group (Capture)
#. +> trunk5
#: kstars.kcfg:1612
#, kde-format
msgid "Index of flat source option."
msgstr ""
#. i18n: ectx: label, entry (CalibrationFlatDurationIndex), group (Capture)
#. +> trunk5
#: kstars.kcfg:1616
#, kde-format
msgid "Index of flat duration option."
msgstr ""
#. i18n: ectx: label, entry (CalibrationWallAz), group (Capture)
#. +> trunk5
#: kstars.kcfg:1620
#, kde-format
msgid "Azimuth of calibration wall location."
msgstr ""
#. i18n: ectx: label, entry (CalibrationWallAlt), group (Capture)
#. +> trunk5
#: kstars.kcfg:1624
#, kde-format
msgid "Altitude of calibration wall location."
msgstr ""
#. i18n: ectx: label, entry (MaxTemperatureDiff), group (Capture)
#. +> trunk5
#: kstars.kcfg:1628
#, kde-format
msgid "Maximum acceptable difference between requested and measured temperature set point."
msgstr ""
#. i18n: ectx: label, entry (GuidingSettle), group (Capture)
#. +> trunk5
#: kstars.kcfg:1632
#, kde-format
msgid "Wait this many seconds after guiding is resumed before starting capture."
msgstr ""
#. i18n: ectx: label, entry (FlatSyncFocus), group (Capture)
#. +> trunk5
#: kstars.kcfg:1640
#, kde-format
msgid "Capture flat frames at the same focus position of light frames."
msgstr ""
#. i18n: ectx: label, entry (HFRThresholdPercentage), group (Capture)
#. +> trunk5
#: kstars.kcfg:1644
#, kde-format
msgid "Increase autofocus HFR value by this percentage gain and store it in Capture Module."
msgstr ""
#. i18n: ectx: label, entry (UseMedianFocus), group (Capture)
#. +> trunk5
#: kstars.kcfg:1648
#, kde-format
msgid "Calculate median focus value after each autofocus operation is complete."
msgstr ""
#. i18n: ectx: label, entry (SaveHFRToFile), group (Capture)
#. +> trunk5
#: kstars.kcfg:1652
#, kde-format
msgid "When saving a sequence file, save current HFR threshold value. By default, zero value is used."
msgstr ""
#. i18n: ectx: label, entry (AutoStretch), group (Capture)
#. +> trunk5
#: kstars.kcfg:1664
#, kde-format
msgid "Perform auto stretch on captured images in FITS Viewer."
msgstr ""
#. i18n: ectx: label, entry (useSummaryPreview), group (Capture)
#. +> trunk5
#: kstars.kcfg:1668
#, kde-format
msgid "Display every image captured sequence image in the Ekos summary screen preview window."
msgstr ""
#. i18n: ectx: label, entry (useDSLRImageViewer), group (Capture)
#. +> trunk5
#: kstars.kcfg:1672
#, kde-format
msgid "Display every captured DSLR image in the Image Viewer window."
msgstr ""
#. i18n: ectx: label, entry (CaptureFormatIndex), group (Capture)
#. +> trunk5
#: kstars.kcfg:1676
#, kde-format
msgid "Index of desired capture format (FITS or Native)."
msgstr ""
#. i18n: ectx: label, entry (CaptureDirectory), group (Capture)
#. +> trunk5
#: kstars.kcfg:1680
#, kde-format
msgid "Path to capture directory to save images."
msgstr ""
#. i18n: ectx: label, entry (RemoteCaptureDirectory), group (Capture)
#. +> trunk5
#: kstars.kcfg:1684
#, kde-format
msgid "Path to remote capture directory to save images."
msgstr ""
#. i18n: ectx: label, entry (ManualCoverTimeout), group (Capture)
#. +> trunk5
#: kstars.kcfg:1687
#, kde-format
msgid "Cover or uncover telescope dialog timeout in seconds."
msgstr ""
#. i18n: ectx: label, entry (DefaultFocusCCD), group (Focus)
#. +> trunk5
#: kstars.kcfg:1693
#, kde-format
msgid "Default focus module CCD."
msgstr ""
#. i18n: ectx: label, entry (DefaultFocusFocuser), group (Focus)
#. +> trunk5
#: kstars.kcfg:1696
#, kde-format
msgid "Default focus module focuser."
msgstr ""
#. i18n: ectx: label, entry (DefaultFocusFilterWheel), group (Focus)
#. +> trunk5
#: kstars.kcfg:1699
#, kde-format
msgid "Default focus module filter wheel."
msgstr ""
#. i18n: ectx: label, entry (FocusTicks), group (Focus)
#. +> trunk5
#: kstars.kcfg:1702
#, kde-format
msgid "Default Focuser step ticks"
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusTicks), group (Focus)
#. +> trunk5
#: kstars.kcfg:1703
#, kde-format
msgid "Step size of the absolute focuser. The step size TICKS should be adjusted so that when the focuser moves TICKS steps, the difference in HFR is more than 0.1 pixels. Lower the value when you are close to optimal focus."
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusSettleTime), group (Focus)
#. +> trunk5
#: kstars.kcfg:1707
#, kde-format
msgid "Wait for this many seconds after moving the focuser before capturing the next image during AutoFocus."
msgstr ""
#. i18n: ectx: whatsthis, entry (GuideSettleTime), group (Focus)
#. +> trunk5
#: kstars.kcfg:1711
#, kde-format
msgid "Wait for this many seconds after resuming guide."
msgstr ""
#. i18n: ectx: label, entry (FocusTolerance), group (Focus)
#. +> trunk5
#: kstars.kcfg:1715
#, kde-format
msgid "Default Focuser tolerance value"
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusTolerance), group (Focus)
#. +> trunk5
#: kstars.kcfg:1716
#, kde-format
msgid "The tolerance specifies the percentage difference between the current focusing position and the minimum obtained during the focusing run. Adjustment of this value is necessary to prevent the focusing algorithm from oscillating back and forth."
msgstr ""
#. i18n: ectx: label, entry (FocusMaxTravel), group (Focus)
#. +> trunk5
#: kstars.kcfg:1720
#, kde-format
msgid "Maximum Focus Travel Distance"
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusMaxTravel), group (Focus)
#. +> trunk5
#: kstars.kcfg:1721
#, kde-format
msgid "Set the maximum travel distance of an absolute focuser."
msgstr ""
#. i18n: ectx: label, entry (FocusGain), group (Focus)
#. +> trunk5
#: kstars.kcfg:1725
#, kde-format
msgid "Default Focuser gain value"
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusGain), group (Focus)
#. +> trunk5
#: kstars.kcfg:1726
#, kde-format
msgid "Specifies gain value of CCD when performing focusing if supported by camera."
msgstr ""
#. i18n: ectx: label, entry (FocusBoxSize), group (Focus)
#. +> trunk5
#: kstars.kcfg:1730
#, kde-format
msgid "Default Focuser star selection box size"
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusBoxSize), group (Focus)
#. +> trunk5
#: kstars.kcfg:1731
#, kde-format
msgid "Set box size to select a focus star."
msgstr ""
#. i18n: ectx: label, entry (FocusXBin), group (Focus)
#. +> trunk5
#: kstars.kcfg:1735
#, kde-format
msgid "Default CCD X binning in focus mode"
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusXBin), group (Focus)
#. +> trunk5
#: kstars.kcfg:1736
#, kde-format
msgid "Set horizontal binning of CCD camera while in focus mode."
msgstr ""
#. i18n: ectx: label, entry (FocusYBin), group (Focus)
#. +> trunk5
#: kstars.kcfg:1740
#, kde-format
msgid "Default CCD Y binning in focus mode"
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusYBin), group (Focus)
#. +> trunk5
#: kstars.kcfg:1741
#, kde-format
msgid "Set vertical binning of CCD camera while in focus mode."
msgstr ""
#. i18n: ectx: label, entry (FocusSubFrame), group (Focus)
#. +> trunk5
#: kstars.kcfg:1745
#, kde-format
msgid "Subframe the focus star during the autofocus procedure."
msgstr ""
#. i18n: ectx: label, entry (FocusUseFullField), group (Focus)
#. +> trunk5
#: kstars.kcfg:1749
#, kde-format
msgid "Measure average HFR from all stars combined in a full frame. This method defaults to the Centroid detection, but can use SEP detection too. Its performance decreases as the number of stars increases."
msgstr ""
#. i18n: ectx: label, entry (FocusFullFieldInnerRadius), group (Focus)
#. +> trunk5
#: kstars.kcfg:1753
#, kde-format
msgid "Full field inner radius."
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusFullFieldInnerRadius), group (Focus)
#. +> trunk5
#: kstars.kcfg:1754
#, kde-format, no-c-format
msgid "During full field focusing, stars which are inside this percentage of the frame are filtered out of HFR calculation (default 0%). Detection algorithms may also have an inherent filter."
msgstr ""
#. i18n: ectx: label, entry (FocusFullFieldOuterRadius), group (Focus)
#. +> trunk5
#: kstars.kcfg:1758
#, kde-format
msgid "Full field outer radius."
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusFullFieldOuterRadius), group (Focus)
#. +> trunk5
#: kstars.kcfg:1759
#, kde-format, no-c-format
msgid "During full field focusing, stars which are outside this percentage of the frame are filtered out of HFR calculation (default 100%). Detection algorithms may also have an inherent filter."
msgstr ""
#. i18n: ectx: label, entry (FocusAutoStarEnabled), group (Focus)
#. +> trunk5
#: kstars.kcfg:1763
#, kde-format
msgid "Automatically select a star to focus."
msgstr ""
#. i18n: ectx: label, entry (SuspendGuiding), group (Focus)
#. +> trunk5
#: kstars.kcfg:1767
#, kde-format
msgid "Suspend guiding while autofocus in progress."
msgstr ""
#. i18n: ectx: label, entry (UseFocusDarkFrame), group (Focus)
#. +> trunk5
#: kstars.kcfg:1771
#, kde-format
msgid "Take a dark frame and subtract it before running autofocus operation."
msgstr ""
#. i18n: ectx: label, entry (FocusEffect), group (Focus)
#. +> trunk5
#: kstars.kcfg:1775
#, kde-format
msgid "Image filter to be applied to focus image upon loading."
msgstr ""
#. i18n: ectx: label, entry (FocusThreshold), group (Focus)
#. +> trunk5
#: kstars.kcfg:1779
#, kde-format
msgid "Relative percentage strength of centroid edge pixel strength to average pixel value."
msgstr ""
#. i18n: ectx: label, entry (FocusDetection), group (Focus)
#. +> trunk5
#: kstars.kcfg:1783
#, kde-format
msgid "Star detection algorithm"
msgstr ""
#. i18n: ectx: label, entry (FocusAlgorithm), group (Focus)
#. +> trunk5
#: kstars.kcfg:1787
#, kde-format
msgid "Focus process algorithm"
msgstr ""
#. i18n: ectx: label, entry (FocusFramesCount), group (Focus)
#. +> trunk5
#: kstars.kcfg:1791
#, kde-format
msgid "Number of focus frames to average for HFR calculations."
msgstr ""
#. i18n: ectx: label, entry (DefaultAlignCCD), group (Align)
#. +> trunk5
#: kstars.kcfg:1797
#, kde-format
msgid "Default align module CCD."
msgstr ""
#. i18n: ectx: label, entry (DefaultAlignFW), group (Align)
#. +> trunk5
#: kstars.kcfg:1800
#, kde-format
msgid "Default align module Filter Wheel."
msgstr ""
#. i18n: ectx: label, entry (AlignExposure), group (Align)
#. +> trunk5
#: kstars.kcfg:1803
#, kde-format
msgid "Default alignment exposure value"
msgstr ""
#. i18n: ectx: whatsthis, entry (AlignExposure), group (Align)
#. +> trunk5
#: kstars.kcfg:1804
#, kde-format
msgid "Specifies exposure value of CCD in seconds when performing plate solving."
msgstr ""
#. i18n: ectx: label, entry (SolverBinningIndex), group (Align)
#. +> trunk5
#: kstars.kcfg:1808
#, kde-format
msgid "Default CCD binning index while in alignment mode"
msgstr ""
#. i18n: ectx: whatsthis, entry (SolverBinningIndex), group (Align)
#. +> trunk5
#: kstars.kcfg:1809
#, kde-format
msgid "Set binning index of CCD camera while in alignment mode. Default values 0-3 corresponding to 1x1 to 4x4 binning. 4 is max binning."
msgstr ""
#. i18n: ectx: whatsthis, entry (AstrometryUseRotator), group (Align)
#. +> trunk5
#: kstars.kcfg:1813
#, kde-format
msgid "Use rotator when performing load and slew."
msgstr ""
#. i18n: ectx: whatsthis, entry (AstrometryRotatorThreshold), group (Align)
#. +> trunk5
#: kstars.kcfg:1817
#, kde-format
msgid "Threshold between measured and FITS position angles in arcminutes to consider the load and slew operation successful."
msgstr ""
#. i18n: ectx: label, entry (SolverType), group (Align)
#. +> trunk5
#: kstars.kcfg:1821
#, kde-format
msgid "Set solver type (online, offline, remote)."
msgstr ""
#. i18n: ectx: label, entry (SolverScopeType), group (Align)
#. +> trunk5
#: kstars.kcfg:1825
#, kde-format
msgid "Index of telescope type to be used when solving an image. 0 for Primary, 1 for Guide"
msgstr ""
#. i18n: ectx: label, entry (SolverGotoOption), group (Align)
#. +> trunk5
#: kstars.kcfg:1829
#, kde-format
msgid "Action to take if solver if successful (Sync, Slew to Target, or None)"
msgstr ""
#. i18n: ectx: label, entry (AstrometrySolverWCS), group (Align)
#. +> trunk5
#: kstars.kcfg:1833
#, kde-format
msgid "World Coordinate System (WCS). WCS is used to encode RA/DEC coordinates in captured CCD images."
msgstr ""
#. i18n: ectx: label, entry (AstrometrySolverOverlay), group (Align)
#. +> trunk5
#: kstars.kcfg:1837
#, kde-format
msgid "Display received FITS images unto solver FOV rectangle in the sky map."
msgstr ""
#. i18n: ectx: label, entry (AstrometryDifferentialSlewing), group (Align)
#. +> trunk5
#: kstars.kcfg:1841
#, kde-format
msgid "Do not use Sync when Slew to Target is selected. Use differential slewing to correct for discrepancies."
msgstr ""
#. i18n: ectx: label, entry (SolverAccuracyThreshold), group (Align)
#. +> trunk5
#: kstars.kcfg:1845
#, kde-format
msgid "Accuracy threshold in arcseconds between solution and target coordinates."
msgstr ""
#. i18n: ectx: label, entry (LockAlignFilterIndex), group (Align)
#. +> trunk5
#: kstars.kcfg:1849
#, kde-format
msgid "Use specified filter index when performing astrometry regardless of current filter settings."
msgstr ""
#. i18n: ectx: label, entry (AlignDarkFrame), group (Align)
#. +> trunk5
#: kstars.kcfg:1853
#, kde-format
msgid "Take a dark frame and subtract it before running astrometry operation."
msgstr ""
#. i18n: ectx: label, entry (SettlingTime), group (Align)
#. +> trunk5
#: kstars.kcfg:1857
#, kde-format
msgid "Time to wait in milliseconds after telescope slewing is complete before starting the next capture."
msgstr ""
#. i18n: ectx: label, entry (AstrometryUseNoFITS2FITS), group (Align)
#. +> trunk5
#: kstars.kcfg:1861
#, kde-format
msgid "Do not sanitize FITS. This option should only be checked if astrometry.net version is 0.67 or earlier. Uncheck for any versions greater than 0.67."
msgstr ""
#. i18n: ectx: label, entry (AstrometryImageScaleLow), group (Align)
#. +> trunk5
#: kstars.kcfg:1877
#, kde-format
msgid "Lower image scale."
msgstr ""
#. i18n: ectx: label, entry (AstrometryImageScaleHigh), group (Align)
#. +> trunk5
#: kstars.kcfg:1880
#, kde-format
msgid "Upper image scale."
msgstr ""
#. i18n: ectx: label, entry (AstrometryAutoUpdateImageScale), group (Align)
#. +> trunk5
#: kstars.kcfg:1883
#, kde-format
msgid "Automatically update image scale when CCD or Mount parameters are updated."
msgstr ""
#. i18n: ectx: label, entry (AstrometryImageScaleUnits), group (Align)
#. +> trunk5
#: kstars.kcfg:1887
#, kde-format
msgid "Image scale units in arcminutes (aw), degrees (dw), or arcsec per pixel (app)"
msgstr ""
#. i18n: ectx: label, entry (AstrometryDownsample), group (Align)
#. +> trunk5
#: kstars.kcfg:1895
#, kde-format
msgid "Downsample factor"
msgstr ""
#. i18n: ectx: label, entry (AstrometryAutoDownsample), group (Align)
#. +> trunk5
#: kstars.kcfg:1899
#, kde-format
msgid "Automatically downsample based on image size."
msgstr ""
#. i18n: ectx: label, entry (AstrometryPositionRA), group (Align)
#. +> trunk5
#: kstars.kcfg:1907
#, kde-format
msgid "User supplied Right Ascension value in degrees to be passed to the solver."
msgstr ""
#. i18n: ectx: label, entry (AstrometryPositionDE), group (Align)
#. +> trunk5
#: kstars.kcfg:1910
#, kde-format
msgid "User supplied declination value in degrees to be passed to the solver."
msgstr ""
#. i18n: ectx: label, entry (AstrometryAutoUpdatePosition), group (Align)
#. +> trunk5
#: kstars.kcfg:1913
#, kde-format
msgid "Automatically update position coordinates when mounts completes slewing."
msgstr ""
#. i18n: ectx: label, entry (AstrometryCustomOptions), group (Align)
#. i18n: ectx: label, entry (AstrometrySolverBinary), group (Align)
#. +> trunk5
#: kstars.kcfg:1928
#, kde-format
msgid "astrometry.net solve-field binary"
msgstr ""
#. i18n: ectx: whatsthis, entry (AstrometrySolverBinary), group (Align)
#. +> trunk5
#: kstars.kcfg:1929
#, kde-format
msgid "Path to astrometry.net solver location."
msgstr ""
#. i18n: ectx: label, entry (AstrometryWCSInfo), group (Align)
#. +> trunk5
#: kstars.kcfg:1937
#, kde-format
msgid "astrometry.net wcsinfo binary"
msgstr ""
#. i18n: ectx: whatsthis, entry (AstrometryWCSInfo), group (Align)
#. +> trunk5
#: kstars.kcfg:1938
#, kde-format
msgid "Path to astrometry.net wcsinfo location."
msgstr ""
#. i18n: ectx: label, entry (AstrometryConfFile), group (Align)
#. +> trunk5
#: kstars.kcfg:1946
#, kde-format
msgid "astrometry.net configuration file"
msgstr ""
#. i18n: ectx: whatsthis, entry (AstrometryConfFile), group (Align)
#. +> trunk5
#: kstars.kcfg:1947
#, kde-format
msgid "Path to astrometry.net file location."
msgstr ""
#. i18n: ectx: label, entry (AstrometryIndexFileLocation), group (Align)
#. +> trunk5
#: kstars.kcfg:1951
#, kde-format
msgid "Astrometry.net Index files Location"
msgstr ""
#. i18n: ectx: whatsthis, entry (AstrometryIndexFileLocation), group (Align)
#. +> trunk5
#: kstars.kcfg:1952
#, kde-format
msgid "Astrometry.net Index files Location."
msgstr ""
#. i18n: ectx: label, entry (AstrometryConfFileIsInternal), group (Align)
#. +> trunk5
#: kstars.kcfg:1956
#, kde-format
msgid "Internal or External Astrometry.net Conf File?"
msgstr ""
#. i18n: ectx: label, entry (UseDefaultPython), group (Align)
#. +> trunk5
#: kstars.kcfg:1960
#, kde-format
msgid "Use the Default System Python Path"
msgstr ""
#. i18n: ectx: whatsthis, entry (PythonExecPath), group (Align)
#. +> trunk5
#: kstars.kcfg:1965
#, kde-format
msgid "Folder in which the desired python executable or link to be used for astrometry.net resides."
msgstr ""
#. i18n: ectx: label, entry (AstrometryAPIKey), group (Align)
#. +> trunk5
#: kstars.kcfg:1970
#, kde-format
msgid "astrometry.net API Key"
msgstr ""
#. i18n: ectx: whatsthis, entry (AstrometryAPIKey), group (Align)
#. +> trunk5
#: kstars.kcfg:1971
#, kde-format
msgid "Key to access astrometry.net online web services. You must register with astrometry.net to obtain a key."
msgstr ""
#. i18n: ectx: label, entry (AstrometryAPIURL), group (Align)
#. +> trunk5
#: kstars.kcfg:1975
#, kde-format
msgid "astrometry.net API URL"
msgstr ""
#. i18n: ectx: label, entry (AstrometryUseJPEG), group (Align)
#. +> trunk5
#: kstars.kcfg:1979
#, kde-format
msgid "Use JPEG format, instead of FITS, to upload images to the astrometry.net online service."
msgstr ""
#. i18n: ectx: label, entry (AstrometryTimeout), group (Align)
#. +> trunk5
#: kstars.kcfg:1983
#, kde-format
msgid "Timeout in seconds to wait for astrometry solver to complete."
msgstr ""
#. i18n: ectx: label, entry (PAHMountSpeedIndex), group (Align)
#. +> trunk5
#: kstars.kcfg:1987
#, kde-format
msgid "Speed index to set mount in Polar Alignment Assistant Tool."
msgstr ""
#. i18n: ectx: label, entry (PAHAutoPark), group (Align)
#. +> trunk5
#: kstars.kcfg:1991
#, kde-format
msgid "Automatically park the mount after Polar Alignment Assistant Tool is complete."
msgstr ""
#. i18n: ectx: label, entry (DefaultGuideCCD), group (Guide)
#. +> trunk5
#: kstars.kcfg:1997
#, kde-format
msgid "Default guide module CCD."
msgstr ""
#. i18n: ectx: label, entry (DefaultST4Driver), group (Guide)
#. +> trunk5
#: kstars.kcfg:2000
#, kde-format
msgid "Default guide module ST4 Driver."
msgstr ""
#. i18n: ectx: label, entry (GuideExposure), group (Guide)
#. +> trunk5
#: kstars.kcfg:2003
#, kde-format
msgid "Guider exposure duration in seconds."
msgstr ""
#. i18n: ectx: label, entry (GuiderType), group (Guide)
#. +> trunk5
#: kstars.kcfg:2007
#, kde-format
msgid "Which guider process to utilize for guiding (0 Internal Guider, 1 PHD2, 2 lin_guider)"
msgstr ""
#. i18n: ectx: label, entry (GuideAlgorithm), group (Guide)
#. +> trunk5
#: kstars.kcfg:2011
#, kde-format
msgid "Which Algorithm to use track guide square (0 smart, 1 fast, 2 threshold, 3 no threshold)."
msgstr ""
#. i18n: ectx: label, entry (PHD2Host), group (Guide)
#. +> trunk5
#: kstars.kcfg:2015
#, kde-format
msgid "Host name of external PHD2 service"
msgstr ""
#. i18n: ectx: label, entry (PHD2Port), group (Guide)
#. +> trunk5
#: kstars.kcfg:2019
#, kde-format
msgid "PHD2 Event Monitoring Port"
msgstr ""
#. i18n: ectx: label, entry (LinGuiderHost), group (Guide)
#. +> trunk5
#: kstars.kcfg:2023
#, kde-format
msgid "Host name of external lin_guider service"
msgstr ""
#. i18n: ectx: label, entry (LinGuiderPort), group (Guide)
#. +> trunk5
#: kstars.kcfg:2027
#, kde-format
msgid "Lin_guider Event Monitoring Port"
msgstr ""
#. i18n: ectx: label, entry (GuideScopeType), group (Guide)
#. +> trunk5
#: kstars.kcfg:2031
#, kde-format
msgid "Index of telescope type to be used when guiding. 0 for Primary, 1 for Guide"
msgstr ""
#. i18n: ectx: label, entry (CalibrationPulseDuration), group (Guide)
#. +> trunk5
#: kstars.kcfg:2035
#, kde-format
msgid "Pulse duration in milliseconds used for guiding pulses during calibration stage."
msgstr ""
#. i18n: ectx: label, entry (GuideSquareSizeIndex), group (Guide)
#. +> trunk5
#: kstars.kcfg:2039
#, kde-format
msgid "Guide square size index (0 to 4) corresponding to pixel sizes (8 to 128)."
msgstr ""
#. i18n: ectx: label, entry (ImageGuidingEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2043
#, kde-format
msgid "Use Image Guiding algorithms instead of classical centroid guiding."
msgstr ""
#. i18n: ectx: label, entry (GuideRegionAxis), group (Guide)
#. +> trunk5
#: kstars.kcfg:2047
#, kde-format
msgid "Region Axis Index (0 to 4) corresponding to NxN partition size used Image Guiding (64 to 1024)."
msgstr ""
#. i18n: ectx: label, entry (GuideAutoStarEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2051
#, kde-format
msgid "Automatically select calibration star and perform calibration."
msgstr ""
#. i18n: ectx: label, entry (GuideRemoteImagesEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2059
#, kde-format
msgid "When using external guiders, enable reception of remote images in Ekos guide module. By default, remote images are disabled."
msgstr ""
#. i18n: ectx: label, entry (AutoModeIterations), group (Guide)
#. +> trunk5
#: kstars.kcfg:2063
#, kde-format
msgid "Number of automode iterations for calibration process."
msgstr ""
#. i18n: ectx: label, entry (GuideLostStarTimeout), group (Guide)
#. +> trunk5
#: kstars.kcfg:2067
#, kde-format
msgid "When star tracking is lost, wait this many seconds before aborting."
msgstr ""
#. i18n: ectx: label, entry (GuideMaxDeltaRMS), group (Guide)
#. +> trunk5
#: kstars.kcfg:2071
#, kde-format
msgid "Maximum delta RMS permitted while guiding before aborting."
msgstr ""
#. i18n: ectx: label, entry (TwoAxisEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2075
#, kde-format
msgid "Use both axes to perform calibration."
msgstr ""
#. i18n: ectx: label, entry (RapidGuideEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2079
#, kde-format
msgid "Use driver side Rapid Guide to perform guiding."
msgstr ""
#. i18n: ectx: label, entry (GuideDarkFrameEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2083
#, kde-format
msgid "Take dark frame for autoguider images."
msgstr ""
#. i18n: ectx: label, entry (GuideSubframeEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2087
#, kde-format
msgid "Subframe guide image around selected region"
msgstr ""
#. i18n: ectx: label, entry (DitherPixels), group (Guide)
#. +> trunk5
#: kstars.kcfg:2091
#, kde-format
msgid "How many pixels to move between subsequent exposures under auto dithering mode."
msgstr ""
#. i18n: ectx: label, entry (DitherFrames), group (Guide)
#. +> trunk5
#: kstars.kcfg:2095
#, kde-format
msgid "Dither after this many frames."
msgstr ""
#. i18n: ectx: label, entry (DitherThreshold), group (Guide)
#. +> trunk5
#: kstars.kcfg:2103
#, kde-format
msgid "Maximum distance (pixels) for guiding to be considered settled."
msgstr ""
#. i18n: ectx: label, entry (DitherTimeout), group (Guide)
#. +> trunk5
#: kstars.kcfg:2107
#, kde-format
msgid "Time limit (seconds) on dithering to settle down."
msgstr ""
#. i18n: ectx: label, entry (DitherMaxIterations), group (Guide)
#. +> trunk5
#: kstars.kcfg:2111
#, kde-format
msgid "How many dithering attempts to undertake before giving up."
msgstr ""
#. i18n: ectx: label, entry (DitherNoGuidingPulse), group (Guide)
#. +> trunk5
#: kstars.kcfg:2115
#, kde-format
msgid "Pulse length in milliseconds used for non-guiding dither."
msgstr ""
#. i18n: ectx: label, entry (DitherFailAbortsAutoGuide), group (Guide)
#. +> trunk5
#: kstars.kcfg:2119
#, kde-format
msgid "If dithering fails then abort autoguide."
msgstr ""
#. i18n: ectx: label, entry (DitherEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2123
#, kde-format
msgid "Use Auto Dithering when guiding."
msgstr ""
#. i18n: ectx: label, entry (DitherNoGuiding), group (Guide)
#. +> trunk5
#: kstars.kcfg:2127
#, kde-format
msgid "Perform dithering even when not guiding."
msgstr ""
#. i18n: ectx: label, entry (AOLimit), group (Guide)
#. +> trunk5
#: kstars.kcfg:2131
#, kde-format
msgid "The Adaptive Optics unit is utilized if the guiding deviation is less than this limit in arcseconds. Once exceeded, mechanical guiding is utilized."
msgstr ""
#. i18n: ectx: label, entry (RAGuideEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2135
#, kde-format
msgid "Enable autoguiding in the RA axis."
msgstr ""
#. i18n: ectx: label, entry (DECGuideEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2139
#, kde-format
msgid "Enable autoguiding in the DEC axis."
msgstr ""
#. i18n: ectx: label, entry (NorthDECGuideEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2143
#, kde-format
msgid "Enable North autoguiding in the DEC axis."
msgstr ""
#. i18n: ectx: label, entry (SouthDECGuideEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2147
#, kde-format
msgid "Enable South autoguiding in the DEC axis."
msgstr ""
#. i18n: ectx: label, entry (EastRAGuideEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2151
#, kde-format
msgid "Enable East autoguiding in the RA axis."
msgstr ""
#. i18n: ectx: label, entry (WestRAGuideEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2155
#, kde-format
msgid "Enable West autoguiding in the RA axis."
msgstr ""
#. i18n: ectx: label, entry (GuiderAccuracyThreshold), group (Guide)
#. +> trunk5
#: kstars.kcfg:2192
#, kde-format
msgid "Accuracy threshold for the Guide Graphs."
msgstr ""
#. i18n: ectx: label, entry (RADisplayedOnGuideGraph), group (Guide)
#. +> trunk5
#: kstars.kcfg:2196
#, kde-format
msgid "Display the RA Plot on the Guide Drift Graphics."
msgstr ""
#. i18n: ectx: label, entry (DEDisplayedOnGuideGraph), group (Guide)
#. +> trunk5
#: kstars.kcfg:2200
#, kde-format
msgid "Display the DEC Plot on the Guide Drift Graphics."
msgstr ""
#. i18n: ectx: label, entry (RACorrDisplayedOnGuideGraph), group (Guide)
#. +> trunk5
#: kstars.kcfg:2204
#, kde-format
msgid "Display the RA Corrections Plot on the Guide Drift Graphics."
msgstr ""
#. i18n: ectx: label, entry (DECorrDisplayedOnGuideGraph), group (Guide)
#. +> trunk5
#: kstars.kcfg:2208
#, kde-format
msgid "Display the DEC Corrections Plot on the Guide Drift Graphics."
msgstr ""
#. i18n: ectx: whatsthis, entry (SchedulerLogging), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2214
#, kde-format
msgid "Log Ekos Scheduler Module activity."
msgstr ""
#. i18n: ectx: whatsthis, entry (SortSchedulerJobs), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2218
#, kde-format
msgid "Sort scheduler jobs by priority and altitude."
msgstr ""
#. i18n: ectx: label, entry (StopEkosAfterShutdown), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2222
#, kde-format
msgid "After shutdown procedure is successfully executed, shutdown INDI and Ekos."
msgstr ""
#. i18n: ectx: label, entry (ShutdownScriptTerminatesINDI), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2226
#, kde-format
msgid "Whether shutdown script, if exists, terminates INDI server in the process."
msgstr ""
#. i18n: ectx: label, entry (PreemptiveShutdown), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2230
#, kde-format
msgid "Perform pre-emptive shutdown if no jobs are due for a number of hours."
msgstr ""
#. i18n: ectx: label, entry (ResetMountModelOnAlignFail), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2234
#, kde-format
msgid "Reset mount model in case of alignment failure."
msgstr ""
#. i18n: ectx: label, entry (ResetMountModelBeforeJob), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2238
#, kde-format
msgid "Reset mount model before starting each job."
msgstr ""
#. i18n: ectx: label, entry (ResetGuideCalibration), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2242
#, kde-format
msgid "Always Reset guiding calibration before starting each job."
msgstr ""
#. i18n: ectx: label, entry (RealignAfterCalibrationFailure), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2246
#, kde-format
msgid "If guiding calibration fails, run alignment process again before proceeding to recalibration."
msgstr ""
#. i18n: ectx: label, entry (PreemptiveShutdownTime), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2250
#, kde-format
msgid "Maximum number of hours before the next job is due to trigger a pre-emptive shutdown."
msgstr ""
#. i18n: ectx: label, entry (RememberJobProgress), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2254
#, kde-format
msgid "When processing a scheduled job, resume the sequence starting from the last image present in storage."
msgstr ""
#. i18n: ectx: label, entry (LeadTime), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2258
#, kde-format
msgid "Minimum time between jobs in minutes."
msgstr ""
#. i18n: ectx: label, entry (PreDawnTime), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2262
#, kde-format
msgid "Do not permit jobs to be scheduled or executed past this many minutes before dawn."
msgstr ""
#. i18n: ectx: label, entry (SettingAltitudeCutoff), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2266
#, kde-format
msgid "Do not permit jobs to be scheduled less than this many degrees before the altitude restriction. Actual execution proceeds until the altitude limit."
msgstr ""
#. i18n: ectx: label, entry (TelescopeFocalLength), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2270
#, kde-format
msgid "Telescope focal length in millimeters."
msgstr ""
#. i18n: ectx: label, entry (CameraPixelWidth), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2274
#, kde-format
msgid "Camera pixel size width in micrometers."
msgstr ""
#. i18n: ectx: label, entry (CameraPixelHeight), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2278
#, kde-format
msgid "Camera pixel size height in micrometers."
msgstr ""
#. i18n: ectx: label, entry (CameraWidth), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2282
#, kde-format
msgid "Camera Width in pixels."
msgstr ""
#. i18n: ectx: label, entry (CameraHeight), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2286
#, kde-format
msgid "Camera Height in pixels."
msgstr ""
#. i18n: ectx: label, entry (CameraRotation), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2290
#, kde-format
msgid "Position angle of the camera with respect to north."
msgstr ""
#. i18n: ectx: label, entry (LastServer), group (INDI Lite)
#. +> trunk5
#: kstars.kcfg:2296
#, kde-format
msgid "The address of last used server"
msgstr ""
#. i18n: ectx: label, entry (LastServerPort), group (INDI Lite)
#. +> trunk5
#: kstars.kcfg:2299
#, kde-format
msgid "The port of last used server"
msgstr ""
#. i18n: ectx: label, entry (LastWebManagerPort), group (INDI Lite)
#. +> trunk5
#: kstars.kcfg:2303
#, kde-format
msgid "The port of last used Web Manager"
msgstr ""
#. i18n: ectx: label, entry (HIPSMemoryCache), group (HIPS)
#. +> trunk5
#: kstars.kcfg:2309
#, kde-format
msgid "RAM cache size in MB used to store cached HIPS images."
msgstr ""
#. i18n: ectx: label, entry (HIPSNetCache), group (HIPS)
#. +> trunk5
#: kstars.kcfg:2313
#, kde-format
msgid "Hard disk cache size in MB used to store cached HIPS images."
msgstr ""
#. i18n: ectx: label, entry (HIPSSource), group (HIPS)
#. +> trunk5
#: kstars.kcfg:2317
#, kde-format
msgid "HIPS source catalog title."
msgstr ""
#. i18n: ectx: label, entry (HIPSBiLinearInterpolation), group (HIPS)
#. +> trunk5
#: kstars.kcfg:2321
#, kde-format
msgid "Use Bilinear interpolation when rendering HiPS images?"
msgstr ""
#. i18n: ectx: label, entry (HIPSShowGrid), group (HIPS)
#. +> trunk5
#: kstars.kcfg:2325
#, kde-format
msgid "Show HiPS grid on the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowHIPS), group (HIPS)
#. +> trunk5
#: kstars.kcfg:2329
#, kde-format
msgid "Draw HiPS sources in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowHIPS), group (HIPS)
#. +> trunk5
#: kstars.kcfg:2330
#, kde-format
msgid "Toggle whether the HIPS sources are drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (warningActionsActive), group (Observatory)
#. +> trunk5
#: kstars.kcfg:2336
#, kde-format
msgid "Will be reacted upon warnings?"
msgstr ""
#. i18n: ectx: label, entry (alertActionsActive), group (Observatory)
#. +> trunk5
#: kstars.kcfg:2340
#, kde-format
msgid "Will be reacted upon alerts?"
msgstr ""
#. i18n: ectx: label, entry (weatherWarningCloseDome), group (Observatory)
#. +> trunk5
#: kstars.kcfg:2344
#, kde-format
msgid "Shall the dome being closed when a weather warning occurs?"
msgstr ""
#. i18n: ectx: label, entry (weatherWarningCloseShutter), group (Observatory)
#. +> trunk5
#: kstars.kcfg:2348
#, kde-format
msgid "Shall the shutter being closed when a weather warning occurs?"
msgstr ""
#. i18n: ectx: label, entry (weatherWarningStopScheduler), group (Observatory)
#. i18n: ectx: label, entry (weatherAlertCloseShutter), group (Observatory)
#. i18n: ectx: label, entry (weatherAlertStopScheduler), group (Observatory)
#. addSmoothCurveAction = new QAction(QIcon::fromTheme("labplot-xy-smooth-curve"), i18n("xy-curve from a smooth"), this);
#. addFourierFilterCurveAction = new QAction(QIcon::fromTheme("labplot-xy-fourier_filter-curve"), i18n("xy-curve from a Fourier filter"), this);
#. addFourierTransformCurveAction = new QAction(QIcon::fromTheme("labplot-xy-fourier_transform-curve"), i18n("xy-curve from a Fourier transform"), this);
#. addConvolutionCurveAction = new QAction(QIcon::fromTheme("labplot-xy-convolution-curve"), i18n("xy-curve from a (de-)convolution"), this);
#. addCorrelationCurveAction = new QAction(QIcon::fromTheme("labplot-xy-correlation-curve"), i18n("xy-curve from a auto-/cross-correlation"), this);
"For 'C Format', a period is used for the decimal point character and comma is used for the thousands group separator. Valid number representations are:"
"<ul>"
"<li>1234.56</li>"
"<li>1,234.56</li>"
"<li>etc.</li>"
"</ul>"
"When using 'System locale', the system settings will be used. E.g., for the German local the valid number representations are:"
msgid "This option determines how the imported strings have to be converted to calendar date, i.e. year, month, and day numbers in the Gregorian calendar and to time."
msgid "The column \"%1\" is not available. If a new column at this path is created, it is linked to this curve. If you wanna hold this column, don't change anything in this combobox."
"You are running an unsupported version of Windows: %1.\n"
"This is not recommended. Do not report any bugs.\n"
"Please update to a supported version of Windows: Windows 7, 8, 8.1 or 10."
msgstr ""
#. +> trunk5 stable5
#: krita/main.cc:476 krita/main.cc:481
#, kde-format
msgid "Krita Tablet Support"
msgstr ""
#. +> trunk5 stable5
#: krita/main.cc:477
#, kde-format
msgid "Cannot load WinTab driver and no Windows Ink pen devices are found. If you have a drawing tablet, please make sure the tablet driver is properly installed."
msgstr ""
#. +> trunk5 stable5
#: krita/main.cc:482
#, kde-format
msgid "Cannot load WinTab driver. If you have a drawing tablet, please make sure the tablet driver is properly installed."
msgid "Adds pixels using the color of surrounding pixels. Produces smoother tonal gradations than Bilinear."
msgstr ""
#. +> trunk5 stable5
#: libs/image/kis_filter_strategy.h:97
#, kde-format
msgid "Nearest Neighbor"
msgstr ""
#. +> trunk5 stable5
#: libs/image/kis_filter_strategy.h:105
#, kde-format
msgid "Replicate pixels in the image. Preserves all the original detail, but can produce jagged effects."
msgstr ""
#. +> trunk5 stable5
#: libs/image/kis_filter_strategy.h:119
-#: libs/ui/canvas/kis_canvas_controller.cpp:308
+#: libs/ui/canvas/kis_canvas_controller.cpp:296
#, kde-format
msgid "Bilinear"
msgstr ""
#. +> trunk5 stable5
#: libs/image/kis_filter_strategy.h:125
#, kde-format
msgid "Adds pixels averaging the color values of surrounding pixels. Produces medium quality results when the image is scaled from half to two times the original size."
msgstr ""
#. +> trunk5 stable5
#: libs/image/kis_filter_strategy.h:135
#, kde-format
msgid "Bell"
msgstr ""
#. +> trunk5 stable5
#: libs/image/kis_filter_strategy.h:146
#, kde-format
msgid "BSpline"
msgstr ""
#. +> trunk5 stable5
#: libs/image/kis_filter_strategy.h:157
#, kde-format
msgid "Lanczos3"
msgstr ""
#. +> trunk5 stable5
#: libs/image/kis_filter_strategy.h:163
#, kde-format
msgid "Offers similar results than Bicubic, but maybe a little bit sharper. Can produce light and dark halos along strong edges."
msgid "This image is larger than <b>%1 x %2</b>. Images this size cannot be saved to this format."
msgstr ""
#. +> trunk5 stable5
#: libs/impex/ColorModelCheck.h:44
#, kde-format
msgctxt "image conversion warning"
msgid "The color model <b>%1</b> or channel depth <b>%2</b> cannot be saved to this format. Your image will be converted."
msgstr ""
#. +> trunk5 stable5
#: libs/impex/ColorModelHomogenousCheck.h:125
#, kde-format
msgctxt "image conversion warning"
msgid "Your image contains layers with a color model that is different from the image. The layers will be converted."
msgstr ""
#. +> trunk5 stable5
#: libs/impex/ColorModelPerLayerCheck.h:129
#, kde-format
msgctxt "image conversion warning"
msgid "Your image contains layers with the color model <b>%1</b> and channel depth <b>%2</b> which cannot be saved to this format. The layers will be converted."
msgstr ""
#. +> trunk5 stable5
#: libs/impex/CompositionsCheck.h:36
#, kde-format
msgctxt "image conversion warning"
msgid "The image contains <b>compositions</b>. The compositions will not be saved."
msgstr ""
#. +> trunk5 stable5
#: libs/impex/ExifCheck.h:40
#, kde-format
msgctxt "image conversion warning"
msgid "The image contains <b>Exif</b> metadata. The metadata will not be saved."
msgid "This merge strategy attempts to find the best solution for merging, for instance by merging the list of authors together, or keeping identical photographic information."
"<p><i>Thanks! You were all <b>awesome</b>!</i></p>"
"</body></html>"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/dialogs/kis_about_application.cpp:113
#, kde-format
msgid "Backers"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/dialogs/kis_about_application.cpp:119
#, kde-format
msgid ""
"<html><head/><body>"
"<h1 align=\"center\">Thanks To</h1>"
"<p>"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/dialogs/kis_about_application.cpp:138
#, kde-format
msgid ""
".</p>"
"<p><i>For supporting Krita development with advice, icons, brush sets and more.</i></p>"
"</body></html>"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/dialogs/kis_about_application.cpp:141
#, kde-format
msgid "Also Thanks To"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/dialogs/kis_about_application.cpp:145
#, kde-format
msgid ""
"<html><head/><body>"
"<h1 align=\"center\"><b>Your Rights</b></h1>"
"<p>Krita is released under the GNU General Public License (version 3 or any later version).</p>"
"<p>This license grants people a number of freedoms:</p>"
"<ul>"
"<li>You are free to use Krita, for any purpose</li>"
"<li>You are free to distribute Krita</li>"
"<li>You can study how Krita works and change it</li>"
"<li>You can distribute changed versions of Krita</li>"
"</ul>"
"<p>The Krita Foundation and its projects on krita.org are <b>committed</b> to preserving Krita as free software.</p>"
"<h1 align=\"center\">Your artwork</h1>"
"<p>What you create with Krita is your sole property. All your artwork is free for you to use as you like.</p>"
"<p>That means that Krita can be used commercially, for any purpose. There are no restrictions whatsoever.</p>"
"<p>Krita’s GNU GPL license guarantees you this freedom. Nobody is ever permitted to take it away, in contrast to trial or educational versions of commercial software that will forbid your work in commercial situations.</p>"
"<br/>"
"<hr/>"
"<pre>"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/dialogs/kis_about_application.cpp:173
#, kde-format
msgid "License"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/dialogs/kis_about_application.cpp:181
#, kde-format
msgid ""
"<html><head/><body>"
"<h1 align=\"center\"><b>Third-party Libraries used by Krita</b></h1>"
"<p>Krita is built on the following free software libraries:</p>"
msgid "The image data you want to paste does not have an ICM profile associated with it. If you do not select a profile, Krita will assume that the image data is encoded in the import profile defined in the Settings dialog."
msgid "Hue hopefully maintained (but not required), lightness and saturation sacrificed to maintain the perceived color. White point changed to result in neutral grays. Intended for images."
msgid "Hue and saturation maintained with lightness sacrificed to maintain saturation. White point changed to result in neutral grays. Intended for business graphics (make it colorful charts, graphs, overheads, ...)"
msgid "Within the destination device gamut; hue, lightness and saturation are maintained. Outside the gamut; hue and lightness are maintained, saturation is sacrificed. White point for source and destination; unchanged. Intended for spot colors (Pantone, TruMatch, logo colors, ...)"
"<p><a href=\"https://en.wikipedia.org/wiki/Color_space\"><span style=\" font-weight:600; text-decoration: underline; color:#006e28;\">Color Spaces</span></a> determine how colors are encoded in your files. Different color spaces have different properties and are used for different purposes.</p>"
"<p>Try to disable vsync for Krita. This makes painting more responsive. Uncheck only when experiencing crashes with some GPU/driver combinations.</p>"
"<p><span style=\" font-weight:600;\">Note:</span> This changes only the colorspace of the rendered image. To convert the colorspace of the layers, use Convert Image Colorspace.</p>"
"<p>Set how much you wish to correct the adaptation state. This will affect how <span style=\" font-style:italic;\">Absolute Colorimetric</span> changes the whites of your image. In Layman's terms: how much do you wish to have the color management correct the paper-color to screen white while using <span style=\" font-style:italic;\">Absolute Colorimetric</span>?</p>"
"<p>Black Point compensation matches the darkest color of the source device to the darkest color of the destination device. Relative Colorimetric without Black Point Compensation will show the difference between the darkest values. With blackpoint compensation, black is black.</p>"
"<p>When rendering animation frames (into files or during animation cache regeneration), Krita will make the specified number of copies of your image and will work on them in parallel. Each copy will demand more RAM for its storage (about 20% of the size of you image), so raise this limit only if you have enough RAM installed.</p>"
"<p><br/>"
"</p>"
"<p><span style=\" font-weight:600;\">Recommended value:</span> set Clones Limit to the number of <span style=\" text-decoration: underline;\">physical</span> (non-hyperthreaded) cores your CPU has</p>"
"<p>Krita will try to limit the number of screen updates per second to the given number. A lower number will decrease visual responsiveness but increase stylus precision on some systems like macOS."
"<p>When performance logging is enabled Krita saves timing information into the '<working_dir>/log' folder. If you experience performance problems and want to help us, enable this option and add the contents of the directory to a bug report.</p>"
"<p>Animation frame cache will be stored in RAM completely without any limitations</p>"
"<p><span style=\" font-weight:600;\">WARNING:</span> please make sure your computer has enough RAM <span style=\" text-decoration: underline;\">above</span> the amount you requested in General tab. Otherwise you might face system freezes.</p>"
"<p>* for 1 second of FullHD@25fps video you need extra 200 MiB of memory</p>"
"<p>* for 1 second of 4K UltraHD@25fps video you need extra 800 MiB of memory</p>"
"<p>Animation frames are stored on hard disk in the same folder as swap file. The cache is stored in a compressed way. Little amount of extra RAM is needed.</p>"
"<p>Since data transfer speed of the hard drive is low, you might want to limit cached frame size to be able to play your video at 25 fps. The limit of 2500 px is usually a good choice.</p>"
"<p>Render scaled down version of the frame if the image is bigger than the provided limit. Make sure you enable this option when using on-disk storage backend.</p>"
"<p>Choose the optional emblem icon that indicates extra information, such as the preset being a special effects brush, or just using tilt, or angled in some way.</p>"
"<p>Some tablet devices don't pass barrel-button clicks via tablet API. If you have such a device, you can try activate this workaround. Krita will try to read right- and middle-button clicks from the mouse events stream. It may or may not work on your device (depends on the tablet driver implementation).</p>"
"<p><br/>"
"</p>"
"<p>After changing this option Krita should be restarted.</p>"
msgid "The <i>Alternate Invocation</i> action performs an alternate action with the current tool. For example, using the brush tool it picks a color from the canvas."
"<p>The driver for your drawing tablet and Windows do not agree on the size of the screen your tablet is connected to. Please select the right option.</p>"
msgid "A spot color is a color that the printer is able to print without mixing the paints it has available to it. The opposite is called a process color."
msgid "The Intel graphics driver in use is known to have issues with OpenGL."
msgstr ""
#. +> trunk5 stable5
#: libs/ui/opengl/kis_opengl.cpp:491
#, kde-format
msgid "Intel graphics drivers tend to have issues with OpenGL so ANGLE will be used by default. You may manually switch to OpenGL but it is not guaranteed to work properly."
msgstr ""
#. +> trunk5 stable5
#: libs/ui/opengl/kis_opengl.cpp:872
#, kde-format
msgid "Preferred renderer doesn't support requested surface format. Another renderer has been selected."
msgstr ""
#. +> trunk5 stable5
#: libs/ui/opengl/kis_opengl.cpp:874
#, kde-format
msgid "Preferred output format is not supported by available renderers"
#. i18nc("Who made the profile?","Manufacturer: ") + currentColorSpace()->profile()->manufacturer() + "</p>"); //This would work if people actually wrote the manufacturer into the manufacturer fiedl...
"<b><a href=\"https://en.wikipedia.org/wiki/RGB_color_space\">RGB (Red, Green, Blue)</a></b>, is the color model used by screens and other light-based media.<br/>"
"RGB is an additive color model: adding colors together makes them brighter. This color model is the most extensive of all color models, and is recommended as a model for painting,that you can later convert to other spaces. RGB is also the recommended colorspace for HDR editing."
"<b><a href=\"https://en.wikipedia.org/wiki/CMYK_color_model\">CMYK (Cyan, Magenta, Yellow, Key)</a></b>, is the model used by printers and other ink-based media.<br/>"
"CMYK is a subtractive model, meaning that adding colors together will turn them darker. Because of CMYK profiles being very specific per printer, it is recommended to work in RGB space, and then later convert to a CMYK profile, preferably one delivered by your printer. <br/>"
"CMYK is <b>not</b> recommended for painting.Unfortunately, Krita cannot retrieve colorants or the TRC for this space."
msgid "<b><a href=\"https://en.wikipedia.org/wiki/CIE_1931_color_space\">CIE XYZ</a></b>is the space determined by the CIE as the space that encompasses all other colors, and used to convert colors between profiles. XYZ is an additive color model, meaning that adding colors together makes them brighter. XYZ is <b>not</b> recommended for painting, but can be useful to encode in. The Tone Response Curve is assumed to be linear."
"<b><a href=\"https://en.wikipedia.org/wiki/Grayscale\">Grayscale</a></b> only allows for gray values and transparent values. Grayscale images use half the memory and disk space compared to an RGB image of the same bit-depth.<br/>"
"Grayscale is useful for inking and grayscale images. In Krita, you can mix Grayscale and RGB layers in the same image."
"<b><a href=\"https://en.wikipedia.org/wiki/Lab_color_space\">L*a*b</a></b>. <b>L<b> stands for Lightness, the <b>a</b> and <b>b</b> components represent color channels.<br/>"
"L*a*b is a special model for color correction. It is based on human perception, meaning that it tries to encode the difference in lightness, red-green balance and yellow-blue balance. This makes it useful for color correction, but the vast majority of color maths in the blending modes do <b>not</b> work as expected here.<br/>"
"Similarly, Krita does not support HDR in LAB, meaning that HDR images converted to LAB lose color information. This colorspace is <b>not</b> recommended for painting, nor for export, but best as a space to do post-processing in. The TRC is assumed to be the L* TRC."
msgid "<b><a href=\"https://en.wikipedia.org/wiki/YCbCr\">YCbCr (Luma, Blue Chroma, Red Chroma)</a></b>, is a model designed for video encoding. It is based on human perception, meaning that it tries to encode the difference in lightness, red-green balance and yellow-blue balance. Chroma in this case is then a word indicating a special type of saturation, in these cases the saturation of Red and Blue, of which the desaturated equivalents are Green and Yellow respectively. It is available to open up certain images correctly, but Krita does not currently ship a profile for this due to lack of open source ICC profiles for YCrCb."
msgid "<b>8 bit integer</b>: The default number of colors per channel. Each channel will have 256 values available, leading to a total amount of colors of 256 to the power of the number of channels. Recommended to use for images intended for the web, or otherwise simple images."
msgid "<b>16 bit integer</b>: Also known as 'deep color'. 16 bit is ideal for editing images with a linear TRC, large color space, or just when you need more precise color blending. This does take twice as much space on the RAM and hard-drive than any given 8 bit image of the same properties, and for some devices it takes much more processing power. We recommend watching the RAM usage of the file carefully, or otherwise use 8 bit if your computer slows down. Take care to disable conversion optimization when converting from 16 bit/channel to 8 bit/channel."
msgctxt "When the selected Bitdepth is 16 bit float"
msgid "<b>16 bit floating point</b>: Also known as 'Half Floating Point', and the standard in VFX industry images. 16 bit float is ideal for editing images with a linear Tone Response Curve, large color space, or just when you need more precise color blending. It being floating point is an absolute requirement for Scene Referred (HDR) images. This does take twice as much space on the RAM and hard-drive than any given 8 bit image of the same properties, and for some devices it takes much more processing power. We recommend watching the RAM usage of the file carefully, or otherwise use 8 bit if your computer slows down."
msgctxt "When the selected Bitdepth is 32bit float"
msgid "<b>32 bit float point</b>: Also known as 'Full Floating Point'. 32 bit float is ideal for editing images with a linear TRC, large color space, or just when you need more precise color blending. It being floating point is an absolute requirement for Scene Referred (HDR) images. This does take four times as much space on the RAM and hard-drive than any given 8 bit image of the same properties, and for some devices it takes much more processing power. We recommend watching the RAM usage of the file carefully, or otherwise use 8 bit if your computer slows down."
msgctxt "When the selected Bitdepth is 64bit float, but this isn't actually available in Krita at the moment."
msgid "<b>64 bit float point</b>: 64 bit float is as precise as it gets in current technology, and this depth is used most of the time for images that are generated or used as an input for software. It being floating point is an absolute requirement for Scene Referred (HDR) images. This does take eight times as much space on the RAM and hard-drive than any given 8 bit image of the same properties, and for some devices it takes much more processing power. We recommend watching the RAM usage of the file carefully, or otherwise use 8 bit if your computer slows down."
msgctxt "These are Elle Stone's notes on her profiles that we ship."
msgid ""
"<p><b>Extra notes on profiles by Elle Stone:</b></p>"
"<p><i>Krita comes with a number of high quality profiles created by <a href=\"http://ninedegreesbelow.com\">Elle Stone</a>. This is a summary. Please check <a href=\"http://ninedegreesbelow.com/photography/lcms-make-icc-profiles.html\">the full documentation</a> as well.</i></p>"
msgid "<p>Quoting Wikipedia, 'Academy Color Encoding System (ACES) is a color image encoding system proposed by the Academy of Motion Picture Arts and Sciences that will allow for a fully encompassing color accurate workflow, with 'seamless interchange of high quality motion picture images regardless of source'.</p>"
msgid "<p>The ACEScg color space is smaller than the ACES color space, but large enough to contain the 'Rec-2020 gamut and the DCI-P3 gamut', unlike the ACES color space it has no negative values and contains only few colors that fall just barely outside the area of real colors humans can see</p>"
"<p>To avoid possible copyright infringement issues, I used 'ClayRGB' (following ArgyllCMS) as the base name for these profiles. As used below, 'Compatible with Adobe RGB 1998' is terminology suggested in the preamble to the AdobeRGB 1998 color space specifications.</p>"
"<p>The Adobe RGB 1998 color gamut covers a higher percentage of real-world cyans, greens, and yellow-greens than sRGB, but still doesn't include all printable cyans, greens, yellow-greens, especially when printing using today's high-end, wider gamut, ink jet printers. BetaRGB (not included in the profile pack) and Rec.2020 are better matches for the color gamuts of today's wide gamut printers.</p>"
"<p>The Adobe RGB 1998 color gamut is a reasonable approximation to some of today's high-end wide gamut monitors.</p>"
"<p>This profile's color gamut is roughly the same size and shape as the ACES color space gamut, and like the ACES color space, AllColorsRGB holds all possible real colors. But AllColorsRGB actually has a slightly larger color gamut (to capture some fringe colors that barely qualify as real when viewed by the standard observer) and uses the D50 white point.</p>"
"<p>Just like the ACES color space, AllColorsRGB holds a high percentage of imaginary colors. See the Completely <a href=\"http://ninedegreesbelow.com/photography/xyz-rgb.html\">Painless Programmer's Guide to XYZ, RGB, ICC, xyY, and TRCs</a> for more information about imaginary colors.</p>"
"<p>There is no particular reason why anyone would want to use this profile for editing, unless one needs to make sure your color space really does hold all possible real colors.</p>"
"<p>This profile is included mostly for its historical significance. It's the color space that was used in the original color matching experiments that led to the creation of the XYZ reference color space.</p>"
"<p>The ASTM E white point is probably the right E white point to use when making the CIERGB color space profile. It's not clear to me what the correct CIERGB primaries really are. Lindbloom gives one set. The LCMS version 1 tutorial gives a different set. Experts in the field contend that the real primaries should be calculated from the spectral wavelengths, so I did.</p>"
msgid "<p>The IdentityRGB working space is included in the profile pack because it's a mathematically obvious way to include all possible visible colors, though it has a higher percentage of imaginary colors than the ACES and AllColorsRGB color spaces. I cannot think of any reason why you'd ever want to actually edit images in the IdentityRGB working space.</p>"
"<p>To avoid possible copyright infringement issues, I used 'LargeRGB' (following RawTherapee) as the base name for these profiles."
"<p>Kodak designed the RIMM/ROMM (ProPhotoRGB) color gamut to include all printable and most real world colors. It includes some imaginary colors and excludes some of the real world blues and violet blues that can be captured by digital cameras. It also excludes some very saturated 'camera-captured' yellows as interpreted by some (and probably many) camera matrix input profiles.</p>"
"<p>The ProPhotoRGB primaries are hard-coded into Adobe products such as Lightroom and the Dng-DCP camera 'profiles'. However, other than being large enough to hold a lot of colors, ProPhotoRGB has no particular merit as an RGB working space. Personally I recommend the Rec.2020 or ACEScg profiles over ProPhotoRGB. But if you have an already well-established workflow using ProPhotoRGB, you might find a shift to another RGB working space a little odd, at least at first, and so you have to weight the pros and cons of changing your workflow.</p>"
"<p>To avoid possible copyright infringement issues, I used 'LargeRGB' (following RawTherapee) as the base name for these profiles."
"<p>Kodak designed the RIMM/ROMM (ProPhotoRGB) color gamut to include all printable and most real world colors. It includes some imaginary colors and excludes some of the real world blues and violet blues that can be captured by digital cameras. It also excludes some very saturated 'camera-captured' yellows as interpreted by some (and probably many) camera matrix input profiles.</p>"
"<p>The ProPhotoRGB primaries are hard-coded into Adobe products such as Lightroom and the Dng-DCP camera 'profiles'. However, other than being large enough to hold a lot of colors, ProPhotoRGB has no particular merit as an RGB working space. Personally I recommend the Rec.2020 or ACEScg profiles overProPhotoRGB. But if you have an already well-established workflow using ProPhotoRGB, youmight find a shift to another RGB working space a little odd, at least at first, and so youhave to weight the pros and cons of changing your workflow.</p>"
msgid "<p>Rec.2020 is the up-and-coming replacement for the thoroughly outdated sRGB color space. As of June 2015, very few (if any) display devices (and certainly no affordable display devices) can display all of Rec.2020. However, display technology is closing in on Rec.2020, movies are already being made for Rec.2020, and various cameras offer support for Rec.2020. And in the digital darkroom Rec.2020 is much more suitable as a general RGB working space than the exceedingly small sRGB color space.</p>"
"<p>Hewlett-Packard and Microsoft designed sRGB to match the color gamut of consumer-grade CRTs from the 1990s. sRGB is the standard color space for the world wide web and is still the best choice for exporting images to the internet.</p>"
"<p>The sRGB color gamut was a good match to calibrated decent quality CRTs. But sRGB is not a good match to many consumer-grade LCD monitors, which often cannot display the more saturated sRGB blues and magentas (the good news: as technology progresses, wider gamuts are trickling down to consumer grade monitors).</p>"
"<p>Printer color gamuts can easily exceed the sRGB color gamut in cyans, greens, and yellow-greens. Colors from interpolated camera raw files also often exceed the sRGB color gamut.</p>"
"<p>As a very relevant aside, using perceptual intent when converting to sRGB does not magically makes otherwise out of gamut colors fit inside the sRGB color gamut! The standard sRGB color space (along with all the other the RGB profiles provided in my profile pack) is a matrix profile, and matrix profiles don't have perceptual intent tables.</p>"
"<p>To avoid possible copyright infringement issues, I used 'WideRGB' as the base name for these profiles.</p>"
"<p>WideGamutRGB was designed by Adobe to be a wide gamut color space that uses spectral colors as its primaries. Pascale's primary values produce a profile that matches old V2 Widegamut profiles from Adobe and Canon. It is an interesting color space, but shortly after its introduction, Adobe switched their emphasis to the ProPhotoRGB color space.</p>"
msgid "<p>These profiles are for use with RGB images that have been converted to monotone gray (black and white). The main reason to convert from RGB to Gray is to save the file space needed to encode the image. Google places a premium on fast-loading web pages, and images are one of the slower-loading elements of a web page. So converting black and white images to Grayscale images does save some kilobytes. For grayscale images uploaded to the internet, convert the image to the V2 Gray profile with the sRGB TRC.</p>"
msgid "<p>The profiles that end in '-g10.icc' are linear gamma (gamma=1.0, 'linear light', etc) profiles and should only be used when editing at high bit depths (16-bit floating point, 16-bit integer, 32-bit floating point, 32-bit integer). Many editing operations produce better results in linear gamma color spaces.</p>"
msgid "<p>The profiles that end in '-labl.icc' have perceptually uniform TRCs. A few editing operations really should be done on perceptually uniform RGB. Make sure you use the V4 versions for editing high bit depth images.</p>"
msgid "<p>The profiles that end in '-srgbtrc.icc', '-g22.icc', and '-rec709.icc' have approximately but not exactly perceptually uniform TRCs. ProPhotoRGB's gamma=1.8 TRC is not quite as close to being perceptually uniform.</p>"
msgid "<p>When editing 8-bit images, you should use a profile with a small color gamut and an approximately or exactly perceptually uniform TRC. Of the profiles supplied in my profile pack, only the sRGB and AdobeRGB1998 (ClayRGB) color spaces are small enough for 8-bit editing. Even with the AdobeRGB1998 color space you need to be careful to not cause posterization. And of course you cannot use the linear gamma versions of these profiles for 8-bit editing.</p>"
msgid "<p>Use V4 profiles for editing images using high bit depth image editors that use LCMS as the Color Management Module. This includes Krita, digiKam/showFoto, and GIMP 2.9.</p>"
"Linear gamma RGB color spaces are not supposed to be used in 8-bit integer modes. It is suggested to use 16-bit integer or any floating point colorspace for linear profiles.\n"
"\n"
"Press \"Ok\" to create a 8-bit integer linear RGB color space or \"Cancel\" to return to the settings dialog."
msgstr ""
#. +> trunk5 stable5
#: libs/ui/widgets/kis_custom_image_widget.cc:513
#, kde-format
msgctxt "arg1: width. arg2: height. arg3: colorspace name. arg4: size of a channel in bits. arg5: image size"
msgid "This document will be %1 pixels by %2 pixels in %3, which means the pixel size is %4 bit. A single paint layer will thus take up %5 of RAM."
"<html><b>KDE</b> is a world-wide network of software engineers, artists, writers, translators and facilitators who are committed to <a href=\"%1\">Free Software</a> development. This community has created hundreds of Free Software applications as part of the KDE frameworks, workspaces and applications.<br />"
"<br />"
"KDE is a cooperative enterprise in which no single entity controls the efforts or products of KDE to the exclusion of others. Everyone is welcome to join and contribute to KDE, including you.<br />"
"<br />"
"Visit <a href=\"%2\">%2</a> for more information about the KDE community and the software we produce.</html>"
"<html>Software can always be improved, and the KDE team is ready to do so. However, you - the user - must tell us when something does not work as expected or could be done better.<br />"
"<br />"
"KDE has a bug tracking system. Visit <a href=\"%1\">%1</a> or use the \"Report Bug...\" dialog from the \"Help\" menu to report bugs.<br />"
"<br />"
"If you have a suggestion for improvement then you are welcome to use the bug tracking system to register your wish. Make sure you use the severity called \"Wishlist\".</html>"
"<html>You do not have to be a software developer to be a member of the KDE team. You can join the national teams that translate program interfaces. You can provide graphics, themes, sounds, and improved documentation. You decide!<br />"
"<br />"
"Visit <a href=\"%1\">%1</a> for information on some projects in which you can participate.<br />"
"<br />"
"If you need more information or documentation, then a visit to <a href=\"%2\">%2</a> will provide you with what you need.</html>"
"<html>KDE software is and will always be available free of charge, however creating it is not free.<br />"
"<br />"
"To support development the KDE community has formed the KDE e.V., a non-profit organization legally founded in Germany. KDE e.V. represents the KDE community in legal and financial matters. See <a href=\"%1\">%1</a> for information on KDE e.V.<br />"
"<br />"
"KDE benefits from many kinds of contributions, including financial. We use the funds to reimburse members and others for expenses they incur when contributing. Further funds are used for legal support and organizing conferences and meetings. <br />"
" <br />"
"We would like to encourage you to support our efforts with a financial donation, using one of the ways described at <a href=\"%2\">%2</a>.<br />"
"<br />"
"Thank you very much in advance for your support.</html>"
"<p>Please read <b><a href=\"https://docs.krita.org/en/untranslatable_pages/reporting_bugs.html\">this guide</a></b> for reporting bugs first!</p>"
"<p>To submit a bug report, click on the button below. This will open a web browser window on <a href=\"http://bugs.kde.org\">http://bugs.kde.org</a> where you will find a form to fill in. The information displayed above will be transferred to that server.</p>"
msgid "Here you can see a list of key bindings, i.e. associations between actions (e.g. 'Copy') shown in the left column and keys or combination of keys (e.g. Ctrl+V) shown in the right column."
msgid "Values goes from black to white, or black to the most saturated color. Saturation, in turn, goes from the most saturated color to white, gray or black."
"<p>This sets the gamma value that the linearised HSY Luminosity is crunched with. 1 makes the selector fully linear, 2.2 is a practical default value.</p>"
msgid "The location of FFmpeg is unknown. Please install FFmpeg first: Krita cannot render animations without FFmpeg. (<a href=\"https://www.ffmpeg.org\">www.ffmpeg.org</a>)"
"<p><span style=\" font-weight:600;\">Warning:</span> animated gif images cannot have a framerate higher than 50. The framerate will be reduced to 50 frames per second.</p>"
msgid "Krita tries to automatically check or uncheck this based on the information it can get from the profile you are converting from and the profile you are converting to."
msgid "The icon associated with this action. It is shown alongside text in the menu bar and in toolbars as required. A string to use KDE's image loading system, or a custom QPixmap or QIcon, or None."
msgid "<p>Failed to check version of dependency <application>%1</application>: Module do not have PEP396 <code>__version__</code> attribute. It is not disabled, but behaviour is unpredictable...</p>"
"<p>Select the location of the G'Mic-Qt plugin. You can download the plugin from the <a href=\"http://gmic.eu/\"><span style=\" text-decoration: underline; color:#2980b9;\">G'Mic website</span></a>. Make sure you download the special version for Krita, not the standalone or the GIMP version.</p>"
msgid "The formula decides how the kernel is created, so different formulas choose different values in the kernel, and thus give subtly different results."
"<p style=\" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;\"><span style=\" font-family:'MS Shell Dlg 2'; font-size:8pt;\">This is a line of text before the inserted text. This is a line of inserted text. This is a line after the inserted text.</span></p>"
"<p style=\" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;\"><span style=\" font-family:'MS Shell Dlg 2'; font-size:8pt;\">This is a line of text before the deleted text. This is a line of deleted text. This is a line after the deleted text.</span></p>"
"<p style=\" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;\"><span style=\" font-family:'MS Shell Dlg 2'; font-size:8pt;\">This is a line of text before the format-change text. This is a line of text whose format has been changed. This is a line of text after the format-change text.</span></p>"
"<p style=\" margin-top:12px; margin-bottom:12px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;\">It is possible to assign a named style to text and alter the style properties to change all text with that style.</p>"
"\n"
"<p style=\" margin-top:12px; margin-bottom:12px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;\">Applying a style change will reformat all text that previously got the named style assigned to it. Use the Styles docker to apply styles to text.</p>"
"The image contains pixels with zero alpha channel and non-zero color channels. Krita has modified those pixels to have at least some alpha. The initial values will <i>not</i> be reverted on saving the image back.<br/>"
"<br/>"
"This will hardly make any visual difference just keep it in mind."
msgstr ""
#. +> trunk5 stable5
#: plugins/impex/exr/exr_converter.cc:902
#, kde-format
msgctxt "@title:window"
msgid "EXR image has been modified"
msgstr ""
#. +> trunk5 stable5
#: plugins/impex/exr/exr_converter.cc:1302
#, kde-format
msgctxt "@item:unsupported-node-message"
msgid "%1 (type: \"%2\")"
msgstr ""
#. +> trunk5 stable5
#: plugins/impex/exr/exr_converter.cc:1307
#, kde-format
msgctxt "@info"
msgid ""
"<p>The following layers have a type that is not supported by EXR format:</p>"
"<r>"
"<ul>%1</ul>"
"</p>"
"<p><warning>these layers have <b>not</b> been saved to the final EXR file</warning></p>"
msgid "This option will merge all layers. It is advisable to check this option, otherwise other applications might not be able to read your file correctly."
"<p><span style=\" font-weight:600;\">PNG</span> files have <span style=\" font-style:italic;\">two</span> options to save <span style=\" font-weight:600;\">sRGB</span> information: as a tag or as an explicit profile. For use with in websites, <span style=\" font-style:italic;\">disable</span> this option. For interchange with other applications, <span style=\" font-style:italic;\">enable</span> this option.</p>"
msgid "Indexed PNG images are smaller. If you enabled this option, your image will be analyzed to see whether it is possible to save as an indexed PNG."
"<p>If enabled, all RAW files will be decoded in 16-bit color depth using a linear gamma curve. To prevent dark picture rendering in the editor, it is recommended to use Color Management in this mode.</p>"
"<p>If disabled, all RAW files will be decoded in 8-bit color depth with a BT.709 gamma curve and a 99th-percentile white point. This mode is faster than 16-bit decoding.</p>"
"<p>The default is to assume that all green pixels are the same. If even-row green pixels are more sensitive to ultraviolet light than odd-row this difference causes a mesh pattern in the output; using this option solves this problem with minimal loss of detail.</p>"
"<p>To resume, this option blurs the image a little, but it eliminates false 2x2 mesh patterns with VNG quality method or mazes with AHD quality method.</p>"
"<p>For Fuji Super CCD cameras, show the image tilted 45 degrees. For cameras with non-square pixels, do not stretch the image to its correct aspect ratio. In any case, this option guarantees that each output pixel corresponds to one RAW pixel.</p>"
"<p>Select here the demosaicing method to use when decoding RAW images. A demosaicing algorithm is a digital image process used to interpolate a complete image from the partial raw data received from the color-filtered image sensor, internal to many digital cameras, in form of a matrix of colored pixels. Also known as CFA interpolation or color reconstruction, another common spelling is demosaicing. The following methods are available for demosaicing RAW images:</p>"
"<p>"
"<ul>"
"<li><emphasis strong='true'>Bilinear</emphasis>: use high-speed but low-quality bilinear interpolation (default - for slow computers). In this method, the red value of a non-red pixel is computed as the average of the adjacent red pixels, and similarly for blue and green.</li>"
"<li><emphasis strong='true'>VNG</emphasis>: use Variable Number of Gradients interpolation. This method computes gradients near the pixel of interest and uses the lower gradients (representing smoother and more similar parts of the image) to make an estimate.</li>"
"<li><emphasis strong='true'>PPG</emphasis>: use Patterned-Pixel-Grouping interpolation. Pixel Grouping uses assumptions about natural scenery in making estimates. It has fewer color artifacts on natural images than the Variable Number of Gradients method.</li>"
"<li><emphasis strong='true'>AHD</emphasis>: use Adaptive Homogeneity-Directed interpolation. This method selects the direction of interpolation so as to maximize a homogeneity metric, thus typically minimizing color artifacts.</li>"
"<li><emphasis strong='true'>DCB</emphasis>: DCB interpolation from linuxphoto.org project.</li>"
"<li><emphasis strong='true'>AHD v2</emphasis>: modified AHD interpolation using Variance of Color Differences method.</li>"
"<li><emphasis strong='true'>AFD</emphasis>: Adaptive Filtered Demosaicing interpolation through 5 pass median filter from PerfectRaw project.</li>"
"<li><emphasis strong='true'>VCD</emphasis>: Variance of Color Differences interpolation.</li>"
"<li><emphasis strong='true'>VCD & AHD</emphasis>: Mixed demosaicing between VCD and AHD.</li>"
"<li><emphasis strong='true'>LMMSE</emphasis>: color demosaicing via directional linear minimum mean-square error estimation interpolation from PerfectRaw.</li>"
"<li><emphasis strong='true'>AMaZE</emphasis>: Aliasing Minimization interpolation and Zipper Elimination to apply color aberration removal from RawTherapee project.</li>"
"</ul>"
"</p>"
"<p>Note: some methods can be unavailable if RAW decoder have been built without extension packs.</p>"
"<p>Set here the passes used by the median filter applied after interpolation to Red-Green and Blue-Green channels.</p>"
"<p>This setting is only available for specific Quality options: <emphasis strong='true'>Bilinear</emphasis>, <emphasis strong='true'>VNG</emphasis>, <emphasis strong='true'>PPG</emphasis>, <emphasis strong='true'>AHD</emphasis>, <emphasis strong='true'>DCB</emphasis>, and <emphasis strong='true'>VCD & AHD</emphasis>.</p>"
"<li><emphasis strong='true'>Default D65</emphasis>: Use a standard daylight D65 white balance.</li>"
"<li><emphasis strong='true'>Camera</emphasis>: Use the white balance specified by the camera. If not available, reverts to default neutral white balance.</li>"
"<li><emphasis strong='true'>Automatic</emphasis>: Calculates an automatic white balance averaging the entire image.</li>"
"<li><emphasis strong='true'>Manual</emphasis>: Set a custom temperature and green level values.</li>"
msgid "<p>If enabled, images with overblown channels are processed much more accurately, without 'pink clouds' (and blue highlights under tungsten lamps).</p>"
"<p>Select here the noise reduction method to apply during RAW decoding.</p>"
"<p>"
"<ul>"
"<li><emphasis strong='true'>None</emphasis>: no noise reduction.</li>"
"<li><emphasis strong='true'>Wavelets</emphasis>: wavelets correction to erase noise while preserving real detail. It's applied after interpolation.</li>"
"<li><emphasis strong='true'>FBDD</emphasis>: Fake Before Demosaicing Denoising noise reduction. It's applied before interpolation.</li>"
"<li><emphasis strong='true'>CFA Line Denoise</emphasis>: Banding noise suppression. It's applied after interpolation.</li>"
"<li><emphasis strong='true'>Impulse Denoise</emphasis>: Impulse noise suppression. It's applied after interpolation.</li>"
"<p>If this option is turned on, it will try to shift image channels slightly and evaluate Chromatic Aberration change. Note that if you shot blue-red pattern, the method may fail. In this case, disable this option and tune manually color factors.</p>"
"<p>Select here the output color space used to decode RAW data.</p>"
"<p>"
"<ul>"
"<li><emphasis strong='true'>Raw (no profile)</emphasis>: in this mode, no output color space is used during RAW decoding.</li>"
"<li><emphasis strong='true'>sRGB</emphasis>: this is an RGB color space, created cooperatively by Hewlett-Packard and Microsoft. It is the best choice for images destined for the Web and portrait photography.</li>"
"<li><emphasis strong='true'>Adobe RGB</emphasis>: this color space is an extended RGB color space, developed by Adobe. It is used for photography applications such as advertising and fine art.</li>"
"<li><emphasis strong='true'>Wide Gamut</emphasis>: this color space is an expanded version of the Adobe RGB color space.</li>"
"<li><emphasis strong='true'>Pro-Photo</emphasis>: this color space is an RGB color space, developed by Kodak, that offers an especially large gamut designed for use with photographic outputs in mind.</li>"
"<li><emphasis strong='true'>Custom</emphasis>: use a custom output color space profile.</li>"
msgid "This determines every interval after which the precision should change. For example: if the delta value is set to be 15.00, after every 15 pts change in the size of brush, the precision will change."
msgid "If checked, grid brush fill every particle's background with background color. The background of particle is rectangle of grid width and height and by default it is transparent."
"<p><b>Painting mode</b>: Krita offers a choice between two painting modes: <i>buildup</i> and <i>wash</i>. The first choice builds up color while painting in one stroke, the second choices gives you an even color in one stroke even if you go over the same place again and again.</p>"
msgid "These are keywords that can be used to identify text layers. A layer only needs to contain the keyword to be recognized. Keywords should be comma separated."
msgid "These are keywords that can be used to identify panel layers. A layer only needs to contain the keyword to be recognized. Keywords should be comma separated."
msgid "By default this will be filled with a generated universal unique identifier. The ID by itself is merely so that comic book library management programs can figure out if this particular comic is already in their database and whether it has been rated. Of course, the UUID can be changed into something else by manually changing the JSON, but this is advanced usage."
msgid "The genre of the work. Prefilled values are from the ACBF, but you can fill in your own. Separate genres with commas. Try to limit the amount to about two or three."
msgid "The following is a table of the authors that contributed to this comic. You can set their nickname, proper names (first, middle, last), role (penciller, inker, etc), email and homepage."
msgid "If there is an entry in a comics data base, that should be added here. It is unlikely to be a factor for comics from scratch, but useful when doing a conversion."
msgid "Whether the comic is an adaption of an existing source, and if so, how to find information about that source. So for example, for an adapted webcomic, the official website url should go here."
msgid "Krita doesn't have write access to this folder, so new files cannot be made. Please configure the folder access or move the project to a folder that can be written to."
msgid "The location for extra autocompletion keys in the metadata editor. Point this at a folder containing key_characters/key_format/key_genre/key_rating/key_author_roles/key_other with inside txt files (csv for rating) containing the extra auto-completion keys, each on a new line. This path is stored in the Krita configuration, and not the project configuration."
"This allows you to make a template document with guides.\n"
"The width and height are the size of the live-area, the safe area is the live area minus the margins, and the full image is the live area plus the bleeds."
"<p>Your name for your script. This is used to calculate the name of your package, the name of the class in your package and the associated directory.</p>"
"<p>What you want to appear in the Tools-> Scripts menu. If you leave this blank a default entry will be created based on the name of the script. </p>"
"<p>If this is checked your script will be automatically enabled in Krita. That is, it will show up in the Scripts menu or docker list. If not, you will need to manually enable the script through the Krita->Settings menu entry. </p>"
msgid "<nobr>Blending controls the percentage of color that is picked</nobr> and mixed with your current brush color. A full blending value picks colors completely, ignoring brush color."
"<p>In \"Global Coordinates\" mode Width and Height fields show the size of the shape's bounding box in image-aligned coordinates, even when the shape is rotated or has any other transform. </p>"
"<p>If \"Global Coordinates\" mode is disabled, Width and Height fields show the shape's \"local\" size, before application of any transformations.</p>"
msgid "Sorry, Krita was built without the support of GNU Scientific Library, so you cannot scale the selection with handles. Please compile Krita with GNU Scientific Library support, or use options widget for editing scale values manually."
msgid "Switch between Build Up and Wash mode of painting. Build Up mode adds deformations one on top of the other without any limits. Wash mode gradually deforms the piece to the selected deformation level."
"Just the named directory, no entries. Updates will not pull in any files or subdirectories not already present. </p>"
"\n"
"<p><i>Files depth</i><br />"
"Folder and its file children, but not subdirs. Updates will pull in any files not already present, but not subdirectories. </p>"
"\n"
"<p><i>Immediate depth</i><br />"
"Folder and its entries. Updates will pull in any files or subdirectories not already present; those subdirectories entries will have depth-empty. </p>"
"\n"
"<p>\n"
"<i>Infinity depth</i><br />"
"Updates will pull in any files or subdirectories not already present; those subdirectories' this_dir entries will have depth-infinity.<br />"
"Equivalent to the pre-1.5 default update behavior. </p>"
"If this flag is set, you will have a simple write support for existing items. E.g. you can open files in your editor and save them direct without checking out them before (kdesvn will do it in background).\n"
"\n"
"Use this only if you are sure what you are doing."
"If one between the first or the second form is used, svn itself generates the diff. %f will be replaced with a temporary filename. If %f is not given,\n"
"the diff-display should be able to read data from stdin.\n"
"<br>"
"\n"
"When %s1 and %s2 are given, kdesvn lets this display make the diff. For that it makes a temporary export or get (if needed) and fills out the parameters with the right values. %s1 will be filled with the content of the initial revision, %s2 with the final revision. On large recursive diffs this may get really slow.\n"
"When listing on working copies kdesvn may check for <tt>svn:needs-lock</tt> property.<br>"
"But due this listings/updating on folders containing lot of items may get slow. So you should only switch on if you have repositories containing lot of such entries."
"<p align=\"left\">When checked, kdesvn get more detailed info about file items when making a listing to remote repositories. So you may see remote locks in overview.\n"
"</p>"
"\n"
"<p align=\"left\"><i>Be careful: This may let listings REAL slow.</i></p>"
"When browsing kdesvn may try displaying properties below itemlist from a selected item. \n"
"On networked repositories (e.g., not opened via file:// protocol) this may get real slow. So if you have slow network connections or when browsing hangs often you should deactivate it."
msgid "Storing passwords is often a security problem. Kdesvn itself does not store any passwords, but the Subversion itself inside the configuration area of Subversion. If this area is readable from others you should not set it, but you may select for single non critical accounts inside the authentication dialog."
"<p>Tells if your passwords set in kdesvn should stored into KDE Wallet instead of simple clear text storage of Subversion.</p>"
"\n"
"<p>This would be a little bit more secure because KDE Wallet is (mostly) encrypted with a password. On other hand you must re-enter your passwords with other Subversion clients not accessing KDE wallet (e.g. svn command line itself, rapidsvn and so on).</p>"
"\n"
"<p>If you are HOME storage e.g. Subversion's config folder is on a network drive you should hard think about not storing passwords in a plain text file like Subversion does but put it into an encrypted storage like KDE Wallet or do not save passwords.</p>"
msgid "Reading lists of changed files may sometimes a little bit slow down things. But if this feature is switched off, kdesvn may fail generating differences between node changes from within the log viewer."
"<p>If set, a local addition at the same path as an incoming addition of the same node kind results in a normal node with a possible local modification, instead of a tree conflict.</p>"
msgid "If set, the repository created will compatible to Subversion prior 1.5. This is only useful when svnqt is running with Subversion 1.6 or above."
msgid "If set, the repository created will compatible to Subversion prior 1.5. This is only useful when svnqt is running with Subversion 1.5 or above."
msgid "If set, the repository created will compatible to Subversion prior 1.4. This is only useful when svnqt is running with Subversion 1.8 or above."
"This property can not be set on a directory. A non-recursive attempt will fail, and a recursive attempt will set the property only on the file children of the folder."
msgstr ""
#. +> trunk5 stable5
#: src/svnfrontend/editpropsdlg.cpp:52
#, kde-format
msgid ""
"Keywords to be expanded into the contents of a file.<br/>"
"They can be inserted into documents by placing a keyword anchor which is formatted as $KeywordName$.<br/>"
"Valid keywords are:<br/>"
"<b>URL/HeadURL</b> The URL for the head revision of the project.<br/>"
"<b>Author/LastChangedBy</b> The last person to change the file.<br/>"
"<b>Date/LastChangedDate</b> The date/time the object was last modified.<br/>"
"<b>Revision/Rev/LastChangedRevision</b> The last revision the object changed.<br/>"
"<b>Id</b> A compressed summary of the previous 4 keywords."
msgstr ""
#. +> trunk5 stable5
#: src/svnfrontend/editpropsdlg.cpp:61
#, kde-format
msgid ""
"Set this to any value (e.g. <b>'*'</b>) to enforce locking for this file.<br/>"
"The file will be set read-only when checked out or updated, indicating that a user must acquire a lock on the file before they can edit and commit changes."
msgid "The mimetype of the file. Used to determine whether to merge the file and how to serve it from Apache. A mimetype beginning with <b>'text/'</b> (or an absent mimetype) is treated as text. Anything else is treated as binary."
msgstr ""
#. +> trunk5 stable5
#: src/svnfrontend/editpropsdlg.cpp:90
#, kde-format
msgid ""
"A newline separated list of module specifiers, each consisting of a relative directory path, optional revision flags, and a URL. For example:<br/>"
msgid "String which is appended to a log message when an issue number is entered. The string must contain <b>%BUGID%</b> which gets replaced with the bug issue number."
msgstr ""
#. +> trunk5 stable5
#: src/svnfrontend/editpropsdlg.cpp:109
#, kde-format
msgid ""
"Set to <b>'yes'</b> if a warning shall be shown when no issue is entered in the commit dialog. Possible values:<br/>"
"<b>'true'</b>/<b>'yes'</b> or <b>'false'</b>/<b>'no'</b>."
msgstr ""
#. +> trunk5 stable5
#: src/svnfrontend/editpropsdlg.cpp:112
#, kde-format
msgid ""
"Set to <b>'false'</b> if your bugtracking system has issues which are referenced not by numbers.<br/>"
"Possible values: <b>'true'</b> or <b>'false'</b>."
msgstr ""
#. +> trunk5 stable5
#: src/svnfrontend/editpropsdlg.cpp:115
#, kde-format
msgid "Set to <b>'false'</b> if you want the bugtracking ID to be inserted at the top of the log message. The default is <b>'true'</b> which means the bugtracking ID is appended to the log message."
msgstr ""
#. +> trunk5 stable5
#: src/svnfrontend/editpropsdlg.cpp:119
#, kde-format
msgid ""
"Two regular expressions separated by a newline.<br/>"
"The first expression is used to find a string referring to an issue, the second expression is used to extract the bare bug ID from that string."
msgid "<b>Useractions</b> can be grouped in categories for better distinction. Choose a existing <i>Category</i> or create a new one by entering a name."
"<p>The <i>Command</i> defines the command that will be executed when the <b>Useraction</b> is used. It can be a simple shell command or a complex sequence of multiple commands with <b>Placeholders</b>.</p>"
"The <i>Command</i> defines the command that will be executed when the <b>Useraction</b> is used. It can be a simple shell command or a complex sequence of multiple commands with <b>Placeholders</b>."
msgid "<qt>There was an error while running <b>%1</b>.</qt>"
msgstr ""
#. +> trunk5 stable5
#: krusader/Dialogs/checksumdlg.cpp:139
#, kde-format
msgid "Error reading stdout or stderr"
msgstr ""
#. +> trunk5 stable5
#: krusader/Dialogs/checksumdlg.cpp:196
#, kde-format
msgid "Please wait..."
msgstr ""
#. +> trunk5 stable5
#: krusader/Dialogs/checksumdlg.cpp:214
#, kde-format
msgid "<qt>Krusader cannot find a checksum tool that handles %1 on your system. Please check the <b>Dependencies</b> page in Krusader's settings.</qt>"
msgstr ""
#. +> trunk5 stable5
#: krusader/Dialogs/checksumdlg.cpp:252
#, kde-format
msgid "Creating Checksums"
msgstr ""
#. +> trunk5 stable5
#: krusader/Dialogs/checksumdlg.cpp:266
#, kde-format
msgid "Create Checksums"
msgstr ""
#. +> trunk5 stable5
#: krusader/Dialogs/checksumdlg.cpp:269
#, kde-format
msgid "About to calculate checksum for the following files or directories:"
msgid "The date %1 is not valid according to your locale. Please re-enter a valid date (use the date button for easy access)."
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/advancedfilter.cpp:492
#, kde-format
msgid "Specified sizes are inconsistent."
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/advancedfilter.cpp:493
#, kde-format
msgid "Please re-enter the values, so that the left side size will be smaller than (or equal to) the right side size."
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/advancedfilter.cpp:512
#: krusader/Filter/advancedfilter.cpp:540
#, kde-format
msgid "Dates are inconsistent."
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/advancedfilter.cpp:513
#, kde-format
msgid "The date on the left is later than the date on the right. Please re-enter the dates, so that the left side date will be earlier than the right side date."
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/advancedfilter.cpp:541
#, kde-format
msgid "The date on top is later than the date on the bottom. Please re-enter the dates, so that the top date will be earlier than the bottom date."
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/filterdialog.cpp:36
#, kde-format
msgid "Krusader::Choose Files"
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/filtertabs.cpp:43
#, kde-format
msgid "&General"
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/filtertabs.cpp:48
#, kde-format
msgid "&Advanced"
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/filtertabs.cpp:116
#, kde-format
msgid "Could not load profile."
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/generalfilter.cpp:49
#, kde-format
msgid "Any Character"
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/generalfilter.cpp:50
#, kde-format
msgid "Start of Line"
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/generalfilter.cpp:51
#, kde-format
msgid "End of Line"
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/generalfilter.cpp:52
#, kde-format
msgid "Set of Characters"
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/generalfilter.cpp:53
#, kde-format
msgid "Repeats, Zero or More Times"
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/generalfilter.cpp:54
#, kde-format
msgid "Repeats, One or More Times"
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/generalfilter.cpp:55
#, kde-format
msgid "Optional"
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/generalfilter.cpp:56
#, kde-format
msgid "Escape"
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/generalfilter.cpp:57
#, kde-format
msgid "TAB"
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/generalfilter.cpp:58
#, kde-format
msgid "Newline"
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/generalfilter.cpp:59
#, kde-format
msgid "Carriage Return"
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/generalfilter.cpp:60
#, kde-format
msgid "White Space"
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/generalfilter.cpp:61
#, kde-format
msgid "Digit"
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/generalfilter.cpp:108
#, kde-format
msgid "&Case sensitive"
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/generalfilter.cpp:113
#, kde-format
msgid "Search &for:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Filter/generalfilter.cpp:128
#: krusader/Synchronizer/synchronizergui.cpp:217
#, kde-format
msgid ""
"<p>The filename filtering criteria is defined here.</p>"
"<p>You can make use of wildcards. Multiple patterns are separated by space (means logical OR) and patterns are excluded from the search using the pipe symbol.</p>"
"<p>If the pattern is ended with a slash (<code>*pattern*/</code>), that means that pattern relates to recursive search of folders."
"<ul>"
"<li><code>pattern</code> - means to search those files/folders that name is <code>pattern</code>, recursive search goes through all subfolders independently of the value of <code>pattern</code></li>"
"<li><code>pattern/</code> - means to search all files/folders, but recursive search goes through/excludes the folders that name is <code>pattern</code></li>"
"</ul>"
"</p>"
"<p>It is allowed to use quotation marks for names that contain space. Filter <code>\"Program Files\"</code> searches out those files/folders that name is <code>Program Files</code>.</p>"
"<p>Examples:</p>"
"<ul>"
"<li><code>*.o</code></li>"
"<li><code>*.h *.c??</code></li>"
"<li><code>*.cpp *.h | *.moc.cpp</code></li>"
"<li><code>* | .svn/ .git/</code></li>"
"</ul>"
"<p><b>Note</b>: the search term '<code>text</code>' is equivalent to '<code>*text*</code>'.</p>"
msgid "View the file in hex-mode (better for binary files)"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:106
#, kde-format
msgid "Lister mode"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:106
#, kde-format
msgid "View the file with lister (for huge text files)"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:114
#, kde-format
msgid "Use Okteta as Hex viewer"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:115
#, kde-format
msgid "If available, use Okteta as Hex viewer instead of the internal viewer"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:121
#, kde-format
msgid "Use lister if the text file is bigger than:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:126
#, kde-format
msgid "MB"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:138
#, kde-format
msgid "Editor"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:142
#, kde-format
msgid "Editor:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:148
#, kde-format
msgid "Hint: use 'internal editor' if you want to use Krusader's fast built-in editor"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:156
#, kde-format
msgid "Atomic extensions"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:171
#, kde-format
msgid "Atomic extensions:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:221
#, kde-format
msgid "Warn on exit"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:221
#, kde-format
msgid "Display a warning when trying to close the main window."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:222
#, kde-format
msgid "Show and close to tray"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:222
#, kde-format
msgid "Show an icon in the system tray and keep running in the background when the window is closed."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:231
#, kde-format
msgid "Temp Folder:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:239
#, kde-format
msgid "Note: you must have full permissions for the temporary folder."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:249
#, kde-format
msgid "Delete mode"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:254
#, kde-format
msgid "Move to trash"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:254
#, kde-format
msgid "Files will be moved to trash when deleted."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:255
#, kde-format
msgid "Delete files"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:255
#, kde-format
msgid "Files will be permanently deleted."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:266
#: krusader/Panel/panelcontextmenu.cpp:197
#, kde-format
msgid "Terminal"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:269
#, kde-format
msgid "External Terminal:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:274
#, kde-format
msgid "%d will be replaced by the workdir."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:279
#, kde-format
msgid "Embedded Terminal sends Chdir on panel change"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:279
#, kde-format
msgid "When checked, whenever the panel is changed (for example, by pressing Tab), Krusader changes the current folder in the embedded terminal."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:301
#, kde-format
msgid "Searching for tools..."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:303
#, kde-format
msgid "Make sure to install new tools in your <code>$PATH</code> (e.g. /usr/bin)"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:311
#, kde-format
msgid "Add new atomic extension"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:311
#, kde-format
msgid "Extension:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kggeneral.cpp:316
#, kde-format
msgid "Atomic extensions must start with '.' and must contain at least one more '.' character."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:88
#, kde-format
msgid "Navigator bar"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:93
#, kde-format
msgid "Edit Mode by default"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:93
#, kde-format
msgid "Show editable path in Navigator bar by default"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:94
#, kde-format
msgid "Show full path by default"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:94
#, kde-format
msgid "Always show full path in Navigator bar by default."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:104
#, kde-format
msgid "Operation"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:108
#, kde-format
msgid "Autoselect folders"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:108
#, kde-format
msgid "When matching the select criteria, not only files will be selected, but also folders."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:109
#, kde-format
msgid "Rename selects extension"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:109
#, kde-format
msgid "When renaming a file, the whole text is selected. If you want Total-Commander like renaming of just the name, without extension, uncheck this option."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:110
#, kde-format
msgid "Unselect files before copy/move"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:110
#, kde-format
msgid "Unselect files, which are to be copied/moved, before the operation starts."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:111
#, kde-format
msgid "Filter dialog remembers settings"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:111
#, kde-format
msgid "The filter dialog is opened with the last filter settings that where applied to the panel."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:121
#, kde-format
msgid "Tabs"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:125
#, kde-format
msgid "Use full path tab names"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:125
#, kde-format
msgid "Display the full path in the folder tabs. By default only the last part of the path is displayed."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:126
#, kde-format
msgid "Show new/close tab buttons"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:126
#, kde-format
msgid "Show the new/close tab buttons."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:134
#, kde-format
msgid "Tab Bar position:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:137
#, kde-format
msgid "Top"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:138
#, kde-format
msgid "Bottom"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:149
#, kde-format
msgid "Show Tab Bar on single tab"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:150
#, kde-format
msgid "Show the tab bar with only one tab."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:158
#, kde-format
msgid "Search bar"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:162
#, kde-format
msgid "Start by typing"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:162
#, kde-format
msgid "Open search bar and start searching by typing in panel."
msgid "Bookmark search is also applied to special items in bookmark menu like Trash, Popular URLs, Jump Back, etc."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:218
#, kde-format
msgid "Status/Totalsbar"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:223
#, kde-format
msgid "Show size in bytes too"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:224
#, kde-format
msgid "Show space information"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:224
#, kde-format
msgid "Show free/total space on the device"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:243
#, kde-format
msgid "Layout"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:252
#, kde-format
msgid "Layout:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:265
#, kde-format
msgid "Frame Color:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:269
#, kde-format
msgctxt "Frame color"
msgid "Defined by Layout"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:270
#, kde-format
msgctxt "Frame color"
msgid "None"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:271
#, kde-format
msgctxt "Frame color"
msgid "Statusbar"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:278
#, kde-format
msgid "Frame Shape:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:282
#, kde-format
msgctxt "Frame shape"
msgid "Defined by Layout"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:283
#, kde-format
msgctxt "Frame shape"
msgid "None"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:284
#, kde-format
msgctxt "Frame shape"
msgid "Box"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:285
#, kde-format
msgctxt "Frame shape"
msgid "Panel"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:292
#, kde-format
msgid "Frame Shadow:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:296
#, kde-format
msgctxt "Frame shadow"
msgid "Defined by Layout"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:297
#, kde-format
msgctxt "Frame shadow"
msgid "None"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:298
#, kde-format
msgctxt "Frame shadow"
msgid "Raised"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:299
#, kde-format
msgctxt "Frame shadow"
msgid "Sunken"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:313
#, kde-format
msgid "Default icon size:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:331
#, kde-format
msgid "Use icons in the filenames"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:331
#, kde-format
msgid "Show the icons for filenames and folders."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:332
#, kde-format
msgid "Show previews by default"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:332
#, kde-format
msgid "Show previews of files and folders."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:367
#, kde-format
msgid "View font:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:376
#, kde-format
msgid "Tooltip delay (msec):"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:377
#, kde-format
msgid "The duration after a tooltip is shown for a file item, in milliseconds. Set a negative value to disable tooltips."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:394
#, kde-format
msgid "Use human-readable file size"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:394
#, kde-format
msgid "File sizes are displayed in B, KB, MB and GB, not just in bytes."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:395
#, kde-format
msgid "Show hidden files"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:395
#, kde-format
msgid "Display files beginning with a dot."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:396
#, kde-format
msgid "Numeric Permissions"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:396
#, kde-format
msgid "Show octal numbers (0755) instead of the standard permissions (rwxr-xr-x) in the permission column."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:397
#, kde-format
msgid "Load the user defined folder icons"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:397
#, kde-format
msgid "Load the user defined folder icons (can cause decrease in performance)."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:398
#, kde-format
msgid "Always show current item"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:398
#, kde-format
msgid "Show current item border decoration in inactive panel."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:412
#, kde-format
msgid "Sort method:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:414
#, kde-format
msgid "Alphabetical"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:415
#, kde-format
msgid "Alphabetical and numbers"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:416
#, kde-format
msgid "Character code"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:417
#, kde-format
msgid "Character code and numbers"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:418
#, kde-format
msgctxt "Krusader sort"
msgid "Krusader"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:431
#, kde-format
msgid "Case sensitive sorting"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:432
#, kde-format
msgid "All files beginning with capital letters appear before files beginning with non-capital letters (UNIX default)."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:433
#, kde-format
msgid "Show folders first"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:434
#, kde-format
msgid "Always sort dirs by name"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:435
#, kde-format
msgid "Folders are sorted by name, regardless of the sort column."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:436
#, kde-format
msgid "Locale aware sorting"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:437
#, kde-format
msgid "The sorting is performed in a locale- and also platform-dependent manner. Can be slow."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:451
#, kde-format
msgid "View modes"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:458
#, kde-format
msgid "Default view mode:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:504
#, kde-format
msgid "Buttons"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:513
#, kde-format
msgid "Toolbar buttons have icons"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:514
#, kde-format
msgid "Show Media Button"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:514
#, kde-format
msgid "The media button will be visible."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:515
#, kde-format
msgid "Show Back Button"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:516
#, kde-format
msgid "Show Forward Button"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:517
#, kde-format
msgid "Show History Button"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:517
#, kde-format
msgid "The history button will be visible."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:518
#, kde-format
msgid "Show Bookmarks Button"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:518
#, kde-format
msgid "The bookmarks button will be visible."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:519
#, kde-format
msgid "Show Panel Toolbar"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:519
#, kde-format
msgid "The panel toolbar will be visible."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:525
#, kde-format
msgid "Visible Panel Toolbar buttons"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:529
#, kde-format
msgid "Equal button (=)"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:529
#, kde-format
msgid "Changes the panel folder to the other panel folder."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:530
#, kde-format
msgid "Up button (..)"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:530
#, kde-format
msgid "Changes the panel folder to the parent folder."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:531
#, kde-format
msgid "Home button (~)"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:531
#, kde-format
msgid "Changes the panel folder to the home folder."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:532
#, kde-format
msgid "Root button (/)"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:532
#, kde-format
msgid "Changes the panel folder to the root folder."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:533
#, kde-format
msgid "Toggle-button for sync-browsing"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:533
#, kde-format
msgid "Each folder change in the panel is also performed in the other panel."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:555
#, kde-format
msgid "Selection Mode"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:568
#, kde-format
msgid "Krusader Mode"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:568
#, kde-format
msgid "Both keys allow selecting files. To select more than one file, hold the Ctrl key and click the left mouse button. Right-click menu is invoked using a short click on the right mouse button."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:569
#, kde-format
msgid "Konqueror Mode"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:569
#, kde-format
msgid "Pressing the left mouse button selects files - you can click and select multiple files. Right-click menu is invoked using a short click on the right mouse button."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:570
#, kde-format
msgid "Total-Commander Mode"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:570
#, kde-format
msgid "The left mouse button does not select, but sets the current file without affecting the current selection. The right mouse button selects multiple files and the right-click menu is invoked by pressing and holding the right mouse button."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:571
#, kde-format
msgid "Ergonomic Mode"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:571
#, kde-format
msgid "The left mouse button does not select, but sets the current file without affecting the current selection. The right mouse button invokes the context-menu. You can select with Ctrl key and the left button."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:572
#, kde-format
msgid "Custom Selection Mode"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:572
#, kde-format
msgid "Design your own selection mode."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:584
#, kde-format
msgid "Details"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:591
#, kde-format
msgid "Double-click selects (classic)"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:591
#, kde-format
msgid "A single click on a file will select and focus, a double click opens the file or steps into the folder."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:592
#, kde-format
msgid "Obey global selection policy"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:592
#, kde-format
msgid ""
"<p>Use global setting:</p>"
"<p><i>Plasma System Settings -> Input Devices -> Mouse</i></p>"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:603
#, kde-format
msgid "Based on KDE's selection mode"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:604
#, kde-format
msgid "If checked, use a mode based on KDE's style."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:606
#, kde-format
msgid "Left mouse button selects"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:607
#, kde-format
msgid "If checked, left clicking an item will select it."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:609
#, kde-format
msgid "Left mouse button preserves selection"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:610
#, kde-format
msgid "If checked, left clicking an item will select it, but will not unselect other, already selected items."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:612
#, kde-format
msgid "Shift/Ctrl-Left mouse button selects"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:613
#, kde-format
msgid ""
"If checked, Shift/Ctrl left clicking will select items.\n"
"Note: this is meaningless if 'Left Button Selects' is checked."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:615
#, kde-format
msgid "Right mouse button selects"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:616
#, kde-format
msgid "If checked, right clicking an item will select it."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:618
#, kde-format
msgid "Right mouse button preserves selection"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:619
#, kde-format
msgid "If checked, right clicking an item will select it, but will not unselect other, already selected items."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:621
#, kde-format
msgid "Shift/Ctrl-Right mouse button selects"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:622
#, kde-format
msgid ""
"If checked, Shift/Ctrl right clicking will select items.\n"
"Note: this is meaningless if 'Right Button Selects' is checked."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:624
#, kde-format
msgid "Spacebar moves down"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:625
#, kde-format
msgid ""
"If checked, pressing the spacebar will select the current item and move down.\n"
"Otherwise, current item is selected, but remains the current item."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:627
#, kde-format
msgid "Spacebar calculates disk space"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:628
#, kde-format
msgid ""
"If checked, pressing the spacebar while the current item is a folder, will (except from selecting the folder)\n"
"calculate space occupied of the folder (recursively)."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:630
#, kde-format
msgid "Insert moves down"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:631
#, kde-format
msgid ""
"If checked, pressing Insert will select the current item, and move down to the next item.\n"
"Otherwise, current item is not changed."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:633
#, kde-format
msgid "Right clicking pops context menu immediately"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:634
#, kde-format
msgid ""
"If checked, right clicking will result in an immediate showing of the context menu.\n"
"Otherwise, user needs to click and hold the right mouse button for 500ms."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:670
#, kde-format
msgid "Media Menu"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:679
#, kde-format
msgid "Show Mount Path"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:680
#, kde-format
msgid "Show File System Type"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:689
#, kde-format
msgid "Show Size:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:691
#, kde-format
msgctxt "setting 'show size'"
msgid "Always"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:692
#, kde-format
msgctxt "setting 'show size'"
msgid "When Device has no Label"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgpanel.cpp:693
#, kde-format
msgctxt "setting 'show size'"
msgid "Never"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgprotocols.cpp:47
#, kde-format
msgid "Links"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgprotocols.cpp:51
#, kde-format
msgid "Defined Links"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgprotocols.cpp:68
#, kde-format
msgid "Add protocol to the link list."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgprotocols.cpp:73
#, kde-format
msgid "Remove protocol from the link list."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgprotocols.cpp:85
#, kde-format
msgid "Add MIME to the selected protocol on the link list."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgprotocols.cpp:90
#, kde-format
msgid "Remove MIME from the link list."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgprotocols.cpp:98
#: krusader/Konfigurator/konfigurator.cpp:146
#, kde-format
msgid "Protocols"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgprotocols.cpp:109
#, kde-format
msgid "MIMEs"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgstartup.cpp:46
#, kde-format
msgid ""
"Defines the panel profile used at startup. A panel profile contains:"
"<ul>"
"<li>all the tabs paths</li>"
"<li>the current tab</li>"
"<li>the active panel</li>"
"</ul>"
"<b><Last session></b> is a special panel profile which is saved automatically when Krusader is closed."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgstartup.cpp:47
#, kde-format
msgid "Startup profile:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgstartup.cpp:52
#, kde-format
msgid "<Last session>"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgstartup.cpp:70
#, kde-format
msgid "Show splashscreen"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgstartup.cpp:70
#, kde-format
msgid "Display a splashscreen when starting Krusader."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgstartup.cpp:71
#, kde-format
msgid "Single instance mode"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgstartup.cpp:71
#, kde-format
msgid "Only one Krusader instance is allowed to run."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgstartup.cpp:78
#, kde-format
msgid "Fallback Icon Theme:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgstartup.cpp:79
#, kde-format
msgid "Whenever icon is not found in system icon theme, this theme will be used as a fallback. If fallback theme doesn't contain the icon, Breeze or Oxygen will be used if any of these are present."
msgid "Save last position, size and panel settings"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgstartup.cpp:100
#, kde-format
msgid ""
"<p>At startup, the main window will resize itself to the size it was when last shutdown. It will also appear in the same location of the screen, having panels sorted and aligned as they were before.</p>"
" "
"<p>If this option is disabled, you can use the menu <i>Window -> Save Position</i> option to manually set the main window's size and position at startup.</p>"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgstartup.cpp:104
#, kde-format
msgid "Update default panel settings"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgstartup.cpp:105
#, kde-format
msgid "When settings of a panel are changed, save them as the default for new panels of the same type."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgstartup.cpp:106
#, kde-format
msgid "Start to tray"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgstartup.cpp:107
#, kde-format
msgid "Krusader starts to tray, without showing the main window"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgstartup.cpp:114
#, kde-format
msgid "Save component settings on exit"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgstartup.cpp:115
#, kde-format
msgid "Check the state of the user interface components and restore them to their condition when last shutdown."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgstartup.cpp:116
#, kde-format
msgid "Show function keys"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgstartup.cpp:116
#, kde-format
msgid "Function keys will be visible after startup."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgstartup.cpp:117
#, kde-format
msgid "Show command line"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgstartup.cpp:117
#, kde-format
msgid "Command line will be visible after startup."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgstartup.cpp:118
#, kde-format
msgid "Show embedded terminal"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kgstartup.cpp:119
#, kde-format
msgid "Embedded terminal will be visible after startup."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kguseractions.cpp:41
#, kde-format
msgid "Information"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kguseractions.cpp:46
#, kde-format
msgid ""
"Here you can configure settings about useractions.\n"
"To set up, configure and manage your useractions please use ActionMan."
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kguseractions.cpp:50
#, kde-format
msgid "Start ActionMan"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kguseractions.cpp:57
#, kde-format
msgid "Terminal execution"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kguseractions.cpp:61
#, kde-format
msgid "Terminal for UserActions:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Konfigurator/kguseractions.cpp:67
#, kde-format
msgid ""
"%t will be replaced by the title of the action,\n"
msgid "Statusbar will show basic information about file below mouse pointer."
msgstr ""
#. +> trunk5 stable5
#: krusader/krusader.cpp:328
#, kde-format
msgid ""
"<qt><b>Welcome to Krusader.</b>"
"<p>As this is your first run, your machine will now be checked for external applications. Then the Konfigurator will be launched where you can customize Krusader to your needs.</p>"
msgctxt "%1=number of selected items,%2=total number of items, %3=filesize of selected items,%4=filesize in Bytes, %5=filesize of all items in folder,%6=filesize in Bytes"
msgid "%1 out of %2, %3 (%4) out of %5 (%6)"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/krview.cpp:439
#, kde-format
msgctxt "%1=number of selected items,%2=total number of items, %3=filesize of selected items,%4=filesize of all items in folder"
msgid "%1 out of %2, %3 out of %4"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/krview.cpp:1088
#, kde-format
msgid "Filter Files"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/krview.cpp:1088
#: krusader/Panel/PanelView/krview.cpp:1089
#: krusader/Panel/PanelView/krview.cpp:1098
#, kde-format
msgid "Apply filter to folders"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/krview.cpp:1114
#, kde-format
msgid "Select Files"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/krview.cpp:1114
#: krusader/Panel/PanelView/krview.cpp:1115
#: krusader/Panel/PanelView/krview.cpp:1121
#, kde-format
msgid "Apply selection to folders"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/krviewfactory.cpp:67
#, kde-format
msgid "&Detailed View"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/krviewfactory.cpp:70
#, kde-format
msgid "&Brief View"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/krviewitem.cpp:75
#, kde-format
msgid "Climb up the folder tree"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/krviewitem.cpp:88
#, kde-format
msgid "(Broken Link)"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/krviewitem.cpp:90
#, kde-format
msgid "Symbolic Link"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/krviewitem.cpp:92
#, kde-format
msgid "%1 (Link)"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/listmodel.cpp:143
#: krusader/Synchronizer/synchronizergui.cpp:1583
#, kde-format
msgctxt "Show the string 'DIR' instead of file size in detailed view (for folders)"
msgid "DIR"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/listmodel.cpp:384
#, kde-format
msgctxt "File property"
msgid "Name"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/listmodel.cpp:385
#, kde-format
msgctxt "File property"
msgid "Ext"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/listmodel.cpp:386
#, kde-format
msgctxt "File property"
msgid "Size"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/listmodel.cpp:387
#, kde-format
msgctxt "File property"
msgid "Type"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/listmodel.cpp:388
#, kde-format
msgctxt "File property"
msgid "Modified"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/listmodel.cpp:389
#, kde-format
msgctxt "File property"
msgid "Changed"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/listmodel.cpp:390
#, kde-format
msgctxt "File property"
msgid "Accessed"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/listmodel.cpp:391
#, kde-format
msgctxt "File property"
msgid "Perms"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/listmodel.cpp:392
#, kde-format
msgctxt "File property"
msgid "rwx"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/listmodel.cpp:393
#, kde-format
msgctxt "File property"
msgid "Owner"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/listmodel.cpp:394
#, kde-format
msgctxt "File property"
msgid "Group"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/listmodel.cpp:497
#, kde-format
msgid "Size: %1"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/listmodel.cpp:499
#, kde-format
msgctxt "File property"
msgid "Type: %1"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/listmodel.cpp:500
#, kde-format
msgctxt "File property"
msgid "Modified: %1"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/listmodel.cpp:501
#, kde-format
msgctxt "File property"
msgid "Changed: %1"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/listmodel.cpp:502
#, kde-format
msgctxt "File property"
msgid "Last Access: %1"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/listmodel.cpp:503
#, kde-format
msgctxt "File property"
msgid "Permissions: %1"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/listmodel.cpp:505
#, kde-format
msgctxt "File property"
msgid "Owner: %1"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/listmodel.cpp:506
#, kde-format
msgctxt "File property"
msgid "Group: %1"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/listmodel.cpp:510
#, kde-format
msgctxt "File property; broken symbolic link"
msgid "Link to: %1 - (broken)"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/PanelView/listmodel.cpp:512
#, kde-format
msgctxt "File property"
msgid "Link to: %1"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/sidebar.cpp:68
#, kde-format
msgid "Tree Panel: a tree view of the local file system"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/sidebar.cpp:75
#, kde-format
msgid "Preview Panel: display a preview of the current file"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/sidebar.cpp:82
#, kde-format
msgid "View Panel: view the current file"
msgstr ""
#. +> trunk5 stable5
#: krusader/Panel/sidebar.cpp:89
#, kde-format
msgid "Disk Usage Panel: view the usage of a folder"
msgid "The left base folder used during the synchronization process."
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:233
#, kde-format
msgid "The right base folder used during the synchronization process."
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:247
#, kde-format
msgid "Recurse subfolders"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:250
#, kde-format
msgid "Compare not only the base folders but their subfolders as well."
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:251
#, kde-format
msgid "Follow symlinks"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:255
#, kde-format
msgid "Follow symbolic links during the compare process."
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:259
#, kde-format
msgid "Compare duplicated files with same size by content."
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:260
#, kde-format
msgid "Ignore Date"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:263
#, kde-format
msgid ""
"<p>Ignore date information during the compare process.</p>"
"<p><b>Note</b>: useful if the files are located on network filesystems or in archives.</p>"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:264
#, kde-format
msgid "Asymmetric"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:267
#, kde-format
msgid ""
"<p><b>Asymmetric mode</b></p>"
"<p>The left side is the destination, the right is the source folder. Files existing only in the left folder will be deleted, the other differing ones will be copied from right to left.</p>"
"<p><b>Note</b>: useful when updating a folder from a file server.</p>"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:268
#, kde-format
msgid "Ignore Case"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:271
#, kde-format
msgid ""
"<p>Case insensitive filename compare.</p>"
"<p><b>Note</b>: useful when synchronizing Windows filesystems.</p>"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:278
#, kde-format
msgid "S&how options"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:289
#, kde-format
msgid "Show files marked to <i>Copy from left to right</i>."
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:295
#, kde-format
msgid "Show files considered to be identical."
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:301
#, kde-format
msgid "Show excluded files."
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:307
#, kde-format
msgid "Show files marked to <i>Copy from right to left</i>."
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:313
#, kde-format
msgid "Show files marked to delete."
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:319
#, kde-format
msgid "Show files that exist on both sides."
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:321
#, kde-format
msgid "Duplicates"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:325
#, kde-format
msgid "Show files that exist on one side only."
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:327
#, kde-format
msgid "Singles"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:336
#, kde-format
msgid "The compare results of the synchronizer (Ctrl+M)."
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:347
#: krusader/Synchronizer/synchronizergui.cpp:353
#, kde-format
msgctxt "@title:column file name"
msgid "Name"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:348
#: krusader/Synchronizer/synchronizergui.cpp:352
#, kde-format
msgctxt "@title:column"
msgid "Size"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:349
#: krusader/Synchronizer/synchronizergui.cpp:351
#, kde-format
msgctxt "@title:column"
msgid "Date"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:350
#, kde-format
msgid "<=>"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:385
#, kde-format
msgid "&Synchronizer"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:396
#, kde-format
msgid "&Options"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:403
#, kde-format
msgid "Parallel threads:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:413
#, kde-format
msgid "Equality threshold:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:421
#: krusader/Synchronizer/synchronizergui.cpp:436
#, kde-format
msgid "sec"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:422
#: krusader/Synchronizer/synchronizergui.cpp:437
#, kde-format
msgid "min"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:423
#: krusader/Synchronizer/synchronizergui.cpp:438
#, kde-format
msgid "hour"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:424
#: krusader/Synchronizer/synchronizergui.cpp:439
#, kde-format
msgid "day"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:427
#, kde-format
msgid "Time shift (right-left):"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:446
#, kde-format
msgid "Ignore hidden files"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:460
#, kde-format
msgid "Profile manager (Ctrl+P)."
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:466
#, kde-format
msgid "Swap sides (Ctrl+S)."
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:476
#, kde-format
msgid "Compare"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:486
#: krusader/Synchronizer/synchronizergui.cpp:1481
#, kde-format
msgid "Quiet"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:488
#: krusader/Synchronizer/synchronizergui.cpp:1483
#, kde-format
msgid "Scroll Results"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:505
#, kde-format
msgid "Synchronize"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:621
#, kde-format
msgid "Selected files from targ&et folder:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:622
#, kde-format
msgid "Selected files from sou&rce folder:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:624
#, kde-format
msgid "Selected files from &left folder:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:625
#, kde-format
msgid "Selected files from &right folder:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:627
#, kde-format
msgid "Targ&et folder:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:628
#, kde-format
msgid "Sou&rce folder:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:630
#, kde-format
msgid "&Left folder:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:631
#, kde-format
msgid "&Right folder:"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:664
#, kde-format
msgid "URL must be the descendant of either the left or the right base URL."
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:722
#, kde-format
msgid "Synchronize Folders"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:724
#, kde-format
msgid "E&xclude"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:726
#, kde-format
msgid "Restore ori&ginal operation"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:728
#, kde-format
msgid "Re&verse direction"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:730
#, kde-format
msgid "Copy from &right to left"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:732
#, kde-format
msgid "Copy from &left to right"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:734
#, kde-format
msgid "&Delete (left single)"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:739
#, kde-format
msgid "V&iew left file"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:742
#, kde-format
msgid "Vi&ew right file"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:745
#, kde-format
msgid "&Compare Files"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:751
#, kde-format
msgid "C&opy selected to clipboard (left)"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:753
#, kde-format
msgid "Co&py selected to clipboard (right)"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:758
#, kde-format
msgid "&Select items"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:760
#, kde-format
msgid "Deselec&t items"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:762
#, kde-format
msgid "I&nvert selection"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:772
#, kde-format
msgid "Synchronize with &KGet"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:847
#, kde-format
msgid "Select items"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:848
#, kde-format
msgid "Deselect items"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:972
#, kde-format
msgid "The target folder must not be empty."
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:977
#, kde-format
msgid "The source folder must not be empty."
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:1217
#, kde-format
msgid "Synchronizer has nothing to do."
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizergui.cpp:1307
#, kde-format
msgid "The synchronizer window contains data from a previous compare. If you exit, this data will be lost. Do you really want to exit?"
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizertask.cpp:137
#: krusader/Synchronizer/synchronizertask.cpp:144
#, kde-format
msgid "Error at opening %1."
msgstr ""
#. +> trunk5 stable5
#: krusader/Synchronizer/synchronizertask.cpp:301
#, kde-format
msgid "I/O error while comparing file %1 with %2."
msgid "Please use <a href=\"https://bugs.kde.org\">https://bugs.kde.org</a> to report bugs.\n"
msgstr ""
#. +> trunk5
#: kaboutapplicationdialog.cpp:192
#, kde-format
msgid "Please report bugs to <a href=\"%1\">%2</a>.\n"
msgstr ""
#. +> trunk5
#: kaboutapplicationdialog.cpp:218
#, kde-format
msgid "A&uthor"
msgstr ""
#. +> trunk5
#: kaboutapplicationdialog.cpp:218
#, kde-format
msgid "A&uthors"
msgstr ""
#. +> trunk5
#: kaboutapplicationdialog.cpp:245
#, kde-format
msgid "&Thanks To"
msgstr ""
#. +> trunk5
#: kaboutapplicationdialog.cpp:284
#, kde-format
msgid "T&ranslation"
msgstr ""
#. +> trunk5
#: kaboutapplicationdialog.cpp:316
#, kde-format
msgid "License Agreement"
msgstr ""
#. +> trunk5
#: kaboutapplicationpersonlistdelegate_p.cpp:62
#, kde-format
msgctxt "Action to send an email to a contributor"
msgid "Email contributor"
msgstr ""
#. +> trunk5
#: kaboutapplicationpersonlistdelegate_p.cpp:67
#, kde-format
msgid "Visit contributor's homepage"
msgstr ""
#. +> trunk5
#: kaboutapplicationpersonlistdelegate_p.cpp:128
#, kde-format
msgctxt "Action to send an email to a contributor"
msgid ""
"Email contributor\n"
"%1"
msgstr ""
#. +> trunk5
#: kaboutapplicationpersonlistdelegate_p.cpp:134
#: kaboutapplicationpersonlistdelegate_p.cpp:170
#, kde-format
msgid ""
"Visit contributor's homepage\n"
"%1"
msgstr ""
#. +> trunk5
#: kaboutapplicationpersonlistdelegate_p.cpp:141
#: kaboutapplicationpersonlistdelegate_p.cpp:173
#, kde-format
msgid ""
"Visit contributor's profile on %1\n"
"%2"
msgstr ""
#. +> trunk5
#: kaboutapplicationpersonlistdelegate_p.cpp:164
#, kde-format
msgid ""
"Visit contributor's page\n"
"%1"
msgstr ""
#. +> trunk5
#: kaboutapplicationpersonlistdelegate_p.cpp:167
#, kde-format
msgid ""
"Visit contributor's blog\n"
"%1"
msgstr ""
#. +> trunk5
#: kaboutapplicationpersonlistdelegate_p.cpp:265
#, kde-format
msgctxt "@item Contributor name in about dialog."
msgid "%1"
msgstr ""
#. +> trunk5
#: kaboutapplicationpersonmodel_p.cpp:206
#, kde-format
msgctxt "City, Country"
msgid "%1, %2"
msgstr ""
#. +> trunk5
#: kaboutapplicationpersonmodel_p.cpp:309
#, kde-format
msgctxt "A generic social network or homepage link of an unlisted type."
msgid "Other"
msgstr ""
#. +> trunk5
#: kaboutapplicationpersonmodel_p.cpp:311
#, kde-format
msgctxt "A type of link."
msgid "Blog"
msgstr ""
#. +> trunk5
#: kaboutapplicationpersonmodel_p.cpp:319
#, kde-format
msgctxt "A type of link."
msgid "Homepage"
msgstr ""
#. +> trunk5
#: kaboutkdedialog_p.cpp:43
#, kde-format
msgid "About KDE"
msgstr ""
#. +> trunk5
#: kaboutkdedialog_p.cpp:46
#, kde-format
msgid "<html><font size=\"5\">KDE - Be Free!</font></html>"
msgstr ""
#. +> trunk5
#: kaboutkdedialog_p.cpp:55
#, kde-format
msgid ""
"<html><b>KDE</b> is a world-wide community of software engineers, artists, writers, translators and creators who are committed to <a href=\"%1\">Free Software</a> development. KDE produces the Plasma desktop environment, hundreds of applications, and the many software libraries that support them.<br />"
"<br />"
"KDE is a cooperative enterprise: no single entity controls its direction or products. Instead, we work together to achieve the common goal of building the world's finest Free Software. Everyone is welcome to <a href=\"%2\">join and contribute</a> to KDE, including you.<br />"
"<br />"
"Visit <a href=\"%3\">%3</a> for more information about the KDE community and the software we produce.</html>"
msgstr ""
#. +> trunk5
#: kaboutkdedialog_p.cpp:75
#, kde-format
msgid ""
"<html>Software can always be improved, and the KDE team is ready to do so. However, you - the user - must tell us when something does not work as expected or could be done better.<br />"
"<br />"
"KDE has a bug tracking system. Visit <a href=\"%1\">%1</a> or use the \"Report Bug...\" dialog from the \"Help\" menu to report bugs.<br />"
"<br />"
"If you have a suggestion for improvement then you are welcome to use the bug tracking system to register your wish. Make sure you use the severity called \"Wishlist\".</html>"
msgstr ""
#. +> trunk5
#: kaboutkdedialog_p.cpp:93
#, kde-format
msgid ""
"<html>You do not have to be a software developer to be a member of the KDE team. You can join the national teams that translate program interfaces. You can provide graphics, themes, sounds, and improved documentation. You decide!<br />"
"<br />"
"Visit <a href=\"%1\">%1</a> for information on some projects in which you can participate.<br />"
"<br />"
"If you need more information or documentation, then a visit to <a href=\"%2\">%2</a> will provide you with what you need.</html>"
msgstr ""
#. +> trunk5
#: kaboutkdedialog_p.cpp:115
#, kde-format
msgid ""
"<html>KDE software is and will always be available free of charge, however creating it is not free.<br />"
"<br />"
"To support development the KDE community has formed the KDE e.V., a non-profit organization legally founded in Germany. KDE e.V. represents the KDE community in legal and financial matters. See <a href=\"%1\">%1</a> for information on KDE e.V.<br />"
"<br />"
"KDE benefits from many kinds of contributions, including financial. We use the funds to reimburse members and others for expenses they incur when contributing. Further funds are used for legal support and organizing conferences and meetings. <br />"
" <br />"
"We would like to encourage you to support our efforts with a financial donation, using one of the ways described at <a href=\"%2\">%2</a>.<br />"
"<br />"
"Thank you very much in advance for your support.</html>"
msgstr ""
#. +> trunk5
#: kaboutkdedialog_p.cpp:135
#, kde-format
msgctxt "About KDE"
msgid "&About"
msgstr ""
#. +> trunk5
#: kaboutkdedialog_p.cpp:136
#, kde-format
msgid "&Report Bugs or Wishes"
msgstr ""
#. +> trunk5
#: kaboutkdedialog_p.cpp:137
#, kde-format
msgid "&Join KDE"
msgstr ""
#. +> trunk5
#: kaboutkdedialog_p.cpp:138
#, kde-format
msgid "&Support KDE"
msgstr ""
#. +> trunk5
#: kactionconflictdetector.cpp:50
#, kde-format
msgid ""
"The key sequence '%1' is ambiguous. Use 'Configure Shortcuts'\n"
"from the 'Settings' menu to solve the ambiguity.\n"
"No action will be triggered."
msgstr ""
#. +> trunk5
#: kactionconflictdetector.cpp:54
#, kde-format
msgid "Ambiguous shortcut detected"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:104 kbugreport.cpp:133
#, kde-format
msgid "Submit Bug Report"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:144
#, kde-format
msgid "Your email address. If incorrect, use the Configure Email button to change it"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:145
#, kde-format
msgctxt "Email sender address"
msgid "From:"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:153
#, kde-format
msgid "Configure Email..."
msgstr ""
#. +> trunk5
#: kbugreport.cpp:160
#, kde-format
msgid "The email address this bug report is sent to."
msgstr ""
#. +> trunk5
#: kbugreport.cpp:161
#, kde-format
msgctxt "Email receiver address"
msgid "To:"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:170
#, kde-format
msgid "&Send"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:170
#, kde-format
msgid "Send bug report."
msgstr ""
#. +> trunk5
#: kbugreport.cpp:171
#, kde-format
msgid "Send this bug report to %1."
msgstr ""
#. +> trunk5
#: kbugreport.cpp:179
#, kde-format
msgid "The application for which you wish to submit a bug report - if incorrect, please use the Report Bug menu item of the correct application"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:180
#, kde-format
msgid "Application: "
msgstr ""
#. +> trunk5
#: kbugreport.cpp:207
#, kde-format
msgid "The version of this application - please make sure that no newer version is available before sending a bug report"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:208
#, kde-format
msgid "Version:"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:213
#, kde-format
msgid "no version set (programmer error)"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:226
#, kde-format
msgid "OS:"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:234
#, kde-format
msgid "Compiler:"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:242
#, kde-format
msgid "Se&verity"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:244
#, kde-format
msgid "Critical"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:244
#, kde-format
msgid "Grave"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:244
#, kde-format
msgctxt "normal severity"
msgid "Normal"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:244
#, kde-format
msgid "Wishlist"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:244
#, kde-format
msgid "Translation"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:262
#, kde-format
msgid "S&ubject: "
msgstr ""
#. +> trunk5
#: kbugreport.cpp:270
#, kde-format
msgid ""
"Enter the text (in English if possible) that you wish to submit for the bug report.\n"
"If you press \"Send\", a mail message will be sent to the maintainer of this program.\n"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:294
#, kde-format
msgid "<qt>To submit a bug report, click on the button below. This will open a web browser window on <a href=\"https://bugs.kde.org\">https://bugs.kde.org</a> where you will find a form to fill in. The information displayed above will be transferred to that server.</qt>"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:299
#, kde-format
msgid "<qt>To submit a bug report, click on the button below. This will open a web browser window on <a href=\"%1\">%2</a>.</qt>"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:316
#, kde-format
msgid "&Launch Bug Report Wizard"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:318
#, kde-format
msgid "&Submit Bug Report"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:382
#, kde-format
msgctxt "unknown program name"
msgid "unknown"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:441
#, kde-format
msgid "You must specify both a subject and a description before the report can be sent."
msgstr ""
#. +> trunk5
#: kbugreport.cpp:450
#, kde-format
msgid ""
"<p>You chose the severity <b>Critical</b>. Please note that this severity is intended only for bugs that:</p>"
"<ul>"
"<li>break unrelated software on the system (or the whole system)</li>"
"<li>cause serious data loss</li>"
"<li>introduce a security hole on the system where the affected package is installed</li>"
"</ul>"
"\n"
"<p>Does the bug you are reporting cause any of the above damage? If it does not, please select a lower severity. Thank you.</p>"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:462
#, kde-format
msgid ""
"<p>You chose the severity <b>Grave</b>. Please note that this severity is intended only for bugs that:</p>"
"<ul>"
"<li>make the package in question unusable or mostly so</li>"
"<li>cause data loss</li>"
"<li>introduce a security hole allowing access to the accounts of users who use the affected package</li>"
"</ul>"
"\n"
"<p>Does the bug you are reporting cause any of the above damage? If it does not, please select a lower severity. Thank you.</p>"
msgstr ""
#. +> trunk5
#: kbugreport.cpp:476
#, kde-format
msgid ""
"Unable to send the bug report.\n"
"Please submit a bug report manually....\n"
"See https://bugs.kde.org/ for instructions."
msgstr ""
#. +> trunk5
#: kbugreport.cpp:484
#, kde-format
msgid "Bug report sent, thank you for your input."
msgid "Here you can see a list of key bindings, i.e. associations between actions (e.g. 'Copy') shown in the left column and keys or combination of keys (e.g. Ctrl+V) shown in the right column."
msgid "This is the main application language which will be used first, before any other languages."
msgstr ""
#. +> trunk5
#: kswitchlanguagedialog_p.cpp:423
#, kde-format
msgid "This is the language which will be used if any previous languages do not contain a proper translation."
msgstr ""
#. +> trunk5
#: ktoolbar.cpp:309
#, kde-format
msgctxt "@title:menu"
msgid "Show Text"
msgstr ""
#. +> trunk5
#: ktoolbar.cpp:312
#, kde-format
msgctxt "@title:menu"
msgid "Toolbar Settings"
msgstr ""
#. +> trunk5
#: ktoolbar.cpp:314
#, kde-format
msgctxt "Toolbar orientation"
msgid "Orientation"
msgstr ""
#. +> trunk5
#: ktoolbar.cpp:316
#, kde-format
msgctxt "toolbar position string"
msgid "Top"
msgstr ""
#. +> trunk5
#: ktoolbar.cpp:318
#, kde-format
msgctxt "toolbar position string"
msgid "Left"
msgstr ""
#. +> trunk5
#: ktoolbar.cpp:319
#, kde-format
msgctxt "toolbar position string"
msgid "Right"
msgstr ""
#. +> trunk5
#: ktoolbar.cpp:320
#, kde-format
msgctxt "toolbar position string"
msgid "Bottom"
msgstr ""
#. +> trunk5
#: ktoolbar.cpp:328
#, kde-format
msgid "Text Position"
msgstr ""
#. +> trunk5
#: ktoolbar.cpp:330
#, kde-format
msgid "Icons Only"
msgstr ""
#. +> trunk5
#: ktoolbar.cpp:331
#, kde-format
msgid "Text Only"
msgstr ""
#. +> trunk5
#: ktoolbar.cpp:332
#, kde-format
msgid "Text Alongside Icons"
msgstr ""
#. +> trunk5
#: ktoolbar.cpp:333
#, kde-format
msgid "Text Under Icons"
msgstr ""
#. +> trunk5
#: ktoolbar.cpp:341
#, kde-format
msgid "Icon Size"
msgstr ""
#. +> trunk5
#: ktoolbar.cpp:343
#, kde-format
msgctxt "@item:inmenu Icon size"
msgid "Default"
msgstr ""
#. +> trunk5
#: ktoolbar.cpp:360 ktoolbar.cpp:381
#, kde-format
msgid "Small (%1x%2)"
msgstr ""
#. +> trunk5
#: ktoolbar.cpp:362 ktoolbar.cpp:383
#, kde-format
msgid "Medium (%1x%2)"
msgstr ""
#. +> trunk5
#: ktoolbar.cpp:364 ktoolbar.cpp:385
#, kde-format
msgid "Large (%1x%2)"
msgstr ""
#. +> trunk5
#: ktoolbar.cpp:366 ktoolbar.cpp:387
#, kde-format
msgid "Huge (%1x%2)"
msgstr ""
#. +> trunk5
#: ktoolbar.cpp:409
#, kde-format
msgid "Lock Toolbar Positions"
msgstr ""
#. +> trunk5
#: ktoolbarhandler.cpp:103
#, kde-format
msgid "Toolbars Shown"
msgstr ""
#. +> trunk5
#: kundoactions.cpp:41
#, kde-format
msgid "Redo"
msgstr ""
#. +> trunk5
#: kundoactions.cpp:60
#, kde-format
msgid "Undo"
msgstr ""
#. +> trunk5
-#: kxmlguibuilder.cpp:190 kxmlguibuilder.cpp:354
+#: kxmlguibuilder.cpp:192 kxmlguibuilder.cpp:363
#, kde-format
msgid "No text"
msgstr ""
#. +> trunk5
#: kxmlguiwindow.cpp:437
#, kde-format
msgid "There are two actions (%1, %2) that want to use the same shortcut (%3). This is most probably a bug. Please report it in <a href='https://bugs.kde.org'>bugs.kde.org</a>"
msgid "Hostname on which the application is running"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: helpers/killer/killer.cpp:53
#, kde-format
msgid "hostname"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: helpers/killer/killer.cpp:55
#, kde-format
msgid "Caption of the window to be terminated"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: helpers/killer/killer.cpp:55
#, kde-format
msgid "caption"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: helpers/killer/killer.cpp:57
#, kde-format
msgid "Name of the application to be terminated"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: helpers/killer/killer.cpp:57
#, kde-format
msgid "name"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: helpers/killer/killer.cpp:59
#, kde-format
msgid "ID of resource belonging to the application"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: helpers/killer/killer.cpp:59
#, kde-format
msgid "id"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: helpers/killer/killer.cpp:61
#, kde-format
msgid "Time of user action causing termination"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: helpers/killer/killer.cpp:61
#, kde-format
msgid "time"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: helpers/killer/killer.cpp:63
#, kde-format
msgid "KWin helper utility"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: helpers/killer/killer.cpp:87
#, kde-format
msgid "This helper utility is not supposed to be called directly."
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: helpers/killer/killer.cpp:97
#, kde-format
msgctxt "@info"
msgid "<b>Application \"%1\" is not responding</b>"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: helpers/killer/killer.cpp:99
#, kde-kuit-format
msgctxt "@info"
msgid "<p>You tried to close window \"%1\" from application \"%2\" (Process ID: %3) but the application is not responding.</p>"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: helpers/killer/killer.cpp:101
#, kde-kuit-format
msgctxt "@info"
msgid "<p>You tried to close window \"%1\" from application \"%2\" (Process ID: %3), running on host \"%4\", but the application is not responding.</p>"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: helpers/killer/killer.cpp:104
#, kde-kuit-format
msgctxt "@info"
msgid ""
"<p>Do you want to terminate this application?</p>"
"<p><warning>Terminating the application will close all of its child windows. Any unsaved data will be lost.</warning></p>"
msgctxt "Special entry in alt+tab list for minimizing all windows"
msgid "Show Desktop"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: tabbox/tabbox.cpp:541
#, kde-format
msgid "Walk Through Windows"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: tabbox/tabbox.cpp:542
#, kde-format
msgid "Walk Through Windows (Reverse)"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: tabbox/tabbox.cpp:543
#, kde-format
msgid "Walk Through Windows Alternative"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: tabbox/tabbox.cpp:544
#, kde-format
msgid "Walk Through Windows Alternative (Reverse)"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: tabbox/tabbox.cpp:545
#, kde-format
msgid "Walk Through Windows of Current Application"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: tabbox/tabbox.cpp:546
#, kde-format
msgid "Walk Through Windows of Current Application (Reverse)"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: tabbox/tabbox.cpp:547
#, kde-format
msgid "Walk Through Windows of Current Application Alternative"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: tabbox/tabbox.cpp:548
#, kde-format
msgid "Walk Through Windows of Current Application Alternative (Reverse)"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: tabbox/tabbox.cpp:549
#, kde-format
msgid "Walk Through Desktops"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: tabbox/tabbox.cpp:550
#, kde-format
msgid "Walk Through Desktops (Reverse)"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: tabbox/tabbox.cpp:551
#, kde-format
msgid "Walk Through Desktop List"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: tabbox/tabbox.cpp:552
#, kde-format
msgid "Walk Through Desktop List (Reverse)"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: tabbox/tabboxhandler.cpp:284
#, kde-format
msgid ""
"The Window Switcher installation is broken, resources are missing.\n"
"Contact your distribution about this."
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:205
#, kde-format
msgid ""
"You have selected to show a window without its border.\n"
"Without the border, you will not be able to enable the border again using the mouse: use the window operations menu instead, activated using the %1 keyboard shortcut."
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:213
#, kde-format
msgid ""
"You have selected to show a window in fullscreen mode.\n"
"If the application itself does not have an option to turn the fullscreen mode off you will not be able to disable it again using the mouse: use the window operations menu instead, activated using the %1 keyboard shortcut."
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:276
#, kde-format
msgid "&Move"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:281
#, kde-format
msgid "&Resize"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:285
#, kde-format
msgid "Keep &Above Others"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:291
#, kde-format
msgid "Keep &Below Others"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:297
#, kde-format
msgid "&Fullscreen"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:303
#, kde-format
msgid "&Shade"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:308
#, kde-format
msgid "&No Border"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:315
#, kde-format
msgid "Window Short&cut..."
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:320
#, kde-format
msgid "Special &Window Settings..."
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:325
#, kde-format
msgid "S&pecial Application Settings..."
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:333
#, kde-format
msgctxt "Entry in context menu of window decoration to open the configuration module of KWin"
msgid "Window Manager S&ettings..."
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:363
#, kde-format
msgid "Mi&nimize"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:367
#, kde-format
msgid "Ma&ximize"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:376
#, kde-format
msgid "&Untab"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:380
#, kde-format
msgid "Close Entire &Group"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:391
#, kde-format
msgid "&More Actions"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:395
#, kde-format
msgid "&Close"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:472
#, kde-format
msgid "&Extensions"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:530
#, kde-format
msgctxt "Switch to tab -> Previous"
msgid "Previous"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:531
#, kde-format
msgctxt "Switch to tab -> Next"
msgid "Next"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:572
#, kde-format
msgctxt "There's no window available to be attached as tab to this one"
msgid "None available"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:581
#, kde-format
msgid "Switch to Tab"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:592
#, kde-format
msgid "&Attach as tab to"
msgstr ""
#. +> trunk5 stable5
#: useractions.cpp:618
#, kde-format
msgid "&Desktops"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:631
#, kde-format
msgid "Move To &Desktop"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:648
#, kde-format
msgid "Move To &Screen"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:663
#, kde-format
msgid "Ac&tivities"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:675 useractions.cpp:717
#, kde-format
msgid "&All Desktops"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:702 useractions.cpp:754
#, kde-format
msgctxt "Create a new desktop and move there the window"
msgid "&New Desktop"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:774
#, kde-format
msgctxt "@item:inmenu List of all Screens to send a window to. First argument is a number, second the output identifier. E.g. Screen 1 (HDMI1)"
msgid "Screen &%1 (%2)"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:795
#, kde-format
msgid "&All Activities"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:1038
#, kde-format
msgctxt "'%1' is a keyboard shortcut like 'ctrl+w'"
msgid "<b>%1</b> is already in use"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:1040
#, kde-format
msgctxt "keyboard shortcut '%1' is used by action '%2' in application '%3'"
msgid "<b>%1</b> is used by %2 in %3"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:1172
#, kde-format
msgid "Activate Window (%1)"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: useractions.cpp:1377
#, kde-format
msgid ""
"The window manager is configured to consider the screen with the mouse on it as active one.\n"
"Therefore it is not possible to switch to a screen explicitly."
msgid "Here you can configure your default file manager. The entries in the K menu and all KDE applications in which you can open folders will use this file manager."
msgid "This service allows you to configure your default email client. All KDE applications which need access to an email client application should honor this setting."
msgid "This service allows you to configure your default terminal emulator. All KDE applications which invoke a terminal emulator application should honor this setting."
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: kcms/componentchooser/EXAMPLE.desktop:1
msgctxt "Name"
msgid "A nice name you have chosen for your interface"
msgstr ""
#. +> trunk5 stable5 plasma5lts
#: kcms/componentchooser/EXAMPLE.desktop:89
msgctxt "Comment"
msgid "A helpful description of the interface for the top right info box"
msgid "<b>Note</b>: the information here is used only for annotations. The information is saved in annotated documents, and so will be transmitted together with the document."
msgid "Keeps used memory as low as possible. Do not reuse anything. (For systems with low memory.)"
msgstr ""
#. +> trunk5 stable5
#: conf/dlgperformance.cpp:58
#, kde-format
msgid "A good compromise between memory usage and speed gain. Preload next page and boost searches. (For systems with 2GB of memory, typically.)"
msgstr ""
#. +> trunk5 stable5
#: conf/dlgperformance.cpp:61
#, kde-format
msgid "Keeps everything in memory. Preload next pages. Boost searches. (For systems with more than 4GB of memory.)"
msgstr ""
#. +> trunk5 stable5
#: conf/dlgperformance.cpp:65
#, kde-format, no-c-format
msgid "Loads and keeps everything in memory. Preload all pages. (Will use at maximum 50% of your total memory or your free memory, whatever is bigger.)"
"<qt>More than one backend found for the MIME type:<br />"
"<b>%1</b> (%2).<br />"
"<br />"
"Please select which one to use:</qt>"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:181
#, kde-format
msgctxt "paper type and orientation (eg: Portrait A4)"
msgid "Portrait %1"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:183
#, kde-format
msgctxt "paper type and orientation (eg: Portrait A4)"
msgid "Landscape %1"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:210
#, kde-format
msgctxt "%1 is width, %2 is height, %3 is paper size name"
msgid "%1 x %2 in (%3)"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:214
#, kde-format
msgctxt "%1 is width, %2 is height, %3 is paper size name"
msgid "%1 x %2 mm (%3)"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:1656
#, kde-format
msgid "Continuing search from beginning"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:1661
#, kde-format
msgid "Continuing search from bottom"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:2440
#, kde-format
msgid "Can not find a plugin which is able to handle the document being passed."
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:3571
#, kde-format
msgctxt "remove a collection of annotations from the page"
msgid "remove annotations"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:4148 core/document.cpp:4156
#, kde-format
msgid "The document is trying to execute an external application and, for your safety, Okular does not allow that."
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:4169
#, kde-format
msgid "No application found for opening file of mimetype %1."
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:4427
#, kde-format
msgid "Could not open a temporary file"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:4429
#, kde-format
msgid "Print conversion failed"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:4431
#, kde-format
msgid "Printing process crashed"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:4433
#, kde-format
msgid "Printing process could not start"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:4435
#, kde-format
msgid "Printing to file failed"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:4437
#, kde-format
msgid "Printer was in invalid state"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:4439
#, kde-format
msgid "Unable to find file to print"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:4441
#, kde-format
msgid "There was no file to print"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:4443
#, kde-format
msgid "Could not find a suitable binary for printing. Make sure CUPS lpr binary is available"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:4445
#, kde-format
msgid "The page print size is invalid"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:5104 part.cpp:1109
#, kde-format
msgid "Could not open '%1'. File does not exist"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:5585
#, kde-format
msgid "Title"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:5588
#, kde-format
msgid "Subject"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:5591
#, kde-format
msgid "Description"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:5594
#, kde-format
msgid "Author"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:5597
#, kde-format
msgid "Creator"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:5600
#, kde-format
msgid "Producer"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:5603
#, kde-format
msgid "Copyright"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:5606
#, kde-format
msgid "Pages"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:5609
#, kde-format
msgid "Created"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:5612
#, kde-format
msgid "Modified"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:5615
#, kde-format
msgid "Mime Type"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:5618
#, kde-format
msgid "Category"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:5621
#, kde-format
msgid "Keywords"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:5624
#, kde-format
msgid "File Path"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:5627
#, kde-format
msgid "File Size"
msgstr ""
#. +> trunk5 stable5
#: core/document.cpp:5630
#, kde-format
msgid "Page Size"
msgstr ""
#. +> trunk5 stable5
#: core/documentcommands.cpp:69
#, kde-format
msgctxt "Add an annotation to the page"
msgid "add annotation"
msgstr ""
#. +> trunk5 stable5
#: core/documentcommands.cpp:116
#, kde-format
msgctxt "Remove an annotation from the page"
msgid "remove annotation"
msgstr ""
#. +> trunk5 stable5
#: core/documentcommands.cpp:167
#, kde-format
msgctxt "Modify an annotation's internal properties (Color, line-width, etc.)"
msgid "modify annotation properties"
msgstr ""
#. +> trunk5 stable5
#: core/documentcommands.cpp:205
#, kde-format
msgctxt "Translate an annotation's position on the page"
msgid "translate annotation"
msgstr ""
#. +> trunk5 stable5
#: core/documentcommands.cpp:282
#, kde-format
msgctxt "Change an annotation's size"
msgid "adjust annotation"
msgstr ""
#. +> trunk5 stable5
#: core/documentcommands.cpp:355
#, kde-format
msgctxt "Generic text edit command"
msgid "edit text"
msgstr ""
#. +> trunk5 stable5
#: core/documentcommands.cpp:444
#, kde-format
msgctxt "Edit an annotation's text contents"
msgid "edit annotation contents"
msgstr ""
#. +> trunk5 stable5
#: core/documentcommands.cpp:502
#, kde-format
msgctxt "Edit an form's text contents"
msgid "edit form contents"
msgstr ""
#. +> trunk5 stable5
#: core/documentcommands.cpp:559
#, kde-format
msgctxt "Edit a list form's choices"
msgid "edit list form choices"
msgstr ""
#. +> trunk5 stable5
#: core/documentcommands.cpp:601
#, kde-format
msgctxt "Edit a combo form's selection"
msgid "edit combo form selection"
msgstr ""
#. +> trunk5 stable5
#: core/documentcommands.cpp:690
#, kde-format
msgctxt "Edit the state of a group of form buttons"
msgid "edit form button states"
msgstr ""
#. +> trunk5 stable5
#: core/generator.cpp:771
#, kde-format
msgid "Plain &Text..."
msgstr ""
#. +> trunk5 stable5
#: core/generator.cpp:774
#, kde-format
msgid "PDF"
msgstr ""
#. +> trunk5 stable5
#: core/generator.cpp:779
#, kde-format
msgctxt "This is the document format"
msgid "OpenDocument Text"
msgstr ""
#. +> trunk5 stable5
#: core/generator.cpp:783
#, kde-format
msgctxt "This is the document format"
msgid "HTML"
msgstr ""
#. +> trunk5 stable5
#: core/printoptionswidget.cpp:22
#, kde-format
msgid "Print Options"
msgstr ""
#. +> trunk5 stable5
#: core/printoptionswidget.cpp:26
#, kde-format
msgid "Fit to printable area"
msgstr ""
#. +> trunk5 stable5
#: core/printoptionswidget.cpp:27
#, kde-format
msgid "Fit to full page"
msgstr ""
#. +> trunk5 stable5
#: core/printoptionswidget.cpp:28
#, kde-format
msgid "Scale mode:"
msgstr ""
#. +> trunk5 stable5
#: core/sourcereference.cpp:102
#, kde-format
msgctxt "'source' is a source file"
msgid "Source: %1"
msgstr ""
#. +> trunk5 stable5
#: core/textdocumentsettings.cpp:40
#, kde-format
msgid "&Default Font:"
msgstr ""
#. i18n: ectx: Menu (file)
#. +> trunk5 stable5
#: part-viewermode.rc:5 part.rc:4
#, kde-format
msgid "&File"
msgstr ""
#. i18n: ectx: Menu (settings)
#. +> trunk5 stable5
#: part-viewermode.rc:9 part.rc:88
#, kde-format
msgid "&Settings"
msgstr ""
#. i18n: ectx: Menu (help)
#. +> trunk5 stable5
#: part-viewermode.rc:14 part.rc:94
#, kde-format
msgid "&Help"
msgstr ""
#. i18n: ectx: Menu (view_orientation)
#. +> trunk5 stable5
#: part-viewermode.rc:32 part.rc:44
#, kde-format
msgid "&Orientation"
msgstr ""
#. i18n: ectx: Menu (bookmarks)
#. i18n: ectx: Menu (okular_bookmarks)
#. +> trunk5 stable5
#: part-viewermode.rc:51 part.rc:66
#, kde-format
msgid "&Bookmarks"
msgstr ""
#. i18n: ectx: ToolBar (OkularViewerToolBar)
#. +> trunk5 stable5
#: part-viewermode.rc:64
#, kde-format
msgid "Viewer Toolbar"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:426
#, kde-format
msgid "Contents"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:432
#, kde-format
msgid "Layers"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:444
#, kde-format
msgid "Thumbnails"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:450
#, kde-format
msgid "Reviews"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:455
#, kde-format
msgid "Bookmarks"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:461
#, kde-format
msgid "Signatures"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:495
#, kde-format
msgid ""
"This document contains annotations or form data that were saved internally by a previous Okular version. Internal storage is <b>no longer supported</b>.<br/>"
"Please save to a file in order to move them if you want to continue to edit the document."
msgstr ""
#. +> trunk5 stable5
#: part.cpp:501
#, kde-format
msgid "This document has embedded files. <a href=\"okular:/embeddedfiles\">Click here to see them</a> or go to File -> Embedded Files."
msgstr ""
#. +> trunk5 stable5
#: part.cpp:662
#, kde-format
msgctxt "Previous page"
msgid "Previous"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:663
#, kde-format
msgid "Go back to the Previous Page"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:664
#, kde-format
msgid "Moves to the previous page of the document"
msgid "The program \"ps2pdf\" was not found, so Okular can not import PS files using it."
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1312
#, kde-format
msgid "ps2pdf not found"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1317
#, kde-format
msgid "PostScript files (%1)"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1333
#, kde-format
msgid "Importing PS file as PDF (this may take a while)..."
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1472
#, kde-format
msgid "Please enter the password to read the document:"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1474
#, kde-format
msgid "Incorrect password. Try again:"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1479
#, kde-format
msgid "Document Password"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1591
#, kde-format
msgid "This document has XFA forms, which are currently <b>unsupported</b>."
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1599
#, kde-format
msgid "This document has forms. Click on the button to interact with them, or use View -> Show Forms."
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1612
#, kde-format
msgid "All editing and interactive features for this document are disabled. Please save a copy and reopen to edit this document."
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1616
#, kde-format
msgid "This document is digitally signed."
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1700
#, kde-format
msgid ""
"This document wants to be shown full screen.\n"
"Leave normal mode and enter presentation mode?"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1702
#, kde-format
msgid "Request to Change Viewing Mode"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1703
#, kde-format
msgid "Enter Presentation Mode"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1704
#, kde-format
msgid "Deny Request"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1783
#, kde-format
msgid "Could not open %1"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1803
#, kde-format
msgid ""
"There are unsaved changes, and the file '%1' has been modified by another program. Your changes will be lost, because the file can no longer be saved.<br>"
"Do you want to continue reloading the file?"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1804 part.cpp:1812 part.cpp:2593
#, kde-format
msgid "File Changed"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1805
#, kde-format
msgid "Continue Reloading"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1806
#, kde-format
msgid "Abort Reloading"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1811
#, kde-format
msgid ""
"There are unsaved changes, and the file '%1' has been modified by another program. Your changes will be lost, because the file can no longer be saved.<br>"
"Do you want to continue closing the file?"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1813
#, kde-format
msgid "Continue Closing"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1814
#, kde-format
msgid "Abort Closing"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1820
#, kde-format
msgid "Do you want to save your changes to \"%1\" or discard them?"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1821
#, kde-format
msgid "Close Document"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1940
#, kde-format
msgid "This link points to a close document action that does not work when using the embedded viewer."
msgstr ""
#. +> trunk5 stable5
#: part.cpp:1946
#, kde-format
msgid "This link points to a quit application action that does not work when using the embedded viewer."
msgid "File could not be saved in '%1'. Try to save it to another location."
msgstr ""
#. +> trunk5 stable5
#: part.cpp:2668
#, kde-format
msgid "Filled form contents"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:2669
#, kde-format
msgid "User annotations"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:2675
#, kde-format
msgid "You are about to save changes, but the current file format does not support saving the following elements. Please use the <i>Okular document archive</i> format to preserve them."
msgstr ""
#. +> trunk5 stable5
#: part.cpp:2678 part.cpp:2701
#, kde-format
msgid "Warning"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:2679 part.cpp:2702
#, kde-format
msgid "Save as Okular document archive..."
msgstr ""
#. +> trunk5 stable5
#: part.cpp:2694
#, kde-format
msgid "You are about to save changes, but the current file format does not support saving the following elements. Please use the <i>Okular document archive</i> format to preserve them. Click <i>Continue</i> to save the document and discard these elements."
msgstr ""
#. +> trunk5 stable5
#: part.cpp:2695
#, kde-format
msgid "You are about to save changes, but the current file format does not support saving the following elements. Please use the <i>Okular document archive</i> format to preserve them. Click <i>Continue</i> to save, but you will lose these elements as well as the undo/redo history."
msgstr ""
#. +> trunk5 stable5
#: part.cpp:2697
#, kde-format
msgid "Continue"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:2698
#, kde-format
msgid "Continue losing changes"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:2728
#, kde-format
msgid "File could not be saved in '%1'. %2"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:2772
#, kde-format
msgid ""
"Okular cannot copy %1 to the specified location.\n"
"\n"
"The document does not exist anymore."
msgstr ""
#. +> trunk5 stable5
#: part.cpp:2806
#, kde-format
msgid "File could not be saved in '%1'. Error: '%2'. Try to save it to another location."
msgstr ""
#. +> trunk5 stable5
#: part.cpp:3087
#, kde-format
msgid "Expand whole section"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:3089
#, kde-format
msgid "Collapse whole section"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:3091
#, kde-format
msgid "Expand all"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:3093
#, kde-format
msgid "Collapse all"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:3103 ui/annotationmodel.cpp:334
#, kde-format
msgid "Page %1"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:3108
#, kde-format
msgid "Add Bookmark"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:3118
#, kde-format
msgid "Tools"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:3330
#, kde-format
msgctxt "@title:window"
msgid "Print"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:3407
#, kde-format
msgid "Printing this document is not allowed."
msgstr ""
#. +> trunk5 stable5
#: part.cpp:3416
#, kde-format
msgid "Could not print the document. Unknown error. Please report to bugs.kde.org"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:3420
#, kde-format
msgid "Could not print the document. Detailed error is \"%1\". Please report to bugs.kde.org"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:3507
#, kde-format
msgid "Go to the place you were before"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:3511
#, kde-format
msgid "Go to the place you were after"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:3538
#, kde-format
msgid "<qt><strong>File Error!</strong> Could not create temporary file <nobr><strong>%1</strong></nobr>.</qt>"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:3551
#, kde-format
msgid "<qt><strong>File Error!</strong> Could not open the file <nobr><strong>%1</strong></nobr> for uncompression. The file will not be loaded.</qt>"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:3554
#, kde-format
msgid "<qt>This error typically occurs if you do not have enough permissions to read the file. You can check ownership and permissions if you right-click on the file in the Dolphin file manager, then choose the 'Properties' option, and select 'Permissions' tab in the opened window.</qt>"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:3578
#, kde-format
msgid "<qt><strong>File Error!</strong> Could not uncompress the file <nobr><strong>%1</strong></nobr>. The file will not be loaded.</qt>"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:3581
#, kde-format
msgid "<qt>This error typically occurs if the file is corrupt. If you want to be sure, try to decompress the file manually using command-line tools.</qt>"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:3610
#, kde-format
msgid "No Bookmarks"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:3684
#, kde-format
msgid "There was a problem sharing the document: %1"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:3685 part.cpp:3692
#, kde-format
msgid "Share"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:3689
#, kde-format
msgid "Document shared successfully"
msgstr ""
#. +> trunk5 stable5
#: part.cpp:3691
#, kde-format
msgid "You can find the shared document at: <a href=\"%1\">%1</a>"
msgstr ""
#. i18n: ectx: Menu (edit)
#. +> trunk5 stable5
#: part.rc:18
#, kde-format
msgid "&Edit"
msgstr ""
#. i18n: ectx: Menu (view)
#. +> trunk5 stable5
#: part.rc:31
#, kde-format
msgid "&View"
msgstr ""
#. i18n: ectx: Menu (go)
#. +> trunk5 stable5
#: part.rc:54
#, kde-format
msgid "&Go"
msgstr ""
#. i18n: ectx: Menu (tools)
#. +> trunk5 stable5
#: part.rc:74
#, kde-format
msgid "&Tools"
msgstr ""
#. i18n: ectx: ToolBar (mainToolBar)
#. +> trunk5 stable5
#: part.rc:98 shell/shell.rc:22
#, kde-format
msgid "Main Toolbar"
msgstr ""
#. +> trunk5 stable5
#: shell/main.cpp:54
#, kde-format
msgid "Page of the document to be shown"
msgstr ""
#. +> trunk5 stable5
#: shell/main.cpp:55
#, kde-format
msgid "Start the document in presentation mode"
msgstr ""
#. +> trunk5 stable5
#: shell/main.cpp:56
#, kde-format
msgid "Start with print dialog"
msgstr ""
#. +> trunk5 stable5
#: shell/main.cpp:57
#, kde-format
msgid "Start with print dialog and exit after printing"
msgstr ""
#. +> trunk5 stable5
#: shell/main.cpp:58
#, kde-format
msgid "\"Unique instance\" control"
msgstr ""
#. +> trunk5 stable5
#: shell/main.cpp:59
#, kde-format
msgid "Not raise window"
msgstr ""
#. +> trunk5 stable5
#: shell/main.cpp:60
#, kde-format
msgid "Find a string on the text"
msgstr ""
#. +> trunk5 stable5
#: shell/main.cpp:61
#, kde-format
msgid "Documents to open. Specify '-' to read from stdin."
msgstr ""
#. +> trunk5 stable5
#: shell/okular_main.cpp:127
#, kde-format
msgid "Error: Can't open more than one document with the --unique switch"
msgstr ""
#. +> trunk5 stable5
#: shell/okular_main.cpp:134
#, kde-format
msgid "Error: Can't open more than one document with the --presentation switch"
msgstr ""
#. +> trunk5 stable5
#: shell/okular_main.cpp:141
#, kde-format
msgid "Error: Can't open more than one document with the --print switch"
msgstr ""
#. +> trunk5 stable5
#: shell/okular_main.cpp:148
#, kde-format
msgid "Error: Can't open more than one document with the --page switch"
msgstr ""
#. +> trunk5 stable5
#: shell/okular_main.cpp:155
#, kde-format
msgid "Error: Can't open more than one document with the --find switch"
msgstr ""
#. +> trunk5 stable5
#: shell/shell.cpp:92
#, kde-format
msgid "Unable to find the Okular component: %1"
msgstr ""
#. +> trunk5 stable5
#: shell/shell.cpp:135
#, kde-format
msgid "There is already a unique Okular instance running. This instance won't be the unique one."
msgstr ""
#. +> trunk5 stable5
#: shell/shell.cpp:152
#, kde-format
msgid "Unable to find the Okular component."
msgstr ""
#. +> trunk5 stable5
#: shell/shell.cpp:341
#, kde-format
msgid ""
"Click to open a file\n"
"Click and hold to open a recent file"
msgstr ""
#. +> trunk5 stable5
#: shell/shell.cpp:342
#, kde-format
msgid "<b>Click</b> to open a file or <b>Click and hold</b> to select a recent file"
msgstr ""
#. +> trunk5 stable5
#: shell/shell.cpp:355
#, kde-format
msgid "Next Tab"
msgstr ""
#. +> trunk5 stable5
#: shell/shell.cpp:361
#, kde-format
msgid "Previous Tab"
msgstr ""
#. +> trunk5 stable5
#: shell/shell.cpp:471
#, kde-format
msgid "All files (*)"
msgstr ""
#. +> trunk5 stable5
#: shell/shell.cpp:472
#, kde-format
msgid "All supported files (%1)"
msgstr ""
#. +> trunk5 stable5
#: shell/shell.cpp:475
#, kde-format
msgid "Open Document"
msgstr ""
#. +> trunk5 stable5
#: shell/shell.cpp:580
#, kde-format
msgid "Confirm Close"
msgstr ""
#. +> trunk5 stable5
#: shell/shell.cpp:584
#, kde-format
msgid "Close Tabs"
msgstr ""
#. +> trunk5 stable5
#: shell/shell.cpp:590
#, kde-format
msgid "You are about to close %1 tabs. Are you sure you want to continue?"
msgstr ""
#. +> trunk5 stable5
#: shell/shell.cpp:591
#, kde-format
msgid "Warn me when I attempt to close multiple tabs"
msgid "There are two ways of exiting presentation mode, you can press either ESC key or click with the quit button that appears when placing the mouse in the top-right corner. Of course you can cycle windows (Alt+TAB by default)"
msgstr ""
#. +> trunk5 stable5
-#: ui/presentationwidget.cpp:1756
+#: ui/presentationwidget.cpp:1785
#, kde-format
msgctxt "Reason for inhibiting the screensaver activation, when the presentation mode is active"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. (itstool) path: component/name
#. +> trunk5 stable5
#: org.kde.kdenlive.appdata.xml:6
msgid "Kdenlive"
msgstr ""
#. (itstool) path: component/summary
#. +> trunk5 stable5
#: org.kde.kdenlive.appdata.xml:7
msgid "Video Editor"
msgstr ""
#. (itstool) path: description/p
#. +> trunk5 stable5
#: org.kde.kdenlive.appdata.xml:9
msgid "Kdenlive is a non linear video editor. It is based on the MLT framework and accepts many audio and video formats, allows you to add effects, transitions and render into the format of your choice."
msgid "At least one of the items in the clipboard could not be pasted because an item of the same name already exists. Any other items have been pasted."
"The views are stored in folders in the document. The same tree structure used in the document to store the views can be created in the selected base directory with this option.\n"
"Only the folders made by the user are created in the base directory (Logical view, use case view and so on are not created)."
"<p>The auto layout feature depends on layout generators provided by the GraphViz package, which is normally installed aside Umbrello by a package manager.</p>"
"\n"
"<p>Umbrello has build in support for detecting the install location of these layout generators. For cases where this dependency is not available or do not fit, a different installation path could be provided.</p>"
msgid "Turn on footer and page numbers when printing"
msgstr ""
-#. +> trunk5 stable5
+#. +> trunk5
#: dialogs/pages/generaloptionpage.cpp:82
#, kde-format
+msgid "Enable UML2 support"
+msgstr ""
+
+#. +> trunk5 stable5
+#: dialogs/pages/generaloptionpage.cpp:86
+#, kde-format
msgid "Create new association lines as:"
msgstr ""
#. +> trunk5 stable5
-#: dialogs/pages/generaloptionpage.cpp:98
+#: dialogs/pages/generaloptionpage.cpp:102
#, kde-format
msgid "Autosave"
msgstr ""
#. +> trunk5 stable5
-#: dialogs/pages/generaloptionpage.cpp:105
+#: dialogs/pages/generaloptionpage.cpp:109
#, kde-format
msgid "E&nable autosave"
msgstr ""
#. +> trunk5 stable5
-#: dialogs/pages/generaloptionpage.cpp:109
+#: dialogs/pages/generaloptionpage.cpp:113
#, kde-format
msgid "Select auto-save time interval (mins):"
msgstr ""
#. +> trunk5 stable5
-#: dialogs/pages/generaloptionpage.cpp:125
+#: dialogs/pages/generaloptionpage.cpp:129
#, kde-format
msgid "Set autosave suffix:"
msgstr ""
#. +> trunk5 stable5
-#: dialogs/pages/generaloptionpage.cpp:127
+#: dialogs/pages/generaloptionpage.cpp:131
#, kde-format
msgid ""
"<qt>"
"<p>The autosave file will be saved to ~/autosave.xmi if the autosaving occurs before you have manually saved the file.</p>"
"<p>If you have already saved it, the autosave file will be saved in the same folder as the file and will be named like the file's name, followed by the suffix specified.</p>"
"<p>If the suffix is equal to the suffix of the file you have saved, the autosave will overwrite your file automatically.</p>"
#. m_pProtectedRB = new QRadioButton(i18n("&Unique"), m_pScopeGB);
#. scopeLayout->addWidget(m_pProtectedRB);
#.
#. +> trunk5 stable5
#: dialogs/umlentityattributedialog.cpp:133
#, kde-format
msgid "&Indexed"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlentityattributedialog.cpp:171
#, kde-format
msgid "You have entered an invalid entity attribute name."
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlentityattributedialog.cpp:172
#, kde-format
msgid "Entity Attribute Name Invalid"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlentityattributedialog.cpp:179
#, kde-format
msgid "The entity attribute name you have chosen is already being used in this operation."
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlentityattributedialog.cpp:180
#, kde-format
msgid "Entity Attribute Name Not Unique"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlenumliteraldialog.cpp:34
#, kde-format
msgid "EnumLiteral Properties"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlenumliteraldialog.cpp:60
#, kde-format
msgctxt "literal name"
msgid "&Name:"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlenumliteraldialog.cpp:64
#, kde-format
msgid "&Value:"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlfiledialog.cpp:139
#, kde-format
msgid "All Supported Files"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlforeignkeyconstraintdialog.cpp:60
#, kde-format
msgid "Foreign Key Setup"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlforeignkeyconstraintdialog.cpp:208
#, kde-format
msgctxt "general page title"
msgid "General"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlforeignkeyconstraintdialog.cpp:211
#, kde-format
msgctxt "general group title"
msgid "General"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlforeignkeyconstraintdialog.cpp:219
#, kde-format
msgctxt "label for entering name"
msgid "Name"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlforeignkeyconstraintdialog.cpp:222
#, kde-format
msgid "Referenced Entity"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlforeignkeyconstraintdialog.cpp:228
#, kde-format
msgid "Actions"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlforeignkeyconstraintdialog.cpp:235
#, kde-format
msgid "On Update"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlforeignkeyconstraintdialog.cpp:241
#, kde-format
msgid "On Delete"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlforeignkeyconstraintdialog.cpp:273
#, kde-format
msgid "No Action"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlforeignkeyconstraintdialog.cpp:273
#, kde-format
msgid "Restrict"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlforeignkeyconstraintdialog.cpp:273
#, kde-format
msgid "Cascade"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlforeignkeyconstraintdialog.cpp:273
#, kde-format
msgid "Set Null"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlforeignkeyconstraintdialog.cpp:274
#, kde-format
msgid "Set Default"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlforeignkeyconstraintdialog.cpp:295
#, kde-format
msgid "Columns"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlforeignkeyconstraintdialog.cpp:302
#, kde-format
msgctxt "column header local"
msgid "Local"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlforeignkeyconstraintdialog.cpp:302
#, kde-format
msgctxt "column header referenced"
msgid "Referenced"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlforeignkeyconstraintdialog.cpp:309
#, kde-format
msgid "Local Column"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlforeignkeyconstraintdialog.cpp:315
#, kde-format
msgid "Referenced Column"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlforeignkeyconstraintdialog.cpp:323
#: dialogs/umlforeignkeyconstraintdialog.cpp:329
#: dialogs/umluniqueconstraintdialog.cpp:115
#: dialogs/umluniqueconstraintdialog.cpp:121
#, kde-format
msgid "&Add"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlforeignkeyconstraintdialog.cpp:405
#, kde-format
msgid "You are attempting to change the Referenced Entity of this ForeignKey Constraint. Any unapplied changes to the mappings between local and referenced entities will be lost. Are you sure you want to continue ?"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlinstanceattributedialog.cpp:26
#, kde-format
msgid "Object Attribute Properties"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlinstanceattributedialog.cpp:43
#, kde-format
msgid "Class Name Invalid"
msgstr ""
#. +> trunk5 stable5
#: dialogs/umlinstanceattributedialog.cpp:47
#, kde-format
msgid "You have entered an invalid attribute value."
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-06-25 09:20+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../KritaFAQ.rst:20
msgid "FAQ"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:20
msgid "Frequently Asked Questions"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:27
msgid "Krita FAQ"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:29
msgid "This page contains common problems people have with Krita. Note that we assume that you are using the latest version of Krita. Please verify that to make sure."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:31
msgid "Contents"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:34
msgid "General"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:36
msgid "General questions"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:39
msgid "What is Krita?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:41
msgid "This is our vision for the development of Krita:"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:43
msgid "Krita is a free and open source cross-platform application that offers an end-to-end solution for creating digital art files from scratch. Krita is optimized for frequent, prolonged and focused use. Explicitly supported fields of painting are illustrations, concept art, matte painting, textures, comics and animations. Developed together with users, Krita is an application that supports their actual needs and workflow. Krita supports open standards and interoperates with other applications."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:48
msgid "Is it possible to use Krita in my own language, not English?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:50
msgid "Krita should automatically use the system language. If that is not the case, please follow these steps:"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:52
msgid ":menuselection:`Settings --> Switch Application Language`. A small window will appear."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:53
msgid "Click :guilabel:`Primary language` and select your language."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:54
msgid "Click :guilabel:`OK` to close the window."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:55
msgid "Restart krita and it will be displayed in your selected language!"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:57
msgid "If this doesn't work, you might have to add a fall-back language as well. This is a bug, but we haven't found the solution yet."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:60
msgid "Does Krita have layer clip or clipping mask?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:62
msgid "Krita has no clipping mask, but it has a clipping feature called inherit alpha. Let's see :ref:`this page <clipping_masks_and_alpha_inheritance>` and learn how to do clipping in Krita!"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:67
msgid "Windows: OBS can't record the Krita OpenGL canvas"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:69
msgid "The possible workarounds for this is to do either of the following:"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:71
msgid "Turn off OpenGL in :menuselection:`Settings --> Configure Krita --> Display`."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:72
msgid "Or don't use the hardware accelerated mode (game recording mode) in OBS, thus capturing the whole desktop instead of attempting to capture only Krita."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:76
msgid "You might also be able to work around the problem by using the ANGLE renderer instead of native OpenGL."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:79
msgid "Where are the configuration files stored?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:81
msgid "These are stored at the following places for the following operating systems:"
msgid "The kritarc file is the configuration file. Krita does not store settings in the Windows registry."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:96
msgid "Resetting Krita configuration"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:98
msgid "You can reset the Krita configuration in following way:"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:100
msgid "For Krita 3.0 and later: Delete/rename the kritarc file, found here:"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:105
msgid ":file:`%LOCALAPPDATA%\\\\kritarc`"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:109
msgid "There can be two other files you might want to remove: kritaopenglrc and kritadisplayrc."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:112
msgid "If the configuration was causing a crash, don't delete the mentioned file, but instead rename and send it to us in order for us to figure what caused the crash."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:115
msgid "If you have installed Krita through the Windows store, the kritarc file will be in another location"
msgid "The random string depends on your installation."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:121
msgid "Windows users have a habit of uninstalling and reinstalling applications to solve problems. Unless the problem is that the installation was corrupted by a virus scanner or drive failure, that will NOT work. Uninstalling Krita then reinstalling replaces the bytes on your drive with exactly the same bytes that were there before. It doesn't reset anything, least of all Krita's settings."
msgid "Krita tells me it can't find some files and then closes, what should I do?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:139
msgid "Causes for this could be the following:"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:141
msgid "It might be that your download got corrupted and is missing files (common with bad wifi and bad internet connection in general), in that case, try to find a better internet connection before trying to download again. Krita should be around 80 to 100 MB in size when downloading."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:142
msgid "It might be that something went wrong during installation. Check whether your harddrive is full and reinstall Krita with at least 120 MB of empty space. If not, and the problem still occurs, there might be something odd going on with your device and it's recommended to find a computer expert to diagnose what is the problem."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:143
msgid "Some unzippers don't unpack our zipfiles correctly. The native ones on Windows, OSX and most Linux distributions should be just fine, and we recommend using them."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:144
msgid "You manually, using a file manager deleted or moved resources around, and thus Krita cannot find them anymore."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:147
msgid "What Graphics Cards does Krita support?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:149
msgid "Krita can use OpenGL to accelerate painting and canvas zooming, rotation and panning. Nvidia and recent Intel GPUs give the best results. Make sure your OpenGL drivers support OpenGL 3.2 as the minimum. AMD/ATI GPU’s are known to be troublesome, especially with the proprietary drivers on Linux. However, it works perfectly with the Radeon free driver on Linux for supported AMD GPU. Try to get a graphics card that can support OpenGL 3.2 or above for the best results, some examples:"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:153
msgid "Intel"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:154
msgid "Intel 3rd Generation HD Graphics, IvyBridge or Bay-Trail microarchitecture, released in 2012. Commonly available products: Celeron J1x00, N2x00, Celeron (G)1xx0, Pentium J2x00, N3500, Pentium (G)2xx0, Core i3/5/7-3xx0."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:155
msgid "AMD/ATI"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:156
msgid "Radeon HD 2000 family, TeraScale 1 microarchitecture, Released in 2007. Commonly available products: Radeon HD 2400 PRO, Radeon HD 2600 PRO, etc."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:158
msgid "Nvidia"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:158
msgid "GeForce 8 family, Tesla microarchitecture, released in 2006. Commonly available products: GeForce 8400 GS, GeForce 8800 GTS, 9800 GTX, GTS 250, etc."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:160
msgid "*For Krita 3.3 or later:* Krita on Windows can use Direct3D 11 for graphics acceleration (through ANGLE). This is enabled automatically on systems with an Intel GPU."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:163
msgid "I can't edit text from PSD files created by Photoshop"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:165
msgid "There is no text support for psd file yet. The text will appear rasterized and converted into a paint layer."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:168
msgid "How much memory does my image take?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:170
msgid "For simple images, its easy to calculate: you multiply width \\* height \\* channels \\* size of the channels (so, for a 1000×1000 16 bit integer rgba image: 1000 x 1000 x 4 x 2). You multiply this by the number of layers plus two (one for the image, one for the display). If you add masks, filter layers or clone layers, it gets more complicated."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:173
msgid "Why do I get a checkerboard pattern when I use the eraser?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:175
msgid "You’re probably used to Gimp or Photoshop. The default background or first layer in these applications doesn’t have an alpha channel by default. Thus, on their background layer, the eraser paints in the background color."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:177
msgid "In Krita, all layers have an alpha channel, if you want to paint in the background color, you should simply do it in a layer above the first one (Layer 1), that would prevent you from erasing the white background color, making the checkerboard visible. You get the same effect in, say, gimp, if you create new image, add an alpha channel and then use the eraser tool. Most Krita users will actually start a sketch in Krita by adding a new blank layer first before doing anything else. (The :kbd:`Ins` key is a useful shortcut here). That doesn’t use extra memory, since a blank layer or a layer with a default color just takes one pixel worth of memory."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:180
msgid "Windows: Can I use Krita with Sandboxie?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:182
msgid "No, this is not recommended. Sandboxie causes stuttering and freezes due to the way it intercepts calls for resources on disk."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:185
msgid "Windows: Krita cannot save"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:187
msgid "If the message is \"File not found. Check the file name and try again.\", you probably have Controlled Folder Access enabled."
msgid "Choose :menuselection:`Update & security --> Windows Defender`."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:191
msgid "Select :guilabel:`Open Windows Defender Security Center`."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:192
msgid "Select :guilabel:`Virus & threat protection`, and then choose :guilabel:`Virus & threat protection settings`."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:193
msgid "Under :guilabel:`Controlled folder access`, turn it on or off."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:195
msgid "You can also whitelist Krita, following `these instructions <https://docs.microsoft.com/en-us/windows/security/threat-protection/windows-defender-exploit-guard/customize-controlled-folders-exploit-guard#allow-specific-apps-to-make-changes-to-controlled-folders>`_."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:198
msgid "Can krita work with 8 bit (indexed) images?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:200
msgid "No. Krita has been designed from the ground up to use real colors, not indexed palettes. There are no plans to support indexed color images, although Krita can export to some indexed color image formats, such as GIF. However, it does not offer detailed control over pixel values."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:203
msgid "Krita crashes on Windows 7 on start-up"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:205
msgid "Starting with Krita 4.2.0, Krita uses version 5.12 of the Qt toolkit. This needs to have access to Direct3D 11 or OpenGL ES 2.0 or higher. You might need to install drivers appropriate to your GPU (Nvidia, AMD/ATI, Intel). This also makes it hard to run Krita in a virtual environment: in Virtual Box you need to install the guest addition in safe mode, and enable the experimental Direct3D support."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:209
msgid "How can I produce a backtrace on Windows?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:213
msgid ":ref:`Dr. Mingw debugger <dr_minw>`"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:215
msgid "If you experience a crash on Windows, and can reproduce the crash, the bug report will be much more valuable if you can create a backtrace. A backtrace is somewhat akin to an airplane's blackbox, in that they tell what set of instructions your computer was running when it was crashing (where the crash happened), making it very useful to figure out why the crash happened."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:217
msgid "The :ref:`Dr. Mingw debugger <dr_minw>` is bundled with Krita. Please visit the page :ref:`Dr. Mingw debugger <dr_minw>` for instructions on getting a backtrace with it."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:220
msgid "Where can I find older versions of Krita?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:222
msgid "All the older versions of Krita that are still available can be found here:"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:224
-msgid "`Very old builds <http://download.kde.org/Attic/krita>`_"
+msgid "`Very old builds <https://download.kde.org/Attic/krita/>`_"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:227
msgid "On Windows, the Krita User Interface is too small on my HiDPI screen"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:229
msgid "If you're using Windows, you can set the display scaling to 150% or 200%, and enable the experimental HiDPI support in the configurations:"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:231
msgid "On the menu, select :menuselection:`Settings --> Configure Krita`"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:232
msgid "On :guilabel:`General` page, switch to :guilabel:`Window` tab."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:233
msgid "Check :guilabel:`Enable Hi-DPI support`"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:234
msgid "Restart Krita"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:236
msgid "You can also change the toolbox icon size by right-clicking on the toolbox and selecting a size."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:239
msgid "Windows: In fullscreen mode, why is there a thin gap at the bottom of the window?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:241
msgid "When :ref:`Canvas Graphics Acceleration <display_settings>` is set to OpenGL, you may see a thin gap at the bottom of the window which you can see through. This is done deliberately to work around a bug causing menus and dropdowns to be unusable. If you find it distracting, you can consider changing the Renderer to Direct3D 11 which doesn't require this workaround."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:245
msgid "Tablets"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:248
msgid "What tablets does Krita support?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:250
msgid "Krita isn’t much fun without a pressure sensitive tablet. If the tablet has been properly configured, Krita should work out of the box."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:252
msgid "On Windows, you need to either install the Wintab drivers for your tablet, or enable the :guilabel:`Windows 8+ Pointer Input` option in Krita's settings."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:254
msgid "You can find a community curated list of tablets supported by krita :ref:`here <list_supported_tablets>`."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:256
msgid "If you're looking for information about tablets like the iPad or Android tablets, look :ref:`here <krita_android>`."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:260
msgid "What if your tablet is not recognized by Krita?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:262
msgid "First, check if you have installed drivers and the like. The :ref:`drawing_tablets` page has some explanations and descriptions of common issues. If none of those work, we would like to have a bug report at bugs.kde.org, with a tablet log. Here's how you make a tablet log:"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:264
msgid "You need to have something to output the log to. On 4.2 you can use the :ref:`log_viewer` docker for this. Just open the log viewer, and enable logging."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:268
-msgid "The log viewer got added to Krita in 4.2, so for older versions of Krita, you will need to either run Krita in the terminal if you have Linux or MacOS, or for Windows install `DebugView <http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx>`_ from the official Microsoft site, start DebugView and then start Krita."
+msgid "The log viewer got added to Krita in 4.2, so for older versions of Krita, you will need to either run Krita in the terminal if you have Linux or MacOS, or for Windows install `DebugView <https://docs.microsoft.com/en-us/sysinternals/downloads/debugview>`_ from the official Microsoft site, start DebugView and then start Krita."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:270
msgid "When using a terminal, make sure to enable 'unlimited scrollback'"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:272
-msgid "Press :kbd:`Ctrl + Shift + T`, you will see a message box telling the logging has started."
+msgid "Press the :kbd:`Ctrl + Shift + T` shortcut, you will see a message box telling the logging has started."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:273
msgid "Try to reproduce your problem, you will be able to see the log being created in the log viewer as you draw."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:274
msgid "Save the output from the log viewer into a txt file, and attach it to the bugreport."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:276
msgid "On Linux, it is also useful to have the following information:"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:278
msgid "``lsmod``"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:279
msgid "``xinput``"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:280
msgid "``xinput list-props`` (id can be fetched from the item 2)"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:282
msgid "However, in 100\\% of the cases where Windows users have reported that their tablet didn't work over the past five years, the problem has been either a buggy driver or a broken driver installation, but not a bug in Krita."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:286
msgid "How to fix a tablet offset on multiple screen setup on Windows"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:288
msgid "If you see that your tablet pointer has an offset when working with Krita canvas, it might be highly likely that Krita got an incorrect screen resolution from the system. That problem happens mostly when an external monitor is present and when either a monitor or a tablet was connected after the system booted."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:290
msgid "You can configure this by going to the :ref:`tablet_settings`."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:293
msgid "Microsoft Surface Pro and N-Trig"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:295
msgid "Krita 3.3.0 and later supports the Windows Pointer API (Windows Ink) natively. Your Surface Pro or other N-Trig enabled pen tablet should work out of the box with Krita after you enable Windows Ink in :menuselection:`Settings --> Configure Krita --> Tablet`."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:298
msgid "Tablet Pro and the Surface Pro"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:300
msgid "Unlike Wacom's Companion, the Surface line of tablets doesn't have working hardware buttons. Tablet Pro is a (non-free) utility that puts virtual buttons on screen. Krita 3.1 and above will have predefined shortcut profiles to work with Tablet Pro."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:302
-msgid "http://tabletpro.net/"
+msgid "https://tabletpro.com/"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:304
-msgid "See http://www.youtube.com/watch?v=WKXZgYqC3tI for instructions."
+msgid "See https://www.youtube.com/watch?v=WKXZgYqC3tI for instructions."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:307
msgid "Weird stuff happens on Windows, like ripples, rings, squiggles or poltergeists"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:309
msgid "Windows comes with a lot of settings to make it work with a pen. All these settings can be annoying. This tool can help you set the settings correctly when you're using a tablet:"
msgid "You might have to disable and enable the touch driver: go to the device manager. (Click the :guilabel:`Start` button and type device manager). Choose HID (User interface devices or something like that). Choose Intel(R) Precise Touch Device. Right click, Disable it. Right click, Enable it."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:319
msgid "Toolbox"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:322
msgid "Toolbox missing"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:324
msgid "You can reset the Workspace by pressing the right most button on the toolbar, the Workspace switcher, and click on a desired Workspace from the list."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:326
msgid "Or you can right-click on any docker title bar or open space in any toolbar, and select Toolbox. It's the first option."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:328
msgid "Also, you can check the :guilabel:`Settings` menu, it has got a lot of interesting stuff, then go to the Dockers menu and select :guilabel:`Toolbox`."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:331
msgid "Tool icons size is too big"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:333
msgid "Right click the toolbox to set the size."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:336
msgid "Krita can't get maximized"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:338
msgid "This happens when your dockers are placed in such a way that the window cannot be made less high. Rearrange your Workspace."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:341
msgid "Resources"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:344
msgid "Is there a way to restore a default brush that I have mistakenly overwritten with new settings to default?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:346
msgid "Yes. First go to the resource folder, which is in"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:351
msgid ":file:`user\\\\Appdata\\\\Roaming\\\\krita\\\\` or :file:`%APPDATA%\\\\Roaming\\\\krita\\\\`"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:353
msgid "OSX"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:355
msgid "You can easily do this by going into :menuselection:`Settings --> Manage Resources --> Open Resource Folder`."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:357
msgid "Then go into the *paintoppresets* folder and remove the latest created file that you made of your preset."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:360
msgid "After that go back to the resources folder and edit the blacklist file to remove the previous paintoppreset so Krita will load it. (Yes, it is a bit of a convoluted system, but at the least you don't lose your brushes)"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:366
msgid "How do I set favorite presets?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:368
msgid "Right-click a brush in the brush docker and assign it a tag. Then right-click on canvas to call popup palette, click the second right-most icon on the bottom-right of the palette, now you can pick the tag which contains the brush you assigned to it."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:371
msgid "Can Krita load Photoshop Brushes?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:373
msgid "Yes, but there are limitations. You can load ABR files by using the :guilabel:`Import` button in the :guilabel:`Predefined brush` tab in the brush editor. Since Adobe hasn’t disclosed the file format specification, we depend on reverse-engineering to figure out what to load, and currently that’s limited to basic features."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:376
msgid "Krita is slow"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:378
msgid "There is a myriad of reasons why this might be. Below is a short checklist."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:380
msgid "Something else is hogging the CPU or the memory: spotify and other electron apps have been known to do this."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:381
msgid "You are running Windows, and have 3rdparty security software like Sandboxie or Total Defender installed"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:382
msgid "You are working on images that are too big for your hardware (dimensions, channel depth or number of layers)"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:383
msgid "You do not have canvas acceleration enabled"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:385
msgid "Please also check `this page <https://phabricator.kde.org/T7199>`__"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:388
msgid "Slow start-up"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:390
msgid "You probably have too many resources installed. Deactivate some bundles under :menuselection:`Settings --> Manage Resources`."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:392
msgid "If you're using Windows with the portable zip file, Windows will scan all files every time you start Krita. That takes ages. Either use the installer or tell Microsoft Security Essentials to make an exception for Krita."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:395
msgid "Slow Brushes"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:397
msgid "Check if you accidentally turned on the stabilizer in the tool options docker."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:398
msgid "Try another scaling mode like trilinear. :menuselection:`Settings --> Configure Krita --> Display`."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:399
msgid "Try a lower channel depth than 16-bit."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:400
msgid "For NVidia, try a 16-bit floating point color space."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:401
msgid "For older AMD CPU's (Krita 2.9.10 and above), turn off the vector optimizations that are broken on AMD CPUs. :menuselection:`Settings --> Configure Krita --> Performance`. This isn't needed if you've got an AMD Threadripper™ CPU."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:402
msgid "It's a fairly memory hungry program, so 2GB of RAM is the minimum, and 4GB is the preferable minimum."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:403
msgid "Check that nothing else is hogging your CPU"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:404
msgid "Check that Instant Preview is enabled if you're using bigger brushes (but for very small brushes, make sure is disabled)."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:405
msgid "Set brush precision to 3 or auto."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:406
msgid "Use a larger value for brush spacing."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:407
msgid "If all of this fails, record a video and post a link and description on the Krita forum."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:408
msgid "Check whether OpenGL is enabled, and if it isn't, enable it. If it is enabled, and you are on Windows, try the Angle renderer. Or disable it."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:411
msgid "Slowdown after a been working for a while"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:413
msgid "Once you have the slowdown, click on the image-dimensions in the status bar. It will tell you how much RAM Krita is using, if it has hit the limit, or whether it has started swapping. Swapping can slow down a program a lot, so either work on smaller images or turn up the maximum amount of RAM in :menuselection:`Settings --> Configure Krita --> Performance --> Advanced Tab`."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:416
msgid "Animation"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:419
msgid "Why is my animation black in my video player"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:421
msgid "You did not render the animation using the \"baseline\" option and you are using the default Windows media player. Re-render using the baseline option or use a better video player application, like VLC. Check `this useful diagram <https://www.deviantart.com/tiarevlyn/art/T-Krita-4-1-7-rendering-issues-manual-783473428>`__"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:425
msgid "Tools"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:428
msgid "Why does the Transform Tool give a good result and then get blurry upon finalizing?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:430
msgid "The transform tool makes a preview that you edit before computing the finalized version. As this preview is using the screen resolution rather than the image resolution, it may feel that the result is blurry compared to the preview. See `this page <https://forum.kde.org/viewtopic.php?f=139&t=127269>`__ for more info."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:434
msgid "License, rights and the Krita Foundation"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:437
msgid "Who owns Krita?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:439
msgid "The Stichting Krita Foundation owns the Krita trademark. The copyright on the source code is owned by everyone who has worked on the source code."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:442
msgid "Who and what is Kiki?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:444
msgid "Kiki is a cybersquirrel. She’s our mascot and has been designed by Tyson Tan. We choose a squirrel when we discovered that ‘krita’ is the Albanian word for Squirrel."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:447
msgid "Why is Krita Free?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:449
-msgid "Krita is developed as `free software <http://www.gnu.org/>`_ within the KDE community. We believe that good tools should be available for all artists. You can also buy Krita on the Windows Store if you want to support Krita's development or want to have automatic updates to newer versions."
+msgid "Krita is developed as `free software <https://www.gnu.org/>`_ within the KDE community. We believe that good tools should be available for all artists. You can also buy Krita on the Windows Store if you want to support Krita's development or want to have automatic updates to newer versions."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:452
msgid "Can I use Krita commercially?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:454
msgid "Yes. What you create with Krita is your sole property. You own your work and can license your art however you want. Krita’s GPL license applies to Krita’s source code. Krita can be used commercially by artists for any purpose, by studios to make concept art, textures, or vfx, by game artists to work on commercial games, by scientists for research, and by students in educational institutions."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:456
msgid "If you modify Krita itself, and distribute the result, you have to share your modifications with us. Krita’s GNU GPL license guarantees you this freedom. Nobody is ever permitted to take it away."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:462
msgid "Can I get Krita for iPad? for Android?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:464
msgid "Not at this point in time."
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:467
msgid "Who translates Krita"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:469
-msgid "Krita is a `KDE application <http://www.kde.org/>`_ — and proud of it! That means that Krita’s translations are done by `KDE localization teams <http://i18n.kde.org/>`_. If you want to help out, join the team for your language! There is another way you can help out making Krita look good in any language, and that is join the development team and fix issues within the code that make Krita harder to translate."
+msgid "Krita is a `KDE application <https://www.kde.org/>`_ — and proud of it! That means that Krita’s translations are done by `KDE localization teams <https://l10n.kde.org/>`_. If you want to help out, join the team for your language! There is another way you can help out making Krita look good in any language, and that is join the development team and fix issues within the code that make Krita harder to translate."
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-06-05 08:53+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../contributors_manual/community.rst:1
msgid "Guide to the Krita community"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:10
msgid "community"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:10
msgid "communication"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:16
msgid "The Krita Community"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:18
msgid "Get in touch! Apart from the website at https://www.krita.org, the Krita project has three main communication channels:"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:20
msgid "Internet Relay Chat (IRC)"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:21
msgid "The mailing list"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:22
#: ../../contributors_manual/community.rst:86
msgid "Phabricator"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:24
msgid "While Krita developers and users are present on social media such as Twitter, Mastodon, Reddit, Google+, Tumblr or Facebook, those are not the place where we discuss new features, bugs, development or where we make plans for the future."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:26
msgid "There are also the:"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:28
msgid "bug tracker"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:29
msgid "development sprints"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:31
msgid "You’ll find that there are a number of people are almost always around: the core team."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:33
msgid "Boudewijn (irc: boud): project maintainer, lead developer. Works full-time on Krita. Manages the Krita Foundation, triages bugs, does social media and admin stuff. Boudewijn is also on Reddit as boudewijnrempt."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:34
msgid "Dmitry (irc: dmitryk_log): lead developer. Works full-time on Krita."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:35
msgid "Wolthera (irc: wolthera_laptop): developer, writes the manual and tutorials, triages bugs, helps people out"
msgid "Ben Cooksley (irc: bcooksley): KDE system administrator."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:41
msgid "Krita’s team spans the globe, but most development happens in Europe and Russia."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:43
msgid "Krita is part of the larger KDE community. The KDE® Community is a free software community dedicated to creating an open and user-friendly computing experience, offering an advanced graphical desktop, a wide variety of applications for communication, work, education and entertainment and a platform to easily build new applications upon. The KDE contributors guide is relevant for Krita contributors, too, and can be found `here <https://archive.flossmanuals.net/kde-guide/>`_."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:45
msgid "The Krita Foundation was created to support development of Krita. The Krita Foundation has sponsored Dmitry’s work on Krita since 2013."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:48
msgid "Internet Relay Chat"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:50
msgid "IRC is the main communication channel. There are IRC clients for every operating system out there, as well as a web client on the krita website."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:52
msgid "Joining IRC: connect to irc.freenode.net, select a unique nickname and join the #krita and ##krita-chat channels. #krita is for on-topic talk, ##krita-chat for off-topic chat."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:53
-msgid "Don’t ask to ask: if you’ve got a question, just ask it ."
+msgid "Don’t ask to ask: if you’ve got a question, just ask it."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:54
msgid "Don’t panic if several discussions happen at the same time. That’s normal in a busy channel."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:55
msgid "Talk to an individual by typing their nick and a colon."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:56
msgid "Almost every Monday, at 14:00 CET or CEST, we have a meeting where we discuss what happened in the past week, what we’re doing, and everything that’s relevant for the project. The meeting notes are kept in google docs."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:57
msgid "Activity is highest in CET or CEST daytime and evenings. US daytime and evenings are most quiet."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:58
msgid "**IRC is not logged. If you close the channel, you will be gone, and you will not be able to read what happened when you join the channel again. If you ask a question, you have to stay around!**"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:59
msgid "It is really irritating for other users and disrupting to conversations if you keep connecting and disconnecting."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:63
msgid "Mailing List"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:65
msgid "The mailing list is used for announcements and sparingly for discussions. Everyone who wants to work on Krita one way or another should be subscribed to the mailing list."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:67
msgid "`Mailing List Archives <https://mail.kde.org/mailman/listinfo/kimageshop>`_"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:69
msgid "The mailing list is called \"kimageshop\", because that is the name under which the Krita project was started. Legal issues (surprise!) led to two renames, once to Krayon, then to Krita."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:73
msgid "Gitlab (KDE Invent)"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:75
msgid "Gitlab serves the following purposes for the Krita team:"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:77
msgid "Review volunteers' submissions: https://invent.kde.org/kde/krita/merge_requests for the code itself, https://invent.kde.org/websites/docs-krita-org/merge_requests for the content of the Krita Manual."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:78
msgid "Host the code git repository: https://invent.kde.org/kde/krita . Note that while there are mirrors of our git repository on Github and Phabricator, we do not use them for Krita development."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:79
msgid "Host the Krita Manual content repository: https://invent.kde.org/websites/docs-krita-org"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:81
msgid "**Do not** make new issues on Gitlab or use it to make bug reports."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:83
msgid "**Do** put all your code submissions (merge requests) on Gitlab. **Do not** attach patches to bugs in the bug tracker."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:88
msgid "Phabricator serves the following purposes for the Krita team:"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:90
msgid "Track what we are working on: https://phabricator.kde.org/maniphest/ This includes development tasks, designing new features and UX design, as well as tasks related to the website."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:92
msgid "**Do not** report bugs as tasks on Phabricator. Phabricator is where we organize our work."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:95
msgid "Bugzilla: the Bug Tracker"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:97
msgid "Krita shares the bug tracker with the rest of the KDE community. Krita bugs are found under the Krita product. There are two kinds of reports in the bug tracker: bugs and wishes. See the chapters on :ref:`Bug Reporting <bugs_reporting>` and :ref:`Bug Triaging <triaging_bugs>` on how to handle bugs. Wishes are feature requests. Do not report feature requests in bugzilla unless a developer has asked you to. See the chapter on :ref:`Feature Requests <developing_features>` for what is needed to create a good feature request."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:100
msgid "Sprints"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:102
msgid "Sometimes, core Krita developers and users come together, most often in Deventer, the Netherlands, to work together on our code design, UX design, the website or whatever needs real, face-to-face contact. Travel to sprints is usually funded by KDE e.V., while accommodation is funded by the Krita Foundation."
msgid "We've moved from userbase.kde.org to docs.krita.org, then we moved from Mediawiki to Sphinx. This latter change is because Sphinx allows us to handle translations much better than mediawiki can."
msgid "We've found over the past two years that for certain types of users, a reference manual, even with some examples, just isn't enough. The manual should also provide fast and concise explanations for things, and provide a basic workflow for preparing an image for the web."
msgid "We also have found that certain concepts, such as color management and layer handling are far more advanced in Krita than the average artist is used to. Krita is free and many of its users will not have formal training in digital artwork. So there is no pre-existing artist-focused knowledge on how to use color management or filter layers."
msgid "In addition there are systems that are unique to Krita, for example the brush system, the transform masks, the alpha inheritance and the perspective assistants. Finally, there are users who aren't familiar with even standard painting workflows, and are not flexible enough to understand how to port a tutorial for Sai or Photoshop to Krita."
msgid "Apparently, one of the great things about Krita's team is how we connect with artists and acknowledge that they're doing cool stuff. The same should count for tutorials, especially because there are ways of using Krita and ways of approaching painting that are unique and we should encourage people to share their knowledge."
msgid "Krita is (free) open source software, which makes us effectively a community project, with dozens of volunteers pitching in to make it better. This, of course, requires we keep track of manuals and howto's for new volunteers to come in and help us. The various places we've done this have been rather spread out, and are often under maintained. The contributor's manual is an attempt to solidify all the information. It is therefore very technical in places."
msgid "There have been a bunch of tutorials on the krita.org and the krita-foundation.tumblr.com, the former focusing on explaining how to use a new feature and the later stimulated by user request."
msgid "This one is already online and a merger of the different FAQs that we had. It's currently being translated and we hope to keep this one the primary one to update."
msgid "First things first, you will want to talk to us! For this you can either go to the `IRC on krita.org (#krita on freenode.org) <https://krita.org/en/irc/>`_, or, more importantly, make an account at `identity.kde.org <https://identity.kde.org/>`_. The account you make at identity can be used to both access the forum as well as the `phabricator`_, where we organise Krita development."
msgid "Sphinx works by writing simple text files with reStructuredText mark up, and then it takes those text files and turns them into the manual. We keep track of changes in the manual by putting them into a version control system called :program:`Git`."
msgid "Because we use Git, there's only a few people who can put things into the version control system, so if you want to make changes you will need to put it up for review."
msgid "Not recommended when you plan to contribute more in the future. (See :ref:`merge-request-edit` if you don't have technical knowledge and want to contribute to Krita Manual more than once)."
msgid "Put all the files you changed into a zip file. This also includes the images if you're changing them. Try to keep the filenames the same, that's easier for us to copy over."
msgid "Explain what you did and use drag and drop to move the zip file to the input textbox. That should upload it. We will also need the email address you associate with your kde identity account."
msgid "Then, if the changes are accepted, someone with commit access will unpack those files into the manual folder and push the differences using the mail address."
msgid "Not recommended when you want to change more than one file at once. (See :ref:`merge-request-webide` or :ref:`merge-request-terminal` if you want to change more files, or simply edit only one per merge request)."
msgid "Come back to the official repository. Make sure you're browsing ``Websites/Krita Documentation``, not your own fork. Otherwise this method won't work correctly."
msgid "At the top of the page you see a dropbox with ``master`` as a chosen item; please select ``draft`` if your changes contain anything other than pure typo fixes."
msgid "Go to the smaller textbox below and write a nice message in the commit message section with the changes you've made. When done, press :guilabel:`Commit changes`. This will make a merge request for you, just fill in all of the fields as explained here: :ref:`new-merge-request`."
msgid "The downside is that right now there's no way to tell if you made errors with the mark up using this method. Please check your changes with the `Online Sphinx Editor <https://livesphinx.herokuapp.com/>`_ (just copy and paste the entire file you're editing)."
msgid "Click :guilabel:`WebIDE`. This should take you to a page that has a list of files on the left side and a big empty space for file contents on the right side."
msgid "Click :guilabel:`Commit...`. Double-click on all files in the :guilabel:`Unstaged changes` category to move them to :guilabel:`Staged changes`."
msgid "Click :guilabel:`Commit...` again - it will expand a commit message textbox. Write commit message that explains what changes have you made and why."
msgid "Make sure the settings are correct: you need to select :guilabel:`Create a new branch` (the name of the branch should be: ``[username]/[very short description of your changes]``). If you finished your changes, make sure that :guilabel:`Start a new merge request` is checked. Otherwise you'll need to make a new merge request manually later."
msgid "To create a new merge request manually, go to Krita Manual official repository (make sure the url *doesn't* contain your username now) and click :guilabel:`Create a new merge request` (bright green button at the left). Select your fork and select the branch that you've created in WebIDE."
msgid "If you don't have a push access to the official repository, gitlab won't allow you to save your changes if you were editing the official repository by mistake (and :guilabel:`Create a merge request` won't help with that: you still need to commit your changes to your branch, but if you don't have push access, you can't do it). It will just show the message: `An error occurred whilst committing your changes. Please try again.`"
msgid "Clone the repository locally with :guilabel:`git clone`. The repository page has the urls you can perform git clone from, and you can then push to your fork. The advantage of this is that you can use all the tools on your computer to edit these text files as well as build the manual locally to check for errors. (You need to do this step only once)."
msgid "Make sure you create a new branch for your changes and make sure you branched from the correct branch: ``master`` in case if your changes only contain typo fixes, ``draft`` in all other cases."
msgid "After you make your changes, commit them and push to your fork. For a detailed description of how to use Git in terminal in case of this workflow, go to :ref:`forking_gitlab`."
msgid "Finally, go to the website of the original repository (make sure you're on the correct branch, `master` or `draft`), and then to Merge Requests. Select your fork and the correct branch and create a new merge request. For instruction on how to fill the fields, see :ref:`new-merge-request`."
msgid "Your commit messages should conform to standards explained here: `How to Write a Git Commit Message <https://chris.beams.io/posts/git-commit/>`_"
msgid ":guilabel:`Title` and :guilabel:`Description` should explain what changes did you make and why did you make them, just like a commit message, so follow the guidelines from the link above in this case, too."
msgid "Make sure you checked :guilabel:`Allow commits from members who can merge to the target branch.` -- it is often needed for technical reasons that merge request is rebased on master, which technically changes the merge request, but it doesn't change the actual content of it. Rebase can be done by you or by the reviewer -- if you don't want to be bothered later too much, better check this checkbox so the reviewer can do it themselves with only a few clicks."
msgid "Unless your reviewers tell you otherwise, check :guilabel:`Squash commits when merge request is accepted`. The first line of the commit message will come from the :guilabel:`Title` of your merge request and the rest of it will be taken from the :guilabel:`Description` of the merge request."
msgid "When you finish creating your merge request, go to IRC and ask someone with push access to add the ``Needs Review`` label on your merge request."
msgid "If you want to use :guilabel:`Edit` mode, just go to :guilabel:`Changes` section of the merge request and click on the pencil icon (with a tooltip that says `Edit`) to use the Edit mode again."
msgid "If you edit files on your computer and work with terminal, make sure you're on the correct branch and push your changes - gitlab will update your merge request automatically."
msgid "At the time of writing this guide setting labels on merge requests is only possible by contributors with write access to the official repository. (If you don't know what that means, you're most probably not one of them). Because of that, when you create or change your merge request you need to get on IRC (see :ref:`the_krita_community`) and ask someone to label it for you."
msgid "This is for determining what is an appropriate writing style. A writing style, whether we consider its practical or aesthetic qualities, is usually underpinned by a goal or general philosophy. What do we want to achieve with the manual, and for whom is the manual meant?"
msgid "We cannot talk about a demographic in the sense that we know all Krita users are 55 year old men. Krita is used by a hugely different amount of people, and we are actually kind of proud that we have such a varied userbase."
msgid "High-school and college students trying out drawing software for illustrations. These usually have some previous experience with drawing software, like Painttool Sai or Photoshop, but need to be introduced to possibilities in :program:`Krita`. This group's strength is that they share a lot of information with each other like tips and tricks and tutorials."
msgid "Professionals, people who earn their money with digital drawing software. The strength of this group is that they have a lot of know-how and are willing to donate to improve the program. These come in two types:"
msgid "Non technical professionals. These are people who do not really grasp the more mathematical bits of a piece of software, but have developed solid workflows over the years and work with software using their finely honed instincts. These tend to be illustrators, painters and people working with print."
msgid "Technical professionals. These are people who use :program:`Krita` as part of a pipeline, and care about the precise maths and pixel pushing. These tend to be people working in the games and VFX industry, but occasionally there's a scientist in there as well."
msgid "Adult and elderly hobbyists. This group doesn't know much about computers, and they always seem to get snagged on that one little step missing from a tutorial. Their strength as a group is that they adapt unconventional workflows from real life that the student wouldn't know about and the professional has no time for and create cool stuff with that, as well as that they have a tempering effect on the first group in the larger community."
msgid "there's only one that is technical. Which is why we need the concept pages, so that we can create a solid base to write our manual texts on top of."
msgid "As a community, we want to be welcoming to the users, so we try to avoid language that is unwelcoming. Swearing is already not condoned by KDE, but going to the far other end, an academic style where neither writer nor reader is acknowledged might give the idea that the text is far more complex than necessary, and thus scare away users."
msgid "The reason is that people with epilepsy may be affected by fast moving images. Similarly, gifs can sometimes carry too much of the burden of explanation. If you can't help but use gifs, at the least notify the reader of this in the introduction of the page."
msgid "I would like to discourage photos and traditional paintings in the manual if they are not illustrating a concept. The reason is that it is very silly and a little dishonest to show Rembrandt's work inside the Krita GUI, when we have so many modern works that were made in Krita. All of the pepper&carrot artwork was made in Krita and the original files are available, so when you do not have an image handy, start there. Photos should be avoided because Krita is a painting program. Too many photos can give the impression Krita is trying to be a solution for photo retouching, which really isn't the focus."
msgid "Of course, we still want to show certain concepts in play in photos and master paintings, such as glossing or indirect light. In this case, add a caption that mentions the name of the painting or the painter, or mentions it's a photograph."
msgid "Remember that the manual is licensed under GDPL 1.3, so images submitted will be licensed under that. In the case of CC-By-Sa/CC-By ensure that the file gets attributed appropriately through a figure caption. Needless to say, don't submit images that cannot be licensed under either license."
msgid "Proofreading results for old pages will be considered as bugfixes and thus will go into the ``master`` branch and merged into the ``draft`` branch as necessary."
msgid "Each release will have a version of the epub uploaded as part of the release process. .. Where do we get the POT files from? Even the translated versions?"
msgid "As with images, don't add text that you do not have permission to add. This means that text is either written by you, or you have permission to port it from the original author. The manual is GDPL 1.3+ so the text will be relicensed under that."
msgid "If you change a page because a feature has changed, and you have commit access, the change can be pushed without review (unless you feel more comfortable with a review), but you should add::"
msgid "You can help review merge requests. Request reviewing is usually done by programmers to find mistakes in each other's code, but because programming code is text based just like regular text, we can use this to check against typos as well!"
msgid "A merge request, is an amount of changes done in a document (added, removed) put into a machine readable file. When someone submits a review request (on system like gitlab or github this is a merge or pull request), people who maintain the original files will have to look them over and can make comments about things needing to change. This allows them to comment on things like typos, over-complicated writing but also things that are incorrect. After a patch has been accepted it can be pushed into the version control system."
msgid "Commenting changes happens after the fact. You can comment on a change by going to the commit message (from the repository page, go to history and then click on an entry), where you will be able to make comments on the changes made."
msgid "In both cases, the interface consists of the difference being shown, with on the left the old version, and on the right the new version. Lines that have been added will be marked in green while lines that have been removed will be marked with red. You can click a speech bubble icon to add an 'inline' comment."
msgid "The second major way the manual needs to be proofread is **over the whole file**. Many of the pages have only been checked for correctness but not for style and grammar."
msgid "Translation of the manual is handled by the `KDE localization community <https://l10n.kde.org/>`_. To join the translation effort, go to the localization site, select the list of `translation teams <https://l10n.kde.org/teams-list.php>`_, select the language you wish to translate for, and follow the instructions on the team page to get in contact with fellow translators."
msgid "The localization team has access to the PO files for this manual, which is a file type used by translation programs like POEdit and Lokalize. A translation team is able to work together on translating these files and uploading them to the translations SVN. A special script will then take the translations from the SVN and bring them to the manual section to be incorporated on a daily basis."
msgid "Images can be translated if a translation team wants to provide their own images. All images in the image folder are by default for 'en'. When you want to translate a specific image, go into that folder and add another folder with your language code to add in the translated versions of images. So Sphinx will search for a dutch version of :file:`/images/Pixels-brushstroke.png` at :file:`/images/nl/Pixels-brushstroke.png` and for a dutch version of :file:`/images/dockers/Krita-tutorial2-I.1-2.png` in :file:`/images/dockers/nl/Krita-tutorial2-I.1-2.png`."
msgid "Finished translations also need to be added to the build script to show up online. Translator teams which are confident in the state of their translation should contact the main Krita team via the kimageshop mailinglist(kimageshop@kde.org), or foundation@krita.org, to accomplish this."
msgid "This one is a little bit an extension to :ref:`saving_for_the_web`. In particular it deals with making images for the manual, and how to optimise images."
msgid "Now, if you wish to make an image of the screen with all the dockers and tools, then :ref:`saving_for_the_web` won't be very helpful: It only saves out the canvas contents, after all!"
-msgid "Windows has a build-in screenshot tool. It is by default on the :kbd:`PrtSc` key. On laptops you will sometimes need to use the :kbd:`Fn` key."
+msgid "Windows has a build-in screenshot tool. It is by default on the :kbd:`Print Screen` key. On laptops you will sometimes need to use the :kbd:`Fn` key."
-msgid "Both Gnome and KDE have decent screenshot tools showing up by default when using the :kbd:`PrtSc` key, as well do other popular desktop environments. If, for whatever reason, you have no"
+msgid "Both Gnome and KDE have decent screenshot tools showing up by default when using the :kbd:`Print Screen` key, as well do other popular desktop environments. If, for whatever reason, you have no"
msgid "While we should minimize the amount of gifs in the manual for a variety of accessibility reasons, you sometimes still need to make gifs and short videos. Furthermore, gifs are quite nice to show off features with release notes."
msgid "`Peek <https://github.com/phw/peek>`_ -- This one has an appimage and a very easy user-interface. Like many screenrecording programs it does show trouble on Wayland."
msgid "The Screenshot hotkey on OS X is :kbd:`Shift + Command + 3`, according to `the official apple documentation <https://support.apple.com/en-us/HT201361>`_."
msgid "Different file formats are better for certain types of images. In the end, we want to have images that look nice and have a low filesize, because that makes the manual easier to download or browse on the internet."
msgid "The logic is the way how each of these saves colors. Jpeg is ideal for photos and images with a lot of gradients because it :ref:`compresses differently <lossy_compression>`. However, contrasts don't do well in jpeg. PNG does a lot better with images with sharp contrasts, while in some cases we can even have less than 256 colors, so gif might be better."
msgid "Grayscale images, even when they have a lot of gradients variation, should be PNG. The reason is that when we use full color images, we are, depending on the image, using 3 to 5 numbers to describe those values, with each of those values having a possibility to contain any of 256 values. JPEG and other 'lossy' file formats use clever psychological tricks to cut back on the amount of values an image needs to show its contents. However, when we make grayscale images, we only keep track of the lightness. The lightness is only one number, that can have 256 values, making it much easier to just use gif or PNG, instead of jpeg which could have nasty artifacts. (And, it is also a bit smaller)"
msgid "The most commonly recommended tool for this on Windows is `IrfranView <https://www.irfanview.com/>`_, but the dear writer of this document has no idea how to use it exactly."
msgid "There is a whole laundry list of `PNG optimisation tools <https://css-ig.net/png-tools-overview>`_ available on Linux. They come in two categories: Lossy (Using psychological tricks), and Lossless (trying to compress the data more conventionally). The following are however the most recommended:"
-msgid "Where *image* is replaced with the image file name. When you press :kbd:`Enter`, a new image will appear in the folder with the compressed results. PNGQuant works for most images, but some images, like the color selectors don't do well with it, so always double check that the resulting image looks good, otherwise try one of the following options:"
+msgid "Where *image* is replaced with the image file name. When you press the :kbd:`Enter` key, a new image will appear in the folder with the compressed results. PNGQuant works for most images, but some images, like the color selectors don't do well with it, so always double check that the resulting image looks good, otherwise try one of the following options:"
msgid "where image is the filename. OptiPNG will then proceed to test several compression algorithms and **overwrite** the image.png file with the optimised version. You can avoid overwriting with the ``--out imageout.png`` command."
msgid "Now, JPEG is really tricky to optimize properly. This is because it is a :ref:`lossy file format <lossy_compression>`, and that means that it uses psychological tricks to store its data."
msgid "However, tricks like these become very obvious when your image has a lot of contrast, like text. Furthermore, JPEGs don't do well when they are resaved over and over. Therefore, make sure that there's a lossless version of the image somewhere that you can edit, and that only the final result is in JPEG and gets compressed further."
msgid "where image is the file you'd like to examine. If you just type ``exiftool`` in any given folder it will output all the information it can give about any file it comes across. If you take a good look at some images, you'll see they contain author or location metadata. This can be a bit of a problem sometimes when it comes to privacy, and also the primary reason all metadata gets stripped."
msgid "Sometimes we want to extract metadata, like an icc profile, before stripping everything. This is done by converting the image to the profile type:"
msgid "Description metadata is really useful for the purpose of helping people with screenreaders. Webbrowsers will often try to use the description metadata if there's no alt text to generate the alt-text. Another thing that you might want to embed is stuff like color space data."
msgid "In a certain way, embedding license metadata is really nice because it allows you to permanently mark the image as such. However, if someone then uploads it to another website, it is very likely the metadata is stripped with imagemagick."
msgid "The creative commons website suggest we `use XMP for this <https://wiki.creativecommons.org/wiki/XMP>`_. You can ask the Creative Commons License choose to generate an appropriate XMP file for you when picking a license."
-msgid "exiftool -Marked=true -License=\"http://creativecommons.org/licenses/by-sa/4.0\" -UsageTerms=\"This work is licensed under a <a rel=\"license\" href=\"http://creativecommons.org/licenses/by-sa/4.0/\">Creative Commons Attribution-ShareAlike 4.0 International License</a>.\" -Copyright=\"CC-BY-SA-NC 4.0\" image.png"
+msgid "exiftool -Marked=true -License=\"https://creativecommons.org/licenses/by-sa/4.0\" -UsageTerms=\"This work is licensed under a <a rel=\"license\" href=\"https://creativecommons.org/licenses/by-sa/4.0/\">Creative Commons Attribution-ShareAlike 4.0 International License</a>.\" -Copyright=\"CC-BY-SA-NC 4.0\" image.png"
msgid "You may have heard that Krita has something called color-management. Or maybe you just wondered what all these 'color model' and 'color profile' things you can find in the menus mean. Color management is pretty useful for people who work in digital imaging professionally, and hopefully this page will explain why."
msgid "If you've never worked with color management before, and have no clue what it is, then know that you've probably been working in the 8bit RGB color space with the sRGB profile. This means you can choose for *sRGB built-in* or *sRGB-elle-v2-srgbtrc.icc*. With the new color space browser this profile is marked with *(default)* when using 8bit."
msgid "We'll go into what these terms mean in the theory, but if you're here only for trying to figure out which is the default, you now know it. Maybe, after reading this, you may feel like changing the default, to get new and interesting results from filters, blending modes, or just the color smudge brush."
msgid "The teacher gives them a painting assignment: They need to paint a red triangle, a blue square, a green circle and put a yellow border around the three. The kids are very experienced with painting already, so the teacher can confidently leave the smarter ones to their own devices, and spent more time on those who need help."
msgid "Group 1 had vermillion red, citron yellow and ultramarine blue to their disposal. This means their triangle looks nice and red, but their circle's green is muddy. This is because ultramarine is too dark of a blue to create nice greens with."
msgid "Group 2 had magenta red, citron yellow and cerulean blue. Magenta is a type of red that is closer to pink, opposed to vermillion, which is closer to orange. However, their green looks nice because cerulean is a much lighter blue."
msgid "Now, these are kindergarteners, so this isn't the largest problem in the world. However, imagine that something like this happened at a printing company? Imagine four printers printing the same magazine with wildly different results? That would be disastrous!"
msgid "It usually works by attempting to covert a color to the reference color space XYZ. XYZ is a coordinate system that has a spot for all colors that the average human eye can see."
msgid "Krita has two systems dedicated to color management. On the one hand, we have **lcms2**, which deal with ICC profiles, and on the other, we have **OCIO**, which deal with LUT color management."
msgid "To give a crude estimate, ICC profiles deal with keeping colors consistent over many interpretations of devices (screens, printers) by using a reference space, and OCIO deals with manipulating the interpretation of said colors."
msgid "Device spaces are those describing your monitor, and have to be made using a little device that is called \"colorimeter\". This device, in combination with the right software, measures the strongest red, green and blue your screen can produce, as well as the white, black and gray it produces. Using these and several other measurements it creates an ICC profile unique to your screen. You set these in Krita's color management tab. By default we assume sRGB for screens, but it's very likely that your screen isn't exactly fitting sRGB, especially if you have a high quality screen, where it may be a bigger space instead. Device spaces are also why you should first consult with your printer what profile they expect. Many printing houses have their own device profiles for their printers, or may prefer doing color conversion themselves. You can read more about colorimeter usage :ref:`here <profiling_and_calibration>`."
msgid "These are delivered alongside Krita for ICC, and downloadable from the OCIO website for OCIO. Working spaces are particularly nice to do color calculations in, which programs like Krita do often. It's therefore recommended to have a working space profile for your image."
msgid "These are special spaces that have been deformed to give a certain look to an image. Krita doesn't deliver Look profiles for ICC, nor does it yet support Look spaces for OCIO."
msgid "Knowing this about these spaces of course doesn't give you an idea of how to use them, but it does make it easier to explain how to use them. So let us look at a typical color management workflow:"
msgid "A typical example of a color managed workflow. We have input from scanners and cameras, which we convert to a working space that can be used between different editing software, and is converted to an output space for viewing on screen or printing."
msgid "In a traditional color managed workflow, we usually think in terms of real world colors being converted to computer colors and the other way around. So, for example photos from a camera or scanned in images. If you have a device space of such a device, we first assign said device space to the image, and then convert it to a working space."
msgid "We then do all our editing in the working space, and use the working space to communicate between editing programs. In Krita's case, due to it having two color management systems, we use ICC profiles between programs like Gimp 2.9+, Inkscape, digiKam and Scribus, and OCIO configuration between Blender and Natron."
msgid "You also store your working files in the working space, just like how you have the layers unmerged in the working file, or have it at a very high resolution."
msgid "Sometimes, we apply aesthetic or 'look' spaces to an image as part of the editing process. This is rather advanced, and probably not something to worry about in Krita's case."
msgid "Then, when we're done editing, we try to convert to an output space, which is another device space. This can be CMYK for printers or a special screen RGB profile. When you are dealing with professional printing houses, it is best to ask them about this step. They have a lot of experience with doing the best conversion, and may prefer to do the conversion from your working space to the device space of their printers."
msgid "Another form of output is the way your screen displays the color. Unlike regular output, this one is done all the time during editing: After all, you need to be able to see what you are doing, but your screen is still a device with a device space, so it does distort how the image looks. In this manner, you can see your screen as a set of binoculars you have to look through to see your image at all."
msgid "Therefore, without a profiled monitor, you actually don't know what the actual colors you are working with are like, because the computer doesn't know the relevant properties of your screen. So if you profiled your monitor, give Krita the profile in the settings, and select the sRGB space to draw in, you are for the first time seeing the actual colors of the sRGB space."
msgid "When we paint from scratch, we can see our screen profile as the input space, because we use it to determine what colors to pick. This somewhat simplifies the workflow, but makes the screen profile and viewing conditions more important."
msgid "Now, photographers and people who do a tricky discipline of VFX called 'color grading' will go completely mad over trying to get the colors they put in to come out 100% correctly, and will even count in factors like the time of day and the color they painted their walls. For example, if the wall behind your computer is pure red, your eyes will adjust to be less sensitive to red, which means that the colors they pick in the program could come out redder. We call these the *viewing conditions*."
msgid "Thankfully, artists have to worry a slight bit less about this. As illustrations are fully handmade, we are able to identify the important bits and make appropriate contrasts between colors. This means that even if our images turn out to be slightly redder than intended, it is less likely the whole image is ruined. If we look back at the kindergarten example above, we still understand what the image was supposed to look like, despite there being different colors on each image. Furthermore, because the colors in illustrations are deliberately picked, we can correct them more easily on a later date. Yet, at the same time, it is of course a big drag to do this, and we might have had much more flexibility had we taken viewing conditions under consideration."
msgid "That said, for artists it is also very useful to understand the working spaces. Different working spaces give different results with filters and mixing, and only some working spaces can be used for advanced technology like HDR."
msgid "Similarly, Krita, as a program intended to make images from scratch, doesn't really worry about assigning workspaces after having made the image. But because you are using the screen as a binocular to look at your image, and to pick colors, you can see your screen's device space as an input space to the image. Hence why profiling your monitor and giving the profile to Krita in the settings can help with preparing your work for print and future ventures in the long run."
msgid "Overall, it is kinda useful to keep things like viewing conditions in the back of your mind. Many professional artists use a mid-gray color as their default canvas background because they find they create much more dynamic images due to having improved their viewing conditions. It is also why a lot of graphics programs, including Krita, come with a dark theme nowadays. (Though, of course this might also be because dark themes can be considered cool, who knows.)"
msgid "An ICC profile is a set of coordinates describing the extremities of the device space within XYZ, and it is the color management data you use to communicate your working space to printers and applications that are designed for the print industry, such as Gimp, Scribus, Photoshop, Illustrator, Inkscape, digiKam, RawTheraphee, etc. You have two types of ICC profiles:"
msgid "These are delivered alongside Krita. Matrix shaper profiles are made by setting parameters and interpolating between these to get the exact size of the color space. Due to this, Krita's color space browser can give you a lot of information on these profiles. Such profiles are also preferable as working space."
msgid "These are fairly rare, and primarily used to describe printer profiles, such as CMYK. cLUT, or Color Look-up Table profiles store far more data than Matrix shaper profiles, so they can hold data of little particularities caused by, for example, unexpected results from mixing pigments. This is a far more organic approach to describing a color space, hence why a lot of programs that don't care for color management much don't support these."
msgid "cLUT profiles work by holding tables of each color in a color space and their respective coordinates in a reference space. For CMYK this is typically L\\*A\\*B\\* and for the rest XYZ. These tables are tricky to make, which means these profiles are a lot rarer."
msgid "The interesting thing about ICC profiles is that your working space can be larger than your device space. This is generally not bad. However, when converting, you do end up with the question of how to translate the working space values."
msgid "This just squishes the values of the working space into the space it's converted to. It's a nice method to see all possible values in this, but not so good if you want accurate color reproduction. Use this if you want to see all colors in an image, or want to express all possible contrasts. Doesn't work with Matrix Shaper profiles, defaults to relative colorimetric."
msgid "The opposite to Perceptual, Absolute colorimetric will attempt to retain all the correct colors at whatever cost, which may result in awful looking colors. Recommended only for reproduction work. Doesn't work with Matrix Shaper profiles in Krita due to ICC v4 workflow standards."
msgid "An in between solution between perceptual and absolute, relative will try to fit whatever colors it can match between color spaces. It does this by aligning the white and black points. It cuts off the rest to their respective borders. This is what all matrix shaper profiles default to during conversion, because the ICC v4 workflow specifies to only use Relative Colorimetric for matrix shaper profiles."
msgid "Does anything to retain colorfulness, even hue will be sacrificed. Used in infographics. Doesn't work with Matrix Shaper profiles, defaults to relative colorimetric."
msgid "*ICC profile version* is the last thing to keep in mind when dealing with ICC profiles. Krita delivers both Version 2 and Version 4 profiles, with the later giving better results in doing color maths, but the former being more widely supported (as seen below in 'Interaction with other applications'). This is also why Krita defaults to V2, and we recommend using V2 when you aren't certain if the other programs you are using support V4."
msgid "The :ref:`lut_docker` is the second important bit of color management in Krita that is shared between Krita and programs like Blender, Natron and Nuke, and only uses Look Up Tables that are configured via a config file."
msgid "You can set the workingspace of the image under input color space, and the display to sRGB or your own LUT if you have added it to the configuration. View in this case is for proofing transforms to a certain display device."
msgid "As explained before, we can see our monitor as a telescope or binocular into the world of our picture. Which means it distorts our view of the image a little. But we can modify this binocular, or display filter to see our image in a different way. For example, to allow us to see the white in an image that are whiter than the white of our screen. To explain what that means, we need to think about what white is."
msgid "For example, white, on our monitor is full red, full green and full blue. But it's certainly different from white on our paper, or the color of milk, white from the sun, or even the white of our cell-phone displays."
msgid "This means that there's potentially blacker blacks than screen black, and white whites than screen white. However, for simplicity's sake we still assign the black-point and the white-point to certain values. From there, we can determine whether a white is whiter than the white point, or a black blacker than the black-point."
msgid "The LUT docker allows us to control this display-filter and modify the distortion. This is useful when we start modifying images that are made with scene referred values, such as HDR photos, or images coming out of a render engine."
msgid "The point of this is that you can take advantage of more lightness detail in an image. While you can't see the difference between screen white and whiter-than-screen-white (because your screen can't show the difference), graphics programs can certainly use it."
msgid "A common example is matching the lighting between a 3d model and a real world scene. Others are advanced photo retouching, with much more contrast information available to the user. In painting itself, this allows you to create an image where you can be flippant with the contrast, and allow yourself to go as bright as you'd like."
msgid "LUT docker manipulations are per view, so you can create a new view and set it to luminosity. This way you can see the image in both color as well as grayscale and keep a good eye on your values."
-msgid "Like ICC, the LUT Docker allows you to create a profile of sorts for your device. In this case it's the 'lut', which stands for 'Look Up Table', and which can be added to OCIO by modifying the configuration file. When OCIO is turned on, the configuration in :menuselection:`Settings --> Configure Krita --> Color Management` is turned off, unless you are using the :guilabel:`Internal` color engine."
+msgid "Like ICC, the LUT Docker allows you to create a profile of sorts for your device. In this case it's the 'LUT', which stands for 'Look Up Table', and which can be added to OCIO by modifying the configuration file. When OCIO is turned on, the configuration in :menuselection:`Settings --> Configure Krita --> Color Management` is turned off, unless you are using the :guilabel:`Internal` color engine."
msgid "If you want to have a properly color managed workflow, you have one made customary for the input device (your screen) and the output devices (your printer, or target screen). For web the output is always sRGB."
-msgid "Do NOT use screen profiles or other device profiles to draw in. Use a working space profile such as any of the elle profiles for this, as the color maths will be much more predictable and pleasant. Krita will convert between your screen and working space on the fly, allowing you to pick the correct colors. This turns your screen into binoculars to view the image."
+msgid "Do NOT use screen profiles or other device profiles to draw in. Use a working space profile such as any of the 'elle' profiles for this, as the color maths will be much more predictable and pleasant. Krita will convert between your screen and working space on the fly, allowing you to pick the correct colors. This turns your screen into binoculars to view the image."
msgid "Use the appropriate color management for the appropriate workflow. If you are working with Blender, you will be better off using OCIO, than ICC. If you are working with Scribus or Photoshop, use ICC."
msgid "Krita does a lot of color maths, often concerning the blending of colors. This color maths works best in linear color space, and linear color space requires a bit depth of at the least 16bit to work correctly. The disadvantage is that linear space can be confusing to work in."
msgid "If you like painting, have a decent amount of RAM, and are looking to start your baby-steps in taking advantage of Krita's color management, try upgrading from having all your images in sRGB built-in to sRGB-v2-elle-g10.icc or rec2020-v2-elle-g10.icc at 16bit float. This'll give you better color blending while opening up the possibility for you to start working in HDR!"
msgid "Some graphics cards, such as those of the NVidia-brand actually have the best performance under 16bit float, because NVidia cards convert to floating point internally. When it does not need to do that, it speeds up!"
msgid "Krita doesn't have built-in dithering currently, which means that 16 to 18bit conversions can come out a bit banded. But you can simulate it by adding a fill layer with a pattern, set this fill layer to overlay, and to 5% opacity. Then flatten the whole image and convert it to 8bit. The pattern will function as dithering giving a smoother look to gradients."
msgid "If it's a color image, keep it in the working space profile: Many web browsers these days support color profiles embedded into images. Firefox, for example, will try to convert your image to fit the color profile of the other monitor (if they have one). That way, the image will look almost exactly the same on your screen and on other profiled monitors."
msgid "In some versions of Firefox, the colors actually look strange: This is a bug in Firefox, which is because its `color management system is incomplete <https://ninedegreesbelow.com/galleries/viewing-photographs-on-the-web.html>`_, save your PNG, JPG or TIFF without an embedded profile to work around this."
-msgid "You hopefully made the picture in a working space profile instead of the actual custom profile of your screen, if not, convert it to something like Adobe RGB, sRGB or rec2020."
+msgid "You hopefully made the picture in a working space profile instead of the actual custom profile of your screen, if not, convert it to something like Adobe RGB, sRGB or Rec. 2020."
msgid "If you wish to use Krita's OCIO functionality, and in particular in combination with Blender's color management, you can try to have it use Blender's OCIO config."
msgid "Blender's OCIO config is under ``<Blender-folder>/version number/datafiles/colormanagement``. Set the LUT docker to use the OCIO engine, and select the config from the above path. This will give you Blender's input and screen spaces, but not the looks, as those aren't supported in Krita yet."
msgid "You might encounter some issues when using different applications together. One important thing to note is that the standard Windows Photo Viewer application does not handle modern ICC profiles. Krita uses version 4 profiles; Photo Viewer can only handle version 2 profiles. If you export to JPEG with an embedded profile, Photo Viewer will display your image much too dark."
msgid "As mentioned before, input for your screen is set via :menuselection:`Settings --> Configure Krita --> Color management`, or via the LUT docker's 'screen space'. Working space is set via new file per document, or in the LUT docker via 'input space'."
msgid "Use the sRGB-elle-V2-srgbtrc.icc for going between Inkscape, Photoshop, Painttool Sai, Illustrator, Gimp, Manga Studio, Paintstorm Studio, MyPaint, Artrage, Scribus, etc. and Krita."
msgid "If you are using a larger space via ICC, you will only be able to interchange it between Krita, Photoshop, Illustrator, Gimp 2.9, Manga Studio and Scribus. All others assume sRGB for your space, no matter what, because they don't have color management."
msgid "If you are going between Krita and Blender, Nuke or Natron, use OCIO and set the input space to 'sRGB', but make sure to select the sRGB profile for ICC when creating a new file."
msgid "For the final for the web, convert the image to sRGB 8bit, 'srgbtrc', do not embed the ICC profile. Then, if using PNG, put it through something like 'pngcrush' or other PNG optimizers. sRGB in this case is chosen because you can assume the vast majority of your audience hasn't profiled their screen, nor do they have screens that are advanced enough for the wide gamut stuff. So hence why we convert to the screen default for the internet, sRGB."
msgid "The CMYK profiles are different per printer, and even per paper or ink-type so don't be presumptuous and ask ahead for them, instead of doing something like trying to paint in any random CMYK profile. As mentioned in the viewing conditions section, you want to keep your options open."
msgid "You can set the advanced color selector to transform to a given profile via :menuselection:`Settings --> Configure Krita --> Color Selector Settings`. There, tick :guilabel:`Color Selector Uses Different Color Space than Image` and select the CMYK profile you are aiming for. This will limit your colors a little bit, but keep all the nice filter and blending options from RGB."
msgid "So this one is tricky. You can use OCIO and ICC between programs, but recommended is to have your images to the engine in sRGB or grayscale. Many physically based renderers these days allow you to set whether an image should be read as a linear or 'srgbtrc' image, and this is even vital to have the images being considered properly in the physically based calculations of the game renderer."
msgid "While game engines need to have optimized content, and it's recommended to stay within 8bit, future screens may have higher bit depths, and when renderers will start supporting those, it may be beneficial to develop a workflow where the working-space files are rather unnecessarily big and you run some scripts to optimize them for your current render needs, making updating the game in the future for fancier screens less of a drag."
msgid "Normal maps and heightmaps are officially supposed to be defined with a 'non-color data' working space, but you'll find that most engines will not care much for this. Instead, tell the game engine not to do any conversion on the file when importing."
msgid "Specular, glossiness, metalness and roughness maps are all based on linear calculations, and when you find that certain material has a metalness of 0.3, this is 30% gray in a linear space. Therefore, make sure to tell the game engine renderer that this is a linear space image (or at the very least, should NOT be converted)."
msgid "`Panda3D example of how an image that has gamma encoded without the 3D renderer being notified of it having gamma-encoding can result in too dark images <https://www.panda3d.org/blog/the-new-opengl-features-in-panda3d-1-9/>`_."
msgid "Much like physical media, there are many ways to mix colors together in Krita. Traditional painters and illustrators often use techniques like **glazing**, **scumbling**, and **hatching** to mix colors directly on their canvas, on top of mixing colors together on a **palette** or even within the hairs of their **brush**. With a little bit of practice and know-how, and thanks to the variety of powerful tools in Krita, we can mimic all of these mixing techniques in digital painting."
msgid "In both traditional and digital painting, mixing techniques can be divided into *two major categories*: let's call them **\"on-canvas\"** and **\"off-canvas\"**."
msgid "On-canvas mixing techniques are ones where multiple colors are combined directly on the canvas as the artist paints. This takes a few forms, including **layering semi-transparent color** on top of another color, using **texture** to change how a color is perceived, or even in the interaction between two areas of wet paint in traditional media. Bottom line: on-canvas mixing happens right on the canvas and is a great tool for artistic exploration and \"happy accidents\"."
msgid "In traditional painting, **glazing** is overlaying many different semi-transparent layers to create on-canvas color mixtures. Likewise, in digital painting we can also use glazing to mix colors directly on our canvas. This is one of the most fundamental and commonly used mixing techniques in digital painting."
-msgid "We first lay down a semi-transparent layer on top of another color that we intend to mix with. Then, we pick the **resultant color** with :kbd:`Ctrl` + |mouseleft| (this can be configured in the canvas input settings), and paint with that. Depending on our brush's **opacity setting**, each time we glaze one color over another we will get a color that is somewhere between those two colors, often leading to a nice mixture."
+msgid "We first lay down a semi-transparent layer on top of another color that we intend to mix with. Then, we pick the **resultant color** with the :kbd:`Ctrl +` |mouseleft| shortcut (this can be configured in the canvas input settings), and paint with that. Depending on our brush's **opacity setting**, each time we glaze one color over another we will get a color that is somewhere between those two colors, often leading to a nice mixture."
msgid "We can mix even more easily with glazing when we set our brush's **flow** to a lower setting. Subtly different than opacity, :ref:`flow <option_opacity_n_flow>` is transparency per dab instead of stroke, and so it gives us softer strokes without giving up control."
msgid "Furthermore, we can combine glazing with various **blending modes** to achieve different, interesting effects. For example, glazing with the **multiply** blending mode to create nice shadows:"
msgid "Using a semi-transparent brush that's set to multiply, we can add colored layers to suggest shadows and mid-tones. The multiply blending mode will darken and interact with each base color differently."
msgid "Then, using a brush with low flow (~0.30), we can pick the resulting colors and lay down more layers. Not only does this help you define the different planes and forms that are so crucial for creating a sense of depth and three-dimensionality, it also gives quite a nice, painterly effect!"
msgid "Continue with a lower opacity and flow to create even smoother gradients. Make your **edges** as sharp or smooth as your subject matter and art style demands!"
msgid "**Smudge mixing** is done with the :ref:`color_smudge_brush_engine`, a special brush engine that allows you to mix your current brush color with the color(s) under the brush. It's a very powerful type of brush that gives a lovely painterly effect. *Performance wise, it's a bit more demanding and slower than the regular pixel brush*."
msgid "Like most painting programs, Krita allows you to pick a :ref:`option_brush_tip`, which can be used to create a textured effect like that of scumbling."
msgid "With glazing can get you pretty far when it comes to *defining planes and forms*, scumbling is the best method to *create texture and to break up big pasty flats* in your painting."
msgid "**Off-canvas** mixing has basically always been a core tool for artists everywhere; when we think of the stereotypical artist we might imagine someone with a few **brushes** in one hand and a wooden **palette** in the other. Whether it's oils, watercolor, or other traditional media, for the artist to have absolute control over their colors it's crucial to have some kind of palette, plate, jar, or other **off-canvas area** to mix colors together. While it's easy to overlook this in digital painting (where selecting fresh new colors without mixing at all is both easy and free), Krita has a few very useful and unique features for off-canvas mixing."
msgid "Krita, like almost every art and graphics program, has a :ref:`color_picker_tool` which allows you to very quickly sample a color from any pixel on your canvas. While this tool may seem relatively simple and humble, it is also one of the most important and commonly used tools in the digital artist's toolbox - perhaps only second to the brush! In fact, the color picker tool is at the very heart of mixing colors, and is often used in combination with on-canvas techniques like glazing and scumbling to produce smooth blends of color."
msgid "And still, there is more to this little tool than meets the eye! Not only can you configure Krita's color picker to sample from the average color of a **radius** of pixels, Krita's Color Picker also has a unique **blending** feature: a powerful and intuitive tool for off-canvas color mixing!"
msgid "The Color Picker Blending feature changes the way that picking colors has traditionally worked for decades; instead of completely replacing your current brush color with the newly sampled color, *blending allows you to quickly \"soak up\" some portion of the sampled color*, which is then mixed with your current brush color."
msgid "You can use Color Picker Blending much like a physical paint brush in traditional media. If you were to dip your paint brush into a pool of *blue* paint, and then immediately dip again into a pool of *red* paint and paint a stroke across your canvas, the stoke wouldn't be pure red - it would be some combination of blue and red which would mix to create an intermediate purple color. Which shade of purple would depend on the ratio of paints that mix together within the hairs of your brush, and this is essentially what the Color Picker's \"blend\" option controls: what percentage of sampled color is mixed together with your current brush color!"
msgid "Not only does Krita's Color Picker Blending feel even more like mixing paints, it is also completely off-canvas and independent of opacity, flow, shape, and other brush settings. Furthermore, unlike most on-canvas mixing techniques, Color Picker Blending works regardless of the location of colors on your canvas - enabling you to mix with colors at any position, on any layer, or even in different documents! Quickly mix lighting colors with local colors, mix the ambient sky color into shadows, create atmospheric depth, mix from a preselected palette of colors in another layer/document, etc."
msgid "To use Color Picker Blending, simply set the \"blend\" option in the **Tool Options Docker** while the Color Picker Tool is active; setting blend to 100% will cause your Color Picker to work in the traditional way (completely replacing your brush color with the picked color), setting to around 50% will give you a half-way mix between colors, and setting to a lower value will create more subtle shifts in colors each click. Of course, blending affects both your dedicated Color Picker Tool as well as the :kbd:`Ctrl +` |mouseleft| shortcut."
msgid "Clicking and dragging the Color Picker around the canvas currently causes it to sample many times as it switches pixels. You can use this trait to quickly soak up more color by \"dipping\" your color picker into color and swirling it around. This can be pretty satisfying! However, this also means that some care must be taken to prevent from accidentally picking up more color than you want. It's pretty easy to click a single pixel only one time using a **mouse**, but when painting with a **drawing tablet and pen** it can sometimes be desirable to use a slightly lower blend setting!"
msgid "Somewhat hidden away in the **Dockers** menu (:menuselection:`Settings --> Dockers --> Digital Colors Mixer`), this can be a useful tool for off-canvas mixing. The Digital Colors Mixer looks a little bit like an audio mixing board that you'd see in a recording studio, but instead of mixing music it mixes colors! It contains 6 independent **color mixers** that mix your current brush color with any color of your choosing."
msgid "By clicking the **color buttons** below each mixer you can choose a palette of colors to mix with. Above each mixer is a **color patch** that will produce a color that mixes some amount of your current brush color with the palette color. Colors towards the top of the mixer will deliver subtle changes to your current color, while colors towards the bottom will be much closer to the palette color of that channel."
msgid "Limiting the number of colors we use and then mixing tends to give a more cohesive palette, as we're not trying to do too much at once. This cohesive palette in turn means it will become easier to create a certain mood in an image. Sometimes, mixing in a little bit of accent color can also create unexpected results which in turn can be a little discovery for the audience to delight over as they discover the world of your image."
msgid "What we can learn from this, is that the next time we select, say, gray, instead of reaching for a random or generic gray from the Advanced Color Selector, consider using one of Krita's many wonderful mixing tools to create an interesting and fitting gray from hues that are roughly complementary (opposite each other on the hue wheel)."
msgid "While on-canvas and off-canvas techniques are fundamentally different categories of mixing colors, they are not mutually exclusive. All of the mixing methods in this article have pros and cons; different tools can be useful for different situations, and combining various techniques can be extremely powerful and fun!"
msgid "Finally, mixing colors will often go far better in a :ref:`higher bit-depth like 16bit <bit_depth>`, though it'll make the image take up much more working **memory** (RAM). Furthermore, using a :ref:`linear color space <linear_and_gamma>` can often give far better mixtures than a **gamma-corrected** one, though doing sketches and line art is easier to do in a gamma-corrected space."
msgid "Now, the situation we talk about when talking theory is what we would call 'linear'. Each step of brightness is the same value. Our eyes do not perceive linearly. Rather, we find it more easy to distinguish between darker grays than we do between lighter grays."
msgid "As humans are the ones using computers, we have made it so that computers will give more room to darker values in the coordinate system of the image. We call this 'gamma-encoding', because it is applying a gamma function to the TRC or transfer function of an image. The TRC in this case being the Tone Response Curve or Tone Reproduction Curve or Transfer function (because color management specialists hate themselves), which tells your computer or printer how much color corresponds to a certain value."
msgid "One of the most common issues people have with Krita's color management is the assigning of the right colorspace to the encoded TRC. Above, the center Pepper is the right one, where the encoded and assigned TRC are the same. To the left we have a Pepper encoded in sRGB, but assigned a linear profile, and to the right we have a Pepper encoded with a linear TRC and assigned an sRGB TRC. Image from `Pepper & Carrot <https://www.peppercarrot.com/>`_."
msgid "The following table shows how there's a lot of space being used by lighter values in a linear space compared to the default sRGB TRC of our modern computers and other TRCs available in our delivered profiles:"
-msgid "If you look at linear of rec 709 TRCs, you can see there's quite a jump between the darker shades and the lighter shades, while if we look at the Lab L* TRC or the sRGB TRC, which seem more evenly spaced. This is due to our eyes' sensitivity to darker values. This also means that if you do not have enough bit depth, an image in a linear space will look as if it has ugly banding. Hence why, when we make images for viewing on a screen, we always use something like the LAB L\\*, sRGB or Gamma 2.2 TRCs to encode the image with."
+msgid "If you look at linear of Rec. 709 TRCs, you can see there's quite a jump between the darker shades and the lighter shades, while if we look at the Lab L* TRC or the sRGB TRC, which seem more evenly spaced. This is due to our eyes' sensitivity to darker values. This also means that if you do not have enough bit depth, an image in a linear space will look as if it has ugly banding. Hence why, when we make images for viewing on a screen, we always use something like the Lab L\\*, sRGB or Gamma 2.2 TRCs to encode the image with."
msgid "Colored circles, half blurred. In a gamma-corrected environment, this gives an odd black border. In a linear environment, this gives us a nice gradation."
msgid "That's right, the 'muddying' of colors as is a common complaint by digital painters everywhere, is in fact, a gamma-corrected colorspace mucking up your colors. If you had been working in LAB to avoid this, be sure to try out a linear rgb color space."
msgid "And this is why color mixtures are lighter and softer in linear space. Linear space is more physically correct, but sRGB is more efficient in terms of space, so hence why many images have an sRGB TRC encoded into them. In case this still doesn't make sense: *sRGB gives largely* **darker** *values than linear space for the same coordinates*."
-msgid "So different TRCs give different mixes between colors, in the following example, every set of gradients is in order a mix using linear TRC, a mix using sRGB TRC and a mix using LAB L* TRC."
+msgid "So different TRCs give different mixes between colors, in the following example, every set of gradients is in order a mix using linear TRC, a mix using sRGB TRC and a mix using Lab L* TRC."
msgid "So, you might be asking, how do I tick this option? Is it in the settings somewhere? The answer is that we have several ICC profiles that can be used for this kind of work:"
msgid "In fact, in all the 'elle'-profiles, the last number indicates the gamma. 1.0 is linear, higher is gamma-corrected and 'srgbtrc' is a special gamma correction for the original sRGB profile."
msgid "If you use the color space browser, you can tell the TRC from the 'estimated gamma'(if it's 1.0, it's linear), or from the TRC widget in Krita 3.0, which looks exactly like the curve graphs above."
msgid "Even if you do not paint much, but are for example making textures for a videogame or rendering, using a linear space is very beneficial and will speed up the renderer a little, for it won't have to convert images on its own."
msgid "The downside of linear space is of course that white seems very overpowered when mixing with black, because in a linear space, light grays get more room. In the end, while linear space is physically correct, and a boon to work in when you are dealing with physically correct renderers for videogames and raytracing, Krita is a tool and no-one will hunt you down for preferring the dark mixing of the sRGB TRC."
msgid "So to make it simple, a color profile is just a file defining a set of colors inside a pure XYZ color cube. This \"color set\" can be used to define different things:"
msgid "Choosing the right workspace profile to use depends on how much colors you need and on the bit depth you plan to use. Imagine a line with the whole color spectrum from pure black (0,0,0) to pure blue (0,0,1) in a pure XYZ color cube. If you divide it choosing steps at a regular interval, you get what is called a linear profile, with a gamma=1 curve represented as a straight line from 0 to 1. With 8bit/channel bit depth, we have only 256 values to store this whole line. If we use a linear profile as described above to define those color values, we will miss some important visible color change steps and have a big number of values looking the same (leading to posterization effect)."
-msgid "This is why was created the sRGB profile to fit more different colors in this limited amount of values, in a perceptually regular grading, by applying a custom gamma curve (see picture here: http://en.wikipedia.org/wiki/SRGB) to emulate the standard response curve of old CRT screens. So sRGB profile is optimized to fit all colors that most common screen can reproduce in those 256 values per R/G/B channels. Some other profiles like Adobe RGB are optimized to fit more printable colors in this limited range, primarily extending cyan-green hues. Working with such profile can be useful to improve print results, but is dangerous if not used with a properly profiled and/or calibrated good display. Most common CMYK workspace profile can usually fit all their colors within 8bit/channel depth, but they are all so different and specific that it's usually better to work with a regular RGB workspace first and then convert the output to the appropriate CMYK profile."
+msgid "This is why was created the sRGB profile to fit more different colors in this limited amount of values, in a perceptually regular grading, by applying a custom gamma curve (see picture here: https://en.wikipedia.org/wiki/SRGB) to emulate the standard response curve of old CRT screens. So sRGB profile is optimized to fit all colors that most common screen can reproduce in those 256 values per R/G/B channels. Some other profiles like Adobe RGB are optimized to fit more printable colors in this limited range, primarily extending cyan-green hues. Working with such profile can be useful to improve print results, but is dangerous if not used with a properly profiled and/or calibrated good display. Most common CMYK workspace profile can usually fit all their colors within 8bit/channel depth, but they are all so different and specific that it's usually better to work with a regular RGB workspace first and then convert the output to the appropriate CMYK profile."
msgid "Starting with 16bit/channel, we already have 65536 values instead of 256, so we can use workspace profiles with higher gamut range like Wide-gamut RGB or Pro-photo RGB, or even unlimited gamut like scRGB."
msgid "But sRGB being a generic profile (even more as it comes from old CRT specifications...), there are big chances that your monitor have actually a different color response curve, and so color profile. So when you are using sRGB workspace and have a proper screen profile loaded (see next point), Krita knows that the colors the file contains are within the sRGB color space, and converts those sRGB values to corresponding color values from your monitor profile to display the canvas."
msgid "read the embed profile to know the \"good\" color values from the file (which most software do nowadays; when they don't they usually default to sRGB, so in the case described here we're safe )"
msgid "and then convert it to the profile associated to the monitor (which very few software actually does, and just output to sRGB.. so this can explain some viewing differences most of the time)."
msgid "The most important one is the one of your own screen. It doesn't come bundled, and you have to make it with a color profiling device. In case you don't have access to such a device, you can't make use of Krita's color management as intended. However, Krita does allow the luxury of picking any of the other bundled profiles as working spaces."
msgid "Profiling devices, called Colorimeters, are tiny little cameras of a kind that you connect to your computer via an usb, and then you run a profiling software (often delivered alongside of the device)."
msgid "If you don't have software packaged with your colorimeter, or are unhappy with the results, we recommend `ArgyllCMS <https://www.argyllcms.com/>`_."
msgid "The little camera then measures what the brightest red, green, blue, white and black are like on your screen using a predefined white as base. It also measures how gray the color gray is."
msgid "It's recommended not to change the \"calibration\" (contrast, brightness, you know the menu) of your screen after profiling. Doing so makes the profile useless, as the qualities of the screen change significantly while calibrating."
msgid "Just profiling your screen means measuring the colors of your monitor with its native settings and put those values in a color profile, which can be used by color-managed application to adapt source colors to the screen for optimal result. Calibrating and profiling means the same except that first you try to calibrate the screen colors to match a certain standard setting like sRGB or other more specific profiles. Calibrating is done first with hardware controls (lightness, contrast, gamma curves), and then with software that creates a vcgt (video card gamma table) to load in the GPU."
msgid "You will get just a subset of actual sRGB, and miss lot of details, or even have hue shifts. Trying to calibrate it before profiling can help to get closer to full-sRGB colors."
msgid "When using several monitors, and specially in mirror mode where both monitor have the same content, you can't have this content color-managed for both screen profiles. In such case, calibrating both screens to match sRGB profile (or another standard for high-end monitors if they both support it) can be a good solution."
msgid "When you need to match an exact rendering context for soft-proofing, calibrating can help getting closer to the expected result. Though switching through several monitor calibration and profiles should be done extremely carefully."
msgid "Previously referred to as HDR painting and Scene Referred painting, Scene Linear Painting is doing digital painting in a peculiar type of colorspace. It is painting in a color space that is..."
msgid "Linear - there’s no gamma encoding, or tone-mapping or whatever going on with the pixels you manipulate. (This is different from the pixels you see, but we’ll get to that later)"
msgid "These are the two important characteristics. The colorspace has a few more properties than this, such as the white point, or more importantly, the colorants that make up the gamut. But here’s the thing, those two could be anything, as long as the space is linear and the color depth is floating point."
-msgid "So, *Scene Linear is not a single one colorspace, but a* **TYPE** *of colorspace*. You can have a scene linear space that uses the sRGB/rec 709 colorants, or one that uses adobeRGB, or maybe one that uses rec 2020, as long as it is *linear* and in a *floating point bit depth*."
+msgid "So, *Scene Linear is not a single one colorspace, but a* **TYPE** *of colorspace*. You can have a scene linear space that uses the sRGB/Rec. 709 colorants, or one that uses adobeRGB, or maybe one that uses Rec. 2020, as long as it is *linear* and in a *floating point bit depth*."
-msgid "If you want to create images for display on an HDR canvas, you will need to select the rec 2020 space profile with a linear gamma. The default profile in Krita for that is :guilabel:`Rec2020-elle-V4-g10.icc`."
+msgid "If you want to create images for display on an HDR canvas, you will need to select the Rec. 2020 space profile with a linear gamma. The default profile in Krita for that is :guilabel:`Rec2020-elle-V4-g10.icc`."
msgid "These two factors are for one reason: To make black and white arbitrary values. This might seem a bit weird. But when you are dealing with light-sources, you are dealing with a massive range of contrasts, and will have to decide afterwards which white and black you’d like to have. This is what the scene means in scene-linear, the relevant values are unique per scene, like a real world scene: a flower field lit by moonlight, a city in twilight or a sunny beach. You want to be able to put the right emphasis on the most important contrasting values, and being able to choose what is white and what is black is a very powerful tool here. After all, humans in the real world can see much more when they get used to the dark, or to the sun, so why not apply that to how we make our images?"
msgid "This is also why it needs to be Linear. Gamma and Tone-mapped color spaces are already choosing which contrast is the most important to you. But for that, they too need to choose what is white or black. Linear doesn’t make such assumptions, so much better for when you want to choose yourself. You will eventually want to stick your image through some tone-mapping or gamma correction, but only at the end after you have applied filters and mixed colors!"
msgid "In fact, there’s always a non-destructive sort of transform going on while you are working on your image which includes the tone-mapping. This is called a display or view transform, and they provide a sort of set of binoculars into the world of your image. Without it, your computer cannot show these colors properly; it doesn’t know how to interpret it properly, often making the image too dark. Providing such a transform and allowing you to configure it is the prime function of color management."
msgid "Between different view and display transforms, there’s also a difference in types. Some are really naive, others are more sophisticated, and some need to be used in a certain manner to work properly. The ICC color management can only give a certain type of view transforms, while OCIO color management in the LUT docker can give much more complex transforms easily configurable and custom settings that can be shared between programs."
msgid "Above, an example of the more naive transform provided by going from scene-linear sRGB to regular sRGB, and to the right a more sophisticated transform coming from the filmic blender OCIO configuration. Look at the difference between the paws. Image by Wolthera van Hövell tot Westerflier, License: CC-BY-SA"
msgid "Conversely, transforming and interpreting your image’s colors is the only thing OCIO can do, and it can do it with really complex transforms, really fast. It doesn’t understand what your image’s color space is originally, doesn’t understand what CMYK is, and there’s also no such thing as a OCIO color profile. Therefore you will need to switch to an ICC workflow if you wish to prepare for print."
msgid "Simple Blending Modes like Multiply or Addition are suddenly black magic. This is because Scene-Linear is the closest you can get to the physical (as in, physics, not material) model of color where multiplying colors with one another is one of the main ways to calculate the effect of light."
msgid "Combining painting with other image results such as photography and physically based rendering is much easier as they too work in such a type of colorspace. So you could use such images as a reference with little qualms, or make textures that play nice with such a renderer."
msgid "A very simple but massive problem is one with **inversion**. Inverting colors is done code-wise by taking the color for white and subtracting the color you want to invert from it. It’s used in many blending modes. But often the color white is hardcoded in these filters. There’s currently no application out there that allows you to define the value range that inversion is done with, so inverting is useless. And that also means the filters and blending modes that use it, such as (but not limited to)..."
msgid "Conversely Multiply, Linear Dodge/Addition (they’re the same thing), Subtract, Divide, Darker (only compares colors’ channel values), Lighter (ditto), and Difference *are fine to use*, as long as the program you use doesn’t do weird clipping there."
msgid "Another one is HSL, HSI and HSY algorithms. They too need to assume something about the top value to allow scaling to white. HSV doesn’t have this problem. So it’s best to use an HSV color selector."
-msgid "For the blending modes that use HSY, there’s always the issue that they tend to be hardcoded to sRGB/Rec709 values, but are otherwise fine (and they give actually far more correct results in a linear space). So these are not a good idea to use with wide-gamut colorspaces, and due to the assumption about black and white, not with scene linear painting. The following blending modes use them:"
+msgid "For the blending modes that use HSY, there’s always the issue that they tend to be hardcoded to sRGB/Rec. 709 values, but are otherwise fine (and they give actually far more correct results in a linear space). So these are not a good idea to use with wide-gamut colorspaces, and due to the assumption about black and white, not with scene linear painting. The following blending modes use them:"
msgid "So that is the blending modes. Many filters suffer from similar issues, and in many applications, filters aren’t adjusted to work with arbitrary whites."
msgid "Speaking of filters, when using the transform tool, you should also avoid using lanczos3, it’ll give a weird black halo to sharp contrasts in scene-linear. The bilinear interpolation filter will work just fine in this case."
msgid "If you have mixed pigments before, you will know that black can quite easily overpower the other colors, so you should only add the tiniest amount of it to a mixture. White in contrast gets dirtied quite easily."
msgid "In a Scene Linear Color space, this is flipped. White is now more overpowering and black gets washed out super quickly. This relates to the additive nature of digital color theory, that becomes more obvious when working in linear."
msgid "Sketch on a mid-gray background. This is recommended anyway, as it serves as a neutral backdrop. For a linear space, 18% or 22% gray would be a good neutral."
msgid "16 bit float per channel images are big. 32 bit float per channel images are bigger. This means that they will eat RAM and that painting and filtering will be slower. This is something that will fix itself over the years, but not many people have such a high-end PC yet, so it can be a blocker."
msgid "Scene Linear Painting is painting an image in a color space that is linear and has a floating point bit depth. This does not assume anything about the values of black and white, so you can only use tools that don’t assume anything about the values of black and white. It has the advantage of having nicer filter results and better color mixtures as well as better interoperability with other scene-linear output."
-msgid "To be able to view such an image you use a view transform, also called a display conversion. Which means that if you wish to finalize your image for the web, you make a copy of the image that goes through a display conversion or view transform that then gets saved to png or jpeg or tiff."
+msgid "To be able to view such an image you use a view transform, also called a display conversion. Which means that if you wish to finalize your image for the web, you make a copy of the image that goes through a display conversion or view transform that then gets saved to PNG, JPEG or TIFF."
-msgid "Select either a 16bit or 32bit image. By default Krita will select a linear sRGB profile. If you want to create images for HDR display, you will need to make sure that the profile selected is the :guilabel:`Rec2020-elle-V4-g10.icc` profile. HDR images are standardised to use the rec 2020 gamut, which is much larger than sRGB in size, so this ensures you've got access to all the colors."
+msgid "Select either a 16bit or 32bit image. By default Krita will select a linear sRGB profile. If you want to create images for HDR display, you will need to make sure that the profile selected is the :guilabel:`Rec2020-elle-V4-g10.icc` profile. HDR images are standardised to use the Rec. 2020 gamut, which is much larger than sRGB in size, so this ensures you've got access to all the colors."
msgid "Keep in mind everything mentioned above. Not all filters and not all blending modes work. This will improve in the future. Other than that, everything else is the same."
msgid "Picking regular colors is easy, but how do we pick the really bright colors? There are three ways of getting access to the really bright colors in Krita:"
msgid "By lowering the exposure in the LUT docker. This will increase the visible range of colors in the color selectors. You can even hotkey the exposure in the canvas input settings."
-msgid "Or simply by opening the internal color selector by double clicking the dual color button and typing in values higher than 1 into the field."
+msgid "Or simply by opening the internal color selector by double clicking the dual color button and typing in values higher than 1 into the input field."
-msgid "Then paint. It’s recommended to make a bunch of swatches in the corner, at the least, until Krita’s new palette docker allows you to save the values properly."
+msgid "Then paint. It’s recommended to make a bunch of swatches in the corner, at the least, until Krita’s new Palette docker allows you to save the values properly."
msgid "So, we have our typical value based workflow, where we only paint the grays of the image so that we can focus on the values of the image. We can do something similar with Scene Linear Painting."
-msgid "Where with the value based workflow you paint the image as if it were a grayscale of what you intended to paint, with a lighting based workflow you paint as if all the objects are white. The effect of the color of an object can be determined by multiplying its base color with the color of the light. So you could paint objects as if they were white, paint the colors on a separate layer and just use the multiply blending mode to get the right colors."
+msgid "Where with the value based workflow you paint the image as if it were a grayscale of what you intended to paint, with a lighting based workflow you paint as if all the objects are white. The effect of the color of an object can be determined by multiplying its base color with the color of the light. So you could paint objects as if they were white, paint the colors on a separate layer and just use the Multiply blending mode to get the right colors."
msgid "The leftmost image is both the lighting based one and the color layer separate, the middle with the two layers multiplied and the right a luminosity based view. This cat is a nice example as it demonstrates why having textures and lighting separate could be interesting."
msgid "You can even combine this with a value based workflow by opening a new view and setting the component to luminosity. That way you can see both the grayscale as well as the lighting based version of the image next to one another."
msgid "The keen minded will notice that a lighting based workflow kind of resembles the idea of a light pass and a color pass in 3d rendering. And indeed, it is basically the same, so you can use lighting passes from 3d renders here, just save them as EXR and import them as a layer. One of the examples where scene linear painting simplifies combining methods."
-msgid "When you are done, you will want to apply the view transform you have been using to the image (at the least, if you want to post the end result on the internet)... This is called LUT baking and not possible yet in Krita. Therefore you will have to save out your image in EXR and open it in either Blender or Natron. Then, in Blender it is enough to just use the same OCIO config, select the right values and save the result as a png."
+msgid "When you are done, you will want to apply the view transform you have been using to the image (at the least, if you want to post the end result on the Internet)... This is called LUT baking and not possible yet in Krita. Therefore you will have to save out your image in EXR and open it in either Blender or Natron. Then, in Blender it is enough to just use the same OCIO config, select the right values and save the result as a PNG."
msgid "You can even use some of Blender’s or Natron’s filters at this stage, and when working with others, you would save out in EXR so that others can use those."
msgid "Because our cube is red on both front-sides, and blue on both left and right side, we can just use copies, this simplifies the method for cubes a lot. We call this form of axonometric projection 'dimetric' as it deforms two parallel lines equally."
msgid "(as you can see, it doesn't line up perfectly, because Inkscape, while more designed for making these kinds of diagrams than Krita, doesn't have tools to manipulate the line's angle in degrees)"
msgid "This is a bit of an awkward angle, and on top of that, it doesn't line up with pixels sensibly, so for videogames an angle of 30° from the ground plane is used."
-msgid "On the vector layer, we select the straight line tool, start a line and then hold :kbd:`Shift` to make it snap to angles. This'll allow us to make a 30° setup like above:"
+msgid "On the vector layer, we select the straight line tool, start a line and then hold the :kbd:`Shift` key to make it snap to angles. This'll allow us to make a 30° setup like above:"
msgid "Then crop it by setting the crop tool to :guilabel:`Layer`, and use :menuselection:`Filters --> Colors --> Color to alpha` to remove any background. I also set the layers to 50% opacity. We then align the vectors to them:"
-msgid "To resize a vector but keep its angle, you just select it with the shape handling tool (the white arrow) drag on the corners of the bounding box to start moving them, and then press :kbd:`Shift` to constrain the ratio. This'll allow you to keep the angle."
+msgid "To resize a vector but keep its angle, you just select it with the shape handling tool (the white arrow) drag on the corners of the bounding box to start moving them, and then press the :kbd:`Shift` key to constrain the ratio. This'll allow you to keep the angle."
msgid "Our rectangle we'll be working in slowly becomes visible. Now, this is a bit of a difficult angle to work at, so we go to :menuselection:`Image --> Rotate --> Rotate Image` and fill in 30° clockwise:"
msgid "So the idea here is that you draw parallel lines from both sides to find points in the drawing area. You can use the previews of the assistants for this to keep things clean, but I drew the lines anyway for your convenience."
msgid "Our game-safe isometric has its angle at two pixels horizontal is one pixel vertical. So, we shear the ortho graphics with transform masks to -.5/+.5 pixels (this is proportional)"
msgid "That's because there are less steps involved as the previous version -- We're deriving our image directly from the orthographic view -- so there are less errors involved."
msgid "The creepiness is because we've had the tiniest bit of stylisation in our side view, so the eyes come out HUGE. This is because when we stylize the side view of an eye, we tend to draw it not perfectly from the side, but rather slightly at an angle. If you look carefully at the turntable, the same problem crops up there as well."
msgid "It still feels very squashed compared to the regular parallel projection above, and it might be an idea to not just skew but also stretch the orthos a bit."
msgid "Despite the fancy name, you probably know what orthographic is. It is a schematic representation of an object, draw undeformed. Like the following example:"
msgid "While orthographic representations are kinda boring, they're also a good basis to start with when you find yourself in trouble with a pose. But we'll get to that in a bit."
msgid "So, if we can say that the front view is the viewer looking at the front, and the side view is the viewer directly looking at the side. (The perpendicular line being the view plane it is projected on)"
msgid "But cubes are boring. I am suspecting that projection is so ignored because no tutorial applies it to an object where you actually might NEED projection. Like a face."
-msgid "I always start with the side, and then extrapolate the front view from it. Because you are using Krita, set up two parallel rulers, one vertical and the other horizontal. To snap them perfectly, drag one of the nodes after you have made the ruler, and press :kbd:`Shift` to snap it horizontal or vertical. In 3.0, you can also snap them to the image borders if you have :menuselection:`Snap Image Bounds` active via :kbd:`Shift` + :kbd:`S`"
+msgid "I always start with the side, and then extrapolate the front view from it. Because you are using Krita, set up two parallel rulers, one vertical and the other horizontal. To snap them perfectly, drag one of the nodes after you have made the ruler, and press the :kbd:`Shift` key to snap it horizontal or vertical. In 3.0, you can also snap them to the image borders if you have :menuselection:`Snap Image Bounds` active via the :kbd:`Shift + S` shortcut."
msgid "Then, by moving the mirror to the left, you can design a front view from the side view, while the parallel preview line helps you with aligning the eyes (which in the above screenshot are too low)."
msgid "The top view works as a method for debugging your orthos as well. If we take the red line to figure out the orthographics from, we see that our eyes are obviously too inset. Let's move them a bit more forward, to around the nose."
msgid "If you want to do precision position moving in the tool options docker, just select 'position' and the input box for the X. Pressing down then moves the transformed selection left. With Krita 3.0 you can just use the move tool for this and the arrow keys. Using transform here can be more convenient if you also have to squash and stretch an eye."
msgid "For faces, the multiple slices are actually pretty important. So important even, that I have decided we should have these slices on separate layers. Thankfully, I chose to color them, so all we need to do is go to :menuselection:`Layer --> Split Layer` ."
msgid "Krita can't animate a transformation on multiple layers on multiple frames yet, so let's just only transform the top layer. Add a semi-transparent layer where we draw the guidelines."
msgid "Now, select frame 11 (halfway), add new frames from front view, side view and the guidelines. And turn on the onion skin by toggling the lamp symbols. We copy the frame for the top view and use the transform tool to rotate it 45°."
msgid "While it is not necessary to follow all the steps in the theory section to understand the tutorial, I do recommend making a turn table sometime. It teaches you a lot about drawing 3/4th faces."
msgid "Convex lenses, as this lovely image from `wikipedia <https://en.wikipedia.org/wiki/Lens_%28optics%29>`_ shows us, have the ability to turn parallel lightrays into converging ones."
msgid "The point where all the rays come together is called the focal point, and the vanishing point in a 2d drawing is related to it as it’s the expression of the maximum distortion that can be given to two parallel lines as they’re skewed toward the focal point."
msgid "As you can see from the image, the focal point is not an end-point of the rays. Rather, it is where the rays cross before diverging again… The only difference is that the resulting image will be inverted. Even in our eyes this inversion happens, but our brains are used to this awkwardness since childhood and turn it around automatically."
msgid "That went pretty well. As you can see we sorta ‘merged’ the two sides into one (resulting into the purple side square) so we had an easier time projecting. The projection is limited to one or two vanishing point type projection, so only the horizontal lines get distorted. We can also distort the vertical lines"
msgid "We’ll be using a single vanishing point for our focal point. A guide line will be there for the projection plane, and we’re setting up horizontal and vertical parallel rules to easily draw the straight lines from the view plane to where they intersect."
msgid "Yes, actually. The benefit that 2d art still has over 3d is that it's plain faster for single images, especially with complicated subjects like faces and bodies."
msgid "Perspective projection can help a lot getting down those annoying poses, like people lying down. It also helps when combining 2d and 3d, as when you know where the camera is in the 3d render, you can use that in a projection to get the character projected."
msgid "The side view of a person lying down is often easy to draw, but the top view or the view from the feet isn’t. Hence why we use the side view to do perspective projection on."
msgid "Now, with this one we have a second vanishing point above the front-view. It should be about the same distance above the front-view as it is above the head of the rotated side-view. The projection plane should also be the same distance from the vanishing point, but that doesn’t mean it has to be behind. This is something I avoided in the earlier examples, because it makes the working field really messy, but if you look up perspective projection you’ll see multiple examples of this method."
msgid "Also of note is that you actually should be having the view plane/projection plane perfectly perpendicular to the angle of the focal point, otherwise you get odd distortion, this doesn’t happen here, which means this sitting person is a bit more stretched vertically than necessary."
msgid "Here you can see that the misalignment of the vanishing point to the projection plane causes skewing which was then fixed by Krita’s transform tools, technically it’s of course correct, but what is correct doesn’t always look good. (I also mess up the position of the shoulder for a good while if you look closely.)"
msgid "I probably didn’t make as nice result images as I could have, especially if you compare it to the 3d images. However, you can still see that the main landmarks are there. The real use of this technique lies in poses though, and it allows you to iterate on a pose quite quickly once you get the hang of it."
-msgid "Mathematically robust blending mode for normal maps, using `Reoriented Normal Map Blending <http://blog.selfshadow.com/publications/blending-in-detail/>`_."
+msgid "Mathematically robust blending mode for normal maps, using `Reoriented Normal Map Blending <https://blog.selfshadow.com/publications/blending-in-detail/>`_."
msgid "This is a blending mode that will just copy/blend a source channel to a destination channel. Specifically, it will take the specific channel from the upper layer and copy that over to the lower layers."
msgid "This can also be done with filter layers. So if you quickly want to flip a layer's green channel, make an invert filter layer with 'copy green' above it."
msgid "The clone brush is a brush engine that allows you to paint with a duplication of a section of a paint-layer. This is useful in manipulation of photos and textures. You have to select a source and then you can paint to copy or clone the source to a different area. Other applications normally have a separate tool for this, Krita has a brush engine for this."
-msgid "The clone tool can now clone from the projection and it's possible to change the clone source layer. Press :kbd:`Ctrl + Alt +` |mouseleft| to select a new clone source on the current layer. :kbd:`Ctrl +` |mouseleft| to select a new clone source point on the layer that was active when you selected the clone op."
+msgid "The clone tool can now clone from the projection and it's possible to change the clone source layer. Press the :kbd:`Ctrl + Alt +` |mouseleft| shortcut to select a new clone source on the current layer. The :kbd:`Ctrl +` |mouseleft| shortcut to select a new clone source point on the layer that was active when you selected the clone op."
msgid "This will reset the source point everytime you make a new stroke. So if you were cloning a part in one stroke, having this active will allow you to clone the same part again in a single stroke, instead of using the source point as a permanent offset."
msgid "How much of the foreground color is added to the smudging mix. Works together with :ref:`option_smudge_length` and :ref:`option_smudge_radius`."
msgid "Affects how much the smudge length takes from the previous dab its sampling. This means that smudge-length at 1.0 will never decrease, but smudge-lengths under that will decrease based on spacing and opacity/flow."
msgid "Spacing with Smearing: the lower the spacing, the smoother the effect, so for smearing with a round brush you may prefer a value of 0.05 or less. Spacing affects the length of the smudge trail, but to a much lesser extent. The \"strength\" of the effect remains more or less the same however."
msgid "Spacing with Dulling: the lower the spacing, the stronger the effect: lowering the spacing too much can make the dulling effect too strong (it picks up a color and never lets go of it). The length of the effect is also affected."
msgid "Both Smearing and Dulling have a \"smudge trail\", but in the case of Dulling, the brush shape is preserved. Instead the trail determines how fast the color it picked up is dropped off."
msgid "Just remember that the smudge effects are weaker when a brush tip's opacity is lower, so for low-opacity brush tips, increase the opacity and smudge/color rates."
msgid "However, because of the Smudge effects, the outcome will be different from the Pixel Brush. In particular, the Scatter option becomes much more significant."
msgid "Scattering is proportional to the brush size. It's fine to use a scattering of 5.00 for a tiny round brush, but for bigger brushes, you may want to get it down to 0.50 or less."
msgid "Gradient is equivalent to the :menuselection:`Source --> Gradient` and :menuselection:`Color --> Mix` for the Pixel brush: the color will vary between the colors of the gradient."
msgid "By default, the Color Smudge Brush only takes information from the layer it is on. However, if you want it to take color information from all the layers, you can turn on the Overlay mode."
msgid "Be aware though, that it does so by \"picking up\" bits of the layer underneath, which may mess up your drawing if you later make changes to the layer underneath."
msgid "When using lower opacity brush tips, remember to \"compensate\" for the less visible effects by increasing both :guilabel:`Smudge Rate` and :guilabel:`Opacity`, if necessary to maximum."
msgid "For smoother smearing, decrease spacing. Remember that spacing is proportional to brush tip size. For a small round brush, 0.10 spacing is fine, but for mid-sized and large brushes, decrease spacing to 0.05 or less."
msgid "Lowering the spacing will also make the smudging effect stronger, so find a right balance. 0.10 for most mid-sized round brushes should be fine."
msgid "Unlike Smearing, Dulling preserves the brush shape and size, so it won't \"fade off\" in size like Smearing brushes do. You can mimic that effect through the simple size fade dynamic."
msgid "Optional: Pile on size and other dynamics and vary brush tips. In fact, the Color Smudge brush is not a blur brush, so smudging is not a very good method of \"smooth\" blending. To blend smoothly, you'll have better luck with:"
msgid "Shading on a separate layer, possibly making use of alpha-inheritance. The brush blends with the transparency of the layer it's on. This means:"
msgid "Shading on a separate layer, using Overlay mode. Use this only if you're fairly sure you don't need to adjust the layer below, or the colors may become a mess."
msgid "The Color Smudge Brush blends with transparency. What this means is that when you start a new, transparent layer and \"paint\" on this layer, you will nearly always get less than full opacity."
msgid "For the last solution, use colors that contrast highly with what you're using for best effect. For example, shade in the darkest shadow area first, or the lightest highlights, and use the color smudge brush for the contrasting color."
msgid "Many of the included color smudge brush presets produce a thick oil paint-like effect. This is mainly achieved with the Smearing mode on. Basically:"
msgid "One thing I really like to do is to set different foreground and background colors, then turn on :menuselection:`Gradient --> Fuzzy`. Alternatively, just paint with different colors in succession (bottom-right example)."
msgid "Here's some final random stuff. With pixel brushes, you can get all sorts of frill designs by using elongated brushes and setting the dynamics to rotation. You won't get that with Color Smudge Brushes. Instead you'll get something that looks more like... yarn. Which is cool too. Here, I just used oval brushes and :menuselection:`Rotation --> Distance`."
msgid "When I say \"digital watercolor\", it refers to a style often seen online, i.e. a soft, smooth shading style rather than realistic watercolor. For this you mostly need the Dulling mode. A few things:"
msgid "There are various sections in this dialog box which aid in creation of new document, either using custom document properties or by using contents from clipboard and templates. Following are the sections in this dialog box:"
msgid "From this section you can create a document according to your requirements: you can specify the dimensions, color model, bit depth, resolution, etc."
msgid "In the top-most field of the :guilabel:`Dimensions` tab, from the Predefined drop-down you can select predefined pixel sizes and PPI (pixels per inch). You can also set custom dimensions and the orientation of the document from the input fields below the predefined drop-down. This can also be saved as a new predefined preset for your future use by giving a name in the Save As field and clicking on the Save button. Below we find the Color section of the new document dialog box, where you can select the color model and the bit-depth. Check :ref:`general_concept_color` for more detailed information regarding color."
msgid "On the :guilabel:`Content` tab, you can define a name for your new document. This name will appear in the metadata of the file, and Krita will use it for the auto-save functionality as well. If you leave it empty, the document will be referred to as 'Unnamed' by default. You can select the background color and the amount of layers you want in the new document. Krita remembers the amount of layers you picked last time, so be careful."
msgid "This section allows you to create a document from an image that is in your clipboard, like a screenshot. It will have all the fields set to match the clipboard image."
msgid "These are separate categories where we deliver special defaults. Templates are just .kra files which are saved in a special location, so they can be pulled up by Krita quickly. You can make your own template file from any .kra file, by using :menuselection:`File --> Create Template From Image` in the top menu. This will add your current document as a new template, including all its properties along with the layers and layer contents."
msgid "Once you have created a new document according to your preference, you should now have a white canvas in front of you (or whichever background color you chose in the dialog)."
msgid "As compared to other color selectors in Krita, Advanced color selector provides more control and options to the user. To open Advanced color selector choose :menuselection:`Settings --> Dockers --> Advanced Color Selector`. You can configure this docker by clicking on the little wrench icon on the top left corner. Clicking on the wrench will open a popup window with following tabs and options:"
msgid "Stands for Hue, Saturation, Value. Saturation determines the difference between white, gray, black and the most colorful color. Value in turn measures either the difference between black and white, or the difference between black and the most colorful color."
msgid "This stands for Hue, Saturation and Intensity. Unlike HSL, this one determine the intensity as the sum of total rgb components. Yellow (1,1,0) has higher intensity than blue (0,0,1) but is the same intensity as cyan (0,1,1)."
-msgid "Stands for Hue, Saturation, Luma, with Luma being an RGB approximation of true luminosity. (Luminosity being the measurement of relative lightness). HSY' uses the Luma Coefficients, like `Rec 709 <http://en.wikipedia.org/wiki/Rec._709>`_, to calculate the Luma. Due to this, HSY' can be the most intuitive selector to work with, or the most confusing."
+msgid "Stands for Hue, Saturation, Luma, with Luma being an RGB approximation of true luminosity. (Luminosity being the measurement of relative lightness). HSY' uses the Luma Coefficients, like `Rec. 709 <https://en.wikipedia.org/wiki/Rec._709>`_, to calculate the Luma. Due to this, HSY' can be the most intuitive selector to work with, or the most confusing."
msgid "Triangle is in all color models because to a certain extent, it is a wildcard shape: All color models look the same in an equilateral triangle selector."
-msgid "This allows you to edit the Luma coefficients for the HSY model selectors to your leisure. Want to use `Rec 601 <http://en.wikipedia.org/wiki/Rec._601>`_ instead of Rec 709? These boxes allow you to do that!"
+msgid "This allows you to edit the Luma coefficients for the HSY model selectors to your leisure. Want to use `Rec. 601 <https://en.wikipedia.org/wiki/Rec._601>`_ instead of Rec. 709? These boxes allow you to do that!"
msgid "The HSY selector is linearised, this setting allows you to choose how much gamma is applied to the Luminosity for the gui element. 1.0 is fully linear, 2.2 is the default."
msgid "If your have set the docker size considerably smaller to save space, this option might be helpful to you. This allows you to set whether or not the selector will give a zoomed view of the selector in a size specified by you, you have these options for the zoom selector:"
-msgid "The size given here, is also the size of the Main Color Selector and the MyPaint Shade Selector when they are called with :kbd:`Shift + I` and :kbd:`Shift + M`, respectively."
+msgid "The size given here, is also the size of the Main Color Selector and the MyPaint Shade Selector when they are called with the :kbd:`Shift + I` and :kbd:`Shift + M` shortcuts, respectively."
msgid "This allows you to let the pop-up selectors called with the above hotkeys to disappear upon clicking them instead of having to leave the pop-up boundary. This is useful for faster working."
msgid "This is a radio button to show or hide the section. It also determines whether or not the colors are visible with the advanced color selector docker."
msgid "This is only available for Colors From the Image and tells the docker whether to update the section after every stroke or not, as after each stroke the colors will change in the image."
-msgid "The common patches are generated from the image, and are the most common color in the image. The hotkey for them on canvas is :kbd:`U`."
+msgid "The common patches are generated from the image, and are the most common color in the image. The hotkey for them on canvas is the :kbd:`U` key."
msgid "In the gamut masking toolbar at the top of the selector you can toggle the selected mask off and on (left button). You can also rotate the mask with the rotation slider (right)."
msgid "This docker controls the look and the visibility of both the Grid and the Guides decorations. It also features a checkbox to quickly toggle snapping on or off."
msgid "Grids in Krita can currently only be orthogonal and diagonal. There is a single grid per canvas, and it is saved within the document. Thus it can be saved in a :ref:`templates`."
msgid "Groups cells together as larger squares and changes the look of the lines it contains. A subdivision of 2 will make cells appear twice as big, and the inner lines will become subdivisions."
msgid "The grid's base size is 64 pixels. With a subdivision of 2, the main grid lines are 128 px away from one another, and the intermediate lines have a different look."
msgid "To create a guide, move your cursor over a ruler and drag in the direction of the canvas. A line will appear. Dragging from the left ruler creates a vertical guide, and dragging from the top ruler creates a horizontal guide."
msgid "Place your cursor above a guide on the canvas. If the guides are not locked, your cursor will change to a double arrow. In that case, click and drag to move the guide. To lock and unlock the guides, open the Grid and Guides Docker. Ensure that the Guides tab is selected. From here you can lock the guides, enable snapping, and change the line style."
msgid "Currently, it is not possible to create or to move guides to precise positions. The only way to achieve that for now is to zoom in on the canvas, or to use the grid and snapping to place the guide."
msgid "Click on the guide you want to remove and drag it outside of the canvas area. When you release your mouse or stylus, the guide will be removed."
msgid "The Layers docker is for one of the core concepts of Krita: :ref:`Layer Management <layers_and_masks>`. You can add, delete, rename, duplicate and do many other things to layers here."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:24
msgid "The Layer Stack"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:26
-msgid "You can select the active layer here. Using :kbd:`Shift` and :kbd:`Ctrl` you can select multiple layers and drag-and-drop them. You can also change the visibility, edit state, alpha inheritance and rename layers. You can open and close groups, and you can drag and drop layers, either to reorder them, or to put them in groups."
+msgid "You can select the active layer here. Using the :kbd:`Shift` and :kbd:`Ctrl` keys you can select multiple layers and drag-and-drop them. You can also change the visibility, edit state, alpha inheritance and rename layers. You can open and close groups, and you can drag and drop layers, either to reorder them, or to put them in groups."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:28
msgid "Name"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:29
-msgid "The Layer name, just do double- |mouseleft| to make it editable, and press :kbd:`Enter` to finish editing."
+msgid "The Layer name, just do double- |mouseleft| to make it editable, and press the :kbd:`Enter` key to finish editing."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:31
msgid "This is a color that you can set on the layer. |mouseright| the layer to get a context menu to assign a color to it. You can then later filter on these colors."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:33
msgid "This will set the :ref:`blending_modes` of the layer."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:34
msgid "Opacity"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:35
msgid "This will set the opacity of the whole layer."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:36
msgid "Visibility"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:37
msgid "An eye-icon. Clicking this can hide a whole layer."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:38
msgid "Edit State (Or layer Locking)"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:39
msgid "A lock Icon. Clicking this will prevent the layer from being edited, useful when handling large amounts of layers."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:41
msgid "This will prevent the alpha of the layer being edited. In more plain terms: This will prevent the transparency of a layer being changed. Useful in coloring images."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:42
msgid "Pass-through mode"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:43
msgid "Only available on Group Layers, this allows you to have the blending modes of the layers within affect the layers outside the group. Doesn't work with masks currently, therefore these have a strike-through on group layers set to pass-through."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:45
msgid "This will use the alpha of all the peers of this layer as a transparency mask. For a full explanation see :ref:`layers_and_masks`."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:46
msgid "Open or Close Layers"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:47
msgid "(An Arrow Icon) This will allow you to access sub-layers of a layer. Seen with masks and groups."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:49
msgid "This is only available on :ref:`animated layers <animation>`, and toggles the onion skin feature."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:51
msgid "This is only available on layers which have a :ref:`layer_style` assigned. The button allows you to switch between on/off quickly."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:53
-msgid "To edit these properties on multiple layers at once, press the properties option when you have multiple layers selected or press :kbd:`F3`. There, to change the names of all layers, the checkbox before :guilabel:`Name` should be ticked after which you can type in a name. Krita will automatically add a number behind the layer names. You can change other layer properties like visibility, opacity, lock states, etc. too."
+msgid "To edit these properties on multiple layers at once, press the properties option when you have multiple layers selected or press the :kbd:`F3` key. There, to change the names of all layers, the checkbox before :guilabel:`Name` should be ticked after which you can type in a name. Krita will automatically add a number behind the layer names. You can change other layer properties like visibility, opacity, lock states, etc. too."
msgid "These are buttons for doing layer operations."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:63
msgid "Add"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:64
msgid "Will by default add a new Paint Layer, but using the little arrow, you can call a sub-menu with the other layer types."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:65
msgid "Duplicate"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:66
-msgid "Will Duplicate the active layer(s). Can be quickly invoked with :kbd:`Ctrl` + |mouseleft| + drag."
+msgid "Will Duplicate the active layer(s). Can be quickly invoked with the :kbd:`Ctrl +` |mouseleft| :kbd:`+ drag` shortcut."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:67
msgid "Move layer up."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:68
msgid "Will move the active layer up. Will switch them out and in groups when coming across them."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:69
msgid "Move layer down."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:70
msgid "Will move the active layer down. Will switch them out and in groups when coming across them."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:71
msgid "Layer properties."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:72
msgid "Will open the layer properties window."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:74
msgid "Delete"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:74
msgid "Will delete the active layer(s). For safety reasons, you can only delete visible layers."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:77
msgid "Hot keys and Sticky Keys"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:79
-msgid ":kbd:`Shift` for selecting multiple contiguous layers."
+msgid ":kbd:`Shift` key for selecting multiple contiguous layers."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:80
-msgid ":kbd:`Ctrl` for select or deselect layer without affecting other layers selection."
+msgid ":kbd:`Ctrl` key for select or deselect layer without affecting other layers selection."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:81
-msgid ":kbd:`Ctrl` + |mouseleft| + drag - makes a duplicate of the selected layers, for you to drag and drop."
+msgid ":kbd:`Ctrl +` |mouseleft| :kbd:`+ drag` shortcut makes a duplicate of the selected layers, for you to drag and drop."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:82
-msgid ":kbd:`Ctrl + E` for merging a layer down. This also merges selected layers, layer styles and will keep selection masks intact. Using :kbd:`Ctrl + E` on a single layer with a mask will merge down the mask into the layer."
+msgid ":kbd:`Ctrl + E` shortcut for merging a layer down. This also merges selected layers, layer styles and will keep selection masks intact. Using the :kbd:`Ctrl + E` shortcut on a single layer with a mask will merge down the mask into the layer."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:83
-msgid ":kbd:`Ctrl + Shift + E` merges all layers."
+msgid ":kbd:`Ctrl + Shift + E` shortcut merges all layers."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:84
-msgid ":kbd:`R` + |mouseleft| allows you to select layers on canvas, similar to picking colors directly on canvas. Use :kbd:`Shift + R` + |mouseleft| for multiple layers."
+msgid ":kbd:`R +` |mouseleft| shortcut allows you to select layers on canvas, similar to picking colors directly on canvas. Use the :kbd:`Shift + R +` |mouseleft| shortcut for multiple layers."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:85
-msgid ":kbd:`Ins` for adding a new layer."
+msgid ":kbd:`Ins` key for adding a new layer."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:86
-msgid ":kbd:`Ctrl + G` will create a group layer. If multiple layers are selected, they are put into the group layer."
+msgid ":kbd:`Ctrl + G` shortcut will create a group layer. If multiple layers are selected, they are put into the group layer."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:87
-msgid ":kbd:`Ctrl + Shift + G` will quickly set-up a clipping group, with the selected layers added into the group, and a new layer added on top with alpha-inheritance turned on, ready for painting!"
+msgid ":kbd:`Ctrl + Shift + G` shortcut will quickly set-up a clipping group, with the selected layers added into the group, and a new layer added on top with alpha-inheritance turned on, ready for painting!"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:88
-msgid ":kbd:`Ctrl + Alt + G` will ungroup layers inside a group."
+msgid ":kbd:`Ctrl + Alt + G` shortcut will ungroup layers inside a group."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:89
-msgid ":kbd:`Alt` + |mouseleft| for isolated view of a layer. This will maintain between layers till the same action is repeated again."
+msgid ":kbd:`Alt +` |mouseleft| shortcut for isolated view of a layer. This will maintain between layers till the same action is repeated again."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:90
-msgid ":kbd:`Page Up` and :kbd:`Page Down` for switching between layers."
+msgid ":kbd:`Page Up` and :kbd:`Page Down` keys for switching between layers."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/layers.rst:91
-msgid ":kbd:`Ctrl + Page Up` and :kbd:`Ctrl + Page Down` will move the selected layers up and down."
+msgid ":kbd:`Ctrl + Page Up` and :kbd:`Ctrl + Page Down` shortcuts will move the selected layers up and down."
msgid "Use Open Color IO instead of Krita's internal color management. Open Color IO is a color management library. It is sometimes referred to as OCIO. This is required as Krita uses OCIO for its HDR functionality."
msgid "Some system locals don't allow you to read the configuration files. This is due to a bug in OCIO. If you are using Linux you can fix this. If you start Krita from the terminal with the ``LC_ALL=C krita`` flag set, you should be able to read the configuration files."
msgid "This docker allows you to select the global pattern. Using the open-file button you can import patterns. Some common shortcuts are the following:"
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-05-04 09:38+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../<rst_epilog>:2
msgid ""
".. image:: images/icons/Krita_mouse_left.png\n"
" :alt: mouseleft"
msgstr ""
#. +> trunk5
#: ../../<rst_epilog>:4
msgid ""
".. image:: images/icons/Krita_mouse_right.png\n"
" :alt: mouseright"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:1
msgid "Overview of the timeline docker."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:12
msgid "Animation"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:12
msgid "Timeline"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:12
msgid "Frame"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:17
msgid "Timeline Docker"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:19
msgid "The **Timeline Docker** works in tandem with the :ref:`animation_docker` at the heart of :program:`Krita`'s animation tools. While the Animation Docker provides access to the fundamental controls for playing back and editing animations, the Timeline Docker contains the layered frames and specific timings that define your animation. In other words, the Timeline Docker is the digital equivalent to a traditional animator's \"dope sheet\"."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:25
msgid "Legend:"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:27
msgid "**A. Layer List --** This area contains some subset of the layers of your current document. The currently active layer is always shown and can be \"pinned\" to the timeline using the :guilabel:`Show in Timeline` menu action. Also, Layers that are created via the Timeline or added using the :guilabel:`Add Existing Layer` submenu are automatically pinned to the timeline. Each layer has properties that can also be toggled here (visible, locked, show onion skins, etc.)."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:30
msgid "**Active Layer**"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:30
msgid "A highlighted row in the table shows the current active layer. One can change which layer is active by clicking on the layer's name within the left header. It is *not* possible to change the active layer by clicking inside the table in order to not disturb the user when scrubbing and editing frame positions on the timeline."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:32
msgid "**B. Frame Table --** The Frame Table is a large grid of cells which can either hold a single frame or be empty. Each row of the Frame Table represents an *animation layer* and each column represents a *frame timing*. Just like the Layer List, the active layer is highlighted across the entire Frame Table. It's important to understand that frame timings are not based on units of time like seconds, but are based on frames which can then be played back at any speed, depending on the :ref:`animation_docker`'s *frame rate* and *play speed* settings."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:34
-msgid "Frames can be moved around the timeline by simply left-clicking and dragging from one frame to another slot, even across layers. Furthermore, holding :kbd:`Ctrl` while moving creates a copy. Right-clicking anywhere in the Frame Table will bring up a helpful context menu for adding, removing, copying, and pasting frames or adjusting timing with holds."
+msgid "Frames can be moved around the timeline by simply left-clicking and dragging from one frame to another slot, even across layers. Furthermore, holding the :kbd:`Ctrl` key while moving creates a copy. Right-clicking anywhere in the Frame Table will bring up a helpful context menu for adding, removing, copying, and pasting frames or adjusting timing with holds."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:37
msgid "Frames highlighted in orange represent a selection or multiple selections, which can be created by mouse or keyboard. While multiple frames are selected, right-clicking anywhere in the Frame Table will bring up a context menu that will allow for adding or removing frames or holds within the current selection. Finally, it is also possible to have multiple non-contiguous/separate selections if needed."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:41
msgid "**Current Selection:**"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:41
msgid "Painting always happens only in the *active frame* (represented by a small dot), which is not necessarily part of your current selection."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:44
msgid "**Keys, Blanks, and Holds:**"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:44
msgid "The Timeline Docker now shows us even more useful information about both what is there as well as what is not. **Key frames** which contain drawings are still displayed as *filled blocks* within a cell, while **blank** or empty key frames are shown as a *hollow outline*. In Krita, every drawn frame is automatically held until the next frame; these **holds** are now clearly shown with a *colored line* across all held frames. The color of frames can be set per-frame by the animator using the right-click menu, and is a matter of personal workflow."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:46
msgid "**C. Frame Timing Header --** The Frame Timing Header is a ruler at the top of the Frame Table. This header is divided into small notched sections which are based on the current *frame rate* (set in the :ref:`animation_docker`). Integer multiples of the frame rate have a subtle double-line mark, while smaller subdivisions have small single-line marks. Each major notch is marked with a helpful *frame number*."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:49
msgid "**Cached Frames:**"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:49
msgid "The Frame Timing Header also shows important information about which frames are currently *cached*. When something is said to be \"cached\", that means that it is stored in your device's working memory (RAM) for extra fast access. Cached frames are shown by the header with a small light-gray rectangle in each column. While this information isn't always critical for us artists, it's helpful to know that Krita is working behind the curtains to cache our animation frames for the smoothest possible experience when scrubbing through or playing back your animation."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:51
msgid "**D. Current Time Scrubber --** A highlighted column in the Frame Table which controls the current frame time and, as such, what is currently displayed in the viewport."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:54
msgid "A frame of the *active layer* at the *current time* position. The active frame is always marked with a small circle inside. All drawing, painting, and image editing operations happen on this frame only!"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:58
msgid "**Active Frame:**"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:58
msgid "Don't mix the active frame up with the current selection!"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:60
msgid "**E. Layer Menu --** A small menu for manipulating animation layers. You can create new layers, add or remove existing ones, and you can set 'Show in Timeline' here to pin the active layer to the Timeline. (This menu also shows up when right-clicking on layers inside of the Layer List.)"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:62
msgid "**F. Audio Menu:** Another small menu for animating along with audio sources. This is where you can open or close audio sources and control output volume/muting."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:64
msgid "**G. Zoom Handle:** This allows you to zoom in and out on the Frame Table, centered around the current frame time. Click-dragging starting on the zoom handle controls the zoom level."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:67
msgid "Usage:"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:69
msgid "How to use the Timeline Docker is not immediately obvious because :program:`Krita` doesn't automatically create a key frame out of your initial drawing. In fact, *until you make a key frame on a layer*, Krita assumes that there's no animation going on at all on that layer and it will keep the image static over the whole animation."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:71
msgid "So, to make our first *animated layer*, we need to make a key frame!"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:73
msgid "|mouseright| any square on the timeline docker and select :guilabel:`Create Blank Frame`. A blank frame (one that you haven't yet drawn anything in) appears as a *hollow outline* instead of a solid box, making that frame active and drawing on the canvas will make it appear as a *solid, colored rectangle*."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:75
msgid "To keep a layer visible in the Timeline Docker regardless of which layer is selected, select the layer in the Layers Docker so it shows up in the docker, then |mouseright| it within the Timeline Docker's Layer List and select :guilabel:`Show in Timeline`. This way you can choose which layers are important and which are only minor."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:77
msgid "You can drag and drop the frame around to a different empty frame slot."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:79
msgid "To add a single new frame, either right-click on an empty frame slot and select :guilabel:`Create Blank Frame` to create a fresh blank frame, or select :guilabel:`Create Duplicate Frame` to create a new copy of the previous frame."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:81
msgid "You can also change the color of frames so that you can easily identify important frames or distinguish between different sections of your animation. The current color selection is remembered for new frames so that you can easily make a set of colored frames and then switch to another color."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:83
msgid "It's also possible to add multiple key frames by right-clicking inside the Frame Table and selecting :menuselection:`Keyframes --> Insert Multiple Keyframes`. With this option you can specify a number of frames to add with the option of built in timing for quickly creating a series of 1s, 2s, 3s, etc. These settings are saved between uses."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:85
msgid "Instead of the Frame Table, right-clicking within the Frame Timing Header gives you access to a few more options which allow you to add or remove entire columns of frames or holds at a time. For example, selecting :menuselection:`Keyframe Columns --> Insert Keyframe Column Left` will add new frames to each layer that's currently visible in the Timeline Docker."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:90
msgid ":program:`Krita` only tracks key frame changes. This is unlike :program:`Flash` where you have to manually indicate how long a key frame will hold. Instead, :program:`Krita` just assumes that the space between key frame 1 and key frame 2 is supposed to be filled with key frame 1. Frames that are held in this way (a.k.a. \"holds\") are displayed as a continuous line in the Frame Table."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:92
msgid "To delete frames, |mouseright| the frame and press :guilabel:`Remove Keyframe`. This will delete all selected frames. Similarly, selecting :guilabel:`Remove Frame and Pull` will delete the selected frames and pull or shift all subsequent frames back/left as much as possible."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:94
msgid "To manually play your animation back and forward using your mouse, a concept called *scrubbing*, you click-drag within the Frame Timing Header."
-msgid ":kbd:`Alt` + :kbd:`drag` : Move selected frame(s) and *all* the frames to the right of it. (This is useful for when you need to clear up some space in your animation, but don't want to select all the frames to the right of a particular frame!)"
+msgid ":kbd:`Alt + drag` : Move selected frame(s) and *all* the frames to the right of it. (This is useful for when you need to clear up some space in your animation, but don't want to select all the frames to the right of a particular frame!)"
-msgid "This docker allows you to quickly shift between undo states, and even go back in time far more quickly that rapidly reusing :kbd:`Ctrl + Z`."
+msgid "This docker allows you to quickly shift between undo states, and even go back in time far more quickly that rapidly reusing the :kbd:`Ctrl + Z` shortcut."
msgid "According to this parameter -- groups are made. Every stroke is put into the same group till two consecutive strokes have a time gap of more than T seconds. Then a new group is started."
msgid "A user may want to keep the ability of Undoing/Redoing his last N strokes. Once N is crossed -- the earlier strokes are merged into the group's first stroke."
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-06-15 09:36+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:1
msgid "How to get a backtrace in Krita using the dr. MinW debugger."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:13
msgid "Backtrace"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:13
msgid "Debug"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:18
msgid "Dr. MinW Debugger"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:22
msgid "The information on this page applies only to the Windows release of Krita 3.1 Beta 3 (3.0.92) and later."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:26
msgid "Getting a Backtrace"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:28
msgid "There are some additions to Krita which makes getting a backtrace much easier on Windows."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:32
msgid "When there is a crash, Krita might appear to be unresponsive for a short time, ranging from a few seconds to a few minutes, before the crash dialog appears."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:36
msgid "An example of the crash dialog."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:38
msgid "If Krita keeps on being unresponsive for more than a few minutes, it might actually be locked up, which may not give a backtrace. In that situation, you have to close Krita manually. Continue to follow the following instructions to check whether it was a crash or not."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:40
-msgid "Open Windows Explorer and type ``%LocalAppData%`` (without quotes) on the address bar and press :kbd:`Enter`."
+msgid "Open Windows Explorer and type ``%LocalAppData%`` (without quotes) on the address bar and press the :kbd:`Enter` key."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:44
msgid "Find the file ``kritacrash.log`` (it might appear as simply ``kritacrash`` depending on your settings.)"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:45
msgid "Open the file with Notepad and scroll to the bottom, then scroll up to the first occurrence of “Error occurred on <time>” or the dashes."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:49
msgid "Start of backtrace."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:51
msgid "Check the time and make sure it matches the time of the crash."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:55
msgid "End of backtrace."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:57
msgid "The text starting from this line to the end of the file is the most recent backtrace."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:59
msgid "If ``kritacrash.log`` does not exist, or a backtrace with a matching time does not exist, then you don’t have a backtrace. This means Krita was very likely locked up, and a crash didn’t actually happen. In this case, make a bug report too."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:60
msgid "If the backtrace looks truncated, or there is nothing after the time, it means there was a crash and the crash handler was creating the stack trace before being closed manually. In this case, try to re-trigger the crash and wait longer until the crash dialog appears."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:64
msgid "Starting from Krita 3.1 Beta 3 (3.0.92), the external DrMingw JIT debugger is not needed for getting the backtrace."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:67
msgid "Using the Debug Package"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:69
msgid "Starting from 3.1 Beta 3, the debug package contains only the debug symbols separated from the executables, so you have to download the portable package separately too (though usually you already have it in the first place.)"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:71
msgid "Links to the debug packages should be available on the release announcement news item on https://krita.org/, along with the release packages. You can find debug packages for any release either in https://download.kde.org/stable/krita for stable releases or in https://download.kde.org/unstable/krita for unstable releases. Portable zip and debug zip are found next to each other."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:72
msgid "Make sure you’ve downloaded the same version of debug package for the portable package you intend to debug / get a better (sort of) backtrace."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:73
msgid "Extract the files inside the Krita install directory, where the sub-directories `bin`, `lib` and `share` is located, like in the figures below:"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:79
msgid "After extracting the files, check the ``bin`` dir and make sure you see the ``.debug`` dir inside. If you don't see it, you probably extracted to the wrong place."
msgid "The effect will mostly apply to dark tones."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:31
#: ../../reference_manual/filters/adjust.rst:49
msgid "Midtones"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:32
#: ../../reference_manual/filters/adjust.rst:50
msgid "The effect will apply to mostly midtones."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:33
#: ../../reference_manual/filters/adjust.rst:51
msgid "Highlights"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:34
#: ../../reference_manual/filters/adjust.rst:52
msgid "This will apply the effect on the highlights only."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:36
#: ../../reference_manual/filters/adjust.rst:54
msgid "Exposure"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:36
#: ../../reference_manual/filters/adjust.rst:54
msgid "The strength at which this filter is applied."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:38
#: ../../reference_manual/filters/adjust.rst:41
msgid "Burn"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:43
msgid "An image-wide burn-filter. Burn is named after a trick in traditional dark-room photography that gave similar results."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:46
msgid ".. image:: images/filters/Burn-filter.png"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:56
msgid "Levels Filter"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:59
msgid "Levels"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:61
-msgid "This filter allows you to directly modify the levels of the tone-values of an image, by manipulating sliders for highlights, midtones and shadows. You can even set an output and input range of tones for the image. A histogram is displayed to show you the tonal distribution. The default shortcut for levels filter is :kbd:`Ctrl + L` ."
+msgid "This filter allows you to directly modify the levels of the tone-values of an image, by manipulating sliders for highlights, midtones and shadows. You can even set an output and input range of tones for the image. A histogram is displayed to show you the tonal distribution. The default shortcut for levels filter is :kbd:`Ctrl + L`."
msgid "This is very useful to do an initial cleanup of scanned lineart or grayscale images. If the scanned lineart is light you can slide the black triangle to right to make it darker or if you want to remove the gray areas you can slide the white slider to left."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:68
msgid "Auto levels is a quick way to adjust tone of an image. If you want to change the settings later you can click on the :guilabel:`Create Filter Mask` button to add the levels as a filter mask."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:71
#: ../../reference_manual/filters/adjust.rst:74
msgid "Color Adjustment Curves"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:71
msgid "RGB Curves"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:71
msgid "Curves Filter"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:76
msgid "This filter allows you to adjust each channel by manipulating the curves. You can even adjust the alpha channel and the lightness channel through this filter. This is used very often by artists as a post processing filter to slightly heighten the mood of the painting by adjust the overall color. For example a scene with fire breathing dragon may be made more red and yellow by adjusting the curves to give it more warmer look, similarly a snowy mountain scene can be made to look cooler by adjusting the blues and greens. The default shortcut for this filter is :kbd:`Ctrl + M`."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:81
msgid "Since 4.1 this filter can also handle Hue and Saturation curves."
msgid "Sometimes, when you are adjusting the colors for an image, you want bright colors to be more saturated, or have a little bit of brightness in the purples."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:94
msgid "The Cross-channel color adjustment filter allows you to do this."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:96
msgid "At the top, there are two drop-downs. The first one is to choose which :guilabel:`Channel` you wish to modify. The :guilabel:`Driver Channel` drop down is what channel you use to control which parts are modified."
msgid "The curve, on the horizontal axis, represents the driver channel, while the vertical axis represent the channel you wish to modify."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:102
msgid "So if you wish to increase the saturation in the lighter parts, you pick :guilabel:`Saturation` in the first drop-down, and :guilabel:`Lightness` as the driver channel. Then, pull up the right end to the top."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:104
msgid "If you wish to desaturate everything but the teal/blues, you select :guilabel:`Saturation` for the channel and :guilabel:`Hue` for the driver. Then put a dot in the middle and pull down the dots on either sides."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:107
msgid "Brightness/Contrast curves"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:109
msgid "This filter allows you to adjust the brightness and contrast of the image by adjusting the curves."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:113
msgid "These have been removed in Krita 4.0, because the Color Adjustment filter can do the same. Old files with brightness/contrast curves will be loaded as Color Adjustment curves."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:115
#: ../../reference_manual/filters/adjust.rst:118
msgid "Color Balance"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:120
-msgid "This filter allows you to control the color balance of the image by adjusting the sliders for Shadows, Midtones and Highlights. The default shortcut for this filter is :kbd:`Ctrl + B` ."
+msgid "This filter allows you to control the color balance of the image by adjusting the sliders for Shadows, Midtones and Highlights. The default shortcut for this filter is :kbd:`Ctrl + B`."
-msgid "Image-wide desaturation filter. Will make any image Grayscale. Has several choices by which logic the colors are turned to gray. The default shortcut for this filter is :kbd:`Ctrl + Shift + U` ."
+msgid "Image-wide desaturation filter. Will make any image Grayscale. Has several choices by which logic the colors are turned to gray. The default shortcut for this filter is :kbd:`Ctrl + Shift + U`."
msgid "This will turn colors to gray using the HSL model."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:136
msgid "Luminosity (ITU-R BT.709)"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:137
msgid "Will turn the color to gray by using the appropriate amount of weighting per channel according to ITU-R BT.709."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:138
msgid "Luminosity (ITU-R BT.601)"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:139
msgid "Will turn the color to gray by using the appropriate amount of weighting per channel according to ITU-R BT.601."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:140
msgid "Average"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:141
msgid "Will make an average of all channels."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:142
msgid "Min"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:143
msgid "Subtracts all from one another to find the gray value."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:145
msgid "Max"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:145
msgid "Adds all channels together to get a gray value."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:147
#: ../../reference_manual/filters/adjust.rst:150
msgid "Invert"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:147
msgid "Negative"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:152
msgid "This filter like the name suggests inverts the color values in the image. So white (1,1,1) becomes black (0,0,0), yellow (1,1,0) becomes blue (0,1,1), etc. The default shortcut for this filter is :kbd:`Ctrl + I`."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:155
msgid "Contrast"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:158
msgid "Auto Contrast"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:160
msgid "Tries to adjust the contrast the universally acceptable levels."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:162
msgid "Hue"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:162
msgid "Value"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:162
msgid "Brightness"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:162
msgid "Chroma"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:165
msgid "HSV/HSL Adjustment"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:167
-msgid "With this filter, you can adjust the Hue, Saturation, Value or Lightness, through sliders. The default shortcut for this filter is :kbd:`Ctrl + U` ."
+msgid "With this filter, you can adjust the Hue, Saturation, Value or Lightness, through sliders. The default shortcut for this filter is :kbd:`Ctrl + U`."
msgid "A simple black and white threshold filter that uses sRGB luminosity. It'll convert any image to a image with only black and white, with the input number indicating the threshold value at which black becomes white."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:178
#: ../../reference_manual/filters/adjust.rst:191
msgid "Slope"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:178
msgid "ASC CDL"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:178
msgid "Offset and Power Curves"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:181
msgid "Slope, Offset, Power"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:183
msgid "A different kind of color balance filter, with three color selectors, which will have the same shape as the one used in settings."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:185
msgid "This filter is particular useful because it has been defined by the American Society for Cinema as \"ASC_CDL\", meaning that it is a standard way of describing a color balance method."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:192
msgid "This represents a multiplication and determine the adjustment of the brighter colors in an image."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:193
msgid "Offset"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:194
msgid "This determines how much the bottom is offset from the top, and so determines the color of the darkest colors."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/adjust.rst:196
msgid "This represents a power function, and determines the adjustment of the mid-tone to dark colors of an image."
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-06-15 09:36+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../<rst_epilog>:2
msgid ""
".. image:: images/icons/Krita_mouse_left.png\n"
" :alt: mouseleft"
msgstr ""
#. +> trunk5
#: ../../reference_manual/instant_preview.rst:1
msgid "How the Instant Preview technology in Krita works."
msgstr ""
#. +> trunk5
#: ../../reference_manual/instant_preview.rst:10
#: ../../reference_manual/instant_preview.rst:15
msgid "Instant Preview"
msgstr ""
#. +> trunk5
#: ../../reference_manual/instant_preview.rst:10
msgid "Performance"
msgstr ""
#. +> trunk5
#: ../../reference_manual/instant_preview.rst:10
msgid "Lag"
msgstr ""
#. +> trunk5
#: ../../reference_manual/instant_preview.rst:17
msgid "Instant Preview (previously known under the code name Level Of Detail/LOD strokes) is Krita's special speed-up mechanism that was funded by the 2015 Kickstarter. Krita slows down with really large images due to the large amount of data it's crunching in painting these images. Instant Preview works by taking a smaller version of the canvas, and drawing the feedback on there while Krita calculates the real stroke in the background. This means that if you have a 4k screen and are working on a 4k image at 100% zoom, you won't feel any speed up."
msgstr ""
#. +> trunk5
#: ../../reference_manual/instant_preview.rst:20
msgid "Activating Instant Preview"
msgstr ""
#. +> trunk5
#: ../../reference_manual/instant_preview.rst:24
msgid "Instant Preview requires OpenGL 3.0 support at minimum. So if you don't have :guilabel:`high-quality` scaling available in :menuselection:`Settings --> Configure Krita --> Display --> Display scaling filter`, then you won't be able to use Instant Preview either."
msgid "The Global Instant Preview toggle is under the view menu."
msgstr ""
#. +> trunk5
#: ../../reference_manual/instant_preview.rst:31
-msgid "Instant Preview is activated in two places: The view menu (:kbd:`Shift + L`), and the settings of the given paintop by default. This is because Instant Preview has different limitations with different paint operations."
+msgid "Instant Preview is activated in two places: The view menu (:kbd:`Shift + L` shortcut), and the settings of the given paintop by default. This is because Instant Preview has different limitations with different paint operations."
msgstr ""
#. +> trunk5
#: ../../reference_manual/instant_preview.rst:33
msgid "For example, the overlay mode in the color smudge brush will disable the ability to have Instant Preview on the brush, so does using 'fade' sensor for size."
msgstr ""
#. +> trunk5
#: ../../reference_manual/instant_preview.rst:35
msgid "Similarly, the auto-spacing, fuzzy sensor in size, use of density in brush-tip and the use of texture paintops will make it more difficult to determine a stroke, and thus will give a feeling of 'popping' when the stroke is finished."
msgstr ""
#. +> trunk5
#: ../../reference_manual/instant_preview.rst:37
msgid "When you check the brush settings, the Instant Preview checkbox will have a \\* behind it. Hovering over it will give you a list of options that are affecting the Instant Preview mode."
msgstr ""
#. +> trunk5
#: ../../reference_manual/instant_preview.rst:41
msgid "|mouseleft| this pop-up will give a slider, which can be used to determine the threshold size at which instant preview activates. By default this 100px. This is useful for brushes that are optimised to work on small sizes."
msgid "The Instant Preview checkbox at the bottom of the brush settings editor will give you feedback when there's settings active that can't be previewed right. Hover over it to get more detail. In this case, the issue is that auto-spacing is on."
msgstr ""
#. +> trunk5
#: ../../reference_manual/instant_preview.rst:50
msgid "Tools that benefit from Instant Preview"
msgstr ""
#. +> trunk5
#: ../../reference_manual/instant_preview.rst:52
msgid "The following tools benefit from Instant Preview:"
-msgid "While working in complex artwork you'll often find the need to group the layers or some portions and elements of the artwork in one unit. Group layers come in handy for this, they allow you to make a segregate the layers, so you can hide these quickly, or so you can apply a mask to all the layers inside this group as if they are one, you can also recursively transform the content of the group... Just drag the mask so it moves to the layer. They are quickly made with :kbd:`Ctrl + G`."
+msgid "While working in complex artwork you'll often find the need to group the layers or some portions and elements of the artwork in one unit. Group layers come in handy for this, they allow you to make a segregate the layers, so you can hide these quickly, or so you can apply a mask to all the layers inside this group as if they are one, you can also recursively transform the content of the group... Just drag the mask so it moves to the layer. They are quickly made with the :kbd:`Ctrl + G` shortcut."
msgid "A thing to note is that the layers inside a group layer are considered separately when the layer gets composited, the layers inside a group are separately composited and then this image is taken in to account when compositing the whole image, while on the contrary, the groups in Photoshop have something called pass-through mode which makes the layer behave as if they are not in a group and get composited along with other layers of the stack. The recent versions of Krita have pass-through mode you can enable it to get similar behavior"
msgid "Paint layers are the most commonly used type of layers used in digital paint or image manipulation software like Krita. If you've ever used layers in :program:`Photoshop` or the :program:`Gimp`, you'll be used to how they work. In short, a paint layer, also called a pixel, bitmap or raster layer, is a bitmap image (an image made up of many points of color)."
msgid "Paint layers let you apply many advanced effects such as smearing, smudging and distorting. This makes them the most flexible type of layer. However, paint layers don't scale well when enlarged (they pixelate), and any effects that have been applied can't be edited."
msgid "To deal with these two drawbacks, digital artists will typically work at higher Pixel Per Inch (PPI) counts. It is not unusual to see PPI settings of 400 to 600 PPI for a canvas with a good amount of detail. To combat the issue of applied effects that cannot be edited it is best to take advantage of the non-destructive layer capabilities of filter, transparency and transform masks."
msgid "As long as you have enough resolution / size on your canvas though, and as long as you aren't going to need to go back and tweak an effect you created previously, then a paint layer is usually the type of layer you will want. If you click on the :guilabel:`New layer` icon in the layers docker you'll get a paint layer. Of course you can always choose the :guilabel:`New layer` drop-down to get another type."
msgid "Local Selection masks let you remember and recall edit a selection on a layer. They work in a similar way to extra channels in other image editing programs. One difference is :program:`Krita's` ability to assign them to specific layers and activate a selection with a single click on the layer. Just click the round icon with the dotted outline on the local selection layer in the Layers docker."
-msgid "When isolating a selection mask with :kbd:`Alt` + |mouseleft|, you can perform transformation, deformation and paint operations on the selection layer, modifying the selection."
+msgid "When isolating a selection mask with the :kbd:`Alt +` |mouseleft| shortcut, you can perform transformation, deformation and paint operations on the selection layer, modifying the selection."
msgid "A single layer can contain multiple Local Selection Masks. Repeating. A single layer can contain multiple Local Selection Masks (LSM). This is important because it means that you can, for instance, have several different outline parts of an image and save each as its own LSM and then recall it with a single click. Without using LSM you would have to create layer upon layer for each mask. Not only would this be inefficient for you but also for Krita and the program would slow down trying to keep up with it all. LSM's are one of the most important features in Krita!"
msgid "You can modify the global selection the same way you can with a local-selection. To do so, you first need to activate the global selection as a layer node. To do so, go into :menuselection:`Select --> Show Global Selection Mask`. The global selection, if you have anything selected, will now appear on the top of the layer stack as a selection mask."
msgid "Sometimes especially in the field of game development, artists need to work with the alpha channel of the texture separately. To assist such workflow, Krita has a special functionality called :menuselection:`Split Alpha`. It allows splitting alpha channel of a paint layer into a separate :ref:`transparency_masks`. The artist can work on the transparency mask in an isolated environment and merge it back when he has finished working."
msgid "Use your preferred paint tool to paint on the Transparency Mask. Black paints transparency (see-through), white paints opacity (visible). Gray values paint semi-transparency."
-msgid "If you would like to isolate alpha channel, enter Isolated Mode by |mouseright| + :menuselection:`Isolate Layer` (or :kbd:`Alt` + |mouseleft|)."
+msgid "If you would like to isolate alpha channel, enter Isolated Mode by |mouseright| + :menuselection:`Isolate Layer` (or the :kbd:`Alt +` |mouseleft| shortcut)."
msgid "Normally, when saving an image to a file, all fully transparent areas of the image are filled with black color. It happens because when composing the layers of the image, Krita drop color data of fully transparent pixels for efficiency reason. To avoid this of color data loss you can either avoid compositing of the image i.e. limit image to only one layer without any masks or effects, or use the following method:"
msgid "It shows the vector contents of the layer on the left side. The icon showing the page with the red bookmark denotes that it is a vector layer. To the right of that is the layer name. Next are the layer visibility and accessibility icons. Clicking the \"eye\" will toggle visibility. Clicking the lock into a closed position will lock the content and editing will no longer be allowed until it is clicked again and the lock on the layer is released."
msgid "You can create a vector layer in two ways. Using the extra options from the \"Add Layer\" button you can click the \"Vector Layer\" item and it will create a new vector layer. You can also drag a rectangle or ellipse from the **Add shape** dock onto an active Paint Layer. If the active layer is a Vector Layer then the shape will be added directly to it."
msgid "There's currently a bug with the vector layers that they will always consider themselves to be at 72dpi, regardless of the actual pixel-size. This can make manipulating shapes a little difficult, as the precise input will not allow cm or inch, even though the vector layer coordinate system uses those as a basis."
-msgid "This feature of the tool allows you to move your object by clicking and dragging your shape around the canvas. Holding :kbd:`Ctrl` will lock your moves to one axis."
+msgid "This feature of the tool allows you to move your object by clicking and dragging your shape around the canvas. Holding the :kbd:`Ctrl` key will lock your moves to one axis."
-msgid "This feature of the tool allows you to stretch your shape. Selecting a midpoint will allow stretching along one axis. Selecting a corner point will allow stretching across both axis. Holding :kbd:`Shift` will allow you to scale your object. Holding :kbd:`Ctrl` will cause your manipulation to be mirrored across your object."
+msgid "This feature of the tool allows you to stretch your shape. Selecting a midpoint will allow stretching along one axis. Selecting a corner point will allow stretching across both axis. Holding the :kbd:`Shift` key will allow you to scale your object. Holding the :kbd:`Ctrl` key will cause your manipulation to be mirrored across your object."
-msgid "This feature of the tool will allow you to rotate your object around its center. Holding :kbd:`Ctrl` will cause your rotation to lock to 45 degree angles."
+msgid "This feature of the tool will allow you to rotate your object around its center. Holding the :kbd:`Ctrl` key will cause your rotation to lock to 45 degree angles."
msgid "At the moment there is no way to scale only one side of your vector object. The developers are aware that this could be useful and will work on it as manpower allows."
-msgid "Double-click on a vector object to edit the specific points or curves which make up the shape. Click and drag a point to move it around the canvas. Click and drag along a line to curve it between two points. Holding :kbd:`Ctrl` will lock your moves to one axis."
+msgid "Double-click on a vector object to edit the specific points or curves which make up the shape. Click and drag a point to move it around the canvas. Click and drag along a line to curve it between two points. Holding the :kbd:`Ctrl` key will lock your moves to one axis."
msgid "In addition to being defined by points and curves, a shape also has two defining properties: **Fill** and **Stroke**. **Fill** defines the color, gradient, or pattern that fills the space inside of the shape object. '**Stroke**' defines the color, gradient, pattern, and thickness of the border along the edge of the shape. These two can be edited using the **Stroke and Fill** dock. The dock has two modes. One for stroke and one for fill. You can change modes by clicking in the dock on the filled square or the black line. The active mode will be shown by which is on top of the other."
msgid "Here is the dock with the fill element active. Notice the red line across the solid white square. This tells us that there is no fill assigned therefore the inside of the shape will be transparent."
msgid "The style selector allows you to choose different patterns and line styles. The width option changes the thickness of the outline on your vector shape. The cap option changes how line endings appear. The join option changes how corners appear."
msgid "The Miter limit controls how harsh the corners of your object will display. The higher the number the more the corners will be allowed to stretch out past the points. Lower numbers will restrict the stroke to shorter and less sharp corners."
msgid "To the right of that is the solid square. This sets the fill to be a solid color which is displayed in the long button and can be selected by pressing the arrow just to the right of the long button. To the right of the solid square is the gradient button. This will set the fill to display as a gradient. A gradient can be selected by pressing the down arrow next to the long button."
msgid "Under the **X** is a button that shows a pattern. This inside area will be filled with a pattern. A pattern can be chosen by pressing the arrows next to the long button. The two other buttons are for **fill rules**: the way a self-overlapping path is filled."
msgid "The button with the inner square filled toggles non zero mode, where most of the time a self overlapping path is entirely filled except when it overlaps with a sub-path of a different direction that 'decrease the level of overlapping' so that the region between the two is considered outside the path and remain unfilled, like this:"
msgid "For more (and better) information about fill rules check the `Inkscape manual <http://tavmjong.free.fr/INKSCAPE/MANUAL/html/Attributes-Fill-Stroke.html#Attributes-Fill-Rule>`_."
msgid "Determines whether or not the dockers are visible. This is a nice aid to cleaning up the interface and removing unnecessary \"eye-ball clutter\" when you are painting. If you've got your brush and you know you're just going to be painting for awhile why not flip the dockers off? You'd be amazed what a difference it makes while you're working. However, if you know you're swapping out tools or working with layer or any of the other myriad things Krita lets you do then there's no point getting caught up in flipping the docks on and off. Use you time wisely!"
msgid "This is a great candidate to add to the toolbar so you can just click the dockers on and off and don't even have to open the menu to do it. See :ref:`configure_toolbars` below for more."
msgid "Krita subdivides the access of many of its features into functional panels called Dockers. Dockers are small windows that can contain, for example, things like the Layer Stack, Color Palette or Brush Presets. Think of them as the painter's palette, or his water, or his brushkit."
msgid "There is no easy way to create and share themes. The color themes are defined in the :menuselection:`Share --> Color Schemes` folder where Krita is downloaded."
msgid "Configuring shortcuts is another way to customize the application to fit you. Whether you are transitioning from another app, like Photoshop or MyPaint, or you think your own shortcut keys make more sense for you then Krita has got you covered. You get to the shortcuts interface through :menuselection:`Settings --> Configure Krita` and by choosing the :menuselection:`Keyboard Shortcuts` tab."
-msgid "To use, just type the :guilabel:`Action` into the Search box you want to assign/reassign the shortcut for. Suppose we wanted to assign the shortcut :kbd:`Ctrl + G` to the :guilabel:`Action` of Group Layers so that every time we pressed :kbd:`Ctrl + G` a new Layer Group would be created. Use the following steps to do this:"
+msgid "To use, just type the :guilabel:`Action` into the Search box you want to assign/reassign the shortcut for. Suppose we wanted to assign the shortcut :kbd:`Ctrl + G` to the :guilabel:`Action` of Group Layers so that every time we pressed the :kbd:`Ctrl + G` shortcut a new Layer Group would be created. Use the following steps to do this:"
msgid "Krita allows you to highly customize the Toolbar interface. You can add, remove and change the order of nearly everything to fit your style of work. To get started, choose :menuselection:`Settings --> Configure Toolbars`."
msgid "Use the arrows between the *Available* and *Current* actions sections to move items back and forth and up and down in the hierarchy. This type of inclusion/exclusion interface has been around on PCs for decades so we don't need to go into great detail regarding its use. What is important though is selecting the correct Toolbar to work on. The :guilabel:`File` Toolbar allows you to add items between the :menuselection:`New` , :menuselection:`Open` and :menuselection:`Save` buttons as well as to the right of the :menuselection:`Save` button. The :guilabel:`Brushes and Stuff` Toolbar, lets you modify anything from the Gradients button over to the right. This is probably where you'll do most of your editing."
msgid "Here we've added :menuselection:`Select Opaque` , :menuselection:`Local Selection` , :menuselection:`Transparency Mask` , :guilabel:`Isolate Layer` , :menuselection:`Show Assistant Previews` . This is just an example of a couple of options that are used frequently and might trim your workflow. This is what it looks like in the configuration tool:"
msgid "You'll notice that some of the items are text only and some only icons. This is determined by whether the particular item has an associated icon in Krita. You can select anything from the *Available* section and move it to the *Current* one and rearrange to fit your own workflow."
msgid "If you add so many that they won't all fit on your screen at once, you will see a small chevron icon appear. Click it and the toolbar expands to show the remaining items."
msgid "This will show the status bar. The status bar contains a lot of important information, a zoom widget, and the button to switch Selection Display Mode."
-msgid "Canvas Only mode is Krita's version of full screen mode. It is activated by hitting :kbd:`Tab` on the keyboard. Select which parts of Krita will be hidden in canvas-only mode -- The user can set which UI items will be hidden in canvas-only mode. Selected items will be hidden."
+msgid "Canvas Only mode is Krita's version of full screen mode. It is activated by hitting the :kbd:`Tab` key on the keyboard. Select which parts of Krita will be hidden in canvas-only mode -- The user can set which UI items will be hidden in canvas-only mode. Selected items will be hidden."
msgid "These settings directly affect Advanced Color Selector Dockers and the same dialog box appears when the user clicks the settings button in that docker as well. They also affect certain hotkey actions."
msgid "G'Mic or GREYC's Magic for Image Computing is an opensource filter framework, or, it is an extra program you can download to have access to a whole lot of image filters."
msgid "There is a refresh button at the bottom of the G'Mic window that will update your version. You will need an internet connection to download the latest version."
msgid "If you have issues downloading the update through the plugin, you can also do it manually. If you are trying to update and get an error, copy the URL that is displayed in the error dialog. It will be to a \".gmic\" file. Download it from from your web browser and place the file in one of the following directories."
msgid "Select a cursor shape to use while the brush tools are used. This cursor will always be visible on the canvas. It is usually set to a type exactly where your pen nib is at. The available cursor types are shown below."
msgid "Select an outline shape to use while the brush tools are used. This cursor shape will optionally show in the middle of a painting stroke as well. The available outline shape types are shown below. (pictures will come soon)"
msgid "This option when selected will show the brush outline while a stroke is being made. If unchecked the brush outline will not appear during stroke making, it will show up only after the brush stroke is finished. This option works only when Brush Outline is selected as the Cursor Shape."
msgid "This makes sure that the outline size will always be the maximum possible brush diameter, and not the current one as affected by sensors such as pressure. This makes the cursor a little less noisy to use."
msgid "The default cursor color. This is mixed with the canvas image so that it will usually have a contrasting color, but sometimes this mixing does not work. This is usually due driver problems. When that happens, you can configure a more pleasant color here."
msgid "Whether or not you want to see the on-canvas pop-up messages that tell you whether you are in tabbed mode, rotating the canvas, or mirroring it."
msgid "An instance is a single entry in your system's task manager. Turning this option makes sure that Krita will check if there's an instance of Krita open already when you instruct it to open new documents, and then have your documents opened in that single instance. There's some obscure uses to allowing multiple instances, but if you can't think of any, just keep this option on."
msgid "In Krita 4.2 the behavior of flow in combination with opacity was changed. This allows you to turn it back to the 4.1 behavior. This will however be removed in future versions."
-msgid "This switches the function of the :kbd:`Ctrl` and :kbd:`Alt` buttons when modifying selections. Useful for those used to Gimp instead of Photoshop, or Lefties without a right-:kbd:`Alt` key on their keyboard."
+msgid "This switches the function of the :kbd:`Ctrl` and :kbd:`Alt` keys when modifying selections. Useful for those used to Gimp instead of Photoshop, or Lefties without a :kbd:`Alt + right-click` shortcut on their keyboard."
msgid "This allows finger painting with capacitive screens. Some devices have both capacitive touch and a stylus, and then this can interfere. In that case, just toggle this."
msgid "Kinetic scrolling on the brush chooser drop-down with activation mode set to :guilabel:`On Click Drag`, with this disabled all of these clicks would lead to a brush being selected regardless of drag motion."
msgid "Here the user can specify how often Krita should autosave the file, you can tick the checkbox to turn it off. For Windows these files are saved in the %TEMP% directory. If you are on Linux it is stored in /home/'username'."
msgid "This determines whether the filename of autosaves has a period prepended to the name. On Linux and Mac OS this is a technique to ensure the file is hidden by default."
msgid "When selected Krita will, upon save, rename the original file as a backup file and save the current image to the original name. The result is that you will have saved the image, and there will be a copy of the image that is saved separately as a backup. This is useful in case of crashes during saves."
msgid "This is the main folder of your computer. On Linux and Mac OS this is the 'Home' folder, on Windows, the 'c:\\Users\\YOUR_USER_NAME' folder (where YOUR_USER_NAME is your windows username)."
msgid "This stored the file in the temp folder. Temp folders are special folders of which the contents are emptied when you shut down your computer. If you don't particularly care about your backup files and want them to be 'cleaned' automatically, this is the best place. If you want your backup files to be kept indefinitely, this is a wrong choice."
msgid "The suffix that will be placed after the full filename. 'filename.kra' will then be saved as 'filename.kra~', ensuring the files won't show up in Krita's open file dialog."
msgid "Load the last opened session. If you have :guilabel:`Save session when Krita closes` toggled, this becomes the last files you had open and the like."
msgid "This allows you to set the maximum brush size to a size of up to 10.000 pixels. Do be careful with using this, as a 10.000 pixel size can very quickly be a full gigabyte of data being manipulated, per dab. In other words, this might be slow."
-msgid "Most of Krita's shortcuts are configured in the menu section :menuselection:`Settings --> Configure Krita --> Configure Shortcuts`. The shortcuts configured here are simple key combinations, for example :kbd:`Ctrl + X` to cut. Shortcuts can also be sequences of key combinations (e.g. :kbd:`Shift + S` then :kbd:`B`). Krita also has a special interface for configuring the mouse and stylus events sent to the canvas, found under :ref:`canvas_input_settings`."
+msgid "Most of Krita's shortcuts are configured in the menu section :menuselection:`Settings --> Configure Krita --> Configure Shortcuts`. The shortcuts configured here are simple key combinations, for example the :kbd:`Ctrl + X` shortcut to cut. Shortcuts can also be sequences of key combinations (e.g. :kbd:`Shift + S` shortcut then the :kbd:`B` key). Krita also has a special interface for configuring the mouse and stylus events sent to the canvas, found under :ref:`canvas_input_settings`."
msgid "Each shortcut is assigned a default, which may be empty. The user can assign up to two custom shortcuts, known as primary and alternate shortcuts. Simply click on a \"Custom\" button and type the key combination you wish to assign to the shortcut. If the key combination is already in use for another shortcut, the dialog will prompt the user to resolve the conflict."
msgid "Many users migrate to Krita from other tools with different default shortcuts. Krita users may change the default shortcuts to mimic these other programs. Currently, Krita ships with defaults for Photoshop and Paint Tool Sai. Additional shortcut schemes can be placed in the ~/.config/krita/input/ folder."
msgid "Users may wish to export their shortcuts to use across machines, or even share with other users. This can be done with the save/load drop-down. Note: the shortcuts can be saved and overridden manually by backingup the text file kritashortcutsrc located in ~/.config/krita/. Additionally, the user can export a custom shortcut scheme file generated by merging the existing scheme defaults with the current customizations."
msgid "Input Pressure Global Curve : This is the global curve setting that your tablet will use in Krita. The settings here will make your tablet feel soft or hard globally."
msgid "Some tablet devices don't tell us whether the side buttons on a stylus. If you have such a device, you can try activate this workaround. Krita will try to read right and middle-button clicks as if they were coming from a mouse instead of a tablet. It may or may not work on your device (depends on the tablet driver implementation). After changing this option Krita should be restarted."
msgid "Use the WinTab API to receive tablet pen input. This is the API being used before Krita 3.3. This option is recommended for most Wacom tablets."
msgid "Use the Pointer Input messages to receive tablet pen input. This option depends on Windows Ink support from the tablet driver. This is a relatively new addition so it's still considered to be experimental, but it should work well enough for painting. You should try this if you are using an N-Trig device (e.g. recent Microsoft Surface devices) or if your tablet does not work well with WinTab."
msgid "When using multiple monitors or using a tablet that is also a screen, Krita will get conflicting information about how big your screen is, and sometimes if it has to choose itself, there will be a tablet offset. This window allows you to select the appropriate screen resolution."
msgid "Type in the numbers manually. Use this when you have tried the other options. You might even need to do trial and error if that is the case, but at the least you can configure it."
msgid "If you have a dual monitor setup and only the top half of the screen is reachable, you might have to enter the total width of both screens plus the double height of your monitor in this field."
msgid "If adjusting this doesn't work, and if you have a Wacom tablet, an offset in the canvas can be caused by a faulty Wacom preference file which is not removed or replaced by reinstalling the drivers."
msgid "To fix it, use the “Wacom Tablet Preference File Utility” to clear all the preferences. This should allow Krita to detect the correct settings automatically."
msgid "This is a special feature for debugging tablet input. When you click on it, it will open a window with two sections. The left section is the **Drawing Area** and the right is the **Text Output**."
msgid "The red line represents mouse events. Mouse events are the most basic events that Krita can pick up. However, mouse events have crude coordinates and have no pressure sensitivity."
msgid "The blue line represents the tablet events. The tablet events only show up when Krita can access your tablet. These have more precise coordinates and access to sensors like pressure sensitivity."
msgid "If you have no blue line when drawing on the lefthand drawing area, Krita cannot access your tablet. Check out the :ref:`page on drawing tablets <drawing_tablets>` for suggestions on what is causing this."
msgid "When you draw a line, the output on the right will show all sorts of text output. This text output can be attached to a help request or a bug report to figure out what is going on."
msgid "`David Revoy wrote an indepth guide on using this feature to maximum advantage. <https://www.davidrevoy.com/article182/calibrating-wacom-stylus-pressure-on-krita>`_"
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-06-15 09:36+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../reference_manual/render_animation.rst:1
msgid "How to use the render animation command in Krita."
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:12
#: ../../reference_manual/render_animation.rst:17
#: ../../reference_manual/render_animation.rst:42
msgid "Render Animation"
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:12
msgid "Animation"
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:19
msgid "Render animation allows you to render your animation to an image sequence, gif, mp4, mkv, or ogg file. It replaces :guilabel:`Export Animation`."
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:21
msgid "For rendering to an animated file format, Krita will first render to a png sequence and then use FFmpeg, which is really good at encoding into video files, to render that sequence to an animated file format. The reason for this two-step process is that animation files can be really complex and really big, and this is the best way to allow you to keep control over the export process. For example, if your computer has a hiccup, and one frame saves out weird, first saving the image sequence allows you to only resave that one weird frame before rendering."
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:23
msgid "This means that you will need to find a good place to stick your frames before you can start rendering. If you only do throwaway animations, you can use a spot on your hard-drive with enough room and select :guilabel:`Delete Sequence After Rendering`."
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:26
msgid "Image Sequence"
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:28
msgid "Base Name"
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:29
msgid "The base name of your image sequence. This will get suffixed with a number depending on the frame."
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:30
msgid "File Format"
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:31
msgid "The file format to export the sequence to. When rendering we enforce png. The usual export options can be modified with :guilabel:`...`."
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:32
msgid "Render Location"
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:33
msgid "Where you render the image sequence to. Some people prefer to use a flash-drive or perhaps a harddrive that is fast."
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:34
msgid "First Frame"
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:35
msgid "The first frame of the range of frames you wish to adjust. Automatically set to the first frame of your current selection in the timeline. This is useful when you only want to re-render a little part."
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:36
msgid "Last Frame"
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:37
msgid "As above, the last frame of the range of frames you wish to adjust. Automatically set to the last frame of your current selection in the timeline."
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:39
msgid "Naming Sequence starts with"
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:39
msgid "The frames are named by using :guilabel:`Base Name` above and adding a number for the frame. This allows you to set where the frame number starts, so rendering from 8 to 10 with starting point 3 will give you images named 11 and 15. Useful for programs that don't understand sequences starting with 0, or for precision output."
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:44
msgid "Render As"
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:45
msgid "The file format to render to. All except gif have extra options that can be manipulated via :guilabel:`...`."
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:46
msgid "File"
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:47
msgid "Location and name of the rendered animation."
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:48
msgid "FFmpeg"
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:49
msgid "The location where your have FFmpeg. If you don't have this, Krita cannot render an animation. For proper gif support, you will need FFmpeg 2.6, as we use its palettegen functionality."
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:51
msgid "Delete Sequence After Rendering"
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:51
msgid "Delete the prerendered image sequence after done rendering. This allows you to choose whether to try and save some space, or to save the sequence for when encoding fails."
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:55
msgid "None of the video formats support saving from images with a transparent background, so Krita will try to fill it with something. You should add a background color yourself to avoid it from using, say, black."
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:58
msgid "Setting Up Krita for Exporting Animations"
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:60
msgid "You will need to download an extra application and link it in Krita for it to work. The application is pretty big (50MB), so the Krita developers didn't want to bundle it with the normal application. The software that we will use is free and called FFmpeg. The following instructions will explain how to get it and set it up. The setup is a one-time thing so you won't have to do it again."
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:63
msgid "Step 1 - Downloading FFmpeg"
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:66
#: ../../reference_manual/render_animation.rst:86
msgid "For Windows"
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:68
-msgid "Go to the `FFmpeg website <http://ffmpeg.org/download.html>`_. The URL that had the link for me was `here... <https://ffmpeg.zeranoe.com/builds/>`_"
+msgid "Go to the `FFmpeg website <https://ffmpeg.org/download.html>`_. The URL that had the link for me was `here... <https://ffmpeg.zeranoe.com/builds/>`_"
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:70
msgid "Watch out for the extremely annoying google and that looks like a download button! There is no big button for what we need. Either get the 64-bit STATIC version or 32-bit STATIC version that is shown later down the page. If you bought a computer in the past 5 years, you probably want the 64-bit version. Make sure you get a exe file, if you hover over the options they will give more information about what exactly you are downloading."
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:73
#: ../../reference_manual/render_animation.rst:93
msgid "For OSX"
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:75
msgid "Please see the section above. However, FFmpeg is obtained from `here <https://evermeet.cx/ffmpeg/>`_ instead. Just pick the big green button on the left under the FFmpeg heading. You will also need an archiving utility that supports .7z, since FFmpeg provides their OSX builds in .7z format. If you don't have one, try something like `Keka <https://www.kekaosx.com>`_."
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:78
#: ../../reference_manual/render_animation.rst:98
msgid "For Linux"
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:80
msgid "FFmpeg can be installed from the repositories on most Linux systems. Version 2.6 is required for proper gif support, as we use the palettegen functionality."
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:83
msgid "Step 2 - Unzipping and Linking to Krita"
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:88
msgid "Unzip the package that was just downloaded. Rename the long folder name to just ffmpeg. Let's put this folder in a easy to find location. Go to your C:\\ and place it there. You can put it wherever you want, but that is where I put it."
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:90
-msgid "Open Krita back up and go to :menuselection:`File --> Render Animation`. Click the :guilabel:`Browse` button on the last item called FFmpeg. Select this file ``C:/ffmpeg/bin/ffmpeg.exe`` and click :guilabel:`OK` ."
+msgid "Open Krita back up and go to :menuselection:`File --> Render Animation`. Click the :guilabel:`Browse` button on the last item called FFmpeg. Select this file ``C:/ffmpeg/bin/ffmpeg.exe`` and click :guilabel:`OK`."
msgstr ""
#. +> trunk5
#: ../../reference_manual/render_animation.rst:95
msgid "After downloading FFmpeg, you just need to extract it and then simply point to it in the FFmpeg location in Krita like ``/Users/user/Downloads/ffmpeg`` (assuming you downloaded and extracted the .7z file to /Users/user/Downloads)."
msgid "Let's make an animated GIF. In the Render Animation dialog, change the :guilabel:`Render As` field to \"GIF image\". Choose the file location where it will save with the \"File\" menu below. I just saved it to my desktop and called it \"export.gif\". When it is done, you should be able to open it up and see the animation."
msgid "By default, FFmpeg will render MP4 files with a too new codec, which means that Windows Media Player won't be able to play it. So for Windows, select \"baseline\" for the profile instead of \"high422\" before rendering."
msgid "OSX does not come with any software to play MP4 and MKV files. If you use Chrome for your web browser, you can drag the video file into that and the video should play. Otherwise you will need to get a program like VLC to see the video."
msgid "Resources are pluggable bits of data, like brush presets or patterns. Krita has variety of resources and also has a good resource management starting from 2.9, making it really easy for artists to share and collate all the resources together"
msgid "Starting from 2.9 Krita has a new format to manage resources it is called ''Bundles'', a bundle is just a compressed file containing all the resources together."
msgid "Krita also has a robust tagging system for you to manage the resources on the fly while painting. All Krita resources can be tagged. These tags can be added via the resource manager, but also via the respective dockers such as brush preset docker, pattern docker etc. You can |mouseleft| the plus icon in the docker and add a tag name. In addition to adding you can rename and delete a tag as well."
msgid "Resources can belong to one or more tags. For example, you may have a Brush Preset of a favorite **Ink Pen** variant and have it tagged so it shows in up in your Inking, Painting, Comics and Favorites groups of brushes."
msgid "Some dockers, for example the brush preset docker as shown below, have a resource filter, which functions like a powerful search bar for the resource in question."
msgid "You can enter brush name, tag name to quickly pull up a list of brush presets you want. When you select any tag from the tag drop-down and want to include brush presets from other tags as well then you can add filters the following way:"
msgid "Use the :guilabel:`Resource Filter` at the bottom of the :guilabel:`Brush Presets` dock or :guilabel:`Brush Settings Editor` to type in what you want to group. For instance: if you type **Pencil** in the filter box you will get all Brush Presets with **Pencil** somewhere in their name. Now you have all the Pencil-related Brush Presets together in one place."
-msgid "To finish, click the :guilabel:`Save` button (small disk icon to the right of the :guilabel:`Resource Filter` box) or press :kbd:`Enter` and all the items will be saved with the new tag you created."
+msgid "To finish, click the :guilabel:`Save` button (small disk icon to the right of the :guilabel:`Resource Filter` box) or press the :kbd:`Enter` key and all the items will be saved with the new tag you created."
msgid "Now, anytime you want to open up your \"digital pencil box\" and see what you have to work with all you have to do is use the pull-down and select :guilabel:`Pencils`. The Resource Filter works the same way in other parts of Krita so be on the lookout for it!"
-msgid "If you find the thumbnails of the resources such as color swatches brushes and pattern to be small you can make them bigger or :guilabel:`Zoom in`. All resource selectors can be zoomed in and out of, by hovering over the selector and using :kbd:`Ctrl +` |mousescroll|."
+msgid "If you find the thumbnails of the resources such as color swatches brushes and pattern to be small you can make them bigger or :guilabel:`Zoom in`. All resource selectors can be zoomed in and out of, by hovering over the selector and using the :kbd:`Ctrl +` |mousescroll| shortcut."
msgid "As mentioned earlier Krita has a flexible resource management system. Starting from version 2.9 you can share various resources mentioned above by sharing a single compressed zip file created within Krita."
msgid "The manage resources section in the settings was also revamped for making it easy for the artists to prepare these bundle files. You can open manage resource section by going to :menuselection:`Settings` then :menuselection:`Manage Resources`."
-msgid "To import a bundle click on :guilabel:`Import Bundles/Resources` button on the top right side of the dialog. Select .bundle file format from the file type if it is not already selected, browse to the folder where you have downloaded the bundle, select it and click :guilabel:`Open`. Once the bundle is imported it will be listed in the :guilabel:`Active Bundle` section. If you don't need the bundle you can temporarily make it inactive by selecting it and clicking on the arrow button, this will move it to the :guilabel:`Inactive` section."
+msgid "To import a bundle click on :guilabel:`Import Bundles/Resources` button on the top right side of the dialog. Select ``.bundle`` file format from the file type if it is not already selected, browse to the folder where you have downloaded the bundle, select it and click :guilabel:`Open`. Once the bundle is imported it will be listed in the :guilabel:`Active Bundle` section. If you don't need the bundle you can temporarily make it inactive by selecting it and clicking on the arrow button, this will move it to the :guilabel:`Inactive` section."
msgid "You can create your own bundle from the resources of your choice. Click on the :guilabel:`Create bundle` button. This will open a dialog box as shown below."
msgid "The left hand section is for filling up information about the bundle like author name, website, email, bundle icon, etc. The right hand side provides a list of available resources. Choose the type of resource you wish to add in to the bundle from the drop-down above and add it to the bundle by selecting a resource and clicking on the arrow button."
msgid "Make sure you add brush tips for used in the respective paintop presets you are adding to the bundle. If you don't provide the brush tips then the brush presets loaded from this bundle will have a 'X' mark on the thumbnail denoting that the texture is missing. And the brush preset won't be the same."
msgid "Once you have added all the resources you can create bundle by clicking on the :guilabel:`Save` button, the bundle will be saved in the location you have specified. You can then share this bundle with other artists or load it on other workstations."
msgid "When you delete a preset from Krita, Krita doesn't actually delete the physical copy of the preset. It just adds it to a black list so that the next time when you start Krita the presets from this list are not loaded. To delete the brushes from this list click on :guilabel:`Delete Backup Files`."
msgid "In case you wish to delete the bundles you have imported permanently click on the :guilabel:`Open Resource Folder` button in the :guilabel:`Manage Resources` dialog. This will open the resource folder in your file manager / explorer. Go inside the bundles folder and delete the bundle file which you don't need any more. The next time you start Krita the bundle and its associated resources will not be loaded."
msgid "For some time Photoshop has been using the ABR format to compile brushes into a single file. Krita can read and load .ABR files, although there are certain features. For this example we will use an example of an .ABR file that contains numerous images of types of trees and ferns. We have two objectives. The first is to create a series of brushes that we an quickly access from the Brush Presets dock to easily put together a believable forest. The second is to create a single brush that we can change on the fly to use for a variety of flora, without the need to have a dedicated Brush Preset for each type."
msgid "First up is download the file (.ZIP, .RAR,...) that contains the .ABR file and any licensing or other notes. Be sure to read the license if there is one!"
msgid "Click on the tab \"Predefined\" next to \"Auto\". This will change the editor to show a scrollable screen of thumbnail images, most will be black on a white background. At the bottom of the window are two icons:"
msgid "If everything went fine you will see a number of new thumbnails show up at the bottom of the window. In our case, they would all be thumbnails representing different types of trees. Your job now is to decide which of these you want to have as Brush Preset (Just like your Pencil) or you think you'll only use sporadically."
msgid "Let's say that there is an image of an evergreen tree that we're pretty sure is going to be a regular feature in some of our paintings and we want to have a dedicated brush for it. To do this we would do the following:"
msgid "Change the name of the brush at the very top of the Brush Editor Settings dialog. Something like \"Trees - Tall Evergreen\" would be appropriate."
msgid "Now that you have a \"Tall Evergreen\" brush safely saved you can experiment with the settings to see if there is anything you would like to change, for instance, by altering the size setting and the pressure parameter you could set the brush to change the tree size depending on the pressure you were using with your stylus (assuming you have a stylus!)."
msgid "It's time now to create the Brush Preview graphic. The simplest and easiest way to do this for a brush of this type is to clear out the ScratchPad using the :guilabel:`Reset` button. Now, center your cursor in the Brush Preview square at the top of the ScratchPad and click once. You should see an image of your texture (in this case it would be the evergreen tree). In order to work correctly though the entire image should fit comfortably within the square. This might mean that you have to tweak the size of the brush. Once you have something you are happy with then click the :guilabel:`Overwrite Brush` button and your brush and its preview image will be saved."
msgid "You're ready to add the next texture! From here on it's just a matter of wash, rinse and repeat for each texture where you want to create a dedicated Brush Preset."
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-06-15 09:36+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../<generated>:1
msgid "Palette to use for naming the layers"
msgstr ""
#. +> trunk5
#: ../../<rst_epilog>:2
msgid ""
".. image:: images/icons/Krita_mouse_left.png\n"
" :alt: mouseleft"
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:1
msgid "The Split Layer functionality in Krita"
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:10
msgid "Splitting"
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:10
msgid "Color Islands"
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:15
msgid "Split Layer"
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:16
-msgid "Splits a layer according to color. This is useful in combination with the :ref:`colorize_mask` and :kbd:`R` + |mouseleft| to select layers at the cursor."
+msgid "Splits a layer according to color. This is useful in combination with the :ref:`colorize_mask` and the :kbd:`R +` |mouseleft| shortcut to select layers at the cursor."
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:18
msgid "Put all new layers in a group layer"
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:19
msgid "Put all the result layers into a new group."
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:20
msgid "Put every layer in its own, separate group layer"
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:21
msgid "Put each layer into its own group."
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:22
msgid "Alpha-lock every new layer"
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:23
msgid "Enable the alpha-lock for each layer so it is easier to color."
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:24
msgid "Hide the original layer"
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:25
msgid "Turns off the visibility on the original layer so you won't get confused."
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:26
msgid "Sort layers by amount of non-transparent pixels"
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:27
msgid "This ensures that the layers with large color swathes will end up at the top."
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:28
msgid "Disregard opacity"
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:29
msgid "Whether to take into account transparency of a color."
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:30
msgid "Fuzziness"
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:31
msgid "How precise the algorithm should be. The larger the fuzziness, the less precise the algorithm will be. This is necessary for splitting layers with anti-aliasing, because otherwise you would end up with a separate layer for each tiny pixel."
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:33
msgid "Select the palette to use for naming. Krita will compare the main color of a layer to each color in the palette to get the most appropriate name for it."
-msgid "This tool allows you to choose a point from the canvas and make the color of that point the active foreground color. When a painting or drawing tool is selected the Color Picker tool can also be quickly accessed by pressing :kbd:`Ctrl`."
+msgid "This tool allows you to choose a point from the canvas and make the color of that point the active foreground color. When a painting or drawing tool is selected the Color Picker tool can also be quickly accessed by pressing the :kbd:`Ctrl` key."
msgid "The first drop-down box allows you to select whether you want to sample from all visible layers or only the active layer. You can choose to have your selection update the current foreground color, to be added into a color palette, or to do both."
msgid "The middle section contains a few properties that change how the Color Picker picks up color; you can set a :guilabel:`Radius`, which will average the colors in the area around the cursor, and you can now also set a :guilabel:`Blend` percentage, which controls how much color is \"soaked up\" and mixed in with your current color. Read :ref:`mixing_colors` for information about how the Color Picker's blend option can be used as a tool for off-canvas color mixing."
msgid "At the very bottom is the Info Box, which displays per-channel data about your most recently picked color. Color data can be shown as 8-bit numbers or percentages."
msgid "This tool, represented by a magic wand, allows you to make :ref:`selections_basics` by selecting a point of color. It will select any contiguous areas of a similar color to the one you selected. You can adjust the \"fuzziness\" of the tool in the tool options dock. A lower number will select colors closer to the color that you chose in the first place."
-msgid ":kbd:`Shift` + |mouseleft| sets the subsequent selection to 'add'. You can release the :kbd:`Shift` key while dragging, but it will still be set to 'add'. Same for the others."
+msgid ":kbd:`Shift +` |mouseleft| sets the subsequent selection to 'add'. You can release the :kbd:`Shift` key while dragging, but it will still be set to 'add'. Same for the others."
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-06-21 09:19+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../reference_manual/tools/crop.rst:1
msgid "Krita's crop tool reference."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/crop.rst:11
msgid "Tools"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/crop.rst:11
msgid "Crop"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/crop.rst:11
msgid "Trim"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/crop.rst:16
msgid "Crop Tool"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/crop.rst:18
-msgid "The crop tool can be used to crop an image or layer. To get started, choose the :guilabel:`Crop` tool and then click once to select the entire canvas. Using this method you ensure that you don't inadvertently grab outside of the visible canvas as part of the crop. You can then use the options below to refine your crop. Press :kbd:`Enter` to finalize the crop action, or use the :guilabel:`Crop` button in the tool options docker."
+msgid "The crop tool can be used to crop an image or layer. To get started, choose the :guilabel:`Crop` tool and then click once to select the entire canvas. Using this method you ensure that you don't inadvertently grab outside of the visible canvas as part of the crop. You can then use the options below to refine your crop. Press the :kbd:`Enter` key to finalize the crop action, or use the :guilabel:`Crop` button in the tool options docker."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/crop.rst:20
msgid "At its most basic, the crop tool allows you to size a rectangle around an area and reduce your image or layer to only that content which is contained within that area. There are several options which give a bit more flexibility and precision."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/crop.rst:22
msgid "The two numbers on the left are the exact horizontal position and vertical position of the left and top of the cropping frame respectively. The numbers are the right are from top to bottom: width, height, and aspect ratio. Selecting the check boxes will keep any one of these can be locked to allow you to manipulate the other two without losing the position or ratio of the locked property."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/crop.rst:24
msgid "Center"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/crop.rst:25
msgid "Keeps the crop area centered."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/crop.rst:26
msgid "Grow"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/crop.rst:27
msgid "Allows the crop area to expand beyond the image boundaries."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/crop.rst:28
msgid "Applies to"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/crop.rst:29
msgid "Lets you apply the crop to the entire image or only to the active layer. When you are ready, hit the :guilabel:`Crop` button and the crop will apply to your image."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/crop.rst:31
msgid "Decoration"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/crop.rst:31
msgid "Help you make a composition by showing you lines that divide up the screen. You can for example show thirds here, so you can crop your image according to the `Rule of Thirds <https://en.wikipedia.org/wiki/Rule_of_thirds>`_."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/crop.rst:34
msgid "Continuous Crop"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/crop.rst:36
-msgid "If you crop an image, and try to start a new one directly afterwards, Krita will attempt to recall the previous crop, so you can continue it. This is the *continuous crop*. You can press :kbd:`Esc` to cancel this and crop anew."
+msgid "If you crop an image, and try to start a new one directly afterwards, Krita will attempt to recall the previous crop, so you can continue it. This is the *continuous crop*. You can press the :kbd:`Esc` key to cancel this and crop anew."
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-05-04 09:38+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../<rst_epilog>:28
msgid ""
".. image:: images/icons/ellipse_tool.svg\n"
" :alt: toolellipse"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/ellipse.rst:1
msgid "Krita's ellipse tool reference."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/ellipse.rst:11
msgid "Tools"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/ellipse.rst:11
msgid "Ellipse"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/ellipse.rst:11
msgid "Circle"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/ellipse.rst:16
msgid "Ellipse Tool"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/ellipse.rst:18
msgid "|toolellipse|"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/ellipse.rst:20
msgid "Use this tool to paint an ellipse. The currently selected brush is used for drawing the ellipse outline. Click and hold the left mouse button to indicate one corner of the ‘bounding rectangle’ of the ellipse, then move your mouse to the opposite corner. :program:`Krita` will show a preview of the ellipse using a thin line. Release the button to draw the ellipse."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/ellipse.rst:22
msgid "While dragging the ellipse, you can use different modifiers to control the size and position of your ellipse:"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/ellipse.rst:24
-msgid "In order to make a circle instead of an ellipse, hold :kbd:`Shift` while dragging. After releasing :kbd:`Shift` any movement of the mouse will give you an ellipse again:"
+msgid "In order to make a circle instead of an ellipse, hold the :kbd:`Shift` key while dragging. After releasing the :kbd:`Shift` key any movement of the mouse will give you an ellipse again:"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/ellipse.rst:29
-msgid "In order to keep the center of the ellipse fixed and only growing and shrinking the ellipse around it, hold :kbd:`Ctrl` while dragging:"
+msgid "In order to keep the center of the ellipse fixed and only growing and shrinking the ellipse around it, hold the :kbd:`Ctrl` key while dragging:"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/ellipse.rst:34
-msgid "In order to move the ellipse around, hold :kbd:`Alt`:"
+msgid "In order to move the ellipse around, hold the :kbd:`Alt` key:"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/ellipse.rst:39
-msgid "You can change between the corner/corner and center/corner dragging methods as often as you want by holding down or releasing :kbd:`Ctrl`, provided you keep the left mouse button pressed. With :kbd:`Ctrl` pressed, mouse movements will affect all four corners of the bounding rectangle (relative to the center), without :kbd:`Ctrl`, the corner opposite to the one you are moving remains still. With :kbd:`Alt` pressed, all four corners will be affected, but the size stays the same."
+msgid "You can change between the corner/corner and center/corner dragging methods as often as you want by holding down or releasing the :kbd:`Ctrl` key, provided you keep the left mouse button pressed. With the :kbd:`Ctrl` key pressed, mouse movements will affect all four corners of the bounding rectangle (relative to the center), without the :kbd:`Ctrl` key, the corner opposite to the one you are moving remains still. With the :kbd:`Alt` key pressed, all four corners will be affected, but the size stays the same."
msgid "This tool, represented by an ellipse with a dashed border, allows you to make :ref:`selections_basics` of a elliptical area. Simply click and drag around the section you wish to select."
-msgid ":kbd:`Shift` + |mouseleft| sets the subsequent selection to 'add'. You can release the :kbd:`Shift` key while dragging, but it will still be set to 'add'. Same for the others."
+msgid ":kbd:`Shift +` |mouseleft| sets the subsequent selection to 'add'. You can release the :kbd:`Shift` key while dragging, but it will still be set to 'add'. Same for the others."
-msgid "So to subtract a perfect circle, you do :kbd:`Alt +` |mouseleft|, then release the :kbd:`Alt` key while dragging and press :kbd:`Shift` to constrain."
+msgid "So to subtract a perfect circle, you do :kbd:`Alt +` |mouseleft|, then release the :kbd:`Alt` key while dragging and press the :kbd:`Shift` key to constrain."
msgid "The freehand brush tool allows you to paint on paint layers without constraints like the straight line tool. It makes optimal use of your tablet's input settings to control the brush-appearance. To switch the brush, make use of the brush-preset docker."
-msgid "The alternate invocation is the ''color picker'' (standardly invoked by :kbd:`Ctrl`) Press :kbd:`Ctrl` to switch the tool to \"color picker\", use left or right click to pick fore and background color respectively. Release the :kbd:`Ctrl` to return to the freehand brush tool."
+msgid "The alternate invocation is the ''color picker'' (standardly invoked by the :kbd:`Ctrl` key). Press the :kbd:`Ctrl` key to switch the tool to \"color picker\", use left or right click to pick fore and background color respectively. Release the :kbd:`Ctrl` key to return to the freehand brush tool."
-msgid "The Primary setting is \"size\". (standardly invoked by :kbd:`Shift`) Press :kbd:`Shift` and drag outward to increase brush size. Drag inward to decrease it."
+msgid "The Primary setting is \"size\" (standardly invoked by the :kbd:`Shift` key). Press the :kbd:`Shift` key and drag outward to increase brush size. Drag inward to decrease it."
msgid "The hotkey can be edited in :menuselection:`Settings --> Configure Krita --> Configure Shortcuts`. The sticky-keys can be edited in :menuselection:`Settings --> Configure Krita --> Canvas Input Settings`."
msgid "Smoothing, also known as stabilising in some programs, allows the program to correct the stroke. Useful for people with shaky hands, or particularly difficult long lines."
msgid "This option will smooth the input of older tablets like the Wacom Graphire 3. If you experience slightly jagged lines without any smoothing on, this option will apply a very little bit of smoothing to get rid of those lines."
msgid "The distance the brush needs to move before the first dab is drawn. (Literally the amount of events received by the tablet before the first dab is drawn.)"
msgid "This controls how much the line will attempt to reach the last known position of the cursor after the left-mouse button/or stylus is lifted. Will currently always result in a straight line, so use with caution."
msgid "This option averages all inputs from the tablet. It is different from weighted smoothing in that it allows for always completing the line. It will draw a circle around your cursor and the line will be a bit behind your cursor while painting."
msgid "Ticking this will allow snapping to :ref:`assistant_tool`, and the hotkey to toggle it is :kbd:`Ctrl + Shift + L`. See :ref:`painting_with_assistants` for more information."
msgid "The slider will determine the amount of snapping, with 1000 being perfect snapping, and 0 being no snapping at all. For situations where there is more than one assistant on the canvas, the defaultly ticked :guilabel:`Snap Single` means that Krita will only snap to a single assistant at a time, preventing noise. Unticking it allows you to chain assistants together and snap along them."
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-05-04 09:38+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../<rst_epilog>:2
msgid ""
".. image:: images/icons/Krita_mouse_left.png\n"
" :alt: mouseleft"
msgstr ""
#. +> trunk5
#: ../../<rst_epilog>:48
msgid ""
".. image:: images/icons/grid_tool.svg\n"
" :alt: toolgrid"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/grid_tool.rst:1
msgid "Krita's grid tool reference."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/grid_tool.rst:11
msgid "Tools"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/grid_tool.rst:11
msgid "Grid"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/grid_tool.rst:16
msgid "Grid Tool"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/grid_tool.rst:18
msgid "|toolgrid|"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/grid_tool.rst:22
msgid "Deprecated in 3.0, use the :ref:`grids_and_guides_docker` instead."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/grid_tool.rst:24
-msgid "When you click on the edit grid tool, you'll get a message saying that to activate the grid you must press :kbd:`Enter`. Press :kbd:`Enter` to make the grid visible. Now you must have noticed the tool icon for your pointer has changed to icon similar to move tool."
+msgid "When you click on the edit grid tool, you'll get a message saying that to activate the grid you must press the :kbd:`Enter` key. Press the :kbd:`Enter` key to make the grid visible. Now you must have noticed the tool icon for your pointer has changed to icon similar to move tool."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/grid_tool.rst:27
-msgid "To change the spacing of the grid, press and hold :kbd:`Ctrl` and then |mouseleft| + drag on the canvas. In order to move the grid you have to press :kbd:`Alt` and then |mouseleft| + drag."
+msgid "To change the spacing of the grid, press and hold the :kbd:`Ctrl` key and then the |mouseleft| :kbd:`+ drag` shortcut on the canvas. In order to move the grid you have to press the :kbd:`Alt` key and then the |mouseleft| :kbd:`+ drag` shortcut."
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-06-15 09:36+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../<generated>:1
msgid "Preview"
msgstr ""
#. +> trunk5
#: ../../<rst_epilog>:2
msgid ""
".. image:: images/icons/Krita_mouse_left.png\n"
" :alt: mouseleft"
msgstr ""
#. +> trunk5
#: ../../<rst_epilog>:24
msgid ""
".. image:: images/icons/line_tool.svg\n"
" :alt: toolline"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/line.rst:1
msgid "Krita's line tool reference."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/line.rst:11
msgid "Tools"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/line.rst:11
msgid "Line"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/line.rst:11
msgid "Straight Line"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/line.rst:16
msgid "Straight Line Tool"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/line.rst:18
msgid "|toolline|"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/line.rst:21
msgid "This tool is used to draw lines. Click the |mouseleft| to indicate the first endpoint, keep the button pressed, drag to the second endpoint and release the button."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/line.rst:24
msgid "Hotkeys and Sticky Keys"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/line.rst:26
-msgid "To activate the Line tool from freehand brush mode, use :kbd:`V`. Use other keys afterwards to constraint the line."
+msgid "To activate the Line tool from freehand brush mode, use the :kbd:`V` key. Use other keys afterwards to constraint the line."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/line.rst:28
-msgid "Use :kbd:`Shift` while holding the mouse button to constrain the angle to multiples of 15º. You can press :kbd:`Alt` while still keeping the |mouseleft| down to move the line to a different location."
+msgid "Use the :kbd:`Shift` key while holding the mouse button to constrain the angle to multiples of 15º. You can press the :kbd:`Alt` key while still keeping the |mouseleft| down to move the line to a different location."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/line.rst:32
-msgid "Using the :kbd:`Shift` keys BEFORE pushing the holding the left mouse button/stylus down will, in default Krita, activate the quick brush-resize. Be sure to use :kbd:`Shift` after."
+msgid "Using the :kbd:`Shift` keys BEFORE pushing the holding the left mouse button/stylus down will, in default Krita, activate the quick brush-resize. Be sure to use the :kbd:`Shift` key after."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/line.rst:35
msgid "Tool Options"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/line.rst:37
msgid "The following options allow you to modify the end-look of the straight-line stroke with tablet-values. Of course, this only work for tablets, and currently only on Paint Layers."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/line.rst:40
msgid "Use sensors"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/line.rst:41
msgid "This will draw the line while taking sensors into account. To use this effectively, start the line and trace the path like you would when drawing a straight line before releasing. If you make a mistake, make the line shorter and start over."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/line.rst:43
msgid "This will show the old-fashioned preview line so you know where your line will end up."
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-06-15 09:36+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../<generated>:1
msgid "Position"
msgstr ""
#. +> trunk5
#: ../../<rst_epilog>:44
msgid ""
".. image:: images/icons/move_tool.svg\n"
" :alt: toolmove"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/move.rst:1
msgid "Krita's move tool reference."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/move.rst:11
msgid "Tools"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/move.rst:11
msgid "Move"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/move.rst:11
msgid "Transform"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/move.rst:16
msgid "Move Tool"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/move.rst:18
msgid "|toolmove|"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/move.rst:20
msgid "With this tool, you can move the current layer or selection by dragging the mouse."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/move.rst:22
msgid "Move current layer"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/move.rst:23
msgid "Anything that is on the selected layer will be moved."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/move.rst:24
msgid "Move layer with content"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/move.rst:25
msgid "Any content contained on the layer that is resting under the four-headed Move cursor will be moved."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/move.rst:26
msgid "Move the whole group"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/move.rst:27
msgid "All content on all layers will move. Depending on the number of layers this might result in slow and, sometimes, jerky movements. Use this option sparingly or only when necessary."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/move.rst:28
msgid "Shortcut move distance (3.0+)"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/move.rst:29
msgid "This allows you to set how much, and in which units, the :kbd:`Left Arrow`, :kbd:`Up Arrow`, :kbd:`Right Arrow` and :kbd:`Down Arrow` cursor key actions will move the layer."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/move.rst:30
msgid "Large Move Scale (3.0+)"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/move.rst:31
-msgid "Allows you to multiply the movement of the Shortcut Move Distance when pressing :kbd:`Shift` before pressing a direction key."
+msgid "Allows you to multiply the movement of the Shortcut Move Distance when pressing the :kbd:`Shift` key before pressing a direction key."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/move.rst:32
msgid "Show coordinates"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/move.rst:33
msgid "When toggled will show the coordinates of the top-left pixel of the moved layer in a floating window."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/move.rst:35
-msgid "If you click, then press :kbd:`Shift`, then move the layer, movement is constrained to the horizontal and vertical directions. If you press :kbd:`Shift`, then click, then move, all layers will be moved, with the movement constrained to the horizontal and vertical directions"
+msgid "If you click, then press the :kbd:`Shift` key, then move the layer, movement is constrained to the horizontal and vertical directions. If you press the :kbd:`Shift` key, then click, then move, all layers will be moved, with the movement constrained to the horizontal and vertical directions"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/move.rst:37
msgid "Constrained movement"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/move.rst:40
msgid "Gives the top-left coordinate of the layer, can also be manually edited."
-msgid ":kbd:`Shift` + |mouseleft| sets the subsequent selection to 'add'. You can release the :kbd:`Shift` key while dragging, but it will still be set to 'add'. Same for the others."
+msgid ":kbd:`Shift +` |mouseleft| sets the subsequent selection to 'add'. You can release the :kbd:`Shift` key while dragging, but it will still be set to 'add'. Same for the others."
-msgid "The pan tool allows you to pan your canvas around freely. It can be found at the bottom of the toolbox, and you just it by selecting the tool, and doing |mouseleft| + drag over the canvas."
+msgid "The pan tool allows you to pan your canvas around freely. It can be found at the bottom of the toolbox, and you just it by selecting the tool, and doing |mouseleft| :kbd:`+ drag` over the canvas."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/pan.rst:22
msgid "There are two hotkeys associated with this tool, which makes it easier to access from the other tools:"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/pan.rst:24
-msgid ":kbd:`Space +` |mouseleft| + drag over the canvas."
+msgid ":kbd:`Space +` |mouseleft| :kbd:`+ drag` over the canvas."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/pan.rst:25
-msgid "|mousemiddle| + drag over the canvas."
+msgid "|mousemiddle| :kbd:`+ drag` over the canvas."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/pan.rst:27
msgid "For more information on such hotkeys, check :ref:`navigation`."
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-05-04 09:38+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../<generated>:1
msgid "Activate Angle Snap"
msgstr ""
#. +> trunk5
#: ../../<rst_epilog>:2
msgid ""
".. image:: images/icons/Krita_mouse_left.png\n"
" :alt: mouseleft"
msgstr ""
#. +> trunk5
#: ../../<rst_epilog>:4
msgid ""
".. image:: images/icons/Krita_mouse_right.png\n"
" :alt: mouseright"
msgstr ""
#. +> trunk5
#: ../../<rst_epilog>:34
msgid ""
".. image:: images/icons/bezier_curve.svg\n"
" :alt: toolbeziercurve"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/path.rst:1
msgid "Krita's path tool reference."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/path.rst:11
msgid "Tools"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/path.rst:11
msgid "Vector"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/path.rst:11
msgid "Path"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/path.rst:11
msgid "Bezier Curve"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/path.rst:11
msgid "Pen"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/path.rst:17
msgid "Bezier Curve Tool"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/path.rst:19
msgid "|toolbeziercurve|"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/path.rst:21
msgid "You can draw curves by using this tool. Click the |mouseleft| to indicate the starting point of the curve, then click again for consecutive control points of the curve."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/path.rst:23
msgid ":program:`Krita` will show a blue line with two handles when you add a control point. You can drag these handles to change the direction of the curve in that point."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/path.rst:25
msgid "On a vector layer, you can click on a previously inserted control point to modify it. With an intermediate control point (i.e. a point that is not the starting point and not the ending point), you can move the direction handles separately to have the curve enter and leave the point in different directions. After editing a point, you can just click on the canvas to continue adding points to the curve."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/path.rst:27
-msgid "Pressing :kbd:`Del` will remove the currently selected control point from the curve. Double-click the |mouseleft| on any point of the curve or press :kbd:`Enter` to finish drawing, or press :kbd:`Esc` to cancel the entire curve. You can use :kbd:`Ctrl` while keeping the |mouseleft| pressed to move the entire curve to a different position."
+msgid "Pressing the :kbd:`Del` key will remove the currently selected control point from the curve. Double-click the |mouseleft| on any point of the curve or press the :kbd:`Enter` key to finish drawing, or press the :kbd:`Esc` key to cancel the entire curve. You can use the :kbd:`Ctrl` key while keeping the |mouseleft| pressed to move the entire curve to a different position."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/path.rst:29
-msgid "While drawing :kbd:`Ctrl` while dragging will push the handles both ways. :kbd:`Alt` will create a sharp corner, and :kbd:`Shift` will allow you to make a handle while at the end of the curve. |mouseright| will undo the last added point."
+msgid "While drawing the :kbd:`Ctrl` key while dragging will push the handles both ways. The :kbd:`Alt` key will create a sharp corner, and the :kbd:`Shift` key will allow you to make a handle while at the end of the curve. |mouseright| will undo the last added point."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/path.rst:32
msgid "Tool Options"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/path.rst:36
msgid "Autosmooth Curve"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/path.rst:37
msgid "Toggling this will have nodes initialize with smooth curves instead of angles. Untoggle this if you want to create sharp angles for a node. This will not affect curve sharpness from dragging after clicking."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/path.rst:39
msgid "Angle Snapping Delta"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/path.rst:40
msgid "The angle to snap to."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/path.rst:42
msgid "Angle snap will make it easier to have the next line be at a specific angle of the current. The angle is determined by the :guilabel:`Angle Snapping Delta`."
msgid "This tool, represented by an ellipse with a dashed border and a curve control, allows you to make a :ref:`selections_basics` of an area by drawing a path around it. Click where you want each point of the path to be. Click and drag to curve the line between points. Finally click on the first point you created to close your path."
-msgid ":kbd:`Shift` + |mouseleft| sets the subsequent selection to 'add'. You can release the :kbd:`Shift` key while dragging, but it will still be set to 'add'. Same for the others."
+msgid ":kbd:`Shift +` |mouseleft| sets the subsequent selection to 'add'. You can release the :kbd:`Shift` key while dragging, but it will still be set to 'add'. Same for the others."
msgid "Toggling this will have nodes initialize with smooth curves instead of angles. Untoggle this if you want to create sharp angles for a node. This will not affect curve sharpness from dragging after clicking."
msgid "Angle snap will make it easier to have the next line be at a specific angle of the current. The angle is determined by the :guilabel:`Angle Snapping Delta`."
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-05-04 09:38+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../<rst_epilog>:2
msgid ""
".. image:: images/icons/Krita_mouse_left.png\n"
" :alt: mouseleft"
msgstr ""
#. +> trunk5
#: ../../<rst_epilog>:30
msgid ""
".. image:: images/icons/polygon_tool.svg\n"
" :alt: toolpolygon"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/polygon.rst:1
msgid "Krita's polygon tool reference."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/polygon.rst:10
msgid "Tools"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/polygon.rst:10
msgid "Polygon"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/polygon.rst:15
msgid "Polygon Tool"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/polygon.rst:17
msgid "|toolpolygon|"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/polygon.rst:19
-msgid "With this tool you can draw polygons. Click the |mouseleft| to indicate the starting point and successive vertices, then double-click or press :kbd:`Enter` to connect the last vertex to the starting point."
+msgid "With this tool you can draw polygons. Click the |mouseleft| to indicate the starting point and successive vertices, then double-click or press the :kbd:`Enter` key to connect the last vertex to the starting point."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/polygon.rst:21
msgid ":kbd:`Shift + Z` undoes the last clicked point."
msgid "This tool, represented by a polygon with a dashed border, allows you to make :ref:`selections_basics` of a polygonal area point by point. Click where you want each point of the Polygon to be. Double click to end your polygon and finalize your selection area."
-msgid ":kbd:`Shift` + |mouseleft| sets the subsequent selection to 'add'. You can release the :kbd:`Shift` key while dragging, but it will still be set to 'add'. Same for the others."
+msgid ":kbd:`Shift +` |mouseleft| sets the subsequent selection to 'add'. You can release the :kbd:`Shift` key while dragging, but it will still be set to 'add'. Same for the others."
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-06-15 09:36+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../<generated>:1
msgid "Ratio"
msgstr ""
#. +> trunk5
#: ../../<rst_epilog>:2
msgid ""
".. image:: images/icons/Krita_mouse_left.png\n"
" :alt: mouseleft"
msgstr ""
#. +> trunk5
#: ../../<rst_epilog>:26
msgid ""
".. image:: images/icons/rectangle_tool.svg\n"
" :alt: toolrectangle"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:1
msgid "Krita's rectangle tool reference."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:10
msgid "Tools"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:10
msgid "Rectangle"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:15
msgid "Rectangle Tool"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:17
msgid "|toolrectangle|"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:19
msgid "This tool can be used to paint rectangles, or create rectangle shapes on a vector layer. Click and hold |mouseleft| to indicate one corner of the rectangle, drag to the opposite corner, and release the button."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:22
msgid "Hotkeys and Sticky-keys"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:24
msgid "There's no default hotkey for switching to rectangle."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:26
-msgid "If you hold :kbd:`Shift` while drawing, a square will be drawn instead of a rectangle. Holding :kbd:`Ctrl` will change the way the rectangle is constructed. Normally, the first mouse click indicates one corner and the second click the opposite. With :kbd:`Ctrl`, the initial mouse position indicates the center of the rectangle, and the final mouse position indicates a corner. You can press :kbd:`Alt` while still keeping |mouseleft| down to move the rectangle to a different location."
+msgid "If you hold the :kbd:`Shift` key while drawing, a square will be drawn instead of a rectangle. Holding the :kbd:`Ctrl` key will change the way the rectangle is constructed. Normally, the first mouse click indicates one corner and the second click the opposite. With the :kbd:`Ctrl` key, the initial mouse position indicates the center of the rectangle, and the final mouse position indicates a corner. You can press the :kbd:`Alt` key while still keeping |mouseleft| down to move the rectangle to a different location."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:28
-msgid "You can change between the corner/corner and center/corner drawing methods as often as you want by pressing or releasing :kbd:`Ctrl`, provided that you keep |mouseleft| pressed. With :kbd:`Ctrl` pressed, mouse movements will affect all four corners of the rectangle (relative to the center), without :kbd:`Ctrl`, one of the corners is unaffected."
+msgid "You can change between the corner/corner and center/corner drawing methods as often as you want by pressing or releasing the :kbd:`Ctrl` key, provided that you keep |mouseleft| pressed. With the :kbd:`Ctrl` key pressed, mouse movements will affect all four corners of the rectangle (relative to the center), without the :kbd:`Ctrl` key, one of the corners is unaffected."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:32
msgid "Tool Options"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:35
msgid "Fill"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:37
msgid "Not filled"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:38
msgid "The rectangle will be transparent from the inside."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:39
msgid "Foreground color"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:40
msgid "The rectangle will use the foreground color as fill."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:41
msgid "Background color"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:42
msgid "The rectangle will use the background color as fill."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:44
msgid "Pattern"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:44
msgid "The rectangle will use the active pattern as fill."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:47
msgid "Outline"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:49
msgid "No Outline"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:50
msgid "The Rectangle will render without outline."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:52
msgid "Brush"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:52
msgid "The Rectangle will use the current selected brush to outline."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:55
msgid "On vector layers, the rectangle will not render with a brush outline, but rather a vector outline."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:57
msgid "Anti-aliasing"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:58
msgid "This toggles whether or not to give selections feathered edges. Some people prefer hard-jagged edges for their selections."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:59
msgid "Width"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:60
msgid "Gives the current width. Use the lock to force the next selection made to this width."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:61
msgid "Height"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:62
msgid "Gives the current height. Use the lock to force the next selection made to this height."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:66
msgid "Gives the current ratio. Use the lock to force the next selection made to this ratio."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:68
msgid "Round X"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:70
msgid "The horizontal radius of the rectangle corners."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:72
msgid "Round Y"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/rectangle.rst:74
msgid "The vertical radius of the rectangle corners."
msgid "This tool, represented by a rectangle with a dashed border, allows you to make :ref:`selections_basics` of a rectangular area. Simply click and drag around the section you wish to select."
-msgid ":kbd:`Shift` + |mouseleft| sets the subsequent selection to 'add'. You can release the :kbd:`Shift` key while dragging, but it will still be set to 'add'. Same for the others."
+msgid ":kbd:`Shift +` |mouseleft| sets the subsequent selection to 'add'. You can release the :kbd:`Shift` key while dragging, but it will still be set to 'add'. Same for the others."
-msgid "So to subtract a perfect square, you do :kbd:`Alt +` |mouseleft|, then release the :kbd:`Alt` key while dragging and press :kbd:`Shift` to constrain."
+msgid "So to subtract a perfect square, you do :kbd:`Alt +` |mouseleft|, then release the :kbd:`Alt` key while dragging and press the :kbd:`Shift` key to constrain."
msgid "The reference images tool is a replacement for the reference images docker. You can use it to load images from your disk as reference, which can then be moved around freely on the canvas and placed wherever."
msgid "Only link to the reference image, krita will open it from the disk everytime it loads this file. This is recommended for big files, or files that change a lot."
-msgid "You can move around reference images by selecting them with |mouseleft|, and dragging them. You can rotate reference images by holding the cursor close to the outside of the corners till the rotate cursor appears, while tilting is done by holding the cursor close to the outside of the middle nodes. Resizing can be done by dragging the nodes. You can delete a single reference image by clicking it and pressing :kbd:`Del`. You can select multiple reference images with :kbd:`Shift` and perform all of these actions."
+msgid "You can move around reference images by selecting them with |mouseleft|, and dragging them. You can rotate reference images by holding the cursor close to the outside of the corners till the rotate cursor appears, while tilting is done by holding the cursor close to the outside of the middle nodes. Resizing can be done by dragging the nodes. You can delete a single reference image by clicking it and pressing the :kbd:`Del` key. You can select multiple reference images with the :kbd:`Shift` key and perform all of these actions."
msgid "The shape editing tool is for editing vector shapes. In Krita versions before 4.0 it would only show up in the docker when you had a vector shape selected. In Krita 4.0, this tool is always visible and has the Shape Properties docker as a part of it."
-msgid "You can access the Edit Shapes tool by clicking on the icon in the toolbox, but you can also access it by pressing :kbd:`Enter` when in the Shape Selection tool and having a shape selected that can be most efficiently edited with the edit shapes tool (right now, that's all shapes but text)."
+msgid "You can access the Edit Shapes tool by clicking on the icon in the toolbox, but you can also access it by pressing the :kbd:`Enter` key when in the Shape Selection tool and having a shape selected that can be most efficiently edited with the edit shapes tool (right now, that's all shapes but text)."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:27
msgid "On Canvas Editing of Shapes"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:29
msgid "As detailed further in the Tool Options, there's a difference between path shapes and specialized vector shapes that make it easy to have perfect ellipses, rectangles and more."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:32
#: ../../reference_manual/tools/shape_edit.rst:91
msgid "Path Shapes"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:34
msgid "Path shapes can be recognized by the different nodes they have."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:36
msgid "Paths in Krita are mostly bezier curves, and are made up of nodes. For straight lines, the nodes are connected by a line-segment and that's it. For curved lines, each node has a side handle to allow curving of that segment using the `cubic bezier curve algorithm <https://en.wikipedia.org/wiki/B%C3%A9zier_curve#/media/File:B%C3%A9zier_3_big.gif>`_."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:38
msgid "**What that means, in short, is that moving the side handles into a given direction will make the segment curve in that direction, and the longer the line of the node to the side handle, the stronger the curving.**"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:41
msgid "Selecting Nodes for Editing"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:43
msgid "You can select a single node with |mouseleft|, they will turn bright green if selected."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:45
-msgid "|mouseleft| + :kbd:`Shift` on unselected nodes will add them to a selection."
+msgid "|mouseleft| :kbd:`+ Shift` on unselected nodes will add them to a selection."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:47
-msgid "|mouseleft| + drag will make a selection rectangle. All nodes whose handles are touched by the rectangle will be selected. This combines with |mouseleft| + :kbd:`Shift` above."
+msgid "|mouseleft| + drag will make a selection rectangle. All nodes whose handles are touched by the rectangle will be selected. This combines with the |mouseleft| :kbd:`+ Shift` shortcut above."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:50
msgid "Selected Nodes"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:52
-msgid "You can add and remove side handles from a selected node with |mouseleft| + :kbd:`Shift`."
+msgid "You can add and remove side handles from a selected node with the |mouseleft| :kbd:`+ Shift` shortcut."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:54
msgid "Krita has several node-types that allow you control the side handles more efficiently. These are the corner, smooth and symmetric modes."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:56
msgid "Corner"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:57
msgid "Represented by a circle, the corner type allows you to have handles that can point in different directions and have different lengths."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:58
msgid "Smooth"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:59
msgid "Represented by a square, the smooth type will ensure a smooth transition by always pointing the handles into opposite directions, but they can still have different lengths."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:61
msgid "Symmetric"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:61
msgid "Represented by a diamond, the symmetric node will force handles to always point in opposite directions and have the same length."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:63
-msgid "|mouseleft| + :kbd:`Ctrl` on a selected node will cycle between the node-types."
+msgid "|mouseleft| :kbd:`+ Ctrl` on a selected node will cycle between the node-types."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:65
msgid ":kbd:`Del` will remove the selected node."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:68
msgid "Selected Segments"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:70
msgid "Segments are the lines between nodes. Hovering over a segment will show a dotted line, indicating it can be selected."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:72
msgid "You can |mouseleft| and drag on a segment to curve it to the mouse point. Clicking on different parts of the segment and dragging will curve it differently."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:74
msgid "Double |mouseleft| on a segment will add a node on the segment under the mouse cursor. The new node will be selected."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:77
msgid "Other Shapes"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:79
msgid "Shapes that aren't path shapes only have a single type of node: A small diamond like, that changes the specific parameters of that shape on-canvas. For example, you can change the corner radius on rectangles by dragging the nodes, or make the ellipse into a pie-segment."
msgid "Path shapes have options. The top left options are for converting to different anchor point types. The bottom left options are for adding or removing points. The top right options are for converting the line to different types. The bottom right options are for breaking and joining line segments."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/shape_edit.rst:88
msgid "The tool options of the Edit Shapes Tool change depending on the type of shape you have selected. With the exception of the path shape, all shapes have a :guilabel:`Convert to Path` action, which converts said shape to a path shape."
msgid "A cord shape will add a straight line between the two ends if the path isn't fully circular, as if a cord is being strung between the two points."
msgid "This tool, represented by a dropper over an area with a dashed border, allows you to make :ref:`selections_basics` by selecting a point of color. It will select any areas of a similar color to the one you selected. You can adjust the \"fuzziness\" of the tool in the tool options dock. A lower number will select colors closer to the color that you chose in the first place."
-msgid ":kbd:`Shift` + |mouseleft| sets the subsequent selection to 'add'. You can release the :kbd:`Shift` key while dragging, but it will still be set to 'add'. Same for the others."
+msgid ":kbd:`Shift +` |mouseleft| sets the subsequent selection to 'add'. You can release the :kbd:`Shift` key while dragging, but it will still be set to 'add'. Same for the others."
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-06-15 09:36+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../<rst_epilog>:2
msgid ""
".. image:: images/icons/Krita_mouse_left.png\n"
" :alt: mouseleft"
msgstr ""
#. +> trunk5
#: ../../<rst_epilog>:14
msgid ""
".. image:: images/icons/text-tool.svg\n"
" :alt: tooltext"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:1
msgid "Krita's text tool reference."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:11
msgid "Tools"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:11
msgid "Text"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:11
msgid "Vector"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:16
msgid "Text Tool"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:18
msgid "|tooltext|"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:20
msgid "This tool allows you to add text to your artwork."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:22
msgid "You use it by doing |mouseleft| + drag to create a rectangular selection. When releasing |mouseleft| a default text will be created and the text editor window will pop-up."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:24
msgid "Hovering over other text shapes will highlight their bounding box. |mouseleft| on a highlighted text will select it as the active text."
msgid "This contains features with which to create new texts, the following items are available:"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:34
msgid "Font"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:35
msgid "The letter type used by newly created texts."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:36
msgid "Size in pt"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:37
msgid "The letter-size used by newly created texts. It is in pts (points), which is a common standard for fonts that is measured 72 points per inch. It therefore will stay proportionally the same size if you increase or decrease canvas dpi."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:38
msgid "Create new texts with..."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:38
msgid "Anchor/Align text to the left/middle/right"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:39
msgid "Text alignment. This allows you to align text to the left, center it, or to the right. This is called text-anchor because svg 1.1's multiline text only uses text-anchor, and this is a slight bit different than text-align (and also the reason justify isn't available at the moment)."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:41
msgid "Edit Text"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:41
-msgid "This will summon the text editor for the currently selected shape. This can be quickly invoked with either pressing :kbd:`Enter` or Double - |mouseleft| the shape."
+msgid "This will summon the text editor for the currently selected shape. This can be quickly invoked with either pressing the :kbd:`Enter` key or :kbd:`double-click +` |mouseleft| shortcut on the shape."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:44
msgid "Text Editor"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:46
msgid "A small window for all your text editing needs. The Text Editor has two tabs: Rich text and SVG source."
msgid "You can use the Text tool to first create a text box. There are a few options in the tool options if you want to customize how the text will be adding. You will need to drag a rectangle on the canvas to create the text area. Once your text is created, you can edit the text from two ways:"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:54
msgid "Select the text with the shape selection tool (first tool). Press the :kbd:`Enter` key. The text editor will appear."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:55
msgid "Select the text with the shape selection tool (first tool). Then click the Text tool. In the tool options there is an :guilabel:`Edit Text` button. When you click that the text editor window will appear."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:58
msgid "Editing"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:58
msgid "If you are unfamiliar with the way svg text works, use the rich text tab, it will allow you to edit the text as you see it, at the cost of not having all functionality."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:60
msgid "If you are a little bit more familiar with svg text, you can directly edit the SVG source. Do note that certain things, like stroke, fill, letter-spacing don't convert back to the rich text editor, so do be careful when switching back."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:62
msgid "Press :guilabel:`Save` as you're done with your edits to preview them on canvas."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:64
msgid "File"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:66
msgid "Save :kbd:`Ctrl + S`"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:67
msgid "Save current edits to the text on canvas."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:69
msgid "Close :kbd:`Ctrl + W`"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:69
-msgid "Close the editor"
+msgid "Close the editor."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:72
msgid "Basic editing functions:"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:74
msgid "Undo :kbd:`Ctrl + Z`"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:75
msgid "Undo the last action in the text editor."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:76
msgid "Redo :kbd:`Ctrl + Shift + Z`"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:77
msgid "Redo the last undone action in the text editor."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:78
msgid "Cut :kbd:`Ctrl + X`"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:79
msgid "Cut selected text to the clipboard."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:80
msgid "Copy :kbd:`Ctrl + C`"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:81
msgid "Copy selected text to the clipboard."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:82
msgid "Paste :kbd:`Ctrl + V`"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:83
msgid "Paste text from the clipboard."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:84
msgid "Select all :kbd:`Ctrl + A`"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:85
msgid "Select all text in the active editor."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:86
msgid "Deselect :kbd:`Ctrl + Shift + A`"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:87
msgid "Deselect any selected text."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:88
msgid "Find :kbd:`Ctrl + F`"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:89
msgid "Pops up a window with an input to find the given text in the active editor."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:90
msgid "Find Next :kbd:`F3`"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:91
msgid "Searches for the next text using the last search key."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:92
msgid "Find Previous :kbd:`Shift + F3`"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:93
msgid "Searches for the last text using the last search key."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:95
msgid "Edit"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:95
msgid "Replace... :kbd:`Ctrl + R`"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:95
msgid "Pops up a dialog with two inputs: The string you wish to find, and the string you wish to replace it with. Will always replace ALL found instances."
msgid "Pops up a dialog that allows you to search for special characters that are difficult to type in with your keyboard."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:109
msgid "Format"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:111
msgid "Bold :kbd:`Ctrl + B`"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:112
msgid "Set the font-weight to **bold**."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:113
msgid "Italic :kbd:`Ctrl + I`"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:114
msgid "Sets the selected text *italic*."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:115
msgid "Underline :kbd:`Ctrl + U`"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:116
msgid "Underline the selected text."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:117
msgid "Strike-Through"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:118
msgid "Adds a strike-through text decoration."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:119
msgid "Superscript :kbd:`Ctrl + Shift + P`"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:120
msgid "Sets the text to super-script baseline."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:121
msgid "Subscript :kbd:`Ctrl + Shift + B`"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:122
msgid "Sets the text to subscript baseline."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:123
msgid "Weight"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:124
msgid "Sets the font weight a little more specifically. Possibilities are... Light, Normal, Bold, and Black."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:125
msgid "Align Left"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:126
msgid "Align the selected paragraph to the left."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:127
msgid "Align Center :kbd:`Ctrl + Alt + C`"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:128
msgid "Center the selected paragraph."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:130
msgid "Align Right :kbd:`Ctrl + Alt + R`"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:130
msgid "Align the selected paragraph to the right."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:132
msgid "Settings"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:135
msgid "Settings..."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:135
msgid "Calls up the text-editor settings dialog."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:138
msgid "Text Editor Settings"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:140
msgid "The settings that can be configured for the text editor."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:142
msgid "Editor Mode"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:143
msgid "Whether you want both the Rich Text Editor and the SVG Source Editor, or only one of either."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:145
msgid "Here you can configure the syntax highlighting for the SVG source."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:147
msgid "Keyword"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:148
msgid "These highlights important characters like <, /, and >."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:149
msgid "Element"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:150
msgid "The format for highlighting the element tag name. **text** and **tspan** are examples of element names."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:151
msgid "Attribute"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:152
msgid "The format for highlighting the attributes of the tag. For example, font-family, when it isn't in the style tag is usually written as an attribute."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:153
msgid "Value"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:154
msgid "The format for highlighting value of attributes."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:155
msgid "Comment"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:156
msgid "This highlights xml comments, which are written as following: ``<!-- This is an xml comment -->``. Comments are pieces of text that never get interpreted."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:157
msgid "Editor Text Color"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:158
msgid "The main color of the editor."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:160
msgid "Colors"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:160
msgid "Editor background color"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:160
msgid "The main background color of the editor."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:163
msgid "Fonts"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:163
msgid "This allows you to filter the selection of fonts in the editor by writing system. Some systems have a lot of fonts specifically for showing foreign languages properly, but these might not be useful for you. You just tick the writing systems which you use yourself, and the font drop-down will only show fonts that have full support for that language."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:166
msgid "Fine typographic control with the SVG Source tab"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:168
msgid "So, the rich text editor cannot control all functionality that SVG text allows for. For that, you will need to touch the SVG source directly. But to do that, you will first need to go to the text editor settings and enable either :guilabel:`SVG Source` or :guilabel:`Both`. The Rich Text editor will lose some information, so if you go all out, use :guilabel:`SVG Source`."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:171
msgid "Word-spacing, Letter-spacing and Kerning"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:173
msgid "These three are written and read from the rich text tab, but have no sliders associated with them, because there was no time."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:176
msgid "`Kerning, in SVG 1.1 <https://www.w3.org/TR/SVG/text.html#KerningProperty>`_ behaves slightly differently than font-kerning in css. Krita by default uses the auto property for this, which means it is on. To turn it off use kerning:0 in the style section of the text."
msgid "This is the distance between letters in pts, usually. Just write ``letter-spacing`` in the style and add a distance in pts behind it. A negative value will decrease the value between letters."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:190
msgid "This is the extra distance between words, defaulting to pts. By default, ``word-spacing: 0;`` will have it use only the width of the space character for that font. A negative value will decrease the amount of space between words:"
msgid "These are even finer-grained controls that can be used to position text. However, they CANNOT be reliably converted to the format of the rich text editor, because the rich text editor uses these to figure out if a line is a new-line and thus writes to these."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:211
msgid "X and Y"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:212
msgid "X and Y are absolute coordinates. But because you cannot change the absolute coordinates of the text from the editor, these get added to the position when they show up in a tspan."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:214
msgid "dx and dy"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:214
msgid "These are relative coordinates to the position of the previous letter."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:217
msgid "Font-stretch and Small-caps"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:219
msgid "These can also be stored and written to the rich text tab's internal format, but they don't get used in the on screen text object."
msgid "These are not stored in the rich text right now, and while they can be written into the SVG text, the SVG text-shape doesn't do anything with them."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/text.rst:226
msgid "Krita generates font-size-adjust for the font when coming from rich text, as this can help designers when they want to use the SVG source as a basis for later adjustments."
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-06-15 09:36+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../<rst_epilog>:46
msgid ""
".. image:: images/icons/transform_tool.svg\n"
" :alt: tooltransform"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:1
msgid "Krita's transform tool reference."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:13
msgid "Tools"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:13
msgid "Transform"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:18
msgid "Transform Tool"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:20
msgid "|tooltransform|"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:22
msgid "The Transform tool lets you quickly transform the current selection or layer. Basic transformation options include resize, rotate and skew. In addition, you have the option to apply advanced transforms such as Perspective, Warp, Cage and Liquid. These are all powerful options and will give you complete control over your selections/layers."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:24
msgid "When you first invoke the tool, handles will appear at the corners and sides, which you can use to resize your selection or layer. You can perform rotations by moving the mouse above or to the left of the handles and dragging it. You can also click anywhere inside the selection or layer and move it by dragging the mouse."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:26
msgid "You can fine-tune the transform tool parameters using tool options docker. The parameters are split between five tabs: Free Transform, Warp, Perspective, Cage and Liquify."
-msgid "This allows you to do basic rotation, resizing, flipping, and even perspective skewing if you hold :kbd:`Ctrl`. Holding the :kbd:`Shift` key will maintain your aspect ratio throughout the transform."
+msgid "This allows you to do basic rotation, resizing, flipping, and even perspective skewing if you hold the :kbd:`Ctrl` key. Holding the :kbd:`Shift` key will maintain your aspect ratio throughout the transform."
msgid "If you look at the bottom, there are quick buttons for flipping horizontally, vertically and rotating 90 degrees left and right. Furthermore, the button to the left of the anchor point widget allows you to choose whether to always transform using the anchor point, or not."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:43
msgid "`Video of how to use the anchor point for resizing. <https://www.youtube.com/watch?v=grzccBVd0O8>`_"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:46
msgid "Perspective"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:48
msgid "While free transform has some perspective options, the perspective transform allows for maximum control. You can drag the corner points, or even the designated vanishing point."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:50
msgid "You can also change the size, shear and position transform while remaining in perspective with the tool-options."
msgid "There are warp options: Rigid, Affine and Similtude. These change the algorithm used to determine the strength of the deformation. The flexibility determines, how strong the effect of moving these points are."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:72
msgid "Anchor Points"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:74
msgid "You can divide these either by subdivision or drawing custom points."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:76
msgid "Subdivision"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:77
msgid "This allows you to subdivide the selected area into a grid."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:79
msgid "Draw"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:79
msgid "Draw the anchor points yourself. Locking the points will put you in transform mode. Unlocking the points back into edit mode."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:82
msgid "Cage"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:84
msgid "Create a cage around an image, and when it's closed, you can use it to deform the image. If you have at the least 3 points on the canvas, you can choose to switch between deforming and editing the existing points."
msgid "Transforming a straight banana to be curved with the cage tool."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:91
msgid "Adjust Granularity"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:95
msgid "This adjusts the precision of the cage transform grid. Lower precision gives more speed but also gives less precise results."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:97
msgid "Preview"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:98
msgid "Adjusts the granularity of the preview. It is recommended to have this lower than the :guilabel:`Real` value, as it speeds up adjusting."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:100
msgid "Real"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:100
msgid "Adjusts the granularity of the final result."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:103
msgid "Hotkeys"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:105
-msgid "Both Cage and Warp use little nodes. These nodes can be selected and deselected together by pressing :kbd:`Ctrl` before clicking nodes."
+msgid "Both Cage and Warp use little nodes. These nodes can be selected and deselected together by pressing the :kbd:`Ctrl` key before clicking nodes."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:107
-msgid "Then you can move them by pressing the cursor inside the bounding box. Rotating is done by pressing and dragging the cursor outside the bounding box and scaling the same, only one presses :kbd:`Ctrl` before doing the motion."
+msgid "Then you can move them by pressing the cursor inside the bounding box. Rotating is done by pressing and dragging the cursor outside the bounding box and scaling the same, only one presses the :kbd:`Ctrl` key before doing the motion."
msgid "This is either :guilabel:`Wash` or :guilabel:`Build up`. :guilabel:`Wash` will normalize the effect to be between none, and the amount parameter as maximum. :guilabel:`Build up` will just add on until it's impossible."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:137
msgid "Size"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:138
msgid "The brush size. The button to the right allow you to let it scale with pressure."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:139
msgid "Amount"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:140
msgid "The strength of the brush. The button to the right lets it scale with tablet pressure."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:141
msgid "Flow"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:142
msgid "Only applicable with :guilabel:`Build up`."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:143
msgid "Spacing"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:144
msgid "The spacing of the liquify dabs."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:146
msgid "Reverse"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:146
msgid "Reverses the action, so grow becomes shrink, rotate results in clockwise becoming counter-clockwise."
msgid "Liquify on the left and deform brush on the right."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:152
msgid "Krita also has a :ref:`deform_brush_engine` which is much faster than liquify, but has less quality. If you are attempting to make liquefy a little faster, note that it speeds up with the less information it needs to process, so working with liquefy within a selection or using liquefy on a separate layer with little on it will greatly enhance the speed."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:155
msgid "Recursive Transform"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:156
msgid "The little spider icon on the lower-left of the transform tool options is the :guilabel:`Recursive Transform`."
msgid "Recursive transform transforms all the layers in the group, so with this apple, both the lineart as the fill will be transformed."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:162
msgid "Recursive transform, when toggled, allows you to mass-transform all the layers in a group when only transforming the group."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:165
msgid "Continuous Transform"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:167
-msgid "If you apply a transformation, and try to start a new one directly afterwards, Krita will attempt to recall the previous transform, so you can continue it. This is the *continuous transform*. You can press :kbd:`Esc` to cancel this and start a new transform, or press :guilabel:`Reset` in the tool options while no transform is active."
+msgid "If you apply a transformation, and try to start a new one directly afterwards, Krita will attempt to recall the previous transform, so you can continue it. This is the *continuous transform*. You can press the :kbd:`Esc` key to cancel this and start a new transform, or press :guilabel:`Reset` in the tool options while no transform is active."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:170
msgid "Transformation Masks"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:172
msgid "These allow you make non-destructive transforms, check :ref:`here <transformation_masks>` for more info."
msgid "The zoom tool allows you to zoom your canvas in and out discretely. It can be found at the bottom of the toolbox, and you just activate it by selecting the tool, and doing |mouseleft| on the canvas will zoom in, while |mouseright| will zoom out."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/zoom.rst:22
msgid "You can reverse this behavior in the :guilabel:`Tool Options`."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/zoom.rst:24
msgid "There's a number of hotkeys associated with this tool, which makes it easier to access from the other tools:"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/zoom.rst:26
-msgid ":kbd:`Ctrl + Space` + |mouseleft| + drag on the canvas will zoom in or out fluently."
+msgid ":kbd:`Ctrl + Space +` |mouseleft| :kbd:`+ drag` on the canvas will zoom in or out fluently."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/zoom.rst:27
-msgid ":kbd:`Ctrl` + |mousemiddle| + drag on the canvas will zoom in or out fluently."
+msgid ":kbd:`Ctrl +` |mousemiddle| :kbd:`+ drag` on the canvas will zoom in or out fluently."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/zoom.rst:28
-msgid ":kbd:`Ctrl + Alt + Space` + |mouseleft| + drag on the canvas will zoom in or out with discrete steps."
+msgid ":kbd:`Ctrl + Alt + Space +` |mouseleft| :kbd:`+ drag` on the canvas will zoom in or out with discrete steps."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/zoom.rst:29
-msgid ":kbd:`Ctrl + Alt +` |mousemiddle| + drag on the canvas will zoom in or out with discrete steps."
+msgid ":kbd:`Ctrl + Alt +` |mousemiddle| :kbd:`+ drag` on the canvas will zoom in or out with discrete steps."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/zoom.rst:30
msgid ":kbd:`+` will zoom in with discrete steps."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/zoom.rst:31
msgid ":kbd:`-` will zoom out with discrete steps."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/zoom.rst:32
msgid ":kbd:`1` will set the zoom to 100%."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/zoom.rst:33
msgid ":kbd:`2` will set the zoom so that the document fits fully into the canvas area."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/zoom.rst:34
msgid ":kbd:`3` will set the zoom so that the document width fits fully into the canvas area."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/zoom.rst:36
-msgid "For more information on such hotkeys, check :ref:`navigation`."
+msgid "For more information on such hotkeys, check :ref:`navigation`."
msgid "Simón Sanchez' \"Learn to Create Pixel Art from Zero\" course on Udemy"
msgstr ""
#. +> trunk5
#: ../../resources_page.rst:104
msgid "User-made Python Plugins"
msgstr ""
#. +> trunk5
#: ../../resources_page.rst:105
msgid "To install and manage your plugins, visit the :ref:`krita_python_plugin_howto` area. See the second area on how to get Krita to recognize your plugin."
msgid "Have a resource you made and want to to share it with other artists? Let us know in the forum or visit our chat room to discuss getting the resource added to here."
msgid "Krita doesn't have clipping mask functionality in the manner that Photoshop and programs that mimic Photoshop's functionality have. That's because in Krita, unlike such software, a group layer is not an arbitrary collection of layers. Rather, in Krita, group layers are composited separately from the rest of the stack, and then the result is added into the stack. In other words, in Krita group layers are in effect a separate image inside your image."
-msgid "Here we have an image with line art and a layer for each flat of colors. We want to add complicated multi-layered shading to this, while keeping the neatness of the existing color flats. To get a clipping mask working, you first need to put layers into a group. You can do this by making a group layer and drag-and-dropping the layers into it, or by selecting the layers you want grouped and pressing :kbd:`Ctrl+G`. Here we do that with the iris and the eye-white layers."
+msgid "Here we have an image with line art and a layer for each flat of colors. We want to add complicated multi-layered shading to this, while keeping the neatness of the existing color flats. To get a clipping mask working, you first need to put layers into a group. You can do this by making a group layer and drag-and-dropping the layers into it, or by selecting the layers you want grouped and pressing the :kbd:`Ctrl + G` shortcut. Here we do that with the iris and the eye-white layers."
msgid "In the above, we have our layer with a white scribble on the left, and on the right, the same layer, but with alpha inheritance active, limiting it to the combined area of the iris and eye-white layers."
-msgid "Now there’s an easier way to set up alpha inheritance. If you select a layer or set of layers and press :kbd:`Ctrl+Shift+G`, you create a quick clipping group. That is, you group the layers, and a ‘mask layer’ set with alpha inheritance is added on top."
+msgid "Now there’s an easier way to set up alpha inheritance. If you select a layer or set of layers and press the :kbd:`Ctrl + Shift + G` shortcut, you create a quick clipping group. That is, you group the layers, and a ‘mask layer’ set with alpha inheritance is added on top."
msgid "The fact that alpha inheritance can use the composited transparency from a combination of layers means that you can have a layer with the erase-blending mode in between, and have that affect the area that the layer above is clipped to. Above, the lower image is exactly the same as the upper one, except with the erase-layer hidden. Filters can also affect the alpha inheritance:"
msgid "Krita's main goal is to help artists create a digital painting from scratch. Krita is used by comic artists, matte painters, texture artists, and illustrators around the world. This section explains some common workflow that artists use in Krita. When you open a new document in Krita for the first time, you can start painting instantly. The brush tool is selected by default and you just have to paint on the canvas. However, let us look at what artists do in Krita. Below are some of the common workflows used in Krita:"
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:20
msgid "Speed Painting and Conceptualizing"
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:22
msgid "Some artists work only on the digital medium, sketching and visualizing concepts in Krita from scratch. As the name suggests a technique of painting done within a matter of hours to quickly visualize the basic scene, character, look and feel of the environment or to denote the general mood and overall concept is called a **speed painting**. Finishing and finer details are not the main goals of this type of painting, but the representation of form value and layout is the main goal."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:24
msgid "Some artists set a time limit to complete the painting while some paint casually. Speed painting then can be taken forward by adding finer details and polish to create a final piece. Generally, artists first block in the composition by adding patches and blobs of flat colors, defining the silhouette, etc. Krita has some efficient brushes for this situation, for example, the brush under **Block Tag** like Block fuzzy, Block basic, layout_block, etc."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:26
-msgid "After the composition and a basic layout has been laid out the artists add as many details as possible in the given limited time, this requires a decent knowledge of forms, value perspective and proportions of the objects. Below is an example of speed paint done by `David Revoy <http://www.davidrevoy.com/>`_ in an hours time."
+msgid "After the composition and a basic layout has been laid out the artists add as many details as possible in the given limited time, this requires a decent knowledge of forms, value perspective and proportions of the objects. Below is an example of speed paint done by `David Revoy <https://www.davidrevoy.com/>`_ in an hours time."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:32
-msgid "Artwork by David Revoy, license : `CC-BY <http://creativecommons.org/licenses/by/3.0/>`_"
+msgid "Artwork by David Revoy, license : `CC-BY <https://creativecommons.org/licenses/by/3.0/>`_"
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:34
msgid "You can view the recorded speed painting demo for the above image `on Youtube <https://www.youtube.com/watch?v=93lMLEuxSLk>`_."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:37
msgid "Colorizing Line Art"
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:39
msgid "Often an artist, for example, a comic book colorist will need to take a pencil sketch or other line art of some sort and use Krita to paint underneath it. This can be either an image created digitally or something that was done outside the computer and has been scanned."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:42
msgid "Preparing the line art"
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:44
msgid "If your images have a white or other single-tone background, you can use either of the following methods to prepare the art for coloring:"
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:46
msgid "Place the line art at the top of the layer stack and set its layer blending mode to :guilabel:`Multiply`"
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:48
-msgid "If you want to clean the line art a bit you can press :kbd:`Ctrl + L` or go to :menuselection:`Filters --> Adjust --> Levels`"
+msgid "If you want to clean the line art a bit you can press the :kbd:`Ctrl + L` shortcut or go to :menuselection:`Filters --> Adjust --> Levels`"
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:53
msgid "You can clean the unwanted grays by moving the white triangle in the input levels section to left and darken the black by moving the black triangle to right."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:55
-msgid "If you draw in blue pencils and then ink your line art you may need to remove the blue lines first to do that go to :menuselection:`Filters --> Adjust --> Color adjustment` curves or press shortcut :kbd:`Ctrl + M`."
+msgid "If you draw in blue pencils and then ink your line art you may need to remove the blue lines first to do that go to :menuselection:`Filters --> Adjust --> Color adjustment` curves or press the :kbd:`Ctrl + M` shortcut."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:60
msgid "Now select **Red** from the drop-down, click on the top right node on the graph and slide it all the way down. Or you can click on the top right node and enter **0** in the input field. Repeat this step for **Green** too."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:65
msgid "Now the whole drawing will have a blue overlay, zoom in and check if the blue pencil lines are still visible slightly. If you still see them, then go to **Blue** Channel in the color adjustment and shift the top right node towards left a bit, Or enter a value around 190 (one that removes the remaining rough lines) in the input box."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:70
-msgid "Now apply the color adjustment filter, yes we still have lots of blue on the artwork. Be patient and move on to the next step. Go to :menuselection:`Filters --> Adjust --> Desaturate` or press :kbd:`Ctrl + Shift + U`. Now select :guilabel:`Max` from the list."
+msgid "Now apply the color adjustment filter, yes we still have lots of blue on the artwork. Be patient and move on to the next step. Go to :menuselection:`Filters --> Adjust --> Desaturate` or press the :kbd:`Ctrl + Shift + U` shortcut. Now select :guilabel:`Max` from the list."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:75
msgid "It is good to use non-photo-blue pencils to create the blue lines as those are easy to remove. If you are drawing digitally in blue lines use #A4DDED color as this is closer to non-photo-blue color."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:77
-msgid "You can learn more about doing a sketch from blue sketch to digital painting `here in a tutorial by David Revoy <http://www.davidrevoy.com/article239/cleaning-blue-lines-sketch-in-krita>`_."
+msgid "You can learn more about doing a sketch from blue sketch to digital painting `here in a tutorial by David Revoy <https://www.davidrevoy.com/article239/clean-blue-sketch-traditional-line-art-to-color-it-digital-with-in-krita>`_."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:79
msgid "After you have a clean black and white line art you may need to erase the white color and keep only black line art, to achieve that go to :menuselection:`Filters --> Color --> Color to Alpha`. Use the dialog box to turn all the white areas of the image transparent. The Color Picker is set to White by default. If you have imported scanned art and need to select another color for the paper color then you would do it here."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:84
msgid "This will convert the white color in your line art to alpha i.e. it will make the white transparent leaving only the line art. Your line art can be in grayscale color space, this is a unique feature in Krita which allows you to keep a layer in a color-space independent from the image."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:87
msgid "Laying in Flat Colors"
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:89
msgid "There are many ways to color a line art in Krita, but generally, these three are common among the artists."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:91
msgid "Paint blocks of color directly with block brushes."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:92
msgid "Fill with Flood fill Tool."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:93
msgid "Use one of the G'MIC colorize comics filters."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:96
msgid "Blocking with brush"
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:98
msgid "The first is the more traditional method of taking a shape brush or using the geometric tools to lay in color. This would be similar to using an analog marker or brush on paper. There are various block brushes in Krita, you can select **Block** Tag from the drop-down in the brush presets docker and use the brushes listed there."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:100
-msgid "Add a layer underneath your line art layer and start painting with the brush. If you want to correct any area you can press :kbd:`E` and convert the same brush into an eraser. You can also use a layer each for different colors for more flexibility."
+msgid "Add a layer underneath your line art layer and start painting with the brush. If you want to correct any area you can press the :kbd:`E` key and convert the same brush into an eraser. You can also use a layer each for different colors for more flexibility."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:103
msgid "Filling with Flood Fill tool"
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:105
msgid "The second method is to use the Flood fill tool to fill large parts of your line art quickly. This method generally requires closed gaps in the line art. To begin with this method place your line art on a separate layer. Then activate the flood fill tool and set the :guilabel:`Grow selection` to 2px, uncheck :guilabel:`Limit to current layer` if previously checked."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:110
msgid "Choose a color from color selector and just click on the area you want to fill the color. As we have expanded the fill with grow selection the color will be filled slightly underneath the line art thus giving us a clean fill."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:113
msgid "GMIC Colorize [Interactive]"
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:115
msgid "The third method is to use take advantage of the integrated G'Mic filters. These are powerful filters that can dramatically improve your workflow and cut you down on your production time. To begin coloring with the G'MIC colorize interactive, go to :menuselection:`Filters --> G'MIC`. Choose :menuselection:`Filters --> G'MIC --> Black & white --> Colorize[interactive]` from the list of filters. Then select Line art for :menuselection:`Input type, Image + Colors (2 Layers)` for output type, set the view resolution according to your need. If you have any specific color palette to use for coloring add the path for it in an additional color palette. The example of the filter window with the required inputs is shown below."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:121
msgid "Press **Apply** to begin the coloring, this will open a color selector **palette** window and a window showing your line art. Choose the color from the palette and click on the areas that need to be filled with color like the example shown below."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:126
-msgid "If you feel that the dots are a bit distracting you can press :kbd:`Tab` to reduce the size or hide the dots. To zoom out you can press :kbd:`Ctrl + ↓` and :kbd:`Ctrl + ↑` vice versa. Panning is done by |mousemiddle| + drag. Press :kbd:`Spacebar` to generate the colors. If you want to replace a color select the color by |mousemiddle| and pressing :kbd:`R` then you can select an alternate color from the palette."
+msgid "If you feel that the dots are a bit distracting you can press the :kbd:`Tab` key to reduce the size or hide the dots. To zoom out you can press :kbd:`Ctrl + ↓` and :kbd:`Ctrl + ↑` shortcuts and vice versa. Panning is done by |mousemiddle| :kbd:`+ drag`. Press the :kbd:`Spacebar` key to generate the colors. If you want to replace a color select the color by |mousemiddle| and pressing the :kbd:`R` key then you can select an alternate color from the palette."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:128
-msgid "Once you have finished adding the desired flat colors you can press :kbd:`Enter` to apply the filter. Then don't forget to press **Ok** in the G'MIC dialog box."
+msgid "Once you have finished adding the desired flat colors you can press the :kbd:`Enter` key to apply the filter. Then don't forget to press **Ok** in the G'MIC dialog box."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:130
-msgid "The flats colors will be placed on a separate layer. You can check `this <http://www.davidrevoy.com/article240/gmic-line-art-colorization>`_ tutorial by David Revoy to know more about this technique."
+msgid "The flats colors will be placed on a separate layer. You can check `this <https://www.davidrevoy.com/article240/gmic-line-art-colorization>`_ tutorial by David Revoy to know more about this technique."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:133
msgid "GMIC Colorize [comics]"
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:135
msgid "Krita provides one more option to prepare flat colors through G'MIC colorize comics filter. This technique needs some preparations before you run the G'MIC filter. This layer extrapolates the color spots that you input below the line art"
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:137
msgid "You have to create two layers below the line art, one for the color spots indicating which color you need to be filled in the region and one for the final extrapolated output of the filter. Mark some colors spots in the layer beneath the line art. The layer setup can be seen in the image below."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:142
msgid "The colors spots are marked in red in the image"
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:144
msgid "Now go to :menuselection:`Filters --> G'MIC --> Black & white --> Colorize[comics]`. In the G'MIC dialog box, select :guilabel:`All` for input and :guilabel:`In place (default)` for output, select :guilabel:`Lineart + color spots + extrapolated layers` for both input and output layers on the right-hand side. Smoothness is for filling gap tolerance and details the default is 0.5 you can adjust it according to your line art."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:149
-msgid "Press **Apply** and **Ok** to apply and exit the G'MIC dialog. You'll now have flat colors beneath your line art. More details about this technique can be found in the tutorial `at Timothée Giet's blog <http://timotheegiet.com/blog/comics/gmic-colorize-comics-working-in-krita.html>`_."
+msgid "Press **Apply** and **Ok** to apply and exit the G'MIC dialog. You'll now have flat colors beneath your line art. More details about this technique can be found in the tutorial `at Timothée Giet's blog <https://timotheegiet.com/blog/comics/gmic-colorize-comics-working-in-krita.html>`_."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:153
msgid "Painting"
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:156
msgid "Starting from chaos"
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:158
msgid "Here, you start by making a mess through random shapes and texture, then taking inspirations from the resulting chaos you can form various concepts. It is kind of like making things from clouds or finding recognizable shapes of things in abstract and random textures. Many concept artists work with this technique."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:160
msgid "You can use brushes like the shape brush, or the spray brush to paint a lot of different shapes, and from the resulting noise, you let your brain pick out shapes and compositions."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:165
msgid "You then refine these shapes to look more like shapes you think they look, and paint them over with a normal paintbrush. This method is best done in a painting environment."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:168
msgid "Starting from a value based underground"
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:170
msgid "This method finds its origins in old oil-painting practice: You first make an under-painting and then paint over it with color, having the dark underground shine through."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:172
msgid "With Krita you can use blending modes for this purpose. Choosing the color blending mode on a layer on top allows you to change the colors of the image without changing the relative luminosity. This is useful, because humans are much more sensitive to tonal differences than the difference in saturation and hue. This'll allow you to work in grayscale before going into color for the polishing phase."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:174
-msgid "You can find more about this technique `here <http://www.davidrevoy.com/article185/tutorial-getting-started-with-krita-1-3-bw-portrait>`_."
+msgid "You can find more about this technique `here <https://www.davidrevoy.com/article185/tutorial-getting-started-with-krita-1-3-bw-portrait>`_."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:177
msgid "Preparing Tiles and Textures"
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:179
msgid "Many artists use Krita to create textures for 3d assets used for games animation etc. Krita has many texture templates for you to choose and get started with creating textures. These templates have common sizes, bit depth and color profiles that are used for texturing workflow."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:181
-msgid "Krita also has a real-time seamless tile mode to help texture artist prepare tiles and texture easily and check if it is seamless on the fly. The tiled mode is called wrap-around mode, to activate this mode you have press :kbd:`W`. Now when you paint the canvas is tiled in real-time allowing you to create seamless pattern and texture, it is also easy to prepare interlocking patterns and motifs in this mode."
+msgid "Krita also has a real-time seamless tile mode to help texture artist prepare tiles and texture easily and check if it is seamless on the fly. The tiled mode is called wrap-around mode, to activate this mode you have press the :kbd:`W` key. Now when you paint the canvas is tiled in real-time allowing you to create seamless pattern and texture, it is also easy to prepare interlocking patterns and motifs in this mode."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:184
msgid "Creating Pixel Art"
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:186
msgid "Krita can also be used to create a high definition pixel painting. The pixel art look can be achieved by using Index color filter layer and overlaying dithering patterns. The general layer stack arrangement is as shown below."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:191
msgid "The index color filter maps specific user-selected colors to the grayscale value of the artwork. You can see the example below, the strip below the black and white gradient has an index color applied to it so that the black and white gradient gets the color selected to different values."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:196
msgid "You can choose the required colors and ramps in the index color filter dialog as shown below."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:201
msgid "Dithering can be used to enhance the look of the art and to ease the banding occurred by the index color filter. Krita has a variety of dithering patterns by default, these can be found in pattern docker. You can use these patterns as fill layer, then set the blend mode to **overlay** and adjust the opacity according to your liking. Generally, an opacity range of 10% - 25% is ideal."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:203
msgid "Paint the artwork in grayscale and add an index color filter layer at the top then add the dithering pattern fill layer below the index color filter but above the artwork layer, as shown in the layer stack arrangement above. You can paint or adjust the artwork at any stage as we have added the index color filter as a filter layer."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:205
msgid "You can add different groups for different colors and add different dithering patterns for each group."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:207
msgid "Below is an example painted with this layer arrangement."
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-05-04 09:38+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../<rst_epilog>:2
msgid ""
".. image:: images/icons/Krita_mouse_left.png\n"
" :alt: mouseleft"
msgstr ""
#. +> trunk5
#: ../../<rst_epilog>:4
msgid ""
".. image:: images/icons/Krita_mouse_right.png\n"
" :alt: mouseright"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:1
msgid "Common workflows used in Krita"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:13
msgid "Flat Coloring"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:15
msgid "So you've got a cool black on white drawing, and now you want to color it! The thing we’ll aim for in this tutorial is to get your line art colored in with flat colors. So no shading just yet. We’ll be going through some techniques for preparing the line art, and we’ll be using the layer docker to put each color on a separate layer, so we can easily access each color when we add shading."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:17
msgid "This tutorial is adapted from this `tutorial <http://theratutorial.tumblr.com/post/66584924501/flat-colouring-in-the-kingdom-of-2d-layers-are>`_ by the original author."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:20
msgid "Understanding Layers"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:22
msgid "To fill line art comfortably, it's best to take advantage of the layerstack. The layer stack is pretty awesome, and it's one of those features that make digital art super-convenient."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:24
msgid "In traditional art, it is not uncommon to first draw the full background before drawing the subject. Or to first draw a line art and then color it in. Computers have a similar way of working."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:26
msgid "In programming, if you tell a computer to draw a red circle, and then afterwards tell it to draw a smaller yellow circle, you will see the small yellow circle overlap the red circle. Switch the commands around, and you will not see the yellow circle at all: it was drawn before the red circle and thus ‘behind’ it."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:28
msgid "This is referred to as the “drawing order”. So like the traditional artist, the computer will first draw the images that are behind everything, and layer the subject and foreground on top of it. The layer docker is a way for you to control the drawing order of multiple images, so for example, you can have your line art drawn later than your colors, meaning that the lines will be drawn over the colors, making it easier to make it neat!"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:30
msgid "Other things that a layer stack can do are blending the colors of different layers differently with blending modes, using a filter in the layer stack, or using a mask that allows you to make parts transparent."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:32
msgid "Programmers talk about transparency as ''Alpha'', which is because the 'a' symbol is used to present transparency in the algorithms for painting one color on top of another. Usually when you see the word ''Alpha'' in a graphics program, just think of it as affecting the transparency."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:35
msgid "Preparing your line art"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:37
msgid "Put the new layer underneath the layer containing the line art (drag and drop or use the up/down arrows for that), and draw on it."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:42
msgid "…And notice nothing happening. This is because the white isn’t transparent. You wouldn’t really want it to either, how else would you make convincing highlights? So what we first need to do to color in our drawing is prepare our line art. There’s several methods of doing so, each with varying qualities."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:45
msgid "The Multiply Blending Mode"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:47
msgid "So, typically, to get a black and white line art usable for coloring, you can set the blending mode of the line art layer to Multiply. You do this by selecting the layer and going to the drop-down that says **Normal** and setting that to **Multiply**."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:52
msgid "And then you should be able to see your colors!"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:54
msgid "Multiply is not a perfect solution however. For example, if through some image editing magic I make the line art blue, it results into this:"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:59
msgid "This is because multiply literally multiplies the colors. So it uses maths!"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:61
msgid "What it first does is take the values of the RGB channels, then divides them by the max (because we're in 8bit, this is 255), a process we call normalising. Then it multiplies the normalized values. Finally, it takes the result and multiplies it with 255 again to get the result values."
msgid "Not actually transparent. Is a little funny with colored lines."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:108
msgid "Using Selections"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:110
msgid "The second method is one where we'll make it actually transparent. In other programs this would be done via the channel docker, but Krita doesn't do custom channels, instead it uses Selection Masks to store custom selections."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:112
msgid "Duplicate your line art layer."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:114
msgid "Convert the duplicate to a selection mask. |mouseright| the layer, then :menuselection:`Convert --> to Selection Mask`."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:118
msgid "Invert the selection mask. :menuselection:`Select --> Invert Selection`."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:120
msgid "Make a new layer, and do :menuselection:`Edit --> Fill with Foreground Color`."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:124
msgid "And you should now have the line art on a separate layer."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:129
msgid "Actual transparency."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:134
msgid "Doesn't work when the line art is colored."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:137
msgid "Using Masks"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:139
msgid "This is a simpler variation of the above."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:141
msgid "Make a filled layer underneath the line art layer."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:145
msgid "Convert the line art layer to a transparency mask |mouseright| the layer, then :menuselection:`Convert --> to Transparency Mask`."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:149
msgid "Invert the transparency mask by going to :menuselection:`Filter --> Adjust --> Invert`"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:156
msgid "Actual transparency. You can also very easily doodle a pattern on the filled layer where the mask is on without affecting the transparency."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:161
msgid "Doesn't work when the line art is colored already. We can still get faster."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:164
msgid "Using Color to Alpha"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:166
msgid "By far the fastest way to get transparent line art."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:168
msgid "Select the line art layer and apply the color to alpha filter. :menuselection:`Filter --> Colors --> Color to Alpha`. The default values should be sufficient for line art."
msgid "Actual transparency. Works with colored line art as well, because it removes the white specifically."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:180
msgid "You'll have to lock the layer transparency or separate out the alpha via the right-click menu if you want to easily color it."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:184
msgid "Coloring the image"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:186
msgid "Much like preparing the line art, there are many different ways of coloring a layer."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:188
msgid "You could for example fill in everything by hand, but while that is very precise it also takes a lot of work. Let's take a look at the other options, shall we?"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:191
msgid "Fill Tool"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:196
msgid "In most cases the fill-tool can’t deal with the anti-aliasing (the soft edge in your line art to make it more smooth when zoomed out) In Krita you have the grow-shrink option. Setting that to say… 2 expands the color two pixels."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:198
msgid "Threshold decides when the fill-tool should consider a different color pixel to be a border. And the feathering adds an extra soft border to the fill."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:200
msgid "Now, if you click on a gapless-part of the image with your preferred color… (Remember to set the opacity to 1.0!)"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:202
msgid "Depending on your line art, you can do flats pretty quickly. But setting the threshold low can result in little artifacts around where lines meet:"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:207
msgid "However, setting the threshold high can end with the fill not recognizing some of the lighter lines. Besides these little artifacts can be removed with the brush easily."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:212
msgid "Pretty darn quick depending on the available settings."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:217
msgid "Again, not great with gaps or details. And it works best with aliased line art."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:220
msgid "Selections"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:222
msgid "Selections work using the selection tools."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:227
-msgid "For example with the :ref:`bezier_curve_selection_tool` you can easily select a curved area, and the with :kbd:`Shift` + |mouseleft| (not |mouseleft| + :kbd:`Shift`, there's a difference!) you can easily add to an existing selection."
+msgid "For example with the :ref:`bezier_curve_selection_tool` you can easily select a curved area, and the with :kbd:`Shift +` |mouseleft| (not |mouseleft| :kbd:`+ Shift`, there's a difference!) you can easily add to an existing selection."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:232
msgid "You can also edit the selection if you have :menuselection:`Select --> Show Global Selection Mask` turned on. Then you can select the global selection mask, and paint on it. (Above with the alternative selection mode, activated in the lower-left corner of the stats bar)"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:234
-msgid "When done, select the color you want to fill it with and press :kbd:`Shift` + `backspace`."
+msgid "When done, select the color you want to fill it with and press the :kbd:`Shift + Backspace` shortcut."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:239
msgid "You can save selections in selection masks by |mouseright| a layer, and then going to :menuselection:`Add --> Local Selection`. You first need to deactivate a selection by pressing the circle before adding a new selection."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:241
msgid "This can serve as an alternative way to split out different parts of the image, which is good for more painterly pieces:"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:249
msgid "A bit more precise than filling."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:254
msgid "Previewing your color isn't as easy."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:257
msgid "Geometric tools"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:259
msgid "So you have a tool for making rectangles or circles. And in the case of Krita, a tool for bezier curves. Select the path tool (|path tool|), and set the tool options to fill=foreground and outline=none. Make sure that your opacity is set to 1.00 (fully opaque)."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:262
msgid ""
".. image:: images/icons/bezier_curve.svg\n"
" :alt: path tool"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:264
msgid "By clicking and holding, you can influence how curvy a line draw with the path tool is going to be. Letting go of the mouse button confirms the action, and then you’re free to draw the next point."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:269
-msgid "You can also erase with a geometric tool. Just press :kbd:`E` or the eraser button."
+msgid "You can also erase with a geometric tool. Just press the :kbd:`E` key or the eraser button."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:277
msgid "Quicker than using the brush or selections. Also decent with line art that contains gaps."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:282
msgid "Fiddly details aren’t easy to fill in with this. So I recommend skipping those and filling them in later with a brush."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:285
msgid "Colorize Mask"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:287
msgid "So, this is a bit of an odd one. In the original tutorial, you'll see I'm suggesting using G'Mic, but that was a few years ago, and G'Mic is a little unstable on windows. Therefore, the Krita developers have been attempting to make an internal tool doing the same."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:289
msgid "It is disabled in 3.1, but if you use 4.0 or later, it is in the toolbox. Check the Colorize Mask for more information."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:291
msgid "So it works like this:"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:293
msgid "Select the colorize mask tool."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:294
msgid "Tick the layer you're using."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:295
msgid "Paint the colors you want to use on the colorize mask"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:296
msgid "Click update to see the results:"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:301
msgid "When you are satisfied, |mouseright| the colorize mask, and go to :menuselection:`Convert --> Paint Layer`. This will turn the colorize mask to a generic paint layer. Then, you can fix the last issues by making the line art semi-transparent and painting the flaws away with a pixel art brush."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:306
msgid "Then, when you are done, split the layers via :menuselection:`Layer --> Split --> Split Layer`. There are a few options you can choose, but the following should be fine:"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:311
msgid "Finally, press **Ok** and you should get the following. Each color patch it on a different layer, named by the palette in the menu and alpha locked, so you can start painting right away!"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:319
msgid "Works with anti-aliased line art. Really quick to get the base work done. Can auto-close gaps."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:324
msgid "No anti-aliasing of its own. You have to choose between getting details right or the gaps auto-closed."
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:327
msgid "Conclusion"
msgstr ""
#. +> trunk5
#: ../../tutorials/flat-coloring.rst:329
msgid "I hope this has given you a good idea of how to fill in flats using the various techniques, as well as getting a hand of different Krita features. Remember that a good flat filled line art is better than a badly shaded one, so keep practicing to get the best out of these techniques!"
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-05-04 09:38+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../tutorials/inking.rst:1
msgid "tips and tricks for inking in Krita"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:13
msgid "Inking"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:15
msgid "The first thing to realize about inking is that unlike anatomy, perspective, composition or color theory, you cannot compensate for lack of practice with study or reasoning. This is because all the magic in drawing lines happens from your shoulder to your fingers, very little of it happens in your head, and your lines improve with practice."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:17
msgid "On the other hand, this can be a blessing. You don’t need to worry about whether you are smart enough, or are creative enough to be a good inker. Just dedicated. Doubtlessly, inking is the Hufflepuff of drawing disciplines."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:19
msgid "That said, there are a few tips to make life easy:"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:22
msgid "Pose"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:24
msgid "Notice how I mentioned up there that the magic happens between your shoulders and fingers? A bit weird, not? But perhaps, you have heard of people talking about adopting a different pose for drawing."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:26
msgid "You can in fact, make different strokes depending on which muscles and joints you use to make the movement: The Fingers, the wrist and lower-arm muscles, the elbow and upper-arm muscles or the shoulder and back muscles."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:34
msgid "Generally, the lower down the arm the easier it is to make precise strokes, but also the less durable the joints are for long term use. We tend to start off using our fingers and wrist a lot during drawing, because it’s easier to be precise this way. But it’s difficult to make long strokes, and furthermore, your fingers and wrist get tired far quicker."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:42
msgid "Your shoulders and elbows on the other hand are actually quite good at handling stress, and if you use your whole hand you will be able to make long strokes far more easily. People who do calligraphy need shoulder based strokes to make those lovely flourishes (personally, I can recommend improving your handwriting as a way to improve inking), and train their arms so they can do both big and small strokes with the full arm."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:44
msgid "To control pressure in this state effectively, you should press your pinky against the tablet surface as you make your stroke. This will allow you to precisely judge how far the pen is removed from the tablet surface while leaving the position up to your shoulders. The pressure should then be put by your elbow."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:46
msgid "So, there are not any secret rules to inking, but if there is one, it would be the following: *The longer your stroke, the more of your arms you need to use to make the stroke*."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:49
msgid "Stroke smoothing"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:51
msgid "So, if the above is the secret to drawing long strokes, that would be why people having been inking lovely drawings for years without any smoothing? Then, surely, it is decadence to use something like stroke smoothing, a short-cut for the lazy?"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:56
msgid ""
".. image:: images/inking/Stroke_rigger.gif\n"
" :alt: rigger brush demonstration"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:56
msgid "Example of how a rigger brush can smooth the original movement (here in red)"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:58
msgid "Not really. To both, actually. Inkers have had a real-life tool that made it easier to ink, it’s called a rigger-brush, which is a brush with very long hairs. Due to this length it sorta smooths out shakiness, and thus a favoured brush when inking at three in the morning."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:60
msgid "With some tablet brands, the position events being sent aren’t very precise, which is why we having basic smoothing to apply the tiniest bit of smoothing on tablet strokes."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:62
msgid "On the other hand, doing too much smoothing during the whole drawing can make your strokes very mechanical in the worst way. Having no jitter or tiny bumps removes certain humanity from your drawings, and it can make it impossible to represent fabric properly."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:64
msgid "Therefore, it’s wise to train your inking hand, yet not to be too hard on yourself and refuse to use smoothing at all, as we all get tired, cold or have a bad day once in a while. Stabilizer set to 50 or so should provide a little comfort while keeping the little irregularities."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:67
msgid "Bezier curves and other tools"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:69
msgid "So, you may have heard of a French curve. If not, it’s a piece of plastic representing a stencil. These curves are used to make perfectly smooth curves on the basis of a sketch."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:71
msgid "In digital painting, we don’t have the luxury of being able to use two hands, so you can’t hold a ruler with one hand and adjust it while inking with the other. For this purpose, we have instead Bezier curves, which can be made with the :ref:`path_selection_tool`."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:73
msgid "You can even make these on a vector layer, so they can be modified on the fly."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:75
msgid "The downside of these is that they cannot have line-variation, making them a bit robotic."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:77
msgid "You can also make small bezier curves with the :ref:`assistant_tool`, amongst the other tools there."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:79
msgid "Then, in the freehand brush tool options, you can tick :guilabel:`Snap to Assistants` and start a line that snaps to this assistant."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:82
msgid "Presets"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:84
msgid "So here are some things to consider with the brush-presets that you use:"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:87
msgid "Anti-aliasing versus jagged pixels"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:89
-msgid "A starting inker might be inclined to always want to use anti-aliased brushes, after all, they look so smooth on the screen. However, while these look good on screen, they might become fuzzy when printing them. Therefore, Krita comes with two default types. Anti-aliased brushes like ink_brush_25 and slightly aliased brushes like ink_tilt, with the latter giving better print results. If you are trying to prepare for both, it might be an idea to consider making the inking page 600dpi and the color page 300dpi, so that the inking page has a higher resolution and the ‘jaggies’ aren’t as visible. You can turn any pixel brush into an aliased brush, by going :kbd:`F5` and ticking **Sharpness**."
+msgid "A starting inker might be inclined to always want to use anti-aliased brushes, after all, they look so smooth on the screen. However, while these look good on screen, they might become fuzzy when printing them. Therefore, Krita comes with two default types. Anti-aliased brushes like ink_brush_25 and slightly aliased brushes like ink_tilt, with the latter giving better print results. If you are trying to prepare for both, it might be an idea to consider making the inking page 600dpi and the color page 300dpi, so that the inking page has a higher resolution and the ‘jaggies’ aren’t as visible. You can turn any pixel brush into an aliased brush, by going the :kbd:`F5` key and ticking **Sharpness**."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:92
msgid "Texture"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:94
msgid "Do you make smooth ‘wet’ strokes? Or do you make textured ones? For the longest time, smooth strokes were preferred, as that would be less of a headache when entering the coloring phase. Within Krita there are several methods to color these easily, the colorize mask being the prime example, so textured becomes a viable option even for the lazy amongst us."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:99
msgid ""
".. image:: images/inking/Inking_patterned.png\n"
" :alt: type of strokes"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:99
msgid "Left: No texture, Center: Textured, Right: Predefined Brush tip"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:102
msgid "Pressure curve"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:104
msgid "Of course, the nicest lines are made with pressure sensitivity, so they dynamically change from thick to thin. However, different types of curves on the pressure give different results. The typical example is a slightly concave line to create a brush that more easily makes thin lines."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:109
msgid ""
".. image:: images/inking/Ink_gpen.png\n"
" :alt: pressure curve for ink gpen"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:109
msgid "Ink_Gpen_25 is a good example of a brush with a concave pressure curve. This curve makes it easier to make thin lines."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:114
msgid ""
".. image:: images/inking/Ink_convex.png\n"
" :alt: convex inking brush"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:114
msgid "conversely, here's a convex brush. The strokes are much rounder"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:119
msgid ""
".. image:: images/inking/Ink_fill_circle.png\n"
" :alt: ink fill circle"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:119
msgid "Fill_circle combines both into an s-curve, this allows for very dynamic brush strokes"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:124
msgid ""
".. image:: images/inking/Ink_speed.png\n"
" :alt: inverse convex to speed parameter"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:124
msgid "Pressure isn't the only thing you can do interesting things with, adding an inverse convex curve to speed can add a nice touch to your strokes"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:127
msgid "Preparing sketches for inking"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:129
msgid "So, you have a sketch and you wish to start inking it. Assuming you’ve scanned it in, or drew it, you can try the following things to make it easier to ink."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:132
msgid "Opacity down to 10%"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:134
-msgid "Put a white (just press :kbd:`Backspace`) layer underneath the sketch. Turn down the opacity of the sketch to a really low number and put a layer above it for inking."
+msgid "Put a white (just press the :kbd:`Backspace` key) layer underneath the sketch. Turn down the opacity of the sketch to a really low number and put a layer above it for inking."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:137
msgid "Make the sketch colored"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:139
msgid "Put a layer filled with a color you like between the inking and sketch layer. Then set that layer to ‘screen’ or ‘addition’, this will turn all the black lines into the color! If you have a transparent background, or put this layer into a group, be sure to tick the alpha-inherit symbol!"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:142
msgid "Make the sketch colored, alternative version"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:144
msgid "Or, right-click the layer, go to layer properties, and untick ‘blue’. This works easier with a single layer sketch, while the above works best with multi-layer sketches."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:147
msgid "Super-thin lines"
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:149
msgid "If you are interested in super-thin lines, it might be better to make your ink at double or even triple the size you usually work at, and, only use an aliased pixel brush. Then, when the ink is finished, use the fill tool to fill in flats on a separate layer, split the layer via :menuselection:`Layer --> Split --> Layer Split`, and then resize to the original size."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:154
msgid "This might be a little of an odd way of working, but it does make drawing thin lines trivial, and it's cheaper to buy RAM so you can make HUGE images than to spent hours on trying to color the thin lines precisely, especially as colorize mask will not be able to deal with thin anti-aliased lines very well."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:157
msgid "David Revoy made a set of his own inking tips for Krita and explains them in this `youtube video <https://www.youtube.com/watch?v=xvQ5l0edsq4>`_."
msgid "Krita uses Gimp’s image hose format which allows for random selection of the images, angle based selection, pressure based selection, and incremental selection (I have no idea what constant does)."
msgid "You can also use animated brush tips to emulate, for example, bristle brush tips that go from very fine bristles to a fully opaque stamp based on pressure, like a dry paintbrush might do. To do this, you would follow the above instructions, but for each layer, create a different cross-section of the brush to correspond with the amount of pressure applied."
msgid "The brightness of the rainbow is relative to the color of the currently selected color, so make sure to select bright saturated colors for a bright rainbow!"
msgid "Uncheck **Pressure** and check **Distance** to make the rainbow paint itself over distance. The slider below can be |mouseright| to change the value with keyboard input."
msgid "Then, the trick is to go into **Opacity**, untoggle **Pressure** from the sensors, toggle **Fade** and then reverse the curve as shown above. Make sure that the curve ends a little above the bottom-right, so that you are always painting something. Otherwise, the smudge won't work."
msgid "The **Fade** sensor will base the stroke length on brush size. The **Distance** sensor will base it on actual pixels, and the **Time** on actual seconds."
msgid "Just adjust the fade-length by |mouseright| on the slider bar. You can then input a number. In the screenshot, I have 500, but the sweet spot seems to be somewhere between 150 and 200."
msgid "Now, you'll notice that on the start of a stroke, it might be a little faded, so go into **Color Rate** and turn off the **Enable Pen Settings** there."
msgid "Okay, so I’ve wanted to do a tutorial for transform masks for a while now, and this is sorta ending up to be a flower-drawing tutorial. Do note that this tutorial requires you to use **Krita 2.9.4 at MINIMUM**. It has a certain speed-up that allows you to work with transform masks reliably!"
msgid "I like drawing flowers because they are a bit of an unappreciated subject, yet allow for a lot of practice in terms of rendering. Also, you can explore cool tricks in Krita with them."
msgid "Today’s flower is the Azalea flower. These flowers are usually pink to red and appear in clusters, the clusters allow me to exercise with transform masks!"
msgid "I got an image from Wikipedia for reference, mostly because it’s public domain, and as an artist I find it important to respect other artists. You can copy it and, if you already have a canvas, :menuselection:`Edit --> Paste into New Image` or :menuselection:`New --> Create from Clipboard`."
msgid "Then, if you didn’t have a new canvas make one. I made an A5 300dpi canvas. This is not very big, but we’re only practicing. I also have the background color set to a yellow-grayish color (#CAC5B3), partly because it reminds me of paper, and partly because bright screen white can strain the eyes and make it difficult to focus on values and colors while painting. Also, due to the lack of strain on the eyes, you’ll find yourself soothed a bit. Other artists use #c0c0c0, or even more different values."
msgid "So, if you go to :menuselection:`Window --> Tile`, you will find that now your reference image and your working canvas are side by side. The reason I am using this instead of the docker is because I am lazy and don’t feel like saving the wikipedia image. We’re not going to touch the image much."
msgid "First we make a bunch of branches. I picked a slightly darker color here than usual, because I know that I’ll be painting over these branches with the lighter colors later on. Look at the reference how branches are formed."
msgid "Then we make an approximation of a single flower on a layer. We make a few of these, all on separate layers. We also do not color pick the red, but we guess at it. This is good practice, so we can learn to analyze a color as well as how to use our color selector. If we’d only pick colors, it would be difficult to understand the relationship between them, so it’s best to attempt matching them by eye."
msgid "I chose to make the flower shape opaque quickly by using the *behind* blending mode. This’ll mean Krita is painting the new pixels behind the old ones. Very useful for quickly filling up shapes, just don’t forget to go back to *normal* once you’re done."
-msgid "Now, we’ll put the flowers in the upper left corner, and group them. You can group by making a group layer, and selecting the flower layers in your docker with :kbd:`Ctrl` + |mouseleft| and dragging them into the group. The reason why we’re putting them in the upper left corner is because we’ll be selecting them a lot, and Krita allows you to select layers with kbd:`R` + |mouseleft| on the canvas quickly. Just hold :kbd:`R` and |mouseleft| the pixels belonging to the layer you want, and Krita will select the layer in the layer docker."
+msgid "Now, we’ll put the flowers in the upper left corner, and group them. You can group by making a group layer, and selecting the flower layers in your docker with the :kbd:`Ctrl +` |mouseleft| shortcut and dragging them into the group. The reason why we’re putting them in the upper left corner is because we’ll be selecting them a lot, and Krita allows you to select layers with the kbd:`R +` |mouseleft| shortcut on the canvas quickly. Just hold the :kbd:`R` key and |mouseleft| the pixels belonging to the layer you want, and Krita will select the layer in the layer docker."
msgid "Now, we will make clusters. What we’ll be doing is that we select a given flower and then make a new clone layer. A clone layer is a layer that is literally a clone of the original. They can’t be edited themselves, but edit the original and the clone layer will follow suit. Clone Layers, and File layers, are our greatest friends when it comes to transform masks, and you’ll see why in a moment."
msgid "You’ll quickly notice that our flowers are not good enough for a cluster: we need far more angles on the profile for example. If only there was a way to transform them… but we can’t do that with clone layers. Or can we?"
msgid "Transform Masks are a really powerful feature introduced in 2.9. They are in fact so powerful, that when you first use them, you can’t even begin to grasp where to use them."
msgid "Transform masks allow us to do a transform operation onto a layer, any given layer, and have it be completely dynamic! This includes our clone layer flowers!"
msgid "Now, with the transform mask selected, select the |tooltransform|, and rotate our clone layer. Apply the transform. You know you’re successful when you can hide the transform mask, and the layer goes back to its original state!"
msgid "You can even go and edit your transform! Just activate the |tooltransform| again while on a transform mask, and you will see the original transform so you can edit it. If you go to a different transform operation however, you will reset the transform completely, so watch out."
msgid "We’ll be only using affine transformations in this tutorial (which are the regular and perspective transform), but this can also be done with warp, cage and liquify, which’ll have a bit of a delay (3 seconds to be precise). This is to prevent your computer from being over-occupied with these more complex transforms, so you can keep on painting."
msgid "Above you can see there’s been a new view added so we can focus on painting the flower and at the same time see how it’ll look. You can make a new view by going :menuselection:`Window --> New View` and selecting the name of your current canvas (save first!). Views can be rotated and mirrored differently."
msgid "We’re now going to use *Alpha Inheritance*. Alpha inheritance is an ill-understood concept, because a lot of programs use *clipping masks* instead, which clip the layer’s alpha using only the alpha of the first next layer."
msgid "Alpha inheritance, however, uses all layers in a stack, so all the layers in the group that haven’t got alpha inheritance active themselves, or all the layers in the stack when the layer isn’t in a group. Because most people have an opaque layer at the bottom of their layer stack, alpha inheritance doesn’t seem to do much."
msgid "But for us, alpha inheritance is useful, because we can use all clone-layers in a cluster (if you grouped them), transformed or not, for clipping. Just draw a light blue square over all the flowers in a given cluster."
msgid "For the highlights use exactly the same method, AND exactly the same color, but instead set the layer to Divide (you can find this amongst the Arithmetic blending modes). Using Divide has exactly the opposite effect as using multiply with the same color. The benefit of this is that you can easily set up a complementary harmony in your shadows and highlights using these two."
msgid "Do this with all clusters and leaves, and maybe on the whole plant (you will first need to stick it into a group layer given the background is opaque) and you’re done!"
msgid "Transform masks can be used on paint layers, vector layers, group layers, clone layers and even file layers. I hope this tutorial has given you a nice idea on how to use them, and hope to see much more use of the transform masks in the future!"
msgid "You can get the file I made `here <https://share.kde.org/public.php?service=files&t=48c601aaf17271d7ca516c44cbe8590e>`_ to examine it further! (Caution: It will freeze up Krita if your version is below 2.9.4. The speed-ups in 2.9.4 are due to this file.)"
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-05-04 09:38+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../tutorials/saving-for-the-web.rst:1
msgid "Tutorial for saving images for the web"
msgstr ""
#. +> trunk5
#: ../../tutorials/saving-for-the-web.rst:13
msgid "Saving For The Web"
msgstr ""
#. +> trunk5
#: ../../tutorials/saving-for-the-web.rst:15
msgid "Krita's default saving format is the :ref:`file_kra` format. This format saves everything Krita can manipulate about an image: Layers, Filters, Assistants, Masks, Color spaces, etc. However, that's a lot of data, so ``*.kra`` files are pretty big. This doesn't make them very good for uploading to the internet. Imagine how many people's data-plans hit the limit if they only could look at ``*.kra`` files! So instead, we optimise our images for the web."
msgstr ""
#. +> trunk5
#: ../../tutorials/saving-for-the-web.rst:17
msgid "There are a few steps involved:"
msgstr ""
#. +> trunk5
#: ../../tutorials/saving-for-the-web.rst:19
msgid "Save as a ``.kra``. This is your working file and serves as a backup if you make any mistakes."
msgstr ""
#. +> trunk5
#: ../../tutorials/saving-for-the-web.rst:21
-msgid "Flatten all layers. This turns all your layers into a single one. Just go to :menuselection:`Layer --> Flatten Image` or press :kbd:`Ctrl` + :kbd:`Shift` + :kbd:`E`. Flattening can take a while, so if you have a big image, don't be scared if Krita freezes for a few seconds. It'll become responsive soon enough."
+msgid "Flatten all layers. This turns all your layers into a single one. Just go to :menuselection:`Layer --> Flatten Image` or press the :kbd:`Ctrl + Shift + E` shortcut. Flattening can take a while, so if you have a big image, don't be scared if Krita freezes for a few seconds. It'll become responsive soon enough."
msgstr ""
#. +> trunk5
#: ../../tutorials/saving-for-the-web.rst:23
msgid "Convert the color space to 8bit sRGB (if it isn't yet). This is important to lower the filesize, and PNG for example can't take higher than 16bit. :menuselection:`Image --> Convert Image Color Space` and set the options to **RGB**, **8bit** and **sRGB-elle-v2-srgbtrc.icc** respectively. If you are coming from a linear space, uncheck **little CMS** optimisations"
msgstr ""
#. +> trunk5
#: ../../tutorials/saving-for-the-web.rst:25
-msgid "Resize! Go to :menuselection:`Image --> Scale Image To New Size` or use :kbd:`Ctrl` + :kbd:`Alt` + :kbd:`I`. This calls up the resize menu. A good rule of thumb for resizing is that you try to get both sizes to be less than 1200 pixels. (This being the size of HD formats). You can easily get there by setting the **Resolution** under **Print Size** to **72** dots per inch. Then press **OK** to have everything resized."
+msgid "Resize! Go to :menuselection:`Image --> Scale Image To New Size` or use the :kbd:`Ctrl + Alt + I` shortcut. This calls up the resize menu. A good rule of thumb for resizing is that you try to get both sizes to be less than 1200 pixels. (This being the size of HD formats). You can easily get there by setting the **Resolution** under **Print Size** to **72** dots per inch. Then press **OK** to have everything resized."
msgstr ""
#. +> trunk5
#: ../../tutorials/saving-for-the-web.rst:27
msgid "Save as a web-safe image format. There's three that are especially recommended:"
msgstr ""
#. +> trunk5
#: ../../tutorials/saving-for-the-web.rst:30
msgid "JPG"
msgstr ""
#. +> trunk5
#: ../../tutorials/saving-for-the-web.rst:32
msgid "Use this for images with a lot of different colors, like paintings."
msgstr ""
#. +> trunk5
#: ../../tutorials/saving-for-the-web.rst:35
msgid "PNG"
msgstr ""
#. +> trunk5
#: ../../tutorials/saving-for-the-web.rst:37
msgid "Use this for images with few colors or which are black and white, like comics and pixel-art. Select :guilabel:`Save as indexed PNG, if possible` to optimise even more."
msgstr ""
#. +> trunk5
#: ../../tutorials/saving-for-the-web.rst:40
msgid "GIF"
msgstr ""
#. +> trunk5
#: ../../tutorials/saving-for-the-web.rst:42
msgid "Only use this for animation (will be supported this year) or images with a super low color count, because they will get indexed."
msgid "Saving with transparency is only possible with gif and png. First, make sure you see the transparency checkers (this can be done by simply hiding the bottom layers, changing the projection color in :menuselection:`Image --> Image Background Color and Transparency`, or by using :menuselection:`Filters --> Colors --> Color to Alpha`). Then, save as PNG and tick **Store alpha channel (transparency)**"
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-05-04 09:38+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../<rst_epilog>:2
msgid ""
".. image:: images/icons/Krita_mouse_left.png\n"
" :alt: mouseleft"
msgstr ""
#. +> trunk5
#: ../../<rst_epilog>:4
msgid ""
".. image:: images/icons/Krita_mouse_right.png\n"
" :alt: mouseright"
msgstr ""
#. +> trunk5
#: ../../user_manual/animation.rst:1
msgid "Detailed guide on the animation workflow in Krita."
msgstr ""
#. +> trunk5
#: ../../user_manual/animation.rst:13
msgid "Animation"
msgstr ""
#. +> trunk5
#: ../../user_manual/animation.rst:18
msgid "Animation with Krita"
msgstr ""
#. +> trunk5
#: ../../user_manual/animation.rst:20
msgid "Thanks to the 2015 Kickstarter, :program:`Krita 3.0` now has animation. In specific, :program:`Krita` has frame-by-frame raster animation. There's still a lot of elements missing from it, like tweening, but the basic workflow is there."
msgstr ""
#. +> trunk5
#: ../../user_manual/animation.rst:25
msgid "To access the animation features, the easiest way is to change your workspace to Animation. This will make the animation dockers and workflow appear."
msgstr ""
#. +> trunk5
#: ../../user_manual/animation.rst:30
msgid "Animation curves"
msgstr ""
#. +> trunk5
#: ../../user_manual/animation.rst:32
msgid "To create an animation curve (currently only for opacity) expand the :guilabel:`New Frame` button in the :guilabel:`Animation` dock and click :guilabel:`Add Opacity Keyframe`. You can now edit the keyframed value for opacity directly in the “Layers” dock, adding more keyframes will by default fade from the last to the next upcoming keyframe in the timeline over the frames between them. See :ref:`animation curves <animation_curves_docker>` for details."
msgstr ""
#. +> trunk5
#: ../../user_manual/animation.rst:40
msgid "Workflow"
msgstr ""
#. +> trunk5
#: ../../user_manual/animation.rst:42
msgid "In traditional animation workflow, what you do is that you make *key frames*, which contain the important poses, and then draw frames in between (\\ *tweening* in highly sophisticated animator's jargon)."
msgstr ""
#. +> trunk5
#: ../../user_manual/animation.rst:46
msgid "For this workflow, there are three important dockers:"
msgstr ""
#. +> trunk5
#: ../../user_manual/animation.rst:48
msgid "The :ref:`timeline_docker`. View and control all of the frames in your animation. The timeline docker also contains functions to manage your layers. The layer that are created in the timeline docker also appear on the normal Layer docker."
msgstr ""
#. +> trunk5
#: ../../user_manual/animation.rst:52
msgid "The :ref:`animation_docker`. This docker contains the play buttons as the ability to change the frame-rate, playback speed and useful little options like :guilabel:`auto-key framing`."
msgstr ""
#. +> trunk5
#: ../../user_manual/animation.rst:55
msgid "The :ref:`onion_skin_docker`. This docker controls the look of the onion skin, which in turn is useful for seeing the previous frame."
msgstr ""
#. +> trunk5
#: ../../user_manual/animation.rst:60
msgid "Introduction to animation: How to make a walkcycle"
msgstr ""
#. +> trunk5
#: ../../user_manual/animation.rst:62
msgid "The best way to get to understand all these different parts is to actually use them. Walk cycles are considered the most basic form of a full animation, because of all the different parts involved with them. Therefore, going over how one makes a walkcycle should serve as a good introduction."
msgid "On the first tab, we type in a nice ratio like 1280x1024, set the dpi to 72 (we're making this for screens after all) and title the document 'walkcycle'."
msgstr ""
#. +> trunk5
#: ../../user_manual/animation.rst:79
msgid "In the second tab, we choose a nice background color, and set the background to canvas-color. This means that Krita will automatically fill in any transparent bits with the background color. You can change this in :menuselection:`Image --> Image Properties`. This seems to be most useful to people doing animation, as the layer you do animation on MUST be semi-transparent to get onion skinning working."
msgstr ""
#. +> trunk5
#: ../../user_manual/animation.rst:82
msgid "Krita has a bunch of functionality for meta-data, starting at the :guilabel:`Create Document` screen. The title will be automatically used as a suggestion for saving and the description can be used by databases, or for you to leave comments behind. Not many people use it individually, but it can be useful for working in larger groups."
msgstr ""
#. +> trunk5
#: ../../user_manual/animation.rst:84
msgid "Then hit :guilabel:`Create`!"
msgstr ""
#. +> trunk5
#: ../../user_manual/animation.rst:86
msgid "Then, to get all the necessary tools for animation, select the workspace switcher:"
msgid "The animation workspace adds the timeline, animation and onion skin dockers at the bottom."
msgstr ""
#. +> trunk5
#: ../../user_manual/animation.rst:103
msgid "Animating"
msgstr ""
#. +> trunk5
#: ../../user_manual/animation.rst:105
msgid "We have two transparent layers set up. Let's name the bottom one 'environment' and the top 'walkcycle' by double clicking their names in the layer docker."
msgid "Then, select the 'walkcycle' layer and draw a head and torso (you can use any brush for this)."
msgstr ""
#. +> trunk5
#: ../../user_manual/animation.rst:118
msgid "Now, selecting a new frame will not make a new frame automatically. Krita doesn't actually see the 'walkcycle' layer as an animated layer at all!"
msgid "We can make it animatable by adding a frame to the timeline. |mouseright| a frame in the timeline to get a context menu. Choose :guilabel:`New Frame`."
-msgid "Use the :guilabel:`Copy Frame` button to copy the first frame onto the second. Then, use the with :kbd:`Shift + ↑` to move the frame contents up."
+msgid "Use the :guilabel:`Copy Frame` button to copy the first frame onto the second. Then, use the with the :kbd:`Shift + ↑` shortcut to move the frame contents up."
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:138
+#: ../../user_manual/animation.rst:137
msgid "We can see the difference by turning on the onionskinning:"
msgid "Now, you should see the previous frame as red."
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:145
+#: ../../user_manual/animation.rst:144
msgid "Krita sees white as a color, not as transparent, so make sure the animation layer you are working on is transparent in the bits where there's no drawing. You can fix the situation by use the :ref:`filter_color_to_alpha` filter, but prevention is best."
msgid "Now, we're gonna draw the two extremes of the walkcycle. These are the pose where both legs are as far apart as possible, and the pose where one leg is full stretched and the other pulled in, ready to take the next step."
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:159
-msgid "Now, let's copy these two... We could do that with :kbd:`Ctrl + drag`, but here comes a tricky bit:"
+#: ../../user_manual/animation.rst:158
+msgid "Now, let's copy these two... We could do that with the :kbd:`Ctrl + drag` shortcut, but here comes a tricky bit:"
msgid "You'll find that the more frames you add, the more difficult it becomes to keep track of the onion skins."
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:198
+#: ../../user_manual/animation.rst:197
msgid "You can modify the onion skin by using the onion skin docker, where you can change how many frames are visible at once, by toggling them on the top row. The bottom row is for controlling transparency, while below there you can modify the colors and extremity of the coloring."
msgid "Our walkcycle is gone from the timeline docker! This is a feature actually. A full animation can have so many little parts that an animator might want to remove the layers they're not working on from the timeline docker. So you manually have to add them."
msgid "You can show any given layer in the timeline by doing |mouseright| on the layer in the layer docker, and toggling :guilabel:`Show in Timeline`."
msgid "The images should be saved out as filenameXXX.png, giving their frame number."
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:245
+#: ../../user_manual/animation.rst:244
msgid "Then use something like Gimp (Linux, OSX, Windows), ImageMagick (Linux, OSX, Windows), or any other gif creator to make a gif out of your image sequence:"
-msgid "For example, you can use `VirtualDub <http://www.virtualdub.org/>`__\\ (Windows) and open all the frames and then go to :menuselection:`File --> Export --> GIF`."
+#: ../../user_manual/animation.rst:250
+msgid "For example, you can use `VirtualDub <http://www.virtualdub.org/>`_\\ (Windows) and open all the frames and then go to :menuselection:`File --> Export --> GIF`."
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:255
+#: ../../user_manual/animation.rst:254
msgid "Enjoy your walkcycle!"
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:259
+#: ../../user_manual/animation.rst:258
msgid "Krita 3.1 has a render animation feature. If you're using the 3.1 beta, check out the :ref:`render_animation` page for more information!"
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:262
+#: ../../user_manual/animation.rst:261
msgid "Importing animation frames"
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:264
+#: ../../user_manual/animation.rst:263
msgid "You can import animation frames in Krita 3.0."
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:266
+#: ../../user_manual/animation.rst:265
msgid "First let us take a sprite sheet from Open Game Art. (This is the Libre Pixel Cup male walkcycle)"
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:269
+#: ../../user_manual/animation.rst:268
msgid "And we'll use :menuselection:`Image --> Split Image` to split up the sprite sheet."
msgid "The slices are even, so for a sprite sheet of 9 sprites, use 8 vertical slices and 0 horizontal slices. Give it a proper name and save it as png."
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:275
+#: ../../user_manual/animation.rst:274
msgid "Then, make a new canvas, and select :menuselection:`File --> Import Animation Frames`. This will give you a little window. Select :guilabel:`Add images`. This should get you a file browser where you can select your images."
msgid "The frames are currently automatically ordered. You can set the ordering with the top-left two drop-down boxes."
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:286
+#: ../../user_manual/animation.rst:285
msgid "Start"
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:287
+#: ../../user_manual/animation.rst:286
msgid "Indicates at which point the animation should be imported."
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:289
+#: ../../user_manual/animation.rst:288
msgid "Indicates the difference between the imported animation and the document frame rate. This animation is 8 frames big, and the fps of the document is 24 frames, so there should be a step of 3 to keep it even. As you can see, the window gives feedback on how much fps the imported animation would be with the currently given step."
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:293
+#: ../../user_manual/animation.rst:292
msgid "Step"
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:295
+#: ../../user_manual/animation.rst:294
msgid "Press :guilabel:`OK`, and your animation should be imported as a new layer."
msgid "`The source for the libre pixel cup male walkmediawiki cycle <https://opengameart.org/content/liberated-pixel-cup-lpc-base-assets-sprites-map-tiles>`_"
msgid "If this is your first foray into digital painting, this page should give you a brief introduction to the basic but important concepts required for getting started with digital painting in Krita."
msgid "Although very lengthy, this page tries to give a brief overview of some of the Krita's most important functionality; it tries to help you grasp the functions of various menu and buttons in Krita without going into minute details."
msgid "Even though Krita is regarded primarily a raster based application, it has some vector editing capabilities as well. If you are new to digital painting medium, it is necessary that you first get yourself acquainted with the concepts of raster and :ref:`Vector <vector_graphics>` based images."
msgid "In digital imaging, a pixel (Picture Element) is a basic and lowest element of an Image. It is basically a grid of points each displaying specific color. Raster editing is manipulating and editing these pixels. For example when you take a 1-pixel brush which is colored black and painting on the white canvas in Krita you are actually changing the color of the pixel beneath your brush from white to black. When you zoom in and see a brush stroke you can notice many small squares with colors, these are pixels:"
msgid "In contrast to raster images, vector graphic images are based on mathematical expressions. They are independent of the pixels. For example, when you draw a rectangle on a :ref:`vector layer <vector_layers>` in Krita you are actually drawing paths passing through points that are called nodes, which are located on specific coordinates on the 'x' and 'y' axes. When you re-size or move these points the computer calculates and redraws the path and displays the newly formed shape to you. Hence you can re-size the vector shape to any extent without any loss in quality. In Krita, everything which is not on a vector layer is raster based."
msgid "This is an individual copy of the image that you can open or create via the file dialog. Krita allows you to open the file as a new copy via the :guilabel:`File` menu, or to save it as a new file, or make an incremental copy."
msgid "An image contains data regarding layers, color space of image and layers, canvas size and metadata such as creator, date created and DPI et cetera. Krita can open multiple images at once, you can switch between them via the :guilabel:`Window` menu."
msgid "Makes an internal copy of an existing image. When you press :menuselection:`Save`, you will overwrite the original existing image with your working copy."
msgid "Similar to :menuselection:`Open`, however, :menuselection:`Save` will request you to specify a saving location: you're making a new copy. This is similar to :menuselection:`Import` in other programs."
msgid "These options are great for people doing production work, who need to switch between files quickly or have backup files in case they do something extreme. Krita also has a file backup system in the form of auto-saves, backup files and crash recovery. You can configure the option for these features in the general settings."
-msgid "A view is a window onto your image. Krita allows you to have multiple views, and you can manipulate the view to zoom, rotate and mirror and modify the color of the way you see an image without editing the image itself. This is very useful for artists, as changing the way they view the image is a common way to diagnose some common mistakes, like a drawing which is skewed towards one side. Mirroring with :kbd:`M` makes such skewing easy to identify."
+msgid "A view is a window onto your image. Krita allows you to have multiple views, and you can manipulate the view to zoom, rotate and mirror and modify the color of the way you see an image without editing the image itself. This is very useful for artists, as changing the way they view the image is a common way to diagnose some common mistakes, like a drawing which is skewed towards one side. Mirroring with the :kbd:`M` key makes such skewing easy to identify."
msgid "If you have trouble drawing certain curves you will enjoy using rotation for drawing, and of course, there is zooming in and out for precision and rough work."
-msgid "Multiple views are possible in Krita via :menuselection:`Window --> New view --> image name`. You can switch between them via the :guilabel:`Window` menu, or :kbd:`Ctrl + Tab`, or keep them in the same area when **subwindow** mode is active in the :ref:`settings <general_settings>`, via :menuselection:`Window --> Tile`."
+msgid "Multiple views are possible in Krita via :menuselection:`Window --> New view --> image name`. You can switch between them via the :guilabel:`Window` menu, or the :kbd:`Ctrl + Tab` shortcut, or keep them in the same area when **subwindow** mode is active in the :ref:`settings <general_settings>`, via :menuselection:`Window --> Tile`."
msgid "Dockers are little subwindows in :ref:`Krita's interface <navigation>`. They contain useful tools, like the color selector, layer stack, tool options, et cetera."
msgid "Krita allows you to have multiple windows via :menuselection:`Window --> New Window`. You can then drag this to another monitor for multi-monitor use."
msgid "When you create a new document in Krita for the first time you will see a rectangular white area. This is called a canvas. You can see it in the image below. The area marked by a red rectangle is a canvas."
msgid "When you save the painting as jpg, png et cetera or take a print out of the painting, only the content inside this area is taken into consideration. Anything beyond it is ignored. Krita does store information beyond this area, you just won't be able to see it. This data is stored in the **Layers**."
msgid "Like a landscape painter will first paint the sky and then the furthest away elements before slowly working his way to the foreground elements, computers will do the same with all the things you tell them to draw. So, if you tell them to draw a circle after a square on the same spot, the circle will always be drawn later. This is called the **Drawing Order**."
msgid "The layer stack is a way for you to separate elements of a drawing and manipulate the drawing order by showing you which layers are drawn when and allowing you to change the order they are drawn in and also apply all sorts of other effects. This is called **Compositing**."
msgid "This is a layer type on which you draw vector graphics. Vector graphics are typically more simple than raster graphics and with the benefit that you can deform them with less blurriness."
msgid "These refer to an existing image outside of Krita and update as soon as the outside image updates. Useful for logos and emblems that change a lot."
msgid "Tools help you manipulate the image data. The most common one is of course, the freehand brush, which is the default when you open Krita. There are roughly five types of tools in Krita:"
msgid "These are tools for painting on paint layers. They describe shapes, like rectangles, circles and straight lines, but also freehand paths. These shapes then get used by the Brush engines to make shapes and drawing effects."
msgid "This is the upper row of tools, which are used to edit vectors. Interestingly enough, all paint tools except the freehand brush allow you to draw shapes on the vector layers. The resulting object won't use the brush preset for outline unlike the ones made with paint tools on normal layer."
msgid "Selections allow you to edit a very specific area of the layer you are working on without affecting the others. The selection tools allow you to draw or modify the current selection. This is like using masking-fluids in traditional painting method, but whereas using masking fluids and film is often messy and delicate, selections are far easier to use."
msgid "All tools can be found in the toolbox, and information about individual tools can be found in the :ref:`tools <cat_tools>` section of the manual."
msgid "Engine is a term Krita developers use to describe a complex interacting set of code, that is the core for certain functionality and is highly configurable. In short, like the engine of your car drives your car, and the type of engine and its configuration affects how you use your car, the brush engine drives the look and feel of the brush, and different brush engines have different results."
msgid "For example, the pixel-brush engine is simple and allows you to do most of your basic work, but if you do a lot of painting, the color smudge brush engine might be more useful. Even though it's slower to use than the Pixel Brush engine, its mixing of colors allows you to work faster when you need to blend and mix colors."
msgid "If you want something totally different from that, the sketch brush engine helps with making messy lines, and the shape brush engine allows you to make big flats quickly. There are a lot of cool effects inside Krita's brush engines, so try them all out, and be sure to check the chapters on each."
-msgid "You can configure these effects via the Brush Settings drop-down, which can be quickly accessed via :kbd:`F5`. These configurations can then be saved into presets, which you can quickly access with :kbd:`F6` or the Brush Presets docker."
+msgid "You can configure these effects via the Brush Settings drop-down, which can be quickly accessed via the :kbd:`F5` key. These configurations can then be saved into presets, which you can quickly access with the :kbd:`F6` key or the Brush Presets docker."
msgid "Humans can see a few million colors, which are combinations of electromagnetic waves (light) bouncing off a surface, where the surface absorbs some of it."
msgid "Subtractive CMY colors on the left and additive RGB colors on the right. This difference means that printers benefit from color conversion before printing"
msgid "When painting traditionally, we use pigments which also absorb the right light-waves for the color we want it to have, but the more pigments you combine, the more light is absorbed, leading to a kind of murky black. This is why we call the mixing of paints **subtractive**, as it subtracts light the more pigments you put together. Because of that, in traditional pigment mixing, our most efficient primaries are three fairly light colors: Cyan blue and Magenta red and Yellow (CMY)."
msgid "A computer also uses three primaries and uses a specific amount of each primary in a color as the way it stores color. However, a computer is a screen that emits light. So it makes more light, which means it needs to do **additive** mixing, where adding more and more colored lights result in white. This is why the three most efficient primaries, as used by computers are Red, Green and Blue (RGB)."
msgid "Per pixel, a computer then stores the value of each of these primaries, with the maximum depending on the bit-depth. These are called the **components** or **channels** depending on who you talk to."
msgid "This is the red-channel of an image of a red rose. As you can see, the petals are white here, indicating that those areas contain full red. The leaves are much darker, indicating a lack of red, which is to be expected, as they are green."
msgid "Though by default computers use RGB, they can also convert to CMYK (the subtractive model), or a perceptual model like LAB. In all cases this is just a different way of indicating how the colors relate to each other, and each time it usually has 3 components. The exception here is grayscale, because the computer only needs to remember how white a color is. This is why grayscale is more efficient memory-wise."
msgid "In fact, if you look at each channel separately, they also look like grayscale images, but instead white just means how much Red, Green or Blue there is."
msgid "Just like Red, Green and Blue, the computer can also store how transparent a pixel is. This is important for **compositing** as mentioned before. After all, there's no point in having multiple layers if you can't have transparency."
msgid "Transparency is stored in the same way as colors, meaning that it's also a channel. We usually call this channel the **alpha channel** or **alpha** for short. The reason behind this is that the letter 'α' is used to represent it in programming."
msgid "Some older programs don't always have transparency by default. Krita is the opposite: it doesn't understand images that don't track transparency, and will always add a transparency channel to images. When a given pixel is completely transparent on all layers, Krita will instead show a checkerboard pattern, like the rose image shown above."
msgid "A commonly used blending mode is for example :menuselection:`Multiply` which multiplies the components, leading to darker colors. This allows you to simulate the subtractive mixing, and thus makes painting shadows much easier."
-msgid ":menuselection:`Erasing` is a blending mode in Krita. There is no eraser tool, but you can toggle on the brush quickly with :kbd:`E` to become an eraser. You can also use it on layers. Unlike the other blending modes, this one only affects the alpha channel, making things more transparent."
+msgid ":menuselection:`Erasing` is a blending mode in Krita. There is no eraser tool, but you can toggle on the brush quickly with the :kbd:`E` key to become an eraser. You can also use it on layers. Unlike the other blending modes, this one only affects the alpha channel, making things more transparent."
msgid "Because we can see channels as grayscale images, we can convert grayscale images into channels. Like for example, we can use a grayscale image for the transparency. We call these **Masks**."
msgid "The primary types of mask are :ref:`transparency_masks`, which allow you to use a grayscale image to determine transparency, where black makes everything transparent and white makes the pixel fully opaque."
msgid "You can paint on masks with any of the brushes, or convert a normal paint-layer to a mask. The big benefit of masks is that you can make things transparent without removing the underlying pixels. Furthermore, you can use masks to reveal or hide a whole group layer at once!"
msgid "But you can't really tell whether she's a ghost lady or just really really white. If only we could give the idea that she floats. We right-click the layer and add a transparency mask. Then, we select that mask and draw with a black and white linear gradient so that the black is below."
msgid "The name mask comes from traditional masking fluid and film. You may recall the earlier comparison of selections to traditional masking fluid. Selections too are stored internally as grayscale images, and you can save them as a local selection which is kind of like a mask, or convert them to a transparency mask."
msgid "We mentioned earlier that you can do maths with colors. But you can also do maths with pixels, or groups of pixels or whole layers. In fact, you can make Krita do all sorts of little operations on layers. We call these operations **Filters**."
msgid "In most image manipulation software, these are separate tools, but Krita has it as a brush engine, allowing much more customization than usual."
msgid "Krita also allows you to let the Filters be part of the layer stack, via :ref:`filter_layers` and :ref:`filter_masks`. Filter Layers affect all the layers underneath it in the same hierarchy. Transparency and transparency masks on Filter Layers affect where the layer is applied."
msgid "Masks, on the other hand, can affect one single layer and are driven by a grayscale image. They will also affect all layers in a group, much like a transparency mask."
msgid "We can use these filters to make our ghost lady look even more ethereal, by selecting the ghost lady's layer, and then creating a clone layer. We then right click and add a filter mask and use gaussian blur set to 10 or so pixels. The clone layer is then put behind the original layer, and set to the blending mode '**Color Dodge**', giving her a definite spooky glow. You can keep on painting on the original layer and everything will get updated automatically!"
msgid "Layer Effects or Layer Styles are filter masks popularised by :program:`Photoshop's` that are a little faster than regular masks, but not as versatile. They are available by right clicking a layer and selecting 'layer style'."
msgid "**Transformations** are kind of like filters, in that these are operations done on the pixels of an image. We have a regular image and layer wide transformations in the image and layer top menus, so that you may resize, flip and rotate the whole image."
msgid "We also have the :ref:`crop_tool`, which only affects the canvas size, and the :ref:`move_tool` which only moves a given layer. However, if you want more control, Krita offers a :ref:`transform_tool`."
msgid "With this tool you can rotate and resize on the canvas, or put it in perspective. Or you can use advanced transform tools, like the warp, cage and liquify, which allow you to transform by drawing custom points or even by pretending it's a transforming brush."
msgid "Like the filter brush engine, Krita also has a Deform Brush Engine, which allows you to transform with a brush. The deform is like a much faster version of the Liquify transform tool mode, but in exchange, its results are of much lower quality."
msgid "Like filters, transforms can be applied as a non-destructive operation that is part of the layer stack. Unlike filter and transparency masks however, transform masks can't be driven by a grayscale image, for technical reasons. You can use transform masks to deform clone and file layers as well."
msgid "From version 3.0 onwards, Krita got raster animation support. You can use the timeline, animation and onionskin dockers, plus Krita's amazing variety of brushes to do raster based animations, export those, and then turn them into movies or gifs."
msgid "With all this technical stuff, you might forget that Krita is a painting program. Like how when working with traditional medium, as an illustrator, you can have all sorts of equipment to make drawing easier, Krita also offers a variety of tools:"
msgid "Because you can hardly put a ruler against your tablet to help you draw, the assistants are there to help you draw concentric circles, perspectives, parallel lines and other easily forgotten but tricky to draw details. Krita allows you to snap to these via the tool options as well."
msgid "In addition to rearranging the dockers according to your preferences, Krita provides and saves your configurations as :ref:`resource_workspaces`. This is the button at the top right."
msgid "You can also configure the toolbar via :menuselection:`Settings --> Configure Toolbars`, as well as the shortcuts under both :menuselection:`Settings --> Configure Krita --> Configure Shortcuts` and :menuselection:`Settings --> Configure Krita --> Canvas Input Settings`."
msgid "The versions on the Store and Steam cost money, but are `functionally identical <https://krita.org/en/item/krita-available-from-the-windows-store/>`_ to the (free) website version. Unlike the website version, however, both paid versions get automatic updates when new versions of Krita comes out. After deduction of the Store fee, the purchase cost supports Krita development."
msgid "The page will try to automatically recommend the correct architecture (64- or 32-bit), but you can select \"All Download Versions\" to get more choices. To determine your computer architecture manually, go to :menuselection:`Settings --> About`. Your architecture will be listed as the :guilabel:`System Type` in the :guilabel:`Device Specifications` section."
msgid "Krita by default downloads an **installer EXE**, but you can also download a **portable zip-file** version instead. Unlike the installer version, this portable version does not show previews in Windows Explorer automatically. To get these previews with the portable version, also install Krita's **Windows Shell Extension** extension (available on the download page)."
msgid "For a small fee, you can download Krita `from the Windows Store <https://www.microsoft.com/store/productId/9N6X57ZGRW96>`_. This version requires Windows 10."
-msgid "To download a portable version of Krita go to the `KDE <http://download.kde.org/stable/krita/>`__ download directory and get the zip-file instead of the setup.exe installer."
+msgid "To download a portable version of Krita go to the `KDE <https://download.kde.org/stable/krita/>`_ download directory and get the zip-file instead of the setup.exe installer."
msgid "Many Linux distributions package the latest version of Krita. Sometimes you will have to enable an extra repository. Krita runs fine under most desktop enviroments such as KDE, Gnome, LXDE, Xfce etc. -- even though it is a KDE application and needs the KDE libraries. You might also want to install the KDE system settings module and tweak the gui theme and fonts used, depending on your distributions"
msgid "Since April 2016, KDE's Dolphin file manager shows kra and ora thumbnails by default, but Nautilus and it's derivatives need an extension. `We recommend Moritz Molch's extensions for XCF, KRA, ORA and PSD thumbnails <https://moritzmolch.com/1749>`__."
msgid "For Krita 3.0 and later, first try out the appimage from the website. **90% of the time this is by far the easiest way to get the latest Krita.** Just download the appimage, and then use the file properties or the bash command chmod to make the appimage executable. Double click it, and enjoy Krita. (Or run it in the terminal with ./appimagename.appimage)"
msgid "Appimages are ISOs with all the necessary libraries bundled inside, that means no fiddling with repositories and dependencies, at the cost of a slight bit more diskspace taken up (And this size would only be bigger if you were using Plasma to begin with)."
msgid "It does not matter which version of Ubuntu you use, Krita will run just fine. However, by default, only a very old version of Krita is available. You should either use the appimage, flatpak or the snap available from Ubuntu's app store. We also maintain a ppa for getting latest builds of Krita, you can read more about the ppa and install instructions `here <https://launchpad.net/~kritalime/+archive/ubuntu/ppa>`_."
msgid "You can download the latest binary from our `website <https://krita.org/download/krita-desktop/>`__. The binaries work only with Mac OSX version 10.12 and newer."
msgid "While it is certainly more difficult to compile Krita from source than it is to install from prebuilt packages, there are certain advantages that might make the effort worth it:"
msgid "You can follow the development of Krita on the foot. If you compile Krita regularly from the development repository, you will be able to play with all the new features that the developers are working on."
msgid "You can help the developers by giving us your feedback on features as they are being developed and you can test bug fixes for us. This is hugely important, which is why our regular testers get their name in the about box just like developers."
msgid "Of course, there are also some disadvantages: when building from the current development source repository you also get all the unfinished features. It might mean less stability for a while, or things shown in the user interface that don't work. But in practice, there is seldom really bad instability, and if it is, it's easy for you to go back to a revision that does work."
msgid "If you encounter any problems, or if you are new to compiling software, don't hesitate to contact the Krita developers. There are three main communication channels:"
msgid "Krita's interface is very flexible and provides an ample choice for the artists to arrange the elements of the workspace. An artist can snap and arrange the elements, much like snapping together Lego blocks. Krita provides a set of construction kit parts in the form of Dockers and Toolbars. Every set of elements can be shown, hidden, moved and rearranged that let the artists easily customize their own user interface experience."
msgid "As we've said before, the Krita interface is very malleable and the way that you choose to configure the work surface may not resemble those shown below, but we can use these as a starting point."
msgid "**C** -- Sidebars for the Movable Panels/Dockers. In some applications, these are known as Dockable areas. Krita also allows you to dock panels at the top and/or bottom as well."
msgid "**D** -- Status Bar - This space shows the preferred mode for showing selection i.e. marching ants or mask mode, your selected brush preset, :ref:`Color Space <color_managed_workflow>`, image size and provides a convenient zoom control."
msgid "**E** -- Floating Panel/Docker - These can be \"popped\" in and out of their docks at any time in order to see a greater range of options. A good example of this would be the :ref:`brush_preset_docker` or the :ref:`palette_docker`."
msgid "Your canvas sits in the middle and unlike traditional paper or even most digital painting applications, Krita provides the artist with a scrolling canvas of infinite size (not that you'll need it of course!). The standard navigation tools are as follows:"
-msgid "Discrete zooming can be done through :kbd:`+`, and :kbd:`-`. Using :kbd:`Ctrl + Space` or :kbd:`Ctrl +` |mousemiddle| can allow for direct zooming with the stylus."
+msgid "Discrete zooming can be done through :kbd:`+` and :kbd:`-` keys. Using the :kbd:`Ctrl + Space` or :kbd:`Ctrl +` |mousemiddle| shortcuts can allow for direct zooming with the stylus."
msgid "You can mirror the view can be quickly done via :kbd:`M` key. Mirroring is a great technique that seasoned digital artists use to quickly review the composition of their work to ensure that it \"reads\" well, even when flipped horizontally."
-msgid "You can rotate the canvas without transforming. It can be done with :kbd:`Ctrl + [` or :kbd:`4` and the other way with :kbd:`Ctrl + ]` or :kbd:`6`. Quick mouse based rotation is :kbd:`Shift + Space` and :kbd:`Shift +` |mousemiddle|. To reset rotation use :kbd:`5` ."
+msgid "You can rotate the canvas without transforming. It can be done with the :kbd:`Ctrl + [` shortcut or :kbd:`4`key and the other way with :kbd:`Ctrl + ]` shortcut or :kbd:`6` key. Quick mouse based rotation is the :kbd:`Shift + Space` and :kbd:`Shift +` |mousemiddle| shortcuts. To reset rotation use the :kbd:`5` key."
msgid "Dockers are small windows that can contain, for example, things like the layer stack, Color Palette or list of Brush Presets. Think of them as the painter's palette, or his water, or his brush kit. They can be activated by choosing the :guilabel:`Settings` menu and the :guilabel:`Dockers` sub-menu. There you will find a long list of available options."
msgid "Dockers, as the name implies, can be docked into the main interface. You can do this by dragging the docker to the sides of the canvas (or top or bottom if you prefer)."
msgid "Dockers contain many of the \"hidden\", and powerful, aspects of **Krita** that you will want to explore as you start delving deeper into the application."
msgid "You can arrange the dockers in almost any permutation and combination according to the needs of your workflow, and then save these arrangements as Workspaces."
msgid "The total range is represented from left to right and blue bar gives an indication of where in the possible range the current value is. Clicking anywhere, left or right, of that slider will change the current number to something lower (to the left) or higher (to the right)."
-msgid "Pressing :kbd:`Shift` while dragging the slider changes the values at a smaller increment, and pressing :kbd:`Ctrl` while dragging the slider changes the value in whole numbers or multiples of 5."
+msgid "Pressing the :kbd:`Shift` key while dragging the slider changes the values at a smaller increment, and pressing the :kbd:`Ctrl` key while dragging the slider changes the value in whole numbers or multiples of 5."
msgid "Toolbars are where some of the important actions and menus are placed so that they are readily and quickly available for the artist while painting."
msgid "You can learn more about the Krita Toolbars and how to configure them in over in the :ref:`Toolbars section <configure_toolbars>` of the manual. Putting these to effective use can really speed up the Artist's workflow, especially for users of Tablet-Monitors and Tablet-PCs."
msgid "The button on the very right of the Toolbar is the workspace chooser. This allows you to load and save common configurations of the user interface in Krita. There are a few common workspaces that come with Krita."
msgid ":ref:`Pop-up Palette <pop-up_palette>` is a feature unique to Krita, designed to increase the productivity of the artist. It is a circular menu for quickly choosing brushes, foreground and background colors, recent colors while painting. To access the palette you have to just |mouseright| on the canvas. The palette will spawn at the position of the brush tip or cursor."
msgid "By tagging your brush presets you can add particular sets of brushes to this palette. For example, if you add some inking brush presets to inking tag you can change the tags to inking in the pop-up palette and you'll get all the inking brushes in the palette."
msgid "You can :ref:`tag <tag_management>` brush presets via the :ref:`brush_preset_docker`, check out the :ref:`resource overview page <resource_management>` to know more about tagging in general."
msgid "If you call up the pop-up palette again, you can click the tag icon, and select the tag. In fact, you can make multiple tags and switch between them. When you need more than ten presets, go into :menuselection:`Settings --> Configure Krita --> General --> Miscellaneous --> Number of Palette Presets` and change the number of presets from 10 to something you feel comfortable."
msgid "When you start Krita for the first time there will be no canvas or new document open by default. You will be greeted by a :ref:`welcome screen <welcome_screen>`, which will have option to create a new file or open existing document. To create a new canvas you have to create a new document from the :guilabel:`File` menu or by clicking on :guilabel:`New File` under start section of the welcome screen. This will open the new file dialog box. If you want to open an existing image, either use :menuselection:`File --> Open` or drag the image from your computer into Krita's window."
msgid "Click on the :guilabel:`Custom Document` section and in the :guilabel:`Dimensions` tab choose A4 (300ppi) or any size that you prefer from the :guilabel:`predefined` drop down To know more about the other sections such as create document from clipboard and templates see :ref:`create_new_document`."
msgid "Make sure that the color profile is RGB and depth is set to 8-bit integer/channel in the color section. For advanced information about the color and color management refer to :ref:`general_concept_color`."
msgid "Now, on the blank white canvas, just left click with your mouse or draw with the pen on a graphic tablet. If everything's correct, you should be able to draw on the canvas! The brush tool should be selected by default when you start Krita, but if for some reason it is not, you can click on this |toolfreehandbrush| icon from the toolbox and activate the brush tool."
-msgid "Of course, you'd want to use different brushes. On your right, there's a docker named Brush Presets (or on top, press :kbd:`F6` to find this one) with all these cute squares with pens and crayons."
+msgid "Of course, you'd want to use different brushes. On your right, there's a docker named Brush Presets (or on top, press the :kbd:`F6` key to find this one) with all these cute squares with pens and crayons."
msgid "Tick any of the squares to choose a brush, and then draw on the canvas. To change color, click the triangle in the Advanced Color Selector docker."
msgid "There are brush presets for erasing, but it is often faster to use the eraser toggle. By toggling the :kbd:`E` key, your current brush switches between erasing and painting. This erasing method works with most of the tools. You can erase using the line tool, rectangle tool, and even the gradient tool."
msgid "Now, once you have figured out how to draw something in Krita, you may want to save it. The save option is in the same place as it is in all other computer programs: the top-menu of :guilabel:`File`, and then :guilabel:`Save`. Select the folder you want to have your drawing, and select the file format you want to use ('.kra' is Krita's default format, and will save everything). And then hit :guilabel:`Save`. Some older versions of Krita have a bug and require you to manually type the extension."
msgid "Check out :ref:`navigation` for further basic information, :ref:`basic_concepts` for an introduction as Krita as a medium, or just go out and explore Krita!"
msgid "This document gives an introduction to Krita for users who have been using Photoshop. The intention is to make you productive in Krita as fast as possible and ease the conversion of old habits into new ones. This introduction is written with Krita version 2.9 and Photoshop CS2 and CS3 in mind. But even though things may change in the future, the basics will most likely remain the same. The first thing to remember is that Krita is a 2D paint application while Photoshop (PS) is an image manipulation program. This means that PS has more features than Krita in general, but Krita has the tools that are relevant to digital painting. When you get used to Krita, you will find that Krita has some features that are not part of PS."
-msgid "Rotate the canvas with :kbd:`Shift + Space`, or :kbd:`Ctrl + [` and :kbd:`Ctrl + ]` or with 4 or 6. Reset the rotation with 5."
+msgid "Rotate the canvas with the :kbd:`Shift + Space`, or :kbd:`Ctrl + [` and :kbd:`Ctrl + ]` shortcuts or with the :kbd:`4` or :kbd:`6` keys. Reset the rotation with the :kbd:`5` key."
-msgid "Moving and Transformation of contents is done using tools in Krita. You can then find them in the toolbar. If you are familiar with the way to move layers in PS by holding down :kbd:`Ctrl`, you can do the same in Krita by pressing the :kbd:`T` key for the move tool (think ‘T’ranslate) or :kbd:`Ctrl + T` for transform tool."
+msgid "Moving and Transformation of contents is done using tools in Krita. You can then find them in the toolbar. If you are familiar with the way to move layers in PS by holding down the :kbd:`Ctrl` key, you can do the same in Krita by pressing the :kbd:`T` key for the move tool (think ‘T’ranslate) or the :kbd:`Ctrl + T` shortcut for transform tool."
-msgid "Press :kbd:`B` to go back to the brush tool when the transformation or translation is done. To find how to make advanced deformations using the :guilabel:`Transform` tool, do not right-click on the on-canvas widget: all the option are in the :guilabel:`Tool Options` docker."
+msgid "Press the :kbd:`B` key to go back to the brush tool when the transformation or translation is done. To find how to make advanced deformations using the :guilabel:`Transform` tool, do not right-click on the on-canvas widget: all the option are in the :guilabel:`Tool Options` docker."
-msgid "Like in PS, you can use :kbd:`Alt` or :kbd:`Shift` during a selection to remove or add selection to the active selection. Krita also offers sub tools for this, and you can select them in the :guilabel:`Tool Options` if a select tool is active. These sub tools are represented as icons. You can switch to those sub modes by pressing:"
+msgid "Like in PS, you can use the :kbd:`Alt` or :kbd:`Shift` keys during a selection to remove or add selection to the active selection. Krita also offers sub tools for this, and you can select them in the :guilabel:`Tool Options` if a select tool is active. These sub tools are represented as icons. You can switch to those sub modes by pressing:"
-msgid "You cannot press :kbd:`Ctrl` to move the content of the selection (you have to press :kbd:`T` or select the :guilabel:`Move Tool`)."
+msgid "You cannot press the :kbd:`Ctrl` key to move the content of the selection (you have to press the :kbd:`T` key or select the :guilabel:`Move Tool`)."
msgid "If you want to convert a layer to a selection (to select the visible pixels), right-click on the layer docker, and choose :guilabel:`Select Opaque`."
-msgid "If you use a polygonal selection tool, or a selection which needs to be ‘closed’, you will be able to do it or by using a double-click, or by using a :kbd:`Shift` - |mouseleft| ."
+msgid "If you use a polygonal selection tool, or a selection which needs to be ‘closed’, you will be able to do it or by using a double-click, or by using a :kbd:`Shift +` |mouseleft| shortcut."
msgid "If you enable :guilabel:`Show Global Selection Mask` (:guilabel:`Select` menu) you can scale/rotate/transform/move or paint on selection like on regular grayscale layer."
-msgid "Note for Gimp user: Krita auto-expands and auto defloats new layers created from a selection after a :kbd:`Ctrl + C`, :kbd:`Ctrl + V` so you do not have to worry about not being able to paint outside the pasted element."
+msgid "Note for Gimp user: Krita auto-expands and auto defloats new layers created from a selection after pressing the :kbd:`Ctrl + C`, :kbd:`Ctrl + V` shortcuts so you do not have to worry about not being able to paint outside the pasted element."
-msgid "This doesn't work as intended right now. Intersect is a selection mode which uses :kbd:`T` as the shortcut. However :kbd:`T` is also used to switch to the :guilabel:`Move tool` so this shortcut is not functional right now. You have to use the button on the :guilabel:`Tool Options`."
+msgid "This doesn't work as intended right now. Intersect is a selection mode which use the :kbd:`T` key as the shortcut. However the :kbd:`T` key is also used to switch to the :guilabel:`Move tool` so this shortcut is not functional right now. You have to use the button on the :guilabel:`Tool Options`."
msgid "The group blending mode in Krita has priority over child layers and overrides it. This can be surprising for Photoshop users. On Photoshop you can use groups to just clean your layer stack and keep blending mode of your layer compositing through all the stack. In Krita the compositing will happen at first level inside the group, then taking into account the blending mode of the group itself. Both systems have pros and cons. Krita’s way is more predictable according to some artists, compositing-wise. The PS way leads to a cleaner and better ordered layer stack visually wise."
-msgid "You can select multiple layers on the stack by holding down :kbd:`Shift` as in PS, and if you move the layer inside a group you can move or transform the whole group - including doing selection on the group and cut all the sub layers inside on the fly. You can not apply filters to group to affect multiple layers."
+msgid "You can select multiple layers on the stack by holding down the :kbd:`Shift` key as in PS, and if you move the layer inside a group you can move or transform the whole group - including doing selection on the group and cut all the sub layers inside on the fly. You can not apply filters to group to affect multiple layers."
msgid "Krita has no clipping mask, but there is a workaround involving layer groups and :guilabel:`Inherit alpha` (see the alpha icon). Place a layer with the shape you want to clip the other with at the bottom of a group and layers above with the :guilabel:`Inherit alpha` option. This will create the same effect as the “clipping mask” PS feature."
msgid "This process of arranging groups for inherit alpha can be done automatically by :kbd:`Ctrl + Shift + G` shortcut. It creates a group with base layer and a layer above it with inherit alpha option checked by default."
msgid "These are layers that are an ‘instance’ of the layer you had selected when creating them. They get updated automatically when the original layer updates."
msgid "You can apply Photoshop layerstyles in Krita by right clicking any given layer type and selecting ‘layer style’ from the context menu. Krita can open and save ASL files, but not all layer style functionality is there yet."
msgid "Krita has at least 5 times more blending modes than PS. They are sorted by categories in the drop-down menu. You can use the checkbox to add your most used to the Favorite categories."
msgid "In Krita, there is a totally different paradigm for defining what ‘tools’ are compared to PS. Unlike in PS, you will not find the brush, eraser, clone, blur tool, etc. Instead, you will find a *way to trace* your strokes on the canvas: freehand, line, rectangle, circle, multiple brush, etc. When you have selected the ‘way to trace’ you can choose the *way to paint*: erasing / cloning / blurring, etc are all part of *way it paint* managed by the brush-engines options. These brush engine options are saved into so-called *presets*, which you can find on :guilabel:`Brush presets`. You can fine tune, and build your own presets using the :guilabel:`Edit Brush Settings` icon on the top tool bar."
-msgid "In Krita, the eraser is not a tool, it is a Blending mode (or Composite mode). You can change each brush you have to erase by pressing :kbd:`E`. By pressing :kbd:`E` again you’ll be back to the last blending mode you had selected before pressing :kbd:`E` the first time."
+msgid "In Krita, the eraser is not a tool, it is a Blending mode (or Composite mode). You can change each brush you have to erase by pressing the :kbd:`E` key. By pressing the :kbd:`E` key again you’ll be back to the last blending mode you had selected before pressing the :kbd:`E` key the first time."
-msgid "Some people regard these shortcuts as somewhat unfortunate. The reason is that they are meant to be used during painting and left-:kbd:`Shift` is at the opposite end of the keyboard from :kbd:`I`, :kbd:`M` and :kbd:`N`. So for a right-handed painter, this is very difficult to do while using the stylus with a right hand. Note that you can reassign any shortcut by using the shortcut configuration in :menuselection:`Settings --> Configure Shortcuts`."
+msgid "Some people regard these shortcuts as somewhat unfortunate. The reason is that they are meant to be used during painting and the left :kbd:`Shift` key is at the opposite end of the keyboard from the :kbd:`I`, :kbd:`M` and :kbd:`N` keys. So for a right-handed painter, this is very difficult to do while using the stylus with a right hand. Note that you can reassign any shortcut by using the shortcut configuration in :menuselection:`Settings --> Configure Shortcuts`."
msgid "Using the freehand ‘paint with brush’ tool that you can find on the Tool Options, more settings for smoothing the path and stabilization of your brush strokes are available."
msgid "If you find the feeling of Krita too hard or too soft regarding the pressure when you paint, you can set a softer or harder curve here: :menuselection:`Settings --> Configure Krita --> Tablet settings`"
msgid "Unlike Photoshop, where these are separate tools, in Krita, they are available via the Filter Brush Engine, which allows you to apply the majority of Krita's filters in brush form."
msgid "If you don’t like the dark default theme of Krita go to: :menuselection:`Settings --> Themes`, and choose a brighter or darker theme. If you don’t like the color outside your viewport go to: :menuselection:`Settings --> Configure Krita --> Display`, and change the Canvas border color."
msgid "As mentioned in the introduction, Krita is a specialized paint application. Thus, it also has specialized tools for painting. Similar tools are not found in more generalized image manipulation applications such as PS. Here is a short list of the most important ones."
-msgid "Krita has a lot of different so-called brush engines. These brush engines define various methods on how the pixels end up on your canvas. Brush engines with names like Grid, Particles, Sketch and others will bring you new experiences on how the brushes work and a new landscape of possible results. You can start customizing brushes by using the brush-settings editor, which is accessible via the toolbar, but it's much easier to just press :kbd:`F5`."
+msgid "Krita has a lot of different so-called brush engines. These brush engines define various methods on how the pixels end up on your canvas. Brush engines with names like Grid, Particles, Sketch and others will bring you new experiences on how the brushes work and a new landscape of possible results. You can start customizing brushes by using the brush-settings editor, which is accessible via the toolbar, but it's much easier to just press the :kbd:`F5` key."
msgid "This is a very useful way to configure brush presets. Each brush can have any amount of tags and be in any group. You can make tag for blending brushes, for texture brushes, for effect brushes, favorites etc."
msgid "Easily to be found on |mouseright|, the pop-up palette allows you to quickly access brushes, color history and a color selector within arm's reach. The brushes are determined by tag, and pressing the lower-right configure button calls a drop-down to change tags. This allows you to tag brushes in the preset docker by workflow, and quickly access the right brushes for the workflow you need for your image."
msgid "The Krita transformation tool can perform transformations on a group and affect child layers. There are several modes, like free, perspective, warp, the powerful cage and even liquify. Furthermore, you can use transformation masks to apply transforms non-destructively to any layer type, raster, vector group, you name it."
msgid "You can save your artwork with the pattern : myartworksname_001.kra , myartworksname_002.kra, myartworksname_003.kra etc, by pressing a single key on the keyboard. Krita will increment the final number if the pattern \"_XXX\" is recognized at the end of the file's name."
msgid "If you want to delete the white of the paper from a scanned artwork, you can use this filter. It takes a color and turns it into pure transparency."
msgid "If you like using blending modes, Krita has many of them -- over 70! You have plenty of room for experimentation. A special system of favorite blending modes has been created to let you have fast access to the ones you use the most."
msgid "Krita has many painting assistants. This is a special type vector shapes with a magnetic influence on your brush strokes. You can use them as rulers, but with other shapes than just straight."
msgid "Krita's Multibrush tool allows you to paint with multiple brushes at the same time. Movements of the brushes other than the main brush is created by mirroring what you paint, or duplicating it by any number around any axis. They can also be used in parallel mode."
msgid "Using the LUT docker, Krita allows you to have a separate color correction filter per view. While this is certainly useful to people who do color correction in daily life, to the artist this allows for seeing a copy of the image in luminance grayscale, so that they instantly know the values of the image."
msgid "This same LUT docker is the controller for painting with HDR colors. Using the LUT docker to change the exposure on the view, Krita allows you to paint with HDR colors, and has native open exr support!"
msgid "Again, Krita is a digital paint application and Photoshop is an image manipulation program with some painting features. This means that there are things you can do in PS that you cannot do in Krita. This section gives a short list of these features."
msgid "Krita has a pretty impressive pack of filters available, but you will probably miss one or two of the special filters or color adjustment tools you often use in Photoshop. For example, there is no possibility to tweak a specific color in HSV adjustment."
msgid "Krita does not have an automatic healing tool. It does, however, have a so-called clone tool which can be used to do a healing correction, although not automatically."
msgid "When you transform a layer or a selection in Krita, the transformation appears on the top of your layer stack ignoring the layer blending mode."
msgid "Using these tips you will probably be up to speed with Krita in a short time. If you find other things worth mentioning in this document we, the authors, would be interested in hearing about them. Krita develops fast, so we believe that the list of things possible in Photoshop but not in Krita will become shorter in time. We will maintain this document as this happens."
-msgid "There's a couple of possibilities here: either :kbd:`4` and :kbd:`6`, or :kbd:`Ctrl + [` and :kbd:`Ctrl + ]` for basic 15 degrees rotation left and right. But you can also have more sophisticated rotation with :kbd:`Shift + Space` + drag or :kbd:`Shift` + |mousemiddle| + drag. To reset the rotation, press :kbd:`5`."
+msgid "There's a couple of possibilities here: either the :kbd:`4` and :kbd:`6` keys, or the :kbd:`Ctrl + [` and :kbd:`Ctrl + ]` shortcuts for basic 15 degrees rotation left and right. But you can also have more sophisticated rotation with the :kbd:`Shift + Space + drag` or :kbd:`Shift +` |mousemiddle| :kbd:`+ drag` shortcuts. To reset the rotation, press the :kbd:`5` key."
-msgid "You can use :kbd:`+` and :kbd:`-` to zoom out and in, or use :kbd:`Ctrl` + |mousemiddle|. Use 1, 2 or 3 to reset the zoom, fit the zoom to page or fit the zoom to page width."
+msgid "You can use the :kbd:`+` and :kbd:`-` keys to zoom out and in, or use the :kbd:`Ctrl +` |mousemiddle| shortcut. Use 1, 2 or 3 to reset the zoom, fit the zoom to page or fit the zoom to page width."
msgid "You can also put these commands on the toolbar, so it'll feel a little like Sai. Go to :menuselection:`Settings --> Configure Toolbars`. There are two toolbars, but we'll add to the file toolbar."
msgid "Then, you can type in something in the left column to search for it. So, for example, 'undo'. Then select the action 'undo freehand stroke' and drag it to the right. Select the action to the right, and click :menuselection:`Change text`. There, toggle :menuselection:`Hide text when toolbar shows action alongside icon` to prevent the action from showing the text. Then press :guilabel:`OK`. When done right, the :guilabel:`Undo` should now be sandwiched between the save and the gradient icon."
msgid "You can do the same for :guilabel:`Redo`, :guilabel:`Deselect`, :guilabel:`Invert Selection`, :guilabel:`Zoom out`, :guilabel:`Zoom in`, :guilabel:`Reset zoom`, :guilabel:`Rotate left`, :guilabel:`Rotate right`, :guilabel:`Mirror view` and perhaps :guilabel:`Smoothing: basic` and :guilabel:`Smoothing: stabilizer` to get nearly all the functionality of Sai's top bar in Krita's top bar. (Though, on smaller screens this will cause all the things in the brushes toolbar to hide inside a drop-down to the right, so you need to experiment a little)."
msgid ":guilabel:`Hide Selection`, :guilabel:`Reset Rotation` are currently not available via the Toolbar configuration, you'll need to use the shortcuts :kbd:`Ctrl + H` and :kbd:`5` to toggle these."
-msgid "You can actually set this in :menuselection:`Settings --> Configure Krita --> Canvas input settings --> Alternate invocation`. Just double-click the entry that says :kbd:`Ctrl` + |mouseleft| before :guilabel:`Pick foreground color from image` to get a window to set it to |mouseright|."
+msgid "You can actually set this in :menuselection:`Settings --> Configure Krita --> Canvas input settings --> Alternate invocation`. Just double-click the entry that says :kbd:`Ctrl +` |mouseleft| shortcut before :guilabel:`Pick foreground color from image` to get a window to set it to |mouseright|."
msgid "Krita 3.0 actually has a Paint-tool Sai-compatible input sheet shipped by default. Combine these with the shortcut sheet for Paint tool Sai to get most of the functionality on familiar hotkeys."
msgid "This is in the tool options docker of the freehand brush. Use Basic Smoothing for more advanced tablets, and Stabilizer is much like Paint Tool Sai's. Just turn off :guilabel:`Delay` so that the dead-zone disappears."
msgid "So one of the things that throw a lot of Paint Tool Sai users off is that Krita uses checkers to display transparency, which is actually not that uncommon. Still, if you want to have the canvas background to be white, this is possible. Just choose :guilabel:`Background: As Canvas Color` in the new image dialogue and the image background will be white. You can turn it back to transparent via :menuselection:`Image --> Change image background color`. If you export a PNG or JPG, make sure to uncheck :guilabel:`Save transparency` and to make the background color white (it's black by default)."
msgid "Like Sai, you can quickly turn a black and white image to black and transparent with the :menuselection:`Color to Alpha Filter` under :menuselection:`Filters --> Colors --> Color to Alpha`."
msgid "Another, somewhat amusing misconception is that Krita's brush engine is not very complex. After all, you can only change the Size, Flow and Opacity from the top bar."
-msgid "This is not quite true. It's rather that we don't have our brush settings in a docker but a drop-down on the toolbar. The easiest way to access this is with :kbd:`F5`. As you can see, it's actually quite complex. We have more than a dozen brush engines, which are a type of brush you can make. The ones you are used to from Paint Tool Sai are the Pixel Brush (ink), The Color Smudge Brush (brush) and the filter brush (dodge, burn)."
+msgid "This is not quite true. It's rather that we don't have our brush settings in a docker but a drop-down on the toolbar. The easiest way to access this is with the :kbd:`F5` key. As you can see, it's actually quite complex. We have more than a dozen brush engines, which are a type of brush you can make. The ones you are used to from Paint Tool Sai are the Pixel Brush (ink), The Color Smudge Brush (brush) and the filter brush (dodge, burn)."
msgid "A simple inking brush recipe for example is to take a pixel brush, uncheck the :guilabel:`Enable Pen Settings` on opacity and flow, and uncheck everything but size from the option list. Then, go into brush-tip, pick :ref:`auto_brush_tip` from the tabs, and set the size to 25 (right-click a blue bar if you want to input numbers), turn on anti-aliasing under the brush icon, and set fade to 0.9. Then, as a final touch, set spacing to 'auto' and the spacing number to 0.8."
msgid "You can configure the brushes in a lot of detail, and share the packs with others. Importing of packs and brushes can be done via the :menuselection:`Settings --> Manage Resources`, where you can import .bundle files or .kpp files."
-msgid "Erasing is a blending mode in Krita, much like the transparency mode of Paint Tool Sai. It's activated with :kbd:`E` or you can select it from the Blending Mode drop-down..."
+msgid "Erasing is a blending mode in Krita, much like the transparency mode of Paint Tool Sai. It's activated with the :kbd:`E` key or you can select it from the Blending Mode drop-down..."
msgid "Krita has a lot of Blending modes, and thankfully all of Paint Tool Sai's are amongst them except binary. To manage the blending modes, each of them has a little check-box that you can tick to add them to the favorites."
msgid "Multiple, Screen, Overlay and Normal are amongst the favorites. Krita's Luminosity is actually slightly different from Paint Tool Sai's and it replaces the relative brightness of color with the relative brightness of the color of the layer."
msgid "Sai's Luminosity mode is actually the same as Krita's *Addition* or *linear dodge* mode. The Shade mode is the same as *Color Burn* and *Hard Mix* is the same as the lumi and shade mode."
-msgid "For Clipping masks in Krita you'll need to put all your images in a single layer, and then press the 'a' icon, or press :kbd:`Ctrl + Shift + G`."
+msgid "For Clipping masks in Krita you'll need to put all your images in a single layer, and then press the 'a' icon, or press the :kbd:`Ctrl + Shift + G` shortcut."
msgid "These grayscale layers that allow you to affect the transparency are called transparency masks in Krita, and like Paint Tool Sai, they can be applied to groups as well as layers. If you have a selection and make a transparency mask, it will use the selection as a base."
msgid "If you liked this docker in Paint Tool Sai, Krita's Digital Color Selector docker will be able to help you. Dragging the sliders will change how much of a color is mixed in."
msgid "You already met the brush settings editor. Sketch brushes, grid brushes, deform brushes, clone brushes, brushes that are textures, brushes that respond to tilt, rotation, speed, brushes that draw hatches and brushes that deform the colors. Krita's variety is quite big."
msgid "You can have HSV sliders, RGB sliders, triangle in a hue ring. But you can also have HSI, HSL or HSY' sliders, CMYK sliders, palettes, round selectors, square selectors, tiny selectors, big selectors, color history and shade selectors. Just go into :menuselection:`Settings --> Configure Krita --> Advanced Color Selector Settings` to change the shape and type of the main big color selector."
-msgid "You can call the color history with :kbd:`H`, common colors with :kbd:`U` and the two shade selectors with :kbd:`Shift + N` and :kbd:`Shift + M`. The big selector can be called with :kbd:`Shift + I` on canvas."
+msgid "You can call the color history with the :kbd:`H` key, common colors with the :kbd:`U` key and the two shade selectors with the :kbd:`Shift + N` and :kbd:`Shift + M` shortcuts. The big selector can be called with the :kbd:`Shift + I` shortcut on canvas."
-msgid "If you hold :kbd:`R` and press a spot on your drawing, Krita will select the layer underneath the cursor. Really useful when dealing with a large number of layers."
+msgid "If you hold the :kbd:`R` key and press a spot on your drawing, Krita will select the layer underneath the cursor. Really useful when dealing with a large number of layers."
msgid "This allows you to prepare your work for print, or to do tricks with the LUT docker so you can diagnose your image better. For example, using the LUT docker to turn the colors grayscale in a separate view, so you can see the values instantly."
msgid "With filters like color balance and curves you can make easy shadow layers. In fact, with the filter layers and layer masks you can make them apply on the fly as you draw underneath."
msgid "This is the little circular thing that is by default on the right click. You can organize your brushes in tags, and use those tags to fill up the pop-up palette. It also keeps a little color selector and color history, so you can switch brushes on the fly."
msgid "In the real world, when painting or drawing, you don't just use one tool. You use pencils, erasers, paintbrushes, different types of paint, inks, crayons, etc. All these have different ways of making marks."
msgid "In a digital program like Krita you have something similar. We call this a brush engine. And much like how cars have different engines that give different feels when driving, or how pencils make distinctly different marks than rollerball pens, different brush engines have totally different feels."
msgid "Unlike Photoshop, Krita makes a difference between brush-tips and brush-presets. Tips are only a stamp of sorts, while the preset uses a tip and many other settings to create the full brush."
-msgid "To start, the Brush Settings Editor panel can be accessed in the toolbar, between the :guilabel:`Blending Modes` button on the right and the :guilabel:`Patterns` button on the left. Alternately, you can use the function key :kbd:`F5` to open it."
+msgid "To start, the Brush Settings Editor panel can be accessed in the toolbar, between the :guilabel:`Blending Modes` button on the right and the :guilabel:`Patterns` button on the left. Alternately, you can use the :kbd:`F5` key to open it."
msgid "This contains the **Preset Icon**, **Live Brush Preview**, the **Preset Name**, the **Engine** name, and several buttons for saving, renaming, and reloading."
msgid "Krita's brush settings are stored into the metadata of a 200x200 png (the KPP file), where the image in the png file becomes the preset icon. This icon is used everywhere in Krita, and is useful for differentiating brushes in ways that the live preview cannot."
msgid "The live preview shows a stroke of the current brush as a little s-curve wiggle, with the pressure being non-existent on the left, and increasing to full pressure as it goes to the right. It can thus show the effect of the Pressure, Drawing Angle, Distance, Fade and Fuzzy Dab sensors, but none of the others. For some brush engines it cannot show anything. For the color smudge, filter brush and clone tool, it shows an alternating line pattern because these brush engines use the pixels already on canvas to change their effect."
msgid "The engine of a brush is the underlying programming that generates the stroke from a brush. What that means is that different brush engines have different options and different results. You can see this as the difference between using crayons, pencils and inks, but because computers are maths devices, most of our brush engines produce different things in a more mathematical way."
msgid "For most artists the mathematical nature doesn't matter as much as the different textures and marks each brush engine, and each brush engine has its own distinct flavor and use, and can be further customized by modifying the options."
msgid "If you change a preset, an icon will appear behind the engine name. This is the :guilabel:`reload` button. You can use it to revert to the original brush settings."
msgid "This will only enable if there are any changes. Pressing this will override the current preset with the new settings, keeping the name and the icon intact. It will always make a timestamped back up in the resources folder."
msgid "Will take the current preset and all its changes and save it as a new preset. If no change was made, you will be making a copy of the current preset."
msgid "It allows you to select tool icons, and an optional small emblem. When you press :guilabel:`OK` it will load the resulting combination into the mini scratch pad and you can draw in the stroke."
msgid "If you go to your resources folder, there's a folder there called \"preset\\_icons\", and in this folder there are \"tool\\_icons\" and \"emblem\\_icons\". You can add semi-transparent pngs here and Krita will load those into the icon library as well so you can customize your icons even more!"
msgid "At the top right of the icon library, there are three sliders. They allow you to adjust the tool icon. The top two are the same Hue and Saturation as in HSL adjustment, and the lowest slider is a super simple levels filter. This is done this way because the levels filter allows maintaining the darkest shadows and brightest highlights on a tool icon, making it much better for quick adjustments."
msgid "If you're done with everything, you can press :guilabel:`Save` in the :guilabel:`Save New Brush Preset` dialog and Krita will save the new brush."
-msgid "The preset chooser is much the same as the preset docker and the preset drop-down on :kbd:`F6`. It's unique in that it allows you to filter by engine and this is also where you can create brushes for an engine from scratch."
+msgid "The preset chooser is much the same as the preset docker and the preset drop-down on the :kbd:`F6` key. It's unique in that it allows you to filter by engine and this is also where you can create brushes for an engine from scratch."
msgid "The top drop-down is set to “all” by default, which means it shows all engines. It then shows a tag section where you can select the tags, the preset list and the search bar."
msgid "Underneath that there's a plus icon, which when pressed gives you the full list of Krita's engines. Selecting an engine from the list will show the brushes for that engine."
msgid "When you tweak your brushes, you want to be able to check what each setting does. That's why, to the right of the settings drop-down, there is a scratch pad."
msgid "When saving a new preset, you can choose to get the icon from the scratch pad, this will load the dash area into the mini scratch pad of the Save New Brush Preset dialog."
msgid "The options, as stated above, are different per brush engine. These represent the different parameters, toggles and knobs that you can turn to make a brush preset unique. For a couple of options, the main things to change are sliders and check boxes, but for a lot of them, they use curves instead."
msgid "Some options can be toggled, as noted by the little check boxes next to them, but others, like flow and opacity are so fundamental to how the brush works, that they are always on."
msgid "One of the big important things that make art unique to the artist who created it is the style of the strokes. Strokes are different because they differ in speed, rotation, direction, and the amount of pressure put onto the stylus. Because these are so important, we would want to customize how these values are understood in detail. The best way to do this is to use curves."
msgid "Curves show up with the size widget for example. With an inking brush, we want to have size mapped to pressure. Just toggling the size option in the option list will do that."
msgid "However, different people have different wrists and thus will press differently on their stylus. Someone who presses softly tends to find it easy to make thin strokes, but very difficult to make thick strokes. Conversely, someone who presses hard on their stylus naturally will have a hard time making thin strokes, but easily makes thick ones."
msgid "The brush settings curves even have quick curve buttons for these at the top. Someone who has a hard time making small strokes should try the second to last concave button, while someone who has a hard time making thick strokes should try the third button, the S shape."
msgid "This is for the list of sensors. Toggling this will make all the sensors use the same curve. Unchecked, all checked sensors will have separate curves."
msgid "This indicates how the multiple values of the sensor curves are used. The curves always go from 0 to 1.0, so if one curve outputs 0.5 and the other 0.7, then..."
msgid "This enables dirty presets. Dirty presets store the tweaks you make as long as this session of Krita is active. After that, they revert to default. Dirtied presets can be recognized by the icon in the top-left of the preset."
msgid "This allows you to toggle instant preview on the brush. The Instant Preview has a super-secret feature: when you press the instant preview label, and then right click it, it will show a threshold slider. This slider determines at what brush size instant preview is activated for the brush. This is useful because small brushes can be slower with instant preview, so the threshold ensures it only activates when necessary."
msgid "There are on-canvas brush settings. If you open up the pop-up palette, there should be an icon on the bottom-right. Press that to show the on-canvas brush settings. You will see several sliders here, to quickly make small changes."
msgid "At the top it shows the currently active preset. Next to that is a settings button, click that to get a list of settings that can be shown and organized for the given brush engine. You can use the up and down arrows to order their position, and then left and right arrows to add or remove from the list. You can also drag and drop."
msgid "Then, press the arrow on the upper left to open the preset chooser. There, press the “+” icon to get a list of engines. For this brush we're gonna make a pixel brush."
msgid "Draw on the scratch pad to see what the current brush looks like. If done correctly, you should have a 5px wide brush that has pressure set to opacity."
msgid "Let us turn off the opacity first. Click on the :ref:`opacity <option_opacity_n_flow>` option in the right-hand list. The settings should now be changed to a big curve. This is the sensor curve."
msgid "Now you should be getting somewhere towards an inking brush. It is still too small however, and kinda grainy looking. Click :ref:`Brush Tip <option_brush_tip>` in the brush engine options."
msgid "Here, the diameter is the size of the brush-tip. You can touch the slider change the size, or right-click it and type in a value. Set it to 25 and test again. It should be much better."
msgid "If you test again, you'll notice the fade doesn't seem to have much effect. This has to do with the spacing of the dabs: The closer they are together, the harder the line is. By default, this is 0.1, which is a bit low. If you set it to 10 and test, you'll see what kind of effect spacing has. The :ref:`Auto <option_spacing>` checkbox changes the way the spacing is calculated, and Auto Spacing with a value of 0.8 is the best value for inking brushes. Don't forget that you can use right-click to type in a value."
msgid "Now, when you test, the fade seems to have a normal effect... except on the really small sizes, which look pixelly. To get rid of that, check the anti-aliasing check box. If you test again, the lines should be much nicer now."
msgid "You will get the save preset dialog. Name the brush something like “My Preset”. Then, select :guilabel:`Load from Icon Library` to get the icon library. Choose a nice tool icon and press :guilabel:`OK`."
msgid "The icon will be loaded into the mini scratch pad on the left. Now doodle a nice stroke next to it. If you feel you messed up, just go back to the icon library to load a new icon."
msgid "To do this, select the :ref:`size <option_size>` option, and press the pressure sensor from the list next to the curve. The curve should look like a straight line. Now if you want a brush that gets big with little pressure, tick on the curve to make a point, and drag the point to the upper-left. The more the point is to the upper-left, the more extreme the effect. If you want instead a brush that you have to press really hard on to get to full size, drag the dot to the lower-right. Such a brush is useful for fine details. Don't forget to save the changes to your brush when done."
msgid "To do this, select the flow option, and turn back on the :guilabel:`Enable Pen Settings` check box. Now if you test this, it is indeed a bit softer, but maybe a bit too much. Click on the curve to make a dot, and drag that dot to the top-left, half-way the horizontal of the first square of the grid. Now, if you test, the thin lines are much softer, but the hard your press, the harder the brush becomes."
msgid "The recommended way to share brushes and presets is by using the resource bundle system. We have detailed instructions on how to use them on the :ref:`resource management page <resource_management>`."
msgid "So when you have a brush that uses unique predefined tips for either brush tip or masked brush, or unique textures you will need to share those resources as well with the other person."
-msgid "Now, if you want to use the single preset, you should go to the preset chooser on :kbd:`F6` and press the folder icon there. This will give a file dialog. Navigate to the kpp file and open it to import it."
+msgid "Now, if you want to use the single preset, you should go to the preset chooser on the :kbd:`F6` key and press the folder icon there. This will give a file dialog. Navigate to the kpp file and open it to import it."
msgid "If there are brush tips and patterns coming with the file, do the same with pattern via the pattern docker, and for the brush-tip go to the settings drop-down (:kbd:`F5`) and then go to the “brush-tip” option. There, select predefined brush, and then the “import” button to call up the file dialog."
msgid "Copy the brushes, paintoppresets and patterns folders from the zip file to the resource folder. You should get a prompt to merge the folders, agree to this."
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-05-04 09:38+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../user_manual/oncanvas_brush_editor.rst:1
msgid "Using the oncanvas brush editor in Krita."
msgstr ""
#. +> trunk5
#: ../../user_manual/oncanvas_brush_editor.rst:11
msgid "Brush Settings"
msgstr ""
#. +> trunk5
#: ../../user_manual/oncanvas_brush_editor.rst:11
msgid "Pop-up Palette"
msgstr ""
#. +> trunk5
#: ../../user_manual/oncanvas_brush_editor.rst:16
msgid "On-Canvas Brush Editor"
msgstr ""
#. +> trunk5
#: ../../user_manual/oncanvas_brush_editor.rst:19
-msgid "Krita's brush editor is, as you may know, on :kbd:`F5`. However, sometimes you just want to modify a single parameter quickly. Perhaps even in canvas-only mode. The on canvas brush editor or brush HUD allows you to do this. It's accessible from the pop-up palette, by ticking the lower-right arrow button."
+msgid "Krita's brush editor is, as you may know, on the :kbd:`F5` key. However, sometimes you just want to modify a single parameter quickly. Perhaps even in canvas-only mode. The on canvas brush editor or brush HUD allows you to do this. It's accessible from the pop-up palette, by ticking the lower-right arrow button."
msgid "On the left are all unused settings, on the right are all used settings. You use the :guilabel:`>` and :guilabel:`<` buttons to move a setting between the two columns. The :guilabel:`Up` and :guilabel:`Down` buttons allow you to adjust the order of the used settings, for when you think flow is more important than size."
msgid "They can function as a preview shape, or you can snap onto them with the freehand brush tool. In the tool options of free hand brush, you can toggle :guilabel:`Snap to Assistants` to turn on snapping."
-msgid "If you press :kbd:`Shift` while holding the first two handles, they will snap to perfectly horizontal or vertical lines. Press :kbd:`Shift` while holding the third handle, and it'll snap to a perfect circle."
+msgid "If you press the :kbd:`Shift` key while holding the first two handles, they will snap to perfectly horizontal or vertical lines. Press the :kbd:`Shift` key while holding the third handle, and it'll snap to a perfect circle."
msgid "This assistant allows you to position and adjust four points to create a cubic bezier curve. You can then draw along the curve, snapping your brush stroke directly to the curve line. Perfect curves every time!"
-msgid "If you press :kbd:`Shift` while holding the first two handles, they will snap to perfectly horizontal or vertical lines. Press :kbd:`Shift` while holding the third or fourth handle, they will snap relative to the handle they are attached to."
+msgid "If you press the :kbd:`Shift` key while holding the first two handles, they will snap to perfectly horizontal or vertical lines. Press the :kbd:`Shift` key while holding the third or fourth handle, they will snap relative to the handle they are attached to."
msgid "This assistant allows you to create a vanishing point, typically used for a horizon line. A preview line is drawn and all your snapped lines are drawn to this line."
-msgid "If you press :kbd:`Shift` while holding the center handle, they will snap to perfectly horizontal or vertical lines depending on the position of where it previously was."
+msgid "If you press the :kbd:`Shift` key while holding the center handle, they will snap to perfectly horizontal or vertical lines depending on the position of where it previously was."
msgid "When you've just created, or when you've just moved a vanishing point assistant, it will be selected. This means you can modify the amount of lines shown in the tool options of the :ref:`assistant_tool`."
msgid "Like the vanishing point assistant, this assistant is per a set of parallel lines in a 3d space. So to use it effectively, use two, where the second is at a 90 degrees angle of the first, and add a vanishing point to the center of both. Or combine one with a parallel ruler and a vanishing point, or even one with two vanishing points. The possibilities are quite large."
msgid "This assistant will not just give feedback/snapping between the vanishing points, but also give feedback to the relative left and right of the assistant. This is so you can use it in edge-cases like panoramas with relative ease."
msgid "So now that you've seen the wide range of drawing assistants that Krita offers, here is an example of how using these assistants you can set up Krita for technical drawing."
msgid "Orthographic is a mode where you try to look at something from the left or the front. Typically, you try to keep everything in exact scale with each other, unlike perspective deformation."
msgid "The key assistant you want to use here is the Parallel Ruler. You can set these up horizontally or vertically, so you always have access to a Grid."
msgid "Isometric perspective has technically all three rulers set up at 120° from each other. Except when it's game isometric, then it's a type of dimetric projection where the diagonal values are a 116.565° from the main. The latter can be easily set up by snapping the assistants to a grid."
msgid "A 2 point perspective is set up using 2 vanishing point and 1 vertical parallel ruler. Often, putting the vanishing points outside the frame a little can decrease the strength of it."
msgid "There's a little secret that perspective tutorials don't always tell you, and that's that a vanishing point is the point where any two parallel lines meet. This means that a 1 point perspective and 2 point perspective are virtually the same."
msgid "You are probably familiar with the problem: How to determine where the next beam is going to be, as perspective projection will make them look closer together."
msgid "Typically, the solution is to draw a line in the middle and then draw lines diagonally across. After all, those lines are parallel, meaning that the exact same distance is used."
msgid "But because they are parallel, we can use a vanishing point assistant instead, and we use the alignment handles to align it to the diagonal of the beam, and to the horizontal (here marked with red)."
msgid "Because any given set of lines has a vanishing point (outside of the ones flat on the view-plane), there can be an infinite amount of vanishing points in a linear perspective. Therefore, Krita allows you to set vanishing points yourself instead of forcing you to only use a few."
msgid "Fish eye perspective works much the same as the linear perspective, the big difference being that in a fish-eye perspective, any parallel set of lines has two vanishing points, each for one side."
msgid "When we offered python scripting as one of Kickstarter Stretchgoals we could implement next to vectors and text, it won the backer vote by a landslide. Some people even only picked python and nothing else. So what exactly is python scripting?"
msgid "Python is a scripting language, that can be used to automate tasks. What python scripting in Krita means is that we added an API to krita, which is a bit of programming that allows python to access to parts of Krita. With this we can make dockers, perform menial tasks on a lot of different files and even write our own exporters. People who work with computer graphics, like VFX and video game artists use python a lot to make things like sprite sheets, automate parts of export and more."
msgid "It is outside the scope of this manual to teach you python itself. However, as python is an extremely popular programming language and great for beginners, there's tons of learning material around that can be quickly found with a simple 'learn python' internet search."
msgid "This manual will instead focus on how to use python to automate and extend Krita. For that we'll first start with the basics: How to run Python commands in the scripter."
msgid "The scripter plugin is not necessary to use python, but it is very useful for testing and playing around with python. It is a python console, written in python, which can be used to write small scripts and execute them on the fly."
msgid "To open the scripter, navigate to :menuselection:`Tools --> Scripts --> Scripter`. If you don't see it listed, go to :menuselection:`Settings --> Configure Krita --> Python Plugin Manager` and toggle \"Scripter\" in the list to enable it. If you don't see the scripter plugin, make sure you are using an up-to-date version of Krita."
-msgid "Press the big play button or press :kbd:`Ctrl + R` to run the script. Then, below, in the output area the following should show up::"
+msgid "Press the big play button or press the :kbd:`Ctrl + R` shortcut to run the script. Then, below, in the output area the following should show up::"
msgid "This will open up a new document. Clearly Python gives you quite a lot of control to automate Krita. Over time we expect the community to write all kinds of scripts that you can use simply by pasting them in the scripter."
msgid "But what if you want to write new commands for yourself? The best place to start is very simple: search for examples written by other people! You can save a lot of time if someone else has written code that you can base your work on. It's also worth looking through the python plugins, which are located in /share/krita/pykrita. There's also a step by step guide for :ref:`krita_python_plugin_howto` here in the manual."
msgid "But it's likely that you need more information. For that, we will need see what's hidden behind the asterisk when you ``import * from Krita``. To learn what Krita functions that are available and how to use them, you will want to go for Krita API reference documentation."
msgid "Those pages may look like a lot of jargon at first. This is because Krita's API documentation comes from the underlying C++ language that Krita is written in. The magic happens because of a Python tool called SIP, which makes it possible for python speak in C++ and talk to Krita. The end result is that when we ``import krita`` and call functions, we're actually using the C++ methods listed in that documentation."
msgid "Let's see how this stuff works in more detail. Let's take a look at the second link, the `Krita class reference <https://api.kde.org/extragear-api/graphics-apidocs/krita/libs/libkis/html/classKrita.html#aa55507903d088013ced2df8c74f28a63>`_. There we can see all the functions available to the Krita instance. If you type dir(Krita.instance()) in Python, it should match this page very closely - you can view the documentation of the functions createDocument(), activeWindow(), and action() which we used above."
msgid "One of the more confusing things is seeing all the C++ classes that Krita uses, including the Qt classes that start with Q. But here is the beauty of SIP: it tries to make the translation from these classes into Python as simple and straightforward as possible. For example, you can see that the function filters() returns a QStringList. However, SIP converts those QStringLists into regular python list of strings!"
msgid "It is a list of something, sure, but how to use it? If we go back to the Krita apidocs page and look at the function, documents() we'll see there's actually a clickable link on the 'Document' class. `If you follow that link <https://api.kde.org/extragear-api/graphics-apidocs/krita/libs/libkis/html/classDocument.html>`_, you'll see that the document has a function called name() which returns the name of the document, and functions width() and height() which return the dimensions. So if we wanted to generate an info report about the documents in Krita, we could write a script like this:"
msgid "Krita's API has many more classes, you can get to them by going to the top-left class list, or just clicking their names to get to their API docs. The functions print() or dir() are your friends here as well. This line will print out a list of all the actions in Krita - you could swap in one of these commands instead of 'python_scripter' in the example above."
msgid "Finally, in addition to the LibKis documentation, the Qt documentation, since Krita uses PyQt to expose nearly all of the Qt API to Python. You can build entire windows with buttons and forms this way, using the very same tools that Krita is using! You can read the `Qt documentation <https://doc.qt.io/>`_ and the `PyQt documentation <https://www.riverbankcomputing.com/static/Docs/PyQt5/>`_ for more info about this, and also definitely study the included plugins as well to see how they work."
msgid "To get Python scripting working on Windows 7/8/8.1, you will need to install the `Universal C Runtime from Microsoft's website <https://www.microsoft.com/en-us/download/details.aspx?id=48234>`_. (Windows 10 already comes with it.)"
-msgid "Click where you want each point of the Polygon to be. Double click to end your polygon and finalize your selection area. Use :kbd:`Shift + Z` to undo last point."
+msgid "Click where you want each point of the Polygon to be. Double click to end your polygon and finalize your selection area. Use the :kbd:`Shift + Z` shortcut to undo last point."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:1
msgid ":ref:`outline_selection_tool`"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:1
msgid "|toolselectoutline|"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:1
msgid "Outline/Lasso tool is used for a rough selection by drawing the outline."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:1
msgid ":ref:`similar_selection_tool`"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:1
msgid "|toolselectsimilar|"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:1
msgid "Similar Color Selection Tool."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:1
msgid ":ref:`contiguous_selection_tool`"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:1
msgid "|toolselectcontiguous|"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:1
msgid "Contiguous or “Magic Wand” selects a field of color. Adjust the :guilabel:`Fuzziness` to allow more changes in the field of color, by default limited to the current layer."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:1
msgid ":ref:`path_selection_tool`"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:1
msgid "|toolselectpath|"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:1
-msgid "Path select an area based on a vector path, click to get sharp corners or drag to get flowing lines and close the path with :kbd:`Enter` or connecting back to the first point."
+msgid "Path select an area based on a vector path, click to get sharp corners or drag to get flowing lines and close the path with the :kbd:`Enter` key or connecting back to the first point."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:12
msgid "Selection"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:17
msgid "Selections"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:19
msgid "Selections allow you to pick a specific area of your artwork to change. This is useful for when you want to move a section, transform it, or paint on it without affecting the other sections. There are many selection tools available that select in different ways. Once an area is selected, most tools will stay inside that area. On that area you can draw or use gradients to quickly get colored and/or shaded shapes with hard edges."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:22
msgid "Creating Selections"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:24
msgid "The most common selection tools all exist at the bottom of the toolbox. Each tool selects things slightly differently. The links for each tool go into a more detailed description of how to use it."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:38
msgid "You can also use the transform tools on your selection, a great way to try different proportions on parts of your image."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:41
msgid "Editing Selections"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:43
msgid "The tool options for each selection tool gives you the ability to modify your selection."
msgid "Get the overlapping section of both selections"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:53
msgid "Add"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:53
msgid "Shift"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:53
msgid "A"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:53
msgid "Add the new selection to the current selection."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:55
msgid "Subtract"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:55
msgid "Alt"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:55
msgid "S"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:55
msgid "Subtract the selection from the current selection."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:57
msgid "Symmetric Difference"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:57
msgid "Make a selection where both the new and current do not overlap."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:61
msgid "You can change this in :ref:`tool_options_settings`."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:63
msgid "If you hover over a selection with a selection tool and no selection is activated, you can move it. To quickly go into transform mode, |mouseright| and select :guilabel:`Edit Selection`."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:66
msgid "Removing Selections"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:68
msgid "If you want to delete the entire selection, the easiest way is to deselect everything. :menuselection:`Select --> Deselect`. Shortcut :kbd:`Ctrl + Shift + A`."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:71
msgid "Display Modes"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:73
msgid "In the bottom left-hand corner of the status bar there is a button to toggle how the selection is displayed. The two display modes are the following: (Marching) Ants and Mask. The red color with Mask can be changed in the preferences. You can edit the color under :menuselection:`Settings --> Configure Krita --> Display --> Selection Overlay`. If there is no selection, this button will not do anything."
msgid "Mask display mode is good if you are interested in seeing the various transparency levels for your selection. For example, when you have a selection with very soft edges due using feathering."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:86
msgid "Mask mode is activated as well when a selection mask is the active layer so you can see the different selection levels."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:89
msgid "Global Selection Mask (Painting a Selection)"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:91
msgid "The global Selection Mask is your selection that appears on the layers docker. By default, this is hidden, so you will need to make it visible via :menuselection:`Select --> Show Global Selection Mask`."
msgid "Once the global Selection Mask is shown, you will need to create a selection. The benefit of using this is that you can paint your selection using any of the normal painting tools, including the transform and move. The information is saved as grayscale."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:98
msgid "You can enter the global selection mask mode quickly from the selection tools by doing |mouseright| and select :guilabel:`Edit Selection`."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:101
msgid "Selection from layer transparency"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:104
msgid "You can create a selection based on a layer's transparency by right-clicking on the layer in the layer docker and selecting :guilabel:`Select Opaque` from the context menu."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:108
msgid "You can also do this for adding, subtracting and intersecting by going to :menuselection:`Select --> Select Opaque`, where you can find specific actions for each."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:110
-msgid "If you want to quickly select parts of layers, you can hold :kbd:`Ctrl +` |mouseleft| on the layer *thumbnail*. To add a selection do :kbd:`Ctrl + Shift+` |mouseleft|, to remove :kbd:`Ctrl + Alt +` |mouseleft| and to intersect :kbd:`Ctrl + Shift + Alt` |mouseleft|. This works with any mask that has pixel or vector data (so everything but transform masks)."
+msgid "If you want to quickly select parts of layers, you can hold the :kbd:`Ctrl +` |mouseleft| shortcut on the layer *thumbnail*. To add a selection do :kbd:`Ctrl + Shift +` |mouseleft|, to remove :kbd:`Ctrl + Alt +` |mouseleft| and to intersect :kbd:`Ctrl + Shift + Alt +` |mouseleft|. This works with any mask that has pixel or vector data (so everything but transform masks)."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:114
msgid "Pixel and Vector Selection Types"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:116
msgid "Vector selections allow you to modify your selection with vector anchor tools. Pixel selections allow you to modify selections with pixel information. They both have their benefits and disadvantages. You can convert one type of selection to another."
msgid "When creating a selection, you can select what type of selection you want from the Mode in the selection tool options: Pixel or Vector. By default this will be a vector."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:122
msgid "Vector selections can be modified as any other :ref:`vector shape <vector_graphics>` with the :ref:`shape_selection_tool`, if you try to paint on a vector selection mask it will be converted into a pixel selection. You can also convert vector shapes to selection. In turn, vector selections can be made from vector shapes, and vector shapes can be converted to vector selections using the options in the :guilabel:`Selection` menu. Krita will add a new vector layer for this shape."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:124
msgid "One of the most common reasons to use vector selections is that they give you the ability to move and transform a selection without the kind of resize artifacts you get with a pixel selection. You can also use the :ref:`shape_edit_tool` to change the anchor points in the selection, allowing you to precisely adjust bezier curves or add corners to rectangular selections."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:126
msgid "If you started with a pixel selection, you can still convert it to a vector selection to get these benefits. Go to :menuselection:`Select --> Convert to Vector Selection`."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:130
msgid "If you have multiple levels of transparency when you convert a selection to vector, you will lose the semi-transparent values."
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:133
msgid "Common Shortcuts while Using Selections"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:135
msgid "Copy -- :kbd:`Ctrl + C` or :kbd:`Ctrl + Ins`"
msgstr ""
#. +> trunk5
#: ../../user_manual/selections.rst:136
msgid "Paste -- :kbd:`Ctrl + V` or :kbd:`Shift + Ins`"
msgid "In Krita 3.0, we now have functionality for Grids and Guides, but of course, this functionality is by itself not that interesting without snapping."
msgstr ""
#. +> trunk5
#: ../../user_manual/snapping.rst:21
msgid "Snapping is the ability to have Krita automatically align a selection or shape to the grids and guides, document center and document edges. For Vector layers, this goes even a step further, and we can let you snap to bounding boxes, intersections, extrapolated lines and more."
msgstr ""
#. +> trunk5
#: ../../user_manual/snapping.rst:26
-msgid "All of these can be toggled using the snap pop-up menu which is assigned to :kbd:`Shift+S`."
+msgid "All of these can be toggled using the snap pop-up menu which is assigned to :kbd:`Shift + S` shortcut."
msgstr ""
#. +> trunk5
#: ../../user_manual/snapping.rst:29
msgid "Now, let us go over what each option means:"
msgstr ""
#. +> trunk5
#: ../../user_manual/snapping.rst:32
msgid "This will snap the cursor to the current grid, as configured in the grid docker. This doesn’t need the grid to be visible. Grids are saved per document, making this useful for aligning your art work to grids, as is the case for game sprites and grid-based designs."
msgstr ""
#. +> trunk5
#: ../../user_manual/snapping.rst:34
msgid "Grids"
msgstr ""
#. +> trunk5
#: ../../user_manual/snapping.rst:37
msgid "Pixel"
msgstr ""
#. +> trunk5
#: ../../user_manual/snapping.rst:37
msgid "This allows to snap to every pixel under the cursor. Similar to Grid Snapping but with a grid having spacing = 1px and offset = 0px."
msgstr ""
#. +> trunk5
#: ../../user_manual/snapping.rst:40
msgid "This allows you to snap to guides, which can be dragged out from the ruler. Guides do not need to be visible for this, and are saved per document. This is useful for comic panels and similar print-layouts, though we recommend Scribus for more intensive work."
msgid "This allows you to snap to a horizontal or vertical line from existing vector objects’s nodes (Unless dealing with resizing the height or width only, in which case you can drag the cursor over the path). This is useful for aligning object horizontally or vertically, like with comic panels."
msgstr ""
#. +> trunk5
#: ../../user_manual/snapping.rst:52
msgid "Orthogonal (Vector Only)"
msgstr ""
#. +> trunk5
#: ../../user_manual/snapping.rst:55
msgid ".. image:: images/snapping/Snap-node.png"
msgstr ""
#. +> trunk5
#: ../../user_manual/snapping.rst:57
msgid "Node (Vector Only)"
msgstr ""
#. +> trunk5
#: ../../user_manual/snapping.rst:57
msgid "This snaps a vector node or an object to the nodes of another path."
msgid "When we draw an open path, the last nodes on either side can be mathematically extended. This option allows you to snap to that. The direction of the node depends on its side handles in path editing mode."
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-05-04 09:38+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:1
msgid "How to use softproofing in Krita."
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:11
msgid "Color"
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:11
msgid "Softproofing"
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:16
msgid "Soft Proofing"
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:18
msgid "When we make an image in Krita, and print that out with a printer, the image tends to look different. The colors are darker, or less dark than expected, maybe the reds are more aggressive, maybe contrast is lost. For simple documents, this isn’t much of a problem, but for professional prints, this can be very sad, as it can change the look and feel of an image drastically."
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:20
msgid "The reason this happens is simply because the printer uses a different color model (CMYK) and it has often access to a lower range of colors (called a gamut)."
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:22
msgid "A naive person would suggest the following solution: do your work within the CMYK color model! But there are three problems with that:"
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:24
msgid "Painting in a CMYK space doesn’t guarantee that the colors will be the same on your printer. For each combination of Ink, Paper and Printing device, the resulting gamut of colors you can use is different. Which means that each of these could have a different profile associated with them."
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:25
msgid "Furthermore, even if you have the profile and are working in the exact color space that your printer can output, the CMYK color space is very irregular, meaning that the color maths isn’t as nice as in other spaces. Blending modes are different in CMYK as well."
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:26
msgid "Finally, working in that specific CMYK space means that the image is stuck to that space. If you are preparing your work for different a CMYK profile, due to the paper, printer or ink being different, you might have a bigger gamut with more bright colors that you would like to take advantage of."
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:28
msgid "So ideally, you would do the image in RGB, and use all your favorite RGB tools, and let the computer do a conversion to a given CMYK space on the fly, just for preview. This is possible, and is what we call ''Soft Proofing''."
msgid "On the left, the original, on the right, a view where soft proofing is turned on. The difference is subtle due to the lack of really bright colors, but the soft proofed version is slightly less blueish in the whites of the flowers and slightly less saturated in the greens of the leaves."
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:36
-msgid "You can toggle soft proofing on any image using :kbd:`Ctrl + Y`. Unlike other programs, this is per-view, so that you can look at your image non-proofed and proofed, side by side. The settings are also per image, and saved into the .kra file. You can set the proofing options in :menuselection:`Image --> Image Properties --> Soft Proofing`."
+msgid "You can toggle soft proofing on any image using the :kbd:`Ctrl + Y` shortcut. Unlike other programs, this is per-view, so that you can look at your image non-proofed and proofed, side by side. The settings are also per image, and saved into the .kra file. You can set the proofing options in :menuselection:`Image --> Image Properties --> Soft Proofing`."
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:38
msgid "There you can set the following options:"
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:40
msgid "Profile, Depth, Space"
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:41
msgid "Of these, only the profile is really important. This will serve as the profile you are proofing to. In a professional print workflow, this profile should be determined by the printing house."
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:43
msgid "Set the proofing Intent. It uses the same intents as the intents mentioned in the :ref:`color managed workflow <color_managed_workflow>`."
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:48
msgid "Intent"
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:49
msgid "Left: Soft proofed image with Adaptation state slider set to max. Right: Soft proofed image with Adaptation State set to minimum"
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:50
msgid "Adaptation State"
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:51
msgid "A feature which allows you to set whether :guilabel:`Absolute Colorimetric` will make the white in the image screen-white during proofing (the slider set to max), or whether it will use the white point of the profile (the slider set to minimum). Often CMYK profiles have a different white as the screen, or amongst one another due to the paper color being different."
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:52
msgid "Black Point Compensation"
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:53
msgid "Set the black point compensation. Turning this off will crunch the shadow values to the minimum the screen and the proofing profile can handle, while turning this on will scale the black to the screen-range, showing you the full range of grays in the image."
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:55
msgid "Gamut Warning"
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:55
msgid "Set the color of the out-of-gamut warning."
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:57
msgid "You can set the defaults that Krita uses in :menuselection:`Settings --> Configure Krita --> Color Management`."
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:59
msgid "To configure this properly, it's recommended to make a test image to print (and that is printed by a properly set-up printer) and compare against, and then approximate in the proofing options how the image looks compared to the real-life copy you have made."
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:62
msgid "Out of Gamut Warning"
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:64
msgid "The out of gamut warning, or gamut alarm, is an extra option on top of Soft-Proofing: It allows you to see which colors are being clipped, by replacing the resulting color with the set alarm color."
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:66
msgid "This can be useful to determine where certain contrasts are being lost, and to allow you to change it slowly to a less contrasted image."
msgid "Left: View with original image, Right: View with soft proofing and gamut warnings turned on. Krita will save the gamut warning color alongside the proofing options into the Kra file, so pick a color that you think will stand out for your current image."
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:74
-msgid "You can activate Gamut Warnings with :kbd:`Ctrl + Shift + Y`, but it needs soft proofing activated to work fully."
+msgid "You can activate Gamut Warnings with the :kbd:`Ctrl + Shift + Y` shortcut, but it needs soft proofing activated to work fully."
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:77
msgid "Soft Proofing doesn’t work properly in floating-point spaces, and attempting to force it will cause incorrect gamut alarms. It is therefore disabled."
msgstr ""
#. +> trunk5
#: ../../user_manual/soft_proofing.rst:80
-msgid "Gamut Warnings sometimes give odd warnings for linear profiles in the shadows. This is a bug in LCMS, see `here <http://ninedegreesbelow.com/bug-reports/soft-proofing-problems.html>`_ for more info."
+msgid "Gamut Warnings sometimes give odd warnings for linear profiles in the shadows. This is a bug in LCMS, see `here <https://ninedegreesbelow.com/bug-reports/soft-proofing-problems.html>`_ for more info."
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-05-04 09:38+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../user_manual/tag_management.rst:1
msgid "Detailed steps on how to use the tags to organize resources in Krita."
msgstr ""
#. +> trunk5
#: ../../user_manual/tag_management.rst:11
msgid "Tags"
msgstr ""
#. +> trunk5
#: ../../user_manual/tag_management.rst:16
msgid "Tag Management"
msgstr ""
#. +> trunk5
#: ../../user_manual/tag_management.rst:18
msgid "Tags are how you organize common types of resources. They can be used with brushes, gradients, patterns, and even brush tips. You can select them from a drop-down menu above the resources. Selecting a tag will filter all the resources by that tag. Selecting the tag of :guilabel:`All` will show all resources. Krita comes installed with a few default tags. You can create and edit your own as well. The tags are managed similarly across the different types of resources."
msgstr ""
#. +> trunk5
#: ../../user_manual/tag_management.rst:20
msgid "You can use tags together with the :ref:`Pop-up Palette <navigation>` for increased productivity."
msgid "You can select different brush tags in the pop-up palette. This can be a quick way to access your favorite brushes."
msgstr ""
#. +> trunk5
#: ../../user_manual/tag_management.rst:28
msgid "Adding a New Tag for a Brush"
msgstr ""
#. +> trunk5
#: ../../user_manual/tag_management.rst:30
-msgid "By pressing the :guilabel:`+` next to the tag selection, you will get an option to add a tag. Type in the name you want and press :kbd:`Enter`. You will need to go back to the :guilabel:`All` tag to start assigning brushes."
+msgid "By pressing the :guilabel:`+` next to the tag selection, you will get an option to add a tag. Type in the name you want and press the :kbd:`Enter` key. You will need to go back to the :guilabel:`All` tag to start assigning brushes."
msgstr ""
#. +> trunk5
#: ../../user_manual/tag_management.rst:33
msgid "Assigning an Existing Tag to a Brush"
msgstr ""
#. +> trunk5
#: ../../user_manual/tag_management.rst:35
msgid "Right-click on a brush in the Brush Presets Docker. You will get an option to assign a tag to the brush."
msgstr ""
#. +> trunk5
#: ../../user_manual/tag_management.rst:38
msgid "Changing a Tag's Name"
msgstr ""
#. +> trunk5
#: ../../user_manual/tag_management.rst:40
-msgid "Select the existing tag that you want to have changed from the drop-down. Press the :guilabel:`+` icon next to the tag. You will get an option to rename it. Press :kbd:`Enter` to confirm. All the existing brushes will remain in the newly named tag."
+msgid "Select the existing tag that you want to have changed from the drop-down. Press the :guilabel:`+` icon next to the tag. You will get an option to rename it. Press the :kbd:`Enter` key to confirm. All the existing brushes will remain in the newly named tag."
msgstr ""
#. +> trunk5
#: ../../user_manual/tag_management.rst:43
msgid "Deleting a Tag"
msgstr ""
#. +> trunk5
#: ../../user_manual/tag_management.rst:44
msgid "Select the existing tag that you want to have removed from the drop-down. Press the :guilabel:`+` icon next to the tag. You will get an option to remove it."
msgstr ""
#. +> trunk5
#: ../../user_manual/tag_management.rst:47
msgid "The default brushes that come with Krita cannot have their default tags removed."
# Copyright (C) licensed under the GNU Free Documentation License 1.3+ unless stated otherwise
# This file is distributed under the same license as the Krita Manual package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Krita Manual 4.2\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2019-05-04 09:38+0200\n"
+"POT-Creation-Date: 2019-08-02 09:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <kde-i18n-doc@kde.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: ../../user_manual/working_with_images.rst:1
msgid "Detailed steps on how images work in Krita"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:12
#: ../../user_manual/working_with_images.rst:58
msgid "Metadata"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:12
msgid "Image"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:12
msgid "Document"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:12
msgid "Raster"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:12
msgid "Vector"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:17
msgid "Working with Images"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:19
msgid "Computers work with files and as a painting program, Krita works with images as the type of file it creates and manipulates."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:23
msgid "What do Images Contain?"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:25
msgid "If you have a text document, it of course contains letters, strung in the right order, so the computer loads them as coherent sentences."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:29
msgid "Raster Data"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:31
msgid "This is the main data on the paint layers you make. So these are the strokes with the paint brush and look pixely up close. A multi-layer file will contain several of such layers, that get overlaid on top of each other so make the final image."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:36
msgid "A single layer file will usually only contain raster data."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:39
msgid "Vector Data"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:41
msgid "These are mathematical operations that tell the computer to draw pixels on a spot. This makes them much more scalable, because you just tell the operation to make the coordinates 4 times bigger to scale it up. Due to this vector data is much more editable, lighter, but at the same time it's also much more CPU intensive."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:48
msgid "Operation Data"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:50
msgid "Stuff like the filter layers, that tells Krita to change the colors of a layer, but also transparency masks, group layer and transformation masks are saved to multi-layer files. Being able to load these depend on the software that initially made the file. So Krita can load and save groups, transparency masks and layer effects from PSD, but not load or save transform masks."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:60
msgid "Metadata is information like the creation date, author, description and also information like DPI."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:64
msgid "Image size"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:66
msgid "The image size is the dimension and resolution of the canvas. Image size has direct effect file size of the Krita document. The more pixels that need to be remembered and the higher the bit depth of the color, the heavier the resulting file will be."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:72
msgid "DPI/PPI"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:74
msgid "**DPI** stands for *Dots per Inch*, **PPI** stands for *Pixels per Inch*. In printing industry, suppose if your printer prints at 300 **DPI**. It means it is actually putting 300 dots of colors in an area equal to an Inch. This means the number of pixels your artwork has in a relative area of an inch."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:80
msgid "**DPI** is the concern of the printer, and artists while creating artwork should keep **PPI** in mind. According to the **PPI** you have set, the printers can decide how large your image should be on a piece of paper."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:85
msgid "Some standards:"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:88
msgid "This is the default PPI of monitors as assumed by all programs. It is not fully correct, as most monitors these days have 125 PPI or even 300 PPI for the retina devices. None the less, when making an image for computer consumption, this is the default."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:90
msgid "72 PPI"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:92
msgid "120 PPI"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:93
msgid "This is often used as a standard for low-quality posters."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:94
msgid "300 PPI"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:95
msgid "This is the minimum you should use for quality prints."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:97
msgid "600 PPI"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:97
msgid "The quality used for line art for comics."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:100
msgid "Color depth"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:102
msgid "We went over color depth in the :ref:`Color Management page <general_concept_color>`. What you need to understand is that Krita has image color spaces, and layer color spaces, the latter which can save memory if used right. For example, having a line art layer in grayscale can half the memory costs."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:108
msgid "Image color space vs layer color space vs conversion."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:110
msgid "Because there's a difference between image color space and layer color space, you can change only the image color space in :menuselection:`Image --> Properties` which will leave the layers alone. But if you want to change the color space of the file including all the layers you can do it by going to :menuselection:`Image --> Convert Image Color Space` this will convert all the layers color space as well."
msgid "Krita will automatically save who created the image into your image's metadata. Along with the other data such as time and date of creation and modification, Krita also shows editing time of a document in the document information dialog, useful for professional illustrators, speed-painters to keep track of the time they worked on artwork for billing purposes. It detects when you haven’t performed actions for a while, and has a precision of ±60 seconds. You can empty it in the document info dialog and of course by unzipping you .kra file and editing the metadata there."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:130
msgid "These things can be edited in :menuselection:`File --> Document Information`, and for the author's information :menuselection:`Settings --> Configure Krita --> Author Information`. Profiles can be switched under :menuselection:`Settings --> Active Author Profile`."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:133
msgid "Setting the canvas background color"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:135
msgid "You can set the canvas background color via :menuselection:`Image --> Image Background Color and Transparency`. This allows you to turn the background color non-transparent and to change the color. This is also useful for certain file formats which force a background color instead of transparency. PNG and JPG export use this color as the default color to fill in transparency if you do not want to export transparency."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:142
msgid "If you come in from a program like :program:`Paint Tool Sai`, then using this option, or using :guilabel:`Set Canvas Background Color` in the new file options, will allow you to work in a slightly more comfortable environment, where transparency isn't depicted with checkered boxes."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:148
msgid "Basic transforms"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:150
msgid "There are some basic transforms available in the image menu."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:152
msgid "Shear Image"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:153
msgid "This will allow you to skew the whole image and its layers."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:154
msgid "Rotate"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:155
msgid "This will allow you to rotate the image and all its layers quickly."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:157
msgid "Mirror Horizontal/Vertical"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:157
msgid "This will allow you to mirror the whole image with all its layers."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:159
msgid "But there are more options than that..."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:162
msgid "Cropping and resizing the canvas"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:164
msgid "You can crop and image with the :ref:`crop_tool`, to cut away extra space and improve the composition."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:168
msgid "Trimming"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:170
msgid "Using :menuselection:`Image --> Trim to Layer`, Krita resizes the image to the dimensions of the layer selected. Useful for when you paste a too large image into the layer and want to resize the canvas to the extent of this layer."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:174
msgid ":menuselection:`Image --> Trim to Selection` is a faster cousin to the crop tool. This helps us to resize the canvas to the dimension of any active selection. This is especially useful with right clicking the layer on the layer stack and choosing :guilabel:`Select Opaque`. :menuselection:`Image --> Trim to Selection` will then crop the canvas to the selection bounding box."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:180
msgid ":menuselection:`Image --> Trim to Image Size` is actually for layers, and will trim all layers to the size of the image, making your files lighter by getting rid of invisible data."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:185
msgid "Resizing the canvas"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:187
-msgid "You can also resize the canvas via :menuselection:`Image --> Resize Canvas` (or :kbd:`Ctrl + Alt + C`). The dialog box is shown below."
+msgid "You can also resize the canvas via :menuselection:`Image --> Resize Canvas` (or the :kbd:`Ctrl + Alt + C` shortcut). The dialog box is shown below."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:191
msgid ".. image:: images/Resize_Canvas.png"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:192
msgid "In this, constraint proportions will make sure the height and width stay in proportion to each other as you change them. Offset indicates where the new canvas space is added around the current image. You basically decide where the current image goes (if you press the left-button, it'll go to the center left, and the new canvas space will be added to the right of the image)."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:199
msgid "Another way to resize the canvas according to the need while drawing is when you scroll away from the end of the canvas, you can see an arrow appear. Clicking this will extend the canvas in that direction. You can see the arrow marked in red in the example below:"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:209
msgid "Resizing the image"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:211
msgid ":guilabel:`Scale Image to New Size` allows you to resize the whole image. Also, importantly, this is where you can change the resolution or *upres* your image. So for instance, if you were initially working at 72 PPI to block in large shapes and colors, images, etc... And now you want to really get in and do some detail work at 300 or 400 PPI this is where you would make the change."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:218
msgid "Like all other dialogs where a chain link appears, when the chain is linked the aspect ratio is maintained. To disconnect the chain, just click on the links and the two halves will separate."
msgid "This powerful image manipulation feature lets you separate an image into its different components or channels."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:233
msgid "This is useful for people working in print, or people manipulating game textures. There's no combine functionality, but what you can do, if using colored output, is to set two of the channels to the addition :ref:`blending_modes`."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:238
msgid "For grayscale images in the RGB space, you can use the copy red, copy green and copy blue blending modes, with using the red one for the red channel image, etc."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:243
msgid "Saving, Exporting and Opening Files"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:245
msgid "When Krita creates or opens a file, it has a copy of the file in memory, that it edits. This is part of the way how computers work: They make a copy of their file in the RAM. Thus, when saving, Krita takes its copy and copies it over the existing file. There's a couple of tricks you can do with saving."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:252
msgid "Krita saves the current image in its memory to a defined place on the hard-drive. If the image hadn't been saved before, Krita will ask you where to save it."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:253
msgid "Save"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:256
msgid "Save As"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:256
msgid "Make a copy of your current file by saving it with a different name. Krita will switch to the newly made file as its active document."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:258
msgid "Open"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:259
msgid "Open a saved file. Fairly straightforward."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:261
msgid "Save a file to a new location without actively opening it. Useful for when you are working on a layered file, but only need to save a flattened version of it to a certain location."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:262
msgid "Export"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:265
msgid "This is a bit of an odd one, but it opens a file, and forgets where you saved it to, so that when pressing 'save' it asks you where to save it. This is also called 'import' in other programs."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:266
msgid "Open Existing Document As Untitled Document"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:269
msgid "Create Copy from Current Image"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:269
msgid "Makes a new copy of the current image. Similar to Open Existing Document As Untitled Document, but then with already opened files."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:272
msgid "Save Incremental Version"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:272
msgid "Saves the current image as 'filename'\\_XXX.kra and switches the current document to it."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:275
msgid "Copies and renames the last saved version of your file to a back-up file and saves your document under the original name."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:276
msgid "Save Incremental Backup"
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:279
msgid "Since Krita's file format is compressed data file, in case of a corrupt or broken file you can open it with archive managers and extract the contents of the layers. This will help you to recover as much as possible data from the file. On Windows, you will need to rename it to filename.zip to open it."