diff --git a/contributors_manual/krita_manual_conventions.rst b/contributors_manual/krita_manual_conventions.rst index 7872fa01b..b88c3ea57 100644 --- a/contributors_manual/krita_manual_conventions.rst +++ b/contributors_manual/krita_manual_conventions.rst @@ -1,549 +1,549 @@ .. meta:: :description: reStructuredText conventions for the Krita Manual .. metadata-placeholder :authors: - Wolthera van Hövell tot Westerflier :license: GNU free documentation license 1.3 or later. .. _krita_markup_conventions: ======================================== Mark-up conventions for the Krita Manual ======================================== This details the style conventions for using restructured text for the Krita Manual. It's recommended to look over the `official specification `_ 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): User Manual: * `Primer `_ * `Quick Ref `_ * `Text Cheatsheet `_ Reference Documentation: * `Introduction `_ * `Markup `_ * `Directives `_ * `Roles `_ 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 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:: Meta data --------- 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 an html meta tag which will be used by search engines:: .. meta:: :description: Description. 2. A list of authors and a license. 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:: .. metadata-placeholder :authors: - Author 1 - Author 2 :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 follows:: .. index:: Keyword, Keyword with Spaces, ! Main Definition Keyword 4. A label. This is so we can easily link to the page using ``:ref:`label_name```. Try to make this a nice variable name:: .. _label_name: - After the label you will need to add a heading, as ``:ref:`label_name``` will refer to the heading to fill out it's link-text. + After the label you will need to add a heading, as ``:ref:`label_name``` will refer to the heading to fill out its link-text. Headings -------- Headings will be done in the following order:: ############ Part/Section ############ For pages that have a lot of subpages. ========= Heading 1 ========= Start most manual pages with this. Heading 2 --------- Heading 3 ~~~~~~~~~ Heading 4 ^^^^^^^^^ Heading 5 ''''''''' Heading 6 """"""""" These conventions were more or less decided by pandoc'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. Sometimes you need to link to a subsection of a page, add a label above the heading in that case. Headers should not end with punctuation, as the header will be used as the link name when linking to a label. Linking ------- Linking is done with ``:ref:`label_name```. When you need an alternative link text, you use ``:ref:`actual text shown ```. 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 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 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Footnotes can be made in 3 ways, the most common one is with autonumbering, as per reference: [#]_ is a reference to footnote 1, and [#]_ is a reference to footnote 2. .. [#] This is footnote 1. .. [#] This is footnote 2. .. [#] This is footnote 3. [#]_ is a reference to footnote 3. Here is a citation reference: [CIT2002]_ . .. [CIT2002] This is the citation. It's just like a footnote, except the label is textual. Citation can also be referenced with `citation `_ 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. Images ------ Use the image directive for images without captions:: .. image:: /images/en/sample.png :width: 800 :align: center :alt: an image. And figure directives for images with captions:: .. figure:: /images/en/sample.png :figwidth: 800 :align: center :alt: an image. A caption -- notice how the first letter is aligned with the :figwidth: option. The latter gives: .. figure:: /images/en/sample.png :figwidth: 800 :align: center :alt: an image. A caption -- notice how the first letter of the caption in the directive is aligned with the :figwidth: option. Images should go into the ``/images/en`` folder. By using ``/images`` instead of ``images``, sphinx will know the filepath isn't relative. In-text Markup -------------- You can make text *emphasized* and **strong** with a single asterisk and double respectively:: *emphasize* **strong** You cannot do both ***emphasized and strong***, so take a pick. You can :sub:`subscript text` and :sup:`superscript text` by using ``:sub:`text``` and ``:sup:`text``` 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:: :menuselection:`Settings --> Configure Krita` :guilabel:`File` :kbd:`Ctrl + Z` :program:`Krita` Avoid randomly bolding words. It does *not* make the text easier or friendlier to read. Substitution References ----------------------- You can create a sort of shorthand for a piece of text or an image by doing:: .. |shorthand| replace:: something or the other. -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". +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". 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. For links, if you reuse the same link over and over, you can write something like the following at the end of the file:: .. _bugzilla: https://bugs.kde.org/ .. _Krita Manual: https://docs.krita.org/ 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". Lists ----- Ordinated lists ~~~~~~~~~~~~~~~ 1. Apple 2. Pear 3. Banana Or... A. Table B. Chair C. Wardrobe. I. Augustus #. Nero #. Caligula #. Trajan They can be defined as follows:: 1. Apple 2. Pear 3. Banana #. Apple #. Pear #. Banana A. Table B. Chair C. Wardrobe A. Table #. Chair #. Wardrobe I. Augustus #. Nero #. Caligula #. Trajan Unordered lists ~~~~~~~~~~~~~~~ - red - yellow - green - seagreen - verdigris - teal - veridian - emerald - dark emerald - light emerald - very light emerald. - blue Defined as such:: - red - yellow - green - seagreen - verdigris - teal - veridian - emerald - dark emerald - light emerald - very light emerald. - blue Definition Lists ~~~~~~~~~~~~~~~~ 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. Definition explanation. Another option Explanation. To make them. You can make them like this:: Definition explanation. Another option Explanation. Tables ------ ================== ============ Purpose Table type ================== ============ listing shortcuts Simple table lots of colspans Grid table Simple but long List Table ================== ============ Done as follows:: ================== ============ Purpose Table type ================== ============ listing shortcuts Simple table lots of colspans Grid table Simple but long List Table ================== ============ +-----------------+------------+ |Purpose |Table Type | +=================+============+ |listing shortcuts|Simple table| +-----------------+------------+ |lots of colspans |Grid table | +-----------------+------------+ |Simple but long |List table | +-----------------+------------+ .. list-table:: :header-rows: 1 - * Purpose * Table Type - * listing shortcuts * simple table - * lots of colspans * grid table - * simple but long * list table 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 ------------------------ .. note:: Admonishments are sort of like a separate section that the reader needs to pay attention to. Admonishments that can be used are the following (in order of seriousness): .. hint:: Hints are useful to give a little bit more information on a topic than is useful in the main text. Like, hint: these packages are named differently in openSuse versus Debian. .. tip:: 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". .. important:: Something that is important to note, but is not necessarily negative. .. warning:: This is in general when something is negative. .. attention:: General attention grabber. Use this when the subject is more important than warning, but not as important that is could get a dataloss. .. caution:: This is for things that could cause dataloss, like forgetting to save, or that python currently has no undo functionality. .. danger:: This should be for things that are dangerous for the computer in general, this includes things that can cause out of memory style freezes. .. error:: 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. .. admonition:: generic admonition that can have any text. This looks like the following:: .. admonition:: generic admonition that can have any text. Text Sphinx also adds:: .. seealso:: Which is useful to collect external links and references. .. 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 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 the topic is over several paragraphs, rubric itself only deals with the header, like so:: .. rubric:: The rubric directive. .. rubric:: So, when to use these? Only use them when you think the subject is too minor to have a proper heading. Topic When the text is separated from the flow, so it goes into a different subject than the text itself is naturally going to. Rubric When the text isn't separated from the flow, but it does not need a header either. 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 ------------- ``Inline code snippets`` are done with ````backticks````. Multi-line code snippets are done by ending the previous section with ``::``, which'll look like this:: This is a paragraph, and we define a preformated snippet like so:: Be sure to add a white space and a tab afterwards before starting the snippet. You can also use the ``.. code::`` directive. If you add the language name after it, it'll do the appropriate syntax highlighting:: .. code:: python def my_function(): # comment alist = [] alist.append(1) string = "hello world" Becomes .. code:: python def my_function(): # comment alist = [] alist.append(1) string = "hello world" some more... .. code:: c++ int myFunction(int i) { i += 1; // Check if more than 12 if (i>12) { i = 0; } return i; } .. code:: css body { margin: 0 auto; /* is 800 still sensible? */ max-width:800px; font-size:16px; color:#333; background-color: #eee; padding:1em; font-family:serif; line-height: 1.4; } .. code:: html

