diff --git a/locale/ca/LC_MESSAGES/reference_manual/blending_modes/arithmetic.po b/locale/ca/LC_MESSAGES/reference_manual/blending_modes/arithmetic.po index 3dc63e44c..076c4ebc7 100644 --- a/locale/ca/LC_MESSAGES/reference_manual/blending_modes/arithmetic.po +++ b/locale/ca/LC_MESSAGES/reference_manual/blending_modes/arithmetic.po @@ -1,368 +1,368 @@ # Translation of docs_krita_org_reference_manual___blending_modes___arithmetic.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: reference_manual\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-04-17 03:39+0200\n" "PO-Revision-Date: 2019-04-22 22:26+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 18.12.3\n" #: ../../reference_manual/blending_modes/arithmetic.rst:1 msgid "" "Page about the arithmetic blending modes in Krita: Addition, Divide, Inverse " "Subtract, Multiply and Subtract." msgstr "" "Pàgina sobre els modes de barreja aritmètica al Krita: Addició, Divideix, " "Resta inversa, Multiplica i Sostreu." #: ../../reference_manual/blending_modes/arithmetic.rst:14 msgid "Arithmetic" msgstr "Aritmètic" #: ../../reference_manual/blending_modes/arithmetic.rst:16 msgid "These blending modes are based on simple maths." msgstr "Aquests modes de barreja es basen en matemàtiques senzilles." #: ../../reference_manual/blending_modes/arithmetic.rst:22 msgid "Addition" msgstr "Addició" #: ../../reference_manual/blending_modes/arithmetic.rst:24 msgid "Adds the numerical values of two colors together:" msgstr "Afegeix els valors numèrics de dos colors:" #: ../../reference_manual/blending_modes/arithmetic.rst:26 msgid "Yellow(1, 1, 0) + Blue(0, 0, 1) = White(1, 1, 1)" msgstr "Groc (1, 1, 0) + Blau (0, 0, 1) = Blanc (1, 1, 1)" #: ../../reference_manual/blending_modes/arithmetic.rst:28 msgid "" "Darker Gray(0.4, 0.4, 0.4) + Lighter Gray(0.5, 0.5, 0.5) = Even Lighter Gray " "(0.9, 0.9, 0.9)" msgstr "" "Gris fosc (0,4, 0,4, 0,4) + Gris clar (0,5, 0,5, 0,5) = Gris encara més clar " "(0,9, 0,9, 0,9)" #: ../../reference_manual/blending_modes/arithmetic.rst:33 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Addition_Gray_0.4_and_Gray_0.5_n.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Addition_Gray_0.4_and_Gray_0.5_n.png" #: ../../reference_manual/blending_modes/arithmetic.rst:33 #: ../../reference_manual/blending_modes/arithmetic.rst:40 #: ../../reference_manual/blending_modes/arithmetic.rst:47 #: ../../reference_manual/blending_modes/arithmetic.rst:54 msgid "Left: **Normal**. Right: **Addition**." msgstr "Esquerra: **Normal**. Dreta: **Addició**." #: ../../reference_manual/blending_modes/arithmetic.rst:35 msgid "" "Light Blue(0.1608, 0.6274, 0.8274) + Orange(1, 0.5961, 0.0706) = (1.1608, " "1.2235, 0.8980) → Very Light Yellow(1, 1, 0.8980)" msgstr "" "Blau clar (0,1608, 0,6274, 0,8274) + Taronja (1, 0,5961, 0,0706) = (1,1608, " "1,2235, 0,8980) → Groc molt clar (1, 1, 0,8980)" #: ../../reference_manual/blending_modes/arithmetic.rst:40 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Addition_Light_blue_and_Orange.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Addition_Light_blue_and_Orange.png" #: ../../reference_manual/blending_modes/arithmetic.rst:42 msgid "Red(1, 0, 0) + Gray(0.5, 0.5, 0.5) = Pink(1, 0.5, 0.5)" msgstr "Vermell (1, 0, 0) + Gris (0,5, 0,5, 0,5) = Rosa (1, 0,5, 0,5)" #: ../../reference_manual/blending_modes/arithmetic.rst:47 msgid "" ".. image:: images/blending_modes/Blending_modes_Addition_Red_plus_gray.png" msgstr "" ".. image:: images/blending_modes/Blending_modes_Addition_Red_plus_gray.png" #: ../../reference_manual/blending_modes/arithmetic.rst:49 msgid "" "When the result of the addition is more than 1, white is the color " "displayed. Therefore, white plus any other color results in white. On the " "other hand, black plus any other color results in the added color." msgstr "" "Quan el resultat de l'addició sigui més que 1, es mostrarà el color blanc. " "Per tant, el blanc més qualsevol altre color, resultarà en blanc. D'altra " "banda, el negre més qualsevol altre color, resultarà en el color afegit." #: ../../reference_manual/blending_modes/arithmetic.rst:54 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Addition_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Addition_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/arithmetic.rst:59 msgid "Divide" msgstr "Divideix" #: ../../reference_manual/blending_modes/arithmetic.rst:61 msgid "Divides the numerical value from the lower color by the upper color." msgstr "Divideix el valor numèric del color inferior pel del color superior." #: ../../reference_manual/blending_modes/arithmetic.rst:63 msgid "Red(1, 0, 0) / Gray(0.5, 0.5, 0.5) = (2, 0, 0) → Red(1, 0, 0)" msgstr "" "Vermell (1, 0, 0) / Gris (0.5, 0.5, 0.5) = (2, 0, 0) → Vermell (1, 0, 0)" #: ../../reference_manual/blending_modes/arithmetic.rst:65 msgid "" "Darker Gray(0.4, 0.4, 0.4) / Lighter Gray(0.5, 0.5, 0.5) = Even Lighter Gray " "(0.8, 0.8, 0.8)" msgstr "" "Gris fosc (0,4, 0,4, 0,4) / Gris clar (0,5, 0,5, 0,5) = Gris encara més clar " "(0,8, 0,8, 0,8)" #: ../../reference_manual/blending_modes/arithmetic.rst:70 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Divide_Gray_0.4_and_Gray_0.5_n.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Divide_Gray_0.4_and_Gray_0.5_n.png" #: ../../reference_manual/blending_modes/arithmetic.rst:70 #: ../../reference_manual/blending_modes/arithmetic.rst:77 #: ../../reference_manual/blending_modes/arithmetic.rst:82 msgid "Left: **Normal**. Right: **Divide**." msgstr "Esquerra: **Normal**. Dreta: **Divideix**." #: ../../reference_manual/blending_modes/arithmetic.rst:72 msgid "" "Light Blue(0.1608, 0.6274, 0.8274) / Orange(1, 0.5961, 0.0706) = (0.1608, " "1.0525, 11.7195) → Aqua(0.1608, 1, 1)" msgstr "" "Blau clar (0,1608, 0,6274, 0,8274) / Taronja (1, 0,5961, 0,0706) = (0,1608, " "1,0525, 11,7195) → Aigua (0,1608, 1, 1)" #: ../../reference_manual/blending_modes/arithmetic.rst:77 msgid "" ".. image:: images/blending_modes/Blending_modes_Divide_Light_blue_and_Orange." "png" msgstr "" ".. image:: images/blending_modes/Blending_modes_Divide_Light_blue_and_Orange." "png" #: ../../reference_manual/blending_modes/arithmetic.rst:82 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Divide_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Divide_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/arithmetic.rst:87 msgid "Inverse Subtract" msgstr "Resta inversa" #: ../../reference_manual/blending_modes/arithmetic.rst:89 msgid "" "This inverts the lower layer before subtracting it from the upper layer." msgstr "" "Aquesta inverteix la capa inferior abans de restar-la de la capa superior." #: ../../reference_manual/blending_modes/arithmetic.rst:91 msgid "" "Lighter Gray(0.5, 0.5, 0.5)_(1_Darker Gray(0.4, 0.4, 0.4)) = (-0.1, -0.1, " "-0.1) → Black(0, 0, 0)" msgstr "" "Gris clar (0,5, 0,5, 0,5)_(1_Gris fosc (0,4, 0,4, 0,4)) = (-0,1, -0,1, -0,1) " "→ Negre (0, 0, 0)" #: ../../reference_manual/blending_modes/arithmetic.rst:96 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Inverse_Subtract_Gray_0.4_and_Gray_0.5_n.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Inverse_Subtract_Gray_0.4_and_Gray_0.5_n.png" #: ../../reference_manual/blending_modes/arithmetic.rst:96 #: ../../reference_manual/blending_modes/arithmetic.rst:103 #: ../../reference_manual/blending_modes/arithmetic.rst:108 msgid "Left: **Normal**. Right: **Inverse Subtract**." msgstr "Esquerra: **Normal**. Dreta: **Resta inversa**." #: ../../reference_manual/blending_modes/arithmetic.rst:98 msgid "" "Orange(1, 0.5961, 0.0706)_(1_Light Blue(0.1608, 0.6274, 0.8274)) = (0.1608, " "0.2235, -0.102) → Dark Green(0.1608, 0.2235, 0)" msgstr "" "Taronja (1, 0,5961, 0,0706)_(1_Blau clar (0,1608, 0,6274, 0,8274)) = " "(0,1608, 0,2235, -0,102) → Verd fosc (0,1608, 0,2235, 0)" #: ../../reference_manual/blending_modes/arithmetic.rst:103 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Inverse_Subtract_Light_blue_and_Orange.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Inverse_Subtract_Light_blue_and_Orange.png" #: ../../reference_manual/blending_modes/arithmetic.rst:108 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Inverse_Subtract_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Inverse_Subtract_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/arithmetic.rst:113 msgid "Multiply" msgstr "Multiplica" #: ../../reference_manual/blending_modes/arithmetic.rst:115 msgid "" "Multiplies the two colors with each other, but does not go beyond the upper " "limit." msgstr "" "Multiplica els dos colors entre si, però no va més enllà del límit superior." #: ../../reference_manual/blending_modes/arithmetic.rst:117 msgid "" "This is often used to color in a black and white lineart. One puts the black " "and white lineart on top, and sets the layer to 'Multiply', and then draw in " "color on a layer beneath. Multiply will all the color to go through." msgstr "" -"S'utilitza sovint per aplicar colors en una línia artística en blanc i negre. " -"Es col·loca la línia artística en blanc i negre a la part superior, i " +"S'utilitza sovint per aplicar colors en una línia artística en blanc i " +"negre. Es col·loca la línia artística en blanc i negre a la part superior, i " "estableix la capa a «Multiplica», i després es dibuixa en color en una capa " "a sota. La multiplicació permetrà que tots els colors passin a través seu." #: ../../reference_manual/blending_modes/arithmetic.rst:120 msgid "White(1,1,1) x White(1, 1, 1) = White(1, 1, 1)" msgstr "Blanc (1,1,1) x Blanc (1, 1, 1) = Blanc (1, 1, 1)" #: ../../reference_manual/blending_modes/arithmetic.rst:122 msgid "White(1, 1, 1) x Gray(0.5, 0.5, 0.5) = Gray(0.5, 0.5, 0.5)" msgstr "Blanc (1, 1, 1) x Gris (0,5, 0,5, 0,5) = Gris (0,5, 0,5, 0,5)" #: ../../reference_manual/blending_modes/arithmetic.rst:124 msgid "" "Darker Gray(0.4, 0.4, 0.4) x Lighter Gray(0.5, 0.5, 0.5) = Even Darker Gray " "(0.2, 0.2, 0.2)" msgstr "" "Gris fosc (0,4, 0,4, 0,4) x Gris clar (0,5, 0,5, 0,5) = Gris encara més clar " "(0,2, 0,2, 0,2)" #: ../../reference_manual/blending_modes/arithmetic.rst:129 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Multiply_Gray_0.4_and_Gray_0.5_n.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Multiply_Gray_0.4_and_Gray_0.5_n.png" #: ../../reference_manual/blending_modes/arithmetic.rst:129 #: ../../reference_manual/blending_modes/arithmetic.rst:136 #: ../../reference_manual/blending_modes/arithmetic.rst:141 msgid "Left: **Normal**. Right: **Multiply**." msgstr "Esquerra: **Normal**. Dreta: **Multiplica**." #: ../../reference_manual/blending_modes/arithmetic.rst:131 msgid "" "Light Blue(0.1608, 0.6274, 0.8274) x Orange(1, 0.5961, 0.0706) = " "Green(0.1608, 0.3740, 0.0584)" msgstr "" "Blau clar (0,1608, 0,6274, 0,8274) x Taronja (1, 0,5961, 0,0706) = Verd " "(0,1608, 0,3740, 0,0584)" #: ../../reference_manual/blending_modes/arithmetic.rst:136 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Multiply_Light_blue_and_Orange.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Multiply_Light_blue_and_Orange.png" #: ../../reference_manual/blending_modes/arithmetic.rst:141 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Multiply_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Multiply_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/arithmetic.rst:146 msgid "Subtract" msgstr "Sostreu" #: ../../reference_manual/blending_modes/arithmetic.rst:148 msgid "Subtracts the top layer from the bottom layer." msgstr "Resta la capa superior de la capa inferior." #: ../../reference_manual/blending_modes/arithmetic.rst:150 msgid "White(1, 1, 1)_White(1, 1, 1) = Black(0, 0, 0)" msgstr "Blanc (1, 1, 1)_Blanc (1, 1, 1) = Negre (0, 0, 0)" #: ../../reference_manual/blending_modes/arithmetic.rst:152 msgid "White(1, 1, 1)_Gray(0.5, 0.5, 0.5) = Gray(0.5, 0.5, 0.5)" msgstr "Blanc (1, 1, 1)_Gris (0,5, 0,5, 0,5) = Gris (0,5, 0,5, 0,5)" #: ../../reference_manual/blending_modes/arithmetic.rst:154 msgid "" "Darker Gray(0.4, 0.4, 0.4)_Lighter Gray(0.5, 0.5, 0.5) = (-0.1, -0.1, -0.1) " "→ Black(0, 0, 0)" msgstr "" "Gris fosc (0,4, 0,4, 0,4)_Gris clar (0,5, 0,5, 0,5) = (-0,1, -0,1, -0,1) " "→ Negre (0, 0, 0)" #: ../../reference_manual/blending_modes/arithmetic.rst:159 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Subtract_Gray_0.4_and_Gray_0.5_n.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Subtract_Gray_0.4_and_Gray_0.5_n.png" #: ../../reference_manual/blending_modes/arithmetic.rst:159 #: ../../reference_manual/blending_modes/arithmetic.rst:166 #: ../../reference_manual/blending_modes/arithmetic.rst:171 msgid "Left: **Normal**. Right: **Subtract**." msgstr "Esquerra: **Normal**. Dreta: **Sostreu**." #: ../../reference_manual/blending_modes/arithmetic.rst:161 msgid "" "Light Blue(0.1608, 0.6274, 0.8274) - Orange(1, 0.5961, 0.0706) = (-0.8392, " "0.0313, 0.7568) → Blue(0, 0.0313, 0.7568)" msgstr "" "Blau clar (0,1608, 0,6274, 0,8274) - Taronja (1, 0,5961, 0,0706) = (-0,8392, " "0,0313, 0,7568) → Blau (0, 0,0313, 0,7568)" #: ../../reference_manual/blending_modes/arithmetic.rst:166 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Subtract_Light_blue_and_Orange.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Subtract_Light_blue_and_Orange.png" #: ../../reference_manual/blending_modes/arithmetic.rst:171 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Subtract_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Subtract_Sample_image_with_dots.png" diff --git a/locale/ca/LC_MESSAGES/reference_manual/blending_modes/darken.po b/locale/ca/LC_MESSAGES/reference_manual/blending_modes/darken.po index 172a5fe64..3388977ad 100644 --- a/locale/ca/LC_MESSAGES/reference_manual/blending_modes/darken.po +++ b/locale/ca/LC_MESSAGES/reference_manual/blending_modes/darken.po @@ -1,289 +1,289 @@ # Translation of docs_krita_org_reference_manual___blending_modes___darken.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: reference_manual\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-19 03:36+0100\n" "PO-Revision-Date: 2019-04-22 22:25+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 18.12.3\n" #: ../../reference_manual/blending_modes/darken.rst:1 msgid "" "Page about the darken blending modes in Krita: Darken, Burn, Darker Color, " "Gamma Dark and Linear Burn." msgstr "" "Pàgina sobre els modes de barreja més foscos al Krita: Fosca, Cremat, Color " "més fosc, Gamma fosca i Cremat lineal." #: ../../reference_manual/blending_modes/darken.rst:15 #: ../../reference_manual/blending_modes/darken.rst:52 msgid "Darken" msgstr "Fosca" #: ../../reference_manual/blending_modes/darken.rst:22 msgid "Burn" msgstr "Cremat" #: ../../reference_manual/blending_modes/darken.rst:24 msgid "A variation on Divide, sometimes called 'Color Burn' in some programs." msgstr "" "Una variació de Divideix, de vegades anomenada «Cremat del color» en alguns " "programes." #: ../../reference_manual/blending_modes/darken.rst:26 msgid "" "This inverts the bottom layer, then divides it by the top layer, and inverts " "the result. This results in a darkened effect that takes the colors of the " "lower layer into account, similar to the burn technique used in traditional " "darkroom photography." msgstr "" "Això inverteix la capa inferior, després la divideix per la capa superior i " "inverteix el resultat. Això dóna com a resultat un efecte fosc que té en " "compte els colors de la capa inferior, similar a la tècnica de cremat " "emprada en la cambra fosca de la fotografia tradicional." #: ../../reference_manual/blending_modes/darken.rst:29 msgid "" "1_{[1_Darker Gray(0.4, 0.4, 0.4)] / Lighter Gray(0.5, 0.5, 0.5)} = (-0.2, " "-0.2, -0.2) → Black(0, 0, 0)" msgstr "" "1_{[1_Gris fosc (0,4, 0,4, 0,4)] / Gris clar (0,5, 0,5, 0,5)} = (-0,2, -0,2, " "-0,2) → Negre (0, 0, 0)" #: ../../reference_manual/blending_modes/darken.rst:34 msgid "" ".. image:: images/blending_modes/Blending_modes_Burn_Gray_0.4_and_Gray_0.5_n." "png" msgstr "" ".. image:: images/blending_modes/Blending_modes_Burn_Gray_0.4_and_Gray_0.5_n." "png" #: ../../reference_manual/blending_modes/darken.rst:34 #: ../../reference_manual/blending_modes/darken.rst:41 #: ../../reference_manual/blending_modes/darken.rst:46 msgid "Left: **Normal**. Right: **Burn**." msgstr "Esquerra: **Normal**. Dreta: **Cremat**." #: ../../reference_manual/blending_modes/darken.rst:36 msgid "" "1_{[1_Light Blue(0.1608, 0.6274, 0.8274)] / Orange(1, 0.5961, 0.0706)} = " "(0.1608, 0.3749, -1.4448) → Green(0.1608, 0.3749, 0)" msgstr "" "1_{[1_Blau clar (0,1608, 0,6274, 0,8274)] / Taronja (1, 0,5961, 0,0706)} = " "(0,1608, 0.3749, -1,4448) → Verd (0,1608, 0,3749, 0)" #: ../../reference_manual/blending_modes/darken.rst:41 msgid "" ".. image:: images/blending_modes/Blending_modes_Burn_Light_blue_and_Orange." "png" msgstr "" ".. image:: images/blending_modes/Blending_modes_Burn_Light_blue_and_Orange." "png" #: ../../reference_manual/blending_modes/darken.rst:46 msgid "" ".. image:: images/blending_modes/Blending_modes_Burn_Sample_image_with_dots." "png" msgstr "" ".. image:: images/blending_modes/Blending_modes_Burn_Sample_image_with_dots." "png" #: ../../reference_manual/blending_modes/darken.rst:54 msgid "" "With the darken, the upper layer's colors are checked for their lightness. " "Only if they are darker than the underlying color on the lower layer, will " "they be visible." msgstr "" "Amb l'enfosquiment, els colors de la capa superior es verifiquen per la seva " "claredat. Només seran visibles si són més foscos que el color subjacent a la " "capa inferior." #: ../../reference_manual/blending_modes/darken.rst:56 msgid "" "Is Lighter Gray(0.5, 0.5, 0.5) darker than Darker Gray(0.4, 0.4, 0.4)? = " "(no, no, no) → Darker Gray(0.4, 0.4, 0.4)" msgstr "" "És el gris clar (0,5, 0,5, 0,5) més fosc que el gris fosc (0,4, 0,4, 0,4)? = " "(no, no, no) → Gris fosc (0,4, 0,4, 0,4)" #: ../../reference_manual/blending_modes/darken.rst:61 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Darken_Gray_0.4_and_Gray_0.5_n.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Darken_Gray_0.4_and_Gray_0.5_n.png" #: ../../reference_manual/blending_modes/darken.rst:61 #: ../../reference_manual/blending_modes/darken.rst:68 #: ../../reference_manual/blending_modes/darken.rst:73 msgid "Left: **Normal**. Right: **Darken**." msgstr "Esquerra: **Normal**. Dreta: **Fosca**." #: ../../reference_manual/blending_modes/darken.rst:63 msgid "" "Is Orange(1, 0.5961, 0.0706) darker than Light Blue(0.1608, 0.6274, 0.8274)? " "= (no, yes, yes) → Green(0.1608, 0.5961, 0.0706)" msgstr "" "És el taronja (1, 0,5961, 0,0706) més fosc que el blau clar (0,1608, 0,6274, " "0,8274)? = (no, sí, sí) → Verd (0,1608, 0,5961, 0,0706)" #: ../../reference_manual/blending_modes/darken.rst:68 msgid "" ".. image:: images/blending_modes/Blending_modes_Darken_Light_blue_and_Orange." "png" msgstr "" ".. image:: images/blending_modes/Blending_modes_Darken_Light_blue_and_Orange." "png" #: ../../reference_manual/blending_modes/darken.rst:73 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Darken_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Darken_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/darken.rst:79 msgid "Darker Color" msgstr "Color més fosc" #: ../../reference_manual/blending_modes/darken.rst:84 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Darker_Color_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Darker_Color_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/darken.rst:84 msgid "Left: **Normal**. Right: **Darker Color**." msgstr "Esquerra: **Normal**. Dreta: **Color més fosc**." #: ../../reference_manual/blending_modes/darken.rst:90 msgid "Gamma Dark" msgstr "Gamma fosca" #: ../../reference_manual/blending_modes/darken.rst:92 msgid "" "Divides 1 by the upper layer, and calculates the end result using that as " "the power of the lower layer." msgstr "" -"Divideix 1 per la capa superior i calcula el resultat final utilitzant-lo com " -"la potència de la capa inferior." +"Divideix 1 per la capa superior i calcula el resultat final utilitzant-lo " +"com la potència de la capa inferior." #: ../../reference_manual/blending_modes/darken.rst:94 msgid "" "Darker Gray(0.4, 0.4, 0.4)^[1 / Lighter Gray(0.5, 0.5, 0.5)] = Even Darker " "Gray(0.1600, 0.1600, 0.1600)" msgstr "" "Gris fosc (0,4, 0,4, 0,4)^[1 / Gris clar (0,5, 0,5, 0,5)] = Gris encara més " "fosc (0,1600, 0,1600, 0,1600)" #: ../../reference_manual/blending_modes/darken.rst:99 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Gamma_Dark_Gray_0.4_and_Gray_0.5_n.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Gamma_Dark_Gray_0.4_and_Gray_0.5_n.png" #: ../../reference_manual/blending_modes/darken.rst:99 #: ../../reference_manual/blending_modes/darken.rst:106 #: ../../reference_manual/blending_modes/darken.rst:111 msgid "Left: **Normal**. Right: **Gamma Dark**." msgstr "Esquerra: **Normal**. Dreta: **Gamma fosca**." #: ../../reference_manual/blending_modes/darken.rst:101 msgid "" "Light Blue(0.1608, 0.6274, 0.8274)^[1 / Orange(1, 0.5961, 0.0706)] = " "Green(0.1608, 0.4575, 0.0683)" msgstr "" "Blau clar (0,1608, 0,6274, 0,8274)^[1 / Taronja (1, 0,5961, 0,0706)] = Verd " "(0,1608, 0,4575, 0,0683)" #: ../../reference_manual/blending_modes/darken.rst:106 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Gamma_Dark_Light_blue_and_Orange.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Gamma_Dark_Light_blue_and_Orange.png" #: ../../reference_manual/blending_modes/darken.rst:111 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Gamma_Dark_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Gamma_Dark_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/darken.rst:117 msgid "Linear Burn" msgstr "Cremat lineal" #: ../../reference_manual/blending_modes/darken.rst:119 msgid "" "Adds the values of the two layers together and then subtracts 1. Seems to " "produce the same result as :ref:`bm_inverse_subtract`." msgstr "" "Afegeix els valors de les dues capes i després resta 1. Sembla que produeix " "el mateix resultat que :ref:`bm_inverse_subtract`." #: ../../reference_manual/blending_modes/darken.rst:121 msgid "" "[Darker Gray(0.4, 0.4, 0.4) + Lighter Gray(0.5, 0.5, 0.5)]_1 = (-0.1000, " "-0.1000, -0.1000) → Black(0, 0, 0)" msgstr "" "[Gris fosc (0,4, 0,4, 0,4) + Gris clar (0,5, 0,5, 0,5)]_1 = (-0,1000, " "-0,1000, -0,1000) → Negre (0, 0, 0)" #: ../../reference_manual/blending_modes/darken.rst:126 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Linear_Burn_Gray_0.4_and_Gray_0.5.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Linear_Burn_Gray_0.4_and_Gray_0.5.png" #: ../../reference_manual/blending_modes/darken.rst:126 #: ../../reference_manual/blending_modes/darken.rst:133 #: ../../reference_manual/blending_modes/darken.rst:138 msgid "Left: **Normal**. Right: **Linear Burn**." msgstr "Esquerra: **Normal**. Dreta: **Cremat lineal**." #: ../../reference_manual/blending_modes/darken.rst:128 msgid "" "[Light Blue(0.1608, 0.6274, 0.8274) + Orange(1, 0.5961, 0.0706)]_1 = " "(0.1608, 0.2235, -0.1020) → Dark Green(0.1608, 0.2235, 0)" msgstr "" "[Blau clar (0,1608, 0,6274, 0,8274) + Taronja (1, 0,5961, 0,0706)]_1 = " "(0,1608, 0,2235, -0,1020) → Verd fosc (0,1608, 0,2235, 0)" #: ../../reference_manual/blending_modes/darken.rst:133 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Linear_Burn_Light_blue_and_Orange.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Linear_Burn_Light_blue_and_Orange.png" #: ../../reference_manual/blending_modes/darken.rst:138 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Linear_Burn_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Linear_Burn_Sample_image_with_dots.png" diff --git a/locale/ca/LC_MESSAGES/reference_manual/blending_modes/hsx.po b/locale/ca/LC_MESSAGES/reference_manual/blending_modes/hsx.po index fcde1f948..f76c32ce6 100644 --- a/locale/ca/LC_MESSAGES/reference_manual/blending_modes/hsx.po +++ b/locale/ca/LC_MESSAGES/reference_manual/blending_modes/hsx.po @@ -1,721 +1,722 @@ # Translation of docs_krita_org_reference_manual___blending_modes___hsx.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: reference_manual\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-04-17 03:39+0200\n" "PO-Revision-Date: 2019-04-22 22:27+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 18.12.3\n" #: ../../reference_manual/blending_modes/hsx.rst:1 msgid "" "Page about the HSX blending modes in Krita, amongst which Hue, Color, " "Luminosity and Saturation." msgstr "" "Pàgina sobre els modes de barreja HSX al Krita, entre els quals es troba To, " "Color, Lluminositat i Saturació." #: ../../reference_manual/blending_modes/hsx.rst:15 msgid "HSX" msgstr "HSX" #: ../../reference_manual/blending_modes/hsx.rst:17 msgid "" "Krita has four different HSX coordinate systems. The difference between them " "is how they handle tone." msgstr "" -"El Krita té quatre sistemes de coordenades HSX diferents. La diferència entre " -"ells és com manegen el to." +"El Krita té quatre sistemes de coordenades HSX diferents. La diferència " +"entre ells és com manegen el to." #: ../../reference_manual/blending_modes/hsx.rst:20 msgid "HSI" msgstr "HSI" #: ../../reference_manual/blending_modes/hsx.rst:22 msgid "" "HSI is a color coordinate system, using Hue, Saturation and Intensity to " "categorize a color. Hue is roughly the wavelength, whether the color is red, " "yellow, green, cyan, blue or purple. It is measure in 360°, with 0 being " "red. Saturation is the measurement of how close a color is to gray. " "Intensity, in this case is the tone of the color. What makes intensity " "special is that it recognizes yellow (rgb:1,1,0) having a higher combined " "rgb value than blue (rgb:0,0,1). This is a non-linear tone dimension, which " "means it's gamma-corrected." msgstr "" "El HSI és un sistema de coordenades del color, que utilitza el To, Saturació " "i Intensitat per a categoritzar un color. El to és aproximadament la " "longitud d'ona, si el color és vermell, groc, verd, cian, blau o porpra. Es " "mesura en 360°, amb 0 de color vermell. La saturació és la mesura de la " "proximitat del color gris. La intensitat, en aquest cas és el to del color. " "El que fa que la intensitat sigui especial és que reconeix el groc " "(rgb:1,1,0) que té un valor RGB combinat més gran que el blau (rgb:0,0,1). " "Aquesta és una dimensió no lineal del to, el qual vol dir que es corregeix " "la gamma." #: ../../reference_manual/blending_modes/hsx.rst:28 msgid "HSL" msgstr "HSL" #: ../../reference_manual/blending_modes/hsx.rst:30 msgid "" "HSL is also a color coordinate system. It describes colors in Hue, " "Saturation and Lightness. Lightness specifically puts both yellow " "(rgb:1,1,0), blue (rgb:0,0,1) and middle gray (rgb:0.5,0.5,0.5) at the same " "lightness (0.5)." msgstr "" -"El HSL també és un sistema de coordenades del color. Descriu els colors en el " -"To, Saturació i Claredat. La claredat posa específicament tant el groc " +"El HSL també és un sistema de coordenades del color. Descriu els colors en " +"el To, Saturació i Claredat. La claredat posa específicament tant el groc " "(rgb:1,1,0), el blau (rgb:0,0,1) i el gris mig (rgb:0,5,0,5,0,5) a la " "mateixa claredat (0,5)." #: ../../reference_manual/blending_modes/hsx.rst:34 msgid "HSV" msgstr "HSV" #: ../../reference_manual/blending_modes/hsx.rst:36 msgid "" "HSV, occasionally called HSB, is a color coordinate system. It measures " "colors in Hue, Saturation, and Value (also called Brightness). Value or " "Brightness specifically refers to strength at which the pixel-lights on your " "monitor have to shine. It sets Yellow (rgb:1,1,0), Blue (rgb:0,0,1) and " "White (rgb:1,1,0) at the same Value (100%)" msgstr "" "El HSV, de vegades anomenat HSB, és un sistema de coordenades del color. " "Mesura els colors en el To, Saturació i Valor (també anomenat brillantor). " "El valor o la brillantor es refereix específicament a la força amb la qual " "hauran de brillar els llums dels píxels en el vostre monitor. Estableix el " -"groc (rgb:1,1,0), blau (rgb:0,0,1) i blanc (rgb:1,1,0) al mateix valor (100%)." +"groc (rgb:1,1,0), blau (rgb:0,0,1) i blanc (rgb:1,1,0) al mateix valor " +"(100%)." #: ../../reference_manual/blending_modes/hsx.rst:40 msgid "HSY" msgstr "HSY" #: ../../reference_manual/blending_modes/hsx.rst:42 msgid "" "HSY is a color coordinate system. It categorizes colors in Hue, Saturation " "and Luminosity. Well, not really, it uses Luma instead of true luminosity, " "the difference being that Luminosity is linear while Luma is gamma-corrected " "and just weights the rgb components. Luma is based on scientific studies of " "how much light a color reflects in real-life. While like intensity it " "acknowledges that yellow (rgb:1,1,0) is lighter than blue (rgb:0,0,1), it " "also acknowledges that yellow (rgb:1,1,0) is lighter than cyan (rgb:0,1,1), " "based on these studies." msgstr "" "El HSY és un sistema de coordenades del color. Categoritza els colors en el " "To, Saturació i Lluminositat. Bé, no realment, fa servir la Luma " "(luminància) en lloc d'una lluminositat veritable, la diferència és que la " "lluminositat és lineal, mentre que la luma és corregida per la gamma i només " "pesa els components RGB. La luma es basa en estudis científics sobre quanta " "llum reflecteix un color a la vida real. Si bé té una intensitat similar, " "reconeix que el groc (rgb:1,1,0) és més clar que el blau (rgb:0,0,1), també " "reconeix que el groc (rgb:1,1,0) és més clar que el cian (rgb:0,1,1), a " "partir d'aquests estudis." #: ../../reference_manual/blending_modes/hsx.rst:46 msgid "HSX Blending Modes" msgstr "Modes de barreja HSX" #: ../../reference_manual/blending_modes/hsx.rst:55 msgid "Color, HSV, HSI, HSL, HSY" msgstr "Color, HSV, HSI, HSL o HSY" #: ../../reference_manual/blending_modes/hsx.rst:57 msgid "" "This takes the Luminosity/Value/Intensity/Lightness of the colors on the " "lower layer, and combines them with the Saturation and Hue of the upper " "pixels. We refer to Color HSY as 'Color' in line with other applications." msgstr "" "Això pren la Lluminositat/Valor/Intensitat/Claredat dels colors en la capa " "inferior i els combina amb la Saturació i el To dels píxels superiors. Ens " "referirem al Color HSY com a «Color» en la línia com ho fan altres " "aplicacions." #: ../../reference_manual/blending_modes/hsx.rst:62 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Color_HSI_Gray_0.4_and_Gray_0.5.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Color_HSI_Gray_0.4_and_Gray_0.5.png" #: ../../reference_manual/blending_modes/hsx.rst:62 #: ../../reference_manual/blending_modes/hsx.rst:67 #: ../../reference_manual/blending_modes/hsx.rst:72 msgid "Left: **Normal**. Right: **Color HSI**." msgstr "Esquerra: **Normal**. Dreta: **Color HSI**." #: ../../reference_manual/blending_modes/hsx.rst:67 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Color_HSI_Light_blue_and_Orange.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Color_HSI_Light_blue_and_Orange.png" #: ../../reference_manual/blending_modes/hsx.rst:72 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Color_HSI_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Color_HSI_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:78 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Color_HSL_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Color_HSL_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:78 msgid "Left: **Normal**. Right: **Color HSL**." msgstr "Esquerra: **Normal**. Dreta: **Color HSL**." #: ../../reference_manual/blending_modes/hsx.rst:84 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Color_HSV_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Color_HSV_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:84 msgid "Left: **Normal**. Right: **Color HSV**." msgstr "Esquerra: **Normal**. Dreta: **Color HSV**." #: ../../reference_manual/blending_modes/hsx.rst:90 msgid "" ".. image:: images/blending_modes/Blending_modes_Color_Sample_image_with_dots." "png" msgstr "" ".. image:: images/blending_modes/Blending_modes_Color_Sample_image_with_dots." "png" #: ../../reference_manual/blending_modes/hsx.rst:90 msgid "Left: **Normal**. Right: **Color**." msgstr "Esquerra: **Normal**. Dreta: **Color**." #: ../../reference_manual/blending_modes/hsx.rst:99 msgid "Hue HSV, HSI, HSL, HSY" msgstr "To HSV, HSI, HSL o HSY" #: ../../reference_manual/blending_modes/hsx.rst:101 msgid "" "Takes the saturation and tone of the lower layer and combines them with the " "hue of the upper-layer. Tone in this case being either Value, Lightness, " "Intensity or Luminosity." msgstr "" "Pren la saturació i el to de la capa inferior i els combina amb el to de la " "capa superior. El to en aquest cas és Valor, Claredat, Intensitat o " "Lluminositat." #: ../../reference_manual/blending_modes/hsx.rst:107 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Hue_HSI_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Hue_HSI_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:107 msgid "Left: **Normal**. Right: **Hue HSI**." msgstr "Esquerra: **Normal**. Dreta: **To HSI**." #: ../../reference_manual/blending_modes/hsx.rst:113 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Hue_HSL_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Hue_HSL_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:113 msgid "Left: **Normal**. Right: **Hue HSL**." msgstr "Esquerra: **Normal**. Dreta: **To HSL**." #: ../../reference_manual/blending_modes/hsx.rst:119 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Hue_HSV_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Hue_HSV_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:119 msgid "Left: **Normal**. Right: **Hue HSV**." msgstr "Esquerra: **Normal**. Dreta: **To HSV**." #: ../../reference_manual/blending_modes/hsx.rst:125 msgid "" ".. image:: images/blending_modes/Blending_modes_Hue_Sample_image_with_dots." "png" msgstr "" ".. image:: images/blending_modes/Blending_modes_Hue_Sample_image_with_dots." "png" #: ../../reference_manual/blending_modes/hsx.rst:125 msgid "Left: **Normal**. Right: **Hue**." msgstr "Esquerra: **Normal**. Dreta: **To**." #: ../../reference_manual/blending_modes/hsx.rst:134 msgid "Increase Value, Lightness, Intensity or Luminosity." msgstr "Augmentar el valor, claredat, intensitat o lluminositat." #: ../../reference_manual/blending_modes/hsx.rst:136 msgid "" "Similar to lighten, but specific to tone. Checks whether the upper layer's " "pixel has a higher tone than the lower layer's pixel. If so, the tone is " "increased, if not, the lower layer's tone is maintained." msgstr "" "Similar a Aclarit, però específic al To. Comprova si el píxel de la capa " "superior té un to més alt que el píxel de la capa inferior. Si és així, el " "to augmentarà, de no ser així mantindrà el de la capa inferior." #: ../../reference_manual/blending_modes/hsx.rst:142 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Increase_Intensity_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Increase_Intensity_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:142 msgid "Left: **Normal**. Right: **Increase Intensity**." msgstr "Esquerra: **Normal**. Dreta: **Augmenta la intensitat**." #: ../../reference_manual/blending_modes/hsx.rst:148 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Increase_Lightness_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Increase_Lightness_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:148 msgid "Left: **Normal**. Right: **Increase Lightness**." msgstr "Esquerra: **Normal**. Dreta: **Augmenta la claredat**." #: ../../reference_manual/blending_modes/hsx.rst:154 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Increase_Value_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Increase_Value_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:154 msgid "Left: **Normal**. Right: **Increase Value**." msgstr "Esquerra: **Normal**. Dreta: **Augmenta el valor**." #: ../../reference_manual/blending_modes/hsx.rst:160 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Increase_Luminosity_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Increase_Luminosity_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:160 msgid "Left: **Normal**. Right: **Increase Luminosity**." msgstr "Esquerra: **Normal**. Dreta: **Augmenta la lluminositat**." #: ../../reference_manual/blending_modes/hsx.rst:170 msgid "Increase Saturation HSI, HSV, HSL, HSY" msgstr "Augmentar la saturació HSI, HSV, HSL o HSY" #: ../../reference_manual/blending_modes/hsx.rst:172 msgid "" "Similar to lighten, but specific to Saturation. Checks whether the upper " "layer's pixel has a higher Saturation than the lower layer's pixel. If so, " "the Saturation is increased, if not, the lower layer's Saturation is " "maintained." msgstr "" "Similar a Aclarit, però específic a la Saturació. Comprova si el píxel de la " "capa superior té una saturació més alta que el píxel de la capa inferior. Si " "és així, la saturació augmentarà, de no ser així mantindrà la de la capa " "inferior." #: ../../reference_manual/blending_modes/hsx.rst:178 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Increase_Saturation_HSI_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Increase_Saturation_HSI_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:178 msgid "Left: **Normal**. Right: **Increase Saturation HSI**." msgstr "Esquerra: **Normal**. Dreta: **Augmenta la saturació HSI**." #: ../../reference_manual/blending_modes/hsx.rst:184 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Increase_Saturation_HSL_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Increase_Saturation_HSL_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:184 msgid "Left: **Normal**. Right: **Increase Saturation HSL**." msgstr "Esquerra: **Normal**. Dreta: **Augmenta la saturació HSL**." #: ../../reference_manual/blending_modes/hsx.rst:190 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Increase_Saturation_HSV_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Increase_Saturation_HSV_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:190 msgid "Left: **Normal**. Right: **Increase Saturation HSV**." msgstr "Esquerra: **Normal**. Dreta: **Augmenta la saturació HSV**." #: ../../reference_manual/blending_modes/hsx.rst:196 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Increase_Saturation_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Increase_Saturation_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:196 msgid "Left: **Normal**. Right: **Increase Saturation**." msgstr "Esquerra: **Normal**. Dreta: **Augmenta la saturació**." #: ../../reference_manual/blending_modes/hsx.rst:202 msgid "Intensity" msgstr "Intensitat" #: ../../reference_manual/blending_modes/hsx.rst:204 msgid "" "Takes the Hue and Saturation of the Lower layer and outputs them with the " "intensity of the upper layer." msgstr "" -"Pren el To i la Saturació de la capa inferior i els emet amb la Intensitat de " -"la capa superior." +"Pren el To i la Saturació de la capa inferior i els emet amb la Intensitat " +"de la capa superior." #: ../../reference_manual/blending_modes/hsx.rst:209 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Intensity_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Intensity_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:209 msgid "Left: **Normal**. Right: **Intensity**." msgstr "Esquerra: **Normal**. Dreta: **Intensitat**." #: ../../reference_manual/blending_modes/hsx.rst:214 msgid "Value" msgstr "Valor" #: ../../reference_manual/blending_modes/hsx.rst:216 msgid "" "Takes the Hue and Saturation of the Lower layer and outputs them with the " "Value of the upper layer." msgstr "" "Pren el To i la Saturació de la capa inferior i els emet amb el Valor de la " "capa superior." #: ../../reference_manual/blending_modes/hsx.rst:221 msgid "" ".. image:: images/blending_modes/Blending_modes_Value_Sample_image_with_dots." "png" msgstr "" ".. image:: images/blending_modes/Blending_modes_Value_Sample_image_with_dots." "png" #: ../../reference_manual/blending_modes/hsx.rst:221 msgid "Left: **Normal**. Right: **Value**." msgstr "Esquerra: **Normal**. Dreta: **Valor**." #: ../../reference_manual/blending_modes/hsx.rst:226 msgid "Lightness" msgstr "Claredat" #: ../../reference_manual/blending_modes/hsx.rst:228 msgid "" "Takes the Hue and Saturation of the Lower layer and outputs them with the " "Lightness of the upper layer." msgstr "" "Pren el To i la Saturació de la capa inferior i els emet amb la Claredat de " "la capa superior." #: ../../reference_manual/blending_modes/hsx.rst:233 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Lightness_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Lightness_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:233 msgid "Left: **Normal**. Right: **Lightness**." msgstr "Esquerra: **Normal**. Dreta: **Claredat**." #: ../../reference_manual/blending_modes/hsx.rst:238 msgid "Luminosity" msgstr "Lluminositat" #: ../../reference_manual/blending_modes/hsx.rst:240 msgid "" "As explained above, actually Luma, but called this way as it's in line with " "the terminology in other applications. Takes the Hue and Saturation of the " "Lower layer and outputs them with the Luminosity of the upper layer. The " "most preferred one of the four Tone blending modes, as this one gives fairly " "intuitive results for the Tone of a hue" msgstr "" "Com es va explicar anteriorment, en realitat la Luma, però anomenada així " "perquè s'alinea amb la terminologia en altres aplicacions. Pren el To i la " "Saturació de la capa inferior i els emet amb la Lluminositat de la capa " "superior. El més preferit dels quatre modes de barreja del to, ja que aquest " "proporciona resultats bastant intuïtius per al To d'un matís." #: ../../reference_manual/blending_modes/hsx.rst:247 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Luminosity_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Luminosity_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:247 msgid "Left: **Normal**. Right: **Luminosity**." msgstr "Esquerra: **Normal**. Dreta: **Lluminositat**." #: ../../reference_manual/blending_modes/hsx.rst:256 msgid "Saturation HSI, HSV, HSL, HSY" msgstr "Saturació HSI, HSV, HSL o HSY" #: ../../reference_manual/blending_modes/hsx.rst:258 msgid "" "Takes the Intensity and Hue of the lower layer, and outputs them with the " "HSI saturation of the upper layer." msgstr "" "Pren la Intensitat i el To de la capa inferior i els emet amb la Saturació " "HSI de la capa superior." #: ../../reference_manual/blending_modes/hsx.rst:263 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Saturation_HSI_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Saturation_HSI_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:263 msgid "Left: **Normal**. Right: **Saturation HSI**." msgstr "Esquerra: **Normal**. Dreta: **Saturació HSI**." #: ../../reference_manual/blending_modes/hsx.rst:269 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Saturation_HSL_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Saturation_HSL_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:269 msgid "Left: **Normal**. Right: **Saturation HSL**." msgstr "Esquerra: **Normal**. Dreta: **Saturació HSL**." #: ../../reference_manual/blending_modes/hsx.rst:275 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Saturation_HSV_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Saturation_HSV_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:275 msgid "Left: **Normal**. Right: **Saturation HSV**." msgstr "Esquerra: **Normal**. Dreta: **Saturació HSV**." #: ../../reference_manual/blending_modes/hsx.rst:281 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Saturation_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Saturation_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:281 msgid "Left: **Normal**. Right: **Saturation**." msgstr "Esquerra: **Normal**. Dreta: **Saturació**." #: ../../reference_manual/blending_modes/hsx.rst:289 msgid "Decrease Value, Lightness, Intensity or Luminosity" msgstr "Disminuir el valor, claredat, intensitat o lluminositat" #: ../../reference_manual/blending_modes/hsx.rst:291 msgid "" "Similar to darken, but specific to tone. Checks whether the upper layer's " "pixel has a lower tone than the lower layer's pixel. If so, the tone is " "decreased, if not, the lower layer's tone is maintained." msgstr "" "Similar a Fosca, però específic al To. Comprova si el píxel de la capa " "superior té un to més baix que el píxel de la capa inferior. Si és així, el " "to disminuirà, de no ser així mantindrà el de la capa inferior." #: ../../reference_manual/blending_modes/hsx.rst:297 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Intensity_Gray_0.4_and_Gray_0.5.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Intensity_Gray_0.4_and_Gray_0.5.png" #: ../../reference_manual/blending_modes/hsx.rst:297 #: ../../reference_manual/blending_modes/hsx.rst:302 #: ../../reference_manual/blending_modes/hsx.rst:307 msgid "Left: **Normal**. Right: **Decrease Intensity**." msgstr "Esquerra: **Normal**. Dreta: **Disminueix la intensitat**." #: ../../reference_manual/blending_modes/hsx.rst:302 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Intensity_Light_blue_and_Orange.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Intensity_Light_blue_and_Orange.png" #: ../../reference_manual/blending_modes/hsx.rst:307 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Intensity_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Intensity_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:313 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Lightness_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Lightness_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:313 msgid "Left: **Normal**. Right: **Decrease Lightness**." msgstr "Esquerra: **Normal**. Dreta: **Disminueix la claredat**." #: ../../reference_manual/blending_modes/hsx.rst:319 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Value_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Value_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:319 msgid "Left: **Normal**. Right: **Decrease Value**." msgstr "Esquerra: **Normal**. Dreta: **Disminueix el valor**." #: ../../reference_manual/blending_modes/hsx.rst:325 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Luminosity_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Luminosity_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:325 msgid "Left: **Normal**. Right: **Decrease Luminosity**." msgstr "Esquerra: **Normal**. Dreta: **Disminueix la lluminositat**." #: ../../reference_manual/blending_modes/hsx.rst:334 msgid "Decrease Saturation HSI, HSV, HSL, HSY" msgstr "Disminuir la saturació HSI, HSV, HSL o HSY" #: ../../reference_manual/blending_modes/hsx.rst:336 msgid "" "Similar to darken, but specific to Saturation. Checks whether the upper " "layer's pixel has a lower Saturation than the lower layer's pixel. If so, " "the Saturation is decreased, if not, the lower layer's Saturation is " "maintained." msgstr "" "Similar a Fosca, però específic a la Saturació. Comprova si el píxel de la " "capa superior té una saturació més baixa que el píxel de la capa inferior. " "Si és així, la saturació disminuirà, de no ser així mantindrà la de la capa " "inferior." #: ../../reference_manual/blending_modes/hsx.rst:342 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Saturation_HSI_Gray_0.4_and_Gray_0.5.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Saturation_HSI_Gray_0.4_and_Gray_0.5.png" #: ../../reference_manual/blending_modes/hsx.rst:342 #: ../../reference_manual/blending_modes/hsx.rst:347 #: ../../reference_manual/blending_modes/hsx.rst:352 msgid "Left: **Normal**. Right: **Decrease Saturation HSI**." msgstr "Esquerra: **Normal**. Dreta: **Disminueix la saturació HSI**." #: ../../reference_manual/blending_modes/hsx.rst:347 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Saturation_HSI_Light_blue_and_Orange.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Saturation_HSI_Light_blue_and_Orange.png" #: ../../reference_manual/blending_modes/hsx.rst:352 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Saturation_HSI_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Saturation_HSI_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:358 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Saturation_HSL_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Saturation_HSL_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:358 msgid "Left: **Normal**. Right: **Decrease Saturation HSL**." msgstr "Esquerra: **Normal**. Dreta: **Disminueix la saturació HSL**." #: ../../reference_manual/blending_modes/hsx.rst:364 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Saturation_HSV_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Saturation_HSV_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:364 msgid "Left: **Normal**. Right: **Decrease Saturation HSV**." msgstr "Esquerra: **Normal**. Dreta: **Disminueix la saturació HSV**." #: ../../reference_manual/blending_modes/hsx.rst:370 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Saturation_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Decrease_Saturation_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/hsx.rst:370 msgid "Left: **Normal**. Right: **Decrease Saturation**." msgstr "Esquerra: **Normal**. Dreta: **Disminueix la saturació**." diff --git a/locale/ca/LC_MESSAGES/reference_manual/blending_modes/lighten.po b/locale/ca/LC_MESSAGES/reference_manual/blending_modes/lighten.po index e4068b4ef..0955660d9 100644 --- a/locale/ca/LC_MESSAGES/reference_manual/blending_modes/lighten.po +++ b/locale/ca/LC_MESSAGES/reference_manual/blending_modes/lighten.po @@ -1,423 +1,422 @@ # Translation of docs_krita_org_reference_manual___blending_modes___lighten.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: reference_manual\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-03-30 03:35+0100\n" "PO-Revision-Date: 2019-04-22 22:24+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 18.12.3\n" #: ../../reference_manual/blending_modes/lighten.rst:1 msgid "" "Page about the lighten blending modes in Krita: Color Dodge, Gamma Light, " "Hard Light, Lighten, Lighter Color, Linear Dodge, Linear Light, Pin Light, " "Screen, Soft Light and Vivid Light." msgstr "" "Pàgina sobre els modes de barreja més lleugers al Krita: Esvaïment del " "color, Llum gamma, Llum forta, Lighten, Color més clar, Esvaïment lineal, " "Llum lineal, Llum focal, Pantalla, Llum suau i Llum vívida." #: ../../reference_manual/blending_modes/lighten.rst:15 #: ../../reference_manual/blending_modes/lighten.rst:68 msgid "Lighten" msgstr "Aclarit" #: ../../reference_manual/blending_modes/lighten.rst:17 msgid "Blending modes that lighten the image." msgstr "Modes de barreja que alleugen la imatge." #: ../../reference_manual/blending_modes/lighten.rst:23 msgid "Color Dodge" msgstr "Esvaïment del color" #: ../../reference_manual/blending_modes/lighten.rst:25 msgid "" "Similar to Divide. Inverts the top layer, and divides the lower layer by the " "inverted top layer. This results in a image with emphasized highlights, like " "Dodging would do in traditional darkroom photography." msgstr "" "Similar a Divideix. Inverteix la capa superior i divideix la capa inferior " "per la capa superior invertida. Això dóna com a resultat una imatge amb " "èmfasi en les llums intenses, com ho faria Esvaeix en la cambra fosca de la " "fotografia tradicional." #: ../../reference_manual/blending_modes/lighten.rst:32 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Color_Dodge_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Color_Dodge_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/lighten.rst:32 msgid "Left: **Normal**. Right: **Color Dodge**." msgstr "Esquerra: **Normal**. Dreta: **Esvaïment del color**." #: ../../reference_manual/blending_modes/lighten.rst:38 msgid "Gamma Light" msgstr "Llum gamma" #: ../../reference_manual/blending_modes/lighten.rst:40 msgid "Outputs the upper layer as power of the lower layer." msgstr "Mostra la capa superior com a potència de la capa inferior." #: ../../reference_manual/blending_modes/lighten.rst:45 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Gamma_Light_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Gamma_Light_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/lighten.rst:45 msgid "Left: **Normal**. Right: **Gamma Light**." msgstr "Esquerra: **Normal**. Dreta: **Llum gamma**." #: ../../reference_manual/blending_modes/lighten.rst:51 msgid "Hard Light" msgstr "Llum forta" #: ../../reference_manual/blending_modes/lighten.rst:53 msgid "" "Similar to Overlay. A combination of the Multiply and Screen blending modes, " "switching between both at a middle-lightness." msgstr "" "Similar a la superposició. Una combinació dels modes de barreja Multiplica i " "Pantalla, canviant entre tots dos en una claredat mitjana." #: ../../reference_manual/blending_modes/lighten.rst:56 msgid "" "Hard light checks if the color on the upperlayer has a lightness above 0.5. " "Unlike overlay, if the pixel is lighter than 0.5, it is blended like in " "Multiply mode, if not the pixel is blended like in Screen mode." msgstr "" -"La llum forta comprova si el color a la capa superior té una claredat" -" superior " -"al 0,5. A diferència de la superposició, si el píxel és més clar que 0,5, es " -"barrejarà com en la mode Multiplica, de ser així es barrejarà com en el mode " -"Pantalla." +"La llum forta comprova si el color a la capa superior té una claredat " +"superior al 0,5. A diferència de la superposició, si el píxel és més clar " +"que 0,5, es barrejarà com en la mode Multiplica, de ser així es barrejarà " +"com en el mode Pantalla." #: ../../reference_manual/blending_modes/lighten.rst:58 msgid "Effectively, this decreases contrast." msgstr "Efectivament, això fa disminuir el contrast." #: ../../reference_manual/blending_modes/lighten.rst:63 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Hard_Light_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Hard_Light_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/lighten.rst:63 msgid "Left: **Normal**. Right: **Hard Light**." msgstr "Esquerra: **Normal**. Dreta: **Llum forta**." #: ../../reference_manual/blending_modes/lighten.rst:70 msgid "" "With the darken, the upper layer's colors are checked for their lightness. " "Only if they are Lighter than the underlying color on the lower layer, will " "they be visible." msgstr "" "Amb l'enfosquiment, els colors de la capa superior es verifiquen per la seva " "claredat. Només seran visibles si són més clars que el color subjacent a la " "capa inferior." #: ../../reference_manual/blending_modes/lighten.rst:75 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Lighten_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Lighten_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/lighten.rst:75 msgid "Left: **Normal**. Right: **Lighten**." msgstr "Esquerra: **Normal**. Dreta: **Aclarit**." #: ../../reference_manual/blending_modes/lighten.rst:80 msgid "Lighter Color" msgstr "Color més clar" #: ../../reference_manual/blending_modes/lighten.rst:85 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Lighter_Color_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Lighter_Color_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/lighten.rst:85 msgid "Left: **Normal**. Right: **Lighter Color**." msgstr "Esquerra: **Normal**. Dreta: **Color més clar**." #: ../../reference_manual/blending_modes/lighten.rst:91 msgid "Linear Dodge" msgstr "Esvaïment lineal" #: ../../reference_manual/blending_modes/lighten.rst:93 msgid "Exactly the same as :ref:`bm_addition`." msgstr "Exactament el mateix que :ref:`bm_addition`." #: ../../reference_manual/blending_modes/lighten.rst:95 msgid "Put in for compatibility purposes." msgstr "Posat per propòsits de compatibilitat." #: ../../reference_manual/blending_modes/lighten.rst:100 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Linear_Dodge_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Linear_Dodge_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/lighten.rst:100 msgid "" "Left: **Normal**. Right: **Linear Dodge** (exactly the same as Addition)." msgstr "" "Esquerra: **Normal**. Dreta: **Esvaïment lineal** (exactament el mateix que " "l'addició)." #: ../../reference_manual/blending_modes/lighten.rst:105 msgid "Linear Light" msgstr "Llum lineal" #: ../../reference_manual/blending_modes/lighten.rst:107 msgid "Similar to :ref:`bm_overlay`." msgstr "Similar al :ref:`bm_overlay`." #: ../../reference_manual/blending_modes/lighten.rst:109 msgid "" "Combines :ref:`bm_linear_dodge` and :ref:`bm_linear_burn`. When the " "lightness of the upper-pixel is higher than 0.5, it uses Linear dodge, if " "not, Linear burn to blend the pixels." msgstr "" "Combina :ref:`bm_linear_dodge` i :ref:`bm_linear_burn`. Quan la claredat del " "píxel superior és superior que 0,5, s'utilitzarà l'Esvaïment lineal, de no " "ser així s'emprarà el cremat lineal per a barrejar els píxels." #: ../../reference_manual/blending_modes/lighten.rst:114 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Linear_Light_Gray_0.4_and_Gray_0.5.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Linear_Light_Gray_0.4_and_Gray_0.5.png" #: ../../reference_manual/blending_modes/lighten.rst:114 #: ../../reference_manual/blending_modes/lighten.rst:119 #: ../../reference_manual/blending_modes/lighten.rst:124 msgid "Left: **Normal**. Right: **Linear Light**." msgstr "Esquerra: **Normal**. Dreta: **Llum lineal**." #: ../../reference_manual/blending_modes/lighten.rst:119 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Linear_Light_Light_blue_and_Orange.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Linear_Light_Light_blue_and_Orange.png" #: ../../reference_manual/blending_modes/lighten.rst:124 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Linear_Light_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Linear_Light_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/lighten.rst:129 msgid "Pin Light" msgstr "Llum focal" #: ../../reference_manual/blending_modes/lighten.rst:131 msgid "" "Checks which is darker the lower layer's pixel or the upper layer's double " "so bright. Then checks which is brighter of that result or the inversion of " "the doubled lower layer." msgstr "" "Comprova quins són els valors que proporcionen un píxel més fosc: el valor " "del píxel a la capa inferior o el de la capa superior amb doble brillantor. " "Després verifica quina és més brillant entre aquest resultat i la inversió " "de la capa inferior amb doble brillantor." #: ../../reference_manual/blending_modes/lighten.rst:137 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Pin_Light_Gray_0.4_and_Gray_0.5.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Pin_Light_Gray_0.4_and_Gray_0.5.png" #: ../../reference_manual/blending_modes/lighten.rst:137 #: ../../reference_manual/blending_modes/lighten.rst:142 #: ../../reference_manual/blending_modes/lighten.rst:147 msgid "Left: **Normal**. Right: **Pin Light**." msgstr "Esquerra: **Normal**. Dreta: **Llum focal**." #: ../../reference_manual/blending_modes/lighten.rst:142 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Pin_Light_Light_blue_and_Orange.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Pin_Light_Light_blue_and_Orange.png" #: ../../reference_manual/blending_modes/lighten.rst:147 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Pin_Light_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Pin_Light_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/lighten.rst:152 msgid "Screen" msgstr "Pantalla" #: ../../reference_manual/blending_modes/lighten.rst:154 msgid "Perceptually the opposite of :ref:`bm_multiply`." msgstr "Perceptiblement el contrari que :ref:`bm_multiply`." #: ../../reference_manual/blending_modes/lighten.rst:156 msgid "" "Mathematically, Screen takes both layers, inverts them, then multiplies " "them, and finally inverts them again." msgstr "" "Matemàticament, Pantalla pren ambdues capes, les inverteix, després les " "multiplica i finalment les inverteix de nou." #: ../../reference_manual/blending_modes/lighten.rst:158 msgid "" "This results in light tones being more opaque and dark tones transparent." msgstr "" "Això fa que els tons clars siguin més opacs i els tons foscos transparents." #: ../../reference_manual/blending_modes/lighten.rst:163 msgid "" ".. image:: images/blending_modes/Blending_modes_Screen_Gray_0.4_and_Gray_0.5." "png" msgstr "" ".. image:: images/blending_modes/Blending_modes_Screen_Gray_0.4_and_Gray_0.5." "png" #: ../../reference_manual/blending_modes/lighten.rst:163 #: ../../reference_manual/blending_modes/lighten.rst:168 #: ../../reference_manual/blending_modes/lighten.rst:173 msgid "Left: **Normal**. Right: **Screen**." msgstr "Esquerra: **Normal**. Dreta: **Pantalla**." #: ../../reference_manual/blending_modes/lighten.rst:168 msgid "" ".. image:: images/blending_modes/Blending_modes_Screen_Light_blue_and_Orange." "png" msgstr "" ".. image:: images/blending_modes/Blending_modes_Screen_Light_blue_and_Orange." "png" #: ../../reference_manual/blending_modes/lighten.rst:173 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Screen_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Screen_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/lighten.rst:178 msgid "Soft Light (Photoshop) & Soft Light SVG" msgstr "Llum suau (Photoshop) i Llum suau SVG" #: ../../reference_manual/blending_modes/lighten.rst:180 msgid "" "These are less harsh versions of Hard Light, not resulting in full black or " "full white." msgstr "" "Aquestes són versions menys dures que la Llum forta, que no donen com a " "resultat el negre o blanc total." #: ../../reference_manual/blending_modes/lighten.rst:182 msgid "" "The SVG version is slightly different to the Photoshop version in that it " "uses a slightly different bit of formula when the lightness of the lower " "pixel is lower than 25%, this prevents the strength of the brightness " "increase." msgstr "" "La versió SVG és lleugerament diferent de la versió del Photoshop, ja que " "utilitza una fórmula lleugerament diferent quan la claredat del píxel " "inferior és inferior al 25%, això evita que la intensitat de la brillantor " "augmenti." #: ../../reference_manual/blending_modes/lighten.rst:187 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Soft_Light_Photoshop_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Soft_Light_Photoshop_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/lighten.rst:187 msgid "Left: **Normal**. Right: **Soft Light (Photoshop)**." msgstr "Esquerra: **Normal**. Dreta: **Llum suau (Photoshop)**." #: ../../reference_manual/blending_modes/lighten.rst:193 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Soft_Light_SVG_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Soft_Light_SVG_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/lighten.rst:193 msgid "Left: **Normal**. Right: **Soft Light (SVG)**." msgstr "Esquerra: **Normal**. Dreta: **Llum suau (SVG)**." #: ../../reference_manual/blending_modes/lighten.rst:198 msgid "Vivid Light" msgstr "Llum vívida" #: ../../reference_manual/blending_modes/lighten.rst:200 msgid "Similar to Overlay." msgstr "Similar a la superposició." #: ../../reference_manual/blending_modes/lighten.rst:202 msgid "" "Mixes both Color Dodge and Burn blending modes. If the color of the upper " "layer is darker than 50%, the blending mode will be Burn, if not the " "blending mode will be Color Dodge." msgstr "" "Mescla ambdós modes de barreja Esvaïment del color i Cremat del color. Si el " "color de la capa superior és més fosc que el 50%, el mode de barreja serà " "Cremat del color, d'altra manera el mode de barreja serà Esvaïment del color." #: ../../reference_manual/blending_modes/lighten.rst:206 msgid "" "This algorithm doesn't use color dodge and burn, we don't know WHAT it does " "do but for Color Dodge and Burn you need to use :ref:`bm_hard_mix`" msgstr "" -"Aquest algoritme no utilitza Esvaïment del color i Cremat del color, no sabem " -"QUÈ fa, però per a Esvaïment del color i Cremat del color necessitareu " +"Aquest algoritme no utilitza Esvaïment del color i Cremat del color, no " +"sabem QUÈ fa, però per a Esvaïment del color i Cremat del color necessitareu " "utilitzar la :ref:`bm_hard_mix`." #: ../../reference_manual/blending_modes/lighten.rst:211 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Vivid_Light_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Vivid_Light_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/lighten.rst:211 msgid "Left: **Normal**. Right: **Vivid Light**." msgstr "Esquerra: **Normal**. Dreta: **Llum vívida**." diff --git a/locale/ca/LC_MESSAGES/reference_manual/blending_modes/misc.po b/locale/ca/LC_MESSAGES/reference_manual/blending_modes/misc.po index 4d95c1f49..168ab4a92 100644 --- a/locale/ca/LC_MESSAGES/reference_manual/blending_modes/misc.po +++ b/locale/ca/LC_MESSAGES/reference_manual/blending_modes/misc.po @@ -1,184 +1,184 @@ # Translation of docs_krita_org_reference_manual___blending_modes___misc.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: reference_manual\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-19 03:36+0100\n" "PO-Revision-Date: 2019-04-22 22:27+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 18.12.3\n" #: ../../reference_manual/blending_modes/misc.rst:1 msgid "" "Page about the miscellaneous blending modes in Krita: Bumpmap, Combine " "Normal Map, Copy Red, Copy Green, Copy Blue, Copy and Dissolve." msgstr "" "Pàgina sobre els diversos modes de barreja al Krita: Mapa de relleu, Combina " "mapa normal, Copia el vermell, Copia el verd, Copia el blau, Copia i Dissol." #: ../../reference_manual/blending_modes/misc.rst:15 msgid "Misc" msgstr "Miscel·lània" #: ../../reference_manual/blending_modes/misc.rst:21 msgid "Bumpmap" msgstr "Mapa de relleu" #: ../../reference_manual/blending_modes/misc.rst:23 msgid "This filter seems to both multiply and respect the alpha of the input." msgstr "Aquest filtre sembla multiplicar i respectar l'alfa de l'entrada." #: ../../reference_manual/blending_modes/misc.rst:30 msgid "Combine Normal Map" msgstr "Combina mapes normals" # skip-rule: t-acc_obe #: ../../reference_manual/blending_modes/misc.rst:32 msgid "" "Mathematically robust blending mode for normal maps, using `Reoriented " "Normal Map Blending `_." msgstr "" "Mode de barreja matemàticament robust per a mapes normals, utilitzant la " -"`Barreja de mapes normal reorientada `_." +"`Barreja de mapes normal reorientada `_." #: ../../reference_manual/blending_modes/misc.rst:38 msgid "Copy" msgstr "Copia" #: ../../reference_manual/blending_modes/misc.rst:40 msgid "" "Copies the previous layer exactly. Useful for when using filters and filter-" "masks." msgstr "" "Copia exactament la capa anterior. Útil per a quan s'utilitzen filtres i " "màscares de filtratge." #: ../../reference_manual/blending_modes/misc.rst:46 msgid "" ".. image:: images/blending_modes/Blending_modes_Copy_Sample_image_with_dots." "png" msgstr "" ".. image:: images/blending_modes/Blending_modes_Copy_Sample_image_with_dots." "png" #: ../../reference_manual/blending_modes/misc.rst:46 msgid "Left: **Normal**. Right: **Copy**." msgstr "Esquerra: **Normal**. Dreta: **Copia**." #: ../../reference_manual/blending_modes/misc.rst:54 msgid "Copy Red, Green, Blue" msgstr "Copia el vermell, verd, blau" #: ../../reference_manual/blending_modes/misc.rst:56 msgid "" "This is a blending mode that will just copy/blend a source channel to a " "destination channel. Specifically, it will take the specific channel from " "the upper layer and copy that over to the lower layers." msgstr "" -"Aquesta és un mode de barreja que només copiarà/barrejarà un canal d'origen a " -"un canal de destinació. Específicament, prendrà el canal específic de la " +"Aquesta és un mode de barreja que només copiarà/barrejarà un canal d'origen " +"a un canal de destinació. Específicament, prendrà el canal específic de la " "capa superior i el copiarà a les capes inferiors." #: ../../reference_manual/blending_modes/misc.rst:59 msgid "" "So, if you want the brush to only affect the red channel, set the blending " "mode to 'copy red'." msgstr "" "Per tant, si voleu que el pinzell només afecti el canal vermell, establiu el " "mode de barreja a «Copia el vermell»." #: ../../reference_manual/blending_modes/misc.rst:65 msgid "" ".. image:: images/blending_modes/Krita_Filter_layer_invert_greenchannel.png" msgstr "" ".. image:: images/blending_modes/Krita_Filter_layer_invert_greenchannel.png" #: ../../reference_manual/blending_modes/misc.rst:65 msgid "The copy red, green and blue blending modes also work on filter-layers." msgstr "" "Els modes de barreja copia el vermell, verd i blau també funcionen sobre les " "capes de filtratge." #: ../../reference_manual/blending_modes/misc.rst:67 msgid "" "This can also be done with filter layers. So if you quickly want to flip a " "layer's green channel, make an invert filter layer with 'copy green' above " "it." msgstr "" "Això també es pot fer amb les capes de filtratge. Per tant, si voleu canviar " "ràpidament el canal verd d'una capa, creeu una capa de filtratge invers amb " "un «Copia el verd» a sobre." #: ../../reference_manual/blending_modes/misc.rst:72 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Copy_Red_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Copy_Red_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/misc.rst:72 msgid "Left: **Normal**. Right: **Copy Red**." msgstr "Esquerra: **Normal**. Dreta: **Copia el vermell**." #: ../../reference_manual/blending_modes/misc.rst:78 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Copy_Green_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Copy_Green_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/misc.rst:78 msgid "Left: **Normal**. Right: **Copy Green**." msgstr "Esquerra: **Normal**. Dreta: **Copia el verd**." #: ../../reference_manual/blending_modes/misc.rst:84 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Copy_Blue_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Copy_Blue_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/misc.rst:84 msgid "Left: **Normal**. Right: **Copy Blue**." msgstr "Esquerra: **Normal**. Dreta: **Copia el blau**." #: ../../reference_manual/blending_modes/misc.rst:90 msgid "Dissolve" msgstr "Dissol" #: ../../reference_manual/blending_modes/misc.rst:92 msgid "" "Instead of using transparency, this blending mode will use a random " "dithering pattern to make the transparent areas look sort of transparent." msgstr "" "En lloc d'utilitzar la transparència, aquest mode de barreja utilitzarà un " "patró de juxtaposició a l'atzar per a fer que les àrees transparents semblin " "una mica transparents." #: ../../reference_manual/blending_modes/misc.rst:97 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Dissolve_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Dissolve_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/misc.rst:97 msgid "Left: **Normal**. Right: **Dissolve**." msgstr "Esquerra: **Normal**. Dreta: **Dissol**." diff --git a/locale/ca/LC_MESSAGES/reference_manual/blending_modes/mix.po b/locale/ca/LC_MESSAGES/reference_manual/blending_modes/mix.po index 5e8294ede..e79cc1aa4 100644 --- a/locale/ca/LC_MESSAGES/reference_manual/blending_modes/mix.po +++ b/locale/ca/LC_MESSAGES/reference_manual/blending_modes/mix.po @@ -1,390 +1,390 @@ # Translation of docs_krita_org_reference_manual___blending_modes___mix.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: reference_manual\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-04-17 03:39+0200\n" "PO-Revision-Date: 2019-04-22 22:20+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 18.12.3\n" #: ../../reference_manual/blending_modes/mix.rst:None msgid ".. image:: images/blending_modes/Greaterblendmode.gif" msgstr ".. image:: images/blending_modes/Greaterblendmode.gif" #: ../../reference_manual/blending_modes/mix.rst:1 msgid "" "Page about the mix blending modes in Krita: Allanon, Alpha Darken, Behind, " "Erase, Geometric Mean, Grain Extract, Grain Merge, Greater, Hard Mix, Hard " "Overlay, Normal, Overlay and Parallel." msgstr "" "Pàgina sobre la mescla dels modes de barreja en el Krita: Allanon, " "Enfosquiment alfa, Darrere, Esborra, Mitjana geomètrica, Extracció de gra, " "Fusió del gra, Engrandeix, Barreja forta, Superposició forta, Normal, " "Superposició i Paral·lel." #: ../../reference_manual/blending_modes/mix.rst:15 msgid "Mix" msgstr "Mescla" #: ../../reference_manual/blending_modes/mix.rst:21 msgid "Allanon" msgstr "Allanon" #: ../../reference_manual/blending_modes/mix.rst:23 msgid "" "Blends the upper layer as half-transparent with the lower. (It add the two " "layers together and then halves the value)" msgstr "" -"Barreja la capa superior com a mig transparent amb la inferior. (Afegeix les" -" dues capes juntes i després divideix el valor a la meitat)." +"Barreja la capa superior com a mig transparent amb la inferior. (Afegeix les " +"dues capes juntes i després divideix el valor a la meitat)." #: ../../reference_manual/blending_modes/mix.rst:29 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Allanon_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Allanon_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/mix.rst:29 msgid "Left: **Normal**. Right: **Allanon**." msgstr "Esquerra: **Normal**. Dreta: **Allanon**." #: ../../reference_manual/blending_modes/mix.rst:35 msgid "Alpha Darken" msgstr "Enfosquiment alfa" #: ../../reference_manual/blending_modes/mix.rst:37 msgid "" "As far as I can tell this seems to premultiply the alpha, as is common in " "some file-formats." msgstr "" -"Pel que puc dir, això sembla premultiplicar l'alfa, com és comú en alguns" -" formats de fitxer." +"Pel que puc dir, això sembla premultiplicar l'alfa, com és comú en alguns " +"formats de fitxer." #: ../../reference_manual/blending_modes/mix.rst:42 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Alpha_Darken_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Alpha_Darken_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/mix.rst:42 msgid "Left: **Normal**. Right: **Alpha Darken**." msgstr "Esquerra: **Normal**. Dreta: **Enfosquiment alfa**." #: ../../reference_manual/blending_modes/mix.rst:48 msgid "Behind" msgstr "Darrere" #: ../../reference_manual/blending_modes/mix.rst:50 msgid "" "Does the opposite of normal, and tries to have the upper layer rendered " "below the lower layer." msgstr "" -"Fa el contrari del que és normal, i intenta que la capa superior es" -" renderitzi a sota de la capa inferior." +"Fa el contrari del que és normal, i intenta que la capa superior es " +"renderitzi a sota de la capa inferior." #: ../../reference_manual/blending_modes/mix.rst:55 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Behind_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Behind_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/mix.rst:55 msgid "Left: **Normal**. Right: **Behind**." msgstr "Esquerra: **Normal**. Dreta: **Darrere**." #: ../../reference_manual/blending_modes/mix.rst:61 msgid "Erase" msgstr "Esborra" #: ../../reference_manual/blending_modes/mix.rst:63 msgid "" "This subtracts the opaque pixels of the upper layer from the lower layer, " "effectively erasing." msgstr "" -"Això treu dels píxels opacs de la capa superior de la capa inferior," -" esborrant-los de manera efectiva." +"Això treu dels píxels opacs de la capa superior de la capa inferior, " +"esborrant-los de manera efectiva." #: ../../reference_manual/blending_modes/mix.rst:68 msgid "" ".. image:: images/blending_modes/Blending_modes_Erase_Sample_image_with_dots." "png" msgstr "" ".. image:: images/blending_modes/Blending_modes_Erase_Sample_image_with_dots." "png" #: ../../reference_manual/blending_modes/mix.rst:68 msgid "Left: **Normal**. Right: **Erase**." msgstr "Esquerra: **Normal**. Dreta: **Esborra**." #: ../../reference_manual/blending_modes/mix.rst:74 msgid "Geometric Mean" msgstr "Mitjana geomètrica" #: ../../reference_manual/blending_modes/mix.rst:76 msgid "" "This blending mode multiplies the top layer with the bottom, and then " "outputs the square root of that." msgstr "" -"Aquest mode de barreja multiplica la capa superior amb la inferior i després" -" genera l'arrel quadrada." +"Aquest mode de barreja multiplica la capa superior amb la inferior i després " +"genera l'arrel quadrada." #: ../../reference_manual/blending_modes/mix.rst:81 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Geometric_Mean_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Geometric_Mean_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/mix.rst:81 msgid "Left: **Normal**. Right: **Geometric Mean**." msgstr "Esquerra: **Normal**. Dreta: **Mitjana geomètrica**." #: ../../reference_manual/blending_modes/mix.rst:87 msgid "Grain Extract" msgstr "Extracció de gra" #: ../../reference_manual/blending_modes/mix.rst:89 msgid "" "Similar to subtract, the colors of the upper layer are subtracted from the " "colors of the lower layer, and then 50% gray is added." msgstr "" -"Similar al Sostreu, els colors de la capa superior es restaran dels colors de" -" la capa inferior, i després s'hi afegirà un 50% de gris." +"Similar al Sostreu, els colors de la capa superior es restaran dels colors " +"de la capa inferior, i després s'hi afegirà un 50% de gris." #: ../../reference_manual/blending_modes/mix.rst:94 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Grain_Extract_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Grain_Extract_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/mix.rst:94 msgid "Left: **Normal**. Right: **Grain Extract**." msgstr "Esquerra: **Normal**. Dreta: **Extracció de gra**." #: ../../reference_manual/blending_modes/mix.rst:100 msgid "Grain Merge" msgstr "Fusió de gra" #: ../../reference_manual/blending_modes/mix.rst:102 msgid "" "Similar to addition, the colors of the upper layer are added to the colors, " "and then 50% gray is subtracted." msgstr "" -"Similar a l'Addició, els colors de la capa superior s'afegiran als colors de" -" la capa inferior, i després s'hi restarà un 50% de gris." +"Similar a l'Addició, els colors de la capa superior s'afegiran als colors de " +"la capa inferior, i després s'hi restarà un 50% de gris." #: ../../reference_manual/blending_modes/mix.rst:107 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Grain_Merge_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Grain_Merge_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/mix.rst:107 msgid "Left: **Normal**. Right: **Grain Merge**." msgstr "Esquerra: **Normal**. Dreta: **Fusió de gra**." #: ../../reference_manual/blending_modes/mix.rst:113 msgid "Greater" msgstr "Engrandeix" #: ../../reference_manual/blending_modes/mix.rst:115 msgid "" "A blending mode which checks whether the painted color is painted with a " "higher opacity than the existing colors. If so, it paints over them, if not, " "it doesn't paint at all." msgstr "" -"Un mode de barreja que comprova si el color pintat està pintat amb una" -" opacitat més alta que els colors existents. Si és així, pinta sobre seu, si" -" no, no pinta res." +"Un mode de barreja que comprova si el color pintat està pintat amb una " +"opacitat més alta que els colors existents. Si és així, pinta sobre seu, si " +"no, no pinta res." #: ../../reference_manual/blending_modes/mix.rst:124 msgid "Hard Mix" msgstr "Barreja forta" #: ../../reference_manual/blending_modes/mix.rst:126 msgid "Similar to Overlay." msgstr "Similar a la Superposició." #: ../../reference_manual/blending_modes/mix.rst:128 msgid "" "Mixes both Color Dodge and Burn blending modes. If the color of the upper " "layer is darker than 50%, the blending mode will be Burn, if not the " "blending mode will be Color Dodge." msgstr "" "Mescla ambdós modes de barreja Esvaïment del color i Cremat del color. Si el " "color de la capa superior és més fosc que el 50%, el mode de barreja serà " "Cremat del color, d'altra manera el mode de barreja serà Esvaïment del color." #: ../../reference_manual/blending_modes/mix.rst:134 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Hard_Mix_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Hard_Mix_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/mix.rst:134 msgid "Left: **Normal**. Right: **Hard Mix**." msgstr "Esquerra: **Normal**. Dreta: **Barreja forta**." #: ../../reference_manual/blending_modes/mix.rst:139 msgid "Hard Mix (Photoshop)" msgstr "Barreja forta (Photoshop)" #: ../../reference_manual/blending_modes/mix.rst:141 msgid "This is the hard mix blending mode as it is implemented in photoshop." msgstr "" -"Aquest és el mode de barreja «Barreja forta» tal com està implementat al" -" Photoshop." +"Aquest és el mode de barreja «Barreja forta» tal com està implementat al " +"Photoshop." #: ../../reference_manual/blending_modes/mix.rst:147 msgid ".. image:: images/blending_modes/Krita_4_0_hard_mix_ps.png" msgstr ".. image:: images/blending_modes/Krita_4_0_hard_mix_ps.png" #: ../../reference_manual/blending_modes/mix.rst:147 msgid "" "**Left**: Dots are mixed in with the normal blending mode, on the **Right**: " "Dots are mixed in with hardmix." msgstr "" -"**Esquerra**: Els punts es mesclen amb el mode de barreja normal. **Dreta**:" -" Els punts es mesclen amb la Barreja forta." +"**Esquerra**: Els punts es mesclen amb el mode de barreja normal. **Dreta**: " +"Els punts es mesclen amb la Barreja forta." #: ../../reference_manual/blending_modes/mix.rst:149 msgid "" "This add the two values, and then checks if the value is above the maximum. " "If so it will output the maximum, otherwise the minimum." msgstr "" -"Això afegeix els dos valors i després verifica si el valor està per sobre del" -" màxim. Si és així emetrà el màxim, en cas contrari el mínim." +"Això afegeix els dos valors i després verifica si el valor està per sobre " +"del màxim. Si és així emetrà el màxim, en cas contrari el mínim." #: ../../reference_manual/blending_modes/mix.rst:155 msgid "Hard Overlay" msgstr "Superposició forta" #: ../../reference_manual/blending_modes/mix.rst:159 msgid "" "Similar to Hard light but hard light use Screen when the value is above 50%. " "Divide gives better results than Screen, especially on floating point images." msgstr "" -"Similar a la Llum forta -la qual fa servir Pantalla quan el valor està per" -" sobre del 50%-. Dividir dóna millors resultats que Pantalla, especialment en" -" imatges amb coma flotant." +"Similar a la Llum forta -la qual fa servir Pantalla quan el valor està per " +"sobre del 50%-. Dividir dóna millors resultats que Pantalla, especialment en " +"imatges amb coma flotant." #: ../../reference_manual/blending_modes/mix.rst:164 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Hard_Overlay_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Hard_Overlay_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/mix.rst:164 msgid "Left: **Normal**. Right: **Hard Overlay**." msgstr "Esquerra: **Normal**. Dreta: **Superposició forta**." #: ../../reference_manual/blending_modes/mix.rst:170 msgid "Normal" msgstr "Normal" #: ../../reference_manual/blending_modes/mix.rst:172 msgid "" "As you may have guessed this is the default Blending mode for all layers." msgstr "" #: ../../reference_manual/blending_modes/mix.rst:174 msgid "" "In this mode, the computer checks on the upper layer how transparent a pixel " "is, which color it is, and then mixes the color of the upper layer with the " "lower layer proportional to the transparency." msgstr "" #: ../../reference_manual/blending_modes/mix.rst:179 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Normal_50_Opacity_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Normal_50_Opacity_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/mix.rst:179 msgid "Left: **Normal** 100% Opacity. Right: **Normal** 50% Opacity." msgstr "" "Esquerra: **Normal** 100% d'opacitat. Dreta: **Normal** 50% d'opacitat." #: ../../reference_manual/blending_modes/mix.rst:185 msgid "Overlay" msgstr "Superposició" #: ../../reference_manual/blending_modes/mix.rst:187 msgid "" "A combination of the Multiply and Screen blending modes, switching between " "both at a middle-lightness." msgstr "" #: ../../reference_manual/blending_modes/mix.rst:189 msgid "" "Overlay checks if the color on the upperlayer has a lightness above 0.5. If " "so, the pixel is blended like in Screen mode, if not the pixel is blended " "like in Multiply mode." msgstr "" #: ../../reference_manual/blending_modes/mix.rst:191 msgid "This is useful for deepening shadows and highlights." msgstr "" #: ../../reference_manual/blending_modes/mix.rst:196 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Overlay_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Overlay_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/mix.rst:196 msgid "Left: **Normal**. Right: **Overlay**." msgstr "Esquerra: **Normal**. Dreta: **Superposició**." #: ../../reference_manual/blending_modes/mix.rst:202 msgid "Parallel" msgstr "Paral·lel" #: ../../reference_manual/blending_modes/mix.rst:204 msgid "" "This one first takes the percentage in two decimal behind the comma for both " "layers. It then adds the two values. Divides 2 by the sum." msgstr "" #: ../../reference_manual/blending_modes/mix.rst:211 msgid "" ".. image:: images/blending_modes/" "Blending_modes_Parallel_Sample_image_with_dots.png" msgstr "" ".. image:: images/blending_modes/" "Blending_modes_Parallel_Sample_image_with_dots.png" #: ../../reference_manual/blending_modes/mix.rst:211 msgid "Left: **Normal**. Right: **Parallel**." msgstr "Esquerra: **Normal**. Dreta: **Paral·lel**." diff --git a/locale/ca/LC_MESSAGES/user_manual/loading_saving_brushes.po b/locale/ca/LC_MESSAGES/user_manual/loading_saving_brushes.po index bdb449e0c..60a51a72d 100644 --- a/locale/ca/LC_MESSAGES/user_manual/loading_saving_brushes.po +++ b/locale/ca/LC_MESSAGES/user_manual/loading_saving_brushes.po @@ -1,1269 +1,1257 @@ # Translation of docs_krita_org_user_manual___loading_saving_brushes.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: user_manual\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-04-21 03:37+0200\n" "PO-Revision-Date: 2019-04-21 17:38+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 18.12.3\n" #: ../../user_manual/loading_saving_brushes.rst:0 msgid ".. image:: images/en/Krita_4_0_dirty_preset_icon.png" msgstr ".. image:: images/en/Krita_4_0_dirty_preset_icon.png" #: ../../user_manual/loading_saving_brushes.rst:None msgid ".. image:: images/en/Krita_4_0_Brush_Settings_Layout.svg" msgstr ".. image:: images/en/Krita_4_0_Brush_Settings_Layout.svg" #: ../../user_manual/loading_saving_brushes.rst:1 msgid "" "Detailed guide on the brush settings dialog in Krita as well as how to make " "your own brushes and how to share them." msgstr "" "Guia detallada sobre el diàleg de configuració del pinzell al Krita, així " "sobre com crear els vostres propis pinzells i com compartir-los." #: ../../user_manual/loading_saving_brushes.rst:17 msgid "Loading and Saving Brushes" msgstr "Carregar i desar els pinzells" #: ../../user_manual/loading_saving_brushes.rst:19 msgid "" "In the real world, when painting or drawing, you don't just use one tool. " "You use pencils, erasers, paintbrushes, different types of paint, inks, " "crayons, etc. All these have different ways of making marks." msgstr "" "Al món real, quan es pinta o dibuixa, no només fareu servir una eina. " "Utilitzareu llapis, gomes d'esborrar, pinzells de pintura, diferents tipus " "de pintura, tintes, llapis de colors, etc. Totes elles tenen diferents " "maneres de fer les marques." #: ../../user_manual/loading_saving_brushes.rst:23 msgid "" "In a digital program like Krita you have something similar. We call this a " "brush engine. And much like how cars have different engines that give " "different feels when driving, or how pencils make distinctly different marks " "than rollerball pens, different brush engines have totally different feels." msgstr "" "En un programa digital com el Krita teniu quelcom similar. D'això en diem un " "motor de pinzell. I de la mateixa manera en què els automòbils tenen " "diferents motors que donen diferents sensacions en conduir, o com els llapis " "fan marques distintives diferents dels bolígrafs, els diferents motors de " "pinzell tenen comportaments diferents." #: ../../user_manual/loading_saving_brushes.rst:29 msgid "" "The brush engines have a lot of different settings as well. So, you can save " "those settings into presets." msgstr "" "Els motors de pinzell també tenen un munt d'ajustaments diferents. Per tant, " "podeu desar aquests ajustaments dintre dels predefinits." #: ../../user_manual/loading_saving_brushes.rst:32 msgid "" "Unlike Photoshop, Krita makes a difference between brush-tips and brush-" "presets. Tips are only a stamp of sorts, while the preset uses a tip and " "many other settings to create the full brush." msgstr "" "A diferència del Photoshop, el Krita diferencia entre els pinzells " "aconsellats i els pinzells predefinits. Els aconsellats només són una " "espècie de segell, mentre que el predefinit utilitza una punta i molts " "altres ajustaments per a crear el pinzell complet." #: ../../user_manual/loading_saving_brushes.rst:37 msgid "The Brush settings drop-down" msgstr "El llistat dels ajustaments del pinzell" #: ../../user_manual/loading_saving_brushes.rst:39 msgid "" "To start, the Brush Settings Editor panel can be accessed in the toolbar, " "between the :guilabel:`Blending Modes` button on the right and the :guilabel:" "`Patterns` button on the left. Alternately, you can use the function key :" "kbd:`F5` to open it." msgstr "" "Per a començar, des del plafó de l'Editor d'ajustaments del pinzell es pot " "accedir a la barra d'eines, entre el botó :guilabel:`Modes de barreja` a la " "dreta i el botó :guilabel:`Patrons` a l'esquerra. De manera alternativa, " "podeu utilitzar la tecla de funció :kbd:`F5` per obrir-lo." #: ../../user_manual/loading_saving_brushes.rst:44 msgid "" "When you open Brush Settings Editor panel you will see something like this:" msgstr "" "Quan obriu el plafó Editor d'ajustaments del pinzell, veureu quelcom així:" #: ../../user_manual/loading_saving_brushes.rst:48 msgid "Tour of the brush settings drop-down" msgstr "Recorregut pel llistat dels ajustaments del pinzell" #: ../../user_manual/loading_saving_brushes.rst:53 msgid "The brush settings drop-down is divided into six areas," msgstr "El llistat dels ajustaments del pinzell es divideix en sis àrees," #: ../../user_manual/loading_saving_brushes.rst:56 msgid "Section A - General Information" msgstr "Secció A - Informació general" #: ../../user_manual/loading_saving_brushes.rst:58 msgid "" "This contains the **Preset Icon**, **Live Brush Preview**, the **Preset " "Name**, the **Engine** name, and several buttons for saving, renaming, and " "reloading." msgstr "" "Conté la **Icona predefinida**, **Vista prèvia en viu del pinzell**, el " "**Nom predefinit**, el nom del **Motor** i diversos botons per a desar, " "canviar el nom i tornar a carregar." #: ../../user_manual/loading_saving_brushes.rst:62 msgid "" "Krita's brush settings are stored into the metadata of a 200x200 png (the " "KPP file), where the image in the png file becomes the preset icon. This " "icon is used everywhere in Krita, and is useful for differentiating brushes " "in ways that the live preview cannot." msgstr "" "Els ajustaments del pinzell del Krita s'emmagatzemen a les metadades d'un " "fitxer PNG de 200x200 (el fitxer KPP), on la imatge del fitxer PNG " "esdevindrà la icona predefinida. Aquesta icona s'utilitzarà a tot arreu al " "Krita, i és útil per a diferenciar els pinzells de les formes que la vista " "prèvia en viu no permet." #: ../../user_manual/loading_saving_brushes.rst:67 msgid "" "The live preview shows a stroke of the current brush as a little s-curve " "wiggle, with the pressure being non-existent on the left, and increasing to " "full pressure as it goes to the right. It can thus show the effect of the " "Pressure, Drawing Angle, Distance, Fade and Fuzzy Dab sensors, but none of " "the others. For some brush engines it cannot show anything. For the color " "smudge, filter brush and clone tool, it shows an alternating line pattern " "because these brush engines use the pixels already on canvas to change their " "effect." msgstr "" "La vista prèvia en viu mostra un traç del pinzell actual com una petita " "corba en forma de S, amb la pressió que al començament és inexistent a " "l'esquerra i que augmenta fins a aconseguir la pressió màxima a mesura que " "va cap a la dreta. D'aquesta manera, es pot mostrar l'efecte dels sensors de " "Pressió, Angle de dibuix, Distància, Esvaïment i Toc difús, però cap dels " "altres. Per a alguns motors de pinzell no es pot mostrar res. Per a les " "eines pinzell amb esborronat del color, amb filtratge i de clonat, es mostra " "un patró de línia altern perquè aquests motors de pinzell utilitzen els " "píxels que ja es troben en el llenç per a canviar el seu efecte." #: ../../user_manual/loading_saving_brushes.rst:75 msgid "" "After the preset name, there's a button for **renaming** the brush. This " "will save the brush as a new brush and blacklist the previous name." msgstr "" "Després del nom predefinit, hi ha un botó per a **reanomenar** el pinzell. " "Aquest desarà el pinzell com a un pinzell nou i posarà a la llista negra el " "nom anterior." #: ../../user_manual/loading_saving_brushes.rst:79 msgid "Engine" msgstr "Motor" #: ../../user_manual/loading_saving_brushes.rst:81 msgid "" "The engine of a brush is the underlying programming that generates the " "stroke from a brush. What that means is that different brush engines have " "different options and different results. You can see this as the difference " "between using crayons, pencils and inks, but because computers are maths " "devices, most of our brush engines produce different things in a more " "mathematical way." msgstr "" "El motor d'un pinzell és la programació subjacent que genera el traç del " "pinzell. El que això vol dir és que els diferents motors de pinzell tenen " "opcions diferents i resultats diferents. Ho podeu veure com la diferència " "entre utilitzar llapis de colors, llapis i tintes, però com que els " "ordinadors són dispositius matemàtics, la majoria dels nostres motors de " "pinzell produeixen coses diferents d'una manera més matemàtica." #: ../../user_manual/loading_saving_brushes.rst:88 msgid "" "For most artists the mathematical nature doesn't matter as much as the " "different textures and marks each brush engine, and each brush engine has " "its own distinct flavor and use, and can be further customized by modifying " "the options." msgstr "" "Per a la majoria dels artistes, la naturalesa matemàtica no importa tant com " "les diferents textures i marques de cada motor de pinzell, i cada motor de " "pinzell té el seu propi gust i ús, i es pot personalitzar encara més " "modificant les opcions." #: ../../user_manual/loading_saving_brushes.rst:94 msgid "Reloading" msgstr "Tornar a carregar" #: ../../user_manual/loading_saving_brushes.rst:96 msgid "" "If you change a preset, an icon will appear behind the engine name. This is " "the :guilabel:`reload` button. You can use it to revert to the original " "brush settings." msgstr "" "Si canvieu un predefinit, apareixerà una icona al darrere del nom del motor. " "Aquest és el botó :guilabel:`Torna a carregar`. Podeu utilitzar-lo per " "tornar als ajustaments originals del pinzell." #: ../../user_manual/loading_saving_brushes.rst:101 msgid "Saving a preset" msgstr "Desar un predefinit" #: ../../user_manual/loading_saving_brushes.rst:103 msgid "" "On the right, there's :guilabel:`Save New Brush Preset` and :guilabel:" "`Overwrite Brush`." msgstr "" "A la dreta, hi ha :guilabel:`Desa el pinzell predefinit nou` i :guilabel:" "`Sobreescriu el pinzell`." #: ../../user_manual/loading_saving_brushes.rst:106 msgid "" "This will only enable if there are any changes. Pressing this will override " "the current preset with the new settings, keeping the name and the icon " "intact. It will always make a timestamped back up in the resources folder." msgstr "" "Només estarà habilitat si hi ha algun canvi. En prémer-lo, se solaparà el " "predefinit actual amb els nous ajustaments, mantenint el nom i la icona " "intactes. Sempre es realitzarà una còpia de seguretat amb marca de temps a " "la carpeta de recursos." #: ../../user_manual/loading_saving_brushes.rst:108 msgid "Overwrite Brush" msgstr "Sobreescriu el pinzell" #: ../../user_manual/loading_saving_brushes.rst:111 msgid "" "Will take the current preset and all its changes and save it as a new " "preset. If no change was made, you will be making a copy of the current " "preset." msgstr "" "Prendrà el predefinit actual i tots els seus canvis i els desarà com a un " "predefinit nou. Si no s'ha produït cap canvi, farà una còpia del predefinit " "actual." #: ../../user_manual/loading_saving_brushes.rst:113 msgid "Save New Brush Preset" msgstr "Desa el pinzell predefinit nou" #: ../../user_manual/loading_saving_brushes.rst:115 msgid "" "Save new preset will call up the following window, with a mini scratch pad, " "and all sorts of options to change the preset icon:" msgstr "" "Desar un predefinit nou obrirà la següent finestra, amb un mini bloc des de " "zero i tot tipus d'opcions per a canviar la icona predefinida:" #: ../../user_manual/loading_saving_brushes.rst:119 msgid ".. image:: images/en/Krita_4_0_Save_New_Brush_Preset_Dialog.png" msgstr ".. image:: images/en/Krita_4_0_Save_New_Brush_Preset_Dialog.png" #: ../../user_manual/loading_saving_brushes.rst:120 msgid "" "The image on the left is a mini scratchpad, you can draw on it with the " "current brush, allowing small modifications on the fly." msgstr "" "L'àrea de l'esquerra és un mini bloc des de zero, podreu dibuixar-hi amb el " "pinzell actual, el qual us permetrà realitzar petites modificacions sobre la " "marxa." #: ../../user_manual/loading_saving_brushes.rst:124 msgid "" "The Name of your brush. This is also used for the KPP file. If there's " "already a brush with that name, it will effectively overwrite it." msgstr "" "El nom del vostre pinzell. També s'utilitzarà per al fitxer KPP. Si ja hi ha " "un pinzell amb aquest nom, el sobreescriurà de manera efectiva." #: ../../user_manual/loading_saving_brushes.rst:125 msgid "Brush Name" msgstr "Nom del pinzell" #: ../../user_manual/loading_saving_brushes.rst:127 msgid "Load Existing Thumbnail" msgstr "Carrega la miniatura existent" #: ../../user_manual/loading_saving_brushes.rst:128 msgid "This will load the existing thumbnail inside the preset." msgstr "Carregarà la miniatura existent dins del predefinit." #: ../../user_manual/loading_saving_brushes.rst:130 msgid "Load scratch pad thumbnail" msgstr "Carrega la miniatura des del bloc des de zero" #: ../../user_manual/loading_saving_brushes.rst:130 msgid "" "This will load the dashed area from the big scratch pad (Section C) into the " "thumbnail area." msgstr "" "Carregarà l'àrea discontínua des del bloc des de zero (Secció C) a dins de " "l'àrea de la miniatura." #: ../../user_manual/loading_saving_brushes.rst:132 msgid "Load Image" msgstr "Carrega una imatge" #: ../../user_manual/loading_saving_brushes.rst:133 msgid "With this you can choose an image from disk to load as a thumbnail." msgstr "" "Amb això podreu triar una imatge del disc per carregar-la com a miniatura." #: ../../user_manual/loading_saving_brushes.rst:134 msgid "Load from Icon Library" msgstr "Carrega des de la biblioteca d'icones" #: ../../user_manual/loading_saving_brushes.rst:135 msgid "This opens up the icon library." msgstr "Obrirà la biblioteca d'icones." #: ../../user_manual/loading_saving_brushes.rst:137 msgid "Clear Thumbnail" msgstr "Neteja la miniatura" #: ../../user_manual/loading_saving_brushes.rst:137 msgid "This will make the mini scratch pad white." msgstr "Farà que el mini bloc des de zero estigui en blanc." #: ../../user_manual/loading_saving_brushes.rst:140 msgid "The Icon Library" msgstr "La biblioteca d'icones" #: ../../user_manual/loading_saving_brushes.rst:142 msgid "To make making presets icons faster, Krita got an icon library." msgstr "" "Per a fer que les icones dels predefinits siguin més ràpides, el Krita " "disposa d'una biblioteca d'icones." #: ../../user_manual/loading_saving_brushes.rst:145 msgid ".. image:: images/en/Krita_4_0_Preset_Icon_Library_Dialog.png" msgstr ".. image:: images/en/Krita_4_0_Preset_Icon_Library_Dialog.png" #: ../../user_manual/loading_saving_brushes.rst:146 msgid "" "It allows you to select tool icons, and an optional small emblem. When you " "press :guilabel:`OK` it will load the resulting combination into the mini " "scratch pad and you can draw in the stroke." msgstr "" "Permet seleccionar la icona de l'eina i un petit emblema opcional. Quan " "premeu :guilabel:`D'acord` es carregarà la combinació resultant en el mini " "bloc des de zero i ja podreu dibuixar el traç." #: ../../user_manual/loading_saving_brushes.rst:150 msgid "" "If you go to your resources folder, there's a folder there called \"preset" "\\_icons\", and in this folder there are \"tool\\_icons\" and \"emblem" "\\_icons\". You can add semi-transparent pngs here and Krita will load those " "into the icon library as well so you can customize your icons even more!" msgstr "" "Si aneu a la vostra carpeta de recursos, hi haurà una carpeta anomenada " "«preset\\_icons», i en aquesta carpeta hi haurà «tool\\_icons» i «emblem" "\\_icons». Hi podreu afegir PNG semitransparents i el Krita també els " "carregarà a la biblioteca d'icones perquè pugueu personalitzar les vostres " "icones encara més!" #: ../../user_manual/loading_saving_brushes.rst:156 msgid "" "At the top right of the icon library, there are three sliders. They allow " "you to adjust the tool icon. The top two are the same Hue and Saturation as " "in HSL adjustment, and the lowest slider is a super simple levels filter. " "This is done this way because the levels filter allows maintaining the " "darkest shadows and brightest highlights on a tool icon, making it much " "better for quick adjustments." msgstr "" "A la part superior dreta de la biblioteca d'icones, hi ha tres controls " "lliscants. Permeten ajustar la icona de l'eina. Els dos primers són el " "mateix To i Saturació que en l'ajust HSL, i el control lliscant inferior és " "un filtre de nivells súper senzill. Això es fa d'aquesta manera perquè el " "filtre de nivells permet mantenir les ombres més fosques i els reflexos més " "brillants en una icona d'eina, el qual ho fa molt millor per a ajustos " "ràpids." #: ../../user_manual/loading_saving_brushes.rst:163 -#| msgid "" -#| "If you're done with everything, you can press :guilabel:`Save` in the :" -#| "guilabel:`Save New Preset` dialog and Krita will save the new brush." msgid "" "If you're done with everything, you can press :guilabel:`Save` in the :" "guilabel:`Save New Brush Preset` dialog and Krita will save the new brush." msgstr "" "Si heu acabat amb tot, podeu prémer :guilabel:`Desa` al diàleg :guilabel:" "`Desa el pinzell predefinit nou` i el Krita desarà el pinzell nou." #: ../../user_manual/loading_saving_brushes.rst:167 msgid "Section B - The Preset Chooser" msgstr "Secció B - El selector del predefinit" #: ../../user_manual/loading_saving_brushes.rst:169 msgid "" "The preset chooser is much the same as the preset docker and the preset drop-" "down on :kbd:`F6`. It's unique in that it allows you to filter by engine and " "this is also where you can create brushes for an engine from scratch." msgstr "" "El selector del predefinit és gairebé el mateix que l'acoblador Predefinits " "i la llista desplegable Predefinits sobre la tecla :kbd:`F6`. És únic, ja " "que permet filtrar per motor i també podreu crear pinzells per a un motor " "des de zero." #: ../../user_manual/loading_saving_brushes.rst:174 msgid "" "It is by default collapsed, so you will need to press the arrow at the top " "left of the brush engine to show it." msgstr "" "De manera predeterminada està col·lapsat, pel que haureu de prémer la fletxa " "a la part superior esquerra dels motors de pinzell per a que es mostri." #: ../../user_manual/loading_saving_brushes.rst:177 msgid "" "The top drop-down is set to “all” by default, which means it shows all " "engines. It then shows a tag section where you can select the tags, the " "preset list and the search bar." msgstr "" "El llistat superior està establert a «Tots» de manera predeterminada, el " "qual vol dir que mostra tots els motors. A continuació, mostra una secció " "d'etiquetes on podreu seleccionar les etiquetes, la llista de predefinits i " "la barra de cerca." #: ../../user_manual/loading_saving_brushes.rst:181 msgid "" "Underneath that there's a plus icon, which when pressed gives you the full " "list of Krita's engines. Selecting an engine from the list will show the " "brushes for that engine." msgstr "" "A sota hi ha una icona més, que quan es prem dóna la llista completa dels " "motors del Krita. En seleccionar un motor de la llista, es mostraran els " "pinzells per a aquest motor." #: ../../user_manual/loading_saving_brushes.rst:185 msgid "" "The trashcan icon does the same as it does in the preset docker: delete, or " "rather, blacklist a preset so it won't show up in the list." msgstr "" "La icona de la paperera fa el mateix que a l'acoblador Predefinits: elimina, " "o més aviat, inclou a la llista negra un predefinit de manera que no " "aparegui a la llista." #: ../../user_manual/loading_saving_brushes.rst:189 msgid "Section C - The Scratch pad" msgstr "Secció C - El bloc des de zero" #: ../../user_manual/loading_saving_brushes.rst:191 msgid "" "When you tweak your brushes, you want to be able to check what each setting " "does. That's why, to the right of the settings drop-down, there is a scratch " "pad." msgstr "" "Quan ajusteu els pinzells, voldreu poder comprovar què fa cada ajustament. " "Per això, a la dreta del llistat dels ajustaments, hi ha un bloc des de zero." #: ../../user_manual/loading_saving_brushes.rst:195 msgid "" "It is by default collapsed, so you will have to press the arrow at the top " "right of the brush settings to show it." msgstr "" "De manera predeterminada està col·lapsat, de manera que haureu de prémer la " "fletxa a la part superior dreta dels ajustaments del pinzell per a que es " "mostri." #: ../../user_manual/loading_saving_brushes.rst:198 -#| msgid "" -#| "When saving a new preset, you can choose to get the icon from the scratch " -#| "pad, this will load the dash area into the mini scratch pad of the Save " -#| "New Preset dialog." msgid "" "When saving a new preset, you can choose to get the icon from the scratch " "pad, this will load the dash area into the mini scratch pad of the Save New " "Brush Preset dialog." msgstr "" "En desar un predefinit nou, podreu triar obtenir la icona des del bloc des " "de zero. Això carregarà l'àrea del tauler en el mini bloc des de zero del " "diàleg Desa el pinzell predefinit nou." #: ../../user_manual/loading_saving_brushes.rst:202 -#| msgid "" -#| "The scratch pad has five buttons underneath it. These are in order for:" msgid "The scratch pad has four buttons underneath it. These are in order for:" msgstr "El bloc des de zero té cinc botons per sota. Aquests són:" #: ../../user_manual/loading_saving_brushes.rst:204 msgid "Showing the current brush image" msgstr "Mostra la imatge del pinzell actual" #: ../../user_manual/loading_saving_brushes.rst:206 msgid "Adding a gradient to the scratch pad (useful for smudge brushes)" msgstr "" "Afegeix un degradat al bloc des de zero (útil per als pinzells d'esborronar)" #: ../../user_manual/loading_saving_brushes.rst:207 msgid "Filling with the background color" msgstr "Omple amb el color de fons" #: ../../user_manual/loading_saving_brushes.rst:208 msgid "Clearing everything on the scratch pad" msgstr "Netejar-ho tot al bloc des de zero" #: ../../user_manual/loading_saving_brushes.rst:211 msgid "Section D - The Options List" msgstr "Secció D - La llista d'opcions" #: ../../user_manual/loading_saving_brushes.rst:213 msgid "" "The options, as stated above, are different per brush engine. These " "represent the different parameters, toggles and knobs that you can turn to " "make a brush preset unique. For a couple of options, the main things to " "change are sliders and check boxes, but for a lot of them, they use curves " "instead." msgstr "" "Les opcions, com s'ha indicat anteriorment, són diferents per a cada motor " "de pinzell. Aquestes representen els diferents paràmetres, commutadors i " "ordres que podeu alternar per a fer que un pinzell predefinit sigui únic. " "Per a un parell d'opcions, les coses principals que s'han de canviar són els " "controls lliscants i les caselles de selecció, però per a moltes d'elles, al " "seu lloc es fan servir corbes." #: ../../user_manual/loading_saving_brushes.rst:219 msgid "" "Some options can be toggled, as noted by the little check boxes next to " "them, but others, like flow and opacity are so fundamental to how the brush " "works, that they are always on." msgstr "" "Algunes opcions es poden alternar, com ho indiquen les caselles de selecció " "que hi ha al seu costat, però d'altres, com el flux i l'opacitat, són tan " "fonamentals per al funcionament del pinzell que sempre estaran activades." #: ../../user_manual/loading_saving_brushes.rst:223 msgid "" "The little padlock icon next to the options is for locking the brush. This " "has its own page." msgstr "" "La petita icona de cadenat que hi ha al costat de les opcions és per a " "bloquejar el pinzell. Això disposa la seva pròpia pàgina." #: ../../user_manual/loading_saving_brushes.rst:227 msgid "Section E - Option Configuration Widget" msgstr "Secció E - Estri per a la configuració de les opcions" #: ../../user_manual/loading_saving_brushes.rst:229 msgid "" "Where section D is the list of options, section E is the widget where you " "can change things." msgstr "" "On la secció D és la llista d'opcions, la secció E és l'estri on podreu " "canviar les coses." #: ../../user_manual/loading_saving_brushes.rst:233 msgid "Using sensor curves" msgstr "Emprar les corbes del sensor" #: ../../user_manual/loading_saving_brushes.rst:235 msgid "" "One of the big important things that make art unique to the artist who " "created it is the style of the strokes. Strokes are different because they " "differ in speed, rotation, direction, and the amount of pressure put onto " "the stylus. Because these are so important, we would want to customize how " "these values are understood in detail. The best way to do this is to use " "curves." msgstr "" "Una de les grans coses importants que fan que l'art sigui únic per a " "l'artista que el va crear, és l'estil dels traços. Els traços són diferents " "perquè difereixen en velocitat, gir, direcció i la quantitat de pressió " "aplicada al llapis. Com que són tan importants, ens agradaria personalitzar " "com s'entenen en detall aquests valors. La millor manera de fer-ho és " "emprant les corbes." #: ../../user_manual/loading_saving_brushes.rst:242 msgid "" "Curves show up with the size widget for example. With an inking brush, we " "want to have size mapped to pressure. Just toggling the size option in the " "option list will do that." msgstr "" "Les corbes es mostren amb l'estri de mida, per exemple. Amb un pinzell de " "tinta, volem que la mida estigui assignada a la pressió. Simplement ho farà " "canviant l'opció de mida a la llista d'opcions." #: ../../user_manual/loading_saving_brushes.rst:246 msgid "" "However, different people have different wrists and thus will press " "differently on their stylus. Someone who presses softly tends to find it " "easy to make thin strokes, but very difficult to make thick strokes. " "Conversely, someone who presses hard on their stylus naturally will have a " "hard time making thin strokes, but easily makes thick ones." msgstr "" "No obstant això, diferents persones tenen canells diferents i, per tant, " "pressionaran de manera diferent en el seu llapis. Algú que pressiona amb " "suavitat trobarà que és fàcil fer traços fins, però molt difícil fer traços " "gruixuts. Al revés, algú que pressiona amb força el seu llapis naturalment " "tindrà dificultats per a fer traços fins, però facilitat per als que siguin " "gruixuts." #: ../../user_manual/loading_saving_brushes.rst:252 msgid "" "Such a situation can be improved by using the curves to map pressure to " "output thinner lines or thicker ones." msgstr "" "Aquesta situació es pot millorar utilitzant les corbes per assignar la " "pressió a línies més fines o més gruixudes." #: ../../user_manual/loading_saving_brushes.rst:255 msgid "" "The brush settings curves even have quick curve buttons for these at the " "top. Someone who has a hard time making small strokes should try the second " "to last concave button, while someone who has a hard time making thick " "strokes should try the third button, the S shape." msgstr "" "Els ajustaments del pinzell per a les corbes tenen fins i tot botons de " "corba ràpida a la part superior. Algú que té dificultats per a fer traços " "fins hauria de provar el penúltim botó còncau, mentre que algú que té " "dificultats per a fer traços gruixuts hauria de provar el tercer botó, la " "forma S." #: ../../user_manual/loading_saving_brushes.rst:260 msgid "Underneath the curve widget there are two more options:" msgstr "Sota l'estri de corbes hi ha dues opcions més:" #: ../../user_manual/loading_saving_brushes.rst:263 msgid "" "This is for the list of sensors. Toggling this will make all the sensors use " "the same curve. Unchecked, all checked sensors will have separate curves." msgstr "" "Això és per a la llista de sensors. A l'alternar-ho, tots els sensors " "utilitzaran la mateixa corba. Sense marcar, tots els sensors marcats tindran " "corbes separades." #: ../../user_manual/loading_saving_brushes.rst:264 msgid "Share Curves across all settings" msgstr "Comparteix la corba amb tots els ajustaments" #: ../../user_manual/loading_saving_brushes.rst:267 msgid "" "This indicates how the multiple values of the sensor curves are used. The " "curves always go from 0 to 1.0, so if one curve outputs 0.5 and the other " "0.7, then..." msgstr "" "Això indica com s'utilitzaran els múltiples valors de les corbes del sensor. " "Les corbes sempre van de 0 a 1,0, de manera que si una corba genera 0,5 i " "l'altra 0,7, llavors..." #: ../../user_manual/loading_saving_brushes.rst:271 msgid "Multiply" msgstr "Multiplica" #: ../../user_manual/loading_saving_brushes.rst:272 msgid "Will multiply the two values, 0.5\\*0.7 = 0.35." msgstr "Multiplicarà els dos valors, 0,5\\*0,7 = 0,35." #: ../../user_manual/loading_saving_brushes.rst:274 msgid "Addition" msgstr "Addició" #: ../../user_manual/loading_saving_brushes.rst:274 msgid "" "Will add the two to a maximum of 1.0, so 0.5+0.7 = 1.2, which is then capped " "at 1.0." msgstr "" "S'afegiran els dos a un màxim d'1,0, de manera que 0,5+0,7 = 1,2, el qual es " "limitarà a 1,0." #: ../../user_manual/loading_saving_brushes.rst:277 msgid "Maximum" msgstr "Màxim" #: ../../user_manual/loading_saving_brushes.rst:277 msgid "" "Will compare the two and pick the largest. So in the case of 0.5 and 0.7, " "the result is 0.7." msgstr "" "Compararà els dos i triarà el més gran. Així que en el cas de 0,5 i 0,7, el " "resultat serà 0,7." #: ../../user_manual/loading_saving_brushes.rst:280 msgid "Minimum" msgstr "Mínim" #: ../../user_manual/loading_saving_brushes.rst:280 msgid "" "Will compare the two and pick the smallest. So in the case of 0.5 and 0.7, " "the result is 0.5." msgstr "" "Compararà el dos i triarà el més petit. Així que en el cas de 0,5 i 0,7, el " "resultat serà 0,5." #: ../../user_manual/loading_saving_brushes.rst:283 msgid "Will subtract the smallest value from the largest, so 0.7-0.5 = 0.2." msgstr "Restarà el valor més petit del més gran, de manera que 0,7-0,5 = 0,2." #: ../../user_manual/loading_saving_brushes.rst:284 msgid "Curves Calculation Mode" msgstr "Mode de càlcul de les corbes" #: ../../user_manual/loading_saving_brushes.rst:284 msgid "Difference" msgstr "Diferència" #: ../../user_manual/loading_saving_brushes.rst:286 msgid "It's maybe better to see with the following example:" msgstr "Potser serà millor veure-ho amb el següent exemple:" #: ../../user_manual/loading_saving_brushes.rst:289 msgid ".. image:: images/en/Krita_4_0_brush_curve_calculation_mode.png" msgstr ".. image:: images/en/Krita_4_0_brush_curve_calculation_mode.png" #: ../../user_manual/loading_saving_brushes.rst:290 msgid "" "The first two are regular, the rest with different multiplication types." msgstr "" "Els dos primers són normals, la resta amb diferents tipus de multiplicació." #: ../../user_manual/loading_saving_brushes.rst:292 msgid "Is a brush with size set to the distance sensor." msgstr "És un pinzell amb la mida establerta al sensor de la distància." #: ../../user_manual/loading_saving_brushes.rst:293 msgid "Is a brush with the size set to the fade sensor." msgstr "És un pinzell amb la mida establerta al sensor de l'esvaïment." #: ../../user_manual/loading_saving_brushes.rst:294 msgid "The size is calculated from the fade and distance sensors multiplied." msgstr "" "La mida es calcula a partir dels sensors d'esvaïment i de la distància " "multiplicats." #: ../../user_manual/loading_saving_brushes.rst:295 msgid "" "The size is calculated from the fade and distance sensors added to each " "other. Notice how thick it is." msgstr "" "La mida es calcula a partir dels sensors d'esvaïment i de la distància " "sumats l'un a l'altre. Fixeu-vos el gruix que té." #: ../../user_manual/loading_saving_brushes.rst:297 msgid "" "The size takes the maximum value from the values of the fade and distance " "sensors." msgstr "" "La mida prendrà el valor màxim des dels valors dels sensors d'esvaniment i " "distància." #: ../../user_manual/loading_saving_brushes.rst:299 msgid "" "The size takes the minimum value from the values of the fade and distance " "sensors." msgstr "" "La mida prendrà el valor mínim des dels valors dels sensors d'esvaniment i " "distància." #: ../../user_manual/loading_saving_brushes.rst:301 msgid "" "The size is calculated by having the largest of the values subtracted with " "the smallest of the values." msgstr "" "La mida es calcularà en tenir el més gran dels valors restat amb el menor." #: ../../user_manual/loading_saving_brushes.rst:305 msgid "Section F - Miscellaneous options" msgstr "Secció F - Opcions diverses" #: ../../user_manual/loading_saving_brushes.rst:308 msgid "" "This enables dirty presets. Dirty presets store the tweaks you make as long " "as this session of Krita is active. After that, they revert to default. " "Dirtied presets can be recognized by the icon in the top-left of the preset." msgstr "" "Això permet predefinits en brut. Els predefinits en brut emmagatzemen els " "ajustos que realitzeu mentre aquesta sessió del Krita estigui activa. " "Després d'això, tornaran als valors predeterminats. Els predefinits en brut " "es poden reconèixer per la icona a la part superior esquerra del predefinit." #: ../../user_manual/loading_saving_brushes.rst:316 msgid "Temporarily Save Tweaks to Preset (Dirty Presets)" msgstr "" "Desa temporalment les deformacions als predefinits (predefinits en brut)" #: ../../user_manual/loading_saving_brushes.rst:316 msgid "" "The icon in the top left of the first two presets indicate it is “Dirty”, " "meaning there are tweaks made to the preset." msgstr "" "La icona a la part superior esquerra dels dos primers predefinits indica que " "són «en brut», el qual vol dir que s'han realitzat ajustos al predefinit." #: ../../user_manual/loading_saving_brushes.rst:319 msgid "Eraser Switch Size" msgstr "Canvia la mida de l'esborrador" #: ../../user_manual/loading_saving_brushes.rst:319 msgid "" "This switches the brush to a separately stored size when using the :kbd:`E` " "key." msgstr "" "Això canvia el pinzell a una mida emmagatzemada per separat quan s'utilitza " "la tecla :kbd:`E`." #: ../../user_manual/loading_saving_brushes.rst:321 msgid "Eraser Switch Opacity" msgstr "Canvia l'opacitat de l'esborrador" #: ../../user_manual/loading_saving_brushes.rst:322 msgid "Same as above, but then with Eraser opacity." msgstr "Igual que l'anterior, però amb l'opacitat de l'esborrador." #: ../../user_manual/loading_saving_brushes.rst:324 msgid "" "This allows you to toggle instant preview on the brush. The Instant Preview " "has a super-secret feature: when you press the instant preview label, and " "then right click it, it will show a threshold slider. This slider determines " "at what brush size instant preview is activated for the brush. This is " "useful because small brushes can be slower with instant preview, so the " "threshold ensures it only activates when necessary." msgstr "" "Això permet alternar la vista prèvia instantània del pinzell. La vista " "prèvia instantània té una característica súper secreta: quan premeu " "l'etiqueta de vista prèvia instantània, i després feu clic dret, es mostrarà " "un control lliscant del llindar. Aquest control lliscant determina en quina " "mida del pinzell s'activarà la vista prèvia per al pinzell. Això és útil " "perquè els pinzells petits poden ser més lents amb la vista prèvia " "instantània, de manera que el llindar garanteix que només s'activi quan " "sigui necessari." #: ../../user_manual/loading_saving_brushes.rst:330 msgid "Instant Preview" msgstr "Vista prèvia instantània" #: ../../user_manual/loading_saving_brushes.rst:333 msgid "The On-canvas brush settings" msgstr "Els ajustaments del pinzell al llenç" #: ../../user_manual/loading_saving_brushes.rst:335 msgid "" "There are on-canvas brush settings. If you open up the pop-up palette, there " "should be an icon on the bottom-right. Press that to show the on-canvas " "brush settings. You will see several sliders here, to quickly make small " "changes." msgstr "" "Hi ha ajustaments del pinzell al llenç. Si obriu la paleta emergent, hi " "hauria d'haver una icona a la part inferior dreta. Premeu-la per a mostrar " "els ajustaments del pinzell al llenç. Hi veureu diversos controls lliscants, " "per a fer petits canvis amb rapidesa." #: ../../user_manual/loading_saving_brushes.rst:340 msgid "" "At the top it shows the currently active preset. Next to that is a settings " "button, click that to get a list of settings that can be shown and organized " "for the given brush engine. You can use the up and down arrows to order " "their position, and then left and right arrows to add or remove from the " "list. You can also drag and drop." msgstr "" "A la part superior es mostra el predefinit actualment actiu. Al costat " "d'aquest hi ha un botó d'ajustaments, feu-hi clic per obtenir una llista " "dels ajustaments que es poden mostrar i organitzar per al motor de pinzell " "indicat. Feu servir les fletxes cap amunt i cap avall per ordenar la seva " "posició, i després les fletxes cap a l'esquerra i cap a la dreta per afegir " "o eliminar de la llista. També podeu arrossegar i deixar anar." #: ../../user_manual/loading_saving_brushes.rst:347 msgid "Making a Brush Preset" msgstr "Crear un pinzell predefinit" #: ../../user_manual/loading_saving_brushes.rst:349 msgid "Now, let's make a simple brush to test the waters with:" msgstr "Ara, crearem un pinzell senzill per a provar les aigües amb:" #: ../../user_manual/loading_saving_brushes.rst:352 msgid "Getting a default for the brush engine." msgstr "Obtenir un valor predeterminat per al motor de pinzell." #: ../../user_manual/loading_saving_brushes.rst:354 msgid "First, open the settings with :kbd:`F5`." msgstr "Primer, obriu els ajustaments amb la tecla de funció :kbd:`F5`." #: ../../user_manual/loading_saving_brushes.rst:356 msgid "" "Then, press the arrow on the upper left to open the preset chooser. There, " "press the “+” icon to get a list of engines. For this brush we're gonna make " "a pixel brush." msgstr "" "Després, premeu la fletxa a la part superior esquerra per obrir el selector " "de predefinits. Allà, premeu la icona «+» per obtenir una llista dels " "motors. Per a aquest pinzell crearem un pinzell de píxels." #: ../../user_manual/loading_saving_brushes.rst:361 msgid "Example: Making an inking brush" msgstr "Exemple: crear un pinzell de tinta" #: ../../user_manual/loading_saving_brushes.rst:363 msgid "" "Draw on the scratch pad to see what the current brush looks like. If done " "correctly, you should have a 5px wide brush that has pressure set to opacity." msgstr "" "Dibuixeu al bloc des de zero per a veure com es veurà el pinzell actual. Si " "es fa correctament, hauríeu de tenir una amplada del pinzell de 5 px que " "tindrà la pressió establerta a opacitat." #: ../../user_manual/loading_saving_brushes.rst:366 msgid "" "Let us turn off the opacity first. Click on the :ref:`opacity " "` option in the right-hand list. The settings should " "now be changed to a big curve. This is the sensor curve." msgstr "" "Primer desactivarem l'opacitat. Feu clic a l'opció :ref:`Opacitat " "` des de la llista al costat dret. Els ajustaments " "ara s'haurien d'haver canviat a una gran corba. Aquesta serà la corba del " "sensor." #: ../../user_manual/loading_saving_brushes.rst:370 msgid "Uncheck the :guilabel:`Enable Pen Settings` checkbox." msgstr "" "Desmarqueu la casella de selecció :guilabel:`Activa els ajustaments per al " "llapis`." #: ../../user_manual/loading_saving_brushes.rst:371 msgid "" "Test on the scratch pad... there still seems to be something affecting " "opacity. This is due to the :ref:`flow ` option." msgstr "" "Proveu al bloc des de zero... encara sembla haver-hi quelcom que afecta " "l'opacitat. Això es deu a l'opció :ref:`Flux `." #: ../../user_manual/loading_saving_brushes.rst:375 msgid "" "Select the Flow option from the list on the right hand. Flow is like " "Opacity, except that Flow is per dab, and opacity is per stroke." msgstr "" "Seleccioneu l'opció Flux des de la llista al costat dret. El flux és com " "l'opacitat, excepte que el flux és per al toc i l'opacitat és per al traç." #: ../../user_manual/loading_saving_brushes.rst:377 msgid "" "Uncheck the :guilabel:`Enable Pen Settings` checkbox here as well. Test " "again." msgstr "" "Desmarqueu també la casella de selecció :guilabel:`Activa els ajustaments " "per al llapis`. Intenteu-ho de nou." #: ../../user_manual/loading_saving_brushes.rst:378 msgid "" "Now you should be getting somewhere towards an inking brush. It is still too " "small however, and kinda grainy looking. Click :ref:`Brush Tip " "` in the brush engine options." msgstr "" "Ara hauríeu d'estar arribant a algun lloc amb un pinzell de tinta. Encara és " "massa petit i sembla granulat. Feu clic a :ref:`Punta del pinzell " "` a les opcions del motor de pinzell." #: ../../user_manual/loading_saving_brushes.rst:381 msgid "" "Here, the diameter is the size of the brush-tip. You can touch the slider " "change the size, or right-click it and type in a value. Set it to 25 and " "test again. It should be much better." msgstr "" "Aquí, el diàmetre serà la mida de la punta del pinzell. Podeu tocar el " "control lliscant per a canviar la mida, o fer-hi clic dret i escriure un " "valor. Establiu-ho a 25 i torneu-ho a provar. Hauria de ser molt millor." #: ../../user_manual/loading_saving_brushes.rst:384 msgid "" "Now to make the brush feel a bit softer, turn down the fade parameter to " "about 0.9. This'll give the *brush mask* a softer edge." msgstr "" "Ara, per fer que el pinzell se senti una mica més suau, baixeu el paràmetre " "de l'esvaïment a aproximadament 0,9. Això li donarà a la *màscara del " "pinzell* una vora més suau." #: ../../user_manual/loading_saving_brushes.rst:386 msgid "" "If you test again, you'll notice the fade doesn't seem to have much effect. " "This has to do with the spacing of the dabs: The closer they are together, " "the harder the line is. By default, this is 0.1, which is a bit low. If you " "set it to 10 and test, you'll see what kind of effect spacing has. The :ref:" "`Auto ` checkbox changes the way the spacing is calculated, " "and Auto Spacing with a value of 0.8 is the best value for inking brushes. " "Don't forget that you can use right-click to type in a value." msgstr "" "Si torneu a realitzar la prova, notareu que l'esvaïment no sembla tenir " "gaire efecte. Això té a veure amb l'espaiat dels tocs: com més a prop estan, " "més dura és la línia. De manera predeterminada, això és 0,1, el qual és una " "mica baix. Si l'establiu a 10 i ho proveu, veureu quin tipus d'efecte té " "l'espaiat. La casella de selecció :ref:`Automàtic ` canviarà " "la manera en què es calcula l'espaiat, i l'Espaiat automàtic amb un valor de " "0,8 és el millor valor per als pinzells de tinta. Recordeu que podeu fer " "servir el clic dret per a escriure un valor." #: ../../user_manual/loading_saving_brushes.rst:395 msgid "" "Now, when you test, the fade seems to have a normal effect... except on the " "really small sizes, which look pixelly. To get rid of that, check the anti-" "aliasing check box. If you test again, the lines should be much nicer now." msgstr "" "Ara, quan realitzeu la prova, l'esvaïment semblarà tenir un efecte normal... " "excepte en les mides realment petites, les quals semblen pixelades. Per a " "desfer això, marqueu la casella de selecció Antialiàsing. Si torneu a " "provar, ara les línies haurien de ser molt més agradables." #: ../../user_manual/loading_saving_brushes.rst:401 msgid "Saving the new Brush" msgstr "Desar el pinzell nou" # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/loading_saving_brushes.rst:403 -#| msgid "" -#| "When you're satisfied, go to the upper left and select :guilabel::`Save " -#| "new preset`." msgid "" "When you're satisfied, go to the upper left and select :guilabel:`Save New " "Brush Preset`." msgstr "" "Quan estigueu satisfet, aneu a la part superior esquerra i seleccioneu :" "guilabel:`Desa el pinzell predefinit nou`." #: ../../user_manual/loading_saving_brushes.rst:406 msgid "" "You will get the save preset dialog. Name the brush something like “My " "Preset”. Then, select :guilabel:`Load from Icon Library` to get the icon " "library. Choose a nice tool icon and press :guilabel:`OK`." msgstr "" "Obtindreu el diàleg per a desar el predefinit. El nom del pinzell serà " "quelcom com «El meu predefinit». Després, seleccioneu guilabel:`Carrega des " "de la biblioteca d'icones` per obtenir la biblioteca d'icones. Trieu una " "bonica icona d'eina i premeu :guilabel:`D'acord`." #: ../../user_manual/loading_saving_brushes.rst:410 msgid "" "The icon will be loaded into the mini scratch pad on the left. Now doodle a " "nice stroke next to it. If you feel you messed up, just go back to the icon " "library to load a new icon." msgstr "" "La icona es carregarà a dins del mini bloc des de zero de l'esquerra. Ara " "gargotegeu-hi un bon traç. Si sentiu que heu comès un error, torneu a la " "biblioteca d'icones per a carregar una icona nova." #: ../../user_manual/loading_saving_brushes.rst:414 msgid "Finally press :guilabel:`Save`, and your brush should be done." msgstr "Finalment, premeu :guilabel:`Desa` i es crearà el vostre pinzell." #: ../../user_manual/loading_saving_brushes.rst:416 msgid "You can further modify your inking brush by..." msgstr "" "Encara podreu modificar una mica més el vostre pinzell de tinta per a..." #: ../../user_manual/loading_saving_brushes.rst:419 msgid "" "Changing the amount of pressure you need to put on a brush to make it full " "size." msgstr "" "Canviar la quantitat de pressió que necessitareu aplicar al pinzell perquè " "sigui de mida completa." #: ../../user_manual/loading_saving_brushes.rst:419 msgid "" "To do this, select the :ref:`size ` option, and press the " "pressure sensor from the list next to the curve. The curve should look like " "a straight line. Now if you want a brush that gets big with little pressure, " "tick on the curve to make a point, and drag the point to the upper-left. The " "more the point is to the upper-left, the more extreme the effect. If you " "want instead a brush that you have to press really hard on to get to full " "size, drag the dot to the lower-right. Such a brush is useful for fine " "details. Don't forget to save the changes to your brush when done." msgstr "" "Per a fer això, seleccioneu l'opció :ref:`Mida ` i premeu el " "sensor de pressió des de la llista al costat de la corba. La corba s'hauria " "de veure com una línia recta. Ara, si voleu un pinzell que es faci gran amb " "poca pressió, marqueu la corba per a fer un punt i arrossegueu-la cap a la " "part superior esquerra. Com més gran sigui el punt a la part superior " "esquerra, més extrem serà l'efecte. Si, en canvi, voleu un pinzell en el " "qual s'hagi de prémer molt fort per arribar a la mida completa, arrossegueu " "el punt cap a la part inferior dreta. Aquest pinzell serà útil per a detalls " "fins. No oblideu desar els canvis per al vostre pinzell quan acabeu." #: ../../user_manual/loading_saving_brushes.rst:422 msgid "Making the fine lines look even softer by using the flow option." msgstr "" "Fer que les línies fines resultin encara més suaus mitjançant l'opció del " "flux." #: ../../user_manual/loading_saving_brushes.rst:422 msgid "" "To do this, select the flow option, and turn back on the :guilabel:`Enable " "Pen Settings` check box. Now if you test this, it is indeed a bit softer, " "but maybe a bit too much. Click on the curve to make a dot, and drag that " "dot to the top-left, half-way the horizontal of the first square of the " "grid. Now, if you test, the thin lines are much softer, but the hard your " "press, the harder the brush becomes." msgstr "" "Per a fer-ho, seleccioneu l'opció Flux i torneu a activar la casella de " "selecció :guilabel:`Activa els ajustaments per al llapis`. Ara, si ho " "proveu, serà una mica més suau, però potser massa. Feu clic a la corba per a " "fer un punt i arrossegueu-lo a la part superior esquerra, a la meitat de " "l'horitzontal del primer quadrat de la quadrícula. Ara, si ho proveu, les " "línies fines seran molt més suaus, però com més forta sigui la vostra " "pressió, més dur es tornarà el pinzell." #: ../../user_manual/loading_saving_brushes.rst:425 msgid "Sharing Brushes" msgstr "Compartir els pinzells" #: ../../user_manual/loading_saving_brushes.rst:427 msgid "" "Okay, so you've made a new brush and want to share it. There are several " "ways to share a brush preset." msgstr "" "Bé, així que heu creat un pinzell nou i voleu compartir-lo. Hi ha diverses " "maneres de compartir un pinzell predefinit." #: ../../user_manual/loading_saving_brushes.rst:430 msgid "" "The recommended way to share brushes and presets is by using the resource " "bundle system. We have detailed instructions on how to use them on the :ref:" "`resource management page `." msgstr "" "La manera recomanada de compartir pinzells i predefinits és utilitzant el " "sistema per a paquets de recursos. Tenim instruccions detallades sobre com " "emprar-lo a la :ref:`pàgina per a la gestió dels recursos " "`." #: ../../user_manual/loading_saving_brushes.rst:434 msgid "" "However, there are various old-fashioned ways of sharing brushes that can be " "useful when importing and loading very old packs:" msgstr "" "No obstant això, hi ha diverses maneres antigues de compartir els pinzells " "que poden ser útils en importar i carregar paquets molt antics:" #: ../../user_manual/loading_saving_brushes.rst:438 msgid "Sharing a single preset" msgstr "Compartir un sol predefinit" #: ../../user_manual/loading_saving_brushes.rst:440 msgid "There are three types of resources a single preset can take:" msgstr "Hi ha tres tipus de recursos que poden tenir un sol predefinit:" #: ../../user_manual/loading_saving_brushes.rst:442 msgid "" "A Paintoppreset file: This is the preset proper, with the icon and the " "curves stored inside." msgstr "" "Un fitxer de predefinit per a la pintura: aquest és el predefinit pròpiament " "dit, amb la icona i les corbes a dins." #: ../../user_manual/loading_saving_brushes.rst:444 msgid "" "A Brush file: This is the brush tip. When using masked brushes, there's two " "of these." msgstr "" "Un fitxer de pinzell: és la punta del pinzell. Quan utilitzeu pinzells " "emmascarats, n'hi haurà dos d'aquests." #: ../../user_manual/loading_saving_brushes.rst:446 msgid "A Pattern file: this is when you are using textures." msgstr "Un fitxer de patró: això és quan empreu textures." #: ../../user_manual/loading_saving_brushes.rst:448 msgid "" "So when you have a brush that uses unique predefined tips for either brush " "tip or masked brush, or unique textures you will need to share those " "resources as well with the other person." msgstr "" "Per tant, quan tingueu un pinzell que faci servir puntes predefinides " "úniques per a la punta del pinzell o un pinzell emmascarat, o textures " "úniques, i necessiteu compartir aquests recursos amb alguna altra persona." #: ../../user_manual/loading_saving_brushes.rst:452 msgid "" "To find those resources, go to :menuselection:`Settings --> Manage Resources " "--> Open Resource Folder`." msgstr "" "Per a trobar aquests recursos, aneu a :menuselection:`Arranjament --> " "Gestiona els recursos --> Obre la carpeta de recursos`." #: ../../user_manual/loading_saving_brushes.rst:454 msgid "" "There, the preset file will be inside paintoppresets, the brush tips inside " "brushes and the texture inside patterns." msgstr "" "Allà, el fitxer del predefinit estarà dins de la carpeta " "«paintoppresets» (predefinits de pintura), les puntes del pinzell dins de la " "carpeta «brushes» (pinzells) i la textura dins de la carpeta " "«patterns» (patrons)." #: ../../user_manual/loading_saving_brushes.rst:458 msgid "Importing a single KPP file." msgstr "Importar un únic fitxer KPP." #: ../../user_manual/loading_saving_brushes.rst:460 msgid "" "Now, if you want to use the single preset, you should go to the preset " "chooser on :kbd:`F6` and press the folder icon there. This will give a file " "dialog. Navigate to the kpp file and open it to import it." msgstr "" "Ara, si voleu utilitzar un únic predefinit, haureu d'anar al selector de " "predefinits amb la drecera :kbd:`F6` i prémer la icona de carpeta. Això " "oferirà un diàleg de fitxers. Aneu al fitxer KPP i obriu-lo per importar." # skip-rule: t-acc_obe #: ../../user_manual/loading_saving_brushes.rst:464 msgid "" "If there are brush tips and patterns coming with the file, do the same with " "pattern via the pattern docker, and for the brush-tip go to the settings " "drop-down (:kbd:`F5`) and then go to the “brush-tip” option. There, select " "predefined brush, and then the “import” button to call up the file dialog." msgstr "" "Si hi ha puntes de pinzell i patrons que vénen amb el fitxer, feu el mateix " "amb el patró a través de l'acoblador Patró, i per a la punta del pinzell " "aneu a la llista d'ajustaments (:kbd:`F5`) i després aneu a l'opció «punta " "del pinzell». Allà, seleccioneu el pinzell predefinit i després el botó " "«Importa» per obrir el diàleg de fitxers." #: ../../user_manual/loading_saving_brushes.rst:471 msgid "Sharing via ZIP (old-fashioned)" msgstr "Compartir mitjançant ZIP (antiquat)" #: ../../user_manual/loading_saving_brushes.rst:473 msgid "" "Sharing via ZIP should be replaced with resource bundles, but older brush " "packs are stored in zip files." msgstr "" "El compartir mitjançant ZIP s'hauria de substituir amb paquets de recursos, " "però els paquets de pinzell més antics estan emmagatzemats en fitxers ZIP." #: ../../user_manual/loading_saving_brushes.rst:477 msgid "Using a ZIP with the relevant files." msgstr "Utilitzar un ZIP amb els fitxers pertinents." #: ../../user_manual/loading_saving_brushes.rst:479 msgid "" "Go to :menuselection:`Settings --> Manage Resources --> Open Resource " "Folder` to open the resource folder." msgstr "" "Aneu a :menuselection:`Arranjament --> Gestiona els recursos --> Obre la " "carpeta de recursos` per obrir la carpeta de recursos." #: ../../user_manual/loading_saving_brushes.rst:480 msgid "Then, open up the zip file." msgstr "A continuació, obriu el fitxer ZIP." #: ../../user_manual/loading_saving_brushes.rst:481 msgid "" "Copy the brushes, paintoppresets and patterns folders from the zip file to " "the resource folder. You should get a prompt to merge the folders, agree to " "this." msgstr "" "Copieu les carpetes «brushes» (pinzells), «paintoppresets» (predefinits de " "pintura) i «patterns» (patrons) des del fitxer ZIP a la carpeta " "«resource» (recursos). Hauríeu d'obtenir un avís per a fusionar les " "carpetes, accepteu-ho." #: ../../user_manual/loading_saving_brushes.rst:484 msgid "Restart Krita." msgstr "Torneu a iniciar el Krita." #: ../../user_manual/loading_saving_brushes.rst:485 msgid "Enjoy your brushes!" msgstr "Gaudiu dels vostres pinzells!" diff --git a/locale/ca/LC_MESSAGES/user_manual/painting_with_assistants.po b/locale/ca/LC_MESSAGES/user_manual/painting_with_assistants.po index b0e0e9ea4..0e9a59831 100644 --- a/locale/ca/LC_MESSAGES/user_manual/painting_with_assistants.po +++ b/locale/ca/LC_MESSAGES/user_manual/painting_with_assistants.po @@ -1,595 +1,596 @@ # Translation of docs_krita_org_user_manual___painting_with_assistants.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: user_manual\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-03-04 03:37+0100\n" "PO-Revision-Date: 2019-04-21 17:45+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 18.12.3\n" #: ../../:1 msgid ".. image:: images/en/Assistants_fish-eye_2_02.png" msgstr ".. image:: images/en/Assistants_fish-eye_2_02.png" #: ../../user_manual/painting_with_assistants.rst:2 msgid "How to use the painting assistants in Krita to draw perspectives." msgstr "" "Com utilitzar els assistents de pintura al Krita per a dibuixar perspectives." #: ../../user_manual/painting_with_assistants.rst:17 msgid "Painting with Assistants" msgstr "Pintar amb assistents" #: ../../user_manual/painting_with_assistants.rst:19 msgid "" "The assistant system allows you to have a little help while drawing straight " "lines or circles." msgstr "" "El sistema d'assistents permet tenir una mica d'ajuda mentre dibuixeu línies " "rectes o cercles." #: ../../user_manual/painting_with_assistants.rst:22 msgid "" "They can function as a preview shape, or you can snap onto them with the " "freehand brush tool. In the tool options of free hand brush, you can toggle :" "guilabel:`Snap to Assistants` to turn on snapping." msgstr "" "Poden funcionar com una forma de vista prèvia, o podeu ajustar-los amb " "l'eina del pinzell a mà alçada. En les Opcions de l'eina per al pinzell a mà " -"alçada, podreu alternar :guilabel:`Ajusta als assistents` per activar l'ajust." +"alçada, podreu alternar :guilabel:`Ajusta als assistents` per activar " +"l'ajust." #: ../../user_manual/painting_with_assistants.rst:30 msgid "" ".. image:: images/en/Krita_basic_assistants.png\n" " :alt: Krita's vanishing point assistants in action" msgstr "" ".. image:: images/en/Krita_basic_assistants.png\n" " :alt: Assistents en acció del punt de fuga al Krita" #: ../../user_manual/painting_with_assistants.rst:30 msgid "Krita's vanishing point assistants in action" msgstr "Assistents en acció del punt de fuga al Krita." #: ../../user_manual/painting_with_assistants.rst:32 msgid "The following assistants are available in Krita:" msgstr "En el Krita hi ha disponibles els següents assistents:" #: ../../user_manual/painting_with_assistants.rst:35 msgid "Types" msgstr "Tipus" #: ../../user_manual/painting_with_assistants.rst:37 msgid "" "There are several types in Krita. You can select a type of assistant via the " "tool options docker." msgstr "" "Hi ha diversos tipus en el Krita. Podreu seleccionar un tipus d'assistent a " "través de l'acoblador Opcions de l'eina." #: ../../user_manual/painting_with_assistants.rst:43 msgid "Ellipse" msgstr "El·lipse" #: ../../user_manual/painting_with_assistants.rst:45 msgid "An assistant for drawing ellipses and circles." msgstr "Assistent per a dibuixar el·lipses i cercles." #: ../../user_manual/painting_with_assistants.rst:47 msgid "" "This assistant consists of three points: the first two are the axis of the " "ellipse, and the last one is to determine its width." msgstr "" "Aquest assistent consta de tres punts: els dos primers són l'eix de " "l'el·lipse i l'últim és per a determinar la seva amplada." #: ../../user_manual/painting_with_assistants.rst:51 msgid "" "The same an ellipse, but allows for making ellipses that are concentric to " "each other." msgstr "" "El mateix que una el·lipse, però permet crear el·lipsis que són " "concèntriques entre si." #: ../../user_manual/painting_with_assistants.rst:52 msgid "Concentric Ellipse" msgstr "El·lipse concèntrica" #: ../../user_manual/painting_with_assistants.rst:54 #: ../../user_manual/painting_with_assistants.rst:144 msgid "" "If you press :kbd:`Shift` while holding the first two handles, they will " "snap to perfectly horizontal or vertical lines. Press :kbd:`Shift` while " "holding the third handle, and it'll snap to a perfect circle." msgstr "" "Si premeu :kbd:`Majús.` mentre sosteniu les dues primeres nanses, " "s'ajustaran perfectament les línies horitzontal o vertical. Premeu :kbd:" "`Majús.` mentre sosteniu la tercera nansa, i s'ajustarà a un cercle perfecte." #: ../../user_manual/painting_with_assistants.rst:61 msgid "Perspective" msgstr "Perspectiva" #: ../../user_manual/painting_with_assistants.rst:63 msgid "This ruler takes four points and creates a perspective grid." msgstr "Aquest regle pren quatre punts i crea una quadrícula de perspectiva." #: ../../user_manual/painting_with_assistants.rst:65 msgid "" "This grid can be used with the 'perspective' sensor, which can influence " "brushes." msgstr "" "Aquesta quadrícula es pot utilitzar amb el sensor de «perspectiva», el qual " "pot influir en els pinzells." #: ../../user_manual/painting_with_assistants.rst:68 msgid "" "If you press :kbd:`Shift` while holding any of the corner handles, they'll " "snap to one of the other corner handles, in sets." msgstr "" "Si premeu :kbd:`Majús.` mentre sosteniu qualsevol de les nanses de " "cantonada, s'ajustaran a una de les altres nanses de cantonada, en conjunt." #: ../../user_manual/painting_with_assistants.rst:74 #: ../../user_manual/painting_with_assistants.rst:78 msgid "Ruler" msgstr "Regle" #: ../../user_manual/painting_with_assistants.rst:76 msgid "There are three assistants in this group:" msgstr "En aquest grup hi ha tres assistents:" #: ../../user_manual/painting_with_assistants.rst:79 msgid "Helps create a straight line between two points." msgstr "Ajuda a crear una línia recta entre dos punts." #: ../../user_manual/painting_with_assistants.rst:81 msgid "Infinite Ruler" msgstr "Regle infinit" #: ../../user_manual/painting_with_assistants.rst:81 msgid "" "Extrapolates a straight line beyond the two visible points on the canvas." msgstr "" "Extrapola una línia recta més enllà dels dos punts visibles en el llenç." #: ../../user_manual/painting_with_assistants.rst:84 msgid "" "This ruler allows you to draw a line parallel to the line between the two " "points anywhere on the canvas." msgstr "" "Aquest regle permet dibuixar una línia paral·lela a la línia entre els dos " "punts en qualsevol lloc del llenç." #: ../../user_manual/painting_with_assistants.rst:85 msgid "Parallel Ruler" msgstr "Regle paral·lel" #: ../../user_manual/painting_with_assistants.rst:87 msgid "" "If you press :kbd:`Shift` while holding the first two handles, they will " "snap to perfectly horizontal or vertical lines." msgstr "" "Si premeu :kbd:`Majús.` mentre sosteniu les dues primeres nanses, " "s'ajustaran perfectament les línies horitzontal o vertical." #: ../../user_manual/painting_with_assistants.rst:93 msgid "Spline" msgstr "Spline" #: ../../user_manual/painting_with_assistants.rst:95 msgid "" "This assistant allows you to position and adjust four points to create a " "cubic bezier curve. You can then draw along the curve, snapping your brush " "stroke directly to the curve line. Perfect curves every time!" msgstr "" "Aquest assistent permet col·locar i ajustar quatre punts per a crear una " "corba de Bezier cúbica. Després podreu dibuixar al llarg de la corba, " "ajustant el traç del pinzell directament a la línia de la corba. Corbes " "perfectes cada vegada!" #: ../../user_manual/painting_with_assistants.rst:99 msgid "" "If you press :kbd:`Shift` while holding the first two handles, they will " "snap to perfectly horizontal or vertical lines. Press :kbd:`Shift` while " "holding the third or fourth handle, they will snap relative to the handle " "they are attached to." msgstr "" "Si premeu :kbd:`Majús.` mentre sosteniu les dues primeres nanses, " "s'ajustaran perfectament les línies horitzontal o vertical. Premeu :kbd:" "`Majús.` mentre sosteniu la tercera o quarta nansa, s'ajustaran en relació " "amb on estan adjuntades." #: ../../user_manual/painting_with_assistants.rst:107 msgid "Vanishing Point" msgstr "Punt de fuga" #: ../../user_manual/painting_with_assistants.rst:109 msgid "" "This assistant allows you to create a vanishing point, typically used for a " "horizon line. A preview line is drawn and all your snapped lines are drawn " "to this line." msgstr "" "Aquest assistent permet crear un punt de fuga, normalment utilitzat per a " "una línia de l'horitzó. Es dibuixa una línia de vista prèvia i totes les " "línies que s'hi ajustin seran dibuixades amb aquesta línia." #: ../../user_manual/painting_with_assistants.rst:112 msgid "" "It is one point, with four helper points to align it to previously created " "perspective lines." msgstr "" "És un punt, amb quatre punts d'ajuda per alinear amb les línies de " "perspectiva creades prèviament." #: ../../user_manual/painting_with_assistants.rst:115 msgid "They are made and manipulated with the :ref:`assistant_tool`." msgstr "Són creats i manipulats amb l':ref:`assistant_tool`." #: ../../user_manual/painting_with_assistants.rst:117 msgid "" "If you press :kbd:`Shift` while holding the center handle, they will snap to " "perfectly horizontal or vertical lines depending on the position of where it " "previously was." msgstr "" "Si premeu :kbd:`Majús.` mentre manteniu premuda la nansa central, " "s'ajustaran perfectament les línies horitzontal o vertical, depenent de la " "posició on es trobaven anteriorment." #: ../../user_manual/painting_with_assistants.rst:123 msgid "The vanishing point assistant also shows several general lines." msgstr "L'assistent del punt de fuga també mostra diverses línies generals." #: ../../user_manual/painting_with_assistants.rst:125 msgid "" "When you've just created, or when you've just moved a vanishing point " "assistant, it will be selected. This means you can modify the amount of " "lines shown in the tool options of the :ref:`assistant_tool`." msgstr "" "Quan acabeu de crear, o quan acabeu de moure un punt de fuga a l'assistent, " "aquest serà seleccionat. Això vol dir que podreu modificar la quantitat de " "línies que es mostren a les Opcions de l'eina per a l':ref:`assistant_tool`." #: ../../user_manual/painting_with_assistants.rst:130 msgid "Fish Eye Point" msgstr "Punt d'ull de peix" #: ../../user_manual/painting_with_assistants.rst:132 msgid "" "Like the vanishing point assistant, this assistant is per a set of parallel " "lines in a 3d space. So to use it effectively, use two, where the second is " "at a 90 degrees angle of the first, and add a vanishing point to the center " "of both. Or combine one with a parallel ruler and a vanishing point, or even " "one with two vanishing points. The possibilities are quite large." msgstr "" "Igual que amb l'assistent del punt de fuga, aquest assistent és per a un " "conjunt de línies paral·leles en un espai en 3D. Llavors, per a utilitzar-lo " "de manera efectiva, utilitzeu-ne dos, on el segon estarà a un angle de 90 " "graus del primer, i afegiu un punt de fuga al centre de tots dos. O combineu-" "ne un amb un regle paral·lel i un punt de fuga, o fins i tot un amb dos " "punts de fuga. Les possibilitats són molt grans." #: ../../user_manual/painting_with_assistants.rst:139 msgid "" "This assistant will not just give feedback/snapping between the vanishing " "points, but also give feedback to the relative left and right of the " "assistant. This is so you can use it in edge-cases like panoramas with " "relative ease." msgstr "" "Aquest assistent no només donarà retroalimentació/ajust entre els punts de " "fuga, sinó que també donarà retroalimentació a l'esquerra i dreta relatives " "de l'assistent. Això és perquè pugueu utilitzar-lo en casos extrems com " "panorames amb una facilitat relativa." #: ../../user_manual/painting_with_assistants.rst:149 msgid "Tutorials" msgstr "Guies d'aprenentatge" #: ../../user_manual/painting_with_assistants.rst:151 msgid "" "Check out this in depth discussion and tutorial on https://www.youtube.com/" "watch?v=OhEv2pw3EuI" msgstr "" "Feu una ullada a aquest debat en profunditat i guia d'aprenentatge a https://" "www.youtube.com/watch?v=OhEv2pw3EuI" #: ../../user_manual/painting_with_assistants.rst:157 msgid "Setting up Krita for technical drawing-like perspectives" msgstr "Ajustar el Krita per a perspectives de dibuix tècnic" #: ../../user_manual/painting_with_assistants.rst:159 msgid "" "So now that you've seen the wide range of drawing assistants that Krita " "offers, here is an example of how using these assistants you can set up " "Krita for technical drawing." msgstr "" "Ara que heu vist la gran varietat d'assistents de dibuix que ofereix el " "Krita, aquí teniu un exemple de com utilitzar-los i configurar el Krita per " "al dibuix tècnic." #: ../../user_manual/painting_with_assistants.rst:163 msgid "" "This tutorial below should give you an idea of how to set up the assistants " "for specific types of technical views." msgstr "" "Aquesta guia d'aprenentatge us donarà una idea sobre com configurar els " "assistents per a tipus específics de vistes tècniques." #: ../../user_manual/painting_with_assistants.rst:166 msgid "" "If you want to instead do the true projection, check out :ref:`the " "projection category `." msgstr "" "Si en canvi voleu fer la veritable projecció, reviseu :ref:`la categoria " "Projecció `." #: ../../user_manual/painting_with_assistants.rst:169 msgid "Orthographic" msgstr "Ortogràfica" #: ../../user_manual/painting_with_assistants.rst:171 msgid "" "Orthographic is a mode where you try to look at something from the left or " "the front. Typically, you try to keep everything in exact scale with each " "other, unlike perspective deformation." msgstr "" "Ortogràfica és un mode en el que intenteu mirar quelcom des de l'esquerra o " "el davant. En general, intentareu mantenir-ho tot en l'escala exacta entre " "si, a diferència de amb la deformació de la perspectiva." #: ../../user_manual/painting_with_assistants.rst:175 msgid "" "The key assistant you want to use here is the Parallel Ruler. You can set " "these up horizontally or vertically, so you always have access to a Grid." msgstr "" "L'assistent clau que voldreu utilitzar aquí és el regle paral·lel. Podreu " "configurar-lo horitzontalment o verticalment, de manera que sempre tindreu " "accés a una quadrícula." #: ../../user_manual/painting_with_assistants.rst:180 msgid "Axonometric" msgstr "Axonomètrica" #: ../../user_manual/painting_with_assistants.rst:182 msgid "All of these are set up using three Parallel Rulers." msgstr "Totes aquestes es configuren emprant tres regles paral·lels." #: ../../user_manual/painting_with_assistants.rst:185 msgid ".. image:: images/en/Assistants_oblique.png" msgstr ".. image:: images/en/Assistants_oblique.png" #: ../../user_manual/painting_with_assistants.rst:187 msgid "" "For oblique, set two parallel rulers to horizontal and vertical, and one to " "an angle, representing depth." msgstr "" "Per a obliqua, establiu dos regles paral·lels a horitzontal i vertical, i un " "a un angle, representant la profunditat." #: ../../user_manual/painting_with_assistants.rst:188 msgid "Oblique" msgstr "Obliqua" #: ../../user_manual/painting_with_assistants.rst:191 msgid ".. image:: images/en/Assistants_dimetric.png" msgstr ".. image:: images/en/Assistants_dimetric.png" #: ../../user_manual/painting_with_assistants.rst:193 msgid "" "Isometric perspective has technically all three rulers set up at 120° from " "each other. Except when it's game isometric, then it's a type of dimetric " "projection where the diagonal values are a 116.565° from the main. The " "latter can be easily set up by snapping the assistants to a grid." msgstr "" "La perspectiva isomètrica tècnicament té els tres regles establerts a 120° " "un de l'altra. Excepte quan és un joc isomètric, llavors és un tipus de " "projecció dimètrica on els valors de la diagonal estaran a 116,565° del " "principal. Aquest últim es pot configurar amb facilitat ajustant-lo amb els " "assistents a una quadrícula." #: ../../user_manual/painting_with_assistants.rst:197 msgid "Dimetric & Isometric" msgstr "Dimètrica i isomètrica" #: ../../user_manual/painting_with_assistants.rst:200 msgid ".. image:: images/en/Assistants_trimetric.png" msgstr ".. image:: images/en/Assistants_trimetric.png" #: ../../user_manual/painting_with_assistants.rst:202 msgid "" "Is when all the angles are slightly different. Often looks like a slightly " "angled isometric." msgstr "" "És quan tots els angles són lleugerament diferents. Sovint sembla una " "isomètrica lleugerament angulosa." #: ../../user_manual/painting_with_assistants.rst:203 msgid "Trimetric" msgstr "Trimétrica" #: ../../user_manual/painting_with_assistants.rst:206 msgid "Linear Perspective" msgstr "Perspectiva lineal" #: ../../user_manual/painting_with_assistants.rst:209 msgid ".. image:: images/en/Assistants_1_point_perspective.png" msgstr ".. image:: images/en/Assistants_1_point_perspective.png" #: ../../user_manual/painting_with_assistants.rst:211 msgid "" "A 1 point perspective is set up using 1 vanishing point, and two crossing " "perpendicular parallel rulers." msgstr "" "Una perspectiva d'1 punt es configura utilitzant 1 punt de fuga i dos regles " "paral·lels perpendiculars que es creuen." #: ../../user_manual/painting_with_assistants.rst:212 msgid "1 Point Perspective" msgstr "Perspectiva d'1 punt" #: ../../user_manual/painting_with_assistants.rst:215 msgid ".. image:: images/en/Assistants_2_point_perspective.png" msgstr ".. image:: images/en/Assistants_2_point_perspective.png" #: ../../user_manual/painting_with_assistants.rst:217 msgid "" "A 2 point perspective is set up using 2 vanishing point and 1 vertical " "parallel ruler. Often, putting the vanishing points outside the frame a " "little can decrease the strength of it." msgstr "" "Una perspectiva de 2 punts es configura utilitzant 2 punts de fuga i 1 regle " "vertical paral·lel. Sovint, col·locar els punts de fuga fora del marc pot " "fer disminuir la seva força." #: ../../user_manual/painting_with_assistants.rst:219 msgid "2 Point Perspective" msgstr "Perspectiva de 2 punts" #: ../../user_manual/painting_with_assistants.rst:222 msgid ".. image:: images/en/Assistants_2_pointperspective_02.png" msgstr ".. image:: images/en/Assistants_2_pointperspective_02.png" #: ../../user_manual/painting_with_assistants.rst:224 msgid ".. image:: images/en/Assistants_3_point_perspective.png" msgstr ".. image:: images/en/Assistants_3_point_perspective.png" #: ../../user_manual/painting_with_assistants.rst:226 msgid "3 Point Perspective" msgstr "Perspectiva de 3 punts" #: ../../user_manual/painting_with_assistants.rst:226 msgid "A 3 point perspective is set up using 3 vanishing point rulers." msgstr "" "Una perspectiva de 3 punts es configura utilitzant 3 regles del punt de fuga." #: ../../user_manual/painting_with_assistants.rst:229 msgid "Logic of the vanishing point" msgstr "Lògica del punt de fuga" #: ../../user_manual/painting_with_assistants.rst:231 msgid "" "There's a little secret that perspective tutorials don't always tell you, " "and that's that a vanishing point is the point where any two parallel lines " "meet. This means that a 1 point perspective and 2 point perspective are " "virtually the same." msgstr "" "Hi ha un petit secret que les guies d'aprenentatge de la perspectiva no " "sempre expliquen, i aquest és que un punt de fuga és el punt on es troben " "dues línies paral·leles. Això vol dir que una perspectiva d'1 punt i una " "perspectiva de 2 punts són pràcticament el mateix." #: ../../user_manual/painting_with_assistants.rst:233 msgid "" "We can prove this via a little experiment. That good old problem: drawing a " "rail-road." msgstr "" "Ho demostrarem mitjançant un petit experiment. Aquest és un bon problema " "antic: dibuixar un via de ferrocarril." #: ../../user_manual/painting_with_assistants.rst:236 msgid ".. image:: images/en/Assistants_vanishing_point_logic_01.png" msgstr ".. image:: images/en/Assistants_vanishing_point_logic_01.png" #: ../../user_manual/painting_with_assistants.rst:237 msgid "" "You are probably familiar with the problem: How to determine where the next " "beam is going to be, as perspective projection will make them look closer " "together." msgstr "" "Probablement estigueu familiaritzat amb el problema: com determinar on anirà " "el següent travesser, ja que la projecció en perspectiva farà que es vegin " "més junts." #: ../../user_manual/painting_with_assistants.rst:240 msgid "" "Typically, the solution is to draw a line in the middle and then draw lines " "diagonally across. After all, those lines are parallel, meaning that the " "exact same distance is used." msgstr "" "Normalment, la solució és dibuixar una línia al mig i després dibuixar " "línies en diagonal que travessin. Després de tot, aquestes línies són " "paral·leles, el qual vol dir que s'utilitza la mateixa distància exacta." #: ../../user_manual/painting_with_assistants.rst:243 msgid ".. image:: images/en/Assistants_vanishing_point_logic_02.png" msgstr ".. image:: images/en/Assistants_vanishing_point_logic_02.png" #: ../../user_manual/painting_with_assistants.rst:244 msgid "" "But because they are parallel, we can use a vanishing point assistant " "instead, and we use the alignment handles to align it to the diagonal of the " "beam, and to the horizontal (here marked with red)." msgstr "" "Però com són paral·leles, podem utilitzar un assistent del punt de fuga, i " "utilitzarem les nanses d'alineació per alinear-les amb la diagonal del " "travesser i amb l'horitzontal (aquí marcada amb vermell) del travesser." #: ../../user_manual/painting_with_assistants.rst:247 msgid "" "That diagonal can then in turn be used to determine the position of the " "beams:" msgstr "" "Aquesta diagonal es podrà utilitzar després per a determinar la posició dels " "travessers:" #: ../../user_manual/painting_with_assistants.rst:251 msgid ".. image:: images/en/Assistants_vanishing_point_logic_03.png" msgstr ".. image:: images/en/Assistants_vanishing_point_logic_03.png" #: ../../user_manual/painting_with_assistants.rst:252 msgid "" "Because any given set of lines has a vanishing point (outside of the ones " "flat on the view-plane), there can be an infinite amount of vanishing points " "in a linear perspective. Therefore, Krita allows you to set vanishing points " "yourself instead of forcing you to only use a few." msgstr "" "A causa que qualsevol conjunt de línies té un punt de fuga (fora del pla a " "la vista del mapa), pot haver-hi una quantitat infinita de punts de fuga en " "una perspectiva lineal. Per tant, el Krita permet establir punts de fuga en " "lloc d'obligar-vos a utilitzar-ne només uns pocs." #: ../../user_manual/painting_with_assistants.rst:255 msgid "Fish Eye perspective" msgstr "Perspectiva de l'ull de peix" #: ../../user_manual/painting_with_assistants.rst:257 msgid "" "Fish eye perspective works much the same as the linear perspective, the big " "difference being that in a fish-eye perspective, any parallel set of lines " "has two vanishing points, each for one side." msgstr "" "La perspectiva d'ull de peix funciona de manera molt similar a la " "perspectiva lineal, la gran diferència és que en una perspectiva d'ull de " "peix, qualsevol conjunt de línies paral·leles té dos punts de fuga, cadascun " "per un costat." #: ../../user_manual/painting_with_assistants.rst:261 msgid "" "So, to set them up, the easiest way is one horizontal, one vertical, on the " "same spot, and one vanishing point assistant in the middle." msgstr "" "Llavors, per a configurar-les, la forma més fàcil és una horitzontal i una " "vertical en el mateix lloc, i un assistent de punt de fuga al mig." #: ../../user_manual/painting_with_assistants.rst:265 msgid ".. image:: images/en/Fish-eye.gif" msgstr ".. image:: images/en/Fish-eye.gif" #: ../../user_manual/painting_with_assistants.rst:266 msgid "" "But, you can also make one horizontal one that is just as big as the other " "horizontal one, and put it halfway:" msgstr "" "Però, també podeu crear-ne un en horitzontal que sigui tan gran com l'altre " "en horitzontal, i posar-lo al mig:" diff --git a/locale/ca/LC_MESSAGES/user_manual/working_with_images.po b/locale/ca/LC_MESSAGES/user_manual/working_with_images.po index e7d4bb9e7..56be4abec 100644 --- a/locale/ca/LC_MESSAGES/user_manual/working_with_images.po +++ b/locale/ca/LC_MESSAGES/user_manual/working_with_images.po @@ -1,666 +1,666 @@ # Translation of docs_krita_org_user_manual___working_with_images.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: user_manual\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-04-10 03:45+0200\n" "PO-Revision-Date: 2019-04-22 16:35+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 18.12.3\n" #: ../../user_manual/working_with_images.rst:None msgid ".. image:: images/en/Infinite-canvas.png" msgstr ".. image:: images/en/Infinite-canvas.png" #: ../../user_manual/working_with_images.rst:1 msgid "Detailed steps on how images work in Krita" msgstr "Passos detallats sobre com es treballa amb les imatges en el Krita" #: ../../user_manual/working_with_images.rst:17 msgid "Working with Images" msgstr "Treballar amb imatges" #: ../../user_manual/working_with_images.rst:19 msgid "" "Computers work with files and as a painting program, Krita works with images " "as the type of file it creates and manipulates." msgstr "" "Els ordinadors funcionen amb fitxers i com un programa de pintura, el Krita " "treballa amb imatges com el tipus de fitxer que crea i manipula." #: ../../user_manual/working_with_images.rst:23 msgid "What do Images Contain?" msgstr "Què contenen les imatges?" #: ../../user_manual/working_with_images.rst:25 msgid "" "If you have a text document, it of course contains letters, strung in the " "right order, so the computer loads them as coherent sentences." msgstr "" "Si teniu un document de text, per descomptat contindrà lletres, enfilades en " "l'ordre correcte, de manera que l'ordinador les carregui com a frases " "coherents." #: ../../user_manual/working_with_images.rst:29 msgid "Raster Data" msgstr "Dades rasteritzades" #: ../../user_manual/working_with_images.rst:31 msgid "" "This is the main data on the paint layers you make. So these are the strokes " "with the paint brush and look pixely up close. A multi-layer file will " "contain several of such layers, that get overlaid on top of each other so " "make the final image." msgstr "" "Aquestes són les dades principals de les capes de pintura que creeu. Així " "que aquestes seran els traços amb el pinzell de pintura i de prop es veuran " "pixelades. Un fitxer de múltiples capes contindrà diverses d'aquestes capes, " "que se superposaran una sobre l'altra per a crear la imatge final." #: ../../user_manual/working_with_images.rst:36 msgid "A single layer file will usually only contain raster data." msgstr "" "Un fitxer d'una sola capa generalment només contindrà dades rasteritzades." #: ../../user_manual/working_with_images.rst:39 msgid "Vector Data" msgstr "Dades vectorials" #: ../../user_manual/working_with_images.rst:41 msgid "" "These are mathematical operations that tell the computer to draw pixels on a " "spot. This makes them much more scalable, because you just tell the " "operation to make the coordinates 4 times bigger to scale it up. Due to this " "vector data is much more editable, lighter, but at the same time it's also " "much more CPU intensive." msgstr "" "Aquestes són operacions matemàtiques que li diuen a l'ordinador que dibuixi " "els píxels en un lloc. Això els farà molt més escalables, perquè simplement " -"li diu a l'operació que faci les coordenades 4 vegades més grans per " -"escalar-les. A causa d'aquestes dades vectorials, tot serà molt més " -"editable, més lleuger, però alhora també es requerirà molt més ús de la CPU." +"li diu a l'operació que faci les coordenades 4 vegades més grans per escalar-" +"les. A causa d'aquestes dades vectorials, tot serà molt més editable, més " +"lleuger, però alhora també es requerirà molt més ús de la CPU." #: ../../user_manual/working_with_images.rst:48 msgid "Operation Data" msgstr "Dades de l'operació" #: ../../user_manual/working_with_images.rst:50 msgid "" "Stuff like the filter layers, that tells Krita to change the colors of a " "layer, but also transparency masks, group layer and transformation masks are " "saved to multi-layer files. Being able to load these depend on the software " "that initially made the file. So Krita can load and save groups, " "transparency masks and layer effects from PSD, but not load or save " "transform masks." msgstr "" "Coses com les capes de filtratge, que li diuen al Krita que canviï els " "colors d'una capa, però també les màscares de transparència, capa de grup i " "les màscares de transformació es desen en fitxers de múltiples capes. La " "possibilitat de carregar-los dependrà del programari que va fer inicialment " "el fitxer. Així que el Krita podrà carregar i desar grups, màscares de " "transparència i efectes de capa des del PSD, però no podrà carregar o desar " "les màscares de transformació." #: ../../user_manual/working_with_images.rst:58 msgid "Metadata" msgstr "Metadades" #: ../../user_manual/working_with_images.rst:60 msgid "" "Metadata is information like the creation date, author, description and also " "information like DPI." msgstr "" "Les metadades són informació com la data de creació, autor, descripció i " "també informació com els PPP (DPI)." #: ../../user_manual/working_with_images.rst:64 msgid "Image size" msgstr "Mida de la imatge" #: ../../user_manual/working_with_images.rst:66 msgid "" "The image size is the dimension and resolution of the canvas. Image size has " "direct effect file size of the Krita document. The more pixels that need to " "be remembered and the higher the bit depth of the color, the heavier the " "resulting file will be." msgstr "" "La mida de la imatge és la dimensió i la resolució del llenç. La mida de la " -"imatge tindrà una efecte directe en la mida de fitxer del document del Krita. " -"Com més píxels cal recordar i com més gran sigui la profunditat de bits del " -"color, més gran serà el fitxer resultant." +"imatge tindrà una efecte directe en la mida de fitxer del document del " +"Krita. Com més píxels cal recordar i com més gran sigui la profunditat de " +"bits del color, més gran serà el fitxer resultant." #: ../../user_manual/working_with_images.rst:72 msgid "DPI/PPI" msgstr "DPI/PPI (PPP)" #: ../../user_manual/working_with_images.rst:74 msgid "" "**DPI** stands for *Dots per Inch*, **PPI** stands for *Pixels per Inch*. In " "printing industry, suppose if your printer prints at 300 **DPI**. It means " "it is actually putting 300 dots of colors in an area equal to an Inch. This " "means the number of pixels your artwork has in a relative area of an inch." msgstr "" "**DPI** vol dir *punts per polsada*, **PPI** vol dir *píxels per polsada* " "(la traducció és **PPP** per a ambdós). En la industria de la impressió, se " "suposa que la vostra impressora imprimeix a 300 **DPI**. Això vol dir que en " "realitat s'estan col·locant 300 punts de colors en una àrea igual que una " -"polzada. Això indicarà la quantitat de píxels que tindrà la vostra obra d'art " -"en una àrea relativa d'una polzada." +"polzada. Això indicarà la quantitat de píxels que tindrà la vostra obra " +"d'art en una àrea relativa d'una polzada." #: ../../user_manual/working_with_images.rst:80 msgid "" "**DPI** is the concern of the printer, and artists while creating artwork " "should keep **PPI** in mind. According to the **PPI** you have set, the " "printers can decide how large your image should be on a piece of paper." msgstr "" "Els **DPI** són referents de la impressora, i els artistes mentre creen " "obres d'art haurien de tenir en compte els **PPI**. Segons els **PPI** que " "heu definit, les impressores podran decidir la mida de la vostra imatge en " "un tros de paper." #: ../../user_manual/working_with_images.rst:85 msgid "Some standards:" msgstr "Alguns estàndards:" #: ../../user_manual/working_with_images.rst:88 msgid "" "This is the default PPI of monitors as assumed by all programs. It is not " "fully correct, as most monitors these days have 125 PPI or even 300 PPI for " "the retina devices. None the less, when making an image for computer " "consumption, this is the default." msgstr "" "Aquests són els PPI predeterminats dels monitors com ho assumiran tots els " "programes. No és totalment correcte, ja que la majoria de monitors actuals " "tenen 125 PPI o fins i tot 300 PPI per als dispositius de retina. Tot i " "això, quan es crea una imatge per al consum des de l'ordinador, aquest serà " "el valor predeterminat." #: ../../user_manual/working_with_images.rst:90 msgid "72 PPI" msgstr "72 PPI" #: ../../user_manual/working_with_images.rst:92 msgid "120 PPI" msgstr "120 PPI" #: ../../user_manual/working_with_images.rst:93 msgid "This is often used as a standard for low-quality posters." msgstr "" "Aquests s'utilitzen sovint com un estàndard per a cartells de baixa qualitat." #: ../../user_manual/working_with_images.rst:94 msgid "300 PPI" msgstr "300 PPI" #: ../../user_manual/working_with_images.rst:95 msgid "This is the minimum you should use for quality prints." msgstr "" "Aquests són el mínim que haureu d'utilitzar per a impressions de qualitat." #: ../../user_manual/working_with_images.rst:97 msgid "600 PPI" msgstr "600 PPI" #: ../../user_manual/working_with_images.rst:97 msgid "The quality used for line art for comics." msgstr "La qualitat emprada per a la línia artística dels còmics." #: ../../user_manual/working_with_images.rst:100 msgid "Color depth" msgstr "Profunditat del color" #: ../../user_manual/working_with_images.rst:102 msgid "" "We went over color depth in the :ref:`Color Management page " "`. What you need to understand is that Krita has " "image color spaces, and layer color spaces, the latter which can save memory " "if used right. For example, having a line art layer in grayscale can half " "the memory costs." msgstr "" "Repassem la profunditat de color a la :ref:`pàgina Gestió del color " "`. Cal entendre que el Krita té espais de color de la " "imatge i espais de color de la capa, els últims poden estalviar memòria si " "s'utilitzen correctament. Per exemple, tenir una capa amb la línia artística " "en escala de grisos pot reduir a la meitat el cost en memòria." #: ../../user_manual/working_with_images.rst:108 msgid "Image color space vs layer color space vs conversion." msgstr "" "Espai de color de la imatge enfront de l'espai de color de la capa enfront " "la conversió." #: ../../user_manual/working_with_images.rst:110 msgid "" "Because there's a difference between image color space and layer color " "space, you can change only the image color space in :menuselection:`Image --" "> Properties` which will leave the layers alone. But if you want to change " "the color space of the file including all the layers you can do it by going " "to :menuselection:`Image --> Convert Image Color Space` this will convert " "all the layers color space as well." msgstr "" "Degut a que hi ha una diferència entre l'espai de color de la imatge i " "l'espai de color de la capa, només podreu canviar l'espai de color de la " "imatge a :menuselection:`Imatge --> Propietats`, el qual deixarà les capes " "soles. Però si voleu canviar l'espai de color del fitxer, incloses totes les " "capes, podreu fer-ho anant a :menuselection:`Imatge --> Converteix l'espai " "de color de la imatge`, això també convertirà tot l'espai de color de les " "capes." #: ../../user_manual/working_with_images.rst:116 msgid "Author and Description" msgstr "Autor i descripció" #: ../../user_manual/working_with_images.rst:119 msgid ".. image:: images/en/document_information_screen.png" msgstr ".. image:: images/en/document_information_screen.png" #: ../../user_manual/working_with_images.rst:120 msgid "" "Krita will automatically save who created the image into your image's " "metadata. Along with the other data such as time and date of creation and " "modification, Krita also shows editing time of a document in the document " "information dialog, useful for professional illustrators, speed-painters to " "keep track of the time they worked on artwork for billing purposes. It " "detects when you haven’t performed actions for a while, and has a precision " "of ±60 seconds. You can empty it in the document info dialog and of course " "by unzipping you .kra file and editing the metadata there." msgstr "" "El Krita desarà automàticament qui va crear la imatge en les metadades de la " "imatge. Juntament amb altres dades com la data i hora de creació i " "modificació, el Krita també mostrarà el temps d'edició d'un document en el " "diàleg d'informació del document, útil per a il·lustradors professionals i " "pintors que per velocitat volen realitzar un seguiment del temps que han " "treballat en el disseny gràfic per a fins de facturació. Detecta quan no heu " "realitzat accions durant un temps i té una precisió de ± 60 segons. Podeu " "netejar-ho des del diàleg d'informació del document i, per descomptat, " "descomprimint des de ZIP el vostre fitxer .kra i editant les metadades." #: ../../user_manual/working_with_images.rst:130 msgid "" "These things can be edited in :menuselection:`File --> Document " "Information`, and for the author's information :menuselection:`Settings --> " "Configure Krita --> Author Information`. Profiles can be switched under :" "menuselection:`Settings --> Active Author Profile`." msgstr "" "Aquestes coses es poden editar a :menuselection:`Fitxer --> Informació del " "document`, i per a la informació de l'autor :menuselection:`Arranjament --> " "Configura el Krita --> Informació de l'autor`. Els perfils es poden canviar " "sota :menuselection:`Arranjament --> Perfil actiu d'autor`." #: ../../user_manual/working_with_images.rst:133 msgid "Setting the canvas background color" msgstr "Ajustar el color de fons del llenç" #: ../../user_manual/working_with_images.rst:135 msgid "" "You can set the canvas background color via :menuselection:`Image --> Image " "Background Color and Transparency`. This allows you to turn the background " "color non-transparent and to change the color. This is also useful for " "certain file formats which force a background color instead of transparency. " "PNG and JPG export use this color as the default color to fill in " "transparency if you do not want to export transparency." msgstr "" "Podeu establir el color de fons del llenç mitjançant :menuselection:`Imatge " "--> Color i transparència del fons de la imatge`. Això permet canviar a un " "color de fons no transparent i canviar el color. També és útil per a certs " "formats de fitxer que forcen un color de fons en lloc de la transparència. " "Les exportacions a PNG i JPG empraran aquest color com el color " "predeterminat per omplir la transparència si no la voleu exportar." #: ../../user_manual/working_with_images.rst:142 msgid "" "If you come in from a program like :program:`Paint Tool Sai`, then using " "this option, or using :guilabel:`Set Canvas Background Color` in the new " "file options, will allow you to work in a slightly more comfortable " "environment, where transparency isn't depicted with checkered boxes." msgstr "" "Si veniu des d'un programa com el :program:`Paint Tool Sai`, llavors " "utilitzeu aquesta opció o utilitzeu :guilabel:`Estableix el color de fons " "del llenç` a les opcions del fitxer nou, permetent-vos treballar en un " "entorn una mica més còmode, on la transparència no es representarà amb un " "tauler a quadres." #: ../../user_manual/working_with_images.rst:148 msgid "Basic transforms" msgstr "Transformacions bàsiques" #: ../../user_manual/working_with_images.rst:150 msgid "There are some basic transforms available in the image menu." msgstr "" "Al menú de la imatge hi ha disponibles algunes transformacions bàsiques." #: ../../user_manual/working_with_images.rst:152 msgid "Shear Image" msgstr "Inclina la imatge" #: ../../user_manual/working_with_images.rst:153 msgid "This will allow you to skew the whole image and its layers." msgstr "Permet esbiaixar la imatge sencera i les seves capes." #: ../../user_manual/working_with_images.rst:154 msgid "Rotate" msgstr "Gira" #: ../../user_manual/working_with_images.rst:155 msgid "This will allow you to rotate the image and all its layers quickly." msgstr "Permet girar la imatge i totes les seves capes amb rapidesa." #: ../../user_manual/working_with_images.rst:157 msgid "Mirror Horizontal/Vertical" msgstr "Emmiralla horitzontalment/verticalment" #: ../../user_manual/working_with_images.rst:157 msgid "This will allow you to mirror the whole image with all its layers." msgstr "Permet reflectir tota la imatge amb totes les seves capes." #: ../../user_manual/working_with_images.rst:159 msgid "But there are more options than that..." msgstr "Però hi ha més opcions a part d'aquestes..." #: ../../user_manual/working_with_images.rst:162 msgid "Cropping and resizing the canvas" msgstr "Escapçar i canviar la mida del llenç" #: ../../user_manual/working_with_images.rst:164 msgid "" "You can crop and image with the :ref:`crop_tool`, to cut away extra space " "and improve the composition." msgstr "" "Podeu escapçar la imatge amb l':ref:`crop_tool`, per a retallar l'espai " "extra i millorar la composició." #: ../../user_manual/working_with_images.rst:168 msgid "Trimming" msgstr "Ajustar" #: ../../user_manual/working_with_images.rst:170 msgid "" "Using :menuselection:`Image --> Trim to Layer`, Krita resizes the image to " "the dimensions of the layer selected. Useful for when you paste a too large " "image into the layer and want to resize the canvas to the extent of this " "layer." msgstr "" "Utilitzant :menuselection:`Imatge --> Ajusta a la capa`, el Krita canviarà " "la mida de la imatge a les dimensions de la capa seleccionada. És útil per a " "quan enganxeu una imatge massa gran a dins de la capa i voleu canviar la " "mida del llenç a les dimensions d'aquesta capa." #: ../../user_manual/working_with_images.rst:174 msgid "" ":menuselection:`Image --> Trim to Selection` is a faster cousin to the crop " "tool. This helps us to resize the canvas to the dimension of any active " "selection. This is especially useful with right clicking the layer on the " "layer stack and choosing :guilabel:`Select Opaque`. :menuselection:`Image --" "> Trim to Selection` will then crop the canvas to the selection bounding box." msgstr "" ":menuselection:`Imatge --> Ajusta a la selecció` és un cosí més ràpid que " "l'eina d'escapçar. Aquesta ens ajudarà a canviar la mida del llenç a les " "dimensions de qualsevol selecció activa. Això és especialment útil en fer " "clic dret a la capa sobre la pila de capes i seleccionant :guilabel:" "`Selecciona l'opac`. Fent :menuselection:`Imatge --> Ajusta a la selecció` " "després, es retallarà el llenç al limit del contenidor." #: ../../user_manual/working_with_images.rst:180 msgid "" ":menuselection:`Image --> Trim to Image Size` is actually for layers, and " "will trim all layers to the size of the image, making your files lighter by " "getting rid of invisible data." msgstr "" ":menuselection:`Imatge --> Ajusta a la mida de la imatge` en realitat és per " "a les capes, i ajustarà totes les capes a la mida de la imatge, fent que els " "vostres fitxers siguin més lleugers desfent-se de les dades invisibles." #: ../../user_manual/working_with_images.rst:185 msgid "Resizing the canvas" msgstr "Canviar la mida del llenç" #: ../../user_manual/working_with_images.rst:187 msgid "" "You can also resize the canvas via :menuselection:`Image --> Resize Canvas` " "(or :kbd:`Ctrl + Alt + C`). The dialog box is shown below." msgstr "" "També podeu canviar la mida del llenç mitjançant :menuselection:`Imatge --> " "Redimensiona el llenç` (o :kbd:`Ctrl + Alt + C`). El diàleg es mostra a " "continuació." #: ../../user_manual/working_with_images.rst:191 msgid ".. image:: images/en/Resize_Canvas.png" msgstr ".. image:: images/en/Resize_Canvas.png" #: ../../user_manual/working_with_images.rst:192 msgid "" "In this, constraint proportions will make sure the height and width stay in " "proportion to each other as you change them. Offset indicates where the new " "canvas space is added around the current image. You basically decide where " "the current image goes (if you press the left-button, it'll go to the center " "left, and the new canvas space will be added to the right of the image)." msgstr "" "En aquest sentit, les proporcions restringides s'asseguraran que l'alçada i " "amplada romanguin en proporció entre si. El desplaçament indica on s'afegirà " "l'espai nou del llenç al voltant de la imatge actual. Bàsicament, decidireu " "on va la imatge actual (si premeu el botó esquerre, anireu al centre " "esquerra i l'espai nou del llenç s'afegirà a la dreta de la imatge)." #: ../../user_manual/working_with_images.rst:199 msgid "" "Another way to resize the canvas according to the need while drawing is when " "you scroll away from the end of the canvas, you can see an arrow appear. " "Clicking this will extend the canvas in that direction. You can see the " "arrow marked in red in the example below:" msgstr "" "Una altra manera de canviar la mida del llenç segons calgui mentre es " "dibuixa, és quan es desplaça des del final del llenç, veureu aparèixer una " "fletxa. En fer-hi clic, s'estendrà el llenç en aquesta direcció. Veureu la " "fletxa marcada en vermell en el següent exemple:" #: ../../user_manual/working_with_images.rst:209 msgid "Resizing the image" msgstr "Canviar la mida de la imatge" #: ../../user_manual/working_with_images.rst:211 msgid "" ":guilabel:`Scale Image to New Size` allows you to resize the whole image. " "Also, importantly, this is where you can change the resolution or *upres* " "your image. So for instance, if you were initially working at 72 PPI to " "block in large shapes and colors, images, etc... And now you want to really " "get in and do some detail work at 300 or 400 PPI this is where you would " "make the change." msgstr "" ":guilabel:`Escala la imatge a una mida nova` permet canviar la mida de tota " "la imatge. A més, el més important aquí és que podreu canviar la resolució o " "*augmentar* la vostra imatge. Així que, per exemple, si inicialment estàveu " "treballant amb 72 PPI per a bloquejar formes grans i colors, imatges, etc. I " "ara realment voleu canviar i fer un treball detallat a 300 o 400 PPI, aquí " "és on faríeu el canvi." #: ../../user_manual/working_with_images.rst:218 msgid "" "Like all other dialogs where a chain link appears, when the chain is linked " "the aspect ratio is maintained. To disconnect the chain, just click on the " "links and the two halves will separate." msgstr "" "Igual que en tots els altres diàlegs on apareix un enllaç de cadena, quan la " "cadena està vinculada, la relació d'aspecte es mantindrà. Per a desconnectar " "la cadena, simplement feu clic sobre els enllaços i les dues meitats se " "separaran." #: ../../user_manual/working_with_images.rst:224 msgid ".. image:: images/en/Scale_Image_to_New_Size.png" msgstr ".. image:: images/en/Scale_Image_to_New_Size.png" #: ../../user_manual/working_with_images.rst:226 msgid "Separating Images" msgstr "Descompondre les imatges" #: ../../user_manual/working_with_images.rst:229 msgid ".. image:: images/en/Separate_Image.png" msgstr ".. image:: images/en/Separate_Image.png" #: ../../user_manual/working_with_images.rst:230 msgid "" "This powerful image manipulation feature lets you separate an image into its " "different components or channels." msgstr "" "Aquesta potent característica per a la manipulació de les imatges permet " "descompondre una imatge en els seus diferents components o canals." #: ../../user_manual/working_with_images.rst:233 msgid "" "This is useful for people working in print, or people manipulating game " "textures. There's no combine functionality, but what you can do, if using " "colored output, is to set two of the channels to the addition :ref:" "`blending_modes`." msgstr "" "Això és útil per a les persones que treballen en la impressió o per a les " "persones que manipulen les textures dels jocs. No hi ha cap funcionalitat " "per a la combinació, però el que podeu fer, si utilitzeu una sortida en " "color, és configurar dos dels canals per a l'addició amb els :ref:" "`blending_modes`." #: ../../user_manual/working_with_images.rst:238 msgid "" "For grayscale images in the RGB space, you can use the copy red, copy green " "and copy blue blending modes, with using the red one for the red channel " "image, etc." msgstr "" "Per a les imatges en escala de grisos en l'espai RGB, podeu utilitzar els " "modes de barreja Copia el vermell, Copia el verd i Copia el blau, utilitzant " "el vermell per al canal vermell de la imatge, etc." #: ../../user_manual/working_with_images.rst:243 msgid "Saving, Exporting and Opening Files" msgstr "Desar, exportar i obrir fitxers" #: ../../user_manual/working_with_images.rst:245 msgid "" "When Krita creates or opens a file, it has a copy of the file in memory, " "that it edits. This is part of the way how computers work: They make a copy " "of their file in the RAM. Thus, when saving, Krita takes its copy and copies " "it over the existing file. There's a couple of tricks you can do with saving." msgstr "" "Quan el Krita crea o obre un fitxer, mantindrà una còpia en memòria del " "fitxer que s'està editant. Això forma part de la manera com treballen els " "ordinadors: fan una còpia del seu fitxer a la RAM. Així, en desar, el Krita " "prendrà la seva còpia i la copiarà sobre el fitxer existent. Hi ha un parell " "de trucs que podreu fer amb el desament." #: ../../user_manual/working_with_images.rst:252 msgid "" "Krita saves the current image in its memory to a defined place on the hard-" "drive. If the image hadn't been saved before, Krita will ask you where to " "save it." msgstr "" "El Krita desa la imatge actual a la seva memòria en un lloc definit del disc " "dur. Si la imatge no s'havia desat abans, el Krita preguntarà a on desar-la." #: ../../user_manual/working_with_images.rst:253 msgid "Save" msgstr "Desa" #: ../../user_manual/working_with_images.rst:256 msgid "Save As" msgstr "Desa com a" #: ../../user_manual/working_with_images.rst:256 msgid "" "Make a copy of your current file by saving it with a different name. Krita " "will switch to the newly made file as its active document." msgstr "" "Fa una còpia del vostre fitxer actual desant-lo amb un nom diferent. El " "Krita canviarà al fitxer acabat de crear com el seu document actiu." #: ../../user_manual/working_with_images.rst:258 msgid "Open" msgstr "Obre" #: ../../user_manual/working_with_images.rst:259 msgid "Open a saved file. Fairly straightforward." msgstr "Obre un fitxer desat. Molt senzill." #: ../../user_manual/working_with_images.rst:261 msgid "" "Save a file to a new location without actively opening it. Useful for when " "you are working on a layered file, but only need to save a flattened version " "of it to a certain location." msgstr "" "Desa un fitxer en una ubicació nova sense obrir-lo. És útil per a quan esteu " "treballant en un fitxer de capes, però només necessiteu desar una versió " "aplanada d'aquest en una ubicació determinada." #: ../../user_manual/working_with_images.rst:262 msgid "Export" msgstr "Exporta" #: ../../user_manual/working_with_images.rst:265 msgid "" "This is a bit of an odd one, but it opens a file, and forgets where you " "saved it to, so that when pressing 'save' it asks you where to save it. This " "is also called 'import' in other programs." msgstr "" "Això és una mica estrany, però obre un fitxer i oblida on el vau desar, de " "manera que al prémer «desa» se us demanarà a on desar-lo. En altres " "programes a això també se li diu «importa»." #: ../../user_manual/working_with_images.rst:266 msgid "Open Existing Document As Untitled Document" msgstr "Obre un document existent com a un document sense títol" #: ../../user_manual/working_with_images.rst:269 msgid "Create Copy from Current Image" msgstr "Crea una còpia des de la imatge actual" #: ../../user_manual/working_with_images.rst:269 msgid "" "Makes a new copy of the current image. Similar to Open Existing Document As " "Untitled Document, but then with already opened files." msgstr "" "Realitza una còpia nova de la imatge actual. Similar a Obre un document " "existent com a un document sense títol, però ho fa amb els fitxers ja oberts." #: ../../user_manual/working_with_images.rst:272 msgid "Save Incremental Version" msgstr "Desa la versió incremental" #: ../../user_manual/working_with_images.rst:272 msgid "" "Saves the current image as 'filename'\\_XXX.kra and switches the current " "document to it." msgstr "" "Desa la imatge actual com a «nom_fitxer»\\_XXX.kra i canvia al document " "actual." #: ../../user_manual/working_with_images.rst:275 msgid "" "Copies and renames the last saved version of your file to a back-up file and " "saves your document under the original name." msgstr "" "Copia i reanomena l'última versió desada del vostre fitxer en un fitxer de " "còpia de seguretat i desa el vostre document amb el nom original." #: ../../user_manual/working_with_images.rst:276 msgid "Save Incremental Backup" msgstr "Desa la còpia de seguretat incremental" #: ../../user_manual/working_with_images.rst:279 msgid "" "Since Krita's file format is compressed data file, in case of a corrupt or " "broken file you can open it with archive managers and extract the contents " "of the layers. This will help you to recover as much as possible data from " "the file. On Windows, you will need to rename it to filename.zip to open it." msgstr "" "Atès que el format de fitxer del Krita és un fitxer de dades comprimides, en " "cas d'un fitxer corrupte o malmès, podreu obrir-lo amb els gestors de " "fitxers i extreure el contingut de les capes. Això us ajudarà a recuperar la " "major quantitat possible de dades del fitxer. Al Windows, haureu de canviar-" "li el nom a nom_fitxer.zip per a poder-lo obrir." 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 7c25ada11..9b16df741 100644 --- a/locale/es/LC_MESSAGES/contributors_manual/krita_manual_conventions.po +++ b/locale/es/LC_MESSAGES/contributors_manual/krita_manual_conventions.po @@ -1,875 +1,875 @@ # 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-04-21 03:37+0200\n" +"POT-Creation-Date: 2019-04-23 03:45+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/en/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: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: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: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: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: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:154 msgid "And figure directives for images with captions::" 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/en`` 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: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: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: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: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: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 msgid "veridian" 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: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 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:296 msgid "Explanation." msgstr "Explicación." #: ../../contributors_manual/krita_manual_conventions.rst:299 msgid "You can make them like this::" 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: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, hint: 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 "This looks like the following::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:402 msgid "Sphinx also adds::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:412 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:416 msgid "That said, horizontal rulers can be made with ``----``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:419 msgid "The rubric directive." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:420 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:426 msgid "So, when to use these?" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:427 msgid "" "Only use them when you think the subject is too minor to have a proper " "heading." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:429 msgid "Topic" msgstr "Tema" #: ../../contributors_manual/krita_manual_conventions.rst:430 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:431 msgid "Rubric" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:432 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:434 msgid "Admonishments" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:434 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:437 #, fuzzy #| msgid "Code Snippets:" msgid "Code Snippets" msgstr "Fragmentos de código:" #: ../../contributors_manual/krita_manual_conventions.rst:439 msgid "``Inline code snippets`` are done with ````backticks````." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:441 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:447 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:457 msgid "Becomes" msgstr "Se convierte en" #: ../../contributors_manual/krita_manual_conventions.rst:467 msgid "some more..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:500 #, fuzzy #| msgid "Other preformatted text." msgid "Other preformatted text" msgstr "Otro texto preformateado." #: ../../contributors_manual/krita_manual_conventions.rst:503 msgid "One can" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:504 msgid "preformat" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:505 msgid "text by" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:506 msgid "prepending" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:507 msgid "each line" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:508 msgid "with a pipe" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:509 msgid "symbol" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:511 msgid "Like so::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:521 msgid "We don't actually use this anywhere in the manual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:524 msgid "Glossaries, Terms and Index" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:526 msgid "These are sphinx features." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:528 msgid "" "Index is used in the top section, right now only single index entries are " "used." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:530 msgid "" "Glossaries are used for some of the menu entry sections, but not all of them." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:533 msgid "Quotes" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:535 msgid "Quotes are done like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:541 msgid "This becomes a blockquote." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:543 msgid "I am not sure why you'd need quotes in a user manual..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:547 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:548 msgid "Wolthera" msgstr "Wolthera" 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 96ef343c8..fcf0ccaaf 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,1067 +1,1067 @@ # 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-04-22 03:41+0200\n" +"POT-Creation-Date: 2019-04-23 03:45+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/en/color_category/Kiki_matrix_profile.png" +msgstr "" + +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/en/color_category/Kiki_cLUTprofiles.png" +msgstr "" + #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group1.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group2.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group3.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group4.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/LUT_Management_Docker.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/color_category/Krita_HDR_1.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/color_category/Krita_HDR2.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_webcomic.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_print.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_games.svg" msgstr "" -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/en/color_category/Kiki_matrix_profile.png" -msgstr "" - -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/en/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: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/en/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/en/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 rec2020." 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 rec2020 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 argylcms 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 2807a73e2..2c5a06314 100644 --- a/locale/fr/LC_MESSAGES/contributors_manual/krita_manual_conventions.po +++ b/locale/fr/LC_MESSAGES/contributors_manual/krita_manual_conventions.po @@ -1,861 +1,861 @@ msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-04-21 03:37+0200\n" +"POT-Creation-Date: 2019-04-23 03:45+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/en/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: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: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: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: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: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:154 msgid "And figure directives for images with captions::" 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/en`` 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: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: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: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: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: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 "veridian" 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: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 msgid "explanation." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Another option" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Explanation." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:299 msgid "You can make them like this::" 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: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, hint: 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 "This looks like the following::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:402 msgid "Sphinx also adds::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:412 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:416 msgid "That said, horizontal rulers can be made with ``----``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:419 msgid "The rubric directive." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:420 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:426 msgid "So, when to use these?" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:427 msgid "" "Only use them when you think the subject is too minor to have a proper " "heading." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:429 msgid "Topic" msgstr "Sujet" #: ../../contributors_manual/krita_manual_conventions.rst:430 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:431 msgid "Rubric" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:432 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:434 msgid "Admonishments" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:434 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:437 msgid "Code Snippets" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:439 msgid "``Inline code snippets`` are done with ````backticks````." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:441 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:447 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:457 msgid "Becomes" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:467 msgid "some more..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:500 msgid "Other preformatted text" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:503 msgid "One can" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:504 msgid "preformat" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:505 msgid "text by" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:506 msgid "prepending" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:507 msgid "each line" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:508 msgid "with a pipe" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:509 msgid "symbol" msgstr "symbole" #: ../../contributors_manual/krita_manual_conventions.rst:511 msgid "Like so::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:521 msgid "We don't actually use this anywhere in the manual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:524 msgid "Glossaries, Terms and Index" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:526 msgid "These are sphinx features." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:528 msgid "" "Index is used in the top section, right now only single index entries are " "used." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:530 msgid "" "Glossaries are used for some of the menu entry sections, but not all of them." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:533 msgid "Quotes" msgstr "Guillemets" #: ../../contributors_manual/krita_manual_conventions.rst:535 msgid "Quotes are done like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:541 msgid "This becomes a blockquote." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:543 msgid "I am not sure why you'd need quotes in a user manual..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:547 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:548 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 60b7fb06c..e21535d62 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,1060 +1,1060 @@ msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-04-22 03:41+0200\n" +"POT-Creation-Date: 2019-04-23 03:45+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/en/color_category/Kiki_matrix_profile.png" +msgstr "" + +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/en/color_category/Kiki_cLUTprofiles.png" +msgstr "" + #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group1.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group2.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group3.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group4.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/LUT_Management_Docker.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/color_category/Krita_HDR_1.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/color_category/Krita_HDR2.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_webcomic.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_print.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_games.svg" msgstr "" -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/en/color_category/Kiki_matrix_profile.png" -msgstr "" - -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/en/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: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/en/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/en/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 "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 rec2020." 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 rec2020 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 argylcms manual `_" msgstr "" 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 b03df396f..77c6c498c 100644 --- a/locale/ja/LC_MESSAGES/contributors_manual/krita_manual_conventions.po +++ b/locale/ja/LC_MESSAGES/contributors_manual/krita_manual_conventions.po @@ -1,855 +1,855 @@ msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-04-21 03:37+0200\n" +"POT-Creation-Date: 2019-04-23 03:45+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/en/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: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: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: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: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: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:154 msgid "And figure directives for images with captions::" 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/en`` 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: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: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: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: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: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 "veridian" 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: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 msgid "explanation." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Another option" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Explanation." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:299 msgid "You can make them like this::" 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: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, hint: 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 "This looks like the following::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:402 msgid "Sphinx also adds::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:412 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:416 msgid "That said, horizontal rulers can be made with ``----``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:419 msgid "The rubric directive." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:420 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:426 msgid "So, when to use these?" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:427 msgid "" "Only use them when you think the subject is too minor to have a proper " "heading." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:429 msgid "Topic" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:430 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:431 msgid "Rubric" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:432 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:434 msgid "Admonishments" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:434 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:437 msgid "Code Snippets" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:439 msgid "``Inline code snippets`` are done with ````backticks````." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:441 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:447 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:457 msgid "Becomes" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:467 msgid "some more..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:500 msgid "Other preformatted text" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:503 msgid "One can" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:504 msgid "preformat" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:505 msgid "text by" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:506 msgid "prepending" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:507 msgid "each line" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:508 msgid "with a pipe" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:509 msgid "symbol" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:511 msgid "Like so::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:521 msgid "We don't actually use this anywhere in the manual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:524 msgid "Glossaries, Terms and Index" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:526 msgid "These are sphinx features." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:528 msgid "" "Index is used in the top section, right now only single index entries are " "used." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:530 msgid "" "Glossaries are used for some of the menu entry sections, but not all of them." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:533 msgid "Quotes" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:535 msgid "Quotes are done like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:541 msgid "This becomes a blockquote." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:543 msgid "I am not sure why you'd need quotes in a user manual..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:547 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:548 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 2d18aa55e..33d821258 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,1054 +1,1054 @@ msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-04-22 03:41+0200\n" +"POT-Creation-Date: 2019-04-23 03:45+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/en/color_category/Kiki_matrix_profile.png" +msgstr "" + +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/en/color_category/Kiki_cLUTprofiles.png" +msgstr "" + #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group1.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group2.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group3.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group4.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/LUT_Management_Docker.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/color_category/Krita_HDR_1.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/color_category/Krita_HDR2.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_webcomic.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_print.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_games.svg" msgstr "" -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/en/color_category/Kiki_matrix_profile.png" -msgstr "" - -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/en/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: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/en/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/en/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 rec2020." 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 rec2020 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 argylcms manual `_" msgstr "" diff --git a/locale/ko/LC_MESSAGES/404.po b/locale/ko/LC_MESSAGES/404.po index 5345d6014..37e6364d2 100644 --- a/locale/ko/LC_MESSAGES/404.po +++ b/locale/ko/LC_MESSAGES/404.po @@ -1,56 +1,61 @@ # 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. # Shinjo Park , 2019. # msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-28 03:20+0100\n" "PO-Revision-Date: 2019-04-22 16:16+0200\n" "Last-Translator: Shinjo Park \n" "Language-Team: Korean \n" +"Language: ko\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: ko\n" "Plural-Forms: nplurals=1; plural=0;\n" "X-Generator: Lokalize 18.12.3\n" #: ../../404.rst:None -msgid ".. image:: images/en/color_category/Kiki_cLUTprofiles.png\n" +msgid "" +".. image:: images/en/color_category/Kiki_cLUTprofiles.png\n" " :alt: Image of Kiki looking confused through books." msgstr "" ".. image:: images/en/color_category/Kiki_cLUTprofiles.png\n" " :alt: 책을 찾다가 길을 잃은 Kiki의 그림." #: ../../404.rst:5 msgid "File Not Found (404)" msgstr "파일을 찾을 수 없음(404)" #: ../../404.rst:10 msgid "This page does not exist." msgstr "이 페이지가 존재하지 않습니다." #: ../../404.rst:12 msgid "This might be because of the following:" msgstr "다음 이유 때문일 수 있습니다:" #: ../../404.rst:14 -msgid "We moved the manual from MediaWiki to Sphinx and with that came a lot of reorganization." +msgid "" +"We moved the manual from MediaWiki to Sphinx and with that came a lot of " +"reorganization." msgstr "" -"사용자 설명서를 미디어위키에서 Sphinx 기반으로 이전하면서 많은 부분이 " -"변경되었습니다." +"사용자 설명서를 미디어위키에서 Sphinx 기반으로 이전하면서 많은 부분이 변경되" +"었습니다." #: ../../404.rst:15 msgid "The page has been deprecated." msgstr "페이지가 폐기 예고되었습니다." #: ../../404.rst:16 msgid "Or a simple typo in the url." msgstr "URL에 오타가 있을 수 있습니다." #: ../../404.rst:18 -msgid "In all cases, you might be able to find the page you're looking for by using the search in the lefthand navigation." +msgid "" +"In all cases, you might be able to find the page you're looking for by using " +"the search in the lefthand navigation." msgstr "" "왼쪽의 탐색 창에서 검색 메뉴를 통하여 찾고자 하는 페이지를 찾을 수 있습니다." diff --git a/locale/ko/LC_MESSAGES/contributors_manual.po b/locale/ko/LC_MESSAGES/contributors_manual.po index c9feaffcc..0defcfa81 100644 --- a/locale/ko/LC_MESSAGES/contributors_manual.po +++ b/locale/ko/LC_MESSAGES/contributors_manual.po @@ -1,30 +1,30 @@ # 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. # Shinjo Park , 2019. # msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-19 03:36+0100\n" "PO-Revision-Date: 2019-04-22 16:22+0200\n" "Last-Translator: Shinjo Park \n" "Language-Team: Korean \n" +"Language: ko\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: ko\n" "Plural-Forms: nplurals=1; plural=0;\n" "X-Generator: Lokalize 18.12.3\n" #: ../../contributors_manual.rst:5 msgid "Contributors Manual" msgstr "기여자 설명서" #: ../../contributors_manual.rst:7 msgid "Everything you need to know to help out with Krita!" msgstr "Krita를 도울 수 있는 방법을 소개합니다!" #: ../../contributors_manual.rst:9 msgid "Contents:" msgstr "목차:" diff --git a/locale/ko/LC_MESSAGES/general_concepts.po b/locale/ko/LC_MESSAGES/general_concepts.po index dfc1ade79..b08a3ed2b 100644 --- a/locale/ko/LC_MESSAGES/general_concepts.po +++ b/locale/ko/LC_MESSAGES/general_concepts.po @@ -1,30 +1,32 @@ # 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. # Shinjo Park , 2019. # msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-19 03:36+0100\n" "PO-Revision-Date: 2019-04-22 16:21+0200\n" "Last-Translator: Shinjo Park \n" "Language-Team: Korean \n" +"Language: ko\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: ko\n" "Plural-Forms: nplurals=1; plural=0;\n" "X-Generator: Lokalize 18.12.3\n" #: ../../general_concepts.rst:5 msgid "General Concepts" msgstr "일반적 개념" #: ../../general_concepts.rst:7 -msgid "Learn about general art and technology concepts that are not specific to Krita." +msgid "" +"Learn about general art and technology concepts that are not specific to " +"Krita." msgstr "Krita에 한정된 것이 아닌 일반적인 미술과 기술 개념을 알아봅니다." #: ../../general_concepts.rst:9 msgid "Contents:" msgstr "목차:" diff --git a/locale/ko/LC_MESSAGES/index.po b/locale/ko/LC_MESSAGES/index.po index 36df419f0..5152a1161 100644 --- a/locale/ko/LC_MESSAGES/index.po +++ b/locale/ko/LC_MESSAGES/index.po @@ -1,138 +1,154 @@ # 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. # Shinjo Park , 2019. # msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-19 03:36+0100\n" "PO-Revision-Date: 2019-04-22 16:21+0200\n" "Last-Translator: Shinjo Park \n" "Language-Team: Korean \n" +"Language: ko\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: ko\n" "Plural-Forms: nplurals=1; plural=0;\n" "X-Generator: Lokalize 18.12.3\n" #: ../../index.rst:0 msgid ".. image:: images/en/Hero_userManual.jpg" msgstr ".. image:: images/en/Hero_userManual.jpg" #: ../../index.rst:0 msgid ".. image:: images/en/Hero_tutorials.jpg" msgstr ".. image:: images/en/Hero_tutorials.jpg" #: ../../index.rst:0 msgid ".. image:: images/en/Hero_getting_started.jpg" msgstr ".. image:: images/en/Hero_getting_started.jpg" #: ../../index.rst:0 msgid ".. image:: images/en/Hero_reference.jpg" msgstr ".. image:: images/en/Hero_reference.jpg" #: ../../index.rst:0 msgid ".. image:: images/en/Hero_general.jpg" msgstr ".. image:: images/en/Hero_general.jpg" #: ../../index.rst:0 msgid ".. image:: images/en/Hero_faq.jpg" msgstr ".. image:: images/en/Hero_faq.jpg" #: ../../index.rst:0 msgid ".. image:: images/en/Hero_resources.jpg" msgstr ".. image:: images/en/Hero_resources.jpg" #: ../../index.rst:5 msgid "Welcome to the Krita |version| Manual!" msgstr "Krita |version| 설명서에 오신 것을 환영합니다!" #: ../../index.rst:7 -msgid "Welcome to Krita's documentation page. Krita is a sketching and painting program designed for digital artists." +msgid "" +"Welcome to Krita's documentation page. Krita is a sketching and painting " +"program designed for digital artists." msgstr "" -"Krita 문서 페이지에 오신 것을 환영합니다. Krita는 디지털 아티스트를 위한 " -"스케치 및 페인팅 프로그램입니다." +"Krita 문서 페이지에 오신 것을 환영합니다. Krita는 디지털 아티스트를 위한 스케" +"치 및 페인팅 프로그램입니다." #: ../../index.rst:9 -msgid "As you learn about Krita, keep in mind that it is not intended as a replacement for Photoshop. This means that the other programs may have more features than Krita for image manipulation tasks, such as stitching together photos, while Krita's tools are most relevant to digital painting, concept art, illustration, and texturing. This fact accounts for a great deal of Krita's design." +msgid "" +"As you learn about Krita, keep in mind that it is not intended as a " +"replacement for Photoshop. This means that the other programs may have more " +"features than Krita for image manipulation tasks, such as stitching together " +"photos, while Krita's tools are most relevant to digital painting, concept " +"art, illustration, and texturing. This fact accounts for a great deal of " +"Krita's design." msgstr "" -"Krita를 사용하면서 느낄 수 있겠지만, Krita는 Photoshop을 대체하기 위한 " -"도구가 아닙니다. 사진을 이어 붙이는 등 이미지를 수정하는 기능은 Krita보다 " -"다른 프로그램이 더 강력할 수도 있습니다. Krita의 도구는 디지털 페인팅, 컨셉 " -"아트, 일러스트, 텍스처에 초점을 맞추고 있습니다. Krita는 이 기능을 중점으로 " -"설계되었습니다." +"Krita를 사용하면서 느낄 수 있겠지만, Krita는 Photoshop을 대체하기 위한 도구" +"가 아닙니다. 사진을 이어 붙이는 등 이미지를 수정하는 기능은 Krita보다 다른 프" +"로그램이 더 강력할 수도 있습니다. Krita의 도구는 디지털 페인팅, 컨셉 아트, 일" +"러스트, 텍스처에 초점을 맞추고 있습니다. Krita는 이 기능을 중점으로 설계되었" +"습니다." #: ../../index.rst:11 msgid "`The manual as epub `_" msgstr "" "`EPub 형식으로 설명서 보기 `_" #: ../../index.rst:16 msgid ":ref:`user_manual`" msgstr ":ref:`user_manual`" #: ../../index.rst:16 msgid ":ref:`tutorials`" msgstr ":ref:`tutorials`" #: ../../index.rst:18 -msgid "Discover Krita’s features through an online manual. Guides to help you transition from other applications." +msgid "" +"Discover Krita’s features through an online manual. Guides to help you " +"transition from other applications." msgstr "" -"Krita의 기능을 온라인 사용자 설명서에서 확인하십시오. 다른 프로그램에서 " -"전환하는 데 도움을 줍니다." +"Krita의 기능을 온라인 사용자 설명서에서 확인하십시오. 다른 프로그램에서 전환" +"하는 데 도움을 줍니다." #: ../../index.rst:18 -msgid "Learn through developer and user generated tutorials to see Krita in action." +msgid "" +"Learn through developer and user generated tutorials to see Krita in action." msgstr "" "Krita가 동작하는 모습을 개발자와 사용자들이 만든 튜토리얼에서 확인하십시오." #: ../../index.rst:24 msgid ":ref:`getting_started`" msgstr ":ref:`getting_started`" #: ../../index.rst:24 msgid ":ref:`reference_manual`" msgstr ":ref:`reference_manual`" #: ../../index.rst:26 msgid "New to Krita and don't know where to start?" msgstr "Krita를 처음 사용하십니까?" #: ../../index.rst:26 msgid "A quick run-down of all of the tools that are available" msgstr "사용 가능한 모든 도구 한눈에 보기" #: ../../index.rst:31 msgid ":ref:`general_concepts`" msgstr ":ref:`general_concepts`" #: ../../index.rst:31 msgid ":ref:`faq`" msgstr ":ref:`faq`" #: ../../index.rst:33 -msgid "Learn about general art and technology concepts that are not specific to Krita." +msgid "" +"Learn about general art and technology concepts that are not specific to " +"Krita." msgstr "Krita에 한정된 것이 아닌 일반적인 미술과 기술 개념을 알아봅니다." #: ../../index.rst:33 -msgid "Find answers to the most common questions about Krita and what it offers." +msgid "" +"Find answers to the most common questions about Krita and what it offers." msgstr "Krita와 그 기능에 대한 자주 묻는 질문과 답변을 봅니다." #: ../../index.rst:38 msgid ":ref:`resources_page`" msgstr ":ref:`resources_page`" #: ../../index.rst:38 msgid ":ref:`genindex`" msgstr ":ref:`genindex`" #: ../../index.rst:40 -msgid "Textures, brush packs, and python plugins to help add variety to your artwork." +msgid "" +"Textures, brush packs, and python plugins to help add variety to your " +"artwork." msgstr "아트워크를 풍부하게 만드는 텍스처, 브러시 팩, 파이썬 플러그인입니다." #: ../../index.rst:40 msgid "An index of the manual for searching terms by browsing." msgstr "단어별로 정렬된 검색 색인 목록입니다." diff --git a/locale/ko/LC_MESSAGES/reference_manual.po b/locale/ko/LC_MESSAGES/reference_manual.po index 2904a128f..fb483bf3f 100644 --- a/locale/ko/LC_MESSAGES/reference_manual.po +++ b/locale/ko/LC_MESSAGES/reference_manual.po @@ -1,30 +1,30 @@ # 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. # Shinjo Park , 2019. # msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-19 03:36+0100\n" "PO-Revision-Date: 2019-04-22 16:22+0200\n" "Last-Translator: Shinjo Park \n" "Language-Team: Korean \n" +"Language: ko\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: ko\n" "Plural-Forms: nplurals=1; plural=0;\n" "X-Generator: Lokalize 18.12.3\n" #: ../../reference_manual.rst:5 msgid "Reference Manual" msgstr "참조 문서" #: ../../reference_manual.rst:7 msgid "A quick run-down of all of the tools that are available" msgstr "사용 가능한 모든 도구 한눈에 보기" #: ../../reference_manual.rst:9 msgid "Contents:" msgstr "목차:" diff --git a/locale/ko/LC_MESSAGES/reference_manual/preferences.po b/locale/ko/LC_MESSAGES/reference_manual/preferences.po index 932c8c96c..5d2f7bf0e 100644 --- a/locale/ko/LC_MESSAGES/reference_manual/preferences.po +++ b/locale/ko/LC_MESSAGES/reference_manual/preferences.po @@ -1,59 +1,76 @@ # 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. # Shinjo Park , 2019. # msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-19 03:36+0100\n" "PO-Revision-Date: 2019-04-22 16:25+0200\n" "Last-Translator: Shinjo Park \n" "Language-Team: Korean \n" +"Language: ko\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: ko\n" "Plural-Forms: nplurals=1; plural=0;\n" "X-Generator: Lokalize 18.12.3\n" #: ../../reference_manual/preferences.rst:1 msgid "Krita's settings and preferences options." msgstr "Krita의 환경 설정 옵션입니다." #: ../../reference_manual/preferences.rst:16 msgid "Preferences" msgstr "환경 설정" #: ../../reference_manual/preferences.rst:18 -msgid "Krita is highly customizable and makes many settings and options available to customize through the Preferences area. These settings are accessed by going to :menuselection:`Settings --> Configure Krita`. On MacOS, the settings are under the topleft menu area, as you would expect of any program under MacOS." +msgid "" +"Krita is highly customizable and makes many settings and options available " +"to customize through the Preferences area. These settings are accessed by " +"going to :menuselection:`Settings --> Configure Krita`. On MacOS, the " +"settings are under the topleft menu area, as you would expect of any program " +"under MacOS." msgstr "" -"Krita는 환경 설정을 통하여 다양한 설정과 옵션을 변경할 수 있습니다. 해당 " -"설정은 :menuselection:`설정 --> Krita 설정`에서 확인할 수 있습니다. macOS를 " -"사용한다면 다른 macOS 프로그램처럼 왼쪽 위 메뉴 영역에서 설정을 변경할 수 " -"있습니다." +"Krita는 환경 설정을 통하여 다양한 설정과 옵션을 변경할 수 있습니다. 해당 설정" +"은 :menuselection:`설정 --> Krita 설정`에서 확인할 수 있습니다. macOS를 사용" +"한다면 다른 macOS 프로그램처럼 왼쪽 위 메뉴 영역에서 설정을 변경할 수 있습니" +"다." #: ../../reference_manual/preferences.rst:20 -msgid "Krita's preferences are saved in the file ``kritarc``. This file is located in ``%LOCALAPPDATA%\\`` on Windows, ``~/.config`` on Linux, and ``~/Library/Preferences`` on OS X. If you would like to back up your custom settings or synchronize them from one computer to another, you can just copy this file. It even works across platforms!" +msgid "" +"Krita's preferences are saved in the file ``kritarc``. This file is located " +"in ``%LOCALAPPDATA%\\`` on Windows, ``~/.config`` on Linux, and ``~/Library/" +"Preferences`` on OS X. If you would like to back up your custom settings or " +"synchronize them from one computer to another, you can just copy this file. " +"It even works across platforms!" msgstr "" "Krita 설정 파일은 ``kritarc`` 파일로 저장됩니다. 이 파일은 Windows에서는 ``" "%LOCALAPPDATA%\\``, 리눅스에서는 ``~/.config``, macOS에서는 ``~/Library/" "Preferences`` 아래에 저장됩니다. 사용자 정의 설정을 백업하거나 다른 컴퓨터와 " "동기화하려면 해당 파일을 복사하십시오. 플랫폼이 달라도 설정은 동일합니다!" #: ../../reference_manual/preferences.rst:22 -msgid "If you have installed Krita through the Windows store, the kritarc file will be in another location:" +msgid "" +"If you have installed Krita through the Windows store, the kritarc file will " +"be in another location:" msgstr "" "Windows 스토어에서 Krita를 설치했다면 kritarc 파일은 다른 위치에 저장됩니다:" #: ../../reference_manual/preferences.rst:24 -msgid ":file:`%LOCALAPPDATA%\\\\Packages\\\\49800Krita_{RANDOM STRING}\\\\LocalCache\\\\Local\\\\kritarc`" +msgid "" +":file:`%LOCALAPPDATA%\\\\Packages\\\\49800Krita_{RANDOM STRING}\\\\LocalCache" +"\\\\Local\\\\kritarc`" msgstr "" -":file:`%LOCALAPPDATA%\\\\Packages\\\\49800Krita_{RANDOM STRING}" -"\\\\LocalCache\\\\Local\\\\kritarc`" +":file:`%LOCALAPPDATA%\\\\Packages\\\\49800Krita_{RANDOM STRING}\\\\LocalCache" +"\\\\Local\\\\kritarc`" #: ../../reference_manual/preferences.rst:27 -msgid "Custom shortcuts are saved in a separate file ``kritashortcutsrc`` which can also be backed up in the same way. This is discussed further in the shortcuts section." +msgid "" +"Custom shortcuts are saved in a separate file ``kritashortcutsrc`` which can " +"also be backed up in the same way. This is discussed further in the " +"shortcuts section." msgstr "" -"사용자 정의 단축키는 ``kritashortcutsrc`` 파일에 저장되며 같은 방식으로 " -"백업할 수 있습니다. 단축키 부분에서 더 자세히 설명합니다." +"사용자 정의 단축키는 ``kritashortcutsrc`` 파일에 저장되며 같은 방식으로 백업" +"할 수 있습니다. 단축키 부분에서 더 자세히 설명합니다." diff --git a/locale/ko/LC_MESSAGES/reference_manual/tools.po b/locale/ko/LC_MESSAGES/reference_manual/tools.po index 68455f8b5..6abf59b58 100644 --- a/locale/ko/LC_MESSAGES/reference_manual/tools.po +++ b/locale/ko/LC_MESSAGES/reference_manual/tools.po @@ -1,26 +1,26 @@ # 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. # Shinjo Park , 2019. # msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-19 03:36+0100\n" "PO-Revision-Date: 2019-04-22 16:22+0200\n" "Last-Translator: Shinjo Park \n" "Language-Team: Korean \n" +"Language: ko\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: ko\n" "Plural-Forms: nplurals=1; plural=0;\n" "X-Generator: Lokalize 18.12.3\n" #: ../../reference_manual/tools.rst:5 msgid "Tools" msgstr "도구" #: ../../reference_manual/tools.rst:7 msgid "The contents of the toolbox docker." msgstr "도구 상자 독의 각각 도구입니다." diff --git a/locale/ko/LC_MESSAGES/tutorials.po b/locale/ko/LC_MESSAGES/tutorials.po index 531d85985..05353548a 100644 --- a/locale/ko/LC_MESSAGES/tutorials.po +++ b/locale/ko/LC_MESSAGES/tutorials.po @@ -1,31 +1,32 @@ # 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. # Shinjo Park , 2019. # msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-19 03:36+0100\n" "PO-Revision-Date: 2019-04-22 16:22+0200\n" "Last-Translator: Shinjo Park \n" "Language-Team: Korean \n" +"Language: ko\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: ko\n" "Plural-Forms: nplurals=1; plural=0;\n" "X-Generator: Lokalize 18.12.3\n" #: ../../tutorials.rst:5 msgid "Tutorials and Howto's" msgstr "튜토리얼과 따라하기" #: ../../tutorials.rst:7 -msgid "Learn through developer and user generated tutorials to see Krita in action." +msgid "" +"Learn through developer and user generated tutorials to see Krita in action." msgstr "" "Krita가 동작하는 모습을 개발자와 사용자들이 만든 튜토리얼에서 확인하십시오." #: ../../tutorials.rst:9 msgid "Contents:" msgstr "목차:" diff --git a/locale/ko/LC_MESSAGES/user_manual.po b/locale/ko/LC_MESSAGES/user_manual.po index 51b8743aa..b3a197cb9 100644 --- a/locale/ko/LC_MESSAGES/user_manual.po +++ b/locale/ko/LC_MESSAGES/user_manual.po @@ -1,32 +1,34 @@ # 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. # Shinjo Park , 2019. # msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-19 03:36+0100\n" "PO-Revision-Date: 2019-04-22 16:15+0200\n" "Last-Translator: Shinjo Park \n" "Language-Team: Korean \n" +"Language: ko\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -"Language: ko\n" "Plural-Forms: nplurals=1; plural=0;\n" "X-Generator: Lokalize 18.12.3\n" #: ../../user_manual.rst:5 msgid "User Manual" msgstr "사용자 설명서" #: ../../user_manual.rst:7 -msgid "Discover Krita’s features through an online manual. Guides to help you transition from other applications." +msgid "" +"Discover Krita’s features through an online manual. Guides to help you " +"transition from other applications." msgstr "" -"Krita의 기능을 온라인 사용자 설명서에서 확인하십시오. 다른 프로그램에서 " -"전환하는 데 도움을 줍니다." +"Krita의 기능을 온라인 사용자 설명서에서 확인하십시오. 다른 프로그램에서 전환" +"하는 데 도움을 줍니다." #: ../../user_manual.rst:9 msgid "Contents:" 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 d71ccc2fa..0082ea4a8 100644 --- a/locale/nl/LC_MESSAGES/contributors_manual/krita_manual_conventions.po +++ b/locale/nl/LC_MESSAGES/contributors_manual/krita_manual_conventions.po @@ -1,871 +1,871 @@ # 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-04-21 03:37+0200\n" +"POT-Creation-Date: 2019-04-23 03:45+0200\n" "PO-Revision-Date: 2019-03-06 12:26+0100\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 18.12.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/en/sample.png\n" " :alt: an image." msgstr "" ".. image:: images/en/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 "" #: ../../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 "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: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: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: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: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: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:154 msgid "And figure directives for images with captions::" 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/en`` 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: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: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: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: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: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 "veridian" 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: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 msgid "explanation." msgstr "uitleg." #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Another option" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Explanation." msgstr "Uitleg." #: ../../contributors_manual/krita_manual_conventions.rst:299 msgid "You can make them like this::" 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: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, hint: 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 "This looks like the following::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:402 msgid "Sphinx also adds::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:412 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:416 msgid "That said, horizontal rulers can be made with ``----``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:419 msgid "The rubric directive." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:420 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:426 msgid "So, when to use these?" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:427 msgid "" "Only use them when you think the subject is too minor to have a proper " "heading." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:429 msgid "Topic" msgstr "Onderwerp" #: ../../contributors_manual/krita_manual_conventions.rst:430 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:431 msgid "Rubric" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:432 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:434 msgid "Admonishments" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:434 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:437 msgid "Code Snippets" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:439 msgid "``Inline code snippets`` are done with ````backticks````." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:441 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:447 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:457 msgid "Becomes" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:467 msgid "some more..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:500 msgid "Other preformatted text" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:503 msgid "One can" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:504 msgid "preformat" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:505 msgid "text by" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:506 msgid "prepending" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:507 msgid "each line" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:508 msgid "with a pipe" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:509 msgid "symbol" msgstr "symbool" #: ../../contributors_manual/krita_manual_conventions.rst:511 msgid "Like so::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:521 msgid "We don't actually use this anywhere in the manual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:524 msgid "Glossaries, Terms and Index" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:526 msgid "These are sphinx features." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:528 msgid "" "Index is used in the top section, right now only single index entries are " "used." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:530 msgid "" "Glossaries are used for some of the menu entry sections, but not all of them." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:533 msgid "Quotes" msgstr "Aanhalingstekens" #: ../../contributors_manual/krita_manual_conventions.rst:535 msgid "Quotes are done like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:541 msgid "This becomes a blockquote." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:543 msgid "I am not sure why you'd need quotes in a user manual..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:547 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:548 msgid "Wolthera" msgstr "" 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 ebc3bd9df..c11d658b7 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,1066 +1,1066 @@ # 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-04-22 03:41+0200\n" +"POT-Creation-Date: 2019-04-23 03:45+0200\n" "PO-Revision-Date: 2019-02-19 17:04+0100\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 18.12.2\n" +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/en/color_category/Kiki_matrix_profile.png" +msgstr "" + +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/en/color_category/Kiki_cLUTprofiles.png" +msgstr "" + #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group1.png" msgstr "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group1.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group2.png" msgstr "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group2.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group3.png" msgstr "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group3.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group4.png" msgstr "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group4.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/LUT_Management_Docker.png" msgstr ".. image:: images/en/LUT_Management_Docker.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/color_category/Krita_HDR_1.svg" msgstr ".. image:: images/en/color_category/Krita_HDR_1.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/color_category/Krita_HDR2.svg" msgstr ".. image:: images/en/color_category/Krita_HDR2.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_webcomic.svg" msgstr "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_webcomic.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_print.svg" msgstr "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_print.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_games.svg" msgstr "" -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/en/color_category/Kiki_matrix_profile.png" -msgstr "" - -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/en/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: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 "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 "" #: ../../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/en/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/en/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 "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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "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 "" #: ../../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 rec2020." 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 "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 "" #: ../../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 "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 "" #: ../../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 "Afdrukken" #: ../../general_concepts/colors/color_managed_workflow.rst:342 msgid "sRGB or rec2020 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 "Spellen" #: ../../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 argylcms manual `_" msgstr "" 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 15b8da0b0..53350106b 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,1050 +1,1050 @@ # 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-04-21 03:37+0200\n" +"POT-Creation-Date: 2019-04-23 03:45+0200\n" "PO-Revision-Date: 2019-04-01 14:27+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\n" "X-POFile-IgnoreConsistency: Table\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/en/sample.png\n" " :alt: an image." msgstr "" ".. image:: images/en/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: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: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: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: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: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: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: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/en`` 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/en``. 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: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: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: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: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: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 "veridian" 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: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 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:296 msgid "Explanation." msgstr "Explicaçã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: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: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, hint: 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, hint: 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 "This looks like the following::" msgstr "Isto parece-se como seguinte::" #: ../../contributors_manual/krita_manual_conventions.rst:402 msgid "Sphinx also adds::" msgstr "O Sphinx também adiciona::" #: ../../contributors_manual/krita_manual_conventions.rst:412 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:416 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:419 msgid "The rubric directive." msgstr "A directiva 'rubric'." #: ../../contributors_manual/krita_manual_conventions.rst:420 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:426 msgid "So, when to use these?" msgstr "Por isso, quando devem ser usados?" #: ../../contributors_manual/krita_manual_conventions.rst:427 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:429 msgid "Topic" msgstr "Tópico" #: ../../contributors_manual/krita_manual_conventions.rst:430 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:431 msgid "Rubric" msgstr "Rubrica" #: ../../contributors_manual/krita_manual_conventions.rst:432 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:434 msgid "Admonishments" msgstr "Advertências" #: ../../contributors_manual/krita_manual_conventions.rst:434 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:437 msgid "Code Snippets" msgstr "Excertos de Código" #: ../../contributors_manual/krita_manual_conventions.rst:439 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:441 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:447 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:457 msgid "Becomes" msgstr "Torna-se" #: ../../contributors_manual/krita_manual_conventions.rst:467 msgid "some more..." msgstr "mais alguns..." #: ../../contributors_manual/krita_manual_conventions.rst:500 msgid "Other preformatted text" msgstr "Outro texto pré-formatado" #: ../../contributors_manual/krita_manual_conventions.rst:503 msgid "One can" msgstr "Uma pessoa pode" #: ../../contributors_manual/krita_manual_conventions.rst:504 msgid "preformat" msgstr "pré-formatar" #: ../../contributors_manual/krita_manual_conventions.rst:505 msgid "text by" msgstr "texto se" #: ../../contributors_manual/krita_manual_conventions.rst:506 msgid "prepending" msgstr "anteceder" #: ../../contributors_manual/krita_manual_conventions.rst:507 msgid "each line" msgstr "cada linha" #: ../../contributors_manual/krita_manual_conventions.rst:508 msgid "with a pipe" msgstr "com um símbolo" #: ../../contributors_manual/krita_manual_conventions.rst:509 msgid "symbol" msgstr "de barra vertical ('pipe')" #: ../../contributors_manual/krita_manual_conventions.rst:511 msgid "Like so::" msgstr "Como o seguinte:" #: ../../contributors_manual/krita_manual_conventions.rst:521 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:524 msgid "Glossaries, Terms and Index" msgstr "Glossários, Termos e Índice" #: ../../contributors_manual/krita_manual_conventions.rst:526 msgid "These are sphinx features." msgstr "Estas são funcionalidades do Sphinx." #: ../../contributors_manual/krita_manual_conventions.rst:528 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:530 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:533 msgid "Quotes" msgstr "Citações" #: ../../contributors_manual/krita_manual_conventions.rst:535 msgid "Quotes are done like this::" msgstr "As citações são feitas da seguinte forma::" #: ../../contributors_manual/krita_manual_conventions.rst:541 msgid "This becomes a blockquote." msgstr "Isto torna-se uma citação em bloco." #: ../../contributors_manual/krita_manual_conventions.rst:543 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:547 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:548 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 7b46fe3cf..68fe14037 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,1522 +1,1522 @@ # 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-04-22 03:41+0200\n" +"POT-Creation-Date: 2019-04-23 03:45+0200\n" "PO-Revision-Date: 2019-04-18 12:08+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\n" +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/en/color_category/Kiki_matrix_profile.png" +msgstr ".. image:: images/en/color_category/Kiki_matrix_profile.png" + +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/en/color_category/Kiki_cLUTprofiles.png" +msgstr ".. image:: images/en/color_category/Kiki_cLUTprofiles.png" + #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group1.png" msgstr "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group1.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group2.png" msgstr "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group2.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group3.png" msgstr "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group3.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group4.png" msgstr "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group4.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/LUT_Management_Docker.png" msgstr ".. image:: images/en/LUT_Management_Docker.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/color_category/Krita_HDR_1.svg" msgstr ".. image:: images/en/color_category/Krita_HDR_1.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/color_category/Krita_HDR2.svg" msgstr ".. image:: images/en/color_category/Krita_HDR2.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_webcomic.svg" msgstr "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_webcomic.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_print.svg" msgstr "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_print.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_games.svg" msgstr "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_games.svg" -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/en/color_category/Kiki_matrix_profile.png" -msgstr ".. image:: images/en/color_category/Kiki_matrix_profile.png" - -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/en/color_category/Kiki_cLUTprofiles.png" -msgstr ".. image:: images/en/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: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/en/color_category/Krita-colormanaged-workflow_text.svg" msgstr "" ".. image:: images/en/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/en/color_category/Krita-colormanaged-workflow_krita_text." "svg" msgstr "" ".. image:: images/en/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 rec2020." 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 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 "" "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 rec2020 if you can afford the bit-depth being 16bit." msgstr "" "sRGB ou rec2020 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 argylcms 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 8130be751..9dc829c70 100644 --- a/locale/sk/LC_MESSAGES/contributors_manual/krita_manual_conventions.po +++ b/locale/sk/LC_MESSAGES/contributors_manual/krita_manual_conventions.po @@ -1,857 +1,857 @@ # 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-04-21 03:37+0200\n" +"POT-Creation-Date: 2019-04-23 03:45+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/en/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: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: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: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: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: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:154 msgid "And figure directives for images with captions::" 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/en`` 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: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: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: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: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: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 "veridian" 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: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 msgid "explanation." msgstr "vysvetlenie." #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Another option" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Explanation." msgstr "Vysvetlenie." #: ../../contributors_manual/krita_manual_conventions.rst:299 msgid "You can make them like this::" 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: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, hint: 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 "This looks like the following::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:402 msgid "Sphinx also adds::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:412 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:416 msgid "That said, horizontal rulers can be made with ``----``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:419 msgid "The rubric directive." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:420 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:426 msgid "So, when to use these?" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:427 msgid "" "Only use them when you think the subject is too minor to have a proper " "heading." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:429 msgid "Topic" msgstr "Téma" #: ../../contributors_manual/krita_manual_conventions.rst:430 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:431 msgid "Rubric" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:432 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:434 msgid "Admonishments" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:434 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:437 msgid "Code Snippets" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:439 msgid "``Inline code snippets`` are done with ````backticks````." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:441 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:447 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:457 msgid "Becomes" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:467 msgid "some more..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:500 msgid "Other preformatted text" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:503 msgid "One can" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:504 msgid "preformat" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:505 msgid "text by" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:506 msgid "prepending" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:507 msgid "each line" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:508 msgid "with a pipe" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:509 msgid "symbol" msgstr "symbol" #: ../../contributors_manual/krita_manual_conventions.rst:511 msgid "Like so::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:521 msgid "We don't actually use this anywhere in the manual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:524 msgid "Glossaries, Terms and Index" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:526 msgid "These are sphinx features." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:528 msgid "" "Index is used in the top section, right now only single index entries are " "used." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:530 msgid "" "Glossaries are used for some of the menu entry sections, but not all of them." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:533 msgid "Quotes" msgstr "Úvodzovky" #: ../../contributors_manual/krita_manual_conventions.rst:535 msgid "Quotes are done like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:541 msgid "This becomes a blockquote." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:543 msgid "I am not sure why you'd need quotes in a user manual..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:547 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:548 msgid "Wolthera" msgstr "" 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 618c071c2..009b82962 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,1060 +1,1060 @@ # 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-04-22 03:41+0200\n" +"POT-Creation-Date: 2019-04-23 03:45+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/en/color_category/Kiki_matrix_profile.png" +msgstr "" + +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/en/color_category/Kiki_cLUTprofiles.png" +msgstr "" + #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group1.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group2.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group3.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group4.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/LUT_Management_Docker.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/color_category/Krita_HDR_1.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/color_category/Krita_HDR2.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_webcomic.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_print.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_games.svg" msgstr "" -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/en/color_category/Kiki_matrix_profile.png" -msgstr "" - -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/en/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: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/en/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/en/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 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 rec2020." 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 rec2020 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 argylcms 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 b2f5574a5..271cff3fa 100644 --- a/locale/sv/LC_MESSAGES/contributors_manual/krita_manual_conventions.po +++ b/locale/sv/LC_MESSAGES/contributors_manual/krita_manual_conventions.po @@ -1,921 +1,921 @@ # 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-04-21 03:37+0200\n" +"POT-Creation-Date: 2019-04-23 03:45+0200\n" "PO-Revision-Date: 2019-03-31 18:21+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/en/sample.png\n" " :alt: an image." msgstr "" ".. image:: images/en/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: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: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: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: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: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 pandocs konvertering av " "mediawiki till omstrukturerad text. 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 "" #: ../../contributors_manual/krita_manual_conventions.rst:154 msgid "And figure directives for images with captions::" 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/en`` 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: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: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: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: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: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 "veridian" 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: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 msgid "explanation." msgstr "förklaring." #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Another option" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Explanation." msgstr "Förklaring." #: ../../contributors_manual/krita_manual_conventions.rst:299 msgid "You can make them like this::" 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: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, hint: 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 "This looks like the following::" msgstr "Det ser ut på följande sätt::" #: ../../contributors_manual/krita_manual_conventions.rst:402 msgid "Sphinx also adds::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:412 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:416 msgid "That said, horizontal rulers can be made with ``----``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:419 msgid "The rubric directive." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:420 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:426 msgid "So, when to use these?" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:427 msgid "" "Only use them when you think the subject is too minor to have a proper " "heading." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:429 msgid "Topic" msgstr "Ämne" #: ../../contributors_manual/krita_manual_conventions.rst:430 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:431 msgid "Rubric" msgstr "Rubrik" #: ../../contributors_manual/krita_manual_conventions.rst:432 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:434 msgid "Admonishments" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:434 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:437 msgid "Code Snippets" msgstr "Kodsnuttar" #: ../../contributors_manual/krita_manual_conventions.rst:439 msgid "``Inline code snippets`` are done with ````backticks````." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:441 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:447 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:457 msgid "Becomes" msgstr "Blir" #: ../../contributors_manual/krita_manual_conventions.rst:467 msgid "some more..." msgstr "något mer..." #: ../../contributors_manual/krita_manual_conventions.rst:500 msgid "Other preformatted text" msgstr "Annan förformaterad text" #: ../../contributors_manual/krita_manual_conventions.rst:503 msgid "One can" msgstr "Man kan" #: ../../contributors_manual/krita_manual_conventions.rst:504 msgid "preformat" msgstr "förformatera" #: ../../contributors_manual/krita_manual_conventions.rst:505 msgid "text by" msgstr "text genom att" #: ../../contributors_manual/krita_manual_conventions.rst:506 msgid "prepending" msgstr "inleda" #: ../../contributors_manual/krita_manual_conventions.rst:507 msgid "each line" msgstr "varje rad" #: ../../contributors_manual/krita_manual_conventions.rst:508 msgid "with a pipe" msgstr "med en vertikal" #: ../../contributors_manual/krita_manual_conventions.rst:509 msgid "symbol" msgstr "linje" #: ../../contributors_manual/krita_manual_conventions.rst:511 msgid "Like so::" msgstr "På följande sätt::" #: ../../contributors_manual/krita_manual_conventions.rst:521 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:524 msgid "Glossaries, Terms and Index" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:526 msgid "These are sphinx features." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:528 msgid "" "Index is used in the top section, right now only single index entries are " "used." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:530 msgid "" "Glossaries are used for some of the menu entry sections, but not all of them." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:533 msgid "Quotes" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:535 msgid "Quotes are done like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:541 msgid "This becomes a blockquote." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:543 msgid "I am not sure why you'd need quotes in a user manual..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:547 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:548 msgid "Wolthera" msgstr "" 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 a155ef417..e84fbc764 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,1064 +1,1064 @@ # 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-04-22 03:41+0200\n" +"POT-Creation-Date: 2019-04-23 03:45+0200\n" "PO-Revision-Date: 2019-03-22 18:28+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/en/color_category/Kiki_matrix_profile.png" +msgstr ".. image:: images/en/color_category/Kiki_matrix_profile.png" + +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/en/color_category/Kiki_cLUTprofiles.png" +msgstr ".. image:: images/en/color_category/Kiki_cLUTprofiles.png" + #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group1.png" msgstr "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group1.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group2.png" msgstr "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group2.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group3.png" msgstr "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group3.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group4.png" msgstr "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group4.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/LUT_Management_Docker.png" msgstr ".. image:: images/en/LUT_Management_Docker.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/color_category/Krita_HDR_1.svg" msgstr ".. image:: images/en/color_category/Krita_HDR_1.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/color_category/Krita_HDR2.svg" msgstr ".. image:: images/en/color_category/Krita_HDR2.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_webcomic.svg" msgstr "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_webcomic.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_print.svg" msgstr "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_print.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_games.svg" msgstr "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_games.svg" -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/en/color_category/Kiki_matrix_profile.png" -msgstr ".. image:: images/en/color_category/Kiki_matrix_profile.png" - -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/en/color_category/Kiki_cLUTprofiles.png" -msgstr ".. image:: images/en/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: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 "" #: ../../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 "" #: ../../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 "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 "" #: ../../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 "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/en/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/en/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 "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 "" #: ../../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 "" #: ../../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 "Exporterar" #: ../../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 rec2020." 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 "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 "" #: ../../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 "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 rec2020 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 "Spel" #: ../../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 argylcms manual `_" msgstr "" 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 561bdde67..9b3287cf4 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,1030 +1,1030 @@ # 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-04-21 03:37+0200\n" +"POT-Creation-Date: 2019-04-23 03:45+0200\n" "PO-Revision-Date: 2019-03-31 08:44+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.03.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/en/sample.png\n" " :alt: an image." msgstr "" ".. image:: images/en/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: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: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: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: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: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:154 msgid "And figure directives for images with captions::" 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 "" "Підпис — зауважте, що перша літера підпису у команді вирівняна з параметром :" "figwidth:." #: ../../contributors_manual/krita_manual_conventions.rst:172 msgid "" "Images should go into the ``/images/en`` folder. By using ``/images`` " "instead of ``images``, sphinx will know the filepath isn't relative." msgstr "" "Зображення мають зберігатися у каталозі ``/images/en``. Використання ``/" "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: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: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: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: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: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 "veridian" 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: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 msgid "explanation." msgstr "пояснення." #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Another option" msgstr "Інший варіант" #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Explanation." msgstr "Пояснення." #: ../../contributors_manual/krita_manual_conventions.rst:299 msgid "You can make them like this::" 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: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, hint: 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 "This looks like the following::" msgstr "Це виглядає так::" #: ../../contributors_manual/krita_manual_conventions.rst:402 msgid "Sphinx also adds::" msgstr "Sphinx також додає::" #: ../../contributors_manual/krita_manual_conventions.rst:412 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:416 msgid "That said, horizontal rulers can be made with ``----``." msgstr "Тобто, горизонтальні лінійки можна додавати за допомогою ``----``." #: ../../contributors_manual/krita_manual_conventions.rst:419 msgid "The rubric directive." msgstr "Команда рубрики." #: ../../contributors_manual/krita_manual_conventions.rst:420 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:426 msgid "So, when to use these?" msgstr "Отже, коли нею слід користуватися?" #: ../../contributors_manual/krita_manual_conventions.rst:427 msgid "" "Only use them when you think the subject is too minor to have a proper " "heading." msgstr "" "Користуйтеся рубриками, лише якщо впевнені, що тема є надто незначною, щоб " "мати належний заголовок." #: ../../contributors_manual/krita_manual_conventions.rst:429 msgid "Topic" msgstr "Тема" #: ../../contributors_manual/krita_manual_conventions.rst:430 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:431 msgid "Rubric" msgstr "Рубрика" #: ../../contributors_manual/krita_manual_conventions.rst:432 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:434 msgid "Admonishments" msgstr "Попередження" #: ../../contributors_manual/krita_manual_conventions.rst:434 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:437 msgid "Code Snippets" msgstr "Фрагменти коду" #: ../../contributors_manual/krita_manual_conventions.rst:439 msgid "``Inline code snippets`` are done with ````backticks````." msgstr "" "``Вбудовані фрагменти коду`` можна створити за допомогою ````символів " "зворотних лапок````." #: ../../contributors_manual/krita_manual_conventions.rst:441 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:447 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:457 msgid "Becomes" msgstr "Перетворюється на" #: ../../contributors_manual/krita_manual_conventions.rst:467 msgid "some more..." msgstr "щось інше…" #: ../../contributors_manual/krita_manual_conventions.rst:500 msgid "Other preformatted text" msgstr "Інший попередньо форматований текст" #: ../../contributors_manual/krita_manual_conventions.rst:503 msgid "One can" msgstr "Можна" #: ../../contributors_manual/krita_manual_conventions.rst:504 msgid "preformat" msgstr "створювати фрагменти із попередньо визначеним форматуванням" #: ../../contributors_manual/krita_manual_conventions.rst:505 msgid "text by" msgstr "тексту" #: ../../contributors_manual/krita_manual_conventions.rst:506 msgid "prepending" msgstr "додаванням" #: ../../contributors_manual/krita_manual_conventions.rst:507 msgid "each line" msgstr "до кожного рядка" #: ../../contributors_manual/krita_manual_conventions.rst:508 msgid "with a pipe" msgstr "символу" #: ../../contributors_manual/krita_manual_conventions.rst:509 msgid "symbol" msgstr "вертикальної риски" #: ../../contributors_manual/krita_manual_conventions.rst:511 msgid "Like so::" msgstr "Ось так::" #: ../../contributors_manual/krita_manual_conventions.rst:521 msgid "We don't actually use this anywhere in the manual." msgstr "Насправді, ніде у підручнику ми ще це не використовували." #: ../../contributors_manual/krita_manual_conventions.rst:524 msgid "Glossaries, Terms and Index" msgstr "Глосарії, списки термінів та покажчик" #: ../../contributors_manual/krita_manual_conventions.rst:526 msgid "These are sphinx features." msgstr "Це можливості sphinx." #: ../../contributors_manual/krita_manual_conventions.rst:528 msgid "" "Index is used in the top section, right now only single index entries are " "used." msgstr "" "Покажчик використовується у основному розділі. У поточній версії " "використовуються лише одинарні записи покажчика (без підлеглих записів)." #: ../../contributors_manual/krita_manual_conventions.rst:530 msgid "" "Glossaries are used for some of the menu entry sections, but not all of them." msgstr "" "Глосарії використовуються для деяких розділів щодо пунктів меню, але не для " "усіх." #: ../../contributors_manual/krita_manual_conventions.rst:533 msgid "Quotes" msgstr "Цитати" #: ../../contributors_manual/krita_manual_conventions.rst:535 msgid "Quotes are done like this::" msgstr "Цитати мають такий вигляд::" #: ../../contributors_manual/krita_manual_conventions.rst:541 msgid "This becomes a blockquote." msgstr "Це стане цитатою." #: ../../contributors_manual/krita_manual_conventions.rst:543 msgid "I am not sure why you'd need quotes in a user manual..." msgstr "Не певний, чи потрібні цитати у підручнику для користувачів..." #: ../../contributors_manual/krita_manual_conventions.rst:547 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:548 msgid "Wolthera" msgstr "Wolthera" 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 6db70c77c..c7c0f8518 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-04-22 03:41+0200\n" +"POT-Creation-Date: 2019-04-23 03:45+0200\n" "PO-Revision-Date: 2019-04-17 07:28+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.03.70\n" +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/en/color_category/Kiki_matrix_profile.png" +msgstr ".. image:: images/en/color_category/Kiki_matrix_profile.png" + +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/en/color_category/Kiki_cLUTprofiles.png" +msgstr ".. image:: images/en/color_category/Kiki_cLUTprofiles.png" + #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group1.png" msgstr "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group1.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group2.png" msgstr "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group2.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group3.png" msgstr "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group3.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group4.png" msgstr "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group4.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/LUT_Management_Docker.png" msgstr ".. image:: images/en/LUT_Management_Docker.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/color_category/Krita_HDR_1.svg" msgstr ".. image:: images/en/color_category/Krita_HDR_1.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/color_category/Krita_HDR2.svg" msgstr ".. image:: images/en/color_category/Krita_HDR2.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_webcomic.svg" msgstr "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_webcomic.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_print.svg" msgstr "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_print.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_games.svg" msgstr "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_games.svg" -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/en/color_category/Kiki_matrix_profile.png" -msgstr ".. image:: images/en/color_category/Kiki_matrix_profile.png" - -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/en/color_category/Kiki_cLUTprofiles.png" -msgstr ".. image:: images/en/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: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/en/color_category/Krita-colormanaged-workflow_text.svg" msgstr "" ".. image:: images/en/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/en/color_category/Krita-colormanaged-workflow_krita_text." "svg" msgstr "" ".. image:: images/en/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 rec2020." 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 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 rec2020 if you can afford the bit-depth being 16bit." msgstr "" "sRGB або rec2020, якщо ви можете працювати із бітовою глибиною у 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 argylcms manual `_" msgstr "" "`Базовий огляд керування кольорами з підручника з argylcms `_" 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 1b454c6ba..eeed776a5 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,955 +1,955 @@ msgid "" msgstr "" "Project-Id-Version: kdeorg\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-04-21 03:37+0200\n" +"POT-Creation-Date: 2019-04-23 03:45+0200\n" "PO-Revision-Date: 2019-04-09 18:49\n" "Last-Translator: 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/en/sample.png\n" " :alt: an image." msgstr "" ".. image:: images/en/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 "" "`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 meta 标记以便搜索引擎读取::" #: ../../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: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: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: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: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 "" "这些使用惯例大致遵循了 pandoc 所用的由 Mediakiwi 到 reStructuredText 转换方" "式。如果你想要用超过四级的标题，你最好先想清楚页面会不会变得太杂乱，是不是考" "虑拆分这个页面。" #: ../../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:" "`实际显示的文字```。" #: ../../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 "" "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 为了能够收集兼容 " "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:154 msgid "And figure directives for images with captions::" msgstr "使用 figure 指令来生成带有说明文字的图像::" #: ../../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/en`` folder. By using ``/images`` " "instead of ``images``, sphinx will know the filepath isn't relative." msgstr "" "图像应被上传到 ``/images/en`` 文件夹。使用 ``/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: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: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: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: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 Manual`_`` 则会生成一个叫做 " "“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: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 "veridian" 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: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 msgid "explanation." msgstr "说明文字。" #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Another option" msgstr "另一个定义名称" #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Explanation." msgstr "说明文字。" #: ../../contributors_manual/krita_manual_conventions.rst:299 msgid "You can make them like this::" 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: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, hint: 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 "This looks like the following::" msgstr "它的用法如下::" #: ../../contributors_manual/krita_manual_conventions.rst:402 msgid "Sphinx also adds::" msgstr "Sphinx 还把参见添加为此类信息的一种::" #: ../../contributors_manual/krita_manual_conventions.rst:412 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:416 msgid "That said, horizontal rulers can be made with ``----``." msgstr "如需插入一条水平线，输入 ``----`` 即可。" #: ../../contributors_manual/krita_manual_conventions.rst:419 msgid "The rubric directive." msgstr "标题指令。" #: ../../contributors_manual/krita_manual_conventions.rst:420 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:426 msgid "So, when to use these?" msgstr "那么应该如何选用这些不同的文字类型呢？" #: ../../contributors_manual/krita_manual_conventions.rst:427 msgid "" "Only use them when you think the subject is too minor to have a proper " "heading." msgstr "只有当你认为主题的重要程度配不上一个正式标题时才使用它们。" #: ../../contributors_manual/krita_manual_conventions.rst:429 msgid "Topic" msgstr "主题" #: ../../contributors_manual/krita_manual_conventions.rst:430 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:431 msgid "Rubric" msgstr "标题" #: ../../contributors_manual/krita_manual_conventions.rst:432 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:434 msgid "Admonishments" msgstr "警告" #: ../../contributors_manual/krita_manual_conventions.rst:434 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:437 msgid "Code Snippets" msgstr "代码片段" #: ../../contributors_manual/krita_manual_conventions.rst:439 msgid "``Inline code snippets`` are done with ````backticks````." msgstr "``行内代码片段`` 可用 ````半角反引号```` 生成。" #: ../../contributors_manual/krita_manual_conventions.rst:441 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:447 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:457 msgid "Becomes" msgstr "显示为" #: ../../contributors_manual/krita_manual_conventions.rst:467 msgid "some more..." msgstr "其他例子" #: ../../contributors_manual/krita_manual_conventions.rst:500 msgid "Other preformatted text" msgstr "其他预格式化文本" #: ../../contributors_manual/krita_manual_conventions.rst:503 msgid "One can" msgstr "你可以" #: ../../contributors_manual/krita_manual_conventions.rst:504 msgid "preformat" msgstr "预格式化" #: ../../contributors_manual/krita_manual_conventions.rst:505 msgid "text by" msgstr "文本" #: ../../contributors_manual/krita_manual_conventions.rst:506 msgid "prepending" msgstr "只需在" #: ../../contributors_manual/krita_manual_conventions.rst:507 msgid "each line" msgstr "每行之前" #: ../../contributors_manual/krita_manual_conventions.rst:508 msgid "with a pipe" msgstr "加一个竖线" #: ../../contributors_manual/krita_manual_conventions.rst:509 msgid "symbol" msgstr "代号" #: ../../contributors_manual/krita_manual_conventions.rst:511 msgid "Like so::" msgstr "做法如下::" #: ../../contributors_manual/krita_manual_conventions.rst:521 msgid "We don't actually use this anywhere in the manual." msgstr "我们并没有在本手册中使用该功能。" #: ../../contributors_manual/krita_manual_conventions.rst:524 msgid "Glossaries, Terms and Index" msgstr "词汇表、术语和索引" #: ../../contributors_manual/krita_manual_conventions.rst:526 msgid "These are sphinx features." msgstr "这些都是 Sphinx 提供的特性。" #: ../../contributors_manual/krita_manual_conventions.rst:528 msgid "" "Index is used in the top section, right now only single index entries are " "used." msgstr "索引被显示在页面顶部，目前仅使用单一索引项。" #: ../../contributors_manual/krita_manual_conventions.rst:530 msgid "" "Glossaries are used for some of the menu entry sections, but not all of them." msgstr "词汇表被用在某些菜单项章节，但并非每页都有。" #: ../../contributors_manual/krita_manual_conventions.rst:533 msgid "Quotes" msgstr "引号" #: ../../contributors_manual/krita_manual_conventions.rst:535 msgid "Quotes are done like this::" msgstr "引用通过下述方式生成::" #: ../../contributors_manual/krita_manual_conventions.rst:541 msgid "This becomes a blockquote." msgstr "这会变成块引用。" #: ../../contributors_manual/krita_manual_conventions.rst:543 msgid "I am not sure why you'd need quotes in a user manual..." msgstr "我搞不懂为什么在用户手册里要引用..." #: ../../contributors_manual/krita_manual_conventions.rst:547 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:548 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 cc3a0ac5d..67eece7c5 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,1417 +1,1417 @@ msgid "" msgstr "" "Project-Id-Version: kdeorg\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-04-22 03:41+0200\n" +"POT-Creation-Date: 2019-04-23 03:45+0200\n" "PO-Revision-Date: 2019-04-09 18:50\n" "Last-Translator: 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/en/color_category/Kiki_matrix_profile.png" +msgstr ".. image:: images/en/color_category/Kiki_matrix_profile.png" + +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/en/color_category/Kiki_cLUTprofiles.png" +msgstr ".. image:: images/en/color_category/Kiki_cLUTprofiles.png" + #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group1.png" msgstr "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group1.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group2.png" msgstr "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group2.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group3.png" msgstr "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group3.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group4.png" msgstr "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group4.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/LUT_Management_Docker.png" msgstr ".. image:: images/en/LUT_Management_Docker.png" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/color_category/Krita_HDR_1.svg" msgstr ".. image:: images/en/color_category/Krita_HDR_1.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/color_category/Krita_HDR2.svg" msgstr ".. image:: images/en/color_category/Krita_HDR2.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_webcomic.svg" msgstr "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_webcomic.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_print.svg" msgstr "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_print.svg" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_games.svg" msgstr "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_games.svg" -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/en/color_category/Kiki_matrix_profile.png" -msgstr ".. image:: images/en/color_category/Kiki_matrix_profile.png" - -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/en/color_category/Kiki_cLUTprofiles.png" -msgstr ".. image:: images/en/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: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 "让我们在脑海里想象一个幼儿园：" #: ../../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 "" "第一组使用的颜色是朱红、明黄和群青。他们绘制的三角形的红色很鲜明，但他们绘制" "的圆形的绿色却很浑浊。这是因为群青的颜色实在是太暗了，用它很难调出好看的绿色" "系。" #: ../../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 "" "它的工作方式是将一种颜色转换到参考色彩空间 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 #, fuzzy #| msgid "" #| "Krita has two systems dedicated to color management. On one hand we have " #| "**lcms2**, which deal with ICC profiles, and on the other we have " #| "**OCIO**, which deal with LUT color management." 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 #, fuzzy #| 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 grey 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 `." 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 "" "用于 ICC 的特性文件随 Krita 预装，用于 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 #, fuzzy #| msgid "" #| "Knowing this about these spaces of course doesn't give you an idea how to " #| "use them, but it does make it easier to explain how to use them. So let " #| "us look at a typical color management workflow:" msgid "" "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/en/color_category/Krita-colormanaged-workflow_text.svg" msgstr "" ".. image:: images/en/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/en/color_category/Krita-colormanaged-workflow_krita_text." "svg" msgstr "" ".. image:: images/en/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 "" "尽管如此，了解工作空间的相关知识对于画手来说还是相当有用的。在不同的工作空间" "下面运用滤镜和混合颜色的结果会有所不同，而如果要运用像 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 #, fuzzy #| msgid "" #| "Overall, it is kinda useful to keep things like viewing conditions in the " #| "back of your mind. Many professional artists use a mid-grey color as " #| "their default canvas background because they find they create much more " #| "dynamic images due to having improved their viewing conditions. It is " #| "also why a lot of graphics programs, including Krita, come with a dark " #| "theme nowadays. (Though, of course this might also be because dark themes " #| "can be considered cool, who knows.)" msgid "" "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 预装的。阶调矩阵特性文件中包含了各个坐标的参数和参数之" "间的插值，以此确定色彩空间的确切体积。因为它们是预装文件，Krita 的色彩空间浏" "览器已经为它们准备了详尽的介绍资料。这些特性文件适合用作工作空间。" #: ../../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 "" "这种特性文件并不常见，主要用于描述打印机设备空间，如 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 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 #, fuzzy #| msgid "" #| "A in between solution between perceptual and absolute, relative will try " #| "to fit whatever colors it can match between color spaces. It does this by " #| "aligning the white and black points. It cuts off the rest to their " #| "respective borders. This is what all matrix shaper profiles default to " #| "during conversion, because the ICC v4 workflow specifies to only use " #| "Relative Colorimetric for matrix shaper profiles." msgid "" "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 #, fuzzy #| 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 'interoperability with " #| "other programs'. This is also why Krita defaults to V2, and we recommend " #| "using V2 when you aren't certain if the other programs you are using " #| "support V4." msgid "" "*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 面板上的黑要更亮，它与一间被彻底密封起" "来的房间内部的黑根本没有可比性。" #: ../../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 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 面板里创建一个类似的特性文件。在这个场景下需要创建" "的是 '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 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 #, fuzzy #| msgid "" #| "If you want to have a properly color managed workflow, you have one made " #| "customly for the input device (your screen) and the output devices (your " #| "printer, or target screen). For web the output is always sRGB." 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 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 #, fuzzy #| msgid "" #| "Use the appropriate color management for the appropriate workflow. If you " #| "are working with Blender, you will be better off using OCIO, than ICC. IF " #| "you are working with Scribus or Photoshop, use ICC." msgid "" "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 "" "现实中并没有一种色彩管理手段可以图像在屏幕显示和打印输出之间保持完全一致的颜" "色。" #: ../../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 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 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." 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 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 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 "" "你可能在与一些其他应用程序进行互通时遇到一些问题。其中一个重要的问题发生在 " "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 #, fuzzy #| msgid "" #| "sRGB, ICC version 2, sRGB trc for the internet, and a specialized CMYK " #| "profile from the printing house for the printed images." 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、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”，但记得在创建新文档时为 ICC 选择 sRGB 色彩特性文件。" #: ../../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 或者其他应用对其进行优化处" "理。在此场景中选用 sRGB 的理由是你可以假设绝大多数受众都不会为他们的屏幕进行" "特性化，而他们的屏幕大概也不会高级到可以支持宽色域之类的特性。所以我们应该默" "认使用 sRGB 来转换用于互联网的图像。" #: ../../general_concepts/colors/color_managed_workflow.rst:333 msgid "Print" msgstr "Print" #: ../../general_concepts/colors/color_managed_workflow.rst:342 msgid "sRGB or rec2020 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 #, fuzzy #| msgid "" #| "You can set the advanced color selector to transform to a given profile " #| "via :menuselection:`Settings --> Configure Krita --> Advanced color " #| "selector settings`. There, tick :guilabel:`Color selector uses a " #| "different color space than the image` and select the CMYK profile you are " #| "aiming for. This will limit your colors a little bit, but keep all the " #| "nice filter and blending options from RGB." msgid "" "You can set the advanced color selector to transform to a given profile via :" "menuselection:`Settings --> Configure Krita --> Color Selector Settings`. " "There, tick :guilabel:`Color Selector Uses Different Color Space than Image` " "and select the CMYK profile you are aiming for. This will limit your colors " "a little bit, but keep all the nice filter and blending options from RGB." 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 "" "`Gamma 校正的基础知识 `_" #: ../../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 渲染器编码的图像会被提示其 gamma 编码将造成图像过暗" "的说明 `_" #: ../../general_concepts/colors/color_managed_workflow.rst:377 msgid "" "`2d examples of the effect of gamma-encoding on color maths `_" msgstr "" "`Gamma 编码方式对于色彩运算的影响的 2D 示例 `_" #: ../../general_concepts/colors/color_managed_workflow.rst:378 msgid "" "`Basic overview of color management from argylcms 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 904279e3e..0e375f991 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,858 +1,858 @@ # 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-04-21 03:37+0200\n" +"POT-Creation-Date: 2019-04-23 03:45+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/en/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: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: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: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: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: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:154 msgid "And figure directives for images with captions::" 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/en`` 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: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: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: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: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: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 "veridian" 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: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 msgid "explanation." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Another option" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:296 msgid "Explanation." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:299 msgid "You can make them like this::" 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: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, hint: 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 "This looks like the following::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:402 msgid "Sphinx also adds::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:412 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:416 msgid "That said, horizontal rulers can be made with ``----``." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:419 msgid "The rubric directive." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:420 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:426 msgid "So, when to use these?" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:427 msgid "" "Only use them when you think the subject is too minor to have a proper " "heading." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:429 msgid "Topic" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:430 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:431 msgid "Rubric" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:432 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:434 msgid "Admonishments" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:434 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:437 msgid "Code Snippets" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:439 msgid "``Inline code snippets`` are done with ````backticks````." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:441 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:447 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:457 msgid "Becomes" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:467 msgid "some more..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:500 msgid "Other preformatted text" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:503 msgid "One can" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:504 msgid "preformat" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:505 msgid "text by" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:506 msgid "prepending" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:507 msgid "each line" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:508 msgid "with a pipe" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:509 msgid "symbol" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:511 msgid "Like so::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:521 msgid "We don't actually use this anywhere in the manual." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:524 msgid "Glossaries, Terms and Index" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:526 msgid "These are sphinx features." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:528 msgid "" "Index is used in the top section, right now only single index entries are " "used." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:530 msgid "" "Glossaries are used for some of the menu entry sections, but not all of them." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:533 msgid "Quotes" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:535 msgid "Quotes are done like this::" msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:541 msgid "This becomes a blockquote." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:543 msgid "I am not sure why you'd need quotes in a user manual..." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:547 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:548 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 d08686c0b..c0374381c 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,1057 +1,1057 @@ # 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-04-22 03:41+0200\n" +"POT-Creation-Date: 2019-04-23 03:45+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/en/color_category/Kiki_matrix_profile.png" +msgstr "" + +#: ../../general_concepts/colors/color_managed_workflow.rst:0 +msgid ".. image:: images/en/color_category/Kiki_cLUTprofiles.png" +msgstr "" + #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group1.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group2.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group3.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita_2_9_colormanagement_group4.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/LUT_Management_Docker.png" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/color_category/Krita_HDR_1.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid ".. image:: images/en/color_category/Krita_HDR2.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_webcomic.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_print.svg" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:None msgid "" ".. image:: images/en/color_category/Krita-colormanaged-workflow_games.svg" msgstr "" -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/en/color_category/Kiki_matrix_profile.png" -msgstr "" - -#: ../../general_concepts/colors/color_managed_workflow.rst:0 -msgid ".. image:: images/en/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: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/en/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/en/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 rec2020." 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 rec2020 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 argylcms manual `_" msgstr ""