msgid "&kid3; is an application to edit the ID3v1 and ID3v2 tags in MP3 files in an efficient way. Also tags in Ogg/Vorbis, Opus, DSF, FLAC, MPC, APE, MP4/AAC, MP2, Speex, TrueAudio, WavPack, WMA, WAV, AIFF files and tracker modules (MOD, S3M, IT, XM) are supported. It is easy to set tags of multiple files to the same values (<abbrev>e.g.</abbrev> album, artist, year and genre in all files of the same album) and generate the tags from the file name or vice versa."
msgid "Store configuration in file <filename>kid3.ini</filename> inside application folder."
msgstr ""
#. Tag: replaceable
#. +> trunk5
#: index.docbook:134
#, no-c-format
msgid "FILE"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:135
#, no-c-format
msgid "If <filename><replaceable>FILE</replaceable></filename> is the path to a folder, it will be opened. If one or more file paths are given, their common folder is opened and the files are selected."
msgid "The base file name of the desktop entry for this application."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:169
#, no-c-format
msgid "kid3-qt"
msgstr ""
#. Tag: option
#. +> trunk5
#: index.docbook:172
#, no-c-format
msgid "Qt-options"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:173
#, no-c-format
msgid "See <citerefentry><refentrytitle>qt5options</refentrytitle> <manvolnum>7</manvolnum></citerefentry>."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:179 index.docbook:2628
#, no-c-format
msgid "kid3-cli"
msgstr ""
#. Tag: option
#. +> trunk5
#: index.docbook:183
#, no-c-format
msgid "&doublehyphen;dbus"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:184
#, no-c-format
msgid "Activate the &DBus; interface."
msgstr ""
#. Tag: option
#. +> trunk5
#: index.docbook:188
#, no-c-format
msgid "<option>-c</option>"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:189
#, no-c-format
msgid "Execute a command. Multiple <option>-c</option> options are possible, they are executed in sequence. See the section about <link linkend=\"kid3-cli\">kid3-cli</link> for a description of the available commands."
msgid "&kid3; is an application to edit the ID3v1 and ID3v2 tags in MP3 files in an efficient way. These tags can be edited by most MP3 players, but not in a very comfortable and efficient way. Moreover the tags in Ogg/Vorbis, Opus, DSF, FLAC, MPC, APE, MP4/AAC, MP2, Speex, TrueAudio, WavPack, WMA, WAV, AIFF files and tracker modules (MOD, S3M, IT, XM) are supported too."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:215
#, no-c-format
msgid "&kid3; does not grab nor encode MP3 files, but it is targeted to edit the ID3 tags of all files of an album in an efficient way, <abbrev>i.e.</abbrev> with as few mouse clicks and key strokes as possible. Where most other programs can edit either ID3v1 or ID3v2 tags, &kid3; has full control over both versions, can convert tags between the two formats and has access to all ID3v2 tags. Tags of multiple files can be set to the same value, <abbrev>e.g.</abbrev> the artist, album, year and genre of all files of an album typically have the same values and can be set together. If the information for the tags is contained in the file name, the tags can be automatically set from the file name. It is also possible to set the file name according to the tags found in the file in arbitrary formats."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:228
#, no-c-format
msgid "The editing task is further supported by automatic replacement of characters or substrings, for instance to remove illegal characters from filenames. Automatic control of upper and lower case characters makes it easy to use a consistent naming scheme in all tags."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:234
#, no-c-format
msgid "The tag information for full albums can be taken from <ulink url=\"http://gnudb.org\">gnudb.org</ulink>, <ulink url=\"http://tracktype.org\">TrackType.org</ulink>, <ulink url=\"http://musicbrainz.org\">MusicBrainz</ulink>, <ulink url=\"http://discogs.com\">Discogs</ulink>, <ulink url=\"http://www.amazon.com\">Amazon</ulink> or other sources of track lists. The import format is freely configurable by regular expressions."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:243
#, no-c-format
msgid "Please report any problems or feature requests to the author."
msgid "Generate tags from the contents of tag fields"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:262
#, no-c-format
msgid "Generate filename from tags"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:263
#, no-c-format
msgid "Generate and change folder names from tags"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:264
#, no-c-format
msgid "Generate playlist file"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:265
#, no-c-format
msgid "Automatic case conversion and string translation"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:266
#, no-c-format
msgid "Import from <ulink url=\"http://gnudb.org\">gnudb.org</ulink>, <ulink url=\"http://tracktype.org\">TrackType.org</ulink>, <ulink url=\"http://musicbrainz.org\">MusicBrainz</ulink>, <ulink url=\"http://discogs.com\">Discogs</ulink>, <ulink url=\"http://www.amazon.com\">Amazon</ulink> and other data sources"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:272
#, no-c-format
msgid "Export as CSV, &HTML;, playlist, Kover &XML; and other formats. Exported CSV files can be imported again."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:278
#, no-c-format
msgid "Example Usage"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:279
#, no-c-format
msgid "This section describes a typical session with &kid3;. Let's assume we have a folder containing MP3 files with the tracks from the album \"Let's Tag\" from the band \"One Hit Wonder\". The folder is named in the \"artist - album\" format, in our case <filename>One Hit Wonder - Let's Tag</filename>. The folder contains the tracks in the \"track title.mp3\" format, which I think is useful because the filenames are short (important when using mobile MP3 players with small displays) and in the correct order when sorted alphabetically (important when using hardware MP3 players which play the tracks in alphabetical order or in the order in which they are burnt on &CD; and that order is alphabetical when using <command>mkisofs</command>). Besides this, the artist and album information is already in the folder name and does not have to be repeated in the filename. But back to our example, the folder listing looks like this:"
msgstr ""
#. Tag: filename
#. +> trunk5
#: index.docbook:294
#, no-c-format
msgid "01 Intro.mp3"
msgstr ""
#. Tag: filename
#. +> trunk5
#: index.docbook:295
#, no-c-format
msgid "02 We Only Got This One.mp3"
msgstr ""
#. Tag: filename
#. +> trunk5
#: index.docbook:296
#, no-c-format
msgid "03 Outro.mp3"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:297
#, no-c-format
msgid "These files have no tags yet and we want to generate them using &kid3;. We use <menuchoice><guimenu>File</guimenu><guimenuitem>Open</guimenuitem></menuchoice> menu item (or toolbar button) and select one of the files in this folder. All files will be displayed in the file listbox. Lazy as we are, we want to use the information in the folder and file names to generate tags. Therefore we select all files, then click the <guilabel>To:</guilabel> <guibutton>Tag 1</guibutton> button in the <guilabel>File</guilabel> section. This will set the title, artist, album and track values in all files. To set the year and genre values of all files, we keep all files selected and type in \"2002\" for the <guilabel>Date</guilabel> and select \"Pop\" from the <guilabel>Genre</guilabel> combobox. To set only these two values, their check boxes are automatically checked and all other check boxes are left unchecked. Now we change the selection by only selecting the first file and we see that all tags contain the correct values. The tags of the other files can be verified too by selecting them one by one. When we are satisfied with the tags, we use <menuchoice><guimenu>File</guimenu><guimenuitem>Save</guimenuitem></menuchoice> menu item (or toolbar button). Selecting <menuchoice><guimenu>File</guimenu><guimenuitem> Create Playlist</guimenuitem></menuchoice> menu item (or toolbar button) will generate a file <filename>One Hit Wonder - Let's Tag.m3u</filename> in the folder."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:322
#, no-c-format
msgid "Command Reference"
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:325
#, no-c-format
msgid "The &GUI; Elements"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:326
#, no-c-format
msgid "The &kid3; &GUI; is separated in six sections: At the left are the file and folder listboxes, the right side contains the <guilabel>File</guilabel>, <guilabel>Tag 1</guilabel>, <guilabel>Tag 2</guilabel> and <guilabel>Tag 3 </guilabel> sections."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:333
#, no-c-format
msgid "To navigate between the different sections using the keyboard, several keyboard shortcuts are supported. In the tag sections, the shortcuts are active while not editing text or when being in the first column."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:339
#, no-c-format
msgid "<keycombo>&Alt;<keycap>Left</keycap></keycombo>: Go to previous section (<keycombo><keycap>Command</keycap><keycap>[</keycap></keycombo> on &macOS;)"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:343
#, no-c-format
msgid "<keycombo>&Alt;<keycap>Right</keycap></keycombo>: Go to next section (<keycombo><keycap>Command</keycap><keycap>]</keycap></keycombo> on &macOS;)"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:347
#, no-c-format
msgid "<keycombo>&Ctrl;<keycap>Shift</keycap><keycap>V</keycap></keycombo>: From other tag"
msgid "The file list contains the names of all the files in the opened folder which match the selected file name filter (typically <filename class=\"extension\">*.mp3 *.ogg *.opus *.dsf *.flac *.mpc *.aac *.m4a *.m4b *.m4p *.mp4 *.mp2 *.spx *.tta *.wv *.wma *.wav *.aiff *.ape</filename>). A single or multiple files can be selected. To select no file, click into the empty area after the listbox entries. The selection determines the files which are affected by the operations which are available by using the buttons described below."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:385
#, no-c-format
msgid "Besides <guilabel>Name</guilabel>, also other columns <guilabel>Size</guilabel>, <guilabel>Type</guilabel>, <guilabel>Date Modified</guilabel> with file details can be displayed. Columns can be hidden by unchecking their name in the context menu of the list header. The order of the columns can be changed by drag and drop. The sort order can be toggled by clicking on the column header."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:393
#, no-c-format
msgid "At the left of the names an icon can be displayed: a disc to show that the file has been modified or information about which tags are present (V1, V2, V1V2 or NO TAG, no icon is displayed if the file has not been read in yet)."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:398
#, no-c-format
msgid "Folders are displayed with a folder icon. If a folder is opened, its files are displayed in a hierarchical tree. By selecting files from subfolders, operations can be executed on files in different folders, which is useful if the music collection is organized with a folder for each artist containing folders for albums of this artist."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:405
#, no-c-format
msgid "Clicking the <mousebutton>right</mousebutton> mouse button inside the file list opens a context menu with the following commands:"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:409
#, no-c-format
msgid "<guimenuitem>Expand all</guimenuitem>: Expands all folder trees (only the current tree if the <keycap>Shift</keycap> key is pressed)"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:413
#, no-c-format
msgid "<guimenuitem>Collapse all</guimenuitem>: Collapses all folder trees"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:416
#, no-c-format
msgid "<guimenuitem>Rename</guimenuitem>: Changes the name of a file"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:419
#, no-c-format
msgid "<guimenuitem>Move to Trash</guimenuitem>: Moves a file to the trash"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:422
#, no-c-format
msgid "<guimenuitem>Play</guimenuitem>: Plays a file, see <link linkend=\"play\">Play</link>. If the selected file is a playlist, the files of the playlist will be played."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:427
#, no-c-format
msgid "<guimenuitem>Edit</guimenuitem>: Edit a playlist, see <link linkend=\"edit-playlist\">Edit Playlist</link>."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:431
#, no-c-format
msgid "The subsequent entries are user commands, which can be defined in the <guilabel>User Actions</guilabel> tab of <link linkend=\"configure-kid3\">Configure &kid3;</link>. The playback on double click can also be activated there."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:441
#, no-c-format
msgid "Edit Playlist"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:443
#, no-c-format
msgid "A playlist can be created empty or containing the tracks of a folder, see <link linkend=\"create-playlist\">Create Playlist</link>. The playlist file created in such a way can be edited by double click or using <guilabel>Edit</guilabel> from the file list context menu. A dialog with the entries of the playlist is shown. It is possible to open multiple playlists simultaneously."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:450
#, no-c-format
msgid "New entries can be added by drag and drop from the file list, a file manager or another playlist. If an entry is dragged from another playlist, it will be moved or copied depending on the system. To invoke the other operation, respectively, the <keycap>Shift</keycap>, &Ctrl; or &Alt; (to copy instead of move on &macOS;) key has to be pressed. Reordering entries within the playlist is also possible via drag and drop. Alternatively, entries can be moved using the keyboard shortcuts <keycombo>&Ctrl;<keycap>Shift</keycap><keycap>Up</keycap></keycombo> and <keycombo>&Ctrl;<keycap>Shift</keycap><keycap>Down</keycap></keycombo> (on &macOS; <keycap>Command</keycap> has to be pressed instead of &Ctrl;). An entry can be removed using the <keycap>Delete</keycap> key."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:461
#, no-c-format
msgid "Please note the following: To drag entries from the file list, they have to be held at the left side (near the icons), the same gesture at the right side will perform a multi selection, such an action is hereby still easily possible."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:466
#, no-c-format
msgid "When a playlist has been modified, the changes can be stored using <guibutton>Save</guibutton> or discarded using <guibutton>Cancel</guibutton>. When the window is closed, a confirmation prompt is shown if there are unsaved changes."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:472
#, no-c-format
msgid "Tracks selected in a playlist will be automatically selected in the file list, thereby making it possible to edit their tags."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:476
#, no-c-format
msgid "To execute actions on a playlist, its file must be selected in the file list. <guimenuitem>Edit</guimenuitem> from the context menu will lead to the dialog described in this section, and <guimenuitem>Play</guimenuitem> will start the media player with the tracks from the playlist. User actions can act on playlists, for <link linkend=\"qml-examples\">example</link> <guilabel>Export Playlist Folder</guilabel>, which copies the files from a playlist into a folder."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:488
#, no-c-format
msgid "Folder List"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:490
#, no-c-format
msgid "The folder list contains the names of the folders in the opened folder, as well as the current (<filename class=\"directory\">.</filename>) and the parent (<filename class=\"directory\">..</filename>) folder. It allows one to quickly change the folder without using the <guimenuitem>Open</guimenuitem> command or drag and drop."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:497
#, no-c-format
msgid "Column visibility, order and sorting can be configured as described in the section about the <link linkend=\"file-list\">file list</link>."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:504
#, no-c-format
msgid "File"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:506
#, no-c-format
msgid "Shows information about the encoding (MP3, Ogg, Opus, DSF, FLAC, MPC, APE, MP2, MP4, AAC, Speex, TrueAudio, WavPack, WMA, WAV, AIFF), bit rate, sample rate, channels and the length of the file."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:511
#, no-c-format
msgid "The <guilabel>Name</guilabel> line edit contains the name of the file (if only a single file is selected). If this name is changed, the file will be renamed when the Save command is used."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:516
#, no-c-format
msgid "The <guilabel>Format</guilabel> combo box and line edit contains the format to be used when the filename is generated from the first or the second tag. The filename can contain arbitrary characters, even a folder part separated by a slash from the file name, but that folder must already exist for the renaming to succeed. The following special codes are used to insert tag values into the filename:"
msgid "%{ignore} Ignored when generating tags from the file name"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:538
#, no-c-format
msgid "The format codes are not restricted to the examples given above. Any frame name can be used, for instance unified frame names like <userinput>%{albumartist}</userinput>, <userinput>%{discnumber.1}</userinput>, <userinput>%{bpm}</userinput> or format specific names like <userinput>%{popm}</userinput>."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:546
#, no-c-format
msgid "It is possible to prepend and append strings to the replacement for a format code by adding them in double quotes inside the curly braces of a format code. These strings will only be put into the resulting string if the format code yields a nonempty value. For example, if the file name shall both contain the title and the subtitle, one could use <userinput>%{title} [%{subtitle}]</userinput> in the format string. But this would result in a string ending with <computeroutput> []</computeroutput> if no subtitle frame exists for a file. In order to omit the brackets if no subtitle is present, <userinput>%{title}%{\" [\"subtitle\"]\"}</userinput> shall be used instead. This will omit the brackets, the leading space and the subtitle if not subtitle exists."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:560
#, no-c-format
msgid "The list of available formats can be edited in the dialog which appears when clicking the <guibutton>Filename from tag</guibutton> button in the <guilabel>File</guilabel> tab of the <link linkend=\"configure-kid3\">settings</link>."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:567
#, no-c-format
msgid "A second <guilabel>Format</guilabel> combo box (with arrow down) is used to generate the tags from the filename. If the format of the filename does not match this pattern, a few other commonly used formats are tried."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:574
#, no-c-format
msgid "Some commonly used filename formats are already available in the combo box, but it is also possible to type in some special format into the line edit."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:579
#, no-c-format
msgid "The list of available formats can be edited in the dialog which appears when clicking the <guibutton>Tag from filename</guibutton> button in the <guilabel>File</guilabel> tab of the <link linkend=\"configure-kid3\">settings</link>."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:586
#, no-c-format
msgid "Internally, a regular expression is built from the format codes. If advanced regular expressions are required, the format to generate the tags from the filenames can be given as a complete regular expression with captures which are preceded by the format codes, <abbrev>e.g.</abbrev> to extract the track numbers without removal of leading zeros, a format like \"<userinput>/%{track}(\\d+) %{title}(.*)</userinput>\" could be used."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:594
#, no-c-format
msgid "<guilabel>From:</guilabel> <guibutton>Tag 1</guibutton>, <guibutton>Tag 2</guibutton>: Sets the filename using the selected format and the first tag or the second tag, respectively."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:599
#, no-c-format
msgid "<guilabel>To:</guilabel> <guibutton>Tag 1</guibutton>, <guibutton>Tag 2</guibutton>: The tags are set from the filename. First, the format specified in <guilabel>Format</guilabel> is used. If the existing filename does not match this format, the following formats are tried:"
msgstr ""
#. Tag: filename
#. +> trunk5
#: index.docbook:607
#, no-c-format
msgid "Artist - Album/Track Song"
msgstr ""
#. Tag: filename
#. +> trunk5
#: index.docbook:608
#, no-c-format
msgid "Album/Track - Artist - Song"
msgstr ""
#. Tag: filename
#. +> trunk5
#: index.docbook:609
#, no-c-format
msgid "/Artist - Album - Track - Song"
msgstr ""
#. Tag: filename
#. +> trunk5
#: index.docbook:610
#, no-c-format
msgid "Album/Artist - Track - Song"
msgstr ""
#. Tag: filename
#. +> trunk5
#: index.docbook:611
#, no-c-format
msgid "Album/Artist - Song"
msgstr ""
#. Tag: filename
#. +> trunk5
#: index.docbook:612
#, no-c-format
msgid "Artist/Album/Track Song"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:614
#, no-c-format
msgid "If a single file is selected, the &GUI; controls are filled with the values extracted from the filename. If multiple files are selected, the tags of the files are directly set according to the filenames."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:622
#, no-c-format
msgid "Tag 1"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:624
#, no-c-format
msgid "The line edit widgets for <guilabel>Title</guilabel>, <guilabel>Artist</guilabel>, <guilabel>Album</guilabel>, <guilabel>Comment</guilabel>, <guilabel>Date</guilabel>, <guilabel>Track Number</guilabel> and <guilabel>Genre</guilabel> are used to edit the corresponding value in the first tag of the selected files. The value will be changed when the file selection is altered or before operations like <guimenuitem>Save</guimenuitem> and <guimenuitem>Quit</guimenuitem> and when the corresponding check box at the left of the field name is checked. This is useful to change only some values and leave the other values unchanged."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:636
#, no-c-format
msgid "If a single file is selected, all check boxes are checked and the line edit widgets contain the values found in the tags of this file. If a tag is not found in the file, the corresponding empty value is displayed, which is an empty string for the <guilabel>Title</guilabel>, <guilabel>Artist</guilabel>, <guilabel>Album</guilabel> and <guilabel>Comment</guilabel> line edits, 0 for the numerical <guilabel>Date</guilabel> and <guilabel>Track Number</guilabel> edits and an empty selected value for the <guilabel>Genre</guilabel> combo box. The values can be changed and if the corresponding check box is checked, they will be set for the selected file after the selection is changed. The file is then marked as modified by a disk symbol in the file listbox but remains unchanged until the <guimenuitem>Save</guimenuitem> command is used."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:650
#, no-c-format
msgid "If multiple files are selected, only the values which are identical in all selected files are displayed. In all other controls, the empty values as described above are displayed. All check boxes are unchecked to avoid unwanted changes. If a value has to be set for all selected files, it can be edited and the check box has to be set. The values will be set for all selected files when the selection is changed and can be saved using the <guimenuitem>Save</guimenuitem> command."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:659
#, no-c-format
msgid "The check boxes also control the operation of most commands affecting the tags, such as copy, paste and transfer between tags 1 and 2. To make it easier to use with multiple files where all check boxes are unchecked, these commands behave in the same way when all check boxes are checked and when all check boxes are unchecked."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:666
#, no-c-format
msgid "<guibutton>From Tag 2</guibutton>: The tag 1 fields are set from the corresponding values in tag 2. If a single file is selected, the &GUI; controls are filled with the values from tag 2. If multiple files are selected, the tags of the files are directly set."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:673
#, no-c-format
msgid "<guibutton>Copy</guibutton>: The copy buffer is filled with the Tag 1 values. Only values with checked check box will be used in subsequent Paste commands."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:677
#, no-c-format
msgid "<guibutton>Paste</guibutton>: Pastes the values from the copy buffer into the &GUI; controls."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:681
#, no-c-format
msgid "<guibutton>Remove</guibutton>: This will set all &GUI; controls to their empty values which results in removing all values. The saved file will then contain no tag 1."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:689
#, no-c-format
msgid "Tag 2"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:691
#, no-c-format
msgid "The &GUI; controls function in the same way as described for the <guilabel>Tag 1</guilabel> section, but the size of the strings is not limited."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:695
#, no-c-format
msgid "For the tag 2 <guilabel>Genre</guilabel> you can also use your own names besides the genres listed in the combo box, just type the name into the line edit."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:700
#, no-c-format
msgid "The tag 2 cannot only contain the same values as the tag 1, the format is built in a flexible way from several frames which are themselves composed of several fields. The tag 2 table shows all the frames which are available in the selected file."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:706
#, no-c-format
msgid "<guibutton>Edit</guibutton>: This will open a window which allows one to edit all fields of the selected frame. If multiple files are selected, the edited fields are applied to all selected files which contain such a frame."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:712
#, no-c-format
msgid "<guibutton>Add</guibutton>: A requester to select the frame type will appear and a frame of the selected type can be edited and added to the file. This works also to add a frame to multiple selected files."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:717
#, no-c-format
msgid "<guibutton>Delete</guibutton>: Deletes the selected frame in the selected files."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:720
#, no-c-format
msgid "<guilabel>Drag album artwork here</guilabel> is shown if the file does not contain embedded cover art. A picture can be added using drag and drop from a browser or file manager and will be displayed here. Picture frames can be edited or added by double clicking on this control."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:730
#, no-c-format
msgid "Tag 3"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:732
#, no-c-format
msgid "Some files can have more than two tags, and a third tag section is visible. The following file types can have such a <guilabel>Tag 3</guilabel> section:"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:737
#, no-c-format
msgid "MP3 files can have an ID3v1.1 tag, an ID3v2 (2.3.0 or 2.4.0) tag and in the third section an APE tag. Such APE tags are used for replay gain information. In the <guilabel>Tag 3</guilabel> section, this information is visible, and the APE tag can be removed with the <guibutton>Remove</guibutton> button."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:744
#, no-c-format
msgid "The RIFF INFO chunk of WAV files is available in the <guilabel>Tag 3 </guilabel> section because the <guilabel>Tag 1</guilabel> section is dedicated to ID3v1.1 tags and handles their restrictions. The <guilabel>Tag 2</guilabel> is still used for ID3v2.4.0 tags, which are also supported for WAV files, but RIFF INFO chunks seem to be supported better."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:751
#, no-c-format
msgid "FLAC files normally use a Vorbis comment for their meta data. However, there are FLAC files which have ID3v1 and ID3v2 tags, which can be found in the <guilabel>Tag 1</guilabel> and <guilabel>Tag 3</guilabel> sections. ID3 tags in FLAC files are only supported by TagLib, therefore the OggFlacMetadata plugin has to be disabled in the <guilabel>Plugins</guilabel> tab of the <link linkend=\"configure-kid3\">settings</link>."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:760
#, no-c-format
msgid "The &GUI; controls work in the same way as in the <guilabel>Tag 2</guilabel> section."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:769
#, no-c-format
msgid "Frame List"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:771
#, no-c-format
msgid "&kid3; can edit most of the frames for all of the supported file types. Some frames are accessed using unified names, so that they can be exchanged between files with different formats. Frames which are not unified can be accessed as format specific frames."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:779
#, no-c-format
msgid "Mapping of Unified Frame Types to Various Formats"
msgid "Remarks concerning the mappings to unified frame names:"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:841
#, no-c-format
msgid "The number of unified frame names is limited by the fact that a sensible mapping shall be possible for all supported file formats. Most tags support frames with arbitrary names; these will be used if no specific frame is available (<abbrev>e.g.</abbrev> the names in uppercase in the column MP4). If no such possibility exists, some frame types may not be supported for the format, <abbrev>e.g.</abbrev> Author and Performer for ASF (WMA)."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:849
#, no-c-format
msgid "The mappings are not chosen arbitrarily, they are geared to the usage of the frames in other applications and devices. Thus the ID3v2 frame \"TPE2 - Band/orchestra/accompaniment\" does not suggest its usage as Album Artist, but this is commonly used. The actual meaning for ID3v2 on the other hand is the reason why this frame is used for the orchestra when importing (<abbrev>e.g.</abbrev> from Discogs), although this may seem a bit strange for other tag formats."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:857
#, no-c-format
msgid "The mappings are not always bijective. So ID3v2.3 uses an IPLS frame for both Arranger and Performer. When reading back, both frames are displayed as \"Arranger\"."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:862
#, no-c-format
msgid "The frames Arranger and Performer use a particular format for their contents: \"involvement 1|involvee 1|involvement 2|involvee 2|...\", for instance \"Chorus Master|Ernst Dunshirn|Soprano Vocals|Anna Netrebko\". This will create IPLS (ID3v2.3) or TIPL/TMCL (ID3v2.4) frames with a string list in the specified format (the \"|\" is used as a separator between the strings). Values in this format are also set when importing data from servers which offer this information."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:871
#, no-c-format
msgid "To explicitly use a specific frame name which conflicts with a unified frame name, prepend an exclamation mark. For example, adding a frame of type \"<replaceable>Media</replaceable>\" to a Vorbis comment will create a frame with name \"<literal>SOURCEMEDIA</literal>\" because of the unified type mapping. In order to add a frame with name \"<literal>MEDIA</literal>\" and not \"<literal>SOURCEMEDIA</literal>\", use \"<literal>!MEDIA</literal>\" to force the explicit name."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:887
#, no-c-format
msgid "Synchronized Lyrics and Event Timing Codes"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:889
#, no-c-format
msgid "For information synchronized with the audio data, a specific editor is available. These frames are supported for ID3v2.3.0 and ID3v2.4.0 tags. To add such a frame, the specific frame name has to be selected in the list which appears when the <guibutton>Add</guibutton> button is clicked - <guilabel>Synchronized Lyrics</guilabel> or <guilabel>Event Timing Codes</guilabel>, respectively. The editor is the same for both types, for the event timing codes, only a predefined set of events is available whereas for the synchronized lyrics, text has to be entered. In the following, editing synchronized lyrics is explained."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:900
#, no-c-format
msgid "A file having an ID3v2 tag is selected, the lyrics editor is entered using <guibutton>Add</guibutton> and selecting <guilabel>Synchronized Lyrics</guilabel>. For an existing Synchronized Lyrics frame, it is selected and <guibutton>Edit</guibutton> is clicked. The player is automatically opened with the current file so that the file can be played and paused to synchronize lyrics."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:908
#, no-c-format
msgid "The settings at the top of the SYLT editor normally do not have to be changed. If the lyrics contains characters which are not present in the Latin 1 character set, changing the text encoding to UTF16 (or UTF8 for ID3v2.4.0) is advisable. For English lyrics and maximum compatibility, ISO-8859-1 should be used."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:915
#, no-c-format
msgid "The <guilabel>Lyrics</guilabel> section has five buttons at the top. <guibutton>Add</guibutton> will add a new time event in the table. The time is taken from the position of the player, thus adding an entry while playing the track will add a line for the currently played position. The events in the table have to be chronologically ordered, therefore the row will be inserted accordingly. Entries with an invalid time are treated specially: If the currently selected row has an invalid time, its time stamp will be replaced by the current time instead of adding a new row. If the current time is not invalid, the first row with an invalid time will be used if present. This behavior should facilitate adding time stamps if the lyrics text is already in the table but the time stamps are missing (which is the case when importing unsynchronized lyrics). Note that the invalid time is represented as 00:00.00, <abbrev>i.e.</abbrev> the same as the time at the absolute beginning of the track, which is not invalid. To make a time invalid, press the <keycap>Delete</keycap> key, or use <guimenu>Clear</guimenu> from the context menu. New rows inserted using <guimenu>Insert row</guimenu> from the context menu or created when importing unsynchronized lyrics with <guibutton>From Clipboard</guibutton> or <guibutton>Import</guibutton> also contain invalid time stamps. Rows in the table can be deleted by clicking the <guibutton>Delete</guibutton> button or using <guimenu>Delete rows</guimenu> from the context menu."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:937
#, no-c-format
msgid "Synchronized lyrics can be imported from a file using <guibutton>Import</guibutton>. The expected format is simple or enhanced LRC. If the selected file does not contain a square bracket in the first line, it is supposed to be a simple text file with unsynchronized lyrics. The lines from such a file are then imported having invalid time stamps. The time information can be added using the <guibutton>Add</guibutton> button or by manual entry. It is also possible to import lyrics via copy-paste using <guilabel>From Clipboard</guilabel>. Synchronized lyrics can be written to LRC files using <guibutton>Export</guibutton>. Note that only entries with valid time stamps will be exported and that the entries will be sorted by time. Entries with invalid time won't be stored in the SYLT frame either, so make sure to include all timing information before leaving the dialog."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:951
#, no-c-format
msgid "The <ulink url=\"http://id3.org/id3v2.4.0-frames\">ID3 specification</ulink> suggests a time stamp for each syllable. However most players only support the granularity of a line or sentence. To support both use cases, &kid3; follows the same conventions as <ulink url=\"http://www.compuphase.com/software_sylteditor.htm\">SYLT Editor</ulink>. Text which is entered into the table is assumed to start a new line unless it starts with a space or a hyphen. Exceptions to this rule are possible by starting a line with an underscore ('_') to force continuation or a hash mark ('#') to force a new line. These escape characters are not stored inside the SYLT frame. Inside the SYLT frame, new lines start with a line feed character (hex 0A) whereas continuations do not. When reading SYLT frames, &kid3; checks if the first entry starts with a line feed. If this is not the case, it is assumed that all entries are new lines and that no syllable continuations are used."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:967
#, no-c-format
msgid "While the track is played, the row associated with the current playing position is highlighted, so that the correctness of the synchronization information can be verified. If an offset has to be added to one or more time stamps, this can be accomplished with the <guimenu>Add offset</guimenu> context menu. Negative values can be used to reduce the time. Using <guimenu>Seek to position</guimenu> in the context menu, it is possible to set the playing position to the time of the selected row."
msgstr ""
#. Tag: emphasis
#. +> trunk5
#: index.docbook:977
#, no-c-format
msgid "Recommended procedure to add new synchronized lyrics"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:979
#, no-c-format
msgid "Get the unsynchronized lyrics, <abbrev>e.g.</abbrev> using <menuchoice><guimenu>Lyrics</guimenu><guimenuitem>Embed Lyrics</guimenuitem></menuchoice> from the file list context menu."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:983
#, no-c-format
msgid "Copy the unsynchronized lyrics to the clipboard, just go to the <guilabel>Lyrics</guilabel> row in the frame table and press <keycombo>&Ctrl;<keycap>C</keycap></keycombo>."
msgid "Now all lines from the unsynchronized lyrics are in the table, all time stamps are invalid (0:0:0.00). You can delete empty entries beforehand."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:993
#, no-c-format
msgid "Start playing the song by clicking the play button <guibutton>►</guibutton> in the play toolbar at the bottom of the main window."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:996
#, no-c-format
msgid "When the next lyrics line with invalid timestamp comes, click <guibutton>Add</guibutton> or press <keycombo>&Alt;<keycap>A</keycap></keycombo>, the timestamp will be updated."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1000
#, no-c-format
msgid "Continue like this until all timestamps are set. If you missed something, stop playback and clear the timestamps using the <keycap>Delete</keycap> key or by selecting them and using <guimenuitem>Clear</guimenuitem> from the context menu. To restart playback from a given timestamp, use <guimenuitem>Seek to position</guimenuitem> from the context menu."
msgid "<action>Opens a folder.</action> All files matching the selected file name filter will be displayed in the file listbox and the chosen file is selected."
msgid "<action>Saves all changed files in the folder.</action> The changed files are marked with a disk symbol in the file listbox. If any file names have been changed, those files will be renamed."
msgid "<action>Reverts the changes of one or multiple files.</action> If no files are selected in the file listbox, the changes of all files will be reverted, else only the changes of the selected files are reverted."
msgid "The <action>Import dialog</action> can be used to import data directly from a freedb.org server, from a MusicBrainz server, from Discogs, Amazon or other sources of album track lists in textual format."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1095
#, no-c-format
msgid "Import from a freedb.org server is possible using a dialog which appears when <guibutton>From Server:</guibutton> <guibutton>gnudb.org</guibutton> or <guibutton>TrackType.org</guibutton> is selected. The artist and album name to search for can be entered in the two topmost fields, the albums which match the query will be displayed when <guibutton>Find</guibutton> is clicked and the results from <ulink url=\"http://www.gnudb.org\">www.gnudb.org</ulink> are received. Importing the track data for an album is done by double-clicking the album in the list. The freedb.org server to import from can be selected as well as the CGI path. The imported data is displayed in the preview table of the import dialog. When satisfied with the displayed tracks, they can be imported by terminating the import dialog with <guibutton>OK</guibutton>."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1112
#, no-c-format
msgid "A search on the Discogs server can be performed using <guibutton>Discogs</guibutton>. As in the <guibutton>gnudb.org</guibutton> dialog, you can enter artist and album and then choose from a list of releases. If <guilabel>Standard Tags</guilabel> is marked, the standard information is imported, <abbrev>e.g.</abbrev> artist, album, and title. If <guilabel>Additional Tags</guilabel> is marked, more information is imported if available, <abbrev>e.g.</abbrev> performers, arrangers, or the publisher. If <guilabel>Cover Art</guilabel> is marked, cover art will be downloaded if available."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1123
#, no-c-format
msgid "A search on Amazon can be performed using <guibutton>Amazon</guibutton>. As in the <guibutton>gnudb.org</guibutton> dialog, you can enter artist and album and then choose from a list of releases. If <guilabel>Additional Tags</guilabel> is marked, more information is imported if available, <abbrev>e.g.</abbrev> performers, arrangers, or the publisher. If <guilabel>Cover Art</guilabel> is marked, cover art will be downloaded if available."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1132
#, no-c-format
msgid "You can search in the same way in the release database of MusicBrainz using <guibutton>From MusicBrainz Release</guibutton>. The workflow is the same as described for <guibutton>From gnudb.org</guibutton>."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1138
#, no-c-format
msgid "Import from a MusicBrainz server is possible using the dialog which appears when <guibutton>From MusicBrainz Fingerprint</guibutton> is selected. The Server can be selected as in the freedb import dialog. Below is a table displaying the imported track data. The right column shows the state of the MusicBrainz query, which starts with \"Pending\" when the dialog is opened. Then the fingerprint is looked up and if it does not yield a result, another lookup using the tags in the file is tried. Thus it can be helpful for a successful MusicBrainz query to store known information (<abbrev>e.g.</abbrev> artist and album) in the tags before the import. If a result was found, the search ends in the state \"Recognized\", otherwise nothing was found or multiple ambiguous results and one of them has to be selected by the user. <guibutton>OK</guibutton> and <guibutton>Apply</guibutton> use the imported data, <guibutton>Cancel</guibutton> closes the dialog. The closing can take a while since the whole MusicBrainz machinery has to be shut down."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1155
#, no-c-format
msgid "For the import of textual data, <guibutton>From File/Clipboard</guibutton> opens a subdialog, where several preconfigured import formats are available. The first two, \"CSV unquoted\" and \"CSV quoted\" can be used to import data which was exported by the Export dialog. The CSV data can be edited with a spreadsheet, and shall be written using tabs as delimiters. Import should then be possible using \"CSV quoted\", which is more flexible than \"CSV unquoted\". However, its fields cannot contain any double quotes. If you only export from &kid3; and import later, \"CSV unquoted\" can be used as a simple format for this purpose. Note that there are also \"Export CSV\" and \"Import CSV\" commands in the context menu of the file list, which use scripts to export and import CSV data in a more complete, powerful and flexible way."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1170
#, no-c-format
msgid "The next format, \"freedb &HTML; text\", can be used to copy information from an &HTML; page of <ulink url=\"http://freedb.org\">freedb.org</ulink>. Search an album in freedb and if the desired information is displayed in the web browser, copy the contents to the clipboard. Then click the <guibutton>From Clipboard</guibutton> button and the imported tracks will be displayed in the preview table at the top of the dialog. If you are satisfied with the imported data, terminate the dialog with <guibutton>OK</guibutton>, which will insert the data into the tags of the current folder. The destination (<guilabel>Tag 1</guilabel>, <guilabel>Tag 2</guilabel> or <guilabel>Tag 1 and Tag 2</guilabel>) can be selected with a combo box. The files in the current folder should be in the correct track order to get their tags assigned. This is the case if they are numbered."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1185
#, no-c-format
msgid "The next preconfigured import format, \"freedb &HTML; source\", can be used, if the data is available as an &HTML; document. Import is possible using the <guibutton>From File</guibutton> button, which opens a file selector, or copying its contents from an editor and then importing from clipboard. This format can be useful for offline import, although the &HTML; document could also be opened in a browser and then be imported in the first format via the clipboard."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1193
#, no-c-format
msgid "More preconfigured formats, <abbrev>e.g.</abbrev> \"Track Title Time\", are available. An empty custom format can be created with <guibutton>Add</guibutton> to be set by the user. Two lines below the format name can be set with a regular expression to capture the fields from the import text. The first regular expression will be parsed once per document to gather per-album data such as artist, album, year and genre. The second line is tried to match from the start of the document to the end to get track data, usually number and title. The regular expressions include all the features offered by &Qt;, which is most of the what Perl offers. Bracketing constructs \"(..)\" create capture buffers for the fields to import and are preceded by &kid3; specific codes to specify which field to capture. The codes are the same as used for the filename format, besides the codes listed below, any frame name is possible:"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1216
#, no-c-format
msgid "%t %{track} Track"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1218
#, no-c-format
msgid "%d %{duration} Duration"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1222
#, no-c-format
msgid "For example, a track regular expression (second line) to import from an <filename class=\"extension\">.m3u</filename> playlist could be \"<literal>%{track}(\\d+)\\s+%{title}(\\S[^\\r\\n]*)\\.mp3[\\r\\n]</literal>\". All formats can be changed by editing the regular expressions and the name and then clicking <guibutton>Save Settings</guibutton>. They will be stored in the <filename>kid3rc</filename> file in the configuration folder. This file can be directly edited to have more import formats or it can be deleted to revert to the default formats. Formats can be deleted using <guibutton>Remove</guibutton>."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1232
#, no-c-format
msgid "<guilabel>Accuracy</guilabel> shows an estimation of how good the imported information matches the given tracks. It uses track durations or file names to calculate the level of similarity in percent. <guilabel>Cover Art</guilabel> shows the &URL; of the album cover image which will be downloaded."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1239
#, no-c-format
msgid "To check whether the imported tracks match the current set of files, the duration of the imported tracks can be compared with the duration of the files. This option can be enabled with the check box <guibutton>Check maximum allowable time difference (sec):</guibutton> and the maximum tolerated difference in time can be set in seconds. If a mismatch in a length is detected, the length is displayed with a red background in the preview table."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1247
#, no-c-format
msgid "If the files are ordered differently than the imported tracks, their assigned tracks have to be changed. This task can be facilitated using the <guilabel>Match with</guilabel> option with the buttons <guibutton>Length</guibutton>, <guibutton>Track</guibutton>, and <guibutton>Title</guibutton>, which will reorder the tracks according to the corresponding field. To correct the assignments manually, a track can be dragged with the <mousebutton>left</mousebutton> mouse button and the &Ctrl; key hold down, and then dropped at the new location."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1256
#, no-c-format
msgid "When the import dialog is opened, it contains the actual contents of the tags. The tag type (Tag 1, Tag 2, Tag 1 and Tag 2) can be selected using the <guilabel>Destination</guilabel> combo box. The button on the right of this combo box can be used to revert the table to the current contents of the tags. The check boxes in the first table column can be used to select the tracks which are imported. This can be useful if a folder contains the tracks of both &CD;s of a double &CD; and only the tracks of the second &CD; have to be imported."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1266
#, no-c-format
msgid "To identify the tracks which are imported, it is possible to display the file names or the full paths to the files using the context menu of the table header. The values in the import table can be edited. The revert-button to the right of the <guilabel>Destination</guilabel> combo box can be used to restore the contents of the tags, which can also be useful after changing the <guilabel>Destination</guilabel>."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1274
#, no-c-format
msgid "Almost all dialogs feature a <guibutton>Save Settings</guibutton> button, which can be used to store the dialog specific settings and the window size persistently."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1280
#, no-c-format
msgid "<guibutton>From Tags</guibutton> leads to a subdialog to set tag frames from the contents of other tag frames. This can be used to simply copy information between tags or extract a part from one frame and insert it in another."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1285
#, no-c-format
msgid "As in the <link linkend=\"import-text\">import from file/clipboard</link> dialog, there are freely configurable formats to perform different operations. Already preconfigured are formats to copy the Album value to Album Artist, Composer or Conductor, and to extract the Track Number from Title fields which contain a number. There is also a format to extract a Subtitle from a Title field."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1292
#, no-c-format
msgid "The following example explains how to add a custom format, which sets the information from the Subtitle field also in the Comment field. Create a new format using <guibutton>Add</guibutton> button and set a new name, <abbrev>e.g.</abbrev> \"Subtitle to Comment\". Then enter \"<userinput>%{subtitle}</userinput>\" in <guilabel>Source</guilabel> and \"<userinput>%{comment}(.*)</userinput>\" for <guilabel>Extraction</guilabel> and click <guibutton>Save Settings</guibutton>."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1301
#, no-c-format
msgid "The expression in <guilabel>Source</guilabel> can contain <link linkend=\"format-codes\">format codes</link> for arbitrary tag frames, multiple codes can be used to combine the contents from different frames. For each track, a text is generated from its tags using the <guilabel>Source </guilabel> format, and the regular expression from <guilabel>Extraction</guilabel> is applied to this text to set new values for the tags. Format codes are used before the capturing parentheses to specify the tag frame where the captured text shall be stored. It works in the same way as for the <link linkend=\"import-text\">import from file/clipboard</link>."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1312
#, no-c-format
msgid "<guimenuitem>Import from Tags...</guimenuitem> is also directly available from the <guimenu>File</guimenu> menu. The difference between these two functions is that the import dialog subdialog operates on all files of the current folder whereas the menu function operates on the selected files (which can be in different folders). The menu function supports an additional code \"<literal>%{__return}</literal>\" to return the extracted value, which can be useful with the CLI and QML interfaces."
msgstr ""
#. Tag: menuchoice
#. +> trunk5
#: index.docbook:1325
#, no-c-format
msgid "<guimenu>File</guimenu> <guimenuitem>Import from gnudb.org...</guimenuitem>"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1329
#, no-c-format
msgid "<action>Import from a freedb.org server using gnudb.org album search.</action> This menu item opens the same import dialog as <guimenuitem>Import...</guimenuitem>, but opens directly the <guibutton>gnudb.org</guibutton> dialog."
msgstr ""
#. Tag: menuchoice
#. +> trunk5
#: index.docbook:1337
#, no-c-format
msgid "<guimenu>File</guimenu> <guimenuitem>Import from TrackType.org...</guimenuitem>"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1341
#, no-c-format
msgid "<action>Import from the TrackType.org server.</action> This menu item opens the same import dialog as <guimenuitem>Import...</guimenuitem>, but opens directly the <guibutton>TrackType.org</guibutton> dialog."
msgstr ""
#. Tag: menuchoice
#. +> trunk5
#: index.docbook:1348
#, no-c-format
msgid "<guimenu>File</guimenu> <guimenuitem>Import from Discogs...</guimenuitem>"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1352
#, no-c-format
msgid "<action>Import from the Discogs server.</action> This menu item opens the same import dialog as <guimenuitem>Import...</guimenuitem>, but opens directly the <guibutton>From Discogs</guibutton> dialog."
msgstr ""
#. Tag: menuchoice
#. +> trunk5
#: index.docbook:1360
#, no-c-format
msgid "<guimenu>File</guimenu> <guimenuitem>Import from Amazon...</guimenuitem>"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1364
#, no-c-format
msgid "<action>Import from Amazon.</action> This menu item opens the same import dialog as <guimenuitem>Import...</guimenuitem>, but opens directly the <guibutton>From Amazon</guibutton> dialog."
msgstr ""
#. Tag: menuchoice
#. +> trunk5
#: index.docbook:1372
#, no-c-format
msgid "<guimenu>File</guimenu> <guimenuitem>Import from MusicBrainz Release...</guimenuitem>"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1376
#, no-c-format
msgid "<action>Import from the MusicBrainz release database.</action> This menu item opens the same import dialog as <guimenuitem>Import...</guimenuitem>, but opens directly the <guibutton>From MusicBrainz Release</guibutton> dialog."
msgstr ""
#. Tag: menuchoice
#. +> trunk5
#: index.docbook:1384
#, no-c-format
msgid "<guimenu>File</guimenu> <guimenuitem>Import from MusicBrainz Fingerprint...</guimenuitem>"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1388
#, no-c-format
msgid "<action>Import from a MusicBrainz server.</action> This menu item opens the same import dialog as <guimenuitem>Import...</guimenuitem>, but opens directly the <guibutton>From MusicBrainz Fingerprint</guibutton> dialog."
msgstr ""
#. Tag: menuchoice
#. +> trunk5
#: index.docbook:1395
#, no-c-format
msgid "<guimenu>File</guimenu> <guimenuitem>Import from Tags...</guimenuitem>"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1399
#, no-c-format
msgid "Like <link linkend=\"import-tags\">From Tags</link>, but the import is applied to the selected files."
msgid "<action>Automatic Import</action> allows one to import information for multiple albums from various web services. If folders are selected in the file list, track data for the selected folders will be imported. If no folder is selected, all folders in the file list will be imported."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1414
#, no-c-format
msgid "The tag type (Tag 1, Tag 2, Tag 1 and Tag 2) can be selected using the <guilabel>Destination</guilabel> combo box."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1418
#, no-c-format
msgid "Profiles determine which servers will be contacted to fetch album information. Some profiles are predefined (All, MusicBrainz, Discogs, Cover Art), custom profiles can be added using the <guibutton>Add</guibutton> button at the right of the <guilabel>Profile</guilabel> combo box."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1425
#, no-c-format
msgid "The table below shows the servers which will be used when importing album information using the selected profile. The import process for an album is finished if all required information has been found, so the order of the rows in the table is important. It can be changed using the <guibutton>Move Up</guibutton> and <guibutton>Move Down</guibutton> buttons. <guibutton>Edit</guibutton> can be used to change an existing entry. The <guibutton>Server</guibutton> selection offers the same servers as can be used in the import functions. <guilabel>Standard Tags</guilabel>, <guilabel>Additional Tags</guilabel>, <guilabel>Cover Art</guilabel> determine the information which shall be fetched from the server. Finally, <guilabel>Accuracy</guilabel> is the minimum accuracy which must be achieved to accept the imported data. If the accuracy is insufficient, the next server in the list will be tried. The same dialog containing the server properties appears when <guibutton>Add</guibutton> is clicked to add a new server entry. Existing entries can be deleted using <guibutton>Remove</guibutton>."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1443
#, no-c-format
msgid "To launch an automatic batch import with the selected profile, click <guibutton>Start</guibutton>. Details about the running import are displayed at the top of the dialog. The process can be aborted with the <guibutton>Abort</guibutton> button."
msgid "The <action>Browse Cover Art</action> dialog helps to find album cover art. <guilabel>Artist/Album</guilabel> is filled from the tags if possible. <guilabel>Source</guilabel> offers a variety of websites with album cover art. The &URL; with artist and album as parameters can be found beneath the name. &URL;-encoded values for artist and album can be inserted using \"<userinput>%u{artist}</userinput>\" and \"<userinput>%u{album}</userinput>\", other values from the tags are possible too, as described in <link linkend=\"configure-kid3\">Configure &kid3;</link>, <guilabel>User Actions</guilabel>. More sources can be entered after the entry \"Custom Source\" by replacing \"Custom Source\" with the source's name, pressing <keycap>Enter</keycap>, then inserting the &URL; and finally pressing <guibutton>Save Settings</guibutton>. The resulting browser command is displayed at the top of the dialog and can be started by clicking <guibutton>Browse</guibutton>. The browser, which can be configured in the settings, is started with the selected source. A cover image can then be dragged from the browser into the &kid3; window and will be set in the picture frame of the selected files."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1476
#, no-c-format
msgid "Because not all browsers support drag and drop of images and the pictures on websites often have a &URL;, in such cases &kid3; will receive the &URL; and not the picture. If the &URL; points to a picture, it will be downloaded. However, if the &URL; refers to some other web resource, it has to be translated to the corresponding picture. Such mappings are defined in the table <guilabel>&URL; extraction</guilabel>. The left column <guilabel>Match</guilabel> contains a regular expression which is compared with the &URL;. If it matches, the captured expressions in parentheses are inserted into the pattern of the right <guilabel>Picture &URL;</guilabel> column (at the positions marked with \\1 <abbrev>etc.</abbrev>). The replaced regular expression contains the &URL; of the picture. By this means cover art can be imported from Amazon, Google Images, <abbrev>etc.</abbrev> using drag and drop. It is also possible to define your own mappings."
msgid "The <action>Export Dialog</action> is used to store data from the tags in a file or the clipboard. The editor at the top shows a preview of the data to export. If the export data contain tabulator characters, the export is displayed in a table. The data will be generated from the tags in the current folder according to the configured format."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1505
#, no-c-format
msgid "The format settings are similar as in the Import dialog: The topmost field contains the title (<abbrev>e.g.</abbrev> \"CSV unquoted\"), followed by the header, which will be generated at the begin of the file. The track data follows; it is used for every track. Finally, the trailer can be used to generate some finishing text."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1512
#, no-c-format
msgid "The format fields do not contain regular expressions as in the Import dialog, but only output format expressions with special %-expressions, which will be replaced by values from the tags. The whole thing works like the file name format, and the same codes are used plus some additional codes. Not only the codes listed below but all tag frame names can be used."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1530 index.docbook:1910
#, no-c-format
msgid "%f %{file} File name"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1531
#, no-c-format
msgid "%p %{filepath} Path"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1532
#, no-c-format
msgid "%{modificationdate} Modification date"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1533
#, no-c-format
msgid "%{creationdate} Creation date"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1534
#, no-c-format
msgid "%u %{url} &URL;"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1535
#, no-c-format
msgid "%{dirname} Folder name"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1536
#, no-c-format
msgid "%d %{duration} Duration in minutes:seconds"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1537
#, no-c-format
msgid "%D %{seconds} Duration in seconds"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1538
#, no-c-format
msgid "%n %{tracks} Number of tracks of the album"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1539 index.docbook:1912
#, no-c-format
msgid "%e %{extension} File extension"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1540 index.docbook:1913
#, no-c-format
msgid "%O %{tag1} The format of tag 1 (ID3v1.1 or empty if not existing)"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1542 index.docbook:1915
#, no-c-format
msgid "%o %{tag2} The format of tag 2 (ID3v2.3.0, ID3v2.4.0, ID3v2.2.0, ID3v2.2.1, Vorbis, APE, MP4, ASF, or empty if not existing)"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1544 index.docbook:1917
#, no-c-format
msgid "%b %{bitrate} Bit rate in kbit/s"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1545 index.docbook:1918
#, no-c-format
msgid "%v %{vbr} VBR or empty (only for ID3v2.3 with id3lib)"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1547 index.docbook:1920
#, no-c-format
msgid "%r %{samplerate} Sample rate in Hz"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1548 index.docbook:1921
#, no-c-format
msgid "%m %{mode} Channel mode (Stereo or Joint Stereo)"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1549 index.docbook:1922
#, no-c-format
msgid "%h %{channels} Number of channels (1 or 2)"
msgid "A few formats are predefined. \"CSV unquoted\" separates the fields by tabs. Data in this format can be imported again into &kid3; using the import format with the same name. \"CSV quoted\" additionally encloses the fields by double quotes, which eases the import into spreadsheet applications. However, the fields shall not contain any double quotes when this format is used. \"Extended M3U\" and \"Extended PLS\" generate playlists with extended attributes and absolute path names. \"HTML\" can be used to generate an &HTML; page with hyperlinks to the tracks. \"Kover &XML;\" creates a file which can be imported by the cover printing program Kover. \"Technical Details\" provides information about bit rate, sample rate, channels, <abbrev>etc.</abbrev> Finally, \"Custom Format\" is left empty for definition of a custom format. You can define more formats of your own by adding lines in the file <filename>kid3rc</filename> in the configuration folder. The other formats can be adapted to your needs."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1569
#, no-c-format
msgid "The <guilabel>Source</guilabel> of the tags to generate the export data (<guilabel>Tag 1</guilabel> or <guilabel>Tag 2</guilabel>) can be selected with a combo box. Pushing <guibutton>To File</guibutton> or <guibutton>To Clipboard</guibutton> stores the data in a file or on the clipboard. <guibutton>OK</guibutton> and <guibutton>Cancel</guibutton> close the dialog, whereas <guibutton>OK</guibutton> accepts the current dialog settings."
msgid "<action>Creates a playlist.</action> The format and contents of the playlist can be set by various options."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1587
#, no-c-format
msgid "The name of the playlist can be the <guibutton>Same as folder name</guibutton> or use a <guibutton>Format</guibutton> with values from the tags, <abbrev>e.g.</abbrev> \"<userinput>%{artist} - %{album}</userinput>\" to have the artist and album name in the playlist file name. The format codes are the same as for <link linkend=\"export\">Export</link>. <guibutton>Create new empty playlist</guibutton> will make an empty playlist with the given name. The extension depends on the playlist format."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1597
#, no-c-format
msgid "The location of the generated playlist is determined by the selection of the <guilabel>Create in</guilabel> combo box."
msgstr ""
#. Tag: term
#. +> trunk5
#: index.docbook:1601
#, no-c-format
msgid "Current folder"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1602
#, no-c-format
msgid "The playlist is created in the current folder and contains only files of the current folder. The current folder is the folder where the current file is located. If multiple files are selected, the current file is probably the last selected file."
msgstr ""
#. Tag: term
#. +> trunk5
#: index.docbook:1606
#, no-c-format
msgid "Every folder"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1607
#, no-c-format
msgid "A playlist is created in every folder which contains listed files, and each playlist contains the files of that folder."
msgstr ""
#. Tag: term
#. +> trunk5
#: index.docbook:1610
#, no-c-format
msgid "Top-level folder"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1611
#, no-c-format
msgid "Only one playlist is created in the top-level folder (<abbrev>i.e.</abbrev> the folder of the file list) and it contains the listed files of the top-level folder and all of its sub-folders."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1617
#, no-c-format
msgid "The <guilabel>Format</guilabel> of the playlist can be <guilabel>M3U</guilabel>, <guilabel>PLS</guilabel> or <guilabel>XSPF</guilabel>."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1622
#, no-c-format
msgid "If <guibutton>Include only the selected files</guibutton> is checked, only the selected files will be included in the playlist. If a folder is selected, all of its files are selected. If this check box is not activated, all audio files are included in the playlist."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1628
#, no-c-format
msgid "<guibutton>Sort by file name</guibutton> selects the usual case where the files are ordered by file name. With <guibutton>Sort by tag field</guibutton>, it is possible to sort by a format string with values from tag fields. For instance, \"<userinput>%{track.3}</userinput>\" can be used to sort by track number (the \"<userinput>.3</userinput>\" is used to get three digits with leading zeros because strings are used for sorting). It is also possible to use multiple fields, <abbrev>e.g.</abbrev> \"<userinput>%{genre}%{year}</userinput>\" to sort using a string composed of genre and year."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1638
#, no-c-format
msgid "The playlist entries will have relative or absolute file paths depending on whether <guibutton>Use relative path for files in playlist</guibutton> or <guibutton>Use full path for files in playlist</guibutton> is set."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1643
#, no-c-format
msgid "When <guibutton>Write only list of files</guibutton> is set, the playlist will only contain the paths to the files. To generate an extended playlist with additional information, a format string can be set using the <guibutton>Write info using</guibutton> control."
msgid "Find strings in the file names and the tags. The <guilabel>Find</guilabel> dialog is a subset of the <guilabel>Replace</guilabel> dialog, which is described below."
msgid "This function opens a dialog to find and replace strings in the file names and the tags. The set of frames where the search is performed can be restricted by deactivating the <guilabel>Select all</guilabel> check box and selecting the frames which shall be searched. There are also search options available to search backwards, case sensitively, and to use regular expressions."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1753
#, no-c-format
msgid "Depending on the number of files, the search might take some time, therefore it can be aborted by closing the dialog."
msgid "When <guilabel>Automatically apply format</guilabel> is switched off for the filename format in the configuration dialog, this menu item can be used to <action>apply the configured format to the names of the selected files</action>. This can also be used to check whether the file names conform with the configured format by applying the format to all saved files and then checking if any files were changed (and therefore marked with a disk symbol in the file listbox)."
msgstr ""
#. Tag: menuchoice
#. +> trunk5
#: index.docbook:1781
#, no-c-format
msgid "<guimenu>Tools</guimenu> <guimenuitem>Apply Tag Format</guimenuitem>"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1785
#, no-c-format
msgid "When <guilabel>Automatically apply format</guilabel> is switched off for the tag format in the configuration dialog, this menu item can be used to <action>apply the configured format to the tags of the selected files</action>. This can also be used to check whether the tags conform with the configured format by applying the format to all saved files and then checking if any files were changed (and therefore marked with a disk symbol in the file listbox)."
msgstr ""
#. Tag: menuchoice
#. +> trunk5
#: index.docbook:1795
#, no-c-format
msgid "<guimenu>Tools</guimenu> <guimenuitem>Apply Text Encoding</guimenuitem>"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1799
#, no-c-format
msgid "Sets the <guilabel>Text encoding</guilabel> selected in <menuchoice><guimenu>Settings</guimenu><guimenuitem>Configure &kid3;... </guimenuitem><guimenuitem>Tags section</guimenuitem><guimenuitem>Tag 2 tab</guimenuitem></menuchoice> for all selected files. If UTF8 is selected, UTF16 will be used for ID3v2.3.0 tags because UTF8 is not supported for this format."
msgid "This dialog offers the possibility to automatically rename the currently open folder according to the tags in the files. Several formats are preconfigured to include information about artist, album and year in the folder name. It is also possible to set a custom format and <guibutton>Edit</guibutton> the list of available formats. The following special codes are used to insert tag values into the folder name:"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1830
#, no-c-format
msgid "%{dirname} Folder name (<abbrev>e.g.</abbrev> %{year\" \"}%{dirname} will prepend the year to the current folder name)"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1832
#, no-c-format
msgid "%{max-year} The maximum year value found for this folder, can also be used with other codes than \"year\""
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1834
#, no-c-format
msgid "%{min-year} The minimum year value found for this folder"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1836
#, no-c-format
msgid "%{unq-year} The unique year value found for this folder or empty if not unique"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1840
#, no-c-format
msgid "If a folder separator \"/\" is found in the format, multiple folders are created. If you want to create a new folder instead of renaming the current folder, in the <guilabel>Action</guilabel> combo box select <guilabel>Create Folder</guilabel> instead of <guilabel>Rename Folder</guilabel>. The <guilabel>Source</guilabel> of the tag information can be chosen between <guilabel>Tag 1 and Tag 2</guilabel>, <guilabel>Tag 1</guilabel> and <guilabel>Tag 2</guilabel>. A preview for the rename operation performed on the first file can be seen in the <guilabel>From</guilabel> and <guilabel>To</guilabel> sections of the dialog."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1851
#, no-c-format
msgid "Multiple folders can be renamed by selecting them."
msgid "If the track numbers in the tags are not set or have the wrong values, this function can <action>number the tracks automatically in ascending order</action>. The start number can be set in the dialog. If only part of the tracks have to be numbered, they must be selected."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1866
#, no-c-format
msgid "When <guilabel>Total number of tracks</guilabel> is checked, the number of tracks will also be set in the tags."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1869
#, no-c-format
msgid "It is possible to number the tracks over multiple folders. The folders have to be expanded and selected."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1872
#, no-c-format
msgid "If <guilabel>Reset counter for each folder</guilabel> is checked, track numbering is restarted with the given number for each folder when multiple folders are selected."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1876
#, no-c-format
msgid "The number tracks dialog can also be used to format existing track numbers without changing the values when the check box left to <guilabel>Start number</guilabel> is deactivated. The total number of tracks will be added if the corresponding check box is active, which can be used to set the total for all selected tracks. If only formatting of the existing numbers is desired, this check box has to be deactivated too."
msgid "The filter can be used to display only those files which match certain criteria. This is helpful if you want to organize a large collection and only edit those files which are not in the desired scheme. The expression defining which files to display uses the same format codes which are used in the file name format, import and export."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1911
#, no-c-format
msgid "%p %{filepath} Absolute path to file"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1925
#, no-c-format
msgid "%w %{marked} Marked, is 1 if the file is marked (<abbrev>e.g.</abbrev> because of truncation or standard violation), empty otherwise"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1927
#, no-c-format
msgid "%1a %1{artist}, ... Use the prefix 1 to get values of tag 1"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1928
#, no-c-format
msgid "%2a %2{artist}, ... Use the prefix 2 to get values of tag 2"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1931
#, no-c-format
msgid "These codes are replaced with the values for the file, and the resulting strings can be compared with the following operations:"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1937
#, no-c-format
msgid "s1 equals s2: true if s1 and s2 are equal."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1938
#, no-c-format
msgid "s1 contains s2: true if s1 contains s2, <abbrev>i.e.</abbrev> s2 is a substring of s1."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1940
#, no-c-format
msgid "s matches re: true if s matches the regular expression re."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1942
#, no-c-format
msgid "True expressions are replaced by 1, false by 0. True values are represented by 1, true, on and yes, false values by 0, false, off and no. Boolean operations are not, and, or (in this order of precedence) and can be grouped by parentheses."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1947
#, no-c-format
msgid "Some filter rules are predefined and can serve as examples for your own expressions:"
msgstr ""
#. Tag: term
#. +> trunk5
#: index.docbook:1953
#, no-c-format
msgid "<term>All</term>"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1954
#, no-c-format
msgid "When the file list is filtered - this is shown by \"[filtered]\" in the window title - and all files shall be displayed again, the filtering can be reverted using this filter. It uses an empty expression, but a true value would have the same effect."
msgid "Tests if the file path conforms with the file name format. This rule is automatically adapted if the file name format changes."
msgstr ""
#. Tag: term
#. +> trunk5
#: index.docbook:1972
#, no-c-format
msgid "No Tag 1"
msgstr ""
#. Tag: userinput
#. +> trunk5
#: index.docbook:1973
#, no-c-format
msgid "%{tag1} equals \"\""
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1976
#, no-c-format
msgid "Displays only files which do not have a tag 1."
msgstr ""
#. Tag: term
#. +> trunk5
#: index.docbook:1979
#, no-c-format
msgid "No Tag 2"
msgstr ""
#. Tag: userinput
#. +> trunk5
#: index.docbook:1980
#, no-c-format
msgid "%{tag2} equals \"\""
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1983
#, no-c-format
msgid "Displays only files which do not have a tag 2."
msgstr ""
#. Tag: term
#. +> trunk5
#: index.docbook:1986
#, no-c-format
msgid "ID3v2.3.0 Tag"
msgstr ""
#. Tag: userinput
#. +> trunk5
#: index.docbook:1987
#, no-c-format
msgid "%{tag2} equals \"ID3v2.3.0\""
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1990
#, no-c-format
msgid "Displays only files which have an ID3v2.3.0 tag."
msgstr ""
#. Tag: term
#. +> trunk5
#: index.docbook:1993
#, no-c-format
msgid "ID3v2.4.0 Tag"
msgstr ""
#. Tag: userinput
#. +> trunk5
#: index.docbook:1994
#, no-c-format
msgid "%{tag2} equals \"ID3v2.4.0\""
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:1997
#, no-c-format
msgid "Displays only files which have an ID3v2.4.0 tag."
msgstr ""
#. Tag: term
#. +> trunk5
#: index.docbook:2000
#, no-c-format
msgid "Tag 1 != Tag 2"
msgstr ""
#. Tag: userinput
#. +> trunk5
#: index.docbook:2001
#, no-c-format
msgid "not (%1{title} equals %2{title} and %1{album} equals %2{album} and %1{artist} equals %2{artist} and %1{comment} equals %2{comment} and %1{year} equals %2{year} and %1{track} equals %2{track} and %1{genre} equals %2{genre})"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2006
#, no-c-format
msgid "Displays files with differences between tag 1 and tag2."
msgstr ""
#. Tag: term
#. +> trunk5
#: index.docbook:2009
#, no-c-format
msgid "Tag 1 == Tag 2"
msgstr ""
#. Tag: userinput
#. +> trunk5
#: index.docbook:2010
#, no-c-format
msgid "%1{title} equals %2{title} and %1{album} equals %2{album} and %1{artist} equals %2{artist} and %1{comment} equals %2{comment} and %1{year} equals %2{year} and %1{track} equals %2{track} and %1{genre} equals %2{genre}"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2015
#, no-c-format
msgid "Displays files with identical tag 1 and tag 2."
msgstr ""
#. Tag: term
#. +> trunk5
#: index.docbook:2018
#, no-c-format
msgid "Incomplete"
msgstr ""
#. Tag: userinput
#. +> trunk5
#: index.docbook:2019
#, no-c-format
msgid "%{title} equals \"\" or %{artist} equals \"\" or %{album} equals \"\" or %{year} equals \"\" or %{tracknumber} equals \"\" or %{genre} equals \"\""
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2022
#, no-c-format
msgid "Displays files with empty values in the standard tags (title, artist, album, date, track number, genre)."
msgstr ""
#. Tag: term
#. +> trunk5
#: index.docbook:2026
#, no-c-format
msgid "No Picture"
msgstr ""
#. Tag: userinput
#. +> trunk5
#: index.docbook:2027
#, no-c-format
msgid "%{picture} equals \"\""
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2030
#, no-c-format
msgid "Displays only files which do not have a picture."
msgstr ""
#. Tag: term
#. +> trunk5
#: index.docbook:2033
#, no-c-format
msgid "Marked"
msgstr ""
#. Tag: userinput
#. +> trunk5
#: index.docbook:2034
#, no-c-format
msgid "not (%{marked} equals \"\")"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2037
#, no-c-format
msgid "Displays only files which are marked because they violate the ID3 standard, are truncated or the picture is too large."
msgstr ""
#. Tag: term
#. +> trunk5
#: index.docbook:2041
#, no-c-format
msgid "Custom Filter"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2042
#, no-c-format
msgid "To add your own filter, select this entry. For instance, if you want to have a filter for artists starting with \"The\", replace \"Custom Filter\" with the name \"The Bands\" and press <keycap>Enter</keycap>. Then insert the following expression into the line edit:"
msgstr ""
#. Tag: userinput
#. +> trunk5
#: index.docbook:2048
#, no-c-format
msgid "%{artist} matches \"The.*\""
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2051
#, no-c-format
msgid "Then click <guibutton>Save Settings</guibutton>. Click <guibutton>Apply</guibutton> to filter the files. All files processed are displayed in the text view, with a \"+\" for those who match the filter and a \"-\" for the others. When finished, only the files with an artist starting with \"The\" are displayed, and the window title is marked with \"[filtered]\"."
msgstr ""
#. Tag: menuchoice
#. +> trunk5
#: index.docbook:2066
#, no-c-format
msgid "<guimenu>Tools</guimenu> <guimenuitem>Convert ID3v2.3 to ID3v2.4</guimenuitem>"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2070
#, no-c-format
msgid "If there are any ID3v2.3 tags in the selected files, they will be <action>converted to ID3v2.4</action> tags. Frames which are not supported by TagLib will be discarded. Only files without unsaved changes will be converted."
msgstr ""
#. Tag: menuchoice
#. +> trunk5
#: index.docbook:2078
#, no-c-format
msgid "<guimenu>Tools</guimenu> <guimenuitem>Convert ID3v2.4 to ID3v2.3</guimenuitem>"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2082
#, no-c-format
msgid "If there are any ID3v2.4 tags in the selected files, they will be <action>converted to ID3v2.3</action> tags. Only files without unsaved changes will be converted."
msgid "This opens a simple toolbar to play audio files. It contains buttons for the basic operations (<guibutton>Play/Pause</guibutton>, <guibutton>Stop playback</guibutton>, <guibutton>Previous Track</guibutton>, <guibutton>Next Track</guibutton>, <guibutton>Close</guibutton>), sliders for position and volume and a display of the current position. If multiple files are selected, the selected tracks are played, else all files will be played."
msgid "Empty tags are automatically hidden if this option is active. The <guilabel>File</guilabel>, <guilabel>Tag 1</guilabel> and <guilabel>Tag 2</guilabel> sections can be manually collapsed and expanded by clicking on the corresponding <guibutton>-</guibutton>/<guibutton>+</guibutton> buttons."
msgid "Opens a dialog to assign keyboard shortcuts for most of the program functions. There are even functions without corresponding menu or button available, <abbrev>e.g.</abbrev> next file, previous file, select all."
msgid "Opens the <action>configuration dialog</action>, which consists of pages for tags, files, user actions, and network settings."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2177
#, no-c-format
msgid "Tag specific options can be found on the <guilabel>Tags</guilabel> page, which is itself separated into four tabs for <guilabel>Tag 1</guilabel>, <guilabel>Tag 2</guilabel>, <guilabel>Tag 3</guilabel>, and <guilabel>All Tags</guilabel>."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2183
#, no-c-format
msgid "If <guilabel>Mark truncated fields</guilabel> is checked, truncated ID3v1.1 fields will be marked red. The text fields of ID3v1.1 tags can only have 30 characters, the comment only 28 characters. Also the genre and track numbers are restricted, so that fields can be truncated when imported or transferred from ID3v2. Truncated fields and the file will be marked red, and the mark will be removed after the field has been edited."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2191
#, no-c-format
msgid "With <guilabel>Text encoding</guilabel> for <guilabel>ID3v1</guilabel> it is possible to set the character set used in ID3v1 tags. This encoding is supposed to be ISO-8859-1, so it is recommended to keep this default value. However, there are tags around with different encoding, so it can be set here and the ID3v1 tags can then be copied to ID3v2 which supports Unicode."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2198
#, no-c-format
msgid "The check box <guilabel>Use track/total number of tracks format</guilabel> controls whether the track number field of ID3v2 tags contains simply the track number or additionally the total number of tracks in the folder."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2204
#, no-c-format
msgid "When <guilabel>Genre as text instead of numeric string</guilabel> is checked, all ID3v2 genres will be stored as a text string even if there is a corresponding code for ID3v1 genres. If this option is not set, genres for which an ID3v1 code exists are stored as the number of the genre code (in parentheses for ID3v2.3). Thus the genre Metal is stored as \"Metal\" or \"(9)\" depending on this option. Genres which are not in the list of ID3v1 genres are always stored as a text string. The purpose of this option is improved compatibility with devices which do not correctly interpret genre codes."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2214
#, no-c-format
msgid "When <guilabel>WAV files with lowercase id3 chunk</guilabel> is checked, the RIFF chunk used to store ID3v2 tags in WAV files will be named \"id3 \" instead of \"ID3 \". By default, &kid3; and other applications using TagLib accept both the lowercase and the uppercase variant when reading WAV files, but they use \"ID3 \" when writing ID3v2 tags to WAV files. As there exist other applications which only accept \"id3 \" (<abbrev>e.g.</abbrev> JRiver Media Center and foobar2000), this option can be used to create tags which can be read by such applications."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2223
#, no-c-format
msgid "When <guilabel>Mark standard violations</guilabel> is checked, ID3v2 fields which violate the standard will be marked red. Details about the violation are shown in a tooltip:"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2229
#, no-c-format
msgid "Must be unique"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2230
#, no-c-format
msgid "New line is forbidden"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2231
#, no-c-format
msgid "Carriage return is forbidden"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2232
#, no-c-format
msgid "Owner must be non-empty"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2233
#, no-c-format
msgid "Must be numeric"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2234
#, no-c-format
msgid "Must be numeric or number/total"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2235
#, no-c-format
msgid "Format is DDMM"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2236
#, no-c-format
msgid "Format is HHMM"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2237
#, no-c-format
msgid "Format is YYYY"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2238
#, no-c-format
msgid "Must begin with a year and a space character"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2239
#, no-c-format
msgid "Must be ISO 8601 date/time"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2240
#, no-c-format
msgid "Must be musical key, 3 characters, A-G, b, #, m, o"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2241
#, no-c-format
msgid "Must have ISO 639-2 language code, 3 lowercase characters"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2242
#, no-c-format
msgid "Must be ISRC code, 12 characters"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2243
#, no-c-format
msgid "Must be list of strings separated by '|'"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2244
#, no-c-format
msgid "Has excess white space"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2246
#, no-c-format
msgid "The ID3 standard documents are available online:"
msgstr ""
#. Tag: ulink
#. +> trunk5
#: index.docbook:2250
#, no-c-format
msgid "ID3 tag version 2.3.0"
msgstr ""
#. Tag: ulink
#. +> trunk5
#: index.docbook:2251
#, no-c-format
msgid "ID3 tag version 2.4.0 - Main Structure"
msgstr ""
#. Tag: ulink
#. +> trunk5
#: index.docbook:2252
#, no-c-format
msgid "ID3 tag version 2.4.0 - Native Frames"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2254
#, no-c-format
msgid "<guilabel>Text encoding</guilabel> defines the default encoding used for ID3v2 frames and can be set to <guilabel>ISO-8859-1</guilabel>, <guilabel>UTF16</guilabel>, or <guilabel>UTF8</guilabel>. <guilabel>UTF8</guilabel> is not valid for ID3v2.3.0 frames; if it is set, <guilabel>UTF16</guilabel> will be used instead. For ID3v2.4.0 frames, all three encodings are possible."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2262
#, no-c-format
msgid "<guilabel>Version used for new tags</guilabel> determines whether new ID3v2 tags are created as version 2.3.0 or 2.4.0."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2266
#, no-c-format
msgid "<guilabel>Track number digits</guilabel> is the number of digits in Track Number fields. Leading zeros are used to pad. For instance, with a value of 2 the track number 5 is set as \"05\"."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2271
#, no-c-format
msgid "The combo box <guilabel>Comment field name</guilabel> is only relevant for Ogg/Vorbis and FLAC files and sets the name of the field used for comments. Different applications seem to use different names, \"<literal>COMMENT</literal>\" for instance is used by <application>XMMS</application>, whereas &amarok; uses \"<literal>DESCRIPTION</literal>\"."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2278
#, no-c-format
msgid "The format of pictures in Ogg/Vorbis files is determined by <guilabel>Picture field name</guilabel>, which can be \"<literal>METADATA_BLOCK_PICTURE</literal>\" or \"<literal>COVERART</literal>\". The first is the official standard and uses the same format as pictures in FLAC tags. \"<literal>COVERART</literal>\" is an earlier unofficial way to include pictures in Vorbis comments. It can be used for compatibility with legacy players."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2286
#, no-c-format
msgid "If the <guilabel>Mark if larger than (bytes)</guilabel> check box is activated, files containing embedded album cover art exceeding the given size in bytes are marked red. This can be used to find files containing oversized pictures which are not accepted by some applications and players. The default value is 131072 bytes (128 KB)."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2293
#, no-c-format
msgid "<guilabel>Custom Genres</guilabel> can be used to define genres which are not available in the standard genre list, <abbrev>e.g.</abbrev> \"Gothic Metal\". Such custom genres will appear in the <guilabel>Genre</guilabel> combo box of <guilabel>Tag 2</guilabel>. For ID3v1.1 tags, only the predefined genres can be used."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2300
#, no-c-format
msgid "The list of custom genres can also be used to reduce the number of genres available in the <guilabel>Genre</guilabel> combo box to those typically used. If your collection mostly contains music in the genres Metal, Gothic Metal, Ancient and Hard Rock, you can enter those genres and mark <guilabel>Show only custom genres</guilabel>. The <guilabel>Tag 2</guilabel> <guilabel>Genre</guilabel> combo box will then only contain those four genres and you will not have to search through the complete genres list for them. In this example, only Metal and Hard Rock will be listed in the tag 1 genres list, because those two custom genres entries are standard genres. If <guilabel>Show only custom genres</guilabel> is not active, the custom genres can be found at the end of the genres list."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2313
#, no-c-format
msgid "<guilabel>Quick Access Frames</guilabel> defines which frame types are always shown in the <link linkend=\"tag2\">Tag 2</link> section. Such frames can then be added without first using the <guibutton>Add</guibutton> button. The order of these quick access frames can be changed by dragging and dropping items."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2320
#, no-c-format
msgid "The combo box <guilabel>Track number field name</guilabel> is only relevant for RIFF INFO and sets the name of the field used for track numbers. Track numbers are not specified in the original RIFF standard, there are applications which use \"<literal>ITRK</literal>\", others use \"<literal>IPRT</literal>\"."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2327
#, no-c-format
msgid "<guilabel>Tag Format</guilabel> contains options for the format of the tags. When <guilabel>Automatically apply format</guilabel> is checked, the format configuration is automatically used while editing text in the line edits. <guilabel>Validation</guilabel> enables validators in the controls with track/total and date/time values. The <guilabel>Case conversion</guilabel> can be set to <guilabel>No changes</guilabel>, <guilabel>All lowercase</guilabel>, <guilabel>All uppercase</guilabel>, <guilabel>First letter uppercase</guilabel> or <guilabel>All first letters uppercase</guilabel>. To use locale-aware conversion between lowercase and uppercase characters, a locale can be selected in the combobox below. The string replacement list can be set to arbitrary string mappings. To add a new mapping, select the <guilabel>From</guilabel> cell of a row and insert the text to replace, then go to the <guilabel>To</guilabel> column and enter the replacement text. When the text to replace starts and ends with a slash (\"/\"), a regular expression is used. For regular expressions containing capturing groups, occurrences of \\1, \\2, ... in <guilabel>To</guilabel> are replaced with the string captured by the corresponding capturing group. To remove a mapping set the <guilabel>From</guilabel> cell to an empty value (<abbrev>e.g.</abbrev> by first typing space and then backspace). Inserting and deleting rows is also possible using a context menu which appears when the <mousebutton>right</mousebutton> mouse button is clicked. Replacement is only active, if the <guilabel>String replacement</guilabel> check box is checked."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2353
#, no-c-format
msgid "The table in <guilabel>Rating</guilabel> contains the mapping of star ratings to the effective values stored in the tag. The frames with rating information are listed in the Rating row of the <link linkend=\"table-frame-list\">frame list</link>. For these frames, the rating can be set by giving a number of stars out of five stars. Different tag formats and different applications use different values to map the star rating to the value stored in the tag. In order to display the correct number of stars, &kid3; will look up a map in this table. The key to look up the mapping is the frame name, for example \"RATING\" as used for Vorbis comments or \"IRTD\" for RIFF INFO. For ID3v2 tags, a combined key is used consisting of the frame ID \"POPM\" of the Popularimeter frame and its \"Email\" field, separated by a dot. Therefore, different keys for ID3v2 exist, <abbrev>e.g.</abbrev> \"POPM.Windows Media Player 9 Series\" for the mapping used by Windows Media Player and Explorer, and simply \"POPM\" for POPM frames with an empty \"Email\" field. As multiple entries for \"POPM\" can exist, their order is important. When &kid3; adds a new Popularimeter frame, it will use the first \"POPM\" entry to determine the value to be written into the \"Email\" field. This value will then specify the mapping to be used for star ratings. The first entry is also used if no key was found, it is therefore the default entry."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2374
#, no-c-format
msgid "Besides the <guilabel>Name</guilabel> column containing the keys, the table has columns <guilabel>1</guilabel> to <guilabel>5</guilabel> for the values to be stored when the corresponding number of stars is given. The other way round, the values determine the number of stars which are displayed for the value stored in the frame. For instance, the row in the table below contains the values 1, 64, 128, 196, 255. The thresholds for the number of stars to be displayed lay between these values and are compatible with what the &Windows; Explorer uses."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:2386
#, no-c-format
msgid "Entry in Rating Table"
msgstr ""
#. Tag: entry
#. +> trunk5
#: index.docbook:2389
#, no-c-format
msgid "Name"
msgstr ""
#. Tag: entry
#. +> trunk5
#: index.docbook:2389 index.docbook:2392
#, no-c-format
msgid "<entry>1</entry>"
msgstr ""
#. Tag: entry
#. +> trunk5
#: index.docbook:2389
#, no-c-format
msgid "<entry>2</entry>"
msgstr ""
#. Tag: entry
#. +> trunk5
#: index.docbook:2389
#, no-c-format
msgid "<entry>3</entry>"
msgstr ""
#. Tag: entry
#. +> trunk5
#: index.docbook:2389
#, no-c-format
msgid "<entry>4</entry>"
msgstr ""
#. Tag: entry
#. +> trunk5
#: index.docbook:2389
#, no-c-format
msgid "<entry>5</entry>"
msgstr ""
#. Tag: entry
#. +> trunk5
#: index.docbook:2392
#, no-c-format
msgid "<entry>POPM</entry>"
msgstr ""
#. Tag: entry
#. +> trunk5
#: index.docbook:2392
#, no-c-format
msgid "<entry>64</entry>"
msgstr ""
#. Tag: entry
#. +> trunk5
#: index.docbook:2392
#, no-c-format
msgid "<entry>128</entry>"
msgstr ""
#. Tag: entry
#. +> trunk5
#: index.docbook:2392
#, no-c-format
msgid "<entry>196</entry>"
msgstr ""
#. Tag: entry
#. +> trunk5
#: index.docbook:2392
#, no-c-format
msgid "<entry>255</entry>"
msgstr ""
#. Tag: entry
#. +> trunk5
#: index.docbook:2393
#, no-c-format
msgid "Range"
msgstr ""
#. Tag: entry
#. +> trunk5
#: index.docbook:2393
#, no-c-format
msgid "1-31"
msgstr ""
#. Tag: entry
#. +> trunk5
#: index.docbook:2393
#, no-c-format
msgid "32-95"
msgstr ""
#. Tag: entry
#. +> trunk5
#: index.docbook:2393
#, no-c-format
msgid "96-159"
msgstr ""
#. Tag: entry
#. +> trunk5
#: index.docbook:2393
#, no-c-format
msgid "160-223"
msgstr ""
#. Tag: entry
#. +> trunk5
#: index.docbook:2393
#, no-c-format
msgid "224-255"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2398
#, no-c-format
msgid "On the page <guilabel>Files</guilabel> the check box <guilabel>Load last-opened files</guilabel> can be marked so that &kid3; will open and select the last selected file when it is started the next time. <guilabel>Preserve file timestamp</guilabel> can be checked to preserve the file modification time stamp. <guilabel>Filename for cover</guilabel> sets the name which is suggested when an embedded image is exported to a file. With <guilabel>Text encoding (Export, Playlist)</guilabel> the encoding used when writing files can be set. The default <guilabel>System</guilabel> can be changed for example if playlists have to be used on a different device."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2410
#, no-c-format
msgid "If <guilabel>Mark changes</guilabel> is active, changed fields are marked with a light gray label background."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2414
#, no-c-format
msgid "The section <guilabel>File List</guilabel> determines which files are displayed in the file list. A <guilabel>Filter</guilabel> can be used to restrict the items in this list to files with supported extensions. To explicitly specify which folders to display in the file list or exclude certain folders, the options <guilabel>Include folders</guilabel> and <guilabel>Exclude folders</guilabel> can be used. They can contain wildcard expressions, for instance <filename>*/Music/*</filename> to include only the <filename>Music</filename> folder, or <filename>*/iTunes/*</filename> to exclude the iTunes folder from the file list. If multiple such expressions have to be used, they can be separated by spaces or semicolons."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2426
#, no-c-format
msgid "The buttons <guibutton>Filename from tag</guibutton> and <guibutton>Tag from filename</guibutton> in section <guilabel>Format</guilabel> open dialogs to edit the formats which are available in the <guilabel>Format</guilabel> combo boxes (with arrows up and down), which can be found in the <link linkend=\"file\">File</link> section of the main window."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2433
#, no-c-format
msgid "<guilabel>Filename Format</guilabel> contains options for the format of the filenames. The same options as in <guilabel>Tag Format</guilabel> are available."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2437
#, no-c-format
msgid "The <guilabel>User Actions</guilabel> page contains a table with the commands which are available in the context menu of the file list. For critical operations such as deleting files, it is advisable to mark <guilabel>Confirm</guilabel> to pop up a confirmation dialog before executing the command. <guilabel>Output</guilabel> can be marked to see the output written by console commands (standard output and standard error). <guilabel>Name</guilabel> is the name displayed in the context menu. <guilabel>Command</guilabel> is the command line to be executed. Arguments can be passed using the following codes:"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2451
#, no-c-format
msgid "%F %{files} File paths (a list if multiple files selected)"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2452
#, no-c-format
msgid "%f %{file} File path to single file"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2453
#, no-c-format
msgid "%uF %{urls} &URL;s (a list if multiple files selected)"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2454
#, no-c-format
msgid "%uf %{url} &URL; to single file"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2455
#, no-c-format
msgid "%d %{directory} Folder"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2465
#, no-c-format
msgid "%b %{browser} Command to start the web browser"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2466
#, no-c-format
msgid "%q %{qmlpath} Base folder of provided QML files"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2469
#, no-c-format
msgid "The special code <command>@separator</command> can be set as a command to insert a separator into the user actions context menu. Menu items can be put into a submenu by enclosing them with <command>@beginmenu</command> and <command>@endmenu</command> commands. The name of the submenu is determined by the <guilabel>Name</guilabel> column of the <command>@beginmenu</command> command."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2478
#, no-c-format
msgid "To execute QML scripts, <command>@qml</command> is used as a command name. The path to the QML script is passed as a parameter. The provided scripts can be found in the folder <filename>%{qmlpath}/script/</filename> (on &Linux; typically <filename>/usr/share/kid3/qml/script/</filename>, on Windows <filename>qml/script/</filename> inside the installation folder, and on &macOS; in the app folder <filename>kid3.app/Contents/Resources/qml/script/</filename>). Custom scripts can be stored in any folder. If the QML code uses &GUI; components, <command>@qmlview</command> shall be used instead of <command>@qml</command>. Additional parameters are passed to the QML script where they will be available via the <function>getArguments()</function> function. An overview of some functions and properties which are available in QML can be found in the appendix <link linkend=\"qml-interface\">QML Interface</link>."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2494
#, no-c-format
msgid ""
"The command which will be inserted with %{browser} can be defined in the <guilabel>Web browser</guilabel> line edit above. Commands starting with %{browser} can be used to fetch information about the audio files from the web, for instance <screen width=\"40\">\n"
"</screen> will query the lyrics for the current song in <ulink url=\"http://www.lyricwiki.org\">LyricWiki</ulink>. The \"u\" in %u{artist} and %u{title} is used to &URL;-encode the artist %{artist} and song %{title} information. It is easy to define your own queries in the same way, <abbrev>e.g.</abbrev> an image search with <ulink url=\"http://www.google.com\">Google</ulink>:"
msgid "To add album cover art to tag 2, you can search for images with Google or Amazon using the commands described above. The picture can be added to the tag with drag and drop. You can also add an image with <guibutton>Add</guibutton>, then select the Picture frame and import an image file or paste from the clipboard. Picture frames are supported for ID3v2, MP4, FLAC, Ogg and ASF tags."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2514
#, no-c-format
msgid "To add and delete entries in the table, a context menu can be used."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2518
#, no-c-format
msgid "The <guilabel>Network</guilabel> page contains only a field to insert the proxy address and optionally the port, separated by a colon. The proxy will be used when importing from an Internet server when the check box is checked."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2523
#, no-c-format
msgid "In the <guilabel>Plugins</guilabel> page, available plugins can be enabled or disabled. The plugins are separated into two sections. The <guilabel>Metadata Plugins & Priority</guilabel> list contains plugins which support audio file formats. The order of the plugins is important because they are tried from top to bottom. Some formats are supported by multiple plugins, so files will be opened with the first plugin supporting them. The <guilabel>TaglibMetadata</guilabel> supports most formats, if it is at the top of the list, it will open most of the files. If you want to use a different plugin for a file format, make sure that it is listed before the <guilabel>TaglibMetadata</guilabel> plugin. Details about the metadata plugin and why you may want to use them instead of TagLib are listed below."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2537
#, no-c-format
msgid "<guilabel>Id3libMetadata</guilabel>: Uses <ulink url=\"http://id3lib.sourceforge.net\">id3lib</ulink> for ID3v1.1 and ID3v2.3 tags in MP3, MP2, AAC files. Supports a few more frame types than TagLib."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2541
#, no-c-format
msgid "<guilabel>OggFlacMetadata</guilabel>: Uses <ulink url=\"http://xiph.org/ogg/\">libogg</ulink>, <ulink url=\"http://xiph.org/vorbis/\">libvorbis, libvorbisfile</ulink> for Ogg files, and additionally <ulink url=\"http://flac.sourceforge.net\">libFLAC++ and libFLAC</ulink> for FLAC files. These are the official libraries for these formats."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2547
#, no-c-format
msgid "<guilabel>TaglibMetadata</guilabel>: Uses <ulink url=\"http://taglib.github.io/\">TagLib</ulink> which supports a lot of audio file formats. It can be used for all audio files supported by &kid3;."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2551
#, no-c-format
msgid "<guilabel>Mp4v2Metadata</guilabel>: <ulink url=\"http://code.google.com/p/mp4v2\">mp4v2</ulink> was originally used by &kid3; to support M4A files. Can be used in case of problems with the M4A support of TagLib."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2557
#, no-c-format
msgid "The <guilabel>Available Plugins</guilabel> section lists the remaining plugins. Their order is not important, but they can be enabled or disabled using the check boxes."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2563
#, no-c-format
msgid "<guilabel>AmazonImport</guilabel>: Used for the <guimenuitem>Import from Amazon...</guimenuitem> function."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2566
#, no-c-format
msgid "<guilabel>DiscogsImport</guilabel>: Used for the <guimenuitem>Import from Discogs...</guimenuitem> function."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2569
#, no-c-format
msgid "<guilabel>FreedbImport</guilabel>: Used for the <guimenuitem>Import from gnudb.org...</guimenuitem> and <guimenuitem>Import from TrackType.org...</guimenuitem> functions."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2573
#, no-c-format
msgid "<guilabel>MusicBrainzImport</guilabel>: Used for the <guimenuitem>Import from MusicBrainz Release...</guimenuitem> function."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2577
#, no-c-format
msgid "<guilabel>AcoustidImport</guilabel>: Used for the <guimenuitem>Import from MusicBrainz Fingerprint...</guimenuitem> function, which depends on the <ulink url=\"http://acoustid.org/chromaprint\">Chromaprint</ulink> and <ulink url=\"http://libav.org/\">libav</ulink> libraries."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2584
#, no-c-format
msgid "Plugins which are disabled will not be loaded. This can be used to optimize resource usage and startup time. The settings on this page take only effect after a restart of &kid3;."
msgid "Displays a short information about &kid3;."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:2630
#, no-c-format
msgid "Commands"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2631
#, no-c-format
msgid "<command>kid3-cli</command> offers a command-line-interface for &kid3;. If a folder path is used, the folder is opened. If one or more file paths are given, the common folder is opened and the files are selected. Subsequent commands will then work on these files. Commands are specified using <option>-c</option> options. If multiple commands are passed, they are executed in the given order. If files are modified by the commands, they will be saved at the end. If no command options are passed, <command>kid3-cli</command> starts in interactive mode. Commands can be entered and will operate on the current selection. The following sections list all available commands."
msgid "Overwrite the default command timeout. The CLI commands abort after a command specific timeout is expired. This timeout is 10 seconds for <command>ls</command> and <command>albumart</command>, 60 seconds for <command>autoimport</command> and <command>filter</command>, and 3 seconds for all other commands. If a huge number of files has to be processed, these timeouts may be too restrictive, thus the timeout for all commands can be set to <replaceable>TIME</replaceable> ms, switched off altogether or be left at the default values."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:2678
#, no-c-format
msgid "Quit application"
msgstr ""
#. Tag: cmdsynopsis
#. +> trunk5
#: index.docbook:2679
#, no-c-format
msgid "<command>exit</command> <arg>force</arg>"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2683
#, no-c-format
msgid "Exit application. If there are modified unsaved files, the <parameter class=\"command\">force</parameter> parameter is required."
msgid "If no <replaceable>FOLDER</replaceable> is given, change to the home folder. If a folder is given, change into the folder. If one or more file paths are given, change to their common folder and select the files."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:2701
#, no-c-format
msgid "Print the filename of the current folder"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2705
#, no-c-format
msgid "Print the filename of the current working folder."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:2709
#, no-c-format
msgid "Folder list"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2713
#, no-c-format
msgid "List the contents of the current folder. This corresponds to the file list in the &kid3; &GUI;. Five characters before the file names show the state of the file."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2719
#, no-c-format
msgid "<computeroutput>></computeroutput> File is selected."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2721
#, no-c-format
msgid "<computeroutput>*</computeroutput> File is modified."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2723
#, no-c-format
msgid "<computeroutput>1</computeroutput> File has a tag 1, otherwise '<computeroutput>-</computeroutput>' is displayed."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2725
#, no-c-format
msgid "<computeroutput>2</computeroutput> File has a tag 2, otherwise '<computeroutput>-</computeroutput>' is displayed."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2727
#, no-c-format
msgid "<computeroutput>3</computeroutput> File has a tag 3, otherwise '<computeroutput>-</computeroutput>' is displayed."
msgid "To select all files, enter <userinput>select all</userinput>, to deselect all files, enter <userinput>select none</userinput>. To traverse the files in the current folder start with <userinput>select first</userinput>, then go forward using <userinput>select next</userinput> or backward using <userinput>select previous</userinput>. Specific files can be added to the current selection by giving their file names. Wildcards are possible, so <userinput>select *.mp3</userinput> will select all MP3 files in the current folder."
msgid "Many commands have an optional <replaceable>TAG-NUMBERS</replaceable> parameter, which specifies whether the command operates on tag 1, 2, or 3. If this parameter is omitted, the default tag numbers are used, which can be set by this command. At startup, it is set to <literal>12</literal> which means that information is read from tag 2 if available, else from tag 1; modifications are done on tag 2. The <option><replaceable>TAG-NUMBERS</replaceable></option> can be set to <userinput>1</userinput>, <userinput>2</userinput>, or <userinput>3</userinput> to operate only on the corresponding tag. If the parameter is omitted, the current setting is displayed."
msgid "This command can be used to read the value of a specific tag frame or get information about all tag frames (if the argument is omitted or <option>all</option> is used). Modified frames are marked with a '<computeroutput>*</computeroutput>'."
msgid "It is possible to get only a specific field from a frame, for example <userinput>get POPM.Email</userinput> for the Email field of a Popularimeter frame. If a file has multiple frames of the same kind, the different frames can be indexed with brackets, for example the first performer from a Vorbis comment can be retrieved using <userinput>get performer[0]</userinput>, the second using <userinput>get performer[1]</userinput>."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2823
#, no-c-format
msgid "The pseudo field name \"selected\" can be used to check if a frame is selected, for example <userinput>get artist.selected</userinput> will return <computeroutput>1</computeroutput> if the artist frame is selected, else <computeroutput>0</computeroutput>."
msgid "To set a specific field of a frame, the field name can be given after a dot, <abbrev>e.g.</abbrev> to set the Counter field of a Popularimeter frame, use"
msgstr ""
#. Tag: screen
#. +> trunk5
#: index.docbook:2852
#, no-c-format
msgid "<userinput>set POPM.Counter 5</userinput>"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2854
#, no-c-format
msgid ""
"An application for field specifications is the case where you want a custom TXXX frame with \"rating\" description instead of a standard Popularimeter frame (this seems to be used by some plugins). You can create such a TXXX rating frame with <command>kid3-cli</command>, however, you have to first create a TXXX frame with description \"rating\" and then set the value of this frame to the rating value. <screen width=\"65\">\n"
"</screen> The first command will delete an existing POPM frame, because if such a frame exists, <userinput>set rating 5</userinput> would set the POPM frame and not the TXXX frame. Another possibility would be to use <userinput>set TXXX.Text 5</userinput>, but this would only work if there is no other TXXX frame present."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2868
#, no-c-format
msgid "To set multiple frames of the same kind, an index can be given in brackets, <abbrev>e.g.</abbrev> to set multiple performers in a Vorbis comment, use"
msgstr ""
#. Tag: screen
#. +> trunk5
#: index.docbook:2871
#, no-c-format
msgid ""
"<prompt>kid3-cli> </prompt><userinput>set performer[0] 'Liza don Getti (soprano)'</userinput>\n"
msgid "To select certain frames before a copy, paste or remove action, the pseudo field name \"selected\" can be used. Normally, all frames are selected, to deselect all, use <userinput>set '*.selected' 0</userinput>, then for example <userinput>set artist.selected 1</userinput> to select the artist frame."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:2882
#, no-c-format
msgid "Revert"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2886
#, no-c-format
msgid "Revert all modifications in the selected files (or all files if no files are selected)."
msgid "Tags are imported from the file <replaceable>FILE</replaceable> in the format with the name <replaceable>FORMAT-NAME</replaceable> (<abbrev>e.g.</abbrev> <userinput>\"CSV unquoted\"</userinput>, see <link linkend=\"import-text\">Import</link>)."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2904
#, no-c-format
msgid "If <userinput>tags</userinput> is given for <replaceable>FILE</replaceable>, tags are imported from other tags. Instead of <replaceable>FORMAT-NAME</replaceable> parameters <replaceable>SOURCE</replaceable> and <replaceable>EXTRACTION</replaceable> are required, see <link linkend=\"import-tags\">Import from Tags</link>. To apply the import from tags on the selected files, use <userinput>tagsel</userinput> instead of <userinput>tags</userinput>. This function also supports output of the extracted value by using an <replaceable>EXTRACTION</replaceable> with the value <userinput>%{__return}(.+)</userinput>."
msgid "Batch import using profile <replaceable>PROFILE-NAME</replaceable> (see <link linkend=\"batch-import\">Automatic Import</link>, <userinput>\"All\"</userinput> is used if omitted)."
msgid "Set the album artwork by downloading a picture from <replaceable>URL</replaceable>. The rules defined in the <link linkend=\"browse_pictures\">Browse Cover Art</link> dialog are used to transform general &URL;s (<abbrev>e.g.</abbrev> from Amazon) to a picture &URL;. To set the album cover from a local picture file, use the <link linkend=\"cli-set\">set</link> command."
msgid "Tags are exported to file <replaceable>FILE</replaceable> in the format with the name <replaceable>FORMAT-NAME</replaceable> (<abbrev>e.g.</abbrev> <userinput>\"CSV unquoted\"</userinput>, see <link linkend=\"export\">Export</link>)."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:2962
#, no-c-format
msgid "Create playlist"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2966
#, no-c-format
msgid "Create playlist in the format set in the configuration, see <link linkend=\"create-playlist\">Create Playlist</link>."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:2972
#, no-c-format
msgid "Apply filename format"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2976
#, no-c-format
msgid "Apply file name format set in the configuration, see <link linkend=\"apply-filename-format\">Apply Filename Format</link>."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:2981
#, no-c-format
msgid "Apply tag format"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2985
#, no-c-format
msgid "Apply tag name format set in the configuration, see <link linkend=\"apply-tag-format\">Apply Tag Format</link>."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:2990 index.docbook:3795
#, no-c-format
msgid "Apply text encoding"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:2994
#, no-c-format
msgid "Apply text encoding set in the configuration, see <link linkend=\"apply-text-encoding\">Apply Text Encoding</link>."
msgid "Rename or create folders from the values in the tags according to a given <replaceable>FORMAT</replaceable> (<abbrev>e.g.</abbrev> <userinput>%{artist} - %{album}</userinput>, see <link linkend=\"rename-directory\">Rename Folder</link>), if no format is given, the format defined in the <guilabel>Rename folder</guilabel> dialog is used. The default mode is <option>rename</option>; to create folders, <option>create</option> must be given explicitly. The rename actions will be performed immediately, to just see what would be done, use the <option>dryrun</option> option."
msgid "Filter the files so that only the files matching the <replaceable>FILTER-FORMAT</replaceable> are visible. The name of a predefined filter expression (<abbrev>e.g.</abbrev> <userinput>\"Filename Tag Mismatch\"</userinput>) can be used instead of a filter expression, see <link linkend=\"filter\">Filter</link>."
msgid "Set the file names of the selected files from values in the tags, for example <userinput>fromtag '%{track} - %{title}' 1</userinput>. If no format is specified, the format set in the &GUI; is used."
msgid "Set the tag frames from the file names, for example <userinput>totag '%{albumartist} - %{album}/%{track} %{title}' 2</userinput>. If no format is specified, the format set in the &GUI; is used. If the format of the filename does not match this pattern, a few other commonly used formats are tried."
msgid "Copy the tag frames from one tag to the other tag, <abbrev>e.g.</abbrev> to set the ID3v2 tag from the ID3v1 tag, use <userinput>syncto 2</userinput>."
msgid "Copy the tag frames of the selected file to the internal copy buffer. They can then be set on another file using the <command>paste</command> command."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:3115
#, no-c-format
msgid "To copy only a subset of the frames, use the \"selected\" pseudo field with the <command>set</command> command. For example, to copy only the disc number and copyright frames, use"
msgid "It is possible to remove only a subset of the frames by selecting them as described in the <link linkend=\"cli-copy\"><command>copy</command> command</link>."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:3151
#, no-c-format
msgid "Examples"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:3152
#, no-c-format
msgid "Set title containing an apostrophe. Commands passed to <command>kid3-cli</command> with <parameter>-c</parameter> have to be in quotes if they do not only consist of a single word. If such a command itself has an argument containing spaces, that argument has to be quoted too. In &UNIX; shells single or double quotes can be used, but on the Windows Command Prompt, it is important that the outer quoting is done using double quotes and inside these quotes, single quotes are used. If the text inside the single quotes contains a single quote, it has to be escaped using a backslash character, as shown in the following example:"
msgstr ""
#. Tag: screen
#. +> trunk5
#: index.docbook:3161
#, no-c-format
msgid "<userinput>kid3-cli -c \"set title 'I\\'ll be there for you'\" /path/to/folder</userinput>"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:3163
#, no-c-format
msgid "Set album cover in all files of a folder using the batch import function:"
msgid "In order to make it easier to parse results from <command>kid3-cli</command>, it is possible to get the output in &JSON; format. When the request is in &JSON; format, the response will also be &JSON;. A compact format of the request will also give a compact representation of the response. If the request contains an \"id\" field, it is assumed to be a &JSON;-RPC request and the response will contain a \"jsonrpc\" field and the \"id\" of the request. The request format uses the same commands as the standard CLI, the \"method\" field contains the command and the parameters (if any) are given in the \"params\" list. The response contains a \"result\" object, which can also be null if the corresponding <command>kid3-cli</command> command does not return a result. In case of an error, an \"error\" object is returned with \"code\" and \"message\" fields as used in &JSON;-RPC."
msgid "Program written by Urs Fleisch <email>ufleisch@users.sourceforge.net</email>"
msgstr ""
#. Tag: trans_comment
#. +> trunk5
#: index.docbook:3218
#, no-c-format
msgid "CREDIT_FOR_TRANSLATORS"
msgstr ""
#. Tag: chapter
#. +> trunk5
#: index.docbook:3218
#, no-c-format
msgid "&underFDL; &underGPL;"
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:3226
#, no-c-format
msgid "Installation"
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:3229
#, no-c-format
msgid "How to obtain &kid3;"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:3231
#, no-c-format
msgid "&kid3; can be found at <ulink url=\"https://kid3.kde.org\">https://kid3.kde.org</ulink>."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:3238
#, no-c-format
msgid "Requirements"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:3240
#, no-c-format
msgid "&kid3; needs <ulink url=\"https://www.qt.io\">&Qt;</ulink>. <ulink url=\"http://www.kde.org\">&kde;</ulink> is recommended but not necessary, as &kid3; can also be compiled as a &Qt; application. &kid3; can be compiled for systems where these libraries are available, <abbrev>e.g.</abbrev> for GNU/&Linux;, &Windows; and &macOS;. To tag Ogg/Vorbis files, <ulink url=\"http://xiph.org/ogg/\">libogg</ulink>, <ulink url=\"http://xiph.org/vorbis/\">libvorbis and libvorbisfile</ulink> are required, for FLAC files <ulink url=\"http://flac.sourceforge.net\">libFLAC++ and libFLAC</ulink>. <ulink url=\"http://id3lib.sourceforge.net\">id3lib</ulink> is used for MP3 files. These four formats are also supported by <ulink url=\"http://taglib.github.io/\">TagLib</ulink>, which can also handle Opus, MPC, APE, MP2, Speex, TrueAudio, WavPack, WMA, WAV, AIFF files and tracker modules. To import from acoustic fingerprints, <ulink url=\"http://acoustid.org/chromaprint\">Chromaprint</ulink> and <ulink url=\"http://libav.org/\">libav</ulink> are used."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:3262
#, no-c-format
msgid "&kid3; is available for most &Linux; distributions, &Windows; and &macOS;. Links can be found on <ulink url=\"https://kid3.kde.org\"> https://kid3.kde.org</ulink>."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:3271
#, no-c-format
msgid "Compilation and Installation"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:3273
#, no-c-format
msgid "You can compile &kid3; with or without &kde;. Without &kde;, &kid3; is a simple &Qt; application and lacks some configuration and session features."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:3277
#, no-c-format
msgid "For a &kde; version, go into the top folder and type"
msgid "To compile for different versions of &Qt; or &kde;, set the corresponding <userinput>cmake</userinput> options."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:3285
#, no-c-format
msgid "If not all libraries are present, &kid3; is built with reduced functionality. So you should take care to have all desired development packages installed. On the other side, <userinput>cmake</userinput>-options control which libraries are compiled in. The default is <userinput>-DWITH_TAGLIB:BOOL=ON -DWITH_MP4V2:BOOL=OFF -DWITH_ID3LIB:BOOL=ON -DWITH_CHROMAPRINT:BOOL=ON -DWITH_VORBIS:BOOL=ON -DWITH_FLAC:BOOL=ON </userinput>. These options can be disabled using <userinput>OFF</userinput>."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:3295
#, no-c-format
msgid "To build &kid3; as a &Qt; application without &kde;, use the <userinput>cmake</userinput> option <userinput>-DWITH_APPS=Qt</userinput>. To build both a &kde; and a &Qt; application, set <userinput>-DWITH_APPS=\"Qt;KDE\"</userinput>."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:3301
#, no-c-format
msgid "To use a specific &Qt; installation, set <userinput>-DQT_QMAKE_EXECUTABLE=/path/to/qmake</userinput>."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:3305
#, no-c-format
msgid "Generation of RPM-Packages is supported by the file <filename>kid3.spec</filename>, for &Debian; Packages, the script <filename>build-deb.sh</filename> is available."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:3311
#, no-c-format
msgid "The &Qt; application can also be compiled for &Windows; and &macOS;. The script <filename>buildlibs.sh</filename> can be used to download and build all required libraries and create a &kid3; package."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:3320
#, no-c-format
msgid "Configuration"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:3322
#, no-c-format
msgid "With &kde;, the settings are stored in <filename>.config/kid3rc</filename>. As a &Qt; application, this file is in <filename>.config/Kid3/Kid3.conf</filename>. On &Windows;, the configuration is stored in the registry. on &macOS; in a plist file."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:3328
#, no-c-format
msgid "The environment variable <varname>KID3_CONFIG_FILE</varname> can be used to set the path of the configuration file."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:3336
#, no-c-format
msgid "&DBus; Interface"
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:3339
#, no-c-format
msgid "&DBus; Examples"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:3341
#, no-c-format
msgid "On &Linux; a &DBus;-interface can be used to control &kid3; by scripts. Scripts can be written in any language with &DBus;-bindings (<abbrev>e.g.</abbrev> in Python) and can be added to the <guilabel>User Actions</guilabel> to extend the functionality of &kid3;."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:3348
#, no-c-format
msgid "The artist in tag 2 of the current file can be set to the value \"One Hit Wonder\" with the following code:"
msgid "name of frame (<abbrev>e.g.</abbrev> \"artist\")"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:3979
#, no-c-format
msgid "To get binary data like a picture, the name of a file to write can be added after the <parameter>name</parameter>, <abbrev>e.g.</abbrev> \"Picture:/path/to/file\". In the same way, synchronized lyrics can be exported, <abbrev>e.g.</abbrev> \"SYLT:/path/to/file\"."
msgid "For tag 2 (<parameter>tagMask</parameter> 2), if no frame with <parameter>name</parameter> exists, a new frame is added, if <parameter>value</parameter> is empty, the frame is deleted. To add binary data like a picture, a file can be added after the <parameter>name</parameter>, <abbrev>e.g.</abbrev> \"Picture:/path/to/file\". \"SYLT:/path/to/file\" can be used to import synchronized lyrics."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:4019
#, no-c-format
msgid "Get all frames of a tag"
msgstr ""
#. Tag: funcprototype
#. +> trunk5
#: index.docbook:4021
#, no-c-format
msgid "<funcdef>array of string <function>getTag</function></funcdef> <paramdef>int32 <parameter>tagMask</parameter></paramdef>"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:4032
#, no-c-format
msgid "Returns list with alternating frame names and values."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:4036
#, no-c-format
msgid "Get technical information about file"
msgstr ""
#. Tag: funcdef
#. +> trunk5
#: index.docbook:4039
#, no-c-format
msgid "array of string <function>getInformation</function>"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:4043
#, no-c-format
msgid "Properties are Format, Bitrate, Samplerate, Channels, Duration, Channel Mode, VBR, Tag 1, Tag 2. Properties which are not available are omitted."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:4046
#, no-c-format
msgid "Returns list with alternating property names and values."
msgid "Automated configuration changes are possible by modifying the configuration file and then reparsing the configuration."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:4142
#, no-c-format
msgid "Plays the selected files"
msgstr ""
#. Tag: function
#. +> trunk5
#: index.docbook:4145
#, no-c-format
msgid "playAudio"
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:4156
#, no-c-format
msgid "QML Interface"
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:4159
#, no-c-format
msgid "QML Examples"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:4161
#, no-c-format
msgid "QML scripts can be invoked via the context menu of the file list and can be set in the tab <link linkend=\"configure-user-actions-qml\">User Actions</link> of the settings dialog. The scripts which are set there can be used as examples to program custom scripts. QML uses &javascript;, here is the obligatory \"Hello World\":"
msgid "If this script is saved as <filename>/path/to/Example.qml</filename>, the user command can be defined as <command>@qml /path/to/Example.qml</command> with name <userinput>QML Test</userinput> and <guilabel>Output</guilabel> checked. It can then be started using the <guilabel>QML Test</guilabel> item in the file list context menu, and the output will be visible in the window."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:4180
#, no-c-format
msgid ""
"Alternatively, the script could also be started independent of &kid3; using the QML tools. <screen width=\"80\">\n"
"</screen> On &Windows; and &macOS;, the import path must be adapted to the <filename class=\"directory\">imports</filename> folder inside the installation folder. Scripts started outside of &kid3; will use the current folder, so it should be changed beforehand."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:4193
#, no-c-format
msgid "To list the titles in the tags 2 of all files in the current folder, the following script could be used:"
msgstr ""
#. Tag: programlisting
#. +> trunk5
#: index.docbook:4198
#, no-c-format
msgid ""
"import Kid3 1.0\n"
"\n"
"Kid3Script {\n"
" onRun: {\n"
" app.firstFile()\n"
" do {\n"
" if (app.selectionInfo.tag(Frame.Tag_2).tagFormat) {\n"
" console.log(app.getFrame(tagv2, \"title\"))\n"
" }\n"
" } while (app.nextFile())\n"
" }\n"
"}"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:4200
#, no-c-format
msgid "If the folder contains many files, such a script might block the user interface for some time. For longer operations, it should therefore have a break from time to time. The alternative implementation below has the work for a single file moved out into a function. This function invokes itself with a timeout of 1 ms at the end, given that more files have to be processed. This will ensure that the &GUI; remains responsive while the script is running."
msgstr ""
#. Tag: programlisting
#. +> trunk5
#: index.docbook:4209
#, no-c-format
msgid ""
"import Kid3 1.0\n"
"\n"
"Kid3Script {\n"
" onRun: {\n"
" function doWork() {\n"
" if (app.selectionInfo.tag(Frame.Tag_2).tagFormat) {\n"
" console.log(app.getFrame(tagv2, \"title\"))\n"
" }\n"
" if (!app.nextFile()) {\n"
" Qt.quit()\n"
" } else {\n"
" setTimeout(doWork, 1)\n"
" }\n"
" }\n"
"\n"
" app.firstFile()\n"
" doWork()\n"
" }\n"
"}"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:4211
#, no-c-format
msgid "When using <command>app.firstFile()</command> with <command>app.nextFile()</command>, all files of the current folder will be processed. If only the selected files shall be affected, use <command>firstFile()</command> and <command>nextFile()</command> instead, these are convenience functions of the <classname>Kid3Script</classname> component. The following example is a script which copies only the disc number and copyright frames of the selected file."
msgstr ""
#. Tag: programlisting
#. +> trunk5
#: index.docbook:4221
#, no-c-format
msgid ""
"import Kid3 1.1\n"
"\n"
"Kid3Script {\n"
" onRun: {\n"
" function doWork() {\n"
" if (app.selectionInfo.tag(Frame.Tag_2).tagFormat) {\n"
msgid "More example scripts come with &kid3; and are already registered as user commands."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:4227
#, no-c-format
msgid "<guilabel>ReplayGain to SoundCheck</guilabel> (<filename>ReplayGain2SoundCheck.qml</filename>): Create iTunNORM SoundCheck information from replay gain frames."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:4232
#, no-c-format
msgid "<guilabel>Resize Album Art</guilabel> (<filename>ResizeAlbumArt.qml</filename>): Resize embedded cover art images which are larger than 500x500 pixels."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:4237
#, no-c-format
msgid "<guilabel>Extract Album Art</guilabel> (<filename>ExtractAlbumArt.qml</filename>): Extract all embedded cover art pictures avoiding duplicates."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:4242
#, no-c-format
msgid "<guilabel>Embed Album Art</guilabel> (<filename>EmbedAlbumArt.qml</filename>): Embed cover art found in image files into audio files in the same folder."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:4247
#, no-c-format
msgid "<guilabel>Embed Lyrics</guilabel> (<filename>EmbedLyrics.qml</filename>): Fetch unsynchronized lyrics from web service."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:4252
#, no-c-format
msgid "<guilabel>Text Encoding ID3v1</guilabel> (<filename>ShowTextEncodingV1.qml</filename>): Helps to find the encoding of ID3v1 tags by showing the tags of the current file in all available character encodings."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:4258
#, no-c-format
msgid "<guilabel>ID3v1 to ASCII</guilabel> (<filename>Tag1ToAscii.qml</filename>): Transliterate extended latin characters in the ID3v1 tag to ASCII."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:4263
#, no-c-format
msgid "<guilabel>English Title Case</guilabel> (<filename>TitleCase.qml</filename>): Formats text in the tags to English title case."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:4268
#, no-c-format
msgid "<guilabel>Export CSV</guilabel> (<filename>ExportCsv.qml</filename>): Export recursively all tags of all files to a CSV file."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:4273
#, no-c-format
msgid "<guilabel>Export Playlist Folder</guilabel> (<filename>ExportPlaylist.qml</filename>): Copy all files from a playlist into a folder and rename them according to their position."
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:4279
#, no-c-format
msgid "<guilabel>QML Console</guilabel> (<filename>QmlConsole.qml</filename>): Simple console to play with &kid3;'s QML API."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:4290
#, no-c-format
msgid "QML API"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:4292
#, no-c-format
msgid "The API can be easily explored using the QML Console, which is available as an example script with a user interface."
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:4298
#, no-c-format
msgid "Kid3Script"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:4300
#, no-c-format
msgid "<classname>Kid3Script</classname> is a regular QML component located inside the plugin folder. You could use another QML component just as well. Using <classname>Kid3Script</classname> makes it easy to start the script function using the <function>onRun</function> signal handler. Moreover it offers some functions:"
msgstr ""
#. Tag: programlisting
#. +> trunk5
#: index.docbook:4307
#, no-c-format
msgid ""
"onRun: Signal handler which is invoked when the script is started\n"
"tagv1, tagv2, tagv2v1: Constants for tag parameters\n"
"script: Access to scripting functions\n"
"configs: Access to configuration objects\n"
"getArguments(): List of script arguments\n"
"isStandalone(): true if the script was not started from within Kid3\n"
"setTimeout(callback, delay): Starts callback after delay ms\n"
"firstFile(): To first selected file\n"
"nextFile(): To next selected file"
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:4313
#, no-c-format
msgid "Scripting Functions"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:4315
#, no-c-format
msgid "As &javascript; and therefore QML too has only a limited set of functions for scripting, the <function>script</function> object has some additional methods, for instance:"
msgstr ""
#. Tag: programlisting
#. +> trunk5
#: index.docbook:4321
#, no-c-format
msgid ""
"script.properties(obj): String with Qt properties\n"
"script.writeFile(filePath, data): Write data to file, true if OK\n"
"script.readFile(filePath): Read data from file\n"
"script.removeFile(filePath): Delete file, true if OK\n"
"script.fileExists(filePath): true if file exists\n"
"script.fileIsWritable(filePath): true if file is writable\n"
"script.getFilePermissions(filePath): Get file permission mode bits\n"
"script.setFilePermissions(filePath, modeBits): Set file permission mode bits\n"
"script.classifyFile(filePath): Get class of file (folder \"/\", symlink \"@\", exe \"*\",\n"
" file \" \")\n"
"script.renameFile(oldName, newName): Rename file, true if OK\n"
"script.copyFile(source, dest): Copy file, true if OK\n"
"script.makeDir(path): Create folder, true if OK\n"
"script.removeDir(path): Remove folder, true if OK\n"
"script.tempPath(): Path to temporary folder\n"
"script.musicPath(): Path to music folder\n"
"script.listDir(path, [nameFilters], [classify]): List folder entries\n"
"script.system(program, [args], [msecs]): Synchronously start a system command,\n"
" [exit code, standard output, standard error] if not timeout\n"
"script.systemAsync(program, [args], [callback]): Asynchronously start a system\n"
"command, callback will be called with [exit code, standard output, standard\n"
"error]\n"
"script.getEnv(varName): Get value of environment variable\n"
"script.setEnv(varName, value): Set value of environment variable\n"
"script.getQtVersion(): Qt version string, <abbrev>e.g.</abbrev> \"5.4.1\"\n"
"script.getDataMd5(data): Get hex string of the MD5 hash of data\n"
"script.getDataSize(data): Get size of byte array\n"
"script.dataToImage(data, [format]): Create an image from data bytes\n"
"script.dataFromImage(img, [format]): Get data bytes from image\n"
"script.loadImage(filePath): Load an image from a file\n"
"script.saveImage(img, filePath, [format]): Save an image to a file, true if OK\n"
"script.imageProperties(img): Get properties of an image, map containing\n"
" \"width\", \"height\", \"depth\" and \"colorCount\", empty if invalid image\n"
"script.scaleImage(img, width, [height]): Scale an image, returns scaled image"
msgstr ""
#. Tag: title
#. +> trunk5
#: index.docbook:4326
#, no-c-format
msgid "Application Context"
msgstr ""
#. Tag: para
#. +> trunk5
#: index.docbook:4328
#, no-c-format
msgid "Using QML, a large part of the &kid3; functions are accessible. The API is similar to the one used for <link linkend=\"dbus-api\">&DBus;</link>. For details, refer to the respective notes."
"The different configuration sections are accessible via methods of <function>configs</function>. Their properties can be listed in the QML console. <screen width=\"80\">\n"
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."
msgid "Explanation of the What's Interesting Panel"
msgstr ""
#. +> trunk5
#: data/qml/whatisinteresting/wiview.qml:1559
#, kde-kuit-format
msgid "The What's Interesting Panel is intended to allow you to explore many different interesting objects in the night sky. It includes objects visible to the naked eye as well as objects that require telescopes. It is intended to appeal to both beginners and advanced astronomers. If you click on a category or catalog, a list of objects will appear. Clicking on an object in the list will bring up the details view where you can find out more information about the object. If you have thumbnail images or wikipedia information for this object, these will be displayed as well. If not, you can download them using the download icon. If you make What's Interesting wider, the display will dynamically change to display the information more conveniently. Please see the descriptions below for details on what the buttons at the bottom do."
msgstr ""
#. +> trunk5
#: data/qml/whatisinteresting/wiview.qml:1581
#, kde-kuit-format
msgid "This button will bring up the What's Interesting Settings. It will let you configure what is displayed in What's Interesting based upon which equipment you are using and the observing conditions."
msgstr ""
#. +> trunk5
#: data/qml/whatisinteresting/wiview.qml:1602
#, kde-kuit-format
msgid "This button will turn on and off the Inspector Mode. In this mode you can click on any object in the map and What's Interesting will display the information about it."
msgstr ""
#. +> trunk5
#: data/qml/whatisinteresting/wiview.qml:1623
#, kde-kuit-format
msgid "This button will reload the current object list, update all displayed information, update any images, and update the information and images for the currently selected object."
msgstr ""
#. +> trunk5
#: data/qml/whatisinteresting/wiview.qml:1644
#, kde-kuit-format
msgid "This button will toggle whether to filter the list to display only currently visible objects in a list or to display all of the objects in the list. The visibility is determined based on the current KStars date and time, the current observing equipment, and the current sky conditions based on the What's Interesting Settings."
msgstr ""
#. +> trunk5
#: data/qml/whatisinteresting/wiview.qml:1665
#, kde-kuit-format
msgid "This button will toggle whether to filter the list to display only 'interesting' objects or to display any of the objects in the list. This setting only applies to the Galaxies, Nebulas, and Clusters lists. The objects are considered 'interesting' if they appear on the KStars 'interesting' list."
msgstr ""
#. +> trunk5
#: data/qml/whatisinteresting/wiview.qml:1686
#, kde-kuit-format
msgid "This button will attempt to download information and pictures about the object(s) from Wikipedia. You can select whether to download the information about just one object, all of the objects in a list, or only the objects in a list for which no data was downloaded yet. Please note: If the list is currently filtered for visible objects or 'interesting' objects, only the filtered objects will be downloaded. If you actually want all the objects in the list, turn off the filters."
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:1526
#, kde-format
msgid "Clear Solution Points"
msgstr ""
#. +> trunk5
#: ekos/align/align.cpp:1534
#, kde-format
msgid "Are you sure you want to clear all the alignment points?"
msgstr ""
#. +> trunk5
#: ekos/align/align.cpp:1535
#, kde-format
msgid "Clear Align Points"
msgstr ""
#. +> trunk5
#: ekos/align/align.cpp:1680
#, kde-format
msgid "The Mount Model Tool is Reset."
msgstr ""
#. +> trunk5
#: ekos/align/align.cpp:1717
#, kde-format
msgid "Please Check the Alignment Points."
msgstr ""
#. +> trunk5
#: ekos/align/align.cpp:1724
#, 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 "Slewing to calibration position, please wait until telescope completes slewing."
msgstr ""
#. +> trunk5
#: ekos/align/align.cpp:4671
#, kde-format
msgid "Load Image"
msgstr ""
#. +> trunk5
#: ekos/align/align.cpp:4866
#, 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:4875
#, 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:5670
#, 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:5689
#, 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 "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 with the counter weight down. 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:64
#, 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:65
#, kde-format
msgid "Missing astrometry files"
msgstr ""
#. +> trunk5
#: ekos/align/offlineastrometryparser.cpp:91
#, kde-format
msgid "Detected Astrometry.net version %1"
msgstr ""
#. +> trunk5
#: ekos/align/offlineastrometryparser.cpp:96
#, kde-format
msgid "Setting astrometry option --no-fits2fits"
msgstr ""
#. +> trunk5
#: ekos/align/offlineastrometryparser.cpp:101
#, kde-format
msgid "Turning off option --no-fits2fits"
msgstr ""
#. +> trunk5
#: ekos/align/offlineastrometryparser.cpp:195
#, 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://astrometry.net"
msgstr ""
#. +> trunk5
#: ekos/align/offlineastrometryparser.cpp:199
#, 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://astrometry.net"
msgstr ""
#. +> trunk5
#: ekos/align/offlineastrometryparser.cpp:282
#: ekos/align/offlineastrometryparser.cpp:301
#, kde-format
msgid "Sextractor file write error."
msgstr ""
#. +> trunk5
#: ekos/align/offlineastrometryparser.cpp:314
#, kde-format
msgid "Starting sextractor..."
msgstr ""
#. +> trunk5
#: ekos/align/offlineastrometryparser.cpp:414
#, kde-format
msgid "WCS header missing or corrupted. Solver failed."
msgstr ""
#. +> 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 astrometry.cfg?"
msgstr ""
#. +> trunk5
#: ekos/align/opsalign.cpp:45
#, kde-format
msgid "Internal or External Plate Solver?"
msgstr ""
#. i18n: ectx: label, entry (AstrometryWCSIsInternal), group (Align)
#. +> trunk5
#: ekos/align/opsalign.cpp:50 kstars.kcfg:2006
#, kde-format
msgid "Internal or External wcsinfo?"
msgstr ""
#. i18n: ectx: label, entry (SextractorIsInternal), group (Align)
#. +> trunk5
#: ekos/align/opsalign.cpp:55 kstars.kcfg:2033
#, kde-format
msgid "Internal or External sextractor?"
msgstr ""
#. +> trunk5
#: ekos/align/opsalign.cpp:86
#, kde-format
msgid "Homebrew, python, and astropy are already installed"
msgstr ""
#. +> trunk5
#: ekos/align/opsalign.cpp:90
#, 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:91
#, kde-format
msgid "Install and Configure Python"
msgstr ""
#. +> trunk5
#: ekos/align/opsalign.cpp:101
#, 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:123
#, 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:128
#, kde-format
msgid "Python install failure"
msgstr ""
#. +> trunk5
#: ekos/align/opsalign.cpp:134
#, 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:139
#, kde-format
msgid "Astropy install failure"
msgstr ""
#. +> trunk5
#: ekos/align/opsalign.cpp:143
#, kde-format
msgid "All installations are complete and ready to use."
"<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>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>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 Astrometry.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:4080
#, kde-format
msgid "Save Ekos Sequence Queue"
msgstr ""
#. +> trunk5
#: ekos/capture/capture.cpp:4110
#, kde-format
msgid "Failed to save sequence queue"
msgstr ""
#. +> trunk5
#: ekos/capture/capture.cpp:4144
#, kde-format
msgid "Could not open file"
msgstr ""
#. +> trunk5
#: ekos/capture/capture.cpp:4164
#, 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:4271
#, kde-format
msgid "Sequence queue saved to %1"
msgstr ""
#. +> trunk5
#: ekos/capture/capture.cpp:4295
#, 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:6305
#, kde-format
msgid "Ekos will refocus in %1 seconds, last procedure was %2 seconds ago."
msgstr ""
#. +> trunk5
#: ekos/capture/capture.cpp:6310
#, kde-format
msgid "Ekos will refocus as soon as possible, last procedure was %1 seconds ago."
"<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;\">Locally</span>: Captured images are saved locally on disk in the directory specified above.</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;\">Remotely</span>: When connecting to a remote device, select this option to save images on the remote device only. No images are uploaded to Ekos.</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;\">Both</span>: Captured images are saved on both the remote computer <span style=\" font-weight:600;\">and</span> on the local disk as well.</li>"
"</ol>"
"<p>When selecting <span style=\" font-style:italic;\">Remotely</span> or <span style=\" font-style:italic;\">Both</span>, you must specify the remote directory where the remote images are saved to. By default, all captured images are saved <span style=\" font-style:italic;\">Locally</span>.</p>"
"<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=\"https://www.digicamdb.com/\"><span style=\" text-decoration: underline; color:#007af4;\">Digital Camera Database</span></a>.</p>"
"<p>Set the <span style=\" font-weight:600;\">desired</span> target position angle for a sequence job. Click OK then add the sequence job to the sequence queue. When the job is executed, the position angle is first set to this target value prior to capturing the image.</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>"
"<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;\">Iterative</span>: 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>"
"<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;\">Polynomial</span>: 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>"
"<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;\">Linear</span>: Samples focus inward in a regular fashion, using 2 passes. The algorithm can be slow, but it is more resilient to backlash. Start with the focuser positioned near good focus. Set Initial Step Size and Max Travel for the desired sampling interval and range around start focus position. Tolerance should be around 5%.</li>"
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"
"<p>The maximum single step size the algorithm is allowed to command as it searches for the critical focus zone. The calculated step size would be limited to this maximum value.</p>"
msgctxt "Drift graphics tooltip; %1 is local time; %2 is RA deviation; %3 is DE deviation in arcseconds; %4 is RA Pulse in ms; %5 is DE Pulse in ms"
msgid ""
"<table>"
"<tr>"
"<td>LT: </td>"
"<td>%1</td>"
"</tr>"
"<tr>"
"<td>RA: </td>"
"<td>%2 \"</td>"
"</tr>"
"<tr>"
"<td>DE: </td>"
"<td>%3 \"</td>"
"</tr>"
"<tr>"
"<td>RA Pulse: </td>"
"<td>%4 ms</td>"
"</tr>"
"<tr>"
"<td>DE Pulse: </td>"
"<td>%5 ms</td>"
"</tr>"
"</table>"
msgstr ""
#. +> trunk5
#: ekos/guide/guide.cpp:499
#, kde-format
msgid "Export Guide Data"
msgstr ""
#. +> trunk5
#: ekos/guide/guide.cpp:555
#, kde-format
msgid "Guide Data Saved as: %1"
msgstr ""
#. +> trunk5
#: ekos/guide/guide.cpp:658
#, kde-format
msgid "PHD2's current camera: %1, is NOT connected to Ekos. The PHD2 Guide Star Image will be received, but the full external guide frames cannot."
msgstr ""
#. +> trunk5
#: ekos/guide/guide.cpp:668
#, kde-format
msgid "PHD2's current camera: %1, IS connected to Ekos. You can select whether to use the full external guide frames or just receive the PHD2 Guide Star Image using the SubFrame checkbox."
msgstr ""
#. +> trunk5
#: ekos/guide/guide.cpp:872
#, kde-format
msgid "Connection to the guide CCD is lost."
msgstr ""
#. +> trunk5
#: ekos/guide/guide.cpp:1205
#, kde-format
msgid "Exposure timeout. Aborting Autoguide."
msgstr ""
#. +> trunk5
#: ekos/guide/guide.cpp:1207
#, kde-format
msgid "Exposure timeout. Aborting Dithering."
msgstr ""
#. +> trunk5
#: ekos/guide/guide.cpp:1209
#, kde-format
msgid "Exposure timeout. Aborting Calibration."
msgstr ""
#. +> trunk5
#: ekos/guide/guide.cpp:1517
#, kde-format
msgid "The guide camera is identical to the primary imaging camera. Are you sure you want to continue?"
msgstr ""
#. +> trunk5
#: ekos/guide/guide.cpp:1524
#, kde-format
msgid "The mount is parked. Unpark to start guiding."
msgstr ""
#. +> trunk5
#: ekos/guide/guide.cpp:1614
#, kde-format
msgid "Pier side change detected. Clearing calibration."
msgid "To receive PHD2 images other than the Guide Star Image, SubFrame must be unchecked. Unchecking it now to enable your image captures. You can re-enable it before Guiding"
"<p>Subframe the image around the guide star. Or for PHD2, receive the Guide Star Image instead of the full image frame. For the Internal Guider, 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>"
msgid "Use you equipment without opening remote access but equipment is still connected to INDIHUB-network and all images taken are contributed for scientific purposes."
"<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>Set Hour Angle unit to Degrees. Add 1 degree to the mount meridian flip setting. For example, if the mount meridian flip limit is set to 5 degrees, set the value here to be <span style=\" font-weight:600;\">at least</span> 6 degrees to ensure a successful meridian flip.</p>"
"<p>Enable or Disable the mount travel range limits. Once enabled, Ekos monitors the mount's altitude while slewing or tracking. If the mount slews/tracks below or above the limits, it shall be commanded to stop and tracking will be turned off.</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:522 kstars.kcfg:1672
#, 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:818 kstars.kcfg:1530
#, 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><span style=\" font-weight:600;\">Tip</span>: External INDI Server can be <a href=\"http://www.cloudmakers.eu/indigoserver/\"><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=\"https://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:795
#, 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:803
#, 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:808
#, 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:982
#, kde-format
msgid "Warning: you cannot add or modify a job while the scheduler is running."
msgstr ""
#. +> trunk5
#: ekos/scheduler/scheduler.cpp:1050
#, kde-format
msgid "Use edition fields to create a new job in the observation list."
msgstr ""
#. +> trunk5
#: ekos/scheduler/scheduler.cpp:1314
#, kde-format
msgid "Job '%1' has not been processed upon scheduler stop, marking aborted."
msgstr ""
#. +> trunk5
#: ekos/scheduler/scheduler.cpp:1321
#, kde-format
msgid "Scheduler aborted."
msgstr ""
#. +> trunk5
#: ekos/scheduler/scheduler.cpp:1380
#, 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>The twilight restriction constrains jobs to execute in astronomical darkness. Use the dusk and dawn offsets in the Ekos Scheduler options to adjust the interval.</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>"
"<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;\">Don't re-schedule</span>: Don't restart the job in case of an error or an abort.</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;\">Re-schedule after all terminated</span>: If a job gets aborted, the scheduler will only re-schedule it if when all jobs are finished or aborted. If this is the case, the scheduler re-schedules all aborted jobs and sleeps for the given delay.</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;\">Re-schedule immediately</span>: As soon as a job gets aborted, the scheduler will re-schedule it and waits the given delay.</li>"
"</ul>"
"<p>If the option for re-scheduling errors is selected, errors are handled like aborts. Otherwise, jobs that step into an error are never re-scheduled.</p>"
"<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>"
"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"
"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:249
#, kde-format
msgid ""
"Startup time for job '%1', as estimated by the Scheduler.\n"
"The altitude at startup, if available, is displayed too.\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 (SaveFocusImages), group (indi)
#. +> trunk5
#: kstars.kcfg:173
#, kde-format
msgid "Save autofocus images on disk?"
msgstr ""
#. i18n: ectx: label, entry (messageNotificationINDI), group (indi)
#. +> trunk5
#: kstars.kcfg:177
#, kde-format
msgid "INDI message notifications"
msgstr ""
#. i18n: ectx: whatsthis, entry (messageNotificationINDI), group (indi)
#. +> trunk5
#: kstars.kcfg:178
#, kde-format
msgid "Show INDI messages as desktop notifications instead of dialogs."
msgstr ""
#. i18n: ectx: label, entry (useKStarsSource), group (indi)
#. +> trunk5
#: kstars.kcfg:182
#, kde-format
msgid "Use KStars time and location for synchronization?"
msgstr ""
#. i18n: ectx: label, entry (useMountSource), group (indi)
#. +> trunk5
#: kstars.kcfg:186
#, kde-format
msgid "Use mount time and location for synchronization?"
msgstr ""
#. i18n: ectx: label, entry (useGPSSource), group (indi)
#. +> trunk5
#: kstars.kcfg:190
#, kde-format
msgid "Use GPS time and location for synchronization?"
msgstr ""
#. i18n: ectx: label, entry (fitsDir), group (indi)
#. +> trunk5
#: kstars.kcfg:194
#, kde-format
msgid "FITS Default directory"
msgstr ""
#. i18n: ectx: whatsthis, entry (fitsDir), group (indi)
#. +> trunk5
#: kstars.kcfg:195
#, kde-format
msgid "The default location of saved FITS files"
msgstr ""
#. i18n: ectx: label, entry (serverPortStart), group (indi)
#. +> trunk5
#: kstars.kcfg:199
#, kde-format
msgid "INDI Server Start Port"
msgstr ""
#. i18n: ectx: whatsthis, entry (serverPortStart), group (indi)
#. +> trunk5
#: kstars.kcfg:200
#, 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:204
#, kde-format
msgid "INDI Server Final Port"
msgstr ""
#. i18n: ectx: whatsthis, entry (serverPortEnd), group (indi)
#. +> trunk5
#: kstars.kcfg:205
#, 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:209
#, kde-format
msgid "Aliases for filter wheel slots."
msgstr ""
#. i18n: ectx: whatsthis, entry (filterAlias), group (indi)
#. +> trunk5
#: kstars.kcfg:210
#, 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:213 kstars.kcfg:214
#, kde-format
msgid "PATH to indiserver binary"
msgstr ""
#. i18n: ectx: label, entry (INDIHubAgent), group (indi)
#. i18n: ectx: whatsthis, entry (INDIHubAgent), group (indi)
#. +> trunk5
#: kstars.kcfg:218 kstars.kcfg:219
#, kde-format
msgid "PATH to indihub-agent binary"
msgstr ""
#. i18n: ectx: label, entry (indiServerIsInternal), group (indi)
#. +> trunk5
#: kstars.kcfg:223
#, 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:227 kstars.kcfg:228
#, 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:232 kstars.kcfg:1997
#, kde-format
msgid "Internal or External Astrometry Solver?"
msgstr ""
#. i18n: ectx: label, entry (streamWindowWidth), group (indi)
#. +> trunk5
#: kstars.kcfg:236
#, kde-format
msgid "Video streaming window width"
msgstr ""
#. i18n: ectx: label, entry (streamWindowHeight), group (indi)
#. +> trunk5
#: kstars.kcfg:240
#, kde-format
msgid "Video streaming window height"
msgstr ""
#. i18n: ectx: label, entry (INDIMountLogging), group (indi)
#. +> trunk5
#: kstars.kcfg:244
#, kde-format
msgid "Enable INDI Mount logging"
msgstr ""
#. i18n: ectx: label, entry (INDIFocuserLogging), group (indi)
#. +> trunk5
#: kstars.kcfg:248
#, kde-format
msgid "Enable INDI Focuser logging"
msgstr ""
#. i18n: ectx: label, entry (INDICCDLogging), group (indi)
#. +> trunk5
#: kstars.kcfg:252
#, kde-format
msgid "Enable INDI CCD logging"
msgstr ""
#. i18n: ectx: label, entry (INDIFilterWheelLogging), group (indi)
#. +> trunk5
#: kstars.kcfg:256
#, kde-format
msgid "Enable INDI Filter Wheel logging"
msgstr ""
#. i18n: ectx: label, entry (INDIDomeLogging), group (indi)
#. +> trunk5
#: kstars.kcfg:260
#, kde-format
msgid "Enable INDI Dome logging"
msgstr ""
#. i18n: ectx: label, entry (INDIDetectorLogging), group (indi)
#. +> trunk5
#: kstars.kcfg:264
#, kde-format
msgid "Enable INDI Detector logging"
msgstr ""
#. i18n: ectx: label, entry (INDIWeatherLogging), group (indi)
#. +> trunk5
#: kstars.kcfg:268
#, kde-format
msgid "Enable INDI Weather logging"
msgstr ""
#. i18n: ectx: label, entry (INDIAuxiliaryLogging), group (indi)
#. +> trunk5
#: kstars.kcfg:272
#, kde-format
msgid "Enable INDI Auxiliary logging"
msgstr ""
#. i18n: ectx: label, entry (INDIRotatorLogging), group (indi)
#. +> trunk5
#: kstars.kcfg:276
#, kde-format
msgid "Enable INDI Rotator logging"
msgstr ""
#. i18n: ectx: label, entry (INDIGPSLogging), group (indi)
#. +> trunk5
#: kstars.kcfg:280
#, kde-format
msgid "Enable INDI GPS logging"
msgstr ""
#. i18n: ectx: label, entry (INDIAOLogging), group (indi)
#. +> trunk5
#: kstars.kcfg:284
#, kde-format
msgid "Enable INDI Adaptive Optics logging"
msgstr ""
#. i18n: ectx: label, entry (CityName), group (Location)
#. +> trunk5
#: kstars.kcfg:291
#, kde-format
msgid "City name of geographic location."
msgstr ""
#. i18n: ectx: whatsthis, entry (CityName), group (Location)
#. +> trunk5
#: kstars.kcfg:292
#, kde-format
msgid "The City name of the current geographic location."
msgstr ""
#. i18n: ectx: label, entry (ProvinceName), group (Location)
#. +> trunk5
#: kstars.kcfg:296
#, kde-format
msgid "Province name of geographic location."
msgstr ""
#. i18n: ectx: whatsthis, entry (ProvinceName), group (Location)
#. +> trunk5
#: kstars.kcfg:297
#, 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:301
#, kde-format
msgid "Country name of geographic location."
msgstr ""
#. i18n: ectx: whatsthis, entry (CountryName), group (Location)
#. +> trunk5
#: kstars.kcfg:302
#, kde-format
msgid "The Country name of the current geographic location."
msgstr ""
#. i18n: ectx: label, entry (Longitude), group (Location)
#. +> trunk5
#: kstars.kcfg:306
#, kde-format
msgid "Geographic Longitude, in degrees."
msgstr ""
#. i18n: ectx: whatsthis, entry (Longitude), group (Location)
#. +> trunk5
#: kstars.kcfg:307
#, kde-format
msgid "The longitude of the current geographic location, in decimal degrees."
msgstr ""
#. i18n: ectx: label, entry (Latitude), group (Location)
#. +> trunk5
#: kstars.kcfg:311
#, kde-format
msgid "Geographic Latitude, in degrees."
msgstr ""
#. i18n: ectx: whatsthis, entry (Latitude), group (Location)
#. +> trunk5
#: kstars.kcfg:312
#, kde-format
msgid "The latitude of the current geographic location, in decimal degrees."
msgstr ""
#. i18n: ectx: label, entry (Elevation), group (Location)
#. +> trunk5
#: kstars.kcfg:316
#, kde-format
msgid "Elevation above sea level of geographic location, in meters."
msgstr ""
#. i18n: ectx: label, entry (TimeZone), group (Location)
#. +> trunk5
#: kstars.kcfg:320
#, kde-format
msgid "Time Zone offset of geographic location, in hours."
msgstr ""
#. i18n: ectx: label, entry (DST), group (Location)
#. +> trunk5
#: kstars.kcfg:324
#, 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:325
#, 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:332
#, kde-format
msgid "Use animated slewing effects when changing focus position?"
msgstr ""
#. i18n: ectx: whatsthis, entry (UseAnimatedSlewing), group (View)
#. +> trunk5
#: kstars.kcfg:333
#, 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:337
#, kde-format
msgid "Select objects on left click?"
msgstr ""
#. i18n: ectx: whatsthis, entry (LeftClickSelectsObject), group (View)
#. +> trunk5
#: kstars.kcfg:338
#, 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:342
#, kde-format
msgid "Select default Skymap cursor?"
msgstr ""
#. i18n: ectx: whatsthis, entry (DefaultCursor), group (View)
#. +> trunk5
#: kstars.kcfg:343
#, kde-format
msgid "Type of cursor when exploring the sky map."
msgstr ""
#. i18n: ectx: label, entry (FOVNames), group (View)
#. +> trunk5
#: kstars.kcfg:347
#, kde-format
msgid "Name of selected FOV indicators"
msgstr ""
#. i18n: ectx: whatsthis, entry (FOVNames), group (View)
#. +> trunk5
#: kstars.kcfg:348
#, 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:352
#, kde-format
msgid "Fade planet trails to background color?"
msgstr ""
#. i18n: ectx: whatsthis, entry (FadePlanetTrails), group (View)
#. +> trunk5
#: kstars.kcfg:353
#, 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:357
#, kde-format
msgid "Right Ascension of focus position"
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusRA), group (View)
#. +> trunk5
#: kstars.kcfg:358
#, 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:362
#, kde-format
msgid "Declination of focus position"
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusDec), group (View)
#. +> trunk5
#: kstars.kcfg:363
#, 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:367
#, kde-format
msgid "Name of focused object"
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusObject), group (View)
#. +> trunk5
#: kstars.kcfg:368
#, 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:372
#, kde-format
msgid "Is tracking engaged?"
msgstr ""
#. i18n: ectx: whatsthis, entry (IsTracking), group (View)
#. +> trunk5
#: kstars.kcfg:373
#, 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:377
#, kde-format
msgid "Hide objects while moving?"
msgstr ""
#. i18n: ectx: whatsthis, entry (HideOnSlew), group (View)
#. +> trunk5
#: kstars.kcfg:378
#, 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:382
#, kde-format
msgid "Hide constellation boundaries while moving?"
msgstr ""
#. i18n: ectx: whatsthis, entry (HideCBounds), group (View)
#. +> trunk5
#: kstars.kcfg:383
#, 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:542
#, kde-format
msgid "Coordinate grids will automatically change according to active coordinate system."
msgstr ""
#. i18n: ectx: label, entry (ShowEquatorialGrid), group (View)
#. +> trunk5
#: kstars.kcfg:546
#, kde-format
msgid "Draw equatorial coordinate grid in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowEquatorialGrid), group (View)
#. +> trunk5
#: kstars.kcfg:547
#, 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:551
#, kde-format
msgid "Draw horizontal coordinate grid in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowHorizontalGrid), group (View)
#. +> trunk5
#: kstars.kcfg:552
#, 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:556
#, kde-format
msgid "Draw local meridian line in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowLocalMeridian), group (View)
#. +> trunk5
#: kstars.kcfg:557
#, 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:561
#, kde-format
msgid "Draw opaque ground in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowGround), group (View)
#. +> trunk5
#: kstars.kcfg:562
#, kde-format
msgid "Toggle whether the region below the horizon is opaque."
msgstr ""
#. i18n: ectx: label, entry (ShowHorizon), group (View)
#. +> trunk5
#: kstars.kcfg:566
#, kde-format
msgid "Draw horizon line in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowHorizon), group (View)
#. +> trunk5
#: kstars.kcfg:567
#, 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:571
#, kde-format
msgid "Draw flags in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowFlags), group (View)
#. +> trunk5
#: kstars.kcfg:572
#, kde-format
msgid "Toggle whether flags are drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowIC), group (View)
#. +> trunk5
#: kstars.kcfg:576
#, kde-format
msgid "Draw IC objects in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowIC), group (View)
#. +> trunk5
#: kstars.kcfg:577
#, kde-format
msgid "Toggle whether IC objects are drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowNGC), group (View)
#. +> trunk5
#: kstars.kcfg:581
#, kde-format
msgid "Draw NGC objects in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowNGC), group (View)
#. +> trunk5
#: kstars.kcfg:582
#, kde-format
msgid "Toggle whether NGC objects are drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowMessier), group (View)
#. +> trunk5
#: kstars.kcfg:586
#, kde-format
msgid "Draw Messier objects in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowMessier), group (View)
#. +> trunk5
#: kstars.kcfg:587
#, kde-format
msgid "Toggle whether Messier objects are drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowMessierImages), group (View)
#. +> trunk5
#: kstars.kcfg:591
#, kde-format
msgid "Draw Messier object images in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowMessierImages), group (View)
#. +> trunk5
#: kstars.kcfg:592
#, 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:596
#, kde-format
msgid "Draw extra deep-sky objects in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowOther), group (View)
#. +> trunk5
#: kstars.kcfg:597
#, kde-format
msgid "Toggle whether extra objects are drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowMilkyWay), group (View)
#. +> trunk5
#: kstars.kcfg:601
#, kde-format
msgid "Draw Milky Way contour in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowMilkyWay), group (View)
#. +> trunk5
#: kstars.kcfg:602
#, 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:606
#, kde-format
msgid "Fill Milky Way contour? (false means use outline only)"
msgstr ""
#. i18n: ectx: whatsthis, entry (FillMilkyWay), group (View)
#. +> trunk5
#: kstars.kcfg:607
#, 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:611
#, kde-format
msgid "Meta-option for all planets in the sky map."
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowSolarSystem), group (View)
#. +> trunk5
#: kstars.kcfg:612
#, 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:616
#, kde-format
msgid "Draw planets as images in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowPlanetImages), group (View)
#. +> trunk5
#: kstars.kcfg:617
#, 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:621
#, kde-format
msgid "Label planet names in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowPlanetNames), group (View)
#. +> trunk5
#: kstars.kcfg:622
#, 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:626
#, kde-format
msgid "Draw Sun in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowSun), group (View)
#. +> trunk5
#: kstars.kcfg:627
#, kde-format
msgid "Toggle whether the Sun is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowMoon), group (View)
#. +> trunk5
#: kstars.kcfg:631
#, kde-format
msgid "Draw Moon in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowMoon), group (View)
#. +> trunk5
#: kstars.kcfg:632
#, kde-format
msgid "Toggle whether the Moon is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowMercury), group (View)
#. +> trunk5
#: kstars.kcfg:636
#, kde-format
msgid "Draw Mercury in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowMercury), group (View)
#. +> trunk5
#: kstars.kcfg:637
#, kde-format
msgid "Toggle whether Mercury is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowVenus), group (View)
#. +> trunk5
#: kstars.kcfg:641
#, kde-format
msgid "Draw Venus in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowVenus), group (View)
#. +> trunk5
#: kstars.kcfg:642
#, kde-format
msgid "Toggle whether Venus is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowMars), group (View)
#. +> trunk5
#: kstars.kcfg:646
#, kde-format
msgid "Draw Mars in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowMars), group (View)
#. +> trunk5
#: kstars.kcfg:647
#, kde-format
msgid "Toggle whether Mars is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowJupiter), group (View)
#. +> trunk5
#: kstars.kcfg:651
#, kde-format
msgid "Draw Jupiter in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowJupiter), group (View)
#. +> trunk5
#: kstars.kcfg:652
#, kde-format
msgid "Toggle whether Jupiter is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowSaturn), group (View)
#. +> trunk5
#: kstars.kcfg:656
#, kde-format
msgid "Draw Saturn in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowSaturn), group (View)
#. +> trunk5
#: kstars.kcfg:657
#, kde-format
msgid "Toggle whether Saturn is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowUranus), group (View)
#. +> trunk5
#: kstars.kcfg:661
#, kde-format
msgid "Draw Uranus in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowUranus), group (View)
#. +> trunk5
#: kstars.kcfg:662
#, kde-format
msgid "Toggle whether Uranus is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowNeptune), group (View)
#. +> trunk5
#: kstars.kcfg:666
#, kde-format
msgid "Draw Neptune in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowNeptune), group (View)
#. +> trunk5
#: kstars.kcfg:667
#, kde-format
msgid "Toggle whether Neptune is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowPluto), group (View)
#. +> trunk5
#: kstars.kcfg:671
#, kde-format
msgid "Draw Pluto in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowPluto), group (View)
#. +> trunk5
#: kstars.kcfg:672
#, kde-format
msgid "Toggle whether Pluto is drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowStars), group (View)
#. +> trunk5
#: kstars.kcfg:676
#, kde-format
msgid "Draw stars in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowStars), group (View)
#. +> trunk5
#: kstars.kcfg:677
#, kde-format
msgid "Toggle whether stars are drawn in the sky map."
msgstr ""
#. i18n: ectx: label, entry (ShowStarMagnitudes), group (View)
#. +> trunk5
#: kstars.kcfg:681
#, kde-format
msgid "Label star magnitudes in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowStarMagnitudes), group (View)
#. +> trunk5
#: kstars.kcfg:682
#, 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:686
#, kde-format
msgid "Label star names in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowStarNames), group (View)
#. +> trunk5
#: kstars.kcfg:687
#, 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:691
#, kde-format
msgid "Label deep-sky object magnitudes in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowDeepSkyMagnitudes), group (View)
#. +> trunk5
#: kstars.kcfg:692
#, 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:696
#, kde-format
msgid "Label deep-sky objects in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowDeepSkyNames), group (View)
#. +> trunk5
#: kstars.kcfg:697
#, 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:701
#, kde-format
msgid "Minimum timescale for forced-slewing mode"
msgstr ""
#. i18n: ectx: whatsthis, entry (SlewTimeScale), group (View)
#. +> trunk5
#: kstars.kcfg:702
#, 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:706
#, kde-format
msgid "InfoBoxes Background fill mode"
msgstr ""
#. i18n: ectx: whatsthis, entry (BoxBGMode), group (View)
#. +> trunk5
#: kstars.kcfg:707
#, 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:711
#, kde-format
msgid "Mapping projection algorithm"
msgstr ""
#. i18n: ectx: whatsthis, entry (Projection), group (View)
#. +> trunk5
#: kstars.kcfg:712
#, kde-format
msgid "Algorithm for the mapping projection."
msgstr ""
#. i18n: ectx: label, entry (UseAbbrevConstellNames), group (View)
#. +> trunk5
#: kstars.kcfg:716
#, kde-format
msgid "Use abbreviated constellation names?"
msgstr ""
#. i18n: ectx: whatsthis, entry (UseAbbrevConstellNames), group (View)
#. +> trunk5
#: kstars.kcfg:717
#, kde-format
msgid "Use official IAU abbreviations for constellation names."
msgstr ""
#. i18n: ectx: label, entry (UseLatinConstellNames), group (View)
#. +> trunk5
#: kstars.kcfg:721
#, kde-format
msgid "Use Latin constellation names?"
msgstr ""
#. i18n: ectx: whatsthis, entry (UseLatinConstellNames), group (View)
#. +> trunk5
#: kstars.kcfg:722
#, kde-format
msgid "Use Latin constellation names."
msgstr ""
#. i18n: ectx: label, entry (UseLocalConstellNames), group (View)
#. +> trunk5
#: kstars.kcfg:726
#, kde-format
msgid "Use localized constellation names?"
msgstr ""
#. i18n: ectx: whatsthis, entry (UseLocalConstellNames), group (View)
#. +> trunk5
#: kstars.kcfg:727
#, 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:731
#, kde-format
msgid "Use horizontal coordinate system?"
msgstr ""
#. i18n: ectx: whatsthis, entry (UseAltAz), group (View)
#. +> trunk5
#: kstars.kcfg:732
#, 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:736
#, kde-format
msgid "Automatically label focused object?"
msgstr ""
#. i18n: ectx: whatsthis, entry (UseAutoLabel), group (View)
#. +> trunk5
#: kstars.kcfg:737
#, 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:741 tools/scriptbuilder.cpp:701
#, kde-format
msgid "Automatically add trail to centered solar system body?"
msgstr ""
#. i18n: ectx: whatsthis, entry (UseAutoTrail), group (View)
#. +> trunk5
#: kstars.kcfg:742
#, 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:746
#, kde-format
msgid "Add temporary label on mouse hover?"
msgstr ""
#. i18n: ectx: whatsthis, entry (UseHoverLabel), group (View)
#. +> trunk5
#: kstars.kcfg:747
#, 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:751
#, kde-format
msgid "Correct positions for atmospheric refraction?"
msgstr ""
#. i18n: ectx: whatsthis, entry (UseRefraction), group (View)
#. +> trunk5
#: kstars.kcfg:752
#, 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:756
#, 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:757
#, 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:761
#, kde-format
msgid "Use antialiasing when drawing the screen?"
msgstr ""
#. i18n: ectx: whatsthis, entry (UseAntialias), group (View)
#. +> trunk5
#: kstars.kcfg:762
#, 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:766
#, kde-format
msgid "Zoom Factor, in pixels per radian"
msgstr ""
#. i18n: ectx: whatsthis, entry (ZoomFactor), group (View)
#. +> trunk5
#: kstars.kcfg:767
#, kde-format
msgid "The zoom level, measured in pixels per radian."
msgstr ""
#. i18n: ectx: label, entry (ZoomScrollFactor), group (View)
#. +> trunk5
#: kstars.kcfg:773
#, kde-format
msgid "Zoom scroll sensitivity."
msgstr ""
#. i18n: ectx: whatsthis, entry (ZoomScrollFactor), group (View)
#. +> trunk5
#: kstars.kcfg:774
#, 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:780
#, kde-format
msgid "Faint limit for asteroids"
msgstr ""
#. i18n: ectx: whatsthis, entry (MagLimitAsteroid), group (View)
#. +> trunk5
#: kstars.kcfg:781
#, kde-format
msgid "The faint magnitude limit for drawing asteroids."
msgstr ""
#. i18n: ectx: label, entry (MagLimitAsteroidDownload), group (View)
#. +> trunk5
#: kstars.kcfg:785
#, kde-format
msgid "Maximum magnitude for asteroids to be downloaded from JPL."
msgstr ""
#. i18n: ectx: whatsthis, entry (MagLimitAsteroidDownload), group (View)
#. +> trunk5
#: kstars.kcfg:786
#, 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:790
#, kde-format
msgid "Label density for asteroid names"
msgstr ""
#. i18n: ectx: whatsthis, entry (AsteroidLabelDensity), group (View)
#. +> trunk5
#: kstars.kcfg:791
#, 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:795
#, kde-format
msgid "Faint limit for deep-sky objects"
msgstr ""
#. i18n: ectx: whatsthis, entry (MagLimitDrawDeepSky), group (View)
#. +> trunk5
#: kstars.kcfg:796
#, 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:800
#, kde-format
msgid "Faint limit for deep-sky objects when zoomed out"
msgstr ""
#. i18n: ectx: whatsthis, entry (MagLimitDrawDeepSkyZoomOut), group (View)
#. +> trunk5
#: kstars.kcfg:801
#, 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:805
#, kde-format
msgid "Show deep-sky objects of unknown magnitude"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowUnknownMagObjects), group (View)
#. +> trunk5
#: kstars.kcfg:806
#, 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:811
#, kde-format
msgid "Faint limit for stars"
msgstr ""
#. i18n: ectx: whatsthis, entry (MagLimitDrawStar), group (View)
#. +> trunk5
#: kstars.kcfg:812
#, 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:816
#, kde-format
msgid "Density of stars in the field of view"
msgstr ""
#. i18n: ectx: whatsthis, entry (StarDensity), group (View)
#. +> trunk5
#: kstars.kcfg:817
#, kde-format
msgid "Sets the density of stars in the field of view"
msgstr ""
#. i18n: ectx: label, entry (MagLimitDrawStarZoomOut), group (View)
#. +> trunk5
#: kstars.kcfg:822
#, kde-format
msgid "Faint limit for stars when zoomed out"
msgstr ""
#. i18n: ectx: whatsthis, entry (MagLimitDrawStarZoomOut), group (View)
#. +> trunk5
#: kstars.kcfg:823
#, 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:828
#, kde-format
msgid "Faint limit for stars when slewing"
msgstr ""
#. i18n: ectx: whatsthis, entry (MagLimitHideStar), group (View)
#. +> trunk5
#: kstars.kcfg:829
#, 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:833
#, kde-format
msgid "Relative density for star name labels and/or magnitudes"
msgstr ""
#. i18n: ectx: whatsthis, entry (StarLabelDensity), group (View)
#. +> trunk5
#: kstars.kcfg:834
#, kde-format
msgid "The relative density for drawing star name and magnitude labels."
msgstr ""
#. i18n: ectx: label, entry (DeepSkyLabelDensity), group (View)
#. +> trunk5
#: kstars.kcfg:838
#, 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:839
#, 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:843
#, kde-format
msgid "Show long names in deep-sky object name labels?"
msgstr ""
#. i18n: ectx: whatsthis, entry (DeepSkyLongLabels), group (View)
#. +> trunk5
#: kstars.kcfg:844
#, 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:848
#, kde-format
msgid "Maximum distance from Sun for labeling comets, in AU"
msgstr ""
#. i18n: ectx: whatsthis, entry (MaxRadCometName), group (View)
#. +> trunk5
#: kstars.kcfg:849
#, kde-format
msgid "The maximum solar distance for drawing comets."
msgstr ""
#. i18n: ectx: label, entry (UseGL), group (View)
#. +> trunk5
#: kstars.kcfg:853
#, 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:858
#, kde-format
msgid "Run clock"
msgstr ""
#. i18n: ectx: whatsthis, entry (RunClock), group (View)
#. +> trunk5
#: kstars.kcfg:859
#, kde-format
msgid "The state of the clock (running or not)"
msgstr ""
#. i18n: ectx: label, entry (ObsListSymbol), group (ObservingList)
#. +> trunk5
#: kstars.kcfg:865
#, kde-format
msgid "Use symbols to label observing list objects"
msgstr ""
#. i18n: ectx: whatsthis, entry (ObsListSymbol), group (ObservingList)
#. +> trunk5
#: kstars.kcfg:866
#, 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:870
#, kde-format
msgid "Use text to label observing list objects"
msgstr ""
#. i18n: ectx: whatsthis, entry (ObsListText), group (ObservingList)
#. +> trunk5
#: kstars.kcfg:871
#, 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:875
#, kde-format
msgid "Prefer Digitized Sky Survey imagery in the observing list"
msgstr ""
#. i18n: ectx: whatsthis, entry (ObsListPreferDSS), group (ObservingList)
#. +> trunk5
#: kstars.kcfg:876
#, kde-format
msgid "The observing list will prefer DSS imagery while downloading imagery."
msgstr ""
#. i18n: ectx: label, entry (ObsListPreferSDSS), group (ObservingList)
#. +> trunk5
#: kstars.kcfg:880
#, kde-format
msgid "Prefer Sloan Digital Sky Survey imagery in the observing list"
msgstr ""
#. i18n: ectx: whatsthis, entry (ObsListPreferSDSS), group (ObservingList)
#. +> trunk5
#: kstars.kcfg:881
#, kde-format
msgid "The observing list will prefer SDSS imagery while downloading imagery."
msgstr ""
#. i18n: ectx: label, entry (ObsListDemoteHole), group (ObservingList)
#. +> trunk5
#: kstars.kcfg:885
#, 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:886
#, 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:890
#, 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:891
#, 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:1130
#, 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:1134 kstars.kcfg:1139
#, kde-format
msgid "Show GMT label"
msgstr ""
#. i18n: ectx: whatsthis, entry (XplanetLabelLocalTime), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1135
#, kde-format
msgid "Show local time."
msgstr ""
#. i18n: ectx: whatsthis, entry (XplanetLabelGMT), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1140
#, kde-format
msgid "Show GMT instead of local time."
msgstr ""
#. i18n: ectx: label, entry (XplanetLabelString), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1144
#, kde-format
msgid "Planet string"
msgstr ""
#. i18n: ectx: whatsthis, entry (XplanetLabelString), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1145
#, 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:1149
#, kde-format
msgid "Font Size"
msgstr ""
#. i18n: ectx: whatsthis, entry (XplanetFontSize), group (Xplanet)
#. i18n: ectx: label, entry (XplanetDateFormat), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1159
#, kde-format
msgid "Date format"
msgstr ""
#. i18n: ectx: whatsthis, entry (XplanetDateFormat), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1160
#, 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:1201
#, 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:1211
#, 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:1215
#, kde-format
msgid "Use background image"
msgstr ""
#. i18n: ectx: whatsthis, entry (XplanetBackgroundImage), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1216
#, kde-format
msgid "Use a file as the background image."
msgstr ""
#. i18n: ectx: label, entry (XplanetBackgroundImagePath), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1220
#, kde-format
msgid "Background image path"
msgstr ""
#. i18n: ectx: whatsthis, entry (XplanetBackgroundImagePath), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1221
#, kde-format
msgid "The path of the background image."
msgstr ""
#. i18n: ectx: label, entry (XplanetBackgroundColor), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1225
#, kde-format
msgid "Use background color"
msgstr ""
#. i18n: ectx: whatsthis, entry (XplanetBackgroundColor), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1226
#, 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:1240
#, kde-format
msgid "Arc file"
msgstr ""
#. i18n: ectx: whatsthis, entry (XplanetArcFile), group (Xplanet)
#. +> trunk5
#: kstars.kcfg:1241
#, 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:1245
#, 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:1329
#, 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:1333
#, kde-format
msgid "Default size for DSS images"
msgstr ""
#. i18n: ectx: whatsthis, entry (DefaultDSSImageSize), group (General)
#. +> trunk5
#: kstars.kcfg:1334
#, kde-format
msgid "The default size for DSS images downloaded from the Internet."
msgstr ""
#. i18n: ectx: label, entry (DSSPadding), group (General)
#. +> trunk5
#: kstars.kcfg:1338
#, kde-format
msgid "Additional padding around DSS Images of deep-sky objects"
msgstr ""
#. i18n: ectx: whatsthis, entry (DSSPadding), group (General)
#. +> trunk5
#: kstars.kcfg:1339
#, 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:1343
#, kde-format
msgid "Enable Verbose Logging"
msgstr ""
#. i18n: ectx: whatsthis, entry (VerboseLogging), group (General)
#. +> trunk5
#: kstars.kcfg:1344
#, 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:1348
#, kde-format
msgid "Enable Regular Logging"
msgstr ""
#. i18n: ectx: whatsthis, entry (RegularLogging), group (General)
#. +> trunk5
#: kstars.kcfg:1349
#, kde-format
msgid "Checking this option causes KStars to generate regular debug information."
msgstr ""
#. i18n: ectx: label, entry (DisableLogging), group (General)
#. +> trunk5
#: kstars.kcfg:1353
#, kde-format
msgid "Disable Verbose Logging"
msgstr ""
#. i18n: ectx: whatsthis, entry (DisableLogging), group (General)
#. +> trunk5
#: kstars.kcfg:1354
#, 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:1358
#, kde-format
msgid "Log debug message to default output"
msgstr ""
#. i18n: ectx: whatsthis, entry (LogToDefault), group (General)
#. +> trunk5
#: kstars.kcfg:1359
#, 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:1363
#, kde-format
msgid "Log debug message to a log file"
msgstr ""
#. i18n: ectx: whatsthis, entry (LogToFile), group (General)
#. +> trunk5
#: kstars.kcfg:1364
#, 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:1368
#, kde-format
msgid "Log FITS Data activity."
msgstr ""
#. i18n: ectx: whatsthis, entry (INDILogging), group (General)
#. +> trunk5
#: kstars.kcfg:1372
#, kde-format
msgid "Log INDI devices activity."
msgstr ""
#. i18n: ectx: whatsthis, entry (CaptureLogging), group (General)
#. +> trunk5
#: kstars.kcfg:1376
#, kde-format
msgid "Log Ekos Capture Module activity."
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusLogging), group (General)
#. +> trunk5
#: kstars.kcfg:1380
#, kde-format
msgid "Log Ekos Focus Module activity."
msgstr ""
#. i18n: ectx: whatsthis, entry (GuideLogging), group (General)
#. +> trunk5
#: kstars.kcfg:1384
#, kde-format
msgid "Log Ekos Guide Module activity."
msgstr ""
#. i18n: ectx: whatsthis, entry (AlignmentLogging), group (General)
#. +> trunk5
#: kstars.kcfg:1388
#, kde-format
msgid "Log Ekos Alignment Module activity."
msgstr ""
#. i18n: ectx: whatsthis, entry (MountLogging), group (General)
#. +> trunk5
#: kstars.kcfg:1392
#, kde-format
msgid "Log Ekos Mount Module activity."
msgstr ""
#. i18n: ectx: whatsthis, entry (ObservatoryLogging), group (General)
#. +> trunk5
#: kstars.kcfg:1396
#, kde-format
msgid "Log Ekos Observatory Module activity."
msgstr ""
#. i18n: ectx: label, entry (useFITSViewer), group (FITSViewer)
#. +> trunk5
#: kstars.kcfg:1402
#, kde-format
msgid "Display every image captured in a FITS Viewer window."
msgstr ""
#. i18n: ectx: label, entry (singlePreviewFITS), group (FITSViewer)
#. +> trunk5
#: kstars.kcfg:1406
#, kde-format
msgid "Preview FITS in a single tab?"
msgstr ""
#. i18n: ectx: label, entry (singleWindowCapturedFITS), group (FITSViewer)
#. +> trunk5
#: kstars.kcfg:1411
#, kde-format
msgid "Display all captured FITS in one window?"
msgstr ""
#. i18n: ectx: whatsthis, entry (singleWindowCapturedFITS), group (FITSViewer)
#. +> trunk5
#: kstars.kcfg:1412
#, 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:1416
#, kde-format
msgid "Display all opened FITS in one window?"
msgstr ""
#. i18n: ectx: whatsthis, entry (singleWindowOpenedFITS), group (FITSViewer)
#. +> trunk5
#: kstars.kcfg:1417
#, 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:1421
#, 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:1425
#, kde-format
msgid "Make FITS Viewer window independent of KStars main window"
msgstr ""
#. i18n: ectx: label, entry (AutoDebayer), group (FITSViewer)
#. +> trunk5
#: kstars.kcfg:1429
#, 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:1433
#, kde-format
msgid "Convert received non-FITS images to FITS for display purposes."
msgstr ""
#. i18n: ectx: label, entry (Auto3DCube), group (FITSViewer)
#. +> trunk5
#: kstars.kcfg:1437
#, 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:1441
#, 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:1445
#, 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:1451
#, kde-format
msgid "Bortle dark-sky rating"
msgstr ""
#. i18n: ectx: label, entry (TelescopeCheck), group (WISettings)
#. +> trunk5
#: kstars.kcfg:1455
#, kde-format
msgid "Availability of telescope"
msgstr ""
#. i18n: ectx: label, entry (BinocularsCheck), group (WISettings)
#. +> trunk5
#: kstars.kcfg:1459
#, kde-format
msgid "Availability of binoculars"
msgstr ""
#. i18n: ectx: label, entry (BinocularsAperture), group (WISettings)
#. +> trunk5
#: kstars.kcfg:1463
#, kde-format
msgid "Aperture of available binocular"
msgstr ""
#. i18n: ectx: label, entry (ScopeListIndex), group (WISettings)
#. +> trunk5
#: kstars.kcfg:1467
#, kde-format
msgid "Index of selected scope from list of scopes"
msgstr ""
#. i18n: ectx: label, entry (EkosWindowWidth), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1473
#, kde-format
msgid "Ekos window width"
msgstr ""
#. i18n: ectx: label, entry (EkosWindowHeight), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1477
#, kde-format
msgid "Ekos window height"
msgstr ""
#. i18n: ectx: label, entry (EkosLeftIcons), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1485
#, kde-format
msgid "Ekos modules icons are placed to the left of pages"
msgstr ""
#. i18n: ectx: label, entry (RememberCredentials), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1489
#, kde-format
msgid "Remember Ekos Live credentials."
msgstr ""
#. i18n: ectx: label, entry (AutoStartEkosLive), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1493
#, kde-format
msgid "Start Ekos Live on KStars startup."
msgstr ""
#. i18n: ectx: label, entry (EkosLiveOnline), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1497
#, kde-format
msgid "Whether EkosLive connection mode is online."
msgstr ""
#. i18n: ectx: label, entry (EkosLiveUsername), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1501
#, kde-format
msgid "EkosLive username"
msgstr ""
#. i18n: ectx: label, entry (independentWindowEkos), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1504
#, kde-format
msgid "Make Ekos window independent of KStars main window"
msgstr ""
#. i18n: ectx: label, entry (profile), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1508
#, kde-format
msgid "Ekos drivers profile"
msgstr ""
#. i18n: ectx: label, entry (neverLoadConfig), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1512
#, kde-format
msgid "Never load device configuration?"
msgstr ""
#. i18n: ectx: label, entry (loadConfigOnConnection), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1516
#, kde-format
msgid "Load device configuration upon successful connection?"
msgstr ""
#. i18n: ectx: label, entry (loadDefaultConfig), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1520
#, kde-format
msgid "Always load device default configuration upon successful connection?"
msgstr ""
#. i18n: ectx: label, entry (autoLoadSerialAssistant), group (Ekos)
#. +> trunk5
#: kstars.kcfg:1524
#, 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:1534
#, kde-format
msgid "List of CCDs with mechanical or electronic shutters."
msgstr ""
#. i18n: ectx: label, entry (shutterlessCCDs), group (DarkLibrary)
#. +> trunk5
#: kstars.kcfg:1537
#, kde-format
msgid "List of CCDs without mechanical or electronic shutters."
msgstr ""
#. i18n: ectx: label, entry (MinimumAltLimit), group (Mount)
#. +> trunk5
#: kstars.kcfg:1542
#, kde-format
msgid "Default minimum mount altitude limit"
msgstr ""
#. i18n: ectx: label, entry (MaximumAltLimit), group (Mount)
#. +> trunk5
#: kstars.kcfg:1547
#, kde-format
msgid "Default maximum mount altitude limit."
msgstr ""
#. i18n: ectx: whatsthis, entry (MaximumAltLimit), group (Mount)
#. +> trunk5
#: kstars.kcfg:1548
#, 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:1552
#, kde-format
msgid "Enable mount altitude limits."
msgstr ""
#. i18n: ectx: label, entry (MeridianFlipOffset), group (Mount)
#. +> trunk5
#: kstars.kcfg:1556
#, kde-format
msgid "Default hour angle to perform meridian flip"
msgstr ""
#. i18n: ectx: whatsthis, entry (MeridianFlipOffset), group (Mount)
#. +> trunk5
#: kstars.kcfg:1557
#, 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:1560
#, kde-format
msgid "Flips the mount when reaching the meridian, if supported."
msgstr ""
#. i18n: ectx: label, entry (MeridianFlipUnitDegrees), group (Mount)
#. +> trunk5
#: kstars.kcfg:1564
#, kde-format
msgid "Sets the display unit for meridian flip to degrees."
msgstr ""
#. i18n: ectx: label, entry (LeftRightReversed), group (Mount)
#. +> trunk5
#: kstars.kcfg:1568
#, kde-format
msgid "Reverse the direction of right and left buttons in mount control."
msgstr ""
#. i18n: ectx: label, entry (UpDownReversed), group (Mount)
#. +> trunk5
#: kstars.kcfg:1572
#, kde-format
msgid "Reverse the direction of up and down buttons in mount control."
msgstr ""
#. i18n: ectx: label, entry (ParkEveryDay), group (Mount)
#. +> trunk5
#: kstars.kcfg:1576
#, kde-format
msgid "Automatically start parking timer on startup."
msgstr ""
#. i18n: ectx: label, entry (ParkTime), group (Mount)
#. +> trunk5
#: kstars.kcfg:1580
#, kde-format
msgid "Park mount at this time in 12 hour format."
msgstr ""
#. i18n: ectx: label, entry (DefaultCaptureCCD), group (Capture)
#. +> trunk5
#: kstars.kcfg:1586
#, kde-format
msgid "Default capture module CCD."
msgstr ""
#. i18n: ectx: label, entry (DefaultCaptureFilterWheel), group (Capture)
#. +> trunk5
#: kstars.kcfg:1589
#, kde-format
msgid "Default capture module filter wheel."
msgstr ""
#. i18n: ectx: label, entry (DefaultObserver), group (Capture)
#. +> trunk5
#: kstars.kcfg:1592
#, kde-format
msgid "Default observer full name."
msgstr ""
#. i18n: ectx: label, entry (SyncFOVPA), group (Capture)
#. +> trunk5
#: kstars.kcfg:1595
#, kde-format
msgid "Sync FOV indicator Position Angle with Rotator Settings Position Angle"
msgstr ""
#. i18n: ectx: label, entry (PAMultiplier), group (Capture)
#. +> trunk5
#: kstars.kcfg:1599
#, kde-format
msgid "Position angle multiplier"
msgstr ""
#. i18n: ectx: label, entry (PAOffset), group (Capture)
#. +> trunk5
#: kstars.kcfg:1603
#, kde-format
msgid "Position angle offset"
msgstr ""
#. i18n: ectx: label, entry (GuideDeviation), group (Capture)
#. +> trunk5
#: kstars.kcfg:1607
#, kde-format
msgid "Default maximum permittable guide deviation"
msgstr ""
#. i18n: ectx: whatsthis, entry (GuideDeviation), group (Capture)
#. +> trunk5
#: kstars.kcfg:1608
#, 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:1612
#, kde-format
msgid "Default maximum permittable HFR deviation"
msgstr ""
#. i18n: ectx: whatsthis, entry (HFRDeviation), group (Capture)
#. +> trunk5
#: kstars.kcfg:1613
#, 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:1617
#, kde-format
msgid "Enforce guiding deviation limit."
msgstr ""
#. i18n: ectx: label, entry (EnforceAutofocus), group (Capture)
#. +> trunk5
#: kstars.kcfg:1621
#, kde-format
msgid "Enforce Autofocus HFR limit."
msgstr ""
#. i18n: ectx: label, entry (EnforceRefocusEveryN), group (Capture)
#. +> trunk5
#: kstars.kcfg:1625
#, kde-format
msgid "Enforce Refocus Every N Minutes."
msgstr ""
#. i18n: ectx: label, entry (RefocusEveryN), group (Capture)
#. +> trunk5
#: kstars.kcfg:1629
#, kde-format
msgid "Number of minute between forced refocus attempts"
msgstr ""
#. i18n: ectx: whatsthis, entry (RefocusEveryN), group (Capture)
#. +> trunk5
#: kstars.kcfg:1630
#, 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:1634
#, kde-format
msgid "Reset mount model after meridian flip."
msgstr ""
#. i18n: ectx: label, entry (CalibrationADUValue), group (Capture)
#. +> trunk5
#: kstars.kcfg:1638
#, kde-format
msgid "Desired flat field ADU"
msgstr ""
#. i18n: ectx: whatsthis, entry (CalibrationADUValue), group (Capture)
#. +> trunk5
#: kstars.kcfg:1639
#, 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:1643
#, kde-format
msgid "ADU Value tolerance"
msgstr ""
#. i18n: ectx: whatsthis, entry (CalibrationADUValueTolerance), group (Capture)
#. +> trunk5
#: kstars.kcfg:1644
#, 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:1648
#, kde-format
msgid "Index of flat source option."
msgstr ""
#. i18n: ectx: label, entry (CalibrationFlatDurationIndex), group (Capture)
#. +> trunk5
#: kstars.kcfg:1652
#, kde-format
msgid "Index of flat duration option."
msgstr ""
#. i18n: ectx: label, entry (CalibrationWallAz), group (Capture)
#. +> trunk5
#: kstars.kcfg:1656
#, kde-format
msgid "Azimuth of calibration wall location."
msgstr ""
#. i18n: ectx: label, entry (CalibrationWallAlt), group (Capture)
#. +> trunk5
#: kstars.kcfg:1660
#, kde-format
msgid "Altitude of calibration wall location."
msgstr ""
#. i18n: ectx: label, entry (MaxTemperatureDiff), group (Capture)
#. +> trunk5
#: kstars.kcfg:1664
#, kde-format
msgid "Maximum acceptable difference between requested and measured temperature set point."
msgstr ""
#. i18n: ectx: label, entry (GuidingSettle), group (Capture)
#. +> trunk5
#: kstars.kcfg:1668
#, 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:1676
#, 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:1680
#, 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:1684
#, kde-format
msgid "Calculate median focus value after each autofocus operation is complete."
msgstr ""
#. i18n: ectx: label, entry (SaveHFRToFile), group (Capture)
#. +> trunk5
#: kstars.kcfg:1688
#, 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:1700
#, kde-format
msgid "Perform auto stretch on captured images in FITS Viewer."
msgstr ""
#. i18n: ectx: label, entry (useSummaryPreview), group (Capture)
#. +> trunk5
#: kstars.kcfg:1704
#, 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:1708
#, kde-format
msgid "Display every captured DSLR image in the Image Viewer window."
msgstr ""
#. i18n: ectx: label, entry (ForceDSLRPresets), group (Capture)
#. +> trunk5
#: kstars.kcfg:1712
#, kde-format
msgid "Force exposure times to align with DSLR exposure presets. This insures accurate exposure times for sub-second exposures."
msgstr ""
#. i18n: ectx: label, entry (CaptureFormatIndex), group (Capture)
#. +> trunk5
#: kstars.kcfg:1716
#, kde-format
msgid "Index of desired capture format (FITS or Native)."
msgstr ""
#. i18n: ectx: label, entry (CaptureDirectory), group (Capture)
#. +> trunk5
#: kstars.kcfg:1720
#, kde-format
msgid "Path to capture directory to save images."
msgstr ""
#. i18n: ectx: label, entry (RemoteCaptureDirectory), group (Capture)
#. +> trunk5
#: kstars.kcfg:1724
#, kde-format
msgid "Path to remote capture directory to save images."
msgstr ""
#. i18n: ectx: label, entry (ManualCoverTimeout), group (Capture)
#. +> trunk5
#: kstars.kcfg:1727
#, kde-format
msgid "Cover or uncover telescope dialog timeout in seconds."
msgstr ""
#. i18n: ectx: label, entry (fileSettingsUseFilter), group (Capture)
#. +> trunk5
#: kstars.kcfg:1731
#, kde-format
msgid "Add the filter name to the capture file name."
msgstr ""
#. i18n: ectx: label, entry (fileSettingsUseDuration), group (Capture)
#. +> trunk5
#: kstars.kcfg:1735
#, kde-format
msgid "Add the capture duration to the capture file name."
msgstr ""
#. i18n: ectx: label, entry (fileSettingsUseTimestamp), group (Capture)
#. +> trunk5
#: kstars.kcfg:1739
#, kde-format
msgid "Add the capture timestamp to the capture file name."
msgstr ""
#. i18n: ectx: label, entry (DefaultFocusCCD), group (Focus)
#. +> trunk5
#: kstars.kcfg:1745
#, kde-format
msgid "Default focus module CCD."
msgstr ""
#. i18n: ectx: label, entry (DefaultFocusFocuser), group (Focus)
#. +> trunk5
#: kstars.kcfg:1748
#, kde-format
msgid "Default focus module focuser."
msgstr ""
#. i18n: ectx: label, entry (DefaultFocusFilterWheel), group (Focus)
#. +> trunk5
#: kstars.kcfg:1751
#, kde-format
msgid "Default focus module filter wheel."
msgstr ""
#. i18n: ectx: label, entry (FocusTicks), group (Focus)
#. +> trunk5
#: kstars.kcfg:1754
#, kde-format
msgid "Default Focuser step ticks"
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusTicks), group (Focus)
#. +> trunk5
#: kstars.kcfg:1755
#, 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:1759
#, 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:1763
#, kde-format
msgid "Wait for this many seconds after resuming guide."
msgstr ""
#. i18n: ectx: label, entry (FocusTolerance), group (Focus)
#. +> trunk5
#: kstars.kcfg:1767
#, kde-format
msgid "Default Focuser tolerance value"
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusTolerance), group (Focus)
#. +> trunk5
#: kstars.kcfg:1768
#, 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:1772
#, kde-format
msgid "Maximum Focus Travel Distance"
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusMaxTravel), group (Focus)
#. +> trunk5
#: kstars.kcfg:1773
#, kde-format
msgid "Set the maximum travel distance of an absolute focuser."
msgstr ""
#. i18n: ectx: label, entry (FocusGain), group (Focus)
#. +> trunk5
#: kstars.kcfg:1777
#, kde-format
msgid "Default Focuser gain value"
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusGain), group (Focus)
#. +> trunk5
#: kstars.kcfg:1778
#, 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:1782
#, kde-format
msgid "Default Focuser star selection box size"
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusBoxSize), group (Focus)
#. +> trunk5
#: kstars.kcfg:1783
#, kde-format
msgid "Set box size to select a focus star."
msgstr ""
#. i18n: ectx: label, entry (FocusXBin), group (Focus)
#. +> trunk5
#: kstars.kcfg:1787
#, kde-format
msgid "Default CCD X binning in focus mode"
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusXBin), group (Focus)
#. +> trunk5
#: kstars.kcfg:1788
#, kde-format
msgid "Set horizontal binning of CCD camera while in focus mode."
msgstr ""
#. i18n: ectx: label, entry (FocusYBin), group (Focus)
#. +> trunk5
#: kstars.kcfg:1792
#, kde-format
msgid "Default CCD Y binning in focus mode"
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusYBin), group (Focus)
#. +> trunk5
#: kstars.kcfg:1793
#, kde-format
msgid "Set vertical binning of CCD camera while in focus mode."
msgstr ""
#. i18n: ectx: label, entry (FocusSubFrame), group (Focus)
#. +> trunk5
#: kstars.kcfg:1797
#, kde-format
msgid "Subframe the focus star during the autofocus procedure."
msgstr ""
#. i18n: ectx: label, entry (FocusUseFullField), group (Focus)
#. +> trunk5
#: kstars.kcfg:1801
#, 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:1805
#, kde-format
msgid "Full field inner radius."
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusFullFieldInnerRadius), group (Focus)
#. +> trunk5
#: kstars.kcfg:1806
#, 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:1810
#, kde-format
msgid "Full field outer radius."
msgstr ""
#. i18n: ectx: whatsthis, entry (FocusFullFieldOuterRadius), group (Focus)
#. +> trunk5
#: kstars.kcfg:1811
#, 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:1815
#, kde-format
msgid "Automatically select a star to focus."
msgstr ""
#. i18n: ectx: label, entry (SuspendGuiding), group (Focus)
#. +> trunk5
#: kstars.kcfg:1819
#, kde-format
msgid "Suspend guiding while autofocus in progress."
msgstr ""
#. i18n: ectx: label, entry (UseFocusDarkFrame), group (Focus)
#. +> trunk5
#: kstars.kcfg:1823
#, 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:1827
#, kde-format
msgid "Image filter to be applied to focus image upon loading."
msgstr ""
#. i18n: ectx: label, entry (FocusThreshold), group (Focus)
#. +> trunk5
#: kstars.kcfg:1831
#, 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:1835
#, kde-format
msgid "Star detection algorithm"
msgstr ""
#. i18n: ectx: label, entry (FocusAlgorithm), group (Focus)
#. +> trunk5
#: kstars.kcfg:1839
#, kde-format
msgid "Focus process algorithm"
msgstr ""
#. i18n: ectx: label, entry (FocusFramesCount), group (Focus)
#. +> trunk5
#: kstars.kcfg:1843
#, kde-format
msgid "Number of focus frames to average for HFR calculations."
msgstr ""
#. i18n: ectx: label, entry (FocusMaxSingleStep), group (Focus)
#. +> trunk5
#: kstars.kcfg:1847
#, kde-format
msgid "Maximum single step the focus algorithm is permitted to command."
msgstr ""
#. i18n: ectx: label, entry (FocusExposure), group (Focus)
#. +> trunk5
#: kstars.kcfg:1851
#, kde-format
msgid "Default focus exposure time when no filters are used."
msgstr ""
#. i18n: ectx: label, entry (DefaultAlignCCD), group (Align)
#. +> trunk5
#: kstars.kcfg:1857
#, kde-format
msgid "Default align module CCD."
msgstr ""
#. i18n: ectx: label, entry (DefaultAlignFilterWheel), group (Align)
#. +> trunk5
#: kstars.kcfg:1860
#, kde-format
msgid "Default align module Filter Wheel."
msgstr ""
#. i18n: ectx: label, entry (AlignExposure), group (Align)
#. +> trunk5
#: kstars.kcfg:1863
#, kde-format
msgid "Default alignment exposure value"
msgstr ""
#. i18n: ectx: whatsthis, entry (AlignExposure), group (Align)
#. +> trunk5
#: kstars.kcfg:1864
#, 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:1868
#, kde-format
msgid "Default CCD binning index while in alignment mode"
msgstr ""
#. i18n: ectx: whatsthis, entry (SolverBinningIndex), group (Align)
#. +> trunk5
#: kstars.kcfg:1869
#, 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:1873
#, kde-format
msgid "Use rotator when performing load and slew."
msgstr ""
#. i18n: ectx: whatsthis, entry (AstrometryRotatorThreshold), group (Align)
#. +> trunk5
#: kstars.kcfg:1877
#, kde-format
msgid "Threshold between measured and FITS position angles in arcminutes to consider the load and slew operation successful."
msgstr ""
#. i18n: ectx: whatsthis, entry (SolverBackend), group (Align)
#. i18n: ectx: label, entry (AstrometrySolverType), group (Align)
#. +> trunk5
#: kstars.kcfg:1885
#, kde-format
msgid "Set astrometry.net solver type (online, offline, remote)."
msgstr ""
#. i18n: ectx: label, entry (SolverScopeType), group (Align)
#. +> trunk5
#: kstars.kcfg:1889
#, 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:1893
#, 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:1897
#, 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:1901
#, 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:1905
#, 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:1909
#, kde-format
msgid "Accuracy threshold in arcseconds between solution and target coordinates."
msgstr ""
#. i18n: ectx: label, entry (LockAlignFilterIndex), group (Align)
#. +> trunk5
#: kstars.kcfg:1913
#, 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:1917
#, 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:1921
#, 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:1925
#, 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:1941
#, kde-format
msgid "Lower image scale."
msgstr ""
#. i18n: ectx: label, entry (AstrometryImageScaleHigh), group (Align)
#. +> trunk5
#: kstars.kcfg:1944
#, kde-format
msgid "Upper image scale."
msgstr ""
#. i18n: ectx: label, entry (AstrometryAutoUpdateImageScale), group (Align)
#. +> trunk5
#: kstars.kcfg:1947
#, 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:1951
#, 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:1959
#, kde-format
msgid "Downsample factor"
msgstr ""
#. i18n: ectx: label, entry (AstrometryAutoDownsample), group (Align)
#. +> trunk5
#: kstars.kcfg:1963
#, kde-format
msgid "Automatically downsample based on image size."
msgstr ""
#. i18n: ectx: label, entry (AstrometryPositionRA), group (Align)
#. +> trunk5
#: kstars.kcfg:1971
#, 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:1974
#, 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:1977
#, 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:1992
#, kde-format
msgid "astrometry.net solve-field binary"
msgstr ""
#. i18n: ectx: whatsthis, entry (AstrometrySolverBinary), group (Align)
#. +> trunk5
#: kstars.kcfg:1993
#, kde-format
msgid "Path to astrometry.net solver location."
msgstr ""
#. i18n: ectx: label, entry (AstrometryWCSInfo), group (Align)
#. +> trunk5
#: kstars.kcfg:2001
#, kde-format
msgid "astrometry.net wcsinfo binary"
msgstr ""
#. i18n: ectx: whatsthis, entry (AstrometryWCSInfo), group (Align)
#. +> trunk5
#: kstars.kcfg:2002
#, kde-format
msgid "Path to astrometry.net wcsinfo location."
msgstr ""
#. i18n: ectx: label, entry (AstrometryConfFile), group (Align)
#. +> trunk5
#: kstars.kcfg:2010
#, kde-format
msgid "astrometry.net configuration file"
msgstr ""
#. i18n: ectx: whatsthis, entry (AstrometryConfFile), group (Align)
#. +> trunk5
#: kstars.kcfg:2011
#, kde-format
msgid "Path to astrometry.net file location."
msgstr ""
#. i18n: ectx: label, entry (AstrometryConfFileIsInternal), group (Align)
#. +> trunk5
#: kstars.kcfg:2015
#, kde-format
msgid "Internal or External Astrometry.net Conf File?"
msgstr ""
#. i18n: ectx: label, entry (UseDefaultPython), group (Align)
#. +> trunk5
#: kstars.kcfg:2019
#, kde-format
msgid "Use the Default System Python Path"
msgstr ""
#. i18n: ectx: whatsthis, entry (PythonExecPath), group (Align)
#. +> trunk5
#: kstars.kcfg:2024
#, kde-format
msgid "Folder in which the desired python executable or link to be used for astrometry.net resides."
msgstr ""
#. i18n: ectx: label, entry (UseSextractor), group (Align)
#. +> trunk5
#: kstars.kcfg:2029
#, kde-format
msgid "Use Sextractor to extract an xylist for plate solving with astrometry.net instead of python"
msgstr ""
#. i18n: ectx: whatsthis, entry (SextractorBinary), group (Align)
#. +> trunk5
#: kstars.kcfg:2038
#, kde-format
msgid "Path to the Sextractor executable."
msgstr ""
#. i18n: ectx: label, entry (AstrometryAPIKey), group (Align)
#. +> trunk5
#: kstars.kcfg:2043
#, kde-format
msgid "astrometry.net API Key"
msgstr ""
#. i18n: ectx: whatsthis, entry (AstrometryAPIKey), group (Align)
#. +> trunk5
#: kstars.kcfg:2044
#, 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:2048
#, kde-format
msgid "astrometry.net API URL"
msgstr ""
#. i18n: ectx: label, entry (AstrometryUseJPEG), group (Align)
#. +> trunk5
#: kstars.kcfg:2052
#, 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:2056
#, kde-format
msgid "Timeout in seconds to wait for astrometry solver to complete."
msgstr ""
#. i18n: ectx: label, entry (PAHMountSpeedIndex), group (Align)
#. +> trunk5
#: kstars.kcfg:2060
#, kde-format
msgid "Speed index to set mount in Polar Alignment Assistant Tool."
msgstr ""
#. i18n: ectx: label, entry (PAHAutoPark), group (Align)
#. +> trunk5
#: kstars.kcfg:2064
#, kde-format
msgid "Automatically park the mount after Polar Alignment Assistant Tool is complete."
msgstr ""
#. i18n: ectx: label, entry (PAHFlipCorrectionVector), group (Align)
#. +> trunk5
#: kstars.kcfg:2068
#, kde-format
msgid "Flip correction vector."
msgstr ""
#. i18n: ectx: label, entry (DefaultGuideCCD), group (Guide)
#. +> trunk5
#: kstars.kcfg:2074
#, kde-format
msgid "Default guide module CCD."
msgstr ""
#. i18n: ectx: label, entry (DefaultST4Driver), group (Guide)
#. +> trunk5
#: kstars.kcfg:2077
#, kde-format
msgid "Default guide module ST4 Driver."
msgstr ""
#. i18n: ectx: label, entry (GuideExposure), group (Guide)
#. +> trunk5
#: kstars.kcfg:2080
#, kde-format
msgid "Guider exposure duration in seconds."
msgstr ""
#. i18n: ectx: label, entry (GuiderType), group (Guide)
#. +> trunk5
#: kstars.kcfg:2084
#, 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:2088
#, 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:2092
#, kde-format
msgid "Host name of external PHD2 service"
msgstr ""
#. i18n: ectx: label, entry (PHD2Port), group (Guide)
#. +> trunk5
#: kstars.kcfg:2096
#, kde-format
msgid "PHD2 Event Monitoring Port"
msgstr ""
#. i18n: ectx: label, entry (LinGuiderHost), group (Guide)
#. +> trunk5
#: kstars.kcfg:2100
#, kde-format
msgid "Host name of external lin_guider service"
msgstr ""
#. i18n: ectx: label, entry (LinGuiderPort), group (Guide)
#. +> trunk5
#: kstars.kcfg:2104
#, kde-format
msgid "Lin_guider Event Monitoring Port"
msgstr ""
#. i18n: ectx: label, entry (GuideScopeType), group (Guide)
#. +> trunk5
#: kstars.kcfg:2108
#, 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:2112
#, 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:2116
#, 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:2120
#, kde-format
msgid "Use Image Guiding algorithms instead of classical centroid guiding."
msgstr ""
#. i18n: ectx: label, entry (GuideRegionAxis), group (Guide)
#. +> trunk5
#: kstars.kcfg:2124
#, 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:2128
#, kde-format
msgid "Automatically select calibration star and perform calibration."
msgstr ""
#. i18n: ectx: label, entry (AutoModeIterations), group (Guide)
#. +> trunk5
#: kstars.kcfg:2136
#, kde-format
msgid "Number of automode iterations for calibration process."
msgstr ""
#. i18n: ectx: label, entry (GuideLostStarTimeout), group (Guide)
#. +> trunk5
#: kstars.kcfg:2140
#, 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:2144
#, kde-format
msgid "Maximum delta RMS permitted while guiding before aborting."
msgstr ""
#. i18n: ectx: label, entry (TwoAxisEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2148
#, kde-format
msgid "Use both axes to perform calibration."
msgstr ""
#. i18n: ectx: label, entry (RapidGuideEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2152
#, kde-format
msgid "Use driver side Rapid Guide to perform guiding."
msgstr ""
#. i18n: ectx: label, entry (GuideDarkFrameEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2156
#, kde-format
msgid "Take dark frame for autoguider images."
msgstr ""
#. i18n: ectx: label, entry (GuideSubframeEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2160
#, kde-format
msgid "Subframe guide image around selected region"
msgstr ""
#. i18n: ectx: label, entry (DitherPixels), group (Guide)
#. +> trunk5
#: kstars.kcfg:2164
#, 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:2168
#, kde-format
msgid "Dither after this many frames."
msgstr ""
#. i18n: ectx: label, entry (DitherThreshold), group (Guide)
#. +> trunk5
#: kstars.kcfg:2176
#, kde-format
msgid "Maximum distance (pixels) for guiding to be considered settled."
msgstr ""
#. i18n: ectx: label, entry (DitherTimeout), group (Guide)
#. +> trunk5
#: kstars.kcfg:2180
#, kde-format
msgid "Time limit (seconds) on dithering to settle down."
msgstr ""
#. i18n: ectx: label, entry (DitherMaxIterations), group (Guide)
#. +> trunk5
#: kstars.kcfg:2184
#, kde-format
msgid "How many dithering attempts to undertake before giving up."
msgstr ""
#. i18n: ectx: label, entry (DitherNoGuidingPulse), group (Guide)
#. +> trunk5
#: kstars.kcfg:2188
#, kde-format
msgid "Pulse length in milliseconds used for non-guiding dither."
msgstr ""
#. i18n: ectx: label, entry (DitherFailAbortsAutoGuide), group (Guide)
#. +> trunk5
#: kstars.kcfg:2192
#, kde-format
msgid "If dithering fails then abort autoguide."
msgstr ""
#. i18n: ectx: label, entry (DitherEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2196
#, kde-format
msgid "Use Auto Dithering when guiding."
msgstr ""
#. i18n: ectx: label, entry (DitherNoGuiding), group (Guide)
#. +> trunk5
#: kstars.kcfg:2200
#, kde-format
msgid "Perform dithering even when not guiding."
msgstr ""
#. i18n: ectx: label, entry (AOLimit), group (Guide)
#. +> trunk5
#: kstars.kcfg:2204
#, 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:2208
#, kde-format
msgid "Enable autoguiding in the RA axis."
msgstr ""
#. i18n: ectx: label, entry (DECGuideEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2212
#, kde-format
msgid "Enable autoguiding in the DEC axis."
msgstr ""
#. i18n: ectx: label, entry (NorthDECGuideEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2216
#, kde-format
msgid "Enable North autoguiding in the DEC axis."
msgstr ""
#. i18n: ectx: label, entry (SouthDECGuideEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2220
#, kde-format
msgid "Enable South autoguiding in the DEC axis."
msgstr ""
#. i18n: ectx: label, entry (EastRAGuideEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2224
#, kde-format
msgid "Enable East autoguiding in the RA axis."
msgstr ""
#. i18n: ectx: label, entry (WestRAGuideEnabled), group (Guide)
#. +> trunk5
#: kstars.kcfg:2228
#, kde-format
msgid "Enable West autoguiding in the RA axis."
msgstr ""
#. i18n: ectx: label, entry (GuiderAccuracyThreshold), group (Guide)
#. +> trunk5
#: kstars.kcfg:2265
#, kde-format
msgid "Accuracy threshold for the Guide Graphs."
msgstr ""
#. i18n: ectx: label, entry (RADisplayedOnGuideGraph), group (Guide)
#. +> trunk5
#: kstars.kcfg:2269
#, kde-format
msgid "Display the RA Plot on the Guide Drift Graphics."
msgstr ""
#. i18n: ectx: label, entry (DEDisplayedOnGuideGraph), group (Guide)
#. +> trunk5
#: kstars.kcfg:2273
#, kde-format
msgid "Display the DEC Plot on the Guide Drift Graphics."
msgstr ""
#. i18n: ectx: label, entry (RACorrDisplayedOnGuideGraph), group (Guide)
#. +> trunk5
#: kstars.kcfg:2277
#, kde-format
msgid "Display the RA Corrections Plot on the Guide Drift Graphics."
msgstr ""
#. i18n: ectx: label, entry (DECorrDisplayedOnGuideGraph), group (Guide)
#. +> trunk5
#: kstars.kcfg:2281
#, kde-format
msgid "Display the DEC Corrections Plot on the Guide Drift Graphics."
msgstr ""
#. i18n: ectx: whatsthis, entry (SchedulerLogging), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2287
#, kde-format
msgid "Log Ekos Scheduler Module activity."
msgstr ""
#. i18n: ectx: whatsthis, entry (SortSchedulerJobs), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2291
#, kde-format
msgid "Sort scheduler jobs by priority and altitude."
msgstr ""
#. i18n: ectx: label, entry (StopEkosAfterShutdown), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2295
#, kde-format
msgid "After shutdown procedure is successfully executed, shutdown INDI and Ekos."
msgstr ""
#. i18n: ectx: label, entry (ShutdownScriptTerminatesINDI), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2299
#, 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:2303
#, 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:2307
#, kde-format
msgid "Reset mount model in case of alignment failure."
msgstr ""
#. i18n: ectx: label, entry (ResetMountModelBeforeJob), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2311
#, kde-format
msgid "Reset mount model before starting each job."
msgstr ""
#. i18n: ectx: label, entry (ResetGuideCalibration), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2315
#, kde-format
msgid "Always Reset guiding calibration before starting each job."
msgstr ""
#. i18n: ectx: label, entry (RealignAfterCalibrationFailure), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2319
#, 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:2323
#, 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:2327
#, 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:2331
#, kde-format
msgid "Minimum time between jobs in minutes."
msgstr ""
#. i18n: ectx: label, entry (PreDawnTime), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2335
#, 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:2339
#, 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 (DawnOffset), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2343
#, kde-format
msgid "Offset astronomical dawn by this many hours to relax twilight restriction when using narrowband filters."
msgstr ""
#. i18n: ectx: label, entry (DuskOffset), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2347
#, kde-format
msgid "Offset astronomical dusk by this many hours to relax twilight restriction when using narrowband filters."
msgstr ""
#. i18n: ectx: label, entry (TelescopeFocalLength), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2351
#, kde-format
msgid "Telescope focal length in millimeters."
msgstr ""
#. i18n: ectx: label, entry (CameraPixelWidth), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2355
#, kde-format
msgid "Camera pixel size width in micrometers."
msgstr ""
#. i18n: ectx: label, entry (CameraPixelHeight), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2359
#, kde-format
msgid "Camera pixel size height in micrometers."
msgstr ""
#. i18n: ectx: label, entry (CameraWidth), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2363
#, kde-format
msgid "Camera Width in pixels."
msgstr ""
#. i18n: ectx: label, entry (CameraHeight), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2367
#, kde-format
msgid "Camera Height in pixels."
msgstr ""
#. i18n: ectx: label, entry (CameraRotation), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2371
#, kde-format
msgid "Position angle of the camera with respect to north."
msgstr ""
#. i18n: ectx: label, entry (ErrorHandlingStrategy), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2375
#, kde-format
msgid "Strategy how to react, when a job aborts or steps into an error."
msgstr ""
#. i18n: ectx: label, entry (ErrorHandlingStrategyDelay), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2379
#, kde-format
msgid "Delay in minutes how long the scheduler should pause before restarting an aborted job or a job that ran into an error."
msgstr ""
#. i18n: ectx: label, entry (RescheduleErrors), group (Scheduler)
#. +> trunk5
#: kstars.kcfg:2383
#, kde-format
msgid "Re-schedule jobs that ran into errors."
msgstr ""
#. i18n: ectx: label, entry (LastServer), group (INDI Lite)
#. +> trunk5
#: kstars.kcfg:2389
#, kde-format
msgid "The address of last used server"
msgstr ""
#. i18n: ectx: label, entry (LastServerPort), group (INDI Lite)
#. +> trunk5
#: kstars.kcfg:2392
#, kde-format
msgid "The port of last used server"
msgstr ""
#. i18n: ectx: label, entry (LastWebManagerPort), group (INDI Lite)
#. +> trunk5
#: kstars.kcfg:2396
#, kde-format
msgid "The port of last used Web Manager"
msgstr ""
#. i18n: ectx: label, entry (HIPSMemoryCache), group (HIPS)
#. +> trunk5
#: kstars.kcfg:2402
#, 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:2406
#, 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:2410
#, kde-format
msgid "HIPS source catalog title."
msgstr ""
#. i18n: ectx: label, entry (HIPSBiLinearInterpolation), group (HIPS)
#. +> trunk5
#: kstars.kcfg:2414
#, kde-format
msgid "Use Bilinear interpolation when rendering HiPS images?"
msgstr ""
#. i18n: ectx: label, entry (HIPSShowGrid), group (HIPS)
#. +> trunk5
#: kstars.kcfg:2418
#, kde-format
msgid "Show HiPS grid on the sky map."
msgstr ""
#. i18n: ectx: label, entry (HIPSPanning), group (HIPS)
#. +> trunk5
#: kstars.kcfg:2422
#, kde-format
msgid "Redraw HiPS while panning."
msgstr ""
#. i18n: ectx: label, entry (ShowHIPS), group (HIPS)
#. +> trunk5
#: kstars.kcfg:2426
#, kde-format
msgid "Draw HiPS sources in the sky map?"
msgstr ""
#. i18n: ectx: whatsthis, entry (ShowHIPS), group (HIPS)
#. +> trunk5
#: kstars.kcfg:2427
#, 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:2433
#, kde-format
msgid "Will be reacted upon warnings?"
msgstr ""
#. i18n: ectx: label, entry (alertActionsActive), group (Observatory)
#. +> trunk5
#: kstars.kcfg:2437
#, kde-format
msgid "Will be reacted upon alerts?"
msgstr ""
#. i18n: ectx: label, entry (weatherWarningCloseDome), group (Observatory)
#. +> trunk5
#: kstars.kcfg:2441
#, kde-format
msgid "Shall the dome being closed when a weather warning occurs?"
msgstr ""
#. i18n: ectx: label, entry (weatherWarningCloseShutter), group (Observatory)
#. +> trunk5
#: kstars.kcfg:2445
#, 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)
"<p>The ICC profiles folder seems to be invalid.</p>"
"<p>If you want to try setting it again, choose \"Yes\" here, otherwise choose \"No\", and the \"Color Management\" feature will be disabled until you solve this issue.</p>"
msgid "Edit album properties and collection information."
msgstr ""
#. +> trunk5
#: core/app/main/digikamapp_setup.cpp:233
#, kde-format
msgid "Write Metadata to Files"
msgstr ""
#. +> trunk5
#: core/app/main/digikamapp_setup.cpp:234
#: core/app/main/digikamapp_setup.cpp:393
#, kde-format
msgid "Updates metadata of files in the current album with the contents of digiKam database (file metadata will be overwritten with data from the database)."
msgstr ""
#. +> trunk5
#: core/app/main/digikamapp_setup.cpp:243
#, kde-format
msgid "Reread Metadata From Files"
msgstr ""
#. +> trunk5
#: core/app/main/digikamapp_setup.cpp:244
#: core/app/main/digikamapp_setup.cpp:404
#, kde-format
msgid "Updates the digiKam database from the metadata of the files in the current album (information in the database will be overwritten with data from the files' metadata)."
msgid "Open camera dialog for the device with Solid UDI <udi>"
msgstr ""
#. +> trunk5
#: core/app/main/main.cpp:155
#, kde-format
msgid "Automatically detect and open a connected gphoto2 camera"
msgstr ""
#. +> trunk5
#: core/app/main/main.cpp:157
#, kde-format
msgid "Start digikam with the SQLite database file found in the directory <dir>"
msgstr ""
#. +> trunk5
#: core/app/main/main.cpp:160
#, kde-format
msgid "Start digikam with the configuration file <config>"
msgstr ""
#. +> trunk5
#: core/app/main/main.cpp:181
#, kde-format
msgid ""
"Run-time Qt SQLite or MySQL database plugin is not available. please install it.\n"
"There is no database plugin installed on your computer."
msgstr ""
#. +> trunk5
#: core/app/main/main.cpp:190
#, kde-format
msgid ""
"Run-time Qt SQLite or MySQL database plugin are not available. Please install it.\n"
"Database plugins installed on your computer are listed below."
msgstr ""
#. +> trunk5
#: core/app/main/main.cpp:228
#, kde-format
msgid "<p>The given path for the config file is not valid. Either its parent directory does not exist, it is a directory itself or it cannot be read/written to.</p>"
msgid_plural "Are you sure you want to restore %1 items?"
msgstr[0] ""
msgstr[1] ""
#. +> trunk5
#: core/app/views/stack/trashview.cpp:267
#, kde-format
msgid "Confirm Restore"
msgstr ""
#. +> trunk5
#: core/app/views/stack/trashview.cpp:315
#: core/app/views/stack/trashview.cpp:361
#, kde-format
msgid "Confirm Deletion"
msgstr ""
#. +> trunk5
#: core/app/views/stack/trashview.cpp:316
#, kde-format
msgid "Are you sure you want to delete %1 item permanently?"
msgid_plural "Are you sure you want to delete %1 items permanently?"
msgstr[0] ""
msgstr[1] ""
#. +> trunk5
#: core/app/views/stack/trashview.cpp:362
#, kde-format
msgid "Are you sure you want to delete ALL items permanently?"
msgstr ""
#. +> trunk5
#: core/app/views/stack/trashview.cpp:451
#, kde-format
msgid "%1/%2 items selected"
msgstr ""
#. +> trunk5
#: core/app/views/stack/welcomepageview.cpp:142
#, kde-format
msgid "New Neural Network engine based on OpenCV Deep Learning module to detect and recognize faces."
msgstr ""
#. +> trunk5
#: core/app/views/stack/welcomepageview.cpp:143
#, kde-format
msgid "Update Slideshow to plugin."
msgstr ""
#. +> trunk5
#: core/app/views/stack/welcomepageview.cpp:144
#, kde-format
msgid "Add new theme Html5Responsive for HtmlGallery plugin."
msgstr ""
#. +> trunk5
#: core/app/views/stack/welcomepageview.cpp:145
#, kde-format
msgid "Update internal RAW engine to last Libraw 0.20.0 release including Canon CR3 and Sony A7R4 support."
msgstr ""
#. +> trunk5
#: core/app/views/stack/welcomepageview.cpp:146
#, kde-format
msgid "Face Scan dialog contents is now simplified and embedded into left sidebar."
msgstr ""
#. +> trunk5
#: core/app/views/stack/welcomepageview.cpp:149
#, kde-format
msgid "...and much more."
msgstr ""
#. +> trunk5
#: core/app/views/stack/welcomepageview.cpp:155
#, kde-format
msgid ""
"<li>%1</li>"
"\n"
msgstr ""
#. +> trunk5
#: core/app/views/stack/welcomepageview.cpp:158
#, kde-format
msgid "New Features"
msgstr ""
#. +> trunk5
#: core/app/views/stack/welcomepageview.cpp:160
#, kde-format
msgid ""
"<h3>%1</h3>"
"<ul>%2</ul>"
msgstr ""
#. +> trunk5
#: core/app/views/stack/welcomepageview.cpp:161
#, kde-format
msgid "Some of the new features in this release of digiKam include (compared to digiKam 6.x):"
msgstr ""
#. +> trunk5
#: core/app/views/stack/welcomepageview.cpp:170
#, kde-format
msgid "About"
msgstr ""
#. +> trunk5
#: core/app/views/stack/welcomepageview.cpp:172
#, kde-format
msgid ""
"<h3>%1</h3>"
"<h3>%2</h3>"
"<ul>%3</ul>"
msgstr ""
#. +> trunk5
#: core/app/views/stack/welcomepageview.cpp:173
#, kde-format
msgid "digiKam is an open source photo management program designed to import, organize, enhance, search and export your digital images to and from your computer."
msgstr ""
#. +> trunk5
#: core/app/views/stack/welcomepageview.cpp:174
#, kde-format
msgid "Currently, you are in the Album view mode of digiKam. Albums are the places where your files are stored, and are identical to the folders on your hard disk."
msgstr ""
#. +> trunk5
#: core/app/views/stack/welcomepageview.cpp:175
#, kde-format
msgid ""
"<li>%1</li>"
"<li>%2</li>"
msgstr ""
#. +> trunk5
#: core/app/views/stack/welcomepageview.cpp:176
#, kde-format
msgid "digiKam has many powerful features which are described in the <a href=\"https://docs.kde.org/trunk5/en/extragear-graphics/digikam/index.html\">documentation</a>"
msgstr ""
#. +> trunk5
#: core/app/views/stack/welcomepageview.cpp:177
#, kde-format
msgid "The <a href=\"https://www.digikam.org\">digiKam homepage</a> provides information about new versions of digiKam."
"<p>This Batch Queue Manager tool can convert images data to HEIF format.</p>"
"<p>High Efficiency Image File Format (HEIF), also known as High Efficiency Image Coding (HEIC), is a file format for individual images and image sequences. It was developed by the Moving Picture Experts Group (MPEG) and it claims that twice as much information can be stored in a HEIF image as in a JPEG image of the same size, resulting in a better quality image. HEIF also supports animation, and is capable of storing more information than an animated GIF at a small fraction of the size.</p>"
"<p>See <a href='https://en.wikipedia.org/wiki/High_Efficiency_Image_File_Format'>High Efficiency Image File Format</a> for details.</p>"
"<p>This Batch Queue Manager tool can convert images data to JPEG-2000 format.</p>"
"<p>This is an image compression standard and coding system. It was created by the Joint Photographic Experts Group committee in 2000 with the intention of superseding their original discrete cosine transform-based JPEG standard (created in 1992) with a newly designed, wavelet-based method.</p>"
"<p>See details about this format from <a href='https://en.wikipedia.org/wiki/JPEG_2000'>this page</a>.</p>"
"<p>This Batch Queue Manager tool can convert images data to JPEG format.</p>"
"<p>The Joint Photographic Experts Group format is a commonly used method of lossy compression for digital images, particularly for those images produced by digital photography.</p>"
"<p>See details about this format from <a href='https://en.wikipedia.org/wiki/JPEG'>this page</a>.</p>"
msgid "<b>If conversion to PNG fails, this may be due to the color profile check. Simply insert the tool for color profile conversion before this tool and select the desired color profile.</b>"
"<p>This Batch Queue Manager tool can convert images data to TIFF format.</p>"
"<p>The Tagged Image File Format is a computer file format for storing raster graphics images, popular among graphic artists, the publishing industry, and photographers.</p>"
"<p>See details about this format from <a href='https://en.wikipedia.org/wiki/TIFF'>this page</a>.</p>"
msgid "Enter script for execution. Use $INPUT and $OUTPUT for input / output filenames (with special characters escaped). These would be substituted before shell execution."
msgid "When you choose to have the watermark repeated randomly in the placement combo box, you can specify here to randomly rotate the watermark (0, 90, 180, 270 degrees)."
msgid "Use this to get more control over the sparsity of watermark repetition. The higher the value the sparser the watermarks get. Use floating point values, typically between 1.0 and 3.0. It can also be less than 1.0"
msgid "<p>This Batch Queue Manager tool can rotate images.</p>"
msgstr ""
#. +> trunk5
#: core/dplugins/dimg/heif/dimgheifplugin.cpp:58
#, kde-format
msgid "HEIF loader"
msgstr ""
#. +> trunk5
#: core/dplugins/dimg/heif/dimgheifplugin.cpp:73
#, kde-format
msgid "An image loader based on Libheif codec"
msgstr ""
#. +> trunk5
#: core/dplugins/dimg/heif/dimgheifplugin.cpp:78
#, kde-format
msgid "This library is not present on your system."
msgstr ""
#. +> trunk5
#: core/dplugins/dimg/heif/dimgheifplugin.cpp:86
#, kde-format
msgid "This library is available on your system with a maximum color depth support of %1 bits."
msgstr ""
#. +> trunk5
#: core/dplugins/dimg/heif/dimgheifplugin.cpp:91
#, kde-format
msgid "This library is available on your system but is not able to encode image with a suitable color depth."
msgstr ""
#. +> trunk5
#: core/dplugins/dimg/heif/dimgheifplugin.cpp:97
#, kde-format
msgid ""
"<p>This plugin permit to load and save image using Libheif codec.</p>"
"<p>High Efficiency Image File Format (HEIF), also known as High Efficiency Image Coding (HEIC), is a file format for individual images and image sequences. It was developed by the Moving Picture Experts Group (MPEG) and it claims that twice as much information can be stored in a HEIF image as in a JPEG image of the same size, resulting in a better quality image. HEIF also supports animation, and is capable of storing more information than an animated GIF at a small fraction of the size.</p>"
"<p>Encoding HEIC is relevant of optional libde265 codec. %1</p>"
"<p>See <a href='https://en.wikipedia.org/wiki/High_Efficiency_Image_File_Format'>High Efficiency Image File Format</a> for details.</p>"
"<p>This plugin permit to load and save image using ImageMagick coders.</p>"
"<p>ImageMagick is a free and open-source software suite for converting raster image and vector image files. It can read and write over 200 image file formats.</p>"
"<p>See <a href='https://en.wikipedia.org/wiki/ImageMagick'>ImageMagick documentation</a> for details.</p>"
msgstr ""
#. +> trunk5
#: core/dplugins/dimg/jpeg/dimgjpegplugin.cpp:57
#, kde-format
msgid "JPEG loader"
msgstr ""
#. +> trunk5
#: core/dplugins/dimg/jpeg/dimgjpegplugin.cpp:72
#, kde-format
msgid "An image loader based on Libjpeg codec"
msgstr ""
#. +> trunk5
#: core/dplugins/dimg/jpeg/dimgjpegplugin.cpp:77
#, kde-format
msgid ""
"<p>This plugin permit to load and save image using Libjpeg codec.</p>"
"<p>Joint Photographic Experts Group (JPEG) is a commonly used method of lossy compression for digital images, particularly for those images produced by digital photography. The degree of compression can be adjusted, allowing a selectable tradeoff between storage size and image quality.</p>"
"<p>See <a href='https://en.wikipedia.org/wiki/JPEG'>Joint Photographic Experts Group documentation</a> for details.</p>"
"<p>This plugin permit to load and save image using Libjasper codec</p>"
"<p>The JPEG (Joint Photographic Experts Group) 2000 standard, finalized in 2001, defines a image-coding scheme using state-of-the-art compression techniques based on wavelet technology. Its architecture is useful for many diverse applications, including image archiving, security systems, digital photography, and medical imaging.</p>"
"<p>See <a href='https://en.wikipedia.org/wiki/JPEG_2000'>Joint Photographic Experts Group documentation</a> for details.</p>"
"<p>This plugin permit to load and save image using Libpgf codec.</p>"
"<p>The Progressive Graphics File (PGF) is an efficient image file format, that is based on a fast, discrete wavelet transform with progressive coding features. PGF can be used for lossless and lossy compression. It's most suitable for natural images. PGF can be used as a very efficient and fast replacement of JPEG-2000.</p>"
"<p>See <a href='https://en.wikipedia.org/wiki/Progressive_Graphics_File'>Progressive Graphics File documentation</a> for details.</p>"
msgstr ""
#. +> trunk5
#: core/dplugins/dimg/pgf/dimgpgfplugin.cpp:104
#, kde-format
msgid "Progressive Graphics File"
msgstr ""
#. +> trunk5
#: core/dplugins/dimg/png/dimgpngplugin.cpp:57
#, kde-format
msgid "PNG loader"
msgstr ""
#. +> trunk5
#: core/dplugins/dimg/png/dimgpngplugin.cpp:72
#, kde-format
msgid "An image loader based on Libpng codec"
msgstr ""
#. +> trunk5
#: core/dplugins/dimg/png/dimgpngplugin.cpp:77
#, kde-format
msgid ""
"<p>This plugin permit to load and save image using Libpng codec.</p>"
"<p>Portable Network Graphics (PNG) is a raster-graphics file-format that supports lossless data compression. PNG was developed as an improved, non-patented replacement for Graphics Interchange Format.</p>"
"<p>See <a href='https://en.wikipedia.org/wiki/Portable_Network_Graphics'>Portable Network Graphics documentation</a> for details.</p>"
"<p>This plugin permit to load and save image using QImage plugins from Qt Framework.</p>"
"<p>See <a href='https://doc.qt.io/qt-5/qimage.html'>Qt Framework documentation</a> for details.</p>"
msgstr ""
#. +> trunk5
#: core/dplugins/dimg/raw/dimgrawplugin.cpp:55
#, kde-format
msgid "RAW loader"
msgstr ""
#. +> trunk5
#: core/dplugins/dimg/raw/dimgrawplugin.cpp:70
#, kde-format
msgid "An image loader based on Libraw codec"
msgstr ""
#. +> trunk5
#: core/dplugins/dimg/raw/dimgrawplugin.cpp:75
#, kde-format
msgid ""
"<p>This plugin permit to load and save image using Libraw codec.</p>"
"<p>A camera raw image file contains minimally processed data from the image sensor of either a digital camera, a motion picture film scanner, or other image scanner. Raw files are not yet processed and therefore are not ready to be printed or edited with a bitmap graphics editor. RAW are processed by a raw converter in a wide-gamut internal color space where precise adjustments can be made before conversion to a TIFF or JPEG for storage, printing, or further manipulation. This often encodes the image in a device-dependent color space.</p>"
"<p>See <a href='https://en.wikipedia.org/wiki/Raw_image_format'>Raw Image File documentation</a> for details.</p>"
msgstr ""
#. +> trunk5
#: core/dplugins/dimg/tiff/dimgtiffplugin.cpp:57
#, kde-format
msgid "TIFF loader"
msgstr ""
#. +> trunk5
#: core/dplugins/dimg/tiff/dimgtiffplugin.cpp:72
#, kde-format
msgid "An image loader based on Libtiff codec"
msgstr ""
#. +> trunk5
#: core/dplugins/dimg/tiff/dimgtiffplugin.cpp:77
#, kde-format
msgid ""
"<p>This plugin permit to load and save image using Libtiff codec.</p>"
"<p>Tagged Image File Format, abbreviated TIFF or TIF, is a computer file format for storing raster graphics images, popular among graphic artists, the publishing industry, and photographers. TIFF is widely supported by scanning, faxing, word processing, optical character recognition, image manipulation, desktop publishing, and page-layout applications.</p>"
"<p>See <a href='https://en.wikipedia.org/wiki/TIFF'>Tagged Image File Format documentation</a> for details.</p>"
msgid "With this button, you can pick the color from the original image used to set <b>Shadow Tone</b> input levels on the Red, Green, Blue, and Luminosity channels."
msgid "With this button, you can pick the color from the original image used to set <b>Middle Tone</b> input levels on the Red, Green, Blue, and Luminosity channels."
msgid "With this button, you can pick the color from the original image used to set <b>Highlight Tone</b> input levels on the Red, Green, Blue, and Luminosity channels."
"<p>This option maximizes the tonal range in the Red, Green, and Blue channels. It searches the image shadow and highlight limit values and adjusts the Red, Green, and Blue channels to a full histogram range.</p>"
"<p>This option scales brightness values across the active image so that the darkest point becomes black, and the brightest point becomes as bright as possible without altering its hue. This is often a \"magic fix\" for images that are dim or washed out.</p>"
"<p>This option adjusts the brightness of colors across the active image so that the histogram for the value channel is as nearly as possible flat, that is, so that each possible brightness value appears at about the same number of pixels as each other value. Sometimes Equalize works wonderfully at enhancing the contrasts in an image. Other times it gives garbage. It is a very powerful operation, which can either work miracles on an image or destroy it.</p>"
"<p>This option enhances the contrast and brightness of the RGB values of an image by stretching the lowest and highest values to their fullest range, adjusting everything in between.</p>"
"<p>This option enhances the contrast and brightness of the RGB values of an image to calculate optimal exposition and black level using image histogram properties.</p>"
msgid "With this button, you can pick the color of the orange mask of the scanned color negative. It represents white point of the negative, or the darkest black tone of the positive image after inversion. It is also the reference point for applying the film profile."
msgid "If you press this button, the white point is calculated from the image data automatically. This function requires to have some residual orange mask around the exposed area of the negative."
msgid "Move the slider to higher values until maximum brightness is achieved without clipping any color channel. Use the output histogram to evaluate each channel."
msgid "A percent of 0 has no effect, values above 0 represent a factor for mixing the destination color with source color this is done radially i.e. the inner part of the brush radius is totally from source and mixing with destination is done gradually till the outer part of the circle."
"* Press <b>s</b> to switch to source-selection mode, and select source point on image.<br/>"
"* Press <b>s</b> again and start cloning.<br/>"
"* Press <b>[</b> and <b>]</b> to change brush size.<br/>"
"* Press <b>CTRL+Mousewheel</b> to zoom in/out.<br/>"
"* Press <b>m</b> to pan the image if image is larger than viewport.<br/>"
"* Press <b>l</b> to start lasso mode. Start drawing lasso boundary either continuously or discretely, then double-click or press l again to close the boundary.<br/>"
"* Inside lasso mode, you can clone only inside the lasso region.</p>"
"<p>Select the blurring effect to apply to image.</p>"
"<p><b>Zoom Blur</b>: blurs the image along radial lines starting from a specified center point. This simulates the blur of a zooming camera.</p>"
"<p><b>Radial Blur</b>: blurs the image by rotating the pixels around the specified center point. This simulates the blur of a rotating camera.</p>"
"<p><b>Far Blur</b>: blurs the image by using far pixels. This simulates the blur of an unfocalized camera lens.</p>"
"<p><b>Motion Blur</b>: blurs the image by moving the pixels horizontally. This simulates the blur of a linear moving camera.</p>"
"<p><b>Softener Blur</b>: blurs the image softly in dark tones and hardly in light tones. This gives images a dreamy and glossy soft focus effect. It is ideal for creating romantic portraits, glamour photographs, or giving images a warm and subtle glow.</p>"
"<p><b>Shake Blur</b>: blurs the image by shaking randomly the pixels. This simulates the blur of a random moving camera.</p>"
"<p><b>Focus Blur</b>: blurs the image corners to reproduce the astigmatism distortion of a lens.</p>"
"<p><b>Smart Blur</b>: finds the edges of color in your image and blurs them without muddying the rest of the image.</p>"
"<p><b>Frost Glass</b>: blurs the image by randomly disperse light coming through a frosted glass.</p>"
"<p><b>Mosaic</b>: divides the photograph into rectangular cells and then recreates it by filling those cells with average pixel value.</p>"
"<p>Note: if you have previously selected an area in the editor, this will be unaffected by the filter. You can use this method to disable the Raindrops effect on a human face, for example.</p>"
msgid "<p>This Image Editor tool can crop automatically an image by detection of inner black border, generated while panorama stitching for example.</p>"
msgid "Click on this button to draw zones marking which areas of the image are less important. These zones will be deleted when reducing the picture, or duplicated when enlarging the picture."
msgid "Use this value to give a negative bias to the seams which are not straight. May be useful to prevent distortions in some situations, or to avoid artifacts from pixel skipping (it is better to use low values in such case). This setting applies to the whole selected layer if no rigidity mask is used. Note: the bias is proportional to the difference in the transversal coordinate between each two successive points, elevated to the power of 1.5, and summed up for the whole seam."
msgid "This option lets you choose the maximum transversal step that the pixels in the seams can take. In the standard algorithm, corresponding to the default value step = 1, each pixel in a seam can be shifted by at most one pixel with respect to its neighbors. This implies that the seams can form an angle of at most 45 degrees with respect to their base line. Increasing the step value lets you overcome this limit, but may lead to the introduction of artifacts. In order to balance the situation, you can use the rigidity setting."
msgid "During the carving process, at each step the optimal seam to be carved is chosen based on the relevance value for each pixel. However, in the case where two seams are equivalent (which may happen, for instance, when large portions of the image have the same color), the algorithm always chooses the seams from one side. In some cases, this can pose problems, e.g. an object centered in the original image might not be centered in the resulting image. In order to overcome this effect, this setting allows the favored side to be switched automatically during rescaling, at the cost of slightly worse performance."
msgid "This is the free rotation operation preview. If you move the mouse cursor on this preview, a vertical and horizontal dashed line will be drawn to guide you in adjusting the free rotation correction. Release the left mouse button to freeze the dashed line's position."
msgid "This is the perspective transformation operation preview. You can use the mouse for dragging the corner to adjust the perspective transformation area."
"<p>Select your constrained aspect ratio for cropping. Aspect Ratio Crop tool uses a relative ratio. That means it is the same if you use centimeters or inches and it does not specify the physical size.</p>"
"<p>You can see below a correspondence list of traditional photographic paper sizes and aspect ratio crop:</p>"
"<p><b>8:5</b>: common wide-screen monitor (as 1680x1050)</p>"
"<p><b>2:1</b>, <b>3:1</b>, <b>4:1</b>: common panoramic sizes</p>"
"<p><b>16:9</b>: common tv-screen (as HDTV or Full-HD)</p>"
"<p>The paper <b>Format DIN A</b> use the ratio 1:1.414</p>"
"<p>The <b>Golden Ratio</b> is 1:1.618. A composition following this rule is considered visually harmonious but may not be suitable to print on standard photographic paper.</p>"
"<p>The <b>Current Aspect Ratio</b> takes aspect ratio from the currently opened image.</p>"
msgid "This is the shear operation preview. If you move the mouse cursor on this preview, a vertical and horizontal dashed line will be drawn to guide you in adjusting the shear correction. Release the left mouse button to freeze the dashed line's position."
"<p>This tool permit to changes geolocation information from items.</p>"
"<p>This tool can edit GPS data, manually or over a map. Reverse geo-coding is also available through web services.</p>"
"<p>This tool as also an export function to KML to store map traces in Google format.</p>"
"<p>Finally, this tool is able to read a GPS trace from a device to synchronize geo-location of items if you camera do not have an embedded GPS device.</p>"
msgid "<b>Note: <b><a href='https://en.wikipedia.org/wiki/EXIF'>EXIF</a></b> text tags marked by (*) only support printable <b><a href='https://en.wikipedia.org/wiki/Ascii'>ASCII</a></b> characters.</b>"
msgid "Set here the date and time when the original image data was generated. For a digital still camera the date and time the picture was taken are recorded."
msgid "Set here the date and time when the image was stored as digital data. If, for example, an image was captured by a digital still camera and at the same time the file was recorded, then Original and Digitization date and time will have the same contents."
msgid "<b>Warning: EXIF <b><a href='https://en.wikipedia.org/wiki/Exchangeable_image_file_format#MakerNote_data'>Makernotes</a></b> can be unreadable if you set wrong device manufacturer/model description.</b>"
msgid "Select here the mode used by the camera to set exposure when the picture was taken. In auto-bracketing mode, the camera shoots a series of frames of the same scene at different exposure settings."
msgid "Set here the flash energy used to take the picture in BCPS units. Beam Candle Power Seconds is the measure of effective intensity of a light source when it is focused into a beam by a reflector or lens. This value is the effective intensity for a period of one second."
msgid "<b>Note: <b><a href='https://en.wikipedia.org/wiki/IPTC_Information_Interchange_Model'>IPTC</a></b> text tags only support the printable <b><a href='https://en.wikipedia.org/wiki/Ascii'>ASCII</a></b> characters and limit string sizes. Use contextual help for details.</b>"
msgid "Enter here the Informative Provider Reference. I.P.R is a name registered with the IPTC/NAA, identifying the provider that provides an indicator of the content. The default value for the I.P.R is \"IPTC\" if a standard Reference Code is used. This field is limited to 32 ASCII characters."
msgid "Enter here the Subject Reference Number. Provides a numeric code to indicate the Subject Name plus optional Subject Matter and Subject Detail Names in the language of the service. Subject Reference is a number from the range 01000000 to 17999999 and represent a language independent international reference to a Subject. A Subject is identified by its Reference Number and corresponding Names taken from a standard lists given by IPTC/NAA. If a standard reference code is used, these lists are the English language reference versions. This field is limited to 8 ASCII digit code."
msgid "Enter here the Subject Name. English language is used if you selected a standard IPTC/NAA reference code. This field is limited to 64 ASCII characters."
msgid "Enter here the Subject Matter Name. English language is used if you selected a standard IPTC/NAA reference code. This field is limited to 64 ASCII characters."
msgid "Enter here the Subject Detail Name. English language is used if you selected a standard IPTC/NAA reference code. This field is limited to 64 ASCII characters."
msgid "Enter here the Informative Provider Reference. I.P.R is a name registered with the XMP/NAA, identifying the provider that provides an indicator of the content. The default value for the I.P.R is \"XMP\" if a standard Reference Code is used."
msgid "Enter here the Subject Reference Number. Provides a numeric code to indicate the Subject Name plus optional Subject Matter and Subject Detail Names in the language of the service. Subject Reference is a number from the range 01000000 to 17999999 and represent a language independent international reference to a Subject. A Subject is identified by its Reference Number and corresponding Names taken from a standard lists given by XMP/NAA. If a standard reference code is used, these lists are the English language reference versions. This field is limited to 8 digit code."
"<p style=\" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;\">You can download a calendar for your country from <a href=\"http://www.icalshare.com\"><span style=\" text-decoration: underline; color:#0057ae;\">http://www.icalshare.com</span></a> or other sites.</p>"
"\n"
"<p style=\" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;\">This is fully optional. All the events from this calendar will be printed in red.</p>"
msgid "<p>This tool will also permit to set specific dates on your calendar using external data event files as <a href='https://en.wikipedia.org/wiki/VCalendar'>vCalendar</a>, and <a href='https://en.wikipedia.org/wiki/Icalendar'>iCalendar</a> formats.</p>"
msgid "Set automatic level selection (maximized) for pyramid blending, i.e. optimize image features (contrast, saturation, . . .) to be as global as possible."
msgid "Set the number of levels for pyramid blending. Balances towards local features (small number) or global features (high number). Additionally, a low number trades off quality of results for faster execution time and lower memory usage."
msgid "Force hard blend masks without averaging on finest scale. This is only useful for focus stacks with thin and high contrast features. It improves sharpness at the expense of increased noise."
msgid "Sets the relative weight of high-contrast pixels. Increasing this weight makes pixels with neighboring differently colored pixels contribute more to the final output. Particularly useful for focus stacks."
msgid "Use Color Appearance Modelling (CIECAM02) to render detailed colors. Your input files should have embedded ICC profiles. If no ICC profile is present, sRGB color space will be assumed. The difference between using this option and default color blending algorithm is very slight, and will be most noticeable when you need to blend areas of different primary colors together."
"<p>This tool permit to blend bracketed images together to create pseudo HDR photo.</p>"
"<p>To create high definition range image, you need to use images from same subject taken with a tripod and exposed with different exposure settings.</p>"
"<p>To create image with better results, you can use RAW images instead JPEG, where colors depth is higher and are well adapted for merging pixels by pixels.</p>"
"<p>This tool fuses bracketed images with different exposure to make pseudo <a href='https://en.wikipedia.org/wiki/High_dynamic_range_imaging'>HDR image</a>.</p>"
"<p>It can also be used to <a href='https://en.wikipedia.org/wiki/Focus_stacking'>merge focus bracketed stack</a> to get a single image with increased depth of field.</p>"
"<p>This assistant will help you to configure how to import images before merging them to a single one.</p>"
"<p>Bracketed images must be taken with the same camera, in the same conditions, and if possible using a tripod.</p>"
"<p>For more information, please take a look at <a href='https://en.wikipedia.org/wiki/Bracketing'>this page</a></p>"
"<p>Now, we will pre-process bracketed images before fusing them.</p>"
"<p>To perform auto-alignment, the <b>%1</b> program from the <a href='%2'>%3</a> project will be used. Alignment must be performed if you have not used a tripod to take bracketed images. Alignment operations can take a while.</p>"
"<p>Pre-processing operations include Raw demosaicing. Raw images will be converted to 16-bit sRGB images with auto-gamma.</p>"
"The media server permit to share items through the local network using <a href='https://en.wikipedia.org/wiki/Digital_Living_Network_Alliance'>DLNA</a> standard and <a href='https://en.wikipedia.org/wiki/Universal_Plug_and_Play'>UPNP</a> protocol. Many kind of electronic devices can support DLNA, as tablets, cellulars, TV, etc.<br/>"
"Note: depending of the network features and the configuration, the delay to discover the server on client devices can take a while."
"<p>This tool permit to assemble images together to create large panorama.</p>"
"<p>To create panorama image, you need to use images taken from same point of view with a tripod and exposed with same settings.</p>"
"<p>The tool is able to assemble shot taken horizontally, vertically, or as a matrix. Take a care that target image will become huge and require a lots of memory to be processed.</p>"
msgid "<b>JPEG output</b>: Using JPEG output, the panorama file will be smaller at the cost of information loss during compression. This is the easiest way to share the result, or print it online or in a shop."
msgid "<b>TIFF output</b>: Using TIFF output, you get the same color depth than your original photos using RAW images at the cost of a bigger panorama file."
msgid "<b>File name template</b>: Set here the base name of the files that will be saved. For example, if your template is <i>panorama</i> and if you chose a JPEG output, then your panorama will be saved with the name <i>panorama.jpg</i>. If you choose to save also the project file, it will have the name <i>panorama.pto</i>."
msgid "<b>Save project file</b>: You can keep the project file generated to stitch your panorama for further tweaking within <a href=\"http://hugin.sourceforge.net/\">Hugin</a> by checking this. This is useful if you want a different projection, modify the horizon or the center of the panorama, or modify the control points to get better results."
"<p><font color=\"orange\"><b>Warning:</b> One or more converted raw files already exists (they will be skipped during the copying process).</font></p>"
"<p>Congratulations. Your images are stitched into a panorama.</p>"
"<p>Your panorama will be created to the directory:<br />"
"<b>%1</b><br />"
"once you press the <i>Finish</i> button, with the name set below.</p>"
"<p>If you choose to save the project file, and if your images were raw images then the converted images used during the stitching process will be copied at the same time (those are TIFF files that can be big).</p>"
msgid "<b>Detect moving skies</b>: During the control points selection and matching, this option discards any points that are associated to a possible cloud. This is useful to prevent moving clouds from altering the control points matching process."
"<p>Now, we will pre-process images before stitching them.</p>"
"<p>Pre-processing operations include Raw demosaicing. Raw images will be converted to 16-bit sRGB images with auto-gamma.</p>"
"<p>Pre-processing also include a calculation of some control points to match overlaps between images. For that purpose, the <b>%1</b> program from the <a href='%2'>%3</a> project will be used.</p>"
"<p>You can generate quickly a <a href='https://en.wikipedia.org/wiki/Time-lapse_photography'>Time-lapse</a> movie from images</p>"
"<p>captured with a tripod mounted camera controlled with an <a href='https://en.wikipedia.org/wiki/Intervalometer#Photography'>intervalometer</a>.</p>"
"<p></p>"
"<p>You can also create a video presentation with transition</p>"
"<p>effects and audio tracks to show on a TV screen.</p>"
msgid "<i>An effect is an visual panning or zooming applied while an image is displayed. The effect duration will follow the number of frames used to render the image on video stream.</i>"
msgid "<i>A transition is an visual effect applied between two images. For some effects, the duration can depend of random values and can change while the slideshow.</i>"
"<li style=\" margin-top:12px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;\">move mouse in up/down-direction while pressing the right mouse button</li>"
"\n"
"<li style=\" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;\">alternatively, press c and use the scrollwheel<br />"
"<li style=\" margin-top:12px; margin-bottom:12px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;\">move mouse while pressing the left button</li>"
"<p>This tool permit to export and import items with Google web-services.</p>"
"Google Photo and Google Drive web services are supported."
"<p>See Google web sites for details: <a href='https://photos.google.com'>https://photos.google.com</a> and <a href='https://www.google.com/drive/'>https://www.google.com/drive/</a></p>"
"<p>You cannot use digiKam without a working database. digiKam will attempt to start now, but it will <b>not</b> be functional. Please check the database settings in the <b>configuration menu</b>.</p>"
"<p>Failed to open the database. Error message from database:</p>"
"<p><b>%1</b></p>"
"<p>You cannot use digiKam without a working database. digiKam will attempt to start now, but it will <b>not</b> be functional. Please check the database settings in the <b>configuration menu</b>.</p>"
"Your locale has changed since this album was last opened.\n"
"Old locale: %1, new locale: %2\n"
"If you have recently changed your locale, you need not be concerned.\n"
"Please note that if you switched to a locale that does not support some of the filenames in your collection, these files may no longer be found in the collection. If you are sure that you want to continue, click 'Yes'. Otherwise, click 'No' and correct your locale setting before restarting digiKam."
"<p>You have chosen the folder \"%1\" as the place to store the database. A database file from an older version of digiKam is found in this folder.</p>"
" "
"<p>Would you like to upgrade the old database file - confirming that this database file was indeed created for the pictures located in the folder \"%2\" - or ignore the old file and start with a new database?</p>"
"<p>You have chosen the folder \"%1\" as the new place to store the database. A database file from an older version of digiKam is found in this folder.</p>"
" "
"<p>Would you like to upgrade the old database file, start with a new database, or copy the current database to this location and continue using it?</p>"
"<p>You have chosen the folder \"%1\" as the new place to store the database. A database file from an older version of digiKam is found in this folder.</p>"
" "
"<p>Would you like to upgrade the old database file or start with a new database?</p>"
msgid "This is a CD/DVD, which is identified by the label that you can set in your CD burning application. There is already another entry with the same label. The two will be distinguished by the files in the top directory, so please do not append files to the CD, or it will not be recognized. In the future, please set a unique label on your CDs and DVDs if you intend to use them with digiKam."
msgid "This is a CD/DVD. It will be identified by the label (\"%1\")that you have set in your CD burning application. If you create further CDs for use with digikam in the future, please remember to give them a unique label as well."
msgid "This entry will only be identified by the path where it is found on your system (\"%1\"). No more specific means of identification (UUID, label) is available."
msgid "It is not possible on your system to identify the storage medium of this path. It will be added using the file path as the only identifier. This will work well for your local hard disk."
msgid "The database is not valid: the \"DBVersion\" setting does not exist. The current database schema version cannot be verified. Try to start with an empty database. "
msgid "The database has been used with a more recent version of digiKam and has been updated to a database schema which cannot be used with this version. (This means this digiKam version is too old, or the database format is too recent.) Please use the more recent version of digiKam that you used before. "
msgid "Failed to open a database transaction on your database file \"%1\". This is unusual. Please check that you can access the file and no other process has currently locked the file. If the problem persists you can get help from the digikam developers mailing list (see www.digikam.org/support). As well, please have a look at what digiKam prints on the console. "
msgid "The schema updating process from version 4 to 6 failed, caused by an error that we did not expect. You can try to discard your old database and start with an empty one. (In this case, please move the database files \"%1\" and \"%2\" from the directory \"%3\"). More probably you will want to report this error to the digikam developers mailing list (see www.digikam.org/support). As well, please have a look at what digiKam prints on the console. "
msgid "Failed to update the database schema from version %1 to version %2. Please read the error messages printed on the console and report this error as a bug at bugs.kde.org. "
msgid "The database update action cannot be found. Please ensure that the dbconfig.xml file of the current version of digiKam is installed at the correct place. "
msgid "Failed to copy the old database file (\"%1\") to its new location (\"%2\"). Error message: \"%3\". Please make sure that the file can be copied, or delete it."
msgid "The old database file (\"%1\") has been copied to the new location (\"%2\") but it cannot be opened. Please delete both files and try again, starting with an empty database. "
msgid "No album library path has been found in the configuration file. Giving up the schema updating process. Please try with an empty database, or repair your configuration."
msgid "There was an error associating your albumLibraryPath (\"%1\") with a storage volume of your system. This problem may indicate that there is a problem with your installation. If you are working on Linux, check that HAL is installed and running. In any case, you can seek advice from the digikam developers mailing list (see www.digikam.org/support). The database updating process will now be aborted because we do not want to create a new database based on false assumptions from a broken installation."
msgid "Could not open the configuration file <b>%1</b>. This file is installed with the digikam application and is absolutely required to run digikam. Please check your installation."
msgid "An old version of the configuration file <b>%1</b> is found. Please ensure that the version released with the running version of digiKam is installed. "
msgid "The database is not valid: the \"DBSimilarityVersion\" setting does not exist. The current database schema version cannot be verified. Try to start with an empty database. "
msgid "The database has been used with a more recent version of digiKam and has been updated to a database schema which cannot be used with this version. (This means this digiKam version is too old, or the database format is to recent) Please use the more recent version of digikam that you used before. "
msgstr ""
#. +> trunk5
#: core/libs/database/tags/facetags.cpp:393
#, kde-format
msgctxt "People on your photos"
msgid "People"
msgstr ""
#. +> trunk5
#: core/libs/database/tags/facetags.cpp:441
#, kde-format
msgctxt "The list of detected faces from the collections but not recognized"
msgid "Unknown"
msgstr ""
#. +> trunk5
#: core/libs/database/tags/facetags.cpp:461
#, kde-format
msgctxt "The list of recognized faces from the collections but not confirmed"
msgid "The database is not valid: the \"DBThumbnailsVersion\" setting does not exist. The current database schema version cannot be verified. Try to start with an empty database. "
"<p>Select here the type of database backend.</p>"
"<p><b>SQlite</b> backend is for local database storage with a small or medium collection sizes. It is the default and recommended backend for collections with less than 100K items.</p>"
"<p><b>MySQL Internal</b> backend is for local database storage with huge collection sizes. This backend is recommend for local collections with more than 100K items.</p>"
"<p><i>Be careful: this one still in experimental stage.</i></p>"
"<p><b>MySQL Server</b> backend is a more robust solution especially for remote and shared database storage. It is also more efficient to manage huge collection sizes with more than 100K items.</p>"
"<p><i>Be careful: this one still in experimental stage.</i></p>"
"<p>Set here the location where the database files will be stored on your system. There are three databases: one for all collections properties, one to store compressed thumbnails, and one to store faces recognition metadata.<br/>"
"Write access is required to be able to edit image properties.</p>"
"<p>Databases are digiKam core engines. Take care to use a place hosted by fast hardware (as SSD) with enough free space especially for thumbnails database.</p>"
"<p>Note: a remote file system such as NFS, cannot be used here. For performance reasons, it is also recommended not to use removable media.</p>"
msgid "<p>Here you can configure locations where MySQL binary tools are located. digiKam will try to find these binaries automatically if they are already installed on your computer.</p>"
"<p>digiKam expects that database is already created with a dedicated user account. This user name <i>digikam</i> will require full access to the database.<br/>"
"If your database is not already set up, you can use the following SQL commands (after replacing the <b><i>password</i></b> with the correct one).</p>"
"<p>Note: with a Linux server, a database can be initialized following the commands below:</p>"
"<p># su</p>"
"<p># systemctl restart mysqld</p>"
"<p># mysql -u root</p>"
"<p>...</p>"
"<p>Enter SQL code to Mysql prompt in order to init digiKam databases with grant privileges (see behind)</p>"
"<p>...</p>"
"<p>quit</p>"
"<p>NOTE: If you have an enormous collection, you should start MySQL server with mysql --max_allowed_packet=128M OR in my.ini or ~/.my.cnf, change the settings</p>"
"<p>Use this configuration view to set all information to be connected to a remote <a href=\"https://en.wikipedia.org/wiki/MySQL\">Mysql database server</a> (or <a href=\"https://en.wikipedia.org/wiki/MariaDB\">MariaDB</a>) through a network. As with Sqlite or MySQL internal server, 3 databases will be stored on the remote server: one for all collections properties, one to store compressed thumbnails, and one to store faces recognition metadata.</p>"
"<p>Unlike Sqlite or MySQL internal server, you can customize the database names to simplify your backups.</p>"
"<p>Databases are digiKam core engines. To prevent performance issues, take a care to use a fast network link between the client and the server computers. It is also recommended to host database files on fast hardware (as <a href=\"https://en.wikipedia.org/wiki/Solid-state_drive\">SSD</a>) with enough free space, especially for thumbnails database, even if data are compressed using wavelets image format <a href=\"https://en.wikipedia.org/wiki/Progressive_Graphics_File\">PGF</a>.</p>"
"<p>The databases must be created previously on the remote server by the administrator. Look in <b>Requirements</b> tab for details.</p>"
"<p>Simulate black and white film exposure using a green filter. This is useful for all scenic shoots, especially portraits photographed against the sky.</p>"
"<p>Simulate black and white film exposure using a yellow filter. This has the most natural tonal correction, and improves contrast. Ideal for landscapes.</p>"
"<p>Simulate black and white film exposure using a yellow-green filter. A yellow-green filter is highly effective for outdoor portraits because red is rendered dark while green appears lighter. Great for correcting skin tones, bringing out facial expressions in close-ups and emphasizing the feeling of liveliness. This filter is highly effective for indoor portraits under tungsten lighting.</p>"
"<p>Gives a warm highlight and mid-tone while adding a bit of coolness to the shadows - very similar to the process of bleaching a print and re-developing in a sepia toner.</p>"
msgid "With this button, you can pick the color from original image used to set <b>Shadow Tone</b> smooth curves point on Red, Green, Blue, and Luminosity channels."
msgid "With this button, you can pick the color from original image used to set <b>Middle Tone</b> smooth curves point on Red, Green, Blue, and Luminosity channels."
msgid "With this button, you can pick the color from original image used to set <b>Highlight Tone</b> smooth curves point on Red, Green, Blue, and Luminosity channels."
msgid "Enable this option if you want to preserve the aspect ratio of image. If enabled, the border width will be a percentage of the image size, else the border width will be in pixels."
msgid "Total smoothing power: if the Detail Factor sets the relative smoothing and the Anisotropy Factor the direction, the Smoothing Factor sets the overall effect."
msgid "<b>Function</b>: This function combines the original RGB channels with the desaturated blurred image. This function is used in each of the tonemapping stages. It can be linear or power. Basically, this function increases the values where both the original and blurred image's value are low and do the opposite on high values."
msgid "<b>Highlights saturation</b>: Usually the (perceived) saturation is increased. The user can choose to lower the saturation on original highlight and shadows from the image with these parameters."
msgid "<b>Shadow saturation</b>: Usually the (perceived) saturation is increased. The user can choose to lower the saturation on original highlight and shadows from the image with these parameters."
msgid "This value is the radius of the inner circle of the filter. In the inner circle the image is preserved. It is expressed as a multiple of the outer radius of the filter."
msgid "This value is the radius of the outer circle of the filter. Outside the outer circle the effect of the filter is at its maximum. It is expressed as a multiple of the diagonal of the image."
msgid "This is the camera maker description string found in image meta-data. This one is used to query and find relevant camera device information from Lensfun database."
msgid "This is the camera model description string found in image meta-data. This one is used to query and found relevant camera device information from Lensfun database."
msgid "This is the lens description string found in image meta-data. This one is used to query and found relevant lens information from Lensfun database."
msgid "Vignetting refers to an image darkening, mostly in the corners. Optical and natural vignetting can be canceled out with this option, whereas mechanical vignetting will not be cured."
msgid "Distortion refers to an image deformation, which is most pronounced towards the corners. These Seidel aberrations are known as pincushion and barrel distortions."
msgid "<b>Note: lens correction options depend of filters available in LensFun library. See <a href='http://lensfun.sourceforge.net'>LensFun project web site</a> for more information.</b>"
"<p>If the image's maximal counts are small, you can use the <b>linear</b> scale.</p>"
"<p><b>Logarithmic</b> scale can be used when the maximal counts are big; if it is used, all values (small and large) will be visible on the graph.</p>"
msgid "<b>Alpha</b>: display the alpha image-channel values. This channel corresponds to the transparency value and is supported by some image formats, such as PNG or TIF."
msgid "<b>Threshold</b>: Adjusts the threshold for denoising of the image in a range from 0.0 (none) to 10.0. The threshold is the value below which everything is considered noise."
msgstr ""
#. +> trunk5
#: core/libs/dimg/filters/nr/nrsettings.cpp:120
#, kde-format
msgid "<b>Softness</b>: This adjusts the softness of the thresholding (soft as opposed to hard thresholding). The higher the softness the more noise remains in the image."
msgstr ""
#. +> trunk5
#: core/libs/dimg/filters/nr/nrsettings.cpp:126
#, kde-format
msgid "Estimate Noise"
msgstr ""
#. +> trunk5
#: core/libs/dimg/filters/nr/nrsettings.cpp:127
#, kde-format
msgid "Compute automatically all noise reduction settings by a parse of noise contained in image."
msgid "This is the radius of the circular convolution. It is the most important parameter for using this tool. For most images the default value of 1.0 should give good results. Select a higher value when your image is very blurred."
msgid "Increasing the correlation may help to reduce artifacts. The correlation can range from 0-1. Useful values are 0.5 and values close to 1, e.g. 0.95 and 0.99. Using a high value for the correlation will reduce the sharpening effect of the tool."
msgid "Increasing the noise filter parameter may help to reduce artifacts. The noise filter can range from 0-1 but values higher than 0.1 are rarely helpful. When the noise filter value is too low, e.g. 0.0 the image quality will be very poor. A useful value is 0.01. Using a high value for the noise filter will reduce the sharpening effect of the tool."
msgid "This is the sharpness for the Gaussian convolution. Use this parameter when your blurring is of a Gaussian type. In most cases you should set this parameter to 0, because it causes nasty artifacts. When you use non-zero values, you will probably also have to increase the correlation and/or noise filter parameters."
msgid "This parameter determines the size of the transformation matrix. Increasing the matrix width may give better results, especially when you have chosen large values for circular or Gaussian sharpness."
msgid "<font color='red'><i>Warning: <a href='https://en.wikipedia.org/wiki/JPEG'>JPEG</a> is a lossy image compression format.</i></font>"
msgstr ""
#. +> trunk5
#: core/libs/dimg/loaders/jpegsettings.cpp:107
#, kde-format
msgid "Chroma subsampling:"
msgstr ""
#. +> trunk5
#: core/libs/dimg/loaders/jpegsettings.cpp:110
#, kde-format
msgid "4:4:4 (best quality)"
msgstr ""
#. +> trunk5
#: core/libs/dimg/loaders/jpegsettings.cpp:111
#, kde-format
msgid "4:2:2 (good quality)"
msgstr ""
#. +> trunk5
#: core/libs/dimg/loaders/jpegsettings.cpp:112
#, kde-format
msgid "4:2:0 (low quality)"
msgstr ""
#. +> trunk5
#: core/libs/dimg/loaders/jpegsettings.cpp:113
#, kde-format
msgid "4:1:1 (low quality)"
msgstr ""
#. +> trunk5
#: core/libs/dimg/loaders/jpegsettings.cpp:114
#, kde-format
msgid ""
"<p>Chroma subsampling reduces file size by taking advantage of the eye's lesser sensitivity to color resolution. How perceptible the difference is depends on the image - large photos will generally show no difference, while sharp, down-scaled pixel graphics may lose fine color detail.</p>"
"<p><b>4:4:4</b> - No chroma subsampling, highest quality but lowest compression.</p>"
"<p><b>4:2:2</b> - Chroma halved horizontally, average compression, average quality.</p>"
"<p><b>4:2:0</b> - Chroma quartered in 2x2 blocks, high compression but low quality.</p>"
"<p><b>4:1:1</b> - Chroma quartered in 4x1 blocks, high compression but low quality.</p>"
msgid "The database is not valid: the \"DBFaceVersion\" setting does not exist. The current database schema version cannot be verified. Try to start with an empty database. "
msgid "The database has been used with a more recent version of digiKam and has been updated to a database schema which cannot be used with this version. (This means this digiKam version is too old, or the database format is to recent.) Please use the more recent version of digiKam that you used before."
"Background color indicates the global image filter status, encompassing all filter settings from the right sidebar.\n"
"\n"
"NO COLOR: no filter is active, all items are visible.\n"
"RED: filtering is on, but no items match.\n"
"GREEN: filter(s) match(es) at least one item.\n"
"\n"
"Move mouse cursor over this text to see more details about active filters.\n"
"Press the Reset button from the right side to clear all filter settings.\n"
"Press the Settings button from the right side to open the filters panel."
msgstr ""
#. +> trunk5
#: core/libs/filters/filterstatusbar.cpp:96
#, kde-format
msgid "Reset all active filters"
msgstr ""
#. +> trunk5
#: core/libs/filters/filterstatusbar.cpp:102
#, kde-format
msgid "Open filter settings panel"
msgstr ""
#. +> trunk5
#: core/libs/filters/filterstatusbar.cpp:132
#, kde-format
msgid ""
"<br/>"
"<nobr><i>Text</i></nobr>"
msgstr ""
#. +> trunk5
#: core/libs/filters/filterstatusbar.cpp:137
#, kde-format
msgid ""
"<br/>"
"<nobr><i>Mime Type</i></nobr>"
msgstr ""
#. +> trunk5
#: core/libs/filters/filterstatusbar.cpp:142
#, kde-format
msgid ""
"<br/>"
"<nobr><i>Geolocation</i></nobr>"
msgstr ""
#. +> trunk5
#: core/libs/filters/filterstatusbar.cpp:147
#, kde-format
msgid ""
"<br/>"
"<nobr><i>Rating</i></nobr>"
msgstr ""
#. +> trunk5
#: core/libs/filters/filterstatusbar.cpp:152
#, kde-format
msgid ""
"<br/>"
"<nobr><i>Pick Labels</i></nobr>"
msgstr ""
#. +> trunk5
#: core/libs/filters/filterstatusbar.cpp:157
#, kde-format
msgid ""
"<br/>"
"<nobr><i>Color Labels</i></nobr>"
msgstr ""
#. +> trunk5
#: core/libs/filters/filterstatusbar.cpp:162
#, kde-format
msgid ""
"<br/>"
"<nobr><i>Tags</i></nobr>"
msgstr ""
#. +> trunk5
#: core/libs/filters/filterstatusbar.cpp:167
#, kde-format
msgid "<nobr><b>Active filters:</b></nobr>"
msgstr ""
#. +> trunk5
#: core/libs/filters/filterstatusbar.cpp:171
#, kde-format
msgid "<nobr><b>Active filter:</b></nobr>"
msgstr ""
#. +> trunk5
#: core/libs/filters/filterstatusbar.cpp:178
#, kde-format
msgid "No active filter"
msgstr ""
#. +> trunk5
#: core/libs/filters/filterstatusbar.cpp:187
#, kde-format
msgid "One active filter"
msgstr ""
#. +> trunk5
#: core/libs/filters/filterstatusbar.cpp:191
#, kde-format
msgid "1 active filter"
msgid_plural "%1 active filters"
msgstr[0] ""
msgstr[1] ""
#. +> trunk5
#: core/libs/filters/geolocationfilter.cpp:37
#, kde-format
msgid "No geo filtering"
msgstr ""
#. +> trunk5
#: core/libs/filters/geolocationfilter.cpp:38
#, kde-format
msgid "Images with coordinates"
msgstr ""
#. +> trunk5
#: core/libs/filters/geolocationfilter.cpp:39
#, kde-format
msgid "Images without coordinates"
msgstr ""
#. +> trunk5
#: core/libs/filters/geolocationfilter.cpp:41
#, kde-format
msgid "Filter by geolocation"
msgstr ""
#. +> trunk5
#: core/libs/filters/geolocationfilter.cpp:42
#, kde-format
msgid "Select how geolocation should affect the images which are shown."
msgstr ""
#. +> trunk5
#: core/libs/filters/mimefilter.cpp:36
#, kde-format
msgid "All Files"
msgstr ""
#. +> trunk5
#: core/libs/filters/mimefilter.cpp:37
#: core/utilities/setup/album/setupmime.cpp:105
#, kde-format
msgid "Image Files"
msgstr ""
#. +> trunk5
#: core/libs/filters/mimefilter.cpp:38
#, kde-format
msgid "No RAW Files"
msgstr ""
#. +> trunk5
#: core/libs/filters/mimefilter.cpp:39
#, kde-format
msgid "JPEG Files"
msgstr ""
#. +> trunk5
#: core/libs/filters/mimefilter.cpp:40
#, kde-format
msgid "PNG Files"
msgstr ""
#. +> trunk5
#: core/libs/filters/mimefilter.cpp:41
#, kde-format
msgid "TIFF Files"
msgstr ""
#. +> trunk5
#: core/libs/filters/mimefilter.cpp:42
#, kde-format
msgid "PGF Files"
msgstr ""
#. +> trunk5
#: core/libs/filters/mimefilter.cpp:43
#, kde-format
msgid "HEIF Files"
msgstr ""
#. +> trunk5
#: core/libs/filters/mimefilter.cpp:44
#, kde-format
msgid "DNG Files"
msgstr ""
#. +> trunk5
#: core/libs/filters/mimefilter.cpp:45
#, kde-format
msgid "RAW Files"
msgstr ""
#. +> trunk5
#: core/libs/filters/mimefilter.cpp:46
#: core/utilities/setup/album/setupmime.cpp:137
#, kde-format
msgid "Video Files"
msgstr ""
#. +> trunk5
#: core/libs/filters/mimefilter.cpp:47
#: core/utilities/setup/album/setupmime.cpp:172
#, kde-format
msgid "Audio Files"
msgstr ""
#. +> trunk5
#: core/libs/filters/mimefilter.cpp:48
#, kde-format
msgid "Raster Graphics"
msgstr ""
#. +> trunk5
#: core/libs/filters/mimefilter.cpp:50
#, kde-format
msgid "Filter by file type"
msgstr ""
#. +> trunk5
#: core/libs/filters/mimefilter.cpp:51
#, kde-format
msgid "Select the file types (MIME types) that you want shown. Note: \"Raster Graphics\" are file formats from raster graphics editors, such as Photoshop, The Gimp, Krita, etc."
msgstr ""
#. +> trunk5
#: core/libs/filters/ratingfilter.cpp:75
#, kde-format
msgid "Select the rating value used to filter albums' contents. Use the context pop-up menu to set rating filter conditions."
msgstr ""
#. +> trunk5
#: core/libs/filters/ratingfilter.cpp:173
#, kde-format
msgid "Rating greater than or equal to %1."
msgstr ""
#. +> trunk5
#: core/libs/filters/ratingfilter.cpp:178
#, kde-format
msgid "Rating equal to %1."
msgstr ""
#. +> trunk5
#: core/libs/filters/ratingfilter.cpp:183
#, kde-format
msgid "Rating less than or equal to %1."
msgstr ""
#. +> trunk5
#: core/libs/filters/ratingfilter.cpp:227
#, kde-format
msgid "Rating Filter Options"
msgstr ""
#. +> trunk5
#: core/libs/filters/ratingfilter.cpp:232
#, kde-format
msgid "Greater Than or Equals Condition"
msgstr ""
#. +> trunk5
#: core/libs/filters/ratingfilter.cpp:234
#, kde-format
msgid "Equals Condition"
msgstr ""
#. +> trunk5
#: core/libs/filters/ratingfilter.cpp:236
#, kde-format
msgid "Less Than or Equals Condition"
msgstr ""
#. +> trunk5
#: core/libs/filters/ratingfilter.cpp:239
#, kde-format
msgid "Exclude Items Without Rating"
msgstr ""
#. +> trunk5
#: core/libs/filters/textfilter.cpp:81
#, kde-format
msgid "Text quick filter (search)"
msgstr ""
#. +> trunk5
#: core/libs/filters/textfilter.cpp:82
#, kde-format
msgid "Enter search patterns to quickly filter this view on item names, captions (comments), and tags"
msgstr ""
#. +> trunk5
#: core/libs/filters/textfilter.cpp:86
#, kde-format
msgid "Text Search Fields"
msgstr ""
#. +> trunk5
#: core/libs/filters/textfilter.cpp:89
#, kde-format
msgid "Defines which fields to search for the text in."
msgstr ""
#. +> trunk5
#: core/libs/filters/textfilter.cpp:92
#, kde-format
msgid "Item Name"
msgstr ""
#. +> trunk5
#: core/libs/filters/textfilter.cpp:94
#, kde-format
msgid "Item Title"
msgstr ""
#. +> trunk5
#: core/libs/filters/textfilter.cpp:96
#, kde-format
msgid "Item Comment"
msgstr ""
#. +> trunk5
#: core/libs/filters/textfilter.cpp:98
#, kde-format
msgid "Tag Name"
msgstr ""
#. +> trunk5
#: core/libs/filters/textfilter.cpp:100
#, kde-format
msgid "Album Name"
msgstr ""
#. +> trunk5
#: core/libs/filters/textfilter.cpp:102
#, kde-format
msgid "Item Aspect Ratio"
msgstr ""
#. +> trunk5
#: core/libs/filters/textfilter.cpp:104
#, kde-format
msgid "Item Pixel Size"
msgstr ""
#. +> trunk5
#: core/libs/filters/textfilter.cpp:107
#, kde-format
msgid "Clear All"
msgstr ""
#. +> trunk5
#: core/libs/iojobs/iojob.cpp:78
#, kde-format
msgid "File/Folder %1 does not exist anymore"
msgstr ""
#. +> trunk5
#: core/libs/iojobs/iojob.cpp:84
#, kde-format
msgid "Album %1 does not exist anymore"
msgstr ""
#. +> trunk5
#: core/libs/iojobs/iojob.cpp:95
#, kde-format
msgid "A file or folder named %1 already exists in %2"
msgstr ""
#. +> trunk5
#: core/libs/iojobs/iojob.cpp:119
#, kde-format
msgid "Could not move folder %1 to album %2"
msgstr ""
#. +> trunk5
#: core/libs/iojobs/iojob.cpp:127
#, kde-format
msgid "Could not move folder %1 to album %2. The folder %1 was copied as well to album %2"
msgstr ""
#. +> trunk5
#: core/libs/iojobs/iojob.cpp:138
#, kde-format
msgid "Could not move file %1 to album %2"
msgstr ""
#. +> trunk5
#: core/libs/iojobs/iojob.cpp:159
#, kde-format
msgid "Could not copy folder %1 to album %2"
msgstr ""
#. +> trunk5
#: core/libs/iojobs/iojob.cpp:170
#, kde-format
msgid "Could not copy file %1 to album %2"
msgstr ""
#. +> trunk5
#: core/libs/iojobs/iojob.cpp:212
#, kde-format
msgid "File/Folder %1 does not exist"
msgstr ""
#. +> trunk5
#: core/libs/iojobs/iojob.cpp:224
#, kde-format
msgid "Could not move folder %1 to collection trash"
msgid "Enter the text used to create tags here. '/' can be used to create a hierarchy of tags. ',' can be used to create more than one hierarchy at the same time."
"<para>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.</para>"
"<para>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.</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:252
#, kde-format
msgctxt "@option:check"
msgid "Interpolate RGB as four colors"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:253
#, kde-kuit-format
msgctxt "@info:whatsthis"
msgid ""
"<title>Interpolate RGB as four colors</title>"
"<para>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.</para>"
"<para>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.</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:267
#, kde-format
msgctxt "@info:tooltip"
msgid "Visit LibRaw project website"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:277
#, kde-format
msgctxt "@option:check"
msgid "Do not stretch or rotate pixels"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:279
#, kde-kuit-format
msgctxt "@info:whatsthis"
msgid ""
"<title>Do not stretch or rotate pixels</title>"
"<para>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.</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:287
#, kde-format
msgctxt "@label:listbox"
msgid "Quality:"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:291
#, kde-format
msgctxt "@item:inlistbox Quality"
msgid "Bilinear"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:292
#, kde-format
msgctxt "@item:inlistbox Quality"
msgid "VNG"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:293
#, kde-format
msgctxt "@item:inlistbox Quality"
msgid "PPG"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:294
#, kde-format
msgctxt "@item:inlistbox Quality"
msgid "AHD"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:295
#, kde-format
msgctxt "@item:inlistbox Quality"
msgid "DCB"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:296
#, kde-format
msgctxt "@item:inlistbox Quality"
msgid "DHT"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:297
#, kde-format
msgctxt "@item:inlistbox Quality"
msgid "AAHD"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:301
#, kde-kuit-format
msgctxt "@info:whatsthis"
msgid ""
"<title>Quality (interpolation)</title>"
"<para>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:</para>"
"<para>"
"<list>"
"<item><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.</item>"
"<item><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.</item>"
"<item><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.</item>"
"<item><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.</item>"
"<item><emphasis strong='true'>DCB</emphasis>: DCB interpolation from linuxphoto.org project.</item>"
"<item><emphasis strong='true'>DHT</emphasis>: DHT interpolation.See https://www.libraw.org/node/2306 for details.</item>"
"<item><emphasis strong='true'>AAHD</emphasis>: modified AHD interpolation.</item>"
"</list>"
"</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:349
#, kde-format
msgctxt "@label:slider"
msgid "Pass:"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:350
#, kde-kuit-format
msgctxt "@info:whatsthis"
msgid ""
"<title>Pass</title>"
"<para>Set here the passes used by the median filter applied after interpolation to Red-Green and Blue-Green channels.</para>"
"<para>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>.</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:362
#, kde-format
msgctxt "@option:check"
msgid "Refine interpolation"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:363
#, kde-kuit-format
msgctxt "@info:whatsthis"
msgid ""
"<title>Refine interpolation</title>"
"<para>This setting is available only for few Quality options:</para>"
"<para>"
"<list>"
"<item><emphasis strong='true'>DCB</emphasis>: turn on the enhance interpolated colors filter.</item>"
"<item><emphasis strong='true'>VCD & AHD</emphasis>: turn on the enhanced effective color interpolation (EECI) refine to improve sharpness.</item>"
"</list>"
"</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:376
#, kde-format
msgctxt "@label"
msgid "Demosaicing"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:384
#, kde-format
msgctxt "@label:listbox"
msgid "Method:"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:386
#, kde-format
msgctxt "@item:inlistbox"
msgid "Default D65"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:387
#, kde-format
msgctxt "@item:inlistbox"
msgid "Camera"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:388
#, kde-format
msgctxt "@item:inlistbox set while balance automatically"
msgid "Automatic"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:389
#, kde-format
msgctxt "@item:inlistbox set white balance manually"
msgid "Manual"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:391
#, kde-kuit-format
msgctxt "@info:whatsthis"
msgid ""
"<title>White Balance</title>"
"<para>Configure the raw white balance:</para>"
"<para>"
"<list>"
"<item><emphasis strong='true'>Default D65</emphasis>: Use a standard daylight D65 white balance.</item>"
"<item><emphasis strong='true'>Camera</emphasis>: Use the white balance specified by the camera. If not available, reverts to default neutral white balance.</item>"
"<item><emphasis strong='true'>Automatic</emphasis>: Calculates an automatic white balance averaging the entire image.</item>"
"<item><emphasis strong='true'>Manual</emphasis>: Set a custom temperature and green level values.</item>"
"</list>"
"</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:406
#, kde-format
msgctxt "@label:slider"
msgid "T(K):"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:407
#, kde-kuit-format
msgctxt "@info:whatsthis"
msgid ""
"<title>Temperature</title>"
"<para>Set here the color temperature in Kelvin.</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:414
#, kde-format
msgctxt "@label:slider Green component"
msgid "Green:"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:415
#, kde-kuit-format
msgctxt "@info:whatsthis"
msgid "<para>Set here the green component to set magenta color cast removal level.</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:418
#, kde-format
msgctxt "@label:listbox"
msgid "Highlights:"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:420
#, kde-format
msgctxt "@item:inlistbox"
msgid "Solid white"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:421
#, kde-format
msgctxt "@item:inlistbox"
msgid "Unclip"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:422
#, kde-format
msgctxt "@item:inlistbox"
msgid "Blend"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:423
#, kde-format
msgctxt "@item:inlistbox"
msgid "Rebuild"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:425
#, kde-kuit-format
msgctxt "@info:whatsthis"
msgid ""
"<title>Highlights</title>"
"<para>Select here the highlight clipping method:</para>"
"<para>"
"<list>"
"<item><emphasis strong='true'>Solid white</emphasis>: clip all highlights to solid white</item>"
"<item><emphasis strong='true'>Unclip</emphasis>: leave highlights unclipped in various shades of pink</item>"
"<item><emphasis strong='true'>Blend</emphasis>:Blend clipped and unclipped values together for a gradual fade to white</item>"
"<item><emphasis strong='true'>Rebuild</emphasis>: reconstruct highlights using a level value</item>"
"<para>Specify the reconstruct highlight level. Low values favor whites and high values favor colors.</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:444
#, kde-format
msgctxt "@option:check"
msgid "Exposure Correction (E.V)"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:445
#, kde-kuit-format
msgctxt "@info:whatsthis"
msgid "<para>Turn on the exposure correction before interpolation.</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:448
#, kde-format
msgctxt "@label:slider"
msgid "Linear Shift:"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:453
#, kde-kuit-format
msgctxt "@info:whatsthis"
msgid ""
"<title>Shift</title>"
"<para>Linear Shift of exposure correction before interpolation in E.V</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:456
#, kde-format
msgctxt "@label:slider"
msgid "Highlight:"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:461
#, kde-kuit-format
msgctxt "@info:whatsthis"
msgid ""
"<title>Highlight</title>"
"<para>Amount of highlight preservation for exposure correction before interpolation in E.V. Only take effect if Shift Correction is > 1.0 E.V</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:465
#, kde-format
msgctxt "@option:check"
msgid "Correct false colors in highlights"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:466
#, kde-kuit-format
msgctxt "@info:whatsthis"
msgid "<para>If enabled, images with overblown channels are processed much more accurately, without 'pink clouds' (and blue highlights under tungsten lamps).</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:470
#, kde-format
msgctxt "@option:check"
msgid "Auto Brightness"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:471
#, kde-kuit-format
msgctxt "@info:whatsthis"
msgid "<para>If disable, use a fixed white level and ignore the image histogram to adjust brightness.</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:474
#, kde-format
msgctxt "@label:slider"
msgid "Brightness:"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:479
#, kde-kuit-format
msgctxt "@info:whatsthis"
msgid ""
"<title>Brightness</title>"
"<para>Specify the brightness level of output image. The default value is 1.0 (works in 8-bit mode only).</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:489
#, kde-format
msgctxt "@option:check Black point"
msgid "Black:"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:490
#, kde-kuit-format
msgctxt "@info:whatsthis"
msgid ""
"<title>Black point</title>"
"<para>Use a specific black point value to decode RAW pictures. If you set this option to off, the Black Point value will be automatically computed.</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:497
#, kde-kuit-format
msgctxt "@info:whatsthis"
msgid ""
"<title>Black point value</title>"
"<para>Specify specific black point value of the output image.</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:500
#, kde-format
msgctxt "@option:check White point"
msgid "White:"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:501
#, kde-kuit-format
msgctxt "@info:whatsthis"
msgid ""
"<title>White point</title>"
"<para>Use a specific white point value to decode RAW pictures. If you set this option to off, the White Point value will be automatically computed.</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:508
#, kde-kuit-format
msgctxt "@info:whatsthis"
msgid ""
"<title>White point value</title>"
"<para>Specify specific white point value of the output image.</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:547
#, kde-format
msgctxt "@label"
msgid "White Balance"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:555
#, kde-format
msgctxt "@label:listbox"
msgid "Noise reduction:"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:557
#, kde-format
msgctxt "@item:inlistbox Noise Reduction"
msgid "None"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:558
#, kde-format
msgctxt "@item:inlistbox Noise Reduction"
msgid "Wavelets"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:559
#, kde-format
msgctxt "@item:inlistbox Noise Reduction"
msgid "FBDD"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:561
#, kde-kuit-format
msgctxt "@info:whatsthis"
msgid ""
"<title>Noise Reduction</title>"
"<para>Select here the noise reduction method to apply during RAW decoding.</para>"
"<para>"
"<list>"
"<item><emphasis strong='true'>None</emphasis>: no noise reduction.</item>"
"<item><emphasis strong='true'>Wavelets</emphasis>: wavelets correction to erase noise while preserving real detail. It is applied after interpolation.</item>"
"<item><emphasis strong='true'>FBDD</emphasis>: Fake Before Demosaicing Denoising noise reduction. It is applied before interpolation.</item>"
"</list>"
"</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:586
#, kde-format
msgctxt "@label"
msgid "Corrections"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:594
#, kde-format
msgctxt "@label:listbox"
msgid "Camera Profile:"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:596
#, kde-format
msgctxt "@item:inlistbox Camera Profile"
msgid "None"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:597
#, kde-format
msgctxt "@item:inlistbox Camera Profile"
msgid "Embedded"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:598
#, kde-format
msgctxt "@item:inlistbox Camera Profile"
msgid "Custom"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:600
#, kde-kuit-format
msgctxt "@info:whatsthis"
msgid ""
"<title>Camera Profile</title>"
"<para>Select here the input color space used to decode RAW data.</para>"
"<para>"
"<list>"
"<item><emphasis strong='true'>None</emphasis>: no input color profile is used during RAW decoding.</item>"
"<item><emphasis strong='true'>Embedded</emphasis>: use embedded color profile from RAW file, if it exists.</item>"
"<item><emphasis strong='true'>Custom</emphasis>: use a custom input color space profile.</item>"
"</list>"
"</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:611
#: core/libs/rawengine/drawdecoderwidget.cpp:645
#, kde-format
msgid "ICC Files (*.icc *.icm)"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:613
#, kde-format
msgctxt "@label:listbox"
msgid "Workspace:"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:615
#, kde-format
msgctxt "@item:inlistbox Workspace"
msgid "Raw (no profile)"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:616
#, kde-format
msgctxt "@item:inlistbox Workspace"
msgid "sRGB"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:617
#, kde-format
msgctxt "@item:inlistbox Workspace"
msgid "Adobe RGB"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:618
#, kde-format
msgctxt "@item:inlistbox Workspace"
msgid "Wide Gamut"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:619
#, kde-format
msgctxt "@item:inlistbox Workspace"
msgid "Pro-Photo"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:620
#, kde-format
msgctxt "@item:inlistbox Workspace"
msgid "Custom"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:622
#, kde-kuit-format
msgctxt "@info:whatsthis"
msgid ""
"<title>Workspace</title>"
"<para>Select here the output color space used to decode RAW data.</para>"
"<para>"
"<list>"
"<item><emphasis strong='true'>Raw (linear)</emphasis>: in this mode, no output color space is used during RAW decoding.</item>"
"<item><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.</item>"
"<item><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.</item>"
"<item><emphasis strong='true'>Wide Gamut</emphasis>: this color space is an expanded version of the Adobe RGB color space.</item>"
"<item><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.</item>"
"<item><emphasis strong='true'>Custom</emphasis>: use a custom output color space profile.</item>"
"</list>"
"</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:657
#, kde-format
msgctxt "@label"
msgid "Color Management"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:850
#, kde-format
msgctxt "@label"
msgid "Threshold:"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawdecoderwidget.cpp:851
#, kde-kuit-format
msgctxt "@info:whatsthis"
msgid ""
"<title>Threshold</title>"
"<para>Set here the noise reduction threshold value to use.</para>"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawfiles.cpp:58
#, kde-format
msgid "Casio Digital Camera Raw File Format"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawfiles.cpp:59
#, kde-format
msgid "NuCore Raw Image File"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawfiles.cpp:64
#, kde-format
msgid "Canon Digital Camera RAW Image Format version 2.0"
msgstr ""
#. +> trunk5
#: core/libs/rawengine/drawfiles.cpp:66
#, kde-format
msgid "Canon Digital Camera RAW Image Format version 1.0"
"<li>If a tag hierarchy starts with '/', root tag album is used as parent.</li>"
"</ul>"
"</p>"
msgstr ""
#. +> trunk5
#: core/libs/tags/widgets/tageditdlg.cpp:234
#, kde-format
msgid "<p><b>Note</b>: this shortcut can be used to assign or unassign tag to items.</p>"
msgstr ""
#. +> trunk5
#: core/libs/tags/widgets/tageditdlg.cpp:351
#, kde-format
msgid "<b>Create New Tag</b>"
msgstr ""
#. +> trunk5
#: core/libs/tags/widgets/tageditdlg.cpp:355
#, kde-format
msgid ""
"<b>Create New Tag in<br/>"
"\"%1\"</b>"
msgstr ""
#. +> trunk5
#: core/libs/tags/widgets/tageditdlg.cpp:361
#, kde-format
msgid ""
"<b>Properties of Tag<br/>"
"\"%1\"</b>"
msgstr ""
#. +> trunk5
#: core/libs/tags/widgets/tageditdlg.cpp:533
#, kde-format
msgid "Tag creation Error"
msgstr ""
#. +> trunk5
#: core/libs/tags/widgets/tageditdlg.cpp:544
#, kde-format
msgid "An error occurred during tag creation:"
msgstr ""
#. +> trunk5
#: core/libs/tags/widgets/tageditdlg.cpp:546
#, kde-format
msgid "Tag Path"
msgstr ""
#. +> trunk5
#: core/libs/tags/widgets/tagfolderview.cpp:138
#: core/libs/tags/widgets/tagfolderview.cpp:306
#, kde-format
msgid "Collapse Selected Recursively"
msgstr ""
#. +> trunk5
#: core/libs/tags/widgets/tagfolderview.cpp:301
#, kde-format
msgid "Expand Selected Recursively"
msgstr ""
#. +> trunk5
#: core/libs/tags/widgets/tagspopupmenu.cpp:569
#, kde-format
msgid "Recently Assigned Tags"
msgstr ""
#. +> trunk5
#: core/libs/tags/widgets/tagspopupmenu.cpp:627
#: core/libs/tags/widgets/tagspopupmenu.cpp:767
#, kde-format
msgid "Add New Tag..."
msgstr ""
#. +> trunk5
#: core/libs/tags/widgets/tagspopupmenu.cpp:633
#, kde-format
msgid "More Tags..."
msgstr ""
#. +> trunk5
#: core/libs/tags/widgets/tagspopupmenu.cpp:733
#, kde-format
msgid "Assign this Tag"
msgstr ""
#. +> trunk5
#: core/libs/tags/widgets/tagspopupmenu.cpp:742
#, kde-format
msgid "Remove this Tag"
msgstr ""
#. +> trunk5
#: core/libs/tags/widgets/tagspopupmenu.cpp:752
#, kde-format
msgid "Go to this Tag"
msgstr ""
#. +> trunk5
#: core/libs/template/subjectedit.cpp:55
#, kde-format
msgid "Enter the Informative Provider Reference here. I.P.R is a name registered with the XMP/NAA, identifying the provider that provides an indicator of the content. The default value for the I.P.R is \"XMP\" if a standard Reference Code is used."
msgstr ""
#. +> trunk5
#: core/libs/template/subjectedit.cpp:61
#, kde-format
msgid "Enter the Subject Reference Number here. Provides a numeric code to indicate the Subject Name plus optional Subject Matter and Subject Detail Names in the language of the service. Subject Reference is a number from the range 01000000 to 17999999 and represent a language independent international reference to a Subject. A Subject is identified by its Reference Number and corresponding Names taken from a standard lists given by XMP/NAA. If a standard reference code is used, these lists are the English language reference versions. This field is limited to 8 digit code."
msgstr ""
#. +> trunk5
#: core/libs/template/subjectedit.cpp:74
#, kde-format
msgid "Enter the Subject Name here. English language is used if you selected a standard XMP/NAA reference code."
msgstr ""
#. +> trunk5
#: core/libs/template/subjectedit.cpp:78
#, kde-format
msgid "Enter the Subject Matter Name here. English language is used if you selected a standard XMP/NAA reference code."
msgstr ""
#. +> trunk5
#: core/libs/template/subjectedit.cpp:82
#, kde-format
msgid "Enter the Subject Detail Name here. English language is used if you selected a standard XMP/NAA reference code."
msgstr ""
#. +> trunk5
#: core/libs/template/templatelist.cpp:80
#, kde-format
msgid "Here you can see the metadata template list managed by digiKam."
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:118
#, kde-format
msgid "Author Names:"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:121
#, kde-format
msgid "Enter the names of the photograph's creators. Use semi-colons as separator here."
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:123
#, kde-format
msgid ""
"<p>This field should contain the names of the persons who created the photograph. If it is not appropriate to add the name of the photographer (for example, if the identity of the photographer needs to be protected) the name of a company or organization can also be used. Once saved, this field should not be changed by anyone.</p>"
"<p>To enter more than one name, use <b>semi-colons as separators</b>.</p>"
"<p>With IPTC, this field is limited to 32 ASCII characters.</p>"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:132
#, kde-format
msgid "Authors' Positions:"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:135
#, kde-format
msgid "Enter the job titles of the authors here."
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:137
#, kde-format
msgid ""
"<p>This field should contain the job titles of the authors. Examples might include titles such as: Staff Photographer, Freelance Photographer, or Independent Commercial Photographer. Since this is a qualifier for the Author field, the Author field must also be filled out.</p>"
"<p>With IPTC, this field is limited to 32 ASCII characters.</p>"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:148
#, kde-format
msgid "Enter the photograph credit here."
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:150
#, kde-format
msgid ""
"<p>(synonymous to Provider): Use the Provider field to identify who is providing the photograph. This does not necessarily have to be the author. If a photographer is working for a news agency such as Reuters or the Associated Press, these organizations could be listed here as they are \"providing\" the image for use by others. If the image is a stock photograph, then the group (agency) involved in supplying the image should be listed here.</p>"
"<p>With IPTC, this field is limited to 32 ASCII characters.</p>"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:162
#, kde-format
msgid "Enter the copyright notice to identify the current owner(s) of the copyright here."
"In Europe you would use: Copyright {Year} {Copyright owner}, all rights reserved. \n"
"In Japan, for maximum protection, the following three items should appear in the copyright field of the IPTC Core: (a) the word, Copyright; (b) year of the first publication; and (c) name of the author. You may also wish to include the phrase \"all rights reserved\".</p>"
"<p>With XMP, you can include more than one copyright string using different languages.</p>"
"<p>With IPTC, this field is limited to 128 ASCII characters.</p>"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:183
#, kde-format
msgid "Right Usage Terms:"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:185
#, kde-format
msgid "Enter the list of instructions on how a resource can be legally used here."
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:186
#, kde-format
msgid ""
"<p>The Right Usage Terms field should be used to list instructions on how a resource can be legally used.</p>"
"<p>With XMP, you can include more than one right usage terms string using different languages.</p>"
"<p>This field does not exist with IPTC.</p>"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:197
#, kde-format
msgid "Enter the original owner of the photograph here."
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:199
#, kde-format
msgid ""
"<p>The Source field should be used to identify the original owner or copyright holder of the photograph. The value of this field should never be changed after the information is entered following the image's creation. While not yet enforced by the custom panels, you should consider this to be a \"write-once\" field. The source could be an individual, an agency, or a member of an agency. To aid in later searches, it is suggested to separate any slashes \"/\" with a blank space. Use the form \"photographer / agency\" rather than \"photographer/agency.\" Source may also be different from Creator and from the names listed in the Copyright Notice.</p>"
"<p>With IPTC, this field is limited to 32 ASCII characters.</p>"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:211
#: core/libs/template/templateviewer.cpp:164
#, kde-format
msgid "Instructions:"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:214
#, kde-format
msgid "Enter the editorial notice here."
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:216
#, kde-format
msgid ""
"<p>The Instructions field should be used to list editorial instructions concerning the use of photograph.</p>"
"<p>With IPTC, this field is limited to 256 ASCII characters.</p>"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:241
#: core/libs/template/templateviewer.cpp:177
#, kde-format
msgid "Rights"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:252
#, kde-format
msgid "Enter the city of contents here."
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:254
#, kde-format
msgid "<p>This field should contain the name of the city where the photograph was taken.</p>"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:262
#, kde-format
msgid "Enter the city sublocation of contents here."
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:264
#, kde-format
msgid "<p>This field should contain the sublocation of the city where the photograph was taken.</p>"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:269
#: core/libs/template/templateviewer.cpp:186
#: core/libs/template/templateviewer.cpp:208
#, kde-format
msgid "Province/State:"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:272
#, kde-format
msgid "Enter the province or state of contents here."
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:274
#, kde-format
msgid "<p>This field should contain the province or state where the photograph was taken.</p>"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:282
#, kde-format
msgid "<p>Select here the country where the photograph was taken.</p>"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:307
#: core/libs/template/templateviewer.cpp:197
#, kde-format
msgid "Location"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:316
#, kde-format
msgid "Enter the city name of the lead author here."
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:318
#, kde-format
msgid "<p>This field should contain the city name where the lead author lives.</p>"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:326
#, kde-format
msgid "Enter the country name of the lead author here."
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:328
#, kde-format
msgid "<p>This field should contain the country name where the lead author lives.</p>"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:333
#: core/libs/template/templateviewer.cpp:202
#, kde-format
msgid "Address:"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:336
#, kde-format
msgid "Enter the address of the lead author here."
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:338
#, kde-format
msgid "<p>This field should contain the address where the lead author lives.</p>"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:343
#: core/libs/template/templateviewer.cpp:204
#, kde-format
msgid "Postal Code:"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:346
#, kde-format
msgid "Enter the postal code of the lead author here."
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:348
#, kde-format
msgid "<p>This field should contain the postal code where the lead author lives.</p>"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:353
#, kde-format
msgid "Province:"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:356
#, kde-format
msgid "Enter the province of the lead author here."
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:358
#, kde-format
msgid "<p>This field should contain the province where the lead author lives.</p>"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:363
#: core/libs/template/templateviewer.cpp:214
#, kde-format
msgid "Email:"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:366
#, kde-format
msgid "Enter the email of the lead author here."
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:368
#, kde-format
msgid "<p>This field should contain the email of the lead author.</p>"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:376
#, kde-format
msgid "Enter the phone number of the lead author here."
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:378
#, kde-format
msgid "<p>This field should contain the phone number of the lead author.</p>"
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:386
#, kde-format
msgid "Enter the web site URL of the lead author here."
msgstr ""
#. +> trunk5
#: core/libs/template/templatepanel.cpp:388
#, kde-format
msgid "<p>This field should contain the web site URL of the lead author.</p>"
msgstr ""
#. +> trunk5
#: core/libs/template/templateselector.cpp:72
#, kde-format
msgid "Template: "
msgstr ""
#. +> trunk5
#: core/libs/template/templateselector.cpp:76
#, kde-format
msgid "Open metadata template editor"
msgstr ""
#. +> trunk5
#: core/libs/template/templateselector.cpp:77
#, kde-format
msgid ""
"<p>Select here the action to perform using the metadata template.</p>"
msgid "Determine Time Difference With Clock Photo"
msgstr ""
#. +> trunk5
#: core/libs/timeadjust/clockphotodialog.cpp:97
#, kde-format
msgid "Load different photo"
msgstr ""
#. +> trunk5
#: core/libs/timeadjust/clockphotodialog.cpp:105
#, kde-format
msgid "If you have a photo in your set with a clock or another external time source on it, you can load it here and set the indicator to the (date and) time displayed. The difference of your internal camera clock will be determined from this setting."
msgid "An error has occurred with the media player..."
msgstr ""
#. +> trunk5
#: core/libs/widgets/combo/dcombobox.cpp:70
#: core/libs/widgets/range/dnuminput.cpp:80
#: core/libs/widgets/range/dnuminput.cpp:179
#, kde-format
msgctxt "@info:tooltip"
msgid "Reset to default value"
msgstr ""
#. +> trunk5
#: core/libs/widgets/files/dbinaryiface.cpp:214
#, kde-format
msgid "Navigate to %1"
msgstr ""
#. +> trunk5
#: core/libs/widgets/files/dbinarysearch.cpp:69
#, kde-format
msgid "Binary"
msgstr ""
#. +> trunk5
#: core/libs/widgets/files/dbinarysearch.cpp:70
#, kde-format
msgid "Version"
msgstr ""
#. +> trunk5
#: core/libs/widgets/files/dbinarysearch.cpp:108
#, kde-format
msgid "Binary not found."
msgstr ""
#. +> trunk5
#: core/libs/widgets/files/dbinarysearch.cpp:109
#, kde-format
msgid "Minimal version number required for this binary is %1"
msgstr ""
#. +> trunk5
#: core/libs/widgets/files/dbinarysearch.cpp:111
#, kde-format
msgid "Find"
msgstr ""
#. +> trunk5
#: core/libs/widgets/files/dbinarysearch.cpp:113
#, kde-format
msgid " or <a href=\"%1\">download</a>"
msgstr ""
#. +> trunk5
#: core/libs/widgets/files/dbinarysearch.cpp:142
#, kde-format
msgid ""
"<qt>"
"<p><font color=\"red\"><b>Warning:</b> Some necessary binaries have not been found on your system. If you have these binaries installed, please click the 'Find' button to locate them on your system, otherwise please download and install them to proceed.</font></p>"
"</qt>"
msgstr ""
#. +> trunk5
#: core/libs/widgets/files/dbinarysearch.cpp:181
#, kde-format
msgid "A development version has been detect. There is no guarantee on the behavior of this binary."
msgid "Here you can switch between fixed font size and font size to be calculated dynamically and adjusted to changing environment (e.g. widget dimensions, paper size)."
"<p><b>Perceptual intent</b> causes the full gamut of the image to be compressed or expanded to fill the gamut of the destination device, so that gray balance is preserved but colorimetric accuracy may not be preserved.</p>"
"<p>In other words, if certain colors in an image fall outside of the range of colors that the output device can render, the image intent will cause all the colors in the image to be adjusted so that the every color in the image falls within the range that can be rendered and so that the relationship between colors is preserved as much as possible.</p>"
"<p>This intent is most suitable for display of photographs and images, and is the default intent.</p>"
"</li>"
"<li>"
"<p><b>Absolute Colorimetric intent</b> causes any colors that fall outside the range that the output device can render to be adjusted to the closest color that can be rendered, while all other colors are left unchanged.</p>"
"<p>This intent preserves the white point and is most suitable for spot colors (Pantone, TruMatch, logo colors, ....)</p>"
"</li>"
"<li>"
"<p><b>Relative Colorimetric intent</b> is defined such that any colors that fall outside the range that the output device can render are adjusted to the closest color that can be rendered, while all other colors are left unchanged. Proof intent does not preserve the white point.</p>"
"</li>"
"<li>"
"<p><b>Saturation intent</b> preserves the saturation of colors in the image at the possible expense of hue and lightness.</p>"
"<p>Implementation of this intent remains somewhat problematic, and the ICC is still working on methods to achieve the desired effects.</p>"
"<p>This intent is most suitable for business graphics such as charts, where it is more important that the colors be vivid and contrast well with each other rather than a specific color.</p>"
"<p>This area contains a CIE or chromaticity diagram. A CIE diagram is a representation of all the colors that a person with normal vision can see. This is represented by the colored sail-shaped area. In addition you will see a triangle that is superimposed on the diagram outlined in white. This triangle represents the outer boundaries of the color space of the device that is characterized by the inspected profile. This is called the device gamut.</p>"
"<p>In addition there are black dots and yellow lines on the diagram. Each black dot represents one of the measurement points that were used to create this profile. The yellow line represents the amount that each point is corrected by the profile, and the direction of this correction.</p>"
"<p>The ICC profile path seems to be invalid.</p>"
"<p>If you want to set it now, select \"Yes\", otherwise select \"No\". In this case, \"Color Management\" feature will be disabled until you solve this issue</p>"
msgid "<p><a href='https://en.wikipedia.org/wiki/Exif'>EXIF</a> - a standard used by most digital cameras today to store technical information (like aperture and shutter speed) about an image.</p>"
msgid "<p><a href='https://en.wikipedia.org/wiki/IPTC_Information_Interchange_Model'>IPTC</a> - an older standard used in digital photography to store photographer information in images.</p>"
msgid "<p><a href='https://en.wikipedia.org/wiki/Extensible_Metadata_Platform'>XMP</a> - a new standard used in digital photography, designed to replace IPTC.</p>"
msgid "This list shows the results for your renaming pattern. Red items indicate a name collision, either because the new name is equal to the current name, or because the name has already been assigned to another item."
msgid "<p>Enter your renaming pattern here. Use the access buttons to quickly add renaming options and modifiers. For further explanation, use the information button.</p>"
msgid "<p>Add a modifier to a renaming option. To activate this button, place the cursor behind a renaming option or an already assigned modifier.</p>"
msgid "<b>Configure where you keep your images</b>"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/collectionpage.cpp:83
#, kde-format
msgctxt "This is a path name so you should include the slash in the translation"
msgid "/Pictures"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/collectionpage.cpp:89
#, kde-format
msgid ""
"<p>Please enter a location where you keep your images.</p>"
" "
"<p>You can choose any local folder, even one that already contains images.<br/>"
" More folders can be added later under the <i>Settings</i> menu. </p>"
" "
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/collectionpage.cpp:97
#, kde-format
msgid "<p><i>Note:</i> removable media (such as USB drives or DVDs) and remote file systems (such as NFS, or Samba mounted with cifs/smbfs) are supported.</p>"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/collectionpage.cpp:159
#, kde-format
msgid "You must select a folder for digiKam to use as the root album. All of your images will go there."
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/collectionpage.cpp:187
#, kde-format
msgid "Create Root Album Folder?"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/collectionpage.cpp:188
#, kde-format
msgid ""
"<p>The folder to use as the root album path does not exist:</p>"
"<p><b>%1</b></p>"
"Would you like digiKam to create it for you?"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/collectionpage.cpp:200
#, kde-format
msgid "Create Root Album Folder Failed"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/collectionpage.cpp:201
#, kde-format
msgid ""
"<p>digiKam could not create the folder to use as the root album.\n"
"Please select a different location.</p>"
"<p><b>%1</b></p>"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/collectionpage.cpp:226
#, kde-format
msgid ""
"You do not seem to have write access for the folder selected to be the root album.\n"
"Warning: Without write access, items cannot be edited."
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/databasepage.cpp:62
#, kde-format
msgid "<b>Configure where you will store databases</b>"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/metadatapage.cpp:64
#, kde-format
msgid "<b>Configure Metadata Storage to Files</b>"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/metadatapage.cpp:72
#, kde-format
msgid ""
"<qt>"
"<p>Set here if you want to store the information assigned to items in digiKam in the files' metadata, to improve interoperability with other photo management programs:</p>"
"</qt>"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/metadatapage.cpp:82
#, kde-format
msgid "Do nothing"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/metadatapage.cpp:87
#, kde-format
msgid "Add information to files"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/metadatapage.cpp:97
#, kde-format
msgid ""
"<qt>"
"<p><i>Note:</i> recording information to the files' metadata can slow down photo management operations.</p>"
"<h1><b>Migrate configuration and metadata from digiKam 4</b></h1>"
"</p>"
"<p>You can choose here if you want to use the configuration and albums from digiKam 4 in new digiKam. Please note the following warnings:</p>"
"<p>Migration is done <b>at your own risk</b>. digiKam developers do not recommend it and do not support it. On the other hand, creating a new configuration might result in loss of tags and other metadata that was not embedded inside the pictures and was only available in digiKam 4's database.</p>"
"<p>In either case you are recommended to backup the configuration files and databases before proceeding.</p>"
"<p>Specify how images should be opened when left-clicked on in the icon view:</p>"
"</qt>"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/openfilepage.cpp:83
#, kde-format
msgid "Open a preview"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/openfilepage.cpp:88
#, kde-format
msgid "Open in the editor"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/openfilepage.cpp:98
#, kde-format
msgid ""
"<qt>"
"<p><i>Note:</i> using a preview is always faster than using the editor, especially when checking a series of shots. However, you cannot change or fix the image in preview mode. Note that if you want to compare images quickly, it is often better to use the light table: images can be displayed side-by-side, and synchronized zooming and panning can be performed.</p>"
"</qt>"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/previewpage.cpp:65
#, kde-format
msgid "<b>Configure Preview Behavior</b>"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/previewpage.cpp:73
#, kde-format
msgid ""
"<qt>"
"<p>Set here how images are displayed in preview mode and on the light table:</p>"
"</qt>"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/previewpage.cpp:82
#, kde-format
msgid "Load reduced version of image"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/previewpage.cpp:87
#, kde-format
msgid "Load image"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/previewpage.cpp:97
#, kde-format
msgid ""
"<qt>"
"<p><i>Note:</i> loading a reduced version of an image is faster but can differ from the original, especially with Raw. In this case, a JPEG version of Raw pre-processed by camera is loaded, instead of the real image data. This JPEG image is embedded in the file metadata and is used by the camera to display a Raw image faster to a TV screen.</p>"
"</qt>"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/rawpage.cpp:65
#, kde-format
msgid "<b>Configure Raw File Handling</b>"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/rawpage.cpp:73
#, kde-format
msgid ""
"<qt>"
"<p>Set here how you want to open Raw images in the editor:</p>"
"</qt>"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/rawpage.cpp:82
#, kde-format
msgid "Open directly, with adjustments made automatically"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/rawpage.cpp:87
#, kde-format
msgid "Use the Raw import tool to adjust corrections manually"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/rawpage.cpp:97
#, kde-format
msgid ""
"<qt>"
"<p><i>Note:</i> the Raw import tool is designed for advanced users who want to have the best control over the image. This requires more time in your workflow.</p>"
"</qt>"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/startscanpage.cpp:43
#, kde-format
msgid "Scan Your Collection"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/startscanpage.cpp:49
#, kde-format
msgid ""
"<qt>"
"<p>Congratulations. Your minimal setup is done.</p>"
"<p>Remember, you can customize more settings using the digiKam configuration panel. To learn more about the digiKam world, we recommend reading the <b>digiKam handbook</b> using the <b>Help/Handbook</b> menu entry (you need to install the separate digiKam documentation package.) You can also read the manual online from the <a href='https://www.digikam.org/docs'>digikam.org website</a>.</p>"
"<p>Press <b>Finish</b> to close this assistant. digiKam will scan your collection to register all albums in the database. Items including in albums are collected after startup stage in background.</p>"
"<p><i>Note:</i> depending on your collection size, this operation can take a while. If you cancel the scanning operation, it will start again in the next digiKam session.</p>"
"<p>When scanning has completed, at next start-up, digiKam will only check your collection to identify new albums - which is much faster. You can force digiKam to scan for new items manually using the <b>Tools->Maintenance->Scan for new items</b> menu entry.</p>"
"</qt>"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/tooltipspage.cpp:65
#, kde-format
msgid "<b>Enabled Contextual Tooltips</b>"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/tooltipspage.cpp:73
#, kde-format
msgid ""
"<qt>"
"<p>Set here if you want to show contextual tooltips in icon-view and folder-view:</p>"
"</qt>"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/tooltipspage.cpp:82
#, kde-format
msgid "Do not show tooltips"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/tooltipspage.cpp:87
#, kde-format
msgid "Use Tooltips"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/tooltipspage.cpp:97
#, kde-format
msgid ""
"<qt>"
"<p><i>Note:</i> tooltips show photograph and digiKam metadata on the fly, as the mouse moves over items. This can be useful when selecting items. Tooltips are displayed in the album folder view, album icon view, camera icon view, batch queue list, and thumb bar. From the digiKam configuration dialog, you can customize the contents of these tooltips and the fonts used.</p>"
"</qt>"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/welcomepage.cpp:49
#, kde-format
msgid ""
"<qt>"
"<p>"
"<h1><b>Welcome to digiKam %1</b></h1>"
"</p>"
"<p>digiKam is an advanced digital photo management application published as open-source.</p>"
"<p>This assistant will help you to configure first run settings to be able to use digiKam quickly.</p>"
"</qt>"
msgstr ""
#. +> trunk5
#: core/utilities/firstrun/welcomepage.cpp:75
#, kde-format
msgid ""
"<qt><br/>"
"<p>You can ignore the following if you use digiKam for the first time:</p>"
"<p><b>Transition from digiKam 4</b></p>"
"<p>Configuration files from digiKam 4 are not migrated. The old database can still be used, you just need to choose the same locations for collections and database in the following dialogs. It is recommended to create a backup of your database before proceeding.</p>"
"<p>The new location for configuration files is %1 (old %2). There are unresolved problems reported when re-using old configuration files, so it is not recommended to do it for the moment, and at your own risk.</p>"
msgid "Use this option to restrict the duplicate search with some criteria, as to limit search to the album of reference image, or to exclude the album of reference image of the search."
msgid "Image fingerprints have not yet been generated for your collection. The Similarity Search Tools will not be operational without pre-generated fingerprints. Please generate the fingerprints first."
"You have enabled writing to sidecar files for metadata storage in the host application, but not for reading. This means that any metadata stored in the sidecar files will be overwritten here.\n"
"Please enable reading of sidecar files in the host application or continue at your own risk."
"<p>Sets the time zone the camera was set to during photo shooting, so that the time stamps of the images can be converted to GMT to match the GPS time reference.</p>"
"<p>Note: positive offsets count eastwards from zero longitude (GMT), they are 'ahead of time'.</p>"
msgid "Sets the maximum time difference to interpolate GPX file points to image time data. If the time difference exceeds this setting, no match will be attempted."
msgid "Sets the maximum time difference from a GPS track point to the image time to be matched. If the time difference exceeds this setting, no match will be attempted."
msgid "<p>Select the profile for your output device (usually, your printer). This profile will be used to do a soft proof, so you will be able to preview how an image will be rendered via an output device.</p>"
msgid "Cannot open the specified working space profile (\"%1\"). No color transformation will be applied. Please check the color management configuration in digiKam's setup."
msgid "If this option is enabled, the preview area will split vertically. A contiguous area of the image will be shown, with one half from the original image, the other half from the target image."
msgid "If this option is enabled, the preview area will split horizontally. A contiguous area of the image will be shown, with one half from the original image, the other half from the target image."
msgid "If this option is enabled, the preview area will split vertically. The same part of the original and the target image will be shown side by side."
msgid "If this option is enabled, the preview area will split horizontally. The same part of the original and the target image will be shown side by side."
msgid "For more information about the <b>Mounted Camera</b> driver, please read the <b>Supported Digital Still Cameras</b> section in the digiKam manual."
msgid "Set how digiKam will rename files as they are downloaded."
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:245
#, kde-format
msgid "File Renaming Options"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:251
#, kde-format
msgid "Auto-creation of Albums"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:257
#, kde-format
msgid "On the Fly Operations (JPEG only)"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:263
#, kde-format
msgid "DNG Convert Options"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:269
#, kde-format
msgid "Scripting"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:288
#, kde-format
msgctxt "@action Cancel process"
msgid "Cancel"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:295
#, kde-format
msgctxt "@action Information about camera"
msgid "Information"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:302
#, kde-format
msgctxt "@action Capture photo from camera"
msgid "Capture"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:314
#, kde-format
msgctxt "@action:inmenu"
msgid "Select All"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:322
#, kde-format
msgctxt "@action:inmenu"
msgid "Select None"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:330
#, kde-format
msgctxt "@action:inmenu"
msgid "Invert Selection"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:338
#, kde-format
msgctxt "@action:inmenu"
msgid "Select New Items"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:345
#, kde-format
msgctxt "@action:inmenu"
msgid "Select Locked Items"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:353
#, kde-format
msgctxt "@title:menu"
msgid "Download"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:358
#, kde-format
msgctxt "@action"
msgid "Download New"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:368
#, kde-format
msgctxt "@action"
msgid "Download Selected"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:375
#, kde-format
msgctxt "@action"
msgid "Download All"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:383
#, kde-format
msgctxt "@action"
msgid "Download && Delete New"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:391
#, kde-format
msgctxt "@action"
msgid "Download && Delete Selected"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:399
#, kde-format
msgctxt "@action"
msgid "Download && Delete All"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:406
#, kde-format
msgctxt "@action"
msgid "Upload..."
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:414
#, kde-format
msgctxt "@action"
msgid "Toggle Lock"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:422
#, kde-format
msgctxt "@action"
msgid "Mark as downloaded"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:429
#, kde-format
msgctxt "@title:menu"
msgid "Delete"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:434
#, kde-format
msgctxt "@action"
msgid "Delete Selected"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:442
#, kde-format
msgctxt "@action"
msgid "Delete All"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:448
#, kde-format
msgctxt "@action"
msgid "Delete New"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:456
#, kde-format
msgctxt "@title:group"
msgid "Views"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:467
#, kde-format
msgctxt "@action View the selected image"
msgid "Preview Item"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:487
#, kde-format
msgctxt "@title:menu"
msgid "&Sort Items"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:488
#, kde-format
msgctxt "@info:whatsthis"
msgid "The value by which the items are sorted in the thumbnail view"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:492
#, kde-format
msgctxt "item:inmenu Sort by"
msgid "By Name"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:493
#, kde-format
msgctxt "item:inmenu Sort by"
msgid "By Path"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:494
#, kde-format
msgctxt "item:inmenu Sort by"
msgid "By Date"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:495
#, kde-format
msgctxt "item:inmenu Sort by"
msgid "By Size"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:496
#, kde-format
msgctxt "item:inmenu Sort by"
msgid "By Rating"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:497
#, kde-format
msgctxt "item:inmenu Sort by"
msgid "By Download State"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:521
#, kde-format
msgctxt "@title:inmenu"
msgid "Item Sorting &Order"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:522
#, kde-format
msgctxt "@info:whatsthis"
msgid "Defines whether items are sorted in ascending or descending manner."
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:526
#, kde-format
msgctxt "@item:inmenu Sorting Order"
msgid "Ascending"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:528
#, kde-format
msgctxt "@item:inmenu Sorting Order"
msgid "Descending"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:540
#, kde-format
msgctxt "@title:menu"
msgid "&Group Items"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:541
#, kde-format
msgctxt "@info:whatsthis"
msgid "The categories in which the items in the thumbnail view are displayed"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:545
#, kde-format
msgctxt "@item:inmenu Group Items"
msgid "Flat List"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:546
#, kde-format
msgctxt "@item:inmenu Group Items"
msgid "By Folder"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:547
#, kde-format
msgctxt "@item:inmenu Group Items"
msgid "By Format"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:548
#, kde-format
msgctxt "@item:inmenu Group Items"
msgid "By Date"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:574
#, kde-format
msgctxt "@action:inmenu"
msgid "Fit to &Window"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:579
#, kde-format
msgctxt "@action:inmenu"
msgid "Zoom to 100%"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:597
#, kde-format
msgctxt "@option:check"
msgid "Show History"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:603
#, kde-format
msgctxt "@option:check"
msgid "Show Thumbbar"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:628
#: core/utilities/import/main/importui.cpp:858
#, kde-format
msgctxt "@action"
msgid "Previous Image"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:635
#, kde-format
msgctxt "@action Connection failed, try again?"
msgid "Retry"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:847
#, kde-format
msgctxt "@action"
msgid "Exit Preview Mode"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:852
#, kde-format
msgctxt "@action"
msgid "Next Image"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:864
#, kde-format
msgctxt "@action Go to first image"
msgid "First Image"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:869
#, kde-format
msgctxt "@action Go to last image"
msgid "Last Image"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:951
#, kde-format
msgctxt "@info:status"
msgid "Canceling current operation, please wait..."
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:1006
#, kde-format
msgctxt "@info"
msgid "Do you want to close the dialog and cancel the current operation?"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:1016
#, kde-format
msgctxt "@info:status"
msgid "Disconnecting from camera, please wait..."
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:1058
#, kde-format
msgctxt "@info:status"
msgid "Scanning for new files, please wait..."
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:1097
#, kde-format
msgctxt "@info:status"
msgid "Ready"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:1153
#, kde-format
msgctxt "@info"
msgid "Failed to connect to the camera. Please make sure it is connected properly and turned on."
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:1243
#, kde-format
msgctxt "@title:window"
msgid "Select Image to Upload"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:1277
#, kde-format
msgctxt "@info"
msgid ""
"There is not enough free space on the Camera Medium to upload pictures.\n"
"\n"
"Space require: %1\n"
"Available free space: %2"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:1331
#, kde-format
msgctxt "@info"
msgid ""
"<qt>Camera Folder <resource>%1</resource> already contains the item <resource>%2</resource>.<br/>"
"Please enter a new filename (without extension):</qt>"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:1335
#, kde-format
msgctxt "@title:window"
msgid "File already exists"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:1401
#, kde-format
msgctxt "@info"
msgid "Your custom target album date format is not valid. Please check your settings..."
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:1441
#, kde-format
msgctxt "@info"
msgid "Collection which host your default target album set to process download from camera device is not available. Please select another one from camera configuration dialog."
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:1450
#, kde-format
msgctxt "@info"
msgid "Your default target album set to process download from camera device is not available. Please select another one from camera configuration dialog."
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:1475
#, kde-format
msgctxt "@info"
msgid "<p>Please select the destination album from the digiKam library to import the camera pictures into.</p>"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:1566
#, kde-format
msgctxt "@info Popup notification"
msgid "Images download finished, you can now detach your camera while the images will be auto-rotated"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:1573
#, kde-format
msgctxt "@info Popup notification"
msgid "Images download finished"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:1968
#, kde-format
msgctxt "@info"
msgid "The items listed below are locked by camera (read-only). These items will not be deleted. If you really want to delete these items, please unlock them and try again."
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:1979
#, kde-format
msgctxt "@info"
msgid "About to delete this image. <b>Deleted file is unrecoverable.</b> Are you sure?"
msgid_plural "About to delete these %1 images. <b>Deleted files are unrecoverable.</b> Are you sure?"
msgstr[0] ""
msgstr[1] ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:2030
#, kde-format
msgctxt "@title:window"
msgid "Insufficient Disk Space"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:2031
#, kde-format
msgctxt "@info"
msgid ""
"There is not enough free space on the disk of the album you selected to download and process the selected pictures from the camera.\n"
"\n"
"Estimated space required: %1\n"
"Available free space: %2\n"
"\n"
"Try Anyway?"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:2345
#: core/utilities/import/main/importui.cpp:2371
#, kde-format
msgctxt "@info:status"
msgid "No item selected (%1 item)"
msgid_plural "No item selected (%1 items)"
msgstr[0] ""
msgstr[1] ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:2363
#, kde-format
msgctxt "@info:status Filename of first selected item of number of items"
msgid "<b>%1</b> (%2 of %3)"
msgstr ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:2381
#, kde-format
msgctxt "@info:status"
msgid "%2/%1 item selected"
msgid_plural "%2/%1 items selected"
msgstr[0] ""
msgstr[1] ""
#. +> trunk5
#: core/utilities/import/main/importui.cpp:2452
#, kde-format
msgctxt "@info"
msgid "A file with the same name (<b>%1</b>) already exists in folder <resource>%2</resource>."
msgid "Enable this option to set date and time metadata tags to the right values if your camera does not set these tags correctly when pictures are taken. The values will be saved in the DateTimeDigitized and DateTimeCreated EXIF, XMP, and IPTC tags."
msgid "Enable this option to automatically convert all JPEG files to a lossless image format. <b>Note:</b> Image conversion can take a while on a slow computer."
"<p>These expressions may be used to customize date format:</p>"
"<p><b>d</b>: The day as a number without a leading zero (1 to 31)</p>"
"<p><b>dd</b>: The day as a number with a leading zero (01 to 31)</p>"
"<p><b>ddd</b>: The abbreviated localized day name (e.g. 'Mon' to 'Sun')</p>"
"<p><b>dddd</b>: The long localized day name (e.g. 'Monday' to 'Sunday').</p>"
"<p><b>M</b>: The month as a number without a leading zero (1 to 12)</p>"
"<p><b>MM</b>: The month as a number with a leading zero (01 to 12)</p>"
"<p><b>MMM</b>: The abbreviated localized month name (e.g. 'Jan' to 'Dec')</p>"
"<p><b>MMMM</b>: The long localized month name (e.g. 'January' to 'December')</p>"
"<p><b>yy</b>: The year as two digit number (eg. 00 to 99)</p>"
"<p><b>yyyy</b>: The year as four digit number (eg. 2012)</p>"
"<p>All other input characters will be treated as text. Any sequence of characters that are enclosed in singlequotes will be treated as text and not be used as an expression. Examples, if date is 20 July 1969:</p>"
"<p><b>dd.MM.yyyy</b> : 20.07.1969</p>"
"<p><b>ddd MMMM d yy</b> : Sun July 20 69</p>"
"<p><b>'Photo shot on ' dddd</b> : Photo shot on Sunday</p>"
msgid "Enable this option if you want to download your pictures into automatically created file extension-based sub-albums of the destination album. This way, you can separate JPEG and RAW files as they are downloaded from your camera."
msgid "Set this option to show the file modification date below the image thumbnail if it is different than camera creation date. This option is useful to identify quickly which items have been modified."
"Set this option to render icon-view with large thumbnail size, for example in case of 4K monitor is used.\n"
"By default this option is turned off and the maximum thumbnail size is limited to 256x256 pixels. When this option is enabled, thumbnail size can be extended to 512x512 pixels.\n"
"This option will store more data in thumbnail database and will use more system memory. digiKam needs to be restarted to take effect, and Rebuild Thumbnails option from Maintenance tool needs to be processed over whole collections."
msgid "This option changes the size in which thumbnails are generated. You need to restart digiKam for this option to take effect. Furthermore, you need to regenerate all already stored thumbnails via the <interface>Tools / Maintenance</interface> menu."
"<p>Add new file types to show as album items.</p>"
"<p>digiKam attempts to support all of the image formats that digital cameras produce, while being able to handle a few other important video and audio formats.</p>"
" "
"<p>You can add to the already-appreciable list of formats that digiKam handles by adding the extension of the type you want to add. Multiple extensions need to be separated by a semicolon or space.</p>"
"<p><b><u>Note:</u> changes done in this view will perform a database rescan in the background.</b></p>"
"<p>Here you can add the extensions of image files (including RAW files) to be displayed in the Album view. Just put \"xyz abc\" to display files with the xyz and abc extensions in your Album view.</p>"
"<p>You can also remove file formats that are shown by default by putting a minus sign in front of the extension: e.g. \"-gif\" would remove all GIF files from your Album view and any trace of them in your database. They would not be deleted, just not shown in digiKam.</p>"
"<p><b>Warning:</b> Removing files from the database means losing all of their tags and ratings.</p>"
"<p>Here you can add extra extensions of video files to be displayed in your Album view. Just write \"xyz abc\" to support files with the *.xyz and *.abc extensions. Clicking on these files will play them in an embedded video player.</p>"
"<p>You can also remove file formats that are supported by default by putting a minus sign in front of the extension: e.g. \"-avi\" would remove all AVI files from your Album view and any trace of them in your database. They would not be deleted, just not shown in digiKam.</p>"
"<p><b>Warning:</b> Removing files from the database means losing all of their tags and ratings.</p>"
"<p>Here you can add extra extensions of audio files to be displayed in your Album view. Just write \"xyz abc\" to support files with the *.xyz and *.abc extensions. Clicking on these files will play them in an embedded audio player.</p>"
"<p>You can also remove file formats that are supported by default by putting a minus sign in front of the extension: e.g. \"-ogg\" would remove all OGG files from your Album view and any trace of them in your database. They would not be deleted, just not shown in digiKam.</p>"
"<p><b>Warning:</b> Removing files from the database means losing all of their tags and ratings.</p>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/album/setupmime.cpp:195
#, kde-format
msgid "Enter additional audio file extensions."
msgstr ""
#. +> trunk5
#: core/utilities/setup/album/setupmime.cpp:259
#, kde-format
msgid ""
"<p>You have chosen to remove the following image formats from the list of supported formats: <b>%1</b>.</p>"
"<p>These are very common formats. If you have images in your collection with these formats, they will be removed from the database and you will lose all information about them, including rating and tags.</p>"
"<p>Are you sure you want to apply your changes and lose the support for these formats?</p>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/album/setupmime.cpp:312
#, kde-format
msgid ""
"<p>Files with these extensions will be recognized as images and included into the database:<br/>"
" <code>%1</code></p>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/album/setupmime.cpp:322
#, kde-format
msgid ""
"<p>Files with these extensions will be recognized as video files and included into the database:<br/>"
" <code>%1</code></p>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/album/setupmime.cpp:332
#, kde-format
msgid ""
"<p>Files with these extensions will be recognized as audio files and included into the database:<br/>"
" <code>%1</code></p>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/camera/cameralist.cpp:287
#, kde-format
msgid "Failed to auto-detect camera; please make sure it is connected properly and is turned on. Would you like to try again?"
"<p>Set this option to load images at their full size for preview, rather than at a reduced size. As this option will make it take longer to load images, only use it if you have a fast computer.</p>"
"<p><b>Note:</b> for Raw images, a half size version of the Raw data is used instead of the embedded JPEG preview.</p>"
+msgid "<b>Note: Album monitoring consumes system resources and can slow down digiKam. If you are using MacOS and network collections, you should not activate album monitoring.</b>"
msgid "If this option is enabled, over- and under-exposure indicators will be displayed only when pure white and pure black color matches, as all color components match the condition in the same time. Otherwise, indicators are turned on when one of the color components matches the condition."
"<para><interface>Non-Destructive Editing and Versioning</interface> allows different versions of an image to be created, whilst always preserving the original image.</para>"
" "
"<para> All steps of the editing history are recorded and can be accessed later.</para>"
"<para>Select the file format in which edited images are saved automatically. Format-specific options, like compression settings, can be configured on the <interface>Format Options</interface> tab.</para>"
"<para>"
"<list>"
"<item><emphasis strong='true'>JPEG</emphasis>: JPEG is the most commonly used file format, but it employs lossy compression, which means that with each saving operation some image information will be irreversibly lost. JPEG offers a good compression rate, resulting in smaller files. </item>"
"<item><emphasis strong='true'>PNG</emphasis>: A widely used format employing lossless compression. The files, though, will be larger because PNG does not achieve very good compression rates.</item>"
"<item><emphasis strong='true'>TIFF</emphasis>: A commonly used format, usually uncompressed or with modest lossless compression. Resulting files will be large, but without quality loss due to compression. </item>"
"<item><emphasis strong='true'>PGF</emphasis>: This is a technically superior file format offering good compression rates with either lossy or lossless compression. But it is not yet widely used and supported, so your friends may not directly be able to open these files, and you may not be able to directly publish them on the web. </item>"
"<item><emphasis strong='true'>JPEG 2000</emphasis>: JPEG 2000 is similar to PGF. Loading or saving is slower, the compression rate is better, and the format more widely supported, though still not comparable to the tradition formats JPEG, PNG or TIFF. </item>"
"<para>First and foremost, the <emphasis>original image will never be overwritten.</emphasis> Instead, when an image is edited, a new file is created: The <interface>current version</interface>.</para>"
" "
"<para>You can also create multiple <interface>versions</interface> deriving from the same <interface>original image</interface>.</para>"
" "
"<para>In addition to these files representing a current version, digiKam can take and keep additional, <interface>intermediate snapshots</interface> during the editing process. This can be useful if you want to preserve the intermediate steps for later access, for example if some editing steps cannot be automatically reproduced.</para>"
"<para>If an image has been edited, only the <interface>current versions</interface> will be shown in the main thumbnail view. From the <interface>right sidebar</interface>, you always have access to all hidden files.</para>"
" "
"<para>With the options here, you can choose to show certain files permanently.</para>"
" "
"<para>If you activate non-destructive editing and image versioning for the first time, it will only be work for newly saved images.</para>"
"<para>In addition to the pixel content, image files usually contain a variety of metadata. A lot of the parameters you can use in digiKam to manage files, such as rating or comment, can be written to the files' metadata.</para>"
" "
"<para>Storing in metadata allows one to preserve this information when moving or sending the files to different systems.</para>"
msgid "Instead of synchronizing metadata, just schedule it for synchronization.Synchronization can be done later by triggering the apply pending, or at digikam exit"
msgid "Turn on this option to write metadata into RAW TIFF/EP files. This feature requires the Exiv2 shared library, version >= 0.18.0. It is still experimental, and is disabled by default."
msgid "Turn off this option to not update file timestamps when files are changed as when you update metadata or image data. Note: disabling this option can introduce some dysfunctions with applications which use file timestamps properties to detect file modifications automatically."
msgid "Turning this option on, will force digiKam to rescan files that has been modified outside digiKam. If a file has changed it is file size or if the last modified timestamp has changed, a rescan of that file will be performed when digiKam starts."
msgid "Turning this option on, will force digiKam to delete the file metadata contained in the database before the file is rescanned. WARNING: if your metadata has been written to the database only and not to the file or sidecar, you will be able to lose inserted metadata such as tags, keywords, or geographic coordinates."
" You can change the contents, rearranging the individual pixels of the image data.<nl/>"
" Or you can set a flag that the file is to be rotated before it is shown.</para>"
" "
"<para>Select this option if you always want to set only a flag. This is less obtrusive, but requires support if the file is accessed with another software. Ensure to allow setting the flag in the metadata if you want to share your files outside digiKam.</para>"
" You can change the contents, rearranging the individual pixels of the image data.<nl/>"
" Or you can set a flag that the file is to be rotated before it is shown.</para>"
" "
"<para>Select this option if you want the file to be rotated by changing the content. This is a lossless operation for JPEG files. For other formats it is a lossy operation, which you need to enable explicitly. It is not support for RAW and other read-only formats, which will be rotated by flag only.</para>"
msgid "For some file formats which apply lossy compression, data will be lost each time the content is rotated. Check this option to allow lossy rotation. If not enabled, these files will be rotated by flag."
msgid "<b>Note: These settings affect the album view and not the image editor. The image editor always changes the image data during the rotation.</b>"
msgid "Turn on this option if you want to apply changes to rating, comments and tags made in Baloo to digiKam's metadata storage. Please note that image metadata will not be edited automatically."
"<p><a href='http://community.kde.org/Baloo'>Baloo</a> provides the basis to handle all kinds of metadata on the KDE desktop in a generic fashion. It allows you to tag, rate and comment your files in KDE applications like Dolphin.</p>"
" "
"<p>Please set here if you want to synchronize the metadata stored by digiKam desktop-wide with the Baloo Desktop Search.</p>"
msgid "Turn on this option to create the XMP sidecar files with a compatible file name (BASENAME.xmp) used by many commercial programs. For Darktable do not enable this option."
"<p>Add file types to be recognised as sidecars.</p>"
"<p>digiKam (optionally) writes metadata to *.xmp sidecar files. Other programs might use different types, which can be specified below. digiKam will neither display these nor read from or write to them. But whenever a matching album item (e.g. \"image.dng\" for \"image.dng.pp3\") is renamed, moved, copied or deleted, the same operation will be done on these sidecar files.</p>"
"<p>Multiple extensions must be separated by a semicolon or a space.</p>"
msgid "<p>Here you can add extra extensions of sidecars files to be processed alongside regular items. These files will not be visible, but regarded as an extension of the main file. Just write \"xyz abc\" to support files with the *.xyz and *.abc extensions. The internally used sidecars type *.xmp is always included.</p>"
msgid "Switching off exif auto rotation will most probably show your images in a wrong orientation, so only change this option if you explicitly require this."
msgid "Switching on this option and your metadata has been written to the database only and not to the file or sidecar, you will be able to lose inserted metadata such as tags, keywords, or geographic coordinates."
"<p><b>Do you really want to enable metadata writing to RAW files?</b></p>"
"<p>DigiKam delegates this task to the Exiv2 library. With different RAW formats, problems are known which can lead to the destruction of RAW files. If you decide to do so, make a backup of your RAW files.</p>"
"<p><b>We strongly recommend not to enable this option.</b></p>"
msgid "You would rather disable writing metadata to RAW files?"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setup.cpp:145
#, kde-format
msgid "Database"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setup.cpp:146
#, kde-format
msgid ""
"<qt>Database Settings<br/>"
"<i>Customize database settings</i></qt>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setup.cpp:151
#, kde-format
msgid "Collections"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setup.cpp:152
#, kde-format
msgid ""
"<qt>Collections Settings<br/>"
"<i>Set root albums locations</i></qt>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setup.cpp:158
#, kde-format
msgid ""
"<qt>Application Views Settings<br/>"
"<i>Customize the look of the views</i></qt>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setup.cpp:163
#, kde-format
msgid "Tool-Tip"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setup.cpp:164
#, kde-format
msgid ""
"<qt>Items Tool-Tip Settings<br/>"
"<i>Customize information in item tool-tips</i></qt>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setup.cpp:175
#, kde-format
msgid "Templates"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setup.cpp:176
#, kde-format
msgid ""
"<qt>Metadata templates<br/>"
"<i>Manage your collection of metadata templates</i></qt>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setup.cpp:182
#, kde-format
msgid ""
"<qt>Image Editor Settings<br/>"
"<i>Customize the image editor settings</i></qt>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setup.cpp:188
#, kde-format
msgid ""
"<qt>Settings for Color Management<br/>"
"<i>Customize the color management settings</i></qt>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setup.cpp:194
#, kde-format
msgid ""
"<qt>Light Table Settings<br/>"
"<i>Customize tool used to compare images</i></qt>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setup.cpp:200
#, kde-format
msgid "<qt>Image Quality Sorter Settings</qt>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setup.cpp:205
#, kde-format
msgid ""
"<qt>Camera Settings<br/>"
"<i>Manage your camera devices</i></qt>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setup.cpp:214
#, kde-format
msgid ""
"<qt>Plug-in Settings<br/>"
"<i>Set which plugins will be accessible from application</i></qt>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setup.cpp:220
#, kde-format
msgid ""
"<qt>Miscellaneous Settings<br/>"
"<i>Customize behavior of the other parts of digiKam</i></qt>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupdatabase.cpp:114
#, kde-format
msgctxt "@title:tab"
msgid "Database Settings"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupdatabase.cpp:122
#, kde-format
msgid ""
"<p>Set the names of directories that you want to ignore from your photo collections. The names are case sensitive and should be separated by a semicolon.</p>"
"<p>This is for example useful when you store your photos on a Synology NAS (Network Attached Storage). In every directory the system creates a subdirectory @eaDir to store thumbnails. To avoid digiKam inserting the original photo and its corresponding thumbnail twice, @eaDir is ignored by default.</p>"
"<p>To re-include directories that are ignored by default prefix it with a minus, e.g. -@eaDir.</p>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupdatabase.cpp:140
#, kde-format
msgid "Additional directories to ignore (<a href='image'>Currently ignored directories</a>):"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupdatabase.cpp:145
#, kde-format
msgid "Enter directories that you want to ignore from adding to your collections."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupdatabase.cpp:166
#, kde-format
msgctxt "@title:tab"
msgid "Ignored Directories"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupdatabase.cpp:265
#, kde-format
msgctxt "@info"
msgid ""
"<p>The process of updating the file hashes takes a few minutes.</p>"
" "
"<p>Please ensure that any important collections on removable media are connected. <i>After the upgrade you cannot use your database with a digiKam version prior to 2.0.</i></p>"
" "
"<p>Do you want to begin the update?</p>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupdatabase.cpp:280
#, kde-format
msgctxt "@title:group"
msgid "Updates"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupdatabase.cpp:283
#, kde-format
msgctxt "@action:button"
msgid "Update File Hashes"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupdatabase.cpp:285
#, kde-format
msgctxt "@info:tooltip"
msgid ""
"<qt>File hashes are used to identify identical files and to display thumbnails. A new, improved algorithm to create the hash is now used. The old algorithm, though, still works quite well, so it is recommended to carry out this upgrade, but not required.<br/>"
" After the upgrade you cannot use your database with a digiKam version prior to 2.0.</qt>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupdatabase.cpp:294
#, kde-format
msgctxt "@info:tooltip"
msgid "Get information about <interface>Update File Hashes</interface>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupdatabase.cpp:318
#, kde-format
msgid ""
"<p>Directories starting with a dot are ignored by default.<br/>"
" <code>%1</code></p>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:188
#, kde-format
msgid "Enable Color Management"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:189
#, kde-format
msgid ""
"<ul>"
"<li>Checked: Color Management is enabled</li>"
"<li>Unchecked: Color Management is disabled</li>"
"</ul>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:196
#, kde-format
msgid "Visit Little CMS project website"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:206
#, kde-format
msgid "Working Color Space"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:212
#, kde-format
msgid "<p>This is the color space all the images will be converted to when opened (if you choose to convert) and the profile that will be embedded when saving. Good and safe choices are <b>Adobe RGB (1998)</b> and <b>sRGB IEC61966-2.1</b></p>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:218
#, kde-format
msgid "<p>You can use this button to get more detailed information about the selected workspace profile.</p>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:232
#, kde-format
msgid "When the profile of an image does not match the working color space"
msgid "<p>If an image has an embedded color profile not matching the working space profile, digiKam will ask if you want to convert to the working space, keep the embedded profile or discard the embedded profile and assign a different one.</p>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:247
#, kde-format
msgid "Convert the image to the working color space"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:248
#, kde-format
msgid "<p>If an image has an embedded color profile not matching the working space profile, digiKam will convert the image's color information to the working color space. This changes the pixel data, but not the appearance of the image.</p>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:264
#, kde-format
msgid "When an image has no color profile information"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:272
#, kde-format
msgid "<p>If an image has no embedded color profile, digiKam will ask which color space shall be used to interpret the image and to which color space it shall be transformed for editing.</p>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:276
#, kde-format
msgid "Assume it is using the sRGB color space (Internet standard)"
msgstr ""
#. i18n("<p></p>"));
#.
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:282
#, kde-format
msgid "and convert it to the working color space"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:295
#, kde-format
msgid "Assume it is using the working color space"
msgstr ""
#. i18n("<p></p>"));
#.
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:301
#, kde-format
msgid "Convert it from default input color space to working space"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:320
#, kde-format
msgid "When loading a RAW file with uncalibrated colors"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:327
#, kde-format
msgid "Ask for the input profile"
msgstr ""
#. i18n("<p></p>"));
#.
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:333
#, kde-format
msgid "Automatic color correction"
msgstr ""
#. i18n("<p></p>"));
#.
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:339
#, kde-format
msgid "Convert it from the default input profile"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:364
#, kde-format
msgid "Color Managed View"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:369
#, kde-format
msgid "Monitor profile:"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:373
#, kde-format
msgid "<p>Select the color profile for your monitor here.</p>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:377
#, kde-format
msgid "<p>You can use this button to get more detailed information about the selected monitor profile.</p>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:381
#, kde-format
msgid "Use color managed view in editor"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:382
#, kde-format
msgid "<p>Turn on this option if you want to use your <b>Monitor Color Profile</b> to show your pictures in the Image Editor window with a color correction adapted to your monitor. You can at any time toggle this option from the Editor window. <i>Warning</i>: This can slow down rendering of the image, depending on the speed of your computer.</p>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:389
#, kde-format
msgid "Use color managed view for previews and thumbnails"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:405
#, kde-format
msgid "Camera and Scanner"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:410
#, kde-format
msgid "Default input color profile:"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:412
#, kde-format
msgid "<p>This is the default color profile for your input device (that is your camera - or your scanner). A camera input profile is recommended for correct conversion of RAW images in 16bit. Some of the options about loading behavior above refer to this profile.</p>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:419
#, kde-format
msgid "<p>You can use this button to get more detailed information about the selected input profile.</p>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:430
#, kde-format
msgid "Printing and Proofing"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:435
#, kde-format
msgid "Output device profile:"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:444
#, kde-format
msgid "<p>You can use this button to get more detailed information about the selected proofing profile.</p>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:455
#, kde-format
msgid "Color Profiles Repository"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:460
#, kde-format
msgid "digiKam looks for ICC profiles in a number of <a href='default'>default locations</a>. You can specify an additional folder:"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:468
#, kde-format
msgid "<p>digiKam searches ICC profiles in default system folders and ships itself a few selected profiles. Store all your additional color profiles in the directory set here.</p>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:491
#, kde-format
msgid "Use black point compensation"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:492
#, kde-format
msgid "<p><b>Black Point Compensation</b> is a way to make adjustments between the maximum black levels of digital files and the black capabilities of various digital devices.</p>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:498
#, kde-format
msgid "Rendering Intents:"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:514
#, kde-format
msgid "Profiles"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:708
#, kde-format
msgid "Monitor Profile From System Settings"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:740
#, kde-format
msgid "No ICC profiles files found."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:756
#, kde-format
msgid "No Display Profile Available"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:758
#, kde-format
msgid "No Output Profile Available"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:892
#, kde-format
msgctxt "none of the paths"
msgid "none"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:901
#, kde-format
msgid ""
"On Windows, the default search paths include "
"<ul>"
"<li>%1/Windows/Spool/Drivers/Color/</li>"
"<li>%2/Windows/Color/</li>"
"</ul>"
"On your system, currently these paths exist and are scanned:"
"<ul>"
"<li>%3</li>"
"</ul>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:916
#, kde-format
msgid ""
"On Mac OS X, the default search paths include "
"<ul>"
"<li>/System/Library/ColorSync/Profiles</li>"
"<li>/Library/ColorSync/Profiles</li>"
"<li>~/Library/ColorSync/Profiles</li>"
"<li>/opt/local/share/color/icc</li>"
"<li>/opt/digikam/share/color/icc</li>"
"<li>~/.local/share/color/icc/</li>"
"<li>~/.local/share/icc/</li>"
"<li>~/.color/icc/</li>"
"</ul>"
"On your system, currently these paths exist and are scanned:"
"<ul>"
"<li>%1</li>"
"</ul>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupicc.cpp:934
#, kde-format
msgid ""
"On Linux, the default search paths include "
"<ul>"
"<li>/usr/share/color/icc</li>"
"<li>/usr/local/share/color/icc</li>"
"<li>~/.local/share/color/icc/</li>"
"<li>~/.local/share/icc/</li>"
"<li>~/.color/icc/</li>"
"</ul>"
"On your system, currently these paths exist and are scanned:"
"<ul>"
"<li>%1</li>"
"</ul>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuplighttable.cpp:99
#, kde-format
msgid "Synchronize panels automatically"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuplighttable.cpp:100
#, kde-format
msgid "Set this option to automatically synchronize zooming and panning between left and right panels if the images have the same size."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuplighttable.cpp:104
#, kde-format
msgid "Selecting a thumbbar item loads the image to the right panel"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuplighttable.cpp:106
#, kde-format
msgid "Set this option to automatically load an image into the right panel when the corresponding item is selected on the thumbbar."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuplighttable.cpp:109
#, kde-format
msgid "Clear the light table on close"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuplighttable.cpp:110
#, kde-format
msgid "Set this option to remove all images from the light table when you close it, or unset it to preserve the images currently on the light table."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:137
#, kde-format
msgid "String comparison type:"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:139
#, kde-format
msgctxt "method to compare strings"
msgid "Natural"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:140
#, kde-format
msgctxt "method to compare strings"
msgid "Normal"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:141
#, kde-format
msgid ""
"<qt>Sets the way in which strings are compared inside digiKam. This eg. influences the sorting of the tree views.<br/>"
"<b>Natural</b> tries to compare strings in a way that regards some normal conventions and will eg. result in sorting numbers naturally even if they have a different number of digits.<br/>"
"<b>Normal</b> uses a more technical approach. Use this style if you eg. want to entitle albums with ISO dates (201006 or 20090523) and the albums should be sorted according to these dates.</qt>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:151
#, kde-format
msgid "Confirm when moving items to the &trash"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:152
#, kde-format
msgid "Confirm when permanently deleting items"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:153
#, kde-format
msgid "Do not confirm when applying changes in the &right sidebar"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:154
#, kde-format
msgid "&Scan for new items at startup (makes startup slower)"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:155
#, kde-format
msgid ""
"Set this option to force digiKam to scan all collections for new items to\n"
"register new elements in database. The scan is performed in the background through\n"
"the progress manager available in the statusbar\n"
" when digiKam main interface\n"
"is loaded. If your computer is fast enough, this will have no effect on usability\n"
"of digiKam while scanning. If your collections are huge or if you use a remote database,\n"
"this can introduce low latency, and it is recommended to disable this option and to plan\n"
"a manual scan through the maintenance tool at the right moment."
"Set this option to force digiKam to clean up the core database from obsolete item entries.\n"
"Entries are only deleted if the connected image/video/audio file was already removed, i.e.\n"
"the database object wastes space.\n"
"This option does not clean up other databases as the thumbnails or recognition db.\n"
"For clean up routines for other databases, please use the maintenance."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:172
#, kde-format
msgid "Show only face tags for assigning names in people sidebar"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:177
#, kde-format
msgid "Lower bound for minimum similarity:"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:183
#, kde-format
msgid "Select here the lower bound of the minimum similarity threshold for fuzzy and duplicates searches. The default value is 40. Selecting a lower value than 40 can make the search <b>really</b> slow."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:213
#, kde-format
msgid "Use native file dialogs from system"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:214
#, kde-format
msgid "Draw frames around grouped items"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:221
#, kde-format
msgid "Set this option to configure how sidebar tab titles are visible. Use \"Only For Active Tab\" option if you use a small screen resolution as with a laptop computer."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:253
#, kde-format
msgctxt "icon theme"
msgid "Adwaita"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:254
#, kde-format
msgctxt "icon theme"
msgid "Breeze"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:255
#, kde-format
msgctxt "icon theme"
msgid "Breeze Dark"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:256
#, kde-format
msgctxt "icon theme"
msgid "Faenza"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:257
#, kde-format
msgctxt "icon theme"
msgid "Ambiance"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:258
#, kde-format
msgctxt "icon theme"
msgid "Humanity"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:259
#, kde-format
msgctxt "icon theme"
msgid "Oxygen"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:314
#, kde-format
msgid "Perform the following operations on all group members:"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:315
#, kde-format
msgid ""
"When images are grouped the following operations<br/>"
"are performed only on the displayed item (No)<br/>"
"or on all the hidden items in the group as well (Yes).<br/>"
"If Ask is selected, there will be a prompt every<br/>"
"time this operation is executed."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:323
#, kde-format
msgid "Ask"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupmisc.cpp:368
#, kde-format
msgctxt "@title:tab"
msgid "Grouping"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setupplugins.cpp:94
#, kde-format
msgctxt "@title:tab"
msgid "Batch Queue Manager"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptemplate.cpp:93
#, kde-format
msgid "Template Title:"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptemplate.cpp:96
#, kde-format
msgid "Enter the metadata template title here."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptemplate.cpp:97
#, kde-format
msgid "<p>Enter the metadata template title here. This title will be used to identify a template in your collection.</p>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptemplate.cpp:107
#, kde-format
msgid "<b>Note: These information are used to set <b><a href='https://en.wikipedia.org/wiki/Extensible_Metadata_Platform'>XMP</a></b> and <b><a href='https://en.wikipedia.org/wiki/IPTC'>IPTC</a></b> tag contents. There is no limitation with XMP, but note that IPTC text tags only support the printable <b><a href='https://en.wikipedia.org/wiki/Ascii'>ASCII</a></b> character set, and tag sizes are limited. Use contextual help for details.</b>"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptemplate.cpp:128
#, kde-format
msgid "&Replace..."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptemplate.cpp:247
#: core/utilities/setup/setuptemplate.cpp:278
#, kde-format
msgid "Cannot register new metadata template without title."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptemplate.cpp:254
#, kde-format
msgid "A metadata template named '%1' already exists."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:195
#, kde-format
msgid "Tool-Tips Font:"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:196
#, kde-format
msgid "Select here the font used to display text in tool-tips."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:204
#, kde-format
msgid "Show icon-view and thumb-bar items' tool-tips"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:205
#, kde-format
msgid "Set this option to display image information when the mouse hovers over an icon-view or thumb-bar item."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:208
#, kde-format
msgid "File/Item Information"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:211
#, kde-format
msgid "File name"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:214
#, kde-format
msgid "File date"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:217
#, kde-format
msgid "File size"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:220
#, kde-format
msgid "Image type"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:223
#, kde-format
msgid "Image dimensions"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:226
#, kde-format
msgid "Image aspect ratio"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:227
#, kde-format
msgid "Set this option to display the image aspect ratio."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:243
#: core/utilities/setup/setuptooltip.cpp:423
#, kde-format
msgid "Camera make and model"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:251
#, kde-format
msgid "Camera date"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:254
#: core/utilities/setup/setuptooltip.cpp:431
#, kde-format
msgid "Camera aperture and focal length"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:258
#: core/utilities/setup/setuptooltip.cpp:435
#, kde-format
msgid "Camera exposure and sensitivity"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:262
#, kde-format
msgid "Camera mode and program"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:266
#: core/utilities/setup/setuptooltip.cpp:439
#, kde-format
msgid "Camera flash settings"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:270
#: core/utilities/setup/setuptooltip.cpp:443
#, kde-format
msgid "Camera white balance settings"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:287
#, kde-format
msgid "digiKam Information"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:290
#: core/utilities/setup/setuptooltip.cpp:363
#, kde-format
msgid "Album name"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:291
#: core/utilities/setup/setuptooltip.cpp:364
#, kde-format
msgid "Set this option to display the album name."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:293
#, kde-format
msgid "Image title"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:294
#, kde-format
msgid "Set this option to display the image title."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:296
#, kde-format
msgid "Image caption"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:297
#, kde-format
msgid "Set this option to display the image captions."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:299
#, kde-format
msgid "Image tags"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:300
#, kde-format
msgid "Set this option to display the image tags."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:302
#, kde-format
msgid "Image labels"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:303
#, kde-format
msgid "Set this option to display the image pick, color, rating labels."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:315
#, kde-format
msgid "Audio/Video Information"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:318
#, kde-format
msgid "Video Aspect Ratio"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:319
#: core/utilities/setup/setuptooltip.cpp:334
#, kde-format
msgid "Set this option to display the Aspect Ratio of the Video."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:322
#, kde-format
msgid "Set this option to display the Audio Bit Rate of the Video."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:325
#, kde-format
msgid "Set this option to display the Audio Channel Type of the Video."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:328
#, kde-format
msgid "Set this option to display the Audio Codec of the Video."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:330
#, kde-format
msgid "Video Duration"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:331
#, kde-format
msgid "Set this option to display the Duration of the Video."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:333
#, kde-format
msgid "Video Frame Rate"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:337
#, kde-format
msgid "Set this option to display the Codec of the Video."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:357
#, kde-format
msgid "Show album items' tool-tips"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:358
#, kde-format
msgid "Album Information"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:360
#: core/utilities/setup/setuptooltip.cpp:401
#, kde-format
msgid "Set this option to display album information when the mouse hovers over a folder-view item."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:366
#, kde-format
msgid "Album date"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:367
#, kde-format
msgid "Set this option to display the album date."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:369
#, kde-format
msgid "Album collection"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:370
#, kde-format
msgid "Set this option to display the album collection."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:372
#, kde-format
msgid "Album category"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:373
#, kde-format
msgid "Set this option to display the album category."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:375
#, kde-format
msgid "Album caption"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:376
#, kde-format
msgid "Set this option to display the album caption."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:378
#, kde-format
msgid "Album preview"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:379
#, kde-format
msgid "Set this option to display the album preview."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:398
#, kde-format
msgid "Show import items' tool-tips"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:399
#, kde-format
msgid "Import Information"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:404
#, kde-format
msgid "Item name"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:405
#, kde-format
msgid "Set this option to display the item name."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:407
#, kde-format
msgid "Item date"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:408
#, kde-format
msgid "Set this option to display the item date."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:410
#, kde-format
msgid "Item size"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:411
#, kde-format
msgid "Set this option to display the item size."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:413
#, kde-format
msgid "Item type"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:414
#, kde-format
msgid "Set this option to display the item type."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:416
#, kde-format
msgid "Item dimensions"
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:417
#, kde-format
msgid "Set this option to display the item dimensions."
msgstr ""
#. +> trunk5
#: core/utilities/setup/setuptooltip.cpp:420
#, kde-format
msgid "Note: these settings require \"Use File Metadata\" option from Camera Setup Behavior page."
"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:531 krita/main.cc:536
#, kde-format
msgid "Krita Tablet Support"
msgstr ""
#. +> trunk5 stable5
#: krita/main.cc:532
#, 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:537
#, 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:294
#, 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>Enter search terms here to add resources to, or remove them from, the current tag view.</p>"
"<p>To filter based on the partial, case insensitive name of a resource:<br/>"
"<tt>partialname</tt> or <tt>!partialname</tt></p>"
"<p>To include or exclude other tag sets:<br/>"
"<tt>[Tagname]</tt> or <tt>![Tagname]</tt></p>"
"<p>For case sensitive and full name matching in-/exclusion:<br/>"
"<tt>\"ExactMatch\"</tt> or <tt>!\"ExactMatch\"</tt></p>"
msgstr ""
#. +> trunk5 stable5
#: libs/resourcewidgets/KisTagFilterWidget.cpp:75
#, kde-format
msgctxt "@info:tooltip"
msgid "<p>Filter results cannot be saved for the <b>All Presets</b> view. In this view, pressing <b>Enter</b> or clearing the filter box will restore all items. Create and/or switch to a different tag if you want to save filtered resources into named sets.</p>"
msgstr ""
#. +> trunk5 stable5
#: libs/resourcewidgets/KisTagFilterWidget.cpp:81
#, kde-format
msgctxt "@info:tooltip"
msgid "<p>Pressing <b>Enter</b> or clicking the <b>Save</b> button will save the changes.</p>"
msgstr ""
#. +> stable5
#: libs/widgets/KoTagFilterWidget.cpp:86
#, kde-format
msgctxt "@info:tooltip"
msgid "<qt>Save the currently filtered set as the new members of the current tag.</qt>"
msgctxt "Heading for the list of Krita authors/developers"
msgid "Authors"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/dialogs/kis_about_application.cpp:98
#, kde-format
msgid ""
"<html><head/><body>"
"<h1 align=\"center\">Backed By</h1>"
"<p>"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/dialogs/kis_about_application.cpp:111
#, kde-format
msgid ""
".</p>"
"<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>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 "Cannot add %1 as a file layer: the file does not exist."
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplication.cpp:666
#, kde-format
msgid ""
"Cannot add the file layer: no document is open.\n"
"\n"
"You can create a new document using the --new-image option, or you can open an existing file.\n"
"\n"
"If you instead want to add the file layer to a document in an already running instance of Krita, check the \"Allow only one instance of Krita\" checkbox in the settings (Settings -> General -> Window)."
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplication.cpp:672
#, kde-format
msgid ""
"Cannot add the file layer: no document is open.\n"
"You can either create a new file using the --new-image option, or you can open an existing file."
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplication.cpp:773
#, kde-format
msgid "Couldn't open file %1"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplication.cpp:792
#, kde-format
msgid "Cannot add the file layer: no document is open."
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplication.cpp:910
#, kde-format
msgid "No template found for: %1"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplication.cpp:913
#, kde-format
msgid "Too many templates found for: %1"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplication.cpp:938
#, kde-format
msgid "Template %1 failed to load."
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplication.cpp:970
#, kde-format
msgid ""
"Krita configurations reset!\n"
"\n"
"Backup file was created at: %1\n"
"\n"
"Restart Krita for changes to take effect."
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplication.cpp:984
#, kde-format
msgid ""
"Failed to clear %1\n"
"\n"
"Please make sure no other program is using the file and try again."
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplication.cpp:1012
#, kde-format
msgid "Do you want to clear the settings file?"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplicationArguments.cpp:80
#, kde-format
msgid "Open a new document with a template"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplicationArguments.cpp:81
#, kde-format
msgid ""
"Create a new image.\n"
"Possible colorspace values are:\n"
" * RGBA\n"
" * XYZA\n"
" * LABA\n"
" * CMYKA\n"
" * GRAY\n"
" * YCbCrA\n"
"Possible channel depth arguments are\n"
" * U8 (8 bits integer)\n"
" * U16 (16 bits integer)\n"
" * F16 (16 bits floating point)\n"
" * F32 (32 bits floating point)\n"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplicationArguments.cpp:95
#, kde-format
msgid "The name of the workspace to open Krita with"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplicationArguments.cpp:96
#, kde-format
msgid "The name of the window layout to open Krita with"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplicationArguments.cpp:97
#, kde-format
msgid "The name of the session to open Krita with"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplicationArguments.cpp:98
#, kde-format
msgid "Start Krita in canvas-only mode"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplicationArguments.cpp:99
#, kde-format
msgid "Do not show the splash screen"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplicationArguments.cpp:100
#, kde-format
msgid "Start Krita in full-screen mode"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplicationArguments.cpp:101
#, kde-format
msgid "Override display DPI"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplicationArguments.cpp:102
#, kde-format
msgid "Export to the given filename and exit"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplicationArguments.cpp:103
#, kde-format
msgid "Export animation to the given filename and exit"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplicationArguments.cpp:104
#, kde-format
msgid "Filename for export"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplicationArguments.cpp:105
#, kde-format
msgid "File layer to be added to existing or new file"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisApplicationArguments.cpp:106
#, kde-format
msgid "File(s) or URL(s) to open"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisAutoSaveRecoveryDialog.cpp:181
#, kde-format
msgctxt "@title:window"
msgid "Recover Files"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisAutoSaveRecoveryDialog.cpp:183
#, kde-format
msgid "Discard All"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisAutoSaveRecoveryDialog.cpp:188
#, kde-format
msgid "The following autosave file can be recovered:"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisAutoSaveRecoveryDialog.cpp:191
#, kde-format
msgid "The following autosave files can be recovered:"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisAutoSaveRecoveryDialog.cpp:238
#, kde-format
msgid ""
"If you select Cancel, all recoverable files will be kept.\n"
"If you press OK, selected files will be recovered, the unselected files discarded."
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisCloneDocumentStroke.cpp:37
msgctxt "(qtundo-format)"
msgid "Clone Document"
msgstr ""
#. +> trunk5 stable5
#: libs/ui/KisDocument.cpp:633
#, kde-format
msgid "%1 cannot be written to. Please save under a different name."
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:492
#, 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:875
#, 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:877
#, 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=\"https://ninedegreesbelow.com\">Elle Stone</a>. This is a summary. Please check <a href=\"https://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=\"https://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>"
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=\"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.</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>"
" <i>Krita depends on another free program called FFmpeg to turn frame-by-frame animations into video files. (<a href=\"https://www.ffmpeg.org\">www.ffmpeg.org</a>)</i><br>"
"<br>"
" To learn more about setting up Krita for rendering animations, <a href=\"https://docs.krita.org/en/reference_manual/render_animation.html#setting-up-krita-for-exporting-animations\">please visit this section of our User Manual.</a>"
msgid "This is a source code archive. Please download the application archive ('Windows Builds'), unpack it and then provide the path to the extracted ffmpeg file."
"<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=\"https://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 "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 "Luminosity of the brush tip image is used as lightness correction for the painting color. Alpha channel of the brush tip image is used as alpha for the final stroke"
msgid "Luminosity value of the brush that will not change the painting color. All brush pixels darker than neutral point will paint with darker color, pixels lighter than neutral point — lighter."
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 adaptation 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."
msgid "Breakpoint is <a href=\"pending\">pending</a>"
msgstr ""
#. +> trunk5 stable5
#: debugger/breakpoint/breakpointdetails.cpp:130
#, kde-format
msgid "Breakpoint is <a href=\"dirty\">dirty</a>"
msgstr ""
#. +> trunk5 stable5
#: debugger/breakpoint/breakpointdetails.cpp:133
#, kde-format
msgid "Breakpoint is active"
msgstr ""
#. +> trunk5 stable5
#: debugger/breakpoint/breakpointdetails.cpp:140
#, kde-format
msgid "Hit %1 time"
msgid_plural "Hit %1 times"
msgstr[0] ""
msgstr[1] ""
#. +> trunk5 stable5
#: debugger/breakpoint/breakpointdetails.cpp:144
#, kde-format
msgid "Breakpoint has errors"
msgstr ""
#. +> trunk5 stable5
#: debugger/breakpoint/breakpointdetails.cpp:157
#, kde-format
msgid ""
"<b>Breakpoint is pending</b>"
"<p>Pending breakpoints are those that have been passed to GDB, but which are not yet installed in the target, because GDB cannot find the function or file to which the breakpoint refers. The most common case is a breakpoint in a shared library: GDB will insert this breakpoint only when the library is loaded.</p>"
msgstr ""
#. +> trunk5 stable5
#: debugger/breakpoint/breakpointdetails.cpp:170
#, kde-format
msgid ""
"<b>Breakpoint is dirty</b>"
"<p>The breakpoint has not yet been passed to the debugger.</p>"
msgid "Displays a list of breakpoints with their current status. Clicking on a breakpoint item allows you to change the breakpoint and will take you to the source in the editor window."
msgid "<b>Frame stack</b>Often referred to as the \"call stack\", this is a list showing which function is currently active, and what called each function to get to this point in your program. By clicking on an item you can see the values in any of the previous calling functions."
"<b>Variable tree</b>The variable tree allows you to see the values of local variables and arbitrary expressions.<br />"
"Local variables are displayed automatically and are updated as you step through your program. For each expression you enter, you can either evaluate it once, or \"watch\" it (make it auto-updated). Expressions that are not auto-updated can be updated manually from the context menu. Expressions can be renamed to more descriptive names by clicking on the name column.<br />"
"To change the value of a variable or an expression, click on the value.<br />"
msgstr ""
#. +> trunk5 stable5
#: debugger/variable/variablewidget.cpp:114
#, kde-format
msgid "<b>Expression entry</b>Type in expression to watch."
msgid "This list should contain targets that the application does not directly depend on, but for which an action needs to be taken before running the application."
msgid "Failed writing to %1, probably the disk is full"
msgstr ""
#. +> trunk5 stable5
#: serialization/itemrepositoryregistry.cpp:81
#, kde-format
msgid "The previous session crashed."
msgid_plural "Session crashed %1 times in a row."
msgstr[0] ""
msgstr[1] ""
#. +> trunk5 stable5
#: serialization/itemrepositoryregistry.cpp:83
#, kde-format
msgctxt "@action"
msgid "Clear cache"
msgstr ""
#. +> trunk5 stable5
#: serialization/itemrepositoryregistry.cpp:84
#, kde-format
msgctxt "@title"
msgid "Session crashed"
msgstr ""
#. +> trunk5 stable5
#: serialization/itemrepositoryregistry.cpp:85
#, kde-format
msgid ""
"The crash may be caused by a corruption of cached data.\n"
"\n"
"Press Clear if you want KDevelop to clear the cache, otherwise press Continue if you are sure the crash has another origin."
msgstr ""
#. +> trunk5 stable5
#: serialization/itemrepositoryregistry.cpp:87
#, kde-format
msgctxt "@action"
msgid "Clear Cache"
msgstr ""
#. +> trunk5 stable5
#: serialization/itemrepositoryregistry.cpp:88
#, kde-format
msgid "Continue"
msgstr ""
#. +> trunk5 stable5
#: shell/areadisplay.cpp:55
#, kde-format
msgid ""
"Execute actions to change the area.<br />"
"An area is a tool view configuration for a specific use case. From here you can also navigate back to the default code area."
msgstr ""
#. +> trunk5 stable5
#: shell/areadisplay.cpp:81
#, kde-format
msgid "Back to code"
msgstr ""
#. +> trunk5 stable5
#: shell/checkerstatus.cpp:50
#, kde-format
msgctxt "@info:progress"
msgid "Running %1"
msgstr ""
#. +> trunk5
#: shell/colorschemechooser.cpp:59
#, kde-format
msgid "&Color Scheme"
msgstr ""
#. +> stable5
#: shell/colorschemechooser.cpp:59
#, kde-format
msgid "&Color Theme"
msgstr ""
#. +> trunk5 stable5
#: shell/configdialog.cpp:44
#, kde-format
msgid "Configure"
msgstr ""
#. +> trunk5 stable5
#: shell/configdialog.cpp:92
#, kde-format
msgid ""
"The settings of the current module have changed.\n"
"Do you want to apply the changes or discard them?"
msgstr ""
#. +> trunk5 stable5
#: shell/configdialog.cpp:93
#, kde-format
msgid "Apply Settings"
msgstr ""
#. +> trunk5 stable5
#: shell/core.cpp:126
#, kde-format
msgid "Could not find any plugins"
msgstr ""
#. +> trunk5 stable5
#: shell/core.cpp:127
#, kde-format
msgid ""
"<p>Could not find any plugins during startup.<br/>"
"Please make sure QT_PLUGIN_PATH is set correctly.</p>"
"Refer to <a href=\"https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source#Set_up_the_runtime_environment\">this article</a> for more information."
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:104
#, kde-format
msgid "Debugger"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:122
#, kde-format
msgid "Frame Stack"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:128
#, kde-format
msgid "Breakpoints"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:134
#, kde-format
msgid "Variables"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:200
#, kde-format
msgid "&Restart"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:201
#, kde-format
msgid "Restart program"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:202
#, kde-format
msgid "Restarts applications from the beginning."
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:208
#, kde-format
msgid "Interrupt"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:209
#, kde-format
msgid "Interrupt application"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:210
#, kde-format
msgid "Interrupts the debugged process or current debugger command."
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:214
#, kde-format
msgid "Run to &Cursor"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:215
#, kde-format
msgid "Run to cursor"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:216
#, kde-format
msgid "Continues execution until the cursor position is reached."
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:221
#, kde-format
msgid "Set E&xecution Position to Cursor"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:222
#, kde-format
msgid "Jump to cursor"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:223
#, kde-format
msgid "Continue execution from the current cursor position."
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:227
#, kde-format
msgid "Step &Over"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:229
#, kde-format
msgid "Step over the next line"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:230
#, kde-format
msgid "Executes one line of source in the current source file. If the source line is a call to a function the whole function is executed and the app will stop at the line following the function call."
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:238
#, kde-format
msgid "Step over Ins&truction"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:239
#, kde-format
msgid "Step over instruction"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:240
#, kde-format
msgid "Steps over the next assembly instruction."
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:245
#, kde-format
msgid "Step &Into"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:247
#, kde-format
msgid "Step into the next statement"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:248
#, kde-format
msgid "Executes exactly one line of source. If the source line is a call to a function then execution will stop after the function has been entered."
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:255
#, kde-format
msgid "Step into I&nstruction"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:256
#, kde-format
msgid "Step into instruction"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:257
#, kde-format
msgid "Steps into the next assembly instruction."
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:261
#, kde-format
msgid "Step O&ut"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:263
#, kde-format
msgid "Step out of the current function"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:264
#, kde-format
msgid "Executes the application until the currently executing function is completed. The debugger will then display the line after the original call to that function. If program execution is in the outermost frame (i.e. in main()) then this operation has no effect."
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:272
#, kde-format
msgid "Toggle Breakpoint"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:273
#, kde-format
msgid "Ctrl+Alt+B"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:274
#, kde-format
msgid "Toggle breakpoint"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:275
#, kde-format
msgid "Toggles the breakpoint at the current line in editor."
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:279
#, kde-format
msgid "Show Current Line"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:280
#, kde-format
msgid "Show the current execution position"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:281
#, kde-format
msgid "Jumps to the execution line in the editor."
msgid "Executes the target or the program specified in currently active launch configuration inside a Debugger."
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:441
#, kde-format
msgid "&Continue"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:443
#, kde-format
msgid "Continue application execution"
msgstr ""
#. +> trunk5 stable5
#: shell/debugcontroller.cpp:444
#, kde-format
msgid "Continues the execution of your application in the debugger. This only takes effect when the application has been halted by the debugger (i.e. a breakpoint has been activated or the interrupt was pressed)."
msgid "Unable to create hidden dir (%1) for developer file"
msgstr ""
#. +> trunk5 stable5
#: shell/project.cpp:281
#, kde-format
msgid "Unable to get project file: %1"
msgstr ""
#. +> trunk5 stable5
#: shell/project.cpp:321
#, kde-format
msgid "Could not load %1, a project with the same name '%2' is already open."
msgstr ""
#. +> trunk5 stable5
#: shell/project.cpp:352
#, kde-format
msgid ""
"Could not load project management plugin <b>%1</b>.<br>"
"Check that the required programs are installed, or see console output for more information."
msgstr ""
#. +> trunk5 stable5
#: shell/project.cpp:362
#, kde-format
msgid "The project importing plugin (%1) does not support the IProjectFileManager interface."
msgstr ""
#. +> trunk5 stable5
#: shell/project.cpp:415
#, kde-format
msgid "Could not open project."
msgstr ""
#. +> trunk5 stable5
#: shell/project.cpp:573
#, kde-format
msgid ""
"Could not store developer specific project configuration.\n"
"Attention: The project settings you changed will be lost."
msgstr ""
#. +> trunk5 stable5
#: shell/projectcontroller.cpp:174
#, kde-format
msgid "Configure Project %1"
msgstr ""
#. +> trunk5 stable5
#: shell/projectcontroller.cpp:317
#, kde-format
msgid "Invalid Location: %1"
msgstr ""
#. +> trunk5 stable5
#: shell/projectcontroller.cpp:327
#, kde-format
msgid "Already opening %1, not opening again"
msgstr ""
#. +> trunk5 stable5
#: shell/projectcontroller.cpp:489
#, kde-format
msgid "Override"
msgstr ""
#. +> trunk5 stable5
#: shell/projectcontroller.cpp:490
#, kde-format
msgctxt "@info:tooltip"
msgid "Continue to open the project and use the just provided project configuration."
msgstr ""
#. +> trunk5 stable5
#: shell/projectcontroller.cpp:493
#, kde-format
msgid "Open Existing File"
msgstr ""
#. +> trunk5 stable5
#: shell/projectcontroller.cpp:494
#, kde-format
msgctxt "@info:tooltip"
msgid "Continue to open the project but use the existing project configuration."
msgstr ""
#. +> trunk5 stable5
#: shell/projectcontroller.cpp:497
#, kde-format
msgctxt "@info:tooltip"
msgid "Cancel and do not open the project."
msgstr ""
#. +> trunk5 stable5
#: shell/projectcontroller.cpp:499
#, kde-format
msgid ""
"There already exists a project configuration file at %1.\n"
"Do you want to override it or open the existing file?"
msgstr ""
#. +> trunk5 stable5
#: shell/projectcontroller.cpp:501
#, kde-format
msgid "Override existing project configuration"
msgstr ""
#. +> trunk5 stable5
#: shell/projectcontroller.cpp:521
#, kde-format
msgid "Unable to create configuration file %1"
msgstr ""
#. +> trunk5 stable5
#: shell/projectcontroller.cpp:535
#, kde-format
msgid "Reopen the current project?"
msgstr ""
#. +> trunk5 stable5
#: shell/projectcontroller.cpp:574
#, kde-format
msgctxt "@action"
msgid "Open / Import Project..."
msgstr ""
#. +> trunk5 stable5
#: shell/projectcontroller.cpp:575
#, kde-format
msgctxt "@info:tooltip"
msgid "Open or import project"
msgstr ""
#. +> trunk5 stable5
#: shell/projectcontroller.cpp:576
#, kde-format
msgctxt "@info:whatsthis"
msgid "Open an existing KDevelop 4 project or import an existing Project into KDevelop 4. This entry allows one to select a KDevelop4 project file or an existing directory to open it in KDevelop. When opening an existing directory that does not yet have a KDevelop4 project file, the file will be created."
msgstr ""
#. +> trunk5 stable5
#: shell/projectcontroller.cpp:587
#, kde-format
msgctxt "@action"
msgid "Fetch Project..."
msgstr ""
#. +> trunk5 stable5
#: shell/projectcontroller.cpp:589
#, kde-format
msgctxt "@info:tooltip"
msgid "Fetch project"
msgstr ""
#. +> trunk5 stable5
#: shell/projectcontroller.cpp:590
#, kde-format
msgctxt "@info:whatsthis"
msgid "Guides the user through the project fetch and then imports it into KDevelop 4."
msgid "The current launch configuration does not support the '%1' mode."
msgstr ""
#. +> trunk5 stable5
#: shell/runcontroller.cpp:440
#, kde-format
msgid "Configure Launches..."
msgstr ""
#. +> trunk5 stable5
#: shell/runcontroller.cpp:443
#, kde-format
msgid "Open Launch Configuration Dialog"
msgstr ""
#. +> trunk5 stable5
#: shell/runcontroller.cpp:444
#, kde-format
msgctxt "@info:tooltip"
msgid "Open Launch Configuration Dialog"
msgstr ""
#. +> trunk5 stable5
#: shell/runcontroller.cpp:445
#, kde-format
msgctxt "@info:whatsthis"
msgid "Opens a dialog to setup new launch configurations, or to change the existing ones."
msgstr ""
#. +> trunk5 stable5
#: shell/runcontroller.cpp:448
#, kde-format
msgid "Execute Launch"
msgstr ""
#. +> trunk5 stable5
#: shell/runcontroller.cpp:449
#, kde-format
msgctxt "Short text for 'Execute launch' used in the toolbar"
msgid "Execute"
msgstr ""
#. +> trunk5 stable5
#: shell/runcontroller.cpp:451
#, kde-format
msgctxt "@info:tooltip"
msgid "Execute current launch"
msgstr ""
#. +> trunk5 stable5
#: shell/runcontroller.cpp:452
#, kde-format
msgid "Execute current launch"
msgstr ""
#. +> trunk5 stable5
#: shell/runcontroller.cpp:453
#, kde-format
msgctxt "@info:whatsthis"
msgid "Executes the target or the program specified in currently active launch configuration."
msgstr ""
#. +> trunk5 stable5
#: shell/runcontroller.cpp:459
#, kde-format
msgctxt "Short text for 'Debug launch' used in the toolbar"
msgid "Debug"
msgstr ""
#. +> trunk5 stable5
#: shell/runcontroller.cpp:460
#, kde-format
msgctxt "@info:tooltip"
msgid "Debug current launch"
msgstr ""
#. +> trunk5 stable5
#: shell/runcontroller.cpp:462
#, kde-format
msgctxt "@info:whatsthis"
msgid "Executes the target or the program specified in currently active launch configuration inside a Debugger."
msgstr ""
#. i18n("Profile Launch"), this);
#. profileAction->setToolTip(i18nc("@info:tooltip", "Profile current launch"));
#. profileAction->setStatusTip(i18n("Profile current launch"));
#. profileAction->setWhatsThis(i18nc("@info:whatsthis", "Executes the target or the program specified in currently active launch configuration inside a Profiler."));
"<p>When a project contains more files than this number, the project will be\n"
"parsed in simplified mode, increasing the efficiency by gathering less information. Global code navigation and quickopen capabilities will be reduced.</p>"
# This file is distributed under the same license as the PROJECT project.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2020.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PROJECT VERSION\n"
"Report-Msgid-Bugs-To: EMAIL@ADDRESS\n"
-"POT-Creation-Date: 2020-04-20 09:26+0200\n"
+"POT-Creation-Date: 2020-04-22 08:19+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"
#. # Dear potential translators: Thank you for your interest in KDE
#. Connect! We do not actually handle our own translations. All
#. translations for all KDE apps are handled by the [localization
#. team](https://l10n.kde.org). We really appreciate your translations,
#. but make sure to submit them by working with the proper team!
#. +> trunk5
msgctxt "kde_connect"
msgid "KDE Connect"
msgstr ""
#. +> trunk5
msgctxt "foreground_notification_no_devices"
msgid "Not connected to any device"
msgstr ""
#. +> trunk5
#, c-format
msgctxt "foreground_notification_devices"
msgid "Connected to: %s"
msgstr ""
#. +> trunk5
+msgctxt "foreground_notification_send_clipboard"
+msgid "Send Clipboard"
+msgstr ""
+
+#. +> trunk5
msgctxt "pref_plugin_telephony"
msgid "Telephony notifier"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_telephony_desc"
msgid "Send notifications for incoming calls"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_battery"
msgid "Battery report"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_battery_desc"
msgid "Periodically report battery status"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_sftp"
msgid "Filesystem expose"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_sftp_desc"
msgid "Allows to browse this device's filesystem remotely"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_clipboard"
msgid "Clipboard sync"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_clipboard_desc"
msgid "Share the clipboard content"
msgstr ""
#. +> trunk5
+msgctxt "pref_plugin_clipboard_sent"
+msgid "Clipboard Sent"
+msgstr ""
+
+#. +> trunk5
msgctxt "pref_plugin_mousepad"
msgid "Remote input"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_mousepad_desc"
msgid "Use your phone or tablet as a touchpad and keyboard"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_presenter"
msgid "Slideshow remote"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_presenter_desc"
msgid "Use your device to change slides in a presentation"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_remotekeyboard"
msgid "Receive remote keypresses"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_remotekeyboard_desc"
msgid "Receive keypress events from remote devices"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_mpris"
msgid "Multimedia controls"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_mpris_desc"
msgid "Provides a remote control for your media player"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_runcommand"
msgid "Run Command"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_runcommand_desc"
msgid "Trigger remote commands from your phone or tablet"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_contacts"
msgid "Contacts Synchronizer"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_contacts_desc"
msgid "Allow synchronizing the device's contacts book"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_ping"
msgid "Ping"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_ping_desc"
msgid "Send and receive pings"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_notifications"
msgid "Notification sync"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_notifications_desc"
msgid "Access your notifications from other devices"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_receive_notifications"
msgid "Receive notifications"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_receive_notifications_desc"
msgid "Receive notifications from the other device and display them on Android"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_sharereceiver"
msgid "Share and receive"
msgstr ""
#. +> trunk5
msgctxt "pref_plugin_sharereceiver_desc"
msgid "Share files and URLs between devices"
msgstr ""
#. +> trunk5
msgctxt "device_list_empty"
msgid "No devices"
msgstr ""
#. +> trunk5
msgctxt "ok"
msgid "OK"
msgstr ""
#. +> trunk5
msgctxt "sad_ok"
msgid "OK :("
msgstr ""
#. +> trunk5
msgctxt "cancel"
msgid "Cancel"
msgstr ""
#. +> trunk5
msgctxt "open_settings"
msgid "Open settings"
msgstr ""
#. +> trunk5
msgctxt "no_permissions"
msgid "You need to grant permission to access notifications"
msgstr ""
#. +> trunk5
msgctxt "no_permission_mprisreceiver"
msgid "To be able to control your media players you need to grant access to the notifications"
msgstr ""
#. +> trunk5
msgctxt "no_permissions_remotekeyboard"
msgid "To receive keypresses you need to activate the KDE Connect Remote Keyboard"
msgstr ""
#. +> trunk5
msgctxt "send_ping"
msgid "Send ping"
msgstr ""
#. +> trunk5
msgctxt "open_mpris_controls"
msgid "Multimedia control"
msgstr ""
#. +> trunk5
msgctxt "remotekeyboard_editing_only_title"
msgid "Handle remote keys only when editing"
msgstr ""
#. +> trunk5
msgctxt "remotekeyboard_not_connected"
msgid "There is no active remote keyboard connection, establish one in kdeconnect"
msgstr ""
#. +> trunk5
msgctxt "remotekeyboard_connected"
msgid "Remote keyboard connection is active"
msgstr ""
#. +> trunk5
msgctxt "remotekeyboard_multiple_connections"
msgid "There is more than one remote keyboard connection, select the device to configure"
msgstr ""
#. +> trunk5
msgctxt "open_mousepad"
msgid "Remote input"
msgstr ""
#. +> trunk5
msgctxt "mousepad_info"
msgid "Move a finger on the screen to move the mouse cursor. Tap for a click, and use two/three fingers for right and middle buttons. Use 2 fingers to scroll. Use a long press to drag'n drop."
msgid "Keeping the window thumbnail always interferes with the minimized state of windows. This can result in windows not suspending their work when minimized."
msgid "<b>Julia</b> is a high-level, high-performance dynamic programming language for technical computing, with syntax that is familiar to users of other technical computing environments. It provides a sophisticated compiler, distributed parallel execution, numerical accuracy, and an extensive mathematical function library."
msgstr ""
#. +> trunk5 stable5
#: backends/julia/juliabackend.cpp:85
#, kde-format
msgctxt "The url to the documentation of Julia, please check if there is a translated version and use the correct url"
msgid "https://docs.julialang.org/en/latest/"
msgstr ""
#. +> trunk5 stable5
#: backends/julia/juliabackend.cpp:101
#, kde-format
msgid "The path to Julia specified in the application settings must point directly to the executable. Symlinks are not allowed. Please provide the correct path in the application settings and try again."
msgid "Сantor couldn’t determine the version of Julia for %1. Please specify the correct path to Julia executable (no symlinks allowed) and try again."
msgstr ""
#. +> trunk5 stable5
#: backends/julia/juliabackend.cpp:141
#, kde-format
msgid "You are trying to use Cantor with Julia v%1.%2.%3. This version of Cantor was compiled with the support of Julia v%4.%5.%6. Please point to this version of Julia or recompile Cantor using the version %1.%2.%3."
msgstr ""
#. i18n: ectx: label, entry (replPath), group (JuliaBackend)
msgid "<b>Lua</b> is a fast and lightweight scripting language, with a simple procedural syntax. There are several libraries in Lua aimed at math and science."
msgstr ""
#. i18n: ectx: label, entry (Path), group (LuaBackend)
msgid "<b>Maxima</b> is a system for the manipulation of symbolic and numerical expressions, including differentiation, integration, Taylor series, Laplace transforms, ordinary differential equations, systems of linear equations, polynomials, and sets, lists, vectors, matrices, and tensors. Maxima yields high precision numeric results by using exact fractions, arbitrary precision integers, and variable precision floating point numbers. Maxima can plot functions and data in two and three dimensions."
msgstr ""
#. i18n: ectx: label, entry (Path), group (MaximaBackend)
#. +> trunk5 stable5
#: backends/maxima/maximabackend.kcfg:10
#, kde-format
msgid "Path to the Maxima executable"
msgstr ""
#. i18n: ectx: label, entry (localDoc), group (MaximaBackend)
#. +> trunk5 stable5
#: backends/maxima/maximabackend.kcfg:14
#, kde-format
msgid "Url to the local Maxima documentation"
msgstr ""
#. +> trunk5 stable5
#: backends/maxima/maximaexpression.cpp:118
#, kde-format
msgid "Error: Too many */"
msgstr ""
#. +> trunk5 stable5
#: backends/maxima/maximaexpression.cpp:131
#, kde-format
msgid "Error: Too many /*"
msgstr ""
#. +> trunk5 stable5
#: backends/maxima/maximaexpression.cpp:137
#, kde-format
msgid "Error: expected \" before ;"
msgstr ""
#. +> trunk5 stable5
#: backends/maxima/maximaexpression.cpp:358
#, kde-format
msgid "Waiting for the plot result"
msgstr ""
#. +> trunk5 stable5
#: backends/maxima/maximaextensions.cpp:46
#, kde-format
msgid "Maxima batch file (*.mac)"
msgstr ""
#. +> trunk5 stable5
#: backends/maxima/maximasession.cpp:188
#, kde-format
msgid "Failed to start Maxima"
msgstr ""
#. +> trunk5 stable5
#: backends/maxima/maximasession.cpp:275
#, kde-format
msgid "Maxima crashed. restarting..."
msgstr ""
#. +> trunk5 stable5
#: backends/maxima/maximasession.cpp:289
#, kde-format
msgid "Maxima crashed twice within a short time. Stopping to try starting"
msgctxt "the url to the documentation of Octave, please check if there is a translated version (currently Czech and Japanese) and use the correct url"
msgid "https://octave.org/doc/interpreter/"
msgstr ""
#. +> trunk5 stable5
#: backends/octave/octavebackend.cpp:82
#, kde-format
msgid ""
"<b>GNU Octave</b> is a high-level language, primarily intended for numerical computations. <br/>"
"It provides a convenient command line interface for solving linear and nonlinear problems numerically, and for performing other numerical experiments using a language that is mostly compatible with Matlab."
msgstr ""
#. i18n: ectx: label, entry (Path), group (OctaveBackend)
#. +> trunk5 stable5
#: backends/octave/octavebackend.kcfg:10
#, kde-format
msgid "Path to the Octave executable"
msgstr ""
#. i18n: ectx: label, entry (localDoc), group (SageBackend)
#. i18n: ectx: label, entry (localDoc), group (OctaveBackend)
msgid "<b>Python</b> is a remarkably powerful dynamic programming language that is used in a wide variety of application domains. There are several Python packages to scientific programming."
msgstr ""
#. i18n: ectx: label, entry (pythonServerPath), group (PythonBackend)
#. +> trunk5 stable5
#: backends/python/pythonbackend.kcfg:10
#, kde-format
msgid "Path to Cantor python server executable"
msgstr ""
#. i18n: ectx: label, entry (localDoc), group (PythonBackend)
#. +> trunk5 stable5
#: backends/python/pythonbackend.kcfg:14
#, kde-format
msgid "Url to the local Python documentation"
msgstr ""
#. +> trunk5 stable5
#: backends/python/pythonextensions.cpp:184
#, kde-format
msgid "Python script file (*.py)"
msgstr ""
#. +> trunk5 stable5
#: backends/python/pythonsession.cpp:267
#, kde-format
msgid "Cantor Python server stopped working."
msgstr ""
#. +> trunk5 stable5
#: backends/python/pythonsession.cpp:271
#, kde-format
msgid "Failed to start Cantor python server."
msgstr ""
#. +> trunk5 stable5
#: backends/python/pythonsession.cpp:275
#, kde-format
msgid "Communication with Cantor python server failed for unknown reasons."
msgid "<b>Qalculate!</b> is not your regular software replication of the cheapest available calculator. Qalculate! aims to make full use of the superior interface, power and flexibility of modern computers. The center of attention in Qalculate! is the expression entry. Instead of entering each number in a mathematical expression separately, you can directly write the whole expression and later modify it. The interpretation of expressions is flexible and fault tolerant, and if you nevertheless do something wrong, Qalculate! will tell you so. Not fully solvable expressions are however not errors. Qalculate! will simplify as far as it can and answer with an expression. In addition to numbers and arithmetic operators, an expression may contain any combination of variables, units, and functions."
msgstr ""
#. i18n: ectx: label, entry (postConversion), group (QalculateBackend)
#. +> trunk5 stable5
#: backends/qalculate/qalculatebackend.kcfg:9
#, kde-format
msgid "If and how units will be automatically converted. If true, convert to the best suited SI units (the least amount of units)."
msgstr ""
#. i18n: ectx: label, entry (angleUnit), group (QalculateBackend)
#. +> trunk5 stable5
#: backends/qalculate/qalculatebackend.kcfg:13
#, kde-format
msgid "Default angle unit for trigonometric functions."
msgstr ""
#. i18n: ectx: label, entry (base), group (QalculateBackend)
#. +> trunk5 stable5
#: backends/qalculate/qalculatebackend.kcfg:23
#, kde-format
msgid "Base of parsed and evaluated numbers."
msgstr ""
#. i18n: ectx: label, entry (structuring), group (QalculateBackend)
#. +> trunk5 stable5
#: backends/qalculate/qalculatebackend.kcfg:32
#, kde-format
msgid "If the evaluation result will be simplified or factorized."
msgstr ""
#. i18n: ectx: label, entry (fractionFormat), group (QalculateBackend)
#. +> trunk5 stable5
#: backends/qalculate/qalculatebackend.kcfg:42
#, kde-format
msgid "If rational numbers will be displayed with decimals, as a fraction, or something in between."
msgstr ""
#. i18n: ectx: label, entry (indicateInfiniteSeries), group (QalculateBackend)
#. +> trunk5 stable5
#: backends/qalculate/qalculatebackend.kcfg:46
#, kde-format
msgid "Show that the digit series of a number continues forever with three dots, instead of rounding (ex. 2/3 displays as 0.666666... instead of 0.666667)."
msgstr ""
#. i18n: ectx: label, entry (useAllPrefixes), group (QalculateBackend)
#. +> trunk5 stable5
#: backends/qalculate/qalculatebackend.kcfg:50
#, kde-format
msgid "Use all decimal SI prefixes. If false, prefixes which is not a multiple of thousand (centi, deci, deca, hecto) will not be used automatically."
msgstr ""
#. i18n: ectx: label, entry (negativeExponents), group (QalculateBackend)
#. +> trunk5 stable5
#: backends/qalculate/qalculatebackend.kcfg:54
#, kde-format
msgid "If true, negative exponents will be used instead of division (ex. 5/x^2 becomes 5*x^-2)."
msgstr ""
#. i18n: ectx: label, entry (minExp), group (QalculateBackend)
#. +> trunk5 stable5
#: backends/qalculate/qalculatebackend.kcfg:64
#, kde-format
msgid "Numerical display."
msgstr ""
#. i18n: ectx: label, entry (inlinePlot), group (QalculateBackend)
#. +> trunk5 stable5
#: backends/qalculate/qalculatebackend.kcfg:68
#, kde-format
msgid "If true, plots will be displayed inside the worksheet. If not they appear in a separate window."
msgstr ""
#. i18n: ectx: label, entry (coloredPlot), group (QalculateBackend)
#. +> trunk5 stable5
#: backends/qalculate/qalculatebackend.kcfg:72
#, kde-format
msgid "Whether colors should be used in plots."
msgstr ""
#. i18n: ectx: label, entry (plotGrid), group (QalculateBackend)
#. +> trunk5 stable5
#: backends/qalculate/qalculatebackend.kcfg:76
#, kde-format
msgid "Whether a grid should be plotted."
msgstr ""
#. i18n: ectx: label, entry (plotBorder), group (QalculateBackend)
#. +> trunk5 stable5
#: backends/qalculate/qalculatebackend.kcfg:80
#, kde-format
msgid "Whether full borders should be drawn around the plot."
msgstr ""
#. i18n: ectx: label, entry (plotLineWidth), group (QalculateBackend)
#. +> trunk5 stable5
#: backends/qalculate/qalculatebackend.kcfg:84
#, kde-format
msgid "Width of lines, in pixels."
msgstr ""
#. i18n: ectx: label, entry (plotSteps), group (QalculateBackend)
#. +> trunk5 stable5
#: backends/qalculate/qalculatebackend.kcfg:88
#, kde-format
msgid "Number of interpolation steps to be used in plotting."
msgstr ""
#. i18n: ectx: label, entry (plotSmoothing), group (QalculateBackend)
#. +> trunk5 stable5
#: backends/qalculate/qalculatebackend.kcfg:99
#, kde-format
msgid "Smoothing mode in plots."
msgstr ""
#. i18n: ectx: label, entry (plotStyle), group (QalculateBackend)
#. +> trunk5 stable5
#: backends/qalculate/qalculatebackend.kcfg:113
#, kde-format
msgid "Style of plots."
msgstr ""
#. i18n: ectx: label, entry (plotLegend), group (QalculateBackend)
#. +> trunk5 stable5
#: backends/qalculate/qalculatebackend.kcfg:126
#, kde-format
msgid "Legend position in plots."
msgstr ""
#. +> trunk5 stable5
#: backends/qalculate/qalculateexpression.cpp:157
#, kde-format
msgid "Qalculate reports it cannot print. Is gnuplot installed?"
msgstr ""
#. +> trunk5 stable5
#: backends/qalculate/qalculateexpression.cpp:178
#, kde-format
msgid "missing %1"
msgstr ""
#. +> trunk5 stable5
#: backends/qalculate/qalculateexpression.cpp:268
#, kde-format
msgid "%1 must be a number."
msgstr ""
#. +> trunk5 stable5
#: backends/qalculate/qalculateexpression.cpp:269
#, kde-format
msgid "%1 must be a integer."
msgstr ""
#. +> trunk5 stable5
#: backends/qalculate/qalculateexpression.cpp:270
#, kde-format
msgid "%1 must be a boolean."
msgstr ""
#. +> trunk5 stable5
#: backends/qalculate/qalculateexpression.cpp:271
#, kde-format
msgid "invalid option for %1: %2"
msgstr ""
#. +> trunk5 stable5
#: backends/qalculate/qalculateexpression.cpp:598
#, kde-format
msgid "found multiple expressions in one plot command (%1 and %2)."
msgctxt "the url to the documentation of R, please check if there is a translated version and use the correct url"
msgid "https://cran.r-project.org/manuals.html"
msgstr ""
#. +> trunk5 stable5
#: backends/R/rbackend.cpp:99
#, kde-format
msgid ""
"<b>R</b> is a language and environment for statistical computing and graphics, similar to the S language and environment. <br/>"
"It provides a wide variety of statistical (linear and nonlinear modelling, classical statistical tests, time-series analysis, classification, clustering, ...) and graphical techniques, and is highly extensible. The S language is often the vehicle of choice for research in statistical methodology, and R provides an Open Source route to participation in that activity."
msgid "<b>Scilab</b> is a free software, cross-platform numerical computational package and a high-level, numerically oriented programming language.Scilab is distributed under CeCILL license (GPL compatible)."
msgstr ""
#. i18n: ectx: label, entry (Path), group (ScilabBackend)
#. +> trunk5 stable5
#: backends/scilab/scilabbackend.kcfg:10
#, kde-format
msgid "Path to scilab-adv-cli command (Warning: Scilab version must better or equal than 5.4 version)"
msgstr ""
#. +> trunk5 stable5
#: backends/scilab/scilabextensions.cpp:38
#, kde-format
msgid ";;Scilab script file (*.sce);;Scilab function file (*.sci)"
"There is useful data available in Alternate Translations view.\n"
"\n"
"For Gettext PO files it displays difference between current source text and the source text corresponding to the fuzzy translation found by msgmerge when updating PO based on POT template.\n"
"\n"
"Do you want to show the view with the data?"
msgstr ""
#. +> trunk5 stable5
#: src/alttransview.cpp:247
#, kde-format
msgctxt "@info:tooltip"
msgid ""
"<p>Sometimes, if source text is changed, its translation becomes deprecated and is either marked as <emphasis>needing review</emphasis> (i.e. looses approval status), or (only in case of XLIFF file) moved to the <emphasis>alternate translations</emphasis> section accompanying the unit.</p>"
"<p>This toolview also shows the difference between current source string and the previous source string, so that you can easily see which changes should be applied to existing translation to make it reflect current source.</p>"
"<p>Double-clicking any word in this toolview inserts it into translation.</p>"
"<p>Drop translation file onto this toolview to use it as a source for additional alternate translations.</p>"
msgstr ""
#. +> trunk5 stable5
#: src/alttransview.cpp:268
#, kde-format
msgctxt "@info:tooltip"
msgid "Origin: %1"
msgstr ""
#. +> trunk5 stable5
#: src/alttransview.cpp:291
#, kde-format
msgctxt "@item Undo action"
msgid "Use alternate translation"
msgstr ""
#. +> trunk5 stable5
#: src/binunitsview.cpp:123
#, kde-format
msgid "no"
msgstr ""
#. +> trunk5 stable5
#: src/binunitsview.cpp:123
#, kde-format
msgid "yes"
msgstr ""
#. +> trunk5 stable5
#: src/binunitsview.cpp:139
#, kde-format
msgctxt "@title:column"
msgid "Source"
msgstr ""
#. +> trunk5 stable5
#: src/binunitsview.cpp:140
#, kde-format
msgctxt "@title:column"
msgid "Target"
msgstr ""
#. +> trunk5 stable5
#: src/binunitsview.cpp:141
#, kde-format
msgctxt "@title:column"
msgid "Approved"
msgstr ""
#. +> trunk5 stable5
#: src/binunitsview.cpp:149
#, kde-format
msgctxt "@title toolview name"
msgid "Binary Units"
msgstr ""
#. +> trunk5 stable5
#: src/binunitsview.cpp:187
#, kde-format
msgctxt "@action:inmenu"
msgid "Set the file"
msgstr ""
#. +> trunk5 stable5
#: src/binunitsview.cpp:188
#, kde-format
msgctxt "@action:inmenu"
msgid "Use source file"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalog.cpp:77
#, kde-format
msgid "All supported files (*.po *.pot *.xlf *.xliff *.ts)"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalog.cpp:78
#, kde-format
msgid "Gettext (*.po *.pot)"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalog.cpp:78
#, kde-format
msgid "Gettext (*.po)"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalog.cpp:78
#, kde-format
msgid "XLIFF (*.xlf *.xliff)"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalog.cpp:78
#, kde-format
msgid "Linguist (*.ts)"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalog.cpp:84
#, kde-format
msgid "New"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalog.cpp:84
#, kde-format
msgid "Needs translation"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalog.cpp:84
#, kde-format
msgid "Needs full localization"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalog.cpp:84
#, kde-format
msgid "Needs adaptation"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalog.cpp:84
#, kde-format
msgid "Translated"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalog.cpp:85
#, kde-format
msgid "Needs translation review"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalog.cpp:85
#, kde-format
msgid "Needs full localization review"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalog.cpp:85
#, kde-format
msgid "Needs adaptation review"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalog.cpp:85
#, kde-format
msgid "Final"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalog.cpp:86
#, kde-format
msgid "Signed-off"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:75
#, kde-format
msgctxt "XLIFF inline tag name"
msgid "Start of paired tag"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:76
#, kde-format
msgctxt "XLIFF inline tag name"
msgid "End of paired tag"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:77
#, kde-format
msgctxt "XLIFF inline tag name"
msgid "Stand-alone tag"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:78
#, kde-format
msgctxt "XLIFF inline tag name"
msgid "Isolated tag"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:80
#, kde-format
msgctxt "XLIFF inline tag name"
msgid "Marker"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:81
#, kde-format
msgctxt "XLIFF inline tag name"
msgid "Generic group placeholder"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:82
#, kde-format
msgctxt "XLIFF inline tag name"
msgid "Sub-flow"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:84
#, kde-format
msgctxt "XLIFF inline tag name"
msgid "Generic placeholder"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:85
#, kde-format
msgctxt "XLIFF inline tag name"
msgid "Start of paired placeholder"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:86
#, kde-format
msgctxt "XLIFF inline tag name"
msgid "End of paired placeholder"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:133
#, kde-format
msgctxt "XLIFF mark type"
msgid "abbreviation"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:134
#, kde-format
msgctxt "XLIFF mark type"
msgid "abbreviated form: a term resulting from the omission of any part of the full term while designating the same concept"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:135
#, kde-format
msgctxt "XLIFF mark type"
msgid "abbreviation: an abbreviated form of a simple term resulting from the omission of some of its letters (e.g. 'adj.' for 'adjective')"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:136
#, kde-format
msgctxt "XLIFF mark type"
msgid "acronym: an abbreviated form of a term made up of letters from the full form of a multiword term strung together into a sequence pronounced only syllabically (e.g. 'radar' for 'radio detecting and ranging')"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:137
#, kde-format
msgctxt "XLIFF mark type"
msgid "appellation: a proper-name term, such as the name of an agency or other proper entity"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:138
#, kde-format
msgctxt "XLIFF mark type"
msgid "collocation: a recurrent word combination characterized by cohesion in that the components of the collocation must co-occur within an utterance or series of utterances, even though they do not necessarily have to maintain immediate proximity to one another"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:139
#, kde-format
msgctxt "XLIFF mark type"
msgid "common name: a synonym for an international scientific term that is used in general discourse in a given language"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:140
#, kde-format
msgctxt "XLIFF mark type"
msgid "date and/or time"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:141
#, kde-format
msgctxt "XLIFF mark type"
msgid "equation: an expression used to represent a concept based on a statement that two mathematical expressions are, for instance, equal as identified by the equal sign (=), or assigned to one another by a similar sign"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:142
#, kde-format
msgctxt "XLIFF mark type"
msgid "expanded form: The complete representation of a term for which there is an abbreviated form"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:143
#, kde-format
msgctxt "XLIFF mark type"
msgid "formula: figures, symbols or the like used to express a concept briefly, such as a mathematical or chemical formula"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:144
#, kde-format
msgctxt "XLIFF mark type"
msgid "head term: the concept designation that has been chosen to head a terminological record"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:145
#, kde-format
msgctxt "XLIFF mark type"
msgid "initialism: an abbreviated form of a term consisting of some of the initial letters of the words making up a multiword term or the term elements making up a compound term when these letters are pronounced individually (e.g. 'BSE' for 'bovine spongiform encephalopathy')"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:146
#, kde-format
msgctxt "XLIFF mark type"
msgid "international scientific term: a term that is part of an international scientific nomenclature as adopted by an appropriate scientific body"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:147
#, kde-format
msgctxt "XLIFF mark type"
msgid "internationalism: a term that has the same or nearly identical orthographic or phonemic form in many languages"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:148
#, kde-format
msgctxt "XLIFF mark type"
msgid "logical expression: an expression used to represent a concept based on mathematical or logical relations, such as statements of inequality, set relationships, Boolean operations, and the like"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:149
#, kde-format
msgctxt "XLIFF mark type"
msgid "materials management unit: a unit to track object"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:150
#, kde-format
msgctxt "XLIFF mark type"
msgid "name"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:151
#, kde-format
msgctxt "XLIFF mark type"
msgid "near synonym: a term that represents the same or a very similar concept as another term in the same language, but for which interchangeability is limited to some contexts and inapplicable in others"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:152
#, kde-format
msgctxt "XLIFF mark type"
msgid "part number: a unique alphanumeric designation assigned to an object in a manufacturing system"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:153
#, kde-format
msgctxt "XLIFF mark type"
msgid "phrase"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:154
#, kde-format
msgctxt "XLIFF mark type"
msgid "phraseological: a group of two or more words that form a unit, the meaning of which frequently cannot be deduced based on the combined sense of the words making up the phrase"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:155
#, kde-format
msgctxt "XLIFF mark type"
msgid "protected: the marked text should not be translated"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:156
#, kde-format
msgctxt "XLIFF mark type"
msgid "romanized form: a form of a term resulting from an operation whereby non-Latin writing systems are converted to the Latin alphabet"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:157
#, kde-format
msgctxt "XLIFF mark type"
msgid "segment: the marked text represents a segment"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:158
#, kde-format
msgctxt "XLIFF mark type"
msgid "set phrase: a fixed, lexicalized phrase"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:159
#, kde-format
msgctxt "XLIFF mark type"
msgid "short form: a variant of a multiword term that includes fewer words than the full form of the term (e.g. 'Group of Twenty-four' for 'Intergovernmental Group of Twenty-four on International Monetary Affairs')"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:160
#, kde-format
msgctxt "XLIFF mark type"
msgid "stock keeping unit: an inventory item identified by a unique alphanumeric designation assigned to an object in an inventory control system"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:161
#, kde-format
msgctxt "XLIFF mark type"
msgid "standard text: a fixed chunk of recurring text"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:162
#, kde-format
msgctxt "XLIFF mark type"
msgid "symbol: a designation of a concept by letters, numerals, pictograms or any combination thereof"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:163
#, kde-format
msgctxt "XLIFF mark type"
msgid "synonym: a term that represents the same or a very similar concept as the main entry term in a term entry"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:164
#, kde-format
msgctxt "XLIFF mark type"
msgid "synonymous phrase: phraseological unit in a language that expresses the same semantic content as another phrase in that same language"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:165
#, kde-format
msgctxt "XLIFF mark type"
msgid "term"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:166
#, kde-format
msgctxt "XLIFF mark type"
msgid "transcribed form: a form of a term resulting from an operation whereby the characters of one writing system are represented by characters from another writing system, taking into account the pronunciation of the characters converted"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:167
#, kde-format
msgctxt "XLIFF mark type"
msgid "transliterated form: a form of a term resulting from an operation whereby the characters of an alphabetic writing system are represented by characters from another alphabetic writing system"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:168
#, kde-format
msgctxt "XLIFF mark type"
msgid "truncated term: an abbreviated form of a term resulting from the omission of one or more term elements or syllables (e.g. 'flu' for 'influenza')"
msgstr ""
#. +> trunk5 stable5
#: src/catalog/catalogstring.cpp:169
#, kde-format
msgctxt "XLIFF mark type"
msgid "variant: one of the alternate forms of a term"
"This will delete all the translations from the file.\n"
"Do you really want to clear all translated entries?"
msgstr ""
#. +> trunk5 stable5
#: src/editortab.cpp:1446
#, kde-format
msgctxt "@info words count"
msgid ""
"Source text words: %1<br/>"
"Target text words: %2"
msgstr ""
#. +> trunk5 stable5
#: src/editortab.cpp:1447
#, kde-format
msgctxt "@title"
msgid "Word Count"
msgstr ""
#. +> trunk5 stable5
#: src/editortab.cpp:1524
#, kde-format
msgctxt "@info"
msgid "Would you like to search for the source file locally or via lxr.kde.org?"
msgstr ""
#. +> trunk5 stable5
#: src/editortab.cpp:1524 src/editortab.cpp:1565
#, kde-format
msgctxt "@title:window"
msgid "Source file lookup"
msgstr ""
#. +> trunk5 stable5
#: src/editortab.cpp:1525
#, kde-format
msgid "Locally"
msgstr ""
#. +> trunk5 stable5
#: src/editortab.cpp:1537 src/editortab.cpp:1576
#, kde-format
msgid "Select project's base folder for source file lookup"
msgstr ""
#. +> trunk5 stable5
#: src/editortab.cpp:1564
#, kde-format
msgctxt "@info"
msgid ""
"Could not find source file in the folder specified.\n"
"Do you want to change source files folder?"
msgstr ""
#. +> trunk5 stable5
#: src/editortab.cpp:1566
#, kde-format
msgid "lxr.kde.org"
msgstr ""
#. +> trunk5 stable5
#: src/editortab.cpp:1595
#, kde-format
msgctxt "@info"
msgid "Cannot open the target source file: The target source file is not relative to the current translation file, and there are currently no scripts loaded to handle opening source files in custom paths. Refer to the Lokalize handbook for script examples and how to plug them into your project."
msgstr ""
#. +> trunk5 stable5
#: src/editortab.cpp:1610
#, kde-format
msgid "Install translate-toolkit package and retry."
msgstr ""
#. +> trunk5 stable5
#: src/editortab.cpp:1619
#, kde-format
msgid "Select original OpenDocument on which current XLIFF file is based"
"<p>Translations for common terms appear here.</p>"
"<p>Press shortcut displayed near the term to insert its translation.</p>"
"<p>Use context menu to add new entry (tip: select words in original and translation fields before calling <interface>Define new term</interface>).</p>"
msgstr ""
#. +> trunk5 stable5
#: src/glossary/glossarywindow.cpp:253
#, kde-format
msgctxt "@action:button reloads glossary from disk"
msgid "Restore from disk"
msgstr ""
#. +> trunk5 stable5
#: src/glossary/glossarywindow.cpp:254
#, kde-format
msgctxt "@info:tooltip"
msgid "Reload glossary from disk, discarding any changes"
msgstr ""
#. +> trunk5 stable5
#: src/glossary/glossarywindow.cpp:504
#, kde-format
msgctxt "@info"
msgid ""
"The glossary contains unsaved changes.\n"
"Do you want to save your changes or discard them?"
msgid "Check to see if a string ends in a space (which is often important when displaying it in the user interface, or when it gets concatenated with others)."
"<html>When this option is enabled, the mouse wheel is used to go to the previous or next translation unit (without modifier keys). Modifier keys can be used to change this behavior. Use:"
"<ul>"
"<li><b>Shift</b> to scroll within the text of the current unit,</li>"
"<li><b>Ctrl+Shift</b> to go to previous or next non-ready unit,</li>"
"<li><b>Ctrl</b> to go to previous or next non-ready not empty unit,</li>"
"<li><b>Alt</b> to go to previous or next untranslated unit.</li>"
"</ul>"
"When the option is disabled, the mouse wheel scrolls within the text of the current translation unit.</html>"
msgid "The Pology command to run in order to check a single entry. Use the following placeholders in order to set-up the commands: %u is the entry number, %f is the file name. For instance: posieve -u %u check-rules %f"
msgid "The Pology command to run in order to check a whole file. This command should include \"-s lokalize\", placeholder %f is the file name. For instance: posieve -s lokalize check-rules %f"
msgid "Install translate-toolkit package and retry"
msgstr ""
#. +> trunk5 stable5
#: src/project/project.cpp:482
#, kde-format
msgctxt "project folder name. %2 is targetLangCode"
msgid "%1 %2 Translation"
msgstr ""
#. +> trunk5 stable5
#: src/project/projectbase.kcfg:11
#, kde-format
msgid "default"
msgstr ""
#. i18n: ectx: label, entry (LangCode), group (General)
#. +> trunk5 stable5
#: src/project/projectbase.kcfg:18
#, kde-format
msgid "Language"
msgstr ""
#. i18n: ectx: label, entry (UserLangTeam), group (General)
#. +> trunk5 stable5
#: src/project/projectbase.kcfg:32
#, kde-format
msgid "User Language Team in Lokalize settings"
msgstr ""
#. i18n: ectx: label, entry (OverrideLangTeam), group (General)
#. +> trunk5 stable5
#: src/project/projectbase.kcfg:38
#, kde-format
msgid "Override Lokalize Language Team"
msgstr ""
#. i18n: ectx: label, entry (ProjLangTeam), group (General)
#. +> trunk5 stable5
#: src/project/projectbase.kcfg:44
#, kde-format
msgid "Project Language Team"
msgstr ""
#. i18n: ectx: label, entry (PoBaseDir), group (General)
#. +> trunk5 stable5
#: src/project/projectbase.kcfg:59
#, kde-format
msgid "The base directory for PO files (translations)"
msgstr ""
#. i18n: ectx: label, entry (PotBaseDir), group (General)
#. +> trunk5 stable5
#: src/project/projectbase.kcfg:65
#, kde-format
msgid "The base directory for POT files (templates to be translated)"
msgstr ""
#. i18n: ectx: label, entry (GlossaryTbx), group (General)
#. +> trunk5 stable5
#: src/project/projectbase.kcfg:73
#, kde-format
msgid "Project's glossary"
msgstr ""
#. +> trunk5 stable5
#: src/project/projectmodel.cpp:525
#, kde-format
msgctxt "@title:column File name"
msgid "Name"
msgstr ""
#. +> trunk5 stable5
#: src/project/projectmodel.cpp:527
#, kde-format
msgctxt "@title:column Graphical representation of Translated/Fuzzy/Untranslated counts"
msgid "Graph"
msgstr ""
#. +> trunk5 stable5
#: src/project/projectmodel.cpp:529
#, kde-format
msgctxt "@title:column Number of entries"
msgid "Total"
msgstr ""
#. +> trunk5 stable5
#: src/project/projectmodel.cpp:531
#, kde-format
msgctxt "@title:column Number of entries"
msgid "Translated"
msgstr ""
#. +> trunk5 stable5
#: src/project/projectmodel.cpp:533
#, kde-format
msgctxt "@title:column Number of entries"
msgid "Not ready"
msgstr ""
#. +> trunk5 stable5
#: src/project/projectmodel.cpp:535
#, kde-format
msgctxt "@title:column Number of entries"
msgid "Untranslated"
msgstr ""
#. +> trunk5 stable5
#: src/project/projectmodel.cpp:537
#, kde-format
msgctxt "@title:column Number of fuzzy or untranslated entries"
msgid "Incomplete"
msgstr ""
#. +> trunk5 stable5
#: src/project/projectmodel.cpp:539
#, kde-format
msgctxt "@title:column"
msgid "Last Translation"
msgstr ""
#. +> trunk5 stable5
#: src/project/projectmodel.cpp:541
#, kde-format
msgctxt "@title:column"
msgid "Template Revision"
msgstr ""
#. +> trunk5 stable5
#: src/project/projectmodel.cpp:543
#, kde-format
msgctxt "@title:column"
msgid "Last Translator"
msgstr ""
#. +> trunk5 stable5
#: src/project/projecttab.cpp:66
#, kde-format
msgctxt "@title:window"
msgid "Project Overview"
msgstr ""
#. +> trunk5 stable5
#: src/project/projecttab.cpp:70
#, 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>"
"<p align=\"justify\">To facilitate KDE translation, Lokalize can capture text from applications' user interfaces and search for translation files containing the text.</p>"
"\n"
"<p align=\"justify\">When enabled, the capture can be initiated by middle mouse clicking on any non-editable GUI element (widget). After that, switch to the Lokalize window and choose the entry with this text. Even if several files contain the same string, the right one will be chosen in most cases.</p>"
"\n"
"<p align=\"justify\">Remember that you need to have an up-to-date actual translation memory with all translation files indexed for this feature to work.</p>"
msgid "Addflag is used to add flags to a list of [IMAP] flags. It doesn't replace any previously set flags. This means that multiple occurrences of addflag are treated additively."
msgid "The \"convert\" action specifies that all body parts with a media type equal to \"media-type\" be converted to the media type in \"media-type\" using conversion parameters."
msgid "If the optional \":create\" argument is specified, it instructs the Sieve interpreter to create the specified mailbox, if needed, before attempting to deliver the message into the specified mailbox."
msgid "If the optional \":copy\" keyword is specified, the tagged command does not cancel the implicit \"keep\". Instead, it merely files or redirects a copy in addition to whatever else is happening to the message."
msgid "The \"keep\" action is whatever action is taken in lieu of all other actions, if no filtering happens at all; generally, this simply means to file the message into the user's main mailbox."
msgid "The \"redirect\" action is used to send the message to another user at a supplied address, as a mail forwarding feature does. The \"redirect\" action makes no changes to the message body or existing headers, but it may add new headers."
msgid "If the optional \":copy\" keyword is specified, the tagged command does not cancel the implicit \"keep\". Instead, it redirects a copy in addition to whatever else is happening to the message."
msgid "Removeflag is used to remove flags from a list of [IMAP] flags. Removeflag clears flags previously set by \"set\"/\"addflag\". Calling removeflag with a flag that wasn't set before is not an error and is ignored."
msgid "This modifier adds the necessary quoting to ensure that the expanded text will only match a literal occurrence if used as a parameter to :regex. Every character with special meaning (. , *, ? , etc.) is prefixed with \\ in the expansion"
msgid "The \"vacation\" action implements a vacation autoresponder similar to the vacation command available under many versions of Unix. Its purpose is to provide correspondents with notification that the user is away for an extended period of time and that they should not expect quick responses."
msgid "Through the \":days\" parameter, it limits the number of auto-replies to the same sender to one per [n] days, for a specified number of days. But there are cases when one needs more granularity, if one would like to generate \"vacation\" replies more frequently."
msgid "The \"address\" test matches Internet addresses in structured headers that contain addresses. It returns true if any header contains any key in the specified part of the address, as modified by the comparator and the match keyword."
msgid "The body test matches content in the body of an email message, that is, anything following the first empty line after the header. (The empty line itself, if present, is not considered to be part of the body.)"
msgid "The currentdate test is similar to the date test, except that it operates on the current date/time rather than a value extracted from the message header."
msgid "The environment test retrieves the item of environment information specified by the name string and matches it to the values specified in the key-list argument."
msgid "The \"exists\" test is true if the headers listed in the header-names argument exist within the message. All of the headers must exist or the test is false."
msgid "The \"mailboxexists\" test is true if all mailboxes listed in the \"mailbox-names\" argument exist in the mailstore, and each allows the user in whose context the Sieve script runs to \"deliver\" messages into it."
msgid "This test retrieves the value of the mailbox annotation \"annotation-name\" for the mailbox \"mailbox\". The retrieved value is compared to the \"key-list\". The test returns true if the annotation exists and its value matches any of the keys."
msgid "This test retrieves the value of the server annotation \"annotation-name\". The retrieved value is compared to the \"key-list\". The test returns true if the annotation exists and its value matches any of the keys."
msgid "The \"size\" test deals with the size of a message. It takes either a tagged argument of \":over\" or \":under\", followed by a number representing the size of the message."
msgid "Sieve implementations that implement the \"spamtest\" test use an identifier of either \"spamtest\" or \"spamtestplus\" for use with the capability mechanism."
msgid "\"foreverypart\", which is an iterator that walks though every MIME part of a message, including nested parts, depth first, and applies the commands in the specified block to each of them."
msgid "A variable has global scope in all scripts that have declared it with the \"global\" command. If a script uses that variable name without declaring it global, the name specifies a separate, non-global variable within that script."
msgid "The \"include\" command takes an optional \"location\" parameter, an optional \":once\" parameter, an optional \":optional\" parameter, and a single string argument representing the name of the script to include for processing at that point."
#. i18n: ectx: label, entry (AllowOutOfOfficeSettings), group (OutOfOffice)
#. +> trunk5 stable5
#: ksieveui/settings/sieve-vacation.kcfg:12
#, kde-format
msgid "Allow out-of-office settings to be changeable by the user."
msgstr ""
#. i18n: ectx: label, entry (AllowOutOfOfficeUploadButNoSettings), group (OutOfOffice)
#. +> trunk5 stable5
#: ksieveui/settings/sieve-vacation.kcfg:16
#, kde-format
msgid "Allow users to upload out-of-office sieve scripts, but prevent them from changing any settings, such as the domain to react to or the spam reaction switch."
msgstr ""
#. i18n: ectx: label, entry (OutOfOfficeDomain), group (OutOfOffice)
#. +> trunk5 stable5
#: ksieveui/settings/sieve-vacation.kcfg:20
#, kde-format
msgid "Send out-of-office replies to mails coming from this domain only."
msgstr ""
#. i18n: ectx: label, entry (OutOfOfficeReactToSpam), group (OutOfOffice)
#. +> trunk5 stable5
#: ksieveui/settings/sieve-vacation.kcfg:24
#, kde-format
msgid "Allow out-of-office replies to be sent to messages marked as SPAM."
msgstr ""
#. i18n: ectx: label, entry (CheckOutOfOfficeOnStartup), group (OutOfOffice)
#. +> trunk5 stable5
#: ksieveui/settings/sieve-vacation.kcfg:28
#, kde-format
msgid "Check if there is still an active out-of-office reply configured on startup."
msgid "KMail's Out of Office Reply functionality relies on server-side filtering. You have not yet configured an IMAP server for this. You can do this on the \"Filtering\" tab of the IMAP account configuration."
msgid "Impossible to install script on server '%1'"
msgstr ""
#. +> trunk5 stable5
#: ksieveui/vacation/vacationeditwidget.cpp:60
#, kde-format
msgid "Configure vacation notifications to be sent:"
msgstr ""
#. +> trunk5 stable5
#: ksieveui/vacation/vacationeditwidget.cpp:67
#, kde-format
msgid "&Activate vacation notifications"
msgstr ""
#. +> trunk5 stable5
#: ksieveui/vacation/vacationeditwidget.cpp:86
#, kde-format
msgid "&Subject of the vacation mail:"
msgstr ""
#. +> trunk5 stable5
#: ksieveui/vacation/vacationeditwidget.cpp:116
#, kde-format
msgid "Start date:"
msgstr ""
#. +> trunk5 stable5
#: ksieveui/vacation/vacationeditwidget.cpp:144
#, kde-format
msgid "End date:"
msgstr ""
#. +> trunk5 stable5
#: ksieveui/vacation/vacationeditwidget.cpp:167
#: ksieveui/vacation/vacationeditwidget.cpp:317
#, kde-format
msgid " day"
msgid_plural " days"
msgstr[0] ""
msgstr[1] ""
#. +> trunk5 stable5
#: ksieveui/vacation/vacationeditwidget.cpp:169
#, kde-format
msgid "&Resend notification only after:"
msgstr ""
#. +> trunk5 stable5
#: ksieveui/vacation/vacationeditwidget.cpp:181
#, kde-format
msgid "&Send responses for these addresses:"
msgstr ""
#. +> trunk5 stable5
#: ksieveui/vacation/vacationeditwidget.cpp:207
#, kde-format
msgid "&Action for incoming mails:"
msgstr ""
#. +> trunk5 stable5
#: ksieveui/vacation/vacationeditwidget.cpp:215
#, kde-format
msgid "Do not send vacation replies to spam messages"
msgstr ""
#. +> trunk5 stable5
#: ksieveui/vacation/vacationeditwidget.cpp:223
#, kde-format
msgid "Only react to mail coming from domain"
msgstr ""
#. +> trunk5 stable5
#: ksieveui/vacation/vacationmanager.cpp:68
#, kde-format
msgid ""
"There is still an active out-of-office reply configured.\n"
"Do you want to edit it?"
msgstr ""
#. +> trunk5 stable5
#: ksieveui/vacation/vacationmanager.cpp:69
#, kde-format
msgid "Out-of-office reply still active"
msgstr ""
#. +> trunk5 stable5
#: ksieveui/vacation/vacationmanager.cpp:70
#, kde-format
msgid "Edit"
msgstr ""
#. +> trunk5 stable5
#: ksieveui/vacation/vacationmanager.cpp:71
#, kde-format
msgid "Ignore"
msgstr ""
#. +> trunk5 stable5
#: ksieveui/vacation/vacationpagewidget.cpp:59
#, kde-format
msgid "Your server did not list \"vacation\" in its list of supported Sieve extensions;without it, KMail cannot install out-of-office replies for you.Please contact your system administrator."
msgstr ""
#. +> trunk5 stable5
#: ksieveui/vacation/vacationutils.cpp:52
#, kde-format
msgid "Out of office till %1"
msgstr ""
#. +> trunk5 stable5
#: ksieveui/vacation/vacationutils.cpp:63
#, kde-format
msgid "Redirect to"
msgstr ""
#. +> trunk5 stable5
#: ksieveui/vacation/vacationutils.cpp:65
#, kde-format
msgid "Copy to"
msgstr ""
#. +> trunk5 stable5
#: ksieveui/vacation/vacationutils.cpp:78
#, kde-format
msgid ""
"I am out of office till %1.\n"
"\n"
"In urgent cases, please contact Mrs. \"vacation replacement\"\n"
"\n"
"email: \"email address of vacation replacement\"\n"
"phone: +49 711 1111 11\n"
"fax.: +49 711 1111 12\n"
"\n"
"Yours sincerely,\n"
"-- \"enter your name and email address here\"\n"
msgstr ""
#. +> trunk5 stable5
#: ksieveui/vacation/vacationwarningwidget.cpp:32
#, kde-format
msgid "Someone (probably you) changed the vacation script on the server. KMail is no longer able to determine the parameters for the autoreplies. Default values will be used."
# 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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:19+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."
+msgid "With :menuselection:`Settings --> Switch Application Language...` menu item will appear a small window."
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?"
+msgid "I have a problem, how to get support for Krita?"
msgstr ""
#. +> trunk5
#: ../../KritaFAQ.rst:62
+msgid "Ask your question on one of the user support forums. It can be `Krita Artists forum <https://krita-artists.org/>`_ (recommended), `Krita KDE forum <https://forum.kde.org/viewforum.php?f=136>`_ or alternatively `Krita subreddit <https://forum.kde.org/viewforum.php?f=136>`_ ."
+msgstr ""
+
+#. +> trunk5
+#: ../../KritaFAQ.rst:64
+msgid "Remember -- most probably the person you're interacting with is a volunteer, and even if not, it's not someone actually paid for doing user support. Treat them nicely and respect their time! They will for sure reciprocate that."
+msgstr ""
+
+#. +> trunk5
+#: ../../KritaFAQ.rst:66
+msgid "Create a new thread or post for your issue and state the issue in the title. Even if you don't know how to describe it exactly, for example you title the post \"Krita's text tool is acting weird\", it is much better than simple \"Help!\"."
+msgstr ""
+
+#. +> trunk5
+#: ../../KritaFAQ.rst:68
+msgid "Describe your issue. You can add screenshots and videos, but even if you do that, write a few words what the video shows and what the issue is."
+msgstr ""
+
+#. +> trunk5
+#: ../../KritaFAQ.rst:70
+msgid "State all relevant details: most importantly your operating system (Windows, MacOS, Linux...), which version of Krita you use (go to :menuselection:`Help -> About Krita` to find out) and what kind of tablet you have (if your issue is related to a tablet driver)."
+msgstr ""
+
+#. +> trunk5
+#: ../../KritaFAQ.rst:72
+msgid "Answer all questions your supporter asks, even if you don't think they're relevant. They probably have a reason to ask about that."
+msgstr ""
+
+#. +> trunk5
+#: ../../KritaFAQ.rst:74
+msgid "If you don't know the answer or you don't know how to get the information your supporter asks for, don't hesitate to ask for clarification."
+msgstr ""
+
+#. +> trunk5
+#: ../../KritaFAQ.rst:76
+msgid "If you mentioned an issue, please help with testing if you're asked to do that -- that will speed up the process of finding the cause and preparing a fix."
+msgstr ""
+
+#. +> trunk5
+#: ../../KritaFAQ.rst:81
+msgid "Does Krita have layer clip or clipping mask?"
+msgstr ""
+
+#. +> trunk5
+#: ../../KritaFAQ.rst:83
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
+#: ../../KritaFAQ.rst:88
msgid "Where are the configuration files stored?"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:69
+#: ../../KritaFAQ.rst:90
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:84
+#: ../../KritaFAQ.rst:105
msgid "Resetting Krita configuration"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:86
-msgid "You can reset the Krita configuration in following way:"
+#: ../../KritaFAQ.rst:107
+msgid "You can reset the Krita configuration in one of the following ways:"
+msgstr ""
+
+#. +> trunk5
+#: ../../KritaFAQ.rst:109
+msgid "Press and hold :kbd:`Shift + Alt + Ctrl` while starting Krita. This should show a pop-up asking if you want to reset the configuration. Press :guilabel:`yes` to reset it."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:88
+#: ../../KritaFAQ.rst:111
msgid "For Krita 3.0 and later: Delete/rename the kritarc file, found here:"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:93
+#: ../../KritaFAQ.rst:116
msgid ":file:`%LOCALAPPDATA%\\\\kritarc`"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:97
+#: ../../KritaFAQ.rst:120
msgid "There can be two other files you might want to remove: kritaopenglrc and kritadisplayrc."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:100
+#: ../../KritaFAQ.rst:123
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:103
+#: ../../KritaFAQ.rst:126
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:109
+#: ../../KritaFAQ.rst:132
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."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:112
+#: ../../KritaFAQ.rst:137
+msgid "Why my configuration resets on its own?"
+msgstr ""
+
+#. +> trunk5
+#: ../../KritaFAQ.rst:139
+msgid "There are two possible reasons:"
+msgstr ""
+
+#. +> trunk5
+#: ../../KritaFAQ.rst:141
+msgid "You don't save your settings."
+msgstr ""
+
+#. +> trunk5
+#: ../../KritaFAQ.rst:143
+msgid "This is most probable if you are on Windows and you have either a display with a small resolution (below fullHD) or if you have fullHD resolution with UI scaling in Windows settings (which is 150% by default). In those cases it might happen that you don't see the :guilabel:`OK` button in the :guilabel:`Configure Krita` dialog. You can use :kbd:`Alt + O` instead. (You can go to :menuselection:`Configure Krita... --> General --> Window` and make sure that :guilabel:`Enable HiDPI` checkbox is unchecked to disable scaling for Krita and get a smaller UI)."
+msgstr ""
+
+#. +> trunk5
+#: ../../KritaFAQ.rst:145
+msgid "You close your computer using the power button."
+msgstr ""
+
+#. +> trunk5
+#: ../../KritaFAQ.rst:147
+msgid "If you are on Windows and you use power button instead of a standard procedure to close or restart your computer, it might happen that Krita's configuration file gets corrupted. To solve this, just use the correct way of closing your system: either :menuselection:`Start -> Restart` or :menuselection:`Start -> Shutdown`."
msgid "Krita tells me it can't find some files and then closes, what should I do?"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:127
+#: ../../KritaFAQ.rst:165
msgid "Causes for this could be the following:"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:129
+#: ../../KritaFAQ.rst:167
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:130
+#: ../../KritaFAQ.rst:168
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:131
-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."
+#: ../../KritaFAQ.rst:169
+msgid "Some unzippers don't unpack our ZIP files correctly. The native ones on Windows, OSX and most Linux distributions should be just fine, and we recommend using them."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:132
+#: ../../KritaFAQ.rst:170
msgid "You manually, using a file manager deleted or moved resources around, and thus Krita cannot find them anymore."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:135
+#: ../../KritaFAQ.rst:173
msgid "What Graphics Cards does Krita support?"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:137
+#: ../../KritaFAQ.rst:175
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:141
+#: ../../KritaFAQ.rst:179
msgid "Intel"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:142
+#: ../../KritaFAQ.rst:180
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:143
+#: ../../KritaFAQ.rst:181
msgid "AMD/ATI"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:144
+#: ../../KritaFAQ.rst:182
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:146
+#: ../../KritaFAQ.rst:184
msgid "Nvidia"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:146
+#: ../../KritaFAQ.rst:184
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:148
+#: ../../KritaFAQ.rst:186
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:151
+#: ../../KritaFAQ.rst:189
msgid "I can't edit text from PSD files created by Photoshop"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:153
-msgid "There is no text support for psd file yet. The text will appear rasterized and converted into a paint layer."
+#: ../../KritaFAQ.rst:191
+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:156
+#: ../../KritaFAQ.rst:194
msgid "How much memory does my image take?"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:158
+#: ../../KritaFAQ.rst:196
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:161
+#: ../../KritaFAQ.rst:199
msgid "Why do I get a checkerboard pattern when I use the eraser?"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:163
+#: ../../KritaFAQ.rst:201
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:165
-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."
+#: ../../KritaFAQ.rst:203
+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:168
+#: ../../KritaFAQ.rst:206 ../../KritaFAQ.rst:249
msgid "Can krita work with 8 bit (indexed) images?"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:170
+#: ../../KritaFAQ.rst:208 ../../KritaFAQ.rst:251
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:174
+#: ../../KritaFAQ.rst:212 ../../KritaFAQ.rst:255
msgid "Where can I find older versions of Krita?"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:176
+#: ../../KritaFAQ.rst:214 ../../KritaFAQ.rst:257
msgid "All the older versions of Krita that are still available can be found here:"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:178
-msgid "`Very old builds <https://download.kde.org/Attic/krita/>`_"
+#: ../../KritaFAQ.rst:216
+msgid "`Very old builds <https://download.kde.org/Attic/krita/>`_."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:181
+#: ../../KritaFAQ.rst:219 ../../KritaFAQ.rst:262
msgid "On Windows, the Krita User Interface is too big on my screen"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:183
+#: ../../KritaFAQ.rst:221 ../../KritaFAQ.rst:264
msgid "If you're using Windows, you can set the display scaling to 150% or 200%. Krita comes with HiDPI enabled by default, so if you do that, the Krita UI might be too big for your screen. You can turn it off using the following steps:"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:185
-msgid "On the menu, select :menuselection:`Settings --> Configure Krita`"
+#: ../../KritaFAQ.rst:223
+msgid "On the menu, select :menuselection:`Settings --> Configure Krita...`"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:186
+#: ../../KritaFAQ.rst:224 ../../KritaFAQ.rst:267
msgid "On :guilabel:`General` page, switch to :guilabel:`Window` tab."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:187
+#: ../../KritaFAQ.rst:225 ../../KritaFAQ.rst:268
msgid "Uncheck :guilabel:`Enable Hi-DPI support` (or check if you wish to enable it)"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:188
+#: ../../KritaFAQ.rst:226 ../../KritaFAQ.rst:269
msgid "Press :guilabel:`OK`, if the settings screen is too big, :kbd:`Alt + O` will trigger the OK button too."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:189
+#: ../../KritaFAQ.rst:227 ../../KritaFAQ.rst:270
msgid "Restart Krita"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:191
+#: ../../KritaFAQ.rst:229 ../../KritaFAQ.rst:272
msgid "You can also change the toolbox icon size by right-clicking on the toolbox and selecting a size."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:194
+#: ../../KritaFAQ.rst:232 ../../KritaFAQ.rst:275
msgid "Windows: In fullscreen mode, why is there a thin gap at the bottom of the window?"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:196
+#: ../../KritaFAQ.rst:234 ../../KritaFAQ.rst:277
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:199
+#: ../../KritaFAQ.rst:237 ../../KritaFAQ.rst:280
msgid "Windows: OBS can't record the Krita OpenGL canvas"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:201
+#: ../../KritaFAQ.rst:239 ../../KritaFAQ.rst:282
msgid "The possible workarounds for this is to do either of the following:"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:203
-msgid "Turn off OpenGL in :menuselection:`Settings --> Configure Krita --> Display`."
+#: ../../KritaFAQ.rst:241
+msgid "Turn off OpenGL in :menuselection:`Settings --> Configure Krita... --> Display`."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:204
+#: ../../KritaFAQ.rst:242 ../../KritaFAQ.rst:285
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:208
+#: ../../KritaFAQ.rst:246 ../../KritaFAQ.rst:289
msgid "You might also be able to work around the problem by using the ANGLE renderer instead of native OpenGL."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:211
+#: ../../KritaFAQ.rst:259
+msgid "`Very old builds <https://download.kde.org/Attic/krita/>`_"
+msgstr ""
+
+#. +> trunk5
+#: ../../KritaFAQ.rst:266
+msgid "On the menu, select :menuselection:`Settings --> Configure Krita`"
+msgstr ""
+
+#. +> trunk5
+#: ../../KritaFAQ.rst:284
+msgid "Turn off OpenGL in :menuselection:`Settings --> Configure Krita --> Display`."
+msgstr ""
+
+#. +> trunk5
+#: ../../KritaFAQ.rst:292
msgid "Windows: Can I use Krita with Sandboxie?"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:213
+#: ../../KritaFAQ.rst:294
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:216
+#: ../../KritaFAQ.rst:297
msgid "Windows: Krita cannot save"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:218
+#: ../../KritaFAQ.rst:299
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:222
+#: ../../KritaFAQ.rst:303
msgid "Select :guilabel:`Open Windows Defender Security Center`."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:223
+#: ../../KritaFAQ.rst:304
msgid "Select :guilabel:`Virus & threat protection`, and then choose :guilabel:`Virus & threat protection settings`."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:224
+#: ../../KritaFAQ.rst:305
msgid "Under :guilabel:`Controlled folder access`, turn it on or off."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:226
+#: ../../KritaFAQ.rst:307
msgid "You can also whitelist Krita, following `these instructions <https://docs.microsoft.com/en-us/windows/security/threat-protection/microsoft-defender-atp/customize-controlled-folders#allow-specific-apps-to-make-changes-to-controlled-folders>`_."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:229
+#: ../../KritaFAQ.rst:310
msgid "Windows: Krita cannot open my file anymore"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:231
+#: ../../KritaFAQ.rst:312
msgid "Your file got corrupted. There are several things that might cause this:"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:233
+#: ../../KritaFAQ.rst:314
msgid "Windows was shutdown improperly, like by holding the power button. This prevents your harddrive from finishing up the things it is doing and file away your files incorrectly. Please always try to shutdown your computer via the proper shutdown procedure, and if you are in a situation where this is not possible (like frequent blackouts), make daily backups! This may lead to the file being filled with zeroes, so it cannot be recovered from."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:237
+#: ../../KritaFAQ.rst:318
msgid "Krita version 4.2.8 introduced special safety measure for Windows that should help avoiding this situation. But in any case, unless something makes it impossible, always make sure to shutdown your system using the standard approach. On Windows that means going to Start menu and selecting \"Shutdown\"."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:239
-msgid "Badly programmed security software may attempt to rewrite kra files, or prevent Krita from writing to the folder you wish to save to. These cases can be checked by trying to save in that location, and then, without shutting down Krita, checking in the folder to see if the file saved. Files lost due this cannot be recovered."
+#: ../../KritaFAQ.rst:320
+msgid "Badly programmed security software may attempt to rewrite KRA files, or prevent Krita from writing to the folder you wish to save to. These cases can be checked by trying to save in that location, and then, without shutting down Krita, checking in the folder to see if the file saved. Files lost due this cannot be recovered."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:241
+#: ../../KritaFAQ.rst:321
msgid "Cloud services like dropbox and onedrive have been known to prevent Krita from saving. We've implemented fixes for this, but much like the above point it is worth checking that this isn't the cause of the issue. Files lost due this cannot be recovered."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:242
-msgid "Occasionally the zips that kra files comprise of will have the last few bytes missing. We're doing everything in our power to prevent this kind of corruption, but it might be a file system issue. This particular bug can be fixed by renaming the extension (in windows you will need to enable the file extensions, which this FAQ will not cover) to zip, and then using a zip repairing utility to fix the zip file. Then rename it back to kra."
+#: ../../KritaFAQ.rst:322
+msgid "Occasionally the ZIPs that KRA files comprise of will have the last few bytes missing. We're doing everything in our power to prevent this kind of corruption, but it might be a file system issue. This particular bug can be fixed by renaming the extension (in windows you will need to enable the file extensions, which this FAQ will not cover) to ZIP, and then using a ZIP repairing utility to fix the ZIP file. Then rename it back to KRA."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:243
+#: ../../KritaFAQ.rst:323
msgid "If Krita doesn't give an error message, but rather crashes, your file is too big, and Krita is not so much crashing as that the operating system is shutting it down. Try shutting down some other programs like webbrowsers or streaming services to free up working memory. You should be able to open the file in question. At this point the recommended course of action is to try and reduce the file size in some manner, such as merging layers, splitting up an animation or scaling the image down."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:247
+#: ../../KritaFAQ.rst:327
msgid "How to recover my files?"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:248
-msgid "Check whether you have any backup file or autosave left: :ref:`autosave` ."
+#: ../../KritaFAQ.rst:328
+msgid "Check whether you have any backup file or autosave left: :ref:`autosave`."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:250 ../../KritaFAQ.rst:255
-msgid "Rename the extension of the file from .kra to .zip."
+#: ../../KritaFAQ.rst:330 ../../KritaFAQ.rst:335
+msgid "Rename the extension of the file from ``.kra`` to ``.zip``."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:251
-msgid "Check whether you can open the file as zip archive."
+#: ../../KritaFAQ.rst:331
+msgid "Check whether you can open the file as ZIP archive."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:251
+#: ../../KritaFAQ.rst:331
msgid "Try to open (your system should automatically select an archive opener tool)."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:252
+#: ../../KritaFAQ.rst:332
msgid "There is file called mergedimage.png inside that represents all layers merged that you can use for reference in case you can't restore anything else."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:254
+#: ../../KritaFAQ.rst:334
msgid "Copy the file so you have a backup just in case."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:256
-msgid "Use zip repairer tool on the .zip file."
+#: ../../KritaFAQ.rst:336
+msgid "Use ZIP repairer tool on the ``.zip`` file."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:258
+#: ../../KritaFAQ.rst:338
msgid ""
"# On Linux:\n"
"mv file.kra file_copy.zip\n"
"zip -F file_copy.zip --out file_new1.zip\n"
"unzip file_new1.zip\n"
"# if it still doesn't work:\n"
"zip -FF file_copy.zip --out file_new2.zip\n"
"unzip file_new2.zip\n"
-"# if it still doesn't work, try to run it again on file_new2.zip file, or try on file_new1.zip file\n"
+"# if it still doesn't work, try to run it again on *file_new2.zip* file, or try on *file_new1.zip* file\n"
"\n"
"# On Windows:\n"
"Copy the file, rename the extension.\n"
-"Use any graphical zip repairer on the new file. (Follow the instructions for that specific program)."
+"Use any graphical ZIP repairer on the new file. (Follow the instructions for that specific program)."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:274
+#: ../../KritaFAQ.rst:354
msgid "Try to open in Krita."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:275
-msgid "Check whether zip repairer tool helps."
+#: ../../KritaFAQ.rst:355
+msgid "Check whether ZIP repairer tool helps."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:275
+#: ../../KritaFAQ.rst:355
msgid "If it cannot be opened in Krita, try the trick from 2.: open the archive and find mergedimage.png file."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:277
-msgid "Open your file in Notepad or any other text editor. If the the content of the file is only a repeated `NUL` symbol, it means the file is most probably unrecoverable using the standard method. If it's of a very high importance for you, you can try to recover the previous save using methods that checks the hard drive directly."
+#: ../../KritaFAQ.rst:357
+msgid "Open your file in Notepad or any other text editor. If the the content of the file is only a repeated *NUL* symbol, it means the file is most probably unrecoverable using the standard method. If it's of a very high importance for you, you can try to recover the previous save using methods that checks the hard drive directly."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:281
+#: ../../KritaFAQ.rst:361
msgid "Krita crashes on Windows 7 on start-up"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:283
+#: ../../KritaFAQ.rst:363
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:287
+#: ../../KritaFAQ.rst:367
msgid "Windows: How can I produce a backtrace?"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:291
+#: ../../KritaFAQ.rst:371
msgid ":ref:`Dr. Mingw debugger <dr_minw>`"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:293
+#: ../../KritaFAQ.rst:373
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:295
+#: ../../KritaFAQ.rst:375
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:298
+#: ../../KritaFAQ.rst:378
msgid "Windows: Krita's window is semi-transparent"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:300
+#: ../../KritaFAQ.rst:380
msgid "Chances are you are using an NVidia GPU. Due to a bug in Nvidia's driver that we haven't been able to workaround yet, sometimes Krita's window will be transparent or semi-transparent. The solution is to enable the Angle renderer in Krita's Settings dialog. Open the :menuselection:`Settings` menu (Press Alt-N if the menubar is not visible and your system is in English), then open the :guilabel:`Configure Krita` dialog. In the dialog window select the :guilabel:`Display` page and select the Angle renderer in the :guilabel:`Preferred Renderer` combobox. Restart Krita."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:304
+#: ../../KritaFAQ.rst:384
msgid "Tablets"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:307
+#: ../../KritaFAQ.rst:387
msgid "What tablets does Krita support?"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:309
+#: ../../KritaFAQ.rst:389
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:311
+#: ../../KritaFAQ.rst:391
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:313
+#: ../../KritaFAQ.rst:393
msgid "You can find a community curated list of tablets supported by krita :ref:`here <list_supported_tablets>`."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:315
+#: ../../KritaFAQ.rst:395
msgid "If you're looking for information about tablets like the iPad or Android tablets, look :ref:`here <krita_android>`."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:319
+#: ../../KritaFAQ.rst:399
msgid "What if your tablet is not recognized by Krita?"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:321
+#: ../../KritaFAQ.rst:401
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:323
+#: ../../KritaFAQ.rst:403
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:327
+#: ../../KritaFAQ.rst:407
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:329
-msgid "When using a terminal, make sure to enable 'unlimited scrollback'"
+#: ../../KritaFAQ.rst:409
+msgid "When using a terminal, make sure to enable 'unlimited scrollback'."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:331
+#: ../../KritaFAQ.rst:411
msgid "Press the :kbd:`Ctrl + Shift + T` shortcut, you will see a message box telling the logging has started."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:332
+#: ../../KritaFAQ.rst:412
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:333
+#: ../../KritaFAQ.rst:413
msgid "Save the output from the log viewer into a txt file, and attach it to the bugreport."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:335
+#: ../../KritaFAQ.rst:415
msgid "On Linux, it is also useful to have the following information:"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:337
+#: ../../KritaFAQ.rst:417
msgid "``lsmod``"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:338
+#: ../../KritaFAQ.rst:418
msgid "``xinput``"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:339
+#: ../../KritaFAQ.rst:419
msgid "``xinput list-props`` (id can be fetched from the item 2)"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:341
+#: ../../KritaFAQ.rst:421
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:345
+#: ../../KritaFAQ.rst:425
msgid "How to fix a tablet offset on multiple screen setup on Windows"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:347
+#: ../../KritaFAQ.rst:427
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:349
+#: ../../KritaFAQ.rst:429
msgid "You can configure this by going to the :ref:`tablet_settings`."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:352
+#: ../../KritaFAQ.rst:432
msgid "Microsoft Surface Pro and N-Trig"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:354
-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`."
+#: ../../KritaFAQ.rst:434
+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:357
+#: ../../KritaFAQ.rst:437
msgid "Tablet Pro and the Surface Pro"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:359
+#: ../../KritaFAQ.rst:439
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:361
+#: ../../KritaFAQ.rst:441
msgid "https://tabletpro.com/"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:363
+#: ../../KritaFAQ.rst:443
msgid "See https://www.youtube.com/watch?v=WKXZgYqC3tI for instructions."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:366
+#: ../../KritaFAQ.rst:446
msgid "Weird stuff happens on Windows, like ripples, rings, squiggles or poltergeists"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:368
+#: ../../KritaFAQ.rst:448
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:378
+#: ../../KritaFAQ.rst:458
msgid "Toolbox"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:381
+#: ../../KritaFAQ.rst:461
msgid "Toolbox missing"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:383
+#: ../../KritaFAQ.rst:463
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:385
+#: ../../KritaFAQ.rst:465
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:387
+#: ../../KritaFAQ.rst:467
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:390
+#: ../../KritaFAQ.rst:470
msgid "Tool icons size is too big"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:392
+#: ../../KritaFAQ.rst:472
msgid "Right click the toolbox to set the size."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:395
+#: ../../KritaFAQ.rst:475
msgid "Krita can't get maximized"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:397
+#: ../../KritaFAQ.rst:477
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:400
+#: ../../KritaFAQ.rst:480
msgid "Resources"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:403
+#: ../../KritaFAQ.rst:483
msgid "Is there a way to restore a default brush that I have mistakenly overwritten with new settings to default?"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:405
+#: ../../KritaFAQ.rst:485
msgid "Yes. First go to the resource folder, which is in"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:410
+#: ../../KritaFAQ.rst:490
msgid ":file:`user\\\\Appdata\\\\Roaming\\\\krita\\\\` or :file:`%APPDATA%\\\\Roaming\\\\krita\\\\`"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:412
+#: ../../KritaFAQ.rst:492
msgid "OSX"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:414
-msgid "You can easily do this by going into :menuselection:`Settings --> Manage Resources --> Open Resource Folder`."
+#: ../../KritaFAQ.rst:494
+msgid "You can easily do this by going into :menuselection:`Settings --> Manage Resources... --> Open Resource Folder`."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:416
+#: ../../KritaFAQ.rst:496
msgid "Then go into the *paintoppresets* folder and remove the latest created file that you made of your preset."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:419
+#: ../../KritaFAQ.rst:499
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:425
+#: ../../KritaFAQ.rst:505
msgid "How do I set favorite presets?"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:427
+#: ../../KritaFAQ.rst:507
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:430
+#: ../../KritaFAQ.rst:510
msgid "Can Krita load Photoshop Brushes?"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:432
+#: ../../KritaFAQ.rst:512
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:435
+#: ../../KritaFAQ.rst:515
msgid "Krita is slow"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:437
+#: ../../KritaFAQ.rst:517
msgid "There is a myriad of reasons why this might be. Below is a short checklist."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:439
+#: ../../KritaFAQ.rst:519
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:440
+#: ../../KritaFAQ.rst:520
msgid "You are running Windows, and have 3rdparty security software like Sandboxie or Total Defender installed"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:441
+#: ../../KritaFAQ.rst:521
msgid "You are working on images that are too big for your hardware (dimensions, channel depth or number of layers)"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:442
+#: ../../KritaFAQ.rst:522
msgid "You do not have canvas acceleration enabled"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:443
+#: ../../KritaFAQ.rst:523
msgid "You have (NVidia) Vertical Sync enabled"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:445
-msgid "Please also check `this page <https://phabricator.kde.org/T7199>`__"
+#: ../../KritaFAQ.rst:524
+msgid "On macOS, with some macs, you might need to disable canvas acceleration in Krita's settings."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:448
+#: ../../KritaFAQ.rst:526
+msgid "Please also check `this page <https://phabricator.kde.org/T7199>`_."
+msgstr ""
+
+#. +> trunk5
+#: ../../KritaFAQ.rst:529
msgid "Slow start-up"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:450
-msgid "You probably have too many resources installed. Deactivate some bundles under :menuselection:`Settings --> Manage Resources`."
+#: ../../KritaFAQ.rst:531
+msgid "You probably have too many resources installed. Deactivate some bundles under the :menuselection:`Settings --> Manage Resources...` menu item."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:452
-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."
+#: ../../KritaFAQ.rst:533
+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:455
+#: ../../KritaFAQ.rst:536
msgid "Slow Brushes"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:457
+#: ../../KritaFAQ.rst:538
msgid "Check if you accidentally turned on the stabilizer in the tool options docker."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:458
-msgid "Try another scaling mode like trilinear. :menuselection:`Settings --> Configure Krita --> Display`."
+#: ../../KritaFAQ.rst:539
+msgid "Try another scaling mode like trilinear. :menuselection:`Settings --> Configure Krita... --> Display`."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:459
+#: ../../KritaFAQ.rst:540
msgid "Try a lower channel depth than 16-bit."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:460
+#: ../../KritaFAQ.rst:541
msgid "For NVidia, try a 16-bit floating point color space."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:461
-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."
+#: ../../KritaFAQ.rst:542
+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:462
+#: ../../KritaFAQ.rst:543
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:463
-msgid "Check that nothing else is hogging your CPU"
+#: ../../KritaFAQ.rst:544
+msgid "Check that nothing else is hogging your CPU."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:464
+#: ../../KritaFAQ.rst:545
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:465
+#: ../../KritaFAQ.rst:546
msgid "Set brush precision to 3 or auto."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:466
+#: ../../KritaFAQ.rst:547
msgid "Use a larger value for brush spacing."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:467
+#: ../../KritaFAQ.rst:548
msgid "If all of this fails, record a video and post a link and description on the Krita forum."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:468
+#: ../../KritaFAQ.rst:549
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:471
+#: ../../KritaFAQ.rst:552
msgid "Slowdown after a been working for a while"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:473
-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`."
+#: ../../KritaFAQ.rst:554
+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:476
+#: ../../KritaFAQ.rst:557
msgid "Animation"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:479
+#: ../../KritaFAQ.rst:560
msgid "Why is my animation black in my video player"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:481
-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>`__"
+#: ../../KritaFAQ.rst:562
+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:485
+#: ../../KritaFAQ.rst:566
msgid "Tools"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:488
+#: ../../KritaFAQ.rst:569
msgid "Why does the Transform Tool give a good result and then get blurry upon finalizing?"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:490
+#: ../../KritaFAQ.rst:571
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:494
+#: ../../KritaFAQ.rst:575
msgid "License, rights and the Krita Foundation"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:497
+#: ../../KritaFAQ.rst:578
msgid "Who owns Krita?"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:499
+#: ../../KritaFAQ.rst:580
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:502
+#: ../../KritaFAQ.rst:583
msgid "Who and what is Kiki?"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:504
+#: ../../KritaFAQ.rst:585
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:507
+#: ../../KritaFAQ.rst:588
msgid "Why is Krita Free?"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:509
+#: ../../KritaFAQ.rst:590
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:512
+#: ../../KritaFAQ.rst:593
msgid "Why isn't Krita on Steam and in the Windows Store Free?"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:514
+#: ../../KritaFAQ.rst:595
msgid "Krita on Steam and in the Windows Store is still Free and Open Source software; the binaries are exactly the ones you can also download from krita.org. We've put a price tag on downloading Krita from either store to support Krita's development. Nobody is getting rich out of it, but the income from Steam and the Windows Store currently pays for the full-time involvement with Krita of four developers. See `Krita Available from the Windows Store <https://krita.org/en/item/krita-available-from-the-windows-store/>`_ for more information."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:518
+#: ../../KritaFAQ.rst:599
msgid "Can I use Krita commercially?"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:520
+#: ../../KritaFAQ.rst:601
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:522
+#: ../../KritaFAQ.rst:603
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:528
+#: ../../KritaFAQ.rst:609
msgid "Can I get Krita for iPad? for Android?"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:530
+#: ../../KritaFAQ.rst:611
msgid "Not for iOS or iPadOS at this point in time. Android is being worked on, but it will not have a phone or tablet, but the same desktop ui as always."
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:533
+#: ../../KritaFAQ.rst:614
msgid "Who translates Krita"
msgstr ""
#. +> trunk5
-#: ../../KritaFAQ.rst:535
+#: ../../KritaFAQ.rst:616
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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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"
+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
+#: ../../contributors_manual/community.rst:88
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."
+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 "Wolthera (irc: Wolthera_laptop): developer, writes the manual and tutorials, triages bugs, helps people out. Works full-time on Krita."
+msgid "Alvin Wong (irc: windragon): windows guru."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:41
-msgid "Krita’s team spans the globe, but most development happens in Europe and Russia."
+msgid "Ben Cooksley (irc: bcooksley): KDE system administrator."
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/>`_."
+msgid "Krita’s team spans the globe, but most development happens in Europe and Russia."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/community.rst:45
+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:47
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
+#: ../../contributors_manual/community.rst:50
msgid "Internet Relay Chat"
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/community.rst:50
+#: ../../contributors_manual/community.rst:52
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
+#: ../../contributors_manual/community.rst:54
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
+#: ../../contributors_manual/community.rst:55
msgid "Don’t ask to ask: if you’ve got a question, just ask it."
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/community.rst:54
+#: ../../contributors_manual/community.rst:56
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
+#: ../../contributors_manual/community.rst:57
msgid "Talk to an individual by typing their nick and a colon."
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/community.rst:56
+#: ../../contributors_manual/community.rst:58
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
+#: ../../contributors_manual/community.rst:59
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
+#: ../../contributors_manual/community.rst:60
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
+#: ../../contributors_manual/community.rst:61
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
+#: ../../contributors_manual/community.rst:65
msgid "Mailing List"
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/community.rst:65
+#: ../../contributors_manual/community.rst:67
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
+#: ../../contributors_manual/community.rst:69
msgid "`Mailing List Archives <https://mail.kde.org/mailman/listinfo/kimageshop>`_"
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/community.rst:69
+#: ../../contributors_manual/community.rst:71
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
+#: ../../contributors_manual/community.rst:75
msgid "Gitlab (KDE Invent)"
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/community.rst:75
+#: ../../contributors_manual/community.rst:77
msgid "Gitlab serves the following purposes for the Krita team:"
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/community.rst:77
+#: ../../contributors_manual/community.rst:79
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
+#: ../../contributors_manual/community.rst:80
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
+#: ../../contributors_manual/community.rst:81
msgid "Host the Krita Manual content repository: https://invent.kde.org/websites/docs-krita-org"
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/community.rst:81
+#: ../../contributors_manual/community.rst:83
msgid "**Do not** make new issues on Gitlab or use it to make bug reports."
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/community.rst:83
+#: ../../contributors_manual/community.rst:85
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
+#: ../../contributors_manual/community.rst:90
msgid "Phabricator serves the following purposes for the Krita team:"
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/community.rst:90
+#: ../../contributors_manual/community.rst:92
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
+#: ../../contributors_manual/community.rst:94
msgid "**Do not** report bugs as tasks on Phabricator. Phabricator is where we organize our work."
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/community.rst:95
+#: ../../contributors_manual/community.rst:97
msgid "Bugzilla: the Bug Tracker"
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/community.rst:97
+#: ../../contributors_manual/community.rst:99
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
+#: ../../contributors_manual/community.rst:102
msgid "Sprints"
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/community.rst:102
+#: ../../contributors_manual/community.rst:104
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 "It's recommended to look over the `official specification <http://docutils.sourceforge.net/rst.html>`_ for reStructuredText, and given it lives on sourceforge, to save a copy to your harddrive (sourceforge has, at this time of writing, some issues with server uptime):"
msgid "`Sphinx' page on restructured text <https://www.sphinx-doc.org/en/master/usage/restructuredtext/index.html>`_ -- This is useful for the specific sphinx directives and roles it uses to generate for example table of contents."
msgid "There are differences between the official reStructuredText and the sphinx docs multiple ways to do things. This document specifies the suggested conventions to go with."
msgid "This is just to keep track of who edited the page and to give credit. It should be in a comment so that it will not end up being easily readable by machines. The license of the whole manual is GDL 1.3 and should also be mentioned here::"
-msgid "These are comma-separated terms under which the page will be indexed in :ref:`genindex`. The generated index is quite useful for both pdf as well as people who are not sure what the exact name is of the term they are looking for. They are defined as follows::"
+msgid "These are comma-separated terms under which the page will be indexed in :ref:`genindex`. The generated index is quite useful for both PDF as well as people who are not sure what the exact name is of the term they are looking for. They are defined as follows::"
msgid "These conventions were more or less decided by `Pandoc <https://pandoc.org/>`_'s mediawiki to reStructuredText conversion. If you need more than 4 headings, ask yourself first if the page hasn't gotten too complicated and needs splitting up."
msgid "`Pandoc <https://pandoc.org/>`_ likes to turn these into ```link name`__`` and then add ``.. __ :url`` at the end of the document. This is a so-called 'anonymous hyperlink', meaning that depending on the order of the links appearing in the text the order of the links at the end of the text are associated with one another. If this sounds confusing and difficult, it is because it is. That is also the exact reason why we'd like to avoid links like these."
msgid "We don't actually use footnotes in the manual due to the fact that it is a little bit too academical for our readers. However, we do collect documents and links that give a little bit more information on a topic at the end of a page. Sphinx has the ``.. seealso::`` directive for linking to external links, while reStructuredText suggests to use ``.. rubic:: Footnotes`` for specifically collecting footnotes as that plays nice with LaTeX."
msgid "However, use these super-sparingly! It is preferred to use the existing semantic markup in sphinx in any case, because that makes it easier for translators to make decisions about the nature of the text::"
msgid "which means that if you use ``|shorthand|``, in the text, it'll be replaced with 'something or the other'. This is useful for images and text that needs to be formatted in a complicated way, like in the case of \"LaTeX\"."
msgid "The krita documentation has ``|mouseleft|``, ``|mousemiddle|``, ``|mousescroll|`` and ``|mouseright|``, which'll turn into |mouseleft|, |mousemiddle|, |mousescroll| and |mouseright| respectively. These are defined in the sphinx conf.py, and are appended to each rst file."
msgid "Then, when typing a link, you can just use ```bugzilla`_`` to link to bugzilla with \"bugzilla\" used as the text of the link. ```Krita Manual`_`` will in turn link to docs.krita.org with the text \"Krita Manual\"."
msgid "A favourite! Definition lists are especially useful when dealing with enumerating all the options in a docker and trying to add a simple explanation behind them."
msgid "Full grid tables are best for when you need all features like complex column and row spans, but they're tricky to make. For that reason, small tables are best off being done with the simple syntax, while really long tables are best done with a list directive because that is just much easier to write and maintain."
msgid "Hints are useful to give a little bit more information on a topic than is useful in the main text. Like, \"These packages are named differently in openSuse versus Debian\"."
msgid "Extra information on how to do something, like, \"You can make a template of your favourite document setup\", or \"Use m to mirror the canvas and see errors more easily in your drawing\"."
msgid "This one is probably not relevant for a manual. Sphinx can create these manually given some situations, but our configuration does not do so by default."
msgid "Horizontal rulers are usually used when the topic switches rather directly. This is very common in more narrative based writing, such as history or fiction. The Krita manual is more instruction and reference style writing, that is to say, we don't usually tell a long story to indicate how different elements come together, but rather long stories are there to motivate why certain steps are taken in a certain manner. Topic changes then usually happen because we go into a new section, rather than switching to a related section. It is therefore better to use headings or the ``.. Topic::`` directive. Headings also make it easier to read."
msgid "The rubric directive is a heading directive that at first glance looks like \"topic\", but where the topic is over several paragraphs, rubric itself only deals with the header, like so::"
msgid "Only when they fit semantically. This is especially necessary for the danger and warning admonishments, as seeing them too often can make users blind to them."
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 "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 "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 "At the top of the page you should see a dropbox with ``master`` as a chosen item."
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 "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 "Make sure you create a new branch for your changes, since september 2019, all changes should be branched from ``master``."
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 "Finally, go to the website of the original repository, 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 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 "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:`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:`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 "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 "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 "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 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 "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 "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=\"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"
# 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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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/user_support.rst:1
msgid "Introduction to user support."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/user_support.rst:20
msgid "Introduction to User Support"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/user_support.rst:35
msgid "Contents"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/user_support.rst:38
msgid "Tablet Support"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/user_support.rst:40
msgid "The majority of help requests are about pen pressure and tablet support in general."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/user_support.rst:44
msgid "Quick solutions"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/user_support.rst:46
msgid "*For Windows, all devices:*"
msgstr ""
#. +> trunk5
#: ../../contributors_manual/user_support.rst:48
msgid "Change API in :menuselection:`Settings --> Configure Krita... --> Tablet Settings`."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/user_support.rst:50
-msgid "Wintab: older standard; it supports multiple buttons and high number of pressure levels high. If it works fine for you, don't change to Windows Ink. 2-in-1 devices by default use Windows Ink, you can get a Wintab driver but you need to install it separately."
+msgid "Wintab: older standard; it supports multiple buttons and high number of pressure levels. If it works fine for you, don't change to Windows Ink. 2-in-1 devices by default use Windows Ink, you can get a Wintab driver but you need to install it separately."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/user_support.rst:52
-msgid "Windows Ink: newer standard; it cuts the pressure levels to 1024. It is more suitable for 2-in-1 devices like Surfacce Pro and Yoga. Some less known brands might not have this standard implemented."
+msgid "Windows 8+ Pointer (Windows Ink): newer standard; it cuts the pressure levels to 1024. It is more suitable for 2-in-1 devices like Surface Pro and Yoga. Some less known brands might not have this standard implemented."
msgid "Reinstall your driver (Windows Update often breaks tablet driver settings, reinstallation helps)."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/user_support.rst:58
msgid "*Wacom tablets:* if you get straight lines at the beginnings of the strokes, first try to update your driver: it should be fixed in 6.3.34-3. If it doesn't work, disable/minimize \"double-click distance\" in Wacom settings."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/user_support.rst:60
-msgid "*XP-Pen tablets, pressure being uneven:* either switch to Windows 8+ Pointer, or disable Windows Ink in XP-Pen settings."
+msgid "*XP-Pen tablets, pressure being uneven:* either switch to Windows 8+ Pointer (Windows Ink) in :menuselection:`Settings --> Configure Krita... --> Tablet Settings`, or disable Windows Ink in XP-Pen settings."
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/user_support.rst:65
+#: ../../contributors_manual/user_support.rst:64
msgid "Gathering information"
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/user_support.rst:67
+#: ../../contributors_manual/user_support.rst:66
msgid "Which OS do you use?"
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/user_support.rst:69
+#: ../../contributors_manual/user_support.rst:68
msgid "Which tablet do you have?"
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/user_support.rst:71
+#: ../../contributors_manual/user_support.rst:70
msgid "What is the version of the tablet driver?"
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/user_support.rst:73
+#: ../../contributors_manual/user_support.rst:72
msgid "Please collect Tablet Tester (:menuselection:`Settings --> Configure Krita... --> Tablet Settings`) text output and share it: :ref:`intro_user_support_sharing_files`."
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/user_support.rst:75
+#: ../../contributors_manual/user_support.rst:74
msgid "More detailed Tablet Events log:"
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/user_support.rst:77
+#: ../../contributors_manual/user_support.rst:76
msgid "Go to :menuselection:`Settings --> Dockers --> Log Viewer` docker, make sure it's checked."
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/user_support.rst:79
+#: ../../contributors_manual/user_support.rst:78
msgid "In the Log Viewer docker, make sure the first button is pressed (which means the logging is turned on)."
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/user_support.rst:81
-msgid "Press :kbd:`Ctlr + Shift + T` to turn on tablet events logging."
+#: ../../contributors_manual/user_support.rst:80
+msgid "Press :kbd:`Ctrl + Shift + T` to turn on tablet events logging."
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/user_support.rst:83
+#: ../../contributors_manual/user_support.rst:82
msgid "Make a few strokes (depending on the situation, the user supporter or developer can ask you for specific series of strokes)."
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/user_support.rst:85
-msgid "Press :kbd:`Ctlr + Shift + T` to turn off the logging of the tablet events."
+#: ../../contributors_manual/user_support.rst:84
+msgid "Press :kbd:`Ctrl + Shift + T` to turn off the logging of the tablet events."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/user_support.rst:87
msgid "Press the third button in the Log Viewer to save the output into a file."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/user_support.rst:89
msgid "Share the file or share the content of the file: :ref:`intro_user_support_sharing_files`."
msgstr ""
#. +> trunk5
#: ../../contributors_manual/user_support.rst:91
msgid "On Linux, you can just use a console instead of Log Viewer -- then you'd only need to enable tablet events logging, not logging in general."
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/user_support.rst:97
+#: ../../contributors_manual/user_support.rst:96
msgid "Additional information for supporters"
msgstr ""
#. +> trunk5
-#: ../../contributors_manual/user_support.rst:99
+#: ../../contributors_manual/user_support.rst:98
msgid "Except for the issue with beginnings of the strokes, Wacom tablets usually work no matter the OS."
msgid "If someone asks about a tablet to buy, generally a cheaper Wacom or a Huion are the best options as of 2019, if they want to work with Krita. :ref:`list_supported_tablets`."
msgid "`Possibly useful instruction in case of XP-Pen tablet issues <https://www.reddit.com/r/krita/comments/btzh72/xppen_artist_12s_issue_with_krita_how_to_fix_it/>`_."
msgid "Issues with rendering animation can be of various shapes and colors. First thing to find out is whether the issue happens on Krita's or FFmpeg's side (Krita saves all the frames, then FFmpeg is used to render a video using this sequence of images). To learn that, instruct the user to render as \"Image Sequence\". If the image sequence is correct, FFmpeg (or more often: render options) are at fault. If the image sequence is incorrect, either the options are wrong (if for example not every frame got rendered), or it's a bug in Krita."
msgid "If the user opens the Log Viewer docker, turns on logging and then tries to render a video, Krita will print out the whole ffmpeg command to Log Viewer so it can be easily investigated."
msgid "There is a log file called *log_encode.log* in the directory that user tries to render to. It can contain information useful to investigation of the issue (sharing files: :ref:`intro_user_support_sharing_files`)."
msgid "The great majority of issues with onion skin are just user errors, not bugs. Nonetheless, you need to find out why it happens and direct the user how to use onion skin properly."
msgid "In case of crash try to determine if the problem is known, if not, instruct user to create a bug report (or create it yourself) with following information:"
-msgid "Backtrace (crashlog) -- the instruction is here: :ref:`dr_minw`, and the debug symbols can be found in the annoucement of the version of Krita that the user has. But it could be easier to just point the user to `https://download.kde.org/stable/krita <https://download.kde.org/stable/krita>`_."
+msgid "Backtrace (crashlog) -- the instruction for Windows is here: :ref:`dr_minw`, and the debug symbols can be found in the annoucement of the version of Krita that the user has. But it could be easier to just point the user to `https://download.kde.org/stable/krita <https://download.kde.org/stable/krita>`_."
msgid "When the user has any weird issue, something you've never heard about, ask them to reset the configuration: :ref:`faq_reset_krita_configuration`."
msgid "When the user has trouble with anything related to preview or display, ask them to change :guilabel:`Canvas Graphics Acceleration` in :menuselection:`Settings --> Configure Krita... --> Display`."
msgid "If you don't know the solution but you know what information will be needed to investigate the issue further, don't hesitate to ask. Other supporters may know the answer, but have too little time to move the user through the whole process, so you're helping a lot just by asking for additional information. This is very much true in case of tablet issues, for example."
msgid "If you don't know the answer/solution and the question looks abandoned by other supporters, you can always ask for help on Krita IRC channel. It's #krita on freenote.net: :ref:`the_krita_community`."
msgid "Explain steps the user needs to make clearly, for example if you need them to change something in settings, clearly state the whole path of buttons and tabs to get there."
msgid "Instead of :menuselection:`Settings --> Configure Krita...` use just :menuselection:`Configure Krita` -- it's easy enough to find and Mac users (where you need to select :menuselection:`Krita --> Preferences...`) won't get confused."
msgid "If you ask for an image, mention usage of `Imgur <https://imgur.com>`_ or `Pasteboard <https://pasteboard.co>`_ (:ref:`intro_user_support_sharing_files`), otherwise Reddit users might create a new post with this image instead of including it to the old conversation."
msgid "If you want to quickly answer someone, just link to the appropriate place in this manual page -- you can click on the little link icon next to the section or subsection title and give the link to the user so they for example know what information about their tablet issue you need."
msgid "``.kra`` and other formats: by mail? Or encode the file using *base64* command on Linux, send by mail or on Pastebin, then decode using the same command."
msgid "If you ask user to store their log or other data on a website, make sure it stays there long enough for you to get it -- for example bpaste.net stores files by default only for a day! And you can extend it only to one week."
msgid "If the user is behind a firewall of some sorts (for example lives in China), websites with [*] will probably be blocked; please use the alternatives."
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 "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 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 "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 "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 "For exchanging between programs and devices: most CMYK profiles are a little bigger than our default sRGB in places, while in other places, they are smaller. To get the best conversion, having your image in a space that encompasses both your screen profile as your printer profile."
msgid "For archival purposes. In other words, maybe monitors of the future will have larger amounts of colors they can show (spoiler: they already do), and this allows you to be prepared for that."
-msgid "On the left we have an artifact-ridden color managed jpeg file with an ACES sRGBtrc v2 profile attached (or not, if not, then you can see the exact different between the colors more clearly). This should give an approximation of the actual colors. On the right, we have an sRGB png that was converted in Krita from the base file."
+msgid "On the left we have an artifact-ridden color managed JPEG file with an ACES sRGBtrc v2 profile attached (or not, if not, then you can see the exact different between the colors more clearly). This should give an approximation of the actual colors. On the right, we have an sRGB PNG that was converted in Krita from the base file."
msgid "Each of the gradients is the gradient from the max of a given channel. As you can see, the mid-tone of the ACES color space is much brighter than the mid-tone of the RGB colorspace, and this is because the primaries are further apart."
msgid "What this means for us is that when we start mixing or applying filters, Krita can output values higher than visible, but also generate more correct mixes and gradients. In particular, when color correcting, the bigger space can help with giving more precise information."
msgid "Bigger spaces do have the downside they require more precision if you do not want to see banding, so make sure to have at the least 16bit per channel when choosing a bigger space."
msgid "So, usually what we mean by viewing conditions is the lighting and decoration of the room that you are viewing the image in. Our eyes try to make sense of both the colors that you are looking at actively (the colors of the image) and the colors you aren't looking at actively (the colors of the room), which means that both sets of colors affect how the image looks."
msgid "**Left**: Let's ruin Vermeer by putting a bright purple background that asks for more attention than the famous painting itself. **Center**: a much more neutral backdrop that an interior decorator would hate but brings out the colors. **Right**: The approximate color that this painting is displayed against in real life in the Maurits House, at the least, last time I was there. Original image from wikipedia commons."
msgid "This is for example, the reason why museum exhibitioners can get really angry at the interior decorators when the walls of the museum are painted bright red or blue, because this will drastically change the way how the painting's colors look. (Which, if we are talking about a painter known for their colors like Vermeer, could result in a really bad experience)."
msgid "Lighting is the other component of the viewing condition which can have dramatic effects. Lighting in particular affects the way how all colors look. For example, if you were to paint an image of sunflowers and poppies, print that out, and shine a bright yellow light on it, the sunflowers would become indistinguishable from the white background, and the poppies would look orange. This is called `metamerism <https://en.wikipedia.org/wiki/Metamerism_%28color%29>`_, and it's generally something you want to avoid in your color management pipeline."
msgid "For example, if you are designing a print for a red t-shirt that's not bright red, but not super grayish red either. And you want to make sure the colors of the print match the color of the t-shirt, so you make a dummy background layer that is approximately that red, as correctly as you can observe it, and paint on layers above that dummy layer. When you are done, you hide this dummy layer and sent the image with a transparent background to the press."
msgid "But when you get the t-shirt from the printer, you notice that all your colors look off, mismatched, and maybe too yellowish (and when did that T-Shirt become purple?)."
msgid "You probably observed the t-shirt in a white room where there were incandescent lamps shining, because as a true artist, you started your work in the middle of the night, as that is when the best art is made. However, incandescent lamps have a black body temperature of roughly 2300-2800K, which makes them give a yellowish light, officially called White Point A."
msgid "Your computer screen on the other hand, has a black body temperature of 6500K, also known as D65. Which is a far more blueish color of light than the lamps you are hanging."
msgid "So, by eye-balling your t-shirt's color during the evening, you took its red color as transformed by the yellowish light. Had you made your observation in diffuse sunlight of an overcast (which is also roughly D65), or made it in direct sunlight light and painted your picture with a profile set to D50, the color would have been much closer, and thus your design would not be as yellowish."
msgid "Applying a white balance filter will sort of match the colors to the tone as in the middle, but you would have had a much better design had you designed against the actual color to begin with."
msgid "Now, you could technically quickly fix this by using a white balancing filter, like the ones in G'MIC, but because this error is caught at the end of the production process, you basically limited your use of possible colors when you were designing, which is a pity."
msgid "We have a presentation where we mark one type of item with red, another with yellow and yet another with purple. On a computer the differences between the colors are very obvious."
msgid "However, when we start projecting, the lights of the room aren't dimmed, which means that the tone scale of the colors becomes crunched, and yellow becomes near indistinguishable from white. Furthermore, because the light in the room is slightly yellowish, the purple is transformed into red, making it indistinguishable from the red. Meaning that the graphic is difficult to read."
msgid "In both cases, you can use Krita's color management a little to help you, but mostly, you just need to be ''aware'' of it, as Krita can hardly fix that you are looking at colors at night, or the fact that the presentation hall owner refuses to turn off the lights."
-msgid "That said, unless you have a display profile that uses LUTs, such as an OCIO LUT or a cLUT icc profile, white point won't matter much when choosing a working space, due to weirdness in the icc v4 workflow which always converts matrix profiles with relative colorimetric, meaning the white points are matched up."
+msgid "That said, unless you have a display profile that uses LUTs, such as an OCIO LUT or a cLUT ICC profile, white point won't matter much when choosing a working space, due to weirdness in the ICC v4 workflow which always converts matrix profiles with relative colorimetric, meaning the white points are matched 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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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
#: ../../general_concepts/file_formats.rst:1
msgid "The file formats category."
msgstr ""
#. +> trunk5
#: ../../general_concepts/file_formats.rst:14
msgid "File Formats"
msgstr ""
#. +> trunk5
#: ../../general_concepts/file_formats.rst:16
msgid "This category is for graphics file-formats. While most file-formats can be looked up on wikipedia, this doesn't always explain what the format can be used for and what its strengths and weaknesses are."
msgstr ""
#. +> trunk5
#: ../../general_concepts/file_formats.rst:18
msgid "In this category we try to describe these in a manner that can be read by beginners."
msgstr ""
#. +> trunk5
#: ../../general_concepts/file_formats.rst:20
msgid "Generally, there are the following features that people pay attention to in regards to file formats:"
msgstr ""
#. +> trunk5
#: ../../general_concepts/file_formats.rst:23
msgid "Compression"
msgstr ""
#. +> trunk5
#: ../../general_concepts/file_formats.rst:25
msgid "Compression is how the file-format tries to describe the image with as little data as possible, so that the resulting file is as small as it can get without losing quality."
msgstr ""
#. +> trunk5
#: ../../general_concepts/file_formats.rst:27
msgid "What we generally see is that formats that are small on disk either lose image quality, or require the computer to spend a lot of time thinking about how the image should look."
msgstr ""
#. +> trunk5
#: ../../general_concepts/file_formats.rst:29
msgid "Vector file-formats like ``SVG`` are a typical example of the latter. They are really small because the technology used to create them is based on mathematics, so it only stores maths-variables and can achieve very high quality. The downside is that the computer needs to spend a lot of time thinking about how it should look, and sometimes different programs have different ways of interpreting the values. Furthermore, vector file-formats imply vector graphics, which is a very different way of working than Krita is specialized in."
msgstr ""
#. +> trunk5
#: ../../general_concepts/file_formats.rst:31
msgid ":ref:`Lossy file formats <lossy_compression>`, like ``JPG`` or ``WebP`` are an example of small on disk, but lowering the quality, and are best used for very particular types of images. Lossy thus means that the file format plays fast and loose with describing your image to reduce filesize."
msgstr ""
#. +> trunk5
#: ../../general_concepts/file_formats.rst:33
msgid ":ref:`Non-lossy or lossless formats <lossless_compression>`, like ``PNG``, ``GIF`` or ``BMP`` are in contrast, much heavier on disk, but much more likely to retain quality."
msgstr ""
#. +> trunk5
#: ../../general_concepts/file_formats.rst:35
msgid "Then, there's proper working file formats like Krita's ``KRA``, Gimp's ``XCF``, Photoshop's ``PSD``, but also interchange formats like ``ORA`` and ``EXR``. These are the heaviest on the hard-drive and often require special programs to open them up, but on the other hand these are meant to keep your working environment intact, and keep all the layers and guides in them."
msgstr ""
#. +> trunk5
#: ../../general_concepts/file_formats.rst:38
msgid "Metadata"
msgstr ""
#. +> trunk5
#: ../../general_concepts/file_formats.rst:40
-msgid "Metadata is the ability of a file format to contain information outside of the actual image contents. This can be human readable data, like the date of creation, the name of the author, a description of the image, but also computer readable data, like an icc-profile which tells the computer about the qualities of how the colors inside the file should be read."
+msgid "Metadata is the ability of a file format to contain information outside of the actual image contents. This can be human readable data, like the date of creation, the name of the author, a description of the image, but also computer readable data, like an ICC profile which tells the computer about the qualities of how the colors inside the file should be read."
msgstr ""
#. +> trunk5
#: ../../general_concepts/file_formats.rst:43
msgid "Openness"
msgstr ""
#. +> trunk5
#: ../../general_concepts/file_formats.rst:45
msgid "This is a bit of an odd quality, but it's about how easy it to open or recover the file, and how widely it's supported."
msgstr ""
#. +> trunk5
#: ../../general_concepts/file_formats.rst:47
msgid "Most internal file formats, like PSD are completely closed, and it's really difficult for human outsiders to recover the data inside without opening Photoshop. Other examples are camera raw files which have different properties per camera manufacturer."
msgstr ""
#. +> trunk5
#: ../../general_concepts/file_formats.rst:49
msgid "SVG, as a vector file format, is on the other end of the spectrum, and can be opened with any text-editor and edited."
msgstr ""
#. +> trunk5
#: ../../general_concepts/file_formats.rst:51
msgid "Most formats are in-between, and thus there's also a matter of how widely supported the format is. JPG and PNG cannot be read or edited by human eyes, but the vast majority of programs can open them, meaning the owner has easy access to them."
msgid "``.exr`` is the prime file format for saving and loading :ref:`floating point bit depths <bit_depth>`, and due to the library made to load and save these images being fully open source, the main interchange format as well."
msgid "Floating point bit-depths are used by the computer graphics industry to record scene referred values, which can be made via a camera or a computer renderer. Scene referred values means that the file can have values whiter than white, which in turn means that such a file can record lighting conditions, such as sunsets very accurately. These EXR files can then be used inside a renderer to create realistic lighting."
msgid "Krita can load and save EXR for the purpose of paint-over (yes, Krita can paint with scene referred values) and interchange with applications like Blender, Mari, Nuke and Natron."
msgid "This'll turn the darkest values of the image as the ones that paint, and the whitest as transparent. Untick this if you are using colored images for the brush."
msgid "``.gif`` is a file format mostly known for the fact that it can save animations. It's a fairly old format, and it does its compression by :ref:`indexing <bit_depth>` the colors to a maximum of 256 colors per frame. Because we can technically design an image for 256 colors and are always able save over an edited GIF without any kind of extra degradation, this is a :ref:`lossless <lossless_compression>` compression technique."
msgid "This means that it can handle most grayscale images just fine and without losing any visible quality. But for color images that don't animate it might be better to use :ref:`file_jpg` or :ref:`file_png`."
msgid "Image Hose means that this file format allows you to store multiple images and then set some options to make it specify how to output the multiple images."
+msgid "The GIMP image hose format allows multiple dimensions for a given brush. You could for example have a dimension that updates incrementally, and one that updates on pressure, or updates randomly. Upon export, Krita will use the ranks to subdivide the layers per dimension. If you have a 24 layer image and three ranks, and the first dimension is set to 2, the second to 4 and the third to 3, then Krita will divide 24 into 2 groups of 12, each of which have unique images for the 2 parts of the first dimension. Then those 2 groups of 12 get divided into 8 groups of 4, each of which have unique brush tips for the four parts of the second dimension, and finally, the grouped three images have each a unique brush for the final dimension."
+msgid "So, the following image has a table where dimension 1 is unique in one of 4 numbers, while dimension 2 is unique in one of 3 shapes. So our ranks for dimension 1 and dimension 2 need to be 4 and 3 respectively. Now, to order the layers, you need to subdivide the table first by the first dimension, and then by the second. So we end up with three layers each for a shape in the second dimension but for the first number, then another three layers, each for a shape, but then for the second number, and so forth."
msgid "This'll draw the images randomly. This is good for image-collections used in speedpainting as well as images that generate texture. Or perhaps more graphical symbols."
msgid "When exporting a Krita file as a ``.gih``, you will also get the option to set the default spacing, the option to set the name (very important for looking it up in the UI) and the ability to choose whether or not to generate the mask from the colors."
msgid "This'll turn the darkest values of the image as the ones that paint, and the whitest as transparent. Untick this if you are using colored images for the brush."
msgid "Photographs have the problem that they have a lot of little gradients, which means that you cannot index the file like you can with :ref:`file_gif` and expect the result to look good. What JPEG instead does is that it converts the file to a perceptual color space (:ref:`YCrCb <model_ycrcb>`), and then compresses the channels that encode the colors, while keeping the channel that holds information about the relative lightness uncompressed. This works really well because human eye-sight is not as sensitive to colorfulness as it is to relative lightness. JPEG also uses other :ref:`lossy <lossy_compression>` compression techniques, like using cosine waves to describe image contrasts."
msgid "However, it does mean that JPEG should be used in certain cases. For images with a lot of gradients, like full scale paintings, JPEG performs better than :ref:`file_png` and :ref:`file_gif`."
msgid "But for images with a lot of sharp contrasts, like text and comic book styles, PNG is a much better choice despite a larger file size. For grayscale images, :ref:`file_png` and :ref:`file_gif` will definitely be more efficient."
msgid "Because JPEG uses lossy compression, it is not advised to save over the same JPEG multiple times. The lossy compression will cause the file to reduce in quality each time you save it. This is a fundamental problem with lossy compression methods. Instead use a lossless file format, or a working file format while you are working on the image."
msgid "Since 4.0, Krita has a new palette file-format that can handle colors that are wide gamut, RGB, CMYK, XYZ, GRAY, or LAB, and can be of any of the available bitdepths, as well as groups. These are Krita Palettes, or ``*.kpl``."
-msgid "``*.kpl`` files are ZIP files, with two XMLs and ICC profiles inside. The colorset XML contains the swatches as ColorSetEntry and Groups as Group. The profiles.XML contains a list of profiles, and the ICC profiles themselves are embedded to ensure compatibility over different computers."
+msgid "``*.kpl`` files are ZIP files, with two XMLs and ICC profiles inside. The colorset XML contains the swatches as ColorSetEntry and Groups as Group. The *profiles.xml* contains a list of profiles, and the ICC profiles themselves are embedded to ensure compatibility over different computers."
msgid "``.png``, or Portable Network Graphics, is a modern alternative to :ref:`file_gif` and with that and :ref:`file_jpg` it makes up the three main formats that are widely supported on the internet."
msgid "PNG is a :ref:`lossless <lossless_compression>` file format, which means that it is able to maintain all the colors of your image perfectly. It does so at the cost of the file size being big, and therefore it is recommended to try :ref:`file_jpg` for images with a lot of gradients and different colors. Grayscale images will do better in PNG as well as images with a lot of text and sharp contrasts, like comics."
msgid "Like :ref:`file_gif`, PNG can support indexed color. Unlike :ref:`file_gif`, PNG doesn't support animation. There have been two attempts at giving animation support to PNG, APNG and MNG, the former is unofficial and the latter too complicated, so neither have really taken off yet."
msgid "Since 4.2 we support saving HDR to PNG as according to the `W3C PQ HDR PNG standard <https://www.w3.org/TR/png-hdr-pq/>`_. To save as such files, toggle :guilabel:`Save as HDR image (Rec. 2020 PQ)`, which will convert your image to the Rec 2020 PQ color space and then save it as a special HDR PNG."
msgid "Being vector graphics, SVG is very light weight. This is because it usually only stores coordinates and parameters for the maths involved with vector graphics."
-msgid "While you can open up SVG files with any text-editor to edit them, it is best to use a vector program like Inkscape. Krita 2.9 to 3.3 supports importing SVG via the add shape docker. Since Krita 4.0, SVGs can be properly imported, and you can export singlevector layers via :menuselection:`Layer --> Import/Export --> Save Vector Layer as SVG...`. For 4.0, Krita will also use SVG to save vector data into its :ref:`internal format <file_kra>`."
+msgid "While you can open up SVG files with any text-editor to edit them, it is best to use a vector program like Inkscape. Krita 2.9 to 3.3 supports importing SVG via the add shape docker. Since Krita 4.0, SVGs can be properly imported, and you can export singlevector layers via :menuselection:`Layer --> Import/Export --> Save Vector Layer as SVG...` menu item. For 4.0, Krita will also use SVG to save vector data into its :ref:`internal format <file_kra>`."
msgid "SVG is designed for the internet, though sadly, because vector graphics are considered a bit obscure compared to raster graphics, not a lot of websites accept them yet. Hosting them on your own webhost works just fine though."
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 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 "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 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 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 "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."
# 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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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
#: ../../index.rst:5
msgid "Welcome to the Krita |version| Manual!"
msgstr ""
#. +> trunk5
#: ../../index.rst:7
msgid "Welcome to Krita's documentation page."
msgstr ""
#. +> trunk5
#: ../../index.rst:9
msgid "Krita is a sketching and painting program designed for digital artists. Our vision for Development of Krita is —"
msgstr ""
#. +> trunk5
#: ../../index.rst:11
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
#: ../../index.rst:19
msgid "Krita's tools are developed keeping the above vision in mind. Although it has features that overlap with other raster editors its intended purpose is to provide robust tool for digital painting and creating artworks from scratch. As you learn about Krita, keep in mind that it is not intended as a replacement for Photoshop. This means that the other programs may have more features than Krita for image manipulation tasks, such as stitching together photos, while Krita's tools are most relevant to digital painting, concept art, illustration, and texturing. This fact accounts for a great deal of Krita's design."
msgstr ""
#. +> trunk5
#: ../../index.rst:28
msgid "You can download this manual as an epub `here <https://docs.krita.org/en/epub/KritaManual.epub>`_."
msgstr ""
#. +> trunk5
#: ../../index.rst:33
msgid ":ref:`user_manual`"
msgstr ""
#. +> trunk5
#: ../../index.rst:33
msgid ":ref:`tutorials`"
msgstr ""
#. +> trunk5
#: ../../index.rst:35
msgid "Discover Krita’s features through an online manual. Guides to help you transition from other applications."
msgstr ""
#. +> trunk5
#: ../../index.rst:35
msgid "Learn through developer and user generated tutorials to see Krita in action."
msgstr ""
#. +> trunk5
#: ../../index.rst:41
msgid ":ref:`getting_started`"
msgstr ""
#. +> trunk5
#: ../../index.rst:41
msgid ":ref:`reference_manual`"
msgstr ""
#. +> trunk5
#: ../../index.rst:43
msgid "New to Krita and don't know where to start?"
msgstr ""
#. +> trunk5
#: ../../index.rst:43
-msgid "A quick run-down of all of the tools that are available"
+msgid "A quick run-down of all of the tools that are available."
msgstr ""
#. +> trunk5
#: ../../index.rst:48
msgid ":ref:`general_concepts`"
msgstr ""
#. +> trunk5
#: ../../index.rst:48
msgid ":ref:`faq`"
msgstr ""
#. +> trunk5
#: ../../index.rst:50
msgid "Learn about general art and technology concepts that are not specific to Krita."
msgstr ""
#. +> trunk5
#: ../../index.rst:50
msgid "Find answers to the most common questions about Krita and what it offers."
msgstr ""
#. +> trunk5
#: ../../index.rst:55
msgid ":ref:`resources_page`"
msgstr ""
#. +> trunk5
#: ../../index.rst:55
msgid ":ref:`genindex`"
msgstr ""
#. +> trunk5
#: ../../index.rst:57
msgid "Textures, brush packs, and python plugins to help add variety to your artwork."
msgstr ""
#. +> trunk5
#: ../../index.rst:57
msgid "An index of the manual for searching terms by browsing."
msgid "When the result of the addition is more than 1, white is the color displayed. Therefore, white plus any other color results in white. On the other hand, black plus any other color results in the added color."
-msgid "This is often used to color in a black and white lineart. One puts the black and white lineart on top, and sets the layer to 'Multiply', and then draw in color on a layer beneath. Multiply will all the color to go through."
+msgid "This is often used to color in a black and white lineart. One puts the black and white lineart on top, sets the layer to 'Multiply', and then draws in color on a layer beneath. Multiply will allow all the color to go through."
msgid "This inverts the bottom layer, then divides it by the top layer, and inverts the result. This results in a darkened effect that takes the colors of the lower layer into account, similar to the burn technique used in traditional darkroom photography."
msgid "Aims to solve issues with Color Burn blending mode by using a formula which falloff is similar to Dodge, but the falloff rate is softer. It is within the range of 0.0f and 1.0f unlike Color Burn mode."
msgid "Darken the image in a way that there is a 'fog' in the end result. This is due to the unique property of fog darken in which midtones combined are lighter than non-midtones blend."
msgid "With the darken, the upper layer's colors are checked for their lightness. Only if they are darker than the underlying color on the lower layer, will they be visible."
msgid "Basically, the blending mode only ends in shades of shades. This means that it's very useful for painting shading colors while still in the range of shades."
msgid "Page about the lighten blending modes in Krita: Color Dodge, Gamma Illumination, Gamma Light, Easy Dodge, Flat Light, Fog Lighten, Hard Light, Lighten, Lighter Color, Linear Dodge, Linear Light, P-Norm A, P-Norm B, Pin Light, Screen, Soft Light, Tint and Vivid Light."
msgid "Similar to Divide. Inverts the top layer, and divides the lower layer by the inverted top layer. This results in a image with emphasized highlights, like Dodging would do in traditional darkroom photography."
msgid "Hard light checks if the color on the upperlayer has a lightness above 0.5. Unlike overlay, if the pixel is lighter than 0.5, it is blended like in Multiply mode, if not the pixel is blended like in Screen mode."
msgid "With the darken, the upper layer's colors are checked for their lightness. Only if they are Lighter than the underlying color on the lower layer, will they be visible."
msgid "Aims to solve issues with Color Dodge blending mode by using a formula which falloff is similar to Dodge, but the falloff rate is softer. It is within the range of 0.0f and 1.0f unlike Color Dodge mode."
msgid "Lightens the image in a way that there is a 'fog' in the end result. This is due to the unique property of fog lighten in which midtones combined are lighter than non-midtones blend."
msgid "Combines :ref:`bm_linear_dodge` and :ref:`bm_linear_burn`. When the lightness of the upper-pixel is higher than 0.5, it uses Linear dodge, if not, Linear burn to blend the pixels."
+msgid "Takes the opacity of the new color (combined opacity of the layer, the brush, any used transparency masks etc.) and multiples the color by the opacity, then adds to the original/previous color."
+msgid "The result of this operation is the same as combining the new pixels with a fully opaque black layer in a :ref:`bm_normal` mode and then combining the result with the original layer using :ref:`bm_addition` mode. It should be also the same as the results of \"Luminosity\" blending mode in SAI1 or \"Shine\" blending mode in SAI2."
msgid "P-Norm A is similar to Screen blending mode which slightly darken images, and the falloff is more consistent all-around in terms of outline of values. Can be used an alternative to screen blending mode at times."
msgid "P-Norm B is similar to Screen blending mode which slightly darken images, and the falloff is more consistent all-around in terms of outline of values. The falloff is sharper in P-Norm B than in P-Norm A. Can be used an alternative to screen blending mode at times."
msgid "Checks which is darker the lower layer's pixel or the upper layer's double so bright. Then checks which is brighter of that result or the inversion of the doubled lower layer."
msgid "The SVG version is slightly different to the Photoshop version in that it uses a slightly different bit of formula when the lightness of the lower pixel is lower than 25%, this prevents the strength of the brightness increase."
msgid "These are alternative versions of standard softlight modes which are made to solve discontinuities seen with the standard blend modes. Sometimes, these modes offer subtle advantages by offering more contrast within some areas, and these advantages are more or less noticeable within different color spaces and depth."
msgid "Basically, the blending mode only ends in shades of tints. This means that it's very useful for painting light colors while still in the range of tints."
msgid "Mixes both Color Dodge and Burn blending modes. If the color of the upper layer is darker than 50%, the blending mode will be Burn, if not the blending mode will be Color Dodge."
msgid "This algorithm doesn't use color dodge and burn, we don't know WHAT it does do but for Color Dodge and Burn you need to use :ref:`bm_hard_mix`."
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 "The curve brush is a brush engine which creates strokes made of evenly spaced lines. It has, among other things been used as a replacement for pressure sensitive strokes in lieu of a tablet."
msgid "The curve lines I think, which are the extra fancy lines that form at curves. The curve lines are formed by connecting one point of the curve to a point earlier on the curve. This also means that if you are drawing a straight line, these lines won't be visible, since they'll overlap with the connection line. Drawing faster gives you wider curves areas."
msgid "So in fact, you'll get maximum curve lines area with a mid-value of say... 40~60, which is about the default value. Unless you're drawing at really high resolutions."
msgid "Curves opacity: you can't set different line widths for the connection line and the curve lines, but you can set a different opacity for the curve lines. With low opacity, this will produce the illusion of thinner curve lines."
msgid "Use the Draw Dynamically mode: I tend to increase drag to at least 50. Vary Mass and Drag until you get the feel that's most comfortable for you."
msgid "If you're a tablet user, just set this to Pressure (this should be selected by default so just turn on the Line Width dynamics). I can't check myself, but a tablet user confirmed to me that it works well enough with Draw Dynamically."
msgid "Set Curves opacity to 0: This is the simplest way to turn off the Curve lines. That said, leaving them on will get you more \"expressive\" lines."
msgid "Use smooth, sweeping motions when you're using Draw Dynamically with Line Width set to Speed: abrupt speed transitions will cause abrupt size transitions. It takes a bit of practice, and the thicker the line, the more visible the deformities will be. Also, zoom in to increase control."
msgid "If you need to vary between thin and thick lines, I suggest creating presets of different widths, since you can't vary the base line width from the canvas."
msgid "Brushes are ordered alphabetically. The brush that is selected by default when you start with Krita is the :guilabel:`Pixel Brush`. The pixel brush is the traditional mainstay of digital art. This brush paints impressions of the brush tip along your stroke with a greater or smaller density."
msgid "Select a brush tip. This can be a generated brush tip (round, square, star-shaped), a predefined bitmap brush tip, a custom brush tip or a text."
msgid "Select the effects: the pressure of your stylus, your speed of painting or other inputs can change the size, the color, the opacity or other aspects of the currently painted brush tip instance -- some applications call that a \"dab\"."
msgid "Depending on the brush mode, the previously painted brush tip instance is mixed with the current one, causing a darker, more painterly stroke, or the complete stroke is computed and put on your layer. You will see the stroke grow while painting in both cases, of course!"
msgid "Having all three parameters on Fuzzy will help with rich color texture. In combination with :ref:`option_mix`, you can have even finer control."
msgid "this sets the softness of the brush. You can click the chain-symbol to lock and unlock these settings. Fade has a different effect per mask-type, so don't be alarmed if it looks strange, perhaps you have the wrong mask-type."
msgid "This determines how much area the brush-covers over its size: It makes it noisy. In the example below, the brush is set with density 0%, 50% and 100% respectively."
msgid "Ticking this will set the brush-spacing to a different (quadratic) algorithm. The result is fine control over the spacing. In the below picture, the three examples on right are with auto spacing, 0, 1 and 5 respectively."
msgid "This toggles the super-smooth anti-aliasing. In the below example, both strokes are drawn with a default brush with fade set to 0. On the left without smooth lines, and the right with. Very useful for inking brushes. This option is best used in combination with Auto Spacing."
msgid "This changes how smooth the brush is rendered. The lower, the faster the brush, but the worse the rendering looks. You'd want an inking brush to have a precision of 5 at all times, but a big filling brush for painting doesn't require such precision, and can be easily sped up by setting precision to 1."
msgid "This allows you to set the precision linked to the size. The first value is the brush size at which precision is last 5, and the second is the size-difference at which the precision will decrease."
msgid "If you have used other applications like :program:`GIMP` or :program:`Photoshop`, you will have used this kind of brush. :program:`Krita` is (mostly) compatible with the brush tip definitions files of these applications:"
-msgid "GIMP Image Hose brush tip: contains a series of brush tips that are painted randomly or in order after each other. Can be black and white or colored. :program:`Krita` does not yet support all the parameters yet."
+msgid "Gimp Image Hose brush tip: contains a series of brush tips that are painted randomly or in order after each other. Can be black and white or colored. :program:`Krita` does not yet support all the parameters yet."
msgid "Note that the definition of ABR brushes has been reverse engineered since Adobe does not make the specification public. We strongly recommend every :program:`Krita` user to share brush tips in GBR and GIH format and more complex brushes as :program:`Krita` presets."
msgid "All predefined brush tips are shown in one selector. There are four more options that influence the initial bitmap brush tip you start painting with:"
msgid "Scales the brush tip. 1.0 is the native size of the brush tip. This can be fairly large! When painting with variable size (for instance governed by pressure), this is the base for the calculations."
msgid "For colored brushes, don't paint the actual colors, but make a grayscale brush tip that will be colored by your selected foreground/background color. Lighter areas will be interpreted as more transparent."
msgid "Similar to mask, except maintaining the lightness differences in the brush tip. Transparency stays the same as it does in colored mode, but darker tones will be in the tone of the current foreground color. There are three sliders here, to control the exact feel of the current brush tip in this mode:"
msgid "This is the lightness level that will be the same as your current foreground color. Higher values than this will be lighter versions of the current foreground color, and lower, darker versions of the current color."
msgid "Masked brush is new feature that is only available in the :ref:`pixel_brush_engine`. They are additional settings you will see in the brush editor. Masked brushes allow you to combine two brush tips in one stroke. One brush tip will be a mask for your primary brush tip. A masked brush is a good alternative to texture for creating expressive and textured brushes."
msgid "Due to technological constraints, the masked brush only works in the wash painting mode. However, do remember that flow works as opacity does in the build-up painting mode."
msgid "Like with normal brush tip you can choose any brush tip and change it size, spacing, and rotation. Masking brush size is relative to main brush size. This means when you change your brush size masking tip will be changed to keep the ratio."
msgid "The opacity and flow of the second tip. This is mapped to a sensor by default. Flow can be quite aggressive on subtract mode, so it might be an idea to turn it off there."
msgid "Cutoff is... the grayscale range that you can limit the texture to. This also affects the limit takes by the strength. In the below example, we move from the right arrow moved close to the left one, resulting in only the darkest values being drawn. After that, three images with larger range, and underneath that, three ranges with the left arrow moved, result in the darkest values being cut away, leaving only the lightest. The last example is the pattern without cutoff."
msgid "Adjust the pattern with a simple brightness/contrast filter to make it easier to use. Because Subtract and Multiply work differently, it's recommended to use different values with each:"
msgid "This allows you to set the texture to Sensors. It will use the cutoff to continuously draw lighter values of the texture (making the result darker)."
# 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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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 "Angle"
msgstr ""
#. +> trunk5
#: ../../reference_manual/clones_array.rst:1
-msgid "The Clones Array functionality in Krita"
+msgid "The Clones Array functionality in Krita."
msgstr ""
#. +> trunk5
#: ../../reference_manual/clones_array.rst:10
#: ../../reference_manual/clones_array.rst:15
msgid "Clones Array"
msgstr ""
#. +> trunk5
#: ../../reference_manual/clones_array.rst:10
msgid "Clone"
msgstr ""
#. +> trunk5
#: ../../reference_manual/clones_array.rst:17
msgid "Allows you to create a set of clone layers quickly. These are ordered in terms of rows and columns. The default options will create a 2 by 2 grid. For setting up tiles of an isometric game, for example, you'd want to set the X offset of the rows to half the value input into the X offset for the columns, so that rows are offset by half. For a hexagonal grid, you'd want to do the same, but also reduce the Y offset of the grids by the amount of space the hexagon can overlap with itself when tiled."
msgstr ""
#. +> trunk5
#: ../../reference_manual/clones_array.rst:19
msgid "\\- Elements"
msgstr ""
#. +> trunk5
#: ../../reference_manual/clones_array.rst:20
msgid "The amount of elements that should be generated using a negative of the offset."
msgstr ""
#. +> trunk5
#: ../../reference_manual/clones_array.rst:21
msgid "\\+ Elements"
msgstr ""
#. +> trunk5
#: ../../reference_manual/clones_array.rst:22
msgid "The amount of elements that should be generated using a positive of the offset."
msgstr ""
#. +> trunk5
#: ../../reference_manual/clones_array.rst:23
msgid "X offset"
msgstr ""
#. +> trunk5
#: ../../reference_manual/clones_array.rst:24
msgid "The X offset in pixels. Use this in combination with Y offset to position a clone using Cartesian coordinates."
msgstr ""
#. +> trunk5
#: ../../reference_manual/clones_array.rst:25
msgid "Y offset"
msgstr ""
#. +> trunk5
#: ../../reference_manual/clones_array.rst:26
msgid "The Y offset in pixels. Use this in combination with X offset to position a clone using Cartesian coordinates."
msgstr ""
#. +> trunk5
#: ../../reference_manual/clones_array.rst:27
msgid "Distance"
msgstr ""
#. +> trunk5
#: ../../reference_manual/clones_array.rst:28
msgid "The line-distance of the original origin to the clones origin. Use this in combination with angle to position a clone using a polar coordinate system."
msgstr ""
#. +> trunk5
#: ../../reference_manual/clones_array.rst:30
msgid "The angle-offset of the column or row. Use this in combination with distance to position a clone using a polar coordinate system."
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 "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 :guilabel:`Predefined:` drop-down. This can also be saved as a new predefined preset for your future use by giving a name in the :guilabel:`Save Image Size as:` input box and clicking on the :guilabel:`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 "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 <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 <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 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 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 "Select hue and saturation on the wheel (5) and value on the value scale (4). |mouseleft| changes foreground color (6). |mouseright| changes background color (7)."
msgid "The blip shows the position of current foreground color on the wheel (black&white circle) and on the value scale (black&white line). Last selected swatches are outlined."
msgid "Parameters of the wheel can be set in :ref:`artistic_color_selector_docker_wheel_preferences` menu (2). Selector settings are found under :ref:`artistic_color_selector_docker_selector_settings` menu (3)."
msgid "In the gamut masking toolbar (1) you can toggle the selected mask off and on (left button). You can also rotate the mask with the rotation slider (right)."
msgid "The value scale and hue sectors can also be set to continuous mode (with the infinity icon on the right of the slider). If toggled on, the respective area shows a continuous gradient instead of the discrete swatches."
msgid "Changes the order of saturation rings within the the hue sectors. By default, the wheel has gray in the center and most saturated colors on the perimeter. :guilabel:`Invert saturation` puts gray on the perimeter and most saturated colors in the center."
msgid "If the selector's color space is HSY, you can set custom Luma coefficients and the amount of gamma correction applied to the value scale (set to 1.0 for linear scale; see :ref:`linear_and_gamma`)."
msgid "The selector can be set either to :guilabel:`Enforce gamut mask`, so that colors outside the mask cannot be selected, or to :guilabel:`Just show the shapes`, where the mask is visible but color selection is not limited."
msgid "Values the color wheel and value scale will be reset to default when the :guilabel:`Reset to default` button in :ref:`artistic_color_selector_docker_wheel_preferences` is pressed."
msgid "The channel docker allows you to turn on and off the channels associated with the color space that you are using. Each channel has an enabled and disabled checkbox. You cannot edit individual layer channels from this docker."
msgid "If you want to edit individual channels by their grayscale component, you will need to manually separate a layer. This can be done with a series of commands with the layer docker."
msgid "When working with editing channels, it can be easier to use the Isolate Layer feature to only see the channel. Right-click on the layer to find Isolate Layer."
msgid "The mask is intended to be composed of basic vector shapes. Although interesting results might arise from using advanced vector drawing techniques, not all features are guaranteed to work properly (e.g. grouping, vector text, etc.)."
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 "A Histogram is a chart that shows how much of a specific channel value is used in an image. Its purpose is to give a really technical representation of the colors in an image, which can be helpful in decision making about filters."
msgid "There's an image strip beneath the browser, allowing you to select the image which you want to use. Double click to load it in the :guilabel:`Image` tab."
msgid "This tab allows you to see the images you selected, and change the zoom level. Clicking anywhere on the image will allow you to pick the merged color from it. Using the cross symbol, you can remove the icon."
+msgid "The main part of the docker is a list of all saved snapshots. At the bottom of the docker, there are three buttons: from left to right, they are :guilabel:`Create snapshot`, :guilabel:`Switch to selected snapshot`, and :guilabel:`Remove selected snapshot`. You can create a snapshot from the current state of the document by clicking :guilabel:`Create snapshot`. Click :guilabel:`Switch to selected snapshot` to switch to the selected snapshot. The undo stack will be discarded after switching. If you would like to save the current state, make another snapshot before switching. Click :guilabel:`Remove selected snapshot` to delete the selected snapshot. You can edit the names of snapshots by double-clicking them."
+msgid "Please be aware that all snapshots will be gone if you close the document. If you want to keep them, you need to explicitly save or export them."
-msgid "Fairly straightforward. This color space chooser allows you to pick the color space, the bit depth and the icc profile in which you are going to pick your color. Use the checkbox 'show color space selector' to hide this feature."
+msgid "Fairly straightforward. This color space chooser allows you to pick the color space, the bit depth and the ICC profile in which you are going to pick your color. Use the checkbox 'show color space selector' to hide this feature."
msgid "These change per color space. If you chose 16bit float or 32 bit float, these will go from 0 to 1.0, with the decimals deciding the difference between colors."
msgid "This is only available for the color spaces with a depth of 8 bit. This allows you to input hex color codes, and receive the RGB, CMYK, LAB, XYZ or YCrCb equivalent, and the other way around!"
# 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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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.)."
+msgid "**A. Layer List --** This area contains some subset of the layers of your current document. Similar to the Layers Docker, each layer has various properties that can also be toggled here (visibility, locking, onion skins, etc.). While the currently active layer is always shown here, layers can also be \"pinned\" to the timeline using the :guilabel:`Pin to Timeline` menu action or the :guilabel:`Pin Existing Layer` submenu so they will be visible even when inactive. Layers that are created via the Timeline are pinned automatically and by checking the :guilabel:`Automatically pin new layers to timeline` option in :guilabel:`Configure Krita > General > Miscellaneous` all new paint layers can be pinned automatically."
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 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."
+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.)"
+msgid "**E. Layer Menu --** A small menu for manipulating animation layers. You can create new layers, remove existing ones, as well as pin or unpin the active layer. (This menu also shows up when right-clicking on layer headers 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*."
+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*. To move a frame around, you can drag and drop it into another empty frame slot."
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."
+msgid "While animating you may find that you want to keep a layer \"pinned\", making it visible in the Timeline Docker regardless of which layer is selected. There are a few ways to do this in Krita. By |mouseright| clicking on any layer in the Layers Docker, you can pin it by activating the :guilabel:`Pin to Timeline` menu item. This allows you to decide which layers are important to see in your timeline (i.e. those which contain keyframe drawings) and which layers are not (i.e. a static layout drawing or background painting). Alternatively, you can open the Timeline Docker's Layer Menu and select a layer from the :guilabel:`Pin Existing Layer` submenu. Finally, you can enable the :guilabel:`Automatically pin new layers to timeline` option from the :guilabel:`Configure Krita > General > Miscellaneous` dialog."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dockers/timeline.rst:77
-msgid "You can drag and drop the frame around to a different empty frame slot."
+msgid "To add a 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. 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: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."
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."
-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."
-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."
+msgid "Clicking with |mouseright| within the Frame Timing Header instead of the Frame Table 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."
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."
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."
-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 "To manually play your animation back and forward using your mouse, an important technique that's known as *scrubbing*, click-drag within the Frame Timing Header."
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 "The Touch Docker is a QML docker with several convenient actions on it. Its purpose is to aid those who use Krita on a touch-enabled screen by providing bigger gui elements."
-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 "This docker allows you to quickly shift between undo states, and even go back in time far more quickly than 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 "According to this parameter -- groups are made. Every stroke is put into the same group until 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."
+msgid "A user may want to keep the ability of Undoing/Redoing his/her last N strokes. Once N is crossed -- the earlier strokes are merged into the group's first stroke."
-msgid "The Vector Library Docker loads the symbol libraries in SVG files, when those SVG files are put into the \"symbols\" folder in the resource folder :menuselection:`Settings --> Manage Resources --> Open Resource Folder`."
+msgid "The Vector Library Docker loads the symbol libraries in SVG files, when those SVG files are put into the \"symbols\" folder in the resource folder :menuselection:`Settings --> Manage Resources... --> Open Resource Folder`."
msgid "Currently, you cannot make symbol libraries with Krita yet, but you can make them by hand, as well as use Inkscape to make them. Thankfully, there's quite a few svg symbol libraries out there already!"
-msgid "How to get a backtrace in Krita using the dr. MinW debugger."
+msgid "How to get a backtrace in Krita using the dr. MinGW 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"
+msgid "Dr. MinGW Debugger"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:22
msgid "The information on this page applies only to the Windows release of Krita."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:25
msgid "Using the Debug Package"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:27
-msgid "If you have your Krita version installed and you want to get a backtrace, it's best to download a portable version (either the latest release, or the one that someone told you to try, for example Krita Next or Krita Plus package). Alongside downloading the portable version, download the debug symbols package, too. It should be located in the same place you download Krita. You can see which is which by checking the end of the name of the zip file - debug symbols package always ends with `-dbg.zip`."
+msgid "If you have your Krita version installed and you want to get a backtrace, it's best to download a portable version (either the latest release, or the one that someone told you to try, for example Krita Next or Krita Plus package). Alongside downloading the portable version, download the debug symbols package, too. It should be located in the same place you download Krita. You can see which is which by checking the end of the name of the ZIP file - debug symbols package always ends with *-dbg.zip*."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:32
-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 (for example beta versions). Portable zip and debug zip are found next to each other."
+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 (for example beta versions). Portable ZIP and debug ZIP are found next to each other."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:33
msgid "Make sure you’ve downloaded the same version of debug package for the portable package you intend to debug / get a better backtrace."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:34
msgid "Extract the portable Krita."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:35
-msgid "Extract the files from the debug symbols package inside the portable Krita main directory, where the sub-directories `bin`, `lib` and `share` is located, like in the figures below:"
+msgid "Extract the files from the debug symbols package inside the portable Krita main directory, where the sub-directories *bin*, *lib* and *share* is located, like in the figures below:"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:41
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."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:45
msgid "Getting a Backtrace"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:50
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:54
msgid "An example of the crash dialog."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:56
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:58
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:62
msgid "Find the file ``kritacrash.log`` (it might appear as simply ``kritacrash`` depending on your settings.)"
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:63
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:67
msgid "Start of backtrace."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:69
msgid "Check the time and make sure it matches the time of the crash."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:73
msgid "End of backtrace."
msgstr ""
#. +> trunk5
#: ../../reference_manual/dr_minw_debugger.rst:75
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:77
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:78
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."
msgid "A general edge detection filter that encapsulates all other filters. Edge detection filters that were separate before 4.0 have been folded into this one. It is also available for filter layers and filter brushes."
-msgid "From left to right: Original, with Prewitt edge detection applied, with Prewitt edge detection applied and result applied to alpha channel, and finally the original with an edge detection filter layer with the same settings as 3, and the filter layer blending mode set to multiply"
+msgid "From left to right: Original, with Prewitt edge detection applied, with Prewitt edge detection applied and result applied to alpha channel, and finally the original with an edge detection filter layer with the same settings as 3, and the filter layer blending mode set to multiply."
msgid "The edge detection will be used on a grayscale copy of the image, and the output will be onto the alpha channel of the image, meaning it will output lines only."
+msgid "A High Pass filter is a type of edge detection filter. It is usually used to enhance contrasts, much like a sharpen filter, but within a texture editing workflow it is also used to remove local gradients."
+msgid "To use this as a sharpen filter, create a filter layer with this filter, and then set the blending mode to modes like 'soft light', 'overlay', 'hard light', 'linear light'. Different blending modes give different results."
+msgid "**Top left**: Original, **top right**: Gaussian Highpass Result with radius 3, **bottom left**: Gaussian High Pass Result with radius 3 blended over the original with to Linear Light, **bottom right**: Gaussian High Pass result with radius 3 blended over the original with Soft Light."
+msgid "To remove local gradients from a texture, create a clone layer, and apply this filter as a filter mask. Then, put a filter layer with gaussian blur set to the full amount in between the clone layer and the original. Finally, set the clone layer to luminosity or multiply(in this case an extra filter mask needs to be added to reduce the levels so that the multiplication result will not be as strong)."
+msgid "**Left**: Original, **top right**: Gaussian High Pass Result blended with luminosity to remove the local gradients but keep the sharp details. In this specific example the lack of local gradients removes some character, but the gaussian high pass result could also be used to create a heightmap."
msgid "A filter that converts Height maps to Normal maps through the power of edge detection. It is also available for the filter layer or filter brush."
msgid "The radius of the edge detection. Default is 1 and going higher will increase the strength of the normal map. Adjust this if the effect of the resulting normal map is too weak."
msgid "An XYZ swizzle, that allows you to map Red, Green and Blue to different 3d normal vector coordinates. This is necessary mostly for the difference between MikkT-space normal maps (+X, +Y, +Z) and the OpenGL standard normal map (+X, -Y, +Z)."
msgid "Uses the input image as a height-map to output a 3d something, using the phong-lambert shading model. Useful for checking one's height maps during game texturing. Checking the :guilabel:`Normal Map` box will make it use all channels and interpret them as a normal map."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/map.rst:37
msgid "Round Corners"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/map.rst:39
msgid "Adds little corners to the input image."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/map.rst:41
#: ../../reference_manual/filters/map.rst:44
msgid "Normalize"
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/map.rst:46
msgid "This filter takes the input pixels, puts them into a 3d vector, and then normalizes (makes the vector size exactly 1) the values. This is helpful for normal maps and some minor image-editing functions."
msgid "Maps the lightness of the input to the selected gradient. Useful for fancy artistic effects."
msgstr ""
#. +> trunk5
#: ../../reference_manual/filters/map.rst:57
msgid "In 3.x you could only select predefined gradients. In 4.0, you can select gradients and change them on the fly, as well as use the gradient map filter as a filter layer or filter brush."
msgstr ""
+
+#. +> trunk5
+#: ../../reference_manual/filters/map.rst:60
+msgid "Color Modes"
+msgstr ""
+
+#. +> trunk5
+#: ../../reference_manual/filters/map.rst:62
+msgid "**Blend:** smoothly blend colors between stops"
+msgstr ""
+
+#. +> trunk5
+#: ../../reference_manual/filters/map.rst:63
+msgid "**Nearest:** selects color from nearest stops"
+msgstr ""
+
+#. +> trunk5
+#: ../../reference_manual/filters/map.rst:64
+msgid "**Dither:** dithers between stop colors as per `Dithering Threshold Modes`_."
+msgstr ""
+
+#. +> trunk5
+#: ../../reference_manual/filters/map.rst:66
+#: ../../reference_manual/filters/map.rst:69
+msgid "Palettize"
+msgstr ""
+
+#. +> trunk5
+#: ../../reference_manual/filters/map.rst:66
+msgid "Palette"
+msgstr ""
+
+#. +> trunk5
+#: ../../reference_manual/filters/map.rst:71
+msgid "Maps the color of the input to the nearest color in the selected palette. Useful for limiting color in pixel art and for artistic effects."
+msgstr ""
+
+#. +> trunk5
+#: ../../reference_manual/filters/map.rst:73
+msgid "Optional dithering may be applied with the covered value range controlled by the spread value."
+msgstr ""
+
+#. +> trunk5
+#: ../../reference_manual/filters/map.rst:76
+msgid "Colorspace Modes"
+msgstr ""
+
+#. +> trunk5
+#: ../../reference_manual/filters/map.rst:78
+msgid "**Lab:** finds nearest colors in Lab colorspace"
+msgstr ""
+
+#. +> trunk5
+#: ../../reference_manual/filters/map.rst:79
+msgid "**RGB:** finds nearest colors in RGB colorspace"
+msgstr ""
+
+#. +> trunk5
+#: ../../reference_manual/filters/map.rst:82
+msgid "Dithering Threshold Modes"
+msgstr ""
+
+#. +> trunk5
+#: ../../reference_manual/filters/map.rst:84
+msgid "**Pattern:** uses the lightness or alpha value of the selected pattern to threshold the input color between palette colors"
+msgstr ""
+
+#. +> trunk5
+#: ../../reference_manual/filters/map.rst:85
+msgid "**Noise:** uses a randomly generated value per pixel to threshold the input color between palette colors"
+msgstr ""
+
+#. +> trunk5
+#: ../../reference_manual/filters/map.rst:88
+msgid "Dithering Color Modes"
+msgstr ""
+
+#. +> trunk5
+#: ../../reference_manual/filters/map.rst:90
+msgid "**Per-Component Offset:** independently offsets each color channel by the threshold amount, scaled by the offset scale value"
+msgstr ""
+
+#. +> trunk5
+#: ../../reference_manual/filters/map.rst:91
+msgid "**Nearest Colors:** finds the two nearest colors then applies the threshold amount to the relative distances of the two color to find the resulting color"
+msgstr ""
+
+#. +> trunk5
+#: ../../reference_manual/filters/map.rst:94
+msgid "Dithering Alpha Modes"
+msgstr ""
+
+#. +> trunk5
+#: ../../reference_manual/filters/map.rst:96
+msgid "**Clip:** thresholds alpha at the clip position"
+msgstr ""
+
+#. +> trunk5
+#: ../../reference_manual/filters/map.rst:97
+msgid "**Index:** uses the selected palette index as the transparent color"
+msgstr ""
+
+#. +> trunk5
+#: ../../reference_manual/filters/map.rst:98
+msgid "**Dither:** applies dither to the alpha value as per `Dithering Threshold Modes`_"
msgid "Wavelet decompose uses wavelet scales to turn the current layer into a set of layers with each holding a different type of pattern that is visible within the image. This is used in texture and pattern making to remove unwanted noise quickly from a texture."
msgid "When you select it, it will ask for the amount of wavelet scales. More scales, more different layers. Press :guilabel:`OK`, and it will generate a group layer containing the layers with their proper blending modes:"
msgid "Adjust a given layer with middle gray to neutralize it, and merge everything with the :guilabel:`Grain Merge` blending mode to merge it into the end image properly."
# 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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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 "MaxFALL"
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:1
msgid "How to configure Krita for HDR displays."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:10
msgid "HDR"
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:10
msgid "High Dynamic Range"
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:10
msgid "HDR display"
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:15
msgid "HDR Display"
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:21
msgid "Currently only available on Windows."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:23
msgid "Since 4.2 Krita can not just edit high bitdepths images, but also render them on screen in a way that an HDR capable setup can show them as HDR images. HDR images, to put it simply, are images with really bright colors. They do this by having a very large range of colors available, 16 bit and higher, and to understand the upper range of the available colors as brighter than the brightest white most screens can show. HDR screens, in turn, are screens which can show brighter colors than most screens can show, and can thus show the super-bright colors in these HDR images. This allows for images where bright things, like fire, sunsets, magic, look really spectacular! It also shows more subtle shadows and has a better contrast in lower color values, but this requires a sharper eye."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:26
msgid "Configuring HDR"
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:28
msgid "Krita cannot show HDR with any given monitor, you will need an HDR capable setup. HDR capable setups are screens which can show more than 100 nits, preferably a value like 1000 and can show the rec 2020 PQ space. You will need to have the appropriate display cable(otherwise the values are just turned into regular SDR) and a graphics card which supports HDR, as well as suitable drivers. You then also need to configure the system settings for HDR."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:30
-msgid "If you can confirm that the system understands your setup as an HDR setup, you can continue your :ref:`configuration in Krita<hdr_display_settings>`, in :menuselection:`Settings --> Configure Krita --> Display`. There, you need to select the preferred surface, which should be as close to the display format as possible. Then restart Krita."
+msgid "If you can confirm that the system understands your setup as an HDR setup, you can continue your :ref:`configuration in Krita<hdr_display_settings>`, in :menuselection:`Settings --> Configure Krita... --> Display`. There, you need to select the preferred surface, which should be as close to the display format as possible. Then restart Krita."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:33
msgid "Painting in HDR"
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:35
msgid "To create a proper HDR image, you will need to make a canvas using a profile with rec 2020 gamut and a linear TRC. :guilabel:`Rec2020-elle-V4-g10.icc` is the one we ship by default."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:37
msgid "HDR images are standardized to use the Rec2020 gamut, and the PQ TRC. However, a linear TRC is easier to edit images in, so we don't convert to PQ until we're satisfied with our image."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:39
msgid "For painting in this new exciting color space, check the :ref:`scene_linear_painting` page, which covers things like selecting colors, gotchas, which filters work and cool workflows."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:42
msgid "Exporting HDR"
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:44
msgid "Now for saving and loading."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:46
-msgid "The kra file format can save the floating point image just fine, and is thus a good working file format."
+msgid "The KRA file format can save the floating point image just fine, and is thus a good working file format."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:48
-msgid "For sharing with other image editors, :ref:`file_exr` is recommended. For sharing with the web we currently only have :ref:`HDR png export <file_png>`, but there's currently very little support for this standard. In the future we hope to see heif and avif support."
+msgid "For sharing with other image editors, :ref:`file_exr` is recommended. For sharing with the web we currently only have :ref:`HDR PNG export <file_png>`, but there's currently very little support for this standard. In the future we hope to see heif and avif support."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:50
msgid "For exporting HDR animations, we support saving HDR to the new codec for mp4 and mkv: H.265. To use these options..."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:52
-msgid "Get a version of FFmpeg that supports H.256"
+msgid "Get a version of FFmpeg that supports H.256."
msgid "Select for :guilabel:`Render as`, 'MPEG-4 video' or 'Matroska'."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:57
msgid "Press the configure button next to the file format dropdown."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:58
-msgid "Select at the top 'H.265, MPEG-H Part 2 (HEVC)'"
+msgid "Select at the top 'H.265, MPEG-H Part 2 (HEVC)'."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:59
msgid "Select for the :guilabel:`Profile`, 'main10'."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:60
msgid ":guilabel:`HDR Mode` should now enable. Toggle it."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:61
msgid "click :guilabel:`HDR Metadata` to configure the HDR metadata (options described below)."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:62
msgid "finally, when done, click 'render'."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:65
msgid "HDR Metadata"
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:67
msgid "This is in the render animation screen. It configures the SMPTE ST.2086 or Master Display Color Volumes metadata and is required for the HDR video to be transferred properly to the screen by video players and the cable."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:69
msgid "Master Display"
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:70
msgid "The colorspace characteristics of the display on for which your image was made, typically also the display that you used to paint the image with. There are two default values for common display color spaces, and a custom value, which will enable the :guilabel:`Display` options."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:72
msgid "The precise colorspace characteristics for the display for which your image was made. If you do not have custom selected for :guilabel:`Master Display`, these are disabled as we can use predetermined values."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:74
msgid "Red/Green/Blue Primary"
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:75
msgid "The xyY x and xyY y value of the three chromacities of your screen. These define the gamut."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:76
msgid "White Point"
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:77
msgid "The xyY x and xyY y value of the white point of your screen, this defines what is considered 'neutral grey'."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:78
msgid "Min Luminance"
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:79
msgid "The darkest value your screen can show in nits."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:81
msgid "Display"
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:81
msgid "Max Luminance"
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:81
msgid "The brightest value your screen can show in nits."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:83
msgid "MaxCLL"
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:84
msgid "The value of the brightest pixel of your animation in nits."
msgstr ""
#. +> trunk5
#: ../../reference_manual/hdr_display.rst:86
msgid "The average 'brightest value' of the whole animation."
# 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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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 "Autosave on split"
msgstr ""
#. +> trunk5
#: ../../reference_manual/image_split.rst:1
-msgid "The Image Split functionality in Krita"
+msgid "The Image Split functionality in Krita."
msgstr ""
#. +> trunk5
#: ../../reference_manual/image_split.rst:10
msgid "Splitting"
msgstr ""
#. +> trunk5
#: ../../reference_manual/image_split.rst:15
msgid "Image Split"
msgstr ""
#. +> trunk5
#: ../../reference_manual/image_split.rst:17
msgid "Found under :menuselection:`Image --> Image Split`, the Image Split function allows you to evenly split a document up into several sections. This is useful for splitting up spritesheets for example."
msgstr ""
#. +> trunk5
#: ../../reference_manual/image_split.rst:19
msgid "Horizontal Lines"
msgstr ""
#. +> trunk5
#: ../../reference_manual/image_split.rst:20
msgid "The amount of horizontal lines to split at. 4 lines will mean that the image is split into 5 horizontal stripes."
msgstr ""
#. +> trunk5
#: ../../reference_manual/image_split.rst:22
msgid "Vertical Lines"
msgstr ""
#. +> trunk5
#: ../../reference_manual/image_split.rst:22
msgid "The amount of vertical lines to split at. 4 lines will mean that the image is split into 5 vertical stripes."
msgstr ""
#. +> trunk5
#: ../../reference_manual/image_split.rst:24
msgid "Sort Direction"
msgstr ""
#. +> trunk5
#: ../../reference_manual/image_split.rst:28
msgid "Whether to number the files using the following directions:"
msgstr ""
#. +> trunk5
#: ../../reference_manual/image_split.rst:30
msgid "Horizontal"
msgstr ""
#. +> trunk5
#: ../../reference_manual/image_split.rst:31
msgid "Left to right, top to bottom."
msgstr ""
#. +> trunk5
#: ../../reference_manual/image_split.rst:33
msgid "Vertical"
msgstr ""
#. +> trunk5
#: ../../reference_manual/image_split.rst:33
msgid "Top to bottom, left to right."
msgstr ""
#. +> trunk5
#: ../../reference_manual/image_split.rst:35
msgid "Prefix"
msgstr ""
#. +> trunk5
#: ../../reference_manual/image_split.rst:36
msgid "The prefix at which the files should be saved at. By default this is the current document name."
msgstr ""
#. +> trunk5
#: ../../reference_manual/image_split.rst:37
msgid "File Type"
msgstr ""
#. +> trunk5
#: ../../reference_manual/image_split.rst:38
msgid "Which file format to save to."
msgstr ""
#. +> trunk5
#: ../../reference_manual/image_split.rst:40
msgid "This will result in all slices being saved automatically using the above prefix. Otherwise Krita will ask the name for each slice."
# 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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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 "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` 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 "A clone layer is a layer that keeps an up-to-date copy of another layer. You cannot draw or paint on it directly, but it can be used to create effects by applying different types of layers and masks (e.g. filter layers or masks)."
msgid "For example, if you were painting a picture of some magic person and wanted to create a glow around them that was updated as you updated your character, you could:"
msgid "As you keep painting and adding details, erasing on the first layer, Krita will automatically update the clone layer, making your \"glow\" apply to every change you make."
+msgid "You can change the source of one or more Clone Layers in the Layers Docker. To do so, select one or more Clone Layers in the docker (hold :kbd:`Ctrl` or :kbd:`Shift` and left-click the layers). Then, right-click on any selected layer. In the context menu, there is an action named :guilabel:`Set Copy From`. Click it. A dialog will pop up and there is a drop-down menu with all possible layers to be set as the source of all selected Clone Layers. If the current source of them consists of multiple layers, the default activated selection in the drop-down menu will be blank. Otherwise, it would be the common source of selected Clone Layers."
+msgid "If you select one layer in the drop-down menu, a preview of the canvas will be shown. Click :guilabel:`OK` to apply the changes. Click :guilabel:`Cancel` to discard the changes. If you make changes to the image outside the dialog, the changes will be applied and the dialog will be automatically closed."
-msgid "This fills the layer with a predefined pattern or texture that has been loaded into Krita through the Resource Management interface. Patterns can be a simple and interesting way to add texture to your drawing or painting, helping to recreate the look of watercolor paper, linen, canvas, hardboard, stone or an infinite other number of options. For example if you want to take a digital painting and finish it off with the appearance of it being on canvas you can add a Fill Layer with the Canvas texture from the texture pack below and set the opacity very low so the \"threads\" of the pattern are just barley visible. The effect is quite convincing."
+msgid "Fills the layer with a singular color. Since version 4.2, newly created colored fill layers will be assigned to the currently active foreground color."
-msgid "You can create your own and use those as well. For a great set of well designed and useful patterns check out one of our favorite artists and a great friend of Krita, David Revoy's free texture pack (https://www.davidrevoy.com/article156/texture-pack-1)."
+msgid "This fills the layer with a predefined pattern or texture that has been loaded into Krita through the Resource Management interface. Patterns can be a simple and interesting way to add texture to your drawing or painting, helping to recreate the look of watercolor paper, linen, canvas, hardboard, stone or an infinite other number of options. For example if you want to take a digital painting and finish it off with the appearance of it being on canvas you can add a Fill Layer with the Canvas texture from the texture pack below and set the opacity very low so the \"threads\" of the pattern are just barley visible. The effect is quite convincing."
-msgid "The second option is not quite as exciting, but does the job. Fill the layer with a selected color."
+msgid "You can create your own and use those as well. For a great set of well designed and useful patterns check out one of our favorite artists and a great friend of Krita, David Revoy's free texture pack (https://www.davidrevoy.com/article156/texture-pack-1)."
-msgid "A noise generator that isn't Perline Noise (which is what typical 'clouds' generation is), but it looks similar and can actually loop. Uses the OpenSimplex code."
+msgid "This fills the layer with generated OpenSimplex noise. OpenSimplex is different from the more common Perlin noise (often named 'clouds' in other software) and also different from Improved Perlin noise. OpenSimplex has less dimensional artifacts (the subtle \"checker\" texture often found high frequency Perlin noise) and is a ubiquitous open standard. Since OpenSimplex noise is important to texture generation, this fill layer has the option to loop around the canvas edge. You can read more about OpenSimplex `here <https://en.wikipedia.org/wiki/OpenSimplex_noise>`_."
+msgid "There are a few different use cases for simplex noise. One of these is to create interesting looping patterns, achieved by stacking multiple simplex noise fills with different blending modes. It becomes even more expressive when combined with the levels adjustment layers. For texture artists, this can be a useful utility when combined with a gradient map filter layer to provide color diversity to a looping texture. For traditional artists, simplex noise layers can be converted to selection masks to create brush transparency dynamics and masking effects. Experimenting with different combinations can be fun and produce interesting results!"
-msgid "The seed for the random component. You can input any value or text here, and it will always try to use this value to generate the random values with (which then are always the same for a given seed)."
+msgid "The seed for the random component. You can input any value or text here, and it will always try to use this value to generate the random values with (which then are always the same for a given seed). Leaving the value empty will use the randomly-assigned seed value on layer creation."
msgid "A fill-layer is a single-channel layer, meaning it only has transparency. Therefore, you can erase and paint on fill-layers to make them semi-opaque, or for when you want to have a particular color only. Being single channel, fill-layers are also a little bit less memory-consuming than regular 4-channel paint layers."
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 "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 "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 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 "As a native Linux program, Krita allows you to do operations on images without opening the program when using the Terminal. This option was disabled on Windows and OSX, but with 3.3 it is enabled for them!"
-msgid "This line takes the animation in test.kra, and uses the value of --export-filename (file.png), to determine the sequence fileformat('png') and the frame prefix ('file')."
+msgid "This line takes the animation in *test.kra*, and uses the value of --export-filename (*file.png*), to determine the sequence fileformat('png') and the frame prefix ('file')."
msgid "Open krita and automatically open the given template(s). This allows you to, for example, create a shortcut to Krita that opens a given template, so you can get to work immediately!"
msgid "All templates are saved with the .desktop extension. You can find templates in the .local/share/krita/template or in the install folder of Krita."
+msgid "Starts krita with ``filename`` added as a file-layer. Note that you must either open an existing file or create a new file using the ``new-image`` argument."
+msgid "If an instance of Krita is already running and Multiple :ref:`instances <window_settings>` are disabled, then this option can be used alone to add a file-layer to the running krita document."
msgid "Makes a new document from the current image, so you can easily reiterate on a single image. Useful for areas where the template system is too powerful."
msgid "This is a selection of all the difficult to figure out technical information of your computer. This includes things like, which version of Krita you have, which version your operating system is, and most prudently, what kind of OpenGL functionality your computer is able to provide. The latter varies a lot between computers and due that it is one of the most difficult things to debug. Providing such information can help us figure out what is causing a bug."
msgid "Convert a layer to a transparency mask. The image will be converted to grayscale first, and these grayscale values are used to drive the transparency."
msgid "Convert a layer to a filter mask. The image will be converted to grayscale first, and these grayscale values are used to drive the filter effect area."
msgid "Convert a layer to a selection mask. The image will be converted to grayscale first, and these grayscale values are used to drive the selected area."
+msgid "Convert the selected layer in to a file layer. This will open a dialog box, which will ask the user for a location to save the layer as file layer and reference it in place of the original layer. This feature cannot be used if the selected layer is either a clone layer or a file layer."
msgid "Select all opaque (non-transparent) pixels in the current active layer. If there's already a selection, this will add the new selection to the old one, allowing you to select the opaque pixels of multiple layers into one selection. Semi-transparent (or semi-opaque) pixels will be semi-selected."
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 "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 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 "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...` menu item."
-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 "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 Main Toolbar allows you to add items between the :guilabel:`New`, :guilabel:`Open` and :guilabel:`Save` buttons as well as to the right of the :guilabel:`Save` button. The 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 "Here we've added :menuselection:`Select Opaque`, :menuselection:`Local Selection`, :menuselection:`Transparency Mask`, :menuselection:`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."
# 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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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>:4
msgid ""
".. image:: images/icons/Krita_mouse_right.png\n"
" :alt: mouseright"
msgstr ""
#. +> trunk5
#: ../../reference_manual/popup-palette.rst:1
-msgid "The Pop-up Palette in Krita"
+msgid "The Pop-up Palette in Krita."
msgstr ""
#. +> trunk5
#: ../../reference_manual/popup-palette.rst:10
#: ../../reference_manual/popup-palette.rst:14
msgid "Pop-up Palette"
msgstr ""
#. +> trunk5
#: ../../reference_manual/popup-palette.rst:16
msgid "The Pop-up Palette is a feature unique to Krita amongst the digital painting applications. It is designed to increase productivity and save time of the artists by providing quick access to some of the most frequently used tools and features in Krita. The Pop-up palette can be accessed by |mouseright| on the canvas. A circular palette similar to what is shown in the image below will spawn at the position your mouse cursor."
-msgid "As shown in the image above, the pop-up palette has the following tools and quick access shortcuts integrated into it"
+msgid "As shown in the image above, the pop-up palette has the following tools and quick access shortcuts integrated into it."
msgstr ""
#. +> trunk5
#: ../../reference_manual/popup-palette.rst:22
msgid "Foreground color and Background color indicators on the top left of the palette."
msgstr ""
#. +> trunk5
#: ../../reference_manual/popup-palette.rst:23
msgid "A canvas rotation circular slider, which can help the artist quickly rotate the canvas while painting."
msgstr ""
#. +> trunk5
#: ../../reference_manual/popup-palette.rst:24
msgid "A group of brush presets, based on the tag selected by the artist. By default the **My Favorite** tag is selected. By default only first 10 presets from the tag are shown, however you can change the number of brush presets shown by changing the value in the :ref:`Miscellaneous Settings Section <misc_settings>` of the dialog box."
msgstr ""
#. +> trunk5
#: ../../reference_manual/popup-palette.rst:25
msgid "Color Selector with which you can select the hue from the circular ring and lightness and saturation from the triangular area in the middle."
msgstr ""
#. +> trunk5
#: ../../reference_manual/popup-palette.rst:26
msgid "Color history area shows the most recent color swatches that you have used while painting."
msgstr ""
#. +> trunk5
#: ../../reference_manual/popup-palette.rst:27
msgid "The tag list for brush preset will show you the list of both custom and default tags to choose from, selecting a tag from this list will show the corresponding brush presets in the palette."
msgstr ""
#. +> trunk5
#: ../../reference_manual/popup-palette.rst:28
msgid "The common brush options such as size, opacity, angle et cetera will be shown when you click the **>** icon. A dialog box will appear which will have the sliders to adjust the brush options. You can choose which options are shown in this dialog box by clicking on the settings icon."
msgstr ""
#. +> trunk5
#: ../../reference_manual/popup-palette.rst:29
msgid "The zoom slider allows you to quickly zoom the canvas."
msgstr ""
#. +> trunk5
#: ../../reference_manual/popup-palette.rst:30
msgid "The 100% button sets the zoom to the 100% of the image size."
msgstr ""
#. +> trunk5
#: ../../reference_manual/popup-palette.rst:31
msgid "The button with the canvas icon switches to the canvas only mode, where the toolbar and dockers are hidden."
msgstr ""
#. +> trunk5
#: ../../reference_manual/popup-palette.rst:32
msgid "The button with the mirror icon mirrors the canvas to help you spot the errors in the painting."
# 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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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/preferences.rst:1
msgid "Krita's settings and preferences options."
msgstr ""
#. +> trunk5
#: ../../reference_manual/preferences.rst:16
msgid "Preferences"
msgstr ""
#. +> trunk5
#: ../../reference_manual/preferences.rst:18
-msgid "Krita is highly customizable and makes many settings and options available to customize through the Preferences area. These settings are accessed by going to :menuselection:`Settings --> Configure Krita`. On MacOS, the settings are under the topleft menu area, as you would expect of any program under MacOS."
+msgid "Krita is highly customizable and makes many settings and options available to customize through the Preferences area. These settings are accessed by going to :menuselection:`Settings --> Configure Krita...` menu item. On MacOS, the settings are under the topleft menu area, as you would expect of any program under MacOS."
msgstr ""
#. +> trunk5
#: ../../reference_manual/preferences.rst:20
msgid "Krita's preferences are saved in the file ``kritarc``. This file is located in ``%LOCALAPPDATA%\\`` on Windows, ``~/.config`` on Linux, and ``~/Library/Preferences`` on OS X. If you would like to back up your custom settings or synchronize them from one computer to another, you can just copy this file. It even works across platforms!"
msgstr ""
#. +> trunk5
#: ../../reference_manual/preferences.rst:22
msgid "If you have installed Krita through the Windows store, the kritarc file will be in another location:"
msgid "Custom shortcuts are saved in a separate file ``kritashortcutsrc`` which can also be backed up in the same way. This is discussed further in the shortcuts section."
msgid "By default, it will use the \"Anonymous\" profile, which contains nothing. To create a new profile, press the \"+\" button, and write up a name for the author profile."
msgid "Press :guilabel:`Add Contact Info` to add an entry in the box. By default it will set the type to homepage, because that is the one that causes the least spam. Double |mouseleft| homepage to change the contact type. Double |mouseleft| the \"New Contact Info\" text to turn it into a line edit to change the value."
msgid "To use a profile for your current drawing, go to :menuselection:`Settings --> Active Author Profile` and select the name you gave your profile. Then, when pressing :guilabel:`Save` on your current document, you will be able to see your last author profile as the last person who saved it in :menuselection:`File --> Document Information --> Author`."
-msgid "The jpeg and png export both have :guilabel:`Sign with author data` options. Toggling these will store the Nickname and the *first entry in the contact info* into the metadata of png or jpeg."
+msgid "The JPEG and PNG export both have :guilabel:`Sign with author data` options. Toggling these will store the Nickname and the *first entry in the contact info* into the metadata of PNG or JPEG."
msgid "Krita offers extensive functionality for color management, utilising `Little CMS <http://www.littlecms.com/>`_ We describe Color Management in a more overall level here: :ref:`color_managed_workflow`."
msgid "BPC is a sort of \"poor man's\" gamut mapping. It basically adjust contrast of images in a way that darkest tone of source device gets mapped to darkest tone of destination device. If you have an image that is adjusted to be displayed on a monitor, and want to print it on a large format printer, you should realize printer can render black significantly darker that the screen. So BPC can do the adjustment for you. It only makes sense on Relative colorimetric intent. Perceptual and Saturation does have an implicit BPC."
+msgid "By default, palette selection widgets take the current foreground color, compare it to the swatches in it’s active palette and highlight the swatch that is nearest to the current foreground color."
+msgid "When ‘Enforce palette colors’ option is checked, it switches the internal color selector into a mode in which, instead of just highlighting the swatch, the current foreground color is replaced with the color of the nearest swatch."
msgid "There are as many of these as you have screens connected. The user can select an ICC profile which Krita will use independent of the monitor profile set in system preferences. The default is sRGB built-in. On Unix systems, profile stored in $/usr/share/color/icc (system location) or $~/.local/share/color/icc (local location) will be proposed. Profile stored in Krita preference folder, $~/.local/share/krita/profiles will be visible only in Krita."
msgid "Your choice of rendering intents is a way of telling Littlecms how you want colors mapped from one color space to another. There are four options available, all are explained on the :ref:`icc_profiles` manual page."
msgid "These allow you to configure the *default* softproofing options. To configure the actual softproofing for the current image, go to :menuselection:`Image --> Image Properties --> Softproofing` ."
msgid "Krita has had G'Mic integration for a long time, but this is its most stable incarnation. On Windows, the plugin is included in the installer and Krita will find it automatically. On Linux, we are making an appimage available for download."
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` keys 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 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 "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 "The user can set how the subdivision lines of the grid are shown. Options available are Lines, Dashed Lines, Dots. The color also can be set here."
msgid ":program:`Krita`, as a painting program, juggles a lot of data around, like the brushes you use, the colors you picked, but primarily, each pixel in your image. Due to this, how :program:`Krita` organizes where it stores all the data can really speed up :program:`Krita` while painting, just like having an organized artist's workplace can really speed up the painting process in real life."
msgid "These preferences allow you to configure :program:`Krita's` organisation, but all do require you to restart :program:`Krita`, so it can do this organisation properly."
msgid "RAM, or Random Access Memory, is the memory your computer is immediately using. The difference between RAM and the hard drive memory can be compared to the difference between having files on your desk and having files safely stored away in an archiving room: The files on your desk as much easier to access than the ones in your archive, and it takes time to pull new files from the archive. This is the same for your computer and RAM. Files need to be loaded into RAM before the computer can really use them, and storing and removing them from RAM takes time."
msgid "These settings allow you to choose how much of your virtual desk you dedicate to :program:`Krita`. :program:`Krita` will then reserve them on start-up. This does mean that if you change any of the given options, you need to restart :program:`Krita` so it can make this reservation."
msgid "This is the maximum space :program:`Krita` will reserve on your RAM on startup. It's both available in percentages and Bytes, so you can specify precisely. :program:`Krita` will not take up more space than this, making it safe for you to run an internet browser or music on the background."
msgid "A feature for advanced computer users. This allows :program:`Krita` to organize the area it takes up on the virtual working desk before putting its data on there. Like how a painter has a standard spot for their canvas, :program:`Krita` also benefits from giving certain data it uses its place (a memory pool), so that it can find them easily, and it doesn't get lost among the other data (memory fragmentation). It will then also not have to spend time finding a spot for this data."
msgid "Increasing this, of course, means there's more space for this type of data, but like how filling up your working desk with only one big canvas will make it difficult to find room for your paints and brushes, having a large internal pool will result in :program:`Krita` not knowing where to put the other non-specific data."
msgid "On the opposite end, not giving your canvas a spot at all, will result in you spending more time looking for a place where you will put the new layer or that reference you just took out of the storage. This happens for :program:`Krita` as well, making it slower."
msgid "This is recommended to be a size of one layer of your image, e.g. if you usually paint on the image of 3000x3000x8bit-ARGB, the pool should be something like 36 MiB."
msgid ":program:`Krita` also needs to keep all the Undo states on the virtual desk (RAM). Swapping means that parts of the files on the virtual desk get sent to the virtual archive room. This allows :program:`Krita` to dedicate more RAM space to new actions, by sending old Undo states to the archive room once it hits this limit. This will make undoing a little slower, but this can be desirable for the performance of :program:`Krita` overall. This too needs :program:`Krita` to be restarted."
msgid "This determines the limit of the total space :program:`Krita` can take up in the virtual archive room. If :program:`Krita` hits the limit of both the memory limit above, and this Swap File limit, it can't do anything anymore (and will freeze)."
msgid "This determines where the Swap File will be stored on your hard-drive. Location can make a difference, for example, Solid State Drives (SSD) are faster than Hard Disk Drives (HDD). Some people even like to use USB-sticks for the swap file location."
msgid "When rendering animations to frames, Krita multithreads by keeping a few copies of the image, with a maximum determined by the number of cores your processor has. If you have a heavy animation file and lots of cores, the copies can be quite heavy on your machine, so in that case try lowering this value."
msgid "This makes the canvas update less often, which means Krita can spend more time calculating other things. Some people find fewer updates unnerving to watch however, hence this is configurable."
msgid "Vector optimizations are a special way of asking the CPU to do maths, these have names such as SIMD and AVX. These optimizations can make Krita a lot faster when painting, except when you have an AMD CPU under Windows. There seems to be something strange going on there, so just deactivate them then."
msgid "This allows you to toggle the progress reporter, which is a little feedback progress bar that shows up in the status bar when you let Krita do heavy operations, such as heavy filters or big strokes. The red icon next to the bar will allow you to cancel your operation. This is on by default, but as progress reporting itself can take up some time, you can switch it off here."
msgid "This enables performance logging, which is then saved to the ``Log`` folder in your ``working directory``. Your working directory is where the autosave is saved at as well."
msgid "The animation cache is the space taken up by animation frames in the memory of the computer. A cache in this sense is a cache of precalculated images."
msgid "Playing back a video at 25 FPS means that the computer has to precalculate 25 images per second of video. Now, video playing software is able to do this because it really focuses on this one single task. However, Krita as a painting program also allows you to edit the pictures. Because Krita needs to be able to do this, and a dedicated video player doesn't, Krita cannot do the same kind of optimizations as a dedicated video player can."
msgid "Still, an animator does need to be able to see what kind of animation they are making. To do this properly, we need to decide how Krita will regenerate the cache after the animator makes a change. There's fortunately a lot of different options how we can do this. However, the best solution really depends on what kind of computer you have and what kind of animation you are making. Therefore in this tab you can customize the way how and when the cache is generated."
msgid "Animation frame cache will be stored in RAM, completely without any limitations. This is also the way it was handled before 4.1. This is only recommended for computers with a huge amount of RAM and animations that must show full-canvas full resolution 6k at 25 fps. If you do not have a huge amount (say, 64GiB) of RAM, do *not* use this option (and scale down your projects)."
msgid "Please make sure your computer has enough RAM *above* the amount you requested in the :guilabel:`General` tab. Otherwise you might face system freezes."
msgid "Animation frames are stored in the hard disk in the same folder as the swap file. The cache is stored in a compressed way. A little amount of extra RAM is needed."
msgid "Since data transfer speed of the hard drive is slow, you might want to limit the :guilabel:`Cached Frame Size` to be able to play your video at 25 fps. A limit of 2500 px is usually a good choice."
msgid "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, because On-Disk storage is a little slow. Without the limit, there's a good chance that it will not be able to render at full speed. Lower the size to play back faster at the cost of lower resolution."
msgid "We technically only need to use the section of the image that is in view. Region of interest represents that section. When the image is above the configurable limit, render only the currently visible part of it."
msgid "This allows you to set whether the animation is cached for playback in the background (that is, when you're not using the computer). Then, when animation is cached when pressing play, this caching will take less long. However, turning off this automatic caching can save power by having your computer work less."
-msgid "The python plugin manager can be accessed from :menuselection:`Settings --> Configure Krita --> Python Plugin Manager`. It allows you decide which of the Python Plugins are active."
+msgid "The python plugin manager can be accessed from :menuselection:`Settings --> Configure Krita... --> Python Plugin Manager`. It allows you decide which of the Python Plugins are active."
msgid "It will show you a list of python plugins Krita has found, as well as their description. By default, Python Plugins are disabled, because many python scripts are autostarted, so this ensures only the ones you want to run are being run."
-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 "Most of Krita's shortcuts are configured in the menu section :menuselection:`Settings --> Configure Krita... --> 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>`_"
+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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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`."
+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."
+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:`...`."
+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:`...`."
+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."
+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 <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."
+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`."
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 "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 "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 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 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 "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 "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 --> Manage Resources...` menu item."
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 "Paint Op presets store the preview thumbnail, brush-engine, the parameters, the brush tip, and, if possible, the texture. They are saved as .kpp files"
+msgid "Paint Op presets store the preview thumbnail, brush-engine, the parameters, the brush tip, and, if possible, the texture. They are saved as .kpp files."
msgid "You can edit the preview thumbnail in the brush-scratchpad, but you can also open the \\*.kpp file in Krita to get a 200x200 file to edit to your wishes."
-msgid "These are the brush tip or textures used in the brush presets. They can be png files or .abr file from Photoshop or .gbr files from gimp."
+msgid "These are the brush tip or textures used in the brush presets. They can be PNG files or ``.abr`` file from Photoshop or ``.gbr`` files from Gimp."
-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 "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 "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."
-msgid "You can add new patterns via the pattern docker, or the pattern-quick-access menu in the toolbar. At the bottom of the docker, beneath the resource-filter input field, there are the :guilabel:`Import resource` and :guilabel:`Delete resource` buttons. Select the former to add png or jpg files to the pattern list."
+msgid "You can add new patterns via the pattern docker, or the pattern-quick-access menu in the toolbar. At the bottom of the docker, beneath the resource-filter input field, there are the :guilabel:`Import resource` and :guilabel:`Delete resource` buttons. Select the former to add png or JPG files to the pattern list."
msgid "Similarly, removing patterns can be done by pressing the :guilabel::`Delete resource` button. Krita will not delete the actual file then, but rather black list it, and thus not load it."
msgid "Then go into :guilabel:`custom` and first press :guilabel:`Update` to show the pattern in the docker. Check if it's right. Here, you can also choose whether you use this layer only, or the whole image. Since 3.0.2, Krita will take into account the active selection as well when getting the information of the two."
msgid "Then, click either :guilabel:`Use as Pattern` to use it as a temporary pattern, or :guilabel:`Add to predefined patterns` to save it into your pattern resources!"
# 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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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 "Output to color, not grayscale."
+msgid "Activate the current channel"
msgstr ""
#. +> trunk5
#: ../../reference_manual/separate_image.rst:1
-msgid "The channel separation dialog in Krita"
+msgid "The channel separation dialog in Krita."
msgstr ""
#. +> trunk5
#: ../../reference_manual/separate_image.rst:10
#: ../../reference_manual/separate_image.rst:15
msgid "Separate Image"
msgstr ""
#. +> trunk5
#: ../../reference_manual/separate_image.rst:10
msgid "Channel Separation"
msgstr ""
#. +> trunk5
#: ../../reference_manual/separate_image.rst:17
msgid "The separate image dialog allows you to separate the channels of the image into layers. This is useful in game texturing workflows, as well as more advanced CMYK workflows. When confirming, :guilabel:`Separate Image` creates a series of layers for each channel. So for RGB, it will create Red, Green and Blue layers, each representing the pixels of that channel, and for CMYK, Cyan, Magenta, Yellow and Key layers."
msgstr ""
#. +> trunk5
#: ../../reference_manual/separate_image.rst:20
msgid "Which part of the image should be separated."
msgstr ""
#. +> trunk5
#: ../../reference_manual/separate_image.rst:22
msgid "Current Layer"
msgstr ""
#. +> trunk5
#: ../../reference_manual/separate_image.rst:23
msgid "The active layer."
msgstr ""
#. +> trunk5
#: ../../reference_manual/separate_image.rst:25
msgid "Source"
msgstr ""
#. +> trunk5
#: ../../reference_manual/separate_image.rst:25
msgid "Flatten all layers before separation"
msgstr ""
#. +> trunk5
#: ../../reference_manual/separate_image.rst:25
msgid "The total image."
msgstr ""
#. +> trunk5
#: ../../reference_manual/separate_image.rst:28
msgid "What to do with the alpha channel. All Krita images have an alpha channel, which is the transparency. How should it be handled when separating?"
msgstr ""
#. +> trunk5
#: ../../reference_manual/separate_image.rst:30
msgid "Copy Alpha Channel to Each separate channel as an alpha channel."
msgstr ""
#. +> trunk5
#: ../../reference_manual/separate_image.rst:31
msgid "This adds the transparency of the original source to all the separation layers."
msgstr ""
#. +> trunk5
#: ../../reference_manual/separate_image.rst:32
msgid "Discard Alpha Channel"
msgstr ""
#. +> trunk5
#: ../../reference_manual/separate_image.rst:33
msgid "Just get rid of the alpha altogether."
msgstr ""
#. +> trunk5
#: ../../reference_manual/separate_image.rst:35
msgid "Alpha Options"
msgstr ""
#. +> trunk5
#: ../../reference_manual/separate_image.rst:35
msgid "Create separate separation from alpha channel"
msgstr ""
#. +> trunk5
#: ../../reference_manual/separate_image.rst:35
msgid "Create a separate layer with the alpha channel as a grayscale layer."
msgstr ""
#. +> trunk5
#: ../../reference_manual/separate_image.rst:37
msgid "Downscale to 8bit before separating."
msgstr ""
#. +> trunk5
#: ../../reference_manual/separate_image.rst:38
msgid "Convert the image to 8bit before doing the separation."
msgstr ""
#. +> trunk5
+#: ../../reference_manual/separate_image.rst:39
+msgid "Output to color, not grayscale."
+msgstr ""
+
+#. +> trunk5
#: ../../reference_manual/separate_image.rst:40
msgid "This results in the Red separation using black to red instead of black to white. This can make it easier to recombine using certain methods."
msgstr ""
+
+#. +> trunk5
+#: ../../reference_manual/separate_image.rst:42
+msgid "If the separated layers are in color, activate only the channel that was the origin of this separation layer."
msgid "There are three different kinds of logs that Krita can produce. Depending on the issue, you might be asked for a specific one or for all of them. This page will tell you how to gather the necessary information to give to Krita developers or user supporters."
msgid ":ref:`Krita Usage Log <krita_usage_log>` -- this log contains your last 10 Krita sessions (one session means opening Krita). It shows times when you opened it, basic information about your system and Krita, and all files you created, opened and saved, including all auto-saves."
msgid ":ref:`System information <getting_system_information>` -- this is not exactly a log, but a file that contains detailed system information related to Krita."
msgid ":ref:`Crash log/backtrace <getting_backtrace>` -- this log is created when Krita closes incorrectly because of an internal issue. This log is often necessary to get the issue fixed if developers cannot reproduce issue (repeat steps to get the crash)."
msgid ":ref:`Krita console output/Log Viewer output/DebugView output <krita_console_debugview>` -- this log contains anything random that Krita felt the need to report. It often contains some useful additional information that can help solving the issue."
msgid "The easiest way to get Krita Usage Log is through Krita's GUI. Go to :menuselection:`Help --> Show Krita Log for bug reports`. A new dialog will open, showing the content of the log."
msgid "In versions 4.2.0-4.2.9, Krita Usage Log is accessible through :menuselection:`Help --> Show system information for bug reports`. Note that for Krita versions 4.1.7 and below, no usage log is available and the menu entry only contains system information."
msgid "Sometimes however it is not possible to use Krita's GUI, for example when it doesn't even open. Since logs are regular text files, you can get them from your file system by yourself."
msgid "The easiest way to get system information related to Krita is through Krita's GUI. Go to :menuselection:`Help --> Show system information for bug reports`. A new dialog will open, showing the content."
-msgid "Before version 4.2.9, this file is not created. To find the system information, you need to look for the file mentioned in :ref:`Krita Usage Log <krita_usage_log>`"
msgid "From the short backtrace, it's recommended to cut out all threads that are identical to some others or don't seem to hold any additional information."
msgid "If you feel like you know which part of the backtrace is the most important (it's usually the longest thread), then cut it out and put this fragment in the bug report in a comment. Both backtraces still will be needed: attach them to the bug report as well."
msgid "From the backtrace it's recommended to cut out all threads that are identical to some others or don't seem to hold any additional information to put into the comment (so it's easily accessible for the developer)."
msgid "If you feel like you know which part of the backtrace is the most important (it's usually the longest thread), then cut it out and put this fragment in the bug report in a comment. The full backtrace still will be needed: attach it to the bug report as well."
msgid "Most of Krita's text output can be gathered using :guilabel:`Log Viewer`. The only exception are messages from when Krita is starting up, so there is no GUI yet, or when it closes or crashes so no user interaction is possible after the event."
msgid "Using the console is the most reliable way to get Krita's text output. This way is similar on Mac and Linux. Unfortunately, it's not possible on Windows. To check Windows' equivalent, see :ref:`DebugView guide <using_debug_view>`."
msgid "`Download DebugView <https://docs.microsoft.com/en-us/sysinternals/downloads/debugview>`_ if you haven't already. Click on the blue bold :guilabel:`Download DebugView` text with underline, downloading should start immediately."
msgid "The file you download is a .zip archive. Windows 10 has a zip archive opener already included. Just extract all of the files somewhere. You can learn more about extracing on `Windows extracting manual page <https://support.microsoft.com/en-us/help/4028088/windows-zip-and-unzip-files>`_."
msgid "There is a file inside the archive that is called :file:`DbgView.exe` (which you can see as :file:`DbgView`, depending on your system settings). Double-click on it."
# 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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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"
+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 the :kbd:`R +` |mouseleft| shortcut to select layers at the cursor."
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:18
msgid "At the top, of the dialog there is a dropdown, here you can choose between..."
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:20
msgid "Split Into Layers"
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:21
msgid "The image's colors is split into paint layers. Fantastic for artwork that works more with flats, such as the cel-shaded look."
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:25
msgid "Split Into Local Selection Masks"
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:25
msgid "The image's colors are outlined as a selection, and a :ref:`selection_masks` is made. This is useful for artwork that has a more painterly look, with the selection masks making it easy to select several areas at once. Because selection masks are not paint layers, several of the options below are unavailable."
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:27
msgid "The other options are:"
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:29
msgid "Put all new layers in a group layer"
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:30
msgid "Put all the result layers into a new group."
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:31
msgid "Put every layer in its own, separate group layer"
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:32
msgid "Put each layer into its own group."
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:33
msgid "Alpha-lock every new layer"
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:34
msgid "Enable the alpha-lock for each layer so it is easier to color."
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:35
msgid "Hide the original layer"
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:36
msgid "Turns off the visibility on the original layer so you won't get confused."
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:37
msgid "Sort layers by amount of non-transparent pixels"
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:38
msgid "This ensures that the layers with large color swathes will end up at the top."
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:39
msgid "Disregard opacity"
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:40
msgid "Whether to take into account transparency of a color."
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:41
msgid "Fuzziness"
msgstr ""
#. +> trunk5
#: ../../reference_manual/split_layer.rst:42
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:44
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 feature is technically already in 3.1, but disabled by default because we had not optimized the filling algorithm for production use yet. To enable it, find your krita configuration file, open it in notepad, and add \"disableColorizeMaskFeature=false\" to the top. Then restart Krita. Its official incarnation is in 4.0."
msgid "This image has the line art for the lady separated from the background, and what's more, the background is made up of two layers: one main and one for the details."
msgid "First, select the colorize mask editing tool while having the line art layer selected. |mouseleft| the canvas will add a colorize mask to the layer. You can also |mouseright| the line art layer, and then :menuselection:`Add --> Colorize Mask`. The line art will suddenly become really weird, this is the prefiltering which are filters through which we put the line art to make the algorithm easier to use. The tool options overview below shows which options control that."
msgid "Now, you make strokes with brush colors, press :guilabel:`Update` in the tool options, or tick the last icon of the colorize mask properties. In the layer docker, you will be able to see a little progress bar appear on the colorize mask indicating how long it takes. The bigger your file, the longer it will take."
msgid "We want to have the blue transparent. In the tool options of the colorize editing tool you will see a small palette. These are the colors already used. You can remove colors here, or mark a single color as standing for transparent, by selecting it and pressing \"transparent\". Updating the mask will still show the blue stroke, but the result will be transparent:"
msgid "Because the colorize mask algorithm is slow, and we only need a part of our layer to be filled to fill the whole ghost lady figure, we can make use of :guilabel:`Limit to layer bounds`. This will limit Colorize Mask to use the combined size of the line art and the coloring key strokes. Therefore, make sure that the colorizing keystrokes only take up as much as they really need."
msgid "Now, the colorize mask, being a mask, can also be added to a group of line art layers. It will then use the composition of the whole group as the line art. This is perfect for our background which has two separate line art layers. It also means that the colorize mask will be disabled when added to a group with pass-through enabled, because those have no final composition. You can recognize a disabled colorize mask because its name is stricken through."
msgid "To add a colorize mask to a group, select the group and |mouseleft| the canvas with the Colorize Mask editing tool, or |mouseright| the layer to :menuselection:`Add --> Colorize Mask`."
msgid "Now, we add strokes to the background quickly. We do not need to use the :menuselection:`Limit to Layer Bounds` because the background covers the whole image."
msgid "For the record, you can use other brushes and tools also work on the colorize mask as long as they can draw. The Colorize Mask Editing tool is just the most convenient because you can get to the algorithm options."
msgid "Now we are done, |mouseright| the colorize mask and :menuselection:`Convert --> to Paint Layer`. Then, :menuselection:`Layer --> Split --> Split Layer`. This will give separate color islands that you can easily edit:"
msgid "This way we can very quickly paint the image. Due to the colorize mask going from the first image to the following took only 30 minutes, and would've taken quite a bit longer."
-msgid "The colorize masks are saved to the .kra file, so as long as you don't save and open to a different file format, nor convert the colorize mask to a paintlayer, you can keep working adjust the results."
+msgid "The colorize masks are saved to the ``.kra`` file, so as long as you don't save and open to a different file format, nor convert the colorize mask to a paintlayer, you can keep working adjust the results."
msgid "Put the mask into edit mode. In edit mode, it will also show the 'prefiltering' on the line art, which is for example a blur filter for gap closing."
msgid "Show the output of the colorize mask. If :guilabel:`Edit key strokes` is active, this will be shown semi-transparently, so it will be easy to recognize the difference between the strokes and the output."
msgid "On the **Left**: :guilabel:`Show Output` is on, :guilabel:`Edit Key Strokes` is off. In the **Middle**: :guilabel:`Show Output` and :guilabel:`Edit Key Strokes` are on. On the **Right**: :guilabel:`Show Output` is off and :guilabel:`Edit Key Strokes` is on."
msgid "Limit the colorize mask to the combined layer bounds of the strokes and the line art it is filling. This can speed up the use of the mask on complicated compositions, such as comic pages."
msgid "Activate this for line art with large solid areas, for example shadows on an object. For the best use, set the value to the thinnest lines on the image. In the image below, note how edge detection affects the big black areas:"
msgid "From left to right: an example with big black shadows on an object but no edge detection, the same example without the edit key strokes enabled. Then the same example with edge detection enabled and set to 2px, and that same example without edit key strokes enabled."
msgid "While the algorithm is pretty good against gaps in contours, this will improve the gap recognition. The higher this value is, the bigger the gaps it will try to close, but a too high value can lead to other errors. Note how the prefiltered line art (that's the blurry haze) affects the color patches."
msgid "On the **Left**: :guilabel:`Gap close hint` is 0px. In the **Middle**: :guilabel:`Gap close hint` is 15px (the lines are 10px). On the **Right**: :guilabel:`Gap close hint` is 275px."
msgid "This will attempt to handle messy strokes that overlap the line art where they shouldn't. At 0 no clean up is done, at 100% the clean-up is most aggressive."
msgid "This palette keeps track of the colors used by the strokes. This is useful so you can switch back to colors easily. You can increase the swatch size by hovering over it with the mouse, and doing :kbd:`Ctrl +` |mousescroll|."
msgid "This button is under the keystrokes palette, you can mark the selected color to be interpreted a 'transparent' with this. In the clean-up screenshot above, cyan had been marked as transparent."
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 "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 "This tool, represented by an ellipse with a dashed border, allows you to make :ref:`selections_basics` of a elliptical area. Simply |mouseleft| and drag around the section you wish to select."
+msgid "Most of the behavior of the Elliptical Selection Tool is common to all other selection tools, please make sure to read :ref:`selections_basics` to learn more about this tool."
-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 "Hovering your cursor over the dashed line of the selection, or marching ants as it is commonly called, turns the cursor into the move tool icon, which you |mouseleft| and drag to move the selection."
-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 "Shows you the current width while you are creating the selection. You can manually type the value and use the 'Lock Width' for your next selection to have the selected value."
+msgid "Shows you the current height while you are creating the selection. You can manually type the value and use the 'Lock Height' for your next selection to have the selected value."
+msgid "Shows the ratio between height and width of the selection. Similar to Height, and Width, you can manually type the value and use the 'Lock Ratio' for your next selection to have the selected value."
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 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 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 "The hotkey can be edited in :menuselection:`Settings --> Configure Krita... --> 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."
msgid "The Gradient tool is found in the Tools Panel. Left-Click dragging this tool over the active portion of the canvas will draw out the current gradient. If there is an active selection then, similar to the :ref:`fill_tool`, the paint action will be confined to the selection's borders."
+msgid "This will draw the gradient spiral from a center, defined by where you start the stroke, but direction is flipped perpendicular to the direction of stroke."
+msgid "This tool, represented by a magnet over a selection border, allows you to make freeform :ref:`selections_basics`, but unlike the :ref:`polygonal_selection_tool` or the :ref:`outline_selection_tool`, it will try to magnetically snap to sharp contrasts in your image, simplifying the creation of selection drastically."
+msgid "The first is to use |mouseleft| and place points or nodes of the magnetic selection. To finalize your selection area you can do either |mouseleft| on the first created point to complete the loop and click on it again to create a selection, or press :kbd:`Enter` to end the magnetic selection."
+msgid "You can edit previous points by |mouseleft| dragging them. You can remove points by double |mouseleft| the point, or dragging it out of the canvas area. After a path is closed, you can add points by clicking on nearby empty space. Points can be undone with :kbd:`Shift + Z`. A halfway done magnetic selection can be canceled with :kbd:`Esc`."
+msgid "Most of the behavior of the Magnetic Selection Tool is common to all other selection tools, please make sure to read :ref:`selections_basics` to learn more about this tool."
+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.* :kbd:`Alt +` |mouseleft| sets the subsequent selection to 'subtract'."
+msgid "Hovering your cursor over the dashed line of the selection, or marching ants as it is commonly called, turns the cursor into the move tool icon, which you |mouseleft| and drag to move the selection."
+msgid "You can switch the behavior of the :kbd:`Alt` key to use :kbd:`Ctrl` instead by toggling the switch in Tool Settings in the :ref:`general_settings`."
+msgid "This tool is not bound to any Hotkey, if you want to define one, go to :menuselection:`Settings --> Configure Krita --> Keyboard Shortcuts` and search for 'Magnetic Selection Tool', there you can select the shortcut you want. Check :ref:`shortcut_settings` for more info."
+msgid "Determine the radius of the edge detection kernel. This determines how agressively the tool will interpret contrasts. Low values mean only the sharpest of contrast will be a seen as an edge. High values will pick up on subtle contrasts. The range of which is from 2.5 to 100."
+msgid "The area in which the tool will search for a sharp contrast within an image. More pixels means less precision is needed when placing the points, but this will require Krita to do more work, and thus slows down the tool."
+msgid "When using |mouseleft| :kbd:`+ drag` to place points automatically, this value determines the average gap between 2 anchors. Low values give high precision by placing many nodes, but this is also harder to edit afterwards. The pixels are in screen dimensions and not image dimensions, meaning it is affect by zoom."
# 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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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 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 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"
+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 "Most of the behavior of the Outline Selection Tool is common to all other selection tools, please make sure to read :ref:`selections_basics` to learn more about this tool."
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 "Holding :kbd:`Ctrl` key while drawing the selection temporarily makes this tool to behave like polygon selection tool and you can then draw straight line selections by just clicking on canvas."
+msgid "Hovering your cursor over the dashed line of the selection, or marching ants as it is commonly called, turns the cursor into the move tool icon, which you |mouseleft| and drag to move the selection."
+msgid "You can switch the behavior of the :kbd:`Alt` key to use :kbd:`Ctrl` instead by toggling the switch in Tool Settings in the :ref:`general_settings`"
+msgid "This tool is not bound to any Hotkey, if you want to define one, go to :menuselection:`Settings --> Configure Krita --> Keyboard Shortcuts` and search for 'Outline Selection Tool', there you can select the shortcut you want. Check :ref:`shortcut_settings` for more info."
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| :kbd:`+ drag` over the canvas."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/pan.rst:25
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`."
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 "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`."
-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 "This tool, represented by a polygon with a dashed border, allows you to make :ref:`selections_basics` in a polygonal shape. To make a polygonal selection |mouseleft| and place points or nodes of the polygon. To finalize your selection area you can do either |mouseleft| on the first created point, or double |mouseleft| click to end the polygon."
+msgid "Most of the behavior of the Polygonal Selection Tool is common to all other selection tools, please make sure to read :ref:`selections_basics` to learn more about this tool."
-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.* :kbd:`Alt` + |mouseleft| sets the subsequent selection to 'subtract'."
+msgid "Hovering your cursor over the dashed line of the selection, or marching ants as it is commonly called, turns the cursor into the move tool icon, which you |mouseleft| and drag to move the selection."
+msgid "You can switch the behavior of the :kbd:`Alt` key to use :kbd:`Ctrl` instead by toggling the switch in Tool Settings in the :ref:`general_settings`."
+msgid "This tool is not bound to any Hotkey, if you want to define one, go to :menuselection:`Settings --> Configure Krita --> Keyboard Shortcuts` and search for 'Polygonal Selection Tool', there you can select the shortcut you want. Check :ref:`shortcut_settings` 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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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
+#: ../../reference_manual/tools/rectangle.rst:11
msgid "Tools"
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:10
+#: ../../reference_manual/tools/rectangle.rst:11
msgid "Rectangle"
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:15
+#: ../../reference_manual/tools/rectangle.rst:16
msgid "Rectangle Tool"
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:17
+#: ../../reference_manual/tools/rectangle.rst:18
msgid "|toolrectangle|"
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:19
+#: ../../reference_manual/tools/rectangle.rst:20
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
+#: ../../reference_manual/tools/rectangle.rst:23
msgid "Hotkeys and Sticky-keys"
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:24
+#: ../../reference_manual/tools/rectangle.rst:25
msgid "There's no default hotkey for switching to rectangle."
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:26
+#: ../../reference_manual/tools/rectangle.rst:27
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
+#: ../../reference_manual/tools/rectangle.rst:29
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
+#: ../../reference_manual/tools/rectangle.rst:33
msgid "Tool Options"
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:35
+#: ../../reference_manual/tools/rectangle.rst:36
msgid "Fill"
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:37
+#: ../../reference_manual/tools/rectangle.rst:38
msgid "Not filled"
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:38
+#: ../../reference_manual/tools/rectangle.rst:39
msgid "The rectangle will be transparent from the inside."
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:39
+#: ../../reference_manual/tools/rectangle.rst:40
msgid "Foreground color"
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:40
+#: ../../reference_manual/tools/rectangle.rst:41
msgid "The rectangle will use the foreground color as fill."
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:41
+#: ../../reference_manual/tools/rectangle.rst:42
msgid "Background color"
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:42
+#: ../../reference_manual/tools/rectangle.rst:43
msgid "The rectangle will use the background color as fill."
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:44
+#: ../../reference_manual/tools/rectangle.rst:45
msgid "Pattern"
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:44
+#: ../../reference_manual/tools/rectangle.rst:45
msgid "The rectangle will use the active pattern as fill."
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:47
+#: ../../reference_manual/tools/rectangle.rst:48
msgid "Outline"
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:49
+#: ../../reference_manual/tools/rectangle.rst:50
msgid "No Outline"
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:50
+#: ../../reference_manual/tools/rectangle.rst:51
msgid "The Rectangle will render without outline."
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:52
+#: ../../reference_manual/tools/rectangle.rst:53
msgid "Brush"
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:52
+#: ../../reference_manual/tools/rectangle.rst:53
msgid "The Rectangle will use the current selected brush to outline."
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:55
+#: ../../reference_manual/tools/rectangle.rst:56
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
+#: ../../reference_manual/tools/rectangle.rst:58
msgid "Anti-aliasing"
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:58
+#: ../../reference_manual/tools/rectangle.rst:59
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
+#: ../../reference_manual/tools/rectangle.rst:60
msgid "Width"
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:60
+#: ../../reference_manual/tools/rectangle.rst:61
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
+#: ../../reference_manual/tools/rectangle.rst:62
msgid "Height"
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:62
+#: ../../reference_manual/tools/rectangle.rst:63
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
+#: ../../reference_manual/tools/rectangle.rst:67
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
+#: ../../reference_manual/tools/rectangle.rst:69
msgid "Round X"
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:70
+#: ../../reference_manual/tools/rectangle.rst:71
msgid "The horizontal radius of the rectangle corners."
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:72
+#: ../../reference_manual/tools/rectangle.rst:73
msgid "Round Y"
msgstr ""
#. +> trunk5
-#: ../../reference_manual/tools/rectangle.rst:74
+#: ../../reference_manual/tools/rectangle.rst:75
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 "This tool, represented by a rectangle with a dashed border, allows you to make :ref:`selections_basics` in a rectangular shape. To create a rectangular selection simply |mouseleft| and drag on the area of the canvas that you wish to select."
+msgid "Most of the behavior of the Rectangular Selection Tool is common to all other selection tools, please make sure to read :ref:`selections_basics` to learn more about this tool."
-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 "Hovering your cursor over the dashed line of the selection, or marching ants as it is commonly called, turns the cursor into the move tool icon, which you |mouseleft| and drag to move the selection."
-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 "Shows you the current width while you are creating the selection. You can manually type the value and use the 'Lock Width' for your next selection to have the selected value."
+msgid "Shows you the current height while you are creating the selection. You can manually type the value and use the 'Lock Height' for your next selection to have the selected value."
+msgid "Shows the ratio between height and width of the selection. Similar to Height, and Width, you can manually type the value and use the 'Lock Ratio' for your next selection to have the selected value."
+msgid "When linked the aspect ratio between the roundness of X and Y coordinates will be locked. To disconnect the chain just click in the links and it will separate in two parts."
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 the :kbd:`Del` key. You can select multiple reference images with the :kbd:`Shift` key and perform all of these actions."
+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. This option is only available when reference images are loaded from a local path."
+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 "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 "Most of the behavior of the Similar Color Selection Tool is common to all other selection tools, please make sure to read :ref:`selections_basics` to learn more about this tool."
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 "Hovering your cursor over the dashed line of the selection, or marching ants as it is commonly called, turns the cursor into the move tool icon, which you |mouseleft| and drag to move the selection."
+msgid "You can switch the behavior of the :kbd:`Alt` key to use :kbd:`Ctrl` instead by toggling the switch in Tool Settings in the :ref:`general_settings`"
+msgid "This tool is not bound to any Hotkey, if you want to define one, go to :menuselection:`Settings --> Configure Krita --> Keyboard Shortcuts` and search for 'Similar Color Selection Tool', there you can select the shortcut you want. Check :ref:`shortcut_settings` for more info."
+msgid "This controls the range of the color hue used to create the selection. A lower number will select colors closer to the color that you chose in the first place. And a higher number will expand the hue range and select colors even if they are not so similar to the original color."
# 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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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)."
+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 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."
+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."
+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."
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."
+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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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 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 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 the :kbd:`Ctrl` key before doing the motion."
-msgid "Liquify used to turn an apple into a pear"
+msgid "Liquify used to turn an apple into a pear."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:133
msgid "In the options for each brush there are:"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:135
msgid "Mode"
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/transform.rst:136
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 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| :kbd:`+ drag` on the canvas will zoom in or out fluently."
msgstr ""
#. +> trunk5
#: ../../reference_manual/tools/zoom.rst:27
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| :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| :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 "Simón Sanchez' \"Learn to Create Pixel Art from Zero\" course on Udemy"
msgstr ""
#. +> trunk5
-#: ../../resources_page.rst:104
+#: ../../resources_page.rst:116
msgid "User-made Python Plugins"
msgstr ""
#. +> trunk5
-#: ../../resources_page.rst:105
+#: ../../resources_page.rst:117
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."
msgstr ""
#. +> trunk5
+#: ../../resources_page.rst:183
+msgid "We have curated a list of community created resources for Krita. These resources will be hosted on external website, which is not under the control of Krita or KDE. Please report any error or corrections in the content to the Krita developers."
-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 "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 distinct images 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 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 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."
+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 brushes 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 <https://www.davidrevoy.com/>`_ in an hours time."
msgstr ""
#. +> trunk5
#: ../../tutorials/common_workflows.rst:32
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."
+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`"
+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 the :kbd:`Ctrl + L` shortcut 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 the :kbd:`Ctrl + M` shortcut."
+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 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 <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."
+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 --> Colors --> Color to Alpha...` menu item. 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 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."
+#: ../../tutorials/common_workflows.rst:114
+msgid "Colorize Mask"
msgstr ""
#. +> trunk5
-#: ../../tutorials/common_workflows.rst:126
-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."
+#: ../../tutorials/common_workflows.rst:116
+msgid "The third method is to take advantage of the built-in :ref:`colorize_mask`. This is a powerful tool that can dramatically improve your workflow and cut you down on your production time. To begin coloring with the Colorize Mask, select your line art layer and click the :guilabel:`Colorize Mask Editing Tool` icon in the toolbar."
msgstr ""
#. +> trunk5
-#: ../../tutorials/common_workflows.rst:128
-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."
+#: ../../tutorials/common_workflows.rst:122
+msgid "With the Colorize Mask Editing Tool enabled, click on the canvas—this will add a Colorize Mask layer to your document and make your lineart look a little blurry. You can now lay down solid brush strokes to indicate which areas should be colored in what colors:"
msgstr ""
#. +> trunk5
-#: ../../tutorials/common_workflows.rst:130
-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."
+#: ../../tutorials/common_workflows.rst:127
+msgid "Whenever you press the :guilabel:`Update` button in the Tool Options, you will see which colors will fill which areas. You can continue to edit your brush strokes until you are happy with the result. To get a clean look of your painting, disable the \"Edit key strokes\" checkbox:"
msgstr ""
#. +> trunk5
-#: ../../tutorials/common_workflows.rst:133
-msgid "GMIC Colorize [comics]"
+#: ../../tutorials/common_workflows.rst:132
+msgid "Once you are done, you can convert the Colorize Mask layer into a paint layer in the Layers docker. Have a look at the :ref:`colorize_mask` manual to learn more about this tool."
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"
+msgid "Changing Line Art Color"
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."
+msgid "To change the color of your line art, you can use the Alpha Lock feature. In the layer docker, click on the rightmost icon of your line art layer. It's the icon that looks like a little checker board:"
msgstr ""
#. +> trunk5
-#: ../../tutorials/common_workflows.rst:142
-msgid "The colors spots are marked in red in the image"
+#: ../../tutorials/common_workflows.rst:143
+msgid "When Alpha Lock is enabled, you can only change the *color* of the pixels, not their opacity—meaning that everything you paint will only change the colors of your existing lines, not add new lines."
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."
+#: ../../tutorials/common_workflows.rst:145
+msgid "If you want to change the color of your line art to one solid color, you can now use the bucket fill tool and it will only apply to your existing lines. Or if you want to apply several different colors to specific areas of your line art, you can quickly paint over your line art with a broad brush:"
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 <https://timotheegiet.com/blog/comics/gmic-colorize-comics-working-in-krita.html>`_."
-msgstr ""
-
-#. +> trunk5
-#: ../../tutorials/common_workflows.rst:153
+#: ../../tutorials/common_workflows.rst:152
msgid "Painting"
msgstr ""
#. +> trunk5
-#: ../../tutorials/common_workflows.rst:156
+#: ../../tutorials/common_workflows.rst:155
msgid "Starting from chaos"
msgstr ""
#. +> trunk5
-#: ../../tutorials/common_workflows.rst:158
+#: ../../tutorials/common_workflows.rst:157
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
+#: ../../tutorials/common_workflows.rst:159
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
+#: ../../tutorials/common_workflows.rst:164
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
+#: ../../tutorials/common_workflows.rst:167
msgid "Starting from a value based underground"
msgstr ""
#. +> trunk5
-#: ../../tutorials/common_workflows.rst:170
+#: ../../tutorials/common_workflows.rst:169
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
+#: ../../tutorials/common_workflows.rst:171
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
+#: ../../tutorials/common_workflows.rst:173
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
+#: ../../tutorials/common_workflows.rst:176
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."
+#: ../../tutorials/common_workflows.rst:178
+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 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."
+#: ../../tutorials/common_workflows.rst:180
+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 got to :menuselection:`View --> Wrap Around Mode`. 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
+#: ../../tutorials/common_workflows.rst:183
msgid "Creating Pixel Art"
msgstr ""
#. +> trunk5
-#: ../../tutorials/common_workflows.rst:186
+#: ../../tutorials/common_workflows.rst:185
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
+#: ../../tutorials/common_workflows.rst:190
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
+#: ../../tutorials/common_workflows.rst:195
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
+#: ../../tutorials/common_workflows.rst:200
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
+#: ../../tutorials/common_workflows.rst:202
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
+#: ../../tutorials/common_workflows.rst:204
msgid "You can add different groups for different colors and add different dithering patterns for each group."
msgstr ""
#. +> trunk5
-#: ../../tutorials/common_workflows.rst:207
+#: ../../tutorials/common_workflows.rst:206
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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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"
+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`"
+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 "Select the line art layer and apply the :guilabel:`Filter: Color to Alpha` dialog under :menuselection:`Filters --> Colors --> Color to Alpha...` menu item. 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."
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 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 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"
+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!"
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"
+" :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 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"
+" :alt: Type of strokes."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:99
-msgid "Left: No texture, Center: Textured, Right: Predefined Brush tip"
+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"
+" :alt: Pressure curve for Ink Gpen preset brush."
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"
+" :alt: Convex inking brush."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:114
-msgid "conversely, here's a convex brush. The strokes are much rounder"
+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"
+" :alt: Ink fill circle preset brush."
msgstr ""
#. +> trunk5
#: ../../tutorials/inking.rst:119
-msgid "Fill_circle combines both into an s-curve, this allows for very dynamic brush strokes"
+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"
+" :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"
+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 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."
+msgid "Or, |mouseright| on 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 "Basically, they’re what is officially called an ‘image hose’, and they’re quite fun. They are basically a brush-tip with multiple image files."
+msgid "Basically, they're what are officially called ‘image hoses’, and they're quite fun. They are basically brush-tips with multiple image files."
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 "Overlay mode on the smudge brush allows you to sample all the layers, and the ‘lighter color’ blending mode makes sure that the Bokeh circles only show up when they are a lighter color than the original pixels underneath. You can further modify this brush by adding a ‘fuzzy’ sensor to the spacing and size options, changing the brush blending mode to ‘addition’, or by choosing a different brush-tip."
msgid "Sure, caustics, it’s not like it’s the most complicated effect known to CG graphics… Okay, so the first thing is that light effects never work in isolation: you need to be spot on with colors and other effects to make it work. So we first need to recreate the surroundings a bit."
msgid "We set up something simple with gradients. Some radial, some linear. The eraser mode works with gradients as well, so use that to your advantage!"
msgid "Note how the smudge brush here is used not just to mix areas, but also to create definition of borders by lowering the scatter. (If you reverse the pressure curve on the scatter, this’ll be easily done by increasing the pressure on the stylus)"
msgid "Take *sketch_ink_big*, and add pressure to the :guilabel:`Line width` while setting :guilabel:`Density` under the :guilabel:`Brush size` to 100%. This makes it extra hairy."
msgid "Set the brush blending mode to :guilabel:`Color Dodge`, and select the color of our caustics. Color dodge will cause a move towards white by applying special dodge color maths to our brush dabs instead of the :guilabel:`Normal` averaging color maths."
msgid "Outside of pressure for making varying strokes, glowiness for the light and extra density, we also want to have the size of the line decrease the further away it is…"
msgid "Then, use the assistant editor tool to add a perspective grid. It doesn’t need to be perfectly in perspective, because we’ll only use it for the perspective sensor."
msgid "This will cause the brush to give smaller lines the further it registers on the perspective assistant. (It only works per single perspective assistant, making it not very good for chaining, but for our purpose this is good.)"
msgid "Then you start slowly building up your lines. (Make sure to make a copy of the layer. The color dodge blending doesn’t work well on a separate layer, so do it on one that also has the ground on it.)"
msgid "Make sure to try and follow the shapes you made. (*I failed at this*) The great thing about the sketch brush is that it causes those little ‘melt-togethers’ where two lines cross. This is only per stroke, so make a lot of long ongoing strokes with this brush to make use of it."
msgid "Then take the gradient tool, and set the blending mode to color and the paint tool to a light blue, so we can get in the bluish atmospheric effect."
msgid "Then use the airbrush_pressure with the line tool to make some light-shafts of different sizes on a separate layer. (Don’t forget you can use the eraser mode for subtle erasing with the line tool as well)"
# 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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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/krita-brush-tips/fur.rst:1
-msgid "A tutorial about creating fur in Krita"
+msgid "A tutorial about creating fur in Krita."
msgstr ""
#. +> trunk5
#: ../../tutorials/krita-brush-tips/fur.rst:13
msgid "Brush-tips:Fur"
msgstr ""
#. +> trunk5
#: ../../tutorials/krita-brush-tips/fur.rst:16
msgid "Question"
msgstr ""
#. +> trunk5
#: ../../tutorials/krita-brush-tips/fur.rst:18
msgid "What brushes are best for fur textures?"
msgstr ""
#. +> trunk5
#: ../../tutorials/krita-brush-tips/fur.rst:23
msgid "So typically, you see the same logic applied on fur as on regular :ref:`hair`."
msgstr ""
#. +> trunk5
#: ../../tutorials/krita-brush-tips/fur.rst:25
msgid "However, you can make a brush a little easier by using the Gradient, Mix and HSV options in the :ref:`pixel and color smudge brushes <pixel_brush_engine>`. Basically, what we want to do is have a stroke start dark and then become lighter as we draw with it, to simulate how hair-tips catch more light and look lighter due to being thinner at the ends, while at the base they are frequently more dark."
msgstr ""
#. +> trunk5
#: ../../tutorials/krita-brush-tips/fur.rst:30
msgid "Take the :guilabel:`ink_brush_25` and choose under :menuselection:`Brush Tip --> Predefined “A-2 dirty brush”`. Set the spacing to :guilabel:`Auto` and right-click the spacing bar to type in a value between 0.25 and 0.8. Also turn on the :guilabel:`Enable Pen Settings` on flow. Replicate the pressure curve above on the size option. We don’t want the hairs to collapse to a point, hence why the curve starts so high."
msgstr ""
#. +> trunk5
#: ../../tutorials/krita-brush-tips/fur.rst:35
msgid "Then activate value and reproduce this curve with the :guilabel:`Distance` or :guilabel:`Fade` sensor. Like how the pressure sensor changes a value (like size) with the amount of pressure you put on the stylus, the distance sensor measures how many pixels your stroke is, and can change an option depending on that. For the HSV sensors: If the curve goes beneath the middle, it’ll become remove from that adjustment, and above the vertical middle it’ll add to that adjustment. So in this case, for the first 100px the brush dab will go from a darkened version of the active paint color, to the active paint color, and then for 100px+ it’ll go from the active color to a lightened version. The curve is an inverse S-curve, because we want to give a lot of room to the mid-tones."
msgstr ""
#. +> trunk5
#: ../../tutorials/krita-brush-tips/fur.rst:40
msgid "We do the same thing for saturation, so that the darkened color is also slightly desaturated. Notice how the curve is close to the middle: This means its effect is much less strong than the value adjustment. The result should look somewhat like the fifth one from the left on the first row of this:"
msgstr ""
#. +> trunk5
#: ../../tutorials/krita-brush-tips/fur.rst:45
msgid "The others are done with the smudge brush engine, but a similar setup, though using color rate on distance instead. Do note that it’s very hard to shade realistic fur, so keep a good eye on your form shadow. You can also use this with grass, feathers and other vegetation:"
msgstr ""
#. +> trunk5
#: ../../tutorials/krita-brush-tips/fur.rst:50
msgid "For example, if you use the mix option in the pixel brush, it’ll mix between the fore and background color. You can even attach a gradient to the color smudge brush and the pixel brush. For color smudge, this is just the :guilabel:`Gradient` option, and it’ll use the active gradient. For the pixel brush, set the color-source to :guilabel:`Gradient` and use the mix option."
msgstr ""
#. +> trunk5
#: ../../tutorials/krita-brush-tips/fur.rst:55
msgid "On tumblr it was suggested this could be used to do `this tutorial <https://vimeo.com/78183651>`_. Basically, you can also combine this with the lighter color blending mode and wraparound mode to make making grass-textures really easy!"
# 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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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/krita-brush-tips/hair.rst:1
-msgid "A tutorial about painting hair in Krita"
+msgid "A tutorial about painting hair in Krita."
msgstr ""
#. +> trunk5
#: ../../tutorials/krita-brush-tips/hair.rst:13
msgid "Brush-tips:Hair"
msgstr ""
#. +> trunk5
#: ../../tutorials/krita-brush-tips/hair.rst:18
msgid "Usually, most digital styles tend to focus on simple brushes, like the round brushes, and their usage in hair is no different. So, the typical example would be the one on the left, where we use *fill_round* to draw a silhouette and build up to lighter values."
msgstr ""
#. +> trunk5
#: ../../tutorials/krita-brush-tips/hair.rst:20
msgid "The reason I use *fill_round* here is because the pressure curve on the size is s-shaped. My tablet has a spring-loaded nib which also causes and s-shaped curve hard-ware wise. This means that it becomes really easy to draw thin lines and big lines. Having a trained inking hand helps a lot with this as well, and it’s something you build up over time."
msgstr ""
#. +> trunk5
#: ../../tutorials/krita-brush-tips/hair.rst:25
msgid "We then gloss the shadow parties with the *basic_tip_default*. So you can get really far with basic brushes and basic painting skills and indeed I am almost convinced tysontan, who draws our mascot, doesn’t use anything but the *basic_tip_default* sometimes."
msgstr ""
#. +> trunk5
#: ../../tutorials/krita-brush-tips/hair.rst:30
msgid "However, if you want an easy hair brush, just take the *fill_round*, go to the brush-tip, pick predefined and select *A2-sparkle-1* as the brush tip. You can fiddle with the spacing below the selection of predefined brushtip to space the brush, but I believe the default should be fine enough to get result."
msgid "Not really a brush, but what you can do is add a layer style to a layer, by |mouseright| a layer and selecting layer style. Then input the following settings:"
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 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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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"
+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 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"
+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 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."
+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 "Sharpen the image a little. This is especially necessary for social media. Social media websites often scale and convert your image in such a way that it gets a little blurry, because they optimize towards photos and not paintings. To have your images stay sharp, it is worth it to run a sharpen filter beforehand. Because the sharpen filter is quite powerful, you are best off adding a sharpen filter mask on top of the stack and lowering it's opacity till you feel the sharpness is appropriate."
+msgstr ""
+
+#. +> trunk5
+#: ../../tutorials/saving-for-the-web.rst:29
msgid "Save as a web-safe image format. There's three that are especially recommended:"
msgstr ""
#. +> trunk5
-#: ../../tutorials/saving-for-the-web.rst:30
+#: ../../tutorials/saving-for-the-web.rst:32
msgid "JPG"
msgstr ""
#. +> trunk5
-#: ../../tutorials/saving-for-the-web.rst:32
+#: ../../tutorials/saving-for-the-web.rst:34
msgid "Use this for images with a lot of different colors, like paintings."
msgstr ""
#. +> trunk5
-#: ../../tutorials/saving-for-the-web.rst:35
+#: ../../tutorials/saving-for-the-web.rst:37
msgid "PNG"
msgstr ""
#. +> trunk5
-#: ../../tutorials/saving-for-the-web.rst:37
+#: ../../tutorials/saving-for-the-web.rst:39
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
+#: ../../tutorials/saving-for-the-web.rst:42
msgid "GIF"
msgstr ""
#. +> trunk5
-#: ../../tutorials/saving-for-the-web.rst:42
+#: ../../tutorials/saving-for-the-web.rst:44
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)**"
+#: ../../tutorials/saving-for-the-web.rst:51
+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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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 the :kbd:`Shift + ↑` shortcut to move the frame contents up."
msgstr ""
#. +> trunk5
#: ../../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: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: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: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 "To show a layer whether it's active or not, you can \"pin\" it to the timeline by right-clicking |mouseright| on the layer in the layer docker, and toggling :guilabel:`Pin to Timeline`. We recommend pinning any layers that you're currently animating on."
msgid "The images should be saved out as filenameXXX.png, giving their frame number."
msgstr ""
#. +> trunk5
-#: ../../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:"
+#: ../../user_manual/animation.rst:246
+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`."
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:254
+#: ../../user_manual/animation.rst:256
msgid "Enjoy your walkcycle!"
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:258
+#: ../../user_manual/animation.rst:260
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:261
+#: ../../user_manual/animation.rst:263
msgid "Importing animation frames"
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:263
+#: ../../user_manual/animation.rst:265
msgid "You can import animation frames in Krita 3.0."
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:265
+#: ../../user_manual/animation.rst:267
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:268
+#: ../../user_manual/animation.rst:270
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:274
+#: ../../user_manual/animation.rst:276
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:285
+#: ../../user_manual/animation.rst:287
msgid "Start"
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:286
+#: ../../user_manual/animation.rst:288
msgid "Indicates at which point the animation should be imported."
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:288
+#: ../../user_manual/animation.rst:290
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:292
+#: ../../user_manual/animation.rst:294
msgid "Step"
msgstr ""
#. +> trunk5
-#: ../../user_manual/animation.rst:294
+#: ../../user_manual/animation.rst:296
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 "Krita does its best to keep your work safe. But if you want to make sure that you won't lose work, you will need to understand how Saving, AutoSave and Backup Files work in Krita."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:22
msgid "Krita does not store your images somewhere without your intervention. You need to save your work, or it will be lost, irretrievably. Krita can save your images in many formats. You should always save your work in Krita's native format, ``.kra`` because that supports all Krita's features."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:25
msgid "Additionally, you can export your work to other formats, for compatibility with other applications or publication on the Web or on paper. Krita will warn which aspects of your work are going to be lost when you save to another format than ``.kra`` and offers to make a ``.kra`` file for you as well."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:27
msgid "If you save your work, Krita will ask you where it should save on your computer. By default, this is the Pictures folder in your User folder: this is true for all operating systems."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:29
-msgid "If you use \"Save As\" your image will be saved under a new name. The original file under its own name will not be deleted. From now on, your file will be saved under the new name."
+msgid "If you use :guilabel:`Save As...` your image will be saved under a new name. The original file under its own name will not be deleted. From now on, your file will be saved under the new name."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:31
-msgid "If you use \"Export\" using a new filename, a new file will be created with a new name. The file you have open will keep the new name, and the next time you save it, it will be saved under the old name."
+msgid "If you use :guilabel:`Export...` using a new filename, a new file will be created with a new name. The file you have open will keep the old name, and the next time you save it, it will be saved under the old name."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:33
-msgid "You can Save, Save As and Export to any file format."
+msgid "You can :guilabel:`Save`, :guilabel:`Save As...` and :guilabel:`Export...` to any file format."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:36
msgid "See also"
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:39
msgid ":ref:`Saving for the Web <saving_for_the_web>`"
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:43
msgid "AutoSave"
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:45
-msgid "AutoSave is what happens when you've worked for a bit and not saved your work yourself: Krita will save your work for you. Autosave files are by default hidden in your file manager. You can configure Krita 4.2 and up to create autosave files that are visible in your file manager. By default, Krita autosaves every fifteen minutes; you can configure that in the File tab of the General Settings page of the Configure Krita dialog, which is in the Settings menu (Linux, Windows) or in the Application menu (macOS)."
+msgid "AutoSave is what happens when you've worked for a bit and not saved your work yourself: Krita will save your work for you. Autosave files are by default hidden in your file manager. You can configure Krita 4.2 and up to create autosave files that are visible in your file manager. By default, Krita autosaves every fifteen minutes; you can configure that in the File tab of the General Settings page of the :guilabel:`Configure Krita` dialog, which is in the Settings menu (Linux, Windows) or in the Application menu (macOS)."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:47
msgid "If you close Krita without saving, your unsaved work is lost and cannot be retrieved. Closing Krita normally also means that autosave files are removed."
msgid "If you had not yet saved your work, Krita will create an unnamed AutoSave file."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:61
msgid "If you're using Linux or macOS, the AutoSave file will be a hidden file in your home directory. If you're using Windows, the AutoSave file will be a file in your user's ``%TEMP%`` folder. In Krita 4.2 and up, you can configure Krita to make the AutoSave files visible by default."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:63
msgid "A hidden autosave file will be named like ``.krita-12549-document_1-autosave.kra``"
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:65
msgid "If Krita crashes before you had saved your file, then the next time you start Krita, you will see the file in a dialog that shows up as soon as Krita starts. You can select to restore the files, or to delete them."
msgid "If Krita crashed, and you're on Windows and your ``%TEMP%`` folder gets cleared, you will have lost your work. Windows does not clear the ``%TEMP%`` folder by default, but you can enable this feature in Settings. Applications like Disk Cleanup or cCleaner will also clear the ``%TEMP%`` folder. Again, if Krita crashes, and you haven't saved your work, and you have something enabled that clear your ``%TEMP%`` folder, you will have lost your work."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:71
msgid "If Krita doesn't crash, and you close Krita without saving your work, Krita will remove the AutoSave file: your work will be gone and cannot be retrieved."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:73
msgid "If you save your work and continue, or close Krita and do save your work, the AutoSave file will be removed."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:76
msgid "AutoSave for Saved Files"
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:78
msgid "If you had already saved your work, Krita will create a named AutoSave file."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:80
msgid "A hidden named autosave file will look like ``.myimage.kra-autosave.kra``."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:82
msgid "By default, named AutoSave files are hidden. Named AutoSave files are placed in the same folder as the file you were working on."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:84
msgid "If you start Krita again after it crashed and try to open your original file, Krita will ask you whether to open the AutoSave file instead:"
msgid "If you choose \"no\", the AutoSave file will be removed. The work that has been done since the last time you saved your file yourself will be lost and cannot be retrieved."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:90
msgid "If you choose \"yes\", the AutoSave file will be opened, then removed. The file you have open will have the name of your original file. The file will be set to Modified, so the next time you try to close Krita, Krita will ask you whether you want to save the file. If you choose No, your work is irretrievably gone. It cannot be restored."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:92
-msgid "If you use \"Save As\" your image will be saved under a new name. The original file under its own name and its AutoSave file are not deleted. From now on, your file will be saved under the new name; if you save again, an AutoSave file will be created using the new filename."
+msgid "If you use :guilabel:`Save As...` your image will be saved under a new name. The original file under its own name and its AutoSave file are not deleted. From now on, your file will be saved under the new name; if you save again, an AutoSave file will be created using the new filename."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:94
-msgid "If you use \"Export\" using a new filename, a new file will be created with a new name. The file you have open will keep the new name, and the next time you save it, the AutoSave file will be created from the last file saved with the current name, that is, not the name you choose for \"Export\"."
+msgid "If you use :guilabel:`Export...` using a new filename, a new file will be created with a new name. The file you have open will keep the new name, and the next time you save it, the AutoSave file will be created from the last file saved with the current name, that is, not the name you choose for :guilabel:`Export...`."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:98
msgid "Backup Files"
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:100
msgid "There are three kinds of Backup files"
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:102
msgid "Ordinary Backup files that are created when you save a file that has been opened from disk"
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:103
msgid "Incremental Backup files that are copies of the file as it is on disk to a numbered backup, and while your file is saved under the current name"
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:104
msgid "Incremental Version files that are saves of the file you are working on with a new number, leaving alone the existing files on disk."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:108
msgid "Ordinary Backup Files"
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:110
msgid "If you have opened a file, made changes, then save it, or save a new file after the first time you've saved it, Krita will save a backup of your file."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:112
-msgid "You can disable this mechanism in the File tab of the General Settings page of the Configure Krita dialog, which is in the Settings menu (Linux, Windows) or in the Application menu (macOS). By default, Backup files are enabled."
+msgid "You can disable this mechanism in the File tab of the General Settings page of the :guilabel:`Configure Krita` dialog, which is in the Settings menu (Linux, Windows) or in the Application menu (macOS). By default, Backup files are enabled."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:116
msgid "By default, a Backup file will be in the same folder as your original file. You can also choose to save Backup files in the User folder or the ``%TEMP%`` folder; this is not as safe because if you edit two files with the same name in two different folders, their backups will overwrite each other."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:118
msgid "By default, a Backup file will have ``~`` as a suffix, to distinguish it from an ordinary file. If you are using Windows, you will have to enable \"show file extensions\" in Windows Explorer to see the extension."
msgid "If you want to open the Backup file, you will have to rename it in your file manager. Make sure the extension ends with ``.kra``."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:124
msgid "Every time you save your file, the last version without a ``~`` suffix will be copied to the version with the ``~`` suffix. The contents of the original file will be gone: it will not be possible to restore that version."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:127
msgid "Incremental Backup Files"
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:129
msgid "Incremental Backup files are similar to ordinary Backup files: the last saved state is copied to another file just before saving. However, instead of overwriting the Backup file, the Backup files are numbered:"
msgid "Use this when you want to keep various known good states of your image throughout your painting process. This takes more disk space, of course."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:135
msgid "Do not be confused: Krita does not save the current state of your work to the latest Incremental file, but copies the last saved file to the Backup file and then saves your image under the original filename."
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:138
msgid "Incremental Version Files"
msgstr ""
#. +> trunk5
#: ../../user_manual/autosave.rst:140
msgid "Incremental Version works a bit like Incremental Backup, but it leaves the original files alone. Instead, it will save a new file with a file number:"
# 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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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/drawing_tablets.rst:1
msgid "Basic page describing drawing tablets, how to set them up for Krita and how to troubleshoot common tablet issues."
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:13
msgid "Tablets"
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:18
msgid "Drawing Tablets"
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:20
msgid "This page is about drawing tablets, what they are, how they work, and where things can go wrong."
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:24
msgid "What are tablets?"
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:26
msgid "Drawing with a mouse can be unintuitive and difficult compared to pencil and paper. Even worse, extended mouse use can result in carpal tunnel syndrome. That’s why most people who draw digitally use a specialized piece of hardware known as a drawing tablet."
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:32
msgid ".. image:: images/Krita_tablet_types.png"
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:33
msgid "A drawing tablet is a piece of hardware that you can plug into your machine, much like a keyboard or mouse. It usually looks like a plastic pad, with a stylus. Another popular format is a computer monitor with stylus used to draw directly on the screen. These are better to use than a mouse because it’s more natural to draw with a stylus and generally better for your wrists."
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:40
msgid "With a properly installed tablet stylus, Krita can use information like pressure sensitivity, allowing you to make strokes that get bigger or smaller depending on the pressure you put on them, to create richer and more interesting strokes."
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:46
msgid "Sometimes, people confuse finger-touch styluses with a proper tablet. You can tell the difference because a drawing tablet stylus usually has a pointy nib, while a stylus made for finger-touch has a big rubbery round nib, like a finger. These tablets may not give good results and a pressure-sensitive tablet is recommended."
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:51
msgid "Drivers and Pressure Sensitivity"
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:53
msgid "So you have bought a tablet, a real drawing tablet. And you wanna get it to work with Krita! So you plug in the USB cable, start up Krita and... It doesn’t work! Or well, you can make strokes, but that pressure sensitivity you heard so much about doesn’t seem to work."
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:58
msgid "This is because you need to install a program called a ‘driver’. Usually you can find the driver on a CD that was delivered alongside your tablet, or on the website of the manufacturer. Go install it, and while you wait, we’ll go into the details of what it is!"
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:63
msgid "Running on your computer is a basic system doing all the tricky bits of running a computer for you. This is the operating system, or OS. Most people use an operating system called Windows, but people on an Apple device have an operating system called MacOS, and some people, including many of the developers use a system called Linux."
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:69
msgid "The base principle of all of these systems is the same though. You would like to run programs like Krita, called software, on your computer, and you want Krita to be able to communicate with the hardware, like your drawing tablet. But to have those two communicate can be really difficult - so the operating system, works as a glue between the two."
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:75
msgid "Whenever you start Krita, Krita will first make connections with the operating system, so it can ask it for a lot of these things: It would like to display things, and use the memory, and so on. Most importantly, it would like to get information from the tablet!"
msgid "But it can’t! Turns out your operating system doesn’t know much about tablets. That’s what drivers are for. Installing a driver gives the operating system enough information so the OS can provide Krita with the right information about the tablet. The hardware manufacturer's job is to write a proper driver for each operating system."
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:89
msgid "Because drivers modify the operating system a little, you will always need to restart your computer when installing or deinstalling a driver, so don’t forget to do this! Conversely, because Krita isn’t a driver, you don’t need to even deinstall it to reset the configuration, just rename or delete the configuration file."
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:92
msgid "Where it can go wrong: Windows"
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:94
msgid "Krita automatically connects to your tablet if the drivers are installed. When things go wrong, usually the problem isn't with Krita."
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:98
msgid "Surface pro tablets need two drivers"
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:100
-msgid "Certain tablets using n-trig, like the Surface Pro, have two types of drivers. One is native, n-trig and the other one is called wintab. Since 3.3, Krita can use Windows Ink style drivers, just go to :menuselection:`Settings --> Configure Krita --> Tablet Settings` and toggle the :guilabel:`Windows 8+ Pointer Input` there. You don't need to install the wintab drivers anymore for n-trig based pens."
+msgid "Certain tablets using n-trig, like the Surface Pro, have two types of drivers. One is native, n-trig and the other one is called wintab. Since 3.3, Krita can use Windows Ink style drivers, just go to :menuselection:`Settings --> Configure Krita... --> Tablet Settings` and toggle the :guilabel:`Windows 8+ Pointer Input (Windows Ink)` there. You don't need to install the wintab drivers anymore for n-trig based pens."
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:108
msgid "Windows 10 updates"
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:110
msgid "Sometimes a Windows 10 update can mess up tablet drivers. In that case, reinstalling the drivers should work."
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:114
msgid "Wacom Tablets"
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:116
msgid "There are two known problems with Wacom tablets and Windows."
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:118
msgid "The first is that if you have customized the driver settings, then sometimes, often after a driver update, but that is not necessary, the driver breaks. Resetting the driver to the default settings and then loading your settings from a backup will solve this problem."
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:123
msgid "The second is that for some reason it might be necessary to change the display priority order. You might have to make your Cintiq screen your primary screen, or, on the other hand, make it the secondary screen. Double check in the Wacom settings utility that the tablet in the Cintiq is associated with the Cintiq screen."
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:130
msgid "Broken Drivers"
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:132
msgid "Tablet drivers need to be made by the manufacturer. Sometimes, with really cheap tablets, the hardware is fine, but the driver is badly written, which means that the driver just doesn’t work well. We cannot do anything about this, sadly. You will have to send a complaint to the manufacturer for this, or buy a better tablet with better quality drivers."
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:140
msgid "Conflicting Drivers"
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:142
msgid "On Windows, you can only have a single wintab-style driver installed at a time. So be sure to deinstall the previous driver before installing the one that comes with the tablet you want to use. Other operating systems are a bit better about this, but even Linux, where the drivers are often preinstalled, can't run two tablets with different drivers at once."
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:150
msgid "Interfering software"
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:152
-msgid "Sometimes, there's software that tries to make a security layer between Krita and the operating system. Sandboxie is an example of this. However, Krita cannot always connect to certain parts of the operating system while sandboxed, so it will often break in programs like sandboxie. Similarly, certain mouse software, like Razer utilities can also affect whether Krita can talk to the operating system, converting tablet information to mouse information. This type of software should be configured to leave Krita alone, or be deinstalled."
+msgid "Sometimes, there's software that tries to make a security layer between Krita and the operating system. Sandboxie is an example of this. However, Krita cannot always connect to certain parts of the operating system while sandboxed, so it will often break in programs like Sandboxie. Similarly, certain mouse software, like Razer utilities can also affect whether Krita can talk to the operating system, converting tablet information to mouse information. This type of software should be configured to leave Krita alone, or be deinstalled."
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:161
msgid "The following software has been reported to interfere with tablet events to Krita:"
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:164
msgid "Sandboxie"
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:165
msgid "Razer mouse utilities"
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:166
-msgid "AMD catalyst “game mode” (this broke the right click for someone)"
+msgid "AMD Catalyst:sup:`TM` “game mode” (this broke the right click for someone)"
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:169
msgid "Flicks (Wait circle showing up and then calling the popup palette)"
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:171
msgid "If you have a situation where trying to draw keeps bringing up the pop-up palette on Windows, then the problem might be flicks. These are a type of gesture, a bit of Windows functionality that allows you to make a motion to serve as a keyboard shortcut. Windows automatically turns these on when you install tablet drivers, because the people who made this part of Windows forgot that people also draw with computers. So you will need to turn it off in the Windows flicks configuration."
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:180
msgid "Wacom Double Click Sensitivity (Straight starts of lines)"
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:182
msgid "If you experience an issue where the start of the stroke is straight, and have a wacom tablet, it could be caused by the Wacom driver double-click detection."
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:186
msgid "To fix this, go to the Wacom settings utility and lower the double click sensitivity."
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:190
msgid "Supported Tablets"
msgstr ""
#. +> trunk5
#: ../../user_manual/drawing_tablets.rst:192
msgid "Supported tablets are the ones of which Krita developers have a version themselves, so they can reliably fix bugs with them. :ref:`We maintain a list of those here <list_supported_tablets>`."
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 "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 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 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 "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 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 "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 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 "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 "You can also configure the toolbar via :menuselection:`Settings --> Configure Toolbars...`, as well as the shortcuts under both :menuselection:`Settings --> Configure Krita... --> 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 "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 <https://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 "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 "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 "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 disk space 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 "We also have Flatpak for nightlies and stable builds, these builds are not maintained by the core developers themselves. You can either get the builds from the `KDE community website <https://binary-factory.kde.org>`_ or from the `Flathub Maintainers <https://flathub.org/apps/details/org.kde.krita>`_."
+msgid "To install flatpak build from the software centre just open the flatpakrepo files with Discover or the software center provided by your distribution:"
+msgid "There are snap packages provided by the ubuntu snap developers, these are generally not up to date. The Krita Developers do not provide or build the snap packages themselves. To install Krita as a snap package, first install snapd application. Snapd is installed by default on ubuntu distributions."
+msgid "If you are on ubuntu distribution then Krita's snap package may show up in the software center or you can run the following command in terminal"
+msgid "The Flatpak and Snap builds are not tested by the core developers of Krita, so you may encounter some bugs while running Krita installed from them."
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:`-` 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 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 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 "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 "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 "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 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 "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 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 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 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 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 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| 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 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 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 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 "Krita has no clipping mask, but there is a simpler 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, and also keeps the layer stack cleaner than the clipping mask implementation does."
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 which point to an outside file, and will get automatically updated if the outside file changes. Starting from version 4.0 users can convert an existing layer into a file layer by |mouseright| clicking on it and doing :menuselection:`Convert --> to File Layer` or by going to :menuselection:`Layer --> Convert --> to File Layer`. It will then open a save prompt for the file location and when done will save the file and replace the layer with a file layer pointing at that file."
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 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 "In Krita, the eraser is not its own tool; it is a Blending mode (or Composite mode). You can toggle between erase mode and paint mode by pressing the :kbd:`E` key, individually for each of your brushes."
-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 "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 Krita... --> 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 "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 "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 "As mentioned in the introduction, Krita is a specialized paint application. Thus, it 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 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 "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 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, including with shapes other 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 "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 by 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 "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 OpenEXR 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 "Also, you cannot ‘Export for web’, ‘Image Ready’ for Gif frame or slicing web image, etc."
+msgid "You may have used this tool in Photoshop to seamlessly and automatically stitch together a drawing that was scanned in segments. Krita does not have an equivalent, though an alternative is to use Hugin, which is cross-platform and free, just like Krita."
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 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 the :kbd:`+` and :kbd:`-` keys to zoom out and in, or use the :kbd:`Ctrl +` |mousemiddle| shortcut. Use the :kbd:`1`, :kbd:`2` or :kbd:`3` keys 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 "You can also put these commands on the toolbar, so it'll feel a little like Sai. Go to :menuselection:`Settings --> Configure Toolbars...` menu item. There are two toolbars, but we'll add to the Main 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 "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 and Stuff 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| shortcut 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 Merged 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 "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 --> Image Background Color and Transparency...` menu item. If you export a PNG or JPG, make sure to uncheck :guilabel:`Store alpha channel (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 "Like Sai, you can quickly turn a black and white image to black and transparent with the :guilabel:`Filter: Color to Alpha` dialog under :menuselection:`Filters --> Colors --> Color to Alpha...` menu item."
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 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 "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`` or ``.kpp`` files."
-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 "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 :guilabel:`Blending Mode` drop-down box."
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 "Sai's Luminosity mode (called Shine in Sai2) is the same as Krita's *Luminosity/Shine (SAI)* mode, which is new in Krita 4.2.4. The Sai's Shade mode is the same as *Color Burn* and *Hard Mix* is the same as the Luminosity and Shade modes."
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 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... --> Color Selector Settings --> Color Selector tab`, select an option in the :guilabel:`Docker:` drop-down box, to change the shape and type of your main color selector."
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 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 :kbd:`F5` key to open it."
+msgid "To start, the Brush Settings Editor panel can be accessed in the toolbar, between the :guilabel:`Choose brush preset` button on the right and the :guilabel:`Fill 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 "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 "If you change a preset, an icon will appear behind the engine name. This is the :guilabel:`Reload the brush preset` 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 "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 "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 "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 "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 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 "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 :guilabel:`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 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 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."
+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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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/mirror_tools.rst:1
msgid "How to use the canvas mirroring tools in Krita."
msgstr ""
#. +> trunk5
#: ../../user_manual/mirror_tools.rst:11
msgid "Mirror"
msgstr ""
#. +> trunk5
#: ../../user_manual/mirror_tools.rst:11
msgid "Symmetry"
msgstr ""
#. +> trunk5
#: ../../user_manual/mirror_tools.rst:16
msgid "Mirror Tools"
msgstr ""
#. +> trunk5
#: ../../user_manual/mirror_tools.rst:18
msgid "Draw on one side of a mirror line while the Mirror Tool copies the results to the other side. The Mirror Tools are accessed along the toolbar. You can move the location of the mirror line by grabbing the handle."
msgstr ""
#. +> trunk5
#: ../../user_manual/mirror_tools.rst:21
msgid ".. image:: images/Mirror-tool.png"
msgstr ""
#. +> trunk5
#: ../../user_manual/mirror_tools.rst:22
msgid "Mirror Tools give a similar result to the :ref:`multibrush_tool`, but unlike the Multibrush which only traces brush strokes like the :ref:`freehand_brush_tool`, the Mirror Tools can be used with any other tool that traces strokes, such as the :ref:`line_tool` and the :ref:`path_tool`, and even with the Multibrush Tool."
msgstr ""
#. +> trunk5
#: ../../user_manual/mirror_tools.rst:24
msgid "**Horizontal Mirror Tool** - Mirror the results along the horizontal axis."
msgstr ""
#. +> trunk5
#: ../../user_manual/mirror_tools.rst:27
msgid "**Vertical Mirror Tool** - Mirror the results along the vertical axis."
msgstr ""
#. +> trunk5
#: ../../user_manual/mirror_tools.rst:30
msgid "There are additional options for each tool. You can access these by the clicking the drop-down arrow located on the right of each tool."
msgstr ""
#. +> trunk5
#: ../../user_manual/mirror_tools.rst:33
-msgid "Hide Mirror Line (toggle) -- Locks the mirror axis and hides the axis line."
+msgid "Hide Mirror X/Y Line (toggle) -- Locks the mirror axis and hides the axis line."
msgstr ""
#. +> trunk5
-#: ../../user_manual/mirror_tools.rst:35
-msgid "Lock (toggle) - hides the move icon on the axis line."
+#: ../../user_manual/mirror_tools.rst:34
+msgid "Lock X/Y Line (toggle) - hides the move icon on the axis line."
msgstr ""
#. +> trunk5
-#: ../../user_manual/mirror_tools.rst:36
-msgid "Move to Canvas Center - Moves the axis line to the center of the canvas."
+#: ../../user_manual/mirror_tools.rst:35
+msgid "Move to Canvas Center X/Y - Moves the axis line to the center of the canvas."
msgstr ""
#. +> trunk5
-#: ../../user_manual/mirror_tools.rst:40
+#: ../../user_manual/mirror_tools.rst:38
msgid "Mirroring along a rotated line"
msgstr ""
#. +> trunk5
-#: ../../user_manual/mirror_tools.rst:42
+#: ../../user_manual/mirror_tools.rst:40
msgid "The Mirror Tool can only mirror along a perfectly vertical or horizontal line. To mirror along a line that is at a rotated angle, use the :ref:`multibrush_tool` and its various parameters, it has more advanced options besides basic symmetry."
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 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 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 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 "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 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 "You might have some neat scripts you have written in the Scripter Python runner, but maybe you want to do more with it and run it automatically for instance. Wrapping your script in a plugin can give you much more flexibility and power than running scripts from the Scripter editor."
msgid "Okay, so even if you know python really well, there are some little details to getting Krita to recognize a python plugin. So this page will give an overview how to create the various types of python script unique to Krita."
msgid "These mini-tutorials are written for people with a basic understanding of python, and in such a way to encourage experimentation instead of plainly copy and pasting code, so read the text carefully."
-msgid "A script in Krita has two components - the script directory (holding your script's Python files) and a \".desktop\" file that Krita uses to load and register your script. For Krita to load your script both of these must put be in the pykrita subdirectory of your Krita resources folder (on Linux ~/.local/share/krita/pykrita). To find your resources folder start Krita and click the :menuselection:`Settings --> Manage Resources` menu item. This will open a dialog box. Click the :guilabel:`Open Resources Folder` button. This should open a file manager on your system at your Krita resources folder. See the `API <https://api.kde.org/extragear-api/graphics-apidocs/krita/libs/libkis/html/index.html>`_ docs under \"Auto starting scripts\". If there is no pykrita subfolder in the Krita resources directory use your file manager to create one."
+msgid "A script in Krita has two components - the script directory (holding your script's Python files) and a \".desktop\" file that Krita uses to load and register your script. For Krita to load your script both of these must put be in the pykrita subdirectory of your Krita resources folder (on Linux ~/.local/share/krita/pykrita). To find your resources folder start Krita and click the :menuselection:`Settings --> Manage Resources...` menu item. This will open a dialog box. Click the :guilabel:`Open Resources Folder` button. This should open a file manager on your system at your Krita resources folder. See the `API <https://api.kde.org/extragear-api/graphics-apidocs/krita/libs/libkis/html/index.html>`_ docs under \"Auto starting scripts\". If there is no pykrita subfolder in the Krita resources directory use your file manager to create one."
msgid "Whether it is python 2 compatible. If Krita was built with python 2 instead of 3 (``-DENABLE_PYTHON_2=ON`` in the cmake configuration), then this plugin will not show up in the list."
msgid "An Optional Value that will point to the manual item. This is shown in the Python Plugin manager. If it's `an HTML file it'll be shown as rich text <https://doc.qt.io/qt-5/richtext-html-subset.html>`_, if not, it'll be shown as plain text."
msgid "Where .myplugin is the name of the main file of your plugin. If you restart Krita, it now should show this in the Python Plugin Manager in the settings, but it will be grayed out, because there's no myplugin.py. If you hover over disabled plugins, you can see the error with them."
-msgid "You need to explicitly enable your plugin. Go to the Settings menu, open the Configure Krita dialog and go to the Python Plugin Manager page and enable your plugin."
+msgid "You need to explicitly enable your plugin. Go to the Settings menu, open the :guilabel:`Configure Krita` dialog and go to the Python Plugin Manager page and enable your plugin."
msgid "`Extensions <https://api.kde.org/extragear-api/graphics-apidocs/krita/libs/libkis/html/classExtension.html>`_ are relatively simple python scripts that run on Krita start. They are made by extending the Extension class, and the most barebones extension looks like this:"
msgid "This code of course doesn't do anything. Typically, in createActions we add actions to Krita, so we can access our script from the :guilabel:`Tools` menu."
msgid "First, let's create an `action <https://api.kde.org/extragear-api/graphics-apidocs/krita/libs/libkis/html/classAction.html>`_. We can do that easily with `Window.createAction() <https://api.kde.org/extragear-api/graphics-apidocs/krita/libs/libkis/html/classWindow.html#a72ec58e53844076c1461966c34a9115c>`_. Krita will call createActions for every Window that is created and pass the right window object that we have to use."
msgid "If you now restart Krita, you will have an action called \"My Script\". It still doesn't do anything, because we haven't connected it to a script."
msgid "So, let's make a simple export document script. Add the following to the extension class, make sure it is above where you add the extension to Krita:"
msgid "This is an example of a `signal/slot connection <https://doc.qt.io/qt-5/signalsandslots.html>`_, which Qt applications like Krita use a lot. We'll go over how to make our own signals and slots a bit later."
msgid "Krita, for various reasons, only adds actions to the shortcuts menu when they are present in an .action file. The action file to get our action to be added to shortcuts should look like this:"
msgid "The text it will show when displayed in a toolbar. So for example, \"Resize Image to New Size\" could be shortened to \"Resize Image\" to save space, so we'd put that in here."
msgid "This determines activation conditions (e.g. activate only when selection is editable). See `the code <https://cgit.kde.org/krita.git/tree/libs/ui/kis_action.h#n76>`_ for examples."
msgid "Save this file as \"myplugin.action\" where myplugin is the name of your plugin. The action file should be saved, not in the pykrita resources folder, but rather in a resources folder named \"actions\". (So, share/pykrita is where the python plugins and desktop files go, and share/actions is where the action files go) Restart Krita. The shortcut should now show up in the shortcut action list."
msgid "Creating a custom `docker <https://api.kde.org/extragear-api/graphics-apidocs/krita/libs/libkis/html/classDockWidget.html>`_ is much like creating an extension. Dockers are in some ways a little easier, but they also require more use of widgets. This is the barebones docker code:"
msgid "The window title is how it will appear in the docker list in Krita. canvasChanged always needs to be present, but you don't have to do anything with it, so hence just 'pass'."
msgid "So, if we add our export document function we created in the extension section to this docker code, how do we allow the user to activate it? First, we'll need to do some Qt GUI coding: Let's add a button!"
msgid "By default, Krita uses PyQt, but its documentation is pretty bad, mostly because the regular Qt documentation is really good, and you'll often find that the PyQT documentation of a class, say, `QWidget <https://www.riverbankcomputing.com/static/Docs/PyQt4/qwidget.html>`_ is like a weird copy of the regular `Qt documentation <https://doc.qt.io/qt-5/qwidget.html>`_ for that class."
msgid "Now, to connect the button to our function, we'll need to look at the signals in the documentation. `QPushButton <https://doc.qt.io/qt-5/qpushbutton.html>`_ has no unique signals of its own, but it does say it inherits 4 signals from `QAbstractButton <https://doc.qt.io/qt-5/qabstractbutton.html#signals>`_, which means that we can use those too. In our case, we want clicked."
msgid "Qt has several `layouts <https://doc.qt.io/qt-5/qlayout.html>`_, but the `QHBoxLayout and the QVBoxLayout <https://doc.qt.io/qt-5/qboxlayout.html>`_ are the easiest to use, they just arrange widgets horizontally or vertically."
msgid "We've already been using PyQt signals and slots already, but there are times where you want to create your own signals and slots. `As pyQt's documentation is pretty difficult to understand <https://www.riverbankcomputing.com/static/Docs/PyQt4/new_style_signals_slots.html>`_, and the way how signals and slots are created is very different from C++ Qt, we're explaining it here:"
msgid "All python functions you make in PyQt can be understood as slots, meaning that they can be connected to signals like Action.triggered or QPushButton.clicked. However, QCheckBox has a signal for toggled, which sends a boolean. How do we get our function to accept that boolean?"
msgid "Okay, so that covers all the Krita specific details for creating python plugins. It doesn't handle how to parse the pixel data, or best practices with documents, but if you have a little bit of experience with python you should be able to start creating your own plugins."
msgid "As always, read the code carefully and read the API docs for python, Krita and Qt carefully to see what is possible, and you'll get pretty far."
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 the :kbd:`Enter` key or connecting back to the first point."
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:12
+#: ../../user_manual/selections.rst:1
+msgid ":ref:`magnetic_selection_tool`"
+msgstr ""
+
+#. +> trunk5
+#: ../../user_manual/selections.rst:1
+msgid "|toolselectmagnetic|"
+msgstr ""
+
+#. +> trunk5
+#: ../../user_manual/selections.rst:1
+msgid "Magnetic selection makes a free hand selection where the selection snaps to sharp contrasts in the image."
+msgstr ""
+
+#. +> trunk5
+#: ../../user_manual/selections.rst:13
msgid "Selection"
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:17
+#: ../../user_manual/selections.rst:18
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."
+#: ../../user_manual/selections.rst:20
+msgid "Selections allow you to pick a specific area of your artwork to change. This is useful when you want to move a section of the painting, 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. The selections in Krita are not limited to the canvas boundary, so you can also selection portions of the painting that are beyond the canvas boundary."
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:22
+#: ../../user_manual/selections.rst:23
msgid "Creating Selections"
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:24
+#: ../../user_manual/selections.rst:25
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
+#: ../../user_manual/selections.rst:40
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
+#: ../../user_manual/selections.rst:43
msgid "Editing Selections"
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:43
+#: ../../user_manual/selections.rst:45
msgid "The tool options for each selection tool gives you the ability to modify your selection."
-msgid "Get the overlapping section of both selections"
+#: ../../user_manual/selections.rst:53
+msgid "Get the overlapping section of both selections."
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:53
+#: ../../user_manual/selections.rst:55
msgid "Add"
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:53
+#: ../../user_manual/selections.rst:55
msgid "Shift"
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:53
+#: ../../user_manual/selections.rst:55
msgid "A"
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:53
+#: ../../user_manual/selections.rst:55
msgid "Add the new selection to the current selection."
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:55
+#: ../../user_manual/selections.rst:57
msgid "Subtract"
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:55
+#: ../../user_manual/selections.rst:57
msgid "Alt"
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:55
+#: ../../user_manual/selections.rst:57
msgid "S"
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:55
+#: ../../user_manual/selections.rst:57
msgid "Subtract the selection from the current selection."
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:57
+#: ../../user_manual/selections.rst:59
msgid "Symmetric Difference"
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:57
+#: ../../user_manual/selections.rst:59
msgid "Make a selection where both the new and current do not overlap."
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:61
+#: ../../user_manual/selections.rst:63
msgid "You can change this in :ref:`tool_options_settings`."
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:63
+#: ../../user_manual/selections.rst:65
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
+#: ../../user_manual/selections.rst:68
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`."
+#: ../../user_manual/selections.rst:70
+msgid "If you want to delete the entire selection, the easiest way is to deselect everything. :menuselection:`Select --> Deselect`. Shortcut :kbd:`Ctrl + Shift + A`. When you have one of the selection tool active, and the mode of selection is in intersect, replace or symmetric difference then you can also deselect by just |mouseleft| anywhere on the canvas."
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:71
+#: ../../user_manual/selections.rst:74
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."
+#: ../../user_manual/selections.rst:76
+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
+#: ../../user_manual/selections.rst:89
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
+#: ../../user_manual/selections.rst:92
msgid "Global Selection Mask (Painting a Selection)"
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:91
+#: ../../user_manual/selections.rst:94
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
+#: ../../user_manual/selections.rst:101
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
+#: ../../user_manual/selections.rst:104
msgid "Selection from layer transparency"
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:104
+#: ../../user_manual/selections.rst:107
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
+#: ../../user_manual/selections.rst:111
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
+#: ../../user_manual/selections.rst:113
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
+#: ../../user_manual/selections.rst:119
msgid "Pixel and Vector Selection Types"
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:116
+#: ../../user_manual/selections.rst:121
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."
+#: ../../user_manual/selections.rst:125
+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 Vector."
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:122
+#: ../../user_manual/selections.rst:127
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
+#: ../../user_manual/selections.rst:129
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
+#: ../../user_manual/selections.rst:131
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
+#: ../../user_manual/selections.rst:135
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
+#: ../../user_manual/selections.rst:138
msgid "Common Shortcuts while Using Selections"
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:135
+#: ../../user_manual/selections.rst:140
msgid "Copy -- :kbd:`Ctrl + C` or :kbd:`Ctrl + Ins`"
msgstr ""
#. +> trunk5
-#: ../../user_manual/selections.rst:136
+#: ../../user_manual/selections.rst:141
msgid "Paste -- :kbd:`Ctrl + V` or :kbd:`Shift + Ins`"
# 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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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 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`."
+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"
+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`."
+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."
+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 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 <https://ninedegreesbelow.com/bug-reports/soft-proofing-problems.html>`_ for more info."
-msgid "Templates are just .kra files which are saved in a special location so it can be pulled up by Krita quickly. This is like the :guilabel:`Open Existing Document and Untitled Document` but then with a nicer place in the UI."
+msgid "Templates are just ``.kra`` files which are saved in a special location so it can be pulled up by Krita quickly. This is like the :guilabel:`Open Existing Document as Untitled Document...` but then with a nicer place in the UI."
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:23
-msgid "You can make your own template file from any .kra file, by using :guilabel:`create template from image` in the file menu. This will add your current document as a new template, including all its properties along with the layers and layer contents."
+msgid "You can make your own template file from any ``.kra`` file, by using :menuselection:`File --> Create Template from Image...` menu item. This will add your current document as a new template, including all its properties along with the layers and layer contents."
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:25
msgid "We have the following defaults:"
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:28
msgid "Comic Templates"
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:30
msgid "These templates are specifically designed for you to just get started with drawing comics. The comic template relies on a system of vectors and clones of those vector layers which automatically reflect any changes made to the vector layers. In between these two, you can draw your picture, and not fear them drawing over the panel. Use :guilabel:`Inherit Alpha` to clip the drawing by the panel."
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:32
msgid "European Bande Desinée Template."
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:33
msgid "This one is reminiscent of the system used by for example TinTin or Spirou et Fantasio. These panels focus on wide images, and horizontal cuts."
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:34
msgid "US-style comics Template."
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:35
msgid "This one is reminiscent of old DC and Marvel comics, such as Batman or Captain America. Nine images for quick story progression."
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:36
msgid "Manga Template."
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:37
msgid "This one is based on Japanese comics, and focuses on a thin vertical gutter and a thick horizontal gutter, ensuring that the reader finished the previous row before heading to the next."
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:39
msgid "Waffle Iron Grid"
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:39
msgid "12 little panels at your disposal."
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:42
msgid "Design Templates"
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:44
msgid "These are templates for design and have various defaults with proper ppi at your disposal:"
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:46
msgid "Cinema 16:10"
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:47
msgid "Cinema 2.93:1"
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:48
msgid "Presentation A3-landscape"
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:49
msgid "Presentation A4 portrait"
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:50
msgid "Screen 4:3"
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:51
msgid "Web Design"
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:54
msgid "DSLR templates"
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:56
-msgid "These have some default size for photos"
+msgid "These have some default size for photos:"
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:58
msgid "Canon 55D"
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:59
msgid "Canon 5DMK3"
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:60
msgid "Nikon D3000"
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:61
msgid "Nikon D5000"
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:62
msgid "Nikon D7000"
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:65
msgid "Texture Templates"
msgstr ""
#. +> trunk5
#: ../../user_manual/templates.rst:67
msgid "These are for making 3D textures, and are between 1024, to 4092."
# 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.3\n"
"Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2020-04-12 12:36+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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"
+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 "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."
+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`."
+msgid "These things can be edited in :menuselection:`File --> Document Information`, and for the author's information :menuselection:`Settings --> Configure Krita... --> Author`. 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."
+msgid "You can set the canvas background color via :menuselection:`Image --> Image Background Color and Transparency...` menu item. 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."
+msgid "If you come in from a program like :program:`Paint Tool Sai`, then using this option, or using :guilabel:`As canvas color` radio button at :guilabel:`Background:` section 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."
+msgid "There are some basic transforms available in the Image menu."
msgstr ""
#. +> trunk5
#: ../../user_manual/working_with_images.rst:152
-msgid "Shear Image"
+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."
+msgid "This show a submenu that 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"
+msgid "Mirror Image Horizontally/Vertically"
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."
+msgid "Using :menuselection:`Image --> Trim to Current 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
+#: ../../user_manual/working_with_images.rst:175
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
+#: ../../user_manual/working_with_images.rst:181
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
+#: ../../user_manual/working_with_images.rst:186
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 the :kbd:`Ctrl + Alt + C` shortcut). The dialog box is shown below."
+#: ../../user_manual/working_with_images.rst:188
+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
+#: ../../user_manual/working_with_images.rst:192
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)."
+#: ../../user_manual/working_with_images.rst:193
+msgid "In this, :guilabel:`Constrain proportions` checkbox 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:"
+#: ../../user_manual/working_with_images.rst:200
+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 a strip with 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
+#: ../../user_manual/working_with_images.rst:210
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."
+#: ../../user_manual/working_with_images.rst:212
+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."
+#: ../../user_manual/working_with_images.rst:219
+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 link 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
+#: ../../user_manual/working_with_images.rst:234
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."
+#: ../../user_manual/working_with_images.rst:239
+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
+#: ../../user_manual/working_with_images.rst:244
msgid "Saving, Exporting and Opening Files"
msgstr ""
#. +> trunk5
-#: ../../user_manual/working_with_images.rst:245
+#: ../../user_manual/working_with_images.rst:246
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
+#: ../../user_manual/working_with_images.rst:253
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
+#: ../../user_manual/working_with_images.rst:254
msgid "Save"
msgstr ""
#. +> trunk5
-#: ../../user_manual/working_with_images.rst:256
-msgid "Save As"
+#: ../../user_manual/working_with_images.rst:257
+msgid "Save As..."
msgstr ""
#. +> trunk5
-#: ../../user_manual/working_with_images.rst:256
+#: ../../user_manual/working_with_images.rst:257
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"
+#: ../../user_manual/working_with_images.rst:259
+msgid "Open..."
msgstr ""
#. +> trunk5
-#: ../../user_manual/working_with_images.rst:259
+#: ../../user_manual/working_with_images.rst:260
msgid "Open a saved file. Fairly straightforward."
msgstr ""
#. +> trunk5
-#: ../../user_manual/working_with_images.rst:261
+#: ../../user_manual/working_with_images.rst:262
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"
+#: ../../user_manual/working_with_images.rst:263
+msgid "Export..."
msgstr ""
#. +> trunk5
-#: ../../user_manual/working_with_images.rst:265
+#: ../../user_manual/working_with_images.rst:266
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"
+#: ../../user_manual/working_with_images.rst:267
+msgid "Open Existing Document as Untitled Document..."
msgstr ""
#. +> trunk5
-#: ../../user_manual/working_with_images.rst:269
-msgid "Create Copy from Current Image"
+#: ../../user_manual/working_with_images.rst:270
+msgid "Makes a new copy of the current image. Similar to :menuselection:`Open Existing Document as Untitled Document...`, but then with already opened files."
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."
+#: ../../user_manual/working_with_images.rst:271
+msgid "Create Copy from Current Image"
msgstr ""
#. +> trunk5
-#: ../../user_manual/working_with_images.rst:272
+#: ../../user_manual/working_with_images.rst:274
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."
+#: ../../user_manual/working_with_images.rst:274
+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
+#: ../../user_manual/working_with_images.rst:277
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
+#: ../../user_manual/working_with_images.rst:278
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."
+#: ../../user_manual/working_with_images.rst:281
+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."
# Copyright (C) YEAR Free Software Foundation, Inc.
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
-"POT-Creation-Date: 2020-04-21 09:40+0200\n"
+"POT-Creation-Date: 2020-04-22 08:20+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"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#. +> trunk5
#: config.yaml:0
msgid "Get Involved"
msgstr ""
#. +> trunk5
#: config.yaml:0
msgid "Donate"
msgstr ""
#. +> trunk5
#: config.yaml:0
msgid "KDE Announcement | Release Service"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/19.12-rc/_index.md:3
msgid "title: 19.12 RC Releases"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/19.12-rc/_index.md:5
msgid "summary: \"Over 120 individual programs plus dozens of programmer libraries and feature plugins are released simultaneously as part of KDE's release service.\""
msgid "November 29, 2019. Over 120 individual programs plus dozens of programmer libraries and feature plugins are released simultaneously as part of KDE's release service."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/19.12-rc/_index.md:16
msgid "Today they all get release candidate sources meaning they are feature complete but need testing for final bugfixes."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/19.12-rc/_index.md:18
msgid "Distro and app store packagers should update their pre-release channels to check for issues."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/19.12-rc/_index.md:22
msgid "+ [19.12 release notes](https://community.kde.org/Releases/19.12_Release_Notes) for information on tarballs and known issues. + [Package download wiki page](https://community.kde.org/Get_KDE_Software_on_Your_Linux_Distro) + [19.12 RC source info page](https://kde.org/info/applications-19.11.90)"
msgstr ""
#. type: Title ##
#. +> trunk5
#: content/19.12-rc/_index.md:23
#, no-wrap
msgid "Press Contacts"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/19.12-rc/_index.md:25
msgid "For more information send us an email: [press@kde.org](mailto:press@kde.org)."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:3
msgid "title: KDE's December 2019 Apps Update"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:5
#: content/2020-01-apps-update/_index.md:9
#: content/2020-02-apps-update/_index.md:9
#: content/2020-03-apps-update/_index.md:9
#: content/2020-04-apps-update/_index.md:9
msgid "summary: \"What Happened in KDE's Applications This Month\""
msgid "New versions of KDE applications landing in December"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:16
msgid "The release of new versions for KDE applications is part of KDE's continued effort to bring you a complete and up-to-date catalog of fully-featured, beautiful and useful programs for your system."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:18
msgid "Available now are new versions of KDE's file browser Dolphin; Kdenlive, one of the most complete open source video editors; the document viewer Okular; KDE's image viewer, Gwenview; and all of your other favorite KDE apps and utilities. All of these applications have been improved, making them faster and more stable and they boast exciting new features. The new versions of KDE applications let you be productive and creative, while at the same time making use of KDE software easy and fun."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:20
msgid "We hope you enjoy all the novel features and improvements worked into all of KDE's apps!"
msgid "[Calligra Plan](https://kde.org/applications/office/org.kde.calligraplan) is getting a big release in December. KDE's project planning and management tool has hit a huge milestone since the prior version was released almost two years ago."
msgid "Plan helps you manage small and large projects with multiple resources. In order for you to model your project, Plan offers different types of task dependencies and timing constraints. You can define your tasks, estimate the effort needed to perform each, allocate resources and then schedule the project according to your needs and the resources available."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:30
msgid "One of Plan's strengths is its excellent support for Gantt charts. Gantt charts are charts made up of horizontal bars that provide a graphical illustration of a schedule and help plan, coordinate, and track specific tasks in a project. Using Gantt charts in Plan will help you better monitor your project's workflow."
msgstr ""
#. type: Title ##
#. +> trunk5
#: content/2019-12-apps-update/_index.md:31
#, no-wrap
msgid "Pump up the Volume on [Kdenlive](https://kdenlive.org)"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:34
msgid "Developers of [Kdenlive](https://kdenlive.org) have been adding new features and squashing bugs at breakneck speed. This version alone comes with more than 200 commits."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:36
msgid "A lot of work has gone into improving support for audio. In the \"bug solved\" department they have gotten rid of a huge memory consumption issue, inefficiency of audio thumbnails, and have sped up their storage."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:38
msgid "But even more exciting is that Kdenlive now comes with a spectacular new sound mixer (see image). Developers have also added a new audio clip display in the clip monitor and the project bin so you can better synchronize your moving images with the soundtrack."
msgid "In the \"resolving paper-cuts\" department, Kdenlive has acquired many performance and usability improvements, and developers have fixed many bugs in the Windows version of the video editor."
msgstr ""
#. type: Title ##
#. +> trunk5
#: content/2019-12-apps-update/_index.md:43
#, no-wrap
msgid "[Dolphin](https://userbase.kde.org/Dolphin)'s Previews and Navigation"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:46
msgid "KDE's powerful file browser [Dolphin](https://userbase.kde.org/Dolphin) adds new features to help you find and reach what you are looking for in your file system. One such feature is the redesigned advanced search options and another is that now you can go backwards and forwards in the history of places you have already visited multiple times by long-pressing the arrow icon in the toolbar. The feature that lets you quickly reach recently saved or recently accessed files has been reworked and its glitches ironed out."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:48
msgid "One of the main concerns of Dolphin's developers is to allow users to preview the contents of files before they open them. For example, in the new version of Dolphin you can preview GIFs by highlighting them and then hovering over the preview pane. You can also click and play videos and audio files in the preview pane."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:50
#, no-wrap
msgid "If you are a fan of graphic novels, Dolphin can now display thumbnails for .cb7 comic books (check out the support for this comic book format also in Okular -- see below). And, talking about thumbnails, zooming in on thumbnails has been a thing in Dolphin for a long time now: hold down <kbd>Ctrl</kbd>, spin the wheel and the thumbnail will grow or shrink. A new functionality is that now you can reset the zoom to the default level by hitting <kbd>Ctrl</kbd> + <kbd>0</kbd>.\n"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:52
msgid "Another useful feature is that Dolphin shows you which programs are preventing a device from being unmounted."
msgid "[KDE Connect](https://community.kde.org/KDEConnect): Let your Phone Control your Desktop"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:58
msgid "The latest version of [KDE Connect](https://community.kde.org/KDEConnect) comes stuffed with new features. One of the most noticeable is that there is a new SMS app that lets you read and write SMS with the full conversation history."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:60
msgid "A new [Kirigami](https://kde.org/products/kirigami/)-based user interface means you can run KDE Connect not only on Android, but also on all those mobile Linux platforms we'll be seeing in upcoming devices like the PinePhone and the Librem 5. The Kirigami interface also provides new features for desktop-to-desktop users, such as media control, remote input, device ringing, file transfer and running commands."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:62
#, no-wrap
msgid "{{<img src=\"kdeconnect2.png\" style=\"max-width: 600px\" caption=\"The new interface on desktop\" >}}\n"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:64
msgid "You could already use KDE Connect to control the volume of media playing on your desktop, but now you can use it to also control your system's global volume from your phone -- super handy when using your phone as a remote. When giving a talk, you can also control your presentation using KDE Connect to flip forward and back through your slides."
msgid "Another feature that has been around for while is how you can use KDE Connect to send a file to your phone, but what's new in this version is that you can have your phone immediately open the file once it is received. KDE Itinerary uses this to send travel information to your phone from within KMail."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:70
msgid "In a related note, you can now also send files from Thunar (Xfce's file manager) and Elementary applications such as Pantheon Files. Displaying progress of the copy of multiple files has been improved a lot and files received from Android now show their correct modification time."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:72
msgid "When it comes to notifications, you can now trigger actions from Android notifications from the desktop and KDE Connect uses advanced features from Plasma's notification center to provide better notifications. The pairing confirmation notification does not time out so you can't miss it any more."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:74
msgid "Finally, if you are using KDE Connect from the command line, *kdeconnect-cli* now features improved *zsh* autocompletion."
msgid "[Gwenview](https://userbase.kde.org/Gwenview) now lets you adjust the JPEG compression level when you save images you have edited. Developers have also improved the performance for remote images and Gwenview can now import photos both to or from remote locations."
msgstr ""
#. type: Title ##
#. +> trunk5
#: content/2019-12-apps-update/_index.md:79
#, no-wrap
msgid "[Okular](https://kde.org/applications/office/org.kde.okular) support .cb7 format"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:82
msgid "[Okular](https://kde.org/applications/office/org.kde.okular), the document viewer that lets you read, annotate and verify all sorts of documents, including PDFs, EPubs, ODTs and MDs, now also supports files using the .cb7 comic book format."
msgstr ""
#. type: Title ##
#. +> trunk5
#: content/2019-12-apps-update/_index.md:83
#, no-wrap
msgid "[Elisa](https://kde.org/applications/multimedia/org.kde.elisa): Simple but Complete Music Player"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:86
msgid "[Elisa](https://kde.org/applications/multimedia/org.kde.elisa) is a KDE music player that combines simplicity with an elegant and modern interface. In its latest version, Elisa has optimized its looks to adapt better to High DPI screens. It also integrates better with other KDE applications and has acquired support for KDE's global menu system."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:88
msgid "Indexing music files has also improved and Elisa now supports web radios and ships with a few examples for you to try."
msgid "[Spectacle](https://kde.org/applications/utilities/org.kde.spectacle) is Touchscreen-Ready"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:94
msgid "[Spectacle](https://kde.org/applications/utilities/org.kde.spectacle), KDE's default screen-grabbing program, is another KDE application that has evolved to acquire touchscreen capabilities: Its new touch-friendly drag handler makes it much easier to drag rectangles to capture the parts of the desktop you want on tactile-enabled devices."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:96
msgid "Other improvements are the new autosave function, which comes in handy for rapidly taking multiple screenshots, and the animated progress bars, which make sure you can clearly see what Spectacle is doing."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:98
#, no-wrap
msgid "{{<img style=\"max-width:500px\" src=\"spectacle.png\" caption=\"Spectacle new drag handler\" >}}\n"
msgid "The new release of [Plasma Browser Integration](https://community.kde.org/Plasma/Browser_Integration) now features a blacklist for the media controls functionality. This is useful for when you visit a site with a lot of media you can play, which can make it difficult to select what you want to control from your desktop. The blacklist lets you exclude these sites from the media controls."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:104
msgid "The new version also lets you keep the origin URL in file metadata and adds support for the Web Share API. The Web Share API lets browsers share links, text and files with other apps in the same way KDE apps do, improving the integration of non-native browsers like Firefox, Chrome/Chromium and Vivaldi, with the rest of KDE's applications."
msgid "Quite a few of KDE applications can be downloaded from the Microsoft Store. Krita and Okular have been there for a while, and they are joined now by [Kile](https://kde.org/applications/office/org.kde.kile), a user-friendly LaTeX editor."
msgid "Which brings us to new arrivals: [SubtitleComposer](https://invent.kde.org/kde/subtitlecomposer), an application that lets you easily create subtitles for videos, is now in the KDE Incubator, on track to become a full member of KDE's applications family. Welcome!"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:118
msgid "Meanwhile, [plasma-nano](https://invent.kde.org/kde/plasma-nano), a minimal version of Plasma designed for embedded devices was moved into the Plasma repos ready for release with 5.18."
msgstr ""
#. type: Title ##
#. +> trunk5
#: content/2019-12-apps-update/_index.md:119
#, no-wrap
msgid "Release 19.12"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2019-12-apps-update/_index.md:121
msgid "Some of our projects release on their own timescale and some get released en-masse. The 19.12 bundle of projects was released today and should be available through app stores and distros soon. See the [19.12 releases page](https://www.kde.org/announcements/releases/19.12). This bundle was previously called KDE Applications but has been de-branded to become a release service to avoid confusion with all the other applications by KDE and because it is dozens of different products rather than a single whole."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:3
msgid "title: KDE's January 2020 Apps Update"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:5
msgid "publishDate: 2020-01-09 12:00:00"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:14
msgid "The year is 2020, we are living in the future, let's see what KDE apps has brought us in the last month!"
msgstr ""
#. type: Title ##
#. +> trunk5
#: content/2020-01-apps-update/_index.md:15
#, no-wrap
msgid "KTimeTracker ported to KDE Frameworks 5"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:21
msgid "The long-awaited modernized version of KTimeTracker is finally released. The application is a personal time tracker for busy people which is now available on Linux, FreeBSD and Windows. Over the course of 2019 it had been ported to Qt5 and KDE Frameworks after being unmaintained since around 2013."
msgid "The new version is also polished and slightly modernised with the most noticeable new features being the new Task Time Editing dialog and live preview in the Export dialog as seen in the picture below."
msgid "https://download.kde.org/stable/ktimetracker/5.0.1/src/ It is available through your Linux distro or as a [Windows installer](https://download.kde.org/stable/ktimetracker/5.0.1/win64/) and there's even [untested MacOS builds](https://binary-factory.kde.org/job/KTimeTracker_Nightly_macos/) built nightly."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:34
msgid "[The release is announced in the blog of the maintainer Alexander Potashev](https://aspotashev.blogspot.com/2019/12/ktimetracker-501-released.html)"
msgstr ""
#. type: Title ##
#. +> trunk5
#: content/2020-01-apps-update/_index.md:35
#, no-wrap
msgid "KStars 3.3.9"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:38
msgid "Astronomy program [KStars got new features in 3.3.9](http://knro.blogspot.com/2020/01/kstars-v339-is-released.html)."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:40
msgid "Images can have fine changes in Shadows, Midtones, and Highlights allowing the faintest of stars to be seen."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:42
msgid "Alternative constellations from the Western Sky Culture which is fascinating to [read about](https://sternenkarten.com/2019/12/27/kstars-clines/)."
msgid "[KStars is available for](https://edu.kde.org/kstars/) Android, Windows, MacOS, Snap store and from your Linux distro."
msgstr ""
#. type: Title ##
#. +> trunk5
#: content/2020-01-apps-update/_index.md:47
#, no-wrap
msgid "Common Frameworks - KNewStuff"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:50
msgid "Here on the Apps Update we focus on the apps rather than coding libraries. But new features in the common libraries will mean new features in all your apps :)"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:52
msgid "This month saw a redesigned UI for KNewStuff, the framework to download addons for your applications. The browse and download dialog was redesigned and the comments section can now be filtered. It'll be appearing in all your apps and settings modules shortly starting with the Global Theme module in System Settings."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:54
#, no-wrap
msgid "{{< img src=\"knewstuff-comments.png\" caption=\"Filters on Comments\" alt=\"Filters on Comments\" style=\"width: 800px\">}}\n"
msgid "[KDevelop's monthly bugfix update 5.4.6](https://www.kdevelop.org/news/kdevelop-546-released) fixed a longstanding problem where the GPL and LGPL headers were mixed up, grab it from your distro or Appimage to make sure your licencing is correct."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:62
msgid "[Latte Dock 0.9.7](https://psifidotos.blogspot.com/2019/12/latte-bug-fix-release-v097.html) fixed some features with Qt 5.14 and removed some crashes."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:64
msgid "Dolphin Plugins 19.12.1 fixed a broken SVN Commit dialog."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:66
msgid "There was improved file indexing in Elisa. It also fixed some compilation issues on Android and without Baloo."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:68
msgid "The new release of KPat was declaired to have no [OARS](https://hughsie.github.io/oars/index.html) relevant age restrictions."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:70
msgid "Okular fixed a crash when closing the print preview dialog."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:72
msgid "This month's release of Kdenlive video editor had an impressive number of fixes best of all was updating the [screenshots](https://kde.org/applications/multimedia/org.kde.kdenlive) used in the meta info. It also has dozens of improvements and fixes in timeline and preview handling."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:74
msgid "New JavaScript support is now in Kate's [LSP](https://langserver.org/) client."
msgstr ""
#. type: Title ##
#. +> trunk5
#: content/2020-01-apps-update/_index.md:75
#, no-wrap
msgid "Enjoy KDE on the Flathub Store"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:78
msgid "KDE is embracing all the app stores. We can now deliver more and more of our programs directly to you the user. One of the leading app stores on Linux is [Flathub](https://flathub.org/home) which uses the FlatPak format."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:80
msgid "You may well already have Flatpak and Flathub configured on your system and ready to use in Discover or other app installers. For example KDE neon has set it up by default on installs for over a year now. If not it's a quick [setup process](https://flatpak.org/setup/) for all the major distros."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:82
msgid "If you're interested in the techy details you can browse [KDE's Flatpak packaging repo](https://phabricator.kde.org/source/flatpak-kde-applications/) and read the [KDE Flatpak guide](https://community.kde.org/Guidelines_and_HOWTOs/Flatpak)."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:84
msgid "But probably what you're interested in is the apps so take a look at what the [Flathub store has under KDE](https://flathub.org/apps/search/kde)."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:86
#, no-wrap
msgid "{{< img src=\"flathub.png\" alt=\"KDE on Flathub\" style=\"width: 800px\" >}}\n"
msgstr ""
#. type: Title ##
#. +> trunk5
#: content/2020-01-apps-update/_index.md:87
#, no-wrap
msgid "LabPlot now on Chocolatey"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:90
msgid "[Chocolatey](https://chocolatey.org/) is a package manager for Windows. If you want full control over what software is installed on your Windows machine or whole office of machines then Chocolatey gives you easy control over that just like you are used to on Linux."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:92
msgid "[LabPlot](https://chocolatey.org/packages/labplot) is KDE's app for interactive graphing and analysis of scientific data and it is now available through Chocolatey. Give it a try!"
msgid "{{< img src=\"labplot.png\" alt=\"LabPlot on Chocolatey\" style=\"width: 800px\" >}}\n"
msgstr ""
#. type: Title ##
#. +> trunk5
#: content/2020-01-apps-update/_index.md:97
#: content/2020-02-apps-update/_index.md:69
#: content/2020-03-apps-update/_index.md:56
#, no-wrap
msgid "Website Updates"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:100
msgid "The recently revived KDE Web Team has been updating a bunch of our older themed sites. The newly relaunched [KPhotoAlbum](https://www.kphotoalbum.org/) website is a lovely example, updated and refreshed for our photo storage and search app."
msgid "And if you want to show off a simple to use but full featured local music player but were ashamed by the old looking website, [JuK](https://juk.kde.org/) has just had an updated website too."
msgstr ""
#. type: Title ##
#. +> trunk5
#: content/2020-01-apps-update/_index.md:105
#, no-wrap
msgid "Releases 19.12.1"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-01-apps-update/_index.md:107
msgid "Some of our projects release on their own timescale and some get released en-masse. The 19.12.1 bundle of projects was released today and should be available through app stores and distros soon. See the [19.12.1 releases page](https://www.kde.org/info/releases-19.12.1.php). This bundle was previously called KDE Applications but has been de-branded to become a release service to avoid confusion with all the other applications by KDE and because it is dozens of different products rather than a single whole."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-02-apps-update/_index.md:3
msgid "title: KDE's February 2020 Apps Update"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-02-apps-update/_index.md:5
msgid "publishDate: 2020-02-06 12:00:00"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-02-apps-update/_index.md:14
msgid "This month sees a plethora of bugfix releases. While we all might like new features, we know that people love when mistakes and crashes get tidied up and solved too!"
msgstr ""
#. type: Title ##
#. +> trunk5
#: content/2020-02-apps-update/_index.md:15
#: content/2020-03-apps-update/_index.md:13
#, no-wrap
msgid "New releases"
msgstr ""
#. type: Title ##
#. +> trunk5
#: content/2020-02-apps-update/_index.md:17
#, no-wrap
msgid "KDevelop 5.5"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-02-apps-update/_index.md:20
msgid "The big release this month comes from [KDevelop 5.5](https://www.kdevelop.org/news/kdevelop-550-released), the IDE that makes writing programs in C++, Python and PHP easier. We have fixed a bunch of bugs and tidied up a lot of KDevelop's code. We added Lambda init captures in C++, configurable predefined checkset selections are now in for Clazy-tidy and Clang, and look-ahead completion now tries harder. PHP gets PHP 7.4's typed properties and support was added for array of type and class constant visibility. In Python, support has now been added for Python 3.8."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-02-apps-update/_index.md:22
msgid "KDevelop is available from your Linux distro or as an AppImage."
msgid "[Zanshin](https://zanshin.kde.org/) is our TODO list tracker which integrates with Kontact. Recent releases of Kontact had broken Zanshin and users were left not knowing what tasks to carry out next. But this month, a release was made to [get it working again](https://jriddell.org/2020/01/14/zanshin-0-5-71/). We can now all easily find the tasks that we need to get on with!"
msgid "[Okteta](https://kde.org/applications/utilities/org.kde.okteta), KDE's Hex editor, had a bugfix release and includes a new feature: a CRC-64 algorithm for the checksum tool. Okteta also updates the code for new Qt and KDE Frameworks."
msgid "[KMyMoney](https://kmymoney.org/), the KDE app that helps you manage your finances, [included several bugfixes](https://kmymoney.org/changelogs/kmymoney-5-0-8-release-notes.html) and an enhancement that added support for check forms with split protocol"
msgid "Keysmith is a two-factor code generator for Plasma Mobile and Plasma Desktop that uses oath-toolkit. The user interface is written in the Kirigami, making it slick on any size of screen. Expect releases soon."
msgid "[Chocolatey](https://chocolatey.org) is a package manager for the Windows operating system. Chocolatey deals with installing and updating all the software on the system and can make the life smoother for Windows users."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-02-apps-update/_index.md:66
msgid "[KDE has an account on Chocolatey](https://chocolatey.org/profiles/KDE) and you can install Digikam, Krita, KDevelop and Kate through it. Installation is very easy: All you have to do is `choco install kdevelop` and Chocolatey will do the rest. Chocolatey maintainers have high standards so you can be sure the packages are tested and secure."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-02-apps-update/_index.md:68
msgid "If you are a KDE app maintainer, do consider getting your app added, and if you're a large Windows rollout manager, do consider this for your installs."
"Our web team continues to update our online presence and has recently refreshed the [KMyMoney website](https://kmymoney.org).\n"
msgstr ""
#. type: Title #
#. +> trunk5
#: content/2020-02-apps-update/_index.md:74
#, no-wrap
msgid "Releases 19.12.2"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-02-apps-update/_index.md:77
msgid "Some of our projects release on their own timescale and some get released en-masse. The 19.12.2 bundle of projects was released today and should be available through app stores and distros soon. See the [19.12.2 releases page](https://www.kde.org/info/releases-19.12.2.php) for details. This bundle was previously called KDE Applications but has been de-branded to become a release service to avoid confusion with all the other applications by KDE and because there are dozens of different products rather than a single whole."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-02-apps-update/_index.md:79
#: content/2020-03-apps-update/_index.md:67
msgid "Some of the fixes included in this release are:"
msgstr ""
#. type: Bullet: '* '
#. +> trunk5
#: content/2020-02-apps-update/_index.md:84
msgid "The [Elisa](https://kde.org/applications/multimedia/org.kde.elisa) music player now handles files that do not contain any metadata"
msgstr ""
#. type: Bullet: '* '
#. +> trunk5
#: content/2020-02-apps-update/_index.md:84
msgid "Attachments saved in the *Draft* folder no longer disappear when reopening a message for editing in [KMail](https://kde.org/applications/internet/org.kde.kmail2)"
msgstr ""
#. type: Bullet: '* '
#. +> trunk5
#: content/2020-02-apps-update/_index.md:84
msgid "A timing issue that could cause the [Okular](https://kde.org/applications/office/org.kde.okular) document viewer to stop rendering has been fixed"
msgstr ""
#. type: Bullet: '* '
#. +> trunk5
#: content/2020-02-apps-update/_index.md:84
msgid "The [Umbrello](https://umbrello.kde.org/) UML designer now comes with an improved Java import"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-02-apps-update/_index.md:85
msgid "[19.12.2 release notes](https://community.kde.org/Releases/19.12_Release_Notes) • [Package download wiki page](https://community.kde.org/Get_KDE_Software_on_Your_Linux_Distro) • [19.12.2 source info page](https://kde.org/info/releases-19.12.2) • [19.12.2 full changelog](https://kde.org/announcements/changelog-releases.php?version=19.12.2)"
msgid "February started with a long awaited update to our microblogging app [Choqok](https://choqok.kde.org/news/2020/02/04/choqok-1-7-released.html)."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-03-apps-update/_index.md:20
msgid "Important fixes include the 280 character limit on Twitter, allowing disabling accounts and support extended tweets."
msgid "Our disk formatting program Partition Manager got a new release with lots of work done to the library KPMCore which is also used by the Calamares distro installer. The app itself added support for Minix file systems."
msgid "If you have hundreds or even thousands of images on your hard drive, it becomes impossible to remember the story behind every single image or the names of the persons photographed. KPhotoAlbum was created to help you describe your images and then search the big pile of pictures quickly and efficiently."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-03-apps-update/_index.md:34
msgid "This release particularly brings huge performance improvements when tagging a large number of images and performance improvements for thumbnail view. Kudos to Robert Krawitz for again diving into the code and finding places for optimization and removal of redundancy!"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-03-apps-update/_index.md:36
msgid "Additionally, this release adds support for KDE's purpose plugin framework."
msgid "The MP3 ID tag editor Kid3 was moved into kdereview, the first step to getting new releases."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-03-apps-update/_index.md:44
msgid "And the Rocket.chat app Ruqola passed kdereview and was moved to be ready to release. However the word from the maintainer Laurent Montel is that a rewrite with Qt Widgets is planned so there's still a lot of work to be done."
msgid "New in the Microsoft Store for Windows is [Elisa](https://www.microsoft.com/en-gb/p/elisa/9pb5md7zh8tl?activetab=pivot:overviewtab)."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-03-apps-update/_index.md:53
msgid "A modern and beautiful music player made with love by KDE. Browse, and play your music very easily! Elisa should be able to read almost any music files. Elisa is made to be accessible to everybody."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-03-apps-update/_index.md:55
msgid "Meanwhile Digikam is ready to be submitted to the Microsoft Store."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-03-apps-update/_index.md:59
msgid "[KDE Connect](https://kdeconnect.kde.org/), our nifty phone and desktop integration tool, got a new website."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-03-apps-update/_index.md:61
msgid "[Kid3](https://kid3.kde.org/) has a shiny new website with news and download links from all the stores it's available from."
msgstr ""
#. type: Title ##
#. +> trunk5
#: content/2020-03-apps-update/_index.md:62
#, no-wrap
msgid "Releases 19.12.3"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-03-apps-update/_index.md:65
msgid "Some of our projects release on their own timescale and some get released en-masse. The 19.12.3 bundle of projects was released today and should be available through app stores and distros soon. See the [19.12.3 releases page](https://www.kde.org/info/releases-19.12.3.php) for details. This bundle was previously called KDE Applications but has been de-branded to become a release service to avoid confusion with all the other applications by KDE and because there are dozens of different products rather than a single whole."
msgstr ""
#. type: Bullet: '* '
#. +> trunk5
#: content/2020-03-apps-update/_index.md:71
msgid "Support for file attributes for SMB shares has been improved, [various commits](https://cgit.kde.org/kio-extras.git/log/?h=release/19.12)"
msgstr ""
#. type: Bullet: '* '
#. +> trunk5
#: content/2020-03-apps-update/_index.md:71
msgid "K3b now accepts WAV files as audio files [BUG 399056](https://bugs.kde.org/show_bug.cgi?id=399056) [Commit](https://cgit.kde.org/k3b.git/commit/?h=release/19.12&id=2491cc70f9ffb129cf49633cbdc4f0d77789677d)"
msgstr ""
#. type: Bullet: '* '
#. +> trunk5
#: content/2020-03-apps-update/_index.md:71
msgid "Gwenview now can load remote images via https [Commit](https://cgit.kde.org/gwenview.git/commit/?h=release/19.12&id=9973a097d30a91dd50a4d23388b0b2b00eeeb626)"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-03-apps-update/_index.md:72
msgid "💻 [19.12 release notes](https://community.kde.org/Releases/19.12_Release_Notes) for information on tarballs and known issues. 💻 [Package download wiki page](https://community.kde.org/Get_KDE_Software_on_Your_Linux_Distro) 💻 [19.12.3 source info page](https://kde.org/info/releases-19.12.3) 💻 [19.12 full changelog](https://kde.org/announcements/changelog-releases.php?version=19.12.3) 💻"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:3
msgid "title: KDE's April 2020 Apps Update"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:5
msgid "publishDate: 2020-04-23 16:00:00"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:14
msgid "A new bundle of KDE applications is here! In these releases, you can expect to find more features, stability improvements, and more user-friendly tools that will help you work more effectively."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:16
msgid "There are dozens of changes to look forward to in most of your favorite applications. Take Dolphin, for example. Windows Samba shares are now fully discoverable."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:18
msgid "On the topic of playing music: the Elisa music player is adding features by leaps and bounds. This release brings a new \"Now Playing\" view, easy accessibility through the system tray, and an option to minimize the playlist whenever you want. Thanks to the recently-added visual shuffle mode, it's much easier to rearrange your music in the playlists."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:20
msgid "These are just the highlights of what's new in KDE's applications this month. Read on to find out about everything we've prepared for you."
msgstr ""
#. type: Title ##
#. +> trunk5
#: content/2020-04-apps-update/_index.md:21
#, no-wrap
msgid "[Okular](https://okular.kde.org)"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:24
msgid "Okular is KDE's application that allows you to read PDFs, Markdown documents, comic books, and many other document formats. In this release, Okular received some accessibility improvements for desktop and touchscreen users alike. For the former, Okular now implements smooth scrolling both when you are using the mouse wheel and the keyboard. For touchscreen users, the latest version of Okular comes with inertial scrolling."
msgid "KDE’s powerful file manager Dolphin adds new features, allowing you to better interact with remote file systems like Samba shares and SSH servers. Now you can start watching movies stored on remote sites without having to download them, and instead stream them directly from the cloud to your player through Dolphin."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:32
msgid "In a similar vein, connecting with Windows Samba shares and taking advantage of all the services they offer has never been easier, as Samba shares are now discoverable via the WS-Discovery protocol used by modern versions of Windows. This allows you to seamlessly integrate your Linux box into a Windows network."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:34
#, no-wrap
msgid "As for the news from the usability department: you don’t need your mouse anymore to move focus to and from the terminal panel. Now you can just use the keyboard shortcut <kbd>Ctrl</kbd> + <kbd>Shift</kbd> + <kbd>F4</kbd>. Another long-awaited feature is searching for files not just by their names or content, but also by their tags.\n"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:36
msgid "Support for 7Zip files is now built into Dolphin, meaning you can navigate these compressed files as if they were file system folders. When you install external search applications like KFind, Dolphin lets you quickly access them by creating a link."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:38
#, no-wrap
msgid "Finally, a seemingly small feature that can be a big time-saver is the new \"Duplicate\" function. Select one or more files or folders, hit <kbd>Ctrl</kbd> + <kbd>D</kbd> (or right-click and choose \"Duplicate Here\") and - bam! A copy of each selected item will appear right alongside the originals.\n"
msgid "Lokalize is a utility you can use to translate gettext and xliff files. It now supports the Language-Tool grammatical correction, which helps translators by highlighting grammatical errors in the text."
msgid "KMail is KDE's most popular email client and part of Kontact, a suite of programs that help you manage your emails, contacts, and tasks."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:50
msgid "Quite a few improvements are included in this new release. For starters, email messages can now be easily exported to PDF, and messages formatted with Markdown are displayed better. The security aspect has also received some attention. More specifically, KMail shows a warning when the message composer opens after clicking a link that asks you to attach a file."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:52
msgid "KMail is KDE's most popular email client and part of Kontact, a suite of programs that help you manage your emails, contacts, and tasks. Quite a few improvements are included in this new release. For starters, email messages can now be easily exported to PDF, and messages formatted with Markdown are displayed better. The security aspect has also received some attention. More specifically, KMail shows a warning when the message composer opens after clicking a link that asks you to attach a file."
msgid "Konsole is a terminal emulator that you use to run command-line instructions, processes, and programs. The latest version of Konsole lets you use the <kbd>Alt</kbd> key + a number key to jump directly to any of the first 9 tabs.\n"
msgid "Gwenview is KDE's favorite image viewer, and in this version, the developers have resolved two major issues. The application no longer hangs on launch when the system clipboard contains text from KDE Connect, and importing photos to or from remote locations has been fixed."
msgid "Elisa is a simple and popular music player, and this release features the \"Now Playing\" view that makes it more attractive."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:68
msgid "It's not all about the looks, though. Elisa is also more functional, as you can now access it through the system tray and minimize the playlist whenever you want. This means you can keep listening to your favorite music even when the main Elisa window is closed. The new visual shuffle mode makes it easier to rearrange your music in the playlists, and shows you which song will be played next."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:70
msgid ""
msgstr ""
#. type: Title ##
#. +> trunk5
#: content/2020-04-apps-update/_index.md:71
#, no-wrap
msgid "[Kdenlive](https://kdenlive.org)"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:74
msgid "Kdenlive is KDE's advanced video-editing application, and the new version makes editing faster thanks to its configurable preview resolution. The preview also improves multitrack viewing, making it easy to select tracks from the ones you are editing all at the same time."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:76
msgid "Down on the timeline, the team has improved snapping clips by only snapping on active tracks. They have also fixed the group snap feature and added a shortcut to bypass snapping on move. Another thing you can now do is directly drop your files (videos, music and images) from your file explorer into the timeline. The new \"zooming on keyframes\" feature will help carry out more precise work. Professional video editors and users coming from other editing tools will undoubtedly appreciate the OpenTimelineIO import/export feature."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:78
msgid "This release of Kdenlive also comes with many bug fixes, like the ones for the Motion Tracker, which was broken on some systems. It now lets you add a Pitch compensation filter, as well as add \"Move and resize\" to a Rotoscoping shape. The crash of the DVD Wizard and a bug that plagued the changing of the record volume from the mixer have also been sorted. The Kdenlive team has also added tagging, rating, and filtering functionality to the project bin."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:80
msgid "The new Windows version of Kdenlive also comes with fixes to the timeline dialogs, which previously didn't accept keyboard input. Additionally, you can now select the audio backend on Windows."
msgid "Yakuake is a terminal window that you can pull down from the top of the Plasma desktop by pressing <kbd>F12</kbd>. It is handy for running quick instructions on the command-line, and then moving out of the way.\n"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:88
msgid "When you open new tabs or split panes in this version of Yakuake, you can now start them in the same directory as the current tab/split. You can also resize Yakuake’s window vertically by dragging on its bottom bar."
msgstr ""
#. type: Title ##
#. +> trunk5
#: content/2020-04-apps-update/_index.md:89
#, no-wrap
msgid "System Settings"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:92
msgid "The online accounts integration page in System Settings lets you configure things like your Google account, or set up access to your Nextcloud account. The page has been completely overhauled, and now sports a clean, modern look with a much more reliable functionality."
msgid "KDE Connect is an application that helps you integrate your phone with your desktop and vice versa. One of the newest features shipped with this release is the ability to start new conversations with the SMS app."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:98
msgid "Other changes include remote media players now showing up in the media player applet, a new set of connection status icons, and improved call notification handling."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:100
msgid "In the bug fix department, the error that caused file sharing to block the calling application has been resolved, and the problems with transferring really large files have been sorted out."
msgid "Spectacle, KDE's screen-capturing software, added usability features and resolved some papercuts. One of them prevented you from copying a screenshot to the clipboard when you opened Spectacle from the command-line with the --nonotify option. Although this may have been a niche problem, the point is now you can do exactly that. Likewise, older versions had problems when you tried to drag a screenshot from Spectacle to the default filename pattern that included subfolders. Those problems have been solved."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:106
msgid "Another useful improvement in the new version of Spectacle comes in the form of “Defaults” and “Revert” buttons. You can use them to go back to a prior configuration, or even remove all prior custom configurations and restore everything to its default value."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:108
msgid "Spectacle will not only remember your default configuration, but also the last used screenshot area. This helps you stay consistent, making it easier to create shots of the same shape and size as your previous ones."
msgstr ""
#. type: Title ##
#. +> trunk5
#: content/2020-04-apps-update/_index.md:109
#, no-wrap
msgid "[Krita](https://krita.org/en/) 4.2.9"
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:112
msgid "There were a number of technical upgrades behind the scenes in this release but also some new features such as two new options added to the Color Smudge brush — “Airbrush” and “Airbrush Rate.” Color Smudge also gains a new Ratio setting which allows using the different sensors to make the shape of the brush flatter. A new \"Split Layer into Selection Mask\" feature allows you to create a new layer for every color in the active layer. And smoother paint brush outlines which don't flicker when you hover over the canvas."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:114
msgid "There were a number of technical upgrades behind the scenes in this release but also smoother paint brush outlines which don't flicker when you hover over the canvas. “Airbrush” and “Airbrush Rate” was added to the Color Smudge brush, and a new Ratio setting, also for the Color Smudge brush, which allows making the shape of the brush flatter using the different sensors. A new Split Layer into Selection Mask feature allows you to create a new layer for every color in the active layer."
msgid "The 3.0.4 release of Smb4K fixes several issues and crashes, especially in the mounter. It also makes Smb4K compilable again with Qt version 5.9 and lower."
msgid "This major release of the plugin which integrates Google Drive with KDE's applications adds a support for the Shared Drives feature of Google Drive."
msgstr ""
#. type: Plain text
#. +> trunk5
#: content/2020-04-apps-update/_index.md:125
msgid "It also includes a new \"Copy Google URL to clipboard\" action in the Dolphin context-menu."
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "Why Donate?"
+msgid "Resources"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "Donate via PayPal"
+msgid "Press Contact"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "RSS Feed"
+msgid "International Websites"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "Download KDE Software"
+msgid "KDE Timeline"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "API Documentation"
+msgid "Develop"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "Code of Conduct"
+msgid "Why Donate?"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "Products"
+msgid "Code of Conduct"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "Develop"
+msgid "Donate via PayPal"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "Development and communication of KDE software"
+msgid "Return to kde.org"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "Destinations"
+msgid "Releases"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "Other ways to donate"
+msgid "KDE Patrons"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "Releases"
+msgid "Learn More"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "Learn More"
+msgid "Products"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "Click here to browse"
+msgid "KDE applications"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "International Websites"
+msgid "Development and communication of KDE software"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "Donate to KDE"
+msgid "Visit the KDE MetaStore"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "Return to kde.org"
+msgid "API Documentation"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "Announcements"
+msgid "RSS Feed"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "Screenshots"
+msgid "News & Press"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "Press Contact"
+msgid "Other ways to donate"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "Show your love for KDE! Purchase books, mugs, apparel, and more to support KDE."
+msgid "Destinations"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "Visit the KDE MetaStore"
+msgid "Screenshots"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "Resources"
+msgid "Announcements"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "KDE applications"
+msgid "Download KDE Software"
msgstr ""
#. +> trunk5
#: i18n/en.yaml:0
-msgid "KDE Patrons"
+msgid "Show your love for KDE! Purchase books, mugs, apparel, and more to support KDE."