diff --git a/KritaFAQ.rst b/KritaFAQ.rst --- a/KritaFAQ.rst +++ b/KritaFAQ.rst @@ -49,9 +49,9 @@ Krita should automatically use the system language. If that is not the case, please follow these steps: -#. Settings --> Switch Application Language. A small window will appear. -#. Click Primary language and select your language. -#. Click OK to close the window. +#. :menuselection:`Settings --> Switch Application Language`. A small window will appear. +#. Click :guilabel:`Primary language` and select your language. +#. Click :guilabel:`OK` to close the window. #. Restart krita and it will be displayed in your selected language! 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. @@ -114,7 +114,7 @@ :file:`%LOCALAPPDATA%\\Packages\\49800Krita_{RANDOM STRING}\\LocalCache\\Local\\kritarc` -The random string depends on your installation/ +The random string depends on your installation. 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. @@ -172,7 +172,7 @@ 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. -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 INSert 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. +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. Windows: Can I use Krita with Sandboxie? ---------------------------------------- @@ -296,7 +296,7 @@ #. Put your stylus away from the tablet. #. Start Krita without using a stylus, that is using a mouse or a keyboard. -#. Press Shift key and hold it. +#. Press :kbd:`Shift` key and hold it. #. Touch a tablet with your stylus so Krita would recognize it. You will see a special dialog asking for the real screen resolution. Choose the correct value or enter it manually and press OK. diff --git a/contributors_manual/krita_manual_conventions.rst b/contributors_manual/krita_manual_conventions.rst --- a/contributors_manual/krita_manual_conventions.rst +++ b/contributors_manual/krita_manual_conventions.rst @@ -31,7 +31,7 @@ Sphinx specific docs: * `Sphinx' page on restructured text `_ -- This is useful for the specific sphinx directives and roles it uses to generate for example table of contents. -There's between the official reStructuredText and the sphinx docs multiple ways to do things. This document specifies the suggested conventions to go with. +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. .. contents:: @@ -41,7 +41,7 @@ Each page should start with the following three things: 1. A meta description - This is a general description of the page. It will be converted to a html meta tag which will be used by search engines:: + This is a general description of the page. It will be converted to an html meta tag which will be used by search engines:: .. meta:: :description: @@ -58,7 +58,7 @@ :license: GNU free documentation license 1.3 or later. 3. Indexing terms. - 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 following:: + 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:: .. index:: Keyword, Keyword with Spaces, ! Main Definition Keyword @@ -115,7 +115,7 @@ Linking to external pages is done with ```url`_`` and ```link name `_``, which'll become `link name `_. -Pandoc 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 to 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. +Pandoc 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. Footnotes and further reading ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -348,8 +348,8 @@ 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. -Admonishments and asides. -------------------------- +Admonishments and asides +------------------------ .. note:: @@ -409,15 +409,15 @@ .. Topic:: Horizontal Rulers - 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 then switching to a related section. It is therefore better to use headings or the ``.. Topic::`` directive. Headings also make it easier to read. + 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. ---------------- That said, horizontal rulers can be made with ``----``. .. rubric:: The rubric directive. -The rubric directive is a heading directive that at first glance looks like "topic", but where topic is over several paragraphs, rubric itself only deals with the header, like so:: +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:: .. rubric:: The rubric directive. @@ -433,8 +433,8 @@ Admonishments 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. -Code Snippets: --------------- +Code Snippets +------------- ``Inline code snippets`` are done with ````backticks````. @@ -496,8 +496,8 @@

this is a paragraph.