this is a paragraph.

Other preformatted text ----------------------- | One can | preformat | text by | prepending | each line | with a pipe | symbol Like so:: | One can | preformat | text by | prepending | each line | with a pipe | symbol We don't actually use this anywhere in the manual. Glossaries, Terms and Index --------------------------- These are sphinx features. Index is used in the top section, right now only single index entries are used. Glossaries are used for some of the menu entry sections, but not all of them. Quotes ------ Quotes are done like this:: I am not sure why you'd need quotes in a user manual... -- Wolthera This becomes a blockquote. I am not sure why you'd need quotes in a user manual... -- Wolthera We do actually use quotes in some places. Try to add a link to the name to define where it came from. diff --git a/reference_manual/brushes/brush_engines/tangen_normal_brush_engine.rst b/reference_manual/brushes/brush_engines/tangen_normal_brush_engine.rst index a33034015..c986ae029 100644 --- a/reference_manual/brushes/brush_engines/tangen_normal_brush_engine.rst +++ b/reference_manual/brushes/brush_engines/tangen_normal_brush_engine.rst @@ -1,128 +1,128 @@ .. meta:: :description: The Tangent Normal Brush Engine manual page. .. metadata-placeholder :authors: - Wolthera van Hövell tot Westerflier - Scott Petrovic :license: GNU free documentation license 1.3 or later. .. index:: Brush Engine, Normal Map, Tangent Normal Brush Engine .. _tangent_brush_engine: =========================== Tangent Normal Brush Engine =========================== .. image:: /images/icons/tangentnormal.svg The Tangent Normal Brush Engine is an engine that is specifically designed for drawing normal maps, of the tangent variety. These are in turn used in 3d programs and game engines to do all sorts of lightning trickery. Common uses of normal maps include faking detail where there is none, and to drive transformations (Flow Maps). A Normal map is an image that holds information for vectors. In particular, they hold information for Normal Vectors, which is the information for how the light bends on a surface. Because Normal Vectors are made up of 3 coordinates, just like colors, we can store and see this information as colors. Normals can be seen similar to the stylus on your tablet. Therefore, we can use the tilt-sensors that are available to some tablets to generate the colour of the normals, which can then be used by a 3d program to do lighting effects. In short, you will be able to paint with surfaces instead of colors. The following options are available to the tangent normal brush engine: * :ref:`option_brush_tip` * :ref:`blending_modes` * :ref:`option_opacity_n_flow` * :ref:`option_size` * :ref:`option_ratio` * :ref:`option_spacing` * :ref:`option_mirror` * :ref:`option_softness` * :ref:`option_sharpness` * :ref:`option_rotation` * :ref:`option_scatter` * :ref:`option_airbrush` * :ref:`option_texture` Specific Parameters to the Tangent Normal Brush Engine ------------------------------------------------------ Tangent Tilt ~~~~~~~~~~~~ These are the options that determine how the normals are calculated from tablet input. Tangent Encoding This allows you to set what each color channel means. Different programs set different coordinates to different channels, a common version is that the green channel might need to be inverted (-Y), or that the green channel is actually storing the x-value (+X). Tilt Options Allows you to choose which sensor is used for the X and Y. Tilt Uses Tilt for the X and Y. Direction Uses the drawing angle for the X and Y and Tilt-elevation for the Z, this allows you to draw flowmaps easily. Rotation - Uses rotation for the x and y, and tilt-elevation for the Z. Only available for specialized Pens. + Uses rotation for the X and Y, and tilt-elevation for the Z. Only available for specialized Pens. Elevation Sensitivity Allows you to change the range of the normal that are outputted. At 0 it will only paint the default normal, at 1 it will paint all the normals in a full hemisphere. Usage ----- -The Tangent Normal Map Brush Engine is best used with the Tilt Cursor, which can be set in :menuselection:`Settings --> configure Krita --> general --> Outline Shape --> Tilt Outline`. +The Tangent Normal Map Brush Engine is best used with the Tilt Cursor, which can be set in :menuselection:`Settings --> Configure Krita --> General --> Outline Shape --> Tilt Outline`. Normal Map authoring workflow ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ #. Create an image with a background color of (128, 128, 255) blue/purple. .. figure:: /images/en/Krita-normals-tutorial_1.png :figwidth: 500 Setting up a background with the default color. -#. Set up group with a phongbumpmap-filter mask. Use the 'use normal map' checkbox on the filter to make it use normals. +#. Set up group with a :guilabel:`Phong Bumpmap` filter mask. Use the :guilabel:`Use Normal map` checkbox on the filter to make it use normals. .. figure:: /images/en/Krita-normals-tutorial_2.png :figwidth: 500 - Creating a phong bump map filterlayer, make sure to check 'use normalmap'. + Creating a phong bump map filter layer, make sure to check 'Use Normal map'. .. figure:: /images/en/Krita-normals-tutorial_3.png :figwidth: 500 These settings give a nice daylight-esque lighting setup, with light 1 being the sun, light 3 being the light from the sky, and light 2 being the light from the ground. -#. Make a 'normalize' filter layer or mask to normalize the normal map before feeding it into the phongbumpmap filter for the best results. +#. Make a :guilabel:`Normalize` filter layer or mask to normalize the normal map before feeding it into the Phong bumpmap filter for the best results. #. Then, paint on layers in the group to get direct feedback. .. figure:: /images/en/Krita-normals-tutoria_4.png :figwidth: 500 Paint on the layer beneath the filters with the tangent normal brush to have them be converted in real time. -#. Finally, when done, hide the phongbumpmap filter-layer (but keep the normalize filter layer!) , and export the normal map for use in 3d programs. +#. Finally, when done, hide the Phong bumpmap filter layer (but keep the Normalize filter layer!), and export the normal map for use in 3d programs. Drawing Direction Maps ~~~~~~~~~~~~~~~~~~~~~~ -Direction maps are made with the 'Direction' option in the Tangent Tilt options. These normal maps are used to distort textures in a 3d program (to simulate for example, the flow of water) or to create maps that indicate how hair and brushed metal is brushed. Krita can't currently give feedback on how a given direction map will influence a distortion or shader, but these maps are a little easier to read. +Direction maps are made with the :guilabel:`Direction` option in the :guilabel:`Tangent Tilt` options. These normal maps are used to distort textures in a 3d program (to simulate for example, the flow of water) or to create maps that indicate how hair and brushed metal is brushed. Krita can't currently give feedback on how a given direction map will influence a distortion or shader, but these maps are a little easier to read. -Just set the tangent-tilt option to direction, and draw. The direction your brush draws in will be the direction that is encoded in the colors. +Just set the :guilabel:`Tangent Tilt` option to :guilabel:`Direction`, and draw. The direction your brush draws in will be the direction that is encoded in the colors. Only editing a single channel ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Sometimes you only want to edit a single channel. In that case set the blending mode of the brush to 'copy ', with replaced with red, green or blue. These are under the misc section of the blending modes. +Sometimes you only want to edit a single channel. In that case set the blending mode of the brush to :guilabel:`Copy `, with replaced with red, green or blue. These are under the :guilabel:`Misc` section of the blending modes. -So, if you want the brush to only affect the red channel, set the blending mode to 'copy red'. +So, if you want the brush to only affect the red channel, set the blending mode to :guilabel:`Copy Red`. .. figure:: /images/en/Krita_Filter_layer_invert_greenchannel.png :figwidth: 500 The copy red, green and blue blending modes also work on filter-layers. -This can also be done with filter layers. So if you quickly want to flip a layer's green channel, make an invert filter layer with 'copy green' above it. +This can also be done with filter layers. So if you quickly want to flip a layer's green channel, make an invert filter layer with :guilabel:`Copy Green` above it. Mixing Normal Maps ~~~~~~~~~~~~~~~~~~ -For mixing two normal maps, Krita has the Combine Normal Map blending mode under 'misc'. +For mixing two normal maps, Krita has the :guilabel:`Combine Normal Map` blending mode under :guilabel:`Misc`. diff --git a/reference_manual/resource_management.rst b/reference_manual/resource_management.rst index 848ef4b1b..2b7caea70 100644 --- a/reference_manual/resource_management.rst +++ b/reference_manual/resource_management.rst @@ -1,111 +1,111 @@ .. meta:: :description: Overview of Resource Management in Krita. .. metadata-placeholder :authors: - Wolthera van Hövell tot Westerflier - Scott Petrovic :license: GNU free documentation license 1.3 or later. .. index:: Resources, Bundles .. _resource_management: =================== Resource Management =================== 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 Bundles ------- 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. Tags ---- 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. .. image:: /images/en/Tags-krita.png :align: center * 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. * Brushes in the "Predefined" tab of the Brush Settings Editor can be also tagged and grouped for convenience. Filtering ~~~~~~~~~ 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. .. image:: /images/en/Brushpreset-filters.png You can enter brush name, tag name to quickly pull up a list of brush preset 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: * To filter based on the partial, case insensitive name of the resources you can add ``partialname`` or ``!partialname`` * To include other Tags type the respective name of the tag in square brackets like this ``[Tagname]`` or to exclude a tag type ``![Tagname]``. * For case sensitive matching of preset name type ``"Preset name"`` or ``! "Preset name"`` to exclude. An incredibly quick way to save a group or brushes into a tag is to: #. Create a new tag by |mouseleft| on the green plus sign. This will empty out the contents of the Brush Preset docker. #. 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. #. To finish, click the :guilabel:`Save` button (small disk icon to the right of the :guilabel:`Resource Filter` box) or press :kbd:`Enter` and all the items will be saved with the new tag you created. 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! Resource Zooming If you find the thumbnails of the resources such as color swatches brushes and pattern to be small you can make them bigger or :guilabel:`Zoom in`. All resource selectors can be zoomed in and out of, by hovering over the selector and using :kbd:`Ctrl +` |mousescroll| Managing Resources ------------------ 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. 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` .. image:: /images/en/Manageresources.png :align: center Importing Bundles ~~~~~~~~~~~~~~~~~ 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 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. Creating your own Bundle ~~~~~~~~~~~~~~~~~~~~~~~~ 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 .. image:: /images/en/Creating-bundle.png 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. .. warning:: Make sure you add brush tips for used in the respective paintop preset 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 -Once you have added all the resources you can create bundle by clicking on the 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. +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. Deleting Backup files --------------------- 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 Next time when you start Krita the presets from this list are not loaded. To delete the brushes from this list click on delete backup files Deleting Imported Bundles ------------------------- -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. +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. Resource Types in Krita ----------------------- .. toctree:: :maxdepth: 1 :glob: resource_management/* diff --git a/reference_manual/tools/calligraphy.rst b/reference_manual/tools/calligraphy.rst index 1ab72e0b9..291d8981a 100644 --- a/reference_manual/tools/calligraphy.rst +++ b/reference_manual/tools/calligraphy.rst @@ -1,57 +1,57 @@ .. meta:: :description lang=en: Krita's calligraphy tool reference. .. metadata-placeholder :authors: - Wolthera van Hövell tot Westerflier - Scott Petrovic :license: GNU free documentation license 1.3 or later. .. index:: Tools, Vector, Path, Variable Width Stroke, Calligraphy .. _calligraphy_tool: ================ Calligraphy Tool ================ |toolcalligraphy| The Calligraphy tool allows for variable width lines, with input managed by the tablet. Press down with the stylus/left mouse button on the canvas to make a line, lifting the stylus/mouse button ends the stroke. Tool Options ------------ **Fill** Doesn't actually do anything. **Calligraphy** -The drop-down menu holds your saved presets, the save button next to it allows you to save presets. +The drop-down menu holds your saved presets, the :guilabel:`Save` button next to it allows you to save presets. Follow Selected Path If a stroke has been selected with the default tool, the calligraphy tool will follow this path. Use Tablet Pressure Uses tablet pressure to control the stroke width. Thinning This allows you to set how much thinner a line becomes when speeding up the stroke. Using a negative value makes it thicker. Width Base width for the stroke. Use Tablet Angle Allows you to use the tablet angle to control the stroke, only works for tablets supporting it. Angle The angle of the dab. Fixation The ratio of the dab. 1 is thin, 0 is round. Caps Whether or not an stroke will end with a rounding or flat. Mass How much weight the stroke has. With drag set to 0, high mass increases the 'orbit'. Drag How much the stroke follows the cursor, when set to 0 the stroke will orbit around the cursor path. .. note:: The calligraphy tool can be edited by the edit-line tool, but currently you can't add or remove nodes without converting it to a normal path.