diff --git a/locale/ca/LC_MESSAGES/contributors_manual/krita_manual_conventions.po b/locale/ca/LC_MESSAGES/contributors_manual/krita_manual_conventions.po index 94883e985..a0abbb6f5 100644 --- a/locale/ca/LC_MESSAGES/contributors_manual/krita_manual_conventions.po +++ b/locale/ca/LC_MESSAGES/contributors_manual/krita_manual_conventions.po @@ -1,1534 +1,1534 @@ # Translation of docs_krita_org_contributors_manual___krita_manual_conventions.po to Catalan # Copyright (C) 2019 This_file_is_part_of_KDE # This file is distributed under the license LGPL version 2.1 or # version 3 or later versions approved by the membership of KDE e.V. # # Antoni Bella Pérez , 2019. # Josep Ma. Ferrer , 2019. msgid "" msgstr "" "Project-Id-Version: contributors_manual\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-09 03:27+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: 2019-07-19 19:32+0100\n" "Last-Translator: Josep Ma. Ferrer \n" "Language-Team: Catalan \n" "Language: ca\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" "X-Generator: Lokalize 2.0\n" #: ../../:2 msgid "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: mouseleft" msgstr "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: mouseleft" #: ../../:4 msgid "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: mouseright" msgstr "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: mouseright" #: ../../:6 msgid "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: mousemiddle" msgstr "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: mousemiddle" #: ../../:8 msgid "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" msgstr "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" +#: ../../contributors_manual/krita_manual_conventions.rst:None +msgid "Horizontal Rulers" +msgstr "Regles horitzontals" + #: ../../contributors_manual/krita_manual_conventions.rst:0 msgid "" ".. image:: images/sample.png\n" " :alt: an image." msgstr "" ".. image:: images/sample.png\n" " :alt: una imatge." -#: ../../contributors_manual/krita_manual_conventions.rst:None -msgid "Horizontal Rulers" -msgstr "Regles horitzontals" - #: ../../contributors_manual/krita_manual_conventions.rst:1 msgid "reStructuredText conventions for the Krita Manual" msgstr "Convencions del reStructuredText per al Manual del Krita" #: ../../contributors_manual/krita_manual_conventions.rst:16 msgid "Mark-up conventions for the Krita Manual" msgstr "Convencions del marcatge per al Manual del Krita" #: ../../contributors_manual/krita_manual_conventions.rst:18 msgid "" "This details the style conventions for using restructured text for the Krita " "Manual." msgstr "" "Aquí es detallen les convencions d'estil per a utilitzar text reestructurat " "per al Manual del Krita." # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:20 msgid "" "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):" msgstr "" "Es recomana consultar l'`especificació oficial `_ per a «reStructuredText», i atès que es troba a SourceForge, " "deseu-ne una còpia al vostre disc dur (el SourceForge, en el moment " "d'escriure això, té alguns problemes amb el temps d'activitat del servidor):" # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:23 msgid "" "`Primer `_" msgstr "" "`Llibre elemental `_" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "User Manual:" msgstr "Manual d'usuari:" # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "" "`Quick Ref `_" msgstr "" "`Referència ràpida `_" # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:25 msgid "" "`Text Cheatsheet `_" msgstr "" "`Full amb trucs de text `_" # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:27 msgid "" "`Introduction `_" msgstr "" "`Introducció `_" # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:28 msgid "" "`Markup `_" msgstr "" "`Marcatge `_" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "Reference Documentation:" msgstr "Documentació de referència:" # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "" "`Directives `_" msgstr "" "`Directives `_" # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:30 msgid "`Roles `_" msgstr "`Regles `_" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "Sphinx specific docs:" msgstr "Documentació específica de Sphinx:" # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "" "`Sphinx' page on restructured text `_ -- This is useful for the specific " "sphinx directives and roles it uses to generate for example table of " "contents." msgstr "" "`Pàgina de Sphinx sobre text reestructurat `_: és útil per a les directives " "específiques de Sphinx i les regles que utilitza per a generar, p. ex., el " "contingut d'una taula." #: ../../contributors_manual/krita_manual_conventions.rst:34 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." msgstr "" "Hi ha diferències entre el «reStructuredText» oficial i les múltiples " "maneres en la documentació de Sphinx per a fer les coses. Aquest document " "especifica les convencions aconsellades que cal seguir." #: ../../contributors_manual/krita_manual_conventions.rst:36 msgid "Contents" msgstr "Contingut" #: ../../contributors_manual/krita_manual_conventions.rst:39 msgid "Meta data" msgstr "Metadades" #: ../../contributors_manual/krita_manual_conventions.rst:41 msgid "Each page should start with the following three things:" msgstr "Cada pàgina haurà de començar amb les següents tres coses:" #: ../../contributors_manual/krita_manual_conventions.rst:44 msgid "" "This is a general description of the page. It will be converted to an html " "meta tag which will be used by search engines::" msgstr "" "Aquesta serà una descripció general de la pàgina. Es convertirà en una " "metaetiqueta HTML, la qual utilitzaran els motors de cerca::" #: ../../contributors_manual/krita_manual_conventions.rst:46 msgid "" ".. meta::\n" " :description:\n" " Description." msgstr "" ".. meta::\n" " :description:\n" " Descripció." #: ../../contributors_manual/krita_manual_conventions.rst:49 msgid "A meta description" msgstr "Una metadescripció" #: ../../contributors_manual/krita_manual_conventions.rst:52 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::" msgstr "" "Simplement només és per a fer un seguiment de qui va editar la pàgina i per " "donar crèdit. Haurà d'aparèixer en un comentari de manera que les màquines " "no puguin llegir-lo amb facilitat. La llicència de tot el manual és GDL 1.3 " "i també cal esmentar-ho aquí:" # skip-rule: t-sp_2p #: ../../contributors_manual/krita_manual_conventions.rst:54 msgid "" ".. metadata-placeholder\n" "\n" " :authors: - Author 1\n" " - Author 2\n" " :license: GNU free documentation license 1.3 or later." msgstr "" ".. metadata-placeholder\n" "\n" " :authors: - Autor 1\n" " - Autor 2\n" " :license: GNU free documentation license 1.3 or later." #: ../../contributors_manual/krita_manual_conventions.rst:58 msgid "A list of authors and a license." msgstr "Una llista dels autors i la llicència" # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:61 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::" msgstr "" "Aquests són termes separats per comes sota els quals la pàgina serà indexada " "a l':ref:`genindex`. L'índex generat és força útil tant per al PDF com per a " "les persones que no tenen la certesa de quin és el nom exacte del terme que " "estan cercant. Es defineixen de la següent manera::" #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid "Indexing terms." msgstr "Indexar el termes" # skip-rule: t-sp_ad #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid ".. index:: Keyword, Keyword with Spaces, ! Main Definition Keyword" msgstr "" ".. index:: Paraula clau, Paraula clau amb espais, ! Paraula clau de la " "definició principal" # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:66 msgid "" "This is so we can easily link to the page using ``:ref:`label_name```. Try " "to make this a nice variable name::" msgstr "" "Serveix per a que puguem enllaçar amb facilitat la pàgina utilitzant ``:ref:" "`nom_etiqueta```. Intenteu que sigui un nom de variable bonic::" #: ../../contributors_manual/krita_manual_conventions.rst:68 msgid ".. _label_name:" msgstr ".. _nom_etiqueta:" # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:70 msgid "" "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." msgstr "" "Després de l'etiqueta, haureu d'afegir una capçalera, ja que ``:ref:" "`nom_etiqueta``` farà referència a la capçalera per a completar amb el seu " "text enllaçat." #: ../../contributors_manual/krita_manual_conventions.rst:71 msgid "A label." msgstr "Una etiqueta" #: ../../contributors_manual/krita_manual_conventions.rst:74 msgid "Headings" msgstr "Capçaleres" #: ../../contributors_manual/krita_manual_conventions.rst:76 msgid "Headings will be done in the following order::" msgstr "Les capçaleres es realitzaran en el següent ordre::" #: ../../contributors_manual/krita_manual_conventions.rst:78 msgid "" "############\n" "Part/Section\n" "############\n" "\n" "For pages that have a lot of subpages.\n" "\n" "=========\n" "Heading 1\n" "=========\n" "\n" "Start most manual pages with this.\n" "\n" "Heading 2\n" "---------\n" "\n" "Heading 3\n" "~~~~~~~~~\n" "\n" "Heading 4\n" "^^^^^^^^^\n" "\n" "Heading 5\n" "'''''''''\n" "\n" "Heading 6\n" "\"\"\"\"\"\"\"\"\"" msgstr "" "###########\n" "Part/Secció\n" "###########\n" "\n" "Per a les pàgines que tenen un munt de subpàgines.\n" "\n" "===========\n" "Capçalera 1\n" "===========\n" "\n" "Comenceu així la majoria de les pàgines del manual.\n" "\n" "Capçalera 2\n" "-----------\n" "\n" "Capçalera 3\n" "~~~~~~~~~~~\n" "\n" "Capçalera 4\n" "^^^^^^^^^^^\n" "\n" "Capçalera 5\n" "'''''''''''\n" "\n" "Capçalera 6\n" "\"\"\"\"\"\"\"\"\"\"\"" # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:105 msgid "" "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." msgstr "" "Aquestes convencions van ser més o menys decidides al mediawiki de `Pandoc " "`_ per a la conversió a «reStructuredText». Si " "necessiteu més de 4 capçaleres, pregunteu-vos primer si no s'ha complicat la " "pàgina i necessita dividir-se." #: ../../contributors_manual/krita_manual_conventions.rst:107 msgid "" "Sometimes you need to link to a subsection of a page, add a label above the " "heading in that case." msgstr "" "A vegades és necessari enllaçar amb la subsecció d'una pàgina, en aquest cas " "afegiu una etiqueta per sobre de la capçalera." #: ../../contributors_manual/krita_manual_conventions.rst:109 msgid "" "Headers should not end with punctuation, as the header will be used as the " "link name when linking to a label." msgstr "" "Les capçaleres no hauran d'acabar amb puntuació, ja que la capçalera " "s'utilitzarà com el nom de l'enllaç en vincular amb una etiqueta." #: ../../contributors_manual/krita_manual_conventions.rst:112 msgid "Linking" msgstr "Enllaçar" # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:114 msgid "" "Linking is done with ``:ref:`label_name```. When you need an alternative " "link text, you use ``:ref:`actual text shown ```." msgstr "" "L'enllaç es realitza amb ``:ref:`nom_etiqueta```. Quan necessiteu un text " "alternatiu per a l'enllaç, utilitzeu ``:ref:`text real que es mostrarà " "```." # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:116 msgid "" "Linking to external pages is done with ```url`_`` and ```link name " "`_``, which'll become `link name `_." msgstr "" "Enllaçar amb pàgines externes es realitza amb ```url`_`` i ```nom enllaç " "`_``, els quals es convertiran en el `nom de l'enllaç `_." # skip-rule: t-acc_obe,t-sp_2p,t-2p_sp #: ../../contributors_manual/krita_manual_conventions.rst:118 msgid "" "`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." msgstr "" "A `Pandoc `_ li agrada convertir-los en " "```nom_enllaç`__`` i després afegir ``.. __ :url`` al final del document. " "Aquest és l'anomenat «hipervincle anònim», vol dir que depenent de l'ordre " "en que apareixen els enllaços en el text, l'ordre dels enllaços al final del " "text hi estarà associat. Si això sona confús i difícil, és perquè ho és. " "Aquesta també és la raó exacta per la qual ens agradaria evitar enllaços com " "aquests." #: ../../contributors_manual/krita_manual_conventions.rst:121 msgid "Footnotes and further reading" msgstr "Notes a peu de pàgina i lectura addicional" #: ../../contributors_manual/krita_manual_conventions.rst:123 msgid "" "Footnotes can be made in 3 ways, the most common one is with autonumbering, " "as per reference:" msgstr "" "Les notes a peu de pàgina es poden fer de tres maneres, la més comuna és " "disposar un recompte automàtic, segons la referència:" #: ../../contributors_manual/krita_manual_conventions.rst:125 msgid "" "[#]_ is a reference to footnote 1, and [#]_ is a reference to footnote 2." msgstr "" "[#]_ és una referència a la nota a peu de pàgina 1, i [#]_ és una referència " "a la nota a peu de pàgina 2." #: ../../contributors_manual/krita_manual_conventions.rst:128 msgid "This is footnote 1." msgstr "Aquesta és una nota a peu de pàgina 1." #: ../../contributors_manual/krita_manual_conventions.rst:129 msgid "This is footnote 2." msgstr "Aquesta és una nota a peu de pàgina 2." #: ../../contributors_manual/krita_manual_conventions.rst:130 msgid "This is footnote 3." msgstr "Aquesta és una nota a peu de pàgina 3." #: ../../contributors_manual/krita_manual_conventions.rst:132 msgid "[#]_ is a reference to footnote 3." msgstr "[#]_ és una referència a la nota a peu de pàgina 3." #: ../../contributors_manual/krita_manual_conventions.rst:134 msgid "Here is a citation reference: [CIT2002]_ ." msgstr "Aquesta és una referència de la cita: [CIT2002]_." #: ../../contributors_manual/krita_manual_conventions.rst:136 msgid "" "This is the citation. It's just like a footnote, except the label is " "textual." msgstr "" "Aquesta és la cita. És com una nota a peu de pàgina, excepte que l'etiqueta " "és de text." # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:139 msgid "Citation can also be referenced with ```citation `_``." msgstr "També s'hi pot fer referència amb ```cita `_``." # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:141 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." msgstr "" "En realitat, en aquest manual no fem servir les notes a peu de pàgina perquè " "és una mica massa acadèmic per als nostres lectors. No obstant això, sí " "recollim documents i enllaços al final d'una pàgina que ofereixen una mica " "més d'informació sobre un tema. L'Sphinx té la directiva ``.. seealso::`` " "per enllaçar amb enllaços externs, mentre que «reStructuredText» aconsella " "utilitzar ``.. rubic:: Notes al peu de pàgina`` per a recopilar " "específicament les notes a peu de pàgina, ja que això es veu bonic amb el " "LaTeX." #: ../../contributors_manual/krita_manual_conventions.rst:145 msgid "Images" msgstr "Imatges" #: ../../contributors_manual/krita_manual_conventions.rst:147 msgid "Use the image directive for images without captions::" msgstr "Utilitzeu la directiva «image» per a les imatges sense llegenda::" #: ../../contributors_manual/krita_manual_conventions.rst:149 msgid "" ".. image:: /images/sample.png\n" " :width: 800\n" " :align: center\n" " :alt: an image." msgstr "" ".. image:: /images/sample.png\n" " :width: 800\n" " :align: center\n" " :alt: una imatge." #: ../../contributors_manual/krita_manual_conventions.rst:154 msgid "And figure directives for images with captions::" msgstr "I la directiva «figure» per a les imatges amb llegenda::" #: ../../contributors_manual/krita_manual_conventions.rst:156 msgid "" ".. figure:: /images/sample.png\n" " :figwidth: 800\n" " :align: center\n" " :alt: an image.\n" "\n" " A caption -- notice how the first letter is aligned with the :figwidth: " "option." msgstr "" ".. figure:: /images/sample.png\n" " :figwidth: 800\n" " :align: center\n" " :alt: una imatge.\n" "\n" " Una llegenda: observeu com la primera lletra de la llegenda s'alinea amb " "l'opció «:figwidth:»." #: ../../contributors_manual/krita_manual_conventions.rst:163 msgid "The latter gives:" msgstr "Aquesta última ens donarà:" # skip-rule: t-2p_sp #: ../../contributors_manual/krita_manual_conventions.rst:170 msgid "" "A caption -- notice how the first letter of the caption in the directive is " "aligned with the :figwidth: option." msgstr "" "Una llegenda: observeu com la primera lletra de la llegenda s'alinea amb " "l'opció «:figwidth:»." # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:172 msgid "" "Images should go into the ``/images`` folder. By using ``/images`` instead " "of ``images``, sphinx will know the filepath isn't relative." msgstr "" "Les imatges hauran d'anar a la carpeta ``/images``. En emprar ``/images`` en " "lloc de ``images``, l'Sphinx sabrà que el camí del fitxer no és relatiu." #: ../../contributors_manual/krita_manual_conventions.rst:175 msgid "In-text Markup" msgstr "Marcatge al text" #: ../../contributors_manual/krita_manual_conventions.rst:177 msgid "" "You can make text *emphasized* and **strong** with a single asterisk and " "double respectively::" msgstr "" "Podeu fer que el text estigui *emfatitzat* i **destacat** amb un sol " "asterisc i doble respectivament::" #: ../../contributors_manual/krita_manual_conventions.rst:179 msgid "" "*emphasize*\n" "**strong**" msgstr "" "*emfatitzat*\n" "**destacat**" #: ../../contributors_manual/krita_manual_conventions.rst:182 msgid "You cannot do both ***emphasized and strong***, so take a pick." msgstr "" "No podreu fer ambdues coses, ***emfatitzat i destacat***, així que trieu." # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:184 msgid "" "You can :sub:`subscript text` and :sup:`superscript text` by using ``:sub:" "`text``` and ``:sup:`text```" msgstr "" "Podeu crear text :sub:`amb subscript` i :sup:`amb superscript` emprant ``:" "sub:`text``` i ``:sup:`text```." #: ../../contributors_manual/krita_manual_conventions.rst:186 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::" msgstr "" "No obstant això, utilitzeu-ho amb moderació! En qualsevol cas, es prefereix " "utilitzar el marcatge semàntic existent a l'Sphinx, perquè aquest facilita " "que els traductors prenguin decisions sobre la naturalesa del text::" #: ../../contributors_manual/krita_manual_conventions.rst:188 msgid "" ":menuselection:`Settings --> Configure Krita`\n" ":guilabel:`File`\n" ":kbd:`Ctrl + Z`\n" ":program:`Krita`" msgstr "" ":menuselection:`Settings --> Configure Krita`\n" ":guilabel:`File`\n" ":kbd:`Ctrl + Z`\n" ":program:`Krita`" #: ../../contributors_manual/krita_manual_conventions.rst:193 msgid "" "Avoid randomly bolding words. It does *not* make the text easier or " "friendlier to read." msgstr "" "Eviteu paraules en negreta a l'atzar. *No* farà que el text sigui més fàcil " "o més amigable de llegir." #: ../../contributors_manual/krita_manual_conventions.rst:196 msgid "Substitution References" msgstr "Substitució de les referències" #: ../../contributors_manual/krita_manual_conventions.rst:198 msgid "" "You can create a sort of shorthand for a piece of text or an image by doing::" msgstr "" "Podeu crear una mena de transcripció per a un fragment de text o una imatge " "fent el següent::" #: ../../contributors_manual/krita_manual_conventions.rst:200 msgid ".. |shorthand| replace:: something or the other." msgstr ".. |transcripció| replace:: una cosa o l'altra." # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:202 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\"." msgstr "" "El qual vol dir que si empreu ``|transcripció|`` en el text, serà substituït " "per «una cosa o l'altra». És útil per a les imatges i text que necessiteu " "formatar de manera complicada, com en el cas de LaTeX." # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:204 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." msgstr "" "La documentació del Krita té ``|mouseleft|``, ``|mousemiddle|``, ``|" "mousescroll|`` i ``|mouseright|``, els quals es convertiran en |mouseleft|, |" "mousemiddle|, |mousescroll| i |mouseright| respectivament. Aquests estan " "definits al fitxer «conf.py» de l'Sphinx i s'afegeixen a cada fitxer RST." #: ../../contributors_manual/krita_manual_conventions.rst:206 msgid "" "For links, if you reuse the same link over and over, you can write something " "like the following at the end of the file::" msgstr "" "Per als enllaços, si reutilitzeu el mateix un cop i un altre, podeu escriure " "una cosa com la següent al final del fitxer:" # skip-rule: t-sp_pu #: ../../contributors_manual/krita_manual_conventions.rst:208 msgid "" ".. _bugzilla: https://bugs.kde.org/\n" ".. _Krita Manual: https://docs.krita.org/" msgstr "" ".. _Bugzilla: https://bugs.kde.org/\n" ".. _Krita Manual: https://docs.krita.org/" # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:211 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\"." msgstr "" "Després, en escriure un enllaç, podreu emprar ```Bugzilla`_`` per enllaçar-" "hi i amb «Bugzilla» com a text de l'enllaç. ```Krita Manual`_`` al seu torn " "enllaçarà amb el web docs.krita.org amb el text «Krita Manual»." #: ../../contributors_manual/krita_manual_conventions.rst:214 msgid "Lists" msgstr "Llistes" #: ../../contributors_manual/krita_manual_conventions.rst:217 msgid "Ordinated lists" msgstr "Llistes ordenades" #: ../../contributors_manual/krita_manual_conventions.rst:219 msgid "Apple" msgstr "Poma" #: ../../contributors_manual/krita_manual_conventions.rst:220 msgid "Pear" msgstr "Pera" #: ../../contributors_manual/krita_manual_conventions.rst:221 msgid "Banana" msgstr "Plàtan" #: ../../contributors_manual/krita_manual_conventions.rst:223 msgid "Or..." msgstr "O..." #: ../../contributors_manual/krita_manual_conventions.rst:225 msgid "Table" msgstr "Taula" #: ../../contributors_manual/krita_manual_conventions.rst:226 msgid "Chair" msgstr "Cadira" # skip-rule: punctuation-period #: ../../contributors_manual/krita_manual_conventions.rst:227 msgid "Wardrobe." msgstr "Armari" #: ../../contributors_manual/krita_manual_conventions.rst:229 msgid "Augustus" msgstr "August" #: ../../contributors_manual/krita_manual_conventions.rst:230 msgid "Nero" msgstr "Neró" #: ../../contributors_manual/krita_manual_conventions.rst:231 msgid "Caligula" msgstr "Calígula" #: ../../contributors_manual/krita_manual_conventions.rst:232 msgid "Trajan" msgstr "Trajà" #: ../../contributors_manual/krita_manual_conventions.rst:234 msgid "They can be defined as follows::" msgstr "Es poden definir de la següent manera::" #: ../../contributors_manual/krita_manual_conventions.rst:236 msgid "" "1. Apple\n" "2. Pear\n" "3. Banana\n" "\n" "#. Apple\n" "#. Pear\n" "#. Banana\n" "\n" "A. Table\n" "B. Chair\n" "C. Wardrobe\n" "\n" "A. Table\n" "#. Chair\n" "#. Wardrobe\n" "\n" "I. Augustus\n" "#. Nero\n" "#. Caligula\n" "#. Trajan" msgstr "" "1. Poma\n" "2. Pera\n" "3. Plàtan\n" "\n" "#. Poma\n" "#. Pera\n" "#. Plàtan\n" "\n" "A. Taula\n" "B. Cadira\n" "C. Armari\n" "\n" "A. Taula\n" "#. Cadira\n" "#. Armari\n" "\n" "I. August\n" "#. Neró\n" "#. Calígula\n" "#. Trajà" #: ../../contributors_manual/krita_manual_conventions.rst:258 msgid "Unordered lists" msgstr "Llistes desordenades" #: ../../contributors_manual/krita_manual_conventions.rst:260 msgid "red" msgstr "vermell" #: ../../contributors_manual/krita_manual_conventions.rst:261 msgid "yellow" msgstr "groc" #: ../../contributors_manual/krita_manual_conventions.rst:263 msgid "seagreen" msgstr "verd marí" #: ../../contributors_manual/krita_manual_conventions.rst:264 msgid "verdigris" msgstr "verdet" #: ../../contributors_manual/krita_manual_conventions.rst:265 msgid "teal" msgstr "xarxet" #: ../../contributors_manual/krita_manual_conventions.rst:266 msgid "viridian" msgstr "viridian" #: ../../contributors_manual/krita_manual_conventions.rst:268 msgid "dark emerald" msgstr "maragda fosc" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "green" msgstr "verd" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "emerald" msgstr "maragda" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "light emerald" msgstr "maragda clar" # skip-rule: punctuation-period #: ../../contributors_manual/krita_manual_conventions.rst:270 msgid "very light emerald." msgstr "maragda molt clar" #: ../../contributors_manual/krita_manual_conventions.rst:271 msgid "blue" msgstr "blau" #: ../../contributors_manual/krita_manual_conventions.rst:273 msgid "Defined as such::" msgstr "Es defineix de la següent manera::" #: ../../contributors_manual/krita_manual_conventions.rst:275 msgid "" "- red\n" "- yellow\n" "- green\n" " - seagreen\n" " - verdigris\n" " - teal\n" " - viridian\n" " - emerald\n" " - dark emerald\n" " - light emerald\n" " - very light emerald.\n" "- blue" msgstr "" "- vermell\n" "- groc\n" "- verd\n" " - verd marí\n" " - verdet\n" " - xarxet\n" " - viridian\n" " - maragda\n" " - maragda fosc\n" " - maragda clar\n" " - maragda molt clar\n" "- blau" #: ../../contributors_manual/krita_manual_conventions.rst:289 msgid "Definition Lists" msgstr "Llistes de definicions" #: ../../contributors_manual/krita_manual_conventions.rst:291 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." msgstr "" "Un preferit! Les llistes de definicions són especialment útils quan es " "tracta d'enumerar totes les opcions en un acoblador, per a després intentar " "afegir una explicació senzilla." #: ../../contributors_manual/krita_manual_conventions.rst:293 msgid "Definition" msgstr "Definició" #: ../../contributors_manual/krita_manual_conventions.rst:294 #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Explanation." msgstr "Explicació." #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Another option" msgstr "Una altra opció" #: ../../contributors_manual/krita_manual_conventions.rst:299 msgid "You can make them like this::" msgstr "Per a crear-les farem el següent::" #: ../../contributors_manual/krita_manual_conventions.rst:301 msgid "" "Definition\n" " Explanation.\n" "Another option\n" " Explanation." msgstr "" "Definició\n" " Explicació.\n" "Una altra opció\n" " Explicació." #: ../../contributors_manual/krita_manual_conventions.rst:304 msgid "To make them." msgstr "Per a crear-les." #: ../../contributors_manual/krita_manual_conventions.rst:307 msgid "Tables" msgstr "Taules" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Purpose" msgstr "Propòsit" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Table type" msgstr "Tipus de taula" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "listing shortcuts" msgstr "Llistar les dreceres" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "Simple table" msgstr "Taula senzilla" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "lots of colspans" msgstr "Un munt de «colspan»" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "Grid table" msgstr "Taula de quadrícula" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "Simple but long" msgstr "Senzill però llarg" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "List Table" msgstr "Taula de llista" #: ../../contributors_manual/krita_manual_conventions.rst:317 msgid "Done as follows::" msgstr "Es fa de la següent manera::" # skip-rule: t-sp_2p,t-sp_pu #: ../../contributors_manual/krita_manual_conventions.rst:319 msgid "" "================== ============\n" "Purpose Table type\n" "================== ============\n" "listing shortcuts Simple table\n" "lots of colspans Grid table\n" "Simple but long List Table\n" "================== ============\n" "\n" "+-----------------+------------+\n" "|Purpose |Table Type |\n" "+=================+============+\n" "|listing shortcuts|Simple table|\n" "+-----------------+------------+\n" "|lots of colspans |Grid table |\n" "+-----------------+------------+\n" "|Simple but long |List table |\n" "+-----------------+------------+\n" "\n" ".. list-table::\n" " :header-rows: 1\n" "\n" " - * Purpose\n" " * Table Type\n" " - * listing shortcuts\n" " * simple table\n" " - * lots of colspans\n" " * grid table\n" " - * simple but long\n" " * list table" msgstr "" "====================== =====================\n" "Propòsit Tipus de taula\n" "====================== =====================\n" "Llistar les dreceres Taula senzilla\n" "Un munt de «colspan» Taula de quadrícula\n" "Senzill però llarg Taula de llista\n" "================== =========================\n" "\n" "+---------------------+---------------------+\n" "|Propòsit |Tipus de taula |\n" "+=====================+=====================+\n" "|Llistar les dreceres |Taula senzilla |\n" "+---------------------+---------------------+\n" "|Un munt de «colspan» |Taula de quadrícula |\n" "+---------------------+---------------------+\n" "|Senzill però llarg | Taula de llista |\n" "+---------------------+---------------------+\n" "\n" ".. list-table::\n" " :header-rows: 1\n" "\n" " - * Propòsit\n" " * Tipus de taula\n" " - * Llistar les dreceres\n" " * Taula senzilla\n" " - * Un munt de «colspan»\n" " * Taula de quadrícula\n" " - * Senzill però llarg\n" " * Taula de llista" #: ../../contributors_manual/krita_manual_conventions.rst:349 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." msgstr "" "Les taules de quadrícula són les millors per a quan es necessiten totes les " "característiques, com columnes i files complexes, però són difícils de " "crear. Per aquesta raó, les taules petites es fan millor amb una sintaxi " "senzilla, mentre que les taules realment llargues es fan millor amb una " "directiva de llista perquè és molt més fàcil d'escriure i mantenir." #: ../../contributors_manual/krita_manual_conventions.rst:352 msgid "Admonishments and asides" msgstr "Amonestacions i apartats" #: ../../contributors_manual/krita_manual_conventions.rst:356 msgid "" "Admonishments are sort of like a separate section that the reader needs to " "pay attention to." msgstr "" "Les amonestacions són una mena de secció separada a la qual el lector haurà " "de prestar atenció." #: ../../contributors_manual/krita_manual_conventions.rst:358 msgid "" "Admonishments that can be used are the following (in order of seriousness):" msgstr "" "Les amonestacions que es poden utilitzar són les següents (per ordre de " "serietat):" #: ../../contributors_manual/krita_manual_conventions.rst:362 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\"." msgstr "" "Els suggeriments són útils per a proporcionar una mica més d'informació " "sobre un tema que és útil en el text principal. Com ara, «Aquests paquets " "s'anomenen de diferent manera a openSUSE en comparació amb Debian»." #: ../../contributors_manual/krita_manual_conventions.rst:366 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\"." msgstr "" "Informació addicional sobre com fer alguna cosa, com ara, «Podeu crear una " "plantilla de la configuració del vostre document preferit» o «Utilitzeu m " "per emmirallar el llenç i veure els errors al vostre dibuix amb més " "facilitat»." #: ../../contributors_manual/krita_manual_conventions.rst:370 msgid "Something that is important to note, but is not necessarily negative." msgstr "" "Alguna cosa que és important tenir en compte, però no que no haurà de ser " "necessàriament negativa." #: ../../contributors_manual/krita_manual_conventions.rst:374 msgid "This is in general when something is negative." msgstr "En general, quan alguna cosa és negativa." #: ../../contributors_manual/krita_manual_conventions.rst:378 msgid "" "General attention grabber. Use this when the subject is more important than " "warning, but not as important that is could get a dataloss." msgstr "" "Captador general de l'atenció. Feu-la servir quan el tema sigui més " "important que una avís, però no tan important com per obtenir una pèrdua de " "les dades." #: ../../contributors_manual/krita_manual_conventions.rst:382 msgid "" "This is for things that could cause dataloss, like forgetting to save, or " "that Python currently has no undo functionality." msgstr "" "És per a coses que poden provocar pèrdua de les dades, com oblidar-vos de " "desar o que el Python no disposa actualment de la funcionalitat de desfer." #: ../../contributors_manual/krita_manual_conventions.rst:386 msgid "" "This should be for things that are dangerous for the computer in general, " "this includes things that can cause out of memory style freezes." msgstr "" "Hauria de ser per a coses perilloses per a l'ordinador en general, això " "inclou coses que poden provocar que es congeli l'estil de la memòria." #: ../../contributors_manual/krita_manual_conventions.rst:390 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." msgstr "" "Probablement aquesta no sigui rellevant per a un manual. L'Sphinx pot crear-" "les manualment indicant algunes situacions, però la nostra configuració no " "ho fa de manera predeterminada." #: ../../contributors_manual/krita_manual_conventions.rst:392 msgid "Generic admonition that can have any text" msgstr "Amonestació genèrica que pot contenir qualsevol text" #: ../../contributors_manual/krita_manual_conventions.rst:394 msgid "Text." msgstr "Text." #: ../../contributors_manual/krita_manual_conventions.rst:396 msgid "You can make it like this::" msgstr "Per a crear-les farem el següent::" #: ../../contributors_manual/krita_manual_conventions.rst:398 msgid "" ".. admonition:: Generic admonition that can have any text\n" "\n" " Text." msgstr "" ".. admonition:: Amonestació genèrica que pot contenir qualsevol text\n" "\n" " Text." #: ../../contributors_manual/krita_manual_conventions.rst:404 msgid "Sphinx also adds::" msgstr "L'Sphinx també afegeix::" #: ../../contributors_manual/krita_manual_conventions.rst:406 msgid "" ".. seealso::\n" "\n" " Which is useful to collect external links and references." msgstr "" ".. seealso::\n" "\n" " És útil per a recopilar enllaços externs i referències." # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:414 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." msgstr "" "Els regles horitzontals normalment s'utilitzen quan el tema canvia de forma " "directa. Això és molt comú en una escriptura més narrativa, com ara història " "o ficció. El manual del Krita és més un estil d'escriptura amb instruccions " "i de referència, és a dir, no solem explicar una història llarga per indicar " "com es combinen els diferents elements, sinó que hi ha històries llargues " "per a motivar el fet que es prenguin certs passos d'una determinada manera. " "Els canvis de tema solen succeir perquè entrem en una secció nova, en lloc " "de canviar a una secció relacionada. Per tant, és millor utilitzar " "capçaleres o la directiva ``.. Topic::``. Les capçaleres també faciliten la " "lectura." # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:418 msgid "That said, horizontal rulers can be made with ``----``." msgstr "Dit això, els regles horitzontals es poden crear amb ``----``." #: ../../contributors_manual/krita_manual_conventions.rst:421 msgid "The rubric directive" msgstr "La directiva «rubric»" #: ../../contributors_manual/krita_manual_conventions.rst:422 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::" msgstr "" "La directiva «rubric» és una directiva de capçalera que a primera vista " "sembla un «tema», però quan el tema té diversos paràgrafs, «rubric» només " "tractarà la capçalera, de la següent manera:" #: ../../contributors_manual/krita_manual_conventions.rst:424 msgid ".. rubric:: The rubric directive" msgstr ".. rubric:: La directiva «rubric»" #: ../../contributors_manual/krita_manual_conventions.rst:428 msgid "So, when to use these?" msgstr "Llavors, quan emprar-la?" #: ../../contributors_manual/krita_manual_conventions.rst:429 msgid "" "Only use them when you think the subject is too minor to have a proper " "heading." msgstr "" "Utilitzeu-la només si creieu que el tema és massa petit per a tenir una " "capçalera adequada." #: ../../contributors_manual/krita_manual_conventions.rst:431 msgid "Topic" msgstr "Topic" #: ../../contributors_manual/krita_manual_conventions.rst:432 msgid "" "When the text is separated from the flow, so it goes into a different " "subject than the text itself is naturally going to." msgstr "" "Quan el text estigui separat del flux principal, es tracta d'un tema " "diferent." #: ../../contributors_manual/krita_manual_conventions.rst:433 msgid "Rubric" msgstr "Rubric" #: ../../contributors_manual/krita_manual_conventions.rst:434 msgid "" "When the text isn't separated from the flow, but it does not need a header " "either." msgstr "" "Quan el text no està separat del flux principal, però tampoc necessita una " "capçalera." #: ../../contributors_manual/krita_manual_conventions.rst:436 msgid "Admonishments" msgstr "Amonestacions" #: ../../contributors_manual/krita_manual_conventions.rst:436 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." msgstr "" "Només quan encaixen semànticament. Això és especialment necessari per a les " "amonestacions sobre perill i avís, ja que veure-les amb massa freqüència pot " "fer que els usuaris no les vegin." #: ../../contributors_manual/krita_manual_conventions.rst:439 msgid "Code Snippets" msgstr "Retalls de codi" # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:441 msgid "``Inline code snippets`` are done with ````backticks````." msgstr "Els ``retalls de codi inclosos`` es fan amb ````accents oberts````." # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:443 msgid "" "Multi-line code snippets are done by ending the previous section with ``::" "``, which'll look like this::" msgstr "" "Els retalls de codi de múltiples línies es realitzen en finalitzar la secció " "anterior amb ``::``, el qual es veurà així::" #: ../../contributors_manual/krita_manual_conventions.rst:445 msgid "" "This is a paragraph, and we define a preformated snippet like so::\n" "\n" " Be sure to add a white space and a tab afterwards before starting the " "snippet." msgstr "" "Aquest és un paràgraf, i definim un retall de codi amb format previ així::\n" "\n" " Assegureu-vos d'afegir un espai en blanc i una tabulació abans de " "començar el retall." # skip-rule: t-acc_obe #: ../../contributors_manual/krita_manual_conventions.rst:449 msgid "" "You can also use the ``.. code::`` directive. If you add the language name " "after it, it'll do the appropriate syntax highlighting::" msgstr "" "També podeu utilitzar la directiva ``.. code::``. Si afegiu el nom del " "llenguatge després d'aquest, es farà el ressaltat de sintaxi apropiat::" #: ../../contributors_manual/krita_manual_conventions.rst:451 msgid "" ".. code:: python\n" "\n" " # Python comment\n" " def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" ".. code:: python\n" "\n" " # comentari a Python\n" " def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hola món\"" #: ../../contributors_manual/krita_manual_conventions.rst:459 msgid "Becomes" msgstr "Esdevindrà" #: ../../contributors_manual/krita_manual_conventions.rst:468 msgid "" "# Python comment\n" "def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" "# comentari a Python\n" "def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hola món\"" #: ../../contributors_manual/krita_manual_conventions.rst:469 msgid "some more..." msgstr "alguns més..." #: ../../contributors_manual/krita_manual_conventions.rst:483 msgid "" "// C++ comment\n" "int myFunction(int i) {\n" " i += 1;\n" "\n" " // Check if more than 12\n" " if (i>12) {\n" " i = 0;\n" " }\n" " return i;\n" "}" msgstr "" "// comentari a C++\n" "int myFunction(int i) {\n" " i += 1;\n" "\n" " // Comprova si hi ha més que 12\n" " if (i>12) {\n" " i = 0;\n" " }\n" " return i;\n" "}" # skip-rule: ff-font #: ../../contributors_manual/krita_manual_conventions.rst:498 msgid "" "/* CSS comment */\n" "body {\n" " margin: 0 auto;\n" " /* is 800 still sensible? */\n" " max-width:800px;\n" " font-size:16px;\n" " color:#333;\n" " background-color: #eee;\n" " padding:1em;\n" " font-family:serif;\n" " line-height: 1.4;\n" "}" msgstr "" "# comentari a CSS\n" "body {\n" " margin: 0 auto;\n" " /* 800 encara és sensat? */\n" " max-width:800px;\n" " font-size:16px;\n" " color:#333;\n" " background-color: #eee;\n" " padding:1em;\n" " font-family:serif;\n" " line-height: 1.4;\n" "}" #: ../../contributors_manual/krita_manual_conventions.rst:502 msgid "" "

this is " "a paragraph.

" msgstr "" "

aquest és un paràgraf.

" #: ../../contributors_manual/krita_manual_conventions.rst:504 msgid "Other preformatted text" msgstr "Altres text amb formatat previ" #: ../../contributors_manual/krita_manual_conventions.rst:507 msgid "One can" msgstr "Es pot" #: ../../contributors_manual/krita_manual_conventions.rst:508 msgid "preformat" msgstr "formatar prèviament" #: ../../contributors_manual/krita_manual_conventions.rst:509 msgid "text by" msgstr "el text" #: ../../contributors_manual/krita_manual_conventions.rst:510 msgid "prepending" msgstr "anteposant" #: ../../contributors_manual/krita_manual_conventions.rst:511 msgid "each line" msgstr "cada línia" #: ../../contributors_manual/krita_manual_conventions.rst:512 msgid "with a pipe" msgstr "amb un caràcter" #: ../../contributors_manual/krita_manual_conventions.rst:513 msgid "symbol" msgstr "de barra vertical" #: ../../contributors_manual/krita_manual_conventions.rst:515 msgid "Like so::" msgstr "D'aquesta manera::" #: ../../contributors_manual/krita_manual_conventions.rst:517 msgid "" "| One can\n" "| preformat\n" "| text by\n" "| prepending\n" "| each line\n" "| with a pipe\n" "| symbol" msgstr "" "| Es pot\n" "| formatar prèviament\n" "| el text\n" "| anteposant\n" "| cada línia\n" "| amb un caràcter\n" "| de barra vertical" #: ../../contributors_manual/krita_manual_conventions.rst:525 msgid "We don't actually use this anywhere in the manual." msgstr "En realitat, no ho emprem enlloc del manual." #: ../../contributors_manual/krita_manual_conventions.rst:528 msgid "Glossaries, Terms and Index" msgstr "Glossaris, termes i índexs" #: ../../contributors_manual/krita_manual_conventions.rst:530 msgid "These are sphinx features." msgstr "Aquestes són característiques de l'Sphinx." #: ../../contributors_manual/krita_manual_conventions.rst:532 msgid "" "Index is used in the top section, right now only single index entries are " "used." msgstr "" "«index» s'empra a la secció superior, en aquest moment només s'empren " "entrades «index» úniques." #: ../../contributors_manual/krita_manual_conventions.rst:534 msgid "" "Glossaries are used for some of the menu entry sections, but not all of them." msgstr "" "Els glossaris s'utilitzen per a algunes de les seccions amb entrades del " "menú, però no per a totes." #: ../../contributors_manual/krita_manual_conventions.rst:537 msgid "Quotes" msgstr "Cites de bloc" #: ../../contributors_manual/krita_manual_conventions.rst:539 msgid "Quotes are done like this::" msgstr "Les cites de bloc es fan així::" #: ../../contributors_manual/krita_manual_conventions.rst:541 msgid "" "I am not sure why you'd need quotes in a user manual...\n" "\n" "-- Wolthera" msgstr "" "I am not sure why you'd need quotes in a user manual...\n" "(No estic segur de perquè necessitaríeu cites de bloc en un manual " "d'usuari...)\n" "\n" "-- Wolthera" #: ../../contributors_manual/krita_manual_conventions.rst:545 msgid "This becomes a blockquote." msgstr "Això esdevindrà en una cita de bloc (blockquote)." # skip-rule: punctuation-period,punctuation-3period #: ../../contributors_manual/krita_manual_conventions.rst:547 msgid "I am not sure why you'd need quotes in a user manual..." msgstr "" "I am not sure why you'd need quotes in a user manual...\n" "(No estic segur de perquè necessitaríeu cites de bloc en un manual " "d'usuari...)" #: ../../contributors_manual/krita_manual_conventions.rst:551 msgid "" "We do actually use quotes in some places. Try to add a link to the name to " "define where it came from." msgstr "" "En realitat utilitzem cites de bloc en alguns llocs. Intenteu afegir un " "enllaç al nom per a definir d'on ve." #: ../../contributors_manual/krita_manual_conventions.rst:552 msgid "Wolthera" msgstr "Wolthera" diff --git a/locale/ca/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po b/locale/ca/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po index 86e55f4eb..317bf9ca0 100644 --- a/locale/ca/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po +++ b/locale/ca/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po @@ -1,1514 +1,1514 @@ # Translation of docs_krita_org_general_concepts___colors___color_managed_workflow.po to Catalan # Copyright (C) 2019 This_file_is_part_of_KDE # This file is distributed under the license LGPL version 2.1 or # version 3 or later versions approved by the membership of KDE e.V. # # Antoni Bella Pérez , 2019. msgid "" msgstr "" "Project-Id-Version: general_concepts\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-08 03:08+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: 2019-08-04 22:02+0200\n" "Last-Translator: Antoni Bella Pérez \n" "Language-Team: Catalan \n" "Language: ca\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" "X-Generator: Lokalize 19.07.70\n" +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_matrix_profile.png" +msgstr ".. image:: images/color_category/Kiki_matrix_profile.png" + +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" +msgstr ".. image:: images/color_category/Kiki_cLUTprofiles.png" + #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group1.png" msgstr ".. image:: images/color_category/Krita_2_9_colormanagement_group1.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group2.png" msgstr ".. image:: images/color_category/Krita_2_9_colormanagement_group2.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group3.png" msgstr ".. image:: images/color_category/Krita_2_9_colormanagement_group3.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group4.png" msgstr ".. image:: images/color_category/Krita_2_9_colormanagement_group4.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/dockers/LUT_Management_Docker.png" msgstr ".. image:: images/dockers/LUT_Management_Docker.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR_1.svg" msgstr ".. image:: images/color_category/Krita_HDR_1.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR2.svg" msgstr ".. image:: images/color_category/Krita_HDR2.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_webcomic.svg" msgstr "" ".. image:: images/color_category/Krita-colormanaged-workflow_webcomic.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_print.svg" msgstr ".. image:: images/color_category/Krita-colormanaged-workflow_print.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_games.svg" msgstr ".. image:: images/color_category/Krita-colormanaged-workflow_games.svg" -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_matrix_profile.png" -msgstr ".. image:: images/color_category/Kiki_matrix_profile.png" - -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" -msgstr ".. image:: images/color_category/Kiki_cLUTprofiles.png" - #: ../../general_concepts/colors/color_managed_workflow.rst:1 msgid "How a color managed workflow works." msgstr "Com funciona un flux de treball gestionant el color." #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "Color" msgstr "Color" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "Color Management" msgstr "Gestió del color" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "ICC Profiles" msgstr "Perfils ICC" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "OCIO" msgstr "OCIO" #: ../../general_concepts/colors/color_managed_workflow.rst:17 msgid "Color Managed Workflow" msgstr "Flux de treball gestionant el color" #: ../../general_concepts/colors/color_managed_workflow.rst:19 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." msgstr "" "És possible que hàgiu sentit que el Krita té alguna cosa que s'anomena " "gestió del color. O potser simplement us heu preguntat què signifiquen totes " "aquestes coses com «model de color» i «perfil de color» que trobeu en els " "menús. La gestió del color és força útil per a les persones que treballen en " "les imatges digitals de manera professional, i espero que aquesta pàgina ho " "expliqui." #: ../../general_concepts/colors/color_managed_workflow.rst:22 msgid "Basic Info" msgstr "Informació bàsica" #: ../../general_concepts/colors/color_managed_workflow.rst:24 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." msgstr "" "Si mai heu treballat amb la gestió del color i no teniu ni idea de què és, " "llavors hauríeu de saber que probablement heu estat treballant en l'espai de " "color RGB de 8 bits amb el perfil sRGB. Això vol dir que podreu triar *sRGB " "incorporat* o *sRGB-elle-v2-srgbtrc.icc*. Amb el nou navegador per a l'espai " "de color, quan s'utilitzen els 8 bits aquest perfil estarà marcat amb " "*(predeterminat)*." #: ../../general_concepts/colors/color_managed_workflow.rst:26 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." msgstr "" "Veurem què volen dir aquests termes en la teoria, però si esteu aquí només " "per intentar esbrinar quin és el valor predeterminat, ara ja ho sabeu. " "Potser, després de llegir això, és possible que tingueu ganes de canviar el " "valor predeterminat, per obtenir resultats nous i interessants dels filtres, " "modes de barreja o simplement el pinzell amb esborronat del color." #: ../../general_concepts/colors/color_managed_workflow.rst:29 msgid "What is the problem?" msgstr "Quin és el problema?" #: ../../general_concepts/colors/color_managed_workflow.rst:31 msgid "" "To explain the point of color management, you'd first need to learn which " "problem color management tries to solve." msgstr "" "Per explicar el punt de la gestió del color, primer haureu d'aprendre quin " "problema tracta de resoldre." #: ../../general_concepts/colors/color_managed_workflow.rst:33 msgid "Let us imagine a kinder garden:" msgstr "Imaginem una escola bressol:" #: ../../general_concepts/colors/color_managed_workflow.rst:35 msgid "" "The class of 28 children is subdivided in groups of 7. Each group has its " "own table." msgstr "" "La classe de 28 nens i nenes se subdivideix en grups de 7. Cada grup té la " "seva pròpia taula." #: ../../general_concepts/colors/color_managed_workflow.rst:37 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." msgstr "" "El mestre els dóna una tasca de pintura: cal que pintin un triangle vermell, " "un quadrat blau, un cercle verd i posar una vora groga al voltant dels tres. " "La canalla ja té molta experiència amb la pintura, de manera que el " "professor deixarà als més intel·ligents amb confiança en els seus propis " "dispositius i dedicarà més temps a aquells que necessiten ajuda." #: ../../general_concepts/colors/color_managed_workflow.rst:40 msgid "The following results come from painting:" msgstr "Els següents resultats provenen de la pintura:" #: ../../general_concepts/colors/color_managed_workflow.rst:42 msgid "" "Even though all groups had the same assignment, each group's result looks " "different." msgstr "" "Encara que tots els grups tenien la mateixa assignació, el resultat de cada " "grup sembla diferent." #: ../../general_concepts/colors/color_managed_workflow.rst:49 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." msgstr "" "El grup 1 tenia a la seva disposició el vermelló, el groc cítric i el blau " "ultramarí. Això vol dir que el seu triangle es veu bonic i vermell, però el " "verd del seu cercle és fangós. Això es deu al fet que el blau ultramarí és " "massa fosc per a crear verds bonics." #: ../../general_concepts/colors/color_managed_workflow.rst:56 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." msgstr "" "El grup 2 tenia el vermell magenta, el groc cítric i el blau ceruli. El " "magenta és un tipus de vermell que està més a prop del rosa, oposat al " "vermelló, el qual està més a prop del taronja. No obstant això, el seu verd " "es veu bé perquè el ceruli és un blau molt més clar." #: ../../general_concepts/colors/color_managed_workflow.rst:64 msgid "" "Group 3 had vermillion red, citron yellow, emerald green and cerulean blue. " "They didn't mix their green, and thus ended up with a purer color." msgstr "" "El grup 3 tenia el vermelló, el groc cítric, el verd maragda i el blau " "ceruli. No han mesclat el seu verd, i així han acabat amb un color més pur." #: ../../general_concepts/colors/color_managed_workflow.rst:71 msgid "" "Finally, group 4 has vermillion red, citron yellow and cerulean blue. Their " "colors probably look like what you imagined." msgstr "" "Finalment, el grup 4 té el vermelló, el groc cítric i el blau ceruli. Els " "seus colors probablement s'assemblen al que heu imaginat." #: ../../general_concepts/colors/color_managed_workflow.rst:73 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!" msgstr "" "Ara, aquesta és canalla de guarderia, així que aquest no és el problema més " "gran del món. No obstant això, imagineu-vos que succeeix quelcom així en una " "impremta? Imagineu quatre impressores imprimint la mateixa revista amb " "resultats totalment diferents? Això seria desastrós!" #: ../../general_concepts/colors/color_managed_workflow.rst:75 msgid "For this purpose, we invented color management." msgstr "Amb aquesta finalitat, hem inventat la gestió del color." #: ../../general_concepts/colors/color_managed_workflow.rst:78 msgid "What is color management?" msgstr "Què és la gestió del color?" #: ../../general_concepts/colors/color_managed_workflow.rst:80 msgid "" "Color management is, dryly put, a set of systems that tries to have the same " "color translate properly between color devices." msgstr "" "La gestió del color és, en poques paraules, un conjunt de sistemes que " "intenten que el mateix color es tradueixi correctament entre els dispositius " "de color." #: ../../general_concepts/colors/color_managed_workflow.rst:82 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." msgstr "" "Normalment treballeu intentant cobrir un color a l'espai de color de " "referència XYZ. XYZ és un sistema de coordenades que té un punt per a tots " "els colors que pot veure l'ull humà." #: ../../general_concepts/colors/color_managed_workflow.rst:84 msgid "" "From XYZ it can then be translated back into another device space, such as " "RGB (for screens), or CMYK (for printers)." msgstr "" "A partir de XYZ, es pot traduir de nou a un altre espai de dispositiu, com " "ara RGB (per a les pantalles) o CMYK (per a les impressores)." #: ../../general_concepts/colors/color_managed_workflow.rst:86 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." msgstr "" "El Krita té dos sistemes dedicats a la gestió del color. D'una banda, tenim " "la biblioteca **lcms2**, la qual tracta de perfils ICC i de l'altra tenim " "**OCIO**, el qual tracta la gestió del color LUT." #: ../../general_concepts/colors/color_managed_workflow.rst:88 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." msgstr "" "Per donar una estimació aproximada, els perfils ICC s'ocupen de mantenir els " "colors coherents a través de moltes interpretacions de dispositius " "(pantalles, impressores) emprant un espai de referència i OCIO tracta de " "manipular la interpretació d'aquests colors." #: ../../general_concepts/colors/color_managed_workflow.rst:90 msgid "Within both we can identify the following color spaces:" msgstr "Dins de tots dos podem identificar els següents espais de color:" #: ../../general_concepts/colors/color_managed_workflow.rst:93 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 " "`." msgstr "" "Els espais de dispositiu són els que descriuen el vostre monitor i s'han de " "fer amb un petit dispositiu anomenat «colorímetre». Aquest dispositiu, " "juntament amb el programari adequat, mesura el vermell, el verd i el blau " "més forts que pot produir la pantalla, així com el blanc, el negre i el gris " "que produeix. Mitjançant aquestes i altres mesures, es crearà un perfil ICC " "únic per a la pantalla. L'establireu a la pestanya gestió del color del " "Krita. De manera predeterminada assumim sRGB per a les pantalles, però és " "molt probable que la vostra pantalla no s'ajusti exactament al sRGB, " "sobretot si teniu una pantalla d'alta qualitat, on aquest espai podria ser " "més gran. Els espais de dispositiu també són el motiu pel qual haureu de " "consultar primer amb les especificacions de la vostra impressora per a saber " "quin perfil espera. Moltes impremtes tenen els seus propis perfils de " "dispositiu per a les seves impressores, o bé poden preferir la conversió del " "color. Podeu llegir més sobre l'ús del colorímetre :ref:`aquí " "`." #: ../../general_concepts/colors/color_managed_workflow.rst:94 msgid "Device spaces" msgstr "Espais de dispositiu" #: ../../general_concepts/colors/color_managed_workflow.rst:96 msgid "Working spaces" msgstr "Espais de treball" #: ../../general_concepts/colors/color_managed_workflow.rst:97 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." msgstr "" "Aquests es lliuren al costat del Krita per a ICC i es poden descarregar des " "del lloc web de l'OCIO per a OCIO. Els espais de treball són especialment " "agradables per a fer càlculs de colors, els quals programes com el Krita " "faran sovint. Per tant, es recomana tenir un perfil de l'espai de treball " "per a la vostra imatge." #: ../../general_concepts/colors/color_managed_workflow.rst:99 msgid "Aesthetic or Look spaces" msgstr "Espais d'estètica o d'aspecte" #: ../../general_concepts/colors/color_managed_workflow.rst:99 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." msgstr "" "Són espais especials que s'han deformat per a donar un cert aspecte a una " "imatge. El Krita no lliura perfils d'aspecte per a ICC, ni tampoc admet " "encara els espais d'aspecte per a OCIO." #: ../../general_concepts/colors/color_managed_workflow.rst:102 msgid "Color managed workflow" msgstr "Flux de treball gestionant el color" #: ../../general_concepts/colors/color_managed_workflow.rst:104 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:" msgstr "" "Per descomptat, saber això sobre aquests espais no us donarà una idea de com " "emprar-los, però sí farà que sigui més fàcil explicar-ho. De manera que " "farem una ullada a un flux de treball típic amb la gestió del color:" #: ../../general_concepts/colors/color_managed_workflow.rst:110 msgid ".. image:: images/color_category/Krita-colormanaged-workflow_text.svg" msgstr ".. image:: images/color_category/Krita-colormanaged-workflow_text.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:110 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." msgstr "" "Un exemple típic d'un flux de treball gestionant el color. Tenim l'entrada " "des dels escàners i càmeres, la qual convertirem a un espai de treball que " "es pugui utilitzar entre el diferent programari d'edició i convertir-la en " "un espai de sortida per a la visualització a la pantalla o per a la " "impressió." #: ../../general_concepts/colors/color_managed_workflow.rst:112 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." msgstr "" "En un flux de treball amb la gestió tradicional del color, normalment pensem " "en termes de colors en el món real que es converteixen en colors de " "l'ordinador i, a l'inrevés. Per exemple, les fotografies des d'una càmera o " "escanejades en imatges. Si teniu un espai de dispositiu d'aquest tipus, " "primer assignarem l'espai de dispositiu a la imatge i després la convertirem " "a un espai de treball." #: ../../general_concepts/colors/color_managed_workflow.rst:114 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." msgstr "" "A continuació, farem tota la nostra edició en l'espai de treball i " "utilitzarem l'espai de treball per a comunicar entre els programes d'edició. " "En el cas del Krita, a causa que té dos sistemes per a la gestió del color, " "utilitzem perfils ICC entre els programes com el Gimp 2.9+, Inkscape, " "digiKam i Scribus, i la configuració de l'OCIO entre el Blender i Natron." #: ../../general_concepts/colors/color_managed_workflow.rst:116 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." msgstr "" "També podeu emmagatzemar els fitxers de treball en l'espai de treball, igual " "que la forma com tindreu les capes sense fusionar al fitxer de treball o " "tenir-les a una resolució molt alta." #: ../../general_concepts/colors/color_managed_workflow.rst:118 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." msgstr "" "De vegades, apliquem espais estètics o d'«aspecte» a una imatge com a part " "del procés d'edició. Això és força avançat i probablement no us n'hauríeu de " "preocupar en el cas del Krita." #: ../../general_concepts/colors/color_managed_workflow.rst:120 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." msgstr "" "Aleshores, quan hàgim acabat d'editar, intentarem convertir-les a un espai " "de sortida, el qual és un altre espai de dispositiu. Pot ser CMYK per a " "impressores o un perfil RGB especial de pantalla. Quan es tracta d'impremtes " "professionals, el millor és preguntar sobre aquest pas. Ells tenen un munt " "d'experiència amb la millor conversió i poden preferir la conversió des del " "vostre espai de treball a l'espai de dispositiu de les seves impressores." #: ../../general_concepts/colors/color_managed_workflow.rst:122 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." msgstr "" "Una altra forma de sortida és la manera en què la pantalla mostra el color. " "A diferència de la sortida habitual, aquesta es fa tot el temps durant " "l'edició: després de tot, necessiteu veure el que esteu fent, però la " "pantalla continua sent un dispositiu amb un espai de dispositiu, de manera " "que distorsiona l'aspecte de la imatge. D'aquesta manera, podeu veure la " "pantalla com un joc de prismàtics pels que mireu per a veure la imatge." #: ../../general_concepts/colors/color_managed_workflow.rst:124 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." msgstr "" "Per tant, sense un monitor amb perfil, en realitat no sabreu com són els " "colors reals amb els que esteu treballant, ja que l'ordinador no coneix les " "propietats rellevants de la pantalla. De manera que si creeu un perfil per " "al monitor, indiqueu-li al Krita des dels ajustaments i seleccioneu l'espai " "sRGB per a dibuixar, i ara veureu per primera vegada els colors reals de " "l'espai sRGB." #: ../../general_concepts/colors/color_managed_workflow.rst:127 msgid "So what does this mean?" msgstr "Què vol dir això?" #: ../../general_concepts/colors/color_managed_workflow.rst:133 msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_krita_text.svg" msgstr "" ".. image:: images/color_category/Krita-colormanaged-workflow_krita_text.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:133 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." msgstr "" "Quan pintem des de zero, veurem el nostre perfil de pantalla com a l'espai " "d'entrada, perquè l'utilitzem per a determinar quins colors triar. Això " "simplifica el flux de treball, però fa que el perfil de la pantalla i les " "condicions de la visualització siguin més importants." # Nota: https://ca.wikipedia.org/wiki/Etalonatge_digital #: ../../general_concepts/colors/color_managed_workflow.rst:135 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*." msgstr "" "Ara, els fotògrafs i la gent que fan una disciplina complicada dels efectes " "visuals (VFX) anomenada «etalonatge» («color grading») es tornaran " "completament boges en intentar obtenir els colors que posen el 100% " "correctes, i fins i tot han de comptar amb factors com ara el dia i el color " "en el que estan pintades les seves parets. Per exemple, si la paret al " "darrere de l'ordinador és de color vermell pur, els ulls s'ajustaran per ser " "menys sensibles al vermell, el qual vol dir que els colors que es triïn al " "programa podrien aparèixer més vermells. Això s'anomena les *condicions de " "la visualització*." #: ../../general_concepts/colors/color_managed_workflow.rst:137 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." msgstr "" "Afortunadament, els artistes es poden preocupar molt menys en això. Ja que " "les il·lustracions són completament artesanals, podrem identificar els bits " "importants i fer contrastos adequats entre els colors. Això vol dir que fins " "i tot si les nostres imatges resulten ser una mica més vermelles del que es " "pretén, és menys probable que s'arruïni tota la imatge. Si mirem enrere, a " "l'exemple anterior de l'escola bressol, encara entenem com hauria de ser la " "imatge, tot i que hi hagi diferents colors a cada imatge. A més, com que els " "colors de les il·lustracions es trien deliberadament, podem corregir-los amb " "més facilitat en una data posterior. Tanmateix, és evident que serà un gran " "problema fer-ho, i podríem haver tingut molta més flexibilitat si haguéssim " "tingut en compte les condicions de la visualització." #: ../../general_concepts/colors/color_managed_workflow.rst:139 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." msgstr "" "Dit això, per als artistes també és molt útil entendre els espais de " "treball. Els diferents espais de treball donen resultats diferents amb els " "filtres i la mescla, i per a tecnologies avançades com el HDR només es poden " "utilitzar alguns espais de treball." #: ../../general_concepts/colors/color_managed_workflow.rst:141 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." msgstr "" "De la mateixa manera, el Krita, com un programa destinat a crear imatges des " "de zero, en realitat no es preocupa d'assignar els espais de treball després " "de crear la imatge. Però com que esteu utilitzant la pantalla com uns " "prismàtics per mirar la imatge i per triar els colors, veureu l'espai del " "dispositiu de la pantalla com a un espai d'entrada a la imatge. Per tant, " "elaborar el perfil del vostre monitor i indicar-li al Krita mitjançant els " "ajustaments us ajudarà a preparar el vostre treball per a la impressió i " "futures aventures a llarg termini." #: ../../general_concepts/colors/color_managed_workflow.rst:143 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.)" msgstr "" "En general, és útil mantenir les coses com ara les condicions de la " "visualització al fons de la vostra ment. Molts artistes professionals " "utilitzen un color gris mig com a fons predeterminat del llenç, ja que " "troben que es creen imatges molt més dinàmiques a causa de la millora en les " "condicions de la visualització. També és per això que molts programes " "gràfics, incloent-hi el Krita, tenen avui un tema fosc. (Tot i que, per " "descomptat, això també pot ser perquè els temes foscos es poden considerar " "genials, qui sap)." #: ../../general_concepts/colors/color_managed_workflow.rst:148 msgid "ICC profiles" msgstr "Perfils ICC" #: ../../general_concepts/colors/color_managed_workflow.rst:150 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:" msgstr "" "Un perfil ICC és un conjunt de coordenades que descriuen les extremitats de " "l'espai del dispositiu amb XYZ, i són les dades de la gestió del color que " "utilitzareu per a comunicar el vostre espai de treball a les impressores i " "aplicacions dissenyades per a la indústria gràfica, com ara el Gimp, " "Scribus, Photoshop, Illustrator, Inkscape, digiKam, RawTheraphee, etc. Teniu " "dos tipus de perfils ICC:" #: ../../general_concepts/colors/color_managed_workflow.rst:153 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." msgstr "" "Es lliuren al costat del Krita. Els perfils de configuració de matrius es " "creen ajustant els paràmetres i interpolant-los per obtenir la mida exacta " "de l'espai de color. Per això, el navegador de l'espai de color del Krita " "pot proporcionar molta informació sobre aquests perfils. Aquests perfils " "també són preferibles com a espai de treball." #: ../../general_concepts/colors/color_managed_workflow.rst:159 msgid "Matrix Shaper profiles" msgstr "Perfils de configuració de matrius" #: ../../general_concepts/colors/color_managed_workflow.rst:159 msgid "" "Matrix shaper profiles have a few parameters that describe the color space " "which are then interpolated between, this requires a lot of maths." msgstr "" "Els perfils de configuració de matrius tenen uns quants paràmetres que " "descriuen l'espai de color entre el qual s'interpolen i requereixen un munt " "de matemàtiques." #: ../../general_concepts/colors/color_managed_workflow.rst:162 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." msgstr "" "Aquests són molt rars i principalment s'utilitzen per a descriure els " "perfils de la impressora, com ara el CMYK. Els perfils de la taula de cerca " "del color o cLUT emmagatzemen moltes més dades que els perfils de " "configuració de matrius, de manera que poden contenir dades de petites " "particularitats causades, per exemple, per resultats inesperats en la mescla " "dels pigments. Aquest és un enfocament molt més orgànic per a descriure un " "espai de color, per això, molts programes que no tenen cura de la gestió del " "color no els admeten." #: ../../general_concepts/colors/color_managed_workflow.rst:168 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." msgstr "" "Els perfils de la cLUT funcionen mantenint les taules de cada color en un " "espai de color i les seves respectives coordenades en un espai de " "referència. Per al CMYK, normalment és L\\*A\\*B\\* i per a la resta XYZ. " "Aquestes taules són difícils de crear, el qual vol dir que aquests perfils " "són molt més rars." #: ../../general_concepts/colors/color_managed_workflow.rst:169 msgid "cLUT profiles" msgstr "Perfils de la cLUT" #: ../../general_concepts/colors/color_managed_workflow.rst:171 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." msgstr "" "El més interessant dels perfils ICC és que el vostre espai de treball pot " "ser més gran que l'espai del dispositiu. Això generalment no és dolent. No " "obstant això, en convertir-los acabareu amb la pregunta de com traduir els " "valors de l'espai de treball." #: ../../general_concepts/colors/color_managed_workflow.rst:174 msgid "Perceptual" msgstr "Perceptiu" #: ../../general_concepts/colors/color_managed_workflow.rst:174 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." msgstr "" "Simplement retalla els valors de l'espai de treball a l'espai al qual es " "converteix. És un bon mètode per a veure tots els valors possibles, però no " "tan bo si voleu una reproducció precisa del color. Utilitzeu-lo si voleu " "veure tots els colors d'una imatge o si voleu expressar tots els contrastos " "possibles. No funciona amb els perfils de configuració de matrius, els quals " "estan de manera predeterminada en colorimetria relativa." #: ../../general_concepts/colors/color_managed_workflow.rst:177 msgid "Absolute Colorimetric" msgstr "Colorimetria absoluta" #: ../../general_concepts/colors/color_managed_workflow.rst:177 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." msgstr "" "El contrari de la colorimetria perceptiva, l'absoluta intentarà conservar " "tots els colors correctes a qualsevol preu, el qual pot resultar en colors " "horribles. Només recomanat per a treballs de reproducció. Al Krita no " "funciona amb els perfils de configuració de matrius, a causa dels estàndards " "al flux de treball ICC v4." #: ../../general_concepts/colors/color_managed_workflow.rst:180 msgid "Relative Colorimetric" msgstr "Colorimetria relativa" #: ../../general_concepts/colors/color_managed_workflow.rst:180 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." msgstr "" "Una solució intermèdia entre perceptiu i absoluta, la relativa intentarà " "ajustar-se als colors que puguin coincidir entre els espais de color. Ho fa " "alineant els punts blanc i negre. Retalla la resta a les seves vores " "respectives. Això és el que tots els perfils de configuració de matrius " "predeterminats fan durant la conversió, ja que el flux de treball ICC v4 " "especifica només utilitzar la colorimetria relativa per als perfils de " "configuració de matrius." #: ../../general_concepts/colors/color_managed_workflow.rst:183 msgid "Saturation" msgstr "Saturació" #: ../../general_concepts/colors/color_managed_workflow.rst:183 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." msgstr "" "Sacrificarà qualsevol cosa per a retenir el color, fins i tot el to. " "S'utilitza en les infografies. No funciona amb els perfils de configuració " "de matrius, els quals estan de manera predeterminada en colorimetria " "relativa." #: ../../general_concepts/colors/color_managed_workflow.rst:185 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." msgstr "" "La *versió del perfil ICC* és l'últim que cal tenir en compte a l'hora de " "tractar amb els perfils ICC. El Krita lliura perfils tant de la versió 2 com " "de la versió 4, mentre que l'última versió dóna millors resultats en fer les " "matemàtiques del color, la primera està més àmpliament admesa (tal com es " "veu a continuació a «Interacció amb les altres aplicacions»). Per això, el " "Krita també ve amb la v2 de manera predeterminada i us recomanem que " "utilitzeu la v2 quan no esteu segur si els altres programes que utilitzeu " "són compatibles amb la v4." #: ../../general_concepts/colors/color_managed_workflow.rst:188 msgid "LUT docker and HDR imaging" msgstr "Acoblador de la LUT i imatges en HDR" #: ../../general_concepts/colors/color_managed_workflow.rst:196 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." msgstr "" "La :ref:`lut_docker` és la segona part important de la gestió del color en " "el Krita, es comparteix entre el Krita i programes com el Blender, Natron i " "Nuke, i només utilitza les taules de cerca que es configuren mitjançant un " "fitxer de configuració." #: ../../general_concepts/colors/color_managed_workflow.rst:198 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." msgstr "" "Podeu establir l'espai de treball de la imatge sota l'espai de color " "d'entrada, i la pantalla a sRGB o la vostra pròpia LUT si l'heu afegit a la " "configuració. La visualització en aquest cas serà per a la transformació de " "provatures amb un determinat dispositiu de visualització." #: ../../general_concepts/colors/color_managed_workflow.rst:200 msgid "" "Component, exposure, gamma, whitepoint and blackpoint are knobs which allows " "you to modify the display filter." msgstr "" "El component, l'exposició, la gamma, el punt blanc i el punt negre són " "comandaments que permeten modificar el filtre de la pantalla." #: ../../general_concepts/colors/color_managed_workflow.rst:208 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." msgstr "" "Com s'ha explicat abans, el món de la nostra imatge el veurem al nostre " "monitor com amb un telescopi o uns prismàtics. Això vol dir que es " "distorsionarà una mica la vista de la imatge. Però podrem modificar aquests " "prismàtics o el filtre de la pantalla per a veure la nostra imatge d'una " "manera diferent. Per exemple, per a que ens permeti veure el blanc en una " "imatge més blanca que la pantalla. Per explicar què vol dir això, haurem de " "pensar en què és el blanc." #: ../../general_concepts/colors/color_managed_workflow.rst:210 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." msgstr "" "Per exemple, el blanc, al nostre monitor està ple de vermell, verd i blau. " "Però, sens dubte, és diferent del blanc al nostre paper, o del color de la " "llet, el blanc del sol, o fins i tot el blanc del nostre telèfon mòbil." #: ../../general_concepts/colors/color_managed_workflow.rst:212 msgid "" "Black similarly, is brighter on a LCD display than a LED one, and " "incomparable with the black of a carefully sealed room." msgstr "" "De manera similar, el negre és més brillant en una pantalla LCD que en una " "LED, i és incomparable amb el negre d'una habitació acuradament segellada." #: ../../general_concepts/colors/color_managed_workflow.rst:214 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." msgstr "" "Això vol dir que hi ha negres potencialment més negres que el negre de la " "pantalla i els blancs són més blancs que el blanc de la pantalla. No obstant " "això, per a simplificar, encara assignem el punt negre i el punt blanc a " "certs valors. A partir d'aquí, podrem determinar si un blanc és més blanc " "que el punt blanc, o un negre és més negre que el punt negre." #: ../../general_concepts/colors/color_managed_workflow.rst:216 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." msgstr "" "L'acoblador de la LUT ens permet controlar aquest filtre de la pantalla i " "modificar la distorsió. Això és útil quan comencem a modificar imatges que " "es creen amb valors en referència a l'escena, com ara fotografies en HDR o " "imatges que surten d'un motor de renderitzat." #: ../../general_concepts/colors/color_managed_workflow.rst:224 msgid "" "So, for example, we can choose to scale whiter-than-screen-white to our " "screen-white so we can see the contrasts there." msgstr "" "Així, per exemple, triarem l'escala més blanca que el blanc de la pantalla " "al nostre blanc de la pantalla, de manera que puguem veure els contrastos." #: ../../general_concepts/colors/color_managed_workflow.rst:226 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." msgstr "" "El punt d'això és que aprofitareu els detalls de més claredat en una imatge. " "Si bé no es podrà veure la diferència entre el blanc de la pantalla i el més " "blanc que el blanc de la pantalla (perquè la pantalla no pot mostrar la " "diferència), els programes gràfics sí que poden utilitzar-ho." #: ../../general_concepts/colors/color_managed_workflow.rst:228 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." msgstr "" "Un exemple comú és fer coincidir la il·luminació entre un model en 3D i una " "escena del món real. Altres són un retoc fotogràfic avançat, amb molta més " "informació disponible per a l'usuari sobre el contrast. En la pintura en sí, " "això permetrà crear una imatge en la que podreu ser impetuós amb el " "contrast, i fer-la tan brillant com us agradaria." #: ../../general_concepts/colors/color_managed_workflow.rst:230 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." msgstr "" "Les manipulacions a l'acoblador de la LUT són per a la visualització, de " "manera que podreu crear una nova visualització i establir-la a Lluminositat. " "D'aquesta manera, veureu la imatge tant en color com en escala de grisos i " "mantindreu bon ull en els vostres valors." #: ../../general_concepts/colors/color_managed_workflow.rst:232 msgid "" "Another example is to carefully watch the gradients in a certain section." msgstr "" "Un altre exemple és observar amb atenció els degradats d'una determinada " "secció." #: ../../general_concepts/colors/color_managed_workflow.rst:234 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." msgstr "" "Igual que ICC, l'acoblador de la LUT permet crear una mena de perfil per al " "vostre dispositiu. En aquest cas és la «LUT», el qual vol dir «taula de " "cerca» i la qual es pot afegir a OCIO modificant el fitxer de configuració. " "Quan OCIO estigui activat, la configuració a :menuselection:`Arranjament --> " "Configura el Krita --> Gestió del color` estarà desactivada, llevat que " "utilitzeu el motor de color :guilabel:`Intern`." #: ../../general_concepts/colors/color_managed_workflow.rst:237 msgid "In summary" msgstr "En resum" #: ../../general_concepts/colors/color_managed_workflow.rst:239 msgid "Krita has two modes of color management:" msgstr "El Krita té dos modes per a la gestió del color:" #: ../../general_concepts/colors/color_managed_workflow.rst:241 msgid "" "ICC works in terms of spaces relative to the CIEXYZ space, and requires an " "ICC profile." msgstr "" "ICC treballa en termes relatius als espais a l'espai CIEXYZ, i requereix un " "perfil ICC." #: ../../general_concepts/colors/color_managed_workflow.rst:242 msgid "OCIO works in terms of interpretation, and makes use of LUTs." msgstr "OCIO treballa en termes d'interpretació, i fa ús de les LUT." #: ../../general_concepts/colors/color_managed_workflow.rst:243 msgid "both can be made with a colorimeter." msgstr "Ambdós es poden crear amb un colorímetre." #: ../../general_concepts/colors/color_managed_workflow.rst:244 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." msgstr "" "Si voleu tenir un flux de treball adequat gestionant el color, tingueu-ne un " "personalitzat per al dispositiu d'entrada (la vostra pantalla) i els " "dispositius de sortida (la vostra impressora o pantalla de destinació). Per " "a la web, la sortida sempre serà sRGB." #: ../../general_concepts/colors/color_managed_workflow.rst:245 msgid "" "Set up your screen profiles under :menuselection:`Settings --> Configure " "Krita --> Color management`." msgstr "" "Configureu els perfils de la pantalla sota :menuselection:`Arranjament --> " "Configura el Krita --> Gestió del color`." #: ../../general_concepts/colors/color_managed_workflow.rst:246 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." msgstr "" "NO utilitzeu els perfils de la pantalla o altres perfils de dispositiu per a " "dibuixar. Utilitzeu un perfil de l'espai de treball com qualsevol dels " "perfils «elle» per a això, farà que les matemàtiques del color siguin molt " "més predictibles i agradables. El Krita convertirà entre l'espai de la " "pantalla i l'espai de treball sobre la marxa, permetent triar els colors " "correctes. Això convertirà la pantalla en prismàtics per a veure la imatge." #: ../../general_concepts/colors/color_managed_workflow.rst:247 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." msgstr "" "Utilitzeu la gestió del color adequada per al flux de treball adequat. Si " "esteu treballant amb el Blender, serà millor que utilitzeu OCIO, millor que " "ICC. Si esteu treballant amb Scribus o Photoshop, utilitzeu ICC." #: ../../general_concepts/colors/color_managed_workflow.rst:249 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." msgstr "" "El Krita fa un munt de matemàtiques del color, sovint en relació amb la " "barreja dels colors. Aquestes matemàtiques del color funcionen millor en " "l'espai de color lineal, i aquest requereix una profunditat de bits " "d'almenys 16 bits per a funcionar. El desavantatge és que l'espai lineal pot " "ser confús per a treballar." #: ../../general_concepts/colors/color_managed_workflow.rst:251 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!" msgstr "" "Si us agrada pintar, tingueu una bona quantitat de RAM i cerqueu començar " "els vostres passos de novell aprofitant la gestió del color del Krita, " "intenteu actualitzar de tenir totes les imatges en sRGB incorporat al sRGB-" "v2-elle-g10.icc o rec2020-v2-elle-g10.icc amb flotant de 16 bits. Això " "donarà una millor barreja del color al mateix temps que obrirà la " "possibilitat que comenceu a treballar en HDR!" #: ../../general_concepts/colors/color_managed_workflow.rst:256 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!" msgstr "" "Algunes targetes gràfiques, com les de la marca NVidia, en realitat tenen el " "millor rendiment sota flotant de 16 bits, perquè les targetes NVidia " "converteixen internament a coma flotant. Quan no cal fer-ho, es va més ràpid!" #: ../../general_concepts/colors/color_managed_workflow.rst:260 msgid "" "No amount of color management in the world can make the image on your screen " "and the image out of the printer have 100% the same color." msgstr "" "Cap quantitat de gestió del color en el món farà que la imatge que surti a " "la pantalla i de la impressora tingui el 100% del mateix color." #: ../../general_concepts/colors/color_managed_workflow.rst:263 msgid "Exporting" msgstr "Exportar" #: ../../general_concepts/colors/color_managed_workflow.rst:265 msgid "" "When you have finished your image and are ready to export it, you can modify " "the color space to optimize it:" msgstr "" "En finalitzar la vostra imatge i quan estigueu llest per exportar-la, podreu " "modificar l'espai de color per optimitzar-la:" #: ../../general_concepts/colors/color_managed_workflow.rst:267 msgid "If you are preparing an image for the web:" msgstr "Si esteu preparant una imatge per a la web:" #: ../../general_concepts/colors/color_managed_workflow.rst:269 msgid "" "If you use 16bit color depth or higher, convert the image to 8bit color " "depth. This will make the image much smaller." msgstr "" "Si utilitzeu una profunditat del color de 16 bits o superior, convertiu la " "imatge a una profunditat del color de 8 bits. Això farà que la imatge sigui " "molt més petita." #: ../../general_concepts/colors/color_managed_workflow.rst:271 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." msgstr "" "En l'actualitat, el Krita no té una juxtaposició incorporada, el qual vol " "dir que les conversions de 16 a 18 bits poden sortir una mica amb efecte de " "cartell. Però podreu simular afegint una capa d'emplenat amb un patró, " "configurant aquesta capa d'emplenat a superposició i amb un 5% d'opacitat. " "Després aplaneu tota la imatge i convertiu-la a 8 bits. El patró funcionarà " "com a juxtaposició donant una aparença més suau als degradats." #: ../../general_concepts/colors/color_managed_workflow.rst:273 msgid "If it's a gray-scale image, convert it to gray-scale." msgstr "Si és una imatge en escala de grisos, convertiu-la a escala de grisos." #: ../../general_concepts/colors/color_managed_workflow.rst:274 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." msgstr "" "Si es tracta d'una imatge en color, mantingueu-la en el perfil de l'espai de " "treball: en l'actualitat, molts navegadors web admeten perfils de color " "incrustats en les imatges. El Firefox, per exemple, intentarà convertir la " "vostra imatge perquè s'ajusti al perfil de color de l'altre monitor (si en " "té un). D'aquesta manera, la imatge es veurà gairebé igual que a la vostra " "pantalla i en els altres monitors amb perfil." # skip-rule: t-acc_obe #: ../../general_concepts/colors/color_managed_workflow.rst:279 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 " "`_, save your PNG, JPG or TIFF without an embedded profile to work " "around this." msgstr "" "En algunes versions del Firefox, els colors en realitat es veuran estranys: " "aquest és un error al Firefox, ja que el seu `sistema per a la gestió del " "color està incomplet `_, deseu el vostre PNG, JPG o TIFF sense un " "perfil incrustat per a solucionar aquest problema." #: ../../general_concepts/colors/color_managed_workflow.rst:281 msgid "If you are preparing for print:" msgstr "Si esteu preparant per a imprimir:" #: ../../general_concepts/colors/color_managed_workflow.rst:283 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." msgstr "" "Esperem que hagueu creat la imatge en un perfil de l'espai de treball en " "comptes del perfil personalitzat real de la pantalla, si no, convertiu-lo a " "quelcom com Adobe RGB, sRGB o Rec. 2020." #: ../../general_concepts/colors/color_managed_workflow.rst:284 msgid "" "Check with the printer what kind of image they expect. Maybe they expect " "sRGB color space, or perhaps they have their own profile." msgstr "" "Comproveu amb la impressora quin tipus d'imatge espera. Potser l'espera en " "un espai de color sRGB, o potser té el seu propi perfil." #: ../../general_concepts/colors/color_managed_workflow.rst:287 msgid "Interaction with other applications" msgstr "Interacció amb les altres aplicacions" #: ../../general_concepts/colors/color_managed_workflow.rst:290 msgid "Blender" msgstr "Blender" #: ../../general_concepts/colors/color_managed_workflow.rst:292 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." msgstr "" "Si voleu utilitzar la funcionalitat OCIO del Krita, i en particular en " "combinació amb la gestió del color del Blender, intenteu que s'utilitzi la " "configuració de l'OCIO del Blender." # skip-rule: t-acc_obe #: ../../general_concepts/colors/color_managed_workflow.rst:294 msgid "" "Blender's OCIO config is under ``/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." msgstr "" "La configuració de l'OCIO del Blender es troba a ``/" "número_de_la_versió/datafiles/colormanagement``. Establiu l'acoblador de la " "LUT per utilitzar el motor OCIO i seleccioneu la configuració amb aquest " "camí. Això donarà els espais de l'entrada i de la pantalla del Blender, però " "no d'aspecte, ja que el Krita encara no l'admet." #: ../../general_concepts/colors/color_managed_workflow.rst:298 msgid "Windows Photo Viewer" msgstr "El visor Windows Photo" #: ../../general_concepts/colors/color_managed_workflow.rst:300 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." msgstr "" "És possible que trobeu alguns problemes en utilitzar diferents aplicacions " "juntes. Una cosa important a tenir en compte és que l'aplicació estàndard de " "Windows Photo Viewer no maneja els perfils ICC moderns. El Krita empra els " "perfils de la versió 4. El Photo Viewer només pot gestionar els perfils de " "la versió 2. Si exporteu a JPEG amb un perfil incrustat, el Photo Viewer " "mostrarà la vostra imatge massa fosca." #: ../../general_concepts/colors/color_managed_workflow.rst:303 msgid "Example workflows" msgstr "Fluxos de treball d'exemple" #: ../../general_concepts/colors/color_managed_workflow.rst:305 msgid "" "Here are some example workflows to get a feeling of how your color " "management workflow may look like." msgstr "" "Aquests són alguns exemples de fluxos de treball per a tenir una idea de com " "es veurà el vostre flux de treball en gestionar el color." #: ../../general_concepts/colors/color_managed_workflow.rst:307 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'." msgstr "" "Com s'ha esmentat anteriorment, l'entrada per a la vostra pantalla " "s'estableix a :menuselection:`Arranjament --> Configura el Krita --> Gestió " "del color`, o mitjançant l'«Espai de la pantalla» de l'acoblador de la LUT. " "L'espai de treball s'establirà mitjançant el nou fitxer per document, o a " "l'acoblador de la LUT mitjançant l'«Espai de l'entrada»." #: ../../general_concepts/colors/color_managed_workflow.rst:310 msgid "Webcomic" msgstr "Còmic a la web" #: ../../general_concepts/colors/color_managed_workflow.rst:317 #: ../../general_concepts/colors/color_managed_workflow.rst:339 #: ../../general_concepts/colors/color_managed_workflow.rst:357 msgid "Input" msgstr "Entrada" #: ../../general_concepts/colors/color_managed_workflow.rst:318 #: ../../general_concepts/colors/color_managed_workflow.rst:340 #: ../../general_concepts/colors/color_managed_workflow.rst:358 msgid "Your screen profile. (You pick colors via your screen)" msgstr "" "El vostre perfil de la pantalla. (Trieu els colors a través de la pantalla)." #: ../../general_concepts/colors/color_managed_workflow.rst:319 #: ../../general_concepts/colors/color_managed_workflow.rst:341 #: ../../general_concepts/colors/color_managed_workflow.rst:359 msgid "Workingspace" msgstr "Espai de treball" #: ../../general_concepts/colors/color_managed_workflow.rst:320 msgid "" "sRGB (the default screen profile) or any larger profile if you can spare the " "bit depth and like working in them." msgstr "" "sRGB (el perfil predeterminat de la pantalla) o qualsevol perfil més gran si " "estalvieu en la profunditat de bits i hi voleu treballar." #: ../../general_concepts/colors/color_managed_workflow.rst:322 #: ../../general_concepts/colors/color_managed_workflow.rst:344 #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "Output" msgstr "Sortida" #: ../../general_concepts/colors/color_managed_workflow.rst:322 msgid "" "sRGB, ICC version 2, sRGB TRC for the internet, and a specialized CMYK " "profile from the printing house for the printed images." msgstr "" "sRGB, ICC versió 2, el TRC en sRGB per a Internet i un perfil CMYK " "especialitzat de la impremta per a les imatges impreses." #: ../../general_concepts/colors/color_managed_workflow.rst:324 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." msgstr "" "Utilitzeu sRGB-elle-V2-srgbtrc.icc per anar entre Inkscape, Photoshop, " "Painttool Sai, Illustrator, Gimp, Manga Studio, Paintstorm Studio, MyPaint, " "Artrage, Scribus, etc. i el Krita." #: ../../general_concepts/colors/color_managed_workflow.rst:326 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." msgstr "" "Si utilitzeu un espai més gran a través d'ICC, només podreu intercanviar " "entre el Krita, Photoshop, Illustrator, Gimp 2.9, Manga Studio i Scribus. " "Tots els altres assumeixen sRGB per a l'espai, sense importar el què, perquè " "no tenen gestió del color." #: ../../general_concepts/colors/color_managed_workflow.rst:328 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." msgstr "" "Si aneu entre el Krita i el Blender, Nuke o Natron, utilitzeu OCIO i " "establiu l'espai de l'entrada a «sRGB», però assegureu-vos de seleccionar el " "perfil sRGB per a ICC en crear un fitxer nou." #: ../../general_concepts/colors/color_managed_workflow.rst:330 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." msgstr "" "Al final, per a la web, convertiu la imatge a sRGB de 8 bits, «srgbtrc», no " "incrusteu el perfil ICC. Després, si empreu PNG, passeu-lo a través d'alguna " "cosa com «pngcrush» o altres optimitzadors de PNG. En aquest cas, es tria " "sRGB perquè suposem que la gran majoria de la vostra audiència no ha creat " "un perfil per a la seva pantalla, ni tenen pantalles prou avançades per a " "una gamma àmplia de coses. Per això, convertirem a la pantalla " "predeterminada per a internet, sRGB." #: ../../general_concepts/colors/color_managed_workflow.rst:333 msgid "Print" msgstr "Imprimir" #: ../../general_concepts/colors/color_managed_workflow.rst:342 msgid "sRGB or Rec. 2020 if you can afford the bit-depth being 16bit." msgstr "" "sRGB o Rec. 2020 si us podeu permetre que la profunditat de bits sigui de 16 " "bits." #: ../../general_concepts/colors/color_managed_workflow.rst:344 msgid "" "Specialized CMYK profile from the printing house for the printed images." msgstr "Perfil CMYK especialitzat de la impremta per a les imatges impreses." #: ../../general_concepts/colors/color_managed_workflow.rst:346 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." msgstr "" "Els perfils CMYK són diferents per impressora, i fins i tot per paper o " "tipus de tinta, així que no sigueu presumptuós i pregunteu-li, en lloc de " "fer quelcom com intentar pintar amb qualsevol perfil CMYK aleatori. Com s'ha " "mencionat a la secció de condicions de la visualització, voldreu mantenir " "les vostres opcions obertes." #: ../../general_concepts/colors/color_managed_workflow.rst:348 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." msgstr "" "Podeu establir el Selector avançat del color perquè transformi a un perfil " "determinat a través d':menuselection:`Arranjament --> Configura el Krita --> " "Ajustaments per al selector de color`. Allà, marqueu :guilabel:`El selector " "de color empra un espai de color diferent de la imatge` i seleccioneu el " "perfil CMYK al qual apuntar. Això limitarà una mica els vostres colors, però " "mantindreu totes les opcions de filtre i barreja agradables del RGB." #: ../../general_concepts/colors/color_managed_workflow.rst:351 msgid "Games" msgstr "Jocs" #: ../../general_concepts/colors/color_managed_workflow.rst:360 msgid "sRGB or grayscale linear for roughness and specular maps." msgstr "" "sRGB o escala de grisos lineal per als mapes amb rugositat i especulars." #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "" "This one is tricky, but in the end it'll be sRGB for the regular player." msgstr "Aquesta és complicada, però al final serà sRGB per al jugador normal." #: ../../general_concepts/colors/color_managed_workflow.rst:364 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." msgstr "" "De manera que aquest és complicat. Empreu OCIO i ICC entre els programes, " "però es recomana tenir les vostres imatges al motor en sRGB o en escala de " "grisos. Avui dia, molts renderitzadors basats en la física permeten establir " "si una imatge s'haurà de llegir com una imatge lineal o «srgbtrc», i això és " "fins i tot vital perquè les imatges es considerin correctament en els " "càlculs basats en la física del renderitzador del joc." #: ../../general_concepts/colors/color_managed_workflow.rst:366 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." msgstr "" "Si bé els motors dels jocs necessiten tenir optimitzat el contingut, i es " "recomana mantenir-lo dins dels 8 bits, les pantalles del futur podrien tenir " "una major profunditat de bits, i quan els renderitzadors comencin a " "admetre'ls, podria ser beneficiós desenvolupar un flux de treball on els " "fitxers de l'espai de treball siguin innecessàriament grans i caldrà " "executar alguns scripts per optimitzar-los per a les vostres necessitats de " "renderitzat actuals, fent que en el futur l'actualització del joc per a " "pantalles més sofisticades sigui menys llast." #: ../../general_concepts/colors/color_managed_workflow.rst:368 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." msgstr "" "Els mapes normals i els mapes d'alçades s'hauran de definir oficialment amb " "un espai de treball de «dades sense color», però trobareu que la majoria " "dels motors no tindran cura d'això. En el seu lloc, digueu-li al motor del " "joc que no faci cap conversió en el fitxer quan l'importi." #: ../../general_concepts/colors/color_managed_workflow.rst:370 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)." msgstr "" "Els mapes especulars, brillants, metàl·lics i rugosos es basen en càlculs " "lineals, i descobrireu que algun material té un coeficient metàl·lic de 0,3, " "això serà un 30% de gris en un espai lineal. Per tant, assegureu-vos de dir-" "li al processador del joc que es tracta d'una imatge en espai lineal (o, " "almenys, que NO s'ha de convertir)." # skip-rule: t-acc_obe #: ../../general_concepts/colors/color_managed_workflow.rst:374 msgid "" "`Visualizing the XYZ color space `_." msgstr "" "`Visualitzant l'espai de color XYZ `_." # skip-rule: t-acc_obe #: ../../general_concepts/colors/color_managed_workflow.rst:375 msgid "" "`Basics of gamma correction `_." msgstr "" "`Fonaments en la correcció de la gamma `_." # skip-rule: t-acc_obe,kct-encoding #: ../../general_concepts/colors/color_managed_workflow.rst:376 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 `_." msgstr "" "`Exemple del Panda3D, de com una imatge que té codificada la gamma sense que " "es notifiqui al renderitzador de 3D que la codificació de gamma pot generar " "imatges massa fosques `_." # skip-rule: t-acc_obe #: ../../general_concepts/colors/color_managed_workflow.rst:377 msgid "" "`2D examples of the effect of gamma-encoding on color maths `_." msgstr "" "`Exemples en 2D de l'efecte de codificació de gamma en les matemàtiques del " "color `_." # skip-rule: t-acc_obe #: ../../general_concepts/colors/color_managed_workflow.rst:378 msgid "" "`Basic overview of color management from ArgyllCMS manual `_." msgstr "" "`Resum bàsic de la gestió del color del manual a ArgyllCMS `_." diff --git a/locale/es/LC_MESSAGES/contributors_manual/krita_manual_conventions.po b/locale/es/LC_MESSAGES/contributors_manual/krita_manual_conventions.po index 55d5828ea..c50963a6d 100644 --- a/locale/es/LC_MESSAGES/contributors_manual/krita_manual_conventions.po +++ b/locale/es/LC_MESSAGES/contributors_manual/krita_manual_conventions.po @@ -1,1161 +1,1161 @@ # Spanish translations for docs_krita_org_contributors_manual___krita_manual_conventions.po package. # 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. # # Automatically generated, 2019. # Eloy Cuadra , 2019. # Sofia Priego , %Y. msgid "" msgstr "" "Project-Id-Version: " "docs_krita_org_contributors_manual___krita_manual_conventions\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-09 03:27+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: 2019-02-19 19:50+0100\n" "Last-Translator: Sofia Priego \n" "Language-Team: Spanish \n" "Language: es\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" "X-Generator: Lokalize 18.12.2\n" #: ../../:2 msgid "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: mouseleft" msgstr "" #: ../../:4 msgid "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: mouseright" msgstr "" #: ../../:6 msgid "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: mousemiddle" msgstr "" #: ../../:8 msgid "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" msgstr "" +#: ../../contributors_manual/krita_manual_conventions.rst:None +msgid "Horizontal Rulers" +msgstr "Reglas horizontales" + #: ../../contributors_manual/krita_manual_conventions.rst:0 msgid "" ".. image:: images/sample.png\n" " :alt: an image." msgstr "" -#: ../../contributors_manual/krita_manual_conventions.rst:None -msgid "Horizontal Rulers" -msgstr "Reglas horizontales" - #: ../../contributors_manual/krita_manual_conventions.rst:1 msgid "reStructuredText conventions for the Krita Manual" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:16 msgid "Mark-up conventions for the Krita Manual" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:18 msgid "" "This details the style conventions for using restructured text for the Krita " "Manual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:20 msgid "" "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):" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:23 msgid "" "`Primer `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "User Manual:" msgstr "Manual del usuario:" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "" "`Quick Ref `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:25 msgid "" "`Text Cheatsheet `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:27 msgid "" "`Introduction `_" msgstr "" "`Introducción `_" #: ../../contributors_manual/krita_manual_conventions.rst:28 msgid "" "`Markup `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "Reference Documentation:" msgstr "Documentación de referencia:" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "" "`Directives `_" msgstr "" "`Directivas `_" #: ../../contributors_manual/krita_manual_conventions.rst:30 msgid "`Roles `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "Sphinx specific docs:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "" "`Sphinx' page on restructured text `_ -- This is useful for the specific " "sphinx directives and roles it uses to generate for example table of " "contents." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:34 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:36 msgid "Contents" msgstr "Contenido" #: ../../contributors_manual/krita_manual_conventions.rst:39 msgid "Meta data" msgstr "Metadatos" #: ../../contributors_manual/krita_manual_conventions.rst:41 msgid "Each page should start with the following three things:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:44 msgid "" "This is a general description of the page. It will be converted to an html " "meta tag which will be used by search engines::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:46 msgid "" ".. meta::\n" " :description:\n" " Description." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:49 msgid "A meta description" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:52 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:54 msgid "" ".. metadata-placeholder\n" "\n" " :authors: - Author 1\n" " - Author 2\n" " :license: GNU free documentation license 1.3 or later." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:58 msgid "A list of authors and a license." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:61 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid "Indexing terms." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid ".. index:: Keyword, Keyword with Spaces, ! Main Definition Keyword" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:66 msgid "" "This is so we can easily link to the page using ``:ref:`label_name```. Try " "to make this a nice variable name::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:68 msgid ".. _label_name:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:70 msgid "" "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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:71 msgid "A label." msgstr "Una etiqueta." #: ../../contributors_manual/krita_manual_conventions.rst:74 msgid "Headings" msgstr "Cabeceras" #: ../../contributors_manual/krita_manual_conventions.rst:76 msgid "Headings will be done in the following order::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:78 msgid "" "############\n" "Part/Section\n" "############\n" "\n" "For pages that have a lot of subpages.\n" "\n" "=========\n" "Heading 1\n" "=========\n" "\n" "Start most manual pages with this.\n" "\n" "Heading 2\n" "---------\n" "\n" "Heading 3\n" "~~~~~~~~~\n" "\n" "Heading 4\n" "^^^^^^^^^\n" "\n" "Heading 5\n" "'''''''''\n" "\n" "Heading 6\n" "\"\"\"\"\"\"\"\"\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:105 msgid "" "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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:107 msgid "" "Sometimes you need to link to a subsection of a page, add a label above the " "heading in that case." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:109 msgid "" "Headers should not end with punctuation, as the header will be used as the " "link name when linking to a label." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:112 msgid "Linking" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:114 msgid "" "Linking is done with ``:ref:`label_name```. When you need an alternative " "link text, you use ``:ref:`actual text shown ```." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:116 msgid "" "Linking to external pages is done with ```url`_`` and ```link name " "`_``, which'll become `link name `_." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:118 msgid "" "`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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:121 msgid "Footnotes and further reading" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:123 msgid "" "Footnotes can be made in 3 ways, the most common one is with autonumbering, " "as per reference:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:125 msgid "" "[#]_ is a reference to footnote 1, and [#]_ is a reference to footnote 2." msgstr "" "[#]_ es una referencia a la nota al pie 1, y [#]_ es una referencia a la " "nota al pie 2." #: ../../contributors_manual/krita_manual_conventions.rst:128 msgid "This is footnote 1." msgstr "Esta es la nota al pie 1." #: ../../contributors_manual/krita_manual_conventions.rst:129 msgid "This is footnote 2." msgstr "Esta es la nota al pie 2." #: ../../contributors_manual/krita_manual_conventions.rst:130 msgid "This is footnote 3." msgstr "Esta es la nota al pie 3." #: ../../contributors_manual/krita_manual_conventions.rst:132 msgid "[#]_ is a reference to footnote 3." msgstr "[#]_ es una referencia a la nota al pie 3." #: ../../contributors_manual/krita_manual_conventions.rst:134 msgid "Here is a citation reference: [CIT2002]_ ." msgstr "Esto es una referencia a una cita: [CIT2002]_ ." #: ../../contributors_manual/krita_manual_conventions.rst:136 msgid "" "This is the citation. It's just like a footnote, except the label is " "textual." msgstr "" "Esto es una cita. Es como una nota al pie, excepto que la etiqueta es de " "texto." #: ../../contributors_manual/krita_manual_conventions.rst:139 msgid "Citation can also be referenced with ```citation `_``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:141 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:145 msgid "Images" msgstr "Imágenes" #: ../../contributors_manual/krita_manual_conventions.rst:147 msgid "Use the image directive for images without captions::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:149 msgid "" ".. image:: /images/sample.png\n" " :width: 800\n" " :align: center\n" " :alt: an image." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:154 msgid "And figure directives for images with captions::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:156 msgid "" ".. figure:: /images/sample.png\n" " :figwidth: 800\n" " :align: center\n" " :alt: an image.\n" "\n" " A caption -- notice how the first letter is aligned with the :figwidth: " "option." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:163 msgid "The latter gives:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:170 msgid "" "A caption -- notice how the first letter of the caption in the directive is " "aligned with the :figwidth: option." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:172 msgid "" "Images should go into the ``/images`` folder. By using ``/images`` instead " "of ``images``, sphinx will know the filepath isn't relative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:175 msgid "In-text Markup" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:177 msgid "" "You can make text *emphasized* and **strong** with a single asterisk and " "double respectively::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:179 msgid "" "*emphasize*\n" "**strong**" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:182 msgid "You cannot do both ***emphasized and strong***, so take a pick." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:184 msgid "" "You can :sub:`subscript text` and :sup:`superscript text` by using ``:sub:" "`text``` and ``:sup:`text```" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:186 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:188 msgid "" ":menuselection:`Settings --> Configure Krita`\n" ":guilabel:`File`\n" ":kbd:`Ctrl + Z`\n" ":program:`Krita`" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:193 msgid "" "Avoid randomly bolding words. It does *not* make the text easier or " "friendlier to read." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:196 msgid "Substitution References" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:198 msgid "" "You can create a sort of shorthand for a piece of text or an image by doing::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:200 msgid ".. |shorthand| replace:: something or the other." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:202 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:204 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:206 msgid "" "For links, if you reuse the same link over and over, you can write something " "like the following at the end of the file::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:208 msgid "" ".. _bugzilla: https://bugs.kde.org/\n" ".. _Krita Manual: https://docs.krita.org/" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:211 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:214 msgid "Lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:217 msgid "Ordinated lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:219 msgid "Apple" msgstr "Manzana" #: ../../contributors_manual/krita_manual_conventions.rst:220 msgid "Pear" msgstr "Pera" #: ../../contributors_manual/krita_manual_conventions.rst:221 msgid "Banana" msgstr "Banana" #: ../../contributors_manual/krita_manual_conventions.rst:223 msgid "Or..." msgstr "O..." #: ../../contributors_manual/krita_manual_conventions.rst:225 msgid "Table" msgstr "Mesa" #: ../../contributors_manual/krita_manual_conventions.rst:226 msgid "Chair" msgstr "Silla" #: ../../contributors_manual/krita_manual_conventions.rst:227 msgid "Wardrobe." msgstr "Armario." #: ../../contributors_manual/krita_manual_conventions.rst:229 msgid "Augustus" msgstr "Augusto" #: ../../contributors_manual/krita_manual_conventions.rst:230 msgid "Nero" msgstr "Nerón" #: ../../contributors_manual/krita_manual_conventions.rst:231 msgid "Caligula" msgstr "Calígula" #: ../../contributors_manual/krita_manual_conventions.rst:232 msgid "Trajan" msgstr "Trajano" #: ../../contributors_manual/krita_manual_conventions.rst:234 msgid "They can be defined as follows::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:236 msgid "" "1. Apple\n" "2. Pear\n" "3. Banana\n" "\n" "#. Apple\n" "#. Pear\n" "#. Banana\n" "\n" "A. Table\n" "B. Chair\n" "C. Wardrobe\n" "\n" "A. Table\n" "#. Chair\n" "#. Wardrobe\n" "\n" "I. Augustus\n" "#. Nero\n" "#. Caligula\n" "#. Trajan" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:258 msgid "Unordered lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:260 msgid "red" msgstr "rojo" #: ../../contributors_manual/krita_manual_conventions.rst:261 msgid "yellow" msgstr "amarillo" #: ../../contributors_manual/krita_manual_conventions.rst:263 msgid "seagreen" msgstr "verdemar" #: ../../contributors_manual/krita_manual_conventions.rst:264 msgid "verdigris" msgstr "verdegris" #: ../../contributors_manual/krita_manual_conventions.rst:265 msgid "teal" msgstr "verde azulado" #: ../../contributors_manual/krita_manual_conventions.rst:266 #, fuzzy #| msgid "veridian" msgid "viridian" msgstr "verde esmeralda" #: ../../contributors_manual/krita_manual_conventions.rst:268 msgid "dark emerald" msgstr "esmeralda oscuro" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "green" msgstr "verde" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "emerald" msgstr "esmeralda" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "light emerald" msgstr "esmeralda claro" #: ../../contributors_manual/krita_manual_conventions.rst:270 msgid "very light emerald." msgstr "esmeralda muy claro." #: ../../contributors_manual/krita_manual_conventions.rst:271 msgid "blue" msgstr "azul" #: ../../contributors_manual/krita_manual_conventions.rst:273 msgid "Defined as such::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:275 msgid "" "- red\n" "- yellow\n" "- green\n" " - seagreen\n" " - verdigris\n" " - teal\n" " - viridian\n" " - emerald\n" " - dark emerald\n" " - light emerald\n" " - very light emerald.\n" "- blue" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:289 msgid "Definition Lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:291 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:293 msgid "Definition" msgstr "Definición" #: ../../contributors_manual/krita_manual_conventions.rst:294 #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Explanation." msgstr "Explicación." #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Another option" msgstr "Otra opción" #: ../../contributors_manual/krita_manual_conventions.rst:299 msgid "You can make them like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:301 msgid "" "Definition\n" " Explanation.\n" "Another option\n" " Explanation." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:304 msgid "To make them." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:307 msgid "Tables" msgstr "Tablas" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Purpose" msgstr "Propósito" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Table type" msgstr "Tipo de tabla" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "listing shortcuts" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "Simple table" msgstr "Tabla simple" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "lots of colspans" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "Grid table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "Simple but long" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "List Table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:317 msgid "Done as follows::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:319 msgid "" "================== ============\n" "Purpose Table type\n" "================== ============\n" "listing shortcuts Simple table\n" "lots of colspans Grid table\n" "Simple but long List Table\n" "================== ============\n" "\n" "+-----------------+------------+\n" "|Purpose |Table Type |\n" "+=================+============+\n" "|listing shortcuts|Simple table|\n" "+-----------------+------------+\n" "|lots of colspans |Grid table |\n" "+-----------------+------------+\n" "|Simple but long |List table |\n" "+-----------------+------------+\n" "\n" ".. list-table::\n" " :header-rows: 1\n" "\n" " - * Purpose\n" " * Table Type\n" " - * listing shortcuts\n" " * simple table\n" " - * lots of colspans\n" " * grid table\n" " - * simple but long\n" " * list table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:349 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:352 #, fuzzy #| msgid "Admonishments and asides." msgid "Admonishments and asides" msgstr "Amonestaciones y comentarios al margen." #: ../../contributors_manual/krita_manual_conventions.rst:356 msgid "" "Admonishments are sort of like a separate section that the reader needs to " "pay attention to." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:358 msgid "" "Admonishments that can be used are the following (in order of seriousness):" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:362 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:366 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:370 msgid "Something that is important to note, but is not necessarily negative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:374 msgid "This is in general when something is negative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:378 msgid "" "General attention grabber. Use this when the subject is more important than " "warning, but not as important that is could get a dataloss." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:382 msgid "" "This is for things that could cause dataloss, like forgetting to save, or " "that Python currently has no undo functionality." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:386 msgid "" "This should be for things that are dangerous for the computer in general, " "this includes things that can cause out of memory style freezes." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:390 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:392 msgid "Generic admonition that can have any text" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:394 msgid "Text." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:396 msgid "You can make it like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:398 msgid "" ".. admonition:: Generic admonition that can have any text\n" "\n" " Text." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:404 msgid "Sphinx also adds::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:406 msgid "" ".. seealso::\n" "\n" " Which is useful to collect external links and references." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:414 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:418 msgid "That said, horizontal rulers can be made with ``----``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:421 msgid "The rubric directive" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:422 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:424 msgid ".. rubric:: The rubric directive" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:428 msgid "So, when to use these?" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:429 msgid "" "Only use them when you think the subject is too minor to have a proper " "heading." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:431 msgid "Topic" msgstr "Tema" #: ../../contributors_manual/krita_manual_conventions.rst:432 msgid "" "When the text is separated from the flow, so it goes into a different " "subject than the text itself is naturally going to." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:433 msgid "Rubric" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:434 msgid "" "When the text isn't separated from the flow, but it does not need a header " "either." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:436 msgid "Admonishments" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:436 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:439 #, fuzzy #| msgid "Code Snippets:" msgid "Code Snippets" msgstr "Fragmentos de código:" #: ../../contributors_manual/krita_manual_conventions.rst:441 msgid "``Inline code snippets`` are done with ````backticks````." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:443 msgid "" "Multi-line code snippets are done by ending the previous section with ``::" "``, which'll look like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:445 msgid "" "This is a paragraph, and we define a preformated snippet like so::\n" "\n" " Be sure to add a white space and a tab afterwards before starting the " "snippet." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:449 msgid "" "You can also use the ``.. code::`` directive. If you add the language name " "after it, it'll do the appropriate syntax highlighting::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:451 msgid "" ".. code:: python\n" "\n" " # Python comment\n" " def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:459 msgid "Becomes" msgstr "Se convierte en" #: ../../contributors_manual/krita_manual_conventions.rst:468 msgid "" "# Python comment\n" "def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:469 msgid "some more..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:483 msgid "" "// C++ comment\n" "int myFunction(int i) {\n" " i += 1;\n" "\n" " // Check if more than 12\n" " if (i>12) {\n" " i = 0;\n" " }\n" " return i;\n" "}" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:498 msgid "" "/* CSS comment */\n" "body {\n" " margin: 0 auto;\n" " /* is 800 still sensible? */\n" " max-width:800px;\n" " font-size:16px;\n" " color:#333;\n" " background-color: #eee;\n" " padding:1em;\n" " font-family:serif;\n" " line-height: 1.4;\n" "}" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:502 msgid "" "

this is " "a paragraph.

" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:504 #, fuzzy #| msgid "Other preformatted text." msgid "Other preformatted text" msgstr "Otro texto preformateado." #: ../../contributors_manual/krita_manual_conventions.rst:507 msgid "One can" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:508 msgid "preformat" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:509 msgid "text by" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:510 msgid "prepending" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:511 msgid "each line" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:512 msgid "with a pipe" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:513 msgid "symbol" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:515 msgid "Like so::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:517 msgid "" "| One can\n" "| preformat\n" "| text by\n" "| prepending\n" "| each line\n" "| with a pipe\n" "| symbol" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:525 msgid "We don't actually use this anywhere in the manual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:528 msgid "Glossaries, Terms and Index" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:530 msgid "These are sphinx features." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:532 msgid "" "Index is used in the top section, right now only single index entries are " "used." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:534 msgid "" "Glossaries are used for some of the menu entry sections, but not all of them." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:537 msgid "Quotes" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:539 msgid "Quotes are done like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:541 msgid "" "I am not sure why you'd need quotes in a user manual...\n" "\n" "-- Wolthera" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:545 msgid "This becomes a blockquote." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:547 msgid "I am not sure why you'd need quotes in a user manual..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:551 msgid "" "We do actually use quotes in some places. Try to add a link to the name to " "define where it came from." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:552 msgid "Wolthera" msgstr "Wolthera" #~ msgid "explanation." #~ msgstr "explicación." diff --git a/locale/es/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po b/locale/es/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po index 0d1f3526a..c3acd0fba 100644 --- a/locale/es/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po +++ b/locale/es/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po @@ -1,1079 +1,1079 @@ # Spanish translations for docs_krita_org_general_concepts___colors___color_managed_workflow.po package. # 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. # # Automatically generated, 2019. # Eloy Cuadra , 2019. # Sofia Priego , %Y. msgid "" msgstr "" "Project-Id-Version: " "docs_krita_org_general_concepts___colors___color_managed_workflow\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-08 03:08+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: 2019-02-19 19:58+0100\n" "Last-Translator: Sofia Priego \n" "Language-Team: Spanish \n" "Language: es\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" "X-Generator: Lokalize 18.12.2\n" +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_matrix_profile.png" +msgstr "" + +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" +msgstr "" + #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group1.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group2.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group3.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group4.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/dockers/LUT_Management_Docker.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR_1.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR2.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_webcomic.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_print.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_games.svg" msgstr "" -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_matrix_profile.png" -msgstr "" - -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" -msgstr "" - #: ../../general_concepts/colors/color_managed_workflow.rst:1 msgid "How a color managed workflow works." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "Color" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 #, fuzzy #| msgid "What is colour management?" msgid "Color Management" msgstr "¿Qué es la gestión de colores?" #: ../../general_concepts/colors/color_managed_workflow.rst:12 #, fuzzy #| msgid "Icc profiles" msgid "ICC Profiles" msgstr "Perfiles Icc" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "OCIO" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:17 msgid "Color Managed Workflow" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:19 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:22 msgid "Basic Info" msgstr "Información básica" #: ../../general_concepts/colors/color_managed_workflow.rst:24 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:26 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:29 msgid "What is the problem?" msgstr "¿Cuál es el problema?" #: ../../general_concepts/colors/color_managed_workflow.rst:31 msgid "" "To explain the point of color management, you'd first need to learn which " "problem color management tries to solve." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:33 msgid "Let us imagine a kinder garden:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:35 msgid "" "The class of 28 children is subdivided in groups of 7. Each group has its " "own table." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:37 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:40 msgid "The following results come from painting:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:42 msgid "" "Even though all groups had the same assignment, each group's result looks " "different." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:49 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:56 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:64 msgid "" "Group 3 had vermillion red, citron yellow, emerald green and cerulean blue. " "They didn't mix their green, and thus ended up with a purer color." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:71 msgid "" "Finally, group 4 has vermillion red, citron yellow and cerulean blue. Their " "colors probably look like what you imagined." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:73 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!" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:75 msgid "For this purpose, we invented color management." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:78 #, fuzzy #| msgid "What is colour management?" msgid "What is color management?" msgstr "¿Qué es la gestión de colores?" #: ../../general_concepts/colors/color_managed_workflow.rst:80 msgid "" "Color management is, dryly put, a set of systems that tries to have the same " "color translate properly between color devices." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:82 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:84 msgid "" "From XYZ it can then be translated back into another device space, such as " "RGB (for screens), or CMYK (for printers)." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:86 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:88 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:90 msgid "Within both we can identify the following color spaces:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:93 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 " "`." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:94 msgid "Device spaces" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:96 msgid "Working spaces" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:97 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:99 msgid "Aesthetic or Look spaces" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:99 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:102 msgid "Color managed workflow" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:104 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:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:110 msgid ".. image:: images/color_category/Krita-colormanaged-workflow_text.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:110 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:112 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:114 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:116 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:118 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:120 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:122 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:124 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:127 msgid "So what does this mean?" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:133 msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_krita_text.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:133 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:135 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*." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:137 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:139 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:141 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:143 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.)" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:148 #, fuzzy #| msgid "Icc profiles" msgid "ICC profiles" msgstr "Perfiles Icc" #: ../../general_concepts/colors/color_managed_workflow.rst:150 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:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:153 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:159 msgid "Matrix Shaper profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:159 msgid "" "Matrix shaper profiles have a few parameters that describe the color space " "which are then interpolated between, this requires a lot of maths." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:162 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:168 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:169 msgid "cLUT profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:171 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:174 msgid "Perceptual" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:174 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:177 msgid "Absolute Colorimetric" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:177 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:180 msgid "Relative Colorimetric" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:180 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:183 msgid "Saturation" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:183 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:185 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:188 msgid "LUT docker and HDR imaging" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:196 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:198 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:200 msgid "" "Component, exposure, gamma, whitepoint and blackpoint are knobs which allows " "you to modify the display filter." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:208 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:210 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:212 msgid "" "Black similarly, is brighter on a LCD display than a LED one, and " "incomparable with the black of a carefully sealed room." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:214 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:216 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:224 msgid "" "So, for example, we can choose to scale whiter-than-screen-white to our " "screen-white so we can see the contrasts there." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:226 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:228 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:230 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:232 msgid "" "Another example is to carefully watch the gradients in a certain section." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:234 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:237 msgid "In summary" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:239 #, fuzzy #| msgid "What is colour management?" msgid "Krita has two modes of color management:" msgstr "¿Qué es la gestión de colores?" #: ../../general_concepts/colors/color_managed_workflow.rst:241 msgid "" "ICC works in terms of spaces relative to the CIEXYZ space, and requires an " "ICC profile." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:242 msgid "OCIO works in terms of interpretation, and makes use of LUTs." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:243 msgid "both can be made with a colorimeter." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:244 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:245 msgid "" "Set up your screen profiles under :menuselection:`Settings --> Configure " "Krita --> Color management`." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:246 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:247 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:249 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:251 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!" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:256 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!" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:260 msgid "" "No amount of color management in the world can make the image on your screen " "and the image out of the printer have 100% the same color." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:263 msgid "Exporting" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:265 msgid "" "When you have finished your image and are ready to export it, you can modify " "the color space to optimize it:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:267 msgid "If you are preparing an image for the web:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:269 msgid "" "If you use 16bit color depth or higher, convert the image to 8bit color " "depth. This will make the image much smaller." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:271 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:273 msgid "If it's a gray-scale image, convert it to gray-scale." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:274 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:279 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 " "`_, save your PNG, JPG or TIFF without an embedded profile to work " "around this." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:281 msgid "If you are preparing for print:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:283 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:284 msgid "" "Check with the printer what kind of image they expect. Maybe they expect " "sRGB color space, or perhaps they have their own profile." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:287 msgid "Interaction with other applications" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:290 msgid "Blender" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:292 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:294 msgid "" "Blender's OCIO config is under ``/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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:298 msgid "Windows Photo Viewer" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:300 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:303 msgid "Example workflows" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:305 msgid "" "Here are some example workflows to get a feeling of how your color " "management workflow may look like." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:307 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'." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:310 msgid "Webcomic" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:317 #: ../../general_concepts/colors/color_managed_workflow.rst:339 #: ../../general_concepts/colors/color_managed_workflow.rst:357 msgid "Input" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:318 #: ../../general_concepts/colors/color_managed_workflow.rst:340 #: ../../general_concepts/colors/color_managed_workflow.rst:358 msgid "Your screen profile. (You pick colors via your screen)" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:319 #: ../../general_concepts/colors/color_managed_workflow.rst:341 #: ../../general_concepts/colors/color_managed_workflow.rst:359 msgid "Workingspace" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:320 msgid "" "sRGB (the default screen profile) or any larger profile if you can spare the " "bit depth and like working in them." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:322 #: ../../general_concepts/colors/color_managed_workflow.rst:344 #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "Output" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:322 msgid "" "sRGB, ICC version 2, sRGB TRC for the internet, and a specialized CMYK " "profile from the printing house for the printed images." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:324 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:326 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:328 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:330 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:333 msgid "Print" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:342 msgid "sRGB or Rec. 2020 if you can afford the bit-depth being 16bit." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:344 msgid "" "Specialized CMYK profile from the printing house for the printed images." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:346 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:348 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:351 msgid "Games" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:360 msgid "sRGB or grayscale linear for roughness and specular maps." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "" "This one is tricky, but in the end it'll be sRGB for the regular player." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:364 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:366 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:368 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:370 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)." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:374 msgid "" "`Visualizing the XYZ color space `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:375 msgid "" "`Basics of gamma correction `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:376 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 `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:377 msgid "" "`2D examples of the effect of gamma-encoding on color maths `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:378 msgid "" "`Basic overview of color management from ArgyllCMS manual `_." msgstr "" diff --git a/locale/fr/LC_MESSAGES/contributors_manual/krita_manual_conventions.po b/locale/fr/LC_MESSAGES/contributors_manual/krita_manual_conventions.po index ef48f72b9..68ff805d7 100644 --- a/locale/fr/LC_MESSAGES/contributors_manual/krita_manual_conventions.po +++ b/locale/fr/LC_MESSAGES/contributors_manual/krita_manual_conventions.po @@ -1,1142 +1,1142 @@ msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-09 03:27+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: 2019-02-27 00:46+0100\n" "Last-Translator: KDE Francophone \n" "Language-Team: KDE Francophone \n" "Language: fr\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=(n > 1);\n" "X-Generator: Lokalize 1.5\n" "X-Accelerator-Marker: &\n" "X-Text-Markup: kde4\n" "X-Environment: kde\n" "X-Language: fr_FR\n" "X-Qt-Contexts: true\n" "Generated-By: Babel 0.9.6\n" "X-Source-Language: C\n" #: ../../:2 msgid "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: mouseleft" msgstr "" #: ../../:4 msgid "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: mouseright" msgstr "" #: ../../:6 msgid "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: mousemiddle" msgstr "" #: ../../:8 msgid "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" msgstr "" +#: ../../contributors_manual/krita_manual_conventions.rst:None +msgid "Horizontal Rulers" +msgstr "" + #: ../../contributors_manual/krita_manual_conventions.rst:0 msgid "" ".. image:: images/sample.png\n" " :alt: an image." msgstr "" -#: ../../contributors_manual/krita_manual_conventions.rst:None -msgid "Horizontal Rulers" -msgstr "" - #: ../../contributors_manual/krita_manual_conventions.rst:1 msgid "reStructuredText conventions for the Krita Manual" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:16 msgid "Mark-up conventions for the Krita Manual" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:18 msgid "" "This details the style conventions for using restructured text for the Krita " "Manual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:20 msgid "" "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):" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:23 msgid "" "`Primer `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "User Manual:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "" "`Quick Ref `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:25 msgid "" "`Text Cheatsheet `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:27 msgid "" "`Introduction `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:28 msgid "" "`Markup `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "Reference Documentation:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "" "`Directives `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:30 msgid "`Roles `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "Sphinx specific docs:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "" "`Sphinx' page on restructured text `_ -- This is useful for the specific " "sphinx directives and roles it uses to generate for example table of " "contents." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:34 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:36 msgid "Contents" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:39 msgid "Meta data" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:41 msgid "Each page should start with the following three things:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:44 msgid "" "This is a general description of the page. It will be converted to an html " "meta tag which will be used by search engines::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:46 msgid "" ".. meta::\n" " :description:\n" " Description." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:49 msgid "A meta description" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:52 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:54 msgid "" ".. metadata-placeholder\n" "\n" " :authors: - Author 1\n" " - Author 2\n" " :license: GNU free documentation license 1.3 or later." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:58 msgid "A list of authors and a license." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:61 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid "Indexing terms." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid ".. index:: Keyword, Keyword with Spaces, ! Main Definition Keyword" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:66 msgid "" "This is so we can easily link to the page using ``:ref:`label_name```. Try " "to make this a nice variable name::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:68 msgid ".. _label_name:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:70 msgid "" "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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:71 msgid "A label." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:74 msgid "Headings" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:76 msgid "Headings will be done in the following order::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:78 msgid "" "############\n" "Part/Section\n" "############\n" "\n" "For pages that have a lot of subpages.\n" "\n" "=========\n" "Heading 1\n" "=========\n" "\n" "Start most manual pages with this.\n" "\n" "Heading 2\n" "---------\n" "\n" "Heading 3\n" "~~~~~~~~~\n" "\n" "Heading 4\n" "^^^^^^^^^\n" "\n" "Heading 5\n" "'''''''''\n" "\n" "Heading 6\n" "\"\"\"\"\"\"\"\"\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:105 msgid "" "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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:107 msgid "" "Sometimes you need to link to a subsection of a page, add a label above the " "heading in that case." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:109 msgid "" "Headers should not end with punctuation, as the header will be used as the " "link name when linking to a label." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:112 msgid "Linking" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:114 msgid "" "Linking is done with ``:ref:`label_name```. When you need an alternative " "link text, you use ``:ref:`actual text shown ```." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:116 msgid "" "Linking to external pages is done with ```url`_`` and ```link name " "`_``, which'll become `link name `_." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:118 msgid "" "`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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:121 msgid "Footnotes and further reading" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:123 msgid "" "Footnotes can be made in 3 ways, the most common one is with autonumbering, " "as per reference:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:125 msgid "" "[#]_ is a reference to footnote 1, and [#]_ is a reference to footnote 2." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:128 msgid "This is footnote 1." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:129 msgid "This is footnote 2." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:130 msgid "This is footnote 3." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:132 msgid "[#]_ is a reference to footnote 3." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:134 msgid "Here is a citation reference: [CIT2002]_ ." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:136 msgid "" "This is the citation. It's just like a footnote, except the label is " "textual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:139 msgid "Citation can also be referenced with ```citation `_``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:141 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:145 msgid "Images" msgstr "Images" #: ../../contributors_manual/krita_manual_conventions.rst:147 msgid "Use the image directive for images without captions::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:149 msgid "" ".. image:: /images/sample.png\n" " :width: 800\n" " :align: center\n" " :alt: an image." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:154 msgid "And figure directives for images with captions::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:156 msgid "" ".. figure:: /images/sample.png\n" " :figwidth: 800\n" " :align: center\n" " :alt: an image.\n" "\n" " A caption -- notice how the first letter is aligned with the :figwidth: " "option." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:163 msgid "The latter gives:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:170 msgid "" "A caption -- notice how the first letter of the caption in the directive is " "aligned with the :figwidth: option." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:172 msgid "" "Images should go into the ``/images`` folder. By using ``/images`` instead " "of ``images``, sphinx will know the filepath isn't relative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:175 msgid "In-text Markup" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:177 msgid "" "You can make text *emphasized* and **strong** with a single asterisk and " "double respectively::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:179 msgid "" "*emphasize*\n" "**strong**" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:182 msgid "You cannot do both ***emphasized and strong***, so take a pick." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:184 msgid "" "You can :sub:`subscript text` and :sup:`superscript text` by using ``:sub:" "`text``` and ``:sup:`text```" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:186 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:188 msgid "" ":menuselection:`Settings --> Configure Krita`\n" ":guilabel:`File`\n" ":kbd:`Ctrl + Z`\n" ":program:`Krita`" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:193 msgid "" "Avoid randomly bolding words. It does *not* make the text easier or " "friendlier to read." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:196 msgid "Substitution References" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:198 msgid "" "You can create a sort of shorthand for a piece of text or an image by doing::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:200 msgid ".. |shorthand| replace:: something or the other." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:202 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:204 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:206 msgid "" "For links, if you reuse the same link over and over, you can write something " "like the following at the end of the file::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:208 msgid "" ".. _bugzilla: https://bugs.kde.org/\n" ".. _Krita Manual: https://docs.krita.org/" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:211 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:214 msgid "Lists" msgstr "Listes" #: ../../contributors_manual/krita_manual_conventions.rst:217 msgid "Ordinated lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:219 msgid "Apple" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:220 msgid "Pear" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:221 msgid "Banana" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:223 msgid "Or..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:225 msgid "Table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:226 msgid "Chair" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:227 msgid "Wardrobe." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:229 msgid "Augustus" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:230 msgid "Nero" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:231 msgid "Caligula" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:232 msgid "Trajan" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:234 msgid "They can be defined as follows::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:236 msgid "" "1. Apple\n" "2. Pear\n" "3. Banana\n" "\n" "#. Apple\n" "#. Pear\n" "#. Banana\n" "\n" "A. Table\n" "B. Chair\n" "C. Wardrobe\n" "\n" "A. Table\n" "#. Chair\n" "#. Wardrobe\n" "\n" "I. Augustus\n" "#. Nero\n" "#. Caligula\n" "#. Trajan" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:258 msgid "Unordered lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:260 msgid "red" msgstr "rouge" #: ../../contributors_manual/krita_manual_conventions.rst:261 msgid "yellow" msgstr "jaune" #: ../../contributors_manual/krita_manual_conventions.rst:263 msgid "seagreen" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:264 msgid "verdigris" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:265 msgid "teal" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:266 msgid "viridian" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:268 msgid "dark emerald" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "green" msgstr "vert" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "emerald" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "light emerald" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:270 msgid "very light emerald." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:271 msgid "blue" msgstr "bleu" #: ../../contributors_manual/krita_manual_conventions.rst:273 msgid "Defined as such::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:275 msgid "" "- red\n" "- yellow\n" "- green\n" " - seagreen\n" " - verdigris\n" " - teal\n" " - viridian\n" " - emerald\n" " - dark emerald\n" " - light emerald\n" " - very light emerald.\n" "- blue" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:289 msgid "Definition Lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:291 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:293 msgid "Definition" msgstr "Définition" #: ../../contributors_manual/krita_manual_conventions.rst:294 #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Explanation." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Another option" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:299 msgid "You can make them like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:301 msgid "" "Definition\n" " Explanation.\n" "Another option\n" " Explanation." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:304 msgid "To make them." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:307 msgid "Tables" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Purpose" msgstr "Motif" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Table type" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "listing shortcuts" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "Simple table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "lots of colspans" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "Grid table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "Simple but long" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "List Table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:317 msgid "Done as follows::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:319 msgid "" "================== ============\n" "Purpose Table type\n" "================== ============\n" "listing shortcuts Simple table\n" "lots of colspans Grid table\n" "Simple but long List Table\n" "================== ============\n" "\n" "+-----------------+------------+\n" "|Purpose |Table Type |\n" "+=================+============+\n" "|listing shortcuts|Simple table|\n" "+-----------------+------------+\n" "|lots of colspans |Grid table |\n" "+-----------------+------------+\n" "|Simple but long |List table |\n" "+-----------------+------------+\n" "\n" ".. list-table::\n" " :header-rows: 1\n" "\n" " - * Purpose\n" " * Table Type\n" " - * listing shortcuts\n" " * simple table\n" " - * lots of colspans\n" " * grid table\n" " - * simple but long\n" " * list table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:349 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:352 msgid "Admonishments and asides" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:356 msgid "" "Admonishments are sort of like a separate section that the reader needs to " "pay attention to." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:358 msgid "" "Admonishments that can be used are the following (in order of seriousness):" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:362 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:366 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:370 msgid "Something that is important to note, but is not necessarily negative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:374 msgid "This is in general when something is negative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:378 msgid "" "General attention grabber. Use this when the subject is more important than " "warning, but not as important that is could get a dataloss." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:382 msgid "" "This is for things that could cause dataloss, like forgetting to save, or " "that Python currently has no undo functionality." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:386 msgid "" "This should be for things that are dangerous for the computer in general, " "this includes things that can cause out of memory style freezes." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:390 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:392 msgid "Generic admonition that can have any text" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:394 msgid "Text." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:396 msgid "You can make it like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:398 msgid "" ".. admonition:: Generic admonition that can have any text\n" "\n" " Text." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:404 msgid "Sphinx also adds::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:406 msgid "" ".. seealso::\n" "\n" " Which is useful to collect external links and references." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:414 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:418 msgid "That said, horizontal rulers can be made with ``----``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:421 msgid "The rubric directive" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:422 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:424 msgid ".. rubric:: The rubric directive" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:428 msgid "So, when to use these?" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:429 msgid "" "Only use them when you think the subject is too minor to have a proper " "heading." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:431 msgid "Topic" msgstr "Sujet" #: ../../contributors_manual/krita_manual_conventions.rst:432 msgid "" "When the text is separated from the flow, so it goes into a different " "subject than the text itself is naturally going to." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:433 msgid "Rubric" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:434 msgid "" "When the text isn't separated from the flow, but it does not need a header " "either." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:436 msgid "Admonishments" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:436 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:439 msgid "Code Snippets" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:441 msgid "``Inline code snippets`` are done with ````backticks````." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:443 msgid "" "Multi-line code snippets are done by ending the previous section with ``::" "``, which'll look like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:445 msgid "" "This is a paragraph, and we define a preformated snippet like so::\n" "\n" " Be sure to add a white space and a tab afterwards before starting the " "snippet." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:449 msgid "" "You can also use the ``.. code::`` directive. If you add the language name " "after it, it'll do the appropriate syntax highlighting::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:451 msgid "" ".. code:: python\n" "\n" " # Python comment\n" " def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:459 msgid "Becomes" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:468 msgid "" "# Python comment\n" "def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:469 msgid "some more..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:483 msgid "" "// C++ comment\n" "int myFunction(int i) {\n" " i += 1;\n" "\n" " // Check if more than 12\n" " if (i>12) {\n" " i = 0;\n" " }\n" " return i;\n" "}" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:498 msgid "" "/* CSS comment */\n" "body {\n" " margin: 0 auto;\n" " /* is 800 still sensible? */\n" " max-width:800px;\n" " font-size:16px;\n" " color:#333;\n" " background-color: #eee;\n" " padding:1em;\n" " font-family:serif;\n" " line-height: 1.4;\n" "}" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:502 msgid "" "

this is " "a paragraph.

" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:504 msgid "Other preformatted text" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:507 msgid "One can" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:508 msgid "preformat" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:509 msgid "text by" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:510 msgid "prepending" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:511 msgid "each line" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:512 msgid "with a pipe" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:513 msgid "symbol" msgstr "symbole" #: ../../contributors_manual/krita_manual_conventions.rst:515 msgid "Like so::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:517 msgid "" "| One can\n" "| preformat\n" "| text by\n" "| prepending\n" "| each line\n" "| with a pipe\n" "| symbol" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:525 msgid "We don't actually use this anywhere in the manual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:528 msgid "Glossaries, Terms and Index" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:530 msgid "These are sphinx features." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:532 msgid "" "Index is used in the top section, right now only single index entries are " "used." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:534 msgid "" "Glossaries are used for some of the menu entry sections, but not all of them." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:537 msgid "Quotes" msgstr "Guillemets" #: ../../contributors_manual/krita_manual_conventions.rst:539 msgid "Quotes are done like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:541 msgid "" "I am not sure why you'd need quotes in a user manual...\n" "\n" "-- Wolthera" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:545 msgid "This becomes a blockquote." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:547 msgid "I am not sure why you'd need quotes in a user manual..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:551 msgid "" "We do actually use quotes in some places. Try to add a link to the name to " "define where it came from." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:552 msgid "Wolthera" msgstr "" diff --git a/locale/fr/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po b/locale/fr/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po index 0d4158902..d7493d726 100644 --- a/locale/fr/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po +++ b/locale/fr/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po @@ -1,1070 +1,1070 @@ msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-08 03:08+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: 2019-02-27 00:50+0100\n" "Last-Translator: KDE Francophone \n" "Language-Team: KDE Francophone \n" "Language: fr\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=(n > 1);\n" "X-Generator: Lokalize 1.5\n" "X-Accelerator-Marker: &\n" "X-Text-Markup: kde4\n" "X-Environment: kde\n" "X-Language: fr_FR\n" "X-Qt-Contexts: true\n" "Generated-By: Babel 0.9.6\n" "X-Source-Language: C\n" +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_matrix_profile.png" +msgstr "" + +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" +msgstr "" + #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group1.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group2.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group3.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group4.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/dockers/LUT_Management_Docker.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR_1.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR2.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_webcomic.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_print.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_games.svg" msgstr "" -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_matrix_profile.png" -msgstr "" - -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" -msgstr "" - #: ../../general_concepts/colors/color_managed_workflow.rst:1 msgid "How a color managed workflow works." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "Color" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "Color Management" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "ICC Profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "OCIO" msgstr "OCIO" #: ../../general_concepts/colors/color_managed_workflow.rst:17 msgid "Color Managed Workflow" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:19 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:22 msgid "Basic Info" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:24 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:26 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:29 msgid "What is the problem?" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:31 msgid "" "To explain the point of color management, you'd first need to learn which " "problem color management tries to solve." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:33 msgid "Let us imagine a kinder garden:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:35 msgid "" "The class of 28 children is subdivided in groups of 7. Each group has its " "own table." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:37 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:40 msgid "The following results come from painting:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:42 msgid "" "Even though all groups had the same assignment, each group's result looks " "different." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:49 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:56 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:64 msgid "" "Group 3 had vermillion red, citron yellow, emerald green and cerulean blue. " "They didn't mix their green, and thus ended up with a purer color." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:71 msgid "" "Finally, group 4 has vermillion red, citron yellow and cerulean blue. Their " "colors probably look like what you imagined." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:73 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!" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:75 msgid "For this purpose, we invented color management." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:78 msgid "What is color management?" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:80 msgid "" "Color management is, dryly put, a set of systems that tries to have the same " "color translate properly between color devices." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:82 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:84 msgid "" "From XYZ it can then be translated back into another device space, such as " "RGB (for screens), or CMYK (for printers)." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:86 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:88 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:90 msgid "Within both we can identify the following color spaces:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:93 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 " "`." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:94 msgid "Device spaces" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:96 msgid "Working spaces" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:97 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:99 msgid "Aesthetic or Look spaces" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:99 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:102 msgid "Color managed workflow" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:104 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:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:110 msgid ".. image:: images/color_category/Krita-colormanaged-workflow_text.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:110 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:112 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:114 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:116 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:118 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:120 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:122 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:124 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:127 msgid "So what does this mean?" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:133 msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_krita_text.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:133 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:135 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*." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:137 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:139 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:141 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:143 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.)" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:148 msgid "ICC profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:150 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:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:153 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:159 msgid "Matrix Shaper profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:159 msgid "" "Matrix shaper profiles have a few parameters that describe the color space " "which are then interpolated between, this requires a lot of maths." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:162 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:168 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:169 msgid "cLUT profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:171 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:174 msgid "Perceptual" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:174 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:177 #, fuzzy #| msgid "Relative Colorimetric" msgid "Absolute Colorimetric" msgstr "Colorimétrie relative" #: ../../general_concepts/colors/color_managed_workflow.rst:177 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:180 msgid "Relative Colorimetric" msgstr "Colorimétrie relative" #: ../../general_concepts/colors/color_managed_workflow.rst:180 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:183 msgid "Saturation" msgstr "Saturation" #: ../../general_concepts/colors/color_managed_workflow.rst:183 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:185 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:188 msgid "LUT docker and HDR imaging" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:196 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:198 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:200 msgid "" "Component, exposure, gamma, whitepoint and blackpoint are knobs which allows " "you to modify the display filter." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:208 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:210 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:212 msgid "" "Black similarly, is brighter on a LCD display than a LED one, and " "incomparable with the black of a carefully sealed room." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:214 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:216 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:224 msgid "" "So, for example, we can choose to scale whiter-than-screen-white to our " "screen-white so we can see the contrasts there." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:226 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:228 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:230 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:232 msgid "" "Another example is to carefully watch the gradients in a certain section." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:234 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:237 msgid "In summary" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:239 msgid "Krita has two modes of color management:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:241 msgid "" "ICC works in terms of spaces relative to the CIEXYZ space, and requires an " "ICC profile." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:242 msgid "OCIO works in terms of interpretation, and makes use of LUTs." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:243 msgid "both can be made with a colorimeter." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:244 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:245 msgid "" "Set up your screen profiles under :menuselection:`Settings --> Configure " "Krita --> Color management`." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:246 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:247 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:249 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:251 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!" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:256 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!" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:260 msgid "" "No amount of color management in the world can make the image on your screen " "and the image out of the printer have 100% the same color." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:263 msgid "Exporting" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:265 msgid "" "When you have finished your image and are ready to export it, you can modify " "the color space to optimize it:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:267 msgid "If you are preparing an image for the web:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:269 msgid "" "If you use 16bit color depth or higher, convert the image to 8bit color " "depth. This will make the image much smaller." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:271 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:273 msgid "If it's a gray-scale image, convert it to gray-scale." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:274 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:279 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 " "`_, save your PNG, JPG or TIFF without an embedded profile to work " "around this." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:281 msgid "If you are preparing for print:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:283 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:284 msgid "" "Check with the printer what kind of image they expect. Maybe they expect " "sRGB color space, or perhaps they have their own profile." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:287 msgid "Interaction with other applications" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:290 msgid "Blender" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:292 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:294 msgid "" "Blender's OCIO config is under ``/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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:298 msgid "Windows Photo Viewer" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:300 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:303 msgid "Example workflows" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:305 msgid "" "Here are some example workflows to get a feeling of how your color " "management workflow may look like." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:307 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'." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:310 msgid "Webcomic" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:317 #: ../../general_concepts/colors/color_managed_workflow.rst:339 #: ../../general_concepts/colors/color_managed_workflow.rst:357 msgid "Input" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:318 #: ../../general_concepts/colors/color_managed_workflow.rst:340 #: ../../general_concepts/colors/color_managed_workflow.rst:358 msgid "Your screen profile. (You pick colors via your screen)" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:319 #: ../../general_concepts/colors/color_managed_workflow.rst:341 #: ../../general_concepts/colors/color_managed_workflow.rst:359 msgid "Workingspace" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:320 msgid "" "sRGB (the default screen profile) or any larger profile if you can spare the " "bit depth and like working in them." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:322 #: ../../general_concepts/colors/color_managed_workflow.rst:344 #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "Output" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:322 msgid "" "sRGB, ICC version 2, sRGB TRC for the internet, and a specialized CMYK " "profile from the printing house for the printed images." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:324 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:326 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:328 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:330 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:333 msgid "Print" msgstr "Imprimer" #: ../../general_concepts/colors/color_managed_workflow.rst:342 msgid "sRGB or Rec. 2020 if you can afford the bit-depth being 16bit." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:344 msgid "" "Specialized CMYK profile from the printing house for the printed images." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:346 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:348 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:351 msgid "Games" msgstr "Jeux" #: ../../general_concepts/colors/color_managed_workflow.rst:360 msgid "sRGB or grayscale linear for roughness and specular maps." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "" "This one is tricky, but in the end it'll be sRGB for the regular player." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:364 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:366 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:368 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:370 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)." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:374 msgid "" "`Visualizing the XYZ color space `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:375 msgid "" "`Basics of gamma correction `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:376 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 `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:377 msgid "" "`2D examples of the effect of gamma-encoding on color maths `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:378 msgid "" "`Basic overview of color management from ArgyllCMS manual `_." msgstr "" diff --git a/locale/it/LC_MESSAGES/contributors_manual/krita_manual_conventions.po b/locale/it/LC_MESSAGES/contributors_manual/krita_manual_conventions.po index 0bee75547..12bf53eba 100644 --- a/locale/it/LC_MESSAGES/contributors_manual/krita_manual_conventions.po +++ b/locale/it/LC_MESSAGES/contributors_manual/krita_manual_conventions.po @@ -1,1612 +1,1612 @@ # 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. # Valter Mura , 2019. # msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-09 03:27+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: 2019-06-09 23:23+0200\n" "Last-Translator: Valter Mura \n" "Language-Team: Italian \n" "Language: it\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" "X-Generator: Lokalize 19.04.2\n" #: ../../:2 msgid "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: mouseleft" msgstr "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: mouseleft" #: ../../:4 msgid "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: mouseright" msgstr "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: mouseright" #: ../../:6 msgid "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: mousemiddle" msgstr "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: mousemiddle" #: ../../:8 msgid "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" msgstr "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" +#: ../../contributors_manual/krita_manual_conventions.rst:None +msgid "Horizontal Rulers" +msgstr "Righelli orizzontali" + #: ../../contributors_manual/krita_manual_conventions.rst:0 msgid "" ".. image:: images/sample.png\n" " :alt: an image." msgstr "" ".. image:: images/sample.png\n" " :alt: un'immagine." -#: ../../contributors_manual/krita_manual_conventions.rst:None -msgid "Horizontal Rulers" -msgstr "Righelli orizzontali" - #: ../../contributors_manual/krita_manual_conventions.rst:1 msgid "reStructuredText conventions for the Krita Manual" msgstr "Convenzioni di reStructuredText per il Manuale di Krita" #: ../../contributors_manual/krita_manual_conventions.rst:16 msgid "Mark-up conventions for the Krita Manual" msgstr "Convenzioni di mark-up per il Manuale di Krita" #: ../../contributors_manual/krita_manual_conventions.rst:18 msgid "" "This details the style conventions for using restructured text for the Krita " "Manual." msgstr "" "Questa parte tratta in dettaglio le convenzioni di stile per l'uso di testo " "«restructured» per il Manuale di Krita." #: ../../contributors_manual/krita_manual_conventions.rst:20 msgid "" "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):" msgstr "" "Si raccomanda di consultare le `specifiche ufficiali `_ di reStructuredText e, dato che risiede in " "Sourceforge, di salvarne una copia nel tuo disco rigido (Sourceforge ha, al " "momento della stesura di questa guida, alcuni problemi col server):" #: ../../contributors_manual/krita_manual_conventions.rst:23 msgid "" "`Primer `_" msgstr "" "`Primer `_" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "User Manual:" msgstr "Manuale utente:" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "" "`Quick Ref `_" msgstr "" "`Quick Ref `_" #: ../../contributors_manual/krita_manual_conventions.rst:25 msgid "" "`Text Cheatsheet `_" msgstr "" "`Text Cheatsheet `_" #: ../../contributors_manual/krita_manual_conventions.rst:27 msgid "" "`Introduction `_" msgstr "" "`Introduction `_" #: ../../contributors_manual/krita_manual_conventions.rst:28 msgid "" "`Markup `_" msgstr "" "`Markup `_" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "Reference Documentation:" msgstr "Documentazione di riferimento:" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "" "`Directives `_" msgstr "" "`Directives `_" #: ../../contributors_manual/krita_manual_conventions.rst:30 msgid "`Roles `_" msgstr "`Roles `_" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "Sphinx specific docs:" msgstr "Documenti specifici di Sphinx:" #: ../../contributors_manual/krita_manual_conventions.rst:32 #, fuzzy #| msgid "" #| "`Sphinx' page on restructured text `_ -- This is useful for the specific " #| "sphinx directives and roles it uses to generate for example table of " #| "contents." msgid "" "`Sphinx' page on restructured text `_ -- This is useful for the specific " "sphinx directives and roles it uses to generate for example table of " "contents." msgstr "" "Pagina `Sphinx' sul testo «restructured» `_ -- Utile per le direttive " "specifiche di Sphinx e i ruoli che utilizza per generare, per esempio, " "indici." #: ../../contributors_manual/krita_manual_conventions.rst:34 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." msgstr "" "Esistono differenze nei vari metodi di fare le cose tra la documentazione " "ufficiale di reStructuredText e quella di Sphinx. Questo documento dettaglia " "le convenzioni suggerite da seguire." #: ../../contributors_manual/krita_manual_conventions.rst:36 msgid "Contents" msgstr "Contenuto" #: ../../contributors_manual/krita_manual_conventions.rst:39 msgid "Meta data" msgstr "Metadati" #: ../../contributors_manual/krita_manual_conventions.rst:41 msgid "Each page should start with the following three things:" msgstr "Ogni pagina deve iniziare con i tre elementi seguenti:" #: ../../contributors_manual/krita_manual_conventions.rst:44 msgid "" "This is a general description of the page. It will be converted to an html " "meta tag which will be used by search engines::" msgstr "" "Questa è una descrizione generale della pagina. Sarà convertita in un meta " "tag html che sarà utilizzato dai motori di ricerca::" #: ../../contributors_manual/krita_manual_conventions.rst:46 msgid "" ".. meta::\n" " :description:\n" " Description." msgstr "" ".. meta::\n" " :description:\n" " Descrizione." #: ../../contributors_manual/krita_manual_conventions.rst:49 msgid "A meta description" msgstr "Una meta descrizione" #: ../../contributors_manual/krita_manual_conventions.rst:52 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::" msgstr "" "Serve solo per mantenere traccia di chi ha modificato la pagina e attribuire " "i crediti. Deve essere racchiusa in un commento in modo che non sia " "facilmente leggibile dalle macchine. La licenza dell'intero manuale è GDL " "1.3 e deve essere anch'essa racchiusa qui::" #: ../../contributors_manual/krita_manual_conventions.rst:54 msgid "" ".. metadata-placeholder\n" "\n" " :authors: - Author 1\n" " - Author 2\n" " :license: GNU free documentation license 1.3 or later." msgstr "" ".. metadata-placeholder\n" "\n" " :authors: - Autore 1\n" " - Autore 2\n" " :license: GNU free documentation license 1.3 o successiva." #: ../../contributors_manual/krita_manual_conventions.rst:58 msgid "A list of authors and a license." msgstr "Un elenco degli autori e una licenza." #: ../../contributors_manual/krita_manual_conventions.rst:61 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::" msgstr "" "Sono termini separati da virgola grazie ai quali la pagina sarà indicizzata " "in :ref:`genindex`. L'indice generato è molto utile sia per i pdf, sia per " "le persone che non sono sicure del nome esatto del termine che stanno " "ricercando. Sono definiti come segue::" #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid "Indexing terms." msgstr "Termini di indicizzazione." #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid ".. index:: Keyword, Keyword with Spaces, ! Main Definition Keyword" msgstr "" ".. index:: Parola_chiave, Parola chiave con spazi, ! Parola chiave di una " "definizione principale" #: ../../contributors_manual/krita_manual_conventions.rst:66 msgid "" "This is so we can easily link to the page using ``:ref:`label_name```. Try " "to make this a nice variable name::" msgstr "" "Questo serve in modo che possiamo collegarci facilmente alla pagina " "utilizzando ``:ref:`label_name```. Cerca di scegliere un buon nome di " "variabile::" #: ../../contributors_manual/krita_manual_conventions.rst:68 msgid ".. _label_name:" msgstr ".. _label_name:" #: ../../contributors_manual/krita_manual_conventions.rst:70 msgid "" "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." msgstr "" "Dopo l'etichetta devi aggiungere un titolo, dato che ``:ref:`label_name``` " "si riferirà al titolo per compilare il testo del collegamento." #: ../../contributors_manual/krita_manual_conventions.rst:71 msgid "A label." msgstr "Un'etichetta." #: ../../contributors_manual/krita_manual_conventions.rst:74 msgid "Headings" msgstr "Titoli (Headings)" #: ../../contributors_manual/krita_manual_conventions.rst:76 msgid "Headings will be done in the following order::" msgstr "I titoli vanno creati nell'ordine seguente::" #: ../../contributors_manual/krita_manual_conventions.rst:78 msgid "" "############\n" "Part/Section\n" "############\n" "\n" "For pages that have a lot of subpages.\n" "\n" "=========\n" "Heading 1\n" "=========\n" "\n" "Start most manual pages with this.\n" "\n" "Heading 2\n" "---------\n" "\n" "Heading 3\n" "~~~~~~~~~\n" "\n" "Heading 4\n" "^^^^^^^^^\n" "\n" "Heading 5\n" "'''''''''\n" "\n" "Heading 6\n" "\"\"\"\"\"\"\"\"\"" msgstr "" "############\n" "Parte/Sezione\n" "############\n" "\n" "Per le pagine che hanno molte sotto-pagine.\n" "\n" "=========\n" "Titolo 1\n" "=========\n" "\n" "Inizia la maggior parte delle pagine del manuale con questo.\n" "\n" "Titolo 2\n" "---------\n" "\n" "Titolo 3\n" "~~~~~~~~~\n" "\n" "Titolo 4\n" "^^^^^^^^^\n" "\n" "Titolo 5\n" "'''''''''\n" "\n" "Titolo 6\n" "\"\"\"\"\"\"\"\"\"" #: ../../contributors_manual/krita_manual_conventions.rst:105 #, fuzzy #| msgid "" #| "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." msgid "" "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." msgstr "" "Queste convenzioni sono stabilite più o meno dalla procedura di conversione " "da mediawiki a reStructuredText di pandoc. Se necessiti di più di quattro " "titoli, chiediti prima se la pagina non è troppo complicata e deve essere " "divisa." #: ../../contributors_manual/krita_manual_conventions.rst:107 msgid "" "Sometimes you need to link to a subsection of a page, add a label above the " "heading in that case." msgstr "" "A volte hai bisogno di collegarti a una sottosezione di una pagina, in tal " "caso aggiungi un'etichetta sopra il titolo." #: ../../contributors_manual/krita_manual_conventions.rst:109 msgid "" "Headers should not end with punctuation, as the header will be used as the " "link name when linking to a label." msgstr "" "I titoli non devono terminare con punteggiatura, dato che saranno utilizzati " "come nome del collegamento quando ci si collega a un'etichetta." #: ../../contributors_manual/krita_manual_conventions.rst:112 msgid "Linking" msgstr "Collegamenti" #: ../../contributors_manual/krita_manual_conventions.rst:114 msgid "" "Linking is done with ``:ref:`label_name```. When you need an alternative " "link text, you use ``:ref:`actual text shown ```." msgstr "" "Il collegamento si crea con ``:ref:`label_name```. Quando ti serve un nome " "alternativo, usa ``:ref:`testo reale da mostrare ```." #: ../../contributors_manual/krita_manual_conventions.rst:116 msgid "" "Linking to external pages is done with ```url`_`` and ```link name " "`_``, which'll become `link name `_." msgstr "" "Il collegamento a pagine esterne viene creato con ```url`_`` e ```nome del " "collegamento `_``, che diverranno il `nome del collegamento `_." #: ../../contributors_manual/krita_manual_conventions.rst:118 #, fuzzy #| msgid "" #| "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." msgid "" "`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." msgstr "" "Pandoc preferisce cambiare questi comandi in ```nome del collegamento`__`` e " "poi aggiungere `` .. __ :url `` alla fine del documento. Questo è il " "cosiddetto 'collegamento ipertestuale anonimo', il che significa che a " "seconda dell'ordine in cui appaiono i collegamenti nel testo, l'ordine dei " "collegamenti alla fine del testo è associato a un altro. Se ciò sembra " "confuso e difficoltoso, è perché in realtà lo è. Questo è anche il motivo " "per cui preferiamo evitare collegamenti di questo genere." #: ../../contributors_manual/krita_manual_conventions.rst:121 msgid "Footnotes and further reading" msgstr "Note a piè pagina e ulteriori letture" #: ../../contributors_manual/krita_manual_conventions.rst:123 msgid "" "Footnotes can be made in 3 ways, the most common one is with autonumbering, " "as per reference:" msgstr "" "Le note a piè pagina vengono create in tre modi, il più comune è con la " "numerazione automatica, come i riferimenti:" #: ../../contributors_manual/krita_manual_conventions.rst:125 msgid "" "[#]_ is a reference to footnote 1, and [#]_ is a reference to footnote 2." msgstr "" "[#]_ è un riferimento alla nota a piè pagina 1, e [#]_ è un riferimento alla " "nota a piè pagina 2." #: ../../contributors_manual/krita_manual_conventions.rst:128 msgid "This is footnote 1." msgstr "Questa è la nota a piè pagina 1." #: ../../contributors_manual/krita_manual_conventions.rst:129 msgid "This is footnote 2." msgstr "Questa è la nota a piè pagina 2." #: ../../contributors_manual/krita_manual_conventions.rst:130 msgid "This is footnote 3." msgstr "Questa è la nota a piè pagina 3." #: ../../contributors_manual/krita_manual_conventions.rst:132 msgid "[#]_ is a reference to footnote 3." msgstr "[#]_ è un riferimento alla nota a piè pagina 3." #: ../../contributors_manual/krita_manual_conventions.rst:134 msgid "Here is a citation reference: [CIT2002]_ ." msgstr "Ecco il riferimento di una citazione: [CIT2002]_ ." #: ../../contributors_manual/krita_manual_conventions.rst:136 msgid "" "This is the citation. It's just like a footnote, except the label is " "textual." msgstr "" "Questa è la citazione. È simile a una nota a piè pagina, ad eccezione del " "fatto che la didascalia è testuale." #: ../../contributors_manual/krita_manual_conventions.rst:139 #, fuzzy #| msgid "Citation can also be referenced with `citation `_" msgid "Citation can also be referenced with ```citation `_``." msgstr "" "Si può anche fare riferimento alla citazione con `citazione `_" #: ../../contributors_manual/krita_manual_conventions.rst:141 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." msgstr "" "Nel manuale in realtà non utilizziamo le note a piè pagina, dato che è " "piuttosto accademico per i nostri lettori. Tuttavia, raduniamo alla fine di " "una pagina documenti e collegamenti che forniscono maggiori informazioni su " "un argomento. Sphinx possiede la direttiva ``.. seealso::`` per i " "collegamenti esterni, mentre reStructuredText suggerisce l'uso di ``.. " "rubic:: Footnotes`` per la raccolta specifica di note a piè pagina, dato che " "funziona bene con LaTeX." #: ../../contributors_manual/krita_manual_conventions.rst:145 msgid "Images" msgstr "Immagini" #: ../../contributors_manual/krita_manual_conventions.rst:147 msgid "Use the image directive for images without captions::" msgstr "Usa la direttiva image per le immagini senza didascalie::" #: ../../contributors_manual/krita_manual_conventions.rst:149 msgid "" ".. image:: /images/sample.png\n" " :width: 800\n" " :align: center\n" " :alt: an image." msgstr "" ".. image:: /images/sample.png\n" " :width: 800\n" " :align: center\n" " :alt: un'immagine." #: ../../contributors_manual/krita_manual_conventions.rst:154 msgid "And figure directives for images with captions::" msgstr "E la direttiva figure per le immagini con didascalia::" #: ../../contributors_manual/krita_manual_conventions.rst:156 msgid "" ".. figure:: /images/sample.png\n" " :figwidth: 800\n" " :align: center\n" " :alt: an image.\n" "\n" " A caption -- notice how the first letter is aligned with the :figwidth: " "option." msgstr "" ".. figure:: /images/sample.png\n" " :figwidth: 800\n" " :align: center\n" " :alt: un'immagine.\n" "\n" " Una didascalia -- nota come la prima lettere sia allineata all'opzione :" "figwidth: ." #: ../../contributors_manual/krita_manual_conventions.rst:163 msgid "The latter gives:" msgstr "L'ultima restituisce:" #: ../../contributors_manual/krita_manual_conventions.rst:170 msgid "" "A caption -- notice how the first letter of the caption in the directive is " "aligned with the :figwidth: option." msgstr "" "Una didascalia -- nota come la prima lettera della didascalia nella " "direttiva sia allineata con l'opzione :figwidth:." #: ../../contributors_manual/krita_manual_conventions.rst:172 msgid "" "Images should go into the ``/images`` folder. By using ``/images`` instead " "of ``images``, sphinx will know the filepath isn't relative." msgstr "" "Le immagini devono essere memorizzate nella cartella ``/images``. Se " "utilizzi ``/images`` al posto di ``images``, Sphinx saprà che il percorso " "dei file non è relativo." #: ../../contributors_manual/krita_manual_conventions.rst:175 msgid "In-text Markup" msgstr "Markup nel testo" #: ../../contributors_manual/krita_manual_conventions.rst:177 msgid "" "You can make text *emphasized* and **strong** with a single asterisk and " "double respectively::" msgstr "" "Puoi rendere il testo *in corsivo* e **in grassetto** rispettivamente con " "singolo e doppio asterisco::" #: ../../contributors_manual/krita_manual_conventions.rst:179 msgid "" "*emphasize*\n" "**strong**" msgstr "" "*corsivo*\n" "**grassetto**" #: ../../contributors_manual/krita_manual_conventions.rst:182 msgid "You cannot do both ***emphasized and strong***, so take a pick." msgstr "" "Non puoi utilizzare insieme ***corsivo e grassetto***, fai dunque una scelta." #: ../../contributors_manual/krita_manual_conventions.rst:184 msgid "" "You can :sub:`subscript text` and :sup:`superscript text` by using ``:sub:" "`text``` and ``:sup:`text```" msgstr "" "Puoi scrivere testo in :sub:`pedice` e :sup:`apice` utilizzando " "rispettivamente ``:sub:`testo``` e ``:sup:`testo```" #: ../../contributors_manual/krita_manual_conventions.rst:186 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::" msgstr "" "Tuttavia, usali con molta moderazione. È meglio utilizzare in ogni caso i " "markup semantici esistenti in Sphinx, perché rende più facile ai traduttori " "prendere delle decisioni sulla natura del testo da tradurre::" #: ../../contributors_manual/krita_manual_conventions.rst:188 msgid "" ":menuselection:`Settings --> Configure Krita`\n" ":guilabel:`File`\n" ":kbd:`Ctrl + Z`\n" ":program:`Krita`" msgstr "" ":menuselection:`Impostazioni --> Configura Krita`\n" ":guilabel:`File`\n" ":kbd:`Ctrl + Z`\n" ":program:`Krita`" #: ../../contributors_manual/krita_manual_conventions.rst:193 msgid "" "Avoid randomly bolding words. It does *not* make the text easier or " "friendlier to read." msgstr "" "Evita l'uso del grassetto su parole scelte a caso. Ciò *non* rende più " "semplice o amichevole la lettura del testo." #: ../../contributors_manual/krita_manual_conventions.rst:196 msgid "Substitution References" msgstr "Riferimenti di sostituzione" #: ../../contributors_manual/krita_manual_conventions.rst:198 msgid "" "You can create a sort of shorthand for a piece of text or an image by doing::" msgstr "" "Puoi creare una sorta di forma abbreviata di una parte di testo o " "un'immagine in questo modo::" #: ../../contributors_manual/krita_manual_conventions.rst:200 msgid ".. |shorthand| replace:: something or the other." msgstr ".. |shorthand| replace:: qualcosa o l'altro." #: ../../contributors_manual/krita_manual_conventions.rst:202 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\"." msgstr "" "ciò significa che se usi ``|shorthand|`` nel testo, esso sarà sostituito con " "'qualcosa o l'altro'. Questo è utile per le immagini e il testo che deve " "essere formattato in maniera complicata, come nel caso di «LaTeX»." #: ../../contributors_manual/krita_manual_conventions.rst:204 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." msgstr "" "La documentazione di Krita possiede ``|mouseleft|``, ``|mousemiddle|``, ``|" "mousescroll|`` e ``|mouseright|``, che diventano rispettivamente |" "mouseleft|, |mousemiddle|, |mousescroll| e |mouseright|. Essi sono definiti " "nel file conf.py di Sphinx e vengono allegati a ogni file rst." #: ../../contributors_manual/krita_manual_conventions.rst:206 msgid "" "For links, if you reuse the same link over and over, you can write something " "like the following at the end of the file::" msgstr "" "Per i collegamenti, se riutilizzi lo stesso collegamento più e più volte, " "puoi scrivere alla fine del file qualcosa di simile a questo::" #: ../../contributors_manual/krita_manual_conventions.rst:208 msgid "" ".. _bugzilla: https://bugs.kde.org/\n" ".. _Krita Manual: https://docs.krita.org/" msgstr "" ".. _bugzilla: https://bugs.kde.org/\n" ".. _Krita Manual: https://docs.krita.org/" #: ../../contributors_manual/krita_manual_conventions.rst:211 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\"." msgstr "" "In seguito, quando digiti un collegamento, basta che usi ```bugzilla`_`` per " "collegarlo a bugzilla indicato da «bugzilla» come testo del collegamento. A " "sua volta, ```Krita Manual`_`` diventerà un collegamento a docs.krita.org " "col testo «Krita Manual»." #: ../../contributors_manual/krita_manual_conventions.rst:214 msgid "Lists" msgstr "Elenchi" #: ../../contributors_manual/krita_manual_conventions.rst:217 msgid "Ordinated lists" msgstr "Elenchi ordinati" #: ../../contributors_manual/krita_manual_conventions.rst:219 msgid "Apple" msgstr "Mela" #: ../../contributors_manual/krita_manual_conventions.rst:220 msgid "Pear" msgstr "Pera" #: ../../contributors_manual/krita_manual_conventions.rst:221 msgid "Banana" msgstr "Banana" #: ../../contributors_manual/krita_manual_conventions.rst:223 msgid "Or..." msgstr "Oppure..." #: ../../contributors_manual/krita_manual_conventions.rst:225 msgid "Table" msgstr "Tavolo" #: ../../contributors_manual/krita_manual_conventions.rst:226 msgid "Chair" msgstr "Sedia" #: ../../contributors_manual/krita_manual_conventions.rst:227 msgid "Wardrobe." msgstr "Armadio." #: ../../contributors_manual/krita_manual_conventions.rst:229 msgid "Augustus" msgstr "Augusto" #: ../../contributors_manual/krita_manual_conventions.rst:230 msgid "Nero" msgstr "Nerone" #: ../../contributors_manual/krita_manual_conventions.rst:231 msgid "Caligula" msgstr "Caligola" #: ../../contributors_manual/krita_manual_conventions.rst:232 msgid "Trajan" msgstr "Traiano" #: ../../contributors_manual/krita_manual_conventions.rst:234 msgid "They can be defined as follows::" msgstr "Essi possono essere definiti come segue::" #: ../../contributors_manual/krita_manual_conventions.rst:236 msgid "" "1. Apple\n" "2. Pear\n" "3. Banana\n" "\n" "#. Apple\n" "#. Pear\n" "#. Banana\n" "\n" "A. Table\n" "B. Chair\n" "C. Wardrobe\n" "\n" "A. Table\n" "#. Chair\n" "#. Wardrobe\n" "\n" "I. Augustus\n" "#. Nero\n" "#. Caligula\n" "#. Trajan" msgstr "" "1. Mela\n" "2. Pera\n" "3. Banana\n" "\n" "#. Mela\n" "#. Pera\n" "#. Banana\n" "\n" "A. Tavolo\n" "B. Sedia\n" "C. Armadio\n" "\n" "A. Tavolo\n" "#. Sedia\n" "#. Armadio\n" "\n" "I. Augusto\n" "#. Nerone\n" "#. Caligola\n" "#. Traiano" #: ../../contributors_manual/krita_manual_conventions.rst:258 msgid "Unordered lists" msgstr "Elenchi non ordinati (puntati)" #: ../../contributors_manual/krita_manual_conventions.rst:260 msgid "red" msgstr "rosso" #: ../../contributors_manual/krita_manual_conventions.rst:261 msgid "yellow" msgstr "giallo" #: ../../contributors_manual/krita_manual_conventions.rst:263 msgid "seagreen" msgstr "verdemare" #: ../../contributors_manual/krita_manual_conventions.rst:264 msgid "verdigris" msgstr "verde-grigio" #: ../../contributors_manual/krita_manual_conventions.rst:265 msgid "teal" msgstr "foglia di tè" #: ../../contributors_manual/krita_manual_conventions.rst:266 #, fuzzy #| msgid "veridian" msgid "viridian" msgstr "verdone" #: ../../contributors_manual/krita_manual_conventions.rst:268 msgid "dark emerald" msgstr "smeraldo scuro" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "green" msgstr "verde" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "emerald" msgstr "smeraldo" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "light emerald" msgstr "smeraldo chiaro" #: ../../contributors_manual/krita_manual_conventions.rst:270 msgid "very light emerald." msgstr "smeraldo chiarissimo." #: ../../contributors_manual/krita_manual_conventions.rst:271 msgid "blue" msgstr "blu" #: ../../contributors_manual/krita_manual_conventions.rst:273 msgid "Defined as such::" msgstr "Definiti come segue::" #: ../../contributors_manual/krita_manual_conventions.rst:275 #, fuzzy #| msgid "" #| "- red\n" #| "- yellow\n" #| "- green\n" #| " - seagreen\n" #| " - verdigris\n" #| " - teal\n" #| " - veridian\n" #| " - emerald\n" #| " - dark emerald\n" #| " - light emerald\n" #| " - very light emerald.\n" #| "- blue" msgid "" "- red\n" "- yellow\n" "- green\n" " - seagreen\n" " - verdigris\n" " - teal\n" " - viridian\n" " - emerald\n" " - dark emerald\n" " - light emerald\n" " - very light emerald.\n" "- blue" msgstr "" "- rosso\n" "- giallo\n" "- verde\n" " - verdemare\n" " - verde-grigio\n" " - foglia di tè\n" " - verdone\n" " - smeraldo\n" " - smeraldo scuro\n" " - smeraldo chiaro\n" " - smeraldo chiarissimo.\n" "- blu" #: ../../contributors_manual/krita_manual_conventions.rst:289 msgid "Definition Lists" msgstr "Elenchi di definizioni" #: ../../contributors_manual/krita_manual_conventions.rst:291 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." msgstr "" "Tra i preferiti! Gli elenchi di definizioni si rivelano molto utili quando " "hai a che fare con l'elencazione di tutte le opzioni in un'area e stai " "cercando un modo per aggiungere una breve spiegazione al loro lato." #: ../../contributors_manual/krita_manual_conventions.rst:293 msgid "Definition" msgstr "Definizione" #: ../../contributors_manual/krita_manual_conventions.rst:294 #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Explanation." msgstr "Spiegazione." #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Another option" msgstr "Un'altra opzione" #: ../../contributors_manual/krita_manual_conventions.rst:299 msgid "You can make them like this::" msgstr "Puoi crearli così::" #: ../../contributors_manual/krita_manual_conventions.rst:301 #, fuzzy #| msgid "" #| "Definition\n" #| " explanation.\n" #| "Another option\n" #| " Explanation." msgid "" "Definition\n" " Explanation.\n" "Another option\n" " Explanation." msgstr "" "Definizione\n" " spiegazione.\n" "Un'altra opzione\n" " Spiegazione." #: ../../contributors_manual/krita_manual_conventions.rst:304 msgid "To make them." msgstr "Per crearli." #: ../../contributors_manual/krita_manual_conventions.rst:307 msgid "Tables" msgstr "Tabelle" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Purpose" msgstr "Scopo" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Table type" msgstr "Tipo di tabella" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "listing shortcuts" msgstr "elenco scorciatoie" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "Simple table" msgstr "Tabella semplice" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "lots of colspans" msgstr "molti colspan" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "Grid table" msgstr "Tabella a griglia" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "Simple but long" msgstr "Semplice ma lungo" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "List Table" msgstr "Tabella elenco" #: ../../contributors_manual/krita_manual_conventions.rst:317 msgid "Done as follows::" msgstr "Create come segue::" #: ../../contributors_manual/krita_manual_conventions.rst:319 msgid "" "================== ============\n" "Purpose Table type\n" "================== ============\n" "listing shortcuts Simple table\n" "lots of colspans Grid table\n" "Simple but long List Table\n" "================== ============\n" "\n" "+-----------------+------------+\n" "|Purpose |Table Type |\n" "+=================+============+\n" "|listing shortcuts|Simple table|\n" "+-----------------+------------+\n" "|lots of colspans |Grid table |\n" "+-----------------+------------+\n" "|Simple but long |List table |\n" "+-----------------+------------+\n" "\n" ".. list-table::\n" " :header-rows: 1\n" "\n" " - * Purpose\n" " * Table Type\n" " - * listing shortcuts\n" " * simple table\n" " - * lots of colspans\n" " * grid table\n" " - * simple but long\n" " * list table" msgstr "" "================== =================\n" "Scopo Tipo di tabella\n" "================== =================\n" "elenco scorciatoie Tabella semplice\n" "molti colspan Tabella a griglia\n" "Semplice ma lungo Tabella elenco\n" "================== =================\n" "\n" "+------------------+-----------------+\n" "|Scopo |Tipo di tabella |\n" "+==================+=================+\n" "|elenco scorciatoie|Tabella semplice |\n" "+------------------+-----------------+\n" "|molti colspan |Tabella a griglia|\n" "+------------------+-----------------+\n" "|Semplice ma lungo |Tabella elenco |\n" "+------------------+-----------------+\n" "\n" ".. list-table::\n" " :header-rows: 1\n" "\n" " - * Scopo\n" " * Tipo di tabella\n" " - * elenco scorciatoie\n" " * tabella semplice\n" " - * molti colspan\n" " * tabella a griglia\n" " - * semplice ma lungo\n" " * tabella elenco" #: ../../contributors_manual/krita_manual_conventions.rst:349 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." msgstr "" "Le tabelle a griglia complete sono più adatte quando hai la necessità di " "utilizzare tutte le caratteristiche delle righe e delle colonne, ma sono " "difficili da creare. Per questo motivo, è meglio creare le tabelle piccole " "con la sintassi semplice, mentre è meglio creare quelle davvero lunghe " "utilizzando una direttiva list dato che è molto più semplice da scrivere e " "da gestire." #: ../../contributors_manual/krita_manual_conventions.rst:352 msgid "Admonishments and asides" msgstr "Raccomandazioni e digressioni" #: ../../contributors_manual/krita_manual_conventions.rst:356 msgid "" "Admonishments are sort of like a separate section that the reader needs to " "pay attention to." msgstr "" "Le raccomandazioni sono una sorta di sezione separata cui il lettore deve " "prestare attenzione." #: ../../contributors_manual/krita_manual_conventions.rst:358 msgid "" "Admonishments that can be used are the following (in order of seriousness):" msgstr "" "Le raccomandazioni che si possono utilizzare sono le seguenti (in ordine di " "importanza):" #: ../../contributors_manual/krita_manual_conventions.rst:362 #, fuzzy #| msgid "" #| "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." 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\"." msgstr "" "I suggerimenti (Hints) si rivelano utili per fornire ulteriori informazioni " "su un argomento funzionale al testo principale. Per esempio, suggerimento: " "openSuse chiama questi pacchetti in modo diverso rispetto a Debian." #: ../../contributors_manual/krita_manual_conventions.rst:366 #, fuzzy #| 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 "" "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\"." msgstr "" "Informazioni aggiuntive su come fare qualcosa, per esempio «puoi creare un " "modello per la creazione del tuo documento preferito», oppure «usa m per " "rispecchiare le tele e scoprire più facilmente errori nel disegno»." #: ../../contributors_manual/krita_manual_conventions.rst:370 msgid "Something that is important to note, but is not necessarily negative." msgstr "Qualcosa che è importante da notare ma non necessariamente negativa." #: ../../contributors_manual/krita_manual_conventions.rst:374 msgid "This is in general when something is negative." msgstr "In generale, quando qualcosa è negativa." #: ../../contributors_manual/krita_manual_conventions.rst:378 msgid "" "General attention grabber. Use this when the subject is more important than " "warning, but not as important that is could get a dataloss." msgstr "" "Qualcosa che attira l'attenzione generale. Usalo quando il soggetto è più " "importante dell'avviso ma non così importante da provocare una perdita di " "dati." #: ../../contributors_manual/krita_manual_conventions.rst:382 #, fuzzy #| msgid "" #| "This is for things that could cause dataloss, like forgetting to save, or " #| "that python currently has no undo functionality." msgid "" "This is for things that could cause dataloss, like forgetting to save, or " "that Python currently has no undo functionality." msgstr "" "Da utilizzare per cose che possono causare perdita di dati, come " "dimenticarsi di salvare o che Python attualmente non possiede funzioni di " "annullamento delle azioni." #: ../../contributors_manual/krita_manual_conventions.rst:386 msgid "" "This should be for things that are dangerous for the computer in general, " "this includes things that can cause out of memory style freezes." msgstr "" "Deve essere utilizzato per le cose che sono dannose per il computer in " "generale, che include azioni che possono causare blocchi tipo esaurimento di " "memoria." #: ../../contributors_manual/krita_manual_conventions.rst:390 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." msgstr "" "Questo probabilmente non è pertinente per un manuale. Sphinx può creare " "manualmente questi avvertimenti in determinate situazioni, ma la nostra " "configurazione non lo fa in modo predefinito." #: ../../contributors_manual/krita_manual_conventions.rst:392 #, fuzzy #| msgid "generic admonition that can have any text." msgid "Generic admonition that can have any text" msgstr "avvertimento generico che può contenere del testo." #: ../../contributors_manual/krita_manual_conventions.rst:394 msgid "Text." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:396 #, fuzzy #| msgid "You can make them like this::" msgid "You can make it like this::" msgstr "Puoi crearli così::" #: ../../contributors_manual/krita_manual_conventions.rst:398 #, fuzzy #| msgid "" #| ".. admonition:: generic admonition that can have any text.\n" #| "\n" #| " Text" msgid "" ".. admonition:: Generic admonition that can have any text\n" "\n" " Text." msgstr "" ".. admonition:: avvertimento generico che può contenere del testo.\n" "\n" " Testo" #: ../../contributors_manual/krita_manual_conventions.rst:404 msgid "Sphinx also adds::" msgstr "Sphinx aggiunge anche::" #: ../../contributors_manual/krita_manual_conventions.rst:406 msgid "" ".. seealso::\n" "\n" " Which is useful to collect external links and references." msgstr "" ".. seealso::\n" "\n" " Che è utile per raccogliere collegamenti esterni e riferimenti." #: ../../contributors_manual/krita_manual_conventions.rst:414 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." msgstr "" "I righelli orizzontali sono in genere utilizzati quando l'argomento cambia " "in modo repentino. È molto comune in scritti più narrativi, come storia o " "racconti. Il manuale di Krita possiede uno stile di scrittura più tecnico e " "di riferimenti, ossia non ci dilunghiamo di solito per indicare come due " "elementi si combinano, ma tuttavia possono essere presenti descrizioni " "piuttosto lunghe per giustificare il motivo di certi passaggi fatti in un " "certo modo. I cambi di argomento avvengono, dunque, perché si passa a un " "nuovo paragrafo, anziché passare a un paragrafo collegato. È dunque meglio " "utilizzare i titoli o la direttiva ``.. Topic::``. I titoli rendono anche la " "lettura più semplice." #: ../../contributors_manual/krita_manual_conventions.rst:418 msgid "That said, horizontal rulers can be made with ``----``." msgstr "" "Detto questo, i righelli orizzontali possono essere creati con ``----``." #: ../../contributors_manual/krita_manual_conventions.rst:421 #, fuzzy #| msgid "The rubric directive." msgid "The rubric directive" msgstr "La direttiva rubric (titolo)" #: ../../contributors_manual/krita_manual_conventions.rst:422 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::" msgstr "" "La direttiva rubric è una direttiva per titoli che a un primo sguardo " "assomiglia ad «topic» (argomento), ma laddove l'argomento si occupa di vari " "paragrafi, rubric in sé si occupa solo del titolo, in questo modo::" #: ../../contributors_manual/krita_manual_conventions.rst:424 #, fuzzy #| msgid ".. rubric:: The rubric directive." msgid ".. rubric:: The rubric directive" msgstr ".. rubric:: La direttiva rubric (titolo)." #: ../../contributors_manual/krita_manual_conventions.rst:428 msgid "So, when to use these?" msgstr "Quando utilizzarle, dunque?" #: ../../contributors_manual/krita_manual_conventions.rst:429 msgid "" "Only use them when you think the subject is too minor to have a proper " "heading." msgstr "" "Utilizzale solo quando ritieni che l'oggetto sia troppo secondario per avere " "un proprio titolo." #: ../../contributors_manual/krita_manual_conventions.rst:431 msgid "Topic" msgstr "Argomento" #: ../../contributors_manual/krita_manual_conventions.rst:432 msgid "" "When the text is separated from the flow, so it goes into a different " "subject than the text itself is naturally going to." msgstr "" "Quando il testo è separato dal flusso, dunque finisce all'interno di un " "oggetto diverso da quello in cui il testo stesso andrebbe naturalmente." #: ../../contributors_manual/krita_manual_conventions.rst:433 msgid "Rubric" msgstr "Rubric" #: ../../contributors_manual/krita_manual_conventions.rst:434 msgid "" "When the text isn't separated from the flow, but it does not need a header " "either." msgstr "" "Quando il testo non è separato dal flusso ma non necessita un suo titolo." #: ../../contributors_manual/krita_manual_conventions.rst:436 msgid "Admonishments" msgstr "Raccomandazioni" #: ../../contributors_manual/krita_manual_conventions.rst:436 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." msgstr "" "Solo quando sono significative. Ciò è vero specialmente per le " "raccomandazioni di avviso e pericolo, poiché la loro presenza eccessiva " "rischia di vanificarne l'effetto voluto." #: ../../contributors_manual/krita_manual_conventions.rst:439 msgid "Code Snippets" msgstr "Frammenti di codice" #: ../../contributors_manual/krita_manual_conventions.rst:441 msgid "``Inline code snippets`` are done with ````backticks````." msgstr "" "I ``frammenti di codice in linea`` vengono creati con i caratteri ````apici " "inversi (backtick)````." #: ../../contributors_manual/krita_manual_conventions.rst:443 msgid "" "Multi-line code snippets are done by ending the previous section with ``::" "``, which'll look like this::" msgstr "" "I frammenti di codice multi-riga vengono creati terminando il paragrafo " "precedente con ``::``, che assomiglierà a questo::" #: ../../contributors_manual/krita_manual_conventions.rst:445 msgid "" "This is a paragraph, and we define a preformated snippet like so::\n" "\n" " Be sure to add a white space and a tab afterwards before starting the " "snippet." msgstr "" "Questo è un paragrafo, e definiamo un frammento con testo preformattato in " "questo modo::\n" "\n" " Assicurati di aggiungere uno spazio vuoto e una tabulazione prima di " "iniziare il frammento." #: ../../contributors_manual/krita_manual_conventions.rst:449 msgid "" "You can also use the ``.. code::`` directive. If you add the language name " "after it, it'll do the appropriate syntax highlighting::" msgstr "" "Puoi utilizzare anche la direttiva ``.. code::``. Se, dopo di essa, aggiungi " "il nome del linguaggio, sarà usata l'evidenziazione sintattica appropriata::" #: ../../contributors_manual/krita_manual_conventions.rst:451 #, fuzzy #| msgid "" #| ".. code:: python\n" #| "\n" #| " def my_function():\n" #| " # comment\n" #| " alist = []\n" #| " alist.append(1)\n" #| " string = \"hello world\"" msgid "" ".. code:: python\n" "\n" " # Python comment\n" " def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" ".. code:: python\n" "\n" " def my_function():\n" " # commento\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" #: ../../contributors_manual/krita_manual_conventions.rst:459 msgid "Becomes" msgstr "Diventa" #: ../../contributors_manual/krita_manual_conventions.rst:468 #, fuzzy #| msgid "" #| "def my_function():\n" #| " # comment\n" #| " alist = []\n" #| " alist.append(1)\n" #| " string = \"hello world\"" msgid "" "# Python comment\n" "def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" "def my_function():\n" " # commento\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" #: ../../contributors_manual/krita_manual_conventions.rst:469 msgid "some more..." msgstr "e ancora..." #: ../../contributors_manual/krita_manual_conventions.rst:483 #, fuzzy #| msgid "" #| "int myFunction(int i) {\n" #| " i += 1;\n" #| "\n" #| " // Check if more than 12\n" #| " if (i>12) {\n" #| " i = 0;\n" #| " }\n" #| " return i;\n" #| "}" msgid "" "// C++ comment\n" "int myFunction(int i) {\n" " i += 1;\n" "\n" " // Check if more than 12\n" " if (i>12) {\n" " i = 0;\n" " }\n" " return i;\n" "}" msgstr "" "int myFunction(int i) {\n" " i += 1;\n" "\n" " // Controlla se più di 12\n" " if (i>12) {\n" " i = 0;\n" " }\n" " return i;\n" "}" #: ../../contributors_manual/krita_manual_conventions.rst:498 #, fuzzy #| msgid "" #| "body {\n" #| " margin: 0 auto;\n" #| " /* is 800 still sensible? */\n" #| " max-width:800px;\n" #| " font-size:16px;\n" #| " color:#333;\n" #| " background-color: #eee;\n" #| " padding:1em;\n" #| " font-family:serif;\n" #| " line-height: 1.4;\n" #| "}" msgid "" "/* CSS comment */\n" "body {\n" " margin: 0 auto;\n" " /* is 800 still sensible? */\n" " max-width:800px;\n" " font-size:16px;\n" " color:#333;\n" " background-color: #eee;\n" " padding:1em;\n" " font-family:serif;\n" " line-height: 1.4;\n" "}" msgstr "" "body {\n" " margin: 0 auto;\n" " /* 800 è ancora appropriato? */\n" " max-width:800px;\n" " font-size:16px;\n" " color:#333;\n" " background-color: #eee;\n" " padding:1em;\n" " font-family:serif;\n" " line-height: 1.4;\n" "}" #: ../../contributors_manual/krita_manual_conventions.rst:502 #, fuzzy #| msgid "" #| "

this is a " #| "paragraph.

" msgid "" "

this is " "a paragraph.

" msgstr "" "

questo è un " "paragrafo.

" #: ../../contributors_manual/krita_manual_conventions.rst:504 msgid "Other preformatted text" msgstr "Altro testo preformattato" #: ../../contributors_manual/krita_manual_conventions.rst:507 msgid "One can" msgstr "Uno può" #: ../../contributors_manual/krita_manual_conventions.rst:508 msgid "preformat" msgstr "preformattare" #: ../../contributors_manual/krita_manual_conventions.rst:509 msgid "text by" msgstr "il testo" #: ../../contributors_manual/krita_manual_conventions.rst:510 msgid "prepending" msgstr "mettendo davanti a" #: ../../contributors_manual/krita_manual_conventions.rst:511 msgid "each line" msgstr "ciascuna riga" #: ../../contributors_manual/krita_manual_conventions.rst:512 msgid "with a pipe" msgstr "una barra" #: ../../contributors_manual/krita_manual_conventions.rst:513 msgid "symbol" msgstr "verticale (simbolo pipe)" #: ../../contributors_manual/krita_manual_conventions.rst:515 msgid "Like so::" msgstr "In questo modo::" #: ../../contributors_manual/krita_manual_conventions.rst:517 msgid "" "| One can\n" "| preformat\n" "| text by\n" "| prepending\n" "| each line\n" "| with a pipe\n" "| symbol" msgstr "" "| Uno può\n" "| preformattare\n" "| il testo\n" "| mettendo davanti a\n" "| ciascuna riga\n" "| una barra\n" "| verticale (simbolo pipe)" #: ../../contributors_manual/krita_manual_conventions.rst:525 msgid "We don't actually use this anywhere in the manual." msgstr "In realtà non usiamo questo metodo nel manuale." #: ../../contributors_manual/krita_manual_conventions.rst:528 msgid "Glossaries, Terms and Index" msgstr "Glossari, termini e indice" #: ../../contributors_manual/krita_manual_conventions.rst:530 msgid "These are sphinx features." msgstr "Queste sono funzionalità proprie di Sphinx." #: ../../contributors_manual/krita_manual_conventions.rst:532 msgid "" "Index is used in the top section, right now only single index entries are " "used." msgstr "" "L'indice è utilizzato in cima, al momento sono utilizzate solo voci di " "indice singole." #: ../../contributors_manual/krita_manual_conventions.rst:534 msgid "" "Glossaries are used for some of the menu entry sections, but not all of them." msgstr "" "I glossari sono utilizzati per alcune sezioni delle voci di menu, ma non per " "tutte." #: ../../contributors_manual/krita_manual_conventions.rst:537 msgid "Quotes" msgstr "Virgolette" #: ../../contributors_manual/krita_manual_conventions.rst:539 msgid "Quotes are done like this::" msgstr "Le virgolette si creano in questo modo::" #: ../../contributors_manual/krita_manual_conventions.rst:541 msgid "" "I am not sure why you'd need quotes in a user manual...\n" "\n" "-- Wolthera" msgstr "" "Non siamo sicuri che tu abbia bisogno di virgolette in un manuale utente...\n" "\n" "-- Wolthera" #: ../../contributors_manual/krita_manual_conventions.rst:545 msgid "This becomes a blockquote." msgstr "Questo diventa un elemento blockquote." #: ../../contributors_manual/krita_manual_conventions.rst:547 msgid "I am not sure why you'd need quotes in a user manual..." msgstr "" "Non siamo sicuri che tu abbia bisogno di virgolette in un manuale utente..." #: ../../contributors_manual/krita_manual_conventions.rst:551 msgid "" "We do actually use quotes in some places. Try to add a link to the name to " "define where it came from." msgstr "" "In realtà utilizziamo le virgolette in alcune parti. Prova ad aggiungere un " "collegamento al nome per definire la sua origine." #: ../../contributors_manual/krita_manual_conventions.rst:552 msgid "Wolthera" msgstr "Wolthera" #~ msgid "explanation." #~ msgstr "spiegazione." #~ msgid "This looks like the following::" #~ msgstr "Apparirà più o meno come segue::" diff --git a/locale/ja/LC_MESSAGES/contributors_manual/krita_manual_conventions.po b/locale/ja/LC_MESSAGES/contributors_manual/krita_manual_conventions.po index 0bc7c8189..c39cafb2d 100644 --- a/locale/ja/LC_MESSAGES/contributors_manual/krita_manual_conventions.po +++ b/locale/ja/LC_MESSAGES/contributors_manual/krita_manual_conventions.po @@ -1,1136 +1,1136 @@ msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-09 03:27+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: 2019-03-02 16:12-0800\n" "Last-Translator: Japanese KDE translation team \n" "Language-Team: Japanese \n" "Language: ja\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" "X-Accelerator-Marker: &\n" "X-Text-Markup: kde4\n" #: ../../:2 msgid "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: mouseleft" msgstr "" #: ../../:4 msgid "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: mouseright" msgstr "" #: ../../:6 msgid "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: mousemiddle" msgstr "" #: ../../:8 msgid "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" msgstr "" +#: ../../contributors_manual/krita_manual_conventions.rst:None +msgid "Horizontal Rulers" +msgstr "" + #: ../../contributors_manual/krita_manual_conventions.rst:0 msgid "" ".. image:: images/sample.png\n" " :alt: an image." msgstr "" -#: ../../contributors_manual/krita_manual_conventions.rst:None -msgid "Horizontal Rulers" -msgstr "" - #: ../../contributors_manual/krita_manual_conventions.rst:1 msgid "reStructuredText conventions for the Krita Manual" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:16 msgid "Mark-up conventions for the Krita Manual" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:18 msgid "" "This details the style conventions for using restructured text for the Krita " "Manual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:20 msgid "" "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):" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:23 msgid "" "`Primer `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "User Manual:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "" "`Quick Ref `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:25 msgid "" "`Text Cheatsheet `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:27 msgid "" "`Introduction `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:28 msgid "" "`Markup `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "Reference Documentation:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "" "`Directives `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:30 msgid "`Roles `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "Sphinx specific docs:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "" "`Sphinx' page on restructured text `_ -- This is useful for the specific " "sphinx directives and roles it uses to generate for example table of " "contents." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:34 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:36 msgid "Contents" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:39 msgid "Meta data" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:41 msgid "Each page should start with the following three things:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:44 msgid "" "This is a general description of the page. It will be converted to an html " "meta tag which will be used by search engines::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:46 msgid "" ".. meta::\n" " :description:\n" " Description." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:49 msgid "A meta description" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:52 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:54 msgid "" ".. metadata-placeholder\n" "\n" " :authors: - Author 1\n" " - Author 2\n" " :license: GNU free documentation license 1.3 or later." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:58 msgid "A list of authors and a license." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:61 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid "Indexing terms." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid ".. index:: Keyword, Keyword with Spaces, ! Main Definition Keyword" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:66 msgid "" "This is so we can easily link to the page using ``:ref:`label_name```. Try " "to make this a nice variable name::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:68 msgid ".. _label_name:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:70 msgid "" "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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:71 msgid "A label." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:74 msgid "Headings" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:76 msgid "Headings will be done in the following order::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:78 msgid "" "############\n" "Part/Section\n" "############\n" "\n" "For pages that have a lot of subpages.\n" "\n" "=========\n" "Heading 1\n" "=========\n" "\n" "Start most manual pages with this.\n" "\n" "Heading 2\n" "---------\n" "\n" "Heading 3\n" "~~~~~~~~~\n" "\n" "Heading 4\n" "^^^^^^^^^\n" "\n" "Heading 5\n" "'''''''''\n" "\n" "Heading 6\n" "\"\"\"\"\"\"\"\"\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:105 msgid "" "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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:107 msgid "" "Sometimes you need to link to a subsection of a page, add a label above the " "heading in that case." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:109 msgid "" "Headers should not end with punctuation, as the header will be used as the " "link name when linking to a label." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:112 msgid "Linking" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:114 msgid "" "Linking is done with ``:ref:`label_name```. When you need an alternative " "link text, you use ``:ref:`actual text shown ```." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:116 msgid "" "Linking to external pages is done with ```url`_`` and ```link name " "`_``, which'll become `link name `_." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:118 msgid "" "`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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:121 msgid "Footnotes and further reading" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:123 msgid "" "Footnotes can be made in 3 ways, the most common one is with autonumbering, " "as per reference:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:125 msgid "" "[#]_ is a reference to footnote 1, and [#]_ is a reference to footnote 2." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:128 msgid "This is footnote 1." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:129 msgid "This is footnote 2." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:130 msgid "This is footnote 3." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:132 msgid "[#]_ is a reference to footnote 3." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:134 msgid "Here is a citation reference: [CIT2002]_ ." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:136 msgid "" "This is the citation. It's just like a footnote, except the label is " "textual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:139 msgid "Citation can also be referenced with ```citation `_``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:141 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:145 msgid "Images" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:147 msgid "Use the image directive for images without captions::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:149 msgid "" ".. image:: /images/sample.png\n" " :width: 800\n" " :align: center\n" " :alt: an image." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:154 msgid "And figure directives for images with captions::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:156 msgid "" ".. figure:: /images/sample.png\n" " :figwidth: 800\n" " :align: center\n" " :alt: an image.\n" "\n" " A caption -- notice how the first letter is aligned with the :figwidth: " "option." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:163 msgid "The latter gives:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:170 msgid "" "A caption -- notice how the first letter of the caption in the directive is " "aligned with the :figwidth: option." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:172 msgid "" "Images should go into the ``/images`` folder. By using ``/images`` instead " "of ``images``, sphinx will know the filepath isn't relative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:175 msgid "In-text Markup" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:177 msgid "" "You can make text *emphasized* and **strong** with a single asterisk and " "double respectively::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:179 msgid "" "*emphasize*\n" "**strong**" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:182 msgid "You cannot do both ***emphasized and strong***, so take a pick." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:184 msgid "" "You can :sub:`subscript text` and :sup:`superscript text` by using ``:sub:" "`text``` and ``:sup:`text```" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:186 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:188 msgid "" ":menuselection:`Settings --> Configure Krita`\n" ":guilabel:`File`\n" ":kbd:`Ctrl + Z`\n" ":program:`Krita`" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:193 msgid "" "Avoid randomly bolding words. It does *not* make the text easier or " "friendlier to read." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:196 msgid "Substitution References" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:198 msgid "" "You can create a sort of shorthand for a piece of text or an image by doing::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:200 msgid ".. |shorthand| replace:: something or the other." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:202 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:204 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:206 msgid "" "For links, if you reuse the same link over and over, you can write something " "like the following at the end of the file::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:208 msgid "" ".. _bugzilla: https://bugs.kde.org/\n" ".. _Krita Manual: https://docs.krita.org/" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:211 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:214 msgid "Lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:217 msgid "Ordinated lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:219 msgid "Apple" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:220 msgid "Pear" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:221 msgid "Banana" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:223 msgid "Or..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:225 msgid "Table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:226 msgid "Chair" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:227 msgid "Wardrobe." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:229 msgid "Augustus" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:230 msgid "Nero" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:231 msgid "Caligula" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:232 msgid "Trajan" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:234 msgid "They can be defined as follows::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:236 msgid "" "1. Apple\n" "2. Pear\n" "3. Banana\n" "\n" "#. Apple\n" "#. Pear\n" "#. Banana\n" "\n" "A. Table\n" "B. Chair\n" "C. Wardrobe\n" "\n" "A. Table\n" "#. Chair\n" "#. Wardrobe\n" "\n" "I. Augustus\n" "#. Nero\n" "#. Caligula\n" "#. Trajan" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:258 msgid "Unordered lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:260 msgid "red" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:261 msgid "yellow" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:263 msgid "seagreen" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:264 msgid "verdigris" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:265 msgid "teal" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:266 msgid "viridian" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:268 msgid "dark emerald" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "green" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "emerald" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "light emerald" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:270 msgid "very light emerald." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:271 msgid "blue" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:273 msgid "Defined as such::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:275 msgid "" "- red\n" "- yellow\n" "- green\n" " - seagreen\n" " - verdigris\n" " - teal\n" " - viridian\n" " - emerald\n" " - dark emerald\n" " - light emerald\n" " - very light emerald.\n" "- blue" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:289 msgid "Definition Lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:291 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:293 msgid "Definition" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:294 #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Explanation." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Another option" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:299 msgid "You can make them like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:301 msgid "" "Definition\n" " Explanation.\n" "Another option\n" " Explanation." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:304 msgid "To make them." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:307 msgid "Tables" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Purpose" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Table type" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "listing shortcuts" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "Simple table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "lots of colspans" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "Grid table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "Simple but long" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "List Table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:317 msgid "Done as follows::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:319 msgid "" "================== ============\n" "Purpose Table type\n" "================== ============\n" "listing shortcuts Simple table\n" "lots of colspans Grid table\n" "Simple but long List Table\n" "================== ============\n" "\n" "+-----------------+------------+\n" "|Purpose |Table Type |\n" "+=================+============+\n" "|listing shortcuts|Simple table|\n" "+-----------------+------------+\n" "|lots of colspans |Grid table |\n" "+-----------------+------------+\n" "|Simple but long |List table |\n" "+-----------------+------------+\n" "\n" ".. list-table::\n" " :header-rows: 1\n" "\n" " - * Purpose\n" " * Table Type\n" " - * listing shortcuts\n" " * simple table\n" " - * lots of colspans\n" " * grid table\n" " - * simple but long\n" " * list table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:349 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:352 msgid "Admonishments and asides" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:356 msgid "" "Admonishments are sort of like a separate section that the reader needs to " "pay attention to." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:358 msgid "" "Admonishments that can be used are the following (in order of seriousness):" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:362 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:366 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:370 msgid "Something that is important to note, but is not necessarily negative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:374 msgid "This is in general when something is negative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:378 msgid "" "General attention grabber. Use this when the subject is more important than " "warning, but not as important that is could get a dataloss." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:382 msgid "" "This is for things that could cause dataloss, like forgetting to save, or " "that Python currently has no undo functionality." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:386 msgid "" "This should be for things that are dangerous for the computer in general, " "this includes things that can cause out of memory style freezes." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:390 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:392 msgid "Generic admonition that can have any text" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:394 msgid "Text." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:396 msgid "You can make it like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:398 msgid "" ".. admonition:: Generic admonition that can have any text\n" "\n" " Text." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:404 msgid "Sphinx also adds::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:406 msgid "" ".. seealso::\n" "\n" " Which is useful to collect external links and references." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:414 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:418 msgid "That said, horizontal rulers can be made with ``----``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:421 msgid "The rubric directive" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:422 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:424 msgid ".. rubric:: The rubric directive" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:428 msgid "So, when to use these?" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:429 msgid "" "Only use them when you think the subject is too minor to have a proper " "heading." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:431 msgid "Topic" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:432 msgid "" "When the text is separated from the flow, so it goes into a different " "subject than the text itself is naturally going to." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:433 msgid "Rubric" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:434 msgid "" "When the text isn't separated from the flow, but it does not need a header " "either." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:436 msgid "Admonishments" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:436 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:439 msgid "Code Snippets" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:441 msgid "``Inline code snippets`` are done with ````backticks````." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:443 msgid "" "Multi-line code snippets are done by ending the previous section with ``::" "``, which'll look like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:445 msgid "" "This is a paragraph, and we define a preformated snippet like so::\n" "\n" " Be sure to add a white space and a tab afterwards before starting the " "snippet." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:449 msgid "" "You can also use the ``.. code::`` directive. If you add the language name " "after it, it'll do the appropriate syntax highlighting::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:451 msgid "" ".. code:: python\n" "\n" " # Python comment\n" " def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:459 msgid "Becomes" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:468 msgid "" "# Python comment\n" "def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:469 msgid "some more..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:483 msgid "" "// C++ comment\n" "int myFunction(int i) {\n" " i += 1;\n" "\n" " // Check if more than 12\n" " if (i>12) {\n" " i = 0;\n" " }\n" " return i;\n" "}" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:498 msgid "" "/* CSS comment */\n" "body {\n" " margin: 0 auto;\n" " /* is 800 still sensible? */\n" " max-width:800px;\n" " font-size:16px;\n" " color:#333;\n" " background-color: #eee;\n" " padding:1em;\n" " font-family:serif;\n" " line-height: 1.4;\n" "}" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:502 msgid "" "

this is " "a paragraph.

" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:504 msgid "Other preformatted text" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:507 msgid "One can" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:508 msgid "preformat" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:509 msgid "text by" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:510 msgid "prepending" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:511 msgid "each line" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:512 msgid "with a pipe" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:513 msgid "symbol" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:515 msgid "Like so::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:517 msgid "" "| One can\n" "| preformat\n" "| text by\n" "| prepending\n" "| each line\n" "| with a pipe\n" "| symbol" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:525 msgid "We don't actually use this anywhere in the manual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:528 msgid "Glossaries, Terms and Index" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:530 msgid "These are sphinx features." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:532 msgid "" "Index is used in the top section, right now only single index entries are " "used." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:534 msgid "" "Glossaries are used for some of the menu entry sections, but not all of them." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:537 msgid "Quotes" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:539 msgid "Quotes are done like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:541 msgid "" "I am not sure why you'd need quotes in a user manual...\n" "\n" "-- Wolthera" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:545 msgid "This becomes a blockquote." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:547 msgid "I am not sure why you'd need quotes in a user manual..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:551 msgid "" "We do actually use quotes in some places. Try to add a link to the name to " "define where it came from." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:552 msgid "Wolthera" msgstr "" diff --git a/locale/ja/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po b/locale/ja/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po index 235649b96..24d00707d 100644 --- a/locale/ja/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po +++ b/locale/ja/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po @@ -1,1062 +1,1062 @@ msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-08 03:08+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: 2019-03-02 16:12-0800\n" "Last-Translator: Japanese KDE translation team \n" "Language-Team: Japanese \n" "Language: ja\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" "X-Accelerator-Marker: &\n" "X-Text-Markup: kde4\n" +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_matrix_profile.png" +msgstr "" + +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" +msgstr "" + #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group1.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group2.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group3.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group4.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/dockers/LUT_Management_Docker.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR_1.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR2.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_webcomic.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_print.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_games.svg" msgstr "" -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_matrix_profile.png" -msgstr "" - -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" -msgstr "" - #: ../../general_concepts/colors/color_managed_workflow.rst:1 msgid "How a color managed workflow works." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "Color" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "Color Management" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "ICC Profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "OCIO" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:17 msgid "Color Managed Workflow" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:19 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:22 msgid "Basic Info" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:24 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:26 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:29 msgid "What is the problem?" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:31 msgid "" "To explain the point of color management, you'd first need to learn which " "problem color management tries to solve." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:33 msgid "Let us imagine a kinder garden:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:35 msgid "" "The class of 28 children is subdivided in groups of 7. Each group has its " "own table." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:37 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:40 msgid "The following results come from painting:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:42 msgid "" "Even though all groups had the same assignment, each group's result looks " "different." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:49 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:56 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:64 msgid "" "Group 3 had vermillion red, citron yellow, emerald green and cerulean blue. " "They didn't mix their green, and thus ended up with a purer color." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:71 msgid "" "Finally, group 4 has vermillion red, citron yellow and cerulean blue. Their " "colors probably look like what you imagined." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:73 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!" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:75 msgid "For this purpose, we invented color management." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:78 msgid "What is color management?" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:80 msgid "" "Color management is, dryly put, a set of systems that tries to have the same " "color translate properly between color devices." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:82 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:84 msgid "" "From XYZ it can then be translated back into another device space, such as " "RGB (for screens), or CMYK (for printers)." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:86 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:88 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:90 msgid "Within both we can identify the following color spaces:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:93 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 " "`." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:94 msgid "Device spaces" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:96 msgid "Working spaces" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:97 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:99 msgid "Aesthetic or Look spaces" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:99 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:102 msgid "Color managed workflow" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:104 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:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:110 msgid ".. image:: images/color_category/Krita-colormanaged-workflow_text.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:110 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:112 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:114 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:116 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:118 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:120 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:122 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:124 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:127 msgid "So what does this mean?" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:133 msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_krita_text.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:133 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:135 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*." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:137 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:139 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:141 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:143 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.)" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:148 msgid "ICC profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:150 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:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:153 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:159 msgid "Matrix Shaper profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:159 msgid "" "Matrix shaper profiles have a few parameters that describe the color space " "which are then interpolated between, this requires a lot of maths." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:162 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:168 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:169 msgid "cLUT profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:171 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:174 msgid "Perceptual" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:174 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:177 msgid "Absolute Colorimetric" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:177 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:180 msgid "Relative Colorimetric" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:180 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:183 msgid "Saturation" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:183 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:185 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:188 msgid "LUT docker and HDR imaging" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:196 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:198 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:200 msgid "" "Component, exposure, gamma, whitepoint and blackpoint are knobs which allows " "you to modify the display filter." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:208 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:210 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:212 msgid "" "Black similarly, is brighter on a LCD display than a LED one, and " "incomparable with the black of a carefully sealed room." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:214 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:216 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:224 msgid "" "So, for example, we can choose to scale whiter-than-screen-white to our " "screen-white so we can see the contrasts there." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:226 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:228 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:230 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:232 msgid "" "Another example is to carefully watch the gradients in a certain section." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:234 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:237 msgid "In summary" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:239 msgid "Krita has two modes of color management:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:241 msgid "" "ICC works in terms of spaces relative to the CIEXYZ space, and requires an " "ICC profile." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:242 msgid "OCIO works in terms of interpretation, and makes use of LUTs." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:243 msgid "both can be made with a colorimeter." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:244 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:245 msgid "" "Set up your screen profiles under :menuselection:`Settings --> Configure " "Krita --> Color management`." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:246 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:247 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:249 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:251 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!" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:256 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!" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:260 msgid "" "No amount of color management in the world can make the image on your screen " "and the image out of the printer have 100% the same color." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:263 msgid "Exporting" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:265 msgid "" "When you have finished your image and are ready to export it, you can modify " "the color space to optimize it:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:267 msgid "If you are preparing an image for the web:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:269 msgid "" "If you use 16bit color depth or higher, convert the image to 8bit color " "depth. This will make the image much smaller." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:271 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:273 msgid "If it's a gray-scale image, convert it to gray-scale." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:274 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:279 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 " "`_, save your PNG, JPG or TIFF without an embedded profile to work " "around this." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:281 msgid "If you are preparing for print:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:283 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:284 msgid "" "Check with the printer what kind of image they expect. Maybe they expect " "sRGB color space, or perhaps they have their own profile." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:287 msgid "Interaction with other applications" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:290 msgid "Blender" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:292 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:294 msgid "" "Blender's OCIO config is under ``/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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:298 msgid "Windows Photo Viewer" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:300 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:303 msgid "Example workflows" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:305 msgid "" "Here are some example workflows to get a feeling of how your color " "management workflow may look like." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:307 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'." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:310 msgid "Webcomic" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:317 #: ../../general_concepts/colors/color_managed_workflow.rst:339 #: ../../general_concepts/colors/color_managed_workflow.rst:357 msgid "Input" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:318 #: ../../general_concepts/colors/color_managed_workflow.rst:340 #: ../../general_concepts/colors/color_managed_workflow.rst:358 msgid "Your screen profile. (You pick colors via your screen)" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:319 #: ../../general_concepts/colors/color_managed_workflow.rst:341 #: ../../general_concepts/colors/color_managed_workflow.rst:359 msgid "Workingspace" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:320 msgid "" "sRGB (the default screen profile) or any larger profile if you can spare the " "bit depth and like working in them." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:322 #: ../../general_concepts/colors/color_managed_workflow.rst:344 #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "Output" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:322 msgid "" "sRGB, ICC version 2, sRGB TRC for the internet, and a specialized CMYK " "profile from the printing house for the printed images." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:324 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:326 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:328 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:330 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:333 msgid "Print" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:342 msgid "sRGB or Rec. 2020 if you can afford the bit-depth being 16bit." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:344 msgid "" "Specialized CMYK profile from the printing house for the printed images." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:346 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:348 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:351 msgid "Games" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:360 msgid "sRGB or grayscale linear for roughness and specular maps." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "" "This one is tricky, but in the end it'll be sRGB for the regular player." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:364 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:366 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:368 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:370 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)." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:374 msgid "" "`Visualizing the XYZ color space `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:375 msgid "" "`Basics of gamma correction `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:376 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 `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:377 msgid "" "`2D examples of the effect of gamma-encoding on color maths `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:378 msgid "" "`Basic overview of color management from ArgyllCMS manual `_." msgstr "" diff --git a/locale/lt/LC_MESSAGES/contributors_manual/krita_manual_conventions.po b/locale/lt/LC_MESSAGES/contributors_manual/krita_manual_conventions.po index 5d03b15ec..56aced4f2 100644 --- a/locale/lt/LC_MESSAGES/contributors_manual/krita_manual_conventions.po +++ b/locale/lt/LC_MESSAGES/contributors_manual/krita_manual_conventions.po @@ -1,1140 +1,1140 @@ # Lithuanian translations for Krita Manual package. # 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. # Automatically generated, 2019. # msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-09 03:27+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: 2019-04-23 03:45+0200\n" "Last-Translator: Automatically generated\n" "Language-Team: lt\n" "Language: lt\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=4; plural=(n==1 ? 0 : n%10>=2 && (n%100<10 || n" "%100>=20) ? 1 : n%10==0 || (n%100>10 && n%100<20) ? 2 : 3);\n" #: ../../:2 msgid "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: mouseleft" msgstr "" #: ../../:4 msgid "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: mouseright" msgstr "" #: ../../:6 msgid "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: mousemiddle" msgstr "" #: ../../:8 msgid "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" msgstr "" +#: ../../contributors_manual/krita_manual_conventions.rst:None +msgid "Horizontal Rulers" +msgstr "" + #: ../../contributors_manual/krita_manual_conventions.rst:0 msgid "" ".. image:: images/sample.png\n" " :alt: an image." msgstr "" -#: ../../contributors_manual/krita_manual_conventions.rst:None -msgid "Horizontal Rulers" -msgstr "" - #: ../../contributors_manual/krita_manual_conventions.rst:1 msgid "reStructuredText conventions for the Krita Manual" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:16 msgid "Mark-up conventions for the Krita Manual" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:18 msgid "" "This details the style conventions for using restructured text for the Krita " "Manual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:20 msgid "" "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):" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:23 msgid "" "`Primer `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "User Manual:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "" "`Quick Ref `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:25 msgid "" "`Text Cheatsheet `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:27 msgid "" "`Introduction `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:28 msgid "" "`Markup `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "Reference Documentation:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "" "`Directives `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:30 msgid "`Roles `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "Sphinx specific docs:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "" "`Sphinx' page on restructured text `_ -- This is useful for the specific " "sphinx directives and roles it uses to generate for example table of " "contents." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:34 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:36 msgid "Contents" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:39 msgid "Meta data" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:41 msgid "Each page should start with the following three things:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:44 msgid "" "This is a general description of the page. It will be converted to an html " "meta tag which will be used by search engines::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:46 msgid "" ".. meta::\n" " :description:\n" " Description." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:49 msgid "A meta description" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:52 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:54 msgid "" ".. metadata-placeholder\n" "\n" " :authors: - Author 1\n" " - Author 2\n" " :license: GNU free documentation license 1.3 or later." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:58 msgid "A list of authors and a license." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:61 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid "Indexing terms." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid ".. index:: Keyword, Keyword with Spaces, ! Main Definition Keyword" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:66 msgid "" "This is so we can easily link to the page using ``:ref:`label_name```. Try " "to make this a nice variable name::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:68 msgid ".. _label_name:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:70 msgid "" "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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:71 msgid "A label." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:74 msgid "Headings" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:76 msgid "Headings will be done in the following order::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:78 msgid "" "############\n" "Part/Section\n" "############\n" "\n" "For pages that have a lot of subpages.\n" "\n" "=========\n" "Heading 1\n" "=========\n" "\n" "Start most manual pages with this.\n" "\n" "Heading 2\n" "---------\n" "\n" "Heading 3\n" "~~~~~~~~~\n" "\n" "Heading 4\n" "^^^^^^^^^\n" "\n" "Heading 5\n" "'''''''''\n" "\n" "Heading 6\n" "\"\"\"\"\"\"\"\"\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:105 msgid "" "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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:107 msgid "" "Sometimes you need to link to a subsection of a page, add a label above the " "heading in that case." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:109 msgid "" "Headers should not end with punctuation, as the header will be used as the " "link name when linking to a label." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:112 msgid "Linking" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:114 msgid "" "Linking is done with ``:ref:`label_name```. When you need an alternative " "link text, you use ``:ref:`actual text shown ```." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:116 msgid "" "Linking to external pages is done with ```url`_`` and ```link name " "`_``, which'll become `link name `_." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:118 msgid "" "`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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:121 msgid "Footnotes and further reading" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:123 msgid "" "Footnotes can be made in 3 ways, the most common one is with autonumbering, " "as per reference:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:125 msgid "" "[#]_ is a reference to footnote 1, and [#]_ is a reference to footnote 2." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:128 msgid "This is footnote 1." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:129 msgid "This is footnote 2." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:130 msgid "This is footnote 3." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:132 msgid "[#]_ is a reference to footnote 3." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:134 msgid "Here is a citation reference: [CIT2002]_ ." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:136 msgid "" "This is the citation. It's just like a footnote, except the label is " "textual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:139 msgid "Citation can also be referenced with ```citation `_``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:141 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:145 msgid "Images" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:147 msgid "Use the image directive for images without captions::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:149 msgid "" ".. image:: /images/sample.png\n" " :width: 800\n" " :align: center\n" " :alt: an image." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:154 msgid "And figure directives for images with captions::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:156 msgid "" ".. figure:: /images/sample.png\n" " :figwidth: 800\n" " :align: center\n" " :alt: an image.\n" "\n" " A caption -- notice how the first letter is aligned with the :figwidth: " "option." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:163 msgid "The latter gives:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:170 msgid "" "A caption -- notice how the first letter of the caption in the directive is " "aligned with the :figwidth: option." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:172 msgid "" "Images should go into the ``/images`` folder. By using ``/images`` instead " "of ``images``, sphinx will know the filepath isn't relative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:175 msgid "In-text Markup" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:177 msgid "" "You can make text *emphasized* and **strong** with a single asterisk and " "double respectively::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:179 msgid "" "*emphasize*\n" "**strong**" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:182 msgid "You cannot do both ***emphasized and strong***, so take a pick." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:184 msgid "" "You can :sub:`subscript text` and :sup:`superscript text` by using ``:sub:" "`text``` and ``:sup:`text```" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:186 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:188 msgid "" ":menuselection:`Settings --> Configure Krita`\n" ":guilabel:`File`\n" ":kbd:`Ctrl + Z`\n" ":program:`Krita`" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:193 msgid "" "Avoid randomly bolding words. It does *not* make the text easier or " "friendlier to read." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:196 msgid "Substitution References" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:198 msgid "" "You can create a sort of shorthand for a piece of text or an image by doing::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:200 msgid ".. |shorthand| replace:: something or the other." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:202 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:204 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:206 msgid "" "For links, if you reuse the same link over and over, you can write something " "like the following at the end of the file::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:208 msgid "" ".. _bugzilla: https://bugs.kde.org/\n" ".. _Krita Manual: https://docs.krita.org/" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:211 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:214 msgid "Lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:217 msgid "Ordinated lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:219 msgid "Apple" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:220 msgid "Pear" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:221 msgid "Banana" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:223 msgid "Or..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:225 msgid "Table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:226 msgid "Chair" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:227 msgid "Wardrobe." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:229 msgid "Augustus" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:230 msgid "Nero" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:231 msgid "Caligula" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:232 msgid "Trajan" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:234 msgid "They can be defined as follows::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:236 msgid "" "1. Apple\n" "2. Pear\n" "3. Banana\n" "\n" "#. Apple\n" "#. Pear\n" "#. Banana\n" "\n" "A. Table\n" "B. Chair\n" "C. Wardrobe\n" "\n" "A. Table\n" "#. Chair\n" "#. Wardrobe\n" "\n" "I. Augustus\n" "#. Nero\n" "#. Caligula\n" "#. Trajan" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:258 msgid "Unordered lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:260 msgid "red" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:261 msgid "yellow" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:263 msgid "seagreen" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:264 msgid "verdigris" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:265 msgid "teal" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:266 msgid "viridian" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:268 msgid "dark emerald" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "green" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "emerald" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "light emerald" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:270 msgid "very light emerald." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:271 msgid "blue" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:273 msgid "Defined as such::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:275 msgid "" "- red\n" "- yellow\n" "- green\n" " - seagreen\n" " - verdigris\n" " - teal\n" " - viridian\n" " - emerald\n" " - dark emerald\n" " - light emerald\n" " - very light emerald.\n" "- blue" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:289 msgid "Definition Lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:291 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:293 msgid "Definition" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:294 #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Explanation." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Another option" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:299 msgid "You can make them like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:301 msgid "" "Definition\n" " Explanation.\n" "Another option\n" " Explanation." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:304 msgid "To make them." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:307 msgid "Tables" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Purpose" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Table type" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "listing shortcuts" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "Simple table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "lots of colspans" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "Grid table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "Simple but long" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "List Table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:317 msgid "Done as follows::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:319 msgid "" "================== ============\n" "Purpose Table type\n" "================== ============\n" "listing shortcuts Simple table\n" "lots of colspans Grid table\n" "Simple but long List Table\n" "================== ============\n" "\n" "+-----------------+------------+\n" "|Purpose |Table Type |\n" "+=================+============+\n" "|listing shortcuts|Simple table|\n" "+-----------------+------------+\n" "|lots of colspans |Grid table |\n" "+-----------------+------------+\n" "|Simple but long |List table |\n" "+-----------------+------------+\n" "\n" ".. list-table::\n" " :header-rows: 1\n" "\n" " - * Purpose\n" " * Table Type\n" " - * listing shortcuts\n" " * simple table\n" " - * lots of colspans\n" " * grid table\n" " - * simple but long\n" " * list table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:349 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:352 msgid "Admonishments and asides" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:356 msgid "" "Admonishments are sort of like a separate section that the reader needs to " "pay attention to." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:358 msgid "" "Admonishments that can be used are the following (in order of seriousness):" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:362 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:366 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:370 msgid "Something that is important to note, but is not necessarily negative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:374 msgid "This is in general when something is negative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:378 msgid "" "General attention grabber. Use this when the subject is more important than " "warning, but not as important that is could get a dataloss." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:382 msgid "" "This is for things that could cause dataloss, like forgetting to save, or " "that Python currently has no undo functionality." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:386 msgid "" "This should be for things that are dangerous for the computer in general, " "this includes things that can cause out of memory style freezes." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:390 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:392 msgid "Generic admonition that can have any text" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:394 msgid "Text." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:396 msgid "You can make it like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:398 msgid "" ".. admonition:: Generic admonition that can have any text\n" "\n" " Text." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:404 msgid "Sphinx also adds::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:406 msgid "" ".. seealso::\n" "\n" " Which is useful to collect external links and references." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:414 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:418 msgid "That said, horizontal rulers can be made with ``----``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:421 msgid "The rubric directive" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:422 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:424 msgid ".. rubric:: The rubric directive" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:428 msgid "So, when to use these?" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:429 msgid "" "Only use them when you think the subject is too minor to have a proper " "heading." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:431 msgid "Topic" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:432 msgid "" "When the text is separated from the flow, so it goes into a different " "subject than the text itself is naturally going to." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:433 msgid "Rubric" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:434 msgid "" "When the text isn't separated from the flow, but it does not need a header " "either." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:436 msgid "Admonishments" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:436 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:439 msgid "Code Snippets" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:441 msgid "``Inline code snippets`` are done with ````backticks````." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:443 msgid "" "Multi-line code snippets are done by ending the previous section with ``::" "``, which'll look like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:445 msgid "" "This is a paragraph, and we define a preformated snippet like so::\n" "\n" " Be sure to add a white space and a tab afterwards before starting the " "snippet." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:449 msgid "" "You can also use the ``.. code::`` directive. If you add the language name " "after it, it'll do the appropriate syntax highlighting::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:451 msgid "" ".. code:: python\n" "\n" " # Python comment\n" " def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:459 msgid "Becomes" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:468 msgid "" "# Python comment\n" "def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:469 msgid "some more..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:483 msgid "" "// C++ comment\n" "int myFunction(int i) {\n" " i += 1;\n" "\n" " // Check if more than 12\n" " if (i>12) {\n" " i = 0;\n" " }\n" " return i;\n" "}" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:498 msgid "" "/* CSS comment */\n" "body {\n" " margin: 0 auto;\n" " /* is 800 still sensible? */\n" " max-width:800px;\n" " font-size:16px;\n" " color:#333;\n" " background-color: #eee;\n" " padding:1em;\n" " font-family:serif;\n" " line-height: 1.4;\n" "}" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:502 msgid "" "

this is " "a paragraph.

" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:504 msgid "Other preformatted text" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:507 msgid "One can" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:508 msgid "preformat" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:509 msgid "text by" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:510 msgid "prepending" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:511 msgid "each line" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:512 msgid "with a pipe" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:513 msgid "symbol" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:515 msgid "Like so::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:517 msgid "" "| One can\n" "| preformat\n" "| text by\n" "| prepending\n" "| each line\n" "| with a pipe\n" "| symbol" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:525 msgid "We don't actually use this anywhere in the manual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:528 msgid "Glossaries, Terms and Index" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:530 msgid "These are sphinx features." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:532 msgid "" "Index is used in the top section, right now only single index entries are " "used." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:534 msgid "" "Glossaries are used for some of the menu entry sections, but not all of them." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:537 msgid "Quotes" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:539 msgid "Quotes are done like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:541 msgid "" "I am not sure why you'd need quotes in a user manual...\n" "\n" "-- Wolthera" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:545 msgid "This becomes a blockquote." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:547 msgid "I am not sure why you'd need quotes in a user manual..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:551 msgid "" "We do actually use quotes in some places. Try to add a link to the name to " "define where it came from." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:552 msgid "Wolthera" msgstr "" diff --git a/locale/lt/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po b/locale/lt/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po index 6fe4c1e81..ea1319a49 100644 --- a/locale/lt/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po +++ b/locale/lt/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po @@ -1,1066 +1,1066 @@ # Lithuanian translations for Krita Manual package. # 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. # Automatically generated, 2019. # msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-08 03:08+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: 2019-04-23 03:45+0200\n" "Last-Translator: Automatically generated\n" "Language-Team: lt\n" "Language: lt\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=4; plural=(n==1 ? 0 : n%10>=2 && (n%100<10 || n" "%100>=20) ? 1 : n%10==0 || (n%100>10 && n%100<20) ? 2 : 3);\n" +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_matrix_profile.png" +msgstr "" + +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" +msgstr "" + #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group1.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group2.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group3.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group4.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/dockers/LUT_Management_Docker.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR_1.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR2.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_webcomic.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_print.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_games.svg" msgstr "" -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_matrix_profile.png" -msgstr "" - -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" -msgstr "" - #: ../../general_concepts/colors/color_managed_workflow.rst:1 msgid "How a color managed workflow works." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "Color" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "Color Management" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "ICC Profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "OCIO" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:17 msgid "Color Managed Workflow" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:19 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:22 msgid "Basic Info" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:24 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:26 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:29 msgid "What is the problem?" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:31 msgid "" "To explain the point of color management, you'd first need to learn which " "problem color management tries to solve." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:33 msgid "Let us imagine a kinder garden:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:35 msgid "" "The class of 28 children is subdivided in groups of 7. Each group has its " "own table." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:37 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:40 msgid "The following results come from painting:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:42 msgid "" "Even though all groups had the same assignment, each group's result looks " "different." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:49 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:56 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:64 msgid "" "Group 3 had vermillion red, citron yellow, emerald green and cerulean blue. " "They didn't mix their green, and thus ended up with a purer color." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:71 msgid "" "Finally, group 4 has vermillion red, citron yellow and cerulean blue. Their " "colors probably look like what you imagined." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:73 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!" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:75 msgid "For this purpose, we invented color management." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:78 msgid "What is color management?" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:80 msgid "" "Color management is, dryly put, a set of systems that tries to have the same " "color translate properly between color devices." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:82 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:84 msgid "" "From XYZ it can then be translated back into another device space, such as " "RGB (for screens), or CMYK (for printers)." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:86 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:88 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:90 msgid "Within both we can identify the following color spaces:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:93 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 " "`." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:94 msgid "Device spaces" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:96 msgid "Working spaces" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:97 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:99 msgid "Aesthetic or Look spaces" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:99 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:102 msgid "Color managed workflow" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:104 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:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:110 msgid ".. image:: images/color_category/Krita-colormanaged-workflow_text.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:110 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:112 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:114 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:116 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:118 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:120 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:122 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:124 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:127 msgid "So what does this mean?" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:133 msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_krita_text.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:133 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:135 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*." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:137 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:139 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:141 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:143 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.)" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:148 msgid "ICC profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:150 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:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:153 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:159 msgid "Matrix Shaper profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:159 msgid "" "Matrix shaper profiles have a few parameters that describe the color space " "which are then interpolated between, this requires a lot of maths." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:162 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:168 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:169 msgid "cLUT profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:171 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:174 msgid "Perceptual" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:174 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:177 msgid "Absolute Colorimetric" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:177 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:180 msgid "Relative Colorimetric" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:180 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:183 msgid "Saturation" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:183 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:185 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:188 msgid "LUT docker and HDR imaging" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:196 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:198 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:200 msgid "" "Component, exposure, gamma, whitepoint and blackpoint are knobs which allows " "you to modify the display filter." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:208 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:210 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:212 msgid "" "Black similarly, is brighter on a LCD display than a LED one, and " "incomparable with the black of a carefully sealed room." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:214 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:216 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:224 msgid "" "So, for example, we can choose to scale whiter-than-screen-white to our " "screen-white so we can see the contrasts there." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:226 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:228 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:230 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:232 msgid "" "Another example is to carefully watch the gradients in a certain section." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:234 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:237 msgid "In summary" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:239 msgid "Krita has two modes of color management:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:241 msgid "" "ICC works in terms of spaces relative to the CIEXYZ space, and requires an " "ICC profile." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:242 msgid "OCIO works in terms of interpretation, and makes use of LUTs." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:243 msgid "both can be made with a colorimeter." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:244 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:245 msgid "" "Set up your screen profiles under :menuselection:`Settings --> Configure " "Krita --> Color management`." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:246 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:247 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:249 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:251 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!" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:256 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!" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:260 msgid "" "No amount of color management in the world can make the image on your screen " "and the image out of the printer have 100% the same color." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:263 msgid "Exporting" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:265 msgid "" "When you have finished your image and are ready to export it, you can modify " "the color space to optimize it:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:267 msgid "If you are preparing an image for the web:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:269 msgid "" "If you use 16bit color depth or higher, convert the image to 8bit color " "depth. This will make the image much smaller." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:271 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:273 msgid "If it's a gray-scale image, convert it to gray-scale." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:274 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:279 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 " "`_, save your PNG, JPG or TIFF without an embedded profile to work " "around this." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:281 msgid "If you are preparing for print:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:283 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:284 msgid "" "Check with the printer what kind of image they expect. Maybe they expect " "sRGB color space, or perhaps they have their own profile." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:287 msgid "Interaction with other applications" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:290 msgid "Blender" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:292 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:294 msgid "" "Blender's OCIO config is under ``/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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:298 msgid "Windows Photo Viewer" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:300 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:303 msgid "Example workflows" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:305 msgid "" "Here are some example workflows to get a feeling of how your color " "management workflow may look like." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:307 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'." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:310 msgid "Webcomic" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:317 #: ../../general_concepts/colors/color_managed_workflow.rst:339 #: ../../general_concepts/colors/color_managed_workflow.rst:357 msgid "Input" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:318 #: ../../general_concepts/colors/color_managed_workflow.rst:340 #: ../../general_concepts/colors/color_managed_workflow.rst:358 msgid "Your screen profile. (You pick colors via your screen)" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:319 #: ../../general_concepts/colors/color_managed_workflow.rst:341 #: ../../general_concepts/colors/color_managed_workflow.rst:359 msgid "Workingspace" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:320 msgid "" "sRGB (the default screen profile) or any larger profile if you can spare the " "bit depth and like working in them." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:322 #: ../../general_concepts/colors/color_managed_workflow.rst:344 #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "Output" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:322 msgid "" "sRGB, ICC version 2, sRGB TRC for the internet, and a specialized CMYK " "profile from the printing house for the printed images." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:324 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:326 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:328 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:330 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:333 msgid "Print" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:342 msgid "sRGB or Rec. 2020 if you can afford the bit-depth being 16bit." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:344 msgid "" "Specialized CMYK profile from the printing house for the printed images." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:346 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:348 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:351 msgid "Games" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:360 msgid "sRGB or grayscale linear for roughness and specular maps." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "" "This one is tricky, but in the end it'll be sRGB for the regular player." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:364 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:366 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:368 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:370 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)." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:374 msgid "" "`Visualizing the XYZ color space `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:375 msgid "" "`Basics of gamma correction `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:376 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 `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:377 msgid "" "`2D examples of the effect of gamma-encoding on color maths `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:378 msgid "" "`Basic overview of color management from ArgyllCMS manual `_." msgstr "" diff --git a/locale/nl/LC_MESSAGES/contributors_manual/krita_manual_conventions.po b/locale/nl/LC_MESSAGES/contributors_manual/krita_manual_conventions.po index f9c70706d..3eaf3f2c7 100644 --- a/locale/nl/LC_MESSAGES/contributors_manual/krita_manual_conventions.po +++ b/locale/nl/LC_MESSAGES/contributors_manual/krita_manual_conventions.po @@ -1,1159 +1,1159 @@ # Dutch translations for Krita Manual package # Nederlandse vertalingen voor het pakket Krita Manual. # 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. # # Automatically generated, 2019. # Freek de Kruijf , 2019. msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-09 03:27+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: 2019-06-25 16:29+0200\n" "Last-Translator: Freek de Kruijf \n" "Language-Team: Dutch \n" "Language: nl\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" "X-Generator: Lokalize 19.04.2\n" #: ../../:2 msgid "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: mouseleft" msgstr "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: muislinks" #: ../../:4 msgid "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: mouseright" msgstr "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: muis rechts" #: ../../:6 msgid "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: mousemiddle" msgstr "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: muis midden" #: ../../:8 msgid "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" msgstr "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" +#: ../../contributors_manual/krita_manual_conventions.rst:None +msgid "Horizontal Rulers" +msgstr "Horizontale linialen" + #: ../../contributors_manual/krita_manual_conventions.rst:0 msgid "" ".. image:: images/sample.png\n" " :alt: an image." msgstr "" ".. image:: images/sample.png\n" " :alt: een afbeelding." -#: ../../contributors_manual/krita_manual_conventions.rst:None -msgid "Horizontal Rulers" -msgstr "Horizontale linialen" - #: ../../contributors_manual/krita_manual_conventions.rst:1 msgid "reStructuredText conventions for the Krita Manual" msgstr "reStructuredText conventies voor de Krita handleiding" #: ../../contributors_manual/krita_manual_conventions.rst:16 msgid "Mark-up conventions for the Krita Manual" msgstr "Mark-up conventies voor de Krita handleiding" #: ../../contributors_manual/krita_manual_conventions.rst:18 msgid "" "This details the style conventions for using restructured text for the Krita " "Manual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:20 msgid "" "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):" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:23 msgid "" "`Primer `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "User Manual:" msgstr "Gebruikershandleiding:" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "" "`Quick Ref `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:25 msgid "" "`Text Cheatsheet `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:27 msgid "" "`Introduction `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:28 msgid "" "`Markup `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "Reference Documentation:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "" "`Directives `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:30 msgid "`Roles `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "Sphinx specific docs:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "" "`Sphinx' page on restructured text `_ -- This is useful for the specific " "sphinx directives and roles it uses to generate for example table of " "contents." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:34 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:36 msgid "Contents" msgstr "Inhoud" #: ../../contributors_manual/krita_manual_conventions.rst:39 msgid "Meta data" msgstr "Metagegevens" #: ../../contributors_manual/krita_manual_conventions.rst:41 msgid "Each page should start with the following three things:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:44 msgid "" "This is a general description of the page. It will be converted to an html " "meta tag which will be used by search engines::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:46 msgid "" ".. meta::\n" " :description:\n" " Description." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:49 msgid "A meta description" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:52 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:54 msgid "" ".. metadata-placeholder\n" "\n" " :authors: - Author 1\n" " - Author 2\n" " :license: GNU free documentation license 1.3 or later." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:58 msgid "A list of authors and a license." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:61 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid "Indexing terms." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid ".. index:: Keyword, Keyword with Spaces, ! Main Definition Keyword" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:66 msgid "" "This is so we can easily link to the page using ``:ref:`label_name```. Try " "to make this a nice variable name::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:68 msgid ".. _label_name:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:70 msgid "" "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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:71 msgid "A label." msgstr "Een label." #: ../../contributors_manual/krita_manual_conventions.rst:74 msgid "Headings" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:76 msgid "Headings will be done in the following order::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:78 msgid "" "############\n" "Part/Section\n" "############\n" "\n" "For pages that have a lot of subpages.\n" "\n" "=========\n" "Heading 1\n" "=========\n" "\n" "Start most manual pages with this.\n" "\n" "Heading 2\n" "---------\n" "\n" "Heading 3\n" "~~~~~~~~~\n" "\n" "Heading 4\n" "^^^^^^^^^\n" "\n" "Heading 5\n" "'''''''''\n" "\n" "Heading 6\n" "\"\"\"\"\"\"\"\"\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:105 msgid "" "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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:107 msgid "" "Sometimes you need to link to a subsection of a page, add a label above the " "heading in that case." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:109 msgid "" "Headers should not end with punctuation, as the header will be used as the " "link name when linking to a label." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:112 msgid "Linking" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:114 msgid "" "Linking is done with ``:ref:`label_name```. When you need an alternative " "link text, you use ``:ref:`actual text shown ```." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:116 msgid "" "Linking to external pages is done with ```url`_`` and ```link name " "`_``, which'll become `link name `_." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:118 msgid "" "`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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:121 msgid "Footnotes and further reading" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:123 msgid "" "Footnotes can be made in 3 ways, the most common one is with autonumbering, " "as per reference:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:125 msgid "" "[#]_ is a reference to footnote 1, and [#]_ is a reference to footnote 2." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:128 msgid "This is footnote 1." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:129 msgid "This is footnote 2." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:130 msgid "This is footnote 3." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:132 msgid "[#]_ is a reference to footnote 3." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:134 msgid "Here is a citation reference: [CIT2002]_ ." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:136 msgid "" "This is the citation. It's just like a footnote, except the label is " "textual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:139 msgid "Citation can also be referenced with ```citation `_``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:141 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:145 msgid "Images" msgstr "Afbeeldingen" #: ../../contributors_manual/krita_manual_conventions.rst:147 msgid "Use the image directive for images without captions::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:149 msgid "" ".. image:: /images/sample.png\n" " :width: 800\n" " :align: center\n" " :alt: an image." msgstr "" ".. image:: /images/sample.png\n" " :width: 800\n" " :align: center\n" " :alt: een afbeelding." #: ../../contributors_manual/krita_manual_conventions.rst:154 msgid "And figure directives for images with captions::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:156 msgid "" ".. figure:: /images/sample.png\n" " :figwidth: 800\n" " :align: center\n" " :alt: an image.\n" "\n" " A caption -- notice how the first letter is aligned with the :figwidth: " "option." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:163 msgid "The latter gives:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:170 msgid "" "A caption -- notice how the first letter of the caption in the directive is " "aligned with the :figwidth: option." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:172 msgid "" "Images should go into the ``/images`` folder. By using ``/images`` instead " "of ``images``, sphinx will know the filepath isn't relative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:175 msgid "In-text Markup" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:177 msgid "" "You can make text *emphasized* and **strong** with a single asterisk and " "double respectively::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:179 msgid "" "*emphasize*\n" "**strong**" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:182 msgid "You cannot do both ***emphasized and strong***, so take a pick." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:184 msgid "" "You can :sub:`subscript text` and :sup:`superscript text` by using ``:sub:" "`text``` and ``:sup:`text```" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:186 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:188 msgid "" ":menuselection:`Settings --> Configure Krita`\n" ":guilabel:`File`\n" ":kbd:`Ctrl + Z`\n" ":program:`Krita`" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:193 msgid "" "Avoid randomly bolding words. It does *not* make the text easier or " "friendlier to read." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:196 msgid "Substitution References" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:198 msgid "" "You can create a sort of shorthand for a piece of text or an image by doing::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:200 msgid ".. |shorthand| replace:: something or the other." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:202 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:204 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:206 msgid "" "For links, if you reuse the same link over and over, you can write something " "like the following at the end of the file::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:208 msgid "" ".. _bugzilla: https://bugs.kde.org/\n" ".. _Krita Manual: https://docs.krita.org/" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:211 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:214 msgid "Lists" msgstr "Lijsten" #: ../../contributors_manual/krita_manual_conventions.rst:217 msgid "Ordinated lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:219 msgid "Apple" msgstr "Appel" #: ../../contributors_manual/krita_manual_conventions.rst:220 msgid "Pear" msgstr "Peer" #: ../../contributors_manual/krita_manual_conventions.rst:221 msgid "Banana" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:223 msgid "Or..." msgstr "Of..." #: ../../contributors_manual/krita_manual_conventions.rst:225 msgid "Table" msgstr "Tabel" #: ../../contributors_manual/krita_manual_conventions.rst:226 msgid "Chair" msgstr "Voorzitter" #: ../../contributors_manual/krita_manual_conventions.rst:227 msgid "Wardrobe." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:229 msgid "Augustus" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:230 msgid "Nero" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:231 msgid "Caligula" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:232 msgid "Trajan" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:234 msgid "They can be defined as follows::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:236 msgid "" "1. Apple\n" "2. Pear\n" "3. Banana\n" "\n" "#. Apple\n" "#. Pear\n" "#. Banana\n" "\n" "A. Table\n" "B. Chair\n" "C. Wardrobe\n" "\n" "A. Table\n" "#. Chair\n" "#. Wardrobe\n" "\n" "I. Augustus\n" "#. Nero\n" "#. Caligula\n" "#. Trajan" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:258 msgid "Unordered lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:260 msgid "red" msgstr "rood" #: ../../contributors_manual/krita_manual_conventions.rst:261 msgid "yellow" msgstr "geel" #: ../../contributors_manual/krita_manual_conventions.rst:263 msgid "seagreen" msgstr "zeegroen" #: ../../contributors_manual/krita_manual_conventions.rst:264 msgid "verdigris" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:265 msgid "teal" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:266 msgid "viridian" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:268 msgid "dark emerald" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "green" msgstr "groen" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "emerald" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "light emerald" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:270 msgid "very light emerald." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:271 msgid "blue" msgstr "blauw" #: ../../contributors_manual/krita_manual_conventions.rst:273 msgid "Defined as such::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:275 msgid "" "- red\n" "- yellow\n" "- green\n" " - seagreen\n" " - verdigris\n" " - teal\n" " - viridian\n" " - emerald\n" " - dark emerald\n" " - light emerald\n" " - very light emerald.\n" "- blue" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:289 msgid "Definition Lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:291 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:293 msgid "Definition" msgstr "Definitie" #: ../../contributors_manual/krita_manual_conventions.rst:294 #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Explanation." msgstr "Uitleg." #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Another option" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:299 msgid "You can make them like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:301 msgid "" "Definition\n" " Explanation.\n" "Another option\n" " Explanation." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:304 msgid "To make them." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:307 msgid "Tables" msgstr "Tabellen" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Purpose" msgstr "Omschrijving" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Table type" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "listing shortcuts" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "Simple table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "lots of colspans" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "Grid table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "Simple but long" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "List Table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:317 msgid "Done as follows::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:319 msgid "" "================== ============\n" "Purpose Table type\n" "================== ============\n" "listing shortcuts Simple table\n" "lots of colspans Grid table\n" "Simple but long List Table\n" "================== ============\n" "\n" "+-----------------+------------+\n" "|Purpose |Table Type |\n" "+=================+============+\n" "|listing shortcuts|Simple table|\n" "+-----------------+------------+\n" "|lots of colspans |Grid table |\n" "+-----------------+------------+\n" "|Simple but long |List table |\n" "+-----------------+------------+\n" "\n" ".. list-table::\n" " :header-rows: 1\n" "\n" " - * Purpose\n" " * Table Type\n" " - * listing shortcuts\n" " * simple table\n" " - * lots of colspans\n" " * grid table\n" " - * simple but long\n" " * list table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:349 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:352 msgid "Admonishments and asides" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:356 msgid "" "Admonishments are sort of like a separate section that the reader needs to " "pay attention to." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:358 msgid "" "Admonishments that can be used are the following (in order of seriousness):" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:362 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:366 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:370 msgid "Something that is important to note, but is not necessarily negative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:374 msgid "This is in general when something is negative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:378 msgid "" "General attention grabber. Use this when the subject is more important than " "warning, but not as important that is could get a dataloss." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:382 msgid "" "This is for things that could cause dataloss, like forgetting to save, or " "that Python currently has no undo functionality." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:386 msgid "" "This should be for things that are dangerous for the computer in general, " "this includes things that can cause out of memory style freezes." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:390 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:392 msgid "Generic admonition that can have any text" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:394 msgid "Text." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:396 msgid "You can make it like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:398 msgid "" ".. admonition:: Generic admonition that can have any text\n" "\n" " Text." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:404 msgid "Sphinx also adds::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:406 msgid "" ".. seealso::\n" "\n" " Which is useful to collect external links and references." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:414 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:418 msgid "That said, horizontal rulers can be made with ``----``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:421 msgid "The rubric directive" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:422 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:424 msgid ".. rubric:: The rubric directive" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:428 msgid "So, when to use these?" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:429 msgid "" "Only use them when you think the subject is too minor to have a proper " "heading." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:431 msgid "Topic" msgstr "Onderwerp" #: ../../contributors_manual/krita_manual_conventions.rst:432 msgid "" "When the text is separated from the flow, so it goes into a different " "subject than the text itself is naturally going to." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:433 msgid "Rubric" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:434 msgid "" "When the text isn't separated from the flow, but it does not need a header " "either." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:436 msgid "Admonishments" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:436 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:439 msgid "Code Snippets" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:441 msgid "``Inline code snippets`` are done with ````backticks````." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:443 msgid "" "Multi-line code snippets are done by ending the previous section with ``::" "``, which'll look like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:445 msgid "" "This is a paragraph, and we define a preformated snippet like so::\n" "\n" " Be sure to add a white space and a tab afterwards before starting the " "snippet." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:449 msgid "" "You can also use the ``.. code::`` directive. If you add the language name " "after it, it'll do the appropriate syntax highlighting::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:451 msgid "" ".. code:: python\n" "\n" " # Python comment\n" " def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:459 msgid "Becomes" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:468 msgid "" "# Python comment\n" "def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:469 msgid "some more..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:483 msgid "" "// C++ comment\n" "int myFunction(int i) {\n" " i += 1;\n" "\n" " // Check if more than 12\n" " if (i>12) {\n" " i = 0;\n" " }\n" " return i;\n" "}" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:498 msgid "" "/* CSS comment */\n" "body {\n" " margin: 0 auto;\n" " /* is 800 still sensible? */\n" " max-width:800px;\n" " font-size:16px;\n" " color:#333;\n" " background-color: #eee;\n" " padding:1em;\n" " font-family:serif;\n" " line-height: 1.4;\n" "}" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:502 msgid "" "

this is " "a paragraph.

" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:504 msgid "Other preformatted text" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:507 msgid "One can" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:508 msgid "preformat" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:509 msgid "text by" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:510 msgid "prepending" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:511 msgid "each line" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:512 msgid "with a pipe" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:513 msgid "symbol" msgstr "symbool" #: ../../contributors_manual/krita_manual_conventions.rst:515 msgid "Like so::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:517 msgid "" "| One can\n" "| preformat\n" "| text by\n" "| prepending\n" "| each line\n" "| with a pipe\n" "| symbol" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:525 msgid "We don't actually use this anywhere in the manual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:528 msgid "Glossaries, Terms and Index" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:530 msgid "These are sphinx features." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:532 msgid "" "Index is used in the top section, right now only single index entries are " "used." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:534 msgid "" "Glossaries are used for some of the menu entry sections, but not all of them." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:537 msgid "Quotes" msgstr "Aanhalingstekens" #: ../../contributors_manual/krita_manual_conventions.rst:539 msgid "Quotes are done like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:541 msgid "" "I am not sure why you'd need quotes in a user manual...\n" "\n" "-- Wolthera" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:545 msgid "This becomes a blockquote." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:547 msgid "I am not sure why you'd need quotes in a user manual..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:551 msgid "" "We do actually use quotes in some places. Try to add a link to the name to " "define where it came from." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:552 msgid "Wolthera" msgstr "" #~ msgid "explanation." #~ msgstr "uitleg." diff --git a/locale/nl/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po b/locale/nl/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po index 704295763..c11ee92fc 100644 --- a/locale/nl/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po +++ b/locale/nl/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po @@ -1,1500 +1,1500 @@ # Dutch translations for Krita Manual package # Nederlandse vertalingen voor het pakket Krita Manual. # 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. # # Automatically generated, 2019. # Freek de Kruijf , 2019. # Lo Fernchu , 2019. msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-08 03:08+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: 2019-08-02 12:21+0200\n" "Last-Translator: Freek de Kruijf \n" "Language-Team: Dutch \n" "Language: nl\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" "X-Generator: Lokalize 19.04.3\n" +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_matrix_profile.png" +msgstr ".. image:: images/color_category/Kiki_matrix_profile.png" + +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" +msgstr ".. image:: images/color_category/Kiki_cLUTprofiles.png" + #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group1.png" msgstr ".. image:: images/color_category/Krita_2_9_colormanagement_group1.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group2.png" msgstr ".. image:: images/color_category/Krita_2_9_colormanagement_group2.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group3.png" msgstr ".. image:: images/color_category/Krita_2_9_colormanagement_group3.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group4.png" msgstr ".. image:: images/color_category/Krita_2_9_colormanagement_group4.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/dockers/LUT_Management_Docker.png" msgstr ".. image:: images/dockers/LUT_Management_Docker.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR_1.svg" msgstr ".. image:: images/color_category/Krita_HDR_1.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR2.svg" msgstr ".. image:: images/color_category/Krita_HDR2.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_webcomic.svg" msgstr "" ".. image:: images/color_category/Krita-colormanaged-workflow_webcomic.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_print.svg" msgstr ".. image:: images/color_category/Krita-colormanaged-workflow_print.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_games.svg" msgstr ".. image:: images/color_category/Krita-colormanaged-workflow_games.svg" -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_matrix_profile.png" -msgstr ".. image:: images/color_category/Kiki_matrix_profile.png" - -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" -msgstr ".. image:: images/color_category/Kiki_cLUTprofiles.png" - #: ../../general_concepts/colors/color_managed_workflow.rst:1 msgid "How a color managed workflow works." msgstr "Hoe de workflow voor kleurbeheer werkt." #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "Color" msgstr "Kleur" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "Color Management" msgstr "Kleurenbeheer" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "ICC Profiles" msgstr "ICC-profielen" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "OCIO" msgstr "OCIO" #: ../../general_concepts/colors/color_managed_workflow.rst:17 msgid "Color Managed Workflow" msgstr "Workflow kleurbeheer" #: ../../general_concepts/colors/color_managed_workflow.rst:19 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." msgstr "" "U heeft misschien gehoord dat Krita iets heeft wat ze kleurbeheer noemen. Of " "vroeg u zichzelf af wat al die 'kleurmodel' en 'kleurprofiel' dingen zijn " "die u tegenkomt in de menus. Voor mensen die professioneel met digitale " "afbeeldingen werken is kleurbeheer erg handig, en hopelijk legt deze pagina " "uit waarom." #: ../../general_concepts/colors/color_managed_workflow.rst:22 msgid "Basic Info" msgstr "Basisinformatie" #: ../../general_concepts/colors/color_managed_workflow.rst:24 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." msgstr "" "Als u nog nooit eerder met kleurbeheer heeft gewerkt, en u heeft geen idee " "wat het is, dan heeft u waarschijnlijk in de 8bit RGB kleurruimte met het " "sRGB profiel gewerkt. Dit houd in dat u kan kiezen voor de *ingebouwde sRGB* " "of de *sRGB-elle-v2-srgbtrc.icc*. In de nieuwe kleurruimte-browser is dit " "profiel gemaskeerd met *(default)* als u 8 bit gebruikt." #: ../../general_concepts/colors/color_managed_workflow.rst:26 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." msgstr "" "We zullen later kijken wat deze termen in theorie betekenen, maar als u hier " "alleen maar bent om erachter te komen wat welke de standaardinstelling is, " "dan weet u dan nu. Misschien, wilt u na het lezen van dit de " "standaardinstelling wijzigen, om nieuwe en interessante resultaten uit de " "filters, mengmodus, of allen maar van de kleur uitsmeer-kwast te krijgen." #: ../../general_concepts/colors/color_managed_workflow.rst:29 msgid "What is the problem?" msgstr "Wat is het probleem?" #: ../../general_concepts/colors/color_managed_workflow.rst:31 msgid "" "To explain the point of color management, you'd first need to learn which " "problem color management tries to solve." msgstr "" "Om het idee van kleurbeheer uit te leggen, moet u eerst weten welk probleem " "kleurbeheer probeert op te lossen." #: ../../general_concepts/colors/color_managed_workflow.rst:33 msgid "Let us imagine a kinder garden:" msgstr "Stelt u zich een kleuterschool voor:" #: ../../general_concepts/colors/color_managed_workflow.rst:35 msgid "" "The class of 28 children is subdivided in groups of 7. Each group has its " "own table." msgstr "" "De klas met 28 kinderen is verdeelt in groepjes van 7. Elke groep heeft zijn " "eigen tafel." #: ../../general_concepts/colors/color_managed_workflow.rst:37 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." msgstr "" "De leraar geeft ze een schilder-opdracht: ze moeten een rode driehoek, een " "blauw vierkant, een groene cirkel met om alles een gele rand schilderen. De " "kinderen hebben al veel geschilderd, dus de leraar kan de slimmere kleuters " "zelf laten schilderen zodat hij de andere meer hulp kan geven." #: ../../general_concepts/colors/color_managed_workflow.rst:40 msgid "The following results come from painting:" msgstr "Ze schilderen de volgende resultaten:" #: ../../general_concepts/colors/color_managed_workflow.rst:42 msgid "" "Even though all groups had the same assignment, each group's result looks " "different." msgstr "" "Alhoewel elke groep dezelfde opdracht heeft, is het resultaat van elke groep " "toch verschillend." #: ../../general_concepts/colors/color_managed_workflow.rst:49 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." msgstr "" "Groep 1 had scharlaken rood, citroen geel en ultramarijn blauw om mee te " "schilderen. Dit zorgde ervoor dat hun driehoek prettig rood uitzag, maar hun " "groene cirkel zag er modderig uit. Dit kwam omdat ultramarijn te donker is " "om mooi groen mee te maken." #: ../../general_concepts/colors/color_managed_workflow.rst:56 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." msgstr "" "Groep 2 had magenta rood, citroen geel en hemels blauw. Magenta is een soort " "rood dat meer roze is, in tegenstelling tot scharlaken rood, wat meer oranje " "is. Maar, hun groen is mooier omdat hemels blauw een veel lichter blauw is." #: ../../general_concepts/colors/color_managed_workflow.rst:64 msgid "" "Group 3 had vermillion red, citron yellow, emerald green and cerulean blue. " "They didn't mix their green, and thus ended up with a purer color." msgstr "" "Groep 3 had scharlaken rood, citroen geel, smaragdgroen en hemels blauw. Zij " "mengde hun groen niet en eindigde dus met een pure kleur." #: ../../general_concepts/colors/color_managed_workflow.rst:71 msgid "" "Finally, group 4 has vermillion red, citron yellow and cerulean blue. Their " "colors probably look like what you imagined." msgstr "" "En tenslotte had groep 4 scharlaken rood, citroen geel en hemels blauw. Hun " "kleuren lijken waarschijnlijk het meest op wat u in gedachten had." #: ../../general_concepts/colors/color_managed_workflow.rst:73 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!" msgstr "" "Nu is dit een kleuterklas, dus is dit geen groot probleem. Maar stelt u zich " "voor dat dit gebeurt in een drukkerij? Stelt u zich voor dat vier printers " "hetzelfde tijdschrift drukken met sterk verschillende resultaten? Dat zou " "een ramp zijn!" #: ../../general_concepts/colors/color_managed_workflow.rst:75 msgid "For this purpose, we invented color management." msgstr "hiervoor hebben we kleurbeheer bedacht." #: ../../general_concepts/colors/color_managed_workflow.rst:78 msgid "What is color management?" msgstr "Wat is kleurenbeheer?" #: ../../general_concepts/colors/color_managed_workflow.rst:80 msgid "" "Color management is, dryly put, a set of systems that tries to have the same " "color translate properly between color devices." msgstr "" "Kleurbeheer is eenvoudig gezegd een verzameling systemen dat probeert " "dezelfde kleur te vertalen tussen kleur-weergaven." #: ../../general_concepts/colors/color_managed_workflow.rst:82 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." msgstr "" "Dit gebeurt meestal door te proberen een kleur een plaats in het " "referentiekleurruimte XYZ te plaatsen. XYZ is een coördinatiesysteem dat " "voor alle kleuren dat het menselijke oog kan zien een plekje heeft." #: ../../general_concepts/colors/color_managed_workflow.rst:84 msgid "" "From XYZ it can then be translated back into another device space, such as " "RGB (for screens), or CMYK (for printers)." msgstr "" "Van XYZ kan het terugvertaald worden naar een ander apparaatruimte, zoals " "RGB (voor schermen), of CMYK (voor printers)." #: ../../general_concepts/colors/color_managed_workflow.rst:86 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." msgstr "" "Krita heeft twee systemen speciaal voor kleurenbeheer. Aan de ene kant " "hebben we **lcms2**, die voor ICC profielen is, en aan de andere kant hebben " "we **OCIO**, die voor LUT kleurenbeheer is." #: ../../general_concepts/colors/color_managed_workflow.rst:88 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." msgstr "" "Om een ruwe indruk te geven, ICC profielen zorgen ervoor dat kleuren " "consistent blijven bij de vele omzettingen naar apparaten (schermen, " "printers) door een referentie ruimte te gebruiken, en OCIO zorgt voor de " "omzettingen van de genoemde kleuren." #: ../../general_concepts/colors/color_managed_workflow.rst:90 msgid "Within both we can identify the following color spaces:" msgstr "In beide kunnen we de volgende kleurruimtes vinden:" #: ../../general_concepts/colors/color_managed_workflow.rst:93 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 " "`." msgstr "" "Apparaatruimten zijn dat wat uw monitor beschrijft, en moet gemaakt worden " "met een klein apparaatje genaamd \"colorimeter\". Dit apparaat, in " "combinatie met de juiste software, meet de sterkste rood, groen en blauw dat " "uw scherm kan produceren, maar ook het geproduceerde wit, zwart en grijs. " "Met deze en verschillende andere metingen creëert het een ICC profiel uniek " "voor uw scherm. U kan deze in Krita's kleurbeheer tab bekijken. We nemen " "standaard sRGB aan voor schermen, maar het is waarschijnlijker dat uw scherm " "niet precies met sRGB overeenkomt, met name als u een duur scherm heeft, dat " "het een groter bereik kan hebben. U moet vanwege de apparaatruimten eerst de " "gegevens van uw printer controleren voor welk profiel het verwacht. Veel " "printerfabrikanten hebben hun eigen profielen voor hun printers, of willen " "de kleur-conversie liever zelf doen. U kunt :ref:`hier " "` meer over de colorimeter lezen." #: ../../general_concepts/colors/color_managed_workflow.rst:94 msgid "Device spaces" msgstr "Apparaatruimten" #: ../../general_concepts/colors/color_managed_workflow.rst:96 msgid "Working spaces" msgstr "Werkruimten" #: ../../general_concepts/colors/color_managed_workflow.rst:97 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." msgstr "" "Voor ICC worden ze meegeleverd met Krita, en voor de OCIO kunt u ze " "downloaden van de OCIO website. Werkruimten zijn met name handig bij kleur-" "bewerkingen, wat programma's zoals Krita vaak uitvoeren. Wij raden daarom " "aan om voor uw afbeelding een werkend ruimteprofiel te hebben." #: ../../general_concepts/colors/color_managed_workflow.rst:99 msgid "Aesthetic or Look spaces" msgstr "Aesthetic of Look ruimtes" #: ../../general_concepts/colors/color_managed_workflow.rst:99 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." msgstr "" "Dit zijn speciale plekken waar de afbeelding is verandert om de afbeelding " "een specifiek uiterlijk te geven. Bij Krita worden geen Look profielen voor " "ICC meegeleverd, en het kan ook niet met Look spaces voor OCIO werken." #: ../../general_concepts/colors/color_managed_workflow.rst:102 msgid "Color managed workflow" msgstr "Workflow kleurbeheer" #: ../../general_concepts/colors/color_managed_workflow.rst:104 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:" msgstr "" "Als u van deze ruimten af weet dan heeft u nog geen idee hoe u ze moet " "gebruiken, maar het maakt het wel makkelijker om het uit te leggen hoe u ze " "moet gebruiken. Laten we daarom eens kijken hoe een vaak voorkomende " "workflow van kleurbeheer verloopt:" #: ../../general_concepts/colors/color_managed_workflow.rst:110 msgid ".. image:: images/color_category/Krita-colormanaged-workflow_text.svg" msgstr ".. image:: images/color_category/Krita-colormanaged-workflow_text.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:110 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." msgstr "" "Een gewoon voorbeeld van een workflow voor kleurbeheer. We hebben invoer van " "scanners en cameras, wat we omzetten naar een werkruimte dat we afwisselend " "kunnen gebruiken tussen meerdere bewerkingssoftware, en dat is omgezet naar " "een uitvoerruimte om dit op het scherm te kunnen bekijken of te kunnen " "printen." #: ../../general_concepts/colors/color_managed_workflow.rst:112 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." msgstr "" "In een traditionele workflow voor kleurbeheer, denken we meestal in termen " "over echte kleuren die worden omgezet naar computer kleuren en omgezet. " "Bijvoorbeeld foto's van een camera of gescande afbeeldingen. Als u een " "apparaatruimte van een dergelijk apparaat heeft, dan koppelen we eerst de " "apparaatruimte aan de afbeelding, en zetten het dan om naar een werkruimte." #: ../../general_concepts/colors/color_managed_workflow.rst:114 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." msgstr "" "We voeren vervolgens al onze bewerkingen uit in de werkruimte, en gebruiken " "de werkruimte voor de communicatie tussen de bewerkingssoftware. In het " "geval van Krita, omdat we twee kleurbeheer systemen hebben, gebruiken we ICC " "profielen tussen programma's zoals Gimp 2.9+, Inkscape, digiKam en Scribus, " "en OCIO configuratie tussen Blender en Natron." #: ../../general_concepts/colors/color_managed_workflow.rst:116 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." msgstr "" "U slaat ook u werk-bestanden op in de werkruimte, net zoals hoe u de niet " "samengevoegde lagen in het werk-bestand opslaat, of ze op een zeer hoge " "resolutie heeft." #: ../../general_concepts/colors/color_managed_workflow.rst:118 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." msgstr "" "Soms passen we aesthetic of 'look' ruimtes toe bij een afbeelding als " "onderdeel van het bewerkingsproces. Dit is nogal geavanceerd, en " "waarschijnlijk niet iets waarover u zich zorgen moet maken bij het gebruik " "van Krita." #: ../../general_concepts/colors/color_managed_workflow.rst:120 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." msgstr "" "En als we dan klaar zijn met bewerken, proberen we het om te zetten naar een " "uitvoerruimte, wat een andere apparaatruimte is. Dit kan CMYK zijn voor " "printers of een speciaal RGB profiel voor een beeldscherm. Als u met " "professionele drukkerijen werkt, dan kunt u hierover het beste aan hun " "vragen. Zij hebben meestal veel ervaring met hoe u het beste kunt " "converteren, en geven er misschien de voorkeur aan dat ze zelf de omzetting " "doen van uw werkruimte naar de apparaatruimte van hun printers." #: ../../general_concepts/colors/color_managed_workflow.rst:122 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." msgstr "" "Een andere form van uitvoer is de manier waarop uw beeldscherm de kleur laat " "zien. in tegenstelling tot normale uitvoer, gebeurt dit voortdurend tijdens " "het bewerken: tenslotte moet u kunnen zien wat u doet, maar uw scherm is nog " "steeds een apparaat met een apparaatruimte, het vervormt hoe de afbeelding " "eruit ziet. Op deze manier bekeken, kunt u uw scherm zien als een " "verrekijker waar u door moet kijken om uw afbeelding te kunnen zien." #: ../../general_concepts/colors/color_managed_workflow.rst:124 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." msgstr "" "Daarom, zal u zonder een gekalibreerd beeldscherm, eigenlijk niet kunnen " "weten wat de eigenlijke kleuren zijn die u bewerkt, omdat de computer de " "relevante eigenschappen van uw beeldscherm niet kent. Als u voor uw " "beeldscherm een profiel heeft gemaakt, moet u in de instellingen van Krita " "het profiel geven, en de sRGB selecteren om in te tekenen, dan zal u voor " "het eerst de eigenlijke kleuren van de sRGB kunnen zien." #: ../../general_concepts/colors/color_managed_workflow.rst:127 msgid "So what does this mean?" msgstr "Wat houd dit in?" #: ../../general_concepts/colors/color_managed_workflow.rst:133 msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_krita_text.svg" msgstr "" ".. image:: images/color_category/Krita-colormanaged-workflow_krita_text.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:133 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." msgstr "" "Als we in een leeg vlak gaan schilderen, dan kunnen we ons scherm-profiel " "als invoer-ruimte zien, omdat we het gebruiken om te bepalen welke kleuren " "we selecteren. Dit vereenvoudigt de workflow enigszins, maar maakt het " "scherm-profiel en kijk-condities belangrijker." #: ../../general_concepts/colors/color_managed_workflow.rst:135 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*." msgstr "" "Welnu, fotografen en mensen die het lastige vak van VFX genaamd " "'kleurbepaling' doen gaan helemaal door het dak als ze proberen om de " "kleuren 100% correct te krijgen, en nemen zelfs factoren in overweging zoals " "het moment van de dag en in welke kleur de muren geschilderd zijn. " "Bijvoorbeeld, als de muur achter uw computer helemaal rood is, dan zal uw " "ogen zich aanpassen zodat ze minder gevoelig voor rood zijn, wat betekent " "dat de kleuren die ze in het programma selecteren roder zullen zijn. We " "noemen dat de *kijk-condities*." #: ../../general_concepts/colors/color_managed_workflow.rst:137 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." msgstr "" "Gelukkig hoeven artiesten zich minder zorgen daarover te maken. Omdat " "illustraties volledig handgemaakt zijn, kunnen we de belangrijke stukken " "identificeren en de juiste contrast tussen de kleuren instellen. Dit " "betekent dat zelfs als uw afbeeldingen een beetje roder zijn dan bedoeld, " "het minder waarschijnlijk is dat de hele afbeelding mislukt is. Als we nog " "een keertje naar het kleuterschool-voorbeeld van hierboven kijken, dan " "begrijpen we nog steeds hoe de afbeelding eruit had moeten zien, ondanks dat " "er op elke afbeelding andere kleuren gebruikt zijn. Bovendien, omdat de " "kleuren in de illustraties speciaal gekozen zijn, kunnen we ze op een later " "moment makkelijker corrigeren. Maar tegelijkertijd, is dit natuurlijk " "vervelend om te doen, en hadden we veel meer flexibiliteit als we de kijk-" "condities in overweging hadden genomen." #: ../../general_concepts/colors/color_managed_workflow.rst:139 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." msgstr "" "Dat gezegd hebbende, het is ook voor artiesten erg handig om de werkruimten " "te begrijpen. Verschillende werkruimten geven bij het mengen en bij het " "filteren verschillende resultaten, en u kunt voor geavanceerde technologie " "zoals HDR alleen sommige werkruimten gebruiken." #: ../../general_concepts/colors/color_managed_workflow.rst:141 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." msgstr "" "Vergelijkbaar zal Krita, als programma bedoeld om in een leeg vlak " "illustraties te maken, zich niet druk maken over het toewijzen van " "werkruimten na de creatie van de illustratie. Maar omdat u het scherm " "gebruikt als verrekijker om naar uw afbeelding te kijken en om kleuren te " "selecteren, kunt u de apparaatruimte van uw beeldscherm zien als " "invoerruimte voor de afbeelding. Daarom is het verstandig om een profiel van " "uw monitor te maken en dit profiel via de instellingen aan Krita ter " "beschikking te stellen zodat het daarna u helpt met het voorbereiden van uw " "werk voor het afdrukken en andere projecten." #: ../../general_concepts/colors/color_managed_workflow.rst:143 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.)" msgstr "" "Samengevat is het nogal handig om zaken zoals kijk-condities in uw " "achterhoofd te houden. Veel professionele artiesten gebruiken een neutrale " "grijze kleur als de standaard achtergrond van de werkruimte omdat ze vinden " "dat ze dan veel dynamischer afbeeldingen creëren omdat ze hun kijk-condities " "hebben verbetert. Dit is ook waarom veel grafische programma's zoals Krita, " "tegenwoordig met een donkere thema komen. (Maar dit kan natuurlijk ook zijn " "omdat tegenwoordig donkere thema's als cool worden gezien, wie weet.)" #: ../../general_concepts/colors/color_managed_workflow.rst:148 msgid "ICC profiles" msgstr "ICC profielen" #: ../../general_concepts/colors/color_managed_workflow.rst:150 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:" msgstr "" "Een ICC profiel is een set coördinaten die in XYZ de grenzen van " "apparaatruimte beschrijven, en dit is de kleurbeheer dat die u gebruikt bij " "de communicatie van uw werkruimte naar de printers en programma's die " "bedoelt zijn voor de grafische industrie, zoals Gimp, Scribus, Photoshop, " "Illustrator, Inkscape, digiKam, RawTheraphee, enz. Er zijn twee soorten van " "ICC profielen:" #: ../../general_concepts/colors/color_managed_workflow.rst:153 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." msgstr "" "Deze worden met Krita meegeleverd. Matrix shaper profielen worden gemaakt " "door parameters in te stellen waarna men door interpolatie daartussen de " "precieze afmetingen van de kleurruimte verkrijgt. Hierdoor kan de browser " "voor kleurruimte van Krita u veel informatie over deze profielen geven. Voor " "werkruimte wordt de voorkeur gegeven aan deze profielen." #: ../../general_concepts/colors/color_managed_workflow.rst:159 msgid "Matrix Shaper profiles" msgstr "Matrix Shaper profielen" #: ../../general_concepts/colors/color_managed_workflow.rst:159 msgid "" "Matrix shaper profiles have a few parameters that describe the color space " "which are then interpolated between, this requires a lot of maths." msgstr "" "Matrix shaper profielen hebben een paar parameters die de kleurruimte " "beschrijven waarna een interpolatie daartussen volgt, dit vereist veel " "rekenwerk." #: ../../general_concepts/colors/color_managed_workflow.rst:162 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." msgstr "" "Ze worden vrij weinig gebruikt, en worden voornamelijk gebruikt voor printer-" "profielen, zoals CMYK. cLUT, of Color Look-up Tabel profielen slaan veel " "meer data op dan Matrix shaper profielen, zodat ze ook data kunnen hebben " "over kleine afwijkingen veroorzaakt door, bijvoorbeeld, onverwachte " "resultaten van het mengen van pigmenten. Dit is een veel natuurlijker " "benadering voor het beschrijven van een kleurruimte, waarom veel programma's " "die kleurbeheer niet zo belangrijk vinden deze niet ondersteunen." #: ../../general_concepts/colors/color_managed_workflow.rst:168 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." msgstr "" "cLUT profielen werken door in een kleurruimte voor elke kleur een tabel aan " "te maken met coördinaten in een bijbehorende referentieruimte. Voor CMYK is " "dit standaard L\\*A\\*B\\* en voor de rest XYZ. Deze tabellen zijn moeilijk " "om te maken, wat inhoud dat deze profielen nog veel minder gebruikt worden." #: ../../general_concepts/colors/color_managed_workflow.rst:169 msgid "cLUT profiles" msgstr "cLUT profielen" #: ../../general_concepts/colors/color_managed_workflow.rst:171 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." msgstr "" "Het meest interessante aan ICC profielen is dat uw werkruimte groter kan " "zijn dat uw apparaatruimte. Dit is in het algemeen niet slecht. Maar, bij " "het converteren, heeft u wel de vraag hoe u waarden vanuit de werkruimte " "moet vertalen." #: ../../general_concepts/colors/color_managed_workflow.rst:174 msgid "Perceptual" msgstr "Op waarneming" #: ../../general_concepts/colors/color_managed_workflow.rst:174 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." msgstr "" "Dit perst de waarden uit de werkruimte in de ruimte waarnaar het wordt " "geconverteerd. Dit is een handige methode om alle mogelijke waarden te " "kunnen zien, maar niet zo goed als u een accurate kleuren reproductie wilt. " "Gebruik deze als u alle kleuren van een afbeelding wilt zien, of alle " "mogelijke contrasten wilt tonen. Werkt niet met Matrix Shaper profielen, " "werkt standaard met relatieve colorimetric." #: ../../general_concepts/colors/color_managed_workflow.rst:177 msgid "Absolute Colorimetric" msgstr "Absoluut colorimetrisch" #: ../../general_concepts/colors/color_managed_workflow.rst:177 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." msgstr "" "Als tegenovergestelde van Op waarneming, zal Absoluut colorimetrisch " "proberen om ten koste van alles de correcte kleuren te bewaren, wat kan " "resulteren in verschrikkelijk uitziende kleuren. Wordt alleen aanbevolen " "voor reproductiewerk. Werkt niet met Matrix Shaper profielen in Krita " "vanwege ICC v4 workflow standaarden." #: ../../general_concepts/colors/color_managed_workflow.rst:180 msgid "Relative Colorimetric" msgstr "Relatief colorimetrisch" #: ../../general_concepts/colors/color_managed_workflow.rst:180 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." msgstr "" "Als tussenoplossing ergens tussen Op waarneming en Absoluut, zal relatief " "proberen om alle tussen de kleurruimten overeenkomende kleuren om te zetten. " "Het doet dit door de witte en zwarte punten uit te lijnen. Het snijdt de " "rest af bij hun respectievelijke grenzen. Dit is wat alle matrix shaper " "profielen standaard doen tijdens een conversie, omdat de ICC v4 workflow " "specificeert om alleen Relatieve Colorimetric te gebruiken bij matrix shaper " "profielen." #: ../../general_concepts/colors/color_managed_workflow.rst:183 msgid "Saturation" msgstr "Verzadiging" #: ../../general_concepts/colors/color_managed_workflow.rst:183 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." msgstr "" "Zal ten koste van alles proberen om de kleur te bewaren, zelfs de tint zal " "worden opgeofferd. Gebruikt bij infographics. Werkt niet met Matrix Shaper " "profielen, werkt standaard met Relatief colorimetrisch." #: ../../general_concepts/colors/color_managed_workflow.rst:185 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." msgstr "" "*ICC profiel versie* is het eerste dat u in gedachte moet houden als u ICC " "profielen in de weer gaat. Krita kan zowel Versie 2 en Versie 4 profiles " "leveren, waarbij versie 4 betere resultaten levert wat betreft " "kleurberekeningen, maar versie 2 door meer programma's gebruikt wordt (zoals " "u kunt zien in 'interactie met andere toepassingen'. Dit is de reden waarom " "Krita standaard op V2 staat ingesteld, en we aanbevelen om V2 te gebruiken " "als u er niet zeker van bent dat de andere door u gebruikte programma's V4 " "aankunnen." #: ../../general_concepts/colors/color_managed_workflow.rst:188 msgid "LUT docker and HDR imaging" msgstr "LUT docker en HDR-afbeelding" #: ../../general_concepts/colors/color_managed_workflow.rst:196 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." msgstr "" "De :ref:`lut_docker` is het tweede belangrijke gedeelte van kleurbeheer in " "Krita dat wordt gedeelte tussen Krita en programma's zoals Blender, Natron " "en Nuke, en gebruikt alleen de Look Up Tables die via een " "configuratiebestand zijn ingesteld." #: ../../general_concepts/colors/color_managed_workflow.rst:198 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." msgstr "" "U kunt de werkruimte van de afbeelding onder de kleurruimte plaatsen, en de " "weergave naar sRGB of uw eigen LUT als u deze aan de configuratie heeft " "toegevoegd. Kijk in dit geval voor de controle van de omzetting naar een " "bepaald weergave-apparaat." #: ../../general_concepts/colors/color_managed_workflow.rst:200 msgid "" "Component, exposure, gamma, whitepoint and blackpoint are knobs which allows " "you to modify the display filter." msgstr "" "Componenten, belichting, gamma, witpunt en zwartpunt zijn knoppen waarmee u " "het beeldscherm filter kunt wijzigen." #: ../../general_concepts/colors/color_managed_workflow.rst:208 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." msgstr "" "Zoals eerder uitgelegd, we kunnen ons beeldscherm zien als een telescoop of " "verrekijker waarmee we naar onze afbeelding kijken. Wat betekent dat het ons " "beeld van de afbeelding een beetje verstoort. Maar we kunnen onze " "verrekijker aanpassen, of een filter gebruiken om onze afbeelding op een " "andere wijze te bekijken. Bijvoorbeeld, door het wit in een afbeelding te " "bekijken dat witter is dan het wit van ons scherm. Om uit te leggen wat dat " "inhoud, moeten we bedenken wat wit eigenlijk is." #: ../../general_concepts/colors/color_managed_workflow.rst:210 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." msgstr "" "Bijvoorbeeld, wit is op onze monitor volledig rood, volledig groen en " "volledig blauw. Maar het is heel anders dan het wit van ons papier, of de " "kleur van melk, wit van de zon, of zelfs het wit van het scherm op onze GSM." #: ../../general_concepts/colors/color_managed_workflow.rst:212 msgid "" "Black similarly, is brighter on a LCD display than a LED one, and " "incomparable with the black of a carefully sealed room." msgstr "" " Vergelijkbaar is zwart helderder op een LCD display dan op een LED display, " "en onvergelijkbaar met het zwart van zorgvuldig verduisterde kamer." #: ../../general_concepts/colors/color_managed_workflow.rst:214 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." msgstr "" "Dit betekent dat er mogelijk zwart dat zwarter is dan het beeldscherm-zwart, " "en wit dat witter is dan het beeldscherm-wit. Maar voor de eenvoud koppelen " "we toch de zwartpunt en de witpunt aan bepaalde waarden. Van daaruit kunnen " "we bepalen of een wit witter is dan het witpunt, of een zwart zwarter is dan " "het zwartpunt." #: ../../general_concepts/colors/color_managed_workflow.rst:216 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." msgstr "" "In de LUT docker kunt u dit display-filter instellen en de vervorming " "wijzigen. Dit is handig bij het wijzigen van afbeeldingen die zijn gemaakt " "met bij een scene horende waarden, zoals HDR fotos, of afbeeldingen die uit " "een render engine komen." #: ../../general_concepts/colors/color_managed_workflow.rst:224 msgid "" "So, for example, we can choose to scale whiter-than-screen-white to our " "screen-white so we can see the contrasts there." msgstr "" "Als voorbeeld, kunnen we ervoor kiezen om de witter dan het scherm-wit naar " "onze scherm-wit te verschalen zodat we het contrast daar kunnen zien." #: ../../general_concepts/colors/color_managed_workflow.rst:226 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." msgstr "" "Het idee hierachter is dat u gebruik kunt maken van de lichtere details in " "een afbeelding. Terwijl u het verschil niet kunt zien tussen scherm-wit en " "witter-dan-scherm-wit (omdat uw scherm het verschil niet kan laten zien), " "kunnen grafische programma's dit zeker gebruiken." #: ../../general_concepts/colors/color_managed_workflow.rst:228 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." msgstr "" "Een bekend voorbeeld is om de verlichting in een 3d model overeen te laten " "komen met de foto van een scene in de echte wereld. Een andere is het betere " "retoucheren van een foto, met veel meer voor de gebruiker beschikbare " "contrast-informatie. Bij het schilderen zelf kunt u een afbeelding maken " "waar u met de contrast net zoveel kunt spelen als u wilt, en kunt het net zo " "helder maken als u wilt." #: ../../general_concepts/colors/color_managed_workflow.rst:230 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." msgstr "" "LUT docker bewerkingen zijn per weergave, u kunt daarom een nieuwe weergave " "creëren en het op lichtkracht instellen. Op deze manier kunt u de afbeelding " "zowel in kleur als in grijswaarden zien en uw instellingen in de gaten " "houden." #: ../../general_concepts/colors/color_managed_workflow.rst:232 msgid "" "Another example is to carefully watch the gradients in a certain section." msgstr "" "Een ander voorbeeld is het nauwkeurig bestuderen van het kleurverloop in een " "bepaald gedeelte." #: ../../general_concepts/colors/color_managed_workflow.rst:234 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." msgstr "" "Net zoals met ICC, kunt u met de LUT Docker voor uw apparaten profielen " "maken. In dat geval is het de 'LUT', wat staat voor 'Look Up Table', en wat " "u aan de OCIO kunt toevoegen door de configuratiebestanden aan te passen. " "Als OCIO is ingeschakeld, dan is de configuratie in :menuselection:" "`Instellingen --> Krita instellen--> Kleurbeheer` uitgeschakeld, tenzij u " "de :guilabel:`Interne` kleur-machine gebruikt." #: ../../general_concepts/colors/color_managed_workflow.rst:237 msgid "In summary" msgstr "Samenvattend" #: ../../general_concepts/colors/color_managed_workflow.rst:239 msgid "Krita has two modes of color management:" msgstr "Krita heeft twee methoden voor kleurbeheer:" #: ../../general_concepts/colors/color_managed_workflow.rst:241 msgid "" "ICC works in terms of spaces relative to the CIEXYZ space, and requires an " "ICC profile." msgstr "" "ICC werkt met ruimtes relatief ten opzichte van de CIEXYZ ruimte, en heeft " "een ICC profiel nodig." #: ../../general_concepts/colors/color_managed_workflow.rst:242 msgid "OCIO works in terms of interpretation, and makes use of LUTs." msgstr "OCIO werkt met omzettingen, en maakt gebruik van LUTs." #: ../../general_concepts/colors/color_managed_workflow.rst:243 msgid "both can be made with a colorimeter." msgstr "beide kunt u met een colorimeter maken." #: ../../general_concepts/colors/color_managed_workflow.rst:244 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." msgstr "" "Als u een goede workflow voor kleurbeheer wilt hebben, dan heeft u er een " "gemaakt die is aangepast aan uw invoerapparaat (uw beeldscherm) en de " "uitvoer-apparaten (uw printer, of het doelscherm). Voor web is de uitvoer " "altijd sRGB." #: ../../general_concepts/colors/color_managed_workflow.rst:245 msgid "" "Set up your screen profiles under :menuselection:`Settings --> Configure " "Krita --> Color management`." msgstr "" "Stel u scherm-profielen in :menuselection:`Instellingen --> Krita instellen " "--> Kleurbeheer`." #: ../../general_concepts/colors/color_managed_workflow.rst:246 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." msgstr "" "Gebruik NIET scherm-profielen of andere apparaat-profielen om in te tekenen. " "Gebruik een werkruimte-profiel zoals een van de 'elle'-profielen hiervoor, " "omdat de kleurberekeningen veel voorspelbaarder en prettiger zijn. Krita zal " "tussen uw scherm en werkruimte de omzettingen doen, zodat u de juiste " "kleuren kunt selecteren. Dit verandert u scherm in een verrekijker voor het " "bekijken van de afbeelding." #: ../../general_concepts/colors/color_managed_workflow.rst:247 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." msgstr "" "Gebruik een geschikte kleurbeheer voor de juiste workflow. Als u werkt met " "Blender, dan bent u beter af door OCIO te gebruiken dan met ICC. Als u werkt " "met Scribus of Photoshop, gebruik dan ICC." #: ../../general_concepts/colors/color_managed_workflow.rst:249 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." msgstr "" "Krita voert veel kleurberekeningen uit, vaak betreft het mengen van kleuren. " "Deze kleurberekeningen gaan het best in een lineaire kleurruimte, en een " "lineaire kleurruimte vereist een bit diepte van tenminste 16bit om correct " "te kunnen werken. Het nadeel is dat het verwarrend kan zijn om in een " "lineaire kleurruimte te werken." #: ../../general_concepts/colors/color_managed_workflow.rst:251 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!" msgstr "" "Als u van schilderen houdt, en u heeft genoeg RAM, en u wilt bij uw eerste " "stapjes voordeel hebben van het kleurbeheer van Krita, probeer dan al uw " "afbeeldingen om te zetten van de ingebouwde sRGB naar sRGB-v2-elle-g10.icc " "of rec2020-v2-elle-g10.icc met 16bit drijvende komma. Hierdoor kunt u beter " "kleur mengen terwijl u de mogelijkheid heeft om in HDR te gaan werken!" #: ../../general_concepts/colors/color_managed_workflow.rst:256 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!" msgstr "" "Sommige grafische kaarten zoals die van het NVidia-merk werken het best met " "16 bit drijvende komma, omdat NVidia kaarten intern naar de drijvende komma " "omzetten. Als het da niet meer hoeft te doen dan werkt het sneller!" #: ../../general_concepts/colors/color_managed_workflow.rst:260 msgid "" "No amount of color management in the world can make the image on your screen " "and the image out of the printer have 100% the same color." msgstr "" "Hoeveel kleurbeheer u ook gebruikt, de afbeelding van het scherm en de " "afbeelding uit de printer zullen nooit 100% dezelfde kleur hebben." #: ../../general_concepts/colors/color_managed_workflow.rst:263 msgid "Exporting" msgstr "Exporteren" #: ../../general_concepts/colors/color_managed_workflow.rst:265 msgid "" "When you have finished your image and are ready to export it, you can modify " "the color space to optimize it:" msgstr "" "Als uw afbeelding klaar is en u wilt het exporteren, dan kunt u de " "kleurruimte wijzigen om het te optimaliseren:" #: ../../general_concepts/colors/color_managed_workflow.rst:267 msgid "If you are preparing an image for the web:" msgstr "Als u een afbeelding klaarmaakt voor het web:" #: ../../general_concepts/colors/color_managed_workflow.rst:269 msgid "" "If you use 16bit color depth or higher, convert the image to 8bit color " "depth. This will make the image much smaller." msgstr "" "Als u 16 bit of meer kleurdiepte gebruikt, converteer dan de afbeelding naar " "8 bit kleurdiepte. Dit maakt de de opslag-grootte van de afbeelding veel " "kleiner." #: ../../general_concepts/colors/color_managed_workflow.rst:271 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." msgstr "" "Krita heeft op dit moment geen ingebouwde dithering, wat inhoud dat 16 naar " "18 bit conversies zaagtandpatronen kunnen geven. Maar u kunt dit simuleren " "door een fill layer met een patroon toe te voegen, deze fill layer in te " "stellen op to overlay, en op 5% dekking. Maak de hele afbeelding plat en " "converteer het naar 8bit. Het patroon zal functioneren als dithering wat de " "kleurverloop gladder maakt." #: ../../general_concepts/colors/color_managed_workflow.rst:273 msgid "If it's a gray-scale image, convert it to gray-scale." msgstr "" "Als het een grijswaardeafbeelding is, converteer het naar grijswaarden." #: ../../general_concepts/colors/color_managed_workflow.rst:274 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." msgstr "" "Als het een afbeelding in kleur is, bewaar het dan in de ruimteprofiel " "waarin u bewerkte: heden ten dage ondersteunen veel web browsers het gebruik " "van de kleurprofielen die in de afbeelding zijn ingebed. Firefox, " "bijvoorbeeld, zal proberen om uw afbeelding te converteren zodat het past in " "het kleurprofiel van de andere monitor (als die er een heeft). Op die manier " "zal de afbeelding bijna hetzelfde op uw scherm en op de andere van een " "profiel voorziene monitoren er uit zien." #: ../../general_concepts/colors/color_managed_workflow.rst:279 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 " "`_, save your PNG, JPG or TIFF without an embedded profile to work " "around this." msgstr "" "In sommige versies van Firefox zien de kleuren er raar uit: dit is een bug " "in Firefox, wat wordt veroorzaakt doordat zijn `kleurbeheer systeem " "incompleet is `_, sla uw PNG, JPG of TIFF zonder een ingebed profiel op om " "dit op te lossen." #: ../../general_concepts/colors/color_managed_workflow.rst:281 msgid "If you are preparing for print:" msgstr "Als u klaarmaakt voor afdrukken:" #: ../../general_concepts/colors/color_managed_workflow.rst:283 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." msgstr "" "Hopelijk bewerkte u de afbeelding met een werkruimte-profiel en niet met de " "echte profiel van uw scherm, als u dat niet heeft gedaan, converteer het " "naar iets zoals Adobe RGB, sRGB of Rec. 2020." #: ../../general_concepts/colors/color_managed_workflow.rst:284 msgid "" "Check with the printer what kind of image they expect. Maybe they expect " "sRGB color space, or perhaps they have their own profile." msgstr "" "Controleer wat voor soort afbeelding de printer verwacht. Misschien verwacht " "het sRGB kleurruimte, of heeft het een eigen profiel." #: ../../general_concepts/colors/color_managed_workflow.rst:287 msgid "Interaction with other applications" msgstr "Interactie met andere programma´s" #: ../../general_concepts/colors/color_managed_workflow.rst:290 msgid "Blender" msgstr "Blender" #: ../../general_concepts/colors/color_managed_workflow.rst:292 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." msgstr "" "Als u de functionaliteit van Krita's OCIO wilt gebruiken, en speciaal in " "combinatie met Blender's kleurbeheer, dan kunt u proberen om het in " "combinatie met Blender's OCIO config te gebruiken." #: ../../general_concepts/colors/color_managed_workflow.rst:294 msgid "" "Blender's OCIO config is under ``/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." msgstr "" "Blender's OCIO config is te vinden in ``/version number/" "datafiles/colormanagement``. Stel de LUT docker in op het gebruik van de " "OCIO engine, en selecteer de config in op bovengenoemde pad. Dit zal u " "Blender's invoer en scherm-ruimte geven, maar niet het uiterlijk, omdat deze " "nog niet door Krita worden ondersteund." #: ../../general_concepts/colors/color_managed_workflow.rst:298 msgid "Windows Photo Viewer" msgstr "Windows Photo Viewer" #: ../../general_concepts/colors/color_managed_workflow.rst:300 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." msgstr "" "U kunt problemen tegenkomen als u verschillende programma's samen gebruikt. " "Een belangrijk gegeven is dat de standaard Windows Photo Viewer programma " "niet met moderne ICC profielen overweg kan. Krita gebruikt versie 4 " "profielen; Photo Viewer kan alleen met versie 2 profielen overweg. Als u " "naar JPEG met een ingebouwde profiel exporteert, dan zal Photo Viewer uw " "afbeelding veel te donker tonen." #: ../../general_concepts/colors/color_managed_workflow.rst:303 msgid "Example workflows" msgstr "Voorbeeld workflow" #: ../../general_concepts/colors/color_managed_workflow.rst:305 msgid "" "Here are some example workflows to get a feeling of how your color " "management workflow may look like." msgstr "" "Hier zijn enkele voorbeeld workflows om een idee te krijgen hoe uw " "kleurbeheer workflow er kan uit zien." #: ../../general_concepts/colors/color_managed_workflow.rst:307 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'." msgstr "" "Zoals al eerder vermeld, kunt u de invoer voor uw scherm instellen in :" "menuselection:`Instellen --> Krita instellen --> Kleurbeheer`, of via de LUT " "docker's 'scherm ruimte'. Werkruimte kunt u per document via nieuw bestand " "instellen, of in de LUT docker via 'invoerruimte'." #: ../../general_concepts/colors/color_managed_workflow.rst:310 msgid "Webcomic" msgstr "Webcomic" #: ../../general_concepts/colors/color_managed_workflow.rst:317 #: ../../general_concepts/colors/color_managed_workflow.rst:339 #: ../../general_concepts/colors/color_managed_workflow.rst:357 msgid "Input" msgstr "Invoer" #: ../../general_concepts/colors/color_managed_workflow.rst:318 #: ../../general_concepts/colors/color_managed_workflow.rst:340 #: ../../general_concepts/colors/color_managed_workflow.rst:358 msgid "Your screen profile. (You pick colors via your screen)" msgstr "Uw scherm-profiel. (u selecteert de kleuren via uw scherm)" #: ../../general_concepts/colors/color_managed_workflow.rst:319 #: ../../general_concepts/colors/color_managed_workflow.rst:341 #: ../../general_concepts/colors/color_managed_workflow.rst:359 msgid "Workingspace" msgstr "Werkruimte" #: ../../general_concepts/colors/color_managed_workflow.rst:320 msgid "" "sRGB (the default screen profile) or any larger profile if you can spare the " "bit depth and like working in them." msgstr "" "sRGB (het standaard scherm profiel) of elk groter profiel als u genoeg " "geheugen heeft en er graag mee werkt." #: ../../general_concepts/colors/color_managed_workflow.rst:322 #: ../../general_concepts/colors/color_managed_workflow.rst:344 #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "Output" msgstr "Uitvoer" #: ../../general_concepts/colors/color_managed_workflow.rst:322 msgid "" "sRGB, ICC version 2, sRGB TRC for the internet, and a specialized CMYK " "profile from the printing house for the printed images." msgstr "" "sRGB, ICC version 2, sRGB TRC voor het internet, en een gespecialiseerd CMYK " "profiel van de drukkerij voor de af te drukken afbeeldingen." #: ../../general_concepts/colors/color_managed_workflow.rst:324 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." msgstr "" "Gebruik de sRGB-elle-V2-srgbtrc.icc voor de uitwisseling tussen Inkscape, " "Photoshop, Painttool Sai, Illustrator, Gimp, Manga Studio, Paintstorm " "Studio, MyPaint, Artrage, Scribus, enz. en Krita." #: ../../general_concepts/colors/color_managed_workflow.rst:326 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." msgstr "" "Als u via ICC een grote ruimte gebruikt, dan kunt u het alleen uitwisselen " "met Krita, Photoshop, Illustrator, Gimp 2.9, Manga Studio en Scribus. Alle " "anderen nemen aan dat u sRGB als ruimte gebruikt, onafhankelijk van alles " "omdat ze geen kleurbeheer hebben." #: ../../general_concepts/colors/color_managed_workflow.rst:328 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." msgstr "" "Als u gaat uitwisselen tussen Krita en Blender, Nuke of Natron, gebruik dan " "OCIO en stel de invoer in op 'sRGB', maar zorg er voor dat u voor ICC het " "sRGB profiel selecteert bij het creëren van een nieuw bestand." #: ../../general_concepts/colors/color_managed_workflow.rst:330 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." msgstr "" "En tenslotte voor het web, converteer de afbeelding naar sRGB 8bit, " "'srgbtrc', bed het ICC profiel niet in. En dan, als u PNG gebruikt, haal het " "door een programma zoals pngcrush of een andere PNG optimizer. Er is in dit " "geval voor sRGB gekozen omdat u kunt aannemen dat het grootste gedeelte van " "uw publiek voor hun scherm geen profiel heeft gemaakt, en dat ze geen scherm " "hebben dat geavanceerd genoeg is voor al dat gamut spul. Daarom converteren " "we naar het standaard scherm van het internet, sRGB." #: ../../general_concepts/colors/color_managed_workflow.rst:333 msgid "Print" msgstr "Afdrukken" #: ../../general_concepts/colors/color_managed_workflow.rst:342 msgid "sRGB or Rec. 2020 if you can afford the bit-depth being 16bit." msgstr "" "sRGB of Rec. 2020 als u het zich kan veroorloven dat de bit-diepte 16 bit is." #: ../../general_concepts/colors/color_managed_workflow.rst:344 msgid "" "Specialized CMYK profile from the printing house for the printed images." msgstr "" "Gespecialiseerd CMYK profiel van de drukkerij voor de af te drukken " "afbeeldingen." #: ../../general_concepts/colors/color_managed_workflow.rst:346 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." msgstr "" "De CMYK profielen verschillen per printer, en zelfs per papiersoort of " "inkttype wees dus niet roekeloos en vraag van te voren naar deze profielen, " "in plaats van iets te doen zoals het tekenen in een willekeurig CMYK " "profiel. Zoals al vermeld in de sectie over kijk-condities, wilt u uw opties " "geopend houden." #: ../../general_concepts/colors/color_managed_workflow.rst:348 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." msgstr "" "U kunt de geavanceerde kleurenkiezer zo instellen dat het naar een gekozen " "profiel converteert via :menuselection:`Instellingen --> Krita configureren " "--> Instellingen kleurenkiezer`. Schakel daar :guilabel:`Kleurenkiezer " "gebruikt een andere kleurruimte dan afbeelding` in en selecteer het gewenste " "CMYK profiel. Dit beperkt uw kleuren enigszins, maar houd wel alle filters- " "en mengopties van RGB." #: ../../general_concepts/colors/color_managed_workflow.rst:351 msgid "Games" msgstr "Spellen" #: ../../general_concepts/colors/color_managed_workflow.rst:360 msgid "sRGB or grayscale linear for roughness and specular maps." msgstr "sRGB of lineaire grijswaarden voor roughness en specular maps." #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "" "This one is tricky, but in the end it'll be sRGB for the regular player." msgstr "" "Dit is een moeilijke, maar aan het eind is het sRGB voor de gewone speler." #: ../../general_concepts/colors/color_managed_workflow.rst:364 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." msgstr "" "Dus dit is een moeilijke. U kunt tussen programma's OCIO en ICC gebruiken, " "maar het wordt aangeraden om de afbeeldingen naar de engine in sRGB of " "grijswaarden te sturen. Dezer dagen staan veel op fysiek gebaseerde " "renderers toe dat u instelt of een afbeelding ingelezen moet worden als een " "lineaire of 'srgbtrc' afbeelding, en dit is van vitaal belang zodat de " "afbeelding goed wordt geïnterpreteerd in de fysiek gebaseerde berekeningen " "van de game renderer." #: ../../general_concepts/colors/color_managed_workflow.rst:366 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." msgstr "" "Omdat game engines geoptimaliseerde content moeten hebben, en het daarom " "wordt aanbevolen om in 8bit te blijven, kunnen toekomstige schermen hogere " "bitdieptes hebben, en als renderers dit beginnen te ondersteunen, dan kan " "het handig zijn om een workflow te ontwikkelen waar de werkruimte bestanden " "onnodig groot zijn en u enkele scripts gebruikt om ze te optimaliseren voor " "uw huidige render gebruik, wat in de toekomst het updaten van het spel voor " "betere schermen veel minder omslachtig maakt." #: ../../general_concepts/colors/color_managed_workflow.rst:368 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." msgstr "" "Normal maps en heightmaps worden officieel geacht te zijn gedefinieerd met " "'non-color data' werkruimte, maar u zult merken dat de meeste engines daar " "helemaal niet om geven. Draag in plaats daarvan de game engine op om bij het " "importeren van het bestand geen conversie uit te voeren." #: ../../general_concepts/colors/color_managed_workflow.rst:370 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)." msgstr "" "Specular, glossiness, metalness en roughness maps zijn allemaal gebaseerd op " "lineaire berekeningen, en als u denkt dat een bepaald materiaal een " "metalness van 0.3 heeft, dan is dat 30% grijs in een lineaire ruimte. Zorg " "er daarom voor dat de game engine renderer weet dat dit een lineaire ruimte " "afbeelding is (of tenminste, dat het niet moet worden geconverteerd)." #: ../../general_concepts/colors/color_managed_workflow.rst:374 msgid "" "`Visualizing the XYZ color space `_." msgstr "" "`De XYZ kleurruimte visualiseren `_." #: ../../general_concepts/colors/color_managed_workflow.rst:375 msgid "" "`Basics of gamma correction `_." msgstr "" "`Inleiding tot gamma correctie `_." #: ../../general_concepts/colors/color_managed_workflow.rst:376 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 `_." msgstr "" "`Panda3D voorbeeld van hoe een afbeelding dat is gamma gecodeerd zonder dat " "de 3D renderer weet dat het gamma-codering heeft kan resulteren in te " "donkere afbeeldingen `_." #: ../../general_concepts/colors/color_managed_workflow.rst:377 msgid "" "`2D examples of the effect of gamma-encoding on color maths `_." msgstr "" "`2D voorbeelden van het effect van gamma-codering van kleur-berekeningen " "`_." #: ../../general_concepts/colors/color_managed_workflow.rst:378 msgid "" "`Basic overview of color management from ArgyllCMS manual `_." msgstr "" "`Basis inleiding over kleurbeheer uit ArgyllCMS handleiding `_." diff --git a/locale/pt_PT/LC_MESSAGES/contributors_manual/krita_manual_conventions.po b/locale/pt_PT/LC_MESSAGES/contributors_manual/krita_manual_conventions.po index 99b41b9d2..9ca13c8f8 100644 --- a/locale/pt_PT/LC_MESSAGES/contributors_manual/krita_manual_conventions.po +++ b/locale/pt_PT/LC_MESSAGES/contributors_manual/krita_manual_conventions.po @@ -1,1514 +1,1514 @@ # SOME DESCRIPTIVE TITLE. # 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 , YEAR. # msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-09 03:27+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: 2019-07-09 11:32+0100\n" "Last-Translator: José Nuno Coelho Pires \n" "Language-Team: Portuguese \n" "Language: pt\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" "X-POFile-SpellExtra: hint image Kritamouseleft Kritamousemiddle sample\n" "X-POFile-SpellExtra: MediaWiki code rubric conf CIT images alt pipe icons\n" "X-POFile-SpellExtra: py figwidth openSuse pandoc nomelegenda veridiano sup\n" "X-POFile-SpellExtra: mouseright ref rubic versus genindex Sphinx Trajão\n" "X-POFile-SpellExtra: Bugzilla Wolthera rst seealso Krita Kritamousescroll\n" "X-POFile-SpellExtra: reStructuredText mousescroll Kritamouseright Topic\n" "X-POFile-SpellExtra: url bugzilla alternativ mousemiddle Sourceforge GDL\n" "X-POFile-SpellExtra: backticks mouseleft en Pandoc width align admonition\n" "X-POFile-IgnoreConsistency: Table\n" "X-POFile-SpellExtra: description center rows shorthand license header\n" "X-POFile-SpellExtra: guilabel menuselection kbd colspans list program\n" "X-POFile-SpellExtra: authors table family int height font append\n" "X-POFile-SpellExtra: size index px color minhaFuncao if metadata body\n" "X-POFile-SpellExtra: return max padding serif background minhafuncao line\n" "X-POFile-SpellExtra: placeholder eee margin def\n" #: ../../:2 msgid "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: mouseleft" msgstr "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: botão esquerdo" #: ../../:4 msgid "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: mouseright" msgstr "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: botão direito" #: ../../:6 msgid "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: mousemiddle" msgstr "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: botão do meio" #: ../../:8 msgid "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" msgstr "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: deslocamento do rato" +#: ../../contributors_manual/krita_manual_conventions.rst:None +msgid "Horizontal Rulers" +msgstr "Réguas Horizontais" + #: ../../contributors_manual/krita_manual_conventions.rst:0 msgid "" ".. image:: images/sample.png\n" " :alt: an image." msgstr "" ".. image:: images/sample.png\n" " :alt: uma imagem." -#: ../../contributors_manual/krita_manual_conventions.rst:None -msgid "Horizontal Rulers" -msgstr "Réguas Horizontais" - #: ../../contributors_manual/krita_manual_conventions.rst:1 msgid "reStructuredText conventions for the Krita Manual" msgstr "Convenções de reStructuredText para o Manual do Krita" #: ../../contributors_manual/krita_manual_conventions.rst:16 msgid "Mark-up conventions for the Krita Manual" msgstr "Convenções de formatação para o Manual do Krita" #: ../../contributors_manual/krita_manual_conventions.rst:18 msgid "" "This details the style conventions for using restructured text for the Krita " "Manual." msgstr "" "Isto detalha as convenções de estilo para usar o texto estruturado que é " "usado no Manual do Krita." #: ../../contributors_manual/krita_manual_conventions.rst:20 msgid "" "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):" msgstr "" "Recomenda-se que veja a `especificação oficial `_ do reStructuredText, e dado que a mesma reside no " "Sourceforge, grave uma cópia no seu disco rígido (o Sourceforge, na altura " "em que isto foi escrito, estava a ter alguns problemas de disponibilidade " "dos servidores):" #: ../../contributors_manual/krita_manual_conventions.rst:23 msgid "" "`Primer `_" msgstr "" "`Introdução `_" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "User Manual:" msgstr "Manual do Utilizador:" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "" "`Quick Ref `_" msgstr "" "`Referência Rápida `_" #: ../../contributors_manual/krita_manual_conventions.rst:25 msgid "" "`Text Cheatsheet `_" msgstr "" "`Cábula de Texto `_" #: ../../contributors_manual/krita_manual_conventions.rst:27 msgid "" "`Introduction `_" msgstr "" "`Introdução `_" #: ../../contributors_manual/krita_manual_conventions.rst:28 msgid "" "`Markup `_" msgstr "" "`Formatação `_" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "Reference Documentation:" msgstr "Documentação de Referência:" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "" "`Directives `_" msgstr "" "`Directivas `_" #: ../../contributors_manual/krita_manual_conventions.rst:30 msgid "`Roles `_" msgstr "`Papéis `_" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "Sphinx specific docs:" msgstr "Documentação específica do Sphinx:" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "" "`Sphinx' page on restructured text `_ -- This is useful for the specific " "sphinx directives and roles it uses to generate for example table of " "contents." msgstr "" "A página do `Sphinx' sobre o texto estruturado `_ -- Isto é útil para as " "directivas específicas do Sphinx e os papéis que usa para gerar por exemplo " "os índices analíticos." #: ../../contributors_manual/krita_manual_conventions.rst:34 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." msgstr "" "Existem diferenças entre o formato reStructuredText oficial e a documentação " "do Sphinx em diversas formas de fazer as coisas. Este documento especifica " "as convenções sugeridas a seguir." #: ../../contributors_manual/krita_manual_conventions.rst:36 msgid "Contents" msgstr "Conteúdo" #: ../../contributors_manual/krita_manual_conventions.rst:39 msgid "Meta data" msgstr "Meta-dados" #: ../../contributors_manual/krita_manual_conventions.rst:41 msgid "Each page should start with the following three things:" msgstr "Cada página deverá começar pelas seguintes três coisas:" #: ../../contributors_manual/krita_manual_conventions.rst:44 msgid "" "This is a general description of the page. It will be converted to an html " "meta tag which will be used by search engines::" msgstr "" "Esta é uma descrição geral da página. Será convertida para uma marca 'meta' " "do HTML que será usada pelos motores de busca::" #: ../../contributors_manual/krita_manual_conventions.rst:46 msgid "" ".. meta::\n" " :description:\n" " Description." msgstr "" ".. meta::\n" " :description:\n" " Descrição." #: ../../contributors_manual/krita_manual_conventions.rst:49 msgid "A meta description" msgstr "Uma descrição 'meta'" #: ../../contributors_manual/krita_manual_conventions.rst:52 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::" msgstr "" "Isto serve apenas para manter um registo de quem editou a página e para " "atribuir o crédito merecido. Deverá estar num comentário, para que não acabe " "por se tornar fácil de ler por máquinas. A licença do manual inteiro é a GDL " "1.3 e deverá também ser mencionada aqui::" #: ../../contributors_manual/krita_manual_conventions.rst:54 msgid "" ".. metadata-placeholder\n" "\n" " :authors: - Author 1\n" " - Author 2\n" " :license: GNU free documentation license 1.3 or later." msgstr "" ".. metadata-placeholder\n" "\n" " :authors: - Autor 1\n" " - Autor 2\n" " :license: licença de documentação livre da GNU 1.3 ou posterior." #: ../../contributors_manual/krita_manual_conventions.rst:58 msgid "A list of authors and a license." msgstr "Uma lista de autores e uma licença." #: ../../contributors_manual/krita_manual_conventions.rst:61 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::" msgstr "" "Estes são termos separados por vírgulas, pelos quais a página será indexada " "no :ref:`genindex`. O índice gerado é bastante útil tanto no formato PDF " "como para as pessoas que não sabem qual o nome exacto para o termo que " "procuram. Estes são definidos da seguinte forma::" #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid "Indexing terms." msgstr "Termos de indexação." #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid ".. index:: Keyword, Keyword with Spaces, ! Main Definition Keyword" msgstr "" ".. index:: Palavra-chave, Palavra-chave com Espaços, ! Palavra-chave de " "Definição Principal" #: ../../contributors_manual/krita_manual_conventions.rst:66 msgid "" "This is so we can easily link to the page using ``:ref:`label_name```. Try " "to make this a nice variable name::" msgstr "" "Estes existem para que se possa ligar facilmente à página com o ``:ref:" "`nome_legenda```. Tente fazer deste um nome de variável adequado::" #: ../../contributors_manual/krita_manual_conventions.rst:68 msgid ".. _label_name:" msgstr ".. _nome_legenda:" #: ../../contributors_manual/krita_manual_conventions.rst:70 msgid "" "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." msgstr "" "Depois da legenda, terá de adicionar um cabeçalho, como por exemplo ``:ref:" "`nome_legenda``` para se referir ao cabeçalho como estando em texto de " "hiperligação." #: ../../contributors_manual/krita_manual_conventions.rst:71 msgid "A label." msgstr "Uma legenda." #: ../../contributors_manual/krita_manual_conventions.rst:74 msgid "Headings" msgstr "Cabeçalhos" #: ../../contributors_manual/krita_manual_conventions.rst:76 msgid "Headings will be done in the following order::" msgstr "Os cabeçalhos serão criados pela seguinte ordem::" #: ../../contributors_manual/krita_manual_conventions.rst:78 msgid "" "############\n" "Part/Section\n" "############\n" "\n" "For pages that have a lot of subpages.\n" "\n" "=========\n" "Heading 1\n" "=========\n" "\n" "Start most manual pages with this.\n" "\n" "Heading 2\n" "---------\n" "\n" "Heading 3\n" "~~~~~~~~~\n" "\n" "Heading 4\n" "^^^^^^^^^\n" "\n" "Heading 5\n" "'''''''''\n" "\n" "Heading 6\n" "\"\"\"\"\"\"\"\"\"" msgstr "" "############\n" "Parte/Secção\n" "############\n" "\n" "Para páginas que tenham bastantes sub-páginas.\n" "\n" "=========\n" "Cabeçalho 1\n" "=========\n" "\n" "Inicie a maioria das páginas de manual com isto.\n" "\n" "Cabeçalho 2\n" "---------\n" "\n" "Cabeçalho 3\n" "~~~~~~~~~\n" "\n" "Cabeçalho 4\n" "^^^^^^^^^\n" "\n" "Cabeçalho 5\n" "'''''''''\n" "\n" "Cabeçalho 6\n" "\"\"\"\"\"\"\"\"\"" #: ../../contributors_manual/krita_manual_conventions.rst:105 msgid "" "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." msgstr "" "Estas convenções foram mais ou menos decididas pela conversão de MediaWiki " "para reStructuredText do `Pandoc `_. Se precisar de " "mais que 4 cabeçalhos, pergunte a si próprio se a página não ficou demasiado " "complicada e se precisa de ser dividida." #: ../../contributors_manual/krita_manual_conventions.rst:107 msgid "" "Sometimes you need to link to a subsection of a page, add a label above the " "heading in that case." msgstr "" "Em alguns casos terá de criar uma ligação a uma sub-secção de uma página; " "adicione uma legenda acima do cabeçalho nesse caso." #: ../../contributors_manual/krita_manual_conventions.rst:109 msgid "" "Headers should not end with punctuation, as the header will be used as the " "link name when linking to a label." msgstr "" "Os cabeçalhos não deverão terminar com pontuação, dado que o cabeçalho será " "usado como o nome da ligação ao criar uma ligação para uma legenda." #: ../../contributors_manual/krita_manual_conventions.rst:112 msgid "Linking" msgstr "Ligação" #: ../../contributors_manual/krita_manual_conventions.rst:114 msgid "" "Linking is done with ``:ref:`label_name```. When you need an alternative " "link text, you use ``:ref:`actual text shown ```." msgstr "" "A ligação é feita com um ``:ref:`nome_legenda```. Quando precisar de um " "texto de ligação alternativ, poderá usar a sintaxe ``:ref:`texto real " "apresentado ```." #: ../../contributors_manual/krita_manual_conventions.rst:116 msgid "" "Linking to external pages is done with ```url`_`` and ```link name " "`_``, which'll become `link name `_." msgstr "" "A ligação a páginas externas é feita com um ```url`_`` e o ```nome da " "ligação `_``, que se tornará `nome da ligação `_." #: ../../contributors_manual/krita_manual_conventions.rst:118 msgid "" "`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." msgstr "" "O `Pandoc `_ gosta de transformar estes em ```nome da " "ligação`__`` e depois adicionar `` .. __ :url`` ao fim do documento. Isto é " "o que se chama uma 'hiperligação anónima' o que significa que, dependendo da " "origem das ligações que aparecem no texto, estarão associadas uma à outra na " "ordem das ligações no fim do texto. Se isto soar confuso e difícil, é porque " "é. Isto também é a razão exacta pela qual desejamos evitar ligações deste " "tipo." #: ../../contributors_manual/krita_manual_conventions.rst:121 msgid "Footnotes and further reading" msgstr "Notas de rodapé e leituras posteriores" #: ../../contributors_manual/krita_manual_conventions.rst:123 msgid "" "Footnotes can be made in 3 ways, the most common one is with autonumbering, " "as per reference:" msgstr "" "As notas de rodapé podem ser criadas de 3 formas, sendo a mais comum com " "numeração automática; de acordo com a referência:" #: ../../contributors_manual/krita_manual_conventions.rst:125 msgid "" "[#]_ is a reference to footnote 1, and [#]_ is a reference to footnote 2." msgstr "" "[#]_ é uma referência à nota de rodapé 1, e [#]_ é uma referência à nota de " "rodapé 2." #: ../../contributors_manual/krita_manual_conventions.rst:128 msgid "This is footnote 1." msgstr "Esta é a nota de rodapé 1." #: ../../contributors_manual/krita_manual_conventions.rst:129 msgid "This is footnote 2." msgstr "Esta é a nota de rodapé 2." #: ../../contributors_manual/krita_manual_conventions.rst:130 msgid "This is footnote 3." msgstr "Esta é a nota de rodapé 3." #: ../../contributors_manual/krita_manual_conventions.rst:132 msgid "[#]_ is a reference to footnote 3." msgstr "O [#]_ é uma referência à nota de rodapé 3." #: ../../contributors_manual/krita_manual_conventions.rst:134 msgid "Here is a citation reference: [CIT2002]_ ." msgstr "Esta é uma referência de citação: [CIT2002]_ ." #: ../../contributors_manual/krita_manual_conventions.rst:136 msgid "" "This is the citation. It's just like a footnote, except the label is " "textual." msgstr "" "Esta é a citação. É como uma espécie de nota de rodapé, excepto que a " "legenda é textual." #: ../../contributors_manual/krita_manual_conventions.rst:139 msgid "Citation can also be referenced with ```citation `_``." msgstr "" "A citação também poderá ser referenciada com uma ```citação `_``." #: ../../contributors_manual/krita_manual_conventions.rst:141 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." msgstr "" "Não usamos de facto notas de rodapé no manual, pelo motivo que isso é um " "pouco académico demais para os nossos leitores. Contudo, recolhemos de facto " "os documentos e ligações que adicionem um pouco mais de informação sobre um " "dado tópico no fim de uma página. O Sphinx tem a directiva ``.. seealso::`` " "para se associar a endereços externos, enquanto o reStructuredText sugere o " "`.. rubic:: Notas de Rodapé`` para recolher especificamente notas do rodapé, " "dado que isso resulta bem com o LaTeX." #: ../../contributors_manual/krita_manual_conventions.rst:145 msgid "Images" msgstr "Imagens" #: ../../contributors_manual/krita_manual_conventions.rst:147 msgid "Use the image directive for images without captions::" msgstr "Use a directiva 'image' para as imagens sem legendas::" #: ../../contributors_manual/krita_manual_conventions.rst:149 msgid "" ".. image:: /images/sample.png\n" " :width: 800\n" " :align: center\n" " :alt: an image." msgstr "" ".. image:: /images/sample.png\n" " :width: 800\n" " :align: center\n" " :alt: uma imagem." #: ../../contributors_manual/krita_manual_conventions.rst:154 msgid "And figure directives for images with captions::" msgstr "E as directivas 'figure' para as imagens com legendas::" #: ../../contributors_manual/krita_manual_conventions.rst:156 msgid "" ".. figure:: /images/sample.png\n" " :figwidth: 800\n" " :align: center\n" " :alt: an image.\n" "\n" " A caption -- notice how the first letter is aligned with the :figwidth: " "option." msgstr "" ".. figure:: /images/exemplo.png\n" " :figwidth: 800\n" " :align: center\n" " :alt: uma imagem.\n" " Uma legenda -- repare como a primeira letra fica aninhada com a opção :" "figwidth:." #: ../../contributors_manual/krita_manual_conventions.rst:163 msgid "The latter gives:" msgstr "O último caso gera:" #: ../../contributors_manual/krita_manual_conventions.rst:170 msgid "" "A caption -- notice how the first letter of the caption in the directive is " "aligned with the :figwidth: option." msgstr "" "Uma legenda -- repare como a primeira letra da legenda na directiva está " "alinhada com a opção :figwidth:." #: ../../contributors_manual/krita_manual_conventions.rst:172 msgid "" "Images should go into the ``/images`` folder. By using ``/images`` instead " "of ``images``, sphinx will know the filepath isn't relative." msgstr "" "As imagens deverão ir para a pasta ``/images``. Ao usar o ``/images`` em vez " "do ``images``, o Sphinx irá saber que a localização do ficheiro não é " "relativa." #: ../../contributors_manual/krita_manual_conventions.rst:175 msgid "In-text Markup" msgstr "Formatação Dentro do Texto" #: ../../contributors_manual/krita_manual_conventions.rst:177 msgid "" "You can make text *emphasized* and **strong** with a single asterisk and " "double respectively::" msgstr "" "Poderá criar *ênfase* no texto ou torná-lo **forte** com um asterisco único " "ou um duplo, respectivamente::" #: ../../contributors_manual/krita_manual_conventions.rst:179 msgid "" "*emphasize*\n" "**strong**" msgstr "" "*ênfase*\n" "**negrito**" #: ../../contributors_manual/krita_manual_conventions.rst:182 msgid "You cannot do both ***emphasized and strong***, so take a pick." msgstr "" "Não consegue torná-lo ***enfatizado e forte ao mesmo tempo***, por isso " "escolha um deles." #: ../../contributors_manual/krita_manual_conventions.rst:184 msgid "" "You can :sub:`subscript text` and :sup:`superscript text` by using ``:sub:" "`text``` and ``:sup:`text```" msgstr "" "Poderá :sub:`tornar o texto subscrito` e :sup:`sobrescrito` se usar o ``:sub:" "`texto``` e o ``:sup:`texto```" #: ../../contributors_manual/krita_manual_conventions.rst:186 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::" msgstr "" "Contudo, use-as com muito pouca frequência! É preferível usar a formatação " "semântica existente em qualquer caso, porque facilita aos tradutores tomarem " "decisões sobre a natureza do texto::" #: ../../contributors_manual/krita_manual_conventions.rst:188 msgid "" ":menuselection:`Settings --> Configure Krita`\n" ":guilabel:`File`\n" ":kbd:`Ctrl + Z`\n" ":program:`Krita`" msgstr "" ":menuselection:`Configuração --> Configurar o Krita`\n" ":guilabel:`Ficheiro`\n" ":kbd:`Ctrl + Z`\n" ":program:`Krita`" #: ../../contributors_manual/krita_manual_conventions.rst:193 msgid "" "Avoid randomly bolding words. It does *not* make the text easier or " "friendlier to read." msgstr "" "Evite escolher palavras aleatórias para estar em negrito. *Não* torna o " "texto mais fácil ou amigável para ser lido." #: ../../contributors_manual/krita_manual_conventions.rst:196 msgid "Substitution References" msgstr "Referências de Substituição" #: ../../contributors_manual/krita_manual_conventions.rst:198 msgid "" "You can create a sort of shorthand for a piece of text or an image by doing::" msgstr "" "Poderá criar uma espécie de atalho para um pedaço de texto ou uma imagem se " "escrever::" #: ../../contributors_manual/krita_manual_conventions.rst:200 msgid ".. |shorthand| replace:: something or the other." msgstr ".. |shorthand| substituição:: uma coisa ou a outra." #: ../../contributors_manual/krita_manual_conventions.rst:202 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\"." msgstr "" "o que significa que, se usar o ``|atalho|`` no texto, será substituído por " "'uma coisa ou a outra'. Isto é útil para imagens e texto que precisem de ser " "formatados de uma forma complicada, como acontece no \"LaTeX\"." #: ../../contributors_manual/krita_manual_conventions.rst:204 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." msgstr "" "A documentação do Krita tem o ``|mouseleft|``, o ``|mousemiddle|``, o ``|" "mousescroll|`` e o ``|mouseright|``, os quais serão transformados em |" "mouseleft|, |mousemiddle|, |mousescroll| e |mouseright| respectivamente. " "Estes são definidos no 'conf.py' do Sphinx, sendo adicionados a cada " "ficheiro .rst." #: ../../contributors_manual/krita_manual_conventions.rst:206 msgid "" "For links, if you reuse the same link over and over, you can write something " "like the following at the end of the file::" msgstr "" "Para as ligações, caso reutilize a mesma ligação uma e outra vez, poderá " "escrever algo como se segue no fim do ficheiro::" #: ../../contributors_manual/krita_manual_conventions.rst:208 msgid "" ".. _bugzilla: https://bugs.kde.org/\n" ".. _Krita Manual: https://docs.krita.org/" msgstr "" ".. _bugzilla: https://bugs.kde.org/\n" ".. _Manual do Krita: https://docs.krita.org/" #: ../../contributors_manual/krita_manual_conventions.rst:211 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\"." msgstr "" "Então, ao escrever uma ligação, poderá simplesmente usar ```bugzilla`_`` " "para se ligar ao Bugzilla, usando o \"bugzilla\" como texto para a ligação. " "O ```Krita Manual`_`` irá por seu turno ligar ao docs.krita.org com o texto " "\"Krita Manual\" (Manual do Krita)." #: ../../contributors_manual/krita_manual_conventions.rst:214 msgid "Lists" msgstr "Listas" #: ../../contributors_manual/krita_manual_conventions.rst:217 msgid "Ordinated lists" msgstr "Listas ordenadas" #: ../../contributors_manual/krita_manual_conventions.rst:219 msgid "Apple" msgstr "Maçã" #: ../../contributors_manual/krita_manual_conventions.rst:220 msgid "Pear" msgstr "Pêra" #: ../../contributors_manual/krita_manual_conventions.rst:221 msgid "Banana" msgstr "Banana" #: ../../contributors_manual/krita_manual_conventions.rst:223 msgid "Or..." msgstr "Ou..." #: ../../contributors_manual/krita_manual_conventions.rst:225 msgid "Table" msgstr "Mesa" #: ../../contributors_manual/krita_manual_conventions.rst:226 msgid "Chair" msgstr "Cadeira" #: ../../contributors_manual/krita_manual_conventions.rst:227 msgid "Wardrobe." msgstr "Roupeiro." #: ../../contributors_manual/krita_manual_conventions.rst:229 msgid "Augustus" msgstr "Augusto" #: ../../contributors_manual/krita_manual_conventions.rst:230 msgid "Nero" msgstr "Nero" #: ../../contributors_manual/krita_manual_conventions.rst:231 msgid "Caligula" msgstr "Calígula" #: ../../contributors_manual/krita_manual_conventions.rst:232 msgid "Trajan" msgstr "Trajão" #: ../../contributors_manual/krita_manual_conventions.rst:234 msgid "They can be defined as follows::" msgstr "Eles poderão ser definidos como se segue:" #: ../../contributors_manual/krita_manual_conventions.rst:236 msgid "" "1. Apple\n" "2. Pear\n" "3. Banana\n" "\n" "#. Apple\n" "#. Pear\n" "#. Banana\n" "\n" "A. Table\n" "B. Chair\n" "C. Wardrobe\n" "\n" "A. Table\n" "#. Chair\n" "#. Wardrobe\n" "\n" "I. Augustus\n" "#. Nero\n" "#. Caligula\n" "#. Trajan" msgstr "" "1. Maçã\n" "2. Pêra\n" "3. Banana\n" "\n" "#. Maçã\n" "#. Pêra\n" "#. Banana\n" "\n" "A. Mesa\n" "B. Cadeira\n" "C. Armário\n" "\n" "A. Mesa\n" "#. Cadeira\n" "#. Armário\n" "\n" "I. Augusto\n" "#. Nero\n" "#. Calígula\n" "#. Trajão" #: ../../contributors_manual/krita_manual_conventions.rst:258 msgid "Unordered lists" msgstr "Listas não-ordenadas" #: ../../contributors_manual/krita_manual_conventions.rst:260 msgid "red" msgstr "vermelho" #: ../../contributors_manual/krita_manual_conventions.rst:261 msgid "yellow" msgstr "amarelo" #: ../../contributors_manual/krita_manual_conventions.rst:263 msgid "seagreen" msgstr "verde-marinho" #: ../../contributors_manual/krita_manual_conventions.rst:264 msgid "verdigris" msgstr "verde-acinzentado" #: ../../contributors_manual/krita_manual_conventions.rst:265 msgid "teal" msgstr "azul-esverdeado" #: ../../contributors_manual/krita_manual_conventions.rst:266 msgid "viridian" msgstr "veridiano" #: ../../contributors_manual/krita_manual_conventions.rst:268 msgid "dark emerald" msgstr "esmeralda escuro" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "green" msgstr "verde" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "emerald" msgstr "esmeralda" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "light emerald" msgstr "esmeralda claro" #: ../../contributors_manual/krita_manual_conventions.rst:270 msgid "very light emerald." msgstr "esmeralda muito claro." #: ../../contributors_manual/krita_manual_conventions.rst:271 msgid "blue" msgstr "azul" #: ../../contributors_manual/krita_manual_conventions.rst:273 msgid "Defined as such::" msgstr "Definido como tal::" #: ../../contributors_manual/krita_manual_conventions.rst:275 msgid "" "- red\n" "- yellow\n" "- green\n" " - seagreen\n" " - verdigris\n" " - teal\n" " - viridian\n" " - emerald\n" " - dark emerald\n" " - light emerald\n" " - very light emerald.\n" "- blue" msgstr "" "- vermelho\n" "- amarelo\n" "- verde\n" " - verde-marinho\n" " - verde-acinzentado\n" " - turquesa\n" " - esverdeado\n" " - esmeralda\n" " - esmeralda escuro\n" " - esmeralda claro\n" " - esmeralda muito claro.\n" "- azul" #: ../../contributors_manual/krita_manual_conventions.rst:289 msgid "Definition Lists" msgstr "Listas de Definições" #: ../../contributors_manual/krita_manual_conventions.rst:291 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." msgstr "" "Um favorito! As listas de definições são especialmente úteis ao lidar com a " "enumeração de todas as opções numa área acoplável e ao tentar adicionar uma " "explicação simples atrás delas." #: ../../contributors_manual/krita_manual_conventions.rst:293 msgid "Definition" msgstr "Definição" #: ../../contributors_manual/krita_manual_conventions.rst:294 #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Explanation." msgstr "Explicação." #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Another option" msgstr "Outra opção" #: ../../contributors_manual/krita_manual_conventions.rst:299 msgid "You can make them like this::" msgstr "Podê-las-á criar da seguinte forma:" #: ../../contributors_manual/krita_manual_conventions.rst:301 msgid "" "Definition\n" " Explanation.\n" "Another option\n" " Explanation." msgstr "" "Definição\n" " Explicação.\n" "Outra opção\n" " Explicação." #: ../../contributors_manual/krita_manual_conventions.rst:304 msgid "To make them." msgstr "Para criá-las." #: ../../contributors_manual/krita_manual_conventions.rst:307 msgid "Tables" msgstr "Tabelas" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Purpose" msgstr "Objectivo" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Table type" msgstr "Tipo de tabela" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "listing shortcuts" msgstr "listagem de atalhos" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "Simple table" msgstr "Tabela simples" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "lots of colspans" msgstr "bastantes extensões de colunas" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "Grid table" msgstr "Tabela em grelha" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "Simple but long" msgstr "Simples mas comprida" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "List Table" msgstr "Tabela de Listagem" #: ../../contributors_manual/krita_manual_conventions.rst:317 msgid "Done as follows::" msgstr "Feita da seguinte forma::" #: ../../contributors_manual/krita_manual_conventions.rst:319 msgid "" "================== ============\n" "Purpose Table type\n" "================== ============\n" "listing shortcuts Simple table\n" "lots of colspans Grid table\n" "Simple but long List Table\n" "================== ============\n" "\n" "+-----------------+------------+\n" "|Purpose |Table Type |\n" "+=================+============+\n" "|listing shortcuts|Simple table|\n" "+-----------------+------------+\n" "|lots of colspans |Grid table |\n" "+-----------------+------------+\n" "|Simple but long |List table |\n" "+-----------------+------------+\n" "\n" ".. list-table::\n" " :header-rows: 1\n" "\n" " - * Purpose\n" " * Table Type\n" " - * listing shortcuts\n" " * simple table\n" " - * lots of colspans\n" " * grid table\n" " - * simple but long\n" " * list table" msgstr "" "================== ============\n" "Objectivo Tipo de tabela\n" "================== ============\n" "lista de atalhos Tabela simples\n" "vários 'colspans' Grelha\n" "Simples mas longo Tabela em lista\n" "================== ============\n" "\n" "+-----------------+---------------+\n" "|Objectivo |Tipo de Tabela |\n" "+=================+===============+\n" "|lista de atalhos |Tabela simples |\n" "+-----------------+---------------+\n" "|vários 'colspans'|Grelha |\n" "+-----------------+---------------+\n" "|Simples mas longo|Tabela em lista|\n" "+-----------------+---------------+\n" "\n" ".. list-table::\n" " :header-rows: 1\n" "\n" " - * Objectivo\n" " * Tipo de Tabela\n" " - * lista de atalhos\n" " * tabela simples\n" " - * vários 'colspans'\n" " * grelha\n" " - * simples mas longo\n" " * tabela em lista" #: ../../contributors_manual/krita_manual_conventions.rst:349 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." msgstr "" "As tabelas de grelha completa são melhores quando precisa de todas as " "funcionalidades, como a expansão para árias linhas e colunas, mas são " "difíceis de criar. Por essa razão, as tabelas pequenas são melhores se forem " "criadas com a sintaxe simples, enquanto as tabelas realmente grandes são " "mais fáceis de criar com uma directiva de lista, porque é muito mais fácil " "de escrever e manter." #: ../../contributors_manual/krita_manual_conventions.rst:352 msgid "Admonishments and asides" msgstr "Advertências e notas laterais" #: ../../contributors_manual/krita_manual_conventions.rst:356 msgid "" "Admonishments are sort of like a separate section that the reader needs to " "pay attention to." msgstr "" "As advertências são uma espécie de secção separada que o leitor precisa de " "prestar atenção." #: ../../contributors_manual/krita_manual_conventions.rst:358 msgid "" "Admonishments that can be used are the following (in order of seriousness):" msgstr "" "As advertências que poderão ser usadas são as seguintes (por ordem de " "severidade):" #: ../../contributors_manual/krita_manual_conventions.rst:362 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\"." msgstr "" "As dicas são úteis para nos dar um pouco mais de informações sobre um tópico " "que é útil no texto principal. Por exemplo, \"Estes pacotes têm diferentes " "nomes no openSuse versus Debian\"." #: ../../contributors_manual/krita_manual_conventions.rst:366 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\"." msgstr "" "A documentação extra sobre como fazer algo, como por exemplo, se \"Pode " "fazer um modelo da sua configuração favorita de documentos\", ou \"Use o 'm' " "para criar uma espelho da área de desenho e veja os erros mais facilmente no " "seu desenho\"." #: ../../contributors_manual/krita_manual_conventions.rst:370 msgid "Something that is important to note, but is not necessarily negative." msgstr "" "Algo que é bastante importante de anotar, mas que não é necessariamente " "negativo." #: ../../contributors_manual/krita_manual_conventions.rst:374 msgid "This is in general when something is negative." msgstr "Isto é usado na generalidade em que algo é negativo." #: ../../contributors_manual/krita_manual_conventions.rst:378 msgid "" "General attention grabber. Use this when the subject is more important than " "warning, but not as important that is could get a dataloss." msgstr "" "Chamada de atenção geral. Use isto quando o assunto é mais importante que o " "aviso, mas não é tão importante que possa provocar uma perda de dados." #: ../../contributors_manual/krita_manual_conventions.rst:382 msgid "" "This is for things that could cause dataloss, like forgetting to save, or " "that Python currently has no undo functionality." msgstr "" "Isto serve para as coisas que possam provocar a perda de dados, como se " "esquecer de gravar ou que o Python não tem de momento nenhuma funcionalidade " "para desfazer." #: ../../contributors_manual/krita_manual_conventions.rst:386 msgid "" "This should be for things that are dangerous for the computer in general, " "this includes things that can cause out of memory style freezes." msgstr "" "Isto deverá servir para coisas que sejam perigosas para o computador de um " "modo geral; isto inclui coisas que possam provocar bloqueios p.ex. por falta " "de memória." #: ../../contributors_manual/krita_manual_conventions.rst:390 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." msgstr "" "Isto provavelmente não é relevante para um manual. O Sphinx pode criar estes " "manualmente em algumas situações, mas a nossa configuração não o faz por " "omissão." #: ../../contributors_manual/krita_manual_conventions.rst:392 msgid "Generic admonition that can have any text" msgstr "Admoestação genérica que poderá ter qualquer texto" #: ../../contributors_manual/krita_manual_conventions.rst:394 msgid "Text." msgstr "Texto." #: ../../contributors_manual/krita_manual_conventions.rst:396 msgid "You can make it like this::" msgstr "Podê-las-á criar da seguinte forma::" #: ../../contributors_manual/krita_manual_conventions.rst:398 msgid "" ".. admonition:: Generic admonition that can have any text\n" "\n" " Text." msgstr "" ".. admonition:: Admoestação genérica que poderá ter qualquer texto.\n" "\n" " Texto." #: ../../contributors_manual/krita_manual_conventions.rst:404 msgid "Sphinx also adds::" msgstr "O Sphinx também adiciona::" #: ../../contributors_manual/krita_manual_conventions.rst:406 msgid "" ".. seealso::\n" "\n" " Which is useful to collect external links and references." msgstr "" ".. seealso::\n" " O que é útil para recolher as referências e ligações externas." #: ../../contributors_manual/krita_manual_conventions.rst:414 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." msgstr "" "As réguas horizontais são normalmente usadas quando o tópico muda de forma " "bastante directa. Isto é muito comum nas escritas mais baseadas na " "narrativa, como as histórias e a ficção. O manual do Krita é mais " "instrutório e escrita de estilos de referência, o que significa que " "normalmente não contamos nenhuma história longa sobre os diferentes " "elementos se combinaram, mas sim algumas histórias longas que sirvam para " "dar o motivo para certos passos serem dados de determinada forma. As " "mudanças de tópico normalmente acontecem porque vamos passar para uma nova " "secção, em vez de nos associarmos a uma secção relacionada. Como tal, é " "melhor usar cabeçalhos e a directiva `.. Topic::``. Os cabeçalhos também são " "mais fáceis de ler." #: ../../contributors_manual/krita_manual_conventions.rst:418 msgid "That said, horizontal rulers can be made with ``----``." msgstr "Posto isto, as réguas horizontais podem ser criadas com o ``----``." #: ../../contributors_manual/krita_manual_conventions.rst:421 msgid "The rubric directive" msgstr "A directiva 'rubric'" #: ../../contributors_manual/krita_manual_conventions.rst:422 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::" msgstr "" "A directiva 'rubric' é uma directiva de cabeçalho que à primeira vista " "parece um \"tópico\", mas onde o tópico se encontra por vários parágrafos; o " "'rubric' em si só lida com o cabeçalho, como por exemplo::" #: ../../contributors_manual/krita_manual_conventions.rst:424 msgid ".. rubric:: The rubric directive" msgstr ".. rubric:: A directiva de rubrica" #: ../../contributors_manual/krita_manual_conventions.rst:428 msgid "So, when to use these?" msgstr "Por isso, quando devem ser usados?" #: ../../contributors_manual/krita_manual_conventions.rst:429 msgid "" "Only use them when you think the subject is too minor to have a proper " "heading." msgstr "" "Use-os apenas quando achar que o assunto é demasiado pequeno para ter um " "cabeçalho adequado." #: ../../contributors_manual/krita_manual_conventions.rst:431 msgid "Topic" msgstr "Tópico" #: ../../contributors_manual/krita_manual_conventions.rst:432 msgid "" "When the text is separated from the flow, so it goes into a different " "subject than the text itself is naturally going to." msgstr "" "Quando o texto está separado do fluxo, porque que vai para um assunto " "diferente do texto de destino." #: ../../contributors_manual/krita_manual_conventions.rst:433 msgid "Rubric" msgstr "Rubrica" #: ../../contributors_manual/krita_manual_conventions.rst:434 msgid "" "When the text isn't separated from the flow, but it does not need a header " "either." msgstr "" "Quando o texto não está separado do fluxo, mas também não precisa de um " "cabeçalho para si." #: ../../contributors_manual/krita_manual_conventions.rst:436 msgid "Admonishments" msgstr "Advertências" #: ../../contributors_manual/krita_manual_conventions.rst:436 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." msgstr "" "Só quando são adequadas a nível semântico. Isto é especialmente necessário " "para as advertências de perigo e aviso, dado que as ver com frequência " "poderá tornar os utilizadores mais insensíveis a elas." #: ../../contributors_manual/krita_manual_conventions.rst:439 msgid "Code Snippets" msgstr "Excertos de Código" #: ../../contributors_manual/krita_manual_conventions.rst:441 msgid "``Inline code snippets`` are done with ````backticks````." msgstr "" "Os ``excertos de código incorporados`` são feitos com plicas invertidas " "````backticks````." #: ../../contributors_manual/krita_manual_conventions.rst:443 msgid "" "Multi-line code snippets are done by ending the previous section with ``::" "``, which'll look like this::" msgstr "" "Os excertos de código em várias linhas são feitos ao terminar a secção " "anterior com ``::``, o que se parecerá com o seguinte::" #: ../../contributors_manual/krita_manual_conventions.rst:445 msgid "" "This is a paragraph, and we define a preformated snippet like so::\n" "\n" " Be sure to add a white space and a tab afterwards before starting the " "snippet." msgstr "" "Isto é um parágrafo, e definimos um excerto pré-formatado da seguinte " "forma::\n" "\n" " Certifique-se que adiciona um espaço em branco e uma tabulação a seguir " "antes de iniciar o excerto." #: ../../contributors_manual/krita_manual_conventions.rst:449 msgid "" "You can also use the ``.. code::`` directive. If you add the language name " "after it, it'll do the appropriate syntax highlighting::" msgstr "" "Também poderá usar a directiva ``.. code::``. Se adicionar o nome da " "linguagem a seguir, irá aplicar o realce de sintaxe apropriado::" #: ../../contributors_manual/krita_manual_conventions.rst:451 msgid "" ".. code:: python\n" "\n" " # Python comment\n" " def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" ".. code:: python\n" " # comentário\n" " def minha_funcao():\n" " lista = []\n" " lista.append(1)\n" " texto = \"olá mundo\"" #: ../../contributors_manual/krita_manual_conventions.rst:459 msgid "Becomes" msgstr "Torna-se" #: ../../contributors_manual/krita_manual_conventions.rst:468 msgid "" "# Python comment\n" "def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" "# Comentário de Python\n" "def minha_funcao():\n" " lista = []\n" " lista.append(1)\n" " texto = \"olá mundo\"" #: ../../contributors_manual/krita_manual_conventions.rst:469 msgid "some more..." msgstr "mais alguns..." #: ../../contributors_manual/krita_manual_conventions.rst:483 msgid "" "// C++ comment\n" "int myFunction(int i) {\n" " i += 1;\n" "\n" " // Check if more than 12\n" " if (i>12) {\n" " i = 0;\n" " }\n" " return i;\n" "}" msgstr "" "// Comentário de C++\n" "int minhaFuncao(int i) {\n" " i += 1;\n" "\n" " // Verificar se é maior que 12\n" " if (i>12) {\n" " i = 0;\n" " }\n" " return i;\n" "}" #: ../../contributors_manual/krita_manual_conventions.rst:498 msgid "" "/* CSS comment */\n" "body {\n" " margin: 0 auto;\n" " /* is 800 still sensible? */\n" " max-width:800px;\n" " font-size:16px;\n" " color:#333;\n" " background-color: #eee;\n" " padding:1em;\n" " font-family:serif;\n" " line-height: 1.4;\n" "}" msgstr "" "/* Comentário de CSS */\n" "body {\n" " margin: 0 auto;\n" " /* 800 ainda faz sentido? */\n" " max-width:800px;\n" " font-size:16px;\n" " color:#333;\n" " background-color: #eee;\n" " padding:1em;\n" " font-family:serif;\n" " line-height: 1.4;\n" "}" #: ../../contributors_manual/krita_manual_conventions.rst:502 msgid "" "

this is " "a paragraph.

" msgstr "" "

isto é um parágrafo.

" #: ../../contributors_manual/krita_manual_conventions.rst:504 msgid "Other preformatted text" msgstr "Outro texto pré-formatado" #: ../../contributors_manual/krita_manual_conventions.rst:507 msgid "One can" msgstr "Uma pessoa pode" #: ../../contributors_manual/krita_manual_conventions.rst:508 msgid "preformat" msgstr "pré-formatar" #: ../../contributors_manual/krita_manual_conventions.rst:509 msgid "text by" msgstr "texto se" #: ../../contributors_manual/krita_manual_conventions.rst:510 msgid "prepending" msgstr "anteceder" #: ../../contributors_manual/krita_manual_conventions.rst:511 msgid "each line" msgstr "cada linha" #: ../../contributors_manual/krita_manual_conventions.rst:512 msgid "with a pipe" msgstr "com um símbolo" #: ../../contributors_manual/krita_manual_conventions.rst:513 msgid "symbol" msgstr "de barra vertical ('pipe')" #: ../../contributors_manual/krita_manual_conventions.rst:515 msgid "Like so::" msgstr "Como o seguinte:" #: ../../contributors_manual/krita_manual_conventions.rst:517 msgid "" "| One can\n" "| preformat\n" "| text by\n" "| prepending\n" "| each line\n" "| with a pipe\n" "| symbol" msgstr "" "| Uma pessoa\n" "| pode pré-formatar\n" "| texto se\n" "| anteceder\n" "| cada linha\n" "| com um símbolo\n" "| de barra vertical" #: ../../contributors_manual/krita_manual_conventions.rst:525 msgid "We don't actually use this anywhere in the manual." msgstr "Não usamos de facto isto mais no manual." #: ../../contributors_manual/krita_manual_conventions.rst:528 msgid "Glossaries, Terms and Index" msgstr "Glossários, Termos e Índice" #: ../../contributors_manual/krita_manual_conventions.rst:530 msgid "These are sphinx features." msgstr "Estas são funcionalidades do Sphinx." #: ../../contributors_manual/krita_manual_conventions.rst:532 msgid "" "Index is used in the top section, right now only single index entries are " "used." msgstr "" "O índice é usado na secção de topo; de momento, agora só são usados itens " "simples de índice." #: ../../contributors_manual/krita_manual_conventions.rst:534 msgid "" "Glossaries are used for some of the menu entry sections, but not all of them." msgstr "" "Os glossários são usados para algumas das secções de itens do menu, mas não " "para todas." #: ../../contributors_manual/krita_manual_conventions.rst:537 msgid "Quotes" msgstr "Citações" #: ../../contributors_manual/krita_manual_conventions.rst:539 msgid "Quotes are done like this::" msgstr "As citações são feitas da seguinte forma::" #: ../../contributors_manual/krita_manual_conventions.rst:541 msgid "" "I am not sure why you'd need quotes in a user manual...\n" "\n" "-- Wolthera" msgstr "" "Não tenho a certeza porque irá precisar de citações num manual do " "utilizador...\n" "\n" "-- Wolthera" #: ../../contributors_manual/krita_manual_conventions.rst:545 msgid "This becomes a blockquote." msgstr "Isto torna-se uma citação em bloco." #: ../../contributors_manual/krita_manual_conventions.rst:547 msgid "I am not sure why you'd need quotes in a user manual..." msgstr "" "Não tenho a certeza porque irá precisar de citações num manual do " "utilizador..." #: ../../contributors_manual/krita_manual_conventions.rst:551 msgid "" "We do actually use quotes in some places. Try to add a link to the name to " "define where it came from." msgstr "" "De facto usamos citações em alguns pontos. Tente adicionar uma ligação ao " "nome para definir de onde vem." #: ../../contributors_manual/krita_manual_conventions.rst:552 msgid "Wolthera" msgstr "Wolthera" diff --git a/locale/pt_PT/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po b/locale/pt_PT/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po index 43b27984f..5c748079b 100644 --- a/locale/pt_PT/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po +++ b/locale/pt_PT/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po @@ -1,1523 +1,1523 @@ # SOME DESCRIPTIVE TITLE. # 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 , YEAR. # msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-08 03:08+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: 2019-08-03 14:25+0100\n" "Last-Translator: José Nuno Coelho Pires \n" "Language-Team: Portuguese \n" "Language: pt\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" "X-POFile-IgnoreConsistency: Blender\n" "X-POFile-SpellExtra: OCIO en LUT HDR workflowwebcomic menuselection\n" "X-POFile-SpellExtra: Argylcms colormanagementgroup Nuke lutdocker images\n" "X-POFile-SpellExtra: srgbtrc MyPaint KritaHDR TRC workflowtext CMYK CIEXYZ\n" "X-POFile-SpellExtra: Studio rec Kikimatrixprofile ref image cLUT\n" "X-POFile-SpellExtra: workflowgames Artrage Illustrator Photoshop ICC\n" "X-POFile-SpellExtra: Scribus NVidia workflowprint elle colormanaged icc\n" "X-POFile-SpellExtra: infogramas Viewer LED workflowkritatext Painttool\n" "X-POFile-SpellExtra: colorcategory LUTManagementDocker Krita Photo XYZ\n" "X-POFile-SpellExtra: Paintstorm Natron KikicLUTprofiles sRGB cerúleo\n" "X-POFile-SpellExtra: Blender Inkscape lcms guilabel númeroversão\n" "X-POFile-SpellExtra: RawTheraphee VFX digiKam datafiles Look pngcrush Up\n" "X-POFile-SpellExtra: lut colormanagement Color up JPG optimizadores\n" "X-POFile-SpellExtra: Digikam Table dockers Rec\n" +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_matrix_profile.png" +msgstr ".. image:: images/color_category/Kiki_matrix_profile.png" + +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" +msgstr ".. image:: images/color_category/Kiki_cLUTprofiles.png" + #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group1.png" msgstr ".. image:: images/color_category/Krita_2_9_colormanagement_group1.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group2.png" msgstr ".. image:: images/color_category/Krita_2_9_colormanagement_group2.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group3.png" msgstr ".. image:: images/color_category/Krita_2_9_colormanagement_group3.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group4.png" msgstr ".. image:: images/color_category/Krita_2_9_colormanagement_group4.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/dockers/LUT_Management_Docker.png" msgstr ".. image:: images/dockers/LUT_Management_Docker.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR_1.svg" msgstr ".. image:: images/color_category/Krita_HDR_1.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR2.svg" msgstr ".. image:: images/color_category/Krita_HDR2.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_webcomic.svg" msgstr "" ".. image:: images/color_category/Krita-colormanaged-workflow_webcomic.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_print.svg" msgstr ".. image:: images/color_category/Krita-colormanaged-workflow_print.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_games.svg" msgstr ".. image:: images/color_category/Krita-colormanaged-workflow_games.svg" -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_matrix_profile.png" -msgstr ".. image:: images/color_category/Kiki_matrix_profile.png" - -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" -msgstr ".. image:: images/color_category/Kiki_cLUTprofiles.png" - #: ../../general_concepts/colors/color_managed_workflow.rst:1 msgid "How a color managed workflow works." msgstr "Como funciona um processo gerido por cores." #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "Color" msgstr "Cor" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "Color Management" msgstr "Gestão de Cores" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "ICC Profiles" msgstr "Perfis de ICC" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "OCIO" msgstr "OCIO" #: ../../general_concepts/colors/color_managed_workflow.rst:17 msgid "Color Managed Workflow" msgstr "Processos Geridos por Cores" #: ../../general_concepts/colors/color_managed_workflow.rst:19 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." msgstr "" "Poderá ter ouvido falar que o Krita tem algo chamado de gestão de cores. Ou " "provavelmente poderá ter pensado o que são essas coisas de 'modelos de " "cores' e 'perfis de cores' que encontra nos menus. A gestão de cores é " "bastante útil para as pessoas que trabalham profissionalmente nas imagens " "digitais, e felizmente esta página irá explicar porquê." #: ../../general_concepts/colors/color_managed_workflow.rst:22 msgid "Basic Info" msgstr "Informação Básica" #: ../../general_concepts/colors/color_managed_workflow.rst:24 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." msgstr "" "Se nunca tiver trabalhado anteriormente com a gestão de cores, e não fizer a " "menor ideia o que é, então é porque provavelmente tem estado a trabalhar no " "espaço de cores RGB de 8 bits com o perfil sRGB. Isto significa que poderá " "escolher o *sRGB incorporado* ou o *sRGB-elle-v2-srgbtrc.icc*. Com o novo " "selector de espaços de cores, este perfil está marcado como *(predefinição)* " "ao usar os 8 bits." #: ../../general_concepts/colors/color_managed_workflow.rst:26 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." msgstr "" "Iremos ver o que significam estes termos em teoria, mas se estiver aqui só " "para tentar perceber qual é o predefinido, agora já sabe. Talvez, depois de " "ler isto, se possa sentir como se estiver a alterar a predefinição, para " "obter resultados novos e interessantes dos filtros, modos de mistura ou " "simplesmente o pincel de manchas a cores." #: ../../general_concepts/colors/color_managed_workflow.rst:29 msgid "What is the problem?" msgstr "Qual é o problema?" #: ../../general_concepts/colors/color_managed_workflow.rst:31 msgid "" "To explain the point of color management, you'd first need to learn which " "problem color management tries to solve." msgstr "" "Para explicar o objectivo da gestão de cores, terá de primeiro de aprender " "qual é o problema que a gestão de cores está a tentar resolver." #: ../../general_concepts/colors/color_managed_workflow.rst:33 msgid "Let us imagine a kinder garden:" msgstr "Imaginemos um infantário:" #: ../../general_concepts/colors/color_managed_workflow.rst:35 msgid "" "The class of 28 children is subdivided in groups of 7. Each group has its " "own table." msgstr "" "A turma de 28 crianças está dividida em grupos de 7. Cada grupo tem a sua " "própria mesa." #: ../../general_concepts/colors/color_managed_workflow.rst:37 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." msgstr "" "O professor deu-lhes uma tarefa de pintura: Elas precisam de pintar um " "triângulo vermelho, um quadrado azul, um círculo verde e colocar um contorno " "amarelo em torno dos três. As crianças já são muito experientes com a " "pintura, pelo que o professor pode deixar os mais inteligentes à confiança " "com os seus próprios dispositivos, gastando mais tempo com os que precisam " "de ajuda." #: ../../general_concepts/colors/color_managed_workflow.rst:40 msgid "The following results come from painting:" msgstr "Os seguintes resultados vêm da pintura:" #: ../../general_concepts/colors/color_managed_workflow.rst:42 msgid "" "Even though all groups had the same assignment, each group's result looks " "different." msgstr "" "Ainda que todos os grupos tenham a mesma tarefa, o resultado de cada grupo " "parece diferente." #: ../../general_concepts/colors/color_managed_workflow.rst:49 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." msgstr "" "O grupo 1 tem vermelhão, amarelo cítrico e azul ultramarino ao seu dispor. " "Isto significa que o seu triângulo parece bonito e vermelho, mas o verde do " "círculo deles está feito. Isto é porque o ultramarino é um azul demasiado " "escuro para criar verdes bonitos com ele." #: ../../general_concepts/colors/color_managed_workflow.rst:56 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." msgstr "" "O grupo 2 tem um vermelho magenta, um amarelo cítrico e um azul cerúleo. O " "magenta é um tipo de vermelho que se aproxima mais do rosa, em oposição ao " "vermelhão, que é mais próximo do laranja. Contudo, o verde deles parece " "melhor porque o cerúleo é um azul muito mais claro." #: ../../general_concepts/colors/color_managed_workflow.rst:64 msgid "" "Group 3 had vermillion red, citron yellow, emerald green and cerulean blue. " "They didn't mix their green, and thus ended up with a purer color." msgstr "" "O grupo 3 tinha o vermelhão, o amarelo cítrico, o verde esmeralda e o azul " "cerúleo. Não misturaram o verde deles, e por isso ficaram com um verde mais " "puro." #: ../../general_concepts/colors/color_managed_workflow.rst:71 msgid "" "Finally, group 4 has vermillion red, citron yellow and cerulean blue. Their " "colors probably look like what you imagined." msgstr "" "Finalmente, o grupo 4 tinha o vermelhão, o amarelo cítrico e o azul cerúleo. " "As cores deles provavelmente pareciam-se mais com o que tinha imaginado." #: ../../general_concepts/colors/color_managed_workflow.rst:73 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!" msgstr "" "Agora, eles são alunos de infantário, pelo que isto não será um grande " "problema para o mundo. Contudo, imagine que algo como isto se passava numa " "empresa de impressões? Imagine quatro impressoras a imprimir a mesma revista " "com resultados radicalmente diferentes? Isso seria um desastre!" #: ../../general_concepts/colors/color_managed_workflow.rst:75 msgid "For this purpose, we invented color management." msgstr "Para esse fim, inventámos a gestão de cores." #: ../../general_concepts/colors/color_managed_workflow.rst:78 msgid "What is color management?" msgstr "O que é a gestão de cores?" #: ../../general_concepts/colors/color_managed_workflow.rst:80 msgid "" "Color management is, dryly put, a set of systems that tries to have the same " "color translate properly between color devices." msgstr "" "A gestão de cores é, por assim dizer, um conjunto de sistemas que tentam ter " "a mesma cor a ser traduzida de forma adequada entre os dispositivos a cores." #: ../../general_concepts/colors/color_managed_workflow.rst:82 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." msgstr "" "Normalmente funciona ao tentar converter uma cor para o espaço de referência " "de cores XYZ. O XYZ é um sistema de coordenadas que tem um ponto para todas " "as cores que o olho humano consegue ver." #: ../../general_concepts/colors/color_managed_workflow.rst:84 msgid "" "From XYZ it can then be translated back into another device space, such as " "RGB (for screens), or CMYK (for printers)." msgstr "" "A partir do XYZ, poderá então ser traduzido para outro espaço do " "dispositivo, como o RGB (para os ecrãs) ou o CMYK (para as impressoras)." #: ../../general_concepts/colors/color_managed_workflow.rst:86 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." msgstr "" "O Krita tem dois sistemas dedicados à gestão de cores. Por um lado, temos o " "**lcms2**, que lida com os perfis ICC, e por outro temos o **OCIO**, que " "lida com a gestão de cores por LUT's." #: ../../general_concepts/colors/color_managed_workflow.rst:88 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." msgstr "" "Para dar uma estimativa por alto, os perfis de ICC lidam com a manutenção " "das cores consistentes centre as várias interpretações dos dispositivos " "(ecrãs, impressoras), usando um espaço de referência, e o OCIO lida com a " "manipulação da interpretação dessas cores." #: ../../general_concepts/colors/color_managed_workflow.rst:90 msgid "Within both we can identify the following color spaces:" msgstr "Dentro de ambos, podemos identificar os seguintes espaços de cores:" #: ../../general_concepts/colors/color_managed_workflow.rst:93 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 " "`." msgstr "" "Os espaços de dispositivos são os que descrevem o seu monitor, e terão de " "ser criados com um pequeno dispositivo chamado de \"colorímetro\". Este " "dispositivo, em conjunto com a aplicação correcta, mede o valor mais forte " "de vermelho, verde e azul que o seu ecrã consegue produzir, assim como o " "branco, preto e cinzento que produz. Ao usar esta e outras medidas, irá " "criar um perfil ICC único para o seu ecrã. Poderá configurar estes na página " "de gestão de cores do Krita. Por omissão, assumimos o sRGB para os ecrãs, " "mas é muito provável que o seu ecrã não se ajuste perfeitamente ao sRGB, " "especialmente se tiver um ecrã de alta qualidade, onde poderá ter um espaço " "ainda maior. Os espaços dos dispositivos são também a razão pela qual deverá " "consultar primeiro com a sua impressora o perfil que ela está à espera. " "Muitas casas de impressão têm os seus próprios perfis de dispositivos para " "as suas impressoras, ou poderão preferir fazer eles mesmos a conversão de " "cores. Poderá ler mais sobre a utilização do colorímetro :ref:`aqui " "`." #: ../../general_concepts/colors/color_managed_workflow.rst:94 msgid "Device spaces" msgstr "Espaços do dispositivo" #: ../../general_concepts/colors/color_managed_workflow.rst:96 msgid "Working spaces" msgstr "Espaços de trabalho" #: ../../general_concepts/colors/color_managed_workflow.rst:97 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." msgstr "" "Estes são entregues em conjunto com o Krita para o ICC, e podem ser " "transferidos a partir da página Web do OCIO para o OCIO. Os espaços de " "trabalho são particularmente bons para fazer os cálculos de cores neles, os " "quais os programas como o Krita fazem com frequência. Como tal, é altamente " "recomendado que tenha um perfil do espaço de trabalho para a sua imagem." #: ../../general_concepts/colors/color_managed_workflow.rst:99 msgid "Aesthetic or Look spaces" msgstr "Espaços estéticos ou de aparência" #: ../../general_concepts/colors/color_managed_workflow.rst:99 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." msgstr "" "Estes são espaços especiais que foram deformados para dar um dado aspecto a " "uma imagem. O Krita não oferece perfis de aparência no ICC, nem suporta " "espaços de aparência ainda no OCIO." #: ../../general_concepts/colors/color_managed_workflow.rst:102 msgid "Color managed workflow" msgstr "Processo gerido pela cor" #: ../../general_concepts/colors/color_managed_workflow.rst:104 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:" msgstr "" "Saber algo sobre estes espaços não lhe dá uma ideia de como usá-los, mas " "torna mais fácil explicar como os usar. Como tal, vejamos um processo de " "gestão de cores típico:" #: ../../general_concepts/colors/color_managed_workflow.rst:110 msgid ".. image:: images/color_category/Krita-colormanaged-workflow_text.svg" msgstr ".. image:: images/color_category/Krita-colormanaged-workflow_text.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:110 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." msgstr "" "Um exemplo típico de um processo de gestão de cores. Temos dados " "provenientes de 'scanners' e máquinas fotográficas, os quais são convertidos " "para um espaço de trabalho que possa ser usado entre as várias aplicações de " "edição, sendo convertidos para um espaço de saída para ver no ecrã ou para " "imprimir." #: ../../general_concepts/colors/color_managed_workflow.rst:112 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." msgstr "" "Num processo de gestão de cores tradicional, iremos pensar normalmente em " "termos de cores no mundo real a serem convertidas para cores do computador e " "vice-versa. Como tal, para algumas fotografias de exemplo de uma câmara ou " "para imagens digitalizadas. Se tiver um espaço de cores para um desses " "dispositivos, primeiro iremos atribuir o espaço desses dispositivo à imagem, " "e depois convertê-lo para um espaço de trabalho." #: ../../general_concepts/colors/color_managed_workflow.rst:114 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." msgstr "" "Depois faremos todas as nossas edições no espaço de trabalho, usando o " "espaço em questão para comunicar entre os programas de edição. No caso do " "Krita, devido ao facto de termos dois sistemas de gestão de cores, usamos os " "perfis de ICC entre os programas como o GIMP 2.9+, o Inkscape, o digiKam e o " "Scribus, e a configuração do OCIO entre o Blender e o Natron." #: ../../general_concepts/colors/color_managed_workflow.rst:116 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." msgstr "" "Também irá guardar os seus ficheiros de trabalho no espaço de trabalho, como " "iria ter as camadas não unidas no ficheiro de trabalho, ou tê-lo com uma " "resolução muito elevada." #: ../../general_concepts/colors/color_managed_workflow.rst:118 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." msgstr "" "Em alguns casos, aplicamos espaços estéticos ou de 'aparência' a uma imagem " "como parte do processo de edição. Isto é relativamente avançado e " "provavelmente não será algo com que se tenha de preocupar no caso do Krita." #: ../../general_concepts/colors/color_managed_workflow.rst:120 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." msgstr "" "Assim, quando acabarmos de editar, tentamos converter para um espaço de " "saída, que será o espaço de outro dispositivo. Este poderá ser o CMYK para " "as impressoras ou um perfil RGB especial para um ecrã. Quando estiver a " "lidar com casas de impressão profissionais, é melhor perguntar a eles sobre " "este passo. Eles têm bastante experiência em fazer a melhor conversão, e " "poderão preferir fazer a conversão a partir do seu espaço de trabalho para o " "espaço de trabalho das suas impressoras." #: ../../general_concepts/colors/color_managed_workflow.rst:122 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." msgstr "" "Outra forma de saída é a forma como o seu ecrã mostra a cor. Ao contrário " "das saídas normais, esta é feita a toda a hora durante a edição: Afinal de " "contas, precisa de ser capaz de ver o que está a fazer, mas o seu ecrã " "continua a ser um dispositivo com um espaço próprio, pelo que distorce a " "forma como aparece a imagem. Desta maneira, poderá ver o seu ecrã como um " "conjunto de binóculos que terá de usar e ver através deles para conseguir " "ver de todo a sua imagem." #: ../../general_concepts/colors/color_managed_workflow.rst:124 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." msgstr "" "Como tal, sem um monitor com um perfil, não sabe de facto como é que são as " "cores com que está a trabalhar, porque o computador não conhece as " "propriedades relevantes do seu ecrã. Como tal, se tiver criado um perfil do " "seu monitor, indique ao Krita o perfil na configuração, seleccionando o " "espaço sRGB onde desenhar, e estará pela primeira vez a ver as cores reais " "do espaço sRGB." #: ../../general_concepts/colors/color_managed_workflow.rst:127 msgid "So what does this mean?" msgstr "Então o que significa isto?" #: ../../general_concepts/colors/color_managed_workflow.rst:133 msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_krita_text.svg" msgstr "" ".. image:: images/color_category/Krita-colormanaged-workflow_krita_text.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:133 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." msgstr "" "Quando pintarmos do zero, podemos ver o perfil do nosso monitor como o " "espaço de entrada, dado que o usamos para determinar quais as cores a " "escolher. Isto de certa forma simplifica o processo, mas torna o perfil do " "ecrã e as condições de visualização mais importantes." #: ../../general_concepts/colors/color_managed_workflow.rst:135 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*." msgstr "" "Agora, os fotógrafos e as pessoas que trazem uma grande disciplina dos VFX " "chamada 'graduação de cores', ficarão completamente malucos a tentar obter " "as cores que usam e que saiam 100% correctas, e isso irá ter em conta " "factores como a hora do dia e a cor com que eles pintaram as suas paredes. " "Por exemplo, se a parede atrás do seu computador for um vermelho vivo, os " "seus olhos ajustar-se-ão para ficarem menos sensíveis ao vermelho, o que " "significa que as cores que eles escolherem no programa serão mais " "avermelhadas. Nós chamamos a isso as *condições de apresentação*." #: ../../general_concepts/colors/color_managed_workflow.rst:137 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." msgstr "" "Felizmente, os artistas têm de se preocupar um pouco menos com isso. Dado " "que as ilustrações são completamente feitas à mão, é possível identificar as " "partes importantes e criar contrastes apropriados entre cores. Isto " "significa que, mesmo que as nossas imagens se tornem um pouco mais vermelhas " "que o pretendido, é menos provável que toda a imagem tenha ficado " "danificada. Se olharmos para o nosso exemplo do infantário acima, " "continuamos a compreender ao que era suposto ficar parecida a imagem, apesar " "de existirem cores diferentes para cada imagem. Para além disso, dado que as " "cores nas ilustrações são deliberadamente escolhidas, poderemos corrigi-las " "com maior facilidade numa data posterior. Mesmo assim, ao mesmo tempo, " "obviamente que é um grande incómodo fazer isto, dado que teríamos tido muita " "mais flexibilidade se tivéssemos tido as condições de visualização em " "consideração." #: ../../general_concepts/colors/color_managed_workflow.rst:139 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." msgstr "" "Posto isto, para os artistas também é bastante útil compreender os espaços " "de trabalho. Os diferentes espaços de trabalho irão gerar resultados " "diferentes com os filtros e a mistura, e só alguns espaços de trabalho " "poderão ser usados para tecnologias avançadas, como o HDR." #: ../../general_concepts/colors/color_managed_workflow.rst:141 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." msgstr "" "De forma semelhante, o Krita, como um programa que pretende criar imagens do " "zero, não se preocupa realmente sobre a atribuição de espaços de trabalho " "depois de ter criado a imagem. Contudo, dado que está a usar o ecrã como " "binóculos para olhar para a sua imagem e para escolher cores, poderá ver o " "espaço do dispositivo do seu ecrã como um espaço de entrada para a imagem. É " "por isso que a geração do perfil do seu monitor e a atribuição do perfil ao " "Krita na configuração poderá ajudar o seu trabalho para a impressão e para " "actividades futuras a longo prazo." #: ../../general_concepts/colors/color_managed_workflow.rst:143 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.)" msgstr "" "De um modo geral, é relativamente útil manter as coisas, como as condições " "de visualização, sempre presentes na sua mente. Muitos artistas " "profissionais usam uma cor cinzenta intermédia como fundo por omissão das " "suas telas, porque concluem que criam imagens muito mais dinâmicas devido a " "ter melhorado as suas condições de visualização. Também é por isso que uma " "grande quantidade de programas gráficos, incluindo o Krita, vêm com um tema " "escuro nos dias de hoje. (Ainda que, como é óbvio, possa ser porque achem " "que os temas escuros possam ter estilo - quem sabe?)" #: ../../general_concepts/colors/color_managed_workflow.rst:148 msgid "ICC profiles" msgstr "Perfis ICC" #: ../../general_concepts/colors/color_managed_workflow.rst:150 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:" msgstr "" "Um perfil ICC é um conjunto de coordenadas que descreve as extremidades do " "espaço do dispositivo dentro do XYZ, e são os dados de gestão de cores que " "usa para comunicar o seu espaço de trabalho com as impressoras e as " "aplicações que estão desenhadas para a indústria da impressão, como o Gimp, " "o Scribus, o Photoshop, o Illustrator, o Inkscape, o Digikam, o " "RawTheraphee, etc. Tem dois tipos de perfis ICC:" #: ../../general_concepts/colors/color_managed_workflow.rst:153 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." msgstr "" "Estes são fornecidos com o Krita. Os perfis em matriz são criados através da " "definição dos parâmetros e da interpolação entre eles para obter o tamanho " "exacto do espaço de cores. Devido a este facto, o navegador do espaço de " "cores do Krita poder-lhe-á dar bastantes informações sobre estes perfis. Os " "perfis em questão também são preferíveis como espaços de trabalho." #: ../../general_concepts/colors/color_managed_workflow.rst:159 msgid "Matrix Shaper profiles" msgstr "Perfis em Forma de Matriz" #: ../../general_concepts/colors/color_managed_workflow.rst:159 msgid "" "Matrix shaper profiles have a few parameters that describe the color space " "which are then interpolated between, this requires a lot of maths." msgstr "" "Os perfis em forma de matriz têm alguns parâmetros que descrevem o espaço de " "cores entre os quais são interpolados; isto necessita de bastantes contas " "matemáticas." #: ../../general_concepts/colors/color_managed_workflow.rst:162 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." msgstr "" "Estes são relativamente raros e são usados principalmente para descrever os " "perfis da impressora, como o CMYK. Os perfis cLUT (Color Look-up Table) " "guardam muito mais dados que os perfis em matriz, pelo que poderão guardar " "dados sobre as pequenas particularidades causadas, por exemplo, por " "resultados inesperados provenientes da mistura de pigmentos. Esta é uma " "abordagem muito mais orgânica para descrever um espaço de cores, e é por " "isso que uma data de programas que não se preocupam com a gestão de cores " "não os suportam." #: ../../general_concepts/colors/color_managed_workflow.rst:168 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." msgstr "" "Os perfis do cLUT funcionam através do registo de tabelas de cada cor num " "espaço de cores, bem como das suas coordenadas num espaço de referência. No " "caso do CMYK, este é tipicamente o L\\*A\\*B\\* e, para os restantes, o XYZ. " "Estas tabelas são difíceis de criar, o que significa que estes perfis são um " "bocado mais raros." #: ../../general_concepts/colors/color_managed_workflow.rst:169 msgid "cLUT profiles" msgstr "Perfis do cLUT" #: ../../general_concepts/colors/color_managed_workflow.rst:171 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." msgstr "" "O ponto interessante sobre os perfis ICC é que o seu espaço de trabalho pode " "ser maior que o espaço do seu dispositivo. De um modo geral, isto não é mau. " "Contudo, ao converter, ficará com a questão de como traduzir os valores do " "espaço de trabalho." #: ../../general_concepts/colors/color_managed_workflow.rst:174 msgid "Perceptual" msgstr "Percepção" #: ../../general_concepts/colors/color_managed_workflow.rst:174 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." msgstr "" "Isto apenas esmaga os valores do espaço de trabalho para o espaço que será " "convertido. É um método bom para ver todos os valores possíveis nisto, mas " "não tão bom se quiser uma reprodução de cores exacta. Use isto se quiser ver " "todos os valores numa imagem ou se quiser exprimir todos os contrastes " "possíveis. Não funciona com os perfis em Matriz, usando por omissão a " "colorimétrica relativa." #: ../../general_concepts/colors/color_managed_workflow.rst:177 msgid "Absolute Colorimetric" msgstr "Colorimétrica Absoluta" #: ../../general_concepts/colors/color_managed_workflow.rst:177 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." msgstr "" "Sendo o oposto da Percepção, a Colorimétrica Absoluta irá tentar reter todos " "os valores correctos a qualquer custo, o que poderá resultar em cores com um " "aspecto horrível. Recomendado apenas para trabalhos de reprodução. Não " "funciona com os perfis em Matriz no Krita, devido às normas do processo ICC " "v4." #: ../../general_concepts/colors/color_managed_workflow.rst:180 msgid "Relative Colorimetric" msgstr "Colorimétrica Relativa" #: ../../general_concepts/colors/color_managed_workflow.rst:180 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." msgstr "" "Sendo uma solução intermédia entre a percepção e a absoluta, a relativa irá " "tentar ajustar as cores que conseguir corresponder entre espaços de cores. " "Irá tentar fazer isso através do alinhamento dos pontos preto e branco. Irá " "cortar o resto no que respeita aos seus extremos respectivos. Isto é o que " "todos os perfis em matriz fazem por omissão durante a conversão, porque o " "processo do ICC v4 define que só é usada a Colorimétrica Relativa para os " "perfis em matriz." #: ../../general_concepts/colors/color_managed_workflow.rst:183 msgid "Saturation" msgstr "Saturação" #: ../../general_concepts/colors/color_managed_workflow.rst:183 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." msgstr "" "Faz tudo para manter as cores, mesmo às custas de sacrificar a matiz. É " "usada em infogramas. Não funciona com os perfis em forma de matriz, recaindo " "por omissão na colorimétrica relativa." #: ../../general_concepts/colors/color_managed_workflow.rst:185 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." msgstr "" "A *versão do perfil ICC* é a última coisa a ter em mente ao lidar com os " "perfis ICC. O Krita fornece tanto os perfis na versão 2 como na versão 4, " "sendo que os últimos dão melhores resultados nos cálculos matemáticos, mas " "os primeiros são mais suportados (como pode ser visto abaixo na " "'interoperabilidade com outros programas'. Também é por isso que o Krita usa " "por omissão a V2, e recomendamos que use a V2 a menos que não tenha a " "certeza se os outros programas que usa suportam a V4." #: ../../general_concepts/colors/color_managed_workflow.rst:188 msgid "LUT docker and HDR imaging" msgstr "Área do LUT e imagens HDR" #: ../../general_concepts/colors/color_managed_workflow.rst:196 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." msgstr "" "A :ref:`lut_docker` é a segunda parte importante da gestão de cores no Krita " "que é partilhada entre o Krita e os programas como o Blender, o Natron e o " "Nuke, e só usa as tabelas de pesquisa (LUT's) que estejam configuradas " "através de um ficheiro." #: ../../general_concepts/colors/color_managed_workflow.rst:198 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." msgstr "" "Poderá definir o espaço de trabalho da imagem sob o espaço de cores de " "entrada, e o ecrã como sRGB ou usando a sua própria LUT, caso a tenha " "adicionado à configuração. A janela neste caso serve para testar as " "transformações para um dado dispositivo de visualização." #: ../../general_concepts/colors/color_managed_workflow.rst:200 msgid "" "Component, exposure, gamma, whitepoint and blackpoint are knobs which allows " "you to modify the display filter." msgstr "" "A Componente, exposição, gama, ponto-branco e ponto-preto são parâmetros " "ajustáveis que lhe permitem modificar o filtro de visualização." #: ../../general_concepts/colors/color_managed_workflow.rst:208 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." msgstr "" "Como foi explicado anteriormente, poderemos ver o nosso monitor como um " "telescópio ou como binóculos para o mundo da nossa imagem. Isto significa " "que distorce a nossa vista da imagem um pouco. Contudo, podemos modificar " "estes binóculos ou apresentar um filtro que vê a nossa imagem de uma forma " "diferente. Por exemplo, para nos permitir ver o branco numa imagem que tem " "um branco mais branco que o branco do nosso ecrã. Para explicar o que isto " "significa, precisamos de pensar sobre o que é o branco." #: ../../general_concepts/colors/color_managed_workflow.rst:210 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." msgstr "" "Por exemplo, o branco no nosso monitor é um vermelho total, um verde total e " "um azul total. Mas é certamente diferente do branco no nosso papel, na cor " "do leite, no branco do Sol ou até no branco dos ecrãs dos nossos telemóveis." #: ../../general_concepts/colors/color_managed_workflow.rst:212 msgid "" "Black similarly, is brighter on a LCD display than a LED one, and " "incomparable with the black of a carefully sealed room." msgstr "" "O preto, de forma semelhante, é mais claro num ecrã LCD que num ecrã LED, e " "é incomparável com o preto de uma sala devidamente selada." #: ../../general_concepts/colors/color_managed_workflow.rst:214 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." msgstr "" "Isto significa que provavelmente também existem pretos mais pretos que o " "preto do ecrã, e brancos mais brancos que o branco do ecrã. Contudo, para " "fins de simplicidade, podemos à mesma atribuir o ponto-preto e o ponto-" "branco para determinados valores. A partir daí, podemos determinar se um " "branco é mais branco que o ponto branco, ou um preto mais preto que o ponto " "preto." #: ../../general_concepts/colors/color_managed_workflow.rst:216 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." msgstr "" "A área do LUT permite-nos controlar este filtro de visualização e modificar " "a distorção. Isto é útil quando começamos a modificar as imagens que foram " "feitas com alguns valores referentes a cenas, como as fotografias HDR, ou de " "imagens que provêm de um motor de desenho." #: ../../general_concepts/colors/color_managed_workflow.rst:224 msgid "" "So, for example, we can choose to scale whiter-than-screen-white to our " "screen-white so we can see the contrasts there." msgstr "" "Por isso, por exemplo, podemos optar por escalar o branco-mais-branco-que-o-" "branco-do-ecrã para o nosso branco-do-ecrã, para que possamos ver lá os " "contrastes." #: ../../general_concepts/colors/color_managed_workflow.rst:226 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." msgstr "" "O intuito disto é que poderá tirar partido de mais detalhe de iluminação " "numa imagem. Embora não consiga ver a diferença entre o branco do ecrã e o " "branco-mais-branco-que-o-branco-do-ecrã (porque o seu ecrã não consegue " "mostrar a diferença), os programas gráficos conseguirão decerto usá-lo." #: ../../general_concepts/colors/color_managed_workflow.rst:228 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." msgstr "" "Um exemplo comum é corresponder a iluminação entre um modelo 3D e uma cena " "do mundo real. Os outros são os retoques avançados de fotografias, com muito " "mais informações de contraste disponíveis para o utilizador. Na pintura " "propriamente dita, isto permite-lhe criar uma imagem onde poderá mexer à " "vontade no contraste e aumentar o brilho tanto quanto desejar." #: ../../general_concepts/colors/color_managed_workflow.rst:230 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." msgstr "" "As manipulações na área da LUT são por janela, pelo que poderá criar uma " "nova janela e configurá-la com a luminosidade. Desta forma, poderá ver a " "imagem a cores e em tons de cinzento, e manter um olho firme sobre os seus " "valores." #: ../../general_concepts/colors/color_managed_workflow.rst:232 msgid "" "Another example is to carefully watch the gradients in a certain section." msgstr "Outro exemplo é ver cuidadosamente os gradientes numa dada secção." #: ../../general_concepts/colors/color_managed_workflow.rst:234 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." msgstr "" "Como o ICC, a Área do LUT permite-lhe criar uma espécie de perfil para o seu " "dispositivo. Neste caso, será o 'LUT', que significa 'Look Up Table' (Tabela " "de Consulta), e que poderá ser adicionado pelo OCIO, mudando o ficheiro de " "configuração. Quando o OCIO for ligado, a configuração em :menuselection:" "`Configuração --> Configurar o Krita --> Gestão de Cores` ficará desligada, " "a menos que use o motor de cores :guilabel:`Interno`." #: ../../general_concepts/colors/color_managed_workflow.rst:237 msgid "In summary" msgstr "Em resumo" #: ../../general_concepts/colors/color_managed_workflow.rst:239 msgid "Krita has two modes of color management:" msgstr "O Krita tem dois modos de gestão de cores:" #: ../../general_concepts/colors/color_managed_workflow.rst:241 msgid "" "ICC works in terms of spaces relative to the CIEXYZ space, and requires an " "ICC profile." msgstr "" "O ICC funciona em termos de espaços relativos ao espaço CIEXYZ, e precisa de " "um perfil ICC." #: ../../general_concepts/colors/color_managed_workflow.rst:242 msgid "OCIO works in terms of interpretation, and makes use of LUTs." msgstr "O OCIO funciona em termos de interpretação, e tira partido das LUT's." #: ../../general_concepts/colors/color_managed_workflow.rst:243 msgid "both can be made with a colorimeter." msgstr "ambos podem ser compostos com um colorímetro." #: ../../general_concepts/colors/color_managed_workflow.rst:244 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." msgstr "" "Se quiser ter um processo de gestão de cores adequado, terá um feito à " "medida para o dispositivo de entrada (o seu ecrã e os dispositivos de saída " "(a sua impressora ou ecrã de destino). Para a Web, o resultado é sempre o " "sRGB." #: ../../general_concepts/colors/color_managed_workflow.rst:245 msgid "" "Set up your screen profiles under :menuselection:`Settings --> Configure " "Krita --> Color management`." msgstr "" "Configure os perfis dos seus monitores em :menuselection:`Configuração --> " "Configurar o Krita --> Gestão de cores`." #: ../../general_concepts/colors/color_managed_workflow.rst:246 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." msgstr "" "NÃO use os perfis do ecrã ou outros perfis de dispositivos onde desenhar. " "Use um perfil de espaço de trabalho como um dos perfis 'elle' para esse fim, " "dado que as contas de cores serão muito mais previsíveis e agradáveis. O " "Krita irá converter entre o espaço do seu ecrã e o espaço de trabalho na " "hora, permitindo-lhe escolher as cores correctas. Isto transforma o seu ecrã " "em binóculos para ver a imagem." #: ../../general_concepts/colors/color_managed_workflow.rst:247 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." msgstr "" "Use a gestão de cores apropriada para o processo apropriado. Se estiver a " "trabalhar com o Blender, estará melhor servido com o OCIO do que com o ICC. " "Se estiver a trabalhar com o Scribus ou o Photoshop, use o ICC." #: ../../general_concepts/colors/color_managed_workflow.rst:249 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." msgstr "" "O Krita faz uma grande quantidade de contas, muitas delas respeitantes à " "mistura das cores. Estas contas funcionam melhor num espaço de cores linear, " "e estes espaços lineares precisam de uma profundidade de cor com pelo menos " "16 bits para funcionar correctamente. A desvantagem é que o espaço linear " "poderá ser confuso de trabalhar nele." #: ../../general_concepts/colors/color_managed_workflow.rst:251 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!" msgstr "" "Se gostar de pintura, tiver uma quantidade decente de RAM e estiver a pensar " "em iniciar com calma a tirar partido da gestão de cores do Krita, tente " "actualizar as suas imagens no sRGB incorporado para o sRGB-v2-elle-g10.icc " "ou rec2020-v2-elle-g10.icc com 16 bits de vírgula flutuante. Isto dar-lhe-á " "uma melhor mistura de cores, enquanto abre a possibilidade de você começar a " "trabalhar com HDR!" #: ../../general_concepts/colors/color_managed_workflow.rst:256 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!" msgstr "" "Algumas placas gráficas, como as da marca NVidia, de facto têm a melhor " "performance com 16 bits de vírgula flutuante, porque as placas da NVidia " "convertem internamente para vírgula flutuante. Quando não precisa de o " "fazer, funciona mais depressa!" #: ../../general_concepts/colors/color_managed_workflow.rst:260 msgid "" "No amount of color management in the world can make the image on your screen " "and the image out of the printer have 100% the same color." msgstr "" "Nem toda a gestão de cores do mundo poderá fazer com que a imagem no seu " "ecrã e a imagem que sai na impressora tenham as cores 100% iguais." #: ../../general_concepts/colors/color_managed_workflow.rst:263 msgid "Exporting" msgstr "Exportação" #: ../../general_concepts/colors/color_managed_workflow.rst:265 msgid "" "When you have finished your image and are ready to export it, you can modify " "the color space to optimize it:" msgstr "" "Quando tiver terminado a sua imagem e estiver pronto para a exportar, poderá " "modificar o espaço de cores para a optimizar:" #: ../../general_concepts/colors/color_managed_workflow.rst:267 msgid "If you are preparing an image for the web:" msgstr "Se estiver a preparar uma imagem para a Web:" #: ../../general_concepts/colors/color_managed_workflow.rst:269 msgid "" "If you use 16bit color depth or higher, convert the image to 8bit color " "depth. This will make the image much smaller." msgstr "" "Se usar uma profundidade de cor de 16bits ou superior, converta a imagem " "para uma profundidade de cor de 8 bits. Isto irá tornar a imagem muito mais " "pequena." #: ../../general_concepts/colors/color_managed_workflow.rst:271 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." msgstr "" "O Krita não tem desenhos em meios-tons incorporados de momento, o que " "significa que as conversões de 16 para 18 bits poderão ter alguns cortes. " "Mas poderá simular isso se adicionar uma camada de preenchimento com um " "padrão, definir esta camada de preenchimento como sobreposição e com 5% de " "opacidade. Depois achate a imagem completa e converta-a para 8 bits. O " "padrão irá funcionar como meios-tons, dando um aspecto mais suave para os " "gradientes." #: ../../general_concepts/colors/color_managed_workflow.rst:273 msgid "If it's a gray-scale image, convert it to gray-scale." msgstr "" "Se for uma imagem em tons de cinzento, converta-a para tons de cinzento." #: ../../general_concepts/colors/color_managed_workflow.rst:274 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." msgstr "" "Se for uma imagem a cores, mantenha-a no perfil do espaço de trabalho: " "Muitos navegadores Web dos doas de hoje suportam perfis de cores " "incorporados nas imagens. O Firefox, por exemplo, irá tentar converter a sua " "imagem para corresponder o perfil de cores do outro monitor (se tiverem um). " "Desta forma, a imagem irá parecer quase igual no seu ecrã e noutros " "monitores com perfis." #: ../../general_concepts/colors/color_managed_workflow.rst:279 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 " "`_, save your PNG, JPG or TIFF without an embedded profile to work " "around this." msgstr "" "Em algumas versões do Firefox, as cores realmente parecem estranhas: Isto é " "um erro no Firefox, e é por isso que o seu `sistema de gestão de cores está " "incompleto `_; grave o seu PNG, JPG ou TIFF sem perfis incorporados para " "dar a volta a isto." #: ../../general_concepts/colors/color_managed_workflow.rst:281 msgid "If you are preparing for print:" msgstr "Se estiver a preparar-se para imprimir:" #: ../../general_concepts/colors/color_managed_workflow.rst:283 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." msgstr "" "Provavelmente criou a imagem num perfil de espaço de trabalho em vez do " "perfil personalizado actual do seu ecrã; caso contrário, converta-o para " "algo como o Adobe RGB, sRGB ou Rec. 2020." #: ../../general_concepts/colors/color_managed_workflow.rst:284 msgid "" "Check with the printer what kind of image they expect. Maybe they expect " "sRGB color space, or perhaps they have their own profile." msgstr "" "Verifique com a impressora qual o tipo de imagem que ela está à espera. " "Talvez estejam à espera de sRGB ou talvez tenham o seu próprio perfil." #: ../../general_concepts/colors/color_managed_workflow.rst:287 msgid "Interaction with other applications" msgstr "Interacção com outras aplicações" #: ../../general_concepts/colors/color_managed_workflow.rst:290 msgid "Blender" msgstr "Blender" #: ../../general_concepts/colors/color_managed_workflow.rst:292 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." msgstr "" "Se quiser usar a funcionalidade do OCIO no Krita, e particularmente em " "conjunto com a gestão de cores do Blender, poderá tentar ter o Krita a usar " "a configuração do OCIO no Blender." #: ../../general_concepts/colors/color_managed_workflow.rst:294 msgid "" "Blender's OCIO config is under ``/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." msgstr "" "A configuração de OCIO do Blender está debaixo de ``/" "número_versão/datafiles/colormanagement``. Configure a área do LUT para usar " "o motor do OCIO e seleccione a configuração na pasta acima. Isto dar-lhe-á o " "espaço de entrada do Blender e do ecrã, mas não as aparências, dado que " "estas não são suportadas ainda no Krita." #: ../../general_concepts/colors/color_managed_workflow.rst:298 msgid "Windows Photo Viewer" msgstr "Windows Photo Viewer" #: ../../general_concepts/colors/color_managed_workflow.rst:300 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." msgstr "" "Poderá encontrar alguns problemas quando usar as diferentes aplicações em " "conjunto. Um ponto importante a notar é que a aplicação-padrão Windows Photo " "Viewer não lida com os perfis de ICC recentes. O Krita usa os perfis na " "versão 4; o Photo Viewer só consegue lidar com perfis na versão 2. Se " "exportar para JPEG com um perfil incorporado, o Photo Viewer irá mostrar a " "sua imagem demasiado escura." #: ../../general_concepts/colors/color_managed_workflow.rst:303 msgid "Example workflows" msgstr "Processos de exemplo" #: ../../general_concepts/colors/color_managed_workflow.rst:305 msgid "" "Here are some example workflows to get a feeling of how your color " "management workflow may look like." msgstr "" "Aqui estão alguns processos de exemplo para ter uma ideia de como poderá " "ficar o seu processo de gestão de cores." #: ../../general_concepts/colors/color_managed_workflow.rst:307 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'." msgstr "" "Como foi mencionado anteriormente, a entrada para o seu ecrã é definida com " "a opção :menuselection:`Configuração --> Configurar o Krita --> Gestão de " "cores`, ou através do 'espaço do ecrã' da área de LUT's. O espaço de " "trabalho é definido através de um novo ficheiro por cada documento, ou na " "área de LUT's pelo 'espaço de entrada'." #: ../../general_concepts/colors/color_managed_workflow.rst:310 msgid "Webcomic" msgstr "Banda desenhada da Web" #: ../../general_concepts/colors/color_managed_workflow.rst:317 #: ../../general_concepts/colors/color_managed_workflow.rst:339 #: ../../general_concepts/colors/color_managed_workflow.rst:357 msgid "Input" msgstr "Entrada" #: ../../general_concepts/colors/color_managed_workflow.rst:318 #: ../../general_concepts/colors/color_managed_workflow.rst:340 #: ../../general_concepts/colors/color_managed_workflow.rst:358 msgid "Your screen profile. (You pick colors via your screen)" msgstr "O perfil do se ecrã. (Irá escolher as cores com o seu ecrã)" #: ../../general_concepts/colors/color_managed_workflow.rst:319 #: ../../general_concepts/colors/color_managed_workflow.rst:341 #: ../../general_concepts/colors/color_managed_workflow.rst:359 msgid "Workingspace" msgstr "Espaço de trabalho" #: ../../general_concepts/colors/color_managed_workflow.rst:320 msgid "" "sRGB (the default screen profile) or any larger profile if you can spare the " "bit depth and like working in them." msgstr "" "sRGB (o perfil por omissão do ecrã) ou qualquer perfil maior, caso tenha ao " "seu dispor o espaço ocupado pela profundidade de cor e goste de trabalhar " "nele." #: ../../general_concepts/colors/color_managed_workflow.rst:322 #: ../../general_concepts/colors/color_managed_workflow.rst:344 #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "Output" msgstr "Resultado" #: ../../general_concepts/colors/color_managed_workflow.rst:322 msgid "" "sRGB, ICC version 2, sRGB TRC for the internet, and a specialized CMYK " "profile from the printing house for the printed images." msgstr "" "sRGB, ICC versão 2, TRC de sRGB para a Internet e um perfil CMYK " "especializado da casa de impressão para as imagens impressas." #: ../../general_concepts/colors/color_managed_workflow.rst:324 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." msgstr "" "Use o sRGB-elle-V2-srgbtrc.icc para circular entre o Inkscape, Photoshop, " "Painttool Sai, Illustrator, Gimp, Manga Studio, Paintstorm Studio, MyPaint, " "Artrage, Scribus, etc e o Krita." #: ../../general_concepts/colors/color_managed_workflow.rst:326 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." msgstr "" "Se estiver a usar um espaço maior com o ICC, só será capaz de o trocar entre " "o Krita, o Photoshop, o Illustrator, o Gimp 2.9, o Manga Studio e o Scribus. " "Todos os outros assumem o sRGB para o seu espaço, seja ele qual for, porque " "não têm gestão de cores." #: ../../general_concepts/colors/color_managed_workflow.rst:328 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." msgstr "" "Se estiver a integrar o Krita com o Blender, Nuke ou Natron, use o OCIO e " "configure o espaço de entrada como 'sRGB', mas certifique-se que selecciona " "o perfil do sRGB para o ICC ao criar um novo ficheiro." #: ../../general_concepts/colors/color_managed_workflow.rst:330 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." msgstr "" "Para a versão final para a Web, converta a imagem para sRGB a 8bits, " "srgbtrc, não incorporando o perfil ICC. Depois, se estiver a usar o PNG, " "passe-o por algo como o 'pngcrush' ou outros optimizadores do PNG. O sRGB " "nesse caso será escolhido porque poderá assumir que a maioria da sua " "audiência não criou um perfil para o ecrã deles, nem que eles têm ecrãs " "avançados o suficiente para as coisas de gamute amplo. É por isso que " "convertemos para as predefinições de ecrãs para a Internet, o sRGB." #: ../../general_concepts/colors/color_managed_workflow.rst:333 msgid "Print" msgstr "Imprimir" #: ../../general_concepts/colors/color_managed_workflow.rst:342 msgid "sRGB or Rec. 2020 if you can afford the bit-depth being 16bit." msgstr "" "sRGB ou Rec. 2020 se conseguir usar a profundidade de cor como sendo a 16 " "bits." #: ../../general_concepts/colors/color_managed_workflow.rst:344 msgid "" "Specialized CMYK profile from the printing house for the printed images." msgstr "Perfil CMYK especializado da casa de impressão das imagens impressas." #: ../../general_concepts/colors/color_managed_workflow.rst:346 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." msgstr "" "Os perfis CMYK são diferentes por cada impressora, e até mesmo por papel ou " "tipo de tinta, por isso não seja presunçoso no que respeita a pedi-los por " "antecipação, em vez de fazer algo como tentar pintar sobre qualquer perfil " "de CMYK aleatório. Como foi mencionado na secção de condições de " "visualização, poderá querer manter as suas opções em aberto." #: ../../general_concepts/colors/color_managed_workflow.rst:348 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." msgstr "" "Poderá configurar o selector de cores avançado para transformar para um " "determinado perfil com o :menuselection:`Configuração --> Configurar o Krita " "--> Configuração do Selector Avançado de Cores`. Aí, assinale a opção :" "guilabel:`O selector de cores usa um espaço de cores diferente da imagem` e " "seleccione o perfil CMYK que pretende. Isto irá limitar um pouco as suas " "cores, mas mantém todas as opções de filtros e misturas do RGB." #: ../../general_concepts/colors/color_managed_workflow.rst:351 msgid "Games" msgstr "Jogos" #: ../../general_concepts/colors/color_managed_workflow.rst:360 msgid "sRGB or grayscale linear for roughness and specular maps." msgstr "" "sRGB ou tons de cinzento linear, para os mapas de texturas e especulares." #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "" "This one is tricky, but in the end it'll be sRGB for the regular player." msgstr "" "Este é mais complicado, mas no fim de tudo será o sRGB para o leitor normal." #: ../../general_concepts/colors/color_managed_workflow.rst:364 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." msgstr "" "Isto tem truques. Poderá usar o OCIO e o ICC entre programas, mas recomenda-" "se que tenha as suas imagens no motor em sRGB ou tons de cinzento. Muitos " "dos sistemas de desenho baseados na física destes dias permitem-lhe definir " "se uma imagem deve ser lida como uma imagem linear ou 'srgbtrc', e isto é " "mesmo vital para ter as imagens em consideração de forma adequada nos " "cálculos baseados na física do motor do jogo." #: ../../general_concepts/colors/color_managed_workflow.rst:366 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." msgstr "" "Embora os motores de jogos precisem de ter conteúdo optimizado, e se " "recomende que permaneça dentro dos 8 bits, os ecrãs futuros poderão ter " "profundidades de cor mias elevadas, e quando os sistemas de desenho comecem " "a suportá-los, poderá ser benéfico desenvolver um processo em que os " "ficheiros do espaço de trabalho se tornem demasiado grandes e que possa " "correr alguns programas para os optimizar para as suas necessidades de " "desenho, tornando a actualização do jogo no futuro para melhores monitores " "um incómodo muito menor." #: ../../general_concepts/colors/color_managed_workflow.rst:368 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." msgstr "" "Os mapas da normal e os mapas da altura supostamente estão definidos com um " "espaço de cores com 'dados sem cor', mas irá descobrir que a maioria dos " "motores não querem saber muito disto. Em vez disso, dizem ao motor do jogo " "para não fazer nenhuma conversão sobre o ficheiro ao importar." #: ../../general_concepts/colors/color_managed_workflow.rst:370 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)." msgstr "" "Os mapas especulares, de brilho, metalização e rugosidade são todos baseados " "em cálculos lineares e quando descobrir que um dado material tem um " "coeficiente metálico de 03, isto corresponde a 30% de cinzento num espaço " "linear. Como tal, certifique-se que indica ao sistema de desenho do motor do " "jogo que esta é uma imagem de um espaço linear (ou, pelo menos, que NÃO deve " "ser convertida)." #: ../../general_concepts/colors/color_managed_workflow.rst:374 msgid "" "`Visualizing the XYZ color space `_." msgstr "" "`Visualização do espaço de cores XYZ `_." #: ../../general_concepts/colors/color_managed_workflow.rst:375 msgid "" "`Basics of gamma correction `_." msgstr "" "`Conceitos básicos da correcção do gama `_." #: ../../general_concepts/colors/color_managed_workflow.rst:376 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 `_." msgstr "" "`Exemplo do Panda3d com uma imagem com codificação do gama, sem o motor 3D " "ter sido notificado desse facto, pelo que resultará em imagens demasiado " "escuras `_." #: ../../general_concepts/colors/color_managed_workflow.rst:377 msgid "" "`2D examples of the effect of gamma-encoding on color maths `_." msgstr "" "`Exemplos 2d do efeito da codificação do gama nas contas das cores `_." #: ../../general_concepts/colors/color_managed_workflow.rst:378 msgid "" "`Basic overview of color management from ArgyllCMS manual `_." msgstr "" "`Introdução básica à gestão de cores do manual do Argylcms `_." diff --git a/locale/sk/LC_MESSAGES/contributors_manual/krita_manual_conventions.po b/locale/sk/LC_MESSAGES/contributors_manual/krita_manual_conventions.po index 5c4e98bf1..abc8d8055 100644 --- a/locale/sk/LC_MESSAGES/contributors_manual/krita_manual_conventions.po +++ b/locale/sk/LC_MESSAGES/contributors_manual/krita_manual_conventions.po @@ -1,1141 +1,1141 @@ # translation of docs_krita_org_contributors_manual___krita_manual_conventions.po to Slovak # Roman Paholik , 2019. msgid "" msgstr "" "Project-Id-Version: " "docs_krita_org_contributors_manual___krita_manual_conventions\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-09 03:27+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: 2019-03-01 12:48+0100\n" "Last-Translator: Roman Paholik \n" "Language-Team: Slovak \n" "Language: sk\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Generator: Lokalize 2.0\n" "Plural-Forms: nplurals=3; plural=(n==1) ? 0 : (n>=2 && n<=4) ? 1 : 2;\n" #: ../../:2 msgid "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: mouseleft" msgstr "" #: ../../:4 msgid "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: mouseright" msgstr "" #: ../../:6 msgid "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: mousemiddle" msgstr "" #: ../../:8 msgid "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" msgstr "" +#: ../../contributors_manual/krita_manual_conventions.rst:None +msgid "Horizontal Rulers" +msgstr "" + #: ../../contributors_manual/krita_manual_conventions.rst:0 msgid "" ".. image:: images/sample.png\n" " :alt: an image." msgstr "" -#: ../../contributors_manual/krita_manual_conventions.rst:None -msgid "Horizontal Rulers" -msgstr "" - #: ../../contributors_manual/krita_manual_conventions.rst:1 msgid "reStructuredText conventions for the Krita Manual" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:16 msgid "Mark-up conventions for the Krita Manual" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:18 msgid "" "This details the style conventions for using restructured text for the Krita " "Manual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:20 msgid "" "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):" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:23 msgid "" "`Primer `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "User Manual:" msgstr "Používateľská príručka:" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "" "`Quick Ref `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:25 msgid "" "`Text Cheatsheet `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:27 msgid "" "`Introduction `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:28 msgid "" "`Markup `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "Reference Documentation:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "" "`Directives `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:30 msgid "`Roles `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "Sphinx specific docs:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "" "`Sphinx' page on restructured text `_ -- This is useful for the specific " "sphinx directives and roles it uses to generate for example table of " "contents." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:34 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:36 msgid "Contents" msgstr "Obsah" #: ../../contributors_manual/krita_manual_conventions.rst:39 msgid "Meta data" msgstr "Metadáta" #: ../../contributors_manual/krita_manual_conventions.rst:41 msgid "Each page should start with the following three things:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:44 msgid "" "This is a general description of the page. It will be converted to an html " "meta tag which will be used by search engines::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:46 msgid "" ".. meta::\n" " :description:\n" " Description." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:49 msgid "A meta description" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:52 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:54 msgid "" ".. metadata-placeholder\n" "\n" " :authors: - Author 1\n" " - Author 2\n" " :license: GNU free documentation license 1.3 or later." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:58 msgid "A list of authors and a license." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:61 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid "Indexing terms." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid ".. index:: Keyword, Keyword with Spaces, ! Main Definition Keyword" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:66 msgid "" "This is so we can easily link to the page using ``:ref:`label_name```. Try " "to make this a nice variable name::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:68 msgid ".. _label_name:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:70 msgid "" "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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:71 msgid "A label." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:74 msgid "Headings" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:76 msgid "Headings will be done in the following order::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:78 msgid "" "############\n" "Part/Section\n" "############\n" "\n" "For pages that have a lot of subpages.\n" "\n" "=========\n" "Heading 1\n" "=========\n" "\n" "Start most manual pages with this.\n" "\n" "Heading 2\n" "---------\n" "\n" "Heading 3\n" "~~~~~~~~~\n" "\n" "Heading 4\n" "^^^^^^^^^\n" "\n" "Heading 5\n" "'''''''''\n" "\n" "Heading 6\n" "\"\"\"\"\"\"\"\"\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:105 msgid "" "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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:107 msgid "" "Sometimes you need to link to a subsection of a page, add a label above the " "heading in that case." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:109 msgid "" "Headers should not end with punctuation, as the header will be used as the " "link name when linking to a label." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:112 msgid "Linking" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:114 msgid "" "Linking is done with ``:ref:`label_name```. When you need an alternative " "link text, you use ``:ref:`actual text shown ```." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:116 msgid "" "Linking to external pages is done with ```url`_`` and ```link name " "`_``, which'll become `link name `_." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:118 msgid "" "`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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:121 msgid "Footnotes and further reading" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:123 msgid "" "Footnotes can be made in 3 ways, the most common one is with autonumbering, " "as per reference:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:125 msgid "" "[#]_ is a reference to footnote 1, and [#]_ is a reference to footnote 2." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:128 msgid "This is footnote 1." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:129 msgid "This is footnote 2." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:130 msgid "This is footnote 3." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:132 msgid "[#]_ is a reference to footnote 3." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:134 msgid "Here is a citation reference: [CIT2002]_ ." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:136 msgid "" "This is the citation. It's just like a footnote, except the label is " "textual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:139 msgid "Citation can also be referenced with ```citation `_``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:141 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:145 msgid "Images" msgstr "Obrázky" #: ../../contributors_manual/krita_manual_conventions.rst:147 msgid "Use the image directive for images without captions::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:149 msgid "" ".. image:: /images/sample.png\n" " :width: 800\n" " :align: center\n" " :alt: an image." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:154 msgid "And figure directives for images with captions::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:156 msgid "" ".. figure:: /images/sample.png\n" " :figwidth: 800\n" " :align: center\n" " :alt: an image.\n" "\n" " A caption -- notice how the first letter is aligned with the :figwidth: " "option." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:163 msgid "The latter gives:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:170 msgid "" "A caption -- notice how the first letter of the caption in the directive is " "aligned with the :figwidth: option." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:172 msgid "" "Images should go into the ``/images`` folder. By using ``/images`` instead " "of ``images``, sphinx will know the filepath isn't relative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:175 msgid "In-text Markup" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:177 msgid "" "You can make text *emphasized* and **strong** with a single asterisk and " "double respectively::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:179 msgid "" "*emphasize*\n" "**strong**" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:182 msgid "You cannot do both ***emphasized and strong***, so take a pick." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:184 msgid "" "You can :sub:`subscript text` and :sup:`superscript text` by using ``:sub:" "`text``` and ``:sup:`text```" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:186 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:188 msgid "" ":menuselection:`Settings --> Configure Krita`\n" ":guilabel:`File`\n" ":kbd:`Ctrl + Z`\n" ":program:`Krita`" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:193 msgid "" "Avoid randomly bolding words. It does *not* make the text easier or " "friendlier to read." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:196 msgid "Substitution References" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:198 msgid "" "You can create a sort of shorthand for a piece of text or an image by doing::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:200 msgid ".. |shorthand| replace:: something or the other." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:202 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:204 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:206 msgid "" "For links, if you reuse the same link over and over, you can write something " "like the following at the end of the file::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:208 msgid "" ".. _bugzilla: https://bugs.kde.org/\n" ".. _Krita Manual: https://docs.krita.org/" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:211 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:214 msgid "Lists" msgstr "Zoznamy" #: ../../contributors_manual/krita_manual_conventions.rst:217 msgid "Ordinated lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:219 msgid "Apple" msgstr "Jablko" #: ../../contributors_manual/krita_manual_conventions.rst:220 msgid "Pear" msgstr "Hruška" #: ../../contributors_manual/krita_manual_conventions.rst:221 msgid "Banana" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:223 msgid "Or..." msgstr "alebo..." #: ../../contributors_manual/krita_manual_conventions.rst:225 msgid "Table" msgstr "Stôl" #: ../../contributors_manual/krita_manual_conventions.rst:226 msgid "Chair" msgstr "Stolička" #: ../../contributors_manual/krita_manual_conventions.rst:227 msgid "Wardrobe." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:229 msgid "Augustus" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:230 msgid "Nero" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:231 msgid "Caligula" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:232 msgid "Trajan" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:234 msgid "They can be defined as follows::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:236 msgid "" "1. Apple\n" "2. Pear\n" "3. Banana\n" "\n" "#. Apple\n" "#. Pear\n" "#. Banana\n" "\n" "A. Table\n" "B. Chair\n" "C. Wardrobe\n" "\n" "A. Table\n" "#. Chair\n" "#. Wardrobe\n" "\n" "I. Augustus\n" "#. Nero\n" "#. Caligula\n" "#. Trajan" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:258 msgid "Unordered lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:260 msgid "red" msgstr "červená" #: ../../contributors_manual/krita_manual_conventions.rst:261 msgid "yellow" msgstr "žltá" #: ../../contributors_manual/krita_manual_conventions.rst:263 msgid "seagreen" msgstr "morská zelená" #: ../../contributors_manual/krita_manual_conventions.rst:264 msgid "verdigris" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:265 msgid "teal" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:266 msgid "viridian" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:268 msgid "dark emerald" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "green" msgstr "zelená" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "emerald" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "light emerald" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:270 msgid "very light emerald." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:271 msgid "blue" msgstr "modrá" #: ../../contributors_manual/krita_manual_conventions.rst:273 msgid "Defined as such::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:275 msgid "" "- red\n" "- yellow\n" "- green\n" " - seagreen\n" " - verdigris\n" " - teal\n" " - viridian\n" " - emerald\n" " - dark emerald\n" " - light emerald\n" " - very light emerald.\n" "- blue" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:289 msgid "Definition Lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:291 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:293 msgid "Definition" msgstr "Definícia" #: ../../contributors_manual/krita_manual_conventions.rst:294 #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Explanation." msgstr "Vysvetlenie." #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Another option" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:299 msgid "You can make them like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:301 msgid "" "Definition\n" " Explanation.\n" "Another option\n" " Explanation." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:304 msgid "To make them." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:307 msgid "Tables" msgstr "Stoly" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Purpose" msgstr "Účel" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Table type" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "listing shortcuts" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "Simple table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "lots of colspans" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "Grid table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "Simple but long" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "List Table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:317 msgid "Done as follows::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:319 msgid "" "================== ============\n" "Purpose Table type\n" "================== ============\n" "listing shortcuts Simple table\n" "lots of colspans Grid table\n" "Simple but long List Table\n" "================== ============\n" "\n" "+-----------------+------------+\n" "|Purpose |Table Type |\n" "+=================+============+\n" "|listing shortcuts|Simple table|\n" "+-----------------+------------+\n" "|lots of colspans |Grid table |\n" "+-----------------+------------+\n" "|Simple but long |List table |\n" "+-----------------+------------+\n" "\n" ".. list-table::\n" " :header-rows: 1\n" "\n" " - * Purpose\n" " * Table Type\n" " - * listing shortcuts\n" " * simple table\n" " - * lots of colspans\n" " * grid table\n" " - * simple but long\n" " * list table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:349 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:352 msgid "Admonishments and asides" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:356 msgid "" "Admonishments are sort of like a separate section that the reader needs to " "pay attention to." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:358 msgid "" "Admonishments that can be used are the following (in order of seriousness):" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:362 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:366 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:370 msgid "Something that is important to note, but is not necessarily negative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:374 msgid "This is in general when something is negative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:378 msgid "" "General attention grabber. Use this when the subject is more important than " "warning, but not as important that is could get a dataloss." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:382 msgid "" "This is for things that could cause dataloss, like forgetting to save, or " "that Python currently has no undo functionality." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:386 msgid "" "This should be for things that are dangerous for the computer in general, " "this includes things that can cause out of memory style freezes." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:390 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:392 msgid "Generic admonition that can have any text" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:394 msgid "Text." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:396 msgid "You can make it like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:398 msgid "" ".. admonition:: Generic admonition that can have any text\n" "\n" " Text." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:404 msgid "Sphinx also adds::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:406 msgid "" ".. seealso::\n" "\n" " Which is useful to collect external links and references." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:414 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:418 msgid "That said, horizontal rulers can be made with ``----``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:421 msgid "The rubric directive" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:422 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:424 msgid ".. rubric:: The rubric directive" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:428 msgid "So, when to use these?" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:429 msgid "" "Only use them when you think the subject is too minor to have a proper " "heading." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:431 msgid "Topic" msgstr "Téma" #: ../../contributors_manual/krita_manual_conventions.rst:432 msgid "" "When the text is separated from the flow, so it goes into a different " "subject than the text itself is naturally going to." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:433 msgid "Rubric" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:434 msgid "" "When the text isn't separated from the flow, but it does not need a header " "either." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:436 msgid "Admonishments" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:436 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:439 msgid "Code Snippets" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:441 msgid "``Inline code snippets`` are done with ````backticks````." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:443 msgid "" "Multi-line code snippets are done by ending the previous section with ``::" "``, which'll look like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:445 msgid "" "This is a paragraph, and we define a preformated snippet like so::\n" "\n" " Be sure to add a white space and a tab afterwards before starting the " "snippet." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:449 msgid "" "You can also use the ``.. code::`` directive. If you add the language name " "after it, it'll do the appropriate syntax highlighting::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:451 msgid "" ".. code:: python\n" "\n" " # Python comment\n" " def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:459 msgid "Becomes" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:468 msgid "" "# Python comment\n" "def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:469 msgid "some more..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:483 msgid "" "// C++ comment\n" "int myFunction(int i) {\n" " i += 1;\n" "\n" " // Check if more than 12\n" " if (i>12) {\n" " i = 0;\n" " }\n" " return i;\n" "}" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:498 msgid "" "/* CSS comment */\n" "body {\n" " margin: 0 auto;\n" " /* is 800 still sensible? */\n" " max-width:800px;\n" " font-size:16px;\n" " color:#333;\n" " background-color: #eee;\n" " padding:1em;\n" " font-family:serif;\n" " line-height: 1.4;\n" "}" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:502 msgid "" "

this is " "a paragraph.

" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:504 msgid "Other preformatted text" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:507 msgid "One can" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:508 msgid "preformat" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:509 msgid "text by" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:510 msgid "prepending" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:511 msgid "each line" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:512 msgid "with a pipe" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:513 msgid "symbol" msgstr "symbol" #: ../../contributors_manual/krita_manual_conventions.rst:515 msgid "Like so::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:517 msgid "" "| One can\n" "| preformat\n" "| text by\n" "| prepending\n" "| each line\n" "| with a pipe\n" "| symbol" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:525 msgid "We don't actually use this anywhere in the manual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:528 msgid "Glossaries, Terms and Index" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:530 msgid "These are sphinx features." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:532 msgid "" "Index is used in the top section, right now only single index entries are " "used." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:534 msgid "" "Glossaries are used for some of the menu entry sections, but not all of them." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:537 msgid "Quotes" msgstr "Úvodzovky" #: ../../contributors_manual/krita_manual_conventions.rst:539 msgid "Quotes are done like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:541 msgid "" "I am not sure why you'd need quotes in a user manual...\n" "\n" "-- Wolthera" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:545 msgid "This becomes a blockquote." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:547 msgid "I am not sure why you'd need quotes in a user manual..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:551 msgid "" "We do actually use quotes in some places. Try to add a link to the name to " "define where it came from." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:552 msgid "Wolthera" msgstr "" #~ msgid "explanation." #~ msgstr "vysvetlenie." diff --git a/locale/sk/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po b/locale/sk/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po index 0ffdb9371..c5ad4f57e 100644 --- a/locale/sk/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po +++ b/locale/sk/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po @@ -1,1072 +1,1072 @@ # translation of docs_krita_org_general_concepts___colors___color_managed_workflow.po to Slovak # Roman Paholik , 2019. msgid "" msgstr "" "Project-Id-Version: " "docs_krita_org_general_concepts___colors___color_managed_workflow\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-08 03:08+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: 2019-03-01 13:05+0100\n" "Last-Translator: Roman Paholik \n" "Language-Team: Slovak \n" "Language: sk\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Generator: Lokalize 2.0\n" "Plural-Forms: nplurals=3; plural=(n==1) ? 0 : (n>=2 && n<=4) ? 1 : 2;\n" +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_matrix_profile.png" +msgstr "" + +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" +msgstr "" + #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group1.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group2.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group3.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group4.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/dockers/LUT_Management_Docker.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR_1.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR2.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_webcomic.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_print.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_games.svg" msgstr "" -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_matrix_profile.png" -msgstr "" - -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" -msgstr "" - #: ../../general_concepts/colors/color_managed_workflow.rst:1 msgid "How a color managed workflow works." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "Color" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 #, fuzzy #| msgid "What is colour management?" msgid "Color Management" msgstr "Čo je správa farieb?" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "ICC Profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "OCIO" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:17 msgid "Color Managed Workflow" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:19 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:22 msgid "Basic Info" msgstr "Základné informácie" #: ../../general_concepts/colors/color_managed_workflow.rst:24 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:26 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:29 msgid "What is the problem?" msgstr "Aký je problém?" #: ../../general_concepts/colors/color_managed_workflow.rst:31 msgid "" "To explain the point of color management, you'd first need to learn which " "problem color management tries to solve." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:33 msgid "Let us imagine a kinder garden:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:35 msgid "" "The class of 28 children is subdivided in groups of 7. Each group has its " "own table." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:37 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:40 msgid "The following results come from painting:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:42 msgid "" "Even though all groups had the same assignment, each group's result looks " "different." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:49 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:56 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:64 msgid "" "Group 3 had vermillion red, citron yellow, emerald green and cerulean blue. " "They didn't mix their green, and thus ended up with a purer color." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:71 msgid "" "Finally, group 4 has vermillion red, citron yellow and cerulean blue. Their " "colors probably look like what you imagined." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:73 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!" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:75 msgid "For this purpose, we invented color management." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:78 #, fuzzy #| msgid "What is colour management?" msgid "What is color management?" msgstr "Čo je správa farieb?" #: ../../general_concepts/colors/color_managed_workflow.rst:80 msgid "" "Color management is, dryly put, a set of systems that tries to have the same " "color translate properly between color devices." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:82 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:84 msgid "" "From XYZ it can then be translated back into another device space, such as " "RGB (for screens), or CMYK (for printers)." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:86 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:88 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:90 msgid "Within both we can identify the following color spaces:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:93 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 " "`." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:94 msgid "Device spaces" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:96 msgid "Working spaces" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:97 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:99 msgid "Aesthetic or Look spaces" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:99 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:102 msgid "Color managed workflow" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:104 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:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:110 msgid ".. image:: images/color_category/Krita-colormanaged-workflow_text.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:110 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:112 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:114 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:116 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:118 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:120 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:122 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:124 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:127 msgid "So what does this mean?" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:133 msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_krita_text.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:133 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:135 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*." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:137 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:139 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:141 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:143 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.)" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:148 msgid "ICC profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:150 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:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:153 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:159 msgid "Matrix Shaper profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:159 msgid "" "Matrix shaper profiles have a few parameters that describe the color space " "which are then interpolated between, this requires a lot of maths." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:162 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:168 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:169 msgid "cLUT profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:171 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:174 msgid "Perceptual" msgstr "Vnemový" #: ../../general_concepts/colors/color_managed_workflow.rst:174 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:177 #, fuzzy #| msgid "Absolute Colorimetric." msgid "Absolute Colorimetric" msgstr "Absolútna kolorimetria" #: ../../general_concepts/colors/color_managed_workflow.rst:177 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:180 msgid "Relative Colorimetric" msgstr "Relatívna kolometria" #: ../../general_concepts/colors/color_managed_workflow.rst:180 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:183 msgid "Saturation" msgstr "Sýtosť" #: ../../general_concepts/colors/color_managed_workflow.rst:183 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:185 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:188 msgid "LUT docker and HDR imaging" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:196 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:198 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:200 msgid "" "Component, exposure, gamma, whitepoint and blackpoint are knobs which allows " "you to modify the display filter." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:208 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:210 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:212 msgid "" "Black similarly, is brighter on a LCD display than a LED one, and " "incomparable with the black of a carefully sealed room." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:214 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:216 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:224 msgid "" "So, for example, we can choose to scale whiter-than-screen-white to our " "screen-white so we can see the contrasts there." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:226 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:228 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:230 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:232 msgid "" "Another example is to carefully watch the gradients in a certain section." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:234 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:237 msgid "In summary" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:239 #, fuzzy #| msgid "What is colour management?" msgid "Krita has two modes of color management:" msgstr "Čo je správa farieb?" #: ../../general_concepts/colors/color_managed_workflow.rst:241 msgid "" "ICC works in terms of spaces relative to the CIEXYZ space, and requires an " "ICC profile." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:242 msgid "OCIO works in terms of interpretation, and makes use of LUTs." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:243 msgid "both can be made with a colorimeter." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:244 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:245 msgid "" "Set up your screen profiles under :menuselection:`Settings --> Configure " "Krita --> Color management`." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:246 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:247 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:249 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:251 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!" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:256 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!" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:260 msgid "" "No amount of color management in the world can make the image on your screen " "and the image out of the printer have 100% the same color." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:263 msgid "Exporting" msgstr "Exportujem" #: ../../general_concepts/colors/color_managed_workflow.rst:265 msgid "" "When you have finished your image and are ready to export it, you can modify " "the color space to optimize it:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:267 msgid "If you are preparing an image for the web:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:269 msgid "" "If you use 16bit color depth or higher, convert the image to 8bit color " "depth. This will make the image much smaller." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:271 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:273 msgid "If it's a gray-scale image, convert it to gray-scale." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:274 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:279 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 " "`_, save your PNG, JPG or TIFF without an embedded profile to work " "around this." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:281 msgid "If you are preparing for print:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:283 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:284 msgid "" "Check with the printer what kind of image they expect. Maybe they expect " "sRGB color space, or perhaps they have their own profile." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:287 msgid "Interaction with other applications" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:290 msgid "Blender" msgstr "Blender" #: ../../general_concepts/colors/color_managed_workflow.rst:292 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:294 msgid "" "Blender's OCIO config is under ``/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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:298 msgid "Windows Photo Viewer" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:300 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:303 msgid "Example workflows" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:305 msgid "" "Here are some example workflows to get a feeling of how your color " "management workflow may look like." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:307 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'." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:310 msgid "Webcomic" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:317 #: ../../general_concepts/colors/color_managed_workflow.rst:339 #: ../../general_concepts/colors/color_managed_workflow.rst:357 msgid "Input" msgstr "Vstup" #: ../../general_concepts/colors/color_managed_workflow.rst:318 #: ../../general_concepts/colors/color_managed_workflow.rst:340 #: ../../general_concepts/colors/color_managed_workflow.rst:358 msgid "Your screen profile. (You pick colors via your screen)" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:319 #: ../../general_concepts/colors/color_managed_workflow.rst:341 #: ../../general_concepts/colors/color_managed_workflow.rst:359 msgid "Workingspace" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:320 msgid "" "sRGB (the default screen profile) or any larger profile if you can spare the " "bit depth and like working in them." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:322 #: ../../general_concepts/colors/color_managed_workflow.rst:344 #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "Output" msgstr "Výstup" #: ../../general_concepts/colors/color_managed_workflow.rst:322 msgid "" "sRGB, ICC version 2, sRGB TRC for the internet, and a specialized CMYK " "profile from the printing house for the printed images." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:324 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:326 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:328 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:330 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:333 msgid "Print" msgstr "Tlačiť" #: ../../general_concepts/colors/color_managed_workflow.rst:342 msgid "sRGB or Rec. 2020 if you can afford the bit-depth being 16bit." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:344 msgid "" "Specialized CMYK profile from the printing house for the printed images." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:346 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:348 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:351 msgid "Games" msgstr "Hry" #: ../../general_concepts/colors/color_managed_workflow.rst:360 msgid "sRGB or grayscale linear for roughness and specular maps." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "" "This one is tricky, but in the end it'll be sRGB for the regular player." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:364 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:366 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:368 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:370 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)." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:374 msgid "" "`Visualizing the XYZ color space `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:375 msgid "" "`Basics of gamma correction `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:376 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 `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:377 msgid "" "`2D examples of the effect of gamma-encoding on color maths `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:378 msgid "" "`Basic overview of color management from ArgyllCMS manual `_." msgstr "" diff --git a/locale/sv/LC_MESSAGES/contributors_manual/krita_manual_conventions.po b/locale/sv/LC_MESSAGES/contributors_manual/krita_manual_conventions.po index 3f04154fa..bc1b0c00f 100644 --- a/locale/sv/LC_MESSAGES/contributors_manual/krita_manual_conventions.po +++ b/locale/sv/LC_MESSAGES/contributors_manual/krita_manual_conventions.po @@ -1,1232 +1,1232 @@ # 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. # # Stefan Asserhäll , 2019. msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-09 03:27+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: 2019-06-25 18:00+0100\n" "Last-Translator: Stefan Asserhäll \n" "Language-Team: Swedish \n" "Language: sv\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" "X-Generator: Lokalize 2.0\n" #: ../../:2 msgid "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: mouseleft" msgstr "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: vänsterknapp" #: ../../:4 msgid "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: mouseright" msgstr "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: högerknapp" #: ../../:6 msgid "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: mousemiddle" msgstr "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: mittenknapp" #: ../../:8 msgid "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" msgstr "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mushjul" +#: ../../contributors_manual/krita_manual_conventions.rst:None +msgid "Horizontal Rulers" +msgstr "Horisontella linjaler" + #: ../../contributors_manual/krita_manual_conventions.rst:0 msgid "" ".. image:: images/sample.png\n" " :alt: an image." msgstr "" ".. image:: images/sample.png\n" " :alt: en bild." -#: ../../contributors_manual/krita_manual_conventions.rst:None -msgid "Horizontal Rulers" -msgstr "Horisontella linjaler" - #: ../../contributors_manual/krita_manual_conventions.rst:1 msgid "reStructuredText conventions for the Krita Manual" msgstr "Konventioner för reStructuredText i Kritas handbok" #: ../../contributors_manual/krita_manual_conventions.rst:16 msgid "Mark-up conventions for the Krita Manual" msgstr "Uppmärkningskonventioner för Kritas handbok" #: ../../contributors_manual/krita_manual_conventions.rst:18 msgid "" "This details the style conventions for using restructured text for the Krita " "Manual." msgstr "" "Detta beskriver stilkonventioner för användning av omstrukturerad text för " "Kritas handbok." #: ../../contributors_manual/krita_manual_conventions.rst:20 msgid "" "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):" msgstr "" "Rekommendationen är att titta på den `officiella specifikationen `_ för omstrukturerad text, och eftersom " "den finns på sourceforge, spara en kopia på din hårddisk (sourceforge har " "vissa problem med serverns tillgänglighet när det här skrivs):" #: ../../contributors_manual/krita_manual_conventions.rst:23 msgid "" "`Primer `_" msgstr "" "`Nybörjarhandledning `_" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "User Manual:" msgstr "Användarhandbok:" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "" "`Quick Ref `_" msgstr "" "`Snabbreferens `_" #: ../../contributors_manual/krita_manual_conventions.rst:25 msgid "" "`Text Cheatsheet `_" msgstr "" "`Textfusklapp `_" #: ../../contributors_manual/krita_manual_conventions.rst:27 msgid "" "`Introduction `_" msgstr "" "`Introduktion `_" #: ../../contributors_manual/krita_manual_conventions.rst:28 msgid "" "`Markup `_" msgstr "" "`Uppmärkning `_" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "Reference Documentation:" msgstr "Referensdokumentation:" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "" "`Directives `_" msgstr "" "`Direktiv `_" #: ../../contributors_manual/krita_manual_conventions.rst:30 msgid "`Roles `_" msgstr "`Roller `_" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "Sphinx specific docs:" msgstr "Sphinx-specifika dokument:" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "" "`Sphinx' page on restructured text `_ -- This is useful for the specific " "sphinx directives and roles it uses to generate for example table of " "contents." msgstr "" "`Sphinx' sida om omstrukturerad text `_ : Den är användbar för de specifika " "sphinx-direktiven och rollerna som används för att exempelvis generera " "innehållsförteckningen." #: ../../contributors_manual/krita_manual_conventions.rst:34 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." msgstr "" "Det finns skillnader mellan den officiella omstrukturerad text och sphinx-" "dokumentens flera sätt att göra saker. Dokumentet specificerar föreslagna " "konventioner att följa." #: ../../contributors_manual/krita_manual_conventions.rst:36 msgid "Contents" msgstr "Innehåll" #: ../../contributors_manual/krita_manual_conventions.rst:39 msgid "Meta data" msgstr "Metadata" #: ../../contributors_manual/krita_manual_conventions.rst:41 msgid "Each page should start with the following three things:" msgstr "Varje sida ska börja med följande tre saker:" #: ../../contributors_manual/krita_manual_conventions.rst:44 msgid "" "This is a general description of the page. It will be converted to an html " "meta tag which will be used by search engines::" msgstr "" "Det är en allmän beskrivning av sidan. Den konverteras till en HTML-metatagg " "som används av söktjänster::" #: ../../contributors_manual/krita_manual_conventions.rst:46 msgid "" ".. meta::\n" " :description:\n" " Description." msgstr "" ".. meta::\n" " :description:\n" " Beskrivning." #: ../../contributors_manual/krita_manual_conventions.rst:49 msgid "A meta description" msgstr "En metabeskrivning" #: ../../contributors_manual/krita_manual_conventions.rst:52 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::" msgstr "" "Den är bara till för att hålla reda på vem som redigerade sidan och ge " "erkännanden. Den ska vara i en kommentar så att den inte kommer att bli " "lättläst maskinellt. Hela handbokens licens är GDL 1.3 och ska också nämnas " "här::" #: ../../contributors_manual/krita_manual_conventions.rst:54 msgid "" ".. metadata-placeholder\n" "\n" " :authors: - Author 1\n" " - Author 2\n" " :license: GNU free documentation license 1.3 or later." msgstr "" ".. metadata-placeholder\n" "\n" " :authors: - Författare 1\n" " - Författare 2\n" " :license: GNU free documentation license 1.3 or later." #: ../../contributors_manual/krita_manual_conventions.rst:58 msgid "A list of authors and a license." msgstr "En lista över författare och en licens." #: ../../contributors_manual/krita_manual_conventions.rst:61 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::" msgstr "" "De är termer åtskilda av kommatecken som sidan kommer att indexeras som i :" "ref:`genindex`. Det genererade indexet är mycket användbart för både PDF " "samt de som inte är helt säkra på vad det exakta namnet på termen som de " "söker. De definieras på följande sätt::" #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid "Indexing terms." msgstr "Indexeringstermer." #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid ".. index:: Keyword, Keyword with Spaces, ! Main Definition Keyword" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:66 msgid "" "This is so we can easily link to the page using ``:ref:`label_name```. Try " "to make this a nice variable name::" msgstr "" "Den är till för att enkelt kunna länka till sidan med användning av ``:ref:" "`label_name```. Försök att göra den till ett snyggt variabelnamn::" #: ../../contributors_manual/krita_manual_conventions.rst:68 msgid ".. _label_name:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:70 msgid "" "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." msgstr "" "Efter etiketten måste en rubrik läggas till, eftersom ``:ref:`label_name``` " "hänvisar till rubriken för att fylla i sin länktext." #: ../../contributors_manual/krita_manual_conventions.rst:71 msgid "A label." msgstr "En etikett." #: ../../contributors_manual/krita_manual_conventions.rst:74 msgid "Headings" msgstr "Rubriker" #: ../../contributors_manual/krita_manual_conventions.rst:76 msgid "Headings will be done in the following order::" msgstr "Rubriker görs i följande ordning::" #: ../../contributors_manual/krita_manual_conventions.rst:78 msgid "" "############\n" "Part/Section\n" "############\n" "\n" "For pages that have a lot of subpages.\n" "\n" "=========\n" "Heading 1\n" "=========\n" "\n" "Start most manual pages with this.\n" "\n" "Heading 2\n" "---------\n" "\n" "Heading 3\n" "~~~~~~~~~\n" "\n" "Heading 4\n" "^^^^^^^^^\n" "\n" "Heading 5\n" "'''''''''\n" "\n" "Heading 6\n" "\"\"\"\"\"\"\"\"\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:105 msgid "" "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." msgstr "" "Konventionerna har mer eller mindre bestämts av konvertering av mediawiki " "till omstrukturerad text av `Pandoc `_. Om det behövs " "mer än fyra rubriker, fundera först på om sidan inte har blivit för " "komplicerad och behöver delas upp." #: ../../contributors_manual/krita_manual_conventions.rst:107 msgid "" "Sometimes you need to link to a subsection of a page, add a label above the " "heading in that case." msgstr "" "Ibland behöver man länka till en delsektion på en sida. Lägg till en etikett " "ovanför rubriken i detta fall." #: ../../contributors_manual/krita_manual_conventions.rst:109 msgid "" "Headers should not end with punctuation, as the header will be used as the " "link name when linking to a label." msgstr "" "Rubriker ska inte sluta med interpunktion, eftersom rubriken används som " "länknamn vid länkning till en etikett." #: ../../contributors_manual/krita_manual_conventions.rst:112 msgid "Linking" msgstr "Länkning" #: ../../contributors_manual/krita_manual_conventions.rst:114 msgid "" "Linking is done with ``:ref:`label_name```. When you need an alternative " "link text, you use ``:ref:`actual text shown ```." msgstr "" "Länkning görs med ``:ref:`etikettnamn```. När en alternativ länktext behövs, " "används ``:ref:`verklig visad text ```." #: ../../contributors_manual/krita_manual_conventions.rst:116 msgid "" "Linking to external pages is done with ```url`_`` and ```link name " "`_``, which'll become `link name `_." msgstr "" "Länkning till externa sidor görs med ```webbadress`_`` och ```länknamn " "`_``, vilket blir `länknamn `_." #: ../../contributors_manual/krita_manual_conventions.rst:118 msgid "" "`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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:121 msgid "Footnotes and further reading" msgstr "Fotnoter och vidare läsning" #: ../../contributors_manual/krita_manual_conventions.rst:123 msgid "" "Footnotes can be made in 3 ways, the most common one is with autonumbering, " "as per reference:" msgstr "" "Fotnoter kan skapas på tre sätt, det vanligaste är med automatisk numrering, " "som med en referens:" #: ../../contributors_manual/krita_manual_conventions.rst:125 msgid "" "[#]_ is a reference to footnote 1, and [#]_ is a reference to footnote 2." msgstr "" "[#]_ är en referens till fotnot 1, och [#]_ är en referens till fotnot 2." #: ../../contributors_manual/krita_manual_conventions.rst:128 msgid "This is footnote 1." msgstr "Detta är fotnot 1." #: ../../contributors_manual/krita_manual_conventions.rst:129 msgid "This is footnote 2." msgstr "Detta är fotnot 2." #: ../../contributors_manual/krita_manual_conventions.rst:130 msgid "This is footnote 3." msgstr "Detta är fotnot 3." #: ../../contributors_manual/krita_manual_conventions.rst:132 msgid "[#]_ is a reference to footnote 3." msgstr "[#]_ är en referens till fotnot 3." #: ../../contributors_manual/krita_manual_conventions.rst:134 msgid "Here is a citation reference: [CIT2002]_ ." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:136 msgid "" "This is the citation. It's just like a footnote, except the label is " "textual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:139 msgid "Citation can also be referenced with ```citation `_``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:141 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:145 msgid "Images" msgstr "Bilder" #: ../../contributors_manual/krita_manual_conventions.rst:147 msgid "Use the image directive for images without captions::" msgstr "Använd bilddirektivet för bilder utan rubriker:" #: ../../contributors_manual/krita_manual_conventions.rst:149 msgid "" ".. image:: /images/sample.png\n" " :width: 800\n" " :align: center\n" " :alt: an image." msgstr "" ".. image:: /images/sample.png\n" " :width: 800\n" " :align: center\n" " :alt: en bild." #: ../../contributors_manual/krita_manual_conventions.rst:154 msgid "And figure directives for images with captions::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:156 msgid "" ".. figure:: /images/sample.png\n" " :figwidth: 800\n" " :align: center\n" " :alt: an image.\n" "\n" " A caption -- notice how the first letter is aligned with the :figwidth: " "option." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:163 msgid "The latter gives:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:170 msgid "" "A caption -- notice how the first letter of the caption in the directive is " "aligned with the :figwidth: option." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:172 msgid "" "Images should go into the ``/images`` folder. By using ``/images`` instead " "of ``images``, sphinx will know the filepath isn't relative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:175 msgid "In-text Markup" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:177 msgid "" "You can make text *emphasized* and **strong** with a single asterisk and " "double respectively::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:179 msgid "" "*emphasize*\n" "**strong**" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:182 msgid "You cannot do both ***emphasized and strong***, so take a pick." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:184 msgid "" "You can :sub:`subscript text` and :sup:`superscript text` by using ``:sub:" "`text``` and ``:sup:`text```" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:186 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:188 msgid "" ":menuselection:`Settings --> Configure Krita`\n" ":guilabel:`File`\n" ":kbd:`Ctrl + Z`\n" ":program:`Krita`" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:193 msgid "" "Avoid randomly bolding words. It does *not* make the text easier or " "friendlier to read." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:196 msgid "Substitution References" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:198 msgid "" "You can create a sort of shorthand for a piece of text or an image by doing::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:200 msgid ".. |shorthand| replace:: something or the other." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:202 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:204 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:206 msgid "" "For links, if you reuse the same link over and over, you can write something " "like the following at the end of the file::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:208 msgid "" ".. _bugzilla: https://bugs.kde.org/\n" ".. _Krita Manual: https://docs.krita.org/" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:211 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:214 msgid "Lists" msgstr "Listor" #: ../../contributors_manual/krita_manual_conventions.rst:217 msgid "Ordinated lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:219 msgid "Apple" msgstr "Äpple" #: ../../contributors_manual/krita_manual_conventions.rst:220 msgid "Pear" msgstr "Päron" #: ../../contributors_manual/krita_manual_conventions.rst:221 msgid "Banana" msgstr "Banan" #: ../../contributors_manual/krita_manual_conventions.rst:223 msgid "Or..." msgstr "Eller..." #: ../../contributors_manual/krita_manual_conventions.rst:225 msgid "Table" msgstr "Bord" #: ../../contributors_manual/krita_manual_conventions.rst:226 msgid "Chair" msgstr "Stol" #: ../../contributors_manual/krita_manual_conventions.rst:227 msgid "Wardrobe." msgstr "Garderob." #: ../../contributors_manual/krita_manual_conventions.rst:229 msgid "Augustus" msgstr "Augustus" #: ../../contributors_manual/krita_manual_conventions.rst:230 msgid "Nero" msgstr "Nero" #: ../../contributors_manual/krita_manual_conventions.rst:231 msgid "Caligula" msgstr "Caligula" #: ../../contributors_manual/krita_manual_conventions.rst:232 msgid "Trajan" msgstr "Trajan" #: ../../contributors_manual/krita_manual_conventions.rst:234 msgid "They can be defined as follows::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:236 msgid "" "1. Apple\n" "2. Pear\n" "3. Banana\n" "\n" "#. Apple\n" "#. Pear\n" "#. Banana\n" "\n" "A. Table\n" "B. Chair\n" "C. Wardrobe\n" "\n" "A. Table\n" "#. Chair\n" "#. Wardrobe\n" "\n" "I. Augustus\n" "#. Nero\n" "#. Caligula\n" "#. Trajan" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:258 msgid "Unordered lists" msgstr "Oordnade listor" #: ../../contributors_manual/krita_manual_conventions.rst:260 msgid "red" msgstr "röd" #: ../../contributors_manual/krita_manual_conventions.rst:261 msgid "yellow" msgstr "gul" #: ../../contributors_manual/krita_manual_conventions.rst:263 msgid "seagreen" msgstr "havsgrön" #: ../../contributors_manual/krita_manual_conventions.rst:264 msgid "verdigris" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:265 msgid "teal" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:266 msgid "viridian" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:268 msgid "dark emerald" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "green" msgstr "grön" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "emerald" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "light emerald" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:270 msgid "very light emerald." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:271 msgid "blue" msgstr "blå" #: ../../contributors_manual/krita_manual_conventions.rst:273 msgid "Defined as such::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:275 msgid "" "- red\n" "- yellow\n" "- green\n" " - seagreen\n" " - verdigris\n" " - teal\n" " - viridian\n" " - emerald\n" " - dark emerald\n" " - light emerald\n" " - very light emerald.\n" "- blue" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:289 msgid "Definition Lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:291 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:293 msgid "Definition" msgstr "Definition" #: ../../contributors_manual/krita_manual_conventions.rst:294 #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Explanation." msgstr "Förklaring." #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Another option" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:299 msgid "You can make them like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:301 msgid "" "Definition\n" " Explanation.\n" "Another option\n" " Explanation." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:304 msgid "To make them." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:307 msgid "Tables" msgstr "Tabeller" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Purpose" msgstr "Syfte" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Table type" msgstr "Tabelltyp" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "listing shortcuts" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "Simple table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "lots of colspans" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "Grid table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "Simple but long" msgstr "Enkel men lång" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "List Table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:317 msgid "Done as follows::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:319 msgid "" "================== ============\n" "Purpose Table type\n" "================== ============\n" "listing shortcuts Simple table\n" "lots of colspans Grid table\n" "Simple but long List Table\n" "================== ============\n" "\n" "+-----------------+------------+\n" "|Purpose |Table Type |\n" "+=================+============+\n" "|listing shortcuts|Simple table|\n" "+-----------------+------------+\n" "|lots of colspans |Grid table |\n" "+-----------------+------------+\n" "|Simple but long |List table |\n" "+-----------------+------------+\n" "\n" ".. list-table::\n" " :header-rows: 1\n" "\n" " - * Purpose\n" " * Table Type\n" " - * listing shortcuts\n" " * simple table\n" " - * lots of colspans\n" " * grid table\n" " - * simple but long\n" " * list table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:349 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:352 msgid "Admonishments and asides" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:356 msgid "" "Admonishments are sort of like a separate section that the reader needs to " "pay attention to." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:358 msgid "" "Admonishments that can be used are the following (in order of seriousness):" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:362 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:366 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:370 msgid "Something that is important to note, but is not necessarily negative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:374 msgid "This is in general when something is negative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:378 msgid "" "General attention grabber. Use this when the subject is more important than " "warning, but not as important that is could get a dataloss." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:382 msgid "" "This is for things that could cause dataloss, like forgetting to save, or " "that Python currently has no undo functionality." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:386 msgid "" "This should be for things that are dangerous for the computer in general, " "this includes things that can cause out of memory style freezes." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:390 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:392 msgid "Generic admonition that can have any text" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:394 msgid "Text." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:396 msgid "You can make it like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:398 msgid "" ".. admonition:: Generic admonition that can have any text\n" "\n" " Text." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:404 msgid "Sphinx also adds::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:406 msgid "" ".. seealso::\n" "\n" " Which is useful to collect external links and references." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:414 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:418 msgid "That said, horizontal rulers can be made with ``----``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:421 msgid "The rubric directive" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:422 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:424 msgid ".. rubric:: The rubric directive" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:428 msgid "So, when to use these?" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:429 msgid "" "Only use them when you think the subject is too minor to have a proper " "heading." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:431 msgid "Topic" msgstr "Ämne" #: ../../contributors_manual/krita_manual_conventions.rst:432 msgid "" "When the text is separated from the flow, so it goes into a different " "subject than the text itself is naturally going to." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:433 msgid "Rubric" msgstr "Rubrik" #: ../../contributors_manual/krita_manual_conventions.rst:434 msgid "" "When the text isn't separated from the flow, but it does not need a header " "either." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:436 msgid "Admonishments" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:436 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:439 msgid "Code Snippets" msgstr "Kodsnuttar" #: ../../contributors_manual/krita_manual_conventions.rst:441 msgid "``Inline code snippets`` are done with ````backticks````." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:443 msgid "" "Multi-line code snippets are done by ending the previous section with ``::" "``, which'll look like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:445 msgid "" "This is a paragraph, and we define a preformated snippet like so::\n" "\n" " Be sure to add a white space and a tab afterwards before starting the " "snippet." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:449 msgid "" "You can also use the ``.. code::`` directive. If you add the language name " "after it, it'll do the appropriate syntax highlighting::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:451 msgid "" ".. code:: python\n" "\n" " # Python comment\n" " def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:459 msgid "Becomes" msgstr "Blir" #: ../../contributors_manual/krita_manual_conventions.rst:468 msgid "" "# Python comment\n" "def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:469 msgid "some more..." msgstr "något mer..." #: ../../contributors_manual/krita_manual_conventions.rst:483 msgid "" "// C++ comment\n" "int myFunction(int i) {\n" " i += 1;\n" "\n" " // Check if more than 12\n" " if (i>12) {\n" " i = 0;\n" " }\n" " return i;\n" "}" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:498 msgid "" "/* CSS comment */\n" "body {\n" " margin: 0 auto;\n" " /* is 800 still sensible? */\n" " max-width:800px;\n" " font-size:16px;\n" " color:#333;\n" " background-color: #eee;\n" " padding:1em;\n" " font-family:serif;\n" " line-height: 1.4;\n" "}" msgstr "" "/* CSS-kommentar */\n" "body {\n" " margin: 0 auto;\n" " /* är 800 fortfarande rimligt? */\n" " max-width:800px;\n" " font-size:16px;\n" " color:#333;\n" " background-color: #eee;\n" " padding:1em;\n" " font-family:serif;\n" " line-height: 1.4;\n" "}" #: ../../contributors_manual/krita_manual_conventions.rst:502 msgid "" "

this is " "a paragraph.

" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:504 msgid "Other preformatted text" msgstr "Annan förformaterad text" #: ../../contributors_manual/krita_manual_conventions.rst:507 msgid "One can" msgstr "Man kan" #: ../../contributors_manual/krita_manual_conventions.rst:508 msgid "preformat" msgstr "förformatera" #: ../../contributors_manual/krita_manual_conventions.rst:509 msgid "text by" msgstr "text genom att" #: ../../contributors_manual/krita_manual_conventions.rst:510 msgid "prepending" msgstr "inleda" #: ../../contributors_manual/krita_manual_conventions.rst:511 msgid "each line" msgstr "varje rad" #: ../../contributors_manual/krita_manual_conventions.rst:512 msgid "with a pipe" msgstr "med en vertikal" #: ../../contributors_manual/krita_manual_conventions.rst:513 msgid "symbol" msgstr "linje" #: ../../contributors_manual/krita_manual_conventions.rst:515 msgid "Like so::" msgstr "På följande sätt::" #: ../../contributors_manual/krita_manual_conventions.rst:517 msgid "" "| One can\n" "| preformat\n" "| text by\n" "| prepending\n" "| each line\n" "| with a pipe\n" "| symbol" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:525 msgid "We don't actually use this anywhere in the manual." msgstr "Vi använder i själva verket inte det någonstans i handboken." #: ../../contributors_manual/krita_manual_conventions.rst:528 msgid "Glossaries, Terms and Index" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:530 msgid "These are sphinx features." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:532 msgid "" "Index is used in the top section, right now only single index entries are " "used." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:534 msgid "" "Glossaries are used for some of the menu entry sections, but not all of them." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:537 msgid "Quotes" msgstr "Citationstecken" #: ../../contributors_manual/krita_manual_conventions.rst:539 msgid "Quotes are done like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:541 msgid "" "I am not sure why you'd need quotes in a user manual...\n" "\n" "-- Wolthera" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:545 msgid "This becomes a blockquote." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:547 msgid "I am not sure why you'd need quotes in a user manual..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:551 msgid "" "We do actually use quotes in some places. Try to add a link to the name to " "define where it came from." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:552 msgid "Wolthera" msgstr "Wolthera" #~ msgid "explanation." #~ msgstr "förklaring." #~ msgid "This looks like the following::" #~ msgstr "Det ser ut på följande sätt::" diff --git a/locale/sv/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po b/locale/sv/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po index 93b2e1460..26c60b0d8 100644 --- a/locale/sv/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po +++ b/locale/sv/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po @@ -1,1099 +1,1099 @@ # 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. # # Stefan Asserhäll , 2019. msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-08 03:08+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: 2019-08-02 12:04+0100\n" "Last-Translator: Stefan Asserhäll \n" "Language-Team: Swedish \n" "Language: sv\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" "X-Generator: Lokalize 2.0\n" +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_matrix_profile.png" +msgstr ".. image:: images/color_category/Kiki_matrix_profile.png" + +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" +msgstr ".. image:: images/color_category/Kiki_cLUTprofiles.png" + #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group1.png" msgstr ".. image:: images/color_category/Krita_2_9_colormanagement_group1.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group2.png" msgstr ".. image:: images/color_category/Krita_2_9_colormanagement_group2.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group3.png" msgstr ".. image:: images/color_category/Krita_2_9_colormanagement_group3.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group4.png" msgstr ".. image:: images/color_category/Krita_2_9_colormanagement_group4.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/dockers/LUT_Management_Docker.png" msgstr ".. image:: images/dockers/LUT_Management_Docker.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR_1.svg" msgstr ".. image:: images/color_category/Krita_HDR_1.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR2.svg" msgstr ".. image:: images/color_category/Krita_HDR2.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_webcomic.svg" msgstr "" ".. image:: images/color_category/Krita-colormanaged-workflow_webcomic.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_print.svg" msgstr ".. image:: images/color_category/Krita-colormanaged-workflow_print.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_games.svg" msgstr ".. image:: images/color_category/Krita-colormanaged-workflow_games.svg" -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_matrix_profile.png" -msgstr ".. image:: images/color_category/Kiki_matrix_profile.png" - -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" -msgstr ".. image:: images/color_category/Kiki_cLUTprofiles.png" - #: ../../general_concepts/colors/color_managed_workflow.rst:1 msgid "How a color managed workflow works." msgstr "Hur ett färghanterande arbetsflöde fungerar." #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "Color" msgstr "Färg" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "Color Management" msgstr "Färghantering" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "ICC Profiles" msgstr "ICC-profiler" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "OCIO" msgstr "OCIO" #: ../../general_concepts/colors/color_managed_workflow.rst:17 msgid "Color Managed Workflow" msgstr "Färghanterande arbetsflöde" #: ../../general_concepts/colors/color_managed_workflow.rst:19 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:22 msgid "Basic Info" msgstr "Grundinformation" #: ../../general_concepts/colors/color_managed_workflow.rst:24 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:26 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:29 msgid "What is the problem?" msgstr "Vad är problemet?" #: ../../general_concepts/colors/color_managed_workflow.rst:31 msgid "" "To explain the point of color management, you'd first need to learn which " "problem color management tries to solve." msgstr "" "För att förklara vitsen med färghantering måste man först förstå vilket " "problem som färghantering försöker lösa." #: ../../general_concepts/colors/color_managed_workflow.rst:33 msgid "Let us imagine a kinder garden:" msgstr "Låt oss föreställa oss ett dagis:" #: ../../general_concepts/colors/color_managed_workflow.rst:35 msgid "" "The class of 28 children is subdivided in groups of 7. Each group has its " "own table." msgstr "" "Klassen med 28 barn delas upp i grupper av sju. Varje grupp har sitt eget " "bord." #: ../../general_concepts/colors/color_managed_workflow.rst:37 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:40 msgid "The following results come from painting:" msgstr "Följande resultat kommer från målning:" #: ../../general_concepts/colors/color_managed_workflow.rst:42 msgid "" "Even though all groups had the same assignment, each group's result looks " "different." msgstr "" "Även om alla grupper hade samma uppgift, ser varje grupps resultat " "annorlunda ut." #: ../../general_concepts/colors/color_managed_workflow.rst:49 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:56 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:64 msgid "" "Group 3 had vermillion red, citron yellow, emerald green and cerulean blue. " "They didn't mix their green, and thus ended up with a purer color." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:71 msgid "" "Finally, group 4 has vermillion red, citron yellow and cerulean blue. Their " "colors probably look like what you imagined." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:73 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!" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:75 msgid "For this purpose, we invented color management." msgstr "Vi uppfann färghantering i detta syfte." #: ../../general_concepts/colors/color_managed_workflow.rst:78 msgid "What is color management?" msgstr "Vad är färghantering?" #: ../../general_concepts/colors/color_managed_workflow.rst:80 msgid "" "Color management is, dryly put, a set of systems that tries to have the same " "color translate properly between color devices." msgstr "" "Färghantering är, torrt sagt, en mängd system som försöker få samma färg att " "översättas riktigt mellan färgenheter." #: ../../general_concepts/colors/color_managed_workflow.rst:82 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." msgstr "" "Det fungerar oftast genom att försöka konvertera en färg till " "referensfärgrymden XYZ. XYZ är ett koordinatsystem som har en punkt för " "varje färg som det typiska mänskliga ögat kan se." #: ../../general_concepts/colors/color_managed_workflow.rst:84 msgid "" "From XYZ it can then be translated back into another device space, such as " "RGB (for screens), or CMYK (for printers)." msgstr "" "Från XYZ kan den därefter översättas tillbaka till en annan enhetsrymd, " "såsom RGB (för bildskärmar) eller CMYK (för skrivare)." #: ../../general_concepts/colors/color_managed_workflow.rst:86 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:88 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:90 msgid "Within both we can identify the following color spaces:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:93 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 " "`." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:94 msgid "Device spaces" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:96 msgid "Working spaces" msgstr "Arbetsrymder" #: ../../general_concepts/colors/color_managed_workflow.rst:97 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:99 msgid "Aesthetic or Look spaces" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:99 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:102 msgid "Color managed workflow" msgstr "Färghanterande arbetsflöde" #: ../../general_concepts/colors/color_managed_workflow.rst:104 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:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:110 msgid ".. image:: images/color_category/Krita-colormanaged-workflow_text.svg" msgstr ".. image:: images/color_category/Krita-colormanaged-workflow_text.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:110 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:112 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:114 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:116 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:118 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:120 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:122 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:124 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:127 msgid "So what does this mean?" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:133 msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_krita_text.svg" msgstr "" ".. image:: images/color_category/Krita-colormanaged-workflow_krita_text.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:133 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:135 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*." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:137 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:139 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:141 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:143 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.)" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:148 msgid "ICC profiles" msgstr "ICC-profiler" #: ../../general_concepts/colors/color_managed_workflow.rst:150 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:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:153 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:159 msgid "Matrix Shaper profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:159 msgid "" "Matrix shaper profiles have a few parameters that describe the color space " "which are then interpolated between, this requires a lot of maths." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:162 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:168 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:169 msgid "cLUT profiles" msgstr "cLUT-profiler" #: ../../general_concepts/colors/color_managed_workflow.rst:171 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:174 msgid "Perceptual" msgstr "Perceptuell" #: ../../general_concepts/colors/color_managed_workflow.rst:174 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:177 msgid "Absolute Colorimetric" msgstr "Absolut färgläge" #: ../../general_concepts/colors/color_managed_workflow.rst:177 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:180 msgid "Relative Colorimetric" msgstr "Relativt färgläge" #: ../../general_concepts/colors/color_managed_workflow.rst:180 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:183 msgid "Saturation" msgstr "Färgmättnad" #: ../../general_concepts/colors/color_managed_workflow.rst:183 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:185 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:188 msgid "LUT docker and HDR imaging" msgstr "LUT-panel och HDR-avbildning" #: ../../general_concepts/colors/color_managed_workflow.rst:196 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:198 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:200 msgid "" "Component, exposure, gamma, whitepoint and blackpoint are knobs which allows " "you to modify the display filter." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:208 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:210 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:212 msgid "" "Black similarly, is brighter on a LCD display than a LED one, and " "incomparable with the black of a carefully sealed room." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:214 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:216 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:224 msgid "" "So, for example, we can choose to scale whiter-than-screen-white to our " "screen-white so we can see the contrasts there." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:226 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:228 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:230 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:232 msgid "" "Another example is to carefully watch the gradients in a certain section." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:234 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:237 msgid "In summary" msgstr "Sammanfattning" #: ../../general_concepts/colors/color_managed_workflow.rst:239 msgid "Krita has two modes of color management:" msgstr "Krita har två sorters färghantering:" #: ../../general_concepts/colors/color_managed_workflow.rst:241 msgid "" "ICC works in terms of spaces relative to the CIEXYZ space, and requires an " "ICC profile." msgstr "" "ICC fungerar i termer av färgrymder relativa till CIEZYZ-rymden, och kräver " "en ICC-profil." #: ../../general_concepts/colors/color_managed_workflow.rst:242 msgid "OCIO works in terms of interpretation, and makes use of LUTs." msgstr "" "OCIO fungerar i termer av tolkning, och använder en LUT (uppslagningstabell)." #: ../../general_concepts/colors/color_managed_workflow.rst:243 msgid "both can be made with a colorimeter." msgstr "Båda kan skapas med en kolorimeter." #: ../../general_concepts/colors/color_managed_workflow.rst:244 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:245 msgid "" "Set up your screen profiles under :menuselection:`Settings --> Configure " "Krita --> Color management`." msgstr "" "Ställ in skärmprofiler under :menuselection:`Inställningar --> Anpassa Krita " "--> Färghantering`." #: ../../general_concepts/colors/color_managed_workflow.rst:246 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:247 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:249 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:251 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!" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:256 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!" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:260 msgid "" "No amount of color management in the world can make the image on your screen " "and the image out of the printer have 100% the same color." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:263 msgid "Exporting" msgstr "Export" #: ../../general_concepts/colors/color_managed_workflow.rst:265 msgid "" "When you have finished your image and are ready to export it, you can modify " "the color space to optimize it:" msgstr "" "När man är klar med bilden och är redo att exportera den, kan man ändra " "färgrymden för att optimera den:" #: ../../general_concepts/colors/color_managed_workflow.rst:267 msgid "If you are preparing an image for the web:" msgstr "Om man förbereder en bild för webben:" #: ../../general_concepts/colors/color_managed_workflow.rst:269 msgid "" "If you use 16bit color depth or higher, convert the image to 8bit color " "depth. This will make the image much smaller." msgstr "" "Om 16-bitars eller större färgdjup användes, konvertera bilden till 8-bitars " "färgdjup. Det gör bilden mycket mindre." #: ../../general_concepts/colors/color_managed_workflow.rst:271 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:273 msgid "If it's a gray-scale image, convert it to gray-scale." msgstr "Om det är en gråskalebild, konvertera den till gråskala." #: ../../general_concepts/colors/color_managed_workflow.rst:274 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:279 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 " "`_, save your PNG, JPG or TIFF without an embedded profile to work " "around this." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:281 msgid "If you are preparing for print:" msgstr "Om man förbereder en utskrift:" #: ../../general_concepts/colors/color_managed_workflow.rst:283 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:284 msgid "" "Check with the printer what kind of image they expect. Maybe they expect " "sRGB color space, or perhaps they have their own profile." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:287 msgid "Interaction with other applications" msgstr "Interaktion med andra program" #: ../../general_concepts/colors/color_managed_workflow.rst:290 msgid "Blender" msgstr "Blender" #: ../../general_concepts/colors/color_managed_workflow.rst:292 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:294 msgid "" "Blender's OCIO config is under ``/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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:298 msgid "Windows Photo Viewer" msgstr "Windows fotovisare" #: ../../general_concepts/colors/color_managed_workflow.rst:300 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:303 msgid "Example workflows" msgstr "Exempel på arbetsflöden" #: ../../general_concepts/colors/color_managed_workflow.rst:305 msgid "" "Here are some example workflows to get a feeling of how your color " "management workflow may look like." msgstr "" "Här är några exempel på arbetsflöden för att få en känsla av hur " "färghanteringsarbetsflöden kan se ut." #: ../../general_concepts/colors/color_managed_workflow.rst:307 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'." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:310 msgid "Webcomic" msgstr "Webbserie" #: ../../general_concepts/colors/color_managed_workflow.rst:317 #: ../../general_concepts/colors/color_managed_workflow.rst:339 #: ../../general_concepts/colors/color_managed_workflow.rst:357 msgid "Input" msgstr "Indata" #: ../../general_concepts/colors/color_managed_workflow.rst:318 #: ../../general_concepts/colors/color_managed_workflow.rst:340 #: ../../general_concepts/colors/color_managed_workflow.rst:358 msgid "Your screen profile. (You pick colors via your screen)" msgstr "Bildskärmsprofilen (man väljer färger via skärmen)." #: ../../general_concepts/colors/color_managed_workflow.rst:319 #: ../../general_concepts/colors/color_managed_workflow.rst:341 #: ../../general_concepts/colors/color_managed_workflow.rst:359 msgid "Workingspace" msgstr "Arbetsyta" #: ../../general_concepts/colors/color_managed_workflow.rst:320 msgid "" "sRGB (the default screen profile) or any larger profile if you can spare the " "bit depth and like working in them." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:322 #: ../../general_concepts/colors/color_managed_workflow.rst:344 #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "Output" msgstr "Utdata" #: ../../general_concepts/colors/color_managed_workflow.rst:322 msgid "" "sRGB, ICC version 2, sRGB TRC for the internet, and a specialized CMYK " "profile from the printing house for the printed images." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:324 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:326 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:328 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:330 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:333 msgid "Print" msgstr "Utskrift" #: ../../general_concepts/colors/color_managed_workflow.rst:342 msgid "sRGB or Rec. 2020 if you can afford the bit-depth being 16bit." msgstr "sRGB eller Rek. 2020 om man har råd med 16-bitars bitdjup." #: ../../general_concepts/colors/color_managed_workflow.rst:344 msgid "" "Specialized CMYK profile from the printing house for the printed images." msgstr "Specialiserad CMYK-profil från tryckeriet för de utskrivna bilderna." #: ../../general_concepts/colors/color_managed_workflow.rst:346 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:348 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:351 msgid "Games" msgstr "Spel" #: ../../general_concepts/colors/color_managed_workflow.rst:360 msgid "sRGB or grayscale linear for roughness and specular maps." msgstr "" "sRGB eller linjär gråskala för avbildning av grova eller speglande ytor." #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "" "This one is tricky, but in the end it'll be sRGB for the regular player." msgstr "Den här är svår, men till sist blir det sRGB för den vanliga spelaren." #: ../../general_concepts/colors/color_managed_workflow.rst:364 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:366 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:368 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:370 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)." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:374 msgid "" "`Visualizing the XYZ color space `_." msgstr "" "`Visualisera XYZ-färgrymden `_." #: ../../general_concepts/colors/color_managed_workflow.rst:375 msgid "" "`Basics of gamma correction `_." msgstr "" "`Grunderna i gammakorrigering `_." #: ../../general_concepts/colors/color_managed_workflow.rst:376 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 `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:377 msgid "" "`2D examples of the effect of gamma-encoding on color maths `_." msgstr "" "`Tvådimensionella exempel på gamma-kodning i färgmatematik `_." #: ../../general_concepts/colors/color_managed_workflow.rst:378 msgid "" "`Basic overview of color management from ArgyllCMS manual `_." msgstr "" "Grundläggande översikt av färghantering från handboken för argylcms `_." diff --git a/locale/uk_UA/LC_MESSAGES/contributors_manual/krita_manual_conventions.po b/locale/uk_UA/LC_MESSAGES/contributors_manual/krita_manual_conventions.po index 1b0d22914..1fbb50f59 100644 --- a/locale/uk_UA/LC_MESSAGES/contributors_manual/krita_manual_conventions.po +++ b/locale/uk_UA/LC_MESSAGES/contributors_manual/krita_manual_conventions.po @@ -1,1493 +1,1493 @@ # Translation of docs_krita_org_contributors_manual___krita_manual_conventions.po to Ukrainian # Copyright (C) 2019 This_file_is_part_of_KDE # This file is distributed under the license LGPL version 2.1 or # version 3 or later versions approved by the membership of KDE e.V. # # Yuri Chornoivan , 2019. msgid "" msgstr "" "Project-Id-Version: " "docs_krita_org_contributors_manual___krita_manual_conventions\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-09 03:27+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: 2019-07-09 08:19+0300\n" "Last-Translator: Yuri Chornoivan \n" "Language-Team: Ukrainian \n" "Language: uk\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=4; plural=n==1 ? 3 : n%10==1 && n%100!=11 ? 0 : n" "%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;\n" "X-Generator: Lokalize 19.07.70\n" #: ../../:2 msgid "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: mouseleft" msgstr "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: mouseleft" #: ../../:4 msgid "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: mouseright" msgstr "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: mouseright" #: ../../:6 msgid "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: mousemiddle" msgstr "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: mousemiddle" #: ../../:8 msgid "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" msgstr "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" +#: ../../contributors_manual/krita_manual_conventions.rst:None +msgid "Horizontal Rulers" +msgstr "Горизонтальні лінійки" + #: ../../contributors_manual/krita_manual_conventions.rst:0 msgid "" ".. image:: images/sample.png\n" " :alt: an image." msgstr "" ".. image:: images/sample.png\n" " :alt: зображення." -#: ../../contributors_manual/krita_manual_conventions.rst:None -msgid "Horizontal Rulers" -msgstr "Горизонтальні лінійки" - #: ../../contributors_manual/krita_manual_conventions.rst:1 msgid "reStructuredText conventions for the Krita Manual" msgstr "Правила щодо коду reStructuredText для підручника з Krita" #: ../../contributors_manual/krita_manual_conventions.rst:16 msgid "Mark-up conventions for the Krita Manual" msgstr "Правила розмітки у підручнику з Krita" #: ../../contributors_manual/krita_manual_conventions.rst:18 msgid "" "This details the style conventions for using restructured text for the Krita " "Manual." msgstr "" "Тут докладно викладено вимоги до стильового оформлення тексту у форматі " "restructured для підручника з Krita." #: ../../contributors_manual/krita_manual_conventions.rst:20 msgid "" "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):" msgstr "" "Рекомендуємо ознайомитися із `офіційною специфікацією `_ reStructuredText і, оскільки ця специфікація " "зберігається на sourceforge, збережіть копію на ваш диск (на час написання " "цього підручника у sourceforge є проблеми із працездатністю серверів):" #: ../../contributors_manual/krita_manual_conventions.rst:23 msgid "" "`Primer `_" msgstr "" "`Настанови `_" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "User Manual:" msgstr "Посібник користувача:" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "" "`Quick Ref `_" msgstr "" "`Короткий довідник `_" #: ../../contributors_manual/krita_manual_conventions.rst:25 msgid "" "`Text Cheatsheet `_" msgstr "" "`Текстова шпаргалка `_" #: ../../contributors_manual/krita_manual_conventions.rst:27 msgid "" "`Introduction `_" msgstr "" "`Вступ `_" #: ../../contributors_manual/krita_manual_conventions.rst:28 msgid "" "`Markup `_" msgstr "" "`Розмітка `_" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "Reference Documentation:" msgstr "Довідкова документація:" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "" "`Directives `_" msgstr "" "`Директиви `_" #: ../../contributors_manual/krita_manual_conventions.rst:30 msgid "`Roles `_" msgstr "`Ролі `_" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "Sphinx specific docs:" msgstr "Специфічна документація до Sphinx:" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "" "`Sphinx' page on restructured text `_ -- This is useful for the specific " "sphinx directives and roles it uses to generate for example table of " "contents." msgstr "" "`Сторінка Sphinx щодо текстів restructured `_ — корисна для вивчення " "специфічних для sphinx команд та їхнього використання для створення, " "наприклад, таблиці змісту підручника." #: ../../contributors_manual/krita_manual_conventions.rst:34 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." msgstr "" "Існують відмінності між офіційною документацією reStructuredText та " "документацією sphinx, а також різні способи досягти того самого результату. " "У цьому підручнику описано рекомендовані способи форматування." #: ../../contributors_manual/krita_manual_conventions.rst:36 msgid "Contents" msgstr "Зміст" #: ../../contributors_manual/krita_manual_conventions.rst:39 msgid "Meta data" msgstr "Метадані" #: ../../contributors_manual/krita_manual_conventions.rst:41 msgid "Each page should start with the following three things:" msgstr "Кожна сторінка має розпочинатися з трьох елементів:" #: ../../contributors_manual/krita_manual_conventions.rst:44 msgid "" "This is a general description of the page. It will be converted to an html " "meta tag which will be used by search engines::" msgstr "" "Це загальний опис сторінки. Його буде перетворено на метамітку html, яка " "використовуватиметься рушіями пошуку::" #: ../../contributors_manual/krita_manual_conventions.rst:46 msgid "" ".. meta::\n" " :description:\n" " Description." msgstr "" ".. meta::\n" " :description:\n" " Опис." #: ../../contributors_manual/krita_manual_conventions.rst:49 msgid "A meta description" msgstr "Метаопис" #: ../../contributors_manual/krita_manual_conventions.rst:52 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::" msgstr "" "Просто для стеження за тим, хто редагував сторінку, та зазначення авторських " "прав. Дані має бути закоментовано, щоб комп'ютер не обробляв їх. Умовами " "ліцензування усього підручника є GDL 1.3, і про це також слід згадати::" #: ../../contributors_manual/krita_manual_conventions.rst:54 msgid "" ".. metadata-placeholder\n" "\n" " :authors: - Author 1\n" " - Author 2\n" " :license: GNU free documentation license 1.3 or later." msgstr "" ".. metadata-placeholder\n" "\n" " :authors: - Автор 1\n" " - Автор 2\n" " :license: GNU free documentation license 1.3 or later." #: ../../contributors_manual/krita_manual_conventions.rst:58 msgid "A list of authors and a license." msgstr "Список авторів та ліцензування." #: ../../contributors_manual/krita_manual_conventions.rst:61 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::" msgstr "" "Це список термінів, які відокремлено комами, призначений для індексування " "сторінки у :ref:`genindex`. Створений покажчик є доволі корисним для " "підручника у форматі PDF, а також читачів, яким потрібен пошук значень та " "прикладів за термінами. Список термінів визначається так::" #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid "Indexing terms." msgstr "Індексування термінів." #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid ".. index:: Keyword, Keyword with Spaces, ! Main Definition Keyword" msgstr "" ".. index:: Ключ, Ключове слово із пробілами, ! Ключове слово основного " "визначення" #: ../../contributors_manual/krita_manual_conventions.rst:66 msgid "" "This is so we can easily link to the page using ``:ref:`label_name```. Try " "to make this a nice variable name::" msgstr "" "Цей запис призначено для полегшення посилання на сторінку за допомогою коду " "``:ref:`назва_мітки```. Намагайтеся використовувати прості для використання " "назви змінних::" #: ../../contributors_manual/krita_manual_conventions.rst:68 msgid ".. _label_name:" msgstr ".. _назва_мітки:" #: ../../contributors_manual/krita_manual_conventions.rst:70 msgid "" "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." msgstr "" "Після мітки слід додати заголовок, оскільки ``:ref:`назва_мітки``` " "використовуватиме текст заголовка як замінник самого посилання." #: ../../contributors_manual/krita_manual_conventions.rst:71 msgid "A label." msgstr "Мітка." #: ../../contributors_manual/krita_manual_conventions.rst:74 msgid "Headings" msgstr "Заголовки" #: ../../contributors_manual/krita_manual_conventions.rst:76 msgid "Headings will be done in the following order::" msgstr "Заголовки буде створено у такому порядку::" #: ../../contributors_manual/krita_manual_conventions.rst:78 msgid "" "############\n" "Part/Section\n" "############\n" "\n" "For pages that have a lot of subpages.\n" "\n" "=========\n" "Heading 1\n" "=========\n" "\n" "Start most manual pages with this.\n" "\n" "Heading 2\n" "---------\n" "\n" "Heading 3\n" "~~~~~~~~~\n" "\n" "Heading 4\n" "^^^^^^^^^\n" "\n" "Heading 5\n" "'''''''''\n" "\n" "Heading 6\n" "\"\"\"\"\"\"\"\"\"" msgstr "" "############\n" "Частина/Розділ\n" "############\n" "\n" "Для сторінок, які містять багато підсторінок.\n" "\n" "===========\n" "Заголовок 1\n" "===========\n" "\n" "Починайте сторінки підручника з цього.\n" "\n" "Заголовок 2\n" "-----------\n" "\n" "Заголовок 3\n" "~~~~~~~~~~~\n" "\n" "Заголовок 4\n" "^^^^^^^^^^^\n" "\n" "Заголовок 5\n" "'''''''''''\n" "\n" "Заголовок 6\n" "\"\"\"\"\"\"\"\"\"\"\"" #: ../../contributors_manual/krita_manual_conventions.rst:105 msgid "" "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." msgstr "" "Усі ці правила більшою чи меншою мірою визначила програма для перетворення " "даних mediawiki `Pandoc `_ до reStructuredText. Якщо у " "вас більше 4 рівнів заголовків, переконайтеся, що сторінка не є надто " "складною і не потребує поділу на частини." #: ../../contributors_manual/krita_manual_conventions.rst:107 msgid "" "Sometimes you need to link to a subsection of a page, add a label above the " "heading in that case." msgstr "" "Іноді потрібне посилання на підрозділ сторінки. Для створення такого " "посилання додайте мітку над заголовком." #: ../../contributors_manual/krita_manual_conventions.rst:109 msgid "" "Headers should not end with punctuation, as the header will be used as the " "link name when linking to a label." msgstr "" "Заголовки не повинні завершуватися символами пунктуації, оскільки заголовок " "буде використано як замінник посилання у тексті." #: ../../contributors_manual/krita_manual_conventions.rst:112 msgid "Linking" msgstr "Компонування" #: ../../contributors_manual/krita_manual_conventions.rst:114 msgid "" "Linking is done with ``:ref:`label_name```. When you need an alternative " "link text, you use ``:ref:`actual text shown ```." msgstr "" "Посилання слід вказувати так: ``:ref:`назва_мітки```. Якщо замість самої " "мітки має бути показано якийсь текст, користуйтеся таким форматом: ``:ref:" "`показаний текст <назва_мітки>```." #: ../../contributors_manual/krita_manual_conventions.rst:116 msgid "" "Linking to external pages is done with ```url`_`` and ```link name " "`_``, which'll become `link name `_." msgstr "" "Для посилань на зовнішні сторінки використовується команда ```адреса`_`` або " "```назва посилання <адреса>`_``, яку буде показано так: `назва посилання " "<адреса>`_." #: ../../contributors_manual/krita_manual_conventions.rst:118 msgid "" "`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." msgstr "" "`Pandoc `_ перетворює посилання на " "```назва_посилання`__`` і потім додає ``.. __ :url`` наприкінці документа. " "Це так зване «анонімне посилання», що означає, що залежно порядок посилань " "наприкінці документа залежатиме від від порядку посилань у тексті. Це може " "здатися незручним та складним, але як уже є. У цьому полягає причина того, " "що ми намагаємося уникати таких посилань." #: ../../contributors_manual/krita_manual_conventions.rst:121 msgid "Footnotes and further reading" msgstr "Підрядкові примітки та посилання для подальшого читання" #: ../../contributors_manual/krita_manual_conventions.rst:123 msgid "" "Footnotes can be made in 3 ways, the most common one is with autonumbering, " "as per reference:" msgstr "" "Підрядкові посилання можна створювати у три способи. Найпоширенішим є спосіб " "із автоматичною нумерацією посилань:" #: ../../contributors_manual/krita_manual_conventions.rst:125 msgid "" "[#]_ is a reference to footnote 1, and [#]_ is a reference to footnote 2." msgstr "" "[#]_ є посиланням на підрядкову примітку 1, а [#]_ є посиланням на " "підрядкову примітку 2." #: ../../contributors_manual/krita_manual_conventions.rst:128 msgid "This is footnote 1." msgstr "Це підрядкова примітка 1." #: ../../contributors_manual/krita_manual_conventions.rst:129 msgid "This is footnote 2." msgstr "Це підрядкова примітка 2." #: ../../contributors_manual/krita_manual_conventions.rst:130 msgid "This is footnote 3." msgstr "Це підрядкова примітка 3." #: ../../contributors_manual/krita_manual_conventions.rst:132 msgid "[#]_ is a reference to footnote 3." msgstr "[#]_ є посиланням на підрядкову примітку 3." #: ../../contributors_manual/krita_manual_conventions.rst:134 msgid "Here is a citation reference: [CIT2002]_ ." msgstr "Ось цитата: [CIT2002]_ ." #: ../../contributors_manual/krita_manual_conventions.rst:136 msgid "" "This is the citation. It's just like a footnote, except the label is " "textual." msgstr "" "Це цитата. Вона подібна до підрядкової примітки, але мітка у ній є текстовою." #: ../../contributors_manual/krita_manual_conventions.rst:139 msgid "Citation can also be referenced with ```citation `_``." msgstr "На цитату також можна посилатися. Ось так: ```цитата `_``." #: ../../contributors_manual/krita_manual_conventions.rst:141 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." msgstr "" "Ми не використовуємо підрядкові посилання у підручнику через те, що вважаємо " "їх занадто академічними для наших читачів. Втім, ми збираємо посилання та " "документи, які викладають предмет сторінки ширше, наприкінці сторінки. У " "Sphinx передбачено команду ``.. seealso::`` для визначення зовнішніх " "посилань, а у reStructuredText використовують ``.. rubic:: Footnotes`` для " "спеціально зібраних підрядкових приміток, оскільки так зручніше для " "перетворення на код LaTeX." #: ../../contributors_manual/krita_manual_conventions.rst:145 msgid "Images" msgstr "Зображення" #: ../../contributors_manual/krita_manual_conventions.rst:147 msgid "Use the image directive for images without captions::" msgstr "Використання команди image для зображень без підписів::" #: ../../contributors_manual/krita_manual_conventions.rst:149 msgid "" ".. image:: /images/sample.png\n" " :width: 800\n" " :align: center\n" " :alt: an image." msgstr "" ".. image:: /images/sample.png\n" " :width: 800\n" " :align: center\n" " :alt: Зображення." #: ../../contributors_manual/krita_manual_conventions.rst:154 msgid "And figure directives for images with captions::" msgstr "І команди для роботи із зображеннями з підписами::" #: ../../contributors_manual/krita_manual_conventions.rst:156 msgid "" ".. figure:: /images/sample.png\n" " :figwidth: 800\n" " :align: center\n" " :alt: an image.\n" "\n" " A caption -- notice how the first letter is aligned with the :figwidth: " "option." msgstr "" ".. figure:: /images/sample.png\n" " :figwidth: 800\n" " :align: center\n" " :alt: Зображення.\n" "\n" " Підпис -- зауважте, як вирівнюється перша літера із використанням " "параметра :figwidth:." #: ../../contributors_manual/krita_manual_conventions.rst:163 msgid "The latter gives:" msgstr "Остання дає такий результат:" #: ../../contributors_manual/krita_manual_conventions.rst:170 msgid "" "A caption -- notice how the first letter of the caption in the directive is " "aligned with the :figwidth: option." msgstr "" "Підпис — зауважте, що перша літера підпису у команді вирівняна з параметром :" "figwidth:." #: ../../contributors_manual/krita_manual_conventions.rst:172 msgid "" "Images should go into the ``/images`` folder. By using ``/images`` instead " "of ``images``, sphinx will know the filepath isn't relative." msgstr "" "Зображення мають зберігатися у каталозі ``/images``. Використання ``/" "images`` замість ``images`` вказує sphinx на те, що шлях до файла не є " "відносним." #: ../../contributors_manual/krita_manual_conventions.rst:175 msgid "In-text Markup" msgstr "Розмітка у тексті" #: ../../contributors_manual/krita_manual_conventions.rst:177 msgid "" "You can make text *emphasized* and **strong** with a single asterisk and " "double respectively::" msgstr "" "Ви можете робити фрагмент тексту *курсивним* або **напівжирним** за " "допомогою однією або двох зірочок, відповідно::" #: ../../contributors_manual/krita_manual_conventions.rst:179 msgid "" "*emphasize*\n" "**strong**" msgstr "" "*emphasize*\n" "**strong**" #: ../../contributors_manual/krita_manual_conventions.rst:182 msgid "You cannot do both ***emphasized and strong***, so take a pick." msgstr "" "Не можна одночасно використовувати ***нахилений і напівжирний***, доведеться " "вибрати щось одне." #: ../../contributors_manual/krita_manual_conventions.rst:184 msgid "" "You can :sub:`subscript text` and :sup:`superscript text` by using ``:sub:" "`text``` and ``:sup:`text```" msgstr "" "Можна створювати :sub:`нижні індекси` та :sup:`верхні індекси` за допомогою " "команд ``:sub:`текст``` та ``:sup:`текст```" #: ../../contributors_manual/krita_manual_conventions.rst:186 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::" msgstr "" "Втім, користуйтеся цим дуже обережно! Бажано використовувати наявне " "семантичне форматування у sphinx за будь-яких умов, оскільки це полегшує " "перекладачам визначення того, для чого призначено текст::" #: ../../contributors_manual/krita_manual_conventions.rst:188 msgid "" ":menuselection:`Settings --> Configure Krita`\n" ":guilabel:`File`\n" ":kbd:`Ctrl + Z`\n" ":program:`Krita`" msgstr "" ":menuselection:`Параметри --> Налаштувати Krita`\n" ":guilabel:`Файл`\n" ":kbd:`Ctrl + Z`\n" ":program:`Krita`" #: ../../contributors_manual/krita_manual_conventions.rst:193 msgid "" "Avoid randomly bolding words. It does *not* make the text easier or " "friendlier to read." msgstr "" "Уникайте випадкового позначення слів зміною стилю шрифту. Текст із частою " "зміною ваги шрифту *не* простіше читати." #: ../../contributors_manual/krita_manual_conventions.rst:196 msgid "Substitution References" msgstr "Посилання на замінники" #: ../../contributors_manual/krita_manual_conventions.rst:198 msgid "" "You can create a sort of shorthand for a piece of text or an image by doing::" msgstr "" "Ви можете створити певний різновид скорочень для фрагментів тексту або " "зображень за допомогою такого коду::" #: ../../contributors_manual/krita_manual_conventions.rst:200 msgid ".. |shorthand| replace:: something or the other." msgstr ".. |shorthand| replace:: щось або ще щось." #: ../../contributors_manual/krita_manual_conventions.rst:202 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\"." msgstr "" "Це означає, що якщо ви використаєте ``|shorthand|``, у тексті його буде " "замінено на «something or the other». Це корисно для зображень і тексту, " "який має бути форматовано у складний спосіб, наприклад рядка «LaTeX»." #: ../../contributors_manual/krita_manual_conventions.rst:204 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." msgstr "" "У документації Krita використовуються ``|mouseleft|``, ``|mousemiddle|``, ``|" "mousescroll|`` та ``|mouseright|``, які перетворюються на |mouseleft|, |" "mousemiddle|, |mousescroll| і |mouseright|, відповідно. Ці коди визначено " "conf.py sphinx, вони додаються до кожного файла rst." #: ../../contributors_manual/krita_manual_conventions.rst:206 msgid "" "For links, if you reuse the same link over and over, you can write something " "like the following at the end of the file::" msgstr "" "Для посилань, якщо ви використовуєте посилання багато разів, ви можете " "написати щось подібне до такого наприкінці файла::" #: ../../contributors_manual/krita_manual_conventions.rst:208 msgid "" ".. _bugzilla: https://bugs.kde.org/\n" ".. _Krita Manual: https://docs.krita.org/" msgstr "" ".. _bugzilla: https://bugs.kde.org/\n" ".. _Krita Manual: https://docs.krita.org/" #: ../../contributors_manual/krita_manual_conventions.rst:211 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\"." msgstr "" "Далі, коли використовуватимете посилання, просто введіть ```bugzilla`_``, " "щоб отримати посилання на багзіллу зі словом-замінником посилання у тексті " "«bugzilla». ```Krita Manual`_`` буде перетворено на посилання на docs.krita." "org із текстом «Krita Manual»." #: ../../contributors_manual/krita_manual_conventions.rst:214 msgid "Lists" msgstr "Списки" #: ../../contributors_manual/krita_manual_conventions.rst:217 msgid "Ordinated lists" msgstr "Упорядковані списки" #: ../../contributors_manual/krita_manual_conventions.rst:219 msgid "Apple" msgstr "Яблуко" #: ../../contributors_manual/krita_manual_conventions.rst:220 msgid "Pear" msgstr "Груша" #: ../../contributors_manual/krita_manual_conventions.rst:221 msgid "Banana" msgstr "Банан" #: ../../contributors_manual/krita_manual_conventions.rst:223 msgid "Or..." msgstr "або…" #: ../../contributors_manual/krita_manual_conventions.rst:225 msgid "Table" msgstr "Стіл" #: ../../contributors_manual/krita_manual_conventions.rst:226 msgid "Chair" msgstr "Стілець" #: ../../contributors_manual/krita_manual_conventions.rst:227 msgid "Wardrobe." msgstr "Шафа." #: ../../contributors_manual/krita_manual_conventions.rst:229 msgid "Augustus" msgstr "Август" #: ../../contributors_manual/krita_manual_conventions.rst:230 msgid "Nero" msgstr "Нерон" #: ../../contributors_manual/krita_manual_conventions.rst:231 msgid "Caligula" msgstr "Калігула" #: ../../contributors_manual/krita_manual_conventions.rst:232 msgid "Trajan" msgstr "Траян" #: ../../contributors_manual/krita_manual_conventions.rst:234 msgid "They can be defined as follows::" msgstr "Такі списки визначаються ось так::" #: ../../contributors_manual/krita_manual_conventions.rst:236 msgid "" "1. Apple\n" "2. Pear\n" "3. Banana\n" "\n" "#. Apple\n" "#. Pear\n" "#. Banana\n" "\n" "A. Table\n" "B. Chair\n" "C. Wardrobe\n" "\n" "A. Table\n" "#. Chair\n" "#. Wardrobe\n" "\n" "I. Augustus\n" "#. Nero\n" "#. Caligula\n" "#. Trajan" msgstr "" "1. Яблуко\n" "2. Груша\n" "3. Банан\n" "\n" "#. Яблуко\n" "#. Груша\n" "#. Банан\n" "\n" "A. Стіл\n" "B. Стілець\n" "C. Шафа\n" "\n" "A. Стіл\n" "#. Стілець\n" "#. Шафа\n" "\n" "I. Август\n" "#. Нерон\n" "#. Калігула\n" "#. Траян" #: ../../contributors_manual/krita_manual_conventions.rst:258 msgid "Unordered lists" msgstr "Неупорядковані списки" #: ../../contributors_manual/krita_manual_conventions.rst:260 msgid "red" msgstr "червоний" #: ../../contributors_manual/krita_manual_conventions.rst:261 msgid "yellow" msgstr "жовтий" #: ../../contributors_manual/krita_manual_conventions.rst:263 msgid "seagreen" msgstr "морський зелений" #: ../../contributors_manual/krita_manual_conventions.rst:264 msgid "verdigris" msgstr "жовтаво-зелений" #: ../../contributors_manual/krita_manual_conventions.rst:265 msgid "teal" msgstr "синьо-зелений" #: ../../contributors_manual/krita_manual_conventions.rst:266 msgid "viridian" msgstr "темно-зелений" #: ../../contributors_manual/krita_manual_conventions.rst:268 msgid "dark emerald" msgstr "темно-смарагдовий" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "green" msgstr "зелений" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "emerald" msgstr "смарагдовий" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "light emerald" msgstr "світло-смарагдовий" #: ../../contributors_manual/krita_manual_conventions.rst:270 msgid "very light emerald." msgstr "дуже світлий смарагдовий." #: ../../contributors_manual/krita_manual_conventions.rst:271 msgid "blue" msgstr "синій" #: ../../contributors_manual/krita_manual_conventions.rst:273 msgid "Defined as such::" msgstr "Визначаються ось так::" #: ../../contributors_manual/krita_manual_conventions.rst:275 msgid "" "- red\n" "- yellow\n" "- green\n" " - seagreen\n" " - verdigris\n" " - teal\n" " - viridian\n" " - emerald\n" " - dark emerald\n" " - light emerald\n" " - very light emerald.\n" "- blue" msgstr "" "- червоний\n" "- жовтий\n" "- зелений\n" " - морська хвиля\n" " - мідянковий\n" " - зелено-синій\n" " - темно-зелений\n" " - смарагдовий\n" " - темно-смарагдовий\n" " - світло-смарагдовий\n" " - дуже світло-смарагдовий.\n" "- синій" #: ../../contributors_manual/krita_manual_conventions.rst:289 msgid "Definition Lists" msgstr "Списки визначень" #: ../../contributors_manual/krita_manual_conventions.rst:291 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." msgstr "" "Наше улюблене! Списки визначень особливо корисні при описів усіх пунктів на " "бічній панелі із короткими описами щодо кожного з них." #: ../../contributors_manual/krita_manual_conventions.rst:293 msgid "Definition" msgstr "Визначення" #: ../../contributors_manual/krita_manual_conventions.rst:294 #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Explanation." msgstr "Пояснення." #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Another option" msgstr "Інший варіант" #: ../../contributors_manual/krita_manual_conventions.rst:299 msgid "You can make them like this::" msgstr "Створити їх можна так::" #: ../../contributors_manual/krita_manual_conventions.rst:301 msgid "" "Definition\n" " Explanation.\n" "Another option\n" " Explanation." msgstr "" "Означення\n" " Пояснення.\n" "Інший варіант\n" " Пояснення." #: ../../contributors_manual/krita_manual_conventions.rst:304 msgid "To make them." msgstr "Для створення" #: ../../contributors_manual/krita_manual_conventions.rst:307 msgid "Tables" msgstr "Таблиці" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Purpose" msgstr "Призначення" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Table type" msgstr "Тип таблиці" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "listing shortcuts" msgstr "список клавіатурних скорочень" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "Simple table" msgstr "Проста таблиця" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "lots of colspans" msgstr "таблиця із багатьма стовпчиками" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "Grid table" msgstr "Таблиця із ґраткою" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "Simple but long" msgstr "Проста, але довга" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "List Table" msgstr "Таблиця-список" #: ../../contributors_manual/krita_manual_conventions.rst:317 msgid "Done as follows::" msgstr "Створено за допомогою такого коду::" #: ../../contributors_manual/krita_manual_conventions.rst:319 msgid "" "================== ============\n" "Purpose Table type\n" "================== ============\n" "listing shortcuts Simple table\n" "lots of colspans Grid table\n" "Simple but long List Table\n" "================== ============\n" "\n" "+-----------------+------------+\n" "|Purpose |Table Type |\n" "+=================+============+\n" "|listing shortcuts|Simple table|\n" "+-----------------+------------+\n" "|lots of colspans |Grid table |\n" "+-----------------+------------+\n" "|Simple but long |List table |\n" "+-----------------+------------+\n" "\n" ".. list-table::\n" " :header-rows: 1\n" "\n" " - * Purpose\n" " * Table Type\n" " - * listing shortcuts\n" " * simple table\n" " - * lots of colspans\n" " * grid table\n" " - * simple but long\n" " * list table" msgstr "" "============================= ============\n" "Призначення Тип таблиці\n" "============================= ==================\n" "список скорочень Проста таблиця\n" "багато об'єднаних стовпчиків Таблиця із ґраткою\n" "Проста, але довга Таблиця-список\n" "============================= ============\n" "\n" "+------------------------------+------------------+\n" "|Призначення |Тип таблиці |\n" "+==============================+==================+\n" "|список скорочень |Проста таблиця |\n" "+------------------------------+------------------+\n" "|багато об'єднаних стовпчиків |Таблиця з ґраткою |\n" "+------------------------------+------------------+\n" "|Проста, але довга |Таблиця-список |\n" "+------------------------------+------------------+\n" "\n" ".. list-table::\n" " :header-rows: 1\n" "\n" " - * Призначення\n" " * Тип таблиці\n" " - * список скорочень\n" " * проста таблиця\n" " - * багато об'єднаних стовпчиків\n" " * таблиця з ґраткою\n" " - * проста, але довга\n" " * таблиця-список" #: ../../contributors_manual/krita_manual_conventions.rst:349 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." msgstr "" "Таблиці із повноцінною ґраткою найкраще використовувати, коли вам потрібні " "усі можливості таблиці: складні стовпчики та об'єднані рядки, але код таких " "таблиць є доволі складним. З цієї причини слід віддавати перевагу простому " "коду малих таблиць, а для довгих таблиць використовувати команду ``list``, з " "якою простіше працювати." #: ../../contributors_manual/krita_manual_conventions.rst:352 msgid "Admonishments and asides" msgstr "Попередження та зауваження" #: ../../contributors_manual/krita_manual_conventions.rst:356 msgid "" "Admonishments are sort of like a separate section that the reader needs to " "pay attention to." msgstr "" "Попередження є типом окремих розділів із текстом, на який читач має звернути " "увагу." #: ../../contributors_manual/krita_manual_conventions.rst:358 msgid "" "Admonishments that can be used are the following (in order of seriousness):" msgstr "Можна використовувати такі попередження (за порядком критичності):" #: ../../contributors_manual/krita_manual_conventions.rst:362 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\"." msgstr "" "Підказки корисні для зазначення додаткових відомостей щодо теми, яких немає " "у основному тексті. Приклад підказки: «У openSuse ці пакунки мають інші " "назви, ніж у Debian»." #: ../../contributors_manual/krita_manual_conventions.rst:366 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\"." msgstr "" "Додаткові відомості щодо того, як щось зробити. Приклад: «Ви можете створити " "шаблон на основі ваших улюблених налаштувань документа» або «Скористайтеся " "клавішею M для віддзеркалення полотна — це полегшить виявлення помилок під " "час малювання»." #: ../../contributors_manual/krita_manual_conventions.rst:370 msgid "Something that is important to note, but is not necessarily negative." msgstr "Це щось, що варто зауважити, але не обов'язково у негативному сенсі." #: ../../contributors_manual/krita_manual_conventions.rst:374 msgid "This is in general when something is negative." msgstr "Загалом, це щось негативне." #: ../../contributors_manual/krita_manual_conventions.rst:378 msgid "" "General attention grabber. Use this when the subject is more important than " "warning, but not as important that is could get a dataloss." msgstr "" "Загальне привернення уваги. Скористайтеся цим, якщо тема є важливою, але не " "такою важливою, як, наприклад, втрата даних." #: ../../contributors_manual/krita_manual_conventions.rst:382 msgid "" "This is for things that could cause dataloss, like forgetting to save, or " "that Python currently has no undo functionality." msgstr "" "Це форматування для випадків, коли можлива втрата даних, зокрема через те, " "що дані не було збережено, або через те, що у додатках Python ще не " "передбачено можливості скасовування дій." #: ../../contributors_manual/krita_manual_conventions.rst:386 msgid "" "This should be for things that are dangerous for the computer in general, " "this includes things that can cause out of memory style freezes." msgstr "" "Цей варіант для речей, які є небезпечними для комп'ютера загалом, зокрема " "дій, які можуть призвести до «заморожування» системи через нестачу пам'яті." #: ../../contributors_manual/krita_manual_conventions.rst:390 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." msgstr "" "Ймовірно, не використовуватимуться у цьому підручнику. Sphinx може " "створювати такі сповіщення за визначеними вручну умовами, але у нашому " "варіанті цю можливість типово вимкнено." #: ../../contributors_manual/krita_manual_conventions.rst:392 msgid "Generic admonition that can have any text" msgstr "Загальне попередження із довільним текстом." #: ../../contributors_manual/krita_manual_conventions.rst:394 msgid "Text." msgstr "Текст." #: ../../contributors_manual/krita_manual_conventions.rst:396 msgid "You can make it like this::" msgstr "Створити його можна так::" #: ../../contributors_manual/krita_manual_conventions.rst:398 msgid "" ".. admonition:: Generic admonition that can have any text\n" "\n" " Text." msgstr "" ".. admonition:: Загальне попередження із довільним текстом.\n" "\n" " Текст" #: ../../contributors_manual/krita_manual_conventions.rst:404 msgid "Sphinx also adds::" msgstr "Sphinx також додає::" #: ../../contributors_manual/krita_manual_conventions.rst:406 msgid "" ".. seealso::\n" "\n" " Which is useful to collect external links and references." msgstr "" ".. seealso::\n" "\n" " Це корисно для збирання зовнішніх посилань." #: ../../contributors_manual/krita_manual_conventions.rst:414 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." msgstr "" "Горизонтальні лінійки зазвичай використовують, коли різко змінюють тему. " "Такі лінійки часто зустрічаються у оповідальних текстах, зокрема повістях чи " "романах. Підручник з Krita є інструкцією та довідником, тому ми, зазвичай, " "не використовуємо довгих оповідань про те, які різні елементи програми " "взаємодіють між собою. У нашому підручнику довгі текстові фрагменти " "покликані пояснити, чому певні дії виконуються у певний спосіб. Зміна теми " "трапляється, коли ми переходимо до наступного розділу, а не перемикаємося на " "якусь пов'язану із основною темою річ. Тому краще користуватися заголовками " "або командою ``.. Topic::``. Крім того, заголовки простіше читати." #: ../../contributors_manual/krita_manual_conventions.rst:418 msgid "That said, horizontal rulers can be made with ``----``." msgstr "Тобто, горизонтальні лінійки можна додавати за допомогою ``----``." #: ../../contributors_manual/krita_manual_conventions.rst:421 msgid "The rubric directive" msgstr "Команда рубрики" #: ../../contributors_manual/krita_manual_conventions.rst:422 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::" msgstr "" "Команда ``rubric`` є командою створення заголовка, який на перший погляд " "виглядає як команда «topic», але якщо тема (topic) складається з декількох " "абзаців, рубрика це сам заголовок. Ось так::" #: ../../contributors_manual/krita_manual_conventions.rst:424 msgid ".. rubric:: The rubric directive" msgstr ".. rubric:: Команда рубрики" #: ../../contributors_manual/krita_manual_conventions.rst:428 msgid "So, when to use these?" msgstr "Отже, коли нею слід користуватися?" #: ../../contributors_manual/krita_manual_conventions.rst:429 msgid "" "Only use them when you think the subject is too minor to have a proper " "heading." msgstr "" "Користуйтеся рубриками, лише якщо впевнені, що тема є надто незначною, щоб " "мати належний заголовок." #: ../../contributors_manual/krita_manual_conventions.rst:431 msgid "Topic" msgstr "Тема" #: ../../contributors_manual/krita_manual_conventions.rst:432 msgid "" "When the text is separated from the flow, so it goes into a different " "subject than the text itself is naturally going to." msgstr "" "Коли текст відокремлено від загального ходу думки сторінки, тобто він " "стосується іншої теми, поза межами теми сторінки." #: ../../contributors_manual/krita_manual_conventions.rst:433 msgid "Rubric" msgstr "Рубрика" #: ../../contributors_manual/krita_manual_conventions.rst:434 msgid "" "When the text isn't separated from the flow, but it does not need a header " "either." msgstr "" "Коли текст відокремлено від загального ходу думки сторінки, але він не " "потребує окремого заголовка." #: ../../contributors_manual/krita_manual_conventions.rst:436 msgid "Admonishments" msgstr "Попередження" #: ../../contributors_manual/krita_manual_conventions.rst:436 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." msgstr "" "Лише якщо є семантична відповідність. Це особливо важливо для попереджень " "щодо небезпеки, оскільки надто часте їхнє використання може призвести до " "того, що користувач не звертатиме на них уваги." #: ../../contributors_manual/krita_manual_conventions.rst:439 msgid "Code Snippets" msgstr "Фрагменти коду" #: ../../contributors_manual/krita_manual_conventions.rst:441 msgid "``Inline code snippets`` are done with ````backticks````." msgstr "" "``Вбудовані фрагменти коду`` можна створити за допомогою ````символів " "зворотних лапок````." #: ../../contributors_manual/krita_manual_conventions.rst:443 msgid "" "Multi-line code snippets are done by ending the previous section with ``::" "``, which'll look like this::" msgstr "" "Багаторядкові фрагменти коду можна створювати, завершуючи попередній щодо " "них абзац послідовністю символів ``::``. Виглядає це так::" #: ../../contributors_manual/krita_manual_conventions.rst:445 msgid "" "This is a paragraph, and we define a preformated snippet like so::\n" "\n" " Be sure to add a white space and a tab afterwards before starting the " "snippet." msgstr "" "Це абзац, і ми визначаємо попередньо форматований фрагмент, ось так::\n" "\n" " Не забудьте додати пробіл або табуляцію після, перед початком фрагмента." #: ../../contributors_manual/krita_manual_conventions.rst:449 msgid "" "You can also use the ``.. code::`` directive. If you add the language name " "after it, it'll do the appropriate syntax highlighting::" msgstr "" "Ви також можете скористатися командою ``.. code::``. Якщо ви додасте після " "неї назву мови програмування, текст буде оброблено відповідно до правил " "підсвічування синтаксичних конструкцій мови::" #: ../../contributors_manual/krita_manual_conventions.rst:451 msgid "" ".. code:: python\n" "\n" " # Python comment\n" " def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" ".. code:: python\n" "\n" " # Коментар Python\n" " def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" #: ../../contributors_manual/krita_manual_conventions.rst:459 msgid "Becomes" msgstr "Перетворюється на" #: ../../contributors_manual/krita_manual_conventions.rst:468 msgid "" "# Python comment\n" "def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" "# Коментар Python\n" "def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" #: ../../contributors_manual/krita_manual_conventions.rst:469 msgid "some more..." msgstr "щось інше…" #: ../../contributors_manual/krita_manual_conventions.rst:483 msgid "" "// C++ comment\n" "int myFunction(int i) {\n" " i += 1;\n" "\n" " // Check if more than 12\n" " if (i>12) {\n" " i = 0;\n" " }\n" " return i;\n" "}" msgstr "" "// Коментар C++\n" "int myFunction(int i) {\n" " i += 1;\n" "\n" " // Check if more than 12\n" " if (i>12) {\n" " i = 0;\n" " }\n" " return i;\n" "}" #: ../../contributors_manual/krita_manual_conventions.rst:498 msgid "" "/* CSS comment */\n" "body {\n" " margin: 0 auto;\n" " /* is 800 still sensible? */\n" " max-width:800px;\n" " font-size:16px;\n" " color:#333;\n" " background-color: #eee;\n" " padding:1em;\n" " font-family:serif;\n" " line-height: 1.4;\n" "}" msgstr "" "/* Коментар CSS */\n" "body {\n" " margin: 0 auto;\n" " /* is 800 still sensible? */\n" " max-width:800px;\n" " font-size:16px;\n" " color:#333;\n" " background-color: #eee;\n" " padding:1em;\n" " font-family:serif;\n" " line-height: 1.4;\n" "}" #: ../../contributors_manual/krita_manual_conventions.rst:502 msgid "" "

this is " "a paragraph.

" msgstr "" "

це наш " "абзац.

" #: ../../contributors_manual/krita_manual_conventions.rst:504 msgid "Other preformatted text" msgstr "Інший попередньо форматований текст" #: ../../contributors_manual/krita_manual_conventions.rst:507 msgid "One can" msgstr "Можна" #: ../../contributors_manual/krita_manual_conventions.rst:508 msgid "preformat" msgstr "створювати фрагменти із попередньо визначеним форматуванням" #: ../../contributors_manual/krita_manual_conventions.rst:509 msgid "text by" msgstr "тексту" #: ../../contributors_manual/krita_manual_conventions.rst:510 msgid "prepending" msgstr "додаванням" #: ../../contributors_manual/krita_manual_conventions.rst:511 msgid "each line" msgstr "до кожного рядка" #: ../../contributors_manual/krita_manual_conventions.rst:512 msgid "with a pipe" msgstr "символу" #: ../../contributors_manual/krita_manual_conventions.rst:513 msgid "symbol" msgstr "вертикальної риски" #: ../../contributors_manual/krita_manual_conventions.rst:515 msgid "Like so::" msgstr "Ось так::" #: ../../contributors_manual/krita_manual_conventions.rst:517 msgid "" "| One can\n" "| preformat\n" "| text by\n" "| prepending\n" "| each line\n" "| with a pipe\n" "| symbol" msgstr "" "| Зберегти\n" "| форматування\n" "| тексту\n" "| можна додавши\n" "| на початку\n" "| кожного рядка\n" "| символ вертикальної риски" #: ../../contributors_manual/krita_manual_conventions.rst:525 msgid "We don't actually use this anywhere in the manual." msgstr "Насправді, ніде у підручнику ми ще це не використовували." #: ../../contributors_manual/krita_manual_conventions.rst:528 msgid "Glossaries, Terms and Index" msgstr "Глосарії, списки термінів та покажчик" #: ../../contributors_manual/krita_manual_conventions.rst:530 msgid "These are sphinx features." msgstr "Це можливості sphinx." #: ../../contributors_manual/krita_manual_conventions.rst:532 msgid "" "Index is used in the top section, right now only single index entries are " "used." msgstr "" "Покажчик використовується у основному розділі. У поточній версії " "використовуються лише одинарні записи покажчика (без підлеглих записів)." #: ../../contributors_manual/krita_manual_conventions.rst:534 msgid "" "Glossaries are used for some of the menu entry sections, but not all of them." msgstr "" "Глосарії використовуються для деяких розділів щодо пунктів меню, але не для " "усіх." #: ../../contributors_manual/krita_manual_conventions.rst:537 msgid "Quotes" msgstr "Цитати" #: ../../contributors_manual/krita_manual_conventions.rst:539 msgid "Quotes are done like this::" msgstr "Цитати мають такий вигляд::" #: ../../contributors_manual/krita_manual_conventions.rst:541 msgid "" "I am not sure why you'd need quotes in a user manual...\n" "\n" "-- Wolthera" msgstr "" "Не певний, чи потрібні цитати у підручнику для користувачів...\n" "\n" "-- Wolthera" #: ../../contributors_manual/krita_manual_conventions.rst:545 msgid "This becomes a blockquote." msgstr "Це стане цитатою." #: ../../contributors_manual/krita_manual_conventions.rst:547 msgid "I am not sure why you'd need quotes in a user manual..." msgstr "Не певний, чи потрібні цитати у підручнику для користувачів..." #: ../../contributors_manual/krita_manual_conventions.rst:551 msgid "" "We do actually use quotes in some places. Try to add a link to the name to " "define where it came from." msgstr "" "Ми подекуди все використовуємо цитати. Намагайтеся додати посилання на " "ім'я, щоб вказати, чию цитату використано." #: ../../contributors_manual/krita_manual_conventions.rst:552 msgid "Wolthera" msgstr "Wolthera" #~ msgid "explanation." #~ msgstr "пояснення." #~ msgid "This looks like the following::" #~ msgstr "Це виглядає так::" diff --git a/locale/uk_UA/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po b/locale/uk_UA/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po index 91ea10d07..c4f3c9b30 100644 --- a/locale/uk_UA/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po +++ b/locale/uk_UA/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po @@ -1,1529 +1,1529 @@ # Translation of docs_krita_org_general_concepts___colors___color_managed_workflow.po to Ukrainian # Copyright (C) 2019 This_file_is_part_of_KDE # This file is distributed under the license LGPL version 2.1 or # version 3 or later versions approved by the membership of KDE e.V. # # Yuri Chornoivan , 2019. msgid "" msgstr "" "Project-Id-Version: " "docs_krita_org_general_concepts___colors___color_managed_workflow\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-08 03:08+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: 2019-08-02 11:50+0300\n" "Last-Translator: Yuri Chornoivan \n" "Language-Team: Ukrainian \n" "Language: uk\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=4; plural=n==1 ? 3 : n%10==1 && n%100!=11 ? 0 : n" "%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2;\n" "X-Generator: Lokalize 19.04.0\n" +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_matrix_profile.png" +msgstr ".. image:: images/color_category/Kiki_matrix_profile.png" + +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" +msgstr ".. image:: images/color_category/Kiki_cLUTprofiles.png" + #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group1.png" msgstr ".. image:: images/color_category/Krita_2_9_colormanagement_group1.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group2.png" msgstr ".. image:: images/color_category/Krita_2_9_colormanagement_group2.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group3.png" msgstr ".. image:: images/color_category/Krita_2_9_colormanagement_group3.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group4.png" msgstr ".. image:: images/color_category/Krita_2_9_colormanagement_group4.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/dockers/LUT_Management_Docker.png" msgstr ".. image:: images/dockers/LUT_Management_Docker.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR_1.svg" msgstr ".. image:: images/color_category/Krita_HDR_1.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR2.svg" msgstr ".. image:: images/color_category/Krita_HDR2.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_webcomic.svg" msgstr "" ".. image:: images/color_category/Krita-colormanaged-workflow_webcomic.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_print.svg" msgstr ".. image:: images/color_category/Krita-colormanaged-workflow_print.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_games.svg" msgstr ".. image:: images/color_category/Krita-colormanaged-workflow_games.svg" -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_matrix_profile.png" -msgstr ".. image:: images/color_category/Kiki_matrix_profile.png" - -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" -msgstr ".. image:: images/color_category/Kiki_cLUTprofiles.png" - #: ../../general_concepts/colors/color_managed_workflow.rst:1 msgid "How a color managed workflow works." msgstr "Як працювати із керуванням кольорами." #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "Color" msgstr "Колір" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "Color Management" msgstr "Керування кольорами" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "ICC Profiles" msgstr "Профілі ICC" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "OCIO" msgstr "OCIO" #: ../../general_concepts/colors/color_managed_workflow.rst:17 msgid "Color Managed Workflow" msgstr "Процедура керування кольорами" #: ../../general_concepts/colors/color_managed_workflow.rst:19 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." msgstr "" "Можливо, ви вже чули, що у Krita є щось, що називають «керування кольорами». " "Або, можливо, ви просто хочете дізнатися, що означають усі ці «моделі " "кольорів» та «профілі кольорів», які ви бачите у меню програми. Керування " "кольорами є доволі корисною річчю для тих, хто працює із цифровими " "зображеннями професійно. Сподіваємося, вміст цього розділу допоможе вам " "зрозуміти, чому це так." #: ../../general_concepts/colors/color_managed_workflow.rst:22 msgid "Basic Info" msgstr "Базові відомості" #: ../../general_concepts/colors/color_managed_workflow.rst:24 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." msgstr "" "Якщо ви раніше ніколи не працювати із керуванням кольорами і гадки не маєте, " "що це таке, знайте — ви, ймовірно, працювали у 8-бітовому просторі кольорів " "RGB із профілем sRGB. Це означає, що ви можете вибрати *sRGB built-in* або " "*sRGB-elle-v2-srgbtrc.icc*. Якщо панель навігації просторами кольорів буде " "відкрито вперше, цей профіль буде позначено як *(типовий)*, якщо використано " "8-бітову глибину кольорів." #: ../../general_concepts/colors/color_managed_workflow.rst:26 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." msgstr "" "Ми розберемо теоретичне значення усіх згаданих вище термінів, але якщо ви " "відкрили цю сторінку, намагаючись визначити типові налаштування програми, " "тепер ви їх знаєте. Можливо, після прочитання цього розділу вам захочеться " "змінити типові параметри роботи, щоб отримати нові та цікаві результати від " "застосування фільтрів, режимів змішування або просто пензля розмазування " "кольорів." #: ../../general_concepts/colors/color_managed_workflow.rst:29 msgid "What is the problem?" msgstr "У чому проблема?" #: ../../general_concepts/colors/color_managed_workflow.rst:31 msgid "" "To explain the point of color management, you'd first need to learn which " "problem color management tries to solve." msgstr "" "Щоб зрозуміти пояснення щодо керування кольорами, вам спочатку слід " "розібратися із тим, яку проблему вирішує керування кольорами." #: ../../general_concepts/colors/color_managed_workflow.rst:33 msgid "Let us imagine a kinder garden:" msgstr "Уявімо собі дитячий садок:" #: ../../general_concepts/colors/color_managed_workflow.rst:35 msgid "" "The class of 28 children is subdivided in groups of 7. Each group has its " "own table." msgstr "" "Клас із 28 дітей поділено на групи по 7 дітей. У кожної групи є власна " "таблиця." #: ../../general_concepts/colors/color_managed_workflow.rst:37 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." msgstr "" "Вихователь дає завдання: треба намалювати червоний трикутник, синій квадрат, " "зелений круг і жовту рамку навколо усього намальованого. Діти вже добре " "обізнані у малюванні, отже вихователь може упевнено дозволити " "найдосвідченішим з них виконати роботу самостійно і може зосередитися на " "допомозі тим, хто її потребує." #: ../../general_concepts/colors/color_managed_workflow.rst:40 msgid "The following results come from painting:" msgstr "Малювання дає такі результати:" #: ../../general_concepts/colors/color_managed_workflow.rst:42 msgid "" "Even though all groups had the same assignment, each group's result looks " "different." msgstr "" "Хоча усі групи мали однакове завдання, результати у кожній групі виглядають " "по-різному." #: ../../general_concepts/colors/color_managed_workflow.rst:49 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." msgstr "" "У групи 1 були у розпорядженні карміново-червоний, лимонно-жовтий та " "ультрамариновий синій. Це означає, що трикутники у них є красивими і " "червоними, але круг має дещо болотяний відтінок. Причина полягає у тому, що " "ультрамарин є надто темним відтінком синього, щоб у поєднанні із жовтим дати " "красивий зелений колір." #: ../../general_concepts/colors/color_managed_workflow.rst:56 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." msgstr "" "У групи 2 був малиновий червоний, лимонно-жовтий та лазурово-блакитний. " "Малиновий — різновид червоного кольору, який є ближчим до рожевого, на " "відміну від кармінового, який є ближчим до помаранчевого. Втім, зелений круг " "виглядає добре, оскільки лазуровий є набагато світлішим відтінком синього." #: ../../general_concepts/colors/color_managed_workflow.rst:64 msgid "" "Group 3 had vermillion red, citron yellow, emerald green and cerulean blue. " "They didn't mix their green, and thus ended up with a purer color." msgstr "" "У групи 3 був карміново-червоний, лимонно-жовтий, смарагдовий зелений та " "лазурово-блакитний. Цим дітям не довелося змішувати кольори для отримання " "зеленого, тому колір кругу є чистішим." #: ../../general_concepts/colors/color_managed_workflow.rst:71 msgid "" "Finally, group 4 has vermillion red, citron yellow and cerulean blue. Their " "colors probably look like what you imagined." msgstr "" "Нарешті, у групи 4 був карміново-червоний, лимонно-жовтий та лазурово-" "блакитний. Кольори дітей з цієї групи є, ймовірно, тими, які ви сподівалися " "побачити." #: ../../general_concepts/colors/color_managed_workflow.rst:73 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!" msgstr "" "Гаразд, це лише діти з дитячого садка, тому проблеми, які тут виникли, не " "мають значної ваги. Втім, уявіть собі, що щось подібне трапилося у " "видавництві. Уявіть чотири друкарські верстати, які друкують той самий " "журнал, але у зовсім різних кольорах. Це була б катастрофа!" #: ../../general_concepts/colors/color_managed_workflow.rst:75 msgid "For this purpose, we invented color management." msgstr "" "Саме для того, щоб уникнути цих проблем, і винайшли керування кольорами." #: ../../general_concepts/colors/color_managed_workflow.rst:78 msgid "What is color management?" msgstr "Що таке керування кольорами?" #: ../../general_concepts/colors/color_managed_workflow.rst:80 msgid "" "Color management is, dryly put, a set of systems that tries to have the same " "color translate properly between color devices." msgstr "" "Керування кольорами, якщо коротко, це набір правил, який допомагає належним " "чином переносити кольори між пристроями, які працюють із кольорами." #: ../../general_concepts/colors/color_managed_workflow.rst:82 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." msgstr "" "Зазвичай, таке перенесення відбувається шляхом відображення кольорів до " "еталонного простору кольорів XYZ. XYZ — координатна система, у якій є точка " "для кожного кольору, який може бачити людське око." #: ../../general_concepts/colors/color_managed_workflow.rst:84 msgid "" "From XYZ it can then be translated back into another device space, such as " "RGB (for screens), or CMYK (for printers)." msgstr "" "Комп'ютер переносить дані з XYZ до простору іншого пристрою, зокрема до RGB " "(для екранів комп'ютерів) або CMYK (для принтерів)." #: ../../general_concepts/colors/color_managed_workflow.rst:86 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." msgstr "" "У Krita передбачено дві системи для керування кольорами. З одного боку, у " "нас є **lcms2**, яка працює із профілями ICC, а з іншого — **OCIO**, яка " "працює із керуванням кольорами за таблицями пошуку (LUT)." #: ../../general_concepts/colors/color_managed_workflow.rst:88 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." msgstr "" "Якщо грубо, профілі ICC призначено для підтримання сумісності кольорів між " "різновидами пристроїв (екранами, принтерами) на основі еталонного простору, " "а OCIO працює із інтерпретаціями відповідних кольорів." #: ../../general_concepts/colors/color_managed_workflow.rst:90 msgid "Within both we can identify the following color spaces:" msgstr "Для обох систем ми можемо говорити про такі простори кольорів:" #: ../../general_concepts/colors/color_managed_workflow.rst:93 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 " "`." msgstr "" "Простори пристроїв — простори, які описують роботу, наприклад, вашого " "монітора. Їх створюють невеличкі пристрої, які називають колориметрами. Такі " "пристрої у поєднанні із належним програмним забезпеченням вимірюють " "найяскравіші червоний, зелений і синій кольори, які може бути відтворено " "екраном, а також параметри білого, чорного і сірого кольору. На основі цих " "та декількох інших вимірювань пристрій створює унікальний профіль ICC " "екрана. Такий профіль можна встановити за допомогою вкладки керування " "кольорами у Krita. Типово, програма припускає профіль sRGB для екранів, але, " "дуже ймовірно, що ваш екран не повністю відповідає sRGB, особливо якщо ви " "користуєтеся високоякісним екраном, який може відтворювати кольори із значно " "ширшого простору. Крім того, існування просторів пристроїв призводить до " "того, що перед друком слід обов'язково визначити, на який профіль кольорів " "розраховано ваш принтер. Багато виробників принтерів створюють власні " "профілі пристроїв для принтерів або реалізують перетворення кольорів за " "допомогою власних драйверів. Докладніший опис роботи з колориметрами " "наведено :ref:`тут `." #: ../../general_concepts/colors/color_managed_workflow.rst:94 msgid "Device spaces" msgstr "Простори пристроїв" #: ../../general_concepts/colors/color_managed_workflow.rst:96 msgid "Working spaces" msgstr "Робочі простори" #: ../../general_concepts/colors/color_managed_workflow.rst:97 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." msgstr "" "Ці простори є частиною пакунка Krita для ICC, а для OCIO їх можна отримати з " "сайта OCIO. У робочих просторах, зокрема, зручно виконувати обчислення з " "кольорами, які часто виконують програми, подібні до Krita. Тому рекомендуємо " "використовувати під час роботи з вашим зображенням профіль робочого простору." #: ../../general_concepts/colors/color_managed_workflow.rst:99 msgid "Aesthetic or Look spaces" msgstr "Естетичні простори або простори вигляду" #: ../../general_concepts/colors/color_managed_workflow.rst:99 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." msgstr "" "Це спеціальні простори, які викривлено так, щоб надати зображенню певного " "вигляду. До пакунка Krita не включено профілі вигляду для ICC, а у OCIO " "підтримку просторів вигляду ще не реалізовано." #: ../../general_concepts/colors/color_managed_workflow.rst:102 msgid "Color managed workflow" msgstr "Процедура керування кольорами" #: ../../general_concepts/colors/color_managed_workflow.rst:104 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:" msgstr "" "Загальні знання щодо цих просторів, звичайно ж, не нададуть вам уміння " "користуватися ними, але спростять пояснення способів їхнього використання. " "Отже, погляньмо на типову процедуру керування кольорами:" #: ../../general_concepts/colors/color_managed_workflow.rst:110 msgid ".. image:: images/color_category/Krita-colormanaged-workflow_text.svg" msgstr ".. image:: images/color_category/Krita-colormanaged-workflow_text.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:110 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." msgstr "" "Типовий приклад робочого процесу із керуванням кольорами. Маємо вхідні дані " "зі сканерів та фотокамер, які ми перетворюємо до робочого простору, яким " "можна користуватися у різному програмному забезпеченні для редагування, " "потім перетворюємо дані до простору виведення даних для перегляду на екрані " "або друку." #: ../../general_concepts/colors/color_managed_workflow.rst:112 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." msgstr "" "У традиційному робочому процесі із керуванням кольорами ми, зазвичай, " "працюємо із перетворенням природних кольорів на комп'ютерні кольори, і " "навпаки. Отже, розгляньмо, наприклад, фотографії з фотокамери або скановані " "зображення. Якщо є простір пристрою для вхідних даних, ми спочатку " "пов'язуємо відповідний простір пристрою із зображенням, а потім перетворюємо " "зображення до робочого простору." #: ../../general_concepts/colors/color_managed_workflow.rst:114 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." msgstr "" "Далі, виконуємо редагування у робочому просторі і використовуємо робочий " "простір для обміну даними між програмами. У випадку Krita, через існування " "двох систем керування кольорами ми використовуємо профілі ICC для обміну " "даними з програмами, зокрема GIMP 2.9+, Inkscape, digiKam та Scribus, і " "налаштування OCIO для обміну даними з Blender та Natron." #: ../../general_concepts/colors/color_managed_workflow.rst:116 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." msgstr "" "Крім того, зберігаємо робочі файли у робочому просторі, подібно до того, як " "ви зберігаєте у робочому файлів роз'єднані шари або використовуєте у ньому " "високу роздільну здатність." #: ../../general_concepts/colors/color_managed_workflow.rst:118 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." msgstr "" "Іноді, як частину процесу редагування, ми застосовуємо естетичні простори " "або простори вигляду до зображення. Це приклад доволі складного способу " "обробки, ймовірно, не варто ним перейматися у випадку Krita." #: ../../general_concepts/colors/color_managed_workflow.rst:120 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." msgstr "" "Далі, коли редагування завершено, ми перетворюємо кольори до простору " "кольорів виведення, який є простором кольорів ще одного пристрою. Це може " "бути CMYK для принтерів або спеціальний профіль RGB екрана. Якщо ви маєте " "справу із професійною друкарнею, варто проконсультуватися там, перш ніж " "виконувати цей крок. Працівники друкарні мають більший досвід із " "перетворенням кольорів. Можливо, варто довіритися саме їм у перетворенні з " "робочого простору до простору пристроїв принтерів друкарні." #: ../../general_concepts/colors/color_managed_workflow.rst:122 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." msgstr "" "Іншою формою виведення даних є показ кольорів на дисплеях. На відміну від " "звичайного виведення даних воно виконується увесь час під час редагування: " "що б там не було, а вам завжди потрібно бачити результати роботи. Але екран " "теж є пристроєм зі своїм простором кольорів, тому він теж викривляє вигляд " "зображення. Ваш екран можна уявити як набір біноклів, крізь які ви дивитеся " "на ваше зображення." #: ../../general_concepts/colors/color_managed_workflow.rst:124 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." msgstr "" "Тому, без профільованого монітора ви не матимете уявлення, як насправді " "виглядають кольори вашого зображення, оскільки комп'ютер не знає про " "відповідні властивості вашого екрана. Отже, якщо ви профілювали ваш монітор, " "надали Krita його профіль за допомогою параметрів програми і вибрали простір " "sRGB для малювання, ви вперше бачите справжні кольори простору sRGB." #: ../../general_concepts/colors/color_managed_workflow.rst:127 msgid "So what does this mean?" msgstr "Отже, що це все значить?" #: ../../general_concepts/colors/color_managed_workflow.rst:133 msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_krita_text.svg" msgstr "" ".. image:: images/color_category/Krita-colormanaged-workflow_krita_text.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:133 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." msgstr "" "Якщо малювання виконується «з нуля», профіль екрана можна розглядати як " "вхідний простір кольорів, оскільки він використовується для вибору кольорів. " "Це дещо спрощує робочий процес, але робить профілювання екрана та умови " "перегляду важливішими." #: ../../general_concepts/colors/color_managed_workflow.rst:135 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*." msgstr "" "Фотомитці та ті, хто володіє примхливим мистецтвом візуальних ефектів, яке " "називається «виправленням кольорів», можуть намагатися до запаморочення " "досягти 100% правильного вигляду кольорів, враховуючи навіть такі фактори, " "як пора доби чи кольори, у які пофарбовано стіни. Наприклад, якщо стіну за " "монітором пофарбовано у червоний колір, чутливість ваших очей до червоного " "кольору зменшиться, а це означає, що кольори на екрані здаватимуться " "червонішими. Це називається *умови перегляду*." #: ../../general_concepts/colors/color_managed_workflow.rst:137 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." msgstr "" "На щастя, художникам не слід цим надто перейматися. Оскільки ілюстрації — " "повністю ручна робота, можна ідентифікувати важливі речі і створити " "відповідні контрасти між кольорами. Це означає, що навіть якщо наше " "зображення виглядатиме дещо червонішим, ніж ми сподівалися, ймовірність, що " "його буде зіпсовано, менша. Якщо повернутися до нашого прикладу із дитячим " "садком, неточні кольори не завадять нам зрозуміти, як мало виглядати " "зображення, хоча на кожному із його варіантів ми бачимо різні кольори. " "Більше того, оскільки кольори на ілюстраціях вибрано довільним чином, нам " "згодом буде просто їх виправити. Втім, одночасно, звичайно ж, було б добре " "мати правильні кольори, — у нас би був набагато ширший простір для маневрів, " "якби ми могли взяти до уваги умови перегляду." #: ../../general_concepts/colors/color_managed_workflow.rst:139 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." msgstr "" "Звідси можна зробити висновок, що для художників теж дуже корисним є " "розуміння робочих просторів. Використання різних робочих просторів дає різні " "результати при фільтруванні та змішуванні, і лише деякі робочі простори " "можна використовувати разом із новітніми технологіями, зокрема для зображень " "із широким динамічним діапазоном (HDR)." #: ../../general_concepts/colors/color_managed_workflow.rst:141 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." msgstr "" "Так само, Krita, як програма для створення зображень «з нуля», не " "переймається призначенням робочих просторів після створення зображення. Але " "оскільки ви використовуєте екран як бінокль для перегляду вашого зображення " "і вибору кольорів, ви можете розглядати простір кольорів пристрою вашого " "екрана як вхідний простір зображення. Ось чому профілювання вашого монітора " "і визначення його профілю у параметрах роботи Krita може допомогти у " "приготуванні вашої роботи до друку та подальшій роботі у довгостроковій " "перспективі." #: ../../general_concepts/colors/color_managed_workflow.rst:143 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.)" msgstr "" "Загалом, корисно мати на увазі речі, подібні до умов перегляду. Багато " "професійних художників використовують помірно-сірий колір як типовий колір " "тла полотна, оскільки таким чином вони досягають динамічнішого ефекту на " "зображеннях через поліпшення умов перегляду. Це також одна з причин, чому " "багато програм для роботи з графікою, зокрема Krita, типово використовують " "темні теми оформлення інтерфейсу. (Втім, звичайно ж, причиною може бути і " "проста мода на темні теми, як знати.)" #: ../../general_concepts/colors/color_managed_workflow.rst:148 msgid "ICC profiles" msgstr "Профілі ICC" #: ../../general_concepts/colors/color_managed_workflow.rst:150 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:" msgstr "" "Профіль ICC є набором координат, які описують межі простору кольорів " "пристрою у XYZ, а також дані щодо керування кольорами, які використовують " "для надсилання даних з вашого робочого простору до принтерів та програм, які " "розроблено для друкарської справи, зокрема GIMP, Scribus, Photoshop, " "Illustrator, Inkscape, digiKam, RawTheraphee тощо. Передбачено два типи " "профілів ICC:" #: ../../general_concepts/colors/color_managed_workflow.rst:153 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." msgstr "" "Ці профілі постачаються разом із Krita. Профілі Matrix shaper визначаються " "встановленням параметрів та інтерполяцією між ними для отримання точного " "розміру простору кольорів. Через це засіб навігації просторами кольорів " "Krita може надати вам багато інформації щодо цих профілів. Такі профілі " "також є пріоритетними як робочі простори." #: ../../general_concepts/colors/color_managed_workflow.rst:159 msgid "Matrix Shaper profiles" msgstr "Профілі Matrix Shaper" #: ../../general_concepts/colors/color_managed_workflow.rst:159 msgid "" "Matrix shaper profiles have a few parameters that describe the color space " "which are then interpolated between, this requires a lot of maths." msgstr "" "Профілі Matrix shaper визначаються декількома параметрами опису простору " "кольорів, між якими дані простору кольорів інтерполюють, а це вимагає " "значних математичних обчислень." #: ../../general_concepts/colors/color_managed_workflow.rst:162 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." msgstr "" "Ці профілі є рідкісними. Їхнім основним призначенням є опис кольорів " "принтерів, зокрема CMYK. Профілі cLUT або профілі Color Look-up Table " "(пошуку кольорів за таблицею) містять набагато більше даних за профілі " "Matrix shaper. Там можуть зберігатися дані щодо незначних особливостей, які " "спричинено, наприклад, неочікуваними результатами змішування пігментів. Це " "набагато приземленіший шлях до опису простору кольорів, ось чому у багатьох " "програмах, розробники яких не переймаються керуванням кольорами, підтримки " "таких профілів не передбачено." #: ../../general_concepts/colors/color_managed_workflow.rst:168 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." msgstr "" "Профілі cLUT працюють на основі таблиць для кожного з кольорів у просторі " "кольорів та даних щодо відносних координат кольорів у еталонному просторі. " "Для CMYK це, типово, L\\*A\\*B\\*, а для решти просторів кольорів — XYZ. " "Такі таблиці важко створити, тому профілі цього типу є дуже рідкісними." #: ../../general_concepts/colors/color_managed_workflow.rst:169 msgid "cLUT profiles" msgstr "Профілі cLUT" #: ../../general_concepts/colors/color_managed_workflow.rst:171 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." msgstr "" "Цікавою особливістю профілів ICC є те, що ваш робочий простір може бути " "ширшим за простір пристрою. Зазвичай, у цьому немає нічого поганого. Втім, " "під час перетворення між цими просторами кольорів виникає питання щодо того, " "як передавати значення з одного простору до іншого." #: ../../general_concepts/colors/color_managed_workflow.rst:174 msgid "Perceptual" msgstr "Придатне для сприйняття відтворення" #: ../../general_concepts/colors/color_managed_workflow.rst:174 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." msgstr "" "У цьому режимі програма стискає значення з робочого простору до простору " "перетворення. Цей чудовий спосіб побачити усі можливі значення, але він не є " "надто точним у відтворенні кольорів. Користуйтеся ним, якщо ви хочете " "побачити усі кольори на зображенні або хочете виразити усі можливі " "контрасти. Цей режим не працює з профілями Matrix Shaper, типово " "перетворюючись на відносний колориметричний." #: ../../general_concepts/colors/color_managed_workflow.rst:177 msgid "Absolute Colorimetric" msgstr "Абсолютне колориметричне відтворення" #: ../../general_concepts/colors/color_managed_workflow.rst:177 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." msgstr "" "Протилежність придатного до сприйняття. У режимі абсолютного " "колориметричного відтворення програма намагається зберегти усі правильні " "кольори за будь-яку ціну, що може призвести до жахливого вигляду кольорів. " "Рекомендовано використовувати лише для репродукцій. Не працює з профілями " "Matrix Shaper у Krita через дотримання програмою стандартів робочого процесу " "ICC v4." #: ../../general_concepts/colors/color_managed_workflow.rst:180 msgid "Relative Colorimetric" msgstr "Відносне колориметричне відтворення" #: ../../general_concepts/colors/color_managed_workflow.rst:180 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." msgstr "" "Проміжний варіант між придатним для сприйняття та абсолютним " "колориметричним. У режимі відносного колориметричного відтворення програма " "намагається встановити найкращу відповідність між просторами кольорів. Це " "завдання виконується шляхом вирівнювання точок білого і чорного кольорів у " "просторах. Усе, що виходить за відповідні межі, обрізається. Це типовий " "режим перетворення для усіх профілів matrix shaper, оскільки робочим " "процесом ICC v4 передбачено використання для профілів matrix shaper лише " "відносного колориметричного відтворення." #: ../../general_concepts/colors/color_managed_workflow.rst:183 msgid "Saturation" msgstr "Насиченість" #: ../../general_concepts/colors/color_managed_workflow.rst:183 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." msgstr "" "Зберігає кольоровість за будь-яку ціну, навіть шляхом втрати відтінків. " "Використовується для інфографіки. Не працює із профілями Matrix Shaper, " "типовим відтворенням є відносне колориметричне." #: ../../general_concepts/colors/color_managed_workflow.rst:185 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." msgstr "" "*Версія профілю ICC* — це остання річ, яку слід взяти до уваги при роботі з " "профілями ICC. До складу пакунка Krita включено профілі версій 2 та 4. " "Останні дають кращі результати при виконання математичних дій з кольорами, а " "у перших ширша підтримка (як можна бачити у наведених нижче даних щодо " "сумісності з іншими програмами). Ось чому типовими для Krita є профілі " "версії 2. Ми рекомендуємо використовувати версію 2, якщо ви не певні щодо " "того, чи передбачено в інших програмах, якими ви користуєтеся підтримку " "версії 4." #: ../../general_concepts/colors/color_managed_workflow.rst:188 msgid "LUT docker and HDR imaging" msgstr "" "Бічна панель таблиці пошуку та робота із зображеннями із широким динамічним " "діапазоном" #: ../../general_concepts/colors/color_managed_workflow.rst:196 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." msgstr "" ":ref:`lut_docker` є другим важливим інструментом керування кольорами у " "Krita, інструментом, який є спільним для Krita і програм, подібних до " "Blender, Natron і Nuke, і який використовує лише таблиці пошуку (Look Up " "Tables), які визначено у файлі налаштувань." #: ../../general_concepts/colors/color_managed_workflow.rst:198 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." msgstr "" "Ви можете встановити робочий простір зображення у полі для простору кольорів " "вхідних даних і показати дані у дані зображення у sRGB або вашій власній " "LUT, якщо ви додали її у налаштуваннях. У цьому випадку перегляд буде у " "формі проби кольорів для певного пристрою для показу." #: ../../general_concepts/colors/color_managed_workflow.rst:200 msgid "" "Component, exposure, gamma, whitepoint and blackpoint are knobs which allows " "you to modify the display filter." msgstr "" "Кнопки компонента, експозиції, гамми, точки білого та точки чорного надають " "вам змогу змінити фільтр показу." #: ../../general_concepts/colors/color_managed_workflow.rst:208 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." msgstr "" "Як ми вже пояснювали, монітор можна розглядати як бінокль або телескоп, які " "спрямовано у світ нашого зображення. Це означає, що він певним чином " "викривляє вигляд зображення. Але ми можемо внести зміни до цього бінокля або " "додати фільтр перегляду, щоб бачити зображення інакше. Наприклад, це може " "надати нам змогу бачити білий колір на зображенні, де білий є білішим за " "білий колір на екрані. Щоб пояснити, як це працює, нам слід детальніше " "розглянути поняття «білий колір»." #: ../../general_concepts/colors/color_managed_workflow.rst:210 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." msgstr "" "Наприклад, білий на нашому моніторі складається із найяскравішого червоного, " "найяскравішого зеленого і найяскравішого синього. Але він, напевне, " "відрізняється від білого на нашому папері, кольору молока, білого на сонці " "або навіть білого на дисплеї мобільного телефону." #: ../../general_concepts/colors/color_managed_workflow.rst:212 msgid "" "Black similarly, is brighter on a LCD display than a LED one, and " "incomparable with the black of a carefully sealed room." msgstr "" "Чорний, так само, є яскравішим на рідкокристалічному дисплеї, ніж на " "електропроменевому дисплеї, його навіть не можна порівняти із чорним у " "належним чином світлоізольованій кімнаті." #: ../../general_concepts/colors/color_managed_workflow.rst:214 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." msgstr "" "Це означає, що потенційно існують чорніші за чорний колір на екрані чорні " "кольори і існують біліші за колір на екрані білі кольори. Втім, для " "простоти, ми все одно встановлюємо певні значення для точки чорного кольору " "і точки білого кольору. На основі цих значень ми можемо визначити, чи є " "білий білішим за точку білого або чи є чорний чорнішим за точку чорного." #: ../../general_concepts/colors/color_managed_workflow.rst:216 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." msgstr "" "Бічна панель пошуку за таблицею надає нам змогу керувати цим фільтром показу " "і змінювати викривлення. Це корисно, якщо ми почали вносити зміни до " "зображення, яке було створено із значеннями, які пов'язано зі сценою, " "зокрема до фотографій з широким динамічним діапазоном або зображень, які " "отримано від рушія просторового моделювання." #: ../../general_concepts/colors/color_managed_workflow.rst:224 msgid "" "So, for example, we can choose to scale whiter-than-screen-white to our " "screen-white so we can see the contrasts there." msgstr "" "Отже, наприклад, ми можемо вибрати масштабування кольору, який є білішим за " "білий на екрані, до білого на екрані так, щоб можна було бачити контрасти." #: ../../general_concepts/colors/color_managed_workflow.rst:226 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." msgstr "" "Суть у тому, що ви можете скористатися перевагами детальнішою освітленістю " "на зображенні. Хоча ви не зможете побачити різниці між білим на екрані та " "білішим-за-білий-на-екрані (оскільки ваш екран просто не може показати цієї " "різниці), графічні програми, звичайно ж, можуть використовувати цю різницю." #: ../../general_concepts/colors/color_managed_workflow.rst:228 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." msgstr "" "Типовим прикладом є встановлення відповідності освітлення між просторовою " "моделлю та сценою з реального життя. Іншим прикладом є ретушування " "фотографій із ширшими даними щодо контрастності. У самому малюванні, це " "надає змогу створювати зображення, на якому ви можете використовувати шалені " "контрасти, де ви можете вибирати будь-яку яскравість." #: ../../general_concepts/colors/color_managed_workflow.rst:230 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." msgstr "" "Дії на бічній панелі пошуку за таблицею стосуються окремої панелі перегляду, " "тому ви можете створити панель перегляду і встановити для неї канал " "світності. У такий спосіб ви бачитимете одночасно зображення у кольорі та " "відтінках сірого, отже зможете спостерігати за значеннями кольорів." #: ../../general_concepts/colors/color_managed_workflow.rst:232 msgid "" "Another example is to carefully watch the gradients in a certain section." msgstr "" "Іншим прикладом є доскіпливе стеження за градієнтами у певному перетині." #: ../../general_concepts/colors/color_managed_workflow.rst:234 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." msgstr "" "Подібно до ICC, за допомогою бічної панелі пошуку за таблицею, ви можете " "створити певний профіль для вашого пристрою. У нашому прикладі це 'lut', " "скорочення від 'Look Up Table' (таблиця пошуку). Цей профіль можна додати до " "OCIO внесенням змін до файла налаштувань. Якщо увімкнено OCIO, налаштування " "на сторінці :menuselection:`Параметри --> Налаштувати Krita --> Керування " "кольорами` буде вимкнено, якщо ви не використовуєте рушій кольорів :guilabel:" "`Вбудований`." #: ../../general_concepts/colors/color_managed_workflow.rst:237 msgid "In summary" msgstr "Підсумок" #: ../../general_concepts/colors/color_managed_workflow.rst:239 msgid "Krita has two modes of color management:" msgstr "У Krita передбачено два режими керування кольорами:" #: ../../general_concepts/colors/color_managed_workflow.rst:241 msgid "" "ICC works in terms of spaces relative to the CIEXYZ space, and requires an " "ICC profile." msgstr "" "ICC працює у термінах просторів, відносних до простору CIEXYZ, і потребує " "профілю ICC." #: ../../general_concepts/colors/color_managed_workflow.rst:242 msgid "OCIO works in terms of interpretation, and makes use of LUTs." msgstr "OCIO працює у сенсі інтерпретації і використовує таблиці пошуку (LUT)." #: ../../general_concepts/colors/color_managed_workflow.rst:243 msgid "both can be made with a colorimeter." msgstr "обидва можна виконати за допомогою колориметра." #: ../../general_concepts/colors/color_managed_workflow.rst:244 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." msgstr "" "Якщо вам потрібен робочий процес із належним керуванням кольорами, вам " "знадобиться один нетиповий профіль для пристрою вхідних даних (вашого " "монітора) та профілі для пристроїв виведення даних (вашого принтера або " "екрана призначення). Для інтернету профілем виведення завжди буде sRGB." #: ../../general_concepts/colors/color_managed_workflow.rst:245 msgid "" "Set up your screen profiles under :menuselection:`Settings --> Configure " "Krita --> Color management`." msgstr "" "Налаштуйте ваші профілі екрана за допомогою пункту меню :menuselection:" "`Параметри --> Налаштувати Krita --> Керування кольорами`." #: ../../general_concepts/colors/color_managed_workflow.rst:246 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." msgstr "" "**Не** використовуйте профілів екрана або інших пристроїв для малювання. " "Використовуйте для малювання профіль робочого простору, зокрема будь-який з " "профілів elle, оскільки з такими профілями дії з кольорами будуть набагато " "більш передбачуваними, а їхні наслідки виглядатимуть привабливіше. Krita " "виконуватиме перетворення між простором кольорів вашого екрана та робочим " "простором на льоту, надаючи вам змогу вибрати належні кольори. Це " "перетворить ваше екран на бінокль для перегляду зображення." #: ../../general_concepts/colors/color_managed_workflow.rst:247 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." msgstr "" "Користуйтеся відповідним до робочого процесу керуванням кольорами. Якщо ви " "працюєте з Blender, варто скористатися OCIO, а не ICC. Якщо ви працюєте із " "Scribus або Photoshop, скористайтеся ICC." #: ../../general_concepts/colors/color_managed_workflow.rst:249 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." msgstr "" "Krita виконує багато математичних дій із числовими характеристиками " "кольорів. Часто ці дії пов'язано зі змішуванням кольорів. Дії з кольорами " "найкраще виконувати у лінійному просторі кольорів, а для правильної роботи " "лінійного простору кольорів потрібна бітова глибина кольорів у принаймні 16 " "бітів. Недоліком використання лінійних просторів є те, що іноді робота у них " "є дещо незвичною." #: ../../general_concepts/colors/color_managed_workflow.rst:251 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!" msgstr "" "Якщо ви полюбляєте малювати, на вашому комп'ютері встановлено багато " "оперативної пам'яті і ви робите перші кроки у використанні усіх переваг " "керування кольорами у Krita, спробуйте перейти з використання у всіх ваших " "малюнках вбудованого профілю sRGB на профіль sRGB-v2-elle-g10.icc або " "rec2020-v2-elle-g10.icc із 16-бітовими дійсними значеннями для компонентів " "кольорів. Це надасть вам ширші можливості у змішуванні кольорів і відкриє " "для вас можливості роботи із широким динамічним діапазоном кольорів (HDR)!" #: ../../general_concepts/colors/color_managed_workflow.rst:256 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!" msgstr "" "Деякі графічні картки, зокрема картки виробництва NVidia, демонструють кращу " "швидкодію із 16-бітовими дійсними значенням каналів кольорів, оскільки на " "картках NVidia на внутрішньому рівні виконується перетворення значень на " "дійсні числа. Якщо не потрібно виконувати додаткове перетворення, робота " "пришвидшується!" #: ../../general_concepts/colors/color_managed_workflow.rst:260 msgid "" "No amount of color management in the world can make the image on your screen " "and the image out of the printer have 100% the same color." msgstr "" "Немає жодної методики керування кольорами, яка могла б зробити зображення на " "вашому екрані і надруковане принтером зображення абсолютно однаковими за " "кольорами." #: ../../general_concepts/colors/color_managed_workflow.rst:263 msgid "Exporting" msgstr "Експортування" #: ../../general_concepts/colors/color_managed_workflow.rst:265 msgid "" "When you have finished your image and are ready to export it, you can modify " "the color space to optimize it:" msgstr "" "Коли роботу над вашим зображенням буде завершено, і ви будете готові " "експортувати його, ви можете змінити простір кольорів, щоб оптимізувати " "зображення:" #: ../../general_concepts/colors/color_managed_workflow.rst:267 msgid "If you are preparing an image for the web:" msgstr "Якщо ви готуєте зображення для використання у інтернеті:" #: ../../general_concepts/colors/color_managed_workflow.rst:269 msgid "" "If you use 16bit color depth or higher, convert the image to 8bit color " "depth. This will make the image much smaller." msgstr "" "Якщо ви використовуєте 16-бітову або більшу глибину кольорів, перетворіть " "зображення на зображення із 8-бітовою глибиною кольорів. Це значно зменшить " "розміри зображення." #: ../../general_concepts/colors/color_managed_workflow.rst:271 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." msgstr "" "У поточній версії Krita не передбачено вбудованого згладжування, що означає, " "що перетворення з 16- до 18-бітового зображення може призвести до появи " "смуг. Втім, ви можете імітувати його додаванням шару заповнення із " "візерунком, з наступним встановленням цього шару заповнення як накладки із " "5% непрозорістю. Далі, зведіть усе зображення і перетворіть його на 8-" "бітове. Візерунок працюватиме як згладжування, що надаватиме згладженого " "вигляду градієнтам." #: ../../general_concepts/colors/color_managed_workflow.rst:273 msgid "If it's a gray-scale image, convert it to gray-scale." msgstr "" "Якщо це зображення є зображенням у відтінках сірого, перетворіть його на " "зображення у відтінках сірого." #: ../../general_concepts/colors/color_managed_workflow.rst:274 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." msgstr "" "Якщо зображення є кольоровим, зберігайте його з профілем робочого простору: " "у багатьох сучасних браузерах передбачено підтримку вбудованих до файлів " "зображень профілів кольорів. Наприклад, Firefox намагатиметься перетворити " "ваше зображення до профілю кольорів іншого монітора (якщо у цього монітора є " "профіль). Таким чином, зображення виглядатиме майже тотожно на вашому " "моніторі і на інших моніторах із профілями." #: ../../general_concepts/colors/color_managed_workflow.rst:279 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 " "`_, save your PNG, JPG or TIFF without an embedded profile to work " "around this." msgstr "" "У деяких версіях Firefox кольори виглядають доволі дивно: це вада у Firefox, " "причиною якої є `неповнота системи керування кольорами `_. " "Збережіть PNG, JPG або TIFF без вбудованого профілю, щоб обійти цю проблему." #: ../../general_concepts/colors/color_managed_workflow.rst:281 msgid "If you are preparing for print:" msgstr "Якщо ви готуєте зображення для друку:" #: ../../general_concepts/colors/color_managed_workflow.rst:283 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." msgstr "" "Ймовірно, зображення було створено вами у робочому профілі, замість " "справжнього нетипового профілю вашого екрана. Якщо це не так, перетворіть " "його до одного з таких профілів: Adobe RGB, sRGB або Rec. 2020." #: ../../general_concepts/colors/color_managed_workflow.rst:284 msgid "" "Check with the printer what kind of image they expect. Maybe they expect " "sRGB color space, or perhaps they have their own profile." msgstr "" "Перевірте, якого типу даних очікує принтер. Можливо, йому потрібні дані у " "просторі кольорів sRGB або у принтера є власний профіль кольорів." #: ../../general_concepts/colors/color_managed_workflow.rst:287 msgid "Interaction with other applications" msgstr "Взаємодія із іншими програмами" #: ../../general_concepts/colors/color_managed_workflow.rst:290 msgid "Blender" msgstr "Blender" #: ../../general_concepts/colors/color_managed_workflow.rst:292 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." msgstr "" "Якщо ви хочете скористатися функціональними можливостями OCIO у Krita і " "зокрема у поєднанні із керуванням кольорами Blender, ви можете спробувати " "наказати програмі використовувати налаштування OCIO Blender." #: ../../general_concepts/colors/color_managed_workflow.rst:294 msgid "" "Blender's OCIO config is under ``/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." msgstr "" "Налаштування OCIO Blender зберігаються у файлі ``<тека Blender>/version " "number/datafiles/colormanagement``. Встановіть на бічній панелі таблиці " "пошуку використання рушія OCIO і виберіть налаштування за вказаним вище " "шляхом. Це призведе до використання вхідного простору кольорів та простору " "кольорів показу Blender, але не простору вигляду, оскільки підтримки цих " "просторів у Krita ще не передбачено." #: ../../general_concepts/colors/color_managed_workflow.rst:298 msgid "Windows Photo Viewer" msgstr "Переглядач фотографій Windows" #: ../../general_concepts/colors/color_managed_workflow.rst:300 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." msgstr "" "У процесі спільного використання різних програм можуть виникнути певні " "проблеми. Одним із важливих факторів є те, що стандартна програма перегляду " "фотографій у Windows не обробляє сучасні профілі ICC. У Krita можна " "використовувати профілі версії 4, а переглядач фотографій може працювати " "лише з профілями версії 2. Якщо ви експортуєте JPEG з вбудованим профілем, " "переглядач фотографій покаже ваше зображення надто темним." #: ../../general_concepts/colors/color_managed_workflow.rst:303 msgid "Example workflows" msgstr "Приклади робочого процесу" #: ../../general_concepts/colors/color_managed_workflow.rst:305 msgid "" "Here are some example workflows to get a feeling of how your color " "management workflow may look like." msgstr "" "Ось декілька прикладів робочих процедур, за допомогою яких ви зможете " "зрозуміти, як може виглядати ваша робоча процедура із керування кольорами." #: ../../general_concepts/colors/color_managed_workflow.rst:307 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'." msgstr "" "Як уже згадувалося, вхідний профіль для вашого екрана встановлюється за " "допомогою сторінки :menuselection:`Параметри --> Налаштувати Krita --> " "Керування кольорами` або за допомогою пункту простору екрана на бічній " "панелі таблиці пошуку. Робочий простір встановлюється за допомогою панелі " "створення документа або за допомогою пункту вхідного простору бічної панелі " "таблиці пошуку." #: ../../general_concepts/colors/color_managed_workflow.rst:310 msgid "Webcomic" msgstr "Вебкомікси" #: ../../general_concepts/colors/color_managed_workflow.rst:317 #: ../../general_concepts/colors/color_managed_workflow.rst:339 #: ../../general_concepts/colors/color_managed_workflow.rst:357 msgid "Input" msgstr "Вхідні дані" #: ../../general_concepts/colors/color_managed_workflow.rst:318 #: ../../general_concepts/colors/color_managed_workflow.rst:340 #: ../../general_concepts/colors/color_managed_workflow.rst:358 msgid "Your screen profile. (You pick colors via your screen)" msgstr "Профіль вашого екрана. (Ви вибираєте кольори на вашому екрані)" #: ../../general_concepts/colors/color_managed_workflow.rst:319 #: ../../general_concepts/colors/color_managed_workflow.rst:341 #: ../../general_concepts/colors/color_managed_workflow.rst:359 msgid "Workingspace" msgstr "Робочий простір" #: ../../general_concepts/colors/color_managed_workflow.rst:320 msgid "" "sRGB (the default screen profile) or any larger profile if you can spare the " "bit depth and like working in them." msgstr "" "sRGB (типовий профіль екранів) або будь-який ширший профіль, якщо ви можете " "заощадити на бітовій глибині, і вам подобається з ними працювати." #: ../../general_concepts/colors/color_managed_workflow.rst:322 #: ../../general_concepts/colors/color_managed_workflow.rst:344 #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "Output" msgstr "Вихідні дані" #: ../../general_concepts/colors/color_managed_workflow.rst:322 msgid "" "sRGB, ICC version 2, sRGB TRC for the internet, and a specialized CMYK " "profile from the printing house for the printed images." msgstr "" "sRGB, ICC версії 2, sRGB TRC для інтернету і спеціалізований профіль CMYK " "від виробника принтера для друку зображень." #: ../../general_concepts/colors/color_managed_workflow.rst:324 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." msgstr "" "Користуйтеся sRGB-elle-V2-srgbtrc.icc для перенесення даних між Inkscape, " "Photoshop, Painttool Sai, Illustrator, GIMP, Manga Studio, Paintstorm " "Studio, MyPaint, Artrage, Scribus тощо і Krita." #: ../../general_concepts/colors/color_managed_workflow.rst:326 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." msgstr "" "Якщо ви використовуєте простір кольорів, більший за ICC, ви зможете " "обмінюватися даними лише у наборі Krita, Photoshop, Illustrator, GIMP 2.9, " "Manga Studio і Scribus. В усіх інших програмах припускають простір кольорів " "sRGB, незалежно від визначеного у файлі, оскільки інші програми не " "використовують керування кольорами." #: ../../general_concepts/colors/color_managed_workflow.rst:328 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." msgstr "" "Якщо ви використовуєте Krita у поєднанні з Blender, Nuke або Natron, " "скористайтеся OCIO і встановіть для вхідних даних простір кольорів sRGB, але " "не забувайте вибрати профіль sRGB для ICC під час створення нового файла." #: ../../general_concepts/colors/color_managed_workflow.rst:330 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." msgstr "" "Нарешті, щодо сумісності інтернет-переглядом: радимо вам перетворити " "зображення до 8-бітового простору sRGB, srgbtrc, і не вбудовувати профіль " "ICC. Далі, якщо ви використовуєте формат PNG, пропустіть дані крізь pngcrush " "або іншу програму для оптимізації PNG. sRGB у цьому випадку вибрано, " "оскільки можна припускати, що монітори більшості з ваших глядачів не буде " "профільовано. Крім того, ймовірно, що більшість глядачів не мають достатньо " "якісних екранів, щоб побачити усі кольори розширеної палітри. Ось чому слід " "використовувати типовий профіль для інтернету, sRGB." #: ../../general_concepts/colors/color_managed_workflow.rst:333 msgid "Print" msgstr "Друк" #: ../../general_concepts/colors/color_managed_workflow.rst:342 msgid "sRGB or Rec. 2020 if you can afford the bit-depth being 16bit." msgstr "" "sRGB або Rec. 2020, якщо ви можете працювати із бітовою глибиною у 16 бітів." #: ../../general_concepts/colors/color_managed_workflow.rst:344 msgid "" "Specialized CMYK profile from the printing house for the printed images." msgstr "" "Спеціалізований профіль CMYK від виробника принтера для друку зображень." #: ../../general_concepts/colors/color_managed_workflow.rst:346 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." msgstr "" "Профілі CMYK є різними для різних принтерів і навіть для різного паперу або " "типу чорнила, тому не будьте надто самовпевненими — попросіть надати вам ці " "профілі наперед, а не малюйте щось у випадковому профілі CMYK. Як ми вже " "згадували у розділі щодо умов перегляду, вам слід бути готовими до будь-яких " "варіантів." #: ../../general_concepts/colors/color_managed_workflow.rst:348 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." msgstr "" "Ви можете налаштувати засіб вибору кольору із розширеними можливостями на " "перетворення до вказаного профілю за допомогою пункту меню :menuselection:" "`Параметри --> Налаштувати Krita --> Параметри вибору кольору`. На " "відповідній сторінці позначте пункт :guilabel:`У засобі вибору кольорів " "використано не такий простір кольорів, як на зображенні` і виберіть " "відповідний профіль CMYK. Це дещо обмежить вибір кольорів, але надасть змогу " "використовувати усі фільтри та режими змішування з RGB." #: ../../general_concepts/colors/color_managed_workflow.rst:351 msgid "Games" msgstr "Ігри" #: ../../general_concepts/colors/color_managed_workflow.rst:360 msgid "sRGB or grayscale linear for roughness and specular maps." msgstr "sRGB або лінійні відтінки сірого для грубих і дзеркальних відображень." #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "" "This one is tricky, but in the end it'll be sRGB for the regular player." msgstr "" "Тут все не так просто, але, врешті, для звичайного гравця результатом буде " "sRGB." #: ../../general_concepts/colors/color_managed_workflow.rst:364 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." msgstr "" "Отже, усе не так просто. Ви можете використовувати OCIO і ICC у різних " "програмах, але рекомендовано передавати ваші зображення рушію обробки у sRGB " "або відтінках сірого. У багатьох сучасних засобах обробки зображення з " "фізичним підґрунтям передбачено можливість визначення того, слід читати " "зображення як зображення у лінійному просторі чи як зображення у просторі " "srgbtrc. Для належного використання у рушії обробки зображень у грі на " "основі фізичних принципів ідентифікація зображень є навіть критичною." #: ../../general_concepts/colors/color_managed_workflow.rst:366 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." msgstr "" "Хоча у ігрових рушіях дані намагаються оптимізувати і рекомендують не " "виходити за межі 8-бітових каналів кольорів, можливо, у майбутньому екрани " "зможуть відтворювати кольори із більшою бітовою глибиною. Ймовірно, зараз " "варто працювати з файлами у робочому просторі, який буде надмірно широким, і " "оптимізувати отримані зображення до потреб сучасних засобів обробки, щоб " "коли у ігрових засобах обробки зображень буде реалізовано підтримку кольорів " "з великою бітовою глибиною, оновлення вашої роботи до нових, досконаліших " "моніторів було справою декількох секунд." #: ../../general_concepts/colors/color_managed_workflow.rst:368 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." msgstr "" "Нормальні карти та карти висот офіційно визначаються у робочому просторі " "«без даних кольорів», але у більшість рушіїв ніяк це не враховує. Замість " "переведення у простір без кольорів, просто повідомте ігровому рушію, що не " "слід виконувати ніяких перетворень із файлом під час імпортування даних." #: ../../general_concepts/colors/color_managed_workflow.rst:370 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)." msgstr "" "Дзеркальні, глянсуваті, металічні карти та карти шерсткості засновано на " "лінійних обчисленнях. Отже, якщо певний матеріал має металічність 0.3, це " "означає, що він є на 30% сірим у лінійному просторі. Тому слід повідомити " "засобам обробки ігрового рушія, що зображення збережено у лінійному просторі " "(або, принаймні, що дані зображення не слід додатково перетворювати)." #: ../../general_concepts/colors/color_managed_workflow.rst:374 msgid "" "`Visualizing the XYZ color space `_." msgstr "" "`Візуалізація простору кольорів XYZ `_." #: ../../general_concepts/colors/color_managed_workflow.rst:375 msgid "" "`Basics of gamma correction `_." msgstr "" "`Основи виправлення гами `_." #: ../../general_concepts/colors/color_managed_workflow.rst:376 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 `_." msgstr "" "`Приклад з Panda3D того, як зображення із закодованою гамою без 3D-обробки " "призводить до сповіщення щодо виконання кодування гами може призвести до " "надто темних зображень `_" #: ../../general_concepts/colors/color_managed_workflow.rst:377 msgid "" "`2D examples of the effect of gamma-encoding on color maths `_." msgstr "" "`Двовимірні приклади використання гама-кодування у математиці кольорів " "`_" #: ../../general_concepts/colors/color_managed_workflow.rst:378 msgid "" "`Basic overview of color management from ArgyllCMS manual `_." msgstr "" "`Базовий огляд керування кольорами з підручника з ArgyllCMS `_." diff --git a/locale/zh_CN/LC_MESSAGES/contributors_manual/krita_manual_conventions.po b/locale/zh_CN/LC_MESSAGES/contributors_manual/krita_manual_conventions.po index e42339a5e..62e8d6e94 100644 --- a/locale/zh_CN/LC_MESSAGES/contributors_manual/krita_manual_conventions.po +++ b/locale/zh_CN/LC_MESSAGES/contributors_manual/krita_manual_conventions.po @@ -1,1353 +1,1353 @@ msgid "" msgstr "" "Project-Id-Version: kdeorg\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-09 03:27+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: 2019-07-18 15:06\n" "Last-Translator: Guo Yunhe (guoyunhe)\n" "Language-Team: Chinese Simplified\n" "Language: zh_CN\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=1; plural=0;\n" "X-Generator: crowdin.com\n" "X-Crowdin-Project: kdeorg\n" "X-Crowdin-Language: zh-CN\n" "X-Crowdin-File: /kf5-trunk/messages/www/" "docs_krita_org_contributors_manual___krita_manual_conventions.pot\n" #: ../../:2 msgid "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: mouseleft" msgstr "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: 鼠标左键" #: ../../:4 msgid "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: mouseright" msgstr "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: 鼠标右键" #: ../../:6 msgid "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: mousemiddle" msgstr "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: 鼠标中间键" #: ../../:8 msgid "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" msgstr "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: 鼠标滚轮滚动" +#: ../../contributors_manual/krita_manual_conventions.rst:None +msgid "Horizontal Rulers" +msgstr "水平线" + #: ../../contributors_manual/krita_manual_conventions.rst:0 msgid "" ".. image:: images/sample.png\n" " :alt: an image." msgstr "" ".. image:: images/sample.png\n" " :alt: 一张图像。" -#: ../../contributors_manual/krita_manual_conventions.rst:None -msgid "Horizontal Rulers" -msgstr "水平线" - #: ../../contributors_manual/krita_manual_conventions.rst:1 msgid "reStructuredText conventions for the Krita Manual" msgstr "Krita 使用手册的 reStructuredText 惯例" #: ../../contributors_manual/krita_manual_conventions.rst:16 msgid "Mark-up conventions for the Krita Manual" msgstr "Krita 手册标记语言使用指引" #: ../../contributors_manual/krita_manual_conventions.rst:18 msgid "" "This details the style conventions for using restructured text for the Krita " "Manual." msgstr "本文详细介绍了如何在 Krita 手册中使用 reStructuredText 标记语言。" #: ../../contributors_manual/krita_manual_conventions.rst:20 msgid "" "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):" msgstr "" "我们建议参与文档编写和翻译的人员认真阅读 reStructuredText 项目的 `官方规范 " "`_ 。该项目在 sourceforge 上面运" "作，它的服务器不太稳定，可以把该文档保存一份到本地以便日后查阅 )：" #: ../../contributors_manual/krita_manual_conventions.rst:23 msgid "" "`Primer `_" msgstr "" "`入门知识 `_" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "User Manual:" msgstr "用户手册" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "" "`Quick Ref `_" msgstr "" "`快速参考 `_" #: ../../contributors_manual/krita_manual_conventions.rst:25 msgid "" "`Text Cheatsheet `_" msgstr "" "`文本功能备忘录 `_" #: ../../contributors_manual/krita_manual_conventions.rst:27 msgid "" "`Introduction `_" msgstr "" "`简介 `_" #: ../../contributors_manual/krita_manual_conventions.rst:28 msgid "" "`Markup `_" msgstr "" "`标记规范 `_" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "Reference Documentation:" msgstr "参考文档" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "" "`Directives `_" msgstr "" "`指令规范 `_" #: ../../contributors_manual/krita_manual_conventions.rst:30 msgid "`Roles `_" msgstr "`角色规范 `_" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "Sphinx specific docs:" msgstr "Sphinx 专用文档" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "" "`Sphinx' page on restructured text `_ -- This is useful for the specific " "sphinx directives and roles it uses to generate for example table of " "contents." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:34 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." msgstr "" "由于官方版本的 reStructuredText 和 Sphinx 的文档描述的用法存在差异。本文档会" "统一介绍我们建议遵循的惯例。" #: ../../contributors_manual/krita_manual_conventions.rst:36 msgid "Contents" msgstr "目录" #: ../../contributors_manual/krita_manual_conventions.rst:39 msgid "Meta data" msgstr "元数据" #: ../../contributors_manual/krita_manual_conventions.rst:41 msgid "Each page should start with the following three things:" msgstr "每个页面起始部分都应该包括下列 4 种要素：" #: ../../contributors_manual/krita_manual_conventions.rst:44 msgid "" "This is a general description of the page. It will be converted to an html " "meta tag which will be used by search engines::" msgstr "" "这是对于该页面内容的概述，它的内容会被转换成一组 html meta 标记，方便搜索引擎" "抓取::" #: ../../contributors_manual/krita_manual_conventions.rst:46 msgid "" ".. meta::\n" " :description:\n" " Description." msgstr "" ".. meta::\n" " :description:\n" " 描述文字。" #: ../../contributors_manual/krita_manual_conventions.rst:49 msgid "A meta description" msgstr "元描述" #: ../../contributors_manual/krita_manual_conventions.rst:52 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::" msgstr "" "用于记录哪些人编辑过该页面并对他们的贡献进行声明。最好把此处标记为注解文本，" "以免被机器轻易理解。我们的整个手册均使用 GDL 1.3 许可证，所以我们也要在这里对" "许可证进行声明::" #: ../../contributors_manual/krita_manual_conventions.rst:54 msgid "" ".. metadata-placeholder\n" "\n" " :authors: - Author 1\n" " - Author 2\n" " :license: GNU free documentation license 1.3 or later." msgstr "" ".. metadata-placeholder\n" "\n" " :authors: - 作者 1\n" " - 作者 2\n" " :license: GNU free documentation license 1.3 or later." #: ../../contributors_manual/krita_manual_conventions.rst:58 msgid "A list of authors and a license." msgstr "作者列表和许可证" #: ../../contributors_manual/krita_manual_conventions.rst:61 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::" msgstr "" "关键词以半角逗号进行区分。页面会在 :ref:`genindex` 处按照这些关键词进行排列。" "手册自动生成的索引对于 PDF 和不了解内容关键词的人们来说非常有用。关键词的定义" "方式如下::" #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid "Indexing terms." msgstr "索引关键词" #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid ".. index:: Keyword, Keyword with Spaces, ! Main Definition Keyword" msgstr ".. index:: 关键词, 带有 空 格 的关键词, ! 主要定义关键词" #: ../../contributors_manual/krita_manual_conventions.rst:66 msgid "" "This is so we can easily link to the page using ``:ref:`label_name```. Try " "to make this a nice variable name::" msgstr "" "标签变量会被 ``:ref:`label_name``` 标记生成的页面链接所使用。请尽量构思简明易" "懂的变量名::" #: ../../contributors_manual/krita_manual_conventions.rst:68 msgid ".. _label_name:" msgstr ".. _标签名称 (英语):" #: ../../contributors_manual/krita_manual_conventions.rst:70 msgid "" "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." msgstr "" "在添加标签变量之后，你还要为页面添加一个标题， ``:ref:`label_name``` 将使用页" "面的标题文字作为链接显示的文字。" #: ../../contributors_manual/krita_manual_conventions.rst:71 msgid "A label." msgstr "标签变量" #: ../../contributors_manual/krita_manual_conventions.rst:74 msgid "Headings" msgstr "标题" #: ../../contributors_manual/krita_manual_conventions.rst:76 msgid "Headings will be done in the following order::" msgstr "各个级别的标题通过以下顺序生成::" #: ../../contributors_manual/krita_manual_conventions.rst:78 msgid "" "############\n" "Part/Section\n" "############\n" "\n" "For pages that have a lot of subpages.\n" "\n" "=========\n" "Heading 1\n" "=========\n" "\n" "Start most manual pages with this.\n" "\n" "Heading 2\n" "---------\n" "\n" "Heading 3\n" "~~~~~~~~~\n" "\n" "Heading 4\n" "^^^^^^^^^\n" "\n" "Heading 5\n" "'''''''''\n" "\n" "Heading 6\n" "\"\"\"\"\"\"\"\"\"" msgstr "" "############\n" "部分/章节\n" "############\n" "\n" "用于有许多子页面的页面。\n" "\n" "=========\n" "一级标题\n" "=========\n" "\n" "绝大多数使用手册页面以此类标题开始。\n" "\n" "二级标题\n" "---------\n" "\n" "三级标题\n" "~~~~~~~~~\n" "\n" "四级标题\n" "^^^^^^^^^\n" "\n" "五级标题\n" "'''''''''\n" "\n" "六级标题\n" "\"\"\"\"\"\"\"\"\"" #: ../../contributors_manual/krita_manual_conventions.rst:105 msgid "" "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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:107 msgid "" "Sometimes you need to link to a subsection of a page, add a label above the " "heading in that case." msgstr "如需创建链接到页面的内部章节，可在目标章节的标题前面添加一个标签变量。" #: ../../contributors_manual/krita_manual_conventions.rst:109 msgid "" "Headers should not end with punctuation, as the header will be used as the " "link name when linking to a label." msgstr "标题文字不应该以标点结尾，因为它会在生成链接时被用作链接文字。" #: ../../contributors_manual/krita_manual_conventions.rst:112 msgid "Linking" msgstr "链接" #: ../../contributors_manual/krita_manual_conventions.rst:114 msgid "" "Linking is done with ``:ref:`label_name```. When you need an alternative " "link text, you use ``:ref:`actual text shown ```." msgstr "" "链接通过 ``:ref:`label_name``` 生成。如需把链接显示成自定义文字，则使用 ``:" "ref:`实际显示的文字 ``` 。务必在“label_name”括号的前面保留一个半" "角空格，否则会把整个页面的代码搞乱！" #: ../../contributors_manual/krita_manual_conventions.rst:116 msgid "" "Linking to external pages is done with ```url`_`` and ```link name " "`_``, which'll become `link name `_." msgstr "" "外部链接通过 ```url`_`` 和 ```链接名称 `_`` 生成，它们会被如下显示： `链" "接名称 `_ 。相邻文字和这些链接的代码之间必须保留一个空格，否则整个页面的" "代码会乱掉！" #: ../../contributors_manual/krita_manual_conventions.rst:118 msgid "" "`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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:121 msgid "Footnotes and further reading" msgstr "脚注和延伸阅读" #: ../../contributors_manual/krita_manual_conventions.rst:123 msgid "" "Footnotes can be made in 3 ways, the most common one is with autonumbering, " "as per reference:" msgstr "脚注可以通过三种方式生成，最常用的是自动编号的引用，示例如下：" #: ../../contributors_manual/krita_manual_conventions.rst:125 msgid "" "[#]_ is a reference to footnote 1, and [#]_ is a reference to footnote 2." msgstr "[#]_ 是对脚注 1 的引用，而 [#]_ 则是对脚注 2 的引用。" #: ../../contributors_manual/krita_manual_conventions.rst:128 msgid "This is footnote 1." msgstr "这是脚注 1。" #: ../../contributors_manual/krita_manual_conventions.rst:129 msgid "This is footnote 2." msgstr "这是脚注 2。" #: ../../contributors_manual/krita_manual_conventions.rst:130 msgid "This is footnote 3." msgstr "这是脚注 3。" #: ../../contributors_manual/krita_manual_conventions.rst:132 msgid "[#]_ is a reference to footnote 3." msgstr "[#]_ 是对脚注 3 的引用。" #: ../../contributors_manual/krita_manual_conventions.rst:134 msgid "Here is a citation reference: [CIT2002]_ ." msgstr "这是一处引文：[CIT2002]_ 。" #: ../../contributors_manual/krita_manual_conventions.rst:136 msgid "" "This is the citation. It's just like a footnote, except the label is " "textual." msgstr "这是引文本身。它和脚注类似，但标签是文本串。" #: ../../contributors_manual/krita_manual_conventions.rst:139 msgid "Citation can also be referenced with ```citation `_``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:141 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." msgstr "" "我们在手册中并未使用脚注功能，因为我们觉得这太学术化了。不过我们依然会整理一" "些相关的文档和链接在页面的末尾列出，用于进一步介绍某些事物。Sphinx 用 ``.. " "seealso::`` 指令来生成外部链接，而 reStructuredText 为了兼容 LaTex 而建议使" "用 ``.. rubic:: Footnotes`` 来收集脚注。" #: ../../contributors_manual/krita_manual_conventions.rst:145 msgid "Images" msgstr "图像" #: ../../contributors_manual/krita_manual_conventions.rst:147 msgid "Use the image directive for images without captions::" msgstr "使用 image 标记可以生成不带说明文字的图像::" #: ../../contributors_manual/krita_manual_conventions.rst:149 msgid "" ".. image:: /images/sample.png\n" " :width: 800\n" " :align: center\n" " :alt: an image." msgstr "" ".. image:: /images/sample.png\n" " :width: 800\n" " :align: center\n" " :alt: 此处填入图像替代文字。上面的 center 表示居中。" #: ../../contributors_manual/krita_manual_conventions.rst:154 msgid "And figure directives for images with captions::" msgstr "使用 figure 标记可以生成带有说明文字的图像::" #: ../../contributors_manual/krita_manual_conventions.rst:156 msgid "" ".. figure:: /images/sample.png\n" " :figwidth: 800\n" " :align: center\n" " :alt: an image.\n" "\n" " A caption -- notice how the first letter is aligned with the :figwidth: " "option." msgstr "" ".. figure:: /images/sample.png\n" " :figwidth: 800\n" " :align: center\n" " :alt: 此处填入图像替代文字。上面的 center 表示居中。\n" "\n" " 说明文字 -- 注意说明文字的第一个字母按照图像的 :figwidth: 选项数值对齐。" #: ../../contributors_manual/krita_manual_conventions.rst:163 msgid "The latter gives:" msgstr "后一个标记生成的效果如下：" #: ../../contributors_manual/krita_manual_conventions.rst:170 msgid "" "A caption -- notice how the first letter of the caption in the directive is " "aligned with the :figwidth: option." msgstr "" "说明文字——在标记中，说明文字中的第一个字符是按照“:figwidth:”参数进行对齐的。" #: ../../contributors_manual/krita_manual_conventions.rst:172 msgid "" "Images should go into the ``/images`` folder. By using ``/images`` instead " "of ``images``, sphinx will know the filepath isn't relative." msgstr "" "图像应该上传到 ``/images`` 文件夹。使用 ``/images`` 而不是 ``images``，这样 " "Sphinx 就不会把它作为相对路径进行解释了。" #: ../../contributors_manual/krita_manual_conventions.rst:175 msgid "In-text Markup" msgstr "文字标记" #: ../../contributors_manual/krita_manual_conventions.rst:177 msgid "" "You can make text *emphasized* and **strong** with a single asterisk and " "double respectively::" msgstr "" "在一段文字前后各插入一个半角星号可以生成 *斜体* ，在一段文字的前后插入两个半" "角星号可以生成 **粗体** 。务必留意在星号和内部文字之间 **不可以** 插入空格，" "而星号和外部文字之间却 **一定要** 插入空格，否则整个页面的排版会乱掉。应尽量" "避免把中文标为斜体，如果原文使用了斜体，可以考虑使用中文引号或者粗体代替。 ::" #: ../../contributors_manual/krita_manual_conventions.rst:179 msgid "" "*emphasize*\n" "**strong**" msgstr "" "*斜体*\n" "**粗体**" #: ../../contributors_manual/krita_manual_conventions.rst:182 msgid "You cannot do both ***emphasized and strong***, so take a pick." msgstr "" "在一段文本的前后插入三个半角星号是行不通的，你只能在斜体和粗体之间二选一。" #: ../../contributors_manual/krita_manual_conventions.rst:184 msgid "" "You can :sub:`subscript text` and :sup:`superscript text` by using ``:sub:" "`text``` and ``:sup:`text```" msgstr "" "用 ``:sub:`text``` 可以生成 :sub:`下标文字` ，而用 ``:sup:`text``` 则可以生" "成 :sup:`上标文字`" #: ../../contributors_manual/krita_manual_conventions.rst:186 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::" msgstr "" "切勿滥用文字标记。尽量使用 Sphinx 提供的语义标记，因为它们可以帮助翻译人员理" "解文本的性质，这些标记包括::" #: ../../contributors_manual/krita_manual_conventions.rst:188 msgid "" ":menuselection:`Settings --> Configure Krita`\n" ":guilabel:`File`\n" ":kbd:`Ctrl + Z`\n" ":program:`Krita`" msgstr "" ":menuselection:`设置 --> 配置 Krita`\n" ":guilabel:`文件`\n" ":kbd:`Ctrl + Z`\n" ":program:`Krita`" #: ../../contributors_manual/krita_manual_conventions.rst:193 msgid "" "Avoid randomly bolding words. It does *not* make the text easier or " "friendlier to read." msgstr "不要胡乱加粗文字。那样会把文字变得难以阅读。" #: ../../contributors_manual/krita_manual_conventions.rst:196 msgid "Substitution References" msgstr "置换标记" #: ../../contributors_manual/krita_manual_conventions.rst:198 msgid "" "You can create a sort of shorthand for a piece of text or an image by doing::" msgstr "你可以用以下方式为文字或图像创建速记标签::" #: ../../contributors_manual/krita_manual_conventions.rst:200 msgid ".. |shorthand| replace:: something or the other." msgstr ".. |速记标签| replace:: 被替换的内容。" #: ../../contributors_manual/krita_manual_conventions.rst:202 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\"." msgstr "" "如果你在文字中插入 ``|速记标签|``，它会被显示成“该速记标签所代表的内容”。这对" "于那些会被反复使用的格式繁琐的图像和文字很有用，例如使用了 LaTeX 的情况。" #: ../../contributors_manual/krita_manual_conventions.rst:204 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." msgstr "" "Krita 文档定义了 ``|mouseleft|``、``|mousemiddle|``、``|mousescroll|`` 和 ``|" "mouseright|``，它们会被置换为 |mouseleft|、|mousemiddle|、|mousescroll| 和 |" "mouseright| 。它们通过 Sphinx 的 conf.py 文件进行定义，然后被附加在每个 rst " "文件里面。" #: ../../contributors_manual/krita_manual_conventions.rst:206 msgid "" "For links, if you reuse the same link over and over, you can write something " "like the following at the end of the file::" msgstr "" "对于链接来说，如果需要反复使用同一个链接，你可以在文件的末尾编写类似下面的代" "码::" #: ../../contributors_manual/krita_manual_conventions.rst:208 msgid "" ".. _bugzilla: https://bugs.kde.org/\n" ".. _Krita Manual: https://docs.krita.org/" msgstr "" ".. _bugzilla: https://bugs.kde.org/\n" ".. _Krita 使用说明: https://docs.krita.org/" #: ../../contributors_manual/krita_manual_conventions.rst:211 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\"." msgstr "" "这样日后在需要插入链接的时候，你只需使用 ```bugzilla`_`` 即可生成一个文字显示" "为“bugzilla”，跳传到 bugzilla 的链接。```Krita 使用说明`_`` 则会生成一个叫做 " "“Krita 使用说明” 的超链接并跳传到 docs.krita.org 。" #: ../../contributors_manual/krita_manual_conventions.rst:214 msgid "Lists" msgstr "列表" #: ../../contributors_manual/krita_manual_conventions.rst:217 msgid "Ordinated lists" msgstr "有序列表" #: ../../contributors_manual/krita_manual_conventions.rst:219 msgid "Apple" msgstr "苹果" #: ../../contributors_manual/krita_manual_conventions.rst:220 msgid "Pear" msgstr "梨子" #: ../../contributors_manual/krita_manual_conventions.rst:221 msgid "Banana" msgstr "香蕉" #: ../../contributors_manual/krita_manual_conventions.rst:223 msgid "Or..." msgstr "或者" #: ../../contributors_manual/krita_manual_conventions.rst:225 msgid "Table" msgstr "桌子" #: ../../contributors_manual/krita_manual_conventions.rst:226 msgid "Chair" msgstr "椅子" #: ../../contributors_manual/krita_manual_conventions.rst:227 msgid "Wardrobe." msgstr "衣柜" #: ../../contributors_manual/krita_manual_conventions.rst:229 msgid "Augustus" msgstr "奥古斯都" #: ../../contributors_manual/krita_manual_conventions.rst:230 msgid "Nero" msgstr "尼禄" #: ../../contributors_manual/krita_manual_conventions.rst:231 msgid "Caligula" msgstr "卡利古拉" #: ../../contributors_manual/krita_manual_conventions.rst:232 msgid "Trajan" msgstr "图拉真" #: ../../contributors_manual/krita_manual_conventions.rst:234 msgid "They can be defined as follows::" msgstr "它们的用法是::" #: ../../contributors_manual/krita_manual_conventions.rst:236 msgid "" "1. Apple\n" "2. Pear\n" "3. Banana\n" "\n" "#. Apple\n" "#. Pear\n" "#. Banana\n" "\n" "A. Table\n" "B. Chair\n" "C. Wardrobe\n" "\n" "A. Table\n" "#. Chair\n" "#. Wardrobe\n" "\n" "I. Augustus\n" "#. Nero\n" "#. Caligula\n" "#. Trajan" msgstr "" "1. 苹果\n" "2. 梨子\n" "3. 香蕉\n" "\n" "#. 苹果\n" "#. 梨子\n" "#. 香蕉\n" "\n" "A. 桌子\n" "B. 椅子\n" "C. 柜子\n" "\n" "A. 桌子\n" "#. 椅子\n" "#. 柜子\n" "\n" "I. 奥古斯都\n" "#. 尼禄\n" "#. 卡利古拉\n" "#. 特洛伊" #: ../../contributors_manual/krita_manual_conventions.rst:258 msgid "Unordered lists" msgstr "无序列表" #: ../../contributors_manual/krita_manual_conventions.rst:260 msgid "red" msgstr "红" #: ../../contributors_manual/krita_manual_conventions.rst:261 msgid "yellow" msgstr "黄" #: ../../contributors_manual/krita_manual_conventions.rst:263 msgid "seagreen" msgstr "海绿" #: ../../contributors_manual/krita_manual_conventions.rst:264 msgid "verdigris" msgstr "铜绿" #: ../../contributors_manual/krita_manual_conventions.rst:265 msgid "teal" msgstr "鸭绿" #: ../../contributors_manual/krita_manual_conventions.rst:266 msgid "viridian" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:268 msgid "dark emerald" msgstr "深祖母绿" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "green" msgstr "绿色" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "emerald" msgstr "祖母绿" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "light emerald" msgstr "浅祖母绿" #: ../../contributors_manual/krita_manual_conventions.rst:270 msgid "very light emerald." msgstr "极浅祖母绿" #: ../../contributors_manual/krita_manual_conventions.rst:271 msgid "blue" msgstr "蓝" #: ../../contributors_manual/krita_manual_conventions.rst:273 msgid "Defined as such::" msgstr "用法如下::" #: ../../contributors_manual/krita_manual_conventions.rst:275 msgid "" "- red\n" "- yellow\n" "- green\n" " - seagreen\n" " - verdigris\n" " - teal\n" " - viridian\n" " - emerald\n" " - dark emerald\n" " - light emerald\n" " - very light emerald.\n" "- blue" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:289 msgid "Definition Lists" msgstr "定义列表" #: ../../contributors_manual/krita_manual_conventions.rst:291 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." msgstr "" "它们在罗列某个工具面板的各个选项并逐个进行说明时特别好用。我们特别喜欢使用定" "义列表。" #: ../../contributors_manual/krita_manual_conventions.rst:293 msgid "Definition" msgstr "定义名称" #: ../../contributors_manual/krita_manual_conventions.rst:294 #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Explanation." msgstr "说明文字。" #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Another option" msgstr "另一个定义名称" #: ../../contributors_manual/krita_manual_conventions.rst:299 msgid "You can make them like this::" msgstr "方法如下::" #: ../../contributors_manual/krita_manual_conventions.rst:301 msgid "" "Definition\n" " Explanation.\n" "Another option\n" " Explanation." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:304 msgid "To make them." msgstr "如何生成定义列表。" #: ../../contributors_manual/krita_manual_conventions.rst:307 msgid "Tables" msgstr "表格" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Purpose" msgstr "用途" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Table type" msgstr "表格类型" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "listing shortcuts" msgstr "列举快捷键" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "Simple table" msgstr "简单型" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "lots of colspans" msgstr "单元格跨行跨列" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "Grid table" msgstr "网格型" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "Simple but long" msgstr "结构简单但超长" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "List Table" msgstr "列表型" #: ../../contributors_manual/krita_manual_conventions.rst:317 msgid "Done as follows::" msgstr "用法如下::" #: ../../contributors_manual/krita_manual_conventions.rst:319 msgid "" "================== ============\n" "Purpose Table type\n" "================== ============\n" "listing shortcuts Simple table\n" "lots of colspans Grid table\n" "Simple but long List Table\n" "================== ============\n" "\n" "+-----------------+------------+\n" "|Purpose |Table Type |\n" "+=================+============+\n" "|listing shortcuts|Simple table|\n" "+-----------------+------------+\n" "|lots of colspans |Grid table |\n" "+-----------------+------------+\n" "|Simple but long |List table |\n" "+-----------------+------------+\n" "\n" ".. list-table::\n" " :header-rows: 1\n" "\n" " - * Purpose\n" " * Table Type\n" " - * listing shortcuts\n" " * simple table\n" " - * lots of colspans\n" " * grid table\n" " - * simple but long\n" " * list table" msgstr "" "================== ============\n" "用途 表格类型\n" "================== ============\n" "列举快捷键 简单型\n" "单元格跨行跨列　 网格型\n" "结构简单但超长　 列表型\n" "================== ============\n" "\n" "+-----------------+------------+\n" "|用途　 |表格类型　　 |\n" "+=================+============+\n" "|列举快捷键　 |简单型 |\n" "+-----------------+------------+\n" "|单元格跨行跨列　　 |网格型 |\n" "+-----------------+------------+\n" "|结构简单但超长　　 |列表型 |\n" "+-----------------+------------+\n" "\n" ".. list-table::\n" " :header-rows: 1\n" "\n" " - * 用途\n" " * 表格类型\n" " - * 列举快捷键\n" " * 简单型\n" " - * 单元格跨行跨列\n" " * 网格型\n" " - * 结构简单但超长\n" " * 列表型" #: ../../contributors_manual/krita_manual_conventions.rst:349 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." msgstr "" "完整的网格型表格虽然可以应付复杂的跨行跨列，但却不好制作，所以小型表格最好使" "用简单型表格的句法。如果是非常长的单列表格，还不如直接用列表标记代替，这样编" "写和修改都省时省力。" #: ../../contributors_manual/krita_manual_conventions.rst:352 msgid "Admonishments and asides" msgstr "注解和警告信息框" #: ../../contributors_manual/krita_manual_conventions.rst:356 msgid "" "Admonishments are sort of like a separate section that the reader needs to " "pay attention to." msgstr "“注解”是一种用来吸引读者注意的独立段落。" #: ../../contributors_manual/krita_manual_conventions.rst:358 msgid "" "Admonishments that can be used are the following (in order of seriousness):" msgstr "我们可以使用下列警告文字 (按照严重程度排列)：" #: ../../contributors_manual/krita_manual_conventions.rst:362 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:366 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:370 msgid "Something that is important to note, but is not necessarily negative." msgstr "“重点”可以用来强调一些需要留意的信息，但并不一定是负面的信息。" #: ../../contributors_manual/krita_manual_conventions.rst:374 msgid "This is in general when something is negative." msgstr "“警告”一般在描述负面信息时使用。" #: ../../contributors_manual/krita_manual_conventions.rst:378 msgid "" "General attention grabber. Use this when the subject is more important than " "warning, but not as important that is could get a dataloss." msgstr "" "“注意”可以用来标注那些比“注解”更为重要，但又不至于造成数据损失的事项时使用。" #: ../../contributors_manual/krita_manual_conventions.rst:382 msgid "" "This is for things that could cause dataloss, like forgetting to save, or " "that Python currently has no undo functionality." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:386 msgid "" "This should be for things that are dangerous for the computer in general, " "this includes things that can cause out of memory style freezes." msgstr "" "“危险”信息用于标注那些危及计算机整体运行的情况，包括那些导致内存不足死机的操" "作等。" #: ../../contributors_manual/krita_manual_conventions.rst:390 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." msgstr "" "“错误”信息与手册本身内容无关，Sphinx 在某些情况下会生成这种信息，但我们的配置" "文件默认没有开启这一功能。" #: ../../contributors_manual/krita_manual_conventions.rst:392 msgid "Generic admonition that can have any text" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:394 msgid "Text." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:396 msgid "You can make it like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:398 msgid "" ".. admonition:: Generic admonition that can have any text\n" "\n" " Text." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:404 msgid "Sphinx also adds::" msgstr "Sphinx 还把“参见”信息作为为此类信息框的一种看待::" #: ../../contributors_manual/krita_manual_conventions.rst:406 msgid "" ".. seealso::\n" "\n" " Which is useful to collect external links and references." msgstr "" ".. seealso::\n" "\n" " 方便用于集中列出外部链接和参考资料。" #: ../../contributors_manual/krita_manual_conventions.rst:414 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." msgstr "" "水平线通常用于正文话题发生突然变化的场合。它在叙述性的写作中较为常见，如纪实" "或小说等。Krita 的使用手册主要采用说明文的写作风格，不会为了介绍一项功能而长" "篇大论。但有的时候为了交待设计思路，我们可能会展开讲述事情的来龙去脉。在本文" "档中，如果话题需要发生切换，那么最好另起章节。我们建议尽量使用 ``.. Topic::" "`` 标记，它生成的标题也会让文章更易于阅读。" #: ../../contributors_manual/krita_manual_conventions.rst:418 msgid "That said, horizontal rulers can be made with ``----``." msgstr "上面的便是一条水平线。如需插入一条水平线，使用 ``----`` 即可。" #: ../../contributors_manual/krita_manual_conventions.rst:421 msgid "The rubric directive" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:422 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::" msgstr "" "单独标题标记可以生成看上去和“章节标题”一样的标题文字。一个章节标题代表了整个" "章节和它里面的各个段落，而单独标题标记只管生成标题文字本身。它的用法如下::" #: ../../contributors_manual/krita_manual_conventions.rst:424 msgid ".. rubric:: The rubric directive" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:428 msgid "So, when to use these?" msgstr "如何选用标题类标记" #: ../../contributors_manual/krita_manual_conventions.rst:429 msgid "" "Only use them when you think the subject is too minor to have a proper " "heading." msgstr "" "一般来说应该尽量使用章节，只有在你认为该段文字的重要性不足以作为单独章节时才" "使用其他的标题类标记。" #: ../../contributors_manual/krita_manual_conventions.rst:431 msgid "Topic" msgstr "章节" #: ../../contributors_manual/krita_manual_conventions.rst:432 msgid "" "When the text is separated from the flow, so it goes into a different " "subject than the text itself is naturally going to." msgstr "" "当文字讨论的话题发生了明显变化，无法跟之前的段落归为同一章时，可以另起一章。" #: ../../contributors_manual/krita_manual_conventions.rst:433 msgid "Rubric" msgstr "单独标题" #: ../../contributors_manual/krita_manual_conventions.rst:434 msgid "" "When the text isn't separated from the flow, but it does not need a header " "either." msgstr "" "当文字讨论的内容依然属于当前章节的一部分，虽然需要给它安排一个标题但用不着给" "它指定一个正式章节时使用。" #: ../../contributors_manual/krita_manual_conventions.rst:436 msgid "Admonishments" msgstr "注解信息框" #: ../../contributors_manual/krita_manual_conventions.rst:436 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." msgstr "" "信息框的使用要谨慎，只应在文章非常需要对应的信息框时才偶尔使用，尤其是危险和" "警告类的信息框。如果信息框出现得太频繁，不但页面显得凌乱，读者也会对它们感到" "麻木。" #: ../../contributors_manual/krita_manual_conventions.rst:439 msgid "Code Snippets" msgstr "代码片段" #: ../../contributors_manual/krita_manual_conventions.rst:441 msgid "``Inline code snippets`` are done with ````backticks````." msgstr "``行内代码片段`` 可用 ````半角反引号```` 生成。" #: ../../contributors_manual/krita_manual_conventions.rst:443 msgid "" "Multi-line code snippets are done by ending the previous section with ``::" "``, which'll look like this::" msgstr "要生成多行代码片段，将前一个段落以 ``::`` 结尾::" #: ../../contributors_manual/krita_manual_conventions.rst:445 msgid "" "This is a paragraph, and we define a preformated snippet like so::\n" "\n" " Be sure to add a white space and a tab afterwards before starting the " "snippet." msgstr "" "这是一个代码片段，要定义一段预先格式化的代码片段，可以使用::\n" "\n" " 记得要在代码片段开始之前插入一个空格和一个 tab 占位符。" #: ../../contributors_manual/krita_manual_conventions.rst:449 msgid "" "You can also use the ``.. code::`` directive. If you add the language name " "after it, it'll do the appropriate syntax highlighting::" msgstr "" "你也可以使用 ``.. code::`` 标记。如果你在标记后面注明计算机语言名称，它还可以" "按此进行语法高亮::" #: ../../contributors_manual/krita_manual_conventions.rst:451 msgid "" ".. code:: python\n" "\n" " # Python comment\n" " def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:459 msgid "Becomes" msgstr "显示为" #: ../../contributors_manual/krita_manual_conventions.rst:468 msgid "" "# Python comment\n" "def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:469 msgid "some more..." msgstr "其他例子" #: ../../contributors_manual/krita_manual_conventions.rst:483 msgid "" "// C++ comment\n" "int myFunction(int i) {\n" " i += 1;\n" "\n" " // Check if more than 12\n" " if (i>12) {\n" " i = 0;\n" " }\n" " return i;\n" "}" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:498 msgid "" "/* CSS comment */\n" "body {\n" " margin: 0 auto;\n" " /* is 800 still sensible? */\n" " max-width:800px;\n" " font-size:16px;\n" " color:#333;\n" " background-color: #eee;\n" " padding:1em;\n" " font-family:serif;\n" " line-height: 1.4;\n" "}" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:502 msgid "" "

this is " "a paragraph.

" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:504 msgid "Other preformatted text" msgstr "手动断行" #: ../../contributors_manual/krita_manual_conventions.rst:507 msgid "One can" msgstr "你可以" #: ../../contributors_manual/krita_manual_conventions.rst:508 msgid "preformat" msgstr "手动断行" #: ../../contributors_manual/krita_manual_conventions.rst:509 msgid "text by" msgstr "文字" #: ../../contributors_manual/krita_manual_conventions.rst:510 msgid "prepending" msgstr "只需在" #: ../../contributors_manual/krita_manual_conventions.rst:511 msgid "each line" msgstr "每行文字的前面" #: ../../contributors_manual/krita_manual_conventions.rst:512 msgid "with a pipe" msgstr "插入一个竖线" #: ../../contributors_manual/krita_manual_conventions.rst:513 msgid "symbol" msgstr "符号" #: ../../contributors_manual/krita_manual_conventions.rst:515 msgid "Like so::" msgstr "做法如下::" #: ../../contributors_manual/krita_manual_conventions.rst:517 msgid "" "| One can\n" "| preformat\n" "| text by\n" "| prepending\n" "| each line\n" "| with a pipe\n" "| symbol" msgstr "" "| 你可以\n" "| 预格式化\n" "| 文本\n" "| 只需在\n" "| 每行之前\n" "| 加一个竖线\n" "| 符号" #: ../../contributors_manual/krita_manual_conventions.rst:525 msgid "We don't actually use this anywhere in the manual." msgstr "我们并没有在本手册中使用该功能。" #: ../../contributors_manual/krita_manual_conventions.rst:528 msgid "Glossaries, Terms and Index" msgstr "词汇表、术语和索引" #: ../../contributors_manual/krita_manual_conventions.rst:530 msgid "These are sphinx features." msgstr "这些都是 Sphinx 提供的特性。" #: ../../contributors_manual/krita_manual_conventions.rst:532 msgid "" "Index is used in the top section, right now only single index entries are " "used." msgstr "索引被显示在页面顶部，目前仅使用单一索引项。" #: ../../contributors_manual/krita_manual_conventions.rst:534 msgid "" "Glossaries are used for some of the menu entry sections, but not all of them." msgstr "词汇表被用于处理某些菜单项的章节，但并非每个菜单项都这样处理。" #: ../../contributors_manual/krita_manual_conventions.rst:537 msgid "Quotes" msgstr "引用" #: ../../contributors_manual/krita_manual_conventions.rst:539 msgid "Quotes are done like this::" msgstr "引用通过下述方式生成::" #: ../../contributors_manual/krita_manual_conventions.rst:541 msgid "" "I am not sure why you'd need quotes in a user manual...\n" "\n" "-- Wolthera" msgstr "" "我搞不懂为什么在用户手册里要使用引用...\n" "\n" "-- Wolthera" #: ../../contributors_manual/krita_manual_conventions.rst:545 msgid "This becomes a blockquote." msgstr "它会变成下面的引用文字：" #: ../../contributors_manual/krita_manual_conventions.rst:547 msgid "I am not sure why you'd need quotes in a user manual..." msgstr "我搞不懂为什么在用户手册里要使用引用..." #: ../../contributors_manual/krita_manual_conventions.rst:551 msgid "" "We do actually use quotes in some places. Try to add a link to the name to " "define where it came from." msgstr "" "但如果我们真的在文章里面引用了别人的发言，最好把发言人名字制作成链接，跳传到" "引用文字的出处。" #: ../../contributors_manual/krita_manual_conventions.rst:552 msgid "Wolthera" msgstr "Wolthera" diff --git a/locale/zh_CN/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po b/locale/zh_CN/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po index 5e00842ab..3981d4edf 100644 --- a/locale/zh_CN/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po +++ b/locale/zh_CN/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po @@ -1,1469 +1,1469 @@ msgid "" msgstr "" "Project-Id-Version: kdeorg\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-08 03:08+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: 2019-07-18 15:06\n" "Last-Translator: Guo Yunhe (guoyunhe)\n" "Language-Team: Chinese Simplified\n" "Language: zh_CN\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=1; plural=0;\n" "X-Generator: crowdin.com\n" "X-Crowdin-Project: kdeorg\n" "X-Crowdin-Language: zh-CN\n" "X-Crowdin-File: /kf5-trunk/messages/www/" "docs_krita_org_general_concepts___colors___color_managed_workflow.pot\n" +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_matrix_profile.png" +msgstr "" + +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" +msgstr "" + #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group1.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group2.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group3.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group4.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/dockers/LUT_Management_Docker.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR_1.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR2.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_webcomic.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_print.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_games.svg" msgstr "" -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_matrix_profile.png" -msgstr "" - -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" -msgstr "" - #: ../../general_concepts/colors/color_managed_workflow.rst:1 msgid "How a color managed workflow works." msgstr "介绍色彩管理流程的原理。" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "Color" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "Color Management" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "ICC Profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "OCIO" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:17 msgid "Color Managed Workflow" msgstr "色彩管理流程" #: ../../general_concepts/colors/color_managed_workflow.rst:19 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." msgstr "" "你可能听说过 Krita 具备一种叫做色彩管理的功能，你也可能对“色彩模型”和“色彩特" "性文件”之类的选项感到好奇。色彩管理对于从事专业数字影像工作的人员来说非常有" "用，我们会在此页面介绍它的来龙去脉。" #: ../../general_concepts/colors/color_managed_workflow.rst:22 msgid "Basic Info" msgstr "导言" #: ../../general_concepts/colors/color_managed_workflow.rst:24 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." msgstr "" "如果你从未使用过色彩管理进行作业，或者对此一无所知，那么你很可能正在使用一个 " "sRGB 色彩特性文件，在 8 位 RGB 色彩空间下进行作业。这意味着你可以为图像选用 " "*sRGB built-in* 或者 *sRGB-elle-v2-srgbtrc.icc* 特性文件。在 Krita 全新的色彩" "空间浏览器中，该色彩特性文件是在使用 8 位色彩通道时的默认值。" #: ../../general_concepts/colors/color_managed_workflow.rst:26 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." msgstr "" "如果你阅读本文的目的只是想知道哪个选项是默认值，你的目的已经达到了。但光知道" "默认值其实还远远不够。接下来我们将深入探讨色彩管理的理论知识，也许在阅读了这" "篇文章后，你可能会想要改变默认值，以便从滤镜、混合模式抑或是运用了颜色涂抹模" "型的笔刷中获得全新的结果。" #: ../../general_concepts/colors/color_managed_workflow.rst:29 msgid "What is the problem?" msgstr "色彩管理的目的" #: ../../general_concepts/colors/color_managed_workflow.rst:31 msgid "" "To explain the point of color management, you'd first need to learn which " "problem color management tries to solve." msgstr "要理解色彩管理的意义，我们首先要知道它是用来解决什么问题的。" #: ../../general_concepts/colors/color_managed_workflow.rst:33 msgid "Let us imagine a kinder garden:" msgstr "让我们想象一位老师正在给 4 个孩子上绘画课：" #: ../../general_concepts/colors/color_managed_workflow.rst:35 msgid "" "The class of 28 children is subdivided in groups of 7. Each group has its " "own table." msgstr "" "老师分给每个孩子几支水彩颜料，每个人分到的颜色都不同，然后让他们分开作画。" #: ../../general_concepts/colors/color_managed_workflow.rst:37 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." msgstr "" "老师给孩子们布置了一个绘画任务：画出一个红色的三角形、一个蓝色的正方形、一个" "绿色的圆形，然后用黄色框把这三个图形给围起来。孩子们只能使用手头上的颜料来作" "画。" #: ../../general_concepts/colors/color_managed_workflow.rst:40 msgid "The following results come from painting:" msgstr "下面就是孩子们交上来的结果：" #: ../../general_concepts/colors/color_managed_workflow.rst:42 msgid "" "Even though all groups had the same assignment, each group's result looks " "different." msgstr "尽管每个组的任务都是一样的，但是他们的成果看起来却不一样。" #: ../../general_concepts/colors/color_managed_workflow.rst:49 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." msgstr "" "第一个孩子用的颜料是朱红、明黄和群青。三角形的红色很鲜明，但圆形的绿色却很浑" "浊。这是因为群青的颜色实在是太暗了，用它很难调出鲜艳的绿色系。" #: ../../general_concepts/colors/color_managed_workflow.rst:56 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." msgstr "" "第二个孩子用的颜料是品红、明黄和天蓝。品红是一种接近粉红的红，而第一个孩子用" "的朱红与之相反，更接近橙色。绿色在这张图中看起来更顺眼，因为天蓝比较浅，用它" "调配的绿色也相对明亮一些。" #: ../../general_concepts/colors/color_managed_workflow.rst:64 msgid "" "Group 3 had vermillion red, citron yellow, emerald green and cerulean blue. " "They didn't mix their green, and thus ended up with a purer color." msgstr "" "第三个孩子用的颜料是朱红、明黄、翠绿和天蓝。这张画中的绿色不是用两种颜色调配" "出来的，所以看上去鲜艳明亮。" #: ../../general_concepts/colors/color_managed_workflow.rst:71 msgid "" "Finally, group 4 has vermillion red, citron yellow and cerulean blue. Their " "colors probably look like what you imagined." msgstr "第四个孩子用的颜料是朱红、明黄和天蓝。最终画出来的几种颜色还算正常。" #: ../../general_concepts/colors/color_managed_workflow.rst:73 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!" msgstr "" "在这个例子里，4 个孩子试图使用不同的颜料来呈现同样的颜色，结果颜色发生了偏" "差。不过这只是孩子涂鸦而已，少许偏差没什么大不了的。但想象一下如果这样的事情" "发生在一家印刷公司里会怎样？车间里的四台打印机把同一本杂志印成 4 种截然不同的" "效果，那就是印刷事故啦！" #: ../../general_concepts/colors/color_managed_workflow.rst:75 msgid "For this purpose, we invented color management." msgstr "为了让颜色在不同的输出设备中能够保持一致，我们发明了色彩管理体系。" #: ../../general_concepts/colors/color_managed_workflow.rst:78 msgid "What is color management?" msgstr "色彩管理的原理" #: ../../general_concepts/colors/color_managed_workflow.rst:80 msgid "" "Color management is, dryly put, a set of systems that tries to have the same " "color translate properly between color devices." msgstr "色彩管理是一整套用于在不同的显色设备之间保持颜色转换一致性的系统。" #: ../../general_concepts/colors/color_managed_workflow.rst:82 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." msgstr "" "这套系统一般会先把某种颜色转换到 XYZ 参考色彩空间。XYZ 是一个包含了人眼可以感" "知的一切颜色的坐标系。" #: ../../general_concepts/colors/color_managed_workflow.rst:84 msgid "" "From XYZ it can then be translated back into another device space, such as " "RGB (for screens), or CMYK (for printers)." msgstr "" "然后它会把该颜色从 XYZ 转换到其他设备的色彩空间，如 RGB (用于屏幕) 或 CMYK " "(用于打印)。" #: ../../general_concepts/colors/color_managed_workflow.rst:86 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." msgstr "" "Krita 有两套专门用于色彩管理的系统。一个是 **lcms2**，负责处理 ICC 特性文件。" "另一个则是 **OCIO**，负责处理 LUT 色彩管理。" #: ../../general_concepts/colors/color_managed_workflow.rst:88 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." msgstr "" "大致来说，ICC 特性文件通过一个参考色彩空间来保证在不同设备 (屏幕、打印机等) " "上呈现一致的颜色，而 OCIO 则可以对颜色的展现方式进行调整。" #: ../../general_concepts/colors/color_managed_workflow.rst:90 msgid "Within both we can identify the following color spaces:" msgstr "无论是哪个系统，我们都会按照用途把色彩空间识别为下面几类：" #: ../../general_concepts/colors/color_managed_workflow.rst:93 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 " "`." msgstr "" "设备空间用于描述显示器和打印机等颜色输出设备的色彩空间。设备空间的制作需要使" "用一种叫做“色差计”的小型计算机外设。以显示器为例，色差计与配套软件会测量显示" "器能够显示的最纯的红、绿、蓝、白、黑和灰等颜色，外加一些其他测量，最终生成一" "组受测屏幕的 ICC 特性文件。你可以在 Krita 的色彩管理选项页面里指定该特性文" "件。默认状态下我们会假定显示器符合 sRGB 规范，但大多数屏幕并不能完全符合 " "sRGB，而高品质显示器的色域又往往比 sRGB 更宽。而如果讨论的是打印机，许多印刷" "公司会给自己的打印机准备设备空间，有些公司还会希望由他们进行色彩转换，所以事" "先要问清楚。想要了解色差计的用法，可以 :ref:`阅读此文 " "` 。" #: ../../general_concepts/colors/color_managed_workflow.rst:94 msgid "Device spaces" msgstr "设备空间" #: ../../general_concepts/colors/color_managed_workflow.rst:96 msgid "Working spaces" msgstr "工作空间" #: ../../general_concepts/colors/color_managed_workflow.rst:97 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." msgstr "" "工作空间是色彩管理流程的参考色彩空间，我们一般会使用几种常见的规范性空间。" "Krita 等图像软件需要进行大量与色彩相关的运算，而在工作色彩空间内部进行这种运" "算效果更好，因此我们建议为你的图像指定一个工作空间特性文件。Krita 已经自带了" "用于 ICC 的特性文件，而用于 OCIO 的配置文件则可以从 OCIO 网站下载。" #: ../../general_concepts/colors/color_managed_workflow.rst:99 msgid "Aesthetic or Look spaces" msgstr "审美或观察空间" #: ../../general_concepts/colors/color_managed_workflow.rst:99 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." msgstr "" "这些特殊的色彩空间经过人为扭曲，用来为图像呈现某些特殊的视觉效果。Krita 没有" "自带 ICC 观察空间，也未在 OCIO 中对其提供支持。" #: ../../general_concepts/colors/color_managed_workflow.rst:102 msgid "Color managed workflow" msgstr "色彩管理流程" #: ../../general_concepts/colors/color_managed_workflow.rst:104 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:" msgstr "" "现在让我们粗略介绍一下色彩管理流程的全过程，为后面更深入的学习打下基础。下图" "是一个典型的色彩管理流程：" #: ../../general_concepts/colors/color_managed_workflow.rst:110 msgid ".. image:: images/color_category/Krita-colormanaged-workflow_text.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:110 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." msgstr "" "这是一个典型的色彩管理流程实例。我们先从扫描仪和数码相机输入图像，然后把这些" "图像转换到一个能够被各种编辑软件识别的工作空间，最后转换到用于屏幕观察或者打" "印输出的空间。" #: ../../general_concepts/colors/color_managed_workflow.rst:112 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." msgstr "" "在一个传统的色彩管理流程里，我们通常关注的是现实世界色彩与计算机色彩之间的转" "换。例如数码相机的照片或者扫描到计算机的图像等。如果你的成像设备具有自己的设" "备空间，我们首先要把这台设备的空间指定给它生成的图像，然后再把图像转换到一个" "工作空间。" #: ../../general_concepts/colors/color_managed_workflow.rst:114 #, fuzzy #| 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 "" "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." msgstr "" "我们接下来便要在该工作空间中完成所有的编辑作业，不同的编辑软件之间也通过该工" "作空间来相互配合。Krita 通过 ICC 特性文件与 GIMP 2.9 +、Inkscape、Digikam 和 " "Scribus 等软件对接，通过 OCIO 配置来与 Blender 和 Natron 等软件对接。" #: ../../general_concepts/colors/color_managed_workflow.rst:116 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." msgstr "" "你的工作文件本身也是保存在工作空间下面的。工作文件在这里指的是用于作品编辑的" "高分辨率、图层分离的原文件。" #: ../../general_concepts/colors/color_managed_workflow.rst:118 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." msgstr "" "在图像的编辑过程中，我们还可以把具有某种审美意趣“观察空间”应用到图像上，人为" "地扭曲图像的显示效果。这是一个相当高级的运用领域，在使用 Krita 的时候一般用不" "着关注这个。" #: ../../general_concepts/colors/color_managed_workflow.rst:120 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." msgstr "" "图像在完成编辑之后便要进行输出，这就要求我们把图像转换到输出空间。输出空间是" "另一台设备的色彩空间，它可以是打印机的 CMYK 特性文件，也可以是某台显示器的 " "RGB 特性文件。如果是打印输出，家用和办公打印机会在设备内部完成输出空间转换，" "而印刷公司的情况会复杂一些。每家印刷公司的习惯不同，有些公司习惯让客户自行把" "图像的工作空间转换到他们打印机的设备空间，有些则习惯直接获取客户的原始图像代" "为转换。所以在联系印刷公司时，你应该询问对方关于图像输出的要求。" #: ../../general_concepts/colors/color_managed_workflow.rst:122 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." msgstr "" "屏幕显示本身也是一种输出方式。你可以把屏幕当成一个望远镜，你必须通过它才能看" "到图像，而它的镜片会影响你透过它看见的颜色。每台屏幕的颜色显示效果不同，所以" "在理想状态下它们应该配有自己的特性文件。和打印机只需要转换一次空间相比，图像" "输出到屏幕时必须持续不断地进行色彩空间转换。图像在编辑软件视图中发生的每一次" "变化，都会按照显示器的设备特性文件进行转换。" #: ../../general_concepts/colors/color_managed_workflow.rst:124 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." msgstr "" "因此，如果你的显示器没有特性文件，计算机就无法得知你的屏幕的相对特性并进行相" "应的色彩转换，你也就无法确定它显示的颜色是否准确。你必须首先为你的显示器进行" "特性化，制作它的设备特性文件，然后在 Krita 的色彩管理选项中把该特性文件设为设" "备空间，最后还要把正在编辑的图像的工作空间设为 sRGB 空间。只有满足了这些条" "件，你的显示器才能在 sRGB 色彩空间下显示准确的颜色。" #: ../../general_concepts/colors/color_managed_workflow.rst:127 msgid "So what does this mean?" msgstr "色彩管理和数字绘画" #: ../../general_concepts/colors/color_managed_workflow.rst:133 msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_krita_text.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:133 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." msgstr "" "如果我们使用计算机从头开始绘制作品，我们可以把显示器的特性文件作为输入空间，" "因为画面使用的颜色就是通过这台显示器选取的。虽然这可以简化色彩管理流程，但也" "意味着显示器特性文件和观察条件的作用更加重要了。" #: ../../general_concepts/colors/color_managed_workflow.rst:135 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*." msgstr "" "为了让输入和输出的色彩完全一致，摄影师和特效行业负责颜色修正的人员需要考虑许" "多因素，这里面甚至包括了时间、天气和装修的颜色。这种讲究并不是在故弄玄虚。举" "个例子，如果显示器背后的墙壁是纯红色的，你的眼睛为了适应这个环境会降低对红色" "敏感程度，于是在程序里选择的颜色就会偏红。我们把观察颜色时所在环境的照明等因" "素称为 **观察条件** 。" #: ../../general_concepts/colors/color_managed_workflow.rst:137 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." msgstr "" "观察条件对于画手的影响比摄影师要少一些。画作是全人工绘制的，我们主要靠明暗和" "颜色之间的反差来营造氛围和突出重点。即使成品比我们的原意要偏红，作品整体也不" "至于会因此毁掉。我们可以回顾本文开头孩子们画画的例子，虽然每张图的颜色存在偏" "差，但这并不妨碍我们理解图像想要表达的颜色是什么。我们还可以在后期对颜色进行" "修正，只是修正的过程会很麻烦。要是一开始就把观察条件考虑在内，我们日后的工作" "就可以更加轻松。" #: ../../general_concepts/colors/color_managed_workflow.rst:139 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." msgstr "" "尽管如此，了解工作空间的相关知识对于画手来说还是相当有用的。不同的工作空间在" "使用滤镜和混合颜色时会给出不同的结果。如果要运用像 HDR 这样的高科技，也需要知" "道哪些工作空间与之兼容。" #: ../../general_concepts/colors/color_managed_workflow.rst:141 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." msgstr "" "正如上文所说的那样，Krita 是一个专门为了从头开始绘制图像而设计的程序，它的工" "作空间不是在图像制作完成之后才去指定的。因为你必须通过显示器去观察正在制作的" "图像，在显示器对图像的影响下选取颜色，所以显示器的设备空间可被看作是图像的输" "入空间。这也是为什么你应该为你的显示器进行特性化，并把生成的特性文件指定给 " "Krita。这一步虽然麻烦，但从长远来看可以为你的绘画和印前准备带来极大的好处。" #: ../../general_concepts/colors/color_managed_workflow.rst:143 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.)" msgstr "" "不管怎样，我们应该时刻留意观察条件带来的影响。许多专业的画手会选用中性灰作为" "画布背景色，因为他们发现这样可以画出光色更为明快的作品，而这背后的原理便是中" "性灰改善了他们的观察条件。这也是为什么包括 Krita 在内的众多影像软件都会自带一" "套暗色主题。(不过说不定也因为暗色主题看起来更高大上一些)" #: ../../general_concepts/colors/color_managed_workflow.rst:148 msgid "ICC profiles" msgstr "ICC 特性文件" #: ../../general_concepts/colors/color_managed_workflow.rst:150 #, fuzzy #| 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 "" "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:" msgstr "" "ICC 特性文件是一组用于色彩管理的坐标数据，它描述了在 XYZ 坐标中设备空间的各个" "顶点。它用于在工作空间和打印机之间，或者在不同的印刷行业软件之间进行色彩转换" "和配合，如 GIMP、Scribus、Photoshop、Illustrator、Inkscape、Digikam、" "RawTheraphee 等。ICC 特性文件有两种：" #: ../../general_concepts/colors/color_managed_workflow.rst:153 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." msgstr "" "这些特性文件是 Krita 自带的。阶调矩阵特性文件中包含了各个坐标点的参数和它们之" "间的插值，以此确定色彩空间的确切体积。Krita 的色彩空间浏览器已经为它们准备了" "详尽的介绍资料。这些特性文件适合用作工作空间。" #: ../../general_concepts/colors/color_managed_workflow.rst:159 #, fuzzy #| msgid "Matrix Shaper profiles." msgid "Matrix Shaper profiles" msgstr "阶调矩阵特性文件" #: ../../general_concepts/colors/color_managed_workflow.rst:159 msgid "" "Matrix shaper profiles have a few parameters that describe the color space " "which are then interpolated between, this requires a lot of maths." msgstr "" "阶调矩阵特性文件包含了一些描述色彩空间的坐标参数，在这些参数之间的部分则是通" "过插值来填补的，这需要进行大量的数学运算。" #: ../../general_concepts/colors/color_managed_workflow.rst:162 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." msgstr "" "这种特性文件并不常见，主要用于描述打印机设备空间，如 CMYK 等。cLUT 是 Color " "Look-up Table 即查找表的英文缩写，它们比阶调矩阵特性文件的数据量要大得多，这" "样才能能针对一些难以预见的情况，如某些颜料的混合特性等保存所需的数据。这是描" "述色彩空间的一种极为专业的手段，所以许多不关注色彩管理的程序不会支持它们。" #: ../../general_concepts/colors/color_managed_workflow.rst:168 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." msgstr "" "cLUT 特性文件为处于该色彩空间中的每种颜色准备了表格以记录它们在参考空间中的坐" "标。对 CMYK 而言一般采用 L\\*A\\*B\\* 空间，而其他类型的特性文件通常使用 XYZ " "空间。这些表格的制作过程格外麻烦，所以它们也较为少见。 " #: ../../general_concepts/colors/color_managed_workflow.rst:169 msgid "cLUT profiles" msgstr "cLUT 特性文件" #: ../../general_concepts/colors/color_managed_workflow.rst:171 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." msgstr "" "ICC 特性文件的有趣之处是你可以使用一个比设备空间更宽广的工作空间。一般来说这" "不是坏事，可到了转换空间的时候你就得面对如何转换工作空间数值的问题。" #: ../../general_concepts/colors/color_managed_workflow.rst:174 msgid "Perceptual" msgstr "可感知" #: ../../general_concepts/colors/color_managed_workflow.rst:174 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." msgstr "" "此模式把工作空间中的数值进行挤压，然后塞进要转换到的目标空间里。这种转换手段" "对于重现可感知的全部明度范围很有用，但不适合需要精确重现颜色的用途。如果你想" "分清一个图像中的各种颜色，或者想要完整表达原图各种光色之间的明暗关系，可以选" "用此模式。此模式不兼容阶调矩阵特性文件，它默认给相对比色模式使用。" #: ../../general_concepts/colors/color_managed_workflow.rst:177 #, fuzzy #| msgid "Absolute Colorimetric." msgid "Absolute Colorimetric" msgstr "绝对比色" #: ../../general_concepts/colors/color_managed_workflow.rst:177 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." msgstr "" "与可感知模式相反，绝对比色模式会牺牲一切其他因素来保持正确的颜色数值，这样有" "可能产生难看的颜色。建议仅用于色彩重现工作。由于 ICC v4 色彩管理流程标准的限" "制，此模式不兼容阶调矩阵特性文件。" #: ../../general_concepts/colors/color_managed_workflow.rst:180 msgid "Relative Colorimetric" msgstr "相对比色" #: ../../general_concepts/colors/color_managed_workflow.rst:180 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." msgstr "" "这是一个介于可感知模式和绝对比色模式之间的模式。相对比色模式会首先尝试匹配两" "个色彩空间中相同的颜色。要做到这一点，它首先对齐两个空间的白点和黑点，然后沿" "着两个空间的相对边界进行切除。由于 ICC v4 色彩管理流程规范只允许为阶调矩阵特" "性文件使用相对比色模式，因此所有阶调矩阵特性文件都默认使用此模式。" #: ../../general_concepts/colors/color_managed_workflow.rst:183 msgid "Saturation" msgstr "饱和度优先" #: ../../general_concepts/colors/color_managed_workflow.rst:183 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." msgstr "" "此模式会不惜一切代价来保持颜色的鲜艳程度，为此可以牺牲色相的一致性。用于信息" "图。此模式不兼容阶调矩阵特性文件，那些特性文件会默认使用相对比色模式。" #: ../../general_concepts/colors/color_managed_workflow.rst:185 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." msgstr "" "**ICC 特性文件版本** 是在与 ICC 特性文件打交道时最后一件需要留意的事情。" "Krita 同时预装了符合第 2 版 (V2) 和第 4 版 (V4) 规范的特性文件，后者进行颜色" "运算时效果更好，但前者的受支持范围更广 (参见下文“与其他应用程序配合”一节)，因" "此 Krita 默认使用 V2，我们也建议在无法确定其他程序是否支持 V4 的情况下选用 " "V2。" #: ../../general_concepts/colors/color_managed_workflow.rst:188 msgid "LUT docker and HDR imaging" msgstr "LUT 工具面板和 HDR 成像" #: ../../general_concepts/colors/color_managed_workflow.rst:196 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." msgstr "" ":ref:`lut_docker` 是 Krita 次要的色彩管理模块，它与 Blender、Natron 和 Nuke " "的色彩管理系统可以互通，它仅使用配置文件中定义的查找表。" #: ../../general_concepts/colors/color_managed_workflow.rst:198 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." msgstr "" "你可以在“输入色彩空间”处设置图像的工作空间，然后把“显示设备”设为 sRGB 或者你" "添加到配置中的自定义 LUT 文件。在此场景下的“查看”选单可以用来模拟某种显示设备" "进行软打样。" #: ../../general_concepts/colors/color_managed_workflow.rst:200 msgid "" "Component, exposure, gamma, whitepoint and blackpoint are knobs which allows " "you to modify the display filter." msgstr "颜色分量、曝光、gamma、白点和黑点滑动条用于对视图的显示滤镜进行调整。" #: ../../general_concepts/colors/color_managed_workflow.rst:208 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." msgstr "" "正如前面解释的那样，我们可以把显示器看作是用来观察图像的一个望远镜，它会对图" "像造成轻微的影响。我们也可以对这个望远镜进行改造，就好象插入了一片滤镜的方式" "来以另外一种方式去观察图像。例如我们可以通过某种改造让我们可以看见比我们的显" "示器的白点更亮的白。要说清楚这一点，我们要首先讨论一下白是什么。" #: ../../general_concepts/colors/color_managed_workflow.rst:210 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." msgstr "" "例如，我们显示器上的白是它能够显示的最亮的纯红、纯绿和纯蓝叠加而来的。这种白" "受显示器自身特性的影响，和白纸的白、牛奶的白、阳光的白，甚至是随便一台手机显" "示的白都是不一样的。" #: ../../general_concepts/colors/color_managed_workflow.rst:212 msgid "" "Black similarly, is brighter on a LCD display than a LED one, and " "incomparable with the black of a carefully sealed room." msgstr "" "黑也是同理，在 LCD 面板上的黑要比 LED 面板上的黑要更亮，这是因为 LCD 面板使用" "一组背光照亮整个面板，即使纯黑的画面也会漏出少许背光，而 LED 面板在纯黑的位置" "是不发光的。正因如此，LCD 面板的黑与一间被彻底密封起来的房间内部的黑根本没有" "可比性。" #: ../../general_concepts/colors/color_managed_workflow.rst:214 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." msgstr "" "这意味着可能存在比屏幕显示的黑更暗的黑，比屏幕显示的白更亮的白。不过为了方便" "起见，让我们先将黑点和白点指定成某个数值，然后比较某种黑是否比该黑点更暗，某" "种白是否比该白点更亮。" #: ../../general_concepts/colors/color_managed_workflow.rst:216 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." msgstr "" "LUT 工具面板让我们可以对视图显示滤镜对色彩施加的变化进行控制。这项功能用于修" "改那些为场景参照亮度而制作的图像，如 HDR 照片或者由渲染引擎输出的图像。" #: ../../general_concepts/colors/color_managed_workflow.rst:224 msgid "" "So, for example, we can choose to scale whiter-than-screen-white to our " "screen-white so we can see the contrasts there." msgstr "" "例如我们可以把比屏幕白更亮的白的范围按照我们的屏幕白进行等比挤压，这样就可以" "看清整体的明暗关系了。" #: ../../general_concepts/colors/color_managed_workflow.rst:226 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." msgstr "" "这么做的意义是让你看清楚图像亮部所包含的细节。尽管你无法分辨屏幕白和比它更亮" "的白的真实区别 (因为你的屏幕显示不出来)，图像程序依然能够照常处理其中的色彩数" "据。" #: ../../general_concepts/colors/color_managed_workflow.rst:228 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." msgstr "" "一个常见的用例是在一个 3D 模型与现实场景之间匹配光照效果。另外一个用例是高级" "照片修图作业时通过这种手段呈现图像中尽可能多的色彩对比信息。对于绘画作业本身" "而言，这让你可以自如地控制整体的对比度和亮度。" #: ../../general_concepts/colors/color_managed_workflow.rst:230 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." msgstr "" "LUT 面板可以对每个视图单独进行色彩控制，你可以创建一个新视图并设置为光度模" "式，这样你就可以同时看见彩色图和灰度图，便于把握图像整体的亮度。" #: ../../general_concepts/colors/color_managed_workflow.rst:232 msgid "" "Another example is to carefully watch the gradients in a certain section." msgstr "还有一个用例就是对某段色彩渐变的呈现效果进行仔细的监测。" #: ../../general_concepts/colors/color_managed_workflow.rst:234 #, fuzzy #| 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." msgstr "" "你可以在 LUT 面板里创建一个类似 ICC 的特性文件。在这里我们要创建的" "是“LUT” (Look Up Table，查找表)，通过修改 OCIO 配置文件可将其添加进 OCIO。当 " "OCIO 启用时，菜单栏的 :menuselection:`设置 --> 配置 Krita --> 色彩管理` 选项" "页面将被停用。你只能在使用 :guilabel:`内建` 色彩引擎时才能使用该选项页面。" #: ../../general_concepts/colors/color_managed_workflow.rst:237 msgid "In summary" msgstr "总结" #: ../../general_concepts/colors/color_managed_workflow.rst:239 msgid "Krita has two modes of color management:" msgstr "Krita 具备两种色彩管理模式：" #: ../../general_concepts/colors/color_managed_workflow.rst:241 msgid "" "ICC works in terms of spaces relative to the CIEXYZ space, and requires an " "ICC profile." msgstr "ICC 基于 CIEXYZ 参考色彩空间工作，需要使用 ICC 特性文件。" #: ../../general_concepts/colors/color_managed_workflow.rst:242 #, fuzzy #| msgid "OCIO works in terms of interpretation, and makes use of luts." msgid "OCIO works in terms of interpretation, and makes use of LUTs." msgstr "OCIO 用来调整视图的色彩呈现效果，使用 LUT 查找表。" #: ../../general_concepts/colors/color_managed_workflow.rst:243 msgid "both can be made with a colorimeter." msgstr "ICC 特性文件和 LUT 查找表都可以使用色差计进行制作。" #: ../../general_concepts/colors/color_managed_workflow.rst:244 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." msgstr "" "如果你想要组建一个正确的色彩管理流程，你必须自行为输入设备 (你的显示器) 和输" "出设备 (你的打印机或者目标显示器) 制作相应的 ICC 特性文件或者 LUT 查找表。面" "向网络用途的输出图像应该总是使用 sRGB 空间。" #: ../../general_concepts/colors/color_managed_workflow.rst:245 msgid "" "Set up your screen profiles under :menuselection:`Settings --> Configure " "Krita --> Color management`." msgstr "" "你可以在菜单栏的 :menuselection:`设置 --> 配置 Krita --> 色彩管理` 选项页面设" "置显示器的特性文件。" #: ../../general_concepts/colors/color_managed_workflow.rst:246 #, fuzzy #| msgid "" #| "Do NOT use screen profiles or other device profiles to draw in. Use a " #| "working space profile such as any of the elle profiles for this, as the " #| "color maths will be much more predictable and pleasant. Krita will " #| "convert between your screen and working space on the fly, allowing you to " #| "pick the correct colors. This turns your screen into binoculars to view " #| "the image." msgid "" "Do NOT use screen profiles or other device profiles to draw in. Use a " "working space profile such as any of the 'elle' profiles for this, as the " "color maths will be much more predictable and pleasant. Krita will convert " "between your screen and working space on the fly, allowing you to pick the " "correct colors. This turns your screen into binoculars to view the image." msgstr "" "切勿在制作的图像中使用显示器或者其他设备特性文件作为工作空间。你应当为图像指" "定一个像 elle 系列这样的工作空间，这样色彩的运算效果不但更好，而且更易于预" "测。Krita 会持续地在显示器的设备空间和工作空间之间进行色彩转换，确保你可以看" "到并选取正确的颜色。" #: ../../general_concepts/colors/color_managed_workflow.rst:247 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." msgstr "" "你应该按照色彩管理流程的具体情况选用合适的色彩管理方式。如果你要与 Blender 协" "同工作，你应该选用 OCIO 而不是 ICC。如果你要与 Scribus 或者 Photoshop 协同工" "作，你应该选用 ICC。" #: ../../general_concepts/colors/color_managed_workflow.rst:249 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." msgstr "" "Krita 会进行大量的色彩运算，这常常与颜色的混合有关。此类运算在线性的色彩空间" "中效果最好，而线性的色彩空间要求至少 16 位的通道深度才能正常工作。线性空间纵" "然有诸多好处，但它的缺点是不好理解。" #: ../../general_concepts/colors/color_managed_workflow.rst:251 #, fuzzy #| 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 "" "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!" msgstr "" "如果你喜欢绘画，又有足够的内存，现在想要迈出利用 Krita 色彩管理功能的第一步，" "那么首先你可以把你所有的图像的工作空间从 sRGB built-in 转换到 16 位浮点下的 " "sRGB-v2-elle-g10.icc 或者 rec2020-v2-elle-g10.icc 特性文件。这不但可以使得色" "彩的混合效果更好，而且也为你打开了通向 HDR 图像编辑的大门。" #: ../../general_concepts/colors/color_managed_workflow.rst:256 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!" msgstr "" "某些显卡，如使用 Nvidia 芯片的显卡在使用 16 位浮点通道时性能最佳，这是因为 " "Nvidia 显卡会在内部将数据转换成浮点格式。如果图像本身就是使用浮点，这个转换过" "程就可以省略，处理速度也会因此提高。" #: ../../general_concepts/colors/color_managed_workflow.rst:260 msgid "" "No amount of color management in the world can make the image on your screen " "and the image out of the printer have 100% the same color." msgstr "" "在现实条件下，不管色彩管理手段如何先进，执行过程如何完善，也绝无可能在屏幕显" "示和打印输出之间保持 100% 一致的颜色。" #: ../../general_concepts/colors/color_managed_workflow.rst:263 msgid "Exporting" msgstr "导出图像时的相关技巧" #: ../../general_concepts/colors/color_managed_workflow.rst:265 msgid "" "When you have finished your image and are ready to export it, you can modify " "the color space to optimize it:" msgstr "在处理完一张图像并准备导出时，你可以修改它的色彩空间以优化输出效果：" #: ../../general_concepts/colors/color_managed_workflow.rst:267 msgid "If you are preparing an image for the web:" msgstr "如果你要为网络用途准备该图像：" #: ../../general_concepts/colors/color_managed_workflow.rst:269 msgid "" "If you use 16bit color depth or higher, convert the image to 8bit color " "depth. This will make the image much smaller." msgstr "" "如果你的工作空间色彩深度在 16 位或以上，你应该在导出时把图像转换为 8 位深度。" "这样会大大缩小图像的体积。" #: ../../general_concepts/colors/color_managed_workflow.rst:271 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." msgstr "" "Krita 目前尚不具备内建的抖动算法，这意味着从 16 位转换到 8 位深度时会产生轻微" "的颜色条纹。不过你可以通过下述手段来模拟颜色抖动：插入一个填充图层，在其中填" "充一个图案，将不透明度设为 5% 然后把图层的混合方式设成叠加。把整个图像平整为" "一层，然后再把它转换成 8 位。你刚才填充的图案便会如同抖动效果一样，让转换后的" "渐变色彩更为平滑。" #: ../../general_concepts/colors/color_managed_workflow.rst:273 msgid "If it's a gray-scale image, convert it to gray-scale." msgstr "如果图像只含有灰度，那就把它的色彩空间转换为灰阶。" #: ../../general_concepts/colors/color_managed_workflow.rst:274 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." msgstr "" "如果图像是彩色的，那就把它的工作空间特性文件保存到图像中。现在许多网页浏览器" "都能处理嵌入在图像中的色彩特性文件。以 Firefox 为例，如果对方的显示器具备一个" "色彩特性文件，Firefox 便会把你的图像按照该设备空间进行转换。这样一来该图像便" "可以在你的源显示器和已特性化的其他显示器上呈现几乎一致的效果。" #: ../../general_concepts/colors/color_managed_workflow.rst:279 #, fuzzy #| 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 `_, save your png, jpg or tiff without an embedded profile " #| "to work around this." 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 " "`_, save your PNG, JPG or TIFF without an embedded profile to work " "around this." msgstr "" "嵌入了特性文件的图像在某些版本的 Firefox 里会呈现不正常的颜色。这是 Firefox " "的一个 bug，因为它的 `色彩管理系统并不完整 `_ 。要避免这种情况，可以在保" "存 png、jpg 或 tiff 图像时不嵌入特性文件。" #: ../../general_concepts/colors/color_managed_workflow.rst:281 msgid "If you are preparing for print:" msgstr "如果你在进行印前准备：" #: ../../general_concepts/colors/color_managed_workflow.rst:283 #, fuzzy #| msgid "" #| "You hopefully made the picture in a working space profile instead of the " #| "actual custom profile of your screen, if not, convert it to something " #| "like adobe rgb, sRGB or rec2020." msgid "" "You hopefully made the picture in a working space profile instead of the " "actual custom profile of your screen, if not, convert it to something like " "Adobe RGB, sRGB or Rec. 2020." msgstr "" "在制作需要打印的图像时，应该为图像指定一个工作空间特性文件，最好不要为图像指" "定显示器的自定义设备空间特性文件。如果你的图像使用了显示器特性文件，你应该把" "它转换成例如 Adobe RGB、sRGB 或者 rec2020 这样的工作空间特性文件。" #: ../../general_concepts/colors/color_managed_workflow.rst:284 msgid "" "Check with the printer what kind of image they expect. Maybe they expect " "sRGB color space, or perhaps they have their own profile." msgstr "" "你要检查清楚打印机能够接受的图像色彩空间。有些打印机可以接受 sRGB 色彩空间，" "另外一些则要使用它们自己的特性文件。" #: ../../general_concepts/colors/color_managed_workflow.rst:287 msgid "Interaction with other applications" msgstr "与其他应用程序配合" #: ../../general_concepts/colors/color_managed_workflow.rst:290 msgid "Blender" msgstr "Blender" #: ../../general_concepts/colors/color_managed_workflow.rst:292 #, fuzzy #| 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 "" "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." msgstr "" "如果你想要使用 Krita 的 OCIO 功能，尤其是要与 Blender 的色彩管理协同工作时，" "你可以让它使用 Blender 的 OCIO 配置。" #: ../../general_concepts/colors/color_managed_workflow.rst:294 #, fuzzy #| msgid "" #| "Blender's OCIO config is under ``/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 "" "Blender's OCIO config is under ``/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." msgstr "" "Blender 的 OCIO 配置可以在 ``/版本号/datafiles/" "colormanagement`` 下面找到。将 LUT 面板设为使用 OCIO 引擎，然后把配置指定为上" "述路径。这将让你可以使用 Blender 的输入和屏幕空间，但 Krita 尚不支持它的观察" "空间。" #: ../../general_concepts/colors/color_managed_workflow.rst:298 msgid "Windows Photo Viewer" msgstr "Windows 照片查看器" #: ../../general_concepts/colors/color_managed_workflow.rst:300 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." msgstr "" "Krita 生成的图像与某些应用程序之间存在兼容性问题。其中一个重要的问题发生在 " "Windows 自带的照片查看器上面，因为它无法处理新型的 ICC 特性文件。Krita 使用" "第 4 版的特性文件，而 Windows 照片查看器只能处理第 2 版的特性文件。如果你在导" "出成 JPEG 时嵌入了特性文件，Windows 照片查看器会把该图像显示得过于昏暗。" #: ../../general_concepts/colors/color_managed_workflow.rst:303 msgid "Example workflows" msgstr "色彩管理流程范例" #: ../../general_concepts/colors/color_managed_workflow.rst:305 msgid "" "Here are some example workflows to get a feeling of how your color " "management workflow may look like." msgstr "下面时一些色彩管理流程的范例，你可以参考它们来规划自己的色彩管理流程。" #: ../../general_concepts/colors/color_managed_workflow.rst:307 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'." msgstr "" "如前所述，显示器的输入空间是在菜单栏的 :menuselection:`设置 --> 配置 Krita --" "> 色彩管理` 选项页面或者在 LUT 面板的“显示设备”处设置的。工作空间既可以在新建" "文档时设置，也可以在 LUT 面板的“输入空间”处设置。" #: ../../general_concepts/colors/color_managed_workflow.rst:310 msgid "Webcomic" msgstr "网络漫画" #: ../../general_concepts/colors/color_managed_workflow.rst:317 #: ../../general_concepts/colors/color_managed_workflow.rst:339 #: ../../general_concepts/colors/color_managed_workflow.rst:357 msgid "Input" msgstr "输入空间" #: ../../general_concepts/colors/color_managed_workflow.rst:318 #: ../../general_concepts/colors/color_managed_workflow.rst:340 #: ../../general_concepts/colors/color_managed_workflow.rst:358 msgid "Your screen profile. (You pick colors via your screen)" msgstr "你的显示器特性文件，因为你在制作图像时通过这台显示器选取颜色。" #: ../../general_concepts/colors/color_managed_workflow.rst:319 #: ../../general_concepts/colors/color_managed_workflow.rst:341 #: ../../general_concepts/colors/color_managed_workflow.rst:359 msgid "Workingspace" msgstr "工作空间" #: ../../general_concepts/colors/color_managed_workflow.rst:320 msgid "" "sRGB (the default screen profile) or any larger profile if you can spare the " "bit depth and like working in them." msgstr "" "sRGB (默认显示器特性文件)，如果你喜欢也可以换用其他空间更大的特性文件，但前提" "是你的计算机能够流畅处理更高的位深度。" #: ../../general_concepts/colors/color_managed_workflow.rst:322 #: ../../general_concepts/colors/color_managed_workflow.rst:344 #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "Output" msgstr "输出空间" #: ../../general_concepts/colors/color_managed_workflow.rst:322 msgid "" "sRGB, ICC version 2, sRGB TRC for the internet, and a specialized CMYK " "profile from the printing house for the printed images." msgstr "" "sRGB，ICC 第 2 版，为互联网用途而设的 sRGB TRC 空间，还有印刷公司提供的专供打" "印图像使用的 CMYK 特性文件。" #: ../../general_concepts/colors/color_managed_workflow.rst:324 #, fuzzy #| 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 "" "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." msgstr "" "使用 sRGB-elle-V2-srgbtrc.icc 来在 Inkscape、Photoshop、Painttool SAI、" "Illustrator、Paintstorm Studio、Mypaint、Artrage、Scribus 和 Krita 之间交换图" "像。" #: ../../general_concepts/colors/color_managed_workflow.rst:326 #, fuzzy #| 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 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." msgstr "" "如果你在通过 ICC 运用比这更大的色彩空间，你将只能在 Krita、Photoshop、" "Illustrator、GIMP 2.9、Manga Studio 和 Scribus 之间进行互换。其他的软件会无条" "件地假定你的工作空间是 sRGB，因为它们并没有色彩管理功能。" #: ../../general_concepts/colors/color_managed_workflow.rst:328 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." msgstr "" "如果你在 Krita 与 Blender、Nuke、Natron 之间进行互换，使用 OCIO 并将输入空间" "设为 “sRGB”，但记得在创建新文档时为 ICC 选择 sRGB 色彩特性文件。" #: ../../general_concepts/colors/color_managed_workflow.rst:330 #, fuzzy #| 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 "" "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." msgstr "" "对于面向网络输出的最终图像，应把图像转换为 8 位的 sRGB，srgbtrc，不要嵌入 " "ICC 特性文件。如果你输出成 PNG，还可以用 PNGCrush 或者其他应用对其进行优化处" "理。在此场景中选用 sRGB 的理由是：你可以假设绝大多数受众都不会为他们的屏幕进" "行特性化，而他们的屏幕大概也不会高级到可以支持宽色域之类的特性。所以我们应该" "默认使用 sRGB 来转换用于互联网的图像。" #: ../../general_concepts/colors/color_managed_workflow.rst:333 msgid "Print" msgstr "打印" #: ../../general_concepts/colors/color_managed_workflow.rst:342 #, fuzzy #| msgid "sRGB or rec2020 if you can afford the bit-depth being 16bit." msgid "sRGB or Rec. 2020 if you can afford the bit-depth being 16bit." msgstr "sRGB，如果你能使用 16 位深度，则使用 rec2020。" #: ../../general_concepts/colors/color_managed_workflow.rst:344 msgid "" "Specialized CMYK profile from the printing house for the printed images." msgstr "印刷公司为打印图像提供的专用 CMYK 特性文件。" #: ../../general_concepts/colors/color_managed_workflow.rst:346 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." msgstr "" "每台打印机的 CMYK 特性文件都是不同的，有些打印机甚至针对不同的纸张和油墨准备" "了不同的特性文件，因此不能随便找一个 CMYK 特性文件用于印刷。你应该直接向你的" "印刷公司索取专用的特性文件。" #: ../../general_concepts/colors/color_managed_workflow.rst:348 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." msgstr "" "你可以将高级拾色器设成匹配某个特性文件，首先到菜单栏的 :menuselection:`设置 " "--> 配置 Krita --> 高级拾色器设置` 。勾选 :guilabel:`拾色器使用与图像不同的色" "彩空间` 然后选取你的目标 CMYK 特性文件。这将略微限制你能够运用的颜色，但你依" "然可以在 RGB 空间下面使用所有滤镜和混色选项。" #: ../../general_concepts/colors/color_managed_workflow.rst:351 msgid "Games" msgstr "游戏" #: ../../general_concepts/colors/color_managed_workflow.rst:360 msgid "sRGB or grayscale linear for roughness and specular maps." msgstr "对于粗糙度和高光贴图，应选用线性 sRGB 或灰阶。" #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "" "This one is tricky, but in the end it'll be sRGB for the regular player." msgstr "这个比较棘手，但一般情况下使用 sRGB。" #: ../../general_concepts/colors/color_managed_workflow.rst:364 #, fuzzy #| 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 "" "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." msgstr "" "这一点比较棘手的原因是，虽然你可以在不同的程序之间使用 OCIO 和 ICC，但我们推" "荐把提供给引擎的图像设为 sRGB 或灰阶。许多较新的基于物理原理的渲染器允许指定" "一张图像被视作线性还是 srgbtrc 图像来进行处理。由于在这种游戏渲染器中图像空间" "的正确识别非常重要，所以设为 sRGB 是一种额外的保险。" #: ../../general_concepts/colors/color_managed_workflow.rst:366 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." msgstr "" "虽然游戏引擎需要加载为它们优化过的内容，一般推荐使用 8 位深度，但未来的屏幕可" "能会具备更高的位深度，而渲染器终有一天会支持这些特性。为了减少日后更新游戏素" "材时的痛苦，可以现在就打造一个采用更大色彩空间的色彩管理流程，然后编写一些脚" "本来满足当下的渲染需要。" #: ../../general_concepts/colors/color_managed_workflow.rst:368 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." msgstr "" "法线贴图和高度贴图虽然是在一个“非彩色数据”的工作空间下进行定义的，但你会发现" "绝大多数引擎都不太在乎这个。你应该告诉游戏引擎在导入时不要进行任何转换操作。" #: ../../general_concepts/colors/color_managed_workflow.rst:370 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)." msgstr "" "高光、光泽度、金属度和粗糙度贴图全部基于线性运算，所以如果某种材质的金属度是 " "0.3，就意味着它是在一个线性空间中 30% 的灰。因此记得告诉游戏引擎的渲染器这是" "一个线性图像 (或者至少不要对其进行转换操作)。" #: ../../general_concepts/colors/color_managed_workflow.rst:374 #, fuzzy #| msgid "" #| "`Visualizing the XYZ color space `_" msgid "" "`Visualizing the XYZ color space `_." msgstr "" "`对 XYZ 色彩空间的视觉化介绍 `_" #: ../../general_concepts/colors/color_managed_workflow.rst:375 #, fuzzy #| msgid "" #| "`Basics of gamma correction `_" msgid "" "`Basics of gamma correction `_." msgstr "" "`Gamma 校正的基础知识 `_" #: ../../general_concepts/colors/color_managed_workflow.rst:376 #, fuzzy #| 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 `_" 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 `_." msgstr "" "`Panda3D 关于并非通过 3D 渲染器编码的图像会被提示其 gamma 编码将造成图像过暗" "的说明 `_" #: ../../general_concepts/colors/color_managed_workflow.rst:377 #, fuzzy #| msgid "" #| "`2d examples of the effect of gamma-encoding on color maths `_" msgid "" "`2D examples of the effect of gamma-encoding on color maths `_." msgstr "" "`Gamma 编码方式对于色彩运算的影响的 2D 示例 `_" #: ../../general_concepts/colors/color_managed_workflow.rst:378 #, fuzzy #| msgid "" #| "`Basic overview of color management from argylcms manual `_" msgid "" "`Basic overview of color management from ArgyllCMS manual `_." msgstr "" "`ArgyllCMS 手册中关于色彩管理基础的概览章节 `_" diff --git a/locale/zh_TW/LC_MESSAGES/contributors_manual/krita_manual_conventions.po b/locale/zh_TW/LC_MESSAGES/contributors_manual/krita_manual_conventions.po index 0aa373a7e..2930ebe2b 100644 --- a/locale/zh_TW/LC_MESSAGES/contributors_manual/krita_manual_conventions.po +++ b/locale/zh_TW/LC_MESSAGES/contributors_manual/krita_manual_conventions.po @@ -1,1139 +1,1139 @@ # SOME DESCRIPTIVE TITLE. # 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 , YEAR. # msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-09 03:27+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: Chinese \n" "Language: zh\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=1; plural=0;\n" #: ../../:2 msgid "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: mouseleft" msgstr "" #: ../../:4 msgid "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: mouseright" msgstr "" #: ../../:6 msgid "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: mousemiddle" msgstr "" #: ../../:8 msgid "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" msgstr "" +#: ../../contributors_manual/krita_manual_conventions.rst:None +msgid "Horizontal Rulers" +msgstr "" + #: ../../contributors_manual/krita_manual_conventions.rst:0 msgid "" ".. image:: images/sample.png\n" " :alt: an image." msgstr "" -#: ../../contributors_manual/krita_manual_conventions.rst:None -msgid "Horizontal Rulers" -msgstr "" - #: ../../contributors_manual/krita_manual_conventions.rst:1 msgid "reStructuredText conventions for the Krita Manual" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:16 msgid "Mark-up conventions for the Krita Manual" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:18 msgid "" "This details the style conventions for using restructured text for the Krita " "Manual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:20 msgid "" "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):" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:23 msgid "" "`Primer `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "User Manual:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "" "`Quick Ref `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:25 msgid "" "`Text Cheatsheet `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:27 msgid "" "`Introduction `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:28 msgid "" "`Markup `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "Reference Documentation:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "" "`Directives `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:30 msgid "`Roles `_" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "Sphinx specific docs:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "" "`Sphinx' page on restructured text `_ -- This is useful for the specific " "sphinx directives and roles it uses to generate for example table of " "contents." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:34 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:36 msgid "Contents" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:39 msgid "Meta data" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:41 msgid "Each page should start with the following three things:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:44 msgid "" "This is a general description of the page. It will be converted to an html " "meta tag which will be used by search engines::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:46 msgid "" ".. meta::\n" " :description:\n" " Description." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:49 msgid "A meta description" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:52 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:54 msgid "" ".. metadata-placeholder\n" "\n" " :authors: - Author 1\n" " - Author 2\n" " :license: GNU free documentation license 1.3 or later." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:58 msgid "A list of authors and a license." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:61 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid "Indexing terms." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:63 msgid ".. index:: Keyword, Keyword with Spaces, ! Main Definition Keyword" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:66 msgid "" "This is so we can easily link to the page using ``:ref:`label_name```. Try " "to make this a nice variable name::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:68 msgid ".. _label_name:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:70 msgid "" "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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:71 msgid "A label." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:74 msgid "Headings" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:76 msgid "Headings will be done in the following order::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:78 msgid "" "############\n" "Part/Section\n" "############\n" "\n" "For pages that have a lot of subpages.\n" "\n" "=========\n" "Heading 1\n" "=========\n" "\n" "Start most manual pages with this.\n" "\n" "Heading 2\n" "---------\n" "\n" "Heading 3\n" "~~~~~~~~~\n" "\n" "Heading 4\n" "^^^^^^^^^\n" "\n" "Heading 5\n" "'''''''''\n" "\n" "Heading 6\n" "\"\"\"\"\"\"\"\"\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:105 msgid "" "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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:107 msgid "" "Sometimes you need to link to a subsection of a page, add a label above the " "heading in that case." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:109 msgid "" "Headers should not end with punctuation, as the header will be used as the " "link name when linking to a label." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:112 msgid "Linking" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:114 msgid "" "Linking is done with ``:ref:`label_name```. When you need an alternative " "link text, you use ``:ref:`actual text shown ```." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:116 msgid "" "Linking to external pages is done with ```url`_`` and ```link name " "`_``, which'll become `link name `_." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:118 msgid "" "`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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:121 msgid "Footnotes and further reading" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:123 msgid "" "Footnotes can be made in 3 ways, the most common one is with autonumbering, " "as per reference:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:125 msgid "" "[#]_ is a reference to footnote 1, and [#]_ is a reference to footnote 2." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:128 msgid "This is footnote 1." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:129 msgid "This is footnote 2." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:130 msgid "This is footnote 3." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:132 msgid "[#]_ is a reference to footnote 3." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:134 msgid "Here is a citation reference: [CIT2002]_ ." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:136 msgid "" "This is the citation. It's just like a footnote, except the label is " "textual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:139 msgid "Citation can also be referenced with ```citation `_``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:141 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:145 msgid "Images" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:147 msgid "Use the image directive for images without captions::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:149 msgid "" ".. image:: /images/sample.png\n" " :width: 800\n" " :align: center\n" " :alt: an image." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:154 msgid "And figure directives for images with captions::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:156 msgid "" ".. figure:: /images/sample.png\n" " :figwidth: 800\n" " :align: center\n" " :alt: an image.\n" "\n" " A caption -- notice how the first letter is aligned with the :figwidth: " "option." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:163 msgid "The latter gives:" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:170 msgid "" "A caption -- notice how the first letter of the caption in the directive is " "aligned with the :figwidth: option." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:172 msgid "" "Images should go into the ``/images`` folder. By using ``/images`` instead " "of ``images``, sphinx will know the filepath isn't relative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:175 msgid "In-text Markup" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:177 msgid "" "You can make text *emphasized* and **strong** with a single asterisk and " "double respectively::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:179 msgid "" "*emphasize*\n" "**strong**" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:182 msgid "You cannot do both ***emphasized and strong***, so take a pick." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:184 msgid "" "You can :sub:`subscript text` and :sup:`superscript text` by using ``:sub:" "`text``` and ``:sup:`text```" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:186 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:188 msgid "" ":menuselection:`Settings --> Configure Krita`\n" ":guilabel:`File`\n" ":kbd:`Ctrl + Z`\n" ":program:`Krita`" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:193 msgid "" "Avoid randomly bolding words. It does *not* make the text easier or " "friendlier to read." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:196 msgid "Substitution References" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:198 msgid "" "You can create a sort of shorthand for a piece of text or an image by doing::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:200 msgid ".. |shorthand| replace:: something or the other." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:202 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:204 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:206 msgid "" "For links, if you reuse the same link over and over, you can write something " "like the following at the end of the file::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:208 msgid "" ".. _bugzilla: https://bugs.kde.org/\n" ".. _Krita Manual: https://docs.krita.org/" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:211 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:214 msgid "Lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:217 msgid "Ordinated lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:219 msgid "Apple" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:220 msgid "Pear" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:221 msgid "Banana" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:223 msgid "Or..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:225 msgid "Table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:226 msgid "Chair" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:227 msgid "Wardrobe." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:229 msgid "Augustus" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:230 msgid "Nero" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:231 msgid "Caligula" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:232 msgid "Trajan" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:234 msgid "They can be defined as follows::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:236 msgid "" "1. Apple\n" "2. Pear\n" "3. Banana\n" "\n" "#. Apple\n" "#. Pear\n" "#. Banana\n" "\n" "A. Table\n" "B. Chair\n" "C. Wardrobe\n" "\n" "A. Table\n" "#. Chair\n" "#. Wardrobe\n" "\n" "I. Augustus\n" "#. Nero\n" "#. Caligula\n" "#. Trajan" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:258 msgid "Unordered lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:260 msgid "red" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:261 msgid "yellow" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:263 msgid "seagreen" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:264 msgid "verdigris" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:265 msgid "teal" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:266 msgid "viridian" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:268 msgid "dark emerald" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "green" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "emerald" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:269 msgid "light emerald" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:270 msgid "very light emerald." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:271 msgid "blue" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:273 msgid "Defined as such::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:275 msgid "" "- red\n" "- yellow\n" "- green\n" " - seagreen\n" " - verdigris\n" " - teal\n" " - viridian\n" " - emerald\n" " - dark emerald\n" " - light emerald\n" " - very light emerald.\n" "- blue" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:289 msgid "Definition Lists" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:291 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:293 msgid "Definition" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:294 #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Explanation." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Another option" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:299 msgid "You can make them like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:301 msgid "" "Definition\n" " Explanation.\n" "Another option\n" " Explanation." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:304 msgid "To make them." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:307 msgid "Tables" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Purpose" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Table type" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "listing shortcuts" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:312 msgid "Simple table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "lots of colspans" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:313 msgid "Grid table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "Simple but long" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:314 msgid "List Table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:317 msgid "Done as follows::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:319 msgid "" "================== ============\n" "Purpose Table type\n" "================== ============\n" "listing shortcuts Simple table\n" "lots of colspans Grid table\n" "Simple but long List Table\n" "================== ============\n" "\n" "+-----------------+------------+\n" "|Purpose |Table Type |\n" "+=================+============+\n" "|listing shortcuts|Simple table|\n" "+-----------------+------------+\n" "|lots of colspans |Grid table |\n" "+-----------------+------------+\n" "|Simple but long |List table |\n" "+-----------------+------------+\n" "\n" ".. list-table::\n" " :header-rows: 1\n" "\n" " - * Purpose\n" " * Table Type\n" " - * listing shortcuts\n" " * simple table\n" " - * lots of colspans\n" " * grid table\n" " - * simple but long\n" " * list table" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:349 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:352 msgid "Admonishments and asides" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:356 msgid "" "Admonishments are sort of like a separate section that the reader needs to " "pay attention to." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:358 msgid "" "Admonishments that can be used are the following (in order of seriousness):" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:362 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:366 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\"." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:370 msgid "Something that is important to note, but is not necessarily negative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:374 msgid "This is in general when something is negative." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:378 msgid "" "General attention grabber. Use this when the subject is more important than " "warning, but not as important that is could get a dataloss." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:382 msgid "" "This is for things that could cause dataloss, like forgetting to save, or " "that Python currently has no undo functionality." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:386 msgid "" "This should be for things that are dangerous for the computer in general, " "this includes things that can cause out of memory style freezes." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:390 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:392 msgid "Generic admonition that can have any text" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:394 msgid "Text." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:396 msgid "You can make it like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:398 msgid "" ".. admonition:: Generic admonition that can have any text\n" "\n" " Text." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:404 msgid "Sphinx also adds::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:406 msgid "" ".. seealso::\n" "\n" " Which is useful to collect external links and references." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:414 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:418 msgid "That said, horizontal rulers can be made with ``----``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:421 msgid "The rubric directive" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:422 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::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:424 msgid ".. rubric:: The rubric directive" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:428 msgid "So, when to use these?" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:429 msgid "" "Only use them when you think the subject is too minor to have a proper " "heading." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:431 msgid "Topic" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:432 msgid "" "When the text is separated from the flow, so it goes into a different " "subject than the text itself is naturally going to." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:433 msgid "Rubric" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:434 msgid "" "When the text isn't separated from the flow, but it does not need a header " "either." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:436 msgid "Admonishments" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:436 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." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:439 msgid "Code Snippets" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:441 msgid "``Inline code snippets`` are done with ````backticks````." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:443 msgid "" "Multi-line code snippets are done by ending the previous section with ``::" "``, which'll look like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:445 msgid "" "This is a paragraph, and we define a preformated snippet like so::\n" "\n" " Be sure to add a white space and a tab afterwards before starting the " "snippet." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:449 msgid "" "You can also use the ``.. code::`` directive. If you add the language name " "after it, it'll do the appropriate syntax highlighting::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:451 msgid "" ".. code:: python\n" "\n" " # Python comment\n" " def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:459 msgid "Becomes" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:468 msgid "" "# Python comment\n" "def my_function():\n" " alist = []\n" " alist.append(1)\n" " string = \"hello world\"" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:469 msgid "some more..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:483 msgid "" "// C++ comment\n" "int myFunction(int i) {\n" " i += 1;\n" "\n" " // Check if more than 12\n" " if (i>12) {\n" " i = 0;\n" " }\n" " return i;\n" "}" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:498 msgid "" "/* CSS comment */\n" "body {\n" " margin: 0 auto;\n" " /* is 800 still sensible? */\n" " max-width:800px;\n" " font-size:16px;\n" " color:#333;\n" " background-color: #eee;\n" " padding:1em;\n" " font-family:serif;\n" " line-height: 1.4;\n" "}" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:502 msgid "" "

this is " "a paragraph.

" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:504 msgid "Other preformatted text" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:507 msgid "One can" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:508 msgid "preformat" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:509 msgid "text by" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:510 msgid "prepending" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:511 msgid "each line" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:512 msgid "with a pipe" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:513 msgid "symbol" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:515 msgid "Like so::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:517 msgid "" "| One can\n" "| preformat\n" "| text by\n" "| prepending\n" "| each line\n" "| with a pipe\n" "| symbol" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:525 msgid "We don't actually use this anywhere in the manual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:528 msgid "Glossaries, Terms and Index" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:530 msgid "These are sphinx features." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:532 msgid "" "Index is used in the top section, right now only single index entries are " "used." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:534 msgid "" "Glossaries are used for some of the menu entry sections, but not all of them." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:537 msgid "Quotes" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:539 msgid "Quotes are done like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:541 msgid "" "I am not sure why you'd need quotes in a user manual...\n" "\n" "-- Wolthera" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:545 msgid "This becomes a blockquote." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:547 msgid "I am not sure why you'd need quotes in a user manual..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:551 msgid "" "We do actually use quotes in some places. Try to add a link to the name to " "define where it came from." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:552 msgid "Wolthera" msgstr "" diff --git a/locale/zh_TW/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po b/locale/zh_TW/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po index 654f8124f..39b95f295 100644 --- a/locale/zh_TW/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po +++ b/locale/zh_TW/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po @@ -1,1065 +1,1065 @@ # SOME DESCRIPTIVE TITLE. # 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 , YEAR. # msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-08-08 03:08+0200\n" +"POT-Creation-Date: 2019-08-10 03:13+0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: Chinese \n" "Language: zh\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=1; plural=0;\n" +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_matrix_profile.png" +msgstr "" + +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" +msgstr "" + #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group1.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group2.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group3.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_2_9_colormanagement_group4.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/dockers/LUT_Management_Docker.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR_1.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita_HDR2.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_webcomic.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_print.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/color_category/Krita-colormanaged-workflow_games.svg" msgstr "" -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_matrix_profile.png" -msgstr "" - -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/color_category/Kiki_cLUTprofiles.png" -msgstr "" - #: ../../general_concepts/colors/color_managed_workflow.rst:1 msgid "How a color managed workflow works." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "Color" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "Color Management" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "ICC Profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:12 msgid "OCIO" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:17 msgid "Color Managed Workflow" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:19 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:22 msgid "Basic Info" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:24 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:26 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:29 msgid "What is the problem?" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:31 msgid "" "To explain the point of color management, you'd first need to learn which " "problem color management tries to solve." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:33 msgid "Let us imagine a kinder garden:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:35 msgid "" "The class of 28 children is subdivided in groups of 7. Each group has its " "own table." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:37 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:40 msgid "The following results come from painting:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:42 msgid "" "Even though all groups had the same assignment, each group's result looks " "different." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:49 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:56 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:64 msgid "" "Group 3 had vermillion red, citron yellow, emerald green and cerulean blue. " "They didn't mix their green, and thus ended up with a purer color." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:71 msgid "" "Finally, group 4 has vermillion red, citron yellow and cerulean blue. Their " "colors probably look like what you imagined." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:73 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!" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:75 msgid "For this purpose, we invented color management." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:78 msgid "What is color management?" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:80 msgid "" "Color management is, dryly put, a set of systems that tries to have the same " "color translate properly between color devices." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:82 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:84 msgid "" "From XYZ it can then be translated back into another device space, such as " "RGB (for screens), or CMYK (for printers)." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:86 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:88 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:90 msgid "Within both we can identify the following color spaces:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:93 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 " "`." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:94 msgid "Device spaces" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:96 msgid "Working spaces" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:97 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:99 msgid "Aesthetic or Look spaces" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:99 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:102 msgid "Color managed workflow" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:104 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:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:110 msgid ".. image:: images/color_category/Krita-colormanaged-workflow_text.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:110 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:112 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:114 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:116 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:118 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:120 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:122 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:124 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:127 msgid "So what does this mean?" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:133 msgid "" ".. image:: images/color_category/Krita-colormanaged-workflow_krita_text.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:133 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:135 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*." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:137 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:139 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:141 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:143 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.)" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:148 msgid "ICC profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:150 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:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:153 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:159 msgid "Matrix Shaper profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:159 msgid "" "Matrix shaper profiles have a few parameters that describe the color space " "which are then interpolated between, this requires a lot of maths." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:162 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:168 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:169 msgid "cLUT profiles" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:171 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:174 msgid "Perceptual" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:174 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:177 msgid "Absolute Colorimetric" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:177 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:180 msgid "Relative Colorimetric" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:180 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:183 msgid "Saturation" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:183 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:185 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:188 msgid "LUT docker and HDR imaging" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:196 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:198 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:200 msgid "" "Component, exposure, gamma, whitepoint and blackpoint are knobs which allows " "you to modify the display filter." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:208 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:210 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:212 msgid "" "Black similarly, is brighter on a LCD display than a LED one, and " "incomparable with the black of a carefully sealed room." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:214 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:216 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:224 msgid "" "So, for example, we can choose to scale whiter-than-screen-white to our " "screen-white so we can see the contrasts there." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:226 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:228 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:230 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:232 msgid "" "Another example is to carefully watch the gradients in a certain section." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:234 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:237 msgid "In summary" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:239 msgid "Krita has two modes of color management:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:241 msgid "" "ICC works in terms of spaces relative to the CIEXYZ space, and requires an " "ICC profile." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:242 msgid "OCIO works in terms of interpretation, and makes use of LUTs." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:243 msgid "both can be made with a colorimeter." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:244 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:245 msgid "" "Set up your screen profiles under :menuselection:`Settings --> Configure " "Krita --> Color management`." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:246 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:247 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:249 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:251 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!" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:256 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!" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:260 msgid "" "No amount of color management in the world can make the image on your screen " "and the image out of the printer have 100% the same color." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:263 msgid "Exporting" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:265 msgid "" "When you have finished your image and are ready to export it, you can modify " "the color space to optimize it:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:267 msgid "If you are preparing an image for the web:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:269 msgid "" "If you use 16bit color depth or higher, convert the image to 8bit color " "depth. This will make the image much smaller." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:271 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:273 msgid "If it's a gray-scale image, convert it to gray-scale." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:274 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:279 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 " "`_, save your PNG, JPG or TIFF without an embedded profile to work " "around this." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:281 msgid "If you are preparing for print:" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:283 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:284 msgid "" "Check with the printer what kind of image they expect. Maybe they expect " "sRGB color space, or perhaps they have their own profile." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:287 msgid "Interaction with other applications" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:290 msgid "Blender" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:292 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:294 msgid "" "Blender's OCIO config is under ``/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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:298 msgid "Windows Photo Viewer" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:300 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:303 msgid "Example workflows" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:305 msgid "" "Here are some example workflows to get a feeling of how your color " "management workflow may look like." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:307 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'." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:310 msgid "Webcomic" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:317 #: ../../general_concepts/colors/color_managed_workflow.rst:339 #: ../../general_concepts/colors/color_managed_workflow.rst:357 msgid "Input" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:318 #: ../../general_concepts/colors/color_managed_workflow.rst:340 #: ../../general_concepts/colors/color_managed_workflow.rst:358 msgid "Your screen profile. (You pick colors via your screen)" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:319 #: ../../general_concepts/colors/color_managed_workflow.rst:341 #: ../../general_concepts/colors/color_managed_workflow.rst:359 msgid "Workingspace" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:320 msgid "" "sRGB (the default screen profile) or any larger profile if you can spare the " "bit depth and like working in them." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:322 #: ../../general_concepts/colors/color_managed_workflow.rst:344 #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "Output" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:322 msgid "" "sRGB, ICC version 2, sRGB TRC for the internet, and a specialized CMYK " "profile from the printing house for the printed images." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:324 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:326 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:328 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:330 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:333 msgid "Print" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:342 msgid "sRGB or Rec. 2020 if you can afford the bit-depth being 16bit." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:344 msgid "" "Specialized CMYK profile from the printing house for the printed images." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:346 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:348 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:351 msgid "Games" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:360 msgid "sRGB or grayscale linear for roughness and specular maps." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:362 msgid "" "This one is tricky, but in the end it'll be sRGB for the regular player." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:364 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:366 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:368 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:370 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)." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:374 msgid "" "`Visualizing the XYZ color space `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:375 msgid "" "`Basics of gamma correction `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:376 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 `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:377 msgid "" "`2D examples of the effect of gamma-encoding on color maths `_." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:378 msgid "" "`Basic overview of color management from ArgyllCMS manual `_." msgstr ""