-Other preformatted text. ------------------------- +Other preformatted text +----------------------- | One can diff --git a/contributors_manual/krita_manual_readme.rst b/contributors_manual/krita_manual_readme.rst --- a/contributors_manual/krita_manual_readme.rst +++ b/contributors_manual/krita_manual_readme.rst @@ -82,7 +82,7 @@ Try to keep the filenames the same, that's easier for us to copy over. 5. Upload the zip on phabricator. - 1. First, go to phabricator.kde.org and log in with you identity account. + 1. First, go to phabricator.kde.org and log in with your identity account. 2. Go to the `Manual Project Workboard`_ and there create a new task. 3. 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. 4. 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. @@ -160,13 +160,13 @@ Avoid using gifs (open for debate) 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. Keep it translation compatible - This consists of using svg for infographics, and using the appropriate markup for given text. + This consists of using svg for infographics, and using the appropriate markup for a given text. Regarding photos and paintings ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * 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 Rembrand'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. -* 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 mention it's a photograph. +* 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. * Photos can still be used for photobashing and the like, but only if it's obviously used in the context of photobashing. Regarding images in general @@ -194,7 +194,7 @@ * The master branch will be tagged with the old version. * The draft branch is first double checked that it has updated version number and updated epub cover. -The ``draft`` branch will not be merged until the day before a release to keep the pages in tact for long enough. +The ``draft`` branch will not be merged until the day before a release to keep the pages intact for long enough. 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? @@ -261,7 +261,7 @@ Proofreading ~~~~~~~~~~~~ -There's two types of proofreading that needs to be done. +There are two types of proofreading that needs to be done. The most important one is **reviewing changes people make**. You can do this on phabricator in two ways: @@ -284,9 +284,9 @@ Translating ~~~~~~~~~~~ -Translation of the manual is handled by the `KDE locatization community `_. To join the translation effort, go to the localization site, select the list of `translation teams `_, select the language you wish to translate for, and follow the instructions on the team page to get in contact with fellow translators. +Translation of the manual is handled by the `KDE localization community `_. To join the translation effort, go to the localization site, select the list of `translation teams `_, select the language you wish to translate for, and follow the instructions on the team page to get in contact with fellow translators. -The localisation 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. +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. 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. diff --git a/contributors_manual/optimising_images.rst b/contributors_manual/optimising_images.rst --- a/contributors_manual/optimising_images.rst +++ b/contributors_manual/optimising_images.rst @@ -23,7 +23,7 @@ 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! -So, instead, we'll make a screenshot. Depending on your operating system, there's several screenshot utilities available. +So, instead, we'll make a screenshot. Depending on your operating system, there are several screenshot utilities available. Windows ~~~~~~~ @@ -87,8 +87,8 @@ Linux ~~~~~ -Optimising PNGS -^^^^^^^^^^^^^^^ +Optimising PNG +^^^^^^^^^^^^^^ There is a whole laundry list of `PNG optimisation tools `_ 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: `PNGQuant `_ @@ -141,7 +141,7 @@ Sometimes, personal information gets embedded into an image file. Othertimes, we want to embed information into a file to document it better. -There's no less than 3 to 4 different ways of handling metadata, and metadata has different ways of handling certain files. +There are no less than 3 to 4 different ways of handling metadata, and metadata has different ways of handling certain files. The most commonly used tool to edit metadata is :program:`ExifTool`, another is to use :program:`ImageMagick`. diff --git a/general_concepts/colors/color_managed_workflow.rst b/general_concepts/colors/color_managed_workflow.rst --- a/general_concepts/colors/color_managed_workflow.rst +++ b/general_concepts/colors/color_managed_workflow.rst @@ -276,7 +276,7 @@ .. note:: - In some versions of Firefox, the colours actually look strange: This is a bug in Firefox, which is because it's `color management system is incomplete `_, save your png, jpg or tiff without an embedded profile to work around this. + In some versions of Firefox, the colours actually look strange: This is a bug in Firefox, which is because its `color management system is incomplete `_, save your png, jpg or tiff without an embedded profile to work around this. If you are preparing for print: diff --git a/general_concepts/colors/color_models.rst b/general_concepts/colors/color_models.rst --- a/general_concepts/colors/color_models.rst +++ b/general_concepts/colors/color_models.rst @@ -69,7 +69,7 @@ Intensity Similar to lightness, except it acknowledges that yellow (1,1,0) is lighter than blue (0,0,1). Ranges from 0 to 100. Luma (Y') - Similar to lightness and Intensity, except it weights the red, green and blue components based real-life measurements of how much light a color reflects to determine it's lightness. Ranges from 0 to 100. Luma is well known for being used in film-colour spaces. + Similar to lightness and Intensity, except it weights the red, green and blue components based real-life measurements of how much light a color reflects to determine its lightness. Ranges from 0 to 100. Luma is well known for being used in film-colour spaces. .. _model_gray: diff --git a/general_concepts/colors/linear_and_gamma.rst b/general_concepts/colors/linear_and_gamma.rst --- a/general_concepts/colors/linear_and_gamma.rst +++ b/general_concepts/colors/linear_and_gamma.rst @@ -116,7 +116,7 @@ If you use the color space browser, you can tell the TRC from the 'estimated gamma'(if it's 1.0, it's linear), or from the TRC widget in Krita 3.0, which looks exactly like the curve graphs above. -Even if you do not paint much, but are for example making textures for a videogame or rendering, using a linear space is very beneficial and will speed up the renderer a little, for it won't have to convert images on it's own. +Even if you do not paint much, but are for example making textures for a videogame or rendering, using a linear space is very beneficial and will speed up the renderer a little, for it won't have to convert images on its own. The downside of linear space is of course that white seems very overpowered when mixing with black, because in a linear space, light greys get more room. In the end, while linear space is physically correct, and a boon to work in when you are dealing with physically correct renderers for videogames and raytracing, Krita is a tool and no-one will hunt you down for preferring the dark mixing of the sRGB trc. diff --git a/general_concepts/colors/viewing_conditions.rst b/general_concepts/colors/viewing_conditions.rst --- a/general_concepts/colors/viewing_conditions.rst +++ b/general_concepts/colors/viewing_conditions.rst @@ -67,7 +67,7 @@ :align: center -So, by eye-balling your t-shirt's color during the evening, you took it's 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. +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. .. figure:: /images/en/color_category/White_point_mixup_ex1_03.png diff --git a/reference_manual/brushes/brush_engines/bristle_engine.rst b/reference_manual/brushes/brush_engines/bristle_engine.rst --- a/reference_manual/brushes/brush_engines/bristle_engine.rst +++ b/reference_manual/brushes/brush_engines/bristle_engine.rst @@ -101,7 +101,7 @@ .. image:: /images/en/Krita-tutorial7-B.I.3-2.png .. warning:: - Be aware that this feature is a bit buggy though. It's Supposed to take the color from the current layer, but some buggy behavior causes it to often use the last layer you've painted on (with a non-Bristle brush?) as source. To avoid these weird behaviors, stick to just one layer, or paint something on the current active layer first with another brush (such as a Pixel brush). + Be aware that this feature is a bit buggy though. It's supposed to take the color from the current layer, but some buggy behavior causes it to often use the last layer you've painted on (with a non-Bristle brush?) as source. To avoid these weird behaviors, stick to just one layer, or paint something on the current active layer first with another brush (such as a Pixel brush). Weighted saturation. Works by modifying the saturation with the following: diff --git a/reference_manual/brushes/brush_settings/brush_tips.rst b/reference_manual/brushes/brush_settings/brush_tips.rst --- a/reference_manual/brushes/brush_settings/brush_tips.rst +++ b/reference_manual/brushes/brush_settings/brush_tips.rst @@ -79,7 +79,7 @@ .. image:: /images/en/Krita_2_9_brushengine_brushtips_spikes.png Density - This decreases how much area the brush-covers over it's size: It makes it noisy. In the example below, the brush is set with density 0%, 50% and 100% respectively. + This decreases 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. .. image:: /images/en/Krita_2_9_brushengine_brushtips_density.png diff --git a/reference_manual/brushes/brush_settings/locked_brush_settings.rst b/reference_manual/brushes/brush_settings/locked_brush_settings.rst --- a/reference_manual/brushes/brush_settings/locked_brush_settings.rst +++ b/reference_manual/brushes/brush_settings/locked_brush_settings.rst @@ -23,7 +23,7 @@ .. image:: /images/en/Krita_2_9_brushengine_locking_01.png -To lock an option, |mouseright| the little lock icon next to the parameter name, and set it to 'Lock'.It will now be highlighted to show it's locked: +To lock an option, |mouseright| the little lock icon next to the parameter name, and set it to 'Lock'. It will now be highlighted to show it's locked: .. image:: /images/en/Krita_2_9_brushengine_locking_02.png diff --git a/reference_manual/dockers/animation_curve.rst b/reference_manual/dockers/animation_curve.rst --- a/reference_manual/dockers/animation_curve.rst +++ b/reference_manual/dockers/animation_curve.rst @@ -23,7 +23,7 @@ .. image:: /images/en/Animation_curves_1.png -Opacity should create a bright red curve line in the docker. On the left, in the layer list, you will see that the active layer has an outline of it's properties: A red 'opacity' has appeared. Pressing the red dot will hide the current curve, which'll be more useful in the future when more properties can be animated. +Opacity should create a bright red curve line in the docker. On the left, in the layer list, you will see that the active layer has an outline of its properties: A red 'opacity' has appeared. Pressing the red dot will hide the current curve, which'll be more useful in the future when more properties can be animated. .. image:: /images/en/Animation_curves_2.png diff --git a/reference_manual/dockers/histogram_docker.rst b/reference_manual/dockers/histogram_docker.rst --- a/reference_manual/dockers/histogram_docker.rst +++ b/reference_manual/dockers/histogram_docker.rst @@ -15,11 +15,11 @@ Histogram Docker ================ -A Histogram is a chart that shows how much of a specific channel value is used in an image. It's purpose is to give a really technical representation of the colors in an image, which can be helpful in decision making about filters. +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. .. image:: /images/en/Histogram_docker.png -The histogram docker was already available via :menuselection:`layers --> histogram`, but it's now a proper docker. +The histogram docker was already available via :menuselection:`Layers --> Histogram`, but it's now a proper docker. External Links: diff --git a/reference_manual/dockers/lut_management.rst b/reference_manual/dockers/lut_management.rst --- a/reference_manual/dockers/lut_management.rst +++ b/reference_manual/dockers/lut_management.rst @@ -20,7 +20,7 @@ The Look Up Table (LUT) Management docker controls the high dynamic range (HDR) painting functionality. Use Open Color IO - Use Open Color IO instead of Krita's internal color management. Open Color IO is a color management library. It is sometimes referred to as OCIO. This is required as Krita uses OCIO for it's HDR functionality. + Use Open Color IO instead of Krita's internal color management. Open Color IO is a color management library. It is sometimes referred to as OCIO. This is required as Krita uses OCIO for its HDR functionality. Color Engine Choose the engine. Configuration diff --git a/reference_manual/dockers/touch_docker.rst b/reference_manual/dockers/touch_docker.rst --- a/reference_manual/dockers/touch_docker.rst +++ b/reference_manual/dockers/touch_docker.rst @@ -14,9 +14,9 @@ Touch Docker ============ -The Touch Docker is a QML docker with several convenient actions on it. It's purpose it to aid those who use Krita on a touch-enabled screen by providing bigger gui elements. +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. -It's actions are... +Its actions are... +------------------------------+-----------------------+----------------------+ | Open File | Save File | Save As | diff --git a/reference_manual/filters/map.rst b/reference_manual/filters/map.rst --- a/reference_manual/filters/map.rst +++ b/reference_manual/filters/map.rst @@ -22,7 +22,7 @@ Small Tiles ----------- -Tiles the input image, using it's own layer as output. +Tiles the input image, using its own layer as output. .. index:: Height Map, Bumpmap, Normal Map diff --git a/reference_manual/main_menu/layers_menu.rst b/reference_manual/main_menu/layers_menu.rst --- a/reference_manual/main_menu/layers_menu.rst +++ b/reference_manual/main_menu/layers_menu.rst @@ -125,7 +125,7 @@ A complex bit of functionality to generate clone-layers for quick sprite making. Edit Metadata - Each layer can have it's own meta-data. + Each layer can have its own metadata. Histogram Shows a histogram. Merge With Layer Below diff --git a/reference_manual/main_menu/settings_menu.rst b/reference_manual/main_menu/settings_menu.rst --- a/reference_manual/main_menu/settings_menu.rst +++ b/reference_manual/main_menu/settings_menu.rst @@ -33,7 +33,7 @@ Dockers ------- -Krita subdivides the access of many of it's 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. +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. Learning to use dockers effectively is a key concept to maximizing your time using Krita. diff --git a/reference_manual/preferences/performance_settings.rst b/reference_manual/preferences/performance_settings.rst --- a/reference_manual/preferences/performance_settings.rst +++ b/reference_manual/preferences/performance_settings.rst @@ -29,7 +29,7 @@ Memory Limit 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. Internal Pool - A feature for advanced computer users. This allows :program:`Krita` to organise 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 it's place (a memory pool), so that it can find them easily, and it doesn't get lost amongst the other data (memory fragmentation). It will then also not have to spent time finding a spot for this data. + A feature for advanced computer users. This allows :program:`Krita` to organise 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 amongst the other data (memory fragmentation). It will then also not have to spent time finding a spot for this data. 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. diff --git a/reference_manual/resource_management/resource_brushtips.rst b/reference_manual/resource_management/resource_brushtips.rst --- a/reference_manual/resource_management/resource_brushtips.rst +++ b/reference_manual/resource_management/resource_brushtips.rst @@ -45,9 +45,9 @@ #. Change the name of the brush at the very top of the Brush Editor Settings dialog. Something like "Trees - Tall Evergreen" would be appropriate. #. Click the "Save to Presets" button #. 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!). -#. Once you're satisfied with your brush and it's settings you need to do one last thing (but click Overwrite Preset first!) +#. Once you're satisfied with your brush and its settings you need to do one last thing (but click Overwrite Preset first!) -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 "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 Preset` button and your brush and it's preview image will be saved. +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 "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 Preset` button and your brush and its preview image will be saved. An alternative method that requires a little more work but gives you greater control of the outcome is the following: diff --git a/reference_manual/resource_management/resource_gradients.rst b/reference_manual/resource_management/resource_gradients.rst --- a/reference_manual/resource_management/resource_gradients.rst +++ b/reference_manual/resource_management/resource_gradients.rst @@ -62,7 +62,7 @@ .. image:: /images/en/Krita_move_stop.png :align: center -A selected stop can have it's color and transparency changed using the color button and the opacity slider below. +A selected stop can have its color and transparency changed using the color button and the opacity slider below. .. image:: /images/en/Krita_stop_sudden_change.png :align: center diff --git a/reference_manual/tools/assistant.rst b/reference_manual/tools/assistant.rst --- a/reference_manual/tools/assistant.rst +++ b/reference_manual/tools/assistant.rst @@ -35,4 +35,4 @@ .. versionadded:: 4.1 Custom Color: - Custom color allows you to set a color and opacity per assistant, allowing for different colors on an assistant. To use this functionality, first 'select' an assistant by tapping it's move widget. Then go to the tool options docker to see the :guilabel:`Custom Color` check box. Check that, and then use the opacity and color buttons to pick either for this particular assistant. + Custom color allows you to set a color and opacity per assistant, allowing for different colors on an assistant. To use this functionality, first 'select' an assistant by tapping its move widget. Then go to the tool options docker to see the :guilabel:`Custom Color` check box. Check that, and then use the opacity and color buttons to pick either for this particular assistant. diff --git a/reference_manual/tools/colorize_mask.rst b/reference_manual/tools/colorize_mask.rst --- a/reference_manual/tools/colorize_mask.rst +++ b/reference_manual/tools/colorize_mask.rst @@ -74,7 +74,7 @@ If you want to edit the strokes again, re-enable :guilabel:`Edit Key Strokes`. -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 recognise a disabled colorize mask because it's name is stricken through. +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 recognise a disabled colorize mask because its name is stricken through. 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`. diff --git a/reference_manual/tools/contiguous_select.rst b/reference_manual/tools/contiguous_select.rst --- a/reference_manual/tools/contiguous_select.rst +++ b/reference_manual/tools/contiguous_select.rst @@ -42,7 +42,7 @@ Fuzziness This controls whether or not the contiguous selection sees another color as a border. Grow/Shrink selection. - This value extends/contracts the shape beyond it's initial size. + This value extends/contracts the shape beyond its initial size. Feathering This value will add a soft border to the selection-shape. Limit to Current Layer diff --git a/reference_manual/tools/fill.rst b/reference_manual/tools/fill.rst --- a/reference_manual/tools/fill.rst +++ b/reference_manual/tools/fill.rst @@ -29,7 +29,7 @@ Threshold Determines when the fill-tool sees another color as a border. Grow Selection - This value extends the shape beyond it's initial size. + This value extends the shape beyond its initial size. Feathering Radius This value will add a soft border to the filled-shape. Fill Entire Selection diff --git a/reference_manual/tools/multibrush.rst b/reference_manual/tools/multibrush.rst --- a/reference_manual/tools/multibrush.rst +++ b/reference_manual/tools/multibrush.rst @@ -37,4 +37,4 @@ Snowflake This works as a mirrored symmetry, but is a bit slower than symmetry+toolbar mirror mode. -The assistant and smoothing options work the same as in the :ref:`freehand_brush_tool`, though only on the real brush and not it's copies. +The assistant and smoothing options work the same as in the :ref:`freehand_brush_tool`, though only on the real brush and not its copies. diff --git a/tutorials/common_workflows.rst b/tutorials/common_workflows.rst --- a/tutorials/common_workflows.rst +++ b/tutorials/common_workflows.rst @@ -167,7 +167,7 @@ Starting from a value based underground ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -This method finds it's origins in old oil-painting practice: You first make an under-painting and then paint over it with colour, having the dark underground shine through. +This method finds its origins in old oil-painting practice: You first make an under-painting and then paint over it with colour, having the dark underground shine through. 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 colours of the image without changing the relative luminosity. This is useful, because humans are much more sensitive to tonal differences than difference in saturation and hue. This'll allow you to work in greyscale before going into colour for the polishing phase. diff --git a/untranslatable_pages/build_krita_with_docker.rst b/untranslatable_pages/build_krita_with_docker.rst --- a/untranslatable_pages/build_krita_with_docker.rst +++ b/untranslatable_pages/build_krita_with_docker.rst @@ -67,7 +67,7 @@ ./bin/enter -... now your are inside the container with all the deps prepared ... +... now you are inside the container with all the deps prepared ... .. code:: @@ -83,7 +83,7 @@ Extra developer tools --------------------- -To install QtCreator, enter container and start the installer, downloaded while fetching dependencies. Make sure you install it into '~/qtcreator' directory without any version suffixes, then you will be able to use the script below: +To install QtCreator, enter the container and start the installer, downloaded while fetching dependencies. Make sure you install it into '~/qtcreator' directory without any version suffixes, then you will be able to use the script below: .. code:: diff --git a/untranslatable_pages/cmake_settings_for_developers.rst b/untranslatable_pages/cmake_settings_for_developers.rst --- a/untranslatable_pages/cmake_settings_for_developers.rst +++ b/untranslatable_pages/cmake_settings_for_developers.rst @@ -13,7 +13,7 @@ CMake Settings for Developers ============================= -The `CMake `_ build system generators used by Krita is one of the most used build system generatorss in the C++ world. A build system is a system that describes how a an application should be built from source code. CMake generates a build system from the information given in the CMakeLists.txt and `*.cmake` files. It is a complete but rather unusual language. +The `CMake `_ build system generators used by Krita is one of the most used build system generators in the C++ world. A build system is a system that describes how an application should be built from source code. CMake generates a build system from the information given in the CMakeLists.txt and `*.cmake` files. It is a complete but rather unusual language. If you start working on Krita, you will need knowledge of two things: how to run the cmake generator, and which variables are important there, and how to edit the CMakeLists.txt files. This page tells you how to run the cmake generator. diff --git a/untranslatable_pages/reporting_bugs.rst b/untranslatable_pages/reporting_bugs.rst --- a/untranslatable_pages/reporting_bugs.rst +++ b/untranslatable_pages/reporting_bugs.rst @@ -15,7 +15,7 @@ Krita is, together with many other projects, part of the KDE community. Therefore, bugs for Krita are tracked in KDE's bug tracker: `KDE's bug tracker `_. The bug tracker is a tool for Krita's developers to help them manage bugs in the software, prioritize them and plan fixes. It is not a place to get user support! -The bug tracker contains two kinds of reports: bugs and wishes. Bugs are errors in Krita's code that interrupt using Krita. Wishes are feature requests: the reporder thinks some functionality is missing or would be cool to have. +The bug tracker contains two kinds of reports: bugs and wishes. Bugs are errors in Krita's code that interrupt using Krita. Wishes are feature requests: the reporter thinks some functionality is missing or would be cool to have. Do not just create a feature request in the bug tracker: follow `Feature Requests `_ to learn how to create a good feature request. @@ -56,7 +56,7 @@ Krita's chat channel is maintained on irc.freenode.net. Developers and users hang out to discuss Krita's development and help people who have questions. .. important:: - Most Krita developers live in Europe, and the channel is very quiet when it's night in Europe. You also have to patient: it may take some time for people to notice your question even if they are awake. + Most Krita developers live in Europe, and the channel is very quiet when it's night in Europe. You also have to be patient: it may take some time for people to notice your question even if they are awake. .. admonition:: Also ... @@ -94,7 +94,7 @@ - Hardware information: copy the information from the Help -> System information for Bug Reports window into your report. Note how many displays you have. - If you are using a drawing tablet, tell us the brand and type. - Tell us what kind of image you were working on: the size, the resolution, the color model and channel depth. -- If you are reporting a crash, attach a crash log. Follow `this link `_ to learn how to get a crash log on Windows. On Linux, follow your distributions instructions to install debug symbols if you have installed Krita from a distribution package. It is not possible to create a useful crash log with Linux appimages. +- If you are reporting a crash, attach a crash log. Follow `this link `_ to learn how to get a crash log on Windows. On Linux, follow your distribution's instructions to install debug symbols if you have installed Krita from a distribution package. It is not possible to create a useful crash log with Linux appimages. The problem needs to be clearly stated: - what happened, @@ -105,7 +105,7 @@ If at all possible, attach your original Krita file (the one that ends in .kra) to the bug report, or if it's too big, add a link for download. If you do that, make sure the file will be there for **years** to come: do not remove it. -If you think it would be useful, you can also attach or link to a video. Note that the Krita developers and bug triagers are extremely busy, and that it takes less time to read a good description and a set of steps to reproduce than it takes to wach a video for clues for what is going on. +If you think it would be useful, you can also attach or link to a video. Note that the Krita developers and bug triagers are extremely busy, and that it takes less time to read a good description and a set of steps to reproduce than it takes to watch a video for clues for what is going on. When making a video or a screenshot, include the whole Krita windows, including the titlebar and the statusbar. diff --git a/untranslatable_pages/triaging_bugs.rst b/untranslatable_pages/triaging_bugs.rst --- a/untranslatable_pages/triaging_bugs.rst +++ b/untranslatable_pages/triaging_bugs.rst @@ -180,7 +180,7 @@ .. admonition:: Tell the user: - Windows tablet drivers often have special code for different applications. Whether an application works or not depends on whether the programmers have tested their driver with an application or not. Tablet issues are almost always caused by the drivers being broken. + Windows tablet drivers often have a special code for different applications. Whether an application works or not depends on whether the programmers have tested their driver with an application or not. Tablet issues are almost always caused by the drivers being broken. Krita lags ~~~~~~~~~~ @@ -200,4 +200,4 @@ .. admonition:: Ask the user: - Do you have a selection saved with that document. Use select/deselect on your image and check whether you can paint again. If not, please attach the .kra document to this bug report or make it available. + Do you have a selection saved with that document? Use select/deselect on your image and check whether you can paint again. If not, please attach the .kra document to this bug report or make it available. diff --git a/user_manual/animation.rst b/user_manual/animation.rst --- a/user_manual/animation.rst +++ b/user_manual/animation.rst @@ -156,15 +156,15 @@ apart as possible, and the pose where one leg is full stretched and the other pulled in, read to take the next step. -Now, let's copy these two... We could do that with :kbd:`Ctrl+drag`, but here +Now, let's copy these two... We could do that with :kbd:`Ctrl + drag`, but here comes a tricky bit: .. image:: /images/en/Introduction_to_animation_12.png -Ctrl+ also selects and deselects frames, so to copy... +:kbd:`Ctrl + |mouseleft|` also selects and deselects frames, so to copy... -- drag select all the frames you want to select. -- Ctrl+++drag. You need to make sure the first frame is 'orange', +- :kbd:`Ctrl + |mouseleft|` to select all the frames you want to select. +- :kbd:`Ctrl + drag`. You need to make sure the first frame is 'orange', otherwise it won't be copied along. Now then... diff --git a/user_manual/introduction_from_other_software/introduction_from_sai.rst b/user_manual/introduction_from_other_software/introduction_from_sai.rst --- a/user_manual/introduction_from_other_software/introduction_from_sai.rst +++ b/user_manual/introduction_from_other_software/introduction_from_sai.rst @@ -29,7 +29,7 @@ Mirror This is tied to :kbd:`M` to flip. Rotate - There's a couple of possibilities here: either :kbd:`4` and :kbd:`6`, or :kbd:`Ctrl`+:kbd:`[` and :kbd:`Ctrl+]` for basic 15 degrees rotation left and right. But you can also have more sophisticated rotation with :kbd:`Shift + Space` + drag or :kbd:`Shift` + |mousemiddle| + drag. To reset the rotation, press :kbd:`5`. + There's a couple of possibilities here: either :kbd:`4` and :kbd:`6`, or :kbd:`Ctrl + [` and :kbd:`Ctrl + ]` for basic 15 degrees rotation left and right. But you can also have more sophisticated rotation with :kbd:`Shift + Space` + drag or :kbd:`Shift` + |mousemiddle| + drag. To reset the rotation, press :kbd:`5`. Zoom You can use :kbd:`+` and :kbd:`-` to zoom out and in, or use :kbd:`Ctrl` + |mousemiddle|. Use 1, 2 or 3 to reset the zoom, fit the zoom to page or fit the zoom to page width. @@ -41,7 +41,7 @@ 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). -:guilabel:`Hide Selection`, :guilabel:`Reset Rotation` are currently not available via the Toolbar configuration, you'll need to use the shortcuts :kbd:`Ctrl`+:kbd:`H` and :kbd:`5` to toggle these. +: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. .. note:: @@ -103,7 +103,7 @@ Lock Alpha This is the checker box icon next to every layer. Clipping group - For Clipping masks in Krita you'll need to put all your images in a single layer, and then press the 'a' icon, or press :kbd:`Ctrl`+:kbd:`Shift`+:kbd:`G` + For Clipping masks in Krita you'll need to put all your images in a single layer, and then press the 'a' icon, or press :kbd:`Ctrl + Shift + G` Ink layer This is a vector layer in Krita, and also holds the text. Masks @@ -132,7 +132,7 @@ .. image:: /images/en/Krita_Color_Selector_Types.png :align: center -You can call the color history with :kbd:`H`, common colors with :kbd:`U` and the two shade selectors with :kbd:`Shift`+:kbd:`N` and :kbd:`Shift`+:kbd:`M`. The big selector can be called with :kbd:`Shift`+:kbd:`I` on canvas. +You can call the color history with :kbd:`H`, common colors with :kbd:`U` and the two shade selectors with :kbd:`Shift + N` and :kbd:`Shift + M`. The big selector can be called with :kbd:`Shift + I` on canvas. Geometric Tools ~~~~~~~~~~~~~~~ diff --git a/user_manual/python_scripting/krita_python_plugin_howto.rst b/user_manual/python_scripting/krita_python_plugin_howto.rst --- a/user_manual/python_scripting/krita_python_plugin_howto.rst +++ b/user_manual/python_scripting/krita_python_plugin_howto.rst @@ -282,7 +282,7 @@ buttonExportDocument = QPushButton("Export Document", mainWidget) -Now, to connect the button to our function, we'll need to look at the signals in the documentation. `QPushButton `_ has no unique signals of it's own, but it does say it inherits 4 signals from `QAbstractButton `_, which means that we can use those too. In our case, we want clicked. +Now, to connect the button to our function, we'll need to look at the signals in the documentation. `QPushButton `_ has no unique signals of its own, but it does say it inherits 4 signals from `QAbstractButton `_, which means that we can use those too. In our case, we want clicked. .. code:: python diff --git a/user_manual/working_with_images.rst b/user_manual/working_with_images.rst --- a/user_manual/working_with_images.rst +++ b/user_manual/working_with_images.rst @@ -244,7 +244,7 @@ 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 it's copy +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.