diff --git a/locale/ca/LC_MESSAGES/user_manual/getting_started/basic_concepts.po b/locale/ca/LC_MESSAGES/user_manual/getting_started/basic_concepts.po index a58499d38..770bf4842 100644 --- a/locale/ca/LC_MESSAGES/user_manual/getting_started/basic_concepts.po +++ b/locale/ca/LC_MESSAGES/user_manual/getting_started/basic_concepts.po @@ -1,1488 +1,1488 @@ # Translation of docs_krita_org_user_manual___getting_started___basic_concepts.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: " -"docs_krita_org_user_manual___getting_started___basic_concepts\n" +"Project-Id-Version: docs_krita_org_user_manual___getting_started___basic_conce" +"pts\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-25 03:36+0100\n" -"PO-Revision-Date: 2019-03-12 17:11+0100\n" +"PO-Revision-Date: 2019-03-14 23:22+0100\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/getting_started/basic_concepts.rst:None msgid ".. image:: images/en/Pixels-brushstroke.png" msgstr ".. image:: images/en/Pixels-brushstroke.png" #: ../../user_manual/getting_started/basic_concepts.rst:None msgid ".. image:: images/en/Dockers.png" msgstr ".. image:: images/en/Dockers.png" #: ../../user_manual/getting_started/basic_concepts.rst:None msgid ".. image:: images/en/Multi-window.png" msgstr ".. image:: images/en/Multi-window.png" #: ../../user_manual/getting_started/basic_concepts.rst:None msgid ".. image:: images/en/Canvas-krita.png" msgstr ".. image:: images/en/Canvas-krita.png" #: ../../user_manual/getting_started/basic_concepts.rst:None msgid ".. image:: images/en/Krita_ghostlady_1.png" msgstr ".. image:: images/en/Krita_ghostlady_1.png" #: ../../user_manual/getting_started/basic_concepts.rst:None msgid ".. image:: images/en/Krita_ghostlady_2.png" msgstr ".. image:: images/en/Krita_ghostlady_2.png" #: ../../user_manual/getting_started/basic_concepts.rst:None msgid ".. image:: images/en/Krita_ghostlady_3.png" msgstr ".. image:: images/en/Krita_ghostlady_3.png" #: ../../user_manual/getting_started/basic_concepts.rst:None msgid ".. image:: images/en/Krita_transforms_free.png" msgstr ".. image:: images/en/Krita_transforms_free.png" #: ../../user_manual/getting_started/basic_concepts.rst:None msgid ".. image:: images/en/Introduction_to_animation_walkcycle_02.gif" msgstr ".. image:: images/en/Introduction_to_animation_walkcycle_02.gif" #: ../../user_manual/getting_started/basic_concepts.rst:1 msgid "An overview of the basic concepts of Krita." msgstr "Una visió general dels conceptes bàsics del Krita." #: ../../user_manual/getting_started/basic_concepts.rst:20 msgid "Basic Concepts" msgstr "Conceptes bàsics" #: ../../user_manual/getting_started/basic_concepts.rst:22 msgid "" "If this is your first foray into digital painting, this page should give you " "a brief introduction to the basic but important concepts required for " "getting started with digital painting in Krita." msgstr "" "Si aquesta és la vostra primera incursió en la pintura digital, aquesta " "pàgina us hauria d'oferir una breu introducció als conceptes bàsics però " "importants necessaris per a començar amb la pintura digital al Krita." #: ../../user_manual/getting_started/basic_concepts.rst:24 msgid "" "This page is very, very long because it tries to cover all the important " "things you should know Krita is capable of, and Krita is really powerful. So " "this page can also be considered a guide through Krita's most important " "functionality. Hopefully, it will help you grasp what buttons are for, even " "if you don't know the exact purpose of them." msgstr "" "Aquesta pàgina és molt, molt llarga perquè tracta de cobrir totes les coses " "importants que heu de saber que el Krita és capaç de fer, i el Krita és " "realment poderós. De manera que aquesta pàgina també es pot considerar una " "guia a través de la funcionalitat més important del Krita. Amb sort, us " "ajudarà a comprendre els botons, fins i tot si no coneixeu el seu propòsit " "exacte." #: ../../user_manual/getting_started/basic_concepts.rst:26 msgid "Contents" msgstr "Contingut" #: ../../user_manual/getting_started/basic_concepts.rst:29 msgid "Raster and Vector" msgstr "Rasteritzat i vectors" #: ../../user_manual/getting_started/basic_concepts.rst:31 msgid "" "Even though Krita is primarily a raster based application, it has some " "vector editing capabilities as well. If you are new to Digital painting " "medium, it is necessary that you know the concepts of raster and Vector." msgstr "" "Tot i que el Krita és principalment una aplicació basada en rasteritzat, " "també té algunes capacitats d'edició vectorial. Si sou nou al mitjà de la " "pintura digital, és necessari que conegueu els conceptes del rasteritzat i " "dels vectors." #: ../../user_manual/getting_started/basic_concepts.rst:33 msgid "" "In digital imaging, a pixel (Picture Element) is a basic and lowest element " "of an Image. It is basically a grid of points each displaying specific " "color. Raster editing is manipulating and editing these pixels. For example " "when you take a 1-pixel brush which is colored black and painting on the " "white canvas in Krita you are actually changing the color of the pixel " "beneath your brush from white to black. When you zoom in and see a brush " "stroke you can notice many small squares with colors, these are pixels" msgstr "" "A les imatges digitals, un píxel (element de la imatge) és un element bàsic " "i el més baix d'una imatge. Bàsicament es tracta d'una quadrícula de punts " "on cadascun mostra un color específic. L'edició rasteritzada és la " "manipulació i edició d'aquests píxels. Per exemple, quan agafeu un pinzell " "de píxels d'1 píxel que és de color negre i pinteu sobre el llenç blanc del " "Krita, en realitat estareu canviant el color blanc del píxel sota el pinzell " "a negre. En fer apropament i veure un traç del pinzell, podreu observar " "molts quadrats petits amb colors, aquests són els píxels." # skip-rule: barb-uns #: ../../user_manual/getting_started/basic_concepts.rst:38 msgid "" "In contrast, vector graphic work is based on mathematical expressions. They " "are independent of the pixel. For example, when you draw a rectangle on a " "vector layer in Krita you are actually drawing paths passing through points " "called nodes which are located on specific coordinates on the 'x' and 'y' " "axes. When you re-size or move these points the computer calculates and " "redraws the path and displays the newly formed shape to you. Hence you can " "re-size the vector shape to any extent without any loss in quality." msgstr "" "En canvi, el treball gràfic vectorial es basa en expressions matemàtiques. " "Aquestes són independents del píxel. Per exemple, quan dibuixeu un rectangle " "en una capa vectorial en el Krita, en realitat, dibuixeu trajectes que " "passen per punts anomenats nodes que es troben en unes coordenades " "específiques dels eixos «X» i «Y». Quan torneu a reamidar o moure aquests " "punts, l'ordinador calcularà i tornarà a dibuixar el trajecte i us mostrarà " "la forma que ha pres. Per tant, podeu tornar a reamidar la forma vectorial " "en qualsevol mesura sense cap pèrdua de qualitat." #: ../../user_manual/getting_started/basic_concepts.rst:40 msgid "In Krita, everything which is not on a vector layer is raster based." msgstr "" "Al Krita, tot el que no es troba en una capa vectorial està basat en " "rasteritzat." #: ../../user_manual/getting_started/basic_concepts.rst:43 msgid "Images, Views and Windows" msgstr "Imatges, vistes i finestres" #: ../../user_manual/getting_started/basic_concepts.rst:45 msgid "" "In a painting program, there are three major containers that make up your " "work-space." msgstr "" "En un programa de pintura, hi ha tres contenidors principals que conformen " "el vostre espai de treball." #: ../../user_manual/getting_started/basic_concepts.rst:48 msgid "Image" msgstr "Imatge" #: ../../user_manual/getting_started/basic_concepts.rst:50 msgid "The most important one is the **Image**." msgstr "El més important és la **imatge**." # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:52 msgid "" "This is an individual copy of the image you opened or made via the file " "dialog, and where you edit your file. Krita can allow you to open the file " "as a new copy via the :guilabel:`File` menu, or to save it as a new file, or " "make an incremental save. An image contains layers, a color space, a canvas " "size and metadata such as creator, data created, and DPI. Krita can open " "multiple images at once, you can switch between them via the :guilabel:" "`Window` menu." msgstr "" "Aquesta és una còpia individual de la imatge que heu obert o fet mitjançant " "el diàleg de fitxer i on editareu el vostre fitxer. El Krita permet obrir el " "fitxer com a una còpia nova a través del menú :guilabel:`Fitxer`, desar-lo " "com a fitxer nou o fer un desament incremental. Una imatge conté capes, un " "espai de color, una mida del llenç i metadades com ara el creador, dades " "creades i PPP. El Krita pot obrir múltiples imatges alhora, podreu canviar " "entre elles mitjançant el menú :guilabel:`Finestra`." #: ../../user_manual/getting_started/basic_concepts.rst:54 msgid "" "Because the image is a working copy of the image on the hard drive, you can " "do a lot of little saving tricks with it:" msgstr "" "A causa que la imatge és una còpia de treball de la imatge en el disc dur, " "podreu fer molts petits trucs de desament amb ella:" #: ../../user_manual/getting_started/basic_concepts.rst:56 msgid "New" msgstr "Nova" # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:57 msgid "" "Makes a new image. When you press :menuselection:`Save`, you make a new file " "on the hard drive." msgstr "" "Crea una imatge nova. Quan premeu :menuselection:`Desa`, creareu un fitxer " "nou al disc dur." #: ../../user_manual/getting_started/basic_concepts.rst:58 msgid "Open" msgstr "Obre" # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:59 msgid "" "Makes an internal copy of an existing image. When you press :menuselection:" "`Save`, you will overwrite the original existing image with your working " "copy." msgstr "" "Crea una còpia interna d'una imatge existent. Quan premeu :menuselection:" "`Desa`, sobreescriureu la imatge original existent amb la vostra còpia de " "treball." #: ../../user_manual/getting_started/basic_concepts.rst:60 msgid "Open existing Document as Untitled Document" msgstr "Obre un document existent com a un document sense títol" # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:61 msgid "" "Similar to :menuselection:`Open`, however, :menuselection:`Save` will " "request you to specify a saving location: you're making a new copy. This is " "similar to :menuselection:`Import` in other programs." msgstr "" "Similar a :menuselection:`Obre`, malgrat això, :menuselection:`Desa` us " "demanarà que especifiqueu una ubicació de desament: creareu una còpia nova. " "Això és similar a :menuselection:`Importa` en altres programes." #: ../../user_manual/getting_started/basic_concepts.rst:62 msgid "Create Copy From Current Image" msgstr "Crea una còpia des de la imatge actual" # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:63 msgid "" "Similar to :menuselection:`Open existing Document as Untitled Document` but " "with the currently selected image." msgstr "" "Similar a :menuselection:`Obre un document existent com a un document sense " "títol` però amb la imatge actualment seleccionada." #: ../../user_manual/getting_started/basic_concepts.rst:65 msgid "Save incremental" msgstr "Desament incremental" # skip-rule: kct-snapshot #: ../../user_manual/getting_started/basic_concepts.rst:65 msgid "" "Allows you to quickly make a snapshot of the current image by making a new " "file with a version number added to it." msgstr "" "Permet fer una instantània ràpida de la imatge actual creant un fitxer nou " "amb un número de versió afegit." #: ../../user_manual/getting_started/basic_concepts.rst:67 msgid "" "These options are great for people doing production work, who need to switch " "between files quickly or have backup files in case they do something " "extreme. Krita also has a file backup system in the form of auto-saves and " "back files and crash recovery. You can configure these in the general " "settings." msgstr "" "Aquestes opcions són excel·lents per a les persones que realitzen treballs " "de producció, les quals necessiten canviar entre fitxers amb rapidesa o " "tenir fitxers de còpia de seguretat en cas de fer quelcom extrem. El Krita " "també té un sistema de còpia de seguretat dels fitxers en forma de desament " "automàtic i fitxers de resguard i per a la recuperació de bloqueigs. Podeu " "configurar-los als ajustaments generals." #: ../../user_manual/getting_started/basic_concepts.rst:69 msgid "You view the image via a **View**." msgstr "Veureu la imatge a través d'una **vista**." #: ../../user_manual/getting_started/basic_concepts.rst:72 msgid "View" msgstr "Vista" # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:74 msgid "" "A view is a window onto your image. Krita allows you to have multiple views, " "and you can manipulate the view to zoom, rotate and mirror and modify the " "color of the way you see an image without editing the image itself. This is " "very useful for artists, as changing the way they view the image is a common " "way to diagnose mistakes, like skewing to one side. Mirroring with :kbd:`M` " "makes such skewing easy to identify." msgstr "" "Una vista és una finestra amb la vostra imatge. El Krita permet tenir " "múltiples vistes i podreu manipular la vista per fer zoom, girar, emmirallar " "i modificar el color de manera que veureu la imatge sense editar-la. Això és " "molt útil per als artistes, ja que canviar la manera de veure la imatge és " "una manera comuna de diagnosticar els errors, com ara inclinar-se cap a un " "costat. Emmirallar amb :kbd:`M` fa que aquesta inclinació sigui fàcil " "d'identificar." #: ../../user_manual/getting_started/basic_concepts.rst:77 msgid "" "If you have trouble drawing certain curves you will enjoy using rotation for " "drawing, and of course, there is zooming in and out for precision and rough " "work." msgstr "" "Si teniu problemes per a dibuixar determinades corbes, gaudireu utilitzant " "la rotació per a dibuixar i, per descomptat, hi ha un zoom per a més " "precisió i el treball rude." #: ../../user_manual/getting_started/basic_concepts.rst:82 msgid ".. image:: images/en/Krita_multiple_views.png" msgstr ".. image:: images/en/Krita_multiple_views.png" #: ../../user_manual/getting_started/basic_concepts.rst:82 msgid "Multiple views of the same image in Krita" msgstr "Múltiples vistes de la mateixa imatge en el Krita" # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe,kct-tab #: ../../user_manual/getting_started/basic_concepts.rst:84 msgid "" "Multiple views are possible in Krita via :menuselection:`Window --> New view " "--> image name`. You can switch between them via the :guilabel:`Window` " "menu, or :kbd:`Ctrl + Tab`, or keep them in the same area when **subwindow** " "mode is active in the :ref:`settings `, via :menuselection:" "`Window --> Tile`." msgstr "" "Múltiples visites són possibles en el Krita mitjançant :menuselection:" "`Finestra --> Vista nova --> nom_imatge`. Podreu canviar entre elles " "mitjançant el menú :guilabel:`Finestra`, la drecera :kbd:`Ctrl + Tab` o " "manteniu-les a la mateixa àrea quan estigui activat el mode **subfinestra** " "als :ref:`ajustaments `, mitjançant :menuselection:" "`Finestra --> Mosaic`." #: ../../user_manual/getting_started/basic_concepts.rst:87 msgid "Dockers" msgstr "Acobladors" # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:89 msgid "" "Dockers are little subwindows in :ref:`Krita's interface `. They " "contain useful tools, like the color selector, layer stack, tool options etc." msgstr "" "Els acobladors són petites subfinestres a la :ref:`interfície del Krita " "`. Contenen eines útils, com ara el selector de color, la pila " "de capes, les opcions de les eines, etc." #: ../../user_manual/getting_started/basic_concepts.rst:94 msgid "The image above shows some of the dockers in Krita" msgstr "La imatge de dalt mostra alguns dels acobladors al Krita." #: ../../user_manual/getting_started/basic_concepts.rst:96 msgid "All the views and the dockers are held inside **Windows**" msgstr "Totes les vistes i els acobladors es troben dins de les **finestres**" #: ../../user_manual/getting_started/basic_concepts.rst:99 msgid "Window" msgstr "Finestra" #: ../../user_manual/getting_started/basic_concepts.rst:101 msgid "" "If you've used a computer before, you know what windows are: They are big " "containers for your computer programs." msgstr "" "Si heu utilitzat un ordinador abans, ja sabeu què són les finestres: són " "contenidors grans per als vostres programes d'ordinador." # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:103 msgid "" "Krita allows you to have multiple windows via :menuselection:`Window --> New " "Window`. You can then drag this to another monitor for multi-monitor use." msgstr "" "El Krita permet tenir múltiples finestres mitjançant :menuselection:" "`Finestra -> Finestra nova`. A continuació, podreu arrossegar-la a un altre " "monitor per utilitzar-ho amb múltiples monitors." #: ../../user_manual/getting_started/basic_concepts.rst:105 msgid "The image below shows an example of multiple windows in Krita." msgstr "La imatge següent mostra un exemple de múltiples finestres al Krita." #: ../../user_manual/getting_started/basic_concepts.rst:111 msgid "Canvas in Krita" msgstr "Llenç en el Krita" #: ../../user_manual/getting_started/basic_concepts.rst:113 msgid "" "When you create a new document in Krita for the first time you will see a " "rectangular white area. This is called a canvas. You can see it in the image " "below. The area marked by a red rectangle is a canvas." msgstr "" "Quan creeu un document nou en el Krita per primera vegada, veureu una àrea " "blanca rectangular. Això s'anomena un llenç. Podeu veure-ho a la imatge de " "sota. L'àrea marcada per un rectangle vermell és un llenç." #: ../../user_manual/getting_started/basic_concepts.rst:118 msgid "" "When you save the painting as jpg, png etc or take a print out of the " "painting, only the content inside this area is taken into consideration. " "Anything beyond it is ignored. Krita does store information beyond this " "area, you just won't be able to see it. This data is stored in the " "**Layers**." msgstr "" "Quan deseu la pintura com a JPG, PNG, etc. o quan feu una impressió de la " "pintura, només es tindrà en compte el contingut d'aquesta àrea. Qualsevol " "cosa més enllà serà ignorada. El Krita emmagatzema informació més enllà " "d'aquesta àrea, simplement no la podeu veure. Aquestes dades s'emmagatzemen " "a les **capes**." #: ../../user_manual/getting_started/basic_concepts.rst:122 msgid "Layers and Compositing" msgstr "Capes i composició" #: ../../user_manual/getting_started/basic_concepts.rst:124 msgid "" "Like a landscape painter will first paint the sky and then the furthest away " "elements before slowly working his way to the foreground elements, computers " "will do the same with all the things you tell them to draw. So, if you tell " "them to draw a circle after a square on the same spot, the circle will " "always be drawn later. This is called the **Drawing Order**." msgstr "" "Així com un pintor de paisatges, primer pintaria el cel i després els " "elements més allunyats abans de treballar lentament amb els elements en " "primer pla, els ordinadors faran el mateix amb totes les coses que els hi " "digueu que dibuixin. Per tant, si indiqueu que es dibuixi un cercle després " "d'un quadrat en el mateix lloc, el cercle sempre es dibuixarà després. Això " "s'anomena **ordre del dibuix**." #: ../../user_manual/getting_started/basic_concepts.rst:126 msgid "" "The layer stack is a way for you to separate elements of a drawing and " "manipulate the drawing order by showing you which layers are drawn when, and " "allowing you to change the order they are drawn in, and all sorts of other " "effects. This is called **Compositing**." msgstr "" "La pila de capes és una manera per a que separeu els elements d'un dibuix i " "en manipuleu l'ordre per a mostrar quines capes es dibuixaran quan, el qual " "us permetrà canviar l'ordre en què estan dibuixades i tot tipus d'altres " "efectes. Això s'anomena **composició**." #: ../../user_manual/getting_started/basic_concepts.rst:128 msgid "" "This allows you to have line art above the colors, or trees before the " "mountains, and edit each without affecting the other." msgstr "" "Això us permet tenir art lineal sobre els colors o arbres al davant de les " "muntanyes, i editar-ne cadascun sense afectar a l'altre." #: ../../user_manual/getting_started/basic_concepts.rst:130 msgid "Krita has many layer-types, each doing a slightly different thing:" msgstr "" "El Krita disposa de molts tipus de capes, cadascuna fa quelcom una mica " "diferent:" # skip-rule: t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:132 msgid ":ref:`paint_layers`" msgstr ":ref:`paint_layers`" #: ../../user_manual/getting_started/basic_concepts.rst:133 msgid "" "Also known as raster layers, and the most common layer type, you will be " "painting on these." msgstr "" "També conegudes com a capes de rasteritzat i el tipus de capa més comú, " "pintareu sobre aquestes." # skip-rule: t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:134 msgid ":ref:`vector_layers`" msgstr ":ref:`vector_layers`" #: ../../user_manual/getting_started/basic_concepts.rst:135 msgid "" "This is a layer type on which you draw vector graphics. Vector graphics are " "typically more simple than raster graphics and with the benefit that you can " "deform them with less blurriness." msgstr "" "Aquestes són un tipus de capa on dibuixareu els gràfics vectorials. Els " "gràfics vectorials solen ser més senzills que els gràfics de rasteritzat i " "amb el benefici que els podreu deformar amb menys borrositat." # skip-rule: t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:136 msgid ":ref:`group_layers`" msgstr ":ref:`group_layers`" #: ../../user_manual/getting_started/basic_concepts.rst:137 msgid "" "These allow you to group several layers via drag and drop, so you can " "organize, move, apply masks and perform other actions on them together." msgstr "" "Aquestes us permeten agrupar diverses capes mitjançant l'acció arrossega i " "deixa anar, de manera que podreu organitzar, moure, aplicar màscares i " "realitzar altres accions." # skip-rule: t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:138 msgid ":ref:`clone_layers`" msgstr ":ref:`clone_layers`" #: ../../user_manual/getting_started/basic_concepts.rst:139 msgid "" "These are copies of the layer you selected when making them. They get " "updated automatically when changing the original." msgstr "" "Aquestes són còpies de la capa que heu seleccionat al crear-les. " "S'actualitzen automàticament quan es canvia l'original." # skip-rule: t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:140 msgid ":ref:`file_layers`" msgstr ":ref:`file_layers`" #: ../../user_manual/getting_started/basic_concepts.rst:141 msgid "" "These refer to an outside existing image, and update as soon as the outside " "image updates. Useful for logos and emblems that change a lot." msgstr "" "Aquestes es refereixen a una imatge existent a l'exterior i s'actualitzen " "tan aviat com s'actualitza la imatge externa. Útil per a logotips i emblemes " "que canvien molt." # skip-rule: t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:142 msgid ":ref:`fill_layers`" msgstr ":ref:`fill_layers`" #: ../../user_manual/getting_started/basic_concepts.rst:143 msgid "" "These layers are filled with something that Krita can make up on the fly, " "like colors or patterns." msgstr "" "Aquestes capes estan omplides d'alguna cosa que el Krita pot fer sobre la " "marxa, com ara colors o patrons." # skip-rule: t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:145 msgid ":ref:`filter_layers`" msgstr ":ref:`filter_layers`" #: ../../user_manual/getting_started/basic_concepts.rst:145 msgid "Adding a filter in the layer-stack. We discuss these later on." msgstr "Afegir un filtre a la pila de capes. Parlarem d'això més endavant." #: ../../user_manual/getting_started/basic_concepts.rst:147 msgid "You can manipulate the content of the layers with **Tools**." msgstr "Podeu manipular el contingut de les capes amb les **eines**." #: ../../user_manual/getting_started/basic_concepts.rst:150 msgid "Tools" msgstr "Eines" #: ../../user_manual/getting_started/basic_concepts.rst:152 msgid "" "Tools help you manipulate the image data. The most common one is of course, " "the freehand brush, which is the default when you open Krita. There are " "roughly five types of tools in Krita:" msgstr "" "Les eines us permeten manipular les dades de la imatge. La més comuna és, " "per descomptat, el pinzell a mà alçada, la qual és la predeterminada quan " "obriu el Krita. Aproximadament hi ha cinc tipus d'eines al Krita:" #: ../../user_manual/getting_started/basic_concepts.rst:154 msgid "Paint Tools" msgstr "Eines de pintura" #: ../../user_manual/getting_started/basic_concepts.rst:155 msgid "" "These are tools for painting on paint layers. They describe shapes, like " "rectangles, circles and straight lines, but also freehand paths. These " "shapes then get used by the Brush engines to make shapes and drawing effects." msgstr "" "Són eines per a pintar sobre capes de pintura. Descriuen formes, com ara " "rectangles, cercles i línies rectes, però també traçats a mà alçada. " -"Aquestes formes són utilitzades pels motors de pinzell per a crear formes i " -"efectes de dibuix." +"Aquestes formes són utilitzades pels motors de pinzells per a crear formes " +"i efectes de dibuix." #: ../../user_manual/getting_started/basic_concepts.rst:156 msgid "Vector Tools" msgstr "Eines vectorials" #: ../../user_manual/getting_started/basic_concepts.rst:157 msgid "" "This is the upper row of tools, which are used to edit vectors. " "Interestingly enough, all paint tools except the freehand brush allow you to " "draw shapes on the vector layers. These don't get a brush engine effect " "applied to them, though." msgstr "" "Aquesta és la fila superior d'eines, les quals s'utilitzen per editar els " "vectors. Curiosament, totes les eines de pintura, excepte el pinzell a mà " "alçada, permeten dibuixar formes a les capes vectorials. No obstant això, a " -"aquests no se'ls aplica un efecte motor del pinzell." +"aquests no se'ls aplica un efecte del motor de pinzells." #: ../../user_manual/getting_started/basic_concepts.rst:158 msgid "Selection Tools" msgstr "Eines de selecció" #: ../../user_manual/getting_started/basic_concepts.rst:159 msgid "" "Selections allow you to edit a very specific area of the layer you are " "working on without affecting the others. The selection tools allow you " "modify the current selection. This is not unlike using masking-fluids in " "traditional painting, but whereas using masking fluids and film is often " "messy and delicate, selections are far easier to use." msgstr "" "Les seleccions permeten editar una àrea molt específica de la capa en la " "qual esteu treballant sense afectar a les altres. Les eines de selecció " "permeten modificar la selecció actual. Això no és diferent de l'ús de fluids " "d'emmascarament en la pintura tradicional, però mentre que emprar fluids i " "pel·lícula per a l'emmascarament sovint és desordenat i delicat, les " "seleccions són molt més fàcils d'emprar." #: ../../user_manual/getting_started/basic_concepts.rst:160 msgid "Guide Tools" msgstr "Eines de guia" #: ../../user_manual/getting_started/basic_concepts.rst:161 msgid "These are tools like grids and assistants." msgstr "Aquestes són les eines com quadrícules i assistents." #: ../../user_manual/getting_started/basic_concepts.rst:163 msgid "Transform Tools" msgstr "Eines de transformació" #: ../../user_manual/getting_started/basic_concepts.rst:163 msgid "" "These are tools that allow you to transform your image. More on that later." msgstr "" "Aquestes són les eines que permeten transformar la imatge. Més sobre això " "més endavant." #: ../../user_manual/getting_started/basic_concepts.rst:165 msgid "" "All tools can be found in the toolbox, and information can be found in the " "tools section of the manual." msgstr "" "Totes les eines es troben al quadre d'eines i trobareu la informació a la " "secció d'eines del manual." #: ../../user_manual/getting_started/basic_concepts.rst:168 msgid "Brush Engines" -msgstr "Motors de pinzell" +msgstr "Motors de pinzells" #: ../../user_manual/getting_started/basic_concepts.rst:170 msgid "" "Brush engines, like mentioned before, take a path and tablet information and " "add effects to it, making a stroke." msgstr "" -"Els motors de pinzell, com s'ha mencionat anteriorment, prenen informació " +"Els motors de pinzells, com s'ha mencionat anteriorment, prenen informació " "d'un traç i de la tauleta i li afegeixen els efectes, fent-ho en un traç." #: ../../user_manual/getting_started/basic_concepts.rst:172 msgid "" "Engine is a term programmers use to describe a complex interacting set of " "code that is the core for a certain functionality, and is highly " "configurable. In short, like the engine of your car drives your car, and the " "type of engine and its configuration affects how you use your car, the brush " "engine drives the look and feel of the brush, and different brush engines " "have different results." msgstr "" "El motor és un terme que els programadors utilitzen per a descriure un " "conjunt complex de codi interactiu que és el nucli d'una determinada " "característica i és altament configurable. En resum, com el motor del cotxe " "que conduïu; el cotxe, el tipus de motor i la seva configuració afectarà a " -"la forma en què l'utilitzeu, el motor del pinzell impulsa l'aspecte i el " +"la forma en què l'utilitzeu, el motor de pinzell impulsa l'aspecte i el " "comportament del pinzell i diferents motors de pinzell tenen resultats " "diferents." # skip-rule: t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:174 msgid "" "Krita has :ref:`a LOT of different brush engines `, " "all with different effects." msgstr "" "El Krita disposa d':ref:`un munt de motors de pinzell diferents " "`, tots amb efectes diferents." #: ../../user_manual/getting_started/basic_concepts.rst:179 msgid ".. image:: images/en/Krita_example_differentbrushengines.png" msgstr ".. image:: images/en/Krita_example_differentbrushengines.png" #: ../../user_manual/getting_started/basic_concepts.rst:179 msgid "" "**Left:** pixel brush, **Center:** color smudge brush, **Right:** sketch " "brush" msgstr "" "**Esquerra:** pinzell de píxels, **Centre:** pinzell d'esborronat del color, " "**Dreta** pinzell d'esbós" #: ../../user_manual/getting_started/basic_concepts.rst:181 msgid "" "For example, the pixel-brush engine is simple and allows you to do most of " "your basic work, but if you do a lot of painting, the color smudge brush " "engine might be more useful. Even though it's slower to use than the Pixel " "Brush engine, its mixing of colors allows you to work faster." msgstr "" "Per exemple, el motor del pinzell de píxels és senzill i permet fer la major " "part del vostre treball bàsic, però si feu una gran quantitat de pintura, el " "motor del pinzell d'esborronat del color pot ser més útil. Encara que sigui " "més lent que utilitzar el motor del pinzell de píxels, la seva barreja de " "colors us permetrà treballar més ràpidament." #: ../../user_manual/getting_started/basic_concepts.rst:183 msgid "" "If you want something totally different from that, the sketch brush engine " "helps with making messy lines, and the shape brush engine allows you to make " "big flats quickly. There are a lot of cool effects inside Krita's brush " "engines, so try them all out, and be sure to check the chapters on each." msgstr "" "Si voleu alguna cosa totalment diferent d'això, el motor del pinzell d'esbós " "ajuda a fer línies desordenades i el motor de pinzell de formes permet fer " "plans grans ràpidament. Hi ha molts efectes interessants als motors de " -"pinzell del Krita, de manera que proveu-los tots i assegureu-vos de " +"pinzells del Krita, de manera que proveu-los tots i assegureu-vos de " "comprovar els capítols de cadascun." # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:185 msgid "" "You can configure these effects via the Brush Settings drop-down, which can " "be quickly accessed via :kbd:`F5`. These configurations can then be saved " "into presets, which you can quickly access with :kbd:`F6` or the Brush " "Presets docker." msgstr "" "Podeu configurar aquests efectes mitjançant el menú desplegable Ajustaments " "del pinzell, al qual es pot accedir ràpidament amb la drecera :kbd:`F5`. " "Aquestes configuracions es poden desar en valors predefinits, als quals " "accedireu ràpidament amb la drecera :kbd:`F6` o l'acoblador Valors " "predefinits del pinzell." #: ../../user_manual/getting_started/basic_concepts.rst:187 msgid "Brushes draw with colors, but how do computers understand colors?" msgstr "" "Els pinzells dibuixen amb colors, però com poden entendre'ls els ordinadors?" #: ../../user_manual/getting_started/basic_concepts.rst:190 msgid "Colors" msgstr "Colors" #: ../../user_manual/getting_started/basic_concepts.rst:192 msgid "" "Humans can see a few million colors, which are combinations of " "electromagnetic waves (light) bouncing off a surface, where the surface " "absorbs some of it." msgstr "" "Els humans poden veure alguns milions de colors, els quals són combinacions " "d'ones electromagnètiques (llum) que reboten sobre una superfície, on la " "superfície n'absorbeix una part." #: ../../user_manual/getting_started/basic_concepts.rst:197 msgid ".. image:: images/en/Krita_basics_primaries.png" msgstr ".. image:: images/en/Krita_basics_primaries.png" #: ../../user_manual/getting_started/basic_concepts.rst:197 msgid "" "Subtractive CMY colors on the left and additive RGB colors on the right. " "This difference means that printers benefit from color conversion before " "printing" msgstr "" "Els colors CMY subtractius a l'esquerra i els colors RGB additius a la " "dreta. Aquesta diferència significa que les impressores es beneficien de la " "conversió del color abans d'imprimir." #: ../../user_manual/getting_started/basic_concepts.rst:199 msgid "" "When painting traditionally, we use pigments which also absorb the right " "light-waves for the color we want it to have, but the more pigments you " "combine, the more light is absorbed, leading to a kind of murky black. This " "is why we call the mixing of paints **subtractive**, as it subtracts light " "the more pigments you put together. Because of that, in traditional pigment " "mixing, our most efficient primaries are three fairly light colors: Cyan " "blue and Magenta red and Yellow (CMY)." msgstr "" "Quan pintem de la manera tradicional, utilitzem pigments que també " "absorbeixen les ones de llum adequades per al color que volem que tingui, " "però com més pigments es combinin, més llum s'absorbirà, donant lloc a una " "mena de negre tou. Per aquesta raó, anomenem la barreja **substractiva** de " "pintures, ja que resta llum quan més pigments agrupeu. Per això, en la " "barreja tradicional de pigments, els primaris més eficients són tres colors " "força lleugers: blau cian, vermell magenta i groc (Cyan blue, Magenta red " "and Yellow -CMY-)." #: ../../user_manual/getting_started/basic_concepts.rst:201 msgid "" "A computer also uses three primaries and uses a specific amount of each " "primary in a color as the way it stores color. However, a computer is a " "screen that emits light. So it makes more light, which means it needs to do " "**additive** mixing, where adding more and more colored lights result in " "white. This is why the three most efficient primaries, as used by computers " "are Red, Green and Blue (RGB)." msgstr "" "Un ordinador també utilitza els tres primaris i utilitza una quantitat " "específica de cadascun en un color a mesura que emmagatzema el color. No " "obstant això, un ordinador és una pantalla que emet llum. De manera que fa " "més llum, el qual vol dir que haurà de fer una barreja **additiva**, on " "l'addició de més i més llums de color resultarà en blanc. Per aquest motiu, " "els tres primaris més eficients, tal com els utilitzen els ordinadors són " "vermell, verd i blau (Red, Green and Blue -RGB-)." #: ../../user_manual/getting_started/basic_concepts.rst:203 msgid "" "Per pixel, a computer then stores the value of each of these primaries, with " "the maximum depending on the bit-depth. These are called the **components** " "or **channels** depending on who you talk to." msgstr "" "Per píxel, un ordinador emmagatzemarà el valor de cadascun d'aquests " "primaris, amb el màxim depenent de la profunditat de bits. Aquests són els " "anomenats **components** o **canals** segons amb qui parleu." #: ../../user_manual/getting_started/basic_concepts.rst:208 msgid ".. image:: images/en/Krita_basic_channel_rose.png" msgstr ".. image:: images/en/Krita_basic_channel_rose.png" #: ../../user_manual/getting_started/basic_concepts.rst:208 msgid "" "This is the red-channel of an image of a red rose. As you can see, the " "petals are white here, indicating that those areas contain full red. The " "leaves are much darker, indicating a lack of red, which is to be expected, " "as they are green." msgstr "" "Aquest és el canal vermell d'una imatge d'una rosa vermella. Com podeu " "veure, els pètals són blancs, indicant que aquestes àrees contenen vermell " "complet. Les fulles són molt més fosques, indicant una falta de vermell, el " "qual és d'esperar, ja que són verdes." #: ../../user_manual/getting_started/basic_concepts.rst:210 msgid "" "Though by default computers use RGB, they can also convert to CMYK (the " "subtractive model), or a perceptual model like LAB. In all cases this is " "just a different way of indicating how the colors relate to each other, and " "each time it usually has 3 components. The exception here is grayscale, " "because the computer only needs to remember how white a color is. This is " "why grayscale is more efficient memory-wise." msgstr "" "Tot i que, de manera predeterminada, els ordinadors empren RGB, també poden " "convertir-se a CMYK (el model subtractiu) o un model perceptiu com LAB. En " "tots els casos, això només és una manera diferent d'indicar com es " "relacionen els colors entre si, i cada vegada se solen tenir 3 components. " "L'excepció aquí és l'escala de grisos, perquè l'ordinador només necessita " "recordar com és un color blanc. Per això, amb l'escala de grisos és més " "eficient en memòria." #: ../../user_manual/getting_started/basic_concepts.rst:212 msgid "" "In fact, if you look at each channel separately, they also look like " "grayscale images, but instead white just means how much Red, Green or Blue " "there is." msgstr "" "De fet, si observeu cada canal per separat, també les veureu com a imatges " "en escala de grisos, però en blanc voldrà dir només la quantitat de vermell, " "verd o blau que hi ha." # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:214 msgid "" "Krita has a very complex color management system, which you can read more " "about :ref:`here `." msgstr "" "El Krita té un sistema per a la gestió del color molt complex, del qual " "podeu llegir més :ref:`aquí `." #: ../../user_manual/getting_started/basic_concepts.rst:217 msgid "Transparency" msgstr "Transparència" #: ../../user_manual/getting_started/basic_concepts.rst:219 msgid "" "Just like Red, Green and Blue, the computer can also store how transparent a " "pixel is. This is important for **compositing** as mentioned before. After " "all, there's no point in having multiple layers if you can't have " "transparency." msgstr "" "Igual que el vermell, el verd i el blau, l'ordinador també pot emmagatzemar " "la transparència d'un píxel. Això és important per a la **composició** tal " "com s'ha esmentat anteriorment. Després de tot, no té sentit tenir múltiples " "capes si no es pot tenir transparència." #: ../../user_manual/getting_started/basic_concepts.rst:221 msgid "" "Transparency is stored in the same way as colors, meaning that it's also a " "channel. We usually call this channel the **alpha channel** or **alpha** for " "short. The reason behind this is that the letter 'α' is used to represent it " "in programming." msgstr "" "La transparència s'emmagatzema de la mateixa manera que els colors, el qual " "significa que també és un canal. Normalment l'anomenem **canal alfa** o " "**alfa** per escurçar. La raó d'això és que la lletra «α» s'utilitza per a " "representar-la en la programació." # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:223 msgid "" "Some older programs don't always have transparency by default. Krita is the " "opposite: it doesn't understand images that don't track transparency, and " "will always add a transparency channel to images. When a given pixel is " "completely transparent on all layers, Krita will instead show a checkerboard " "pattern, like the rose image to the left." msgstr "" "Alguns programes antics no sempre tenen transparència de manera " "predeterminada. El Krita fa el contrari: no entén les imatges que no " "segueixen la transparència, i sempre afegirà un canal de transparència a les " "imatges. Quan un píxel donat és completament transparent a totes les capes, " "el Krita mostrarà un patró de tauler d'escacs, com la imatge de la rosa que " "hi ha a l'esquerra." #: ../../user_manual/getting_started/basic_concepts.rst:226 msgid "Blending modes" msgstr "Modes de barreja" #: ../../user_manual/getting_started/basic_concepts.rst:228 msgid "" "Because colors are stored as numbers you can do maths with them. We call " "this **Blending Modes** or **Compositing Modes**." msgstr "" "Com que els colors s'emmagatzemen com a números, podreu fer matemàtiques amb " "ells. Això ho anomenem **Modes de barreja** o **Modes de composició**." #: ../../user_manual/getting_started/basic_concepts.rst:230 msgid "" "Blending modes can be done per layer or per brush stroke, and thus are also " "part of the compositing of layers." msgstr "" "Els modes de barreja es poden fer per capa o pel traç del pinzell i, per " "tant, també formen part de la composició de les capes." #: ../../user_manual/getting_started/basic_concepts.rst:233 msgid "Multiply" msgstr "Multiplicar" # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:233 msgid "" "A commonly used blending mode is for example :menuselection:`Multiply` which " "multiplies the components, leading to darker colors. This allows you to " "simulate the subtractive mixing, and thus makes painting shadows much easier." msgstr "" "Un mode de barreja que s'utilitza habitualment és, per exemple :" "menuselection:`Multiplica`, el qual multiplicarà els components, donant lloc " "a colors més foscos. Això permet simular la barreja substractiva i, per " "tant, facilitarà molt les ombres en la pintura." #: ../../user_manual/getting_started/basic_concepts.rst:235 msgid "Addition" msgstr "Sumar" # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:236 msgid "" "Another common one is :menuselection:`Addition`, which adds one layer's " "components to the other, making it perfect for special glow effects." msgstr "" "Un altre ús habitual és :menuselection:`Suma`, el qual afegirà els " "components d'una capa a l'altra, el qual es perfecte per a efectes especials " "de lluïssor." #: ../../user_manual/getting_started/basic_concepts.rst:237 msgid "Erasing" msgstr "Esborrar" # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:238 msgid "" ":menuselection:`Erasing` is a blending mode in Krita. There is no eraser " "tool, but you can toggle on the brush quickly with :kbd:`E` to become an " "eraser. You can also use it on layers. Unlike the other blending modes, this " "one only affects the alpha channel, making things more transparent." msgstr "" ":menuselection:`Esborra` és un mode de barreja al Krita. No hi ha cap eina " "d'esborrador, però podeu alternar ràpidament el pinzell amb la drecera :kbd:" "`E` per a convertir-la en un goma d'esborrar. També podeu utilitzar-la en " "les capes. A diferència dels altres modes de barreja, aquest només afectarà " "el canal alfa, fent que les coses siguin més transparents." #: ../../user_manual/getting_started/basic_concepts.rst:240 msgid "Normal" msgstr "Normal" # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:240 msgid "" "The :menuselection:`Normal` blend mode just averages between colors " "depending on how transparent the topmost color is." msgstr "" "El mode de barreja :menuselection:`Normal` només fa la mitjana entre els " "colors depenent de quina sigui la transparència al color de sobre." # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:242 msgid "" "Krita has 76 blending modes, each doing slightly different things. Head over " "to the :ref:`blending_modes` to learn more." msgstr "" "El Krita disposa de 76 modes de barreja, cadascun fa les coses una mica " "diferents. Aneu cap als :ref:`blending_modes` per obtenir més informació." #: ../../user_manual/getting_started/basic_concepts.rst:244 msgid "" "Because we can see channels as grayscale images, we can convert grayscale " "images into channels. Like for example, we can use a grayscale image for the " "transparency. We call these **Masks**." msgstr "" "Com que podem veure els canals com a imatges en escala de grisos, podrem " "convertir les imatges en escala de grisos a canals. Com, per exemple, podrem " "utilitzar una imatge en escala de grisos per a la transparència. Ho anomenem " "**màscares**." #: ../../user_manual/getting_started/basic_concepts.rst:247 msgid "Masks" msgstr "Màscares" #: ../../user_manual/getting_started/basic_concepts.rst:249 msgid "" "Masks are a type of sub-effect applied to a layer, usually driven by a " "grayscale image." msgstr "" "Les màscares són un tipus de subefecte aplicat a una capa, generalment " "provinent d'una imatge en escala de grisos." # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:251 msgid "" "The primary types of mask are :ref:`transparency_masks`, which allow you to " "use a grayscale image to determine the transparency, where black makes " "everything transparent and white makes the pixel fully opaque." msgstr "" "Els tipus principals de màscara són :ref:`transparency_masks`, els quals " "permeten utilitzar una imatge en escala de grisos per a determinar la " "transparència, on el negre farà que tot sigui transparent i el blanc farà " "que el píxel sigui completament opac." #: ../../user_manual/getting_started/basic_concepts.rst:253 msgid "" "You can paint on masks with any of the brushes, or convert a normal paint-" "layer to a mask. The big benefit of masks is that you can make things " "transparent without removing the underlying pixels. Furthermore, you can use " "masks to reveal or hide a whole group layer at once!" msgstr "" "Podeu pintar sobre les màscares amb qualsevol dels pinzells, o convertir una " "capa de pintura normal en una màscara. El gran benefici de les màscares és " "que podreu fer les coses transparents sense eliminar els píxels subjacents. " "A més, podreu fer servir les màscares per a revelar o ocultar tot un grup de " "capes alhora." #: ../../user_manual/getting_started/basic_concepts.rst:255 msgid "For example, we have a white ghost lady here:" msgstr "Per exemple, aquí tenim una dama fantasma de blanc:" #: ../../user_manual/getting_started/basic_concepts.rst:260 msgid "" "But you can't really tell whether she's a ghost lady or just really really " "white. If only we could give the idea that she floats... We right-click the " "layer and add a transparency mask. Then, we select that mask and draw with a " "black and white linear gradient so that the black is below." msgstr "" "Però en realitat no es pot saber si és una dama fantasma o simplement que en " "realitat és blanca. Si només poguéssim donar-nos la idea que flota... Fem " "clic dret a la capa i afegim una màscara de transparència. Després, " "seleccionem aquesta màscara i dibuixem amb un degradat lineal en blanc i " "negre, de manera que el negre estarà a sota." #: ../../user_manual/getting_started/basic_concepts.rst:266 msgid "" "Wherever the black is, there the lady now becomes transparent, turning her " "into a real ghost!" msgstr "" "On se vulga que es trobi el negre, allà la dama es tornarà transparent. " "Convertint-la en un veritable fantasma!" #: ../../user_manual/getting_started/basic_concepts.rst:268 msgid "" "The name mask comes from traditional masking fluid and film. You may recall " "the earlier comparison of selections to traditional masking fluid. " "Selections too are stored internally as grayscale images, and you can save " "them as a local selection which is kind of like a mask, or convert them to a " "transparency mask." msgstr "" "El nom de màscara prové del fluid i pel·lícula de l'emmascarament " "tradicional. Pot recordar la comparació anterior de seleccions amb el fluid " "per a l'emmascarament tradicional. Les seleccions també s'emmagatzemen " "internament com a imatges en escala de grisos, i podeu desar-les com una " "selecció local, el qual serà com una màscara, o convertir-ho en una màscara " "de transparència." #: ../../user_manual/getting_started/basic_concepts.rst:271 msgid "Filters" msgstr "Filtres" #: ../../user_manual/getting_started/basic_concepts.rst:273 msgid "" "We mentioned earlier that you can do maths with colors. But you can also do " "maths with pixels, or groups of pixels or whole layers. In fact, you can " "make Krita do all sorts of little operations on layers. We call these " "operations **Filters**." msgstr "" "Anteriorment hem esmentat que podeu fer matemàtiques amb els colors. Però " "també podeu fer matemàtiques amb els píxels, grups de píxels o capes " "senceres. De fet, podeu fer que el Krita faci tot tipus de petites " "operacions sobre les capes. A aquestes operacions les anomenem **filtres**." #: ../../user_manual/getting_started/basic_concepts.rst:275 msgid "Examples of such operations are:" msgstr "Exemples d'aquestes operacions són:" #: ../../user_manual/getting_started/basic_concepts.rst:277 msgid "Desaturate" msgstr "Dessatura" #: ../../user_manual/getting_started/basic_concepts.rst:278 msgid "This makes all the pixels turn gray." msgstr "Això fa que tots els píxels es tornin grisos." #: ../../user_manual/getting_started/basic_concepts.rst:279 msgid "Blur" msgstr "Difuminat" #: ../../user_manual/getting_started/basic_concepts.rst:280 msgid "" "This averages the pixels with their neighbors, which removes sharp contrasts " "and makes the whole image look blurry." msgstr "" "Això fa la mitjana dels píxels amb els seus veïns, el qual eliminarà els " "contrastos bruscos i farà que la imatge sencera quedi borrosa." #: ../../user_manual/getting_started/basic_concepts.rst:281 msgid "Sharpen" msgstr "Aguditza" #: ../../user_manual/getting_started/basic_concepts.rst:282 msgid "" "This increases the contrast between pixels that had a pretty high contrast " "to begin with." msgstr "" "Això farà augmentar el contrast entre els píxels que tenien un contrast " "força alt en començar." #: ../../user_manual/getting_started/basic_concepts.rst:284 msgid "Color to Alpha" msgstr "Color a alfa" #: ../../user_manual/getting_started/basic_concepts.rst:284 msgid "A popular filter which makes all of the chosen color transparent." msgstr "Un filtre popular que fa que tot el color escollit sigui transparent." #: ../../user_manual/getting_started/basic_concepts.rst:289 msgid ".. image:: images/en/Krita_basic_filter_brush.png" msgstr ".. image:: images/en/Krita_basic_filter_brush.png" #: ../../user_manual/getting_started/basic_concepts.rst:289 msgid "Different filter brushes being used on different parts of the image." msgstr "" "Diferents pinzells de filtratge que s'utilitzen en diferents parts de la " "imatge." # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:291 msgid "" "Krita has many more filters available: read about them :ref:`here `." msgstr "" "El Krita disposa de molts més filtres disponibles: llegiu sobre seu :ref:" "`aquí `." # skip-rule: t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:294 msgid ":ref:`filter_brush_engine`" msgstr ":ref:`filter_brush_engine`" # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:296 msgid "" "Because many of these operations are per pixel, Krita allows you to use the " "filter as part of the :ref:`filter_brush_engine`." msgstr "" "Com que moltes d'aquestes operacions són per píxel, el Krita permet " "utilitzar el filtre com a part del :ref:`filter_brush_engine`." #: ../../user_manual/getting_started/basic_concepts.rst:298 msgid "" "In most image manipulation software, these are separate tools, but Krita has " "it as a brush engine, allowing much more customization than usual." msgstr "" "En la majoria del programari per a la manipulació d'imatges, aquestes són " -"eines separades, però el Krita les té com a motor de pinzell, permetent una " +"eines separades, però el Krita les té com a motor de pinzells, permetent una " "major personalització del que és habitual." #: ../../user_manual/getting_started/basic_concepts.rst:300 msgid "" "This means you can make a brush that desaturates pixels, or a brush that " "changes the hue of the pixels underneath." msgstr "" "Això vol dir que podeu crear un pinzell que dessatura els píxels o un " "pinzell que canvia el to dels píxels per sota." #: ../../user_manual/getting_started/basic_concepts.rst:303 msgid "Filter Layers, Filter Masks and Layer Styles" msgstr "Capes de filtratge, màscares de filtratge i estils de capa" # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:305 msgid "" "Krita also allows you to let the Filters be part of the layer stack, via :" "ref:`filter_layers` and :ref:`filter_masks`. Filter Layers affect all the " "layers underneath it in the same hierarchy. Transparency and transparency " "masks on Filter Layers affect where the layer is applied." msgstr "" "El Krita també permet deixar que els filtres formin part de la pila de " "capes, mitjançant les :ref:`filter_layers` i :ref:`filter_masks`. Les capes " "del filtratge afectaran a totes les capes situades sota seu en la mateixa " "jerarquia. La transparència i les màscares de transparència a sobre de les " "capes de filtratge afectaran on s'apliqui la capa." #: ../../user_manual/getting_started/basic_concepts.rst:307 msgid "" "Masks, on the other hand, can affect one single layer and are driven by a " "grayscale image. They will also affect all layers in a group, much like a " "transparency mask." msgstr "" "Les màscares, d'altra banda, poden afectar una sola capa i provenen d'una " "imatge en escala de grisos. També afectaran a totes les capes d'un grup, " "igual que una màscara de transparència." # skip-rule: t-apo_ini #: ../../user_manual/getting_started/basic_concepts.rst:309 msgid "" "We can use these filters to make our ghost lady look even more ethereal, by " "selecting the ghost lady's layer, and then creating a clone layer. We then " "right click and add a filter mask and use gaussian blur set to 10 or so " "pixels. The clone layer is then put behind the original layer, and set to " "the blending mode '**Color Dodge**', giving her a definite spooky glow. You " "can keep on painting on the original layer and everything will get updated " "automatically!" msgstr "" "Podem utilitzar aquests filtres per a fer que la nostra dama fantasma es " "vegi encara més etèria, seleccionant la capa de la dama fantasma i després " "creant una capa de clonatge. Després fem clic dret, afegim una màscara de " "filtratge i fem servir el conjunt de difuminat gaussià establert a 10 píxels " "o així. La capa de clonatge es col·locarà al darrere de la capa original i " "s'establirà en el mode barreja «**Esvaïment del color**», el qual li donarà " "una lluïssor esgarrifosament definida. Podeu continuar pintant a la capa " "original i tot s'actualitzarà automàticament!" # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:314 msgid "" "Layer Effects or Layer Styles are :program:`Photoshop's` unique brand of " "Filter Masks that are a little faster than regular masks, but not as " "versatile. They are available by right clicking a layer and selecting 'layer " "style'." msgstr "" "Els efectes de capa o els estils de capa són marca exclusiva de :program:" "`Photoshop`. Les màscares de filtratge són una mica més ràpides que les " "màscares estàndard, però no tan versàtils. Estan disponibles fent clic dret " "sobre una capa i seleccionant «estil de capa»." #: ../../user_manual/getting_started/basic_concepts.rst:317 msgid "Transformations" msgstr "Transformacions" #: ../../user_manual/getting_started/basic_concepts.rst:319 msgid "" "**Transformations** are kind of like filters, in that these are operations " "done on the pixels of an image. We have a regular image and layer wide " "transformations in the image and layer top menus, so that you may resize, " "flip and rotate the whole image." msgstr "" "Les **transformacions** són tipus de filtres, en aquests es tracta " "d'operacions realitzades sobre els píxels d'una imatge. Tenim una imatge " "estàndard i una capa àmplia de transformacions en els menús de la imatge i " "la capa de a sobre, de manera que podreu reamidar, invertir i girar tota la " "imatge." # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:321 msgid "" "We also have the :ref:`crop_tool`, which only affects the canvas size, and " "the :ref:`move_tool` which only moves a given layer. However, if you want " "more control, Krita offers a :ref:`transform_tool`." msgstr "" "També tenim l':ref:`crop_tool`, la qual només afectarà a la mida del llenç, " "i l':ref:`move_tool`, la qual només mourà una capa determinada. Tanmateix, " "si voleu més control, el Krita ofereix una :ref:`transform_tool`." #: ../../user_manual/getting_started/basic_concepts.rst:327 msgid "" "With this tool you can rotate and resize on the canvas, or put it in " "perspective. Or you can use advanced transform tools, like the warp, cage " "and liquify, which allow you to transform by drawing custom points or even " "by pretending it's a transforming brush." msgstr "" "Amb aquesta eina podeu girar i reamidar la mida del llenç o posar-lo en " "perspectiva. O podeu utilitzar les eines de transformació avançada, com ara " "la deformació, gàbia i liqüescent, les quals permeten transformar dibuixant " -"punts personalitzats o fins i tot fingint que es tracta d'un pinzell " -"transformador." +"punts personalitzats o fins i tot fingint que es tracta d'un pinzell de " +"transformació." # skip-rule: t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:330 msgid ":ref:`deform_brush_engine`" msgstr ":ref:`deform_brush_engine`" #: ../../user_manual/getting_started/basic_concepts.rst:332 msgid "" "Like the filter brush engine, Krita also has a Deform Brush Engine, which " "allows you to transform with a brush. The deform is like a much faster " "version of the Liquify transform tool mode, but in exchange, its results are " "of much lower quality." msgstr "" "Igual que el motor del pinzell de filtratge, el Krita també disposa d'un " -"motor de pinzell de deformació, el qual permet transformar amb un pinzell. " +"motor del pinzell de deformació, el qual permet transformar amb un pinzell. " "La deformació és com una versió molt més ràpida del mode d'eina de " "transformació liqüescent, però en canvi, els seus resultats són de molta " "menor qualitat." #: ../../user_manual/getting_started/basic_concepts.rst:337 msgid ".. image:: images/en/Krita_transforms_deformvsliquefy.png" msgstr ".. image:: images/en/Krita_transforms_deformvsliquefy.png" #: ../../user_manual/getting_started/basic_concepts.rst:337 msgid "" "Apple transformed into a pear with liquify on the left and deform brush on " "the right." msgstr "" "Una poma transformada en una pera amb liqüescent a l'esquerra i el pinzell " "de deformació a la dreta." #: ../../user_manual/getting_started/basic_concepts.rst:339 msgid "" "Furthermore, you can't apply the deform brush as a non-destructive mask." msgstr "" "A més, no podreu aplicar el pinzell de deformació com a una màscara no " "destructiva." # skip-rule: t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:342 msgid ":ref:`transformation_masks`" msgstr ":ref:`transformation_masks`" #: ../../user_manual/getting_started/basic_concepts.rst:344 msgid "" "Like filters, transforms can be applied as a non-destructive operation that " "is part of the layer stack. Unlike filter and transparency masks however, " "transform masks can't be driven by a grayscale image, for technical reasons. " "You can use transform masks to deform clone and file layers as well." msgstr "" "Igual que els filtres, les transformacions es poden aplicar com a una " "operació no destructiva que formi part de la pila de capes. A diferència de " "les màscares de filtratge i de transparència, per raons tècniques, les " "màscares de transformació no poden provenir d'una imatge en escala de " "grisos. També podeu utilitzar màscares de transformació per a deformar capes " "de clonatge i de fitxer." # skip-rule: t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:348 msgid ":ref:`animation`" msgstr ":ref:`animation`" #: ../../user_manual/getting_started/basic_concepts.rst:353 msgid "" "In 3.0, Krita got raster animation support. You can use the timeline, " "animation and onionskin dockers, plus Krita's amazing variety of brushes to " "do raster based animations, export those, and then turn them into movies or " "gifs." msgstr "" "En el 3.0, el Krita va aconseguir una implementació de l'animació " "rasteritzada. Podeu utilitzar els acobladors de la línia de temps, animació " "i pell de ceba, a més de l'increïble varietat de pinzells del Krita per a " "crear animacions basades en el rasteritzat; exportar-les i després convertir-" "les en pel·lícules o GIF." #: ../../user_manual/getting_started/basic_concepts.rst:356 msgid "Assistants, Grids and Guides" msgstr "Assistents, quadrícules i guies" #: ../../user_manual/getting_started/basic_concepts.rst:358 msgid "" "With all this technical stuff, you might forget that Krita is a painting " "program. Like how an illustrator in real life can have all sorts of " "equipment to make drawing easier, Krita also offers a variety of tools:" msgstr "" "Amb tot aquest material tècnic, podríeu oblidar que el Krita és un programa " "de pintura. Igual que un il·lustrador a la vida real pot tenir tot tipus " "d'equipament per a facilitar el dibuix, el Krita també ofereix una varietat " "d'eines:" #: ../../user_manual/getting_started/basic_concepts.rst:363 msgid ".. image:: images/en/Krita_basic_assistants.png" msgstr ".. image:: images/en/Krita_basic_assistants.png" #: ../../user_manual/getting_started/basic_concepts.rst:363 msgid "Krita's vanishing point assistants in action" msgstr "Assistents del punt de fuga del Krita en acció." # skip-rule: t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:365 msgid ":ref:`grids_and_guides_docker`" msgstr ":ref:`grids_and_guides_docker`" #: ../../user_manual/getting_started/basic_concepts.rst:366 msgid "" "Very straightforward guiding tool which shows grids or guiding lines that " "can be configured." msgstr "" "Eina de guia molt senzilla que mostra les quadrícules o línies guia que es " "poden configurar." # skip-rule: t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:367 msgid ":ref:`snapping`" msgstr ":ref:`snapping`" #: ../../user_manual/getting_started/basic_concepts.rst:368 msgid "" "You can snap to all sorts of things. Grids, guides, extensions, orthogonals, " "image centers and bounding boxes." msgstr "" "Podeu ajustar-vos a tot tipus de coses. Quadrícules, guies, extensions, " "ortogonals, centres d'imatge i contenidors." # skip-rule: t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:370 msgid ":ref:`painting_with_assistants`" msgstr ":ref:`painting_with_assistants`" #: ../../user_manual/getting_started/basic_concepts.rst:370 msgid "" "Because you can hardly put a ruler against your tablet to help you draw, the " "assistants are there to help you draw concentric circles, perspectives, " "parallel lines and other easily forgotten but tricky to draw details. Krita " "allows you to snap to these via the tool options as well." msgstr "" "Com que difícilment podreu posar una regla a la vostra tauleta per ajudar-" "vos a dibuixar, els assistents us ajudaran a dibuixar cercles concèntrics, " "perspectives, línies paral·leles i altres fàcilment oblidats, però difícils " "de dibuixar. El Krita també permet ajustar-les mitjançant les opcions de " "l'eina." #: ../../user_manual/getting_started/basic_concepts.rst:372 msgid "" "These guides are saved into Krita's native format, which means you can pick " "up your work easily afterwards." msgstr "" "Aquestes guies es desen en el format natiu del Krita, el qual vol dir que " "després podreu reprendre el vostre treball amb facilitat." #: ../../user_manual/getting_started/basic_concepts.rst:375 msgid "Customization" msgstr "Personalitzar" #: ../../user_manual/getting_started/basic_concepts.rst:377 msgid "This leads to the final concept: customization." msgstr "Això ens porta al concepte final: la personalització." # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:379 msgid "" "In addition to rearranging the dockers according to your preferences, Krita " "provides and saves your configurations as :ref:`resource_workspaces`. This " "is the button at the top right." msgstr "" "A més de tornar a ordenar els acobladors segons les vostres preferències, el " "Krita proporciona i desa les configuracions com a :ref:" "`resource_workspaces`. Aquest és el botó situat a la part superior dreta." # skip-rule: t-sp_2p,t-2p_sp,t-acc_obe #: ../../user_manual/getting_started/basic_concepts.rst:381 msgid "" "You can also configure the toolbar via :menuselection:`Settings --> " "Configure Toolbars`, as well as the shortcuts under both :menuselection:" "`Settings --> Configure Krita --> Configure Shortcuts` and :menuselection:" "`Settings --> Configure Krita --> Canvas Input Settings`." msgstr "" "També podeu configurar la barra d'eines mitjançant :menuselection:" "`Arranjament --> Configura les barres d'eines`, així com les dreceres sota :" "menuselection:`Arranjament --> Configura el Krita --> Configura les " "dreceres` i :menuselection:`Arranjament --> Configura el Krita --> " "Arranjament de l'entrada del llenç`." diff --git a/locale/ca/LC_MESSAGES/user_manual/introduction_from_other_software/introduction_from_photoshop.po b/locale/ca/LC_MESSAGES/user_manual/introduction_from_other_software/introduction_from_photoshop.po index c5feb53a5..ce910a95b 100644 --- a/locale/ca/LC_MESSAGES/user_manual/introduction_from_other_software/introduction_from_photoshop.po +++ b/locale/ca/LC_MESSAGES/user_manual/introduction_from_other_software/introduction_from_photoshop.po @@ -1,1187 +1,1187 @@ # Translation of docs_krita_org_user_manual___introduction_from_other_software___introduction_from_photoshop.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: " -"docs_krita_org_user_manual___introduction_from_other_software___introduction_from_photoshop\n" +"Project-Id-Version: docs_krita_org_user_manual___introduction_from_other_softw" +"are___introduction_from_photoshop\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-03-06 03:37+0100\n" -"PO-Revision-Date: 2019-03-12 17:13+0100\n" +"PO-Revision-Date: 2019-03-14 23:15+0100\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" # skip-rule: t-sp_2p #: ../../:2 msgid "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: mouseleft" msgstr "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: mouseleft" # skip-rule: t-sp_2p #: ../../:4 msgid "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: mouseright" msgstr "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: mouseright" # skip-rule: t-sp_2p #: ../../:6 msgid "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: mousemiddle" msgstr "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: mousemiddle" # skip-rule: t-sp_2p #: ../../:8 msgid "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" msgstr "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:None msgid ".. image:: images/en/Settings-curves.jpg" msgstr ".. image:: images/en/Settings-curves.jpg" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:None msgid ".. image:: images/en/Krita-popuppalette.png" msgstr ".. image:: images/en/Krita-popuppalette.png" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:None msgid ".. image:: images/en/Krita-incremental-saves.png" msgstr ".. image:: images/en/Krita-incremental-saves.png" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:None msgid ".. image:: images/en/Krita-color-to-alpha.png" msgstr ".. image:: images/en/Krita-color-to-alpha.png" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:None msgid ".. image:: images/en/Krita-multibrush.png" msgstr ".. image:: images/en/Krita-multibrush.png" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:None msgid ".. image:: images/en/Krita_Color_Selector_Types.png" msgstr ".. image:: images/en/Krita_Color_Selector_Types.png" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:1 msgid "This is a introduction to Krita for users coming from Photoshop." msgstr "" "Aquesta és una introducció al Krita per als usuaris que vénen del Photoshop." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:20 msgid "Introduction to Krita coming from Photoshop" msgstr "Introducció al Krita si es ve del Photoshop" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:23 msgid "Introduction" msgstr "Introducció" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:25 msgid "" "This document gives an introduction to Krita for users who have been using " "Photoshop. The intention is to make you productive in Krita as fast as " "possible and ease the conversion of old habits into new ones. This " "introduction is written with Krita version 2.9 and Photoshop CS2 and CS3 in " "mind. But even though things may change in the future, the basics will most " "likely remain the same. The first thing to remember is that Krita is a 2D " "paint application while Photoshop (PS) is an image manipulation program. " "This means that PS has more features than Krita in general, but Krita has " "the tools that are relevant to digital painting. When you get used to Krita, " "you will find that Krita has some features that are not part of PS." msgstr "" "Aquest document proporciona una introducció al Krita per als usuaris que han " "estat emprant el Photoshop. La intenció és fer-vos productiu en el Krita el " "més ràpid possible i facilitar la conversió dels vells hàbits en altres de " "nous. Aquesta introducció està escrita amb el Krita versió 2.9 i el " "Photoshop CS2 i CS3 en ment. Però encara que les coses puguin canviar en el " "futur, el més probable és que segueixin sent les mateixes. El primer que cal " "recordar és que el Krita és una aplicació de pintura en 2D, mentre que el " "Photoshop (PS) és un programa per a la manipulació d'imatges. Això vol dir " "que en general el PS té més característiques que el Krita en general, però " "el Krita disposa d'eines que són rellevants per a la pintura digital. Quan " "us acostumeu al Krita, veureu que el Krita té algunes característiques que " "no formen part del PS." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:30 msgid "Krita Basics" msgstr "Conceptes bàsics del Krita" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:32 msgid "" "This chapter covers how you use Krita in the basic operations compared to PS." msgstr "" "Aquest capítol tracta sobre com utilitzar el Krita en les operacions " "bàsiques en comparació amb el PS." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:35 msgid "View and Display" msgstr "Veure i mostrar" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:38 msgid "Navigation" msgstr "Navegació" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:40 msgid "In Krita you can navigate your document using all these methods:" msgstr "" "Al Krita podeu navegar pel vostre document emprant tots aquests mètodes:" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:42 msgid "" "'*Mouse wheel*': |mousescroll| down and up for zoom, and press |mousemiddle| " "down to pan your document." msgstr "" "'*Roda del ratolí*': |mousescroll| avall i amunt per fer zoom i premeu el |" "mousemiddle| per a desplaçar el vostre document." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:43 msgid "'*Keyboard*': with :kbd:`+` and :kbd:`-` on your numpad keyboard" msgstr "'*Teclat*': amb :kbd:`+` i :kbd:`-` en el vostre teclat numèric." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:44 msgid "" "As in Photoshop, Painter, Manga Studio: :kbd:`Ctrl + Space` to zoom, and :" "kbd:`Space` to pan." msgstr "" "Com al Photoshop, Painter, Manga Studio: :kbd:`Ctrl + Espai` per a fer zoom, " "i :kbd:`Espai` per a desplaçar." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:48 msgid "" "If you add :kbd:`Alt` and so do a :kbd:`Ctrl + Alt + Space` you’ll have a " "discrete zoom." msgstr "" "Si afegiu :kbd:`Alt` i feu un :kbd:`Ctrl + Alt + Espai` obtindreu un zoom " "discret." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:51 msgid "Rotation" msgstr "Rotació" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:53 msgid "" "Rotate the canvas with :kbd:`Shift + Space`, or :kbd:`Ctrl + [` and :kbd:" "`Ctrl + ]` or with 4 or 6. Reset the rotation with 5." msgstr "" "Gireu el llenç amb :kbd:`Majús. + Espai` o :kbd:`Ctrl + [ i :kbd:`Ctrl +]`, " "o amb 4 o 6. Reinicieu la rotació amb 5." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:56 msgid "Mirror" msgstr "Mirall" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:58 msgid "" "Press :kbd:`M` to see your drawing or painting mirrored in the viewport." msgstr "" "Premeu :kbd:`M` per a veure el dibuix o la pintura reflectits a la finestra." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:61 msgid "Move and Transform" msgstr "Moure i transformar" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:63 msgid "" "Moving and Transformation of contents is done using tools in Krita. You can " "then find them in the toolbar. If you are familiar with the way to move " "layers in PS by holding down :kbd:`Ctrl`, you can do the same in Krita by " "pressing the :kbd:`T` key for the move tool (think ‘T’ranslate) or :kbd:" "`Ctrl + T` for transform tool." msgstr "" "El moviment i la transformació del contingut es realitza utilitzant les " "eines del Krita. Les trobareu a la barra d'eines. Si esteu familiaritzat amb " "la manera de moure les capes al PS, mantenint premuda la tecla :kbd:`Ctrl`, " "podeu fer el mateix al Krita prement la tecla :kbd:`T` per a l'eina de moure " "(penseu en «T»raducció) o :kbd:`Ctrl + T` per a l'eina de transformació." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:66 msgid "" "Press :kbd:`B` to go back to the brush tool when the transformation or " "translation is done. To find how to make advanced deformations using the :" "guilabel:`Transform` tool, do not right-click on the on-canvas widget: all " "the option are in the :guilabel:`Tool Options` docker." msgstr "" "Premeu :kbd:`B` per tornar a l'eina de pinzell quan es fa la transformació o " "la traducció. Per a trobar com fer deformacions avançades utilitzant l'eina :" "guilabel:`Transformació`, no feu clic dret sobre l'estri del llenç: totes " "les opcions es trobaran a l'acoblador :guilabel:`Opcions d'eines`." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:69 msgid "Changes can be applied with :kbd:`Enter` for the Transform tool." msgstr "" "Els canvis es poden aplicar amb :kbd:`Intro` per a l'eina Transformació." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:73 msgid "Move tool changes are auto-applied." msgstr "Els canvis a l'eina de moure seran aplicats automàticament." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:76 msgid "Selections" msgstr "Seleccions" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:78 msgid "" "Like in PS, you can use :kbd:`Alt` or :kbd:`Shift` during a selection to " "remove or add selection to the active selection. Krita also offers sub tools " "for this, and you can select them in the :guilabel:`Tool Options` if a " "select tool is active. These sub tools are represented as icons. You can " "switch to those sub modes by pressing:" msgstr "" "Com en el PS, podeu utilitzar :kbd:`Alt` o :kbd:`Majús.` durant una selecció " "per eliminar o afegir la selecció a la selecció activa. El Krita també " "ofereix subeines per a això, i podeu seleccionar-les a les :guilabel:" "`Opcions d'eina` si hi ha activa una eina de selecció. Aquestes subeines " "estan representades com a icones. Podeu canviar a aquests submodes prement:" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:81 msgid ":kbd:`R` to replace selection" msgstr ":kbd:`R` per a substituir la selecció." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:82 msgid ":kbd:`T` to intersect" msgstr ":kbd:`T` per a intersectar." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:83 msgid "" ":kbd:`A` to add to the selection (this is the one you will want to use often)" msgstr "" ":kbd:`A` per afegir a la selecció (aquesta és la que voldreu utilitzar " "sovint)." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:84 msgid ":kbd:`S` to subtract from the selection (the other one popular)" msgstr ":kbd:`S` per a restar de la selecció (una altra de popular)." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:86 msgid "Or hold:" msgstr "O manteniu premuda:" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:88 msgid ":kbd:`Alt` to subtract from the selection" msgstr ":kbd:`Alt` per a restar de la selecció." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:89 msgid ":kbd:`Shift` to add to the selection" msgstr ":kbd:`Majús.` per afegir a la selecció." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:90 msgid ":kbd:`Alt + Shift` to intersect" msgstr ":kbd:`Alt + Majús.` per a intersectar." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:94 msgid "" "You cannot press :kbd:`Ctrl` to move the content of the selection (you have " "to press :kbd:`T` or select the :guilabel:`Move Tool`)." msgstr "" "No podeu prémer :kbd:`Ctrl` per a moure el contingut de la selecció (heu de " "prémer :kbd:` T` o seleccioneu l'eina :guilabel:`Eina de moure`)." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:96 msgid "Some other tips:" msgstr "Alguns altres consells:" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:98 msgid "" "If you want to convert a layer to a selection (to select the visible " "pixels), right-click on the layer docker, and choose :guilabel:`Select " "Opaque`." msgstr "" "Si voleu convertir una capa a una selecció (per a seleccionar els píxels " "visibles), feu clic dret sobre l'acoblador de la capa i trieu :guilabel:" "`Selecciona opac`." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:99 msgid "" "If you use a polygonal selection tool, or a selection which needs to be " "‘closed’, you will be able to do it or by using a double-click, or by using " "a :kbd:`Shift` - |mouseleft| ." msgstr "" "Si utilitzeu una eina de selecció poligonal o una selecció en la qual s'ha " "de «tancar», podreu fer-ho fent doble clic o bé utilitzant una :kbd:`Majús.` " "- |mouseleft|." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:101 msgid "" "You can scale selection. To do this, choose :menuselection:`Select --> " "Scale`." msgstr "" "Podeu escalar la selecció. Per a fer-ho, trieu :menuselection:`Selecciona --" "> Escala`." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:105 msgid "" "Also, in the :guilabel:`Select` menu there are more classical options to " "grow, shrink, feather, border, etc." msgstr "" "A més, al menú :guilabel:`Selecciona` hi ha més opcions clàssiques per " "augmentar, encongir, suavitzar, vora, etc." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:107 msgid "" "If you enable :guilabel:`Show Global Selection Mask` (:guilabel:`Select` " "menu) you can scale/rotate/transform/move or paint on selection like on " "regular greyscale layer." msgstr "" "Si habiliteu :guilabel:`Mostra la màscara de selecció global` (menú :" "guilabel:`Selecciona`) podreu escalar/girar/transformar/moure o pintar sobre " "la selecció com en la capa en escala de grisos regular." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:109 msgid ":kbd:`Ctrl + H`: Show / Hide selection (same shortcut)" msgstr ":kbd:`Ctrl + H`: Mostra / Oculta la selecció (la mateixa drecera)." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:110 msgid ":kbd:`Ctrl + A`: Select All" msgstr ":kbd:`Ctrl + A`: Selecciona-ho tot." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:111 msgid "" ":kbd:`Ctrl + Shift + A`: deselect All (and not :kbd:`Ctrl + D` as in PS)" msgstr "" ":kbd:`Ctrl + Majús. + A`: desselecciona-ho tot (i no el :kbd:`Ctrl + D` com " "en el PS)." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:113 msgid "" "Note for Gimp user: Krita auto-expands and auto defloats new layers created " "from a selection after a :kbd:`Ctrl + C`, :kbd:`Ctrl + V` so you do not have " "to worry about not being able to paint outside the pasted element." msgstr "" "Nota per als usuaris del Gimp: El Krita s'expandirà i desenvoluparà " "automàticament les noves capes creades a partir d'una selecció després d'una " "drecera :kbd:`Ctrl + C`, :kbd:`Ctrl + V`, de manera que no us haureu de " "preocupar de no poder pintar fora de l'element enganxat." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:117 msgid "" "This doesn't work as intended right now. Intersect is a selection mode which " "uses :kbd:`T` as the shortcut. However :kbd:`T` is also used to switch to " "the :guilabel:`Move tool` so this shortcut is not functional right now. You " "have to use the button on the :guilabel:`Tool Options`." msgstr "" "Per ara això no funciona com es pretén. Interseca és un mode de selecció que " "utilitza la drecera :kbd:`T`. No obstant això, :kbd:`T` també s'utilitza per " "canviar a l':guilabel:`Eina de moure`, de manera que aquesta drecera en " "aquest moment no funciona. Haureu d'utilitzar el botó a :guilabel:`Opcions " "de l'eina`." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:120 msgid "Layer Handling" msgstr "Manegar les capes" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:122 msgid "The most common shortcuts are very similar in PS and Krita:" msgstr "Les dreceres més habituals són molt similars entre el PS i el Krita:" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:124 msgid ":kbd:`Ctrl + J`: duplicate" msgstr ":kbd:`Ctrl + J`: duplica." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:125 msgid ":kbd:`Ctrl + E`: merge down" msgstr ":kbd:`Ctrl + E`: fusiona cap avall." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:126 msgid "" ":kbd:`Ctrl + Shift + E`: flattens all (not :kbd:`Ctrl + Shift + M` as in PS)" msgstr "" ":kbd:`Ctrl + Majús. + E`: aplana-ho tot (no :kbd:`Ctrl + Majús. + M` com en " "el PS)." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:127 msgid ":kbd:`Ins`: insert a new paint layer" msgstr ":kbd:`Inser.`: insereix una capa de pintura nova." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:128 msgid "" ":kbd:`Ctrl + G`: create new layer group and move selected layers to this " "group" msgstr "" ":kbd:`Ctrl + G`: Creeu un grup de capes nou i mou les capes seleccionades a " "aquest grup." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:131 msgid "Groups and Blending Mode (Composite Mode):" msgstr "Grups i mode de barreja (mode de composició):" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:133 msgid "" "The group blending mode in Krita has priority over child layers and " "overrides it. This can be surprising for Photoshop users. On Photoshop you " "can use groups to just clean your layer stack and keep blending mode of your " "layer compositing through all the stack. In Krita the compositing will " "happen at first level inside the group, then taking into account the " "blending mode of the group itself. Both systems have pros and cons. Krita’s " "way is more predictable according to some artists, compositing-wise. The PS " "way leads to a cleaner and better ordered layer stack visually wise." msgstr "" "El mode de barreja de grups en el Krita té prioritat sobre les capes filles " "i les sobreescriu. Això pot ser sorprenent per als usuaris del Photoshop. Al " "Photoshop podeu utilitzar grups per a netejar la vostra pila de capes i " "mantenir el mode de barreja de la capa composició a través de tota la pila. " "Al Krita, la composició passarà al primer nivell dins del grup, tenint en " "compte el mode de barreja del mateix grup. Ambdós sistemes tenen pros i " "contres. La manera del Krita és més predictible segons alguns artistes, " "composició sàvia. La manera del PS condueix a una millor neteja i ordenació " "visual de la pila de capes." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:137 msgid "Multi Layer Transform or Move" msgstr "Transformar o moure múltiples capes" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:139 msgid "" "You can select multiple layers on the stack by holding down :kbd:`Shift` as " "in PS, and if you move the layer inside a group you can move or transform " "the whole group - including doing selection on the group and cut all the sub " "layers inside on the fly. You can not apply filters to group to affect " "multiple layers." msgstr "" "Podeu seleccionar múltiples capes a la pila mantenint premuda :kbd:`Majús.` " "com al PS, i si moveu la capa dins d'un grup, podreu moure o transformar tot " "el grup, fins i tot fent la selecció al grup i retallant totes les subcapes " "a l'interior sobre la marxa. No podreu aplicar filtres al grup per afectar " "múltiples capes." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:142 msgid "Clipping Masks" msgstr "Màscares de retall" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:144 msgid "" "Krita has no clipping mask, but there is a workaround involving layer groups " "and :guilabel:`Inherit alpha` (see the alpha icon). Place a layer with the " "shape you want to clip the other with at the bottom of a group and layers " "above with the :guilabel:`Inherit alpha` option. This will create the same " "effect as the “clipping mask” PS feature." msgstr "" "El Krita no té màscara de retall, però hi ha una solució que implica grups " "de capa i :guilabel:`Hereta l'alfa` (vegeu la icona alfa). Col·loqueu una " "capa amb la forma que voleu enganxar l'altra amb la part inferior d'un grup " "i les capes a sobre amb l'opció :guilabel:`Hereta l'alfa`. Això crearà el " "mateix efecte que la característica «màscara de retall» del PS." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:146 msgid "" "This process of arranging groups for inherit alpha can be done automatically " "by :kbd:`Ctrl + Shift + G` shortcut. It creates a group with base layer and " "a layer above it with inherit alpha option checked by default." msgstr "" "Aquest procés ordenarà els grups per heretar l'alfa, es pot fer " "automàticament amb la drecera :kbd:`Ctrl + Majús. + G`. Això crearà un grup " "amb capa base i una capa sobre seu amb l'opció hereta l'alfa marcada de " "manera predeterminada." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:149 msgid "Pass-through mode" msgstr "Mode curtcircuitat" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:151 msgid "" "This is available in Krita, but not implemented as a blending mode. Rather, " "it is an option next to ‘inherit alpha’ on group layers." msgstr "" "Això està disponible al Krita, però no s'ha implementat com a mode de " "barreja. Al contrari, és una opció al costat d'«hereta l'alfa» sobre les " "capes de grup." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:154 msgid "Smart Layers" msgstr "Capes intel·ligents" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:156 msgid "" "Instead of having smart layers that you can do non-destructive transforms " "on, Krita has the following set of functionality:" msgstr "" "En comptes de tenir capes intel·ligents amb les que podríeu fer " "transformacions no destructives, el Krita té el següent conjunt de " "característiques:" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:158 msgid "File Layers" msgstr "Capes de fitxer" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:159 msgid "" "These are layers which point to an outside file, and will get automatically " "updated if the outside file changes." msgstr "" "Aquestes són capes que apunten a un fitxer extern, i s'actualitzaran " "automàticament si aquest canvia." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:160 msgid "Clone Layers" msgstr "Capes de clonatge" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:161 msgid "" "These are layers that are an ‘instance’ of the layer you had selected when " "creating them. They get updated automatically when the original layer " "updates." msgstr "" "Aquestes capes són una «instància» de la capa que heu seleccionat en crear-" "les. S'actualitzen automàticament quan s'actualitza la capa original." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:162 msgid "Transform Masks" msgstr "Màscares de transformació" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:163 msgid "" "These can be used to non-destructive transform all layer types, including " "the file and clone layers." msgstr "" "Es poden utilitzar per a la transformació no destructiva de tots els tipus " "de capa, incloses les capes de fitxer i de clonatge." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:165 msgid "Filter Masks" msgstr "Màscares de filtratge" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:165 msgid "" "Like adjustment layers, these can apply filters non-destructively to all " "layer types, including file and clone layers." msgstr "" "Igual que les capes d'ajust, aquestes poden aplicar filtres no destructius a " "tots els tipus de capa, incloses les capes de fitxer i de clonatge." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:168 msgid "Layer styles" msgstr "Estils de capa" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:170 msgid "" "You can apply Photoshop layerstyles in Krita by right clicking any given " "layer type and selecting ‘layer style’ from the context menu. Krita can open " "and save ASL files, but not all layer style functionality is there yet." msgstr "" "Podeu aplicar els estils de capa del Photoshop al Krita fent clic dret a " "qualsevol tipus de capa indicada i seleccionant «estil de la capa» des del " "menú contextual. El Krita pot obrir i desar els fitxers ASL, però encara no " "hi ha cap característica per a l'estil de la capa." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:173 #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:384 msgid "Other" msgstr "Altres" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:175 msgid "" "Layers and groups can be exported. See the :guilabel:`Layer` top menu for " "this and many other options." msgstr "" "Es poden exportar les capes i els grups. Vegeu la part superior del menú :" "guilabel:`Capa` per a aquesta i moltes altres opcions." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:177 msgid "" "Krita has at least 5 times more blending modes than PS. They are sorted by " "categories in the drop down menu. You can use the checkbox to add your most " "used to the Favorite categories." msgstr "" "El Krita té almenys 5 vegades més modes de barreja que el PS. Estan ordenats " "per categories a la llista desplegable. Podeu utilitzar la casella de " "selecció per afegir les categories més utilitzades a les Categories " "preferides." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:180 msgid "Paint tools" msgstr "Eines de pintura" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:182 msgid "" "This is Krita's strong point. There are many paint tools and they have a lot " "of options." msgstr "" "Aquest és el punt fort del Krita. Hi ha moltes eines de pintura i tenen " "moltes opcions." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:185 msgid "Tools" msgstr "Eines" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:187 msgid "" "In Krita, there is a totally different paradigm for defining what ‘tools’ " "are compared to PS. Unlike in PS, you will not find the brush, eraser, " "clone, blur tool, etc. Instead, you will find a *way to trace* your strokes " "on the canvas: freehand, line, rectangle, circle, multiple brush, etc. When " "you have selected the ‘way to trace’ you can choose the *way to paint*: " "erasing / cloning / blurring, etc are all part of *way it paint* managed by " "the brush-engines options. These brush engine options are saved into so-" "called *presets*, which you can find on :guilabel:`Brush presets`. You can " "fine tune, and build your own presets using the :guilabel:`Edit Brush " "Settings` icon on the top tool bar." msgstr "" "Al Krita hi ha un paradigma totalment diferent per a definir quines «eines» " "es comparen amb el PS. A diferència del PS, no trobareu les eines de " "pinzell, esborrador, clona, difuminat, etc. En canvi, trobareu una *manera " "de traçar* les vostres pinzellades al llenç: a mà alçada, línia, rectangle, " "cercle, múltiples pinzells, etc. Quan hagueu seleccionat la «manera de " "traçar», podreu triar la *manera de pintar*:esborrar/clonar/difuminar, etc. " "formen part de *manera en què es pinta* gestionada per les opcions dels " -"motors de pinzell. Aquestes opcions del motor de pinzell es desen en els " +"motors de pinzell. Aquestes opcions del motor de pinzells es desen en els " "anomenats *valors predefinits*, els quals trobareu a :guilabel:`Valors " "predefinits del pinzell`. Podeu afinar i crear els vostres propis valors " "predefinits utilitzant la següent icona :guilabel:`Edita els ajustaments del " "pinzell` que hi ha a la part superior de la barra d'eines." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:190 msgid "Erasing" msgstr "Esborrar" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:192 msgid "" "In Krita, the eraser is not a tool, it is a Blending mode (or Composite " "mode). You can change each brush you have to erase by pressing :kbd:`E`. By " "pressing :kbd:`E` again you’ll be back to the last blending mode you had " "selected before pressing :kbd:`E` the first time." msgstr "" "A Krita, l'esborrador no és una eina, és un mode de barreja (o mode de " "composició). Podeu canviar cada pinzell si teniu que esborrar prement :kbd:" "`E`. Prement :kbd:`E` tornarà a estar en l'últim mode de barreja que heu " "seleccionat abans de prémer :kbd:`E` la primera vegada." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:195 msgid "Useful shortcuts" msgstr "Dreceres d'utilitat" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:197 msgid "" ":kbd:`Shift`: Grow or Shrink the brush size (or :kbd:`[` and :kbd:`]`)." msgstr "" ":kbd:`Majús.`: feu augmentar o encongir la mida del pinzell (o :kbd:`[` i :" "kbd:`]`)." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:198 msgid "" ":kbd:`/`: Switch last preset selected and current (ex: a pencil preset, and " "an eraser preset)." msgstr "" ":kbd:`/`: alterna el darrer valor predefinit que està seleccionat i l'actual " "(p. ex., un llapis i un esborrador predefinits)." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:199 msgid "" ":kbd:`K` and :kbd:`L`: increment Darker and Lighter value of the active " "color" msgstr "" ":kbd:`K` i :kbd:`L`: incrementa els valors Més fosc i Més clar del color " "actiu." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:200 msgid ":kbd:`I` and :kbd:`O`: increment opacity plus or minus." msgstr ":kbd:`I` i :kbd:`O`: incrementa més o menys l'opacitat." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:201 msgid ":kbd:`D`: Reset color to black/foreground and white/background" msgstr ":kbd:`D`: restableix el color a negre/primer pla i blanc/fons." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:202 msgid ":kbd:`X`: Switch background and foreground colors" msgstr ":kbd:`X`: alterna els colors de fons i de primer pla." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:203 msgid "" ":kbd:`Shift + I` / :kbd:`Shift + N` / :kbd:`Shift + M`: a set of default " "keyboard shortcuts for accessing the on-canvas color selector." msgstr "" ":kbd:`Majús. + I` / :kbd:`Majús. + N` / :kbd:`Majús. + M`: un conjunt de " "dreceres de teclat predeterminades per accedir al selector de color del " "llenç." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:207 msgid "" "Some people regard these shortcuts as somewhat unfortunate. The reason is " "that they are meant to be used during painting and left-:kbd:`Shift` is at " "the opposite end of the keyboard from :kbd:`I`, :kbd:`M` and :kbd:`N`. So " "for a right-handed painter, this is very difficult to do while using the " "stylus with a right hand. Note that you can reassign any shortcut by using " "the shortcut configuration in :menuselection:`Settings --> Configure " "Shortcuts`." msgstr "" "Alguns consideren que aquestes dreceres són un xic desafortunades. La raó és " "que estan destinades a ser utilitzades durant la pintura i la tecla :kbd:" "`Majús.` esquerra es troba en l'extrem oposat del teclat des de :kbd:`I`, :" "kbd:`M` i :kbd:`N`. De manera que per a un pintor dretà, serà molt difícil " "fer-ho mentre utilitza el llapis amb la mà dreta. Tingueu en compte que " "podeu tornar a assignar qualsevol drecera utilitzant la configuració de les " "dreceres a :menuselection:`Arranjament --> Configura les dreceres`." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:210 msgid "Stabilization / Path Smoothing" msgstr "Estabilització / Suavitzat del traç" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:212 msgid "" "Using the freehand ‘paint with brush’ tool that you can find on the Tool " "Options, more settings for smoothing the path and stabilization of your " "brush strokes are available." msgstr "" "Utilitzant l'eina «pintar amb pinzell» a mà alçada que trobareu a les " "Opcions de l'eina, hi ha més ajustaments per a suavitzar i estabilitzar les " "pinzellades." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:215 msgid "Global pressure curve" msgstr "Corba de pressió global" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:217 msgid "" "If you find the feeling of Krita too hard or too soft regarding the pressure " "when you paint, you can set a softer or harder curve here: :menuselection:" "`Settings --> Configure Krita --> Tablet settings`" msgstr "" "Si teniu la sensació que el Krita és massa dur o suau respecte a la pressió " "quan pinteu, podreu establir una corba més suau o dura aquí: :menuselection:" "`Arranjament --> Configura el Krita --> Arranjament de la tauleta`" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:220 msgid "Adjustment" msgstr "Ajust" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:222 msgid "" "Like in PS, you can use the classic filters to adjust many things while " "painting:" msgstr "" "Igual que al PS, podeu utilitzar els filtres clàssics per ajustar moltes " "coses mentre pinteu:" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:224 msgid ":kbd:`Ctrl + L` : Levels" msgstr ":kbd:`Ctrl + L` : nivells." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:225 msgid ":kbd:`Ctrl + U`: HSV adjustment" msgstr ":kbd:`Ctrl + U`: ajustament HSV." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:226 msgid ":kbd:`Ctrl + I`: Invert" msgstr ":kbd:`Ctrl + I`: inverteix." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:229 msgid "Dodge / Burn / Blur Tools" msgstr "Eines Esvaeix / Crema / Difuminat" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:231 msgid "" "Unlike Photoshop, where these are separate tools, in Krita, they are " "available via the Filter Brush Engine, which allows you to apply the " "majority of Krita's filters in brush form." msgstr "" "A diferència del Photoshop, on es tracta d'eines separades, al Krita, " -"aquestes estan disponibles a través del motor pinzell de filtratge, el qual " -"permet aplicar la majoria dels filtres del Krita en forma de pinzell." +"aquestes estan disponibles a través del motor del pinzell de filtratge, el " +"qual permet aplicar la majoria dels filtres del Krita en forma de pinzell." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:234 msgid "Themes" msgstr "Temes" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:235 msgid "" "If you don’t like the dark default theme of Krita go to: :menuselection:" "`Settings --> Themes`, and choose a brighter or darker theme. If you don’t " "like the color outside your viewport go to: :menuselection:`Settings --> " "Configure Krita --> Display`, and change the Canvas border color." msgstr "" "Si no us agrada el tema predeterminat fosc del Krita, aneu a: :menuselection:" "`Arranjament --> Temes` i trieu un tema més brillant o més fosc. Si no us " "agrada el color fora de l'àrea de visualització, aneu a: :menuselection:" "`Arranjament --> Configura el Krita --> Mostra` i canvieu el color de la " "vora del llenç." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:239 msgid "What Krita Has Over Photoshop" msgstr "Allò que té el Krita sobre el Photoshop" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:241 msgid "" "As mentioned in the introduction, Krita is a specialized paint application. " "Thus, it also has specialized tools for painting. Similar tools are not " "found in more generalized image manipulation applications such as PS. Here " "is a short list of the most important ones." msgstr "" "Com s'ha esmentat en la introducció, el Krita és una aplicació de pintura " "especialitzada. Així, també compta amb eines especialitzades per a la " "pintura. No es troben eines similars en aplicacions de manipulació d'imatges " "més generals, com el PS. Aquí teniu una breu llista de les més importants." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:244 msgid "Brush Engines" -msgstr "Motors de pinzell" +msgstr "Motors de pinzells" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:246 msgid "" "Krita has a lot of different so-called brush engines. These brush engines " "define various methods on how the pixels end up on your canvas. Brush " "engines with names like Grid, Particles, Sketch and others will bring you " "new experiences on how the brushes work and a new landscape of possible " "results. You can start customizing brushes by using the brush-settings " "editor, which is accessible via the toolbar, but it's much easier to just " "press :kbd:`F5`." msgstr "" -"El Krita té un munt de diferents motors de pinzell. Aquests motors de " -"pinzell defineixen diversos mètodes sobre com tracen els píxels al vostre " +"El Krita té un munt de diferents motors de pinzells. Aquests motors de " +"pinzells defineixen diversos mètodes sobre com tracen els píxels al vostre " "llenç. Els motors de pinzell amb noms com Quadrícula, Partícules, Esbós i " "altres us portaran noves experiències sobre com funcionen els pinzells i un " "nou panorama de possibles resultats. Podeu començar a personalitzar els " "pinzells mitjançant l'editor dels ajustaments del pinzell, el qual és " "accessible a través de la barra d'eines, però és molt més senzill prémer :" "kbd:`F5`." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:249 msgid "Tags for brush presets" msgstr "Etiquetes per a valors predefinits del pinzell" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:251 msgid "" "This is a very useful way to configure brush presets. Each brush can have " "any amount of tags and be in any group. You can make tag for blending " "brushes, for texture brushes, for effect brushes, favorites etc." msgstr "" "Aquesta és una manera molt útil de configurar els valors predefinits del " "pinzell. Cada pinzell pot tenir qualsevol quantitat d'etiquetes i estar en " "qualsevol grup. Podeu crear una etiqueta per a pinzells de barreja, per a " "pinzells de textura, per a pinzells d'efecte, preferits, etc." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:254 msgid "Settings curves" msgstr "Ajustaments de les corbes" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:256 msgid "" "You can set setting to pressure (speed/distance/tilt/random/etc.) relation " "for each brush setting." msgstr "" "Podeu establir l'ajustament a la relació de pressió (velocitat/distància/" "inclinació/aleatori, etc.) per a cada ajustament del pinzell." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:262 msgid "The Pop-up Palette" msgstr "La paleta emergent" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:267 msgid "" "Easily to be found on |mouseright|, the pop-up palette allows you to quickly " "access brushes, color history and a color selector within arm's reach. The " "brushes are determined by tag, and pressing the lower-right configure button " "calls a drop-down to change tags. This allows you to tag brushes in the " "preset docker by workflow, and quickly access the right brushes for the " "workflow you need for your image." msgstr "" "Fàcil de trobar amb el |mouseright|, la paleta emergent permet accedir amb " "rapidesa als pinzells, a l'historial de colors i a un selector de color a " "l'abast de la ma. Els pinzells es determinen per etiqueta i, al prémer el " "botó de configuració de la part inferior dreta, es cridarà una llista " "desplegable per a canviar les etiquetes. Això permet que etiqueteu els " "pinzells als valors predefinits de l'acoblador per al flux de treball i " "accedir ràpidament als pinzells adequats durant el flux de treball que " "necessiteu per a la vostra imatge." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:270 msgid "Transformations" msgstr "Transformacions" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:272 msgid "" "The Krita transformation tool can perform transformations on a group and " "affect child layers. There are several modes, like free, perspective, warp, " "the powerful cage and even liquify. Furthermore, you can use transformation " "masks to apply transforms non-destructively to any layer type, raster, " "vector group, you name it." msgstr "" "L'eina de transformació del Krita pot realitzar transformacions sobre un " "grup i afectar les capes filles. Hi ha diversos modes, com ara lliure, " "perspectiva, deformació, la potent gàbia i fins i tot liqüescent. A més, " "podeu utilitzar màscares de transformació per aplicar transformacions de " "forma no destructiva a qualsevol tipus de capa, rasterització, grup de " "vectors, el vostre nom." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:279 msgid ".. image:: images/en/Krita-transform-mask.png" msgstr ".. image:: images/en/Krita-transform-mask.png" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:279 msgid "Transform masks allows non-destructive transforms" msgstr "Les màscares de transformació permeten transformacions no destructives" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:282 msgid "Incremental Save" msgstr "Desament incremental" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:284 msgid "" "You can save your artwork with the pattern : myartworksname_001.kra , " "myartworksname_002.kra, myartworksname_003.kra etc, by pressing a single " "key on the keyboard. Krita will increment the final number if the pattern " "\"_XXX\" is recognized at the end of the file's name." msgstr "" "Podeu desar les vostres obres d'art amb el patró: " "nom_obra_artística_meva_001.kra, nom_obra_artística_meva_002.kra, " "nom_obra_artística_meva_003.kra, etc, prement una sola tecla al teclat. El " "Krita augmentarà el número final si es reconeix el patró «_XXX» al final del " "nom del fitxer." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:289 msgid "" "This feature allows you to avoid overwriting your files, and keep track to " "your older version and work in progress steps." msgstr "" "Aquesta característica permet evitar sobreescriure els vostres fitxers i fer " "un seguiment de la vostra versió anterior i treballar en els passos del " "progrés." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:292 msgid "Color to alpha Filter" msgstr "Filtre de color a alfa" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:294 msgid "" "If you want to delete the white of the paper from a scanned artwork, you can " "use this filter. It takes a color and turns it into pure transparency." msgstr "" "Si voleu eliminar el blanc del paper d'una obra d'art escanejada, podeu " "utilitzar aquest filtre. Pren un color i el converteix a transparència pura." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:300 msgid "Many Blending Modes" msgstr "Molts modes de barreja" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:302 msgid "" "If you like using blending modes, Krita has many of them -- over 70! You " "have plenty of room for experimentation. A special system of favorite " "blending modes has been created to let you have fast access to the ones you " "use the most." msgstr "" "Si us agrada fer servir modes de barreja, el Krita en té molts. Més de 70! " "Teniu molt espai per a l'experimentació. S'ha creat un sistema especial de " "modes de barreja preferits per a permetre-vos accedir amb rapidesa als que " "més utilitzeu." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:306 msgid "Painting Assistants" msgstr "Assistents de pintura" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:308 msgid "" "Krita has many painting assistants. This is a special type vector shapes " "with a magnetic influence on your brush strokes. You can use them as rulers, " "but with other shapes than just straight." msgstr "" "El Krita té molts assistents de pintura. Es tracta d'un tipus especial de " "formes vectorials amb una influència magnètica en les pinzellades. Podeu " "emprar-los com a regles, però amb altres formes que no siguin rectes." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:314 msgid ".. image:: images/en/Krita_basic_assistants.png" msgstr ".. image:: images/en/Krita_basic_assistants.png" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:314 msgid "Krita's vanishing point assistants in action" msgstr "Assistents del punt de fuga del Krita en acció." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:317 msgid "Multibrushes: Symmetry / Parallel / Mirrored / Snowflake" msgstr "Múltiples pinzells: Simetria / Paral·lel / Emmirallat / Floc de neu" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:319 msgid "" "Krita's Multibrush tool allows you to paint with multiple brushes at the " "same time. Movements of the brushes other than the main brush is created by " "mirroring what you paint, or duplicating it by any number around any axis. " "They can also be used in parallel mode." msgstr "" "L'eina Múltiples pinzells del Krita permet pintar amb múltiples pinzells " "alhora. Els moviments dels pinzells que no siguin el pinzell principal es " "crearan reflectint el que pinteu, o duplicant per qualsevol número al " "voltant de qualsevol eix. També es poden utilitzar en mode paral·lel." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:325 msgid "A Wide Variety of Color Selectors" msgstr "Una àmplia varietat de selectors de color" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:327 msgid "" "The :guilabel:`Advanced Color Selector` docker offer you a wide choice of " "color selectors." msgstr "" "L'acoblador :guilabel:`Selector avançat del color` ofereix una àmplia " "selecció de selectors de color." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:333 msgid "View dependent color filters" msgstr "Vista dependent dels filtres de color" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:334 msgid "" "Using the LUT docker, Krita allows you to have a separate color correction " "filter per view. While this is certainly useful to people who do color " "correction in daily life, to the artist this allows for seeing a copy of the " "image in luminance grayscale, so that they instantly know the values of the " "image." msgstr "" "Utilitzant l'acoblador LUT, el Krita permet tenir un filtre de correcció del " "color separat. Si bé això és certament útil per a les persones que realitzen " "correccions de color a la vida quotidiana, per a l'artista, això permet " "veure una còpia de la imatge en escala de grisos amb luminància, de manera " "que coneixereu immediatament els valors de la imatge." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:340 msgid ".. image:: images/en/Krita-view-dependant-lut-management.png" msgstr ".. image:: images/en/Krita-view-dependant-lut-management.png" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:340 msgid "Using the LUT docker to change the colors per view" msgstr "Utilitzar l'acoblador LUT per a canviar els colors per cada vista" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:343 msgid "HDR color painting" msgstr "Pintura en color HDR" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:345 msgid "" "This same LUT docker is the controller for painting with HDR colors. Using " "the LUT docker to change the exposure on the view, Krita allows you to paint " "with HDR colors, and has native open exr support!" msgstr "" "Aquest mateix acoblador LUT és el controlador per a pintar amb colors HDR. " "Utilitzant l'acoblador LUT per a canviar l'exposició sobre la vista, el " "Krita permet pintar amb colors HDR i compta amb suport EXR natiu!" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:351 msgid ".. image:: images/en/Krita-hdr-painting.png" msgstr ".. image:: images/en/Krita-hdr-painting.png" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:351 msgid "Painting with HDR colors" msgstr "Pintura amb colors HDR" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:354 msgid "What Krita Does Not Have" msgstr "El que el Krita no té" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:356 msgid "" "Again, Krita is a digital paint application and Photoshop is an image " "manipulation program with some painting features. This means that there are " "things you can do in PS that you cannot do in Krita. This section gives a " "short list of these features." msgstr "" "Una vegada més, el Krita és una aplicació de pintura digital i el Photoshop " "és un programa per a la manipulació d'imatges amb algunes característiques " "de pintura. Això vol dir que hi ha coses que podeu fer al PS que no podeu " "fer al Krita. Aquesta secció ofereix una breu llista d'aquestes " "característiques." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:359 msgid "Filters" msgstr "Filtres" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:361 msgid "" "Krita has a pretty impressive pack of filters available, but you will " "probably miss one or two of the special filters or color adjustment tools " "you often use in Photoshop. For example, there is no possibility to tweak a " "specific color in HSV adjustment." msgstr "" "El Krita té un paquet de filtres molt impressionant, però probablement " "trobareu a faltar un o dos dels filtres especials o les eines d'ajustament " "del color que utilitzeu sovint en el Photoshop. Per exemple, no hi ha " "possibilitat de modificar un color específic en l'ajustament de HSV." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:364 msgid "Automatic healing tool" msgstr "Eina automàtica de guariment" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:366 msgid "" "Krita does not have an automatic healing tool. It does, however, have a so-" "called clone tool which can be used to do a healing correction, although not " "automatically." msgstr "" "El Krita no té una eina automàtica de guariment. Tanmateix, disposa d'una " "eina de clonatge que es pot utilitzar per a fer una correcció de guariment, " "encara que no de manera automàtica." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:369 msgid "Macro Recording" msgstr "Enregistrar macros" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:371 msgid "" "Macro recording and playback exists in Krita, but it is not working well at " "this time." msgstr "" "L'enregistrament i la reproducció de macros existeix en el Krita, però en " "aquest moment no està funcionant bé." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:374 msgid "Text Tool" msgstr "Eina de text" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:376 msgid "" "The text tool in Krita is less advanced than the similar tool in Photoshop." msgstr "" "L'eina de text al Krita és menys avançada que l'eina similar al Photoshop." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:379 msgid "Blending Modes While Transforming" msgstr "Modes de barreja mentre es transforma" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:381 msgid "" "When you transform a layer or a selection in Krita, the transformation " "appears on the top of your layer stack ignoring the layer blending mode." msgstr "" "Quan transformeu una capa o una selecció al Krita, la transformació " "apareixerà a la part superior de la pila de capes ignorant el mode de " "barreja de capes." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:386 msgid "" "Also, you cannot ‘Export for web’, ‘Image Ready’ for Gif frame or slicing " "web image, etc" msgstr "" "A més, no podreu «Exporta per al web», «Imatge llesta» per al fotograma GIF " "o retallar una imatge del web, etc." #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:389 msgid "Conclusion" msgstr "Conclusió" #: ../../user_manual/introduction_from_other_software/introduction_from_photoshop.rst:391 msgid "" "Using these tips you will probably be up to speed with Krita in a short " "time. If you find other things worth mentioning in this document we, the " "authors, would be interested in hearing about them. Krita develops fast, so " "we believe that the list of things possible in Photoshop but not in Krita " "will become shorter in time. We will maintain this document as this happens." msgstr "" "Amb aquests consells, probablement estareu corrent amb el Krita en poc " "temps. Si trobeu altres coses que cal esmentar en aquest document, " "nosaltres, els autors, estem interessats a escoltar-les. El Krita es " "desenvolupa ràpidament, per la qual cosa creiem que la llista de coses " "possibles al Photoshop, però no al Krita, serà més curta en el temps. " "Mantindrem aquest document mentre això succeeix." diff --git a/locale/ca/LC_MESSAGES/user_manual/introduction_from_other_software/introduction_from_sai.po b/locale/ca/LC_MESSAGES/user_manual/introduction_from_other_software/introduction_from_sai.po index fe3a10454..d48f8d923 100644 --- a/locale/ca/LC_MESSAGES/user_manual/introduction_from_other_software/introduction_from_sai.po +++ b/locale/ca/LC_MESSAGES/user_manual/introduction_from_other_software/introduction_from_sai.po @@ -1,619 +1,686 @@ # Translation of docs_krita_org_user_manual___introduction_from_other_software___introduction_from_sai.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: " -"docs_krita_org_user_manual___introduction_from_other_software___introduction_from_sai\n" +"Project-Id-Version: docs_krita_org_user_manual___introduction_from_other_softw" +"are___introduction_from_sai\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-03-03 03:22+0100\n" -"PO-Revision-Date: 2019-03-12 12:45+0100\n" +"PO-Revision-Date: 2019-03-14 23:12+0100\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" # skip-rule: t-sp_2p #: ../../:2 msgid "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: mouseleft" msgstr "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: mouseleft" # skip-rule: t-sp_2p #: ../../:4 msgid "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: mouseright" msgstr "" ".. image:: images/icons/Krita_mouse_right.png\n" " :alt: mouseright" # skip-rule: t-sp_2p #: ../../:6 msgid "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: mousemiddle" msgstr "" ".. image:: images/icons/Krita_mouse_middle.png\n" " :alt: mousemiddle" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:None msgid ".. image:: images/en/Krita-color-to-alpha.png" msgstr ".. image:: images/en/Krita-color-to-alpha.png" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:None msgid ".. image:: images/en/Krita_Color_Selector_Types.png" msgstr ".. image:: images/en/Krita_Color_Selector_Types.png" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:None msgid ".. image:: images/en/Krita-multibrush.png" msgstr ".. image:: images/en/Krita-multibrush.png" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:None msgid ".. image:: images/en/Krita-view-dependant-lut-management.png" msgstr ".. image:: images/en/Krita-view-dependant-lut-management.png" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:None msgid ".. image:: images/en/Krita_transforms_recursive.png" msgstr ".. image:: images/en/Krita_transforms_recursive.png" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:None msgid ".. image:: images/en/Krita_ghostlady_3.png" msgstr ".. image:: images/en/Krita_ghostlady_3.png" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:None msgid ".. image:: images/en/Krita-popuppalette.png" msgstr ".. image:: images/en/Krita-popuppalette.png" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:1 msgid "This is a introduction to Krita for users coming from Paint Tool Sai." msgstr "" "Aquesta és una introducció al Krita per als usuaris que vénen del Paint Tool " "Sai." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:17 msgid "Introduction to Krita coming from Paint Tool Sai" msgstr "Introducció al Krita si es ve del Paint Tool Sai" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:20 msgid "How do you do that in Krita?" msgstr "Com es fa això en el Krita?" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:22 msgid "" "This section goes over the functionalities that Krita and Paint Tool Sai " "share, but shows how they slightly differ." msgstr "" "Aquesta secció tracta sobre funcionalitats que comparteixen el Krita i el " "Paint Tool Sai, però mostra com es diferencien lleugerament." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:25 msgid "Canvas navigation" msgstr "Navegar pel llenç" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:27 msgid "" "Krita, just like Sai, allows you to flip, rotate and duplicate the view. " "Unlike Sai, these are tied to keyboard keys." msgstr "" "El Krita, igual que el Sai, permet invertir, girar i duplicar la vista. A " "diferència del Sai, aquestes accions disposen de dreceres de teclat." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:29 msgid "Mirror" msgstr "Emmiralla" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:30 msgid "This is tied to :kbd:`M` to flip." msgstr "Està lligada a :kbd:`M` per invertir." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:31 msgid "Rotate" msgstr "Gira" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:32 msgid "" "There's a couple of possibilities here: either :kbd:`4` and :kbd:`6`, or :" "kbd:`Ctrl + [` and :kbd:`Ctrl + ]` for basic 15 degrees rotation left and " "right. But you can also have more sophisticated rotation with :kbd:`Shift + " "Space` + drag or :kbd:`Shift` + |mousemiddle| + drag. To reset the rotation, " "press :kbd:`5`." msgstr "" "Aquí hi ha algunes possibilitats: ja sigui :kbd:`4` i :kbd:`6`, o: kbd:`Ctrl " "+ [` i :kbd:`Ctrl +]` per a la rotació bàsica de 15 graus a l'esquerra i " "dreta. Però també podeu tenir una rotació més sofisticada amb :kbd:`Majús. + " "Espai` + arrossega o :kbd:`Majús.` + |mousemiddle| + arrossega. Per a " "restablir la rotació, premeu :kbd:`5`." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:34 msgid "Zoom" msgstr "Zoom" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:34 msgid "" "You can use :kbd:`+` and :kbd:`-` to zoom out and in, or use :kbd:`Ctrl` + |" "mousemiddle|. Use 1, 2 or 3 to reset the zoom, fit the zoom to page or fit " "the zoom to page width." msgstr "" "Podeu utilitzar :kbd:`+` i :kbd:`-` per allunyar i apropar, o utilitzar :kbd:" "`Ctrl` + |mousemiddle|. Utilitzeu 1, 2 o 3 per a restablir el zoom, ajustar " "el zoom a la pàgina o ajustar el zoom a l'amplada de la pàgina." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:36 msgid "" "You can use the Overview docker in :menuselection:`Settings --> Dockers` to " "quickly navigate over your image." msgstr "" "Podeu utilitzar el connector Resum a :menuselection:`Arranjament --> " "Acobladors` per a navegar ràpidament per sobre de la vostra imatge." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:38 msgid "" "You can also put these commands on the toolbar, so it'll feel a little like " "Sai. Go to :menuselection:`Settings --> Configure Toolbars`. There are two " "toolbars, but we'll add to the file toolbar." msgstr "" "També podeu posar aquestes ordres a la barra d’eines, de manera que " "s’assimilarà una mica al Sai. Aneu a :menuselection:`Arranjament --> " "Configura les barres d’eines`. Hi ha dues barres d’eines, però l'afegirem a " "la barra d’eines de fitxers." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:40 msgid "" "Then, you can type in something in the left column to search for it. So, for " "example, 'undo'. Then select the action 'undo freehand stroke' and drag it " "to the right. Select the action to the right, and click :menuselection:" "`Change text`. There, toggle :menuselection:`Hide text when toolbar shows " "action alongside icon` to prevent the action from showing the text. Then " "press :guilabel:`OK`. When done right, the :guilabel:`Undo` should now be " "sandwiched between the save and the gradient icon." msgstr "" "Llavors, podeu escriure quelcom a la columna esquerra per a cercar-la. Així, " "per exemple, «desfés». Després seleccioneu l’acció «desfés el traç a mà " "alçada» i arrossegueu-la cap a la dreta. Seleccioneu l'acció a la dreta i " "feu clic a :menuselection:`Canvia el text`. Allà, alterneu :menuselection:" "`Oculta el text quan la barra d'eines mostri el text al costat de les " "icones` per evitar que l’acció mostri el text. A continuació, premeu :" "guilabel:`D'acord`. Quan hàgiu acabat, el :guilabel:`Desfés` hauria de ser " "intercalat entre la icona de desa i la de degradat." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:42 msgid "" "You can do the same for :guilabel:`Redo`, :guilabel:`Deselect`, :guilabel:" "`Invert Selection`, :guilabel:`Zoom out`, :guilabel:`Zoom in`, :guilabel:" "`Reset zoom`, :guilabel:`Rotate left`, :guilabel:`Rotate right`, :guilabel:" "`Mirror view` and perhaps :guilabel:`Smoothing: basic` and :guilabel:" "`Smoothing: stabilizer` to get nearly all the functionality of Sai's top bar " "in Krita's top bar. (Though, on smaller screens this will cause all the " "things in the brushes toolbar to hide inside a drop down to the right, so " "you need to experiment a little)." msgstr "" "Podeu fer el mateix amb :guilabel:`Refés`, :guilabel:`Desselecciona`, :" "guilabel:`Inverteix la selecció`, :guilabel:`Allunya`, :guilabel:`Apropa`, :" "guilabel:`Reinicia el zoom`, :guilabel:`Gira a l'esquerra`, :guilabel:`Gira " "a la dreta`, :guilabel:`Visualització en mirall` i potser :guilabel:" "`Suavitzat: Bàsic` i :guilabel:`Suavitzat: Estabilitzador` per obtenir " "gairebé totes les característiques de la barra superior del Sai a la barra " "superior del Krita. (Tot i que, a les pantalles més petites, això farà que " "totes les coses de la barra d’eines dels pinzells s’ocultin dins d’una " "llista desplegable a la dreta, de manera que necessiteu experimentar una " "mica)." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:44 msgid "" ":guilabel:`Hide Selection`, :guilabel:`Reset Rotation` are currently not " "available via the Toolbar configuration, you'll need to use the shortcuts :" "kbd:`Ctrl + H` and :kbd:`5` to toggle these." msgstr "" "Actualment, les ordres :guilabel:`Oculta la selecció`, :guilabel:`Reinicia " "el gir` no estan disponibles a través de la configuració de la barra " "d’eines, haureu d’utilitzar les dreceres :kbd:`Ctrl + H` i :kbd:`5` per " "alternar-les." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:48 msgid "" "Krita 3.0 currently doesn't allow changing the text in the toolbar, we're " "working on it." msgstr "" "Actualment, el Krita 3.0 no permet canviar el text a la barra d'eines, ja hi " "estem treballant." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:51 msgid "Right click color picker" msgstr "Clic dret per al selector de color" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:53 msgid "" "You can actually set this in :menuselection:`Settings --> Configure Krita --" "> Canvas input settings --> Alternate invocation`. Just double-click the " "entry that says :kbd:`Ctrl` + |mouseleft| before :guilabel:`Pick foreground " "color from image` to get a window to set it to |mouseright|." msgstr "" "En realitat, ho podeu establir a :menuselection:`Arranjament --> Configura " "el Krita --> Arranjament d'entrada del llenç --> Invocació alternativa`. " "Simplement feu doble clic a l'entrada que digui :kbd:`Ctrl` + |mouseleft| " "abans de :guilabel:`Tria el color del primer pla des de la imatge` per " "obtenir un diàleg per establir-la a |mouseright|." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:57 msgid "" "Krita 3.0 actually has a Paint-tool Sai-compatible input sheet shipped by " "default. Combine these with the shortcut sheet for Paint tool Sai to get " "most of the functionality on familiar hotkeys." msgstr "" "El Krita 3.0 en realitat té un full d’entrada compatible amb el Paint-tool " "Sai. Combineu-los amb la drecera de full per al Paint tool Sai per obtenir " "la major part de la funcionalitat a les tecles d’accés ràpid conegudes." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:60 msgid "Stabilizer" msgstr "Estabilitzador" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:62 msgid "" "This is in the tool options docker of the freehand brush. Use Basic " "Smoothing for more advanced tablets, and Stabilizer is much like Paint Tool " "Sai's. Just turn off :guilabel:`Delay` so that the dead-zone disappears." msgstr "" "Aquest és l'acoblador per a les opcions de l'eina del pinzell a mà alçada. " "Utilitzeu el Suavitzat bàsic per a les tauletes més avançades i si " "l’estabilitzador s’assembla molt al de Paint Tool Sai. Simplement desactiveu " "el :guilabel:`Retard` de manera que desaparegui la zona morta." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:65 msgid "Transparency" msgstr "Transparència" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:67 msgid "" "So one of the things that throw a lot of Paint Tool Sai users off is that " "Krita uses checkers to display transparency, which is actually not that " "uncommon. Still, if you want to have the canvas background to be white, this " "is possible. Just choose :guilabel:`Background: As Canvas Color` in the new " "image dialogue and the image background will be white. You can turn it back " "to transparent via :menuselection:`Image --> Change image background color`. " "If you export a PNG or JPG, make sure to uncheck :guilabel:`Save " "transparency` and to make the background color white (it's black by default)." msgstr "" +"Així que una de les coses que tiren a molts als usuaris del Paint Tool Sai és" +" que el Krita fa servir els comprovadors per a mostrar la transparència, el" +" qual en realitat no és tan infreqüent. Tot i així, si voleu que el fons del" +" llenç sigui blanc, això serà possible. Simplement trieu :guilabel:`Fons: Com" +" a color del llenç` al nou diàleg de la imatge i el fons de la imatge serà" +" blanc. Es pot tornar transparent mitjançant :menuselection:`Imatge -->" +" Canvia el color de fons de la imatge`. Si exporteu a PNG o JPG," +" assegureu-vos de desmarcar :guilabel:`Desa la transparència` i feu que el" +" color de fons sigui blanc (de manera predeterminada és negre)." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:72 msgid "" "Like Sai, you can quickly turn a black and white image to black and " "transparent with the :menuselection:`Color to Alpha Filter` under :" "menuselection:`Filters --> Colors --> Color to Alpha`" msgstr "" +"Com en el Sai, podeu convertir amb rapidesa una imatge en blanc i negre a" +" negre i transparent amb l'opció :menuselection:`Filtre de color a alfa` sota" +" :menuselection:`Filtres --> Colors --> Color a alfa`." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:75 msgid "Brush Settings" msgstr "Ajustaments del pinzell" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:77 msgid "" "Another, somewhat amusing misconception is that Krita's brush engine is not " "very complex. After all, you can only change the Size, Flow and Opacity from " "the top bar." msgstr "" +"Un altre concepte erroni, és que el motor de pinzells del Krita no és molt" +" complex. Després de tot, des de la barra superior només podeu canviar la" +" Mida, el Flux i l’Opacitat." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:79 msgid "" "This is not quite true. It's rather that we don't have our brush settings in " "a docker but a drop-down on the toolbar. The easiest way to access this is " "with :kbd:`F5`. As you can see, it's actually quite complex. We have more " "than a dozen brush engines, which are a type of brush you can make. The ones " "you are used to from Paint Tool Sai are the Pixel Brush (ink), The Color " "Smudge Brush (brush) and the filter brush (dodge, burn)." msgstr "" +"Això no és cert. Més aviat és que no tenim els ajustaments del nostre pinzell" +" en un acoblador, sinó en una llista desplegable a la barra d’eines. La" +" manera més fàcil d’accedir-hi és :kbd:`F5`. Com podeu veure, en realitat és" +" força complex. Tenim més d’una dotzena de motors de pinzells, els quals són" +" un tipus de pinzell que podeu crear. El que estàveu acostumat al Paint Tool" +" Sai són el Pinzell de píxels (tinta), El pinzell d'esborronat del color" +" (pinzell) i el Pinzell de filtratge (esvaïment, crema)." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:81 msgid "" "A simple inking brush recipe for example is to take a pixel brush, uncheck " "the 'enable pen-settings' on opacity and flow, and uncheck everything but " "size from the option list. Then, go into brush-tip, pick :ref:" "`auto_brush_tip` from the tabs, and set the size to 25 (right-click a blue " "bar if you want to input numbers), turn on anti-aliasing under the brush " "icon, and set fade to 0.9. Then, as a final touch, set spacing to 'auto' and " "the spacing number to 0.8." msgstr "" +"Per exemple, una senzilla recepta del pinzell de tinta és prendre un pinzell" +" de píxels, desmarqueu l'opció «Habilita els ajustaments de la ploma» en" +" l'opacitat i el flux, i desmarqueu-ho tot excepte la mida a la llista" +" d'opcions. A continuació, aneu a la punta del pinzell, escolliu:" +" ref:`auto_brush_tip` des de les pestanyes i establiu la mida a 25 (feu clic" +" dret a la barra blava si voleu introduir algun número), activeu" +" l’antialiàsing sota la icona del pinzell, i establiu l'ombra 0,9. A" +" continuació, com a últim toc, establiu el tipus d'espaiat a «Automàtic» i el" +" número de l’espaiat a 0,8." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:83 msgid "" "You can configure the brushes in a lot of detail, and share the packs with " "others. Importing of packs and brushes can be done via the :menuselection:" "`Settings --> Manage Resources`, where you can import .bundle files or .kpp " "files." msgstr "" +"Podeu configurar els pinzells amb molts detalls i compartir els paquets amb" +" altres usuaris. La importació de paquets i pinzells es pot fer a través del" +" :menuselection:`Arranjament --> Gestió de recursos`, des d'on podreu" +" importar els fitxers «.bundle» o «.kpp»." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:86 msgid "Erasing" msgstr "Esborrar" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:88 msgid "" "Erasing is a blending mode in Krita, much like the transparency mode of " "Paint Tool Sai. It's activated with :kbd:`E` or you can select it from the " "Blending Mode drop-down..." msgstr "" +"L'esborrament és un mode de barreja en el Krita, igual que el mode de" +" transparència del Paint Tool Sai. S'activa amb :kbd:`E` o el podeu" +" seleccionar des del menú desplegable «Mode de barreja...»." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:91 msgid "Blending Modes" msgstr "Modes de barreja" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:93 msgid "" "Krita has a lot of Blending modes, and thankfully all of Paint Tool Sai's " "are amongst them except binary. To manage the blending modes, each of them " "has a little check-box that you can tick to add them to the favorites." msgstr "" +"El Krita té molts modes de barreja i, per sort, s'hi troben tots els del" +" Paint Tool Sai, excepte els binaris. Per a gestionar els modes de barreja," +" cadascun d'ells té una casella de selecció que podeu marcar per afegir-los" +" als preferits." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:95 msgid "" "Multiple, Screen, Overlay and Normal are amongst the favorites. Krita's " "Luminosity is actually slightly different from Paint Tool Sai's and it " "replaces the relative brightness of color with the relative brightness of " "the color of the layer." msgstr "" +"Múltiples, Pantalla, Superposició i Normal es troben entre els preferits. La" +" lluminositat del Krita, en realitat és una mica diferent de la del Paint" +" Tool Sai i substitueix la brillantor relativa del color amb la brillantor" +" relativa del color de la capa." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:98 msgid "" "Sai's Luminosity mode is actually the same as Krita's *Addition* or *linear " "dodge* mode. The Shade mode is the same as *Color Burn* and *Hard Mix* is " "the same as the lumi and shade mode." msgstr "" +"El mode de lluminositat del Sai, en realitat és la mateixa que el mode" +" *Addició* o *Esvaïment lineal* del Krita. El mode Ombra és el mateix que el" +" *Cremat dels colors* i *Barreja forta* és el mateix que el mode Luminància i" +" Ombra." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:101 msgid "Layers" msgstr "Capes" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:103 msgid "Lock Alpha" -msgstr "" +msgstr "Bloqueja l'alfa" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:104 msgid "This is the checker box icon next to every layer." msgstr "" "Aquesta és la icona del quadre de selecció que hi ha al costat de cada capa." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:105 msgid "Clipping group" msgstr "Grup de retall" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:106 msgid "" "For Clipping masks in Krita you'll need to put all your images in a single " "layer, and then press the 'a' icon, or press :kbd:`Ctrl + Shift + G`" msgstr "" +"Per a les màscares de retallada en el Krita, haureu de col·locar totes les" +" vostres imatges en una sola capa i després prémer la icona «a» o prémer la" +" drecera :kbd:`Ctrl + Majús. + G`." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:107 msgid "Ink layer" msgstr "Capa de tintura" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:108 msgid "This is a vector layer in Krita, and also holds the text." msgstr "Aquesta és una capa vectorial al Krita, i també conté el text." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:109 msgid "Masks" msgstr "Màscares" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:110 msgid "" "These grayscale layers that allow you to affect the transparency are called " "transparency masks in Krita, and like Paint Tool Sai, they can be applied to " "groups as well as layers. If you have a selection and make a transparency " "mask, it will use the selection as a base." msgstr "" +"Aquestes capes amb escala de grisos que permeten afectar la transparència," +" s’anomenen màscares de transparència en el Krita i, com al Paint Tool Sai," +" es poden aplicar tant a grups com a capes. Si teniu una selecció i feu una" +" màscara de transparència, s'utilitzarà la selecció com a base." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:112 msgid "Clearing a layer" -msgstr "Esborrar una capa" +msgstr "Netejar una capa" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:112 msgid "" "This is under :menuselection:`Edit --> Clear`, but you can also just press :" "kbd:`Del`." msgstr "" +"Això està sota :menuselection:`Edita -> Neteja`, però també podeu prémer la" +" drecera :kbd:`Supr.`." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:115 msgid "Mixing between two colors" msgstr "Barrejar entre dos colors" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:117 msgid "" "If you liked this docker in Paint Tool Sai, Krita's Digital Color Selector " "docker will be able to help you. Dragging the sliders will change how much " "of a color is mixed in." msgstr "" +"Si us ha agradat aquest acoblador al Paint Tool Sai, l'acoblador Selector de" +" color digital del Krita us ajudarà. Arrossegar els controls lliscants" +" canviarà la quantitat de color que es barreja." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:120 msgid "What do you get extra when using Krita?" msgstr "Què obtindreu de més quan empreu el Krita?" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:123 msgid "More brush customization" msgstr "Més personalització del pinzell" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:125 msgid "" "You already met the brush settings editor. Sketch brushes, grid brushes, " "deform brushes, clone brushes, brushes that are textures, brushes that " "respond to tilt, rotation, speed, brushes that draw hatches and brushes that " "deform the colors. Krita's variety is quite big." msgstr "" +"Ja heu conegut l’editor dels ajustaments del pinzell. Els pinzells d'esbós," +" els pinzells de reixa, Pinzells de deformació, pinzells de clonat, pinzells" +" que són textures, pinzells que responen a la inclinació, rotació, velocitat," +" pinzells que dibuixen escotilles i pinzells que deformen els colors. La" +" varietat al Krita és molt gran." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:128 msgid "More color selectors" msgstr "Més selectors de color" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:130 msgid "" "You can have HSV sliders, RGB sliders, triangle in a hue ring. But you can " "also have HSI, HSL or HSY' sliders, CMYK sliders, palettes, round selectors, " "square selectors, tiny selectors, big selectors, color history and shade " "selectors. Just go into :menuselection:`Settings --> Configure Krita --> " "Advanced Color Selector Settings` to change the shape and type of the main " "big color selector." msgstr "" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:135 msgid "" "You can call the color history with :kbd:`H`, common colors with :kbd:`U` " "and the two shade selectors with :kbd:`Shift + N` and :kbd:`Shift + M`. The " "big selector can be called with :kbd:`Shift + I` on canvas." msgstr "" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:138 msgid "Geometric Tools" msgstr "Eines geomètriques" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:140 msgid "Circles, rectangles, paths, Krita allows you to draw these easily." msgstr "" "Cercles, rectangles, trajectes, el Krita permet dibuixar-los amb facilitat." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:143 msgid "Multibrush, Mirror Symmetry and Wrap Around" msgstr "" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:145 msgid "" "These tools allow you to quickly paint a mirrored image, mandala or tiled " "texture in no time. Useful for backgrounds and abstract vignettes." msgstr "" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:151 msgid "Assistants" msgstr "Assistents" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:153 msgid "" "The painting assistants can help you to set up a perspective, or a " "concentric circle and snap to them with the brush." msgstr "" "Els assistents de pintura poden ajudar-vos a configurar una perspectiva, o " "un cercle concèntric i enganxar-los amb el pinzell." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:159 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 del punt de fuga del Krita en acció" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:159 msgid "Krita's vanishing point assistants in action" msgstr "Assistents del punt de fuga del Krita en acció." #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:162 msgid "Locking the Layer" msgstr "Bloquejar la capa" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:164 msgid "Lock the layer with the padlock so you don't draw on it." msgstr "" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:167 msgid "Quick Layer select" msgstr "" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:169 msgid "" "If you hold :kbd:`R` and press a spot on your drawing, Krita will select the " "layer underneath the cursor. Really useful when dealing with a large number " "of layers." msgstr "" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:172 msgid "Color Management" msgstr "Gestió del color" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:174 msgid "" "This allows you to prepare your work for print, or to do tricks with the LUT " "docker so you can diagnose your image better. For example, using the LUT " "docker to turn the colors grayscale in a separate view, so you can see the " "values instantly." msgstr "" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:180 msgid "Advanced Transform Tools" msgstr "Eines avançades de transformació" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:182 msgid "" "Not just rotate and scale, but also cage, wrap, liquify and non-destructive " "transforms with the transform tool and masks." msgstr "" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:188 msgid "More Filters and non-destructive filter layers and masks" msgstr "" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:190 msgid "" "With filters like color balance and curves you can make easy shadow layers. " "In fact, with the filter layers and layer masks you can make them apply on " "the fly as you draw underneath." msgstr "" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:196 msgid "Pop-up palette" msgstr "Paleta emergent" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:198 msgid "" "This is the little circular thing that is by default on the right click. You " "can organize your brushes in tags, and use those tags to fill up the pop-up " "palette. It also keeps a little color selector and color history, so you can " "switch brushes on the fly." msgstr "" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:204 msgid "What does Krita lack compared to Paint Tool Sai?" msgstr "Què falta en el Krita en comparació amb el Paint Tool Sai?" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:206 msgid "Variable width vector lines" msgstr "" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:207 msgid "The selection source option for layers" msgstr "" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:208 msgid "Dynamic hard-edges for strokes (the fringe effect)" msgstr "" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:209 msgid "No mix-docker." msgstr "" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:210 msgid "No Preset-tied stabilizer." msgstr "" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:211 msgid "No per-preset hotkeys." msgstr "" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:214 msgid "Conclusion" msgstr "Conclusió" #: ../../user_manual/introduction_from_other_software/introduction_from_sai.rst:216 msgid "" "I hope this introduction got you a little more excited to use Krita, if not " "feel a little more at home." msgstr "" "Espero que aquesta introducció us hagi entusiasmat una mica més per emprar " "el Krita, de no ser així, que us trobeu una mica més a casa." 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 7c6173b3d..2fef43d06 100644 --- a/locale/ca/LC_MESSAGES/user_manual/loading_saving_brushes.po +++ b/locale/ca/LC_MESSAGES/user_manual/loading_saving_brushes.po @@ -1,949 +1,949 @@ # 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: docs_krita_org_user_manual___loading_saving_brushes\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-03-12 03:34+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-03-12 17:07+0100\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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:37 msgid "The Brush settings dropdown" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:44 msgid "" "When you open Brush Settings Editor panel you will see something like this:" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:48 msgid "Tour of the brush settings dropdown" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:53 msgid "The brush settings drop down is divided into six areas," msgstr "" #: ../../user_manual/loading_saving_brushes.rst:56 msgid "Section A - General Information" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:101 msgid "Saving a preset" msgstr "Desar un valor predefinit" #: ../../user_manual/loading_saving_brushes.rst:103 msgid "" "On the right, there's :guilabel:`Save New Brush Preset` and :guilabel:" "`Overwrite Brush`." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:113 msgid "Save New Brush Preset" msgstr "Desa el valor predefinit nou del pinzell" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 les miniatures existents" #: ../../user_manual/loading_saving_brushes.rst:128 msgid "This will load the existing thumbnail inside the preset." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:130 msgid "Load scratch pad thumbnail" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:137 msgid "Clear Thumbnail" msgstr "Neteja les miniatures" #: ../../user_manual/loading_saving_brushes.rst:137 msgid "This will make the mini scratch pad white." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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, ad the lowest slider is a super simple levels filter. " +"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 "" #: ../../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." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:167 msgid "Section B - The Preset Chooser" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:169 msgid "" "The preset chooser is much the same as the preset docker and the preset " "dropdown 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 "" #: ../../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 "" #: ../../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 "" #: ../../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 for that " -"engine." +"list of Krita's engines. Selecting an engine from the list will show the " +"brushes for that engine." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:185 msgid "" -"The trashcan icon does the same as it does in the preset docker: delete , or " +"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 "" #: ../../user_manual/loading_saving_brushes.rst:189 msgid "Section C - The Scratch pad" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:202 msgid "The scratch pad has five buttons underneath it. These are in order for:" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:204 msgid "Showing the current brush image" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:206 msgid "Adding a gradient to the scratch pad (useful for smudge brushes)" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:207 msgid "Filling with the background color" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:208 msgid "Clearing everything on the scratch pad." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:211 msgid "Section D - The Options List" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:227 msgid "Section E - Option Configuration Widget" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:233 msgid "Using sensor curves" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:260 msgid "Underneath the curve widget there are two more options:" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:283 msgid "Will subtract the smallest value from the largest, so 0.7-0.5 = 0.2" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:292 msgid "Is a brush with size set to the distance sensor." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:293 msgid "Is a brush with the size set to the fade sensor." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:294 msgid "The size is calculated from the fade and distance sensors multiplied." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:297 msgid "" "The size takes the maximum value from the values of the fade and distance " "sensors." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:299 msgid "" -"The size takes the minimum value from the values of the face and distance " +"The size takes the minimum value from the values of the fade and distance " "sensors." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:305 msgid "Section F - Miscellaneous options" msgstr "" #: ../../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, the revert to default. " "Dirtied presets can be recognized by the icon in the top-left of the preset." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:316 msgid "Temporarily Save Tweaks to Preset (Dirty Presets)" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:347 msgid "Making a Brush Preset" msgstr "Crear un valor predefinit del pinzell" #: ../../user_manual/loading_saving_brushes.rst:349 msgid "Now, let's make a simple brush to test the waters with:" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:352 msgid "Getting a default for the brush engine." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:354 msgid "First, open the settings with :kbd:`F5`." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:361 msgid "Example: Making an inking brush" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:370 -msgid "Uncheck the :guilabel:`enable pen settings` checkbox." +msgid "Uncheck the :guilabel:`Enable Pen Settings` checkbox." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:377 msgid "" -"Uncheck the :guilabel:`enable pen settings` checkbox here as well. Test " +"Uncheck the :guilabel:`Enable Pen Settings` checkbox here as well. Test " "again." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:401 msgid "Saving the new Brush" msgstr "Desar el pinzell nou" #: ../../user_manual/loading_saving_brushes.rst:403 msgid "" "When you're satisfied, go to the upper left and select :guilabel::`Save new " "preset`." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:414 msgid "Finally press :guilabel:`Save`, and your brush should be done." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:416 msgid "You can further modify your inking brush by..." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:422 msgid "Making the fine lines look even softer by using the flow option." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:422 msgid "" "To do this, select the flow option, and turn back on the 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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:438 msgid "Sharing a single preset" msgstr "Compartir un sol valor predefinit" #: ../../user_manual/loading_saving_brushes.rst:440 msgid "There are three types of resources a single preset can take:" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:446 msgid "A Pattern file: this is when you are using textures." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:452 msgid "" "To find those resources, go to :menuselection:`Settings --> Manage Resources " "--> Open Resource Folder`." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:458 msgid "Importing a single KPP file." msgstr "" #: ../../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 "" #: ../../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 " "dropdown (: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 "" #: ../../user_manual/loading_saving_brushes.rst:471 msgid "Sharing via ZIP (old-fashioned)" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:477 msgid "Using a ZIP with the relevant files." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:479 msgid "" "Go to :menuselection:`Settings --> Manage Resources --> Open Resource " "Folder` to open the resource folder." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:480 msgid "Then, open up the zip file." msgstr "" #: ../../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 "" #: ../../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/oncanvas_brush_editor.po b/locale/ca/LC_MESSAGES/user_manual/oncanvas_brush_editor.po index 77272265a..6a8035377 100644 --- a/locale/ca/LC_MESSAGES/user_manual/oncanvas_brush_editor.po +++ b/locale/ca/LC_MESSAGES/user_manual/oncanvas_brush_editor.po @@ -1,84 +1,84 @@ # Translation of docs_krita_org_user_manual___oncanvas_brush_editor.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: docs_krita_org_user_manual___oncanvas_brush_editor\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-03-08 03:41+0100\n" -"PO-Revision-Date: 2019-03-12 10:10+0100\n" +"PO-Revision-Date: 2019-03-14 23:11+0100\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/oncanvas_brush_editor.rst:1 msgid "Using the oncanvas brush editor in Krita." msgstr "Utilitzant l'editor de pinzells en el llenç en el Krita." #: ../../user_manual/oncanvas_brush_editor.rst:16 msgid "On-Canvas Brush Editor" msgstr "Editor de pinzells en el llenç" #: ../../user_manual/oncanvas_brush_editor.rst:19 msgid "" "Krita's brush editor is, as you may know, on :kbd:`F5`. However, sometimes " "you just want to modify a single parameter quickly. Perhaps even in canvas-" "only mode. The on canvas brush editor or brush HUD allows you to do this. " "It's accessible from the pop-up palette, by ticking the lower-right arrow " "button." msgstr "" "L'editor de pinzells del Krita està, com sabreu, al :kbd:`F5`. No obstant " "això, de vegades només voleu modificar un únic paràmetre amb rapidesa. " "Potser fins i tot només en el mode llenç. L'editor de pinzells del llenç o " "HUD, permet fer-ho possible. Es pot accedir des de la paleta emergent, fent " "clic al botó de fletxa dreta que hi ha a la part inferior." #: ../../user_manual/oncanvas_brush_editor.rst:26 msgid ".. image:: images/en/On_canvas_brush_editor.png" msgstr ".. image:: images/en/On_canvas_brush_editor.png" #: ../../user_manual/oncanvas_brush_editor.rst:27 msgid "" "You can change the amount of visible settings and their order by clicking " "the settings icon next to the brush name." msgstr "" "Podeu canviar la quantitat d'ajustaments visibles i el seu ordre fent clic a " "la icona d'ajustaments que hi ha al costat del nom del pinzell." #: ../../user_manual/oncanvas_brush_editor.rst:31 msgid ".. image:: images/en/On_canvas_brush_editor_2.png" msgstr ".. image:: images/en/On_canvas_brush_editor_2.png" #: ../../user_manual/oncanvas_brush_editor.rst:32 msgid "" "On the left are all unused settings, on the right are all used settings. You " "use the :guilabel:`>` and :guilabel:`<` buttons to move a setting between " "the two columns. The :guilabel:`Up` and :guilabel:`Down` buttons allow you " "to adjust the order of the used settings, for when you think flow is more " "important than size." msgstr "" "A l'esquerra hi ha tots els ajustaments no utilitzats, al costat dret hi ha " "tots els ajustaments utilitzats. Utilitzeu els botons :guilabel:`>` i :" "guilabel:`<` per a moure un ajustament entre les dues columnes. Els botons :" "guilabel:`Amunt` i :guilabel:`Avall` permeten ajustar l'ordre dels " "ajustaments emprats, ja que com penseu, el flux és més important que la mida." #: ../../user_manual/oncanvas_brush_editor.rst:38 msgid ".. image:: images/en/On_canvas_brush_editor_3.png" msgstr ".. image:: images/en/On_canvas_brush_editor_3.png" #: ../../user_manual/oncanvas_brush_editor.rst:39 msgid "" "These set-ups are PER brush engine, so different brush engines can have " "different configurations." msgstr "" -"Aquests ajustaments són per al motor del pinzell, de manera que els " -"diferents motors de pinzell poden tenir configuracions diferents." +"Aquests ajustaments són per al motor de pinzells, de manera que els " +"diferents motors de pinzells podran tenir configuracions diferents." diff --git a/locale/ca/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po b/locale/ca/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po index b7346199e..402004c26 100644 --- a/locale/ca/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po +++ b/locale/ca/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po @@ -1,289 +1,289 @@ # Translation of docs_krita_org_user_manual___python_scripting___introduction_to_python_scripting.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: " "docs_krita_org_user_manual___python_scripting___introduction_to_python_scripting\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-03-06 03:37+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-03-11 10:14+0100\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/python_scripting/introduction_to_python_scripting.rst:1 msgid "Introduction to using Krita's python plugin API." msgstr "Introducció a l'ús de l'API del Krita per a connectors en Python." #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:18 msgid "Introduction to Python Scripting" msgstr "Introducció a la creació de scripts en Python" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:22 msgid "" "When we offered python scripting as one of Kickstarter Stretchgoals we could " "implement next to vectors and text, it won the backer vote by a landslide. " "Some people even only picked python and nothing else. So what exactly is " "python scripting?" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:25 msgid "What is Python Scripting?" msgstr "Què és la creació de scripts en Python?" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:27 msgid "" "Python is a scripting language, that can be used to automate tasks. What " "python scripting in Krita means is that we added an API to krita, which is a " "bit of programming that allows python to access to parts of Krita. With this " "we can make dockers, perform menial tasks on a lot of different files and " "even write our own exporters. People who work with computer graphics, like " "VFX and video game artists use python a lot to make things like sprite " "sheets, automate parts of export and more." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:29 msgid "" "It is outside the scope of this manual to teach you python itself. However, " "as python is an extremely popular programming language and great for " "beginners, there's tons of learning material around that can be quickly " "found with a simple 'learn python' internet search." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:31 msgid "" "This manual will instead focus on how to use python to automate and extend " "Krita. For that we'll first start with the basics: How to run Python " "commands in the scripter." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:35 msgid "How to Enable the Scripter Plugin" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:37 msgid "" "The scripter plugin is not necessary to use python, but it is very useful " "for testing and playing around with python. It is a python console, written " "in python, which can be used to write small scripts and execute them on the " "fly." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:39 msgid "" "To open the scripter, navigate to :menuselection:`Tools --> Scripts --> " "Scripter`. If you don't see it listed, go to :menuselection:`Settings --> " "Configure Krita --> Python Plugin Manager` and toggle \"Scripter\" in the " "list to enable it. If you don't see the scripter plugin, make sure you are " "using an up-to-date version of Krita." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:41 msgid "" "The scripter will pop up with a text editor window on top and an output " "window below. Input the following in the text area:" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:48 msgid "" "Press the big play button or press :kbd:`Ctrl + R` to run the script. Then, " "below, in the output area the following should show up::" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:53 msgid "" "Now we have a console that can run functions like print() from the Python " "environment - but how do we use it to manage Krita?" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:56 msgid "Running basic Krita commands" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:58 msgid "" "To allow Python to communicate with Krita, we will use the Krita module. At " "the top of every script, we will write: ``from krita import *``" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:60 msgid "" "This allows us to talk to Krita through ``Krita.instance()``. Let's try to " "double our coding abilities with Python." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:68 msgid "" "You should see a second scripter window open. Pretty neat! Here is a " "slightly more advanced example." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:77 msgid "" "This will open up a new document. Clearly Python gives you quite a lot of " "control to automate Krita. Over time we expect the community to write all " "kinds of scripts that you can use simply by pasting them in the scripter." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:79 msgid "" "But what if you want to write new commands for yourself? The best place to " "start is very simple: search for examples written by other people! You can " "save a lot of time if someone else has written code that you can base your " "work on. It's also worth looking through the python plugins, which are " "located in /share/krita/pykrita. There's also a step by step guide for :ref:" "`krita_python_plugin_howto` here in the manual." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:81 msgid "" "But it's likely that you need more information. For that, we will need see " "what's hidden behind the asterisk when you ``import * from Krita``. To learn " "what Krita functions that are available and how to use them, you will want " "to go for Krita API reference documentation." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:84 msgid "Krita's API" msgstr "API del Krita" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:86 msgid "" "`LibKis API Overview `_" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:87 msgid "" "`Krita class documentation `_" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:89 msgid "" "Those pages may look like a lot of jargon at first. This is because Krita's " "API documentation comes from the underlying C++ language that Krita is " "written in. The magic happens because of a Python tool called SIP, which " "makes it possible for python speak in C++ and talk to Krita. The end result " "is that when we ``import krita`` and call functions, we're actually using " "the C++ methods listed in that documentation." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:91 msgid "" "Let's see how this stuff works in more detail. Let's take a look at the " "second link, the `Krita class reference `_. There we can see all the " "functions available to the Krita instance. If you type dir(Krita.instance()) " "in Python, it should match this page very closely - you can view the " "documentation of the functions createDocument(), activeWindow(), and " "action() which we used above." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:93 msgid "" "One of the more confusing things is seeing all the C++ classes that Krita " -"uses, including the Qt classes that start with Q. But here is the beauty fo " +"uses, including the Qt classes that start with Q. But here is the beauty of " "SIP: it tries to make the translation from these classes into Python as " "simple and straightforward as possible. For example, you can see that the " "function filters() returns a QStringList. However, SIP converts those " "QStringLists into regular python list of strings!" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:101 msgid "Outputs as ::" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:112 msgid "However, sometimes the conversion doesn't go quite as smoothly." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:120 msgid "gives something like this::" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:127 msgid "" "It is a list of something, sure, but how to use it? If we go back to the " "Krita apidocs page and look at the function, documents() we'll see there's " "actually a clickable link on the 'Document' class. `If you follow that link " "`_, you'll see that the document has a function called " "name() which returns the name of the document, and functions width() and " "height() which return the dimensions. So if we wanted to generate an info " "report about the documents in Krita, we could write a script like this:" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:137 msgid "we get an output like::" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:147 msgid "" "Hopefully this will give you an idea of how to navigate the API docs now." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:149 msgid "" "Krita's API has many more classes, you can get to them by going to the top-" "left class list, or just clicking their names to get to their API docs. The " "functions print() or dir() are your friends here as well. This line will " "print out a list of all the actions in Krita - you could swap in one of " "these commands instead of 'python_scripter' in the example above." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:155 msgid "" "The Python module ``inspect`` was designed for this sort of task. Here's a " "useful function to print info about a class to the console." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:167 msgid "" "Finally, in addition to the LibKis documentation, the Qt documentation, " "since Krita uses PyQt to expose nearly all of the Qt API to Python. You can " "build entire windows with buttons and forms this way, using the very same " "tools that Krita is using! You can read the `Qt documentation `_ and the `PyQt documentation `_ for more info about this, and also definitely study the included plugins " "as well to see how they work." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:171 msgid "Technical Details" msgstr "Detalls tècnics" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:177 msgid "Python Scripting on Windows" msgstr "Creació de scripts en Python a Windows" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:179 msgid "" "To get Python scripting working on Windows 7/8/8.1, you will need to install " "the `Universal C Runtime from Microsoft's website `_. (Windows 10 already comes with it.)" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:182 msgid "Python 2 and 3" msgstr "Python 2 i 3" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:184 msgid "By default Krita is compiled for python 3." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:186 msgid "" "However, it is possible to compile it with python 2. To do so, you will need " "to add the following to the cmake configuration line::" msgstr "" 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 7e387f52a..e9ecbd519 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-03-12 03:34+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\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 it's 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 775c1bcf7..f52d2ad03 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,1063 +1,1063 @@ # 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-03-13 03:40+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\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 colour " "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 colour." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:71 msgid "" "Finally, group 4 has Vermillion red, citron yellow and cerulean blue. Their " "colours 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 colour 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 " "colour translate properly between color devices." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:82 msgid "" "It usually works by attempting to covert a colour to the reference colour " "space XYZ. XYZ is a coordinate system that has a spot for all colours 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 colour 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:88 msgid "" "To give a crude estimate, ICC profiles deal with keeping colours consistent " "over many interpretations of devices (screens, printers) by using a " "reference space, and OCIO deals with manipulating the interpretation of said " "colours." 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 grey it produces. Using " "these and several other measurements it creates an icc profile unique to " "your screen. You set these in Krita's colour 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 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-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.)" msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:148 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 colour 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 colorspace 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 colour reproduction. Use this if you want to " "see all colours 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 colours at whatever cost, which may result in awful looking " "colours. 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 "" "A in between solution between perceptual and absolute, relative will try to " "fit whatever colours it can match between colour 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 colourfulness, 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 '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." 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 colour 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 colour 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 colour 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 " "customly 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 colour maths, often concerning the blending of colours. " "This colour maths works best in linear colour space, and linear colour 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 colour 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 " "colour 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's 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 colours actually look strange: This is a " "bug in Firefox, which is because its `color management system is incomplete " "`_, save your png, jpg or tiff without an embedded profile to work " "around this." 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 " "bitdepth 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 specialised 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, mypaint, mangastudio, 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, mangastudio " "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 optimisers. 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 "" "Specialised 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 --> 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." 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 optimised content, and it's recommended to " "stay within 8bit, future screens may have higher bitdepths, 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 optimise 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 "" "`Visualising the XYZ colorspace `_" 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 colormanagement 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 91be12b44..e5674a58d 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-03-12 03:34+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\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 it's 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 6ecf55393..51b5d3ec3 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,1062 +1,1062 @@ msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-03-13 03:40+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\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 colour " "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 colour." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:71 msgid "" "Finally, group 4 has Vermillion red, citron yellow and cerulean blue. Their " "colours 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 colour 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 " "colour translate properly between color devices." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:82 msgid "" "It usually works by attempting to covert a colour to the reference colour " "space XYZ. XYZ is a coordinate system that has a spot for all colours 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 colour 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:88 msgid "" "To give a crude estimate, ICC profiles deal with keeping colours consistent " "over many interpretations of devices (screens, printers) by using a " "reference space, and OCIO deals with manipulating the interpretation of said " "colours." 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 grey it produces. Using " "these and several other measurements it creates an icc profile unique to " "your screen. You set these in Krita's colour 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 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-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.)" 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 colour 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 colorspace 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 colour reproduction. Use this if you want to " "see all colours 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 colours at whatever cost, which may result in awful looking " "colours. 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 "" "A in between solution between perceptual and absolute, relative will try to " "fit whatever colours it can match between colour 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 colourfulness, 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 '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." 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 colour 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 colour 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 colour 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 " "customly 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 colour maths, often concerning the blending of colours. " "This colour maths works best in linear colour space, and linear colour 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 colour 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 " "colour 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's 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 colours actually look strange: This is a " "bug in Firefox, which is because its `color management system is incomplete " "`_, save your png, jpg or tiff without an embedded profile to work " "around this." 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 " "bitdepth 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 specialised 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, mypaint, mangastudio, 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, mangastudio " "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 optimisers. 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 "" "Specialised 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 --> 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." 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 optimised content, and it's recommended to " "stay within 8bit, future screens may have higher bitdepths, 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 optimise 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 "" "`Visualising the XYZ colorspace `_" 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 colormanagement from argylcms manual `_" msgstr "" diff --git a/locale/fr/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po b/locale/fr/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po index a889da906..d0710ef60 100644 --- a/locale/fr/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po +++ b/locale/fr/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po @@ -1,212 +1,212 @@ msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-02-23 03:24+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-02-27 01:18+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" #: ../../:1 msgid "Use Undeformed Image" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:1 msgid "The Deform Brush Engine manual page." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:16 msgid "Deform Brush Engine" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:19 msgid ".. image:: images/icons/deformbrush.svg" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:20 msgid "" "The Deform Brush is a brush that allows you to pull and push pixels around. " "It's quite similar to the :ref:`liquify_mode`, but where liquify has higher " "quality, the deform brush has the speed." msgstr "" # #-#-#-#-# ktorrent.po (ktorrent) #-#-#-#-# # # HERE ENDS asmanur WORK AND BEGINS Metzgermeister WORK #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:24 msgid "Options" msgstr "Options" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:26 msgid ":ref:`option_brush_tip`" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:27 msgid ":ref:`option_deform`" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:28 msgid ":ref:`blending_modes`" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:29 msgid ":ref:`option_opacity_n_flow`" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:30 msgid ":ref:`option_size`" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:31 msgid ":ref:`option_rotation`" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:32 msgid ":ref:`option_airbrush`" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:38 msgid "Deform Options" msgstr "Options de déformation" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:42 msgid ".. image:: images/en/Krita_deform_brush_examples.png" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:42 msgid "" "1: undeformed, 2: Move, 3: Grow, 4: Shrink, 5: Swirl Counter Clock Wise, 6: " "Swirl Clockwise, 7: Lens Zoom In, 8: Lens Zoom Out" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:44 msgid "These decide what strangeness may happen underneath your brush cursor." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:46 msgid "Grow" msgstr "Agrandir" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:47 msgid "This bubbles up the area underneath the brush-cursor." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:48 msgid "Shrink" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:49 msgid "This pinches the Area underneath the brush-cursor." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:50 msgid "Swirl Counter Clock Wise" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:51 msgid "Swirls the area counter clock wise." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:52 msgid "Swirl Clock Wise" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:53 msgid "Swirls the area clockwise." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:54 msgid "Move" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:55 msgid "Nudges the area to the painting direction." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:56 msgid "Color Deformation" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:57 -msgid "This seems to randomly rearrange the pixels underneath the brush," +msgid "This seems to randomly rearrange the pixels underneath the brush." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:58 msgid "Lens Zoom In" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:59 msgid "Literally paints a enlarged version of the area." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:61 msgid "Lens Zoom Out" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:61 msgid "Paints a minimized version of the area." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:65 msgid ".. image:: images/en/Krita_deform_brush_colordeform.png" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:65 msgid "Showing color deform." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:68 msgid "Deform Amount" msgstr "Quantité de déformation" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:68 msgid "Defines the strength of the deformation." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:72 msgid ".. image:: images/en/Krita_deform_brush_bilinear.png" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:72 #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:74 msgid "Bilinear Interpolation" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:75 msgid "Smoothens the result. This causes calculation errors in 16bit." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:77 msgid "Use Counter" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:77 msgid "Slows down the deformation subtlety." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:81 msgid ".. image:: images/en/Krita_deform_brush_useundeformed.png" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:81 msgid "Without 'use undeformed' to the left and with to the right" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:84 msgid "" "Samples from the previous version of the image instead of the current. This " "works better with some deform options than others. Move for example seems to " "almost stop working, but it works really well with Grow." msgstr "" diff --git a/locale/fr/LC_MESSAGES/reference_manual/layers_and_masks/layer_styles.po b/locale/fr/LC_MESSAGES/reference_manual/layers_and_masks/layer_styles.po index b83239482..efc7adef1 100644 --- a/locale/fr/LC_MESSAGES/reference_manual/layers_and_masks/layer_styles.po +++ b/locale/fr/LC_MESSAGES/reference_manual/layers_and_masks/layer_styles.po @@ -1,56 +1,56 @@ 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" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-02-27 02:53+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" #: ../../reference_manual/layers_and_masks/layer_styles.rst:1 msgid "How to use layer styles in Krita." msgstr "" #: ../../reference_manual/layers_and_masks/layer_styles.rst:17 msgid "Layer Styles" msgstr "Styles du calque" #: ../../reference_manual/layers_and_masks/layer_styles.rst:19 msgid "" "Layer styles are effects that are added on top of your layer. They are " "editable and can easily be toggled on and off. To add a layer style to a " "layer go to :menuselection:`Layer --> Layer Style`. You can also right-click " "a layer to access the layer styles." msgstr "" #: ../../reference_manual/layers_and_masks/layer_styles.rst:22 msgid "" -"When you have the layer styles window up, make sure that the \"Enable Effects" -"\" is checked." +"When you have the layer styles window up, make sure that the :guilabel:" +"`Enable Effects` item is checked." msgstr "" #: ../../reference_manual/layers_and_masks/layer_styles.rst:24 msgid "" "There are a variety of effects and styles you can apply to a layer. When you " "add a style, your layer docker will show an extra \"Fx\" icon. This allows " "you to toggle the layer style effects on and off." msgstr "" #: ../../reference_manual/layers_and_masks/layer_styles.rst:30 msgid "" "This feature was added to increase support for :program:`Adobe Photoshop`. " "The features that are included mirror what that application supports." msgstr "" diff --git a/locale/fr/LC_MESSAGES/reference_manual/render_animation.po b/locale/fr/LC_MESSAGES/reference_manual/render_animation.po index baed74288..cce63211e 100644 --- a/locale/fr/LC_MESSAGES/reference_manual/render_animation.po +++ b/locale/fr/LC_MESSAGES/reference_manual/render_animation.po @@ -1,304 +1,304 @@ msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-02-25 03:36+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-02-27 03:15+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" #: ../../reference_manual/render_animation.rst:1 msgid "How to use the render animation command in Krita." msgstr "" #: ../../reference_manual/render_animation.rst:17 #: ../../reference_manual/render_animation.rst:42 msgid "Render Animation" msgstr "Rendu de l'animation" #: ../../reference_manual/render_animation.rst:19 msgid "" "Render animation allows you to render your animation to an image sequence, " "gif, mp4, mkv, or ogg file. It replaces :guilabel:`Export Animation` ." msgstr "" #: ../../reference_manual/render_animation.rst:21 msgid "" "For rendering to an animated fileformat, Krita will first render to a png " "sequence and then use FFMpeg, which is really good at encoding into video " "files, to render that sequence to an animated fileformat. The reason for " "this two-step process is that animation files can be really complex and " "really big, and this is the best way to allow you to keep control over the " "export process. For example, if your computer has a hiccup, and one frame " "saves out weird, first saving the image sequence allows you to only resave " "that one weird frame before rendering." msgstr "" #: ../../reference_manual/render_animation.rst:23 msgid "" "This means that you will need to find a good place to stick your frames " "before you can start rendering. If you only do throwaway animations, you can " "use a spot on your hard-drive with enough room and select :guilabel:`Delete " "Sequence After Rendering`" msgstr "" #: ../../reference_manual/render_animation.rst:26 msgid "Image Sequence" msgstr "" #: ../../reference_manual/render_animation.rst:28 msgid "Base Name" msgstr "" #: ../../reference_manual/render_animation.rst:29 msgid "" "The base name of your image sequence. This will get suffixed with a number " "depending on the frame." msgstr "" #: ../../reference_manual/render_animation.rst:30 msgid "File Format" msgstr "Format de fichier" #: ../../reference_manual/render_animation.rst:31 msgid "" "The fileformat to export the sequence to. When rendering we enforce png. The " "usual export options can be modified with :guilabel:`...`." msgstr "" #: ../../reference_manual/render_animation.rst:32 msgid "Render Location" msgstr "" #: ../../reference_manual/render_animation.rst:33 msgid "" "Where you render the image sequence to. Some people prefer to use a flash-" "drive or perhaps a harddrive that is fast." msgstr "" #: ../../reference_manual/render_animation.rst:34 msgid "First Frame" msgstr "Première image" #: ../../reference_manual/render_animation.rst:35 msgid "" "The first frame of the range of frame you wish to adjust. Automatically set " "to the first frame of your current selection in the timeline. This is useful " "when you only want to re-render a little part." msgstr "" #: ../../reference_manual/render_animation.rst:36 msgid "Last Frame" msgstr "Dernière image" #: ../../reference_manual/render_animation.rst:37 msgid "" "As above, the last frame of the range of frame you wish to adjust. " "Automatically set to the last frame of your current selection in the " "timeline." msgstr "" #: ../../reference_manual/render_animation.rst:39 msgid "Naming Sequence starts with" msgstr "" #: ../../reference_manual/render_animation.rst:39 msgid "" "The frames are named by using :guilabel:`Base Name` above and adding a " "number for the frame. This allows you to set where the frame number starts, " "so rendering from 8 to 10 with starting point 3 will give you images named " "11 and 15. Useful for programs that don't understand sequences starting with " "0, or for precision output." msgstr "" #: ../../reference_manual/render_animation.rst:44 msgid "Render As" msgstr "" #: ../../reference_manual/render_animation.rst:45 msgid "" "The file format to render to. All except gif have extra options that can be " "manipulated via :guilabel:`...`." msgstr "" #: ../../reference_manual/render_animation.rst:46 msgid "File" msgstr "Fichier" #: ../../reference_manual/render_animation.rst:47 msgid "Location and name of the rendered animation." msgstr "" #: ../../reference_manual/render_animation.rst:48 msgid "FFMpeg" msgstr "FFMpeg" #: ../../reference_manual/render_animation.rst:49 msgid "" "The location where your have ffmpeg. If you don't have this, Krita cannot " "render an animation. For proper gif support, you will need ffmpeg 2.6, as we " "use its palettegen functionality." msgstr "" #: ../../reference_manual/render_animation.rst:51 msgid "Delete Sequence After Rendering" msgstr "" #: ../../reference_manual/render_animation.rst:51 msgid "" "Delete the prerendered image sequence after done rendering. This allows you " "to choose whether to try and save some space, or to save the sequence for " "when encoding fails." msgstr "" #: ../../reference_manual/render_animation.rst:55 msgid "" "None of the video formats support saving from images with a transparent " "background, so Krita will try to fill it with something. You should add a " "background color yourself to avoid it from using, say, black." msgstr "" #: ../../reference_manual/render_animation.rst:58 msgid "Setting Up Krita for Exporting Animations" msgstr "" #: ../../reference_manual/render_animation.rst:60 msgid "" "You will need to download an extra application and link it in Krita for it " "to work. The application is pretty big (50MB), so the Krita developers " "didn't want to bundle it with the normal application. The software that we " "will use is free and called FFMpeg. The following instructions will explain " "how to get it and set it up. The setup is a one-time thing so you won't have " "to do it again." msgstr "" #: ../../reference_manual/render_animation.rst:63 msgid "Step 1 - Downloading FFMpeg" msgstr "" #: ../../reference_manual/render_animation.rst:66 #: ../../reference_manual/render_animation.rst:86 msgid "For Windows" msgstr "" #: ../../reference_manual/render_animation.rst:68 msgid "" "Go to the ffmpeg website (http://ffmpeg.org/download.html). The URL that had " "the link for me was here... https://ffmpeg.zeranoe.com/builds/" msgstr "" #: ../../reference_manual/render_animation.rst:70 msgid "" -"Watch out for the extremely annoying google ad that looks like a download " +"Watch out for the extremely annoying google and that looks like a download " "button! There is no big button for what we need. Either get the 64-bit " "STATIC version or 32-bit STATIC version that is shown later down the page. " "If you bought a computer in the past 5 years, you probably want the 64-bit " "version. Make sure you get a exe file, if you hover over the options they " "will give more information about what exactly you are downloading." msgstr "" #: ../../reference_manual/render_animation.rst:73 #: ../../reference_manual/render_animation.rst:93 msgid "For OSX" msgstr "" #: ../../reference_manual/render_animation.rst:75 msgid "" "Please see the section above. However, FFmpeg is obtained from https://" "evermeet.cx/ffmpeg/ instead. Just pick the big green button on the left " "under the FFmpeg heading. You will also need an archiving utility that " "supports .7z, since ffmpeg provides their OSX builds in .7z format. If you " "don't have one, try something like Keka (http://www.kekaosx.com)." msgstr "" #: ../../reference_manual/render_animation.rst:78 #: ../../reference_manual/render_animation.rst:98 msgid "For Linux" msgstr "" #: ../../reference_manual/render_animation.rst:80 msgid "" "FFMPeg can be installed from the repositories on most Linux systems. Version " "2.6 is required for proper gif support, as we use the palettegen " "functionality." msgstr "" #: ../../reference_manual/render_animation.rst:83 msgid "Step 2 - Unzipping and Linking to Krita" msgstr "" #: ../../reference_manual/render_animation.rst:88 msgid "" "Unzip the package that was just downloaded. Rename the long folder name to " "just ffmpeg. Let's put this folder in a easy to find location. go to your C:" "\\ and place it there. You can put it wherever you want, but that is where I " "put it." msgstr "" #: ../../reference_manual/render_animation.rst:90 msgid "" "Open Krita back up and go to :menuselection:`File --> Render Animation`. " "Click the :guilabel:`Browse` button on the last item called FFMpeg. Select " "this file ``C:/ffmpeg/bin/ffmpeg.exe`` and click :guilabel:`OK` ." msgstr "" #: ../../reference_manual/render_animation.rst:95 msgid "" "After downloading ffmpeg, you just need to extract it and then simply point " "to it in the FFMPEG location in Krita like ``/Users/user/Downloads/ffmpeg`` " "(assuming you downloaded and extracted the .7z file to /Users/user/" "Downloads)." msgstr "" #: ../../reference_manual/render_animation.rst:100 msgid "" "FFMpeg is, if installed from the repositories, usually found in ``/usr/bin/" "ffmpeg``" msgstr "" #: ../../reference_manual/render_animation.rst:103 msgid "Step 3 - Testing out an animation" msgstr "" #: ../../reference_manual/render_animation.rst:105 msgid "" "ffmpeg.exe is what Krita uses to do all of its animation export magic. Now " "that it is hooked up, let us test it out." msgstr "" #: ../../reference_manual/render_animation.rst:107 msgid "" "Let's make an animated GIF. in the Render Animation dialog, change the :" "guilabel:`Render As` field to \"GIF image\". Choose the file location where " "it will save with the \"File\" menu below. I just saved it to my desktop and " "called it \"export.gif\". When it is done, you should be able to open it up " "and see the animation." msgstr "" #: ../../reference_manual/render_animation.rst:111 msgid "" "By default, FFMPEG will render MP4 files with a too new codec, which means " "that windows media player won't be able to play it. So for windows, select " "\"baseline\" for the profile instead of \"high422\" before rendering." msgstr "" #: ../../reference_manual/render_animation.rst:115 msgid "" "OSX does not come with any software to play MP4 and MKV files. If you use " "Chrome for your web browser, you can drag the video file into that and the " "video should play. Otherwise you will need to get a program like VLC to see " "the video." msgstr "" diff --git a/locale/fr/LC_MESSAGES/reference_manual/tools/colorize_mask.po b/locale/fr/LC_MESSAGES/reference_manual/tools/colorize_mask.po index e3b5698a2..214a8ecb1 100644 --- a/locale/fr/LC_MESSAGES/reference_manual/tools/colorize_mask.po +++ b/locale/fr/LC_MESSAGES/reference_manual/tools/colorize_mask.po @@ -1,443 +1,443 @@ msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-03-13 03:40+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-02-27 08:00+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 "" #: ../../:8 msgid "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" msgstr "" #: ../../:60 msgid "" ".. image:: images/icons/colorizemask_tool.svg\n" " :alt: toolcolorizemask" msgstr "" -#: ../../reference_manual/tools/colorize_mask.rst:0 -msgid "" -".. image:: images/en/Krita_4_0_colorize_mask_show_output_edit_strokes.png" -msgstr "" - -#: ../../reference_manual/tools/colorize_mask.rst:0 -msgid ".. image:: images/en/Krita_4_0_colorize_mask_edge_detection.png" -msgstr "" - -#: ../../reference_manual/tools/colorize_mask.rst:0 -msgid ".. image:: images/en/Krita_4_0_colorize_mask_gap_close_hint.png" -msgstr "" - -#: ../../reference_manual/tools/colorize_mask.rst:0 -msgid ".. image:: images/en/Krita_4_0_colorize_mask_clean_up.png" -msgstr "" - #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_01.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_02.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_03.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_04.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_05.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_06.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_07.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_08.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_09.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_10.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_11.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_12.png" msgstr "" +#: ../../reference_manual/tools/colorize_mask.rst:0 +msgid "" +".. image:: images/en/Krita_4_0_colorize_mask_show_output_edit_strokes.png" +msgstr "" + +#: ../../reference_manual/tools/colorize_mask.rst:0 +msgid ".. image:: images/en/Krita_4_0_colorize_mask_edge_detection.png" +msgstr "" + +#: ../../reference_manual/tools/colorize_mask.rst:0 +msgid ".. image:: images/en/Krita_4_0_colorize_mask_gap_close_hint.png" +msgstr "" + +#: ../../reference_manual/tools/colorize_mask.rst:0 +msgid ".. image:: images/en/Krita_4_0_colorize_mask_clean_up.png" +msgstr "" + #: ../../reference_manual/tools/colorize_mask.rst:1 msgid "How to use the colorize mask in Krita." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:16 msgid "Colorize Mask" msgstr "Masque de colorisation" #: ../../reference_manual/tools/colorize_mask.rst:18 msgid "|toolcolorizemask|" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:20 msgid "" "A tool for quickly coloring lineart, the Colorize Mask Editing tool can be " "found next to the gradient tool on your toolbox." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:22 msgid "" "This feature is technically already in 3.1, but disabled by default because " "we had not optimised the filling algorithm for production use yet. To enable " "it, find your krita configuration file, open it in notepad, and add " "\"disableColorizeMaskFeature=false\" to the top. Then restart Krita. Its " "official incarnation is in 4.0." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:26 msgid "Usage" msgstr "Utilisation" #: ../../reference_manual/tools/colorize_mask.rst:28 msgid "" "This tool works in conjunction with the colorize mask, and the usage is as " "follows:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:30 msgid "" "For this example, we'll be using the ghost lady also used to explain masks " "on the basic concepts page." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:36 msgid "" "This image has the line art for the lady separated from the background, and " "what's more, the background is made up of two layers: one main and one for " "the details." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:38 msgid "" "First, select the colorize mask editing tool while having the lineart layer " "selected. |mouseleft| the canvas will add a colorize mask to the layer. You " "can also |mouseright| the line art layer, and then :menuselection:`Add --> " "Colorize Mask`. The line art will suddenly become really weird, this is the " "prefiltering which are filters through which we put the lineart to make the " "algorithm easier to use. The tool options overview below shows which options " "control that." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:45 msgid "" "Now, You make strokes with brush colors, press :guilabel:`Update` in the " "tool options, or tick the last icon of the colorize mask properties. In the " "layer docker, you will be able to see a little progress bar appear on the " "colorize mask indicating how long it takes. The bigger your file, the longer " "it will take." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:51 msgid "" "We want to have the blue transparent. In the tool options of the colorize " "editing tool you will see a small palette. These are the colors already " "used. You can remove colors here, or mark a single color as standing for " "transparent, by selecting it and pressing \"transparent\". Updating the mask " "will still show the blue stroke, but the result will be transparent:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:57 msgid "" "Because the colorize mask algorithm is slow, and we only need a part of our " "layer to be filled to fill the whole ghost lady figure, we can make use of :" "guilabel:`Limit to layer bounds`. This will limit Colorize Mask to use the " "combined size of the line art and the coloring key strokes. Therefore, make " "sure that the colorizing keystrokes only take up as much as they really need." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:63 msgid "" "Now the algorithm will be possibly a lot faster, allowing us to add strokes " "and press update in rapid succession:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:69 msgid "" "To see the final result, disable :guilabel:`Edit Key Strokes` or toggle the " "second to last icon on the colorize mask." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:75 msgid "" "If you want to edit the strokes again, re-enable :guilabel:`Edit Key " "Strokes`." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:77 msgid "" "Now, the colorize mask, being a mask, can also be added to a group of line " "art layers. It will then use the composition of the whole group as the line " "art. This is perfect for our background which has two separate line art " "layers. It also means that the colorize mask will be disabled when added to " "a group with pass-through enabled, because those have no final composition. " "You can recognise a disabled colorize mask because its name is stricken " "through." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:79 msgid "" "To add a colorize mask to a group, select the group and |mouseleft| the " "canvas with the Colorize Mask editing tool, or |mouseright| the layer to :" "menuselection:`Add --> Colorize Mask`." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:85 msgid "" "Now, we add strokes to the background quickly. We do not need to use the :" "menuselection:`Limit to Layer Bounds` because the background covers the " "whole image." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:91 msgid "" "For the record, you can use other brushes and tools also work on the " "colorize mask as long as they can draw. The Colorize Mask Editing tool is " "just the most convenient because you can get to the algorithm options." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:93 msgid "Out final result looks like this:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:99 msgid "" "Now we are done, |mouseright| the colorize mask and :menuselection:`Convert " "--> to Paint Layer`. Then, :menuselection:`Layer --> Split --> Split Layer`. " "This will give separate color islands that you can easily edit:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:105 msgid "" "This way we can very quickly paint the image. Due to the colorize mask going " "from the first image to the following took only 30 minutes, and would've " "taken quite a bit longer." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:111 msgid "" "The colorize masks are saved to the .kra file, so as long as you don't save " "and open to a different file format, nor convert the colorize mask to a " "paintlayer, you can keep working adjust the results." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:114 msgid "Tool Options" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:116 #: ../../reference_manual/tools/colorize_mask.rst:172 msgid "Update" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:117 msgid "" "Run the colorize mask algorithm. The progress bar for updates on a colorize " "mask shows only in the layer docker." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:118 #: ../../reference_manual/tools/colorize_mask.rst:169 msgid "Edit key strokes" msgstr "Édition des marques de couleur" #: ../../reference_manual/tools/colorize_mask.rst:119 msgid "" "Put the mask into edit mode. In edit mode, it will also show the 'pre-" "filtering' on the line-art, which is for example a blur filter for gap " "closing." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:121 msgid "" "Show the output of the colorize mask. If :guilabel:`Edit key strokes` is " "active, this will be shown semi-transparently, so it will be easy to " "recognise the difference between the strokes and the output." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:127 #: ../../reference_manual/tools/colorize_mask.rst:165 msgid "Show output" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:127 msgid "" "On the **Left**: :guilabel:`Show Output` is on, :guilabel:`Edit Strokes` is " "off. In the **Middle**: :guilabel:`Show Output` and :guilabel:`Edit Strokes` " "are on. On the **Right**: :guilabel:`Show Output` is off and :guilabel:`Edit " "Strokes` is on.]]" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:129 msgid "Limit to layer bounds" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:130 msgid "" "Limit the colorize mask to the combined layer bounds of the strokes and the " "line art it is filling. This can speed up the use of the mask on complicated " "compositions, such as comic pages." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:132 msgid "" "Activate this for line art with large solid areas, for example shadows on an " "object. For the best use, set the value to the thinnest lines on the image. " "In the image below, note how edge detection affects the big black areas:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:138 msgid "Edge detection" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:138 msgid "" "From left to right: an example with big black shadows on an object but no " "edge detection, the same example without the edit strokes enabled. Then the " "same example with edge detection enabled and set to 2px, and that same " "example with out edit strokes enabled." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:141 msgid "" "While the algorithm is pretty good against gaps in contours, this will " "improve the gap recognition. The higher this value is, the bigger the gaps " "it will try to close, but a too high value can lead to other errors. Note " "how the pre-filtered line art (that's the blurry haze) affects the color " "patches." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:146 msgid "Gap close hint" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:147 msgid "" "On the **Left**: :guilabel:`Gap close hint` is 0px. In the **Middle**: :" "guilabel:`Gap close hint` is 15px (the lines are 10px). On the **Right**: :" "guilabel:`Gap close hint` is 275px." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:149 msgid "" "This will attempt to handle messy strokes that overlap the line art where " "they shouldn't. At 0 no clean up is done, at 100% the clean-up is most " "aggressive." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:153 msgid "Clean-up strokes" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:155 msgid "Keystrokes" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:156 msgid "" "This palette keeps track of the colors used by the strokes. This is useful " "so you can switch back to colors easily. You can increase the swatch size by " "hovering over it with the mouse, and doing :kbd:`Ctrl +` |mousescroll|." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:158 msgid "Transparent" msgstr "Transparent" #: ../../reference_manual/tools/colorize_mask.rst:158 msgid "" "This button is under the keystrokes palette, you can mark the selected color " "to be interpreted a 'transparent' with this. In the clean-up screenshot " "above, cyan had been marked as transparent." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:161 msgid "Layer properties" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:163 msgid "" "The colorize mask layer has four properties. They are all the buttons on the " "right side of the layer:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:166 msgid "" "The first button, it allows you to toggle whether you'll see the output from " "the colorize algorithm." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:167 msgid "Lock" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:168 msgid "Stops the mask from being edited." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:170 msgid "" "Whether the colorize mask is in edit mode. In edit mode it'll show the " "strokes, and the output will be semi-transparent." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:172 msgid "" "The last button will force the colorize mask to update, even when you're in " "a different tool." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:174 msgid "Colorize masks cannot be animated." msgstr "" diff --git a/locale/fr/LC_MESSAGES/reference_manual/tools/dyna.po b/locale/fr/LC_MESSAGES/reference_manual/tools/dyna.po index 7976f1e1c..b329e9009 100644 --- a/locale/fr/LC_MESSAGES/reference_manual/tools/dyna.po +++ b/locale/fr/LC_MESSAGES/reference_manual/tools/dyna.po @@ -1,70 +1,70 @@ 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" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-02-27 08:02+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" #: ../../:38 msgid "" ".. image:: images/icons/dyna_tool.svg\n" " :alt: tooldyna" msgstr "" #: ../../reference_manual/tools/dyna.rst:1 msgid "Krita's dynamic brush tool reference." msgstr "" #: ../../reference_manual/tools/dyna.rst:16 msgid "Dynamic Brush Tool" msgstr "Brosse dynamique" #: ../../reference_manual/tools/dyna.rst:18 msgid "|tooldyna|" msgstr "" #: ../../reference_manual/tools/dyna.rst:20 msgid "" "Add custom smoothing dynamics to your brush. This will give you similar " "smoothing results as the normal freehand brush. There are a couple options " "that you can change." msgstr "" #: ../../reference_manual/tools/dyna.rst:22 msgid "Mass" msgstr "Masse" #: ../../reference_manual/tools/dyna.rst:23 msgid "" "Average your movement to make it appear smoother. Higher values will make " "your brush move slower." msgstr "" #: ../../reference_manual/tools/dyna.rst:25 msgid "Drag" msgstr "Faire glisser" #: ../../reference_manual/tools/dyna.rst:25 msgid "" "A rubberband effect that will help your lines come back to your cursor. " -"lower values will make the effect more extreme." +"Lower values will make the effect more extreme." msgstr "" #: ../../reference_manual/tools/dyna.rst:27 msgid "Recommended values are around 0.02 Mass and 0.92 Drag." msgstr "" diff --git a/locale/fr/LC_MESSAGES/tutorials/flat-coloring.po b/locale/fr/LC_MESSAGES/tutorials/flat-coloring.po index fefe82a38..13c54b727 100644 --- a/locale/fr/LC_MESSAGES/tutorials/flat-coloring.po +++ b/locale/fr/LC_MESSAGES/tutorials/flat-coloring.po @@ -1,763 +1,763 @@ msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-03-12 03:34+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-02-27 08:22+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 "" +#: ../../tutorials/flat-coloring.rst:0 +msgid "" +".. image:: images/en/flat-coloring/Krita_filling_lineart_selection_1.png" +msgstr "" + +#: ../../tutorials/flat-coloring.rst:0 +msgid "" +".. image:: images/en/flat-coloring/Krita_filling_lineart_selection_2.png" +msgstr "" + +#: ../../tutorials/flat-coloring.rst:0 +msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_1.png" +msgstr "" + +#: ../../tutorials/flat-coloring.rst:0 +msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_2.png" +msgstr "" + +#: ../../tutorials/flat-coloring.rst:0 +msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_3.png" +msgstr "" + #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart14.png\n" " :alt: layer structure for flatting in krita" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart1.png\n" " :alt: blend mode setup of lineart flat coloring" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart2.png\n" " :alt: effects of multiply blend mode" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/icons/fill_tool.svg\n" " :alt: fill-tool icon" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart7.png\n" " :alt: colors filled with fill tool" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart15.png\n" " :alt: selecting with selection tools for filling color" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart16.png\n" " :alt: selection mask in Krita" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart17.png\n" " :alt: filling color in selection" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart18.png\n" " :alt: result of coloring made with the help of selection tools" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart8.png\n" " :alt: filling color in lineart using path tool" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart9.png\n" " :alt: erasing with path tool" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart10.png\n" " :alt: coloring with colorise mask" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart11.png\n" " :alt: result from the colorise mask" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart12.png\n" " :alt: slitting colors into islands" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart13.png\n" " :alt: resulting color islands from split layers" msgstr "" -#: ../../tutorials/flat-coloring.rst:0 -msgid "" -".. image:: images/en/flat-coloring/Krita_filling_lineart_selection_1.png" -msgstr "" - -#: ../../tutorials/flat-coloring.rst:0 -msgid "" -".. image:: images/en/flat-coloring/Krita_filling_lineart_selection_2.png" -msgstr "" - -#: ../../tutorials/flat-coloring.rst:0 -msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_1.png" -msgstr "" - -#: ../../tutorials/flat-coloring.rst:0 -msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_2.png" -msgstr "" - -#: ../../tutorials/flat-coloring.rst:0 -msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_3.png" -msgstr "" - #: ../../tutorials/flat-coloring.rst:1 msgid "Common workflows used in Krita" msgstr "" #: ../../tutorials/flat-coloring.rst:13 msgid "Flat Coloring" msgstr "" #: ../../tutorials/flat-coloring.rst:15 msgid "" "So you've got a cool black on white drawing, and now you want to color it! " "The thing we’ll aim for in this tutorial is to get your lineart colored in " "with flat colors. So no shading just yet. We’ll be going through some " "techniques for preparing the lineart, and we’ll be using the layer docker to " "put each colour on a separate layer, so we can easily access each colour " "when we add shading." msgstr "" #: ../../tutorials/flat-coloring.rst:17 msgid "" "This tutorial is adapted from this `tutorial `_ by " "the original author." msgstr "" #: ../../tutorials/flat-coloring.rst:20 msgid "Understanding Layers" msgstr "" #: ../../tutorials/flat-coloring.rst:22 msgid "" "To fill lineart comfortably, it's best to take advantage of the layerstack. " "The layer stack is pretty awesome, and it's one of those features that make " "digital art super-convenient." msgstr "" #: ../../tutorials/flat-coloring.rst:24 msgid "" "In traditional art, it is not uncommon to first draw the full background " "before drawing the subject. Or to first draw a line art and then colour it " "in. Computers have a similar way of working." msgstr "" #: ../../tutorials/flat-coloring.rst:26 msgid "" "In programming, if you tell a computer to draw a red circle, and then " "afterwards tell it to draw a smaller yellow circle, you will see the small " "yellow circle overlap the red circle. Switch the commands around, and you " "will not see the yellow circle at all: it was drawn before the red circle " "and thus ‘behind’ it." msgstr "" #: ../../tutorials/flat-coloring.rst:28 msgid "" "This is referred to as the “drawing order”. So like the traditional artist, " "the computer will first draw the images that are behind everything, and " "layer the subject and foreground on top of it. The layer docker is a way for " "you to control the drawing order of multiple images, so for example, you can " "have your lineart drawn later than your colors, meaning that the lines will " "be drawn over the colors, making it easier to make it neat!" msgstr "" #: ../../tutorials/flat-coloring.rst:30 msgid "" "Other things that a layer stack can do are blending the colors of different " "layers differently with blending modes, using a filter in the layer stack, " "or using a mask that allows you to make parts transparent." msgstr "" #: ../../tutorials/flat-coloring.rst:32 msgid "" "Programmers talk about transparency as ''Alpha'', which is because the 'a' " "symbol is used to present transparency in the algorithms for painting one " "color on top of another. Usually when you see the word ''Alpha'' in a " "graphics program, just think of it as affecting the transparency." msgstr "" #: ../../tutorials/flat-coloring.rst:35 msgid "Preparing your line-art" msgstr "" #: ../../tutorials/flat-coloring.rst:37 msgid "" "Put the new layer underneath the layer containing the lineart (drag and drop " "or use the up/down arrows for that), and draw on it." msgstr "" #: ../../tutorials/flat-coloring.rst:42 msgid "" "…And notice nothing happening. This is because the white isn’t transparent. " "You wouldn’t really want it to either, how else would you make convincing " "highlights? So what we first need to do to colour in our drawing is prepare " "our lineart. There’s several methods of doing so, each with varying " "qualities." msgstr "" #: ../../tutorials/flat-coloring.rst:45 msgid "The Multiply Blending Mode" msgstr "" #: ../../tutorials/flat-coloring.rst:47 msgid "" "So, typically, to get a black and white lineart usable for colouring, you " "can set the blending mode of the lineart layer to Multiply. You do this by " "selecting the layer and going to the drop down that says **Normal** and " "setting that to **Multiply**." msgstr "" #: ../../tutorials/flat-coloring.rst:52 msgid "And then you should be able to see your colors!" msgstr "" #: ../../tutorials/flat-coloring.rst:54 msgid "" "Multiply is not a perfect solution however. For example, if through some " "image editing magic I make the lineart blue, it results into this:" msgstr "" #: ../../tutorials/flat-coloring.rst:59 msgid "" "This is because multiply literally multiplies the colors. So it uses maths!" msgstr "" #: ../../tutorials/flat-coloring.rst:61 msgid "" "What it first does is take the values of the RGB channels, then divides them " "by the max (because we're in 8bit, this is 255), a process we call " "normalising. Then it multiplies the normalised values. Finally, it takes the " "result and multiplies it with 255 again to get the result values." msgstr "" #: ../../tutorials/flat-coloring.rst:67 msgid "Pink" msgstr "Rose" #: ../../tutorials/flat-coloring.rst:68 msgid "Pink (normalised)" msgstr "" #: ../../tutorials/flat-coloring.rst:69 ../../tutorials/flat-coloring.rst:87 msgid "Blue" msgstr "" #: ../../tutorials/flat-coloring.rst:70 msgid "Blue (normalised)" msgstr "" #: ../../tutorials/flat-coloring.rst:71 msgid "Normalised, multiplied" msgstr "" #: ../../tutorials/flat-coloring.rst:72 msgid "Result" msgstr "Résultat" #: ../../tutorials/flat-coloring.rst:73 msgid "Red" msgstr "Rouge" #: ../../tutorials/flat-coloring.rst:74 msgid "222" msgstr "" #: ../../tutorials/flat-coloring.rst:75 msgid "0.8705" msgstr "" #: ../../tutorials/flat-coloring.rst:76 msgid "92" msgstr "" #: ../../tutorials/flat-coloring.rst:77 msgid "0.3607" msgstr "" #: ../../tutorials/flat-coloring.rst:78 msgid "0.3139" msgstr "" #: ../../tutorials/flat-coloring.rst:79 msgid "80" msgstr "" #: ../../tutorials/flat-coloring.rst:80 msgid "Green" msgstr "Vert" #: ../../tutorials/flat-coloring.rst:81 msgid "144" msgstr "" #: ../../tutorials/flat-coloring.rst:82 msgid "0.5647" msgstr "" #: ../../tutorials/flat-coloring.rst:83 msgid "176" msgstr "" #: ../../tutorials/flat-coloring.rst:84 msgid "0.6902" msgstr "" #: ../../tutorials/flat-coloring.rst:85 msgid "0.3897" msgstr "" #: ../../tutorials/flat-coloring.rst:86 msgid "99" msgstr "" #: ../../tutorials/flat-coloring.rst:88 msgid "123" msgstr "" #: ../../tutorials/flat-coloring.rst:89 msgid "0.4823" msgstr "" #: ../../tutorials/flat-coloring.rst:90 msgid "215" msgstr "" #: ../../tutorials/flat-coloring.rst:91 msgid "0.8431" msgstr "" #: ../../tutorials/flat-coloring.rst:92 msgid "0.4066" msgstr "" #: ../../tutorials/flat-coloring.rst:93 msgid "103" msgstr "" #: ../../tutorials/flat-coloring.rst:95 msgid "" "This isn't completely undesirable, and a lot of artists use this effect to " "add a little richness to their colors." msgstr "" #: ../../tutorials/flat-coloring.rst:98 ../../tutorials/flat-coloring.rst:127 #: ../../tutorials/flat-coloring.rst:154 ../../tutorials/flat-coloring.rst:173 #: ../../tutorials/flat-coloring.rst:210 ../../tutorials/flat-coloring.rst:247 #: ../../tutorials/flat-coloring.rst:275 ../../tutorials/flat-coloring.rst:317 msgid "Advantages" msgstr "" #: ../../tutorials/flat-coloring.rst:100 msgid "" "Easy, can work to your benefit even with coloured lines by softening the " "look of the lines while keeping nice contrast." msgstr "" #: ../../tutorials/flat-coloring.rst:103 ../../tutorials/flat-coloring.rst:132 #: ../../tutorials/flat-coloring.rst:159 ../../tutorials/flat-coloring.rst:178 #: ../../tutorials/flat-coloring.rst:215 ../../tutorials/flat-coloring.rst:252 #: ../../tutorials/flat-coloring.rst:280 ../../tutorials/flat-coloring.rst:322 msgid "Disadvantages" msgstr "" #: ../../tutorials/flat-coloring.rst:105 msgid "Not actually transparent. Is a little funny with coloured lines." msgstr "" #: ../../tutorials/flat-coloring.rst:108 msgid "Using Selections" msgstr "" #: ../../tutorials/flat-coloring.rst:110 msgid "" "The second method is one where we'll make it actually transparent. In other " "programs this would be done via the channel docker, but Krita doesn't do " "custom channels, instead it uses Selection Masks to store custom selections." msgstr "" #: ../../tutorials/flat-coloring.rst:112 msgid "duplicate your lineart layer." msgstr "" #: ../../tutorials/flat-coloring.rst:114 msgid "" "convert the duplicate to a selection mask. |mouseright| the layer, then :" "menuselection:`Convert --> to Selection Mask`." msgstr "" #: ../../tutorials/flat-coloring.rst:118 msgid "" "Invert the selection mask. :menuselection:`Select --> Invert Selection`." msgstr "" #: ../../tutorials/flat-coloring.rst:120 msgid "" "Make a new layer, and do :menuselection:`Edit --> Fill with foreground " "color`." msgstr "" #: ../../tutorials/flat-coloring.rst:124 msgid "And you should now have the line art on a separate layer." msgstr "" #: ../../tutorials/flat-coloring.rst:129 msgid "Actual transparency." msgstr "" #: ../../tutorials/flat-coloring.rst:134 msgid "Doesn't work when the lineart is coloured." msgstr "" #: ../../tutorials/flat-coloring.rst:137 msgid "Using Masks" msgstr "" #: ../../tutorials/flat-coloring.rst:139 msgid "This is a simpler variation of the above." msgstr "" #: ../../tutorials/flat-coloring.rst:141 msgid "Make a filled layer underneath the lineart layer." msgstr "" #: ../../tutorials/flat-coloring.rst:145 msgid "" "Convert the lineart layer to a transparency mask |mouseright| the layer, " "then :menuselection:`Convert --> to Transparency Mask`." msgstr "" #: ../../tutorials/flat-coloring.rst:149 msgid "" "Invert the transparency mask by going to :menuselection:`Filter --> Adjust --" "> Invert`" msgstr "" #: ../../tutorials/flat-coloring.rst:156 msgid "" "Actual transparency. You can also very easily doodle a pattern on the filled " "layer where the mask is on without affecting the transparency." msgstr "" #: ../../tutorials/flat-coloring.rst:161 msgid "" "Doesn't work when the lineart is coloured already. We can still get faster." msgstr "" #: ../../tutorials/flat-coloring.rst:164 msgid "Using Color to Alpha" msgstr "" #: ../../tutorials/flat-coloring.rst:166 msgid "By far the fastest way to get transparent lineart." msgstr "" #: ../../tutorials/flat-coloring.rst:168 msgid "" "Select the line art layer and apply the color to alpha filter. :" "menuselection:`Filter --> Colors --> Color to Alpha`. The default values " "should be sufficient for lineart." msgstr "" #: ../../tutorials/flat-coloring.rst:171 msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart_color_to_alpha.png" msgstr "" #: ../../tutorials/flat-coloring.rst:175 msgid "" "Actual transparency. Works with coloured line art as well, because it " "removes the white specifically." msgstr "" #: ../../tutorials/flat-coloring.rst:180 msgid "" "You'll have to lock the layer transparency or separate out the alpha via the " "right-click menu if you want to easily color it." msgstr "" #: ../../tutorials/flat-coloring.rst:184 msgid "Colouring the image" msgstr "" #: ../../tutorials/flat-coloring.rst:186 msgid "" "Much like preparing the line art, there's many different ways of colouring a " "layer." msgstr "" #: ../../tutorials/flat-coloring.rst:188 msgid "" "You could for example fill in everything by hand, but while that is very " "precise it also takes a lot of work. Let's take a look at the other options, " "shall we?" msgstr "" #: ../../tutorials/flat-coloring.rst:191 msgid "Fill Tool" msgstr "Remplir" #: ../../tutorials/flat-coloring.rst:196 msgid "" "In most cases the fill-tool can’t deal with the anti-aliasing (the soft edge " "in your lineart to make it more smooth when zoomed out) In Krita you have " "the grow-shrink option. Setting that to say… 2 expands the colour two pixels." msgstr "" #: ../../tutorials/flat-coloring.rst:198 msgid "" "Threshold decides when the fill-tool should consider a different colour " "pixel to be a border. And the feathering adds a extra soft border to the " "fill." msgstr "" #: ../../tutorials/flat-coloring.rst:200 msgid "" "Now, if you click on a gapless-part of the image with your preferred colour…" "(Remember to set the opacity to 1.0!)" msgstr "" #: ../../tutorials/flat-coloring.rst:202 msgid "" "Depending on your lineart, you can do flats pretty quickly. But setting the " "threshold low can result in little artifacts around where lines meet:" msgstr "" #: ../../tutorials/flat-coloring.rst:207 msgid "" "However, setting the threshold high can end with the fill not recognising " "some of the lighter lines. Besides these little artifacts can be removed " "with the brush easily." msgstr "" #: ../../tutorials/flat-coloring.rst:212 msgid "Pretty darn quick depending on the available settings." msgstr "" #: ../../tutorials/flat-coloring.rst:217 msgid "" "Again, not great with gaps or details. And it works best with aliased line-" "art." msgstr "" #: ../../tutorials/flat-coloring.rst:220 msgid "Selections" msgstr "Sélections" #: ../../tutorials/flat-coloring.rst:222 msgid "Selections work using the selection tools." msgstr "" #: ../../tutorials/flat-coloring.rst:227 msgid "" "For example with the :ref:`bezier_curve_selection_tool` you can easily " "select a curved area, and the with :kbd:`Shift` + |mouseleft| (not |" "mouseleft| + :kbd:`Shift`, there's a difference!) you can easily add to an " "existing selection." msgstr "" #: ../../tutorials/flat-coloring.rst:232 msgid "" "You can also edit the selection if you have :menuselection:`Select --> Show " "Global Selection Mask` turned on. Then you can select the global selection " "mask, and paint on it. (Above with the alternative selection mode, activated " "in the lower-left corner of the stats bar)" msgstr "" #: ../../tutorials/flat-coloring.rst:234 msgid "" "When done, select the color you want to fill it with and press :kbd:`Shift` " "+ `backspace`." msgstr "" #: ../../tutorials/flat-coloring.rst:239 msgid "" "You can save selections in selection masks by |mouseright| a layer, and then " "going to :menuselection:`Add --> Local Selection`. You first need to " "deactivate a selection by pressing the circle before adding a new selection." msgstr "" #: ../../tutorials/flat-coloring.rst:241 msgid "" "This can serve as an alternative way to split out different parts of the " "image, which is good for more painterly pieces:" msgstr "" #: ../../tutorials/flat-coloring.rst:249 msgid "A bit more precise than filling." msgstr "" #: ../../tutorials/flat-coloring.rst:254 msgid "Previewing your color isn't as easy." msgstr "" #: ../../tutorials/flat-coloring.rst:257 msgid "Geometric tools" msgstr "" #: ../../tutorials/flat-coloring.rst:259 msgid "" "So you have a tool for making rectangles or circles. And in the case of " "Krita, a tool for bezier curves. Select the path tool (|path tool|), and set " "the tool options to fill=foreground and outline=none. Make sure that your " "opacity is set to 1.00 (fully opaque)." msgstr "" #: ../../tutorials/flat-coloring.rst:262 msgid "" ".. image:: images/icons/bezier_curve.svg\n" " :alt: path tool" msgstr "" #: ../../tutorials/flat-coloring.rst:264 msgid "" "By clicking and holding, you can influence how curvy a line draw with the " "path tool is going to be. Letting go of the mouse button confirms the " "action, and then you’re free to draw the next point." msgstr "" #: ../../tutorials/flat-coloring.rst:269 msgid "" "You can also erase with a geometric tool. Just press :kbd:`E` or the eraser " "button." msgstr "" #: ../../tutorials/flat-coloring.rst:277 msgid "" "Quicker than using the brush or selections. Also decent with lineart that " "contains gaps." msgstr "" #: ../../tutorials/flat-coloring.rst:282 msgid "" "Fiddly details aren’t easy to fill in with this. So I recommend skipping " "those and filling them in later with a brush." msgstr "" #: ../../tutorials/flat-coloring.rst:285 msgid "Colorize Mask" msgstr "Masque de colorisation" #: ../../tutorials/flat-coloring.rst:287 msgid "" "So, this is a bit of an odd one. In the original tutorial, you'll see I'm " "suggesting using G'Mic, but that was a few years ago, and g'mic is a little " "unstable on windows. Therefore, the Krita developers have been attempting to " "make an internal tool doing the same." msgstr "" #: ../../tutorials/flat-coloring.rst:289 msgid "" "It is disabled in 3.1, but if you use 4.0 or later, it is in the toolbox. " "Check the Colorize Mask for more information." msgstr "" #: ../../tutorials/flat-coloring.rst:291 msgid "So it works like this:" msgstr "" #: ../../tutorials/flat-coloring.rst:293 msgid "Select the colorize mask tool." msgstr "" #: ../../tutorials/flat-coloring.rst:294 msgid "Tick the layer you're using." msgstr "" #: ../../tutorials/flat-coloring.rst:295 msgid "Paint the colors your want to use on the colorize mask" msgstr "" #: ../../tutorials/flat-coloring.rst:296 msgid "Click update to see the results:" msgstr "" #: ../../tutorials/flat-coloring.rst:301 msgid "" "When you are satisfied, |mouseright| the colorize mask, and go to :" "menuselection:`Convert --> Paint Layer`. This will turn the colorize mask to " "a generic paint layer. Then, you can fix the last issues by aking the " "lineart semi-transparent and painting the flaws away with a pixel art brush." msgstr "" #: ../../tutorials/flat-coloring.rst:306 msgid "" "Then, when you are done, split the layers via :menuselection:`Layers --> " "Split --> Split Layer`. There's a few options you can choose, but the " "following should be fine:" msgstr "" #: ../../tutorials/flat-coloring.rst:311 msgid "" "Finally, press **Ok** and you should get the following. Each color patch it " "on a different layer, named by the palette in the menu and alpha locked, so " "you can start painting right away!" msgstr "" #: ../../tutorials/flat-coloring.rst:319 msgid "" "Works with anti aliased lineart. Really quick to get the base work done. Can " "auto-close gaps." msgstr "" #: ../../tutorials/flat-coloring.rst:324 msgid "" "No anti aliasing of it’s own. You have to choose between getting details " "right or the gaps auto-closed." msgstr "" #: ../../tutorials/flat-coloring.rst:327 msgid "Conclusion" msgstr "Conclusion" #: ../../tutorials/flat-coloring.rst:329 msgid "" "I hope this has given you a good idea of how to fill in flats using the " "various techniques, as well as getting a hand of different Krita features. " "Remember that a good flat filled lineart is better than a badly shaded one, " "so keep practising to get the best out of these techniques!" msgstr "" diff --git a/locale/fr/LC_MESSAGES/user_manual/loading_saving_brushes.po b/locale/fr/LC_MESSAGES/user_manual/loading_saving_brushes.po index bca5780b8..53b5d0a24 100644 --- a/locale/fr/LC_MESSAGES/user_manual/loading_saving_brushes.po +++ b/locale/fr/LC_MESSAGES/user_manual/loading_saving_brushes.po @@ -1,950 +1,950 @@ msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-03-12 03:34+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-02-27 08:36+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" #: ../../user_manual/loading_saving_brushes.rst:0 msgid ".. image:: images/en/Krita_4_0_dirty_preset_icon.png" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:None msgid ".. image:: images/en/Krita_4_0_Brush_Settings_Layout.svg" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:17 msgid "Loading and Saving Brushes" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:37 msgid "The Brush settings dropdown" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:44 msgid "" "When you open Brush Settings Editor panel you will see something like this:" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:48 msgid "Tour of the brush settings dropdown" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:53 msgid "The brush settings drop down is divided into six areas," msgstr "" #: ../../user_manual/loading_saving_brushes.rst:56 msgid "Section A - General Information" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:79 msgid "Engine" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:94 msgid "Reloading" msgstr "Rechargement" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:101 msgid "Saving a preset" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:103 msgid "" "On the right, there's :guilabel:`Save New Brush Preset` and :guilabel:" "`Overwrite Brush`." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:108 msgid "Overwrite Brush" msgstr "Écraser la brosse" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:113 msgid "Save New Brush Preset" msgstr "Enregistrer le nouveau préréglage" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:119 msgid ".. image:: images/en/Krita_4_0_Save_New_Brush_Preset_Dialog.png" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:125 msgid "Brush Name" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:127 msgid "Load Existing Thumbnail" msgstr "Charger des vignettes existantes" #: ../../user_manual/loading_saving_brushes.rst:128 msgid "This will load the existing thumbnail inside the preset." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:130 msgid "Load scratch pad thumbnail" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:132 msgid "Load Image" msgstr "Charger l'image" #: ../../user_manual/loading_saving_brushes.rst:133 msgid "With this you can choose an image from disk to load as a thumbnail." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:134 msgid "Load from Icon Library" msgstr "Charger depuis la bibliothèque d'icônes" #: ../../user_manual/loading_saving_brushes.rst:135 msgid "This opens up the icon library." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:137 msgid "Clear Thumbnail" msgstr "Effacer les vignettes" #: ../../user_manual/loading_saving_brushes.rst:137 msgid "This will make the mini scratch pad white." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:140 msgid "The Icon Library" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:142 msgid "To make making presets icons faster, Krita got an icon library." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:145 msgid ".. image:: images/en/Krita_4_0_Preset_Icon_Library_Dialog.png" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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, ad the lowest slider is a super simple levels filter. " +"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 "" #: ../../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." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:167 msgid "Section B - The Preset Chooser" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:169 msgid "" "The preset chooser is much the same as the preset docker and the preset " "dropdown 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 "" #: ../../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 "" #: ../../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 "" #: ../../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 for that " -"engine." +"list of Krita's engines. Selecting an engine from the list will show the " +"brushes for that engine." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:185 msgid "" -"The trashcan icon does the same as it does in the preset docker: delete , or " +"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 "" #: ../../user_manual/loading_saving_brushes.rst:189 msgid "Section C - The Scratch pad" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:202 msgid "The scratch pad has five buttons underneath it. These are in order for:" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:204 msgid "Showing the current brush image" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:206 msgid "Adding a gradient to the scratch pad (useful for smudge brushes)" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:207 msgid "Filling with the background color" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:208 msgid "Clearing everything on the scratch pad." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:211 msgid "Section D - The Options List" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:227 msgid "Section E - Option Configuration Widget" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:233 msgid "Using sensor curves" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:260 msgid "Underneath the curve widget there are two more options:" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:264 msgid "Share Curves across all settings" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:271 msgid "Multiply" msgstr "Multiplier" #: ../../user_manual/loading_saving_brushes.rst:272 msgid "Will multiply the two values, 0.5\\*0.7 = 0.35" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:274 msgid "Addition" msgstr "" #: ../../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 "" # #-#-#-#-# ktorrent.po (ktorrent) #-#-#-#-# # unreviewed-context #: ../../user_manual/loading_saving_brushes.rst:277 msgid "Maximum" msgstr "Maximum" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:280 msgid "Minimum" msgstr "Minimum" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:283 msgid "Will subtract the smallest value from the largest, so 0.7-0.5 = 0.2" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:284 msgid "Curves Calculation Mode" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:284 msgid "Difference" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:286 msgid "It's maybe better to see with the following example:" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:289 msgid ".. image:: images/en/Krita_4_0_brush_curve_calculation_mode.png" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:290 msgid "" "The first two are regular, the rest with different multiplication types." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:292 msgid "Is a brush with size set to the distance sensor." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:293 msgid "Is a brush with the size set to the fade sensor." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:294 msgid "The size is calculated from the fade and distance sensors multiplied." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:297 msgid "" "The size takes the maximum value from the values of the fade and distance " "sensors." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:299 msgid "" -"The size takes the minimum value from the values of the face and distance " +"The size takes the minimum value from the values of the fade and distance " "sensors." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:305 msgid "Section F - Miscellaneous options" msgstr "" #: ../../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, the revert to default. " "Dirtied presets can be recognized by the icon in the top-left of the preset." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:316 msgid "Temporarily Save Tweaks to Preset (Dirty Presets)" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:319 msgid "Eraser Switch Size" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:319 msgid "" "This switches the brush to a separately stored size when using the :kbd:`E` " "key." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:321 msgid "Eraser Switch Opacity" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:322 msgid "Same as above, but then with Eraser opacity." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:330 msgid "Instant Preview" msgstr "Aperçu instantané" #: ../../user_manual/loading_saving_brushes.rst:333 msgid "The On-canvas brush settings" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:347 msgid "Making a Brush Preset" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:349 msgid "Now, let's make a simple brush to test the waters with:" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:352 msgid "Getting a default for the brush engine." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:354 msgid "First, open the settings with :kbd:`F5`." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:361 msgid "Example: Making an inking brush" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:370 -msgid "Uncheck the :guilabel:`enable pen settings` checkbox." +msgid "Uncheck the :guilabel:`Enable Pen Settings` checkbox." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:377 msgid "" -"Uncheck the :guilabel:`enable pen settings` checkbox here as well. Test " +"Uncheck the :guilabel:`Enable Pen Settings` checkbox here as well. Test " "again." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:401 msgid "Saving the new Brush" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:403 msgid "" "When you're satisfied, go to the upper left and select :guilabel::`Save new " "preset`." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:414 msgid "Finally press :guilabel:`Save`, and your brush should be done." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:416 msgid "You can further modify your inking brush by..." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:422 msgid "Making the fine lines look even softer by using the flow option." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:422 msgid "" "To do this, select the flow option, and turn back on the 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 "" #: ../../user_manual/loading_saving_brushes.rst:425 msgid "Sharing Brushes" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:438 msgid "Sharing a single preset" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:440 msgid "There are three types of resources a single preset can take:" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:446 msgid "A Pattern file: this is when you are using textures." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:452 msgid "" "To find those resources, go to :menuselection:`Settings --> Manage Resources " "--> Open Resource Folder`." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:458 msgid "Importing a single KPP file." msgstr "" #: ../../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 "" #: ../../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 " "dropdown (: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 "" #: ../../user_manual/loading_saving_brushes.rst:471 msgid "Sharing via ZIP (old-fashioned)" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:477 msgid "Using a ZIP with the relevant files." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:479 msgid "" "Go to :menuselection:`Settings --> Manage Resources --> Open Resource " "Folder` to open the resource folder." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:480 msgid "Then, open up the zip file." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:484 msgid "Restart Krita" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:485 msgid "Enjoy your brushes!" msgstr "" diff --git a/locale/fr/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po b/locale/fr/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po index 2ae5cb680..7caeef839 100644 --- a/locale/fr/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po +++ b/locale/fr/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po @@ -1,289 +1,289 @@ msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-03-06 03:37+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-02-27 08:39+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" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:1 msgid "Introduction to using Krita's python plugin API." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:18 msgid "Introduction to Python Scripting" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:22 msgid "" "When we offered python scripting as one of Kickstarter Stretchgoals we could " "implement next to vectors and text, it won the backer vote by a landslide. " "Some people even only picked python and nothing else. So what exactly is " "python scripting?" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:25 msgid "What is Python Scripting?" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:27 msgid "" "Python is a scripting language, that can be used to automate tasks. What " "python scripting in Krita means is that we added an API to krita, which is a " "bit of programming that allows python to access to parts of Krita. With this " "we can make dockers, perform menial tasks on a lot of different files and " "even write our own exporters. People who work with computer graphics, like " "VFX and video game artists use python a lot to make things like sprite " "sheets, automate parts of export and more." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:29 msgid "" "It is outside the scope of this manual to teach you python itself. However, " "as python is an extremely popular programming language and great for " "beginners, there's tons of learning material around that can be quickly " "found with a simple 'learn python' internet search." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:31 msgid "" "This manual will instead focus on how to use python to automate and extend " "Krita. For that we'll first start with the basics: How to run Python " "commands in the scripter." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:35 msgid "How to Enable the Scripter Plugin" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:37 msgid "" "The scripter plugin is not necessary to use python, but it is very useful " "for testing and playing around with python. It is a python console, written " "in python, which can be used to write small scripts and execute them on the " "fly." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:39 msgid "" "To open the scripter, navigate to :menuselection:`Tools --> Scripts --> " "Scripter`. If you don't see it listed, go to :menuselection:`Settings --> " "Configure Krita --> Python Plugin Manager` and toggle \"Scripter\" in the " "list to enable it. If you don't see the scripter plugin, make sure you are " "using an up-to-date version of Krita." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:41 msgid "" "The scripter will pop up with a text editor window on top and an output " "window below. Input the following in the text area:" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:48 msgid "" "Press the big play button or press :kbd:`Ctrl + R` to run the script. Then, " "below, in the output area the following should show up::" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:53 msgid "" "Now we have a console that can run functions like print() from the Python " "environment - but how do we use it to manage Krita?" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:56 msgid "Running basic Krita commands" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:58 msgid "" "To allow Python to communicate with Krita, we will use the Krita module. At " "the top of every script, we will write: ``from krita import *``" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:60 msgid "" "This allows us to talk to Krita through ``Krita.instance()``. Let's try to " "double our coding abilities with Python." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:68 msgid "" "You should see a second scripter window open. Pretty neat! Here is a " "slightly more advanced example." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:77 msgid "" "This will open up a new document. Clearly Python gives you quite a lot of " "control to automate Krita. Over time we expect the community to write all " "kinds of scripts that you can use simply by pasting them in the scripter." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:79 msgid "" "But what if you want to write new commands for yourself? The best place to " "start is very simple: search for examples written by other people! You can " "save a lot of time if someone else has written code that you can base your " "work on. It's also worth looking through the python plugins, which are " "located in /share/krita/pykrita. There's also a step by step guide for :ref:" "`krita_python_plugin_howto` here in the manual." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:81 msgid "" "But it's likely that you need more information. For that, we will need see " "what's hidden behind the asterisk when you ``import * from Krita``. To learn " "what Krita functions that are available and how to use them, you will want " "to go for Krita API reference documentation." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:84 msgid "Krita's API" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:86 msgid "" "`LibKis API Overview `_" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:87 msgid "" "`Krita class documentation `_" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:89 msgid "" "Those pages may look like a lot of jargon at first. This is because Krita's " "API documentation comes from the underlying C++ language that Krita is " "written in. The magic happens because of a Python tool called SIP, which " "makes it possible for python speak in C++ and talk to Krita. The end result " "is that when we ``import krita`` and call functions, we're actually using " "the C++ methods listed in that documentation." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:91 msgid "" "Let's see how this stuff works in more detail. Let's take a look at the " "second link, the `Krita class reference `_. There we can see all the " "functions available to the Krita instance. If you type dir(Krita.instance()) " "in Python, it should match this page very closely - you can view the " "documentation of the functions createDocument(), activeWindow(), and " "action() which we used above." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:93 msgid "" "One of the more confusing things is seeing all the C++ classes that Krita " -"uses, including the Qt classes that start with Q. But here is the beauty fo " +"uses, including the Qt classes that start with Q. But here is the beauty of " "SIP: it tries to make the translation from these classes into Python as " "simple and straightforward as possible. For example, you can see that the " "function filters() returns a QStringList. However, SIP converts those " "QStringLists into regular python list of strings!" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:101 msgid "Outputs as ::" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:112 msgid "However, sometimes the conversion doesn't go quite as smoothly." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:120 msgid "gives something like this::" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:127 msgid "" "It is a list of something, sure, but how to use it? If we go back to the " "Krita apidocs page and look at the function, documents() we'll see there's " "actually a clickable link on the 'Document' class. `If you follow that link " "`_, you'll see that the document has a function called " "name() which returns the name of the document, and functions width() and " "height() which return the dimensions. So if we wanted to generate an info " "report about the documents in Krita, we could write a script like this:" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:137 msgid "we get an output like::" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:147 msgid "" "Hopefully this will give you an idea of how to navigate the API docs now." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:149 msgid "" "Krita's API has many more classes, you can get to them by going to the top-" "left class list, or just clicking their names to get to their API docs. The " "functions print() or dir() are your friends here as well. This line will " "print out a list of all the actions in Krita - you could swap in one of " "these commands instead of 'python_scripter' in the example above." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:155 msgid "" "The Python module ``inspect`` was designed for this sort of task. Here's a " "useful function to print info about a class to the console." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:167 msgid "" "Finally, in addition to the LibKis documentation, the Qt documentation, " "since Krita uses PyQt to expose nearly all of the Qt API to Python. You can " "build entire windows with buttons and forms this way, using the very same " "tools that Krita is using! You can read the `Qt documentation `_ and the `PyQt documentation `_ for more info about this, and also definitely study the included plugins " "as well to see how they work." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:171 msgid "Technical Details" msgstr "Renseignements techniques" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:177 msgid "Python Scripting on Windows" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:179 msgid "" "To get Python scripting working on Windows 7/8/8.1, you will need to install " "the `Universal C Runtime from Microsoft's website `_. (Windows 10 already comes with it.)" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:182 msgid "Python 2 and 3" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:184 msgid "By default Krita is compiled for python 3." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:186 msgid "" "However, it is possible to compile it with python 2. To do so, you will need " "to add the following to the cmake configuration line::" 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 e66d20a46..7259a6431 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-03-12 03:34+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\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 it's 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 7df3038d1..000ffcb9f 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,1056 +1,1056 @@ msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-03-13 03:40+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\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 colour " "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 colour." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:71 msgid "" "Finally, group 4 has Vermillion red, citron yellow and cerulean blue. Their " "colours 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 colour 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 " "colour translate properly between color devices." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:82 msgid "" "It usually works by attempting to covert a colour to the reference colour " "space XYZ. XYZ is a coordinate system that has a spot for all colours 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 colour 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:88 msgid "" "To give a crude estimate, ICC profiles deal with keeping colours consistent " "over many interpretations of devices (screens, printers) by using a " "reference space, and OCIO deals with manipulating the interpretation of said " "colours." 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 grey it produces. Using " "these and several other measurements it creates an icc profile unique to " "your screen. You set these in Krita's colour 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 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-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.)" 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 colour 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 colorspace 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 colour reproduction. Use this if you want to " "see all colours 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 colours at whatever cost, which may result in awful looking " "colours. 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 "" "A in between solution between perceptual and absolute, relative will try to " "fit whatever colours it can match between colour 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 colourfulness, 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 '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." 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 colour 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 colour 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 colour 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 " "customly 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 colour maths, often concerning the blending of colours. " "This colour maths works best in linear colour space, and linear colour 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 colour 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 " "colour 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's 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 colours actually look strange: This is a " "bug in Firefox, which is because its `color management system is incomplete " "`_, save your png, jpg or tiff without an embedded profile to work " "around this." 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 " "bitdepth 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 specialised 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, mypaint, mangastudio, 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, mangastudio " "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 optimisers. 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 "" "Specialised 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 --> 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." 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 optimised content, and it's recommended to " "stay within 8bit, future screens may have higher bitdepths, 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 optimise 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 "" "`Visualising the XYZ colorspace `_" 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 colormanagement from argylcms manual `_" msgstr "" diff --git a/locale/ja/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po b/locale/ja/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po index 2170244b0..d8ad17ff0 100644 --- a/locale/ja/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po +++ b/locale/ja/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po @@ -1,204 +1,204 @@ msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-02-23 03:24+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\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" #: ../../:1 msgid "Use Undeformed Image" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:1 msgid "The Deform Brush Engine manual page." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:16 msgid "Deform Brush Engine" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:19 msgid ".. image:: images/icons/deformbrush.svg" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:20 msgid "" "The Deform Brush is a brush that allows you to pull and push pixels around. " "It's quite similar to the :ref:`liquify_mode`, but where liquify has higher " "quality, the deform brush has the speed." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:24 msgid "Options" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:26 msgid ":ref:`option_brush_tip`" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:27 msgid ":ref:`option_deform`" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:28 msgid ":ref:`blending_modes`" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:29 msgid ":ref:`option_opacity_n_flow`" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:30 msgid ":ref:`option_size`" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:31 msgid ":ref:`option_rotation`" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:32 msgid ":ref:`option_airbrush`" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:38 msgid "Deform Options" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:42 msgid ".. image:: images/en/Krita_deform_brush_examples.png" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:42 msgid "" "1: undeformed, 2: Move, 3: Grow, 4: Shrink, 5: Swirl Counter Clock Wise, 6: " "Swirl Clockwise, 7: Lens Zoom In, 8: Lens Zoom Out" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:44 msgid "These decide what strangeness may happen underneath your brush cursor." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:46 msgid "Grow" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:47 msgid "This bubbles up the area underneath the brush-cursor." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:48 msgid "Shrink" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:49 msgid "This pinches the Area underneath the brush-cursor." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:50 msgid "Swirl Counter Clock Wise" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:51 msgid "Swirls the area counter clock wise." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:52 msgid "Swirl Clock Wise" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:53 msgid "Swirls the area clockwise." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:54 msgid "Move" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:55 msgid "Nudges the area to the painting direction." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:56 msgid "Color Deformation" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:57 -msgid "This seems to randomly rearrange the pixels underneath the brush," +msgid "This seems to randomly rearrange the pixels underneath the brush." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:58 msgid "Lens Zoom In" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:59 msgid "Literally paints a enlarged version of the area." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:61 msgid "Lens Zoom Out" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:61 msgid "Paints a minimized version of the area." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:65 msgid ".. image:: images/en/Krita_deform_brush_colordeform.png" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:65 msgid "Showing color deform." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:68 msgid "Deform Amount" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:68 msgid "Defines the strength of the deformation." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:72 msgid ".. image:: images/en/Krita_deform_brush_bilinear.png" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:72 #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:74 msgid "Bilinear Interpolation" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:75 msgid "Smoothens the result. This causes calculation errors in 16bit." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:77 msgid "Use Counter" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:77 msgid "Slows down the deformation subtlety." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:81 msgid ".. image:: images/en/Krita_deform_brush_useundeformed.png" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:81 msgid "Without 'use undeformed' to the left and with to the right" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:84 msgid "" "Samples from the previous version of the image instead of the current. This " "works better with some deform options than others. Move for example seems to " "almost stop working, but it works really well with Grow." msgstr "" diff --git a/locale/ja/LC_MESSAGES/reference_manual/layers_and_masks/layer_styles.po b/locale/ja/LC_MESSAGES/reference_manual/layers_and_masks/layer_styles.po index f34d4a118..a4daf4244 100644 --- a/locale/ja/LC_MESSAGES/reference_manual/layers_and_masks/layer_styles.po +++ b/locale/ja/LC_MESSAGES/reference_manual/layers_and_masks/layer_styles.po @@ -1,50 +1,50 @@ 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" +"POT-Creation-Date: 2019-03-14 03:27+0100\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" #: ../../reference_manual/layers_and_masks/layer_styles.rst:1 msgid "How to use layer styles in Krita." msgstr "" #: ../../reference_manual/layers_and_masks/layer_styles.rst:17 msgid "Layer Styles" msgstr "" #: ../../reference_manual/layers_and_masks/layer_styles.rst:19 msgid "" "Layer styles are effects that are added on top of your layer. They are " "editable and can easily be toggled on and off. To add a layer style to a " "layer go to :menuselection:`Layer --> Layer Style`. You can also right-click " "a layer to access the layer styles." msgstr "" #: ../../reference_manual/layers_and_masks/layer_styles.rst:22 msgid "" -"When you have the layer styles window up, make sure that the \"Enable Effects" -"\" is checked." +"When you have the layer styles window up, make sure that the :guilabel:" +"`Enable Effects` item is checked." msgstr "" #: ../../reference_manual/layers_and_masks/layer_styles.rst:24 msgid "" "There are a variety of effects and styles you can apply to a layer. When you " "add a style, your layer docker will show an extra \"Fx\" icon. This allows " "you to toggle the layer style effects on and off." msgstr "" #: ../../reference_manual/layers_and_masks/layer_styles.rst:30 msgid "" "This feature was added to increase support for :program:`Adobe Photoshop`. " "The features that are included mirror what that application supports." msgstr "" diff --git a/locale/ja/LC_MESSAGES/reference_manual/render_animation.po b/locale/ja/LC_MESSAGES/reference_manual/render_animation.po index 123011cb6..2e72d9d70 100644 --- a/locale/ja/LC_MESSAGES/reference_manual/render_animation.po +++ b/locale/ja/LC_MESSAGES/reference_manual/render_animation.po @@ -1,298 +1,298 @@ msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-02-25 03:36+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\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" #: ../../reference_manual/render_animation.rst:1 msgid "How to use the render animation command in Krita." msgstr "" #: ../../reference_manual/render_animation.rst:17 #: ../../reference_manual/render_animation.rst:42 msgid "Render Animation" msgstr "" #: ../../reference_manual/render_animation.rst:19 msgid "" "Render animation allows you to render your animation to an image sequence, " "gif, mp4, mkv, or ogg file. It replaces :guilabel:`Export Animation` ." msgstr "" #: ../../reference_manual/render_animation.rst:21 msgid "" "For rendering to an animated fileformat, Krita will first render to a png " "sequence and then use FFMpeg, which is really good at encoding into video " "files, to render that sequence to an animated fileformat. The reason for " "this two-step process is that animation files can be really complex and " "really big, and this is the best way to allow you to keep control over the " "export process. For example, if your computer has a hiccup, and one frame " "saves out weird, first saving the image sequence allows you to only resave " "that one weird frame before rendering." msgstr "" #: ../../reference_manual/render_animation.rst:23 msgid "" "This means that you will need to find a good place to stick your frames " "before you can start rendering. If you only do throwaway animations, you can " "use a spot on your hard-drive with enough room and select :guilabel:`Delete " "Sequence After Rendering`" msgstr "" #: ../../reference_manual/render_animation.rst:26 msgid "Image Sequence" msgstr "" #: ../../reference_manual/render_animation.rst:28 msgid "Base Name" msgstr "" #: ../../reference_manual/render_animation.rst:29 msgid "" "The base name of your image sequence. This will get suffixed with a number " "depending on the frame." msgstr "" #: ../../reference_manual/render_animation.rst:30 msgid "File Format" msgstr "" #: ../../reference_manual/render_animation.rst:31 msgid "" "The fileformat to export the sequence to. When rendering we enforce png. The " "usual export options can be modified with :guilabel:`...`." msgstr "" #: ../../reference_manual/render_animation.rst:32 msgid "Render Location" msgstr "" #: ../../reference_manual/render_animation.rst:33 msgid "" "Where you render the image sequence to. Some people prefer to use a flash-" "drive or perhaps a harddrive that is fast." msgstr "" #: ../../reference_manual/render_animation.rst:34 msgid "First Frame" msgstr "" #: ../../reference_manual/render_animation.rst:35 msgid "" "The first frame of the range of frame you wish to adjust. Automatically set " "to the first frame of your current selection in the timeline. This is useful " "when you only want to re-render a little part." msgstr "" #: ../../reference_manual/render_animation.rst:36 msgid "Last Frame" msgstr "" #: ../../reference_manual/render_animation.rst:37 msgid "" "As above, the last frame of the range of frame you wish to adjust. " "Automatically set to the last frame of your current selection in the " "timeline." msgstr "" #: ../../reference_manual/render_animation.rst:39 msgid "Naming Sequence starts with" msgstr "" #: ../../reference_manual/render_animation.rst:39 msgid "" "The frames are named by using :guilabel:`Base Name` above and adding a " "number for the frame. This allows you to set where the frame number starts, " "so rendering from 8 to 10 with starting point 3 will give you images named " "11 and 15. Useful for programs that don't understand sequences starting with " "0, or for precision output." msgstr "" #: ../../reference_manual/render_animation.rst:44 msgid "Render As" msgstr "" #: ../../reference_manual/render_animation.rst:45 msgid "" "The file format to render to. All except gif have extra options that can be " "manipulated via :guilabel:`...`." msgstr "" #: ../../reference_manual/render_animation.rst:46 msgid "File" msgstr "" #: ../../reference_manual/render_animation.rst:47 msgid "Location and name of the rendered animation." msgstr "" #: ../../reference_manual/render_animation.rst:48 msgid "FFMpeg" msgstr "" #: ../../reference_manual/render_animation.rst:49 msgid "" "The location where your have ffmpeg. If you don't have this, Krita cannot " "render an animation. For proper gif support, you will need ffmpeg 2.6, as we " "use its palettegen functionality." msgstr "" #: ../../reference_manual/render_animation.rst:51 msgid "Delete Sequence After Rendering" msgstr "" #: ../../reference_manual/render_animation.rst:51 msgid "" "Delete the prerendered image sequence after done rendering. This allows you " "to choose whether to try and save some space, or to save the sequence for " "when encoding fails." msgstr "" #: ../../reference_manual/render_animation.rst:55 msgid "" "None of the video formats support saving from images with a transparent " "background, so Krita will try to fill it with something. You should add a " "background color yourself to avoid it from using, say, black." msgstr "" #: ../../reference_manual/render_animation.rst:58 msgid "Setting Up Krita for Exporting Animations" msgstr "" #: ../../reference_manual/render_animation.rst:60 msgid "" "You will need to download an extra application and link it in Krita for it " "to work. The application is pretty big (50MB), so the Krita developers " "didn't want to bundle it with the normal application. The software that we " "will use is free and called FFMpeg. The following instructions will explain " "how to get it and set it up. The setup is a one-time thing so you won't have " "to do it again." msgstr "" #: ../../reference_manual/render_animation.rst:63 msgid "Step 1 - Downloading FFMpeg" msgstr "" #: ../../reference_manual/render_animation.rst:66 #: ../../reference_manual/render_animation.rst:86 msgid "For Windows" msgstr "" #: ../../reference_manual/render_animation.rst:68 msgid "" "Go to the ffmpeg website (http://ffmpeg.org/download.html). The URL that had " "the link for me was here... https://ffmpeg.zeranoe.com/builds/" msgstr "" #: ../../reference_manual/render_animation.rst:70 msgid "" -"Watch out for the extremely annoying google ad that looks like a download " +"Watch out for the extremely annoying google and that looks like a download " "button! There is no big button for what we need. Either get the 64-bit " "STATIC version or 32-bit STATIC version that is shown later down the page. " "If you bought a computer in the past 5 years, you probably want the 64-bit " "version. Make sure you get a exe file, if you hover over the options they " "will give more information about what exactly you are downloading." msgstr "" #: ../../reference_manual/render_animation.rst:73 #: ../../reference_manual/render_animation.rst:93 msgid "For OSX" msgstr "" #: ../../reference_manual/render_animation.rst:75 msgid "" "Please see the section above. However, FFmpeg is obtained from https://" "evermeet.cx/ffmpeg/ instead. Just pick the big green button on the left " "under the FFmpeg heading. You will also need an archiving utility that " "supports .7z, since ffmpeg provides their OSX builds in .7z format. If you " "don't have one, try something like Keka (http://www.kekaosx.com)." msgstr "" #: ../../reference_manual/render_animation.rst:78 #: ../../reference_manual/render_animation.rst:98 msgid "For Linux" msgstr "" #: ../../reference_manual/render_animation.rst:80 msgid "" "FFMPeg can be installed from the repositories on most Linux systems. Version " "2.6 is required for proper gif support, as we use the palettegen " "functionality." msgstr "" #: ../../reference_manual/render_animation.rst:83 msgid "Step 2 - Unzipping and Linking to Krita" msgstr "" #: ../../reference_manual/render_animation.rst:88 msgid "" "Unzip the package that was just downloaded. Rename the long folder name to " "just ffmpeg. Let's put this folder in a easy to find location. go to your C:" "\\ and place it there. You can put it wherever you want, but that is where I " "put it." msgstr "" #: ../../reference_manual/render_animation.rst:90 msgid "" "Open Krita back up and go to :menuselection:`File --> Render Animation`. " "Click the :guilabel:`Browse` button on the last item called FFMpeg. Select " "this file ``C:/ffmpeg/bin/ffmpeg.exe`` and click :guilabel:`OK` ." msgstr "" #: ../../reference_manual/render_animation.rst:95 msgid "" "After downloading ffmpeg, you just need to extract it and then simply point " "to it in the FFMPEG location in Krita like ``/Users/user/Downloads/ffmpeg`` " "(assuming you downloaded and extracted the .7z file to /Users/user/" "Downloads)." msgstr "" #: ../../reference_manual/render_animation.rst:100 msgid "" "FFMpeg is, if installed from the repositories, usually found in ``/usr/bin/" "ffmpeg``" msgstr "" #: ../../reference_manual/render_animation.rst:103 msgid "Step 3 - Testing out an animation" msgstr "" #: ../../reference_manual/render_animation.rst:105 msgid "" "ffmpeg.exe is what Krita uses to do all of its animation export magic. Now " "that it is hooked up, let us test it out." msgstr "" #: ../../reference_manual/render_animation.rst:107 msgid "" "Let's make an animated GIF. in the Render Animation dialog, change the :" "guilabel:`Render As` field to \"GIF image\". Choose the file location where " "it will save with the \"File\" menu below. I just saved it to my desktop and " "called it \"export.gif\". When it is done, you should be able to open it up " "and see the animation." msgstr "" #: ../../reference_manual/render_animation.rst:111 msgid "" "By default, FFMPEG will render MP4 files with a too new codec, which means " "that windows media player won't be able to play it. So for windows, select " "\"baseline\" for the profile instead of \"high422\" before rendering." msgstr "" #: ../../reference_manual/render_animation.rst:115 msgid "" "OSX does not come with any software to play MP4 and MKV files. If you use " "Chrome for your web browser, you can drag the video file into that and the " "video should play. Otherwise you will need to get a program like VLC to see " "the video." msgstr "" diff --git a/locale/ja/LC_MESSAGES/reference_manual/tools/colorize_mask.po b/locale/ja/LC_MESSAGES/reference_manual/tools/colorize_mask.po index 5b2381298..b5560a262 100644 --- a/locale/ja/LC_MESSAGES/reference_manual/tools/colorize_mask.po +++ b/locale/ja/LC_MESSAGES/reference_manual/tools/colorize_mask.po @@ -1,437 +1,437 @@ msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-03-13 03:40+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\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 "" #: ../../:8 msgid "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" msgstr "" #: ../../:60 msgid "" ".. image:: images/icons/colorizemask_tool.svg\n" " :alt: toolcolorizemask" msgstr "" -#: ../../reference_manual/tools/colorize_mask.rst:0 -msgid "" -".. image:: images/en/Krita_4_0_colorize_mask_show_output_edit_strokes.png" -msgstr "" - -#: ../../reference_manual/tools/colorize_mask.rst:0 -msgid ".. image:: images/en/Krita_4_0_colorize_mask_edge_detection.png" -msgstr "" - -#: ../../reference_manual/tools/colorize_mask.rst:0 -msgid ".. image:: images/en/Krita_4_0_colorize_mask_gap_close_hint.png" -msgstr "" - -#: ../../reference_manual/tools/colorize_mask.rst:0 -msgid ".. image:: images/en/Krita_4_0_colorize_mask_clean_up.png" -msgstr "" - #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_01.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_02.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_03.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_04.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_05.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_06.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_07.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_08.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_09.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_10.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_11.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_12.png" msgstr "" +#: ../../reference_manual/tools/colorize_mask.rst:0 +msgid "" +".. image:: images/en/Krita_4_0_colorize_mask_show_output_edit_strokes.png" +msgstr "" + +#: ../../reference_manual/tools/colorize_mask.rst:0 +msgid ".. image:: images/en/Krita_4_0_colorize_mask_edge_detection.png" +msgstr "" + +#: ../../reference_manual/tools/colorize_mask.rst:0 +msgid ".. image:: images/en/Krita_4_0_colorize_mask_gap_close_hint.png" +msgstr "" + +#: ../../reference_manual/tools/colorize_mask.rst:0 +msgid ".. image:: images/en/Krita_4_0_colorize_mask_clean_up.png" +msgstr "" + #: ../../reference_manual/tools/colorize_mask.rst:1 msgid "How to use the colorize mask in Krita." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:16 msgid "Colorize Mask" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:18 msgid "|toolcolorizemask|" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:20 msgid "" "A tool for quickly coloring lineart, the Colorize Mask Editing tool can be " "found next to the gradient tool on your toolbox." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:22 msgid "" "This feature is technically already in 3.1, but disabled by default because " "we had not optimised the filling algorithm for production use yet. To enable " "it, find your krita configuration file, open it in notepad, and add " "\"disableColorizeMaskFeature=false\" to the top. Then restart Krita. Its " "official incarnation is in 4.0." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:26 msgid "Usage" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:28 msgid "" "This tool works in conjunction with the colorize mask, and the usage is as " "follows:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:30 msgid "" "For this example, we'll be using the ghost lady also used to explain masks " "on the basic concepts page." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:36 msgid "" "This image has the line art for the lady separated from the background, and " "what's more, the background is made up of two layers: one main and one for " "the details." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:38 msgid "" "First, select the colorize mask editing tool while having the lineart layer " "selected. |mouseleft| the canvas will add a colorize mask to the layer. You " "can also |mouseright| the line art layer, and then :menuselection:`Add --> " "Colorize Mask`. The line art will suddenly become really weird, this is the " "prefiltering which are filters through which we put the lineart to make the " "algorithm easier to use. The tool options overview below shows which options " "control that." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:45 msgid "" "Now, You make strokes with brush colors, press :guilabel:`Update` in the " "tool options, or tick the last icon of the colorize mask properties. In the " "layer docker, you will be able to see a little progress bar appear on the " "colorize mask indicating how long it takes. The bigger your file, the longer " "it will take." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:51 msgid "" "We want to have the blue transparent. In the tool options of the colorize " "editing tool you will see a small palette. These are the colors already " "used. You can remove colors here, or mark a single color as standing for " "transparent, by selecting it and pressing \"transparent\". Updating the mask " "will still show the blue stroke, but the result will be transparent:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:57 msgid "" "Because the colorize mask algorithm is slow, and we only need a part of our " "layer to be filled to fill the whole ghost lady figure, we can make use of :" "guilabel:`Limit to layer bounds`. This will limit Colorize Mask to use the " "combined size of the line art and the coloring key strokes. Therefore, make " "sure that the colorizing keystrokes only take up as much as they really need." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:63 msgid "" "Now the algorithm will be possibly a lot faster, allowing us to add strokes " "and press update in rapid succession:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:69 msgid "" "To see the final result, disable :guilabel:`Edit Key Strokes` or toggle the " "second to last icon on the colorize mask." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:75 msgid "" "If you want to edit the strokes again, re-enable :guilabel:`Edit Key " "Strokes`." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:77 msgid "" "Now, the colorize mask, being a mask, can also be added to a group of line " "art layers. It will then use the composition of the whole group as the line " "art. This is perfect for our background which has two separate line art " "layers. It also means that the colorize mask will be disabled when added to " "a group with pass-through enabled, because those have no final composition. " "You can recognise a disabled colorize mask because its name is stricken " "through." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:79 msgid "" "To add a colorize mask to a group, select the group and |mouseleft| the " "canvas with the Colorize Mask editing tool, or |mouseright| the layer to :" "menuselection:`Add --> Colorize Mask`." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:85 msgid "" "Now, we add strokes to the background quickly. We do not need to use the :" "menuselection:`Limit to Layer Bounds` because the background covers the " "whole image." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:91 msgid "" "For the record, you can use other brushes and tools also work on the " "colorize mask as long as they can draw. The Colorize Mask Editing tool is " "just the most convenient because you can get to the algorithm options." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:93 msgid "Out final result looks like this:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:99 msgid "" "Now we are done, |mouseright| the colorize mask and :menuselection:`Convert " "--> to Paint Layer`. Then, :menuselection:`Layer --> Split --> Split Layer`. " "This will give separate color islands that you can easily edit:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:105 msgid "" "This way we can very quickly paint the image. Due to the colorize mask going " "from the first image to the following took only 30 minutes, and would've " "taken quite a bit longer." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:111 msgid "" "The colorize masks are saved to the .kra file, so as long as you don't save " "and open to a different file format, nor convert the colorize mask to a " "paintlayer, you can keep working adjust the results." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:114 msgid "Tool Options" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:116 #: ../../reference_manual/tools/colorize_mask.rst:172 msgid "Update" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:117 msgid "" "Run the colorize mask algorithm. The progress bar for updates on a colorize " "mask shows only in the layer docker." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:118 #: ../../reference_manual/tools/colorize_mask.rst:169 msgid "Edit key strokes" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:119 msgid "" "Put the mask into edit mode. In edit mode, it will also show the 'pre-" "filtering' on the line-art, which is for example a blur filter for gap " "closing." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:121 msgid "" "Show the output of the colorize mask. If :guilabel:`Edit key strokes` is " "active, this will be shown semi-transparently, so it will be easy to " "recognise the difference between the strokes and the output." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:127 #: ../../reference_manual/tools/colorize_mask.rst:165 msgid "Show output" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:127 msgid "" "On the **Left**: :guilabel:`Show Output` is on, :guilabel:`Edit Strokes` is " "off. In the **Middle**: :guilabel:`Show Output` and :guilabel:`Edit Strokes` " "are on. On the **Right**: :guilabel:`Show Output` is off and :guilabel:`Edit " "Strokes` is on.]]" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:129 msgid "Limit to layer bounds" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:130 msgid "" "Limit the colorize mask to the combined layer bounds of the strokes and the " "line art it is filling. This can speed up the use of the mask on complicated " "compositions, such as comic pages." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:132 msgid "" "Activate this for line art with large solid areas, for example shadows on an " "object. For the best use, set the value to the thinnest lines on the image. " "In the image below, note how edge detection affects the big black areas:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:138 msgid "Edge detection" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:138 msgid "" "From left to right: an example with big black shadows on an object but no " "edge detection, the same example without the edit strokes enabled. Then the " "same example with edge detection enabled and set to 2px, and that same " "example with out edit strokes enabled." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:141 msgid "" "While the algorithm is pretty good against gaps in contours, this will " "improve the gap recognition. The higher this value is, the bigger the gaps " "it will try to close, but a too high value can lead to other errors. Note " "how the pre-filtered line art (that's the blurry haze) affects the color " "patches." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:146 msgid "Gap close hint" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:147 msgid "" "On the **Left**: :guilabel:`Gap close hint` is 0px. In the **Middle**: :" "guilabel:`Gap close hint` is 15px (the lines are 10px). On the **Right**: :" "guilabel:`Gap close hint` is 275px." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:149 msgid "" "This will attempt to handle messy strokes that overlap the line art where " "they shouldn't. At 0 no clean up is done, at 100% the clean-up is most " "aggressive." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:153 msgid "Clean-up strokes" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:155 msgid "Keystrokes" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:156 msgid "" "This palette keeps track of the colors used by the strokes. This is useful " "so you can switch back to colors easily. You can increase the swatch size by " "hovering over it with the mouse, and doing :kbd:`Ctrl +` |mousescroll|." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:158 msgid "Transparent" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:158 msgid "" "This button is under the keystrokes palette, you can mark the selected color " "to be interpreted a 'transparent' with this. In the clean-up screenshot " "above, cyan had been marked as transparent." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:161 msgid "Layer properties" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:163 msgid "" "The colorize mask layer has four properties. They are all the buttons on the " "right side of the layer:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:166 msgid "" "The first button, it allows you to toggle whether you'll see the output from " "the colorize algorithm." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:167 msgid "Lock" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:168 msgid "Stops the mask from being edited." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:170 msgid "" "Whether the colorize mask is in edit mode. In edit mode it'll show the " "strokes, and the output will be semi-transparent." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:172 msgid "" "The last button will force the colorize mask to update, even when you're in " "a different tool." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:174 msgid "Colorize masks cannot be animated." msgstr "" diff --git a/locale/ja/LC_MESSAGES/reference_manual/tools/dyna.po b/locale/ja/LC_MESSAGES/reference_manual/tools/dyna.po index 570939543..66f3503ac 100644 --- a/locale/ja/LC_MESSAGES/reference_manual/tools/dyna.po +++ b/locale/ja/LC_MESSAGES/reference_manual/tools/dyna.po @@ -1,64 +1,64 @@ 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" +"POT-Creation-Date: 2019-03-14 03:27+0100\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" #: ../../:38 msgid "" ".. image:: images/icons/dyna_tool.svg\n" " :alt: tooldyna" msgstr "" #: ../../reference_manual/tools/dyna.rst:1 msgid "Krita's dynamic brush tool reference." msgstr "" #: ../../reference_manual/tools/dyna.rst:16 msgid "Dynamic Brush Tool" msgstr "" #: ../../reference_manual/tools/dyna.rst:18 msgid "|tooldyna|" msgstr "" #: ../../reference_manual/tools/dyna.rst:20 msgid "" "Add custom smoothing dynamics to your brush. This will give you similar " "smoothing results as the normal freehand brush. There are a couple options " "that you can change." msgstr "" #: ../../reference_manual/tools/dyna.rst:22 msgid "Mass" msgstr "" #: ../../reference_manual/tools/dyna.rst:23 msgid "" "Average your movement to make it appear smoother. Higher values will make " "your brush move slower." msgstr "" #: ../../reference_manual/tools/dyna.rst:25 msgid "Drag" msgstr "" #: ../../reference_manual/tools/dyna.rst:25 msgid "" "A rubberband effect that will help your lines come back to your cursor. " -"lower values will make the effect more extreme." +"Lower values will make the effect more extreme." msgstr "" #: ../../reference_manual/tools/dyna.rst:27 msgid "Recommended values are around 0.02 Mass and 0.92 Drag." msgstr "" diff --git a/locale/ja/LC_MESSAGES/tutorials/flat-coloring.po b/locale/ja/LC_MESSAGES/tutorials/flat-coloring.po index 9bb22428f..46226fd91 100644 --- a/locale/ja/LC_MESSAGES/tutorials/flat-coloring.po +++ b/locale/ja/LC_MESSAGES/tutorials/flat-coloring.po @@ -1,757 +1,757 @@ msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-03-12 03:34+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\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 "" +#: ../../tutorials/flat-coloring.rst:0 +msgid "" +".. image:: images/en/flat-coloring/Krita_filling_lineart_selection_1.png" +msgstr "" + +#: ../../tutorials/flat-coloring.rst:0 +msgid "" +".. image:: images/en/flat-coloring/Krita_filling_lineart_selection_2.png" +msgstr "" + +#: ../../tutorials/flat-coloring.rst:0 +msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_1.png" +msgstr "" + +#: ../../tutorials/flat-coloring.rst:0 +msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_2.png" +msgstr "" + +#: ../../tutorials/flat-coloring.rst:0 +msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_3.png" +msgstr "" + #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart14.png\n" " :alt: layer structure for flatting in krita" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart1.png\n" " :alt: blend mode setup of lineart flat coloring" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart2.png\n" " :alt: effects of multiply blend mode" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/icons/fill_tool.svg\n" " :alt: fill-tool icon" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart7.png\n" " :alt: colors filled with fill tool" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart15.png\n" " :alt: selecting with selection tools for filling color" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart16.png\n" " :alt: selection mask in Krita" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart17.png\n" " :alt: filling color in selection" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart18.png\n" " :alt: result of coloring made with the help of selection tools" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart8.png\n" " :alt: filling color in lineart using path tool" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart9.png\n" " :alt: erasing with path tool" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart10.png\n" " :alt: coloring with colorise mask" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart11.png\n" " :alt: result from the colorise mask" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart12.png\n" " :alt: slitting colors into islands" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart13.png\n" " :alt: resulting color islands from split layers" msgstr "" -#: ../../tutorials/flat-coloring.rst:0 -msgid "" -".. image:: images/en/flat-coloring/Krita_filling_lineart_selection_1.png" -msgstr "" - -#: ../../tutorials/flat-coloring.rst:0 -msgid "" -".. image:: images/en/flat-coloring/Krita_filling_lineart_selection_2.png" -msgstr "" - -#: ../../tutorials/flat-coloring.rst:0 -msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_1.png" -msgstr "" - -#: ../../tutorials/flat-coloring.rst:0 -msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_2.png" -msgstr "" - -#: ../../tutorials/flat-coloring.rst:0 -msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_3.png" -msgstr "" - #: ../../tutorials/flat-coloring.rst:1 msgid "Common workflows used in Krita" msgstr "" #: ../../tutorials/flat-coloring.rst:13 msgid "Flat Coloring" msgstr "" #: ../../tutorials/flat-coloring.rst:15 msgid "" "So you've got a cool black on white drawing, and now you want to color it! " "The thing we’ll aim for in this tutorial is to get your lineart colored in " "with flat colors. So no shading just yet. We’ll be going through some " "techniques for preparing the lineart, and we’ll be using the layer docker to " "put each colour on a separate layer, so we can easily access each colour " "when we add shading." msgstr "" #: ../../tutorials/flat-coloring.rst:17 msgid "" "This tutorial is adapted from this `tutorial `_ by " "the original author." msgstr "" #: ../../tutorials/flat-coloring.rst:20 msgid "Understanding Layers" msgstr "" #: ../../tutorials/flat-coloring.rst:22 msgid "" "To fill lineart comfortably, it's best to take advantage of the layerstack. " "The layer stack is pretty awesome, and it's one of those features that make " "digital art super-convenient." msgstr "" #: ../../tutorials/flat-coloring.rst:24 msgid "" "In traditional art, it is not uncommon to first draw the full background " "before drawing the subject. Or to first draw a line art and then colour it " "in. Computers have a similar way of working." msgstr "" #: ../../tutorials/flat-coloring.rst:26 msgid "" "In programming, if you tell a computer to draw a red circle, and then " "afterwards tell it to draw a smaller yellow circle, you will see the small " "yellow circle overlap the red circle. Switch the commands around, and you " "will not see the yellow circle at all: it was drawn before the red circle " "and thus ‘behind’ it." msgstr "" #: ../../tutorials/flat-coloring.rst:28 msgid "" "This is referred to as the “drawing order”. So like the traditional artist, " "the computer will first draw the images that are behind everything, and " "layer the subject and foreground on top of it. The layer docker is a way for " "you to control the drawing order of multiple images, so for example, you can " "have your lineart drawn later than your colors, meaning that the lines will " "be drawn over the colors, making it easier to make it neat!" msgstr "" #: ../../tutorials/flat-coloring.rst:30 msgid "" "Other things that a layer stack can do are blending the colors of different " "layers differently with blending modes, using a filter in the layer stack, " "or using a mask that allows you to make parts transparent." msgstr "" #: ../../tutorials/flat-coloring.rst:32 msgid "" "Programmers talk about transparency as ''Alpha'', which is because the 'a' " "symbol is used to present transparency in the algorithms for painting one " "color on top of another. Usually when you see the word ''Alpha'' in a " "graphics program, just think of it as affecting the transparency." msgstr "" #: ../../tutorials/flat-coloring.rst:35 msgid "Preparing your line-art" msgstr "" #: ../../tutorials/flat-coloring.rst:37 msgid "" "Put the new layer underneath the layer containing the lineart (drag and drop " "or use the up/down arrows for that), and draw on it." msgstr "" #: ../../tutorials/flat-coloring.rst:42 msgid "" "…And notice nothing happening. This is because the white isn’t transparent. " "You wouldn’t really want it to either, how else would you make convincing " "highlights? So what we first need to do to colour in our drawing is prepare " "our lineart. There’s several methods of doing so, each with varying " "qualities." msgstr "" #: ../../tutorials/flat-coloring.rst:45 msgid "The Multiply Blending Mode" msgstr "" #: ../../tutorials/flat-coloring.rst:47 msgid "" "So, typically, to get a black and white lineart usable for colouring, you " "can set the blending mode of the lineart layer to Multiply. You do this by " "selecting the layer and going to the drop down that says **Normal** and " "setting that to **Multiply**." msgstr "" #: ../../tutorials/flat-coloring.rst:52 msgid "And then you should be able to see your colors!" msgstr "" #: ../../tutorials/flat-coloring.rst:54 msgid "" "Multiply is not a perfect solution however. For example, if through some " "image editing magic I make the lineart blue, it results into this:" msgstr "" #: ../../tutorials/flat-coloring.rst:59 msgid "" "This is because multiply literally multiplies the colors. So it uses maths!" msgstr "" #: ../../tutorials/flat-coloring.rst:61 msgid "" "What it first does is take the values of the RGB channels, then divides them " "by the max (because we're in 8bit, this is 255), a process we call " "normalising. Then it multiplies the normalised values. Finally, it takes the " "result and multiplies it with 255 again to get the result values." msgstr "" #: ../../tutorials/flat-coloring.rst:67 msgid "Pink" msgstr "" #: ../../tutorials/flat-coloring.rst:68 msgid "Pink (normalised)" msgstr "" #: ../../tutorials/flat-coloring.rst:69 ../../tutorials/flat-coloring.rst:87 msgid "Blue" msgstr "" #: ../../tutorials/flat-coloring.rst:70 msgid "Blue (normalised)" msgstr "" #: ../../tutorials/flat-coloring.rst:71 msgid "Normalised, multiplied" msgstr "" #: ../../tutorials/flat-coloring.rst:72 msgid "Result" msgstr "" #: ../../tutorials/flat-coloring.rst:73 msgid "Red" msgstr "" #: ../../tutorials/flat-coloring.rst:74 msgid "222" msgstr "" #: ../../tutorials/flat-coloring.rst:75 msgid "0.8705" msgstr "" #: ../../tutorials/flat-coloring.rst:76 msgid "92" msgstr "" #: ../../tutorials/flat-coloring.rst:77 msgid "0.3607" msgstr "" #: ../../tutorials/flat-coloring.rst:78 msgid "0.3139" msgstr "" #: ../../tutorials/flat-coloring.rst:79 msgid "80" msgstr "" #: ../../tutorials/flat-coloring.rst:80 msgid "Green" msgstr "" #: ../../tutorials/flat-coloring.rst:81 msgid "144" msgstr "" #: ../../tutorials/flat-coloring.rst:82 msgid "0.5647" msgstr "" #: ../../tutorials/flat-coloring.rst:83 msgid "176" msgstr "" #: ../../tutorials/flat-coloring.rst:84 msgid "0.6902" msgstr "" #: ../../tutorials/flat-coloring.rst:85 msgid "0.3897" msgstr "" #: ../../tutorials/flat-coloring.rst:86 msgid "99" msgstr "" #: ../../tutorials/flat-coloring.rst:88 msgid "123" msgstr "" #: ../../tutorials/flat-coloring.rst:89 msgid "0.4823" msgstr "" #: ../../tutorials/flat-coloring.rst:90 msgid "215" msgstr "" #: ../../tutorials/flat-coloring.rst:91 msgid "0.8431" msgstr "" #: ../../tutorials/flat-coloring.rst:92 msgid "0.4066" msgstr "" #: ../../tutorials/flat-coloring.rst:93 msgid "103" msgstr "" #: ../../tutorials/flat-coloring.rst:95 msgid "" "This isn't completely undesirable, and a lot of artists use this effect to " "add a little richness to their colors." msgstr "" #: ../../tutorials/flat-coloring.rst:98 ../../tutorials/flat-coloring.rst:127 #: ../../tutorials/flat-coloring.rst:154 ../../tutorials/flat-coloring.rst:173 #: ../../tutorials/flat-coloring.rst:210 ../../tutorials/flat-coloring.rst:247 #: ../../tutorials/flat-coloring.rst:275 ../../tutorials/flat-coloring.rst:317 msgid "Advantages" msgstr "" #: ../../tutorials/flat-coloring.rst:100 msgid "" "Easy, can work to your benefit even with coloured lines by softening the " "look of the lines while keeping nice contrast." msgstr "" #: ../../tutorials/flat-coloring.rst:103 ../../tutorials/flat-coloring.rst:132 #: ../../tutorials/flat-coloring.rst:159 ../../tutorials/flat-coloring.rst:178 #: ../../tutorials/flat-coloring.rst:215 ../../tutorials/flat-coloring.rst:252 #: ../../tutorials/flat-coloring.rst:280 ../../tutorials/flat-coloring.rst:322 msgid "Disadvantages" msgstr "" #: ../../tutorials/flat-coloring.rst:105 msgid "Not actually transparent. Is a little funny with coloured lines." msgstr "" #: ../../tutorials/flat-coloring.rst:108 msgid "Using Selections" msgstr "" #: ../../tutorials/flat-coloring.rst:110 msgid "" "The second method is one where we'll make it actually transparent. In other " "programs this would be done via the channel docker, but Krita doesn't do " "custom channels, instead it uses Selection Masks to store custom selections." msgstr "" #: ../../tutorials/flat-coloring.rst:112 msgid "duplicate your lineart layer." msgstr "" #: ../../tutorials/flat-coloring.rst:114 msgid "" "convert the duplicate to a selection mask. |mouseright| the layer, then :" "menuselection:`Convert --> to Selection Mask`." msgstr "" #: ../../tutorials/flat-coloring.rst:118 msgid "" "Invert the selection mask. :menuselection:`Select --> Invert Selection`." msgstr "" #: ../../tutorials/flat-coloring.rst:120 msgid "" "Make a new layer, and do :menuselection:`Edit --> Fill with foreground " "color`." msgstr "" #: ../../tutorials/flat-coloring.rst:124 msgid "And you should now have the line art on a separate layer." msgstr "" #: ../../tutorials/flat-coloring.rst:129 msgid "Actual transparency." msgstr "" #: ../../tutorials/flat-coloring.rst:134 msgid "Doesn't work when the lineart is coloured." msgstr "" #: ../../tutorials/flat-coloring.rst:137 msgid "Using Masks" msgstr "" #: ../../tutorials/flat-coloring.rst:139 msgid "This is a simpler variation of the above." msgstr "" #: ../../tutorials/flat-coloring.rst:141 msgid "Make a filled layer underneath the lineart layer." msgstr "" #: ../../tutorials/flat-coloring.rst:145 msgid "" "Convert the lineart layer to a transparency mask |mouseright| the layer, " "then :menuselection:`Convert --> to Transparency Mask`." msgstr "" #: ../../tutorials/flat-coloring.rst:149 msgid "" "Invert the transparency mask by going to :menuselection:`Filter --> Adjust --" "> Invert`" msgstr "" #: ../../tutorials/flat-coloring.rst:156 msgid "" "Actual transparency. You can also very easily doodle a pattern on the filled " "layer where the mask is on without affecting the transparency." msgstr "" #: ../../tutorials/flat-coloring.rst:161 msgid "" "Doesn't work when the lineart is coloured already. We can still get faster." msgstr "" #: ../../tutorials/flat-coloring.rst:164 msgid "Using Color to Alpha" msgstr "" #: ../../tutorials/flat-coloring.rst:166 msgid "By far the fastest way to get transparent lineart." msgstr "" #: ../../tutorials/flat-coloring.rst:168 msgid "" "Select the line art layer and apply the color to alpha filter. :" "menuselection:`Filter --> Colors --> Color to Alpha`. The default values " "should be sufficient for lineart." msgstr "" #: ../../tutorials/flat-coloring.rst:171 msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart_color_to_alpha.png" msgstr "" #: ../../tutorials/flat-coloring.rst:175 msgid "" "Actual transparency. Works with coloured line art as well, because it " "removes the white specifically." msgstr "" #: ../../tutorials/flat-coloring.rst:180 msgid "" "You'll have to lock the layer transparency or separate out the alpha via the " "right-click menu if you want to easily color it." msgstr "" #: ../../tutorials/flat-coloring.rst:184 msgid "Colouring the image" msgstr "" #: ../../tutorials/flat-coloring.rst:186 msgid "" "Much like preparing the line art, there's many different ways of colouring a " "layer." msgstr "" #: ../../tutorials/flat-coloring.rst:188 msgid "" "You could for example fill in everything by hand, but while that is very " "precise it also takes a lot of work. Let's take a look at the other options, " "shall we?" msgstr "" #: ../../tutorials/flat-coloring.rst:191 msgid "Fill Tool" msgstr "" #: ../../tutorials/flat-coloring.rst:196 msgid "" "In most cases the fill-tool can’t deal with the anti-aliasing (the soft edge " "in your lineart to make it more smooth when zoomed out) In Krita you have " "the grow-shrink option. Setting that to say… 2 expands the colour two pixels." msgstr "" #: ../../tutorials/flat-coloring.rst:198 msgid "" "Threshold decides when the fill-tool should consider a different colour " "pixel to be a border. And the feathering adds a extra soft border to the " "fill." msgstr "" #: ../../tutorials/flat-coloring.rst:200 msgid "" "Now, if you click on a gapless-part of the image with your preferred colour…" "(Remember to set the opacity to 1.0!)" msgstr "" #: ../../tutorials/flat-coloring.rst:202 msgid "" "Depending on your lineart, you can do flats pretty quickly. But setting the " "threshold low can result in little artifacts around where lines meet:" msgstr "" #: ../../tutorials/flat-coloring.rst:207 msgid "" "However, setting the threshold high can end with the fill not recognising " "some of the lighter lines. Besides these little artifacts can be removed " "with the brush easily." msgstr "" #: ../../tutorials/flat-coloring.rst:212 msgid "Pretty darn quick depending on the available settings." msgstr "" #: ../../tutorials/flat-coloring.rst:217 msgid "" "Again, not great with gaps or details. And it works best with aliased line-" "art." msgstr "" #: ../../tutorials/flat-coloring.rst:220 msgid "Selections" msgstr "" #: ../../tutorials/flat-coloring.rst:222 msgid "Selections work using the selection tools." msgstr "" #: ../../tutorials/flat-coloring.rst:227 msgid "" "For example with the :ref:`bezier_curve_selection_tool` you can easily " "select a curved area, and the with :kbd:`Shift` + |mouseleft| (not |" "mouseleft| + :kbd:`Shift`, there's a difference!) you can easily add to an " "existing selection." msgstr "" #: ../../tutorials/flat-coloring.rst:232 msgid "" "You can also edit the selection if you have :menuselection:`Select --> Show " "Global Selection Mask` turned on. Then you can select the global selection " "mask, and paint on it. (Above with the alternative selection mode, activated " "in the lower-left corner of the stats bar)" msgstr "" #: ../../tutorials/flat-coloring.rst:234 msgid "" "When done, select the color you want to fill it with and press :kbd:`Shift` " "+ `backspace`." msgstr "" #: ../../tutorials/flat-coloring.rst:239 msgid "" "You can save selections in selection masks by |mouseright| a layer, and then " "going to :menuselection:`Add --> Local Selection`. You first need to " "deactivate a selection by pressing the circle before adding a new selection." msgstr "" #: ../../tutorials/flat-coloring.rst:241 msgid "" "This can serve as an alternative way to split out different parts of the " "image, which is good for more painterly pieces:" msgstr "" #: ../../tutorials/flat-coloring.rst:249 msgid "A bit more precise than filling." msgstr "" #: ../../tutorials/flat-coloring.rst:254 msgid "Previewing your color isn't as easy." msgstr "" #: ../../tutorials/flat-coloring.rst:257 msgid "Geometric tools" msgstr "" #: ../../tutorials/flat-coloring.rst:259 msgid "" "So you have a tool for making rectangles or circles. And in the case of " "Krita, a tool for bezier curves. Select the path tool (|path tool|), and set " "the tool options to fill=foreground and outline=none. Make sure that your " "opacity is set to 1.00 (fully opaque)." msgstr "" #: ../../tutorials/flat-coloring.rst:262 msgid "" ".. image:: images/icons/bezier_curve.svg\n" " :alt: path tool" msgstr "" #: ../../tutorials/flat-coloring.rst:264 msgid "" "By clicking and holding, you can influence how curvy a line draw with the " "path tool is going to be. Letting go of the mouse button confirms the " "action, and then you’re free to draw the next point." msgstr "" #: ../../tutorials/flat-coloring.rst:269 msgid "" "You can also erase with a geometric tool. Just press :kbd:`E` or the eraser " "button." msgstr "" #: ../../tutorials/flat-coloring.rst:277 msgid "" "Quicker than using the brush or selections. Also decent with lineart that " "contains gaps." msgstr "" #: ../../tutorials/flat-coloring.rst:282 msgid "" "Fiddly details aren’t easy to fill in with this. So I recommend skipping " "those and filling them in later with a brush." msgstr "" #: ../../tutorials/flat-coloring.rst:285 msgid "Colorize Mask" msgstr "" #: ../../tutorials/flat-coloring.rst:287 msgid "" "So, this is a bit of an odd one. In the original tutorial, you'll see I'm " "suggesting using G'Mic, but that was a few years ago, and g'mic is a little " "unstable on windows. Therefore, the Krita developers have been attempting to " "make an internal tool doing the same." msgstr "" #: ../../tutorials/flat-coloring.rst:289 msgid "" "It is disabled in 3.1, but if you use 4.0 or later, it is in the toolbox. " "Check the Colorize Mask for more information." msgstr "" #: ../../tutorials/flat-coloring.rst:291 msgid "So it works like this:" msgstr "" #: ../../tutorials/flat-coloring.rst:293 msgid "Select the colorize mask tool." msgstr "" #: ../../tutorials/flat-coloring.rst:294 msgid "Tick the layer you're using." msgstr "" #: ../../tutorials/flat-coloring.rst:295 msgid "Paint the colors your want to use on the colorize mask" msgstr "" #: ../../tutorials/flat-coloring.rst:296 msgid "Click update to see the results:" msgstr "" #: ../../tutorials/flat-coloring.rst:301 msgid "" "When you are satisfied, |mouseright| the colorize mask, and go to :" "menuselection:`Convert --> Paint Layer`. This will turn the colorize mask to " "a generic paint layer. Then, you can fix the last issues by aking the " "lineart semi-transparent and painting the flaws away with a pixel art brush." msgstr "" #: ../../tutorials/flat-coloring.rst:306 msgid "" "Then, when you are done, split the layers via :menuselection:`Layers --> " "Split --> Split Layer`. There's a few options you can choose, but the " "following should be fine:" msgstr "" #: ../../tutorials/flat-coloring.rst:311 msgid "" "Finally, press **Ok** and you should get the following. Each color patch it " "on a different layer, named by the palette in the menu and alpha locked, so " "you can start painting right away!" msgstr "" #: ../../tutorials/flat-coloring.rst:319 msgid "" "Works with anti aliased lineart. Really quick to get the base work done. Can " "auto-close gaps." msgstr "" #: ../../tutorials/flat-coloring.rst:324 msgid "" "No anti aliasing of it’s own. You have to choose between getting details " "right or the gaps auto-closed." msgstr "" #: ../../tutorials/flat-coloring.rst:327 msgid "Conclusion" msgstr "" #: ../../tutorials/flat-coloring.rst:329 msgid "" "I hope this has given you a good idea of how to fill in flats using the " "various techniques, as well as getting a hand of different Krita features. " "Remember that a good flat filled lineart is better than a badly shaded one, " "so keep practising to get the best out of these techniques!" msgstr "" diff --git a/locale/ja/LC_MESSAGES/user_manual/loading_saving_brushes.po b/locale/ja/LC_MESSAGES/user_manual/loading_saving_brushes.po index 034a40e51..f20c53b09 100644 --- a/locale/ja/LC_MESSAGES/user_manual/loading_saving_brushes.po +++ b/locale/ja/LC_MESSAGES/user_manual/loading_saving_brushes.po @@ -1,942 +1,942 @@ msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-03-12 03:34+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\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" #: ../../user_manual/loading_saving_brushes.rst:0 msgid ".. image:: images/en/Krita_4_0_dirty_preset_icon.png" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:None msgid ".. image:: images/en/Krita_4_0_Brush_Settings_Layout.svg" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:17 msgid "Loading and Saving Brushes" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:37 msgid "The Brush settings dropdown" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:44 msgid "" "When you open Brush Settings Editor panel you will see something like this:" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:48 msgid "Tour of the brush settings dropdown" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:53 msgid "The brush settings drop down is divided into six areas," msgstr "" #: ../../user_manual/loading_saving_brushes.rst:56 msgid "Section A - General Information" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:79 msgid "Engine" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:94 msgid "Reloading" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:101 msgid "Saving a preset" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:103 msgid "" "On the right, there's :guilabel:`Save New Brush Preset` and :guilabel:" "`Overwrite Brush`." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:108 msgid "Overwrite Brush" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:113 msgid "Save New Brush Preset" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:119 msgid ".. image:: images/en/Krita_4_0_Save_New_Brush_Preset_Dialog.png" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:125 msgid "Brush Name" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:127 msgid "Load Existing Thumbnail" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:128 msgid "This will load the existing thumbnail inside the preset." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:130 msgid "Load scratch pad thumbnail" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:132 msgid "Load Image" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:133 msgid "With this you can choose an image from disk to load as a thumbnail." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:134 msgid "Load from Icon Library" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:135 msgid "This opens up the icon library." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:137 msgid "Clear Thumbnail" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:137 msgid "This will make the mini scratch pad white." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:140 msgid "The Icon Library" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:142 msgid "To make making presets icons faster, Krita got an icon library." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:145 msgid ".. image:: images/en/Krita_4_0_Preset_Icon_Library_Dialog.png" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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, ad the lowest slider is a super simple levels filter. " +"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 "" #: ../../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." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:167 msgid "Section B - The Preset Chooser" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:169 msgid "" "The preset chooser is much the same as the preset docker and the preset " "dropdown 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 "" #: ../../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 "" #: ../../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 "" #: ../../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 for that " -"engine." +"list of Krita's engines. Selecting an engine from the list will show the " +"brushes for that engine." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:185 msgid "" -"The trashcan icon does the same as it does in the preset docker: delete , or " +"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 "" #: ../../user_manual/loading_saving_brushes.rst:189 msgid "Section C - The Scratch pad" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:202 msgid "The scratch pad has five buttons underneath it. These are in order for:" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:204 msgid "Showing the current brush image" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:206 msgid "Adding a gradient to the scratch pad (useful for smudge brushes)" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:207 msgid "Filling with the background color" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:208 msgid "Clearing everything on the scratch pad." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:211 msgid "Section D - The Options List" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:227 msgid "Section E - Option Configuration Widget" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:233 msgid "Using sensor curves" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:260 msgid "Underneath the curve widget there are two more options:" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:264 msgid "Share Curves across all settings" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:271 msgid "Multiply" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:272 msgid "Will multiply the two values, 0.5\\*0.7 = 0.35" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:274 msgid "Addition" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:277 msgid "Maximum" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:280 msgid "Minimum" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:283 msgid "Will subtract the smallest value from the largest, so 0.7-0.5 = 0.2" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:284 msgid "Curves Calculation Mode" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:284 msgid "Difference" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:286 msgid "It's maybe better to see with the following example:" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:289 msgid ".. image:: images/en/Krita_4_0_brush_curve_calculation_mode.png" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:290 msgid "" "The first two are regular, the rest with different multiplication types." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:292 msgid "Is a brush with size set to the distance sensor." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:293 msgid "Is a brush with the size set to the fade sensor." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:294 msgid "The size is calculated from the fade and distance sensors multiplied." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:297 msgid "" "The size takes the maximum value from the values of the fade and distance " "sensors." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:299 msgid "" -"The size takes the minimum value from the values of the face and distance " +"The size takes the minimum value from the values of the fade and distance " "sensors." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:305 msgid "Section F - Miscellaneous options" msgstr "" #: ../../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, the revert to default. " "Dirtied presets can be recognized by the icon in the top-left of the preset." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:316 msgid "Temporarily Save Tweaks to Preset (Dirty Presets)" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:319 msgid "Eraser Switch Size" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:319 msgid "" "This switches the brush to a separately stored size when using the :kbd:`E` " "key." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:321 msgid "Eraser Switch Opacity" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:322 msgid "Same as above, but then with Eraser opacity." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:330 msgid "Instant Preview" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:333 msgid "The On-canvas brush settings" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:347 msgid "Making a Brush Preset" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:349 msgid "Now, let's make a simple brush to test the waters with:" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:352 msgid "Getting a default for the brush engine." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:354 msgid "First, open the settings with :kbd:`F5`." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:361 msgid "Example: Making an inking brush" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:370 -msgid "Uncheck the :guilabel:`enable pen settings` checkbox." +msgid "Uncheck the :guilabel:`Enable Pen Settings` checkbox." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:377 msgid "" -"Uncheck the :guilabel:`enable pen settings` checkbox here as well. Test " +"Uncheck the :guilabel:`Enable Pen Settings` checkbox here as well. Test " "again." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:401 msgid "Saving the new Brush" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:403 msgid "" "When you're satisfied, go to the upper left and select :guilabel::`Save new " "preset`." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:414 msgid "Finally press :guilabel:`Save`, and your brush should be done." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:416 msgid "You can further modify your inking brush by..." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:422 msgid "Making the fine lines look even softer by using the flow option." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:422 msgid "" "To do this, select the flow option, and turn back on the 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 "" #: ../../user_manual/loading_saving_brushes.rst:425 msgid "Sharing Brushes" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:438 msgid "Sharing a single preset" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:440 msgid "There are three types of resources a single preset can take:" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:446 msgid "A Pattern file: this is when you are using textures." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:452 msgid "" "To find those resources, go to :menuselection:`Settings --> Manage Resources " "--> Open Resource Folder`." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:458 msgid "Importing a single KPP file." msgstr "" #: ../../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 "" #: ../../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 " "dropdown (: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 "" #: ../../user_manual/loading_saving_brushes.rst:471 msgid "Sharing via ZIP (old-fashioned)" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:477 msgid "Using a ZIP with the relevant files." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:479 msgid "" "Go to :menuselection:`Settings --> Manage Resources --> Open Resource " "Folder` to open the resource folder." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:480 msgid "Then, open up the zip file." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:484 msgid "Restart Krita" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:485 msgid "Enjoy your brushes!" msgstr "" diff --git a/locale/ja/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po b/locale/ja/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po index feeb6245c..86e9404f8 100644 --- a/locale/ja/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po +++ b/locale/ja/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po @@ -1,283 +1,283 @@ msgid "" msgstr "" "Project-Id-Version: Krita Manual 4.1\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-03-06 03:37+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\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" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:1 msgid "Introduction to using Krita's python plugin API." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:18 msgid "Introduction to Python Scripting" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:22 msgid "" "When we offered python scripting as one of Kickstarter Stretchgoals we could " "implement next to vectors and text, it won the backer vote by a landslide. " "Some people even only picked python and nothing else. So what exactly is " "python scripting?" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:25 msgid "What is Python Scripting?" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:27 msgid "" "Python is a scripting language, that can be used to automate tasks. What " "python scripting in Krita means is that we added an API to krita, which is a " "bit of programming that allows python to access to parts of Krita. With this " "we can make dockers, perform menial tasks on a lot of different files and " "even write our own exporters. People who work with computer graphics, like " "VFX and video game artists use python a lot to make things like sprite " "sheets, automate parts of export and more." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:29 msgid "" "It is outside the scope of this manual to teach you python itself. However, " "as python is an extremely popular programming language and great for " "beginners, there's tons of learning material around that can be quickly " "found with a simple 'learn python' internet search." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:31 msgid "" "This manual will instead focus on how to use python to automate and extend " "Krita. For that we'll first start with the basics: How to run Python " "commands in the scripter." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:35 msgid "How to Enable the Scripter Plugin" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:37 msgid "" "The scripter plugin is not necessary to use python, but it is very useful " "for testing and playing around with python. It is a python console, written " "in python, which can be used to write small scripts and execute them on the " "fly." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:39 msgid "" "To open the scripter, navigate to :menuselection:`Tools --> Scripts --> " "Scripter`. If you don't see it listed, go to :menuselection:`Settings --> " "Configure Krita --> Python Plugin Manager` and toggle \"Scripter\" in the " "list to enable it. If you don't see the scripter plugin, make sure you are " "using an up-to-date version of Krita." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:41 msgid "" "The scripter will pop up with a text editor window on top and an output " "window below. Input the following in the text area:" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:48 msgid "" "Press the big play button or press :kbd:`Ctrl + R` to run the script. Then, " "below, in the output area the following should show up::" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:53 msgid "" "Now we have a console that can run functions like print() from the Python " "environment - but how do we use it to manage Krita?" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:56 msgid "Running basic Krita commands" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:58 msgid "" "To allow Python to communicate with Krita, we will use the Krita module. At " "the top of every script, we will write: ``from krita import *``" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:60 msgid "" "This allows us to talk to Krita through ``Krita.instance()``. Let's try to " "double our coding abilities with Python." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:68 msgid "" "You should see a second scripter window open. Pretty neat! Here is a " "slightly more advanced example." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:77 msgid "" "This will open up a new document. Clearly Python gives you quite a lot of " "control to automate Krita. Over time we expect the community to write all " "kinds of scripts that you can use simply by pasting them in the scripter." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:79 msgid "" "But what if you want to write new commands for yourself? The best place to " "start is very simple: search for examples written by other people! You can " "save a lot of time if someone else has written code that you can base your " "work on. It's also worth looking through the python plugins, which are " "located in /share/krita/pykrita. There's also a step by step guide for :ref:" "`krita_python_plugin_howto` here in the manual." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:81 msgid "" "But it's likely that you need more information. For that, we will need see " "what's hidden behind the asterisk when you ``import * from Krita``. To learn " "what Krita functions that are available and how to use them, you will want " "to go for Krita API reference documentation." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:84 msgid "Krita's API" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:86 msgid "" "`LibKis API Overview `_" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:87 msgid "" "`Krita class documentation `_" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:89 msgid "" "Those pages may look like a lot of jargon at first. This is because Krita's " "API documentation comes from the underlying C++ language that Krita is " "written in. The magic happens because of a Python tool called SIP, which " "makes it possible for python speak in C++ and talk to Krita. The end result " "is that when we ``import krita`` and call functions, we're actually using " "the C++ methods listed in that documentation." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:91 msgid "" "Let's see how this stuff works in more detail. Let's take a look at the " "second link, the `Krita class reference `_. There we can see all the " "functions available to the Krita instance. If you type dir(Krita.instance()) " "in Python, it should match this page very closely - you can view the " "documentation of the functions createDocument(), activeWindow(), and " "action() which we used above." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:93 msgid "" "One of the more confusing things is seeing all the C++ classes that Krita " -"uses, including the Qt classes that start with Q. But here is the beauty fo " +"uses, including the Qt classes that start with Q. But here is the beauty of " "SIP: it tries to make the translation from these classes into Python as " "simple and straightforward as possible. For example, you can see that the " "function filters() returns a QStringList. However, SIP converts those " "QStringLists into regular python list of strings!" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:101 msgid "Outputs as ::" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:112 msgid "However, sometimes the conversion doesn't go quite as smoothly." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:120 msgid "gives something like this::" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:127 msgid "" "It is a list of something, sure, but how to use it? If we go back to the " "Krita apidocs page and look at the function, documents() we'll see there's " "actually a clickable link on the 'Document' class. `If you follow that link " "`_, you'll see that the document has a function called " "name() which returns the name of the document, and functions width() and " "height() which return the dimensions. So if we wanted to generate an info " "report about the documents in Krita, we could write a script like this:" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:137 msgid "we get an output like::" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:147 msgid "" "Hopefully this will give you an idea of how to navigate the API docs now." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:149 msgid "" "Krita's API has many more classes, you can get to them by going to the top-" "left class list, or just clicking their names to get to their API docs. The " "functions print() or dir() are your friends here as well. This line will " "print out a list of all the actions in Krita - you could swap in one of " "these commands instead of 'python_scripter' in the example above." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:155 msgid "" "The Python module ``inspect`` was designed for this sort of task. Here's a " "useful function to print info about a class to the console." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:167 msgid "" "Finally, in addition to the LibKis documentation, the Qt documentation, " "since Krita uses PyQt to expose nearly all of the Qt API to Python. You can " "build entire windows with buttons and forms this way, using the very same " "tools that Krita is using! You can read the `Qt documentation `_ and the `PyQt documentation `_ for more info about this, and also definitely study the included plugins " "as well to see how they work." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:171 msgid "Technical Details" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:177 msgid "Python Scripting on Windows" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:179 msgid "" "To get Python scripting working on Windows 7/8/8.1, you will need to install " "the `Universal C Runtime from Microsoft's website `_. (Windows 10 already comes with it.)" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:182 msgid "Python 2 and 3" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:184 msgid "By default Krita is compiled for python 3." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:186 msgid "" "However, it is possible to compile it with python 2. To do so, you will need " "to add the following to the cmake configuration line::" 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 9c4329405..f38dc5ce4 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-03-12 03:34+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\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 it's 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 1c214c410..c4a114b86 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,1068 +1,1068 @@ # 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-03-13 03:40+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\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 colour " "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 colour." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:71 msgid "" "Finally, group 4 has Vermillion red, citron yellow and cerulean blue. Their " "colours 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 colour 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 " "colour translate properly between color devices." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:82 msgid "" "It usually works by attempting to covert a colour to the reference colour " "space XYZ. XYZ is a coordinate system that has a spot for all colours 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 colour 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:88 msgid "" "To give a crude estimate, ICC profiles deal with keeping colours consistent " "over many interpretations of devices (screens, printers) by using a " "reference space, and OCIO deals with manipulating the interpretation of said " "colours." 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 grey it produces. Using " "these and several other measurements it creates an icc profile unique to " "your screen. You set these in Krita's colour 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 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-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.)" 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 colour 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 colorspace 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 colour reproduction. Use this if you want to " "see all colours 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 colours at whatever cost, which may result in awful looking " "colours. 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 "" "A in between solution between perceptual and absolute, relative will try to " "fit whatever colours it can match between colour 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 colourfulness, 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 '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." 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 colour 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 colour 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 colour 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 " "customly 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 colour maths, often concerning the blending of colours. " "This colour maths works best in linear colour space, and linear colour 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 colour 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 " "colour 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's 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 colours actually look strange: This is a " "bug in Firefox, which is because its `color management system is incomplete " "`_, save your png, jpg or tiff without an embedded profile to work " "around this." 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 " "bitdepth 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 specialised 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, mypaint, mangastudio, 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, mangastudio " "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 optimisers. 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 "" "Specialised 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 --> 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." 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 optimised content, and it's recommended to " "stay within 8bit, future screens may have higher bitdepths, 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 optimise 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 "" "`Visualising the XYZ colorspace `_" 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 colormanagement from argylcms manual `_" msgstr "" diff --git a/locale/nl/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po b/locale/nl/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po index 56b9d3545..b4145fdaf 100644 --- a/locale/nl/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po +++ b/locale/nl/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po @@ -1,214 +1,214 @@ # 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-02-23 03:24+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-02-23 23: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" #: ../../:1 msgid "Use Undeformed Image" msgstr "Niet vervormde afbeelding gebruiken" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:1 msgid "The Deform Brush Engine manual page." msgstr "De handleidingpagina vervormendepenseel-engine." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:16 msgid "Deform Brush Engine" msgstr "Vervormendepenseel-engine" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:19 msgid ".. image:: images/icons/deformbrush.svg" msgstr ".. image:: images/icons/deformbrush.svg" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:20 msgid "" "The Deform Brush is a brush that allows you to pull and push pixels around. " "It's quite similar to the :ref:`liquify_mode`, but where liquify has higher " "quality, the deform brush has the speed." msgstr "" "De vervormendepenseel is een penseel die u in staat stelt om willekeurig " "pixels te trekken en te duwen. Het is tamelijk gelijk aan het :ref:" "`liquify_mode`, maar waar liquefy een hogere kwaliteit heeft, heeft de " "vervormendepenseel snelheid." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:24 msgid "Options" msgstr "Opties" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:26 msgid ":ref:`option_brush_tip`" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:27 msgid ":ref:`option_deform`" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:28 msgid ":ref:`blending_modes`" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:29 msgid ":ref:`option_opacity_n_flow`" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:30 msgid ":ref:`option_size`" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:31 msgid ":ref:`option_rotation`" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:32 msgid ":ref:`option_airbrush`" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:38 msgid "Deform Options" msgstr "Vervormingsopties" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:42 msgid ".. image:: images/en/Krita_deform_brush_examples.png" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:42 msgid "" "1: undeformed, 2: Move, 3: Grow, 4: Shrink, 5: Swirl Counter Clock Wise, 6: " "Swirl Clockwise, 7: Lens Zoom In, 8: Lens Zoom Out" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:44 msgid "These decide what strangeness may happen underneath your brush cursor." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:46 msgid "Grow" msgstr "Groeien" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:47 msgid "This bubbles up the area underneath the brush-cursor." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:48 msgid "Shrink" msgstr "Krimpen" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:49 msgid "This pinches the Area underneath the brush-cursor." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:50 msgid "Swirl Counter Clock Wise" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:51 msgid "Swirls the area counter clock wise." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:52 msgid "Swirl Clock Wise" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:53 msgid "Swirls the area clockwise." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:54 msgid "Move" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:55 msgid "Nudges the area to the painting direction." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:56 msgid "Color Deformation" msgstr "Kleurdeformatie" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:57 -msgid "This seems to randomly rearrange the pixels underneath the brush," +msgid "This seems to randomly rearrange the pixels underneath the brush." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:58 msgid "Lens Zoom In" msgstr "Inzoomen van de lens" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:59 msgid "Literally paints a enlarged version of the area." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:61 msgid "Lens Zoom Out" msgstr "Uitzoomen van de lens" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:61 msgid "Paints a minimized version of the area." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:65 msgid ".. image:: images/en/Krita_deform_brush_colordeform.png" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:65 msgid "Showing color deform." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:68 msgid "Deform Amount" msgstr "Vervormingshoeveelheid:" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:68 msgid "Defines the strength of the deformation." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:72 msgid ".. image:: images/en/Krita_deform_brush_bilinear.png" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:72 #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:74 msgid "Bilinear Interpolation" msgstr "Bi-lineaire interpolatie" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:75 msgid "Smoothens the result. This causes calculation errors in 16bit." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:77 msgid "Use Counter" msgstr "Teller gebruiken" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:77 msgid "Slows down the deformation subtlety." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:81 msgid ".. image:: images/en/Krita_deform_brush_useundeformed.png" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:81 msgid "Without 'use undeformed' to the left and with to the right" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:84 msgid "" "Samples from the previous version of the image instead of the current. This " "works better with some deform options than others. Move for example seems to " "almost stop working, but it works really well with Grow." msgstr "" diff --git a/locale/nl/LC_MESSAGES/reference_manual/layers_and_masks/layer_styles.po b/locale/nl/LC_MESSAGES/reference_manual/layers_and_masks/layer_styles.po index 1cbc4697e..c16b706fc 100644 --- a/locale/nl/LC_MESSAGES/reference_manual/layers_and_masks/layer_styles.po +++ b/locale/nl/LC_MESSAGES/reference_manual/layers_and_masks/layer_styles.po @@ -1,56 +1,56 @@ # 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-02-19 03:36+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-02-25 12:35+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" #: ../../reference_manual/layers_and_masks/layer_styles.rst:1 msgid "How to use layer styles in Krita." msgstr "Hoe laagstijlen in Krita gebruiken." #: ../../reference_manual/layers_and_masks/layer_styles.rst:17 msgid "Layer Styles" msgstr "Laagstijlen" #: ../../reference_manual/layers_and_masks/layer_styles.rst:19 msgid "" "Layer styles are effects that are added on top of your layer. They are " "editable and can easily be toggled on and off. To add a layer style to a " "layer go to :menuselection:`Layer --> Layer Style`. You can also right-click " "a layer to access the layer styles." msgstr "" #: ../../reference_manual/layers_and_masks/layer_styles.rst:22 msgid "" -"When you have the layer styles window up, make sure that the \"Enable Effects" -"\" is checked." +"When you have the layer styles window up, make sure that the :guilabel:" +"`Enable Effects` item is checked." msgstr "" #: ../../reference_manual/layers_and_masks/layer_styles.rst:24 msgid "" "There are a variety of effects and styles you can apply to a layer. When you " "add a style, your layer docker will show an extra \"Fx\" icon. This allows " "you to toggle the layer style effects on and off." msgstr "" #: ../../reference_manual/layers_and_masks/layer_styles.rst:30 msgid "" "This feature was added to increase support for :program:`Adobe Photoshop`. " "The features that are included mirror what that application supports." msgstr "" diff --git a/locale/nl/LC_MESSAGES/reference_manual/render_animation.po b/locale/nl/LC_MESSAGES/reference_manual/render_animation.po index 1f3f9e0d7..16bda1e99 100644 --- a/locale/nl/LC_MESSAGES/reference_manual/render_animation.po +++ b/locale/nl/LC_MESSAGES/reference_manual/render_animation.po @@ -1,304 +1,304 @@ # 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-02-25 03:36+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-02-26 13:44+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" #: ../../reference_manual/render_animation.rst:1 msgid "How to use the render animation command in Krita." msgstr "Hoe het commando voor renderanimatie in Krita gebruiken." #: ../../reference_manual/render_animation.rst:17 #: ../../reference_manual/render_animation.rst:42 msgid "Render Animation" msgstr "Animatie renderen" #: ../../reference_manual/render_animation.rst:19 msgid "" "Render animation allows you to render your animation to an image sequence, " "gif, mp4, mkv, or ogg file. It replaces :guilabel:`Export Animation` ." msgstr "" #: ../../reference_manual/render_animation.rst:21 msgid "" "For rendering to an animated fileformat, Krita will first render to a png " "sequence and then use FFMpeg, which is really good at encoding into video " "files, to render that sequence to an animated fileformat. The reason for " "this two-step process is that animation files can be really complex and " "really big, and this is the best way to allow you to keep control over the " "export process. For example, if your computer has a hiccup, and one frame " "saves out weird, first saving the image sequence allows you to only resave " "that one weird frame before rendering." msgstr "" #: ../../reference_manual/render_animation.rst:23 msgid "" "This means that you will need to find a good place to stick your frames " "before you can start rendering. If you only do throwaway animations, you can " "use a spot on your hard-drive with enough room and select :guilabel:`Delete " "Sequence After Rendering`" msgstr "" #: ../../reference_manual/render_animation.rst:26 msgid "Image Sequence" msgstr "Volgorde afbeeldingen" #: ../../reference_manual/render_animation.rst:28 msgid "Base Name" msgstr "Basisnaam" #: ../../reference_manual/render_animation.rst:29 msgid "" "The base name of your image sequence. This will get suffixed with a number " "depending on the frame." msgstr "" #: ../../reference_manual/render_animation.rst:30 msgid "File Format" msgstr "Bestandsformaat" #: ../../reference_manual/render_animation.rst:31 msgid "" "The fileformat to export the sequence to. When rendering we enforce png. The " "usual export options can be modified with :guilabel:`...`." msgstr "" #: ../../reference_manual/render_animation.rst:32 msgid "Render Location" msgstr "" #: ../../reference_manual/render_animation.rst:33 msgid "" "Where you render the image sequence to. Some people prefer to use a flash-" "drive or perhaps a harddrive that is fast." msgstr "" #: ../../reference_manual/render_animation.rst:34 msgid "First Frame" msgstr "Eerste frame" #: ../../reference_manual/render_animation.rst:35 msgid "" "The first frame of the range of frame you wish to adjust. Automatically set " "to the first frame of your current selection in the timeline. This is useful " "when you only want to re-render a little part." msgstr "" #: ../../reference_manual/render_animation.rst:36 msgid "Last Frame" msgstr "Laatste frame" #: ../../reference_manual/render_animation.rst:37 msgid "" "As above, the last frame of the range of frame you wish to adjust. " "Automatically set to the last frame of your current selection in the " "timeline." msgstr "" #: ../../reference_manual/render_animation.rst:39 msgid "Naming Sequence starts with" msgstr "" #: ../../reference_manual/render_animation.rst:39 msgid "" "The frames are named by using :guilabel:`Base Name` above and adding a " "number for the frame. This allows you to set where the frame number starts, " "so rendering from 8 to 10 with starting point 3 will give you images named " "11 and 15. Useful for programs that don't understand sequences starting with " "0, or for precision output." msgstr "" #: ../../reference_manual/render_animation.rst:44 msgid "Render As" msgstr "Renderen als" #: ../../reference_manual/render_animation.rst:45 msgid "" "The file format to render to. All except gif have extra options that can be " "manipulated via :guilabel:`...`." msgstr "" #: ../../reference_manual/render_animation.rst:46 msgid "File" msgstr "" #: ../../reference_manual/render_animation.rst:47 msgid "Location and name of the rendered animation." msgstr "" #: ../../reference_manual/render_animation.rst:48 msgid "FFMpeg" msgstr "FFMpeg" #: ../../reference_manual/render_animation.rst:49 msgid "" "The location where your have ffmpeg. If you don't have this, Krita cannot " "render an animation. For proper gif support, you will need ffmpeg 2.6, as we " "use its palettegen functionality." msgstr "" #: ../../reference_manual/render_animation.rst:51 msgid "Delete Sequence After Rendering" msgstr "" #: ../../reference_manual/render_animation.rst:51 msgid "" "Delete the prerendered image sequence after done rendering. This allows you " "to choose whether to try and save some space, or to save the sequence for " "when encoding fails." msgstr "" #: ../../reference_manual/render_animation.rst:55 msgid "" "None of the video formats support saving from images with a transparent " "background, so Krita will try to fill it with something. You should add a " "background color yourself to avoid it from using, say, black." msgstr "" #: ../../reference_manual/render_animation.rst:58 msgid "Setting Up Krita for Exporting Animations" msgstr "" #: ../../reference_manual/render_animation.rst:60 msgid "" "You will need to download an extra application and link it in Krita for it " "to work. The application is pretty big (50MB), so the Krita developers " "didn't want to bundle it with the normal application. The software that we " "will use is free and called FFMpeg. The following instructions will explain " "how to get it and set it up. The setup is a one-time thing so you won't have " "to do it again." msgstr "" #: ../../reference_manual/render_animation.rst:63 msgid "Step 1 - Downloading FFMpeg" msgstr "" #: ../../reference_manual/render_animation.rst:66 #: ../../reference_manual/render_animation.rst:86 msgid "For Windows" msgstr "" #: ../../reference_manual/render_animation.rst:68 msgid "" "Go to the ffmpeg website (http://ffmpeg.org/download.html). The URL that had " "the link for me was here... https://ffmpeg.zeranoe.com/builds/" msgstr "" #: ../../reference_manual/render_animation.rst:70 msgid "" -"Watch out for the extremely annoying google ad that looks like a download " +"Watch out for the extremely annoying google and that looks like a download " "button! There is no big button for what we need. Either get the 64-bit " "STATIC version or 32-bit STATIC version that is shown later down the page. " "If you bought a computer in the past 5 years, you probably want the 64-bit " "version. Make sure you get a exe file, if you hover over the options they " "will give more information about what exactly you are downloading." msgstr "" #: ../../reference_manual/render_animation.rst:73 #: ../../reference_manual/render_animation.rst:93 msgid "For OSX" msgstr "" #: ../../reference_manual/render_animation.rst:75 msgid "" "Please see the section above. However, FFmpeg is obtained from https://" "evermeet.cx/ffmpeg/ instead. Just pick the big green button on the left " "under the FFmpeg heading. You will also need an archiving utility that " "supports .7z, since ffmpeg provides their OSX builds in .7z format. If you " "don't have one, try something like Keka (http://www.kekaosx.com)." msgstr "" #: ../../reference_manual/render_animation.rst:78 #: ../../reference_manual/render_animation.rst:98 msgid "For Linux" msgstr "" #: ../../reference_manual/render_animation.rst:80 msgid "" "FFMPeg can be installed from the repositories on most Linux systems. Version " "2.6 is required for proper gif support, as we use the palettegen " "functionality." msgstr "" #: ../../reference_manual/render_animation.rst:83 msgid "Step 2 - Unzipping and Linking to Krita" msgstr "" #: ../../reference_manual/render_animation.rst:88 msgid "" "Unzip the package that was just downloaded. Rename the long folder name to " "just ffmpeg. Let's put this folder in a easy to find location. go to your C:" "\\ and place it there. You can put it wherever you want, but that is where I " "put it." msgstr "" #: ../../reference_manual/render_animation.rst:90 msgid "" "Open Krita back up and go to :menuselection:`File --> Render Animation`. " "Click the :guilabel:`Browse` button on the last item called FFMpeg. Select " "this file ``C:/ffmpeg/bin/ffmpeg.exe`` and click :guilabel:`OK` ." msgstr "" #: ../../reference_manual/render_animation.rst:95 msgid "" "After downloading ffmpeg, you just need to extract it and then simply point " "to it in the FFMPEG location in Krita like ``/Users/user/Downloads/ffmpeg`` " "(assuming you downloaded and extracted the .7z file to /Users/user/" "Downloads)." msgstr "" #: ../../reference_manual/render_animation.rst:100 msgid "" "FFMpeg is, if installed from the repositories, usually found in ``/usr/bin/" "ffmpeg``" msgstr "" #: ../../reference_manual/render_animation.rst:103 msgid "Step 3 - Testing out an animation" msgstr "" #: ../../reference_manual/render_animation.rst:105 msgid "" "ffmpeg.exe is what Krita uses to do all of its animation export magic. Now " "that it is hooked up, let us test it out." msgstr "" #: ../../reference_manual/render_animation.rst:107 msgid "" "Let's make an animated GIF. in the Render Animation dialog, change the :" "guilabel:`Render As` field to \"GIF image\". Choose the file location where " "it will save with the \"File\" menu below. I just saved it to my desktop and " "called it \"export.gif\". When it is done, you should be able to open it up " "and see the animation." msgstr "" #: ../../reference_manual/render_animation.rst:111 msgid "" "By default, FFMPEG will render MP4 files with a too new codec, which means " "that windows media player won't be able to play it. So for windows, select " "\"baseline\" for the profile instead of \"high422\" before rendering." msgstr "" #: ../../reference_manual/render_animation.rst:115 msgid "" "OSX does not come with any software to play MP4 and MKV files. If you use " "Chrome for your web browser, you can drag the video file into that and the " "video should play. Otherwise you will need to get a program like VLC to see " "the video." msgstr "" diff --git a/locale/nl/LC_MESSAGES/reference_manual/tools/colorize_mask.po b/locale/nl/LC_MESSAGES/reference_manual/tools/colorize_mask.po index f9b1f6cb4..1ad4ebd53 100644 --- a/locale/nl/LC_MESSAGES/reference_manual/tools/colorize_mask.po +++ b/locale/nl/LC_MESSAGES/reference_manual/tools/colorize_mask.po @@ -1,452 +1,452 @@ # 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-03-13 03:40+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-02-27 10:28+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: muisrechts" #: ../../:8 msgid "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" msgstr "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" #: ../../:60 msgid "" ".. image:: images/icons/colorizemask_tool.svg\n" " :alt: toolcolorizemask" msgstr "" ".. image:: images/icons/colorizemask_tool.svg\n" " :alt: toolcolorizemask" -#: ../../reference_manual/tools/colorize_mask.rst:0 -msgid "" -".. image:: images/en/Krita_4_0_colorize_mask_show_output_edit_strokes.png" -msgstr "" -".. image:: images/en/Krita_4_0_colorize_mask_show_output_edit_strokes.png" - -#: ../../reference_manual/tools/colorize_mask.rst:0 -msgid ".. image:: images/en/Krita_4_0_colorize_mask_edge_detection.png" -msgstr ".. image:: images/en/Krita_4_0_colorize_mask_edge_detection.png" - -#: ../../reference_manual/tools/colorize_mask.rst:0 -msgid ".. image:: images/en/Krita_4_0_colorize_mask_gap_close_hint.png" -msgstr ".. image:: images/en/Krita_4_0_colorize_mask_gap_close_hint.png" - -#: ../../reference_manual/tools/colorize_mask.rst:0 -msgid ".. image:: images/en/Krita_4_0_colorize_mask_clean_up.png" -msgstr ".. image:: images/en/Krita_4_0_colorize_mask_clean_up.png" - #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_01.png" msgstr ".. image:: images/en/Krita_4_0_colorize_mask_usage_01.png" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_02.png" msgstr ".. image:: images/en/Krita_4_0_colorize_mask_usage_02.png" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_03.png" msgstr ".. image:: images/en/Krita_4_0_colorize_mask_usage_03.png" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_04.png" msgstr ".. image:: images/en/Krita_4_0_colorize_mask_usage_04.png" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_05.png" msgstr ".. image:: images/en/Krita_4_0_colorize_mask_usage_05.png" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_06.png" msgstr ".. image:: images/en/Krita_4_0_colorize_mask_usage_06.png" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_07.png" msgstr ".. image:: images/en/Krita_4_0_colorize_mask_usage_07.png" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_08.png" msgstr ".. image:: images/en/Krita_4_0_colorize_mask_usage_08.png" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_09.png" msgstr ".. image:: images/en/Krita_4_0_colorize_mask_usage_09.png" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_10.png" msgstr ".. image:: images/en/Krita_4_0_colorize_mask_usage_10.png" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_11.png" msgstr ".. image:: images/en/Krita_4_0_colorize_mask_usage_11.png" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_12.png" msgstr ".. image:: images/en/Krita_4_0_colorize_mask_usage_12.png" +#: ../../reference_manual/tools/colorize_mask.rst:0 +msgid "" +".. image:: images/en/Krita_4_0_colorize_mask_show_output_edit_strokes.png" +msgstr "" +".. image:: images/en/Krita_4_0_colorize_mask_show_output_edit_strokes.png" + +#: ../../reference_manual/tools/colorize_mask.rst:0 +msgid ".. image:: images/en/Krita_4_0_colorize_mask_edge_detection.png" +msgstr ".. image:: images/en/Krita_4_0_colorize_mask_edge_detection.png" + +#: ../../reference_manual/tools/colorize_mask.rst:0 +msgid ".. image:: images/en/Krita_4_0_colorize_mask_gap_close_hint.png" +msgstr ".. image:: images/en/Krita_4_0_colorize_mask_gap_close_hint.png" + +#: ../../reference_manual/tools/colorize_mask.rst:0 +msgid ".. image:: images/en/Krita_4_0_colorize_mask_clean_up.png" +msgstr ".. image:: images/en/Krita_4_0_colorize_mask_clean_up.png" + #: ../../reference_manual/tools/colorize_mask.rst:1 msgid "How to use the colorize mask in Krita." msgstr "Hoe het inkleurmasker gebruiken in Krita." #: ../../reference_manual/tools/colorize_mask.rst:16 msgid "Colorize Mask" msgstr "Inkleurmasker" #: ../../reference_manual/tools/colorize_mask.rst:18 msgid "|toolcolorizemask|" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:20 msgid "" "A tool for quickly coloring lineart, the Colorize Mask Editing tool can be " "found next to the gradient tool on your toolbox." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:22 msgid "" "This feature is technically already in 3.1, but disabled by default because " "we had not optimised the filling algorithm for production use yet. To enable " "it, find your krita configuration file, open it in notepad, and add " "\"disableColorizeMaskFeature=false\" to the top. Then restart Krita. Its " "official incarnation is in 4.0." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:26 msgid "Usage" msgstr "Gebruik" #: ../../reference_manual/tools/colorize_mask.rst:28 msgid "" "This tool works in conjunction with the colorize mask, and the usage is as " "follows:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:30 msgid "" "For this example, we'll be using the ghost lady also used to explain masks " "on the basic concepts page." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:36 msgid "" "This image has the line art for the lady separated from the background, and " "what's more, the background is made up of two layers: one main and one for " "the details." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:38 msgid "" "First, select the colorize mask editing tool while having the lineart layer " "selected. |mouseleft| the canvas will add a colorize mask to the layer. You " "can also |mouseright| the line art layer, and then :menuselection:`Add --> " "Colorize Mask`. The line art will suddenly become really weird, this is the " "prefiltering which are filters through which we put the lineart to make the " "algorithm easier to use. The tool options overview below shows which options " "control that." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:45 msgid "" "Now, You make strokes with brush colors, press :guilabel:`Update` in the " "tool options, or tick the last icon of the colorize mask properties. In the " "layer docker, you will be able to see a little progress bar appear on the " "colorize mask indicating how long it takes. The bigger your file, the longer " "it will take." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:51 msgid "" "We want to have the blue transparent. In the tool options of the colorize " "editing tool you will see a small palette. These are the colors already " "used. You can remove colors here, or mark a single color as standing for " "transparent, by selecting it and pressing \"transparent\". Updating the mask " "will still show the blue stroke, but the result will be transparent:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:57 msgid "" "Because the colorize mask algorithm is slow, and we only need a part of our " "layer to be filled to fill the whole ghost lady figure, we can make use of :" "guilabel:`Limit to layer bounds`. This will limit Colorize Mask to use the " "combined size of the line art and the coloring key strokes. Therefore, make " "sure that the colorizing keystrokes only take up as much as they really need." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:63 msgid "" "Now the algorithm will be possibly a lot faster, allowing us to add strokes " "and press update in rapid succession:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:69 msgid "" "To see the final result, disable :guilabel:`Edit Key Strokes` or toggle the " "second to last icon on the colorize mask." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:75 msgid "" "If you want to edit the strokes again, re-enable :guilabel:`Edit Key " "Strokes`." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:77 msgid "" "Now, the colorize mask, being a mask, can also be added to a group of line " "art layers. It will then use the composition of the whole group as the line " "art. This is perfect for our background which has two separate line art " "layers. It also means that the colorize mask will be disabled when added to " "a group with pass-through enabled, because those have no final composition. " "You can recognise a disabled colorize mask because its name is stricken " "through." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:79 msgid "" "To add a colorize mask to a group, select the group and |mouseleft| the " "canvas with the Colorize Mask editing tool, or |mouseright| the layer to :" "menuselection:`Add --> Colorize Mask`." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:85 msgid "" "Now, we add strokes to the background quickly. We do not need to use the :" "menuselection:`Limit to Layer Bounds` because the background covers the " "whole image." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:91 msgid "" "For the record, you can use other brushes and tools also work on the " "colorize mask as long as they can draw. The Colorize Mask Editing tool is " "just the most convenient because you can get to the algorithm options." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:93 msgid "Out final result looks like this:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:99 msgid "" "Now we are done, |mouseright| the colorize mask and :menuselection:`Convert " "--> to Paint Layer`. Then, :menuselection:`Layer --> Split --> Split Layer`. " "This will give separate color islands that you can easily edit:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:105 msgid "" "This way we can very quickly paint the image. Due to the colorize mask going " "from the first image to the following took only 30 minutes, and would've " "taken quite a bit longer." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:111 msgid "" "The colorize masks are saved to the .kra file, so as long as you don't save " "and open to a different file format, nor convert the colorize mask to a " "paintlayer, you can keep working adjust the results." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:114 msgid "Tool Options" msgstr "Hulpmiddelopties" #: ../../reference_manual/tools/colorize_mask.rst:116 #: ../../reference_manual/tools/colorize_mask.rst:172 msgid "Update" msgstr "Bijwerken" #: ../../reference_manual/tools/colorize_mask.rst:117 msgid "" "Run the colorize mask algorithm. The progress bar for updates on a colorize " "mask shows only in the layer docker." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:118 #: ../../reference_manual/tools/colorize_mask.rst:169 msgid "Edit key strokes" msgstr "Toetsaanslagen bewerken" #: ../../reference_manual/tools/colorize_mask.rst:119 msgid "" "Put the mask into edit mode. In edit mode, it will also show the 'pre-" "filtering' on the line-art, which is for example a blur filter for gap " "closing." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:121 msgid "" "Show the output of the colorize mask. If :guilabel:`Edit key strokes` is " "active, this will be shown semi-transparently, so it will be easy to " "recognise the difference between the strokes and the output." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:127 #: ../../reference_manual/tools/colorize_mask.rst:165 msgid "Show output" msgstr "Uitvoer tonen" #: ../../reference_manual/tools/colorize_mask.rst:127 msgid "" "On the **Left**: :guilabel:`Show Output` is on, :guilabel:`Edit Strokes` is " "off. In the **Middle**: :guilabel:`Show Output` and :guilabel:`Edit Strokes` " "are on. On the **Right**: :guilabel:`Show Output` is off and :guilabel:`Edit " "Strokes` is on.]]" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:129 msgid "Limit to layer bounds" msgstr "Beperken tot grenzen van de laag" #: ../../reference_manual/tools/colorize_mask.rst:130 msgid "" "Limit the colorize mask to the combined layer bounds of the strokes and the " "line art it is filling. This can speed up the use of the mask on complicated " "compositions, such as comic pages." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:132 msgid "" "Activate this for line art with large solid areas, for example shadows on an " "object. For the best use, set the value to the thinnest lines on the image. " "In the image below, note how edge detection affects the big black areas:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:138 msgid "Edge detection" msgstr "Randdetectie" #: ../../reference_manual/tools/colorize_mask.rst:138 msgid "" "From left to right: an example with big black shadows on an object but no " "edge detection, the same example without the edit strokes enabled. Then the " "same example with edge detection enabled and set to 2px, and that same " "example with out edit strokes enabled." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:141 msgid "" "While the algorithm is pretty good against gaps in contours, this will " "improve the gap recognition. The higher this value is, the bigger the gaps " "it will try to close, but a too high value can lead to other errors. Note " "how the pre-filtered line art (that's the blurry haze) affects the color " "patches." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:146 msgid "Gap close hint" msgstr "Tip voor gat sluiten" #: ../../reference_manual/tools/colorize_mask.rst:147 msgid "" "On the **Left**: :guilabel:`Gap close hint` is 0px. In the **Middle**: :" "guilabel:`Gap close hint` is 15px (the lines are 10px). On the **Right**: :" "guilabel:`Gap close hint` is 275px." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:149 msgid "" "This will attempt to handle messy strokes that overlap the line art where " "they shouldn't. At 0 no clean up is done, at 100% the clean-up is most " "aggressive." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:153 msgid "Clean-up strokes" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:155 msgid "Keystrokes" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:156 msgid "" "This palette keeps track of the colors used by the strokes. This is useful " "so you can switch back to colors easily. You can increase the swatch size by " "hovering over it with the mouse, and doing :kbd:`Ctrl +` |mousescroll|." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:158 msgid "Transparent" msgstr "Transparant" #: ../../reference_manual/tools/colorize_mask.rst:158 msgid "" "This button is under the keystrokes palette, you can mark the selected color " "to be interpreted a 'transparent' with this. In the clean-up screenshot " "above, cyan had been marked as transparent." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:161 msgid "Layer properties" msgstr "Laageigenschappen" #: ../../reference_manual/tools/colorize_mask.rst:163 msgid "" "The colorize mask layer has four properties. They are all the buttons on the " "right side of the layer:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:166 msgid "" "The first button, it allows you to toggle whether you'll see the output from " "the colorize algorithm." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:167 msgid "Lock" msgstr "Vergrendelen" #: ../../reference_manual/tools/colorize_mask.rst:168 msgid "Stops the mask from being edited." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:170 msgid "" "Whether the colorize mask is in edit mode. In edit mode it'll show the " "strokes, and the output will be semi-transparent." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:172 msgid "" "The last button will force the colorize mask to update, even when you're in " "a different tool." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:174 msgid "Colorize masks cannot be animated." msgstr "" diff --git a/locale/nl/LC_MESSAGES/reference_manual/tools/dyna.po b/locale/nl/LC_MESSAGES/reference_manual/tools/dyna.po index 97bc8dcd9..68933a5d7 100644 --- a/locale/nl/LC_MESSAGES/reference_manual/tools/dyna.po +++ b/locale/nl/LC_MESSAGES/reference_manual/tools/dyna.po @@ -1,72 +1,72 @@ # 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-02-19 03:36+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-02-27 10:34+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" #: ../../:38 msgid "" ".. image:: images/icons/dyna_tool.svg\n" " :alt: tooldyna" msgstr "" ".. image:: images/icons/dyna_tool.svg\n" " :alt: tooldyna" #: ../../reference_manual/tools/dyna.rst:1 msgid "Krita's dynamic brush tool reference." msgstr "Verwijzing naar hulpmiddel voor dynamische penseel van Krita." #: ../../reference_manual/tools/dyna.rst:16 msgid "Dynamic Brush Tool" msgstr "Hulpmiddel voor dynamische penseel" #: ../../reference_manual/tools/dyna.rst:18 msgid "|tooldyna|" msgstr "" #: ../../reference_manual/tools/dyna.rst:20 msgid "" "Add custom smoothing dynamics to your brush. This will give you similar " "smoothing results as the normal freehand brush. There are a couple options " "that you can change." msgstr "" #: ../../reference_manual/tools/dyna.rst:22 msgid "Mass" msgstr "Gewicht" #: ../../reference_manual/tools/dyna.rst:23 msgid "" "Average your movement to make it appear smoother. Higher values will make " "your brush move slower." msgstr "" #: ../../reference_manual/tools/dyna.rst:25 msgid "Drag" msgstr "Verslepen" #: ../../reference_manual/tools/dyna.rst:25 msgid "" "A rubberband effect that will help your lines come back to your cursor. " -"lower values will make the effect more extreme." +"Lower values will make the effect more extreme." msgstr "" #: ../../reference_manual/tools/dyna.rst:27 msgid "Recommended values are around 0.02 Mass and 0.92 Drag." msgstr "" diff --git a/locale/nl/LC_MESSAGES/tutorials/flat-coloring.po b/locale/nl/LC_MESSAGES/tutorials/flat-coloring.po index 9012a5aee..dd0b34515 100644 --- a/locale/nl/LC_MESSAGES/tutorials/flat-coloring.po +++ b/locale/nl/LC_MESSAGES/tutorials/flat-coloring.po @@ -1,767 +1,767 @@ # 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-03-12 03:34+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-02-27 23:42+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: muisrechts" +#: ../../tutorials/flat-coloring.rst:0 +msgid "" +".. image:: images/en/flat-coloring/Krita_filling_lineart_selection_1.png" +msgstr "" + +#: ../../tutorials/flat-coloring.rst:0 +msgid "" +".. image:: images/en/flat-coloring/Krita_filling_lineart_selection_2.png" +msgstr "" + +#: ../../tutorials/flat-coloring.rst:0 +msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_1.png" +msgstr "" + +#: ../../tutorials/flat-coloring.rst:0 +msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_2.png" +msgstr "" + +#: ../../tutorials/flat-coloring.rst:0 +msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_3.png" +msgstr "" + #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart14.png\n" " :alt: layer structure for flatting in krita" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart1.png\n" " :alt: blend mode setup of lineart flat coloring" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart2.png\n" " :alt: effects of multiply blend mode" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/icons/fill_tool.svg\n" " :alt: fill-tool icon" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart7.png\n" " :alt: colors filled with fill tool" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart15.png\n" " :alt: selecting with selection tools for filling color" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart16.png\n" " :alt: selection mask in Krita" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart17.png\n" " :alt: filling color in selection" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart18.png\n" " :alt: result of coloring made with the help of selection tools" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart8.png\n" " :alt: filling color in lineart using path tool" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart9.png\n" " :alt: erasing with path tool" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart10.png\n" " :alt: coloring with colorise mask" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart11.png\n" " :alt: result from the colorise mask" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart12.png\n" " :alt: slitting colors into islands" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart13.png\n" " :alt: resulting color islands from split layers" msgstr "" -#: ../../tutorials/flat-coloring.rst:0 -msgid "" -".. image:: images/en/flat-coloring/Krita_filling_lineart_selection_1.png" -msgstr "" - -#: ../../tutorials/flat-coloring.rst:0 -msgid "" -".. image:: images/en/flat-coloring/Krita_filling_lineart_selection_2.png" -msgstr "" - -#: ../../tutorials/flat-coloring.rst:0 -msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_1.png" -msgstr "" - -#: ../../tutorials/flat-coloring.rst:0 -msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_2.png" -msgstr "" - -#: ../../tutorials/flat-coloring.rst:0 -msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_3.png" -msgstr "" - #: ../../tutorials/flat-coloring.rst:1 msgid "Common workflows used in Krita" msgstr "" #: ../../tutorials/flat-coloring.rst:13 msgid "Flat Coloring" msgstr "" #: ../../tutorials/flat-coloring.rst:15 msgid "" "So you've got a cool black on white drawing, and now you want to color it! " "The thing we’ll aim for in this tutorial is to get your lineart colored in " "with flat colors. So no shading just yet. We’ll be going through some " "techniques for preparing the lineart, and we’ll be using the layer docker to " "put each colour on a separate layer, so we can easily access each colour " "when we add shading." msgstr "" #: ../../tutorials/flat-coloring.rst:17 msgid "" "This tutorial is adapted from this `tutorial `_ by " "the original author." msgstr "" #: ../../tutorials/flat-coloring.rst:20 msgid "Understanding Layers" msgstr "" #: ../../tutorials/flat-coloring.rst:22 msgid "" "To fill lineart comfortably, it's best to take advantage of the layerstack. " "The layer stack is pretty awesome, and it's one of those features that make " "digital art super-convenient." msgstr "" #: ../../tutorials/flat-coloring.rst:24 msgid "" "In traditional art, it is not uncommon to first draw the full background " "before drawing the subject. Or to first draw a line art and then colour it " "in. Computers have a similar way of working." msgstr "" #: ../../tutorials/flat-coloring.rst:26 msgid "" "In programming, if you tell a computer to draw a red circle, and then " "afterwards tell it to draw a smaller yellow circle, you will see the small " "yellow circle overlap the red circle. Switch the commands around, and you " "will not see the yellow circle at all: it was drawn before the red circle " "and thus ‘behind’ it." msgstr "" #: ../../tutorials/flat-coloring.rst:28 msgid "" "This is referred to as the “drawing order”. So like the traditional artist, " "the computer will first draw the images that are behind everything, and " "layer the subject and foreground on top of it. The layer docker is a way for " "you to control the drawing order of multiple images, so for example, you can " "have your lineart drawn later than your colors, meaning that the lines will " "be drawn over the colors, making it easier to make it neat!" msgstr "" #: ../../tutorials/flat-coloring.rst:30 msgid "" "Other things that a layer stack can do are blending the colors of different " "layers differently with blending modes, using a filter in the layer stack, " "or using a mask that allows you to make parts transparent." msgstr "" #: ../../tutorials/flat-coloring.rst:32 msgid "" "Programmers talk about transparency as ''Alpha'', which is because the 'a' " "symbol is used to present transparency in the algorithms for painting one " "color on top of another. Usually when you see the word ''Alpha'' in a " "graphics program, just think of it as affecting the transparency." msgstr "" #: ../../tutorials/flat-coloring.rst:35 msgid "Preparing your line-art" msgstr "" #: ../../tutorials/flat-coloring.rst:37 msgid "" "Put the new layer underneath the layer containing the lineart (drag and drop " "or use the up/down arrows for that), and draw on it." msgstr "" #: ../../tutorials/flat-coloring.rst:42 msgid "" "…And notice nothing happening. This is because the white isn’t transparent. " "You wouldn’t really want it to either, how else would you make convincing " "highlights? So what we first need to do to colour in our drawing is prepare " "our lineart. There’s several methods of doing so, each with varying " "qualities." msgstr "" #: ../../tutorials/flat-coloring.rst:45 msgid "The Multiply Blending Mode" msgstr "" #: ../../tutorials/flat-coloring.rst:47 msgid "" "So, typically, to get a black and white lineart usable for colouring, you " "can set the blending mode of the lineart layer to Multiply. You do this by " "selecting the layer and going to the drop down that says **Normal** and " "setting that to **Multiply**." msgstr "" #: ../../tutorials/flat-coloring.rst:52 msgid "And then you should be able to see your colors!" msgstr "" #: ../../tutorials/flat-coloring.rst:54 msgid "" "Multiply is not a perfect solution however. For example, if through some " "image editing magic I make the lineart blue, it results into this:" msgstr "" #: ../../tutorials/flat-coloring.rst:59 msgid "" "This is because multiply literally multiplies the colors. So it uses maths!" msgstr "" #: ../../tutorials/flat-coloring.rst:61 msgid "" "What it first does is take the values of the RGB channels, then divides them " "by the max (because we're in 8bit, this is 255), a process we call " "normalising. Then it multiplies the normalised values. Finally, it takes the " "result and multiplies it with 255 again to get the result values." msgstr "" #: ../../tutorials/flat-coloring.rst:67 msgid "Pink" msgstr "Roze" #: ../../tutorials/flat-coloring.rst:68 msgid "Pink (normalised)" msgstr "" #: ../../tutorials/flat-coloring.rst:69 ../../tutorials/flat-coloring.rst:87 msgid "Blue" msgstr "Blauw" #: ../../tutorials/flat-coloring.rst:70 msgid "Blue (normalised)" msgstr "" #: ../../tutorials/flat-coloring.rst:71 msgid "Normalised, multiplied" msgstr "" #: ../../tutorials/flat-coloring.rst:72 msgid "Result" msgstr "Resultaat" #: ../../tutorials/flat-coloring.rst:73 msgid "Red" msgstr "Rood" #: ../../tutorials/flat-coloring.rst:74 msgid "222" msgstr "" #: ../../tutorials/flat-coloring.rst:75 msgid "0.8705" msgstr "" #: ../../tutorials/flat-coloring.rst:76 msgid "92" msgstr "" #: ../../tutorials/flat-coloring.rst:77 msgid "0.3607" msgstr "" #: ../../tutorials/flat-coloring.rst:78 msgid "0.3139" msgstr "" #: ../../tutorials/flat-coloring.rst:79 msgid "80" msgstr "" #: ../../tutorials/flat-coloring.rst:80 msgid "Green" msgstr "Groen" #: ../../tutorials/flat-coloring.rst:81 msgid "144" msgstr "" #: ../../tutorials/flat-coloring.rst:82 msgid "0.5647" msgstr "" #: ../../tutorials/flat-coloring.rst:83 msgid "176" msgstr "" #: ../../tutorials/flat-coloring.rst:84 msgid "0.6902" msgstr "" #: ../../tutorials/flat-coloring.rst:85 msgid "0.3897" msgstr "" #: ../../tutorials/flat-coloring.rst:86 msgid "99" msgstr "" #: ../../tutorials/flat-coloring.rst:88 msgid "123" msgstr "" #: ../../tutorials/flat-coloring.rst:89 msgid "0.4823" msgstr "" #: ../../tutorials/flat-coloring.rst:90 msgid "215" msgstr "" #: ../../tutorials/flat-coloring.rst:91 msgid "0.8431" msgstr "" #: ../../tutorials/flat-coloring.rst:92 msgid "0.4066" msgstr "" #: ../../tutorials/flat-coloring.rst:93 msgid "103" msgstr "" #: ../../tutorials/flat-coloring.rst:95 msgid "" "This isn't completely undesirable, and a lot of artists use this effect to " "add a little richness to their colors." msgstr "" #: ../../tutorials/flat-coloring.rst:98 ../../tutorials/flat-coloring.rst:127 #: ../../tutorials/flat-coloring.rst:154 ../../tutorials/flat-coloring.rst:173 #: ../../tutorials/flat-coloring.rst:210 ../../tutorials/flat-coloring.rst:247 #: ../../tutorials/flat-coloring.rst:275 ../../tutorials/flat-coloring.rst:317 msgid "Advantages" msgstr "" #: ../../tutorials/flat-coloring.rst:100 msgid "" "Easy, can work to your benefit even with coloured lines by softening the " "look of the lines while keeping nice contrast." msgstr "" #: ../../tutorials/flat-coloring.rst:103 ../../tutorials/flat-coloring.rst:132 #: ../../tutorials/flat-coloring.rst:159 ../../tutorials/flat-coloring.rst:178 #: ../../tutorials/flat-coloring.rst:215 ../../tutorials/flat-coloring.rst:252 #: ../../tutorials/flat-coloring.rst:280 ../../tutorials/flat-coloring.rst:322 msgid "Disadvantages" msgstr "Nadelen" #: ../../tutorials/flat-coloring.rst:105 msgid "Not actually transparent. Is a little funny with coloured lines." msgstr "" #: ../../tutorials/flat-coloring.rst:108 msgid "Using Selections" msgstr "" #: ../../tutorials/flat-coloring.rst:110 msgid "" "The second method is one where we'll make it actually transparent. In other " "programs this would be done via the channel docker, but Krita doesn't do " "custom channels, instead it uses Selection Masks to store custom selections." msgstr "" #: ../../tutorials/flat-coloring.rst:112 msgid "duplicate your lineart layer." msgstr "" #: ../../tutorials/flat-coloring.rst:114 msgid "" "convert the duplicate to a selection mask. |mouseright| the layer, then :" "menuselection:`Convert --> to Selection Mask`." msgstr "" #: ../../tutorials/flat-coloring.rst:118 msgid "" "Invert the selection mask. :menuselection:`Select --> Invert Selection`." msgstr "" #: ../../tutorials/flat-coloring.rst:120 msgid "" "Make a new layer, and do :menuselection:`Edit --> Fill with foreground " "color`." msgstr "" #: ../../tutorials/flat-coloring.rst:124 msgid "And you should now have the line art on a separate layer." msgstr "" #: ../../tutorials/flat-coloring.rst:129 msgid "Actual transparency." msgstr "" #: ../../tutorials/flat-coloring.rst:134 msgid "Doesn't work when the lineart is coloured." msgstr "" #: ../../tutorials/flat-coloring.rst:137 msgid "Using Masks" msgstr "" #: ../../tutorials/flat-coloring.rst:139 msgid "This is a simpler variation of the above." msgstr "" #: ../../tutorials/flat-coloring.rst:141 msgid "Make a filled layer underneath the lineart layer." msgstr "" #: ../../tutorials/flat-coloring.rst:145 msgid "" "Convert the lineart layer to a transparency mask |mouseright| the layer, " "then :menuselection:`Convert --> to Transparency Mask`." msgstr "" #: ../../tutorials/flat-coloring.rst:149 msgid "" "Invert the transparency mask by going to :menuselection:`Filter --> Adjust --" "> Invert`" msgstr "" #: ../../tutorials/flat-coloring.rst:156 msgid "" "Actual transparency. You can also very easily doodle a pattern on the filled " "layer where the mask is on without affecting the transparency." msgstr "" #: ../../tutorials/flat-coloring.rst:161 msgid "" "Doesn't work when the lineart is coloured already. We can still get faster." msgstr "" #: ../../tutorials/flat-coloring.rst:164 msgid "Using Color to Alpha" msgstr "" #: ../../tutorials/flat-coloring.rst:166 msgid "By far the fastest way to get transparent lineart." msgstr "" #: ../../tutorials/flat-coloring.rst:168 msgid "" "Select the line art layer and apply the color to alpha filter. :" "menuselection:`Filter --> Colors --> Color to Alpha`. The default values " "should be sufficient for lineart." msgstr "" #: ../../tutorials/flat-coloring.rst:171 msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart_color_to_alpha.png" msgstr "" #: ../../tutorials/flat-coloring.rst:175 msgid "" "Actual transparency. Works with coloured line art as well, because it " "removes the white specifically." msgstr "" #: ../../tutorials/flat-coloring.rst:180 msgid "" "You'll have to lock the layer transparency or separate out the alpha via the " "right-click menu if you want to easily color it." msgstr "" #: ../../tutorials/flat-coloring.rst:184 msgid "Colouring the image" msgstr "" #: ../../tutorials/flat-coloring.rst:186 msgid "" "Much like preparing the line art, there's many different ways of colouring a " "layer." msgstr "" #: ../../tutorials/flat-coloring.rst:188 msgid "" "You could for example fill in everything by hand, but while that is very " "precise it also takes a lot of work. Let's take a look at the other options, " "shall we?" msgstr "" #: ../../tutorials/flat-coloring.rst:191 msgid "Fill Tool" msgstr "Hulpmiddel voor vullen" #: ../../tutorials/flat-coloring.rst:196 msgid "" "In most cases the fill-tool can’t deal with the anti-aliasing (the soft edge " "in your lineart to make it more smooth when zoomed out) In Krita you have " "the grow-shrink option. Setting that to say… 2 expands the colour two pixels." msgstr "" #: ../../tutorials/flat-coloring.rst:198 msgid "" "Threshold decides when the fill-tool should consider a different colour " "pixel to be a border. And the feathering adds a extra soft border to the " "fill." msgstr "" #: ../../tutorials/flat-coloring.rst:200 msgid "" "Now, if you click on a gapless-part of the image with your preferred colour…" "(Remember to set the opacity to 1.0!)" msgstr "" #: ../../tutorials/flat-coloring.rst:202 msgid "" "Depending on your lineart, you can do flats pretty quickly. But setting the " "threshold low can result in little artifacts around where lines meet:" msgstr "" #: ../../tutorials/flat-coloring.rst:207 msgid "" "However, setting the threshold high can end with the fill not recognising " "some of the lighter lines. Besides these little artifacts can be removed " "with the brush easily." msgstr "" #: ../../tutorials/flat-coloring.rst:212 msgid "Pretty darn quick depending on the available settings." msgstr "" #: ../../tutorials/flat-coloring.rst:217 msgid "" "Again, not great with gaps or details. And it works best with aliased line-" "art." msgstr "" #: ../../tutorials/flat-coloring.rst:220 msgid "Selections" msgstr "Selecties" #: ../../tutorials/flat-coloring.rst:222 msgid "Selections work using the selection tools." msgstr "" #: ../../tutorials/flat-coloring.rst:227 msgid "" "For example with the :ref:`bezier_curve_selection_tool` you can easily " "select a curved area, and the with :kbd:`Shift` + |mouseleft| (not |" "mouseleft| + :kbd:`Shift`, there's a difference!) you can easily add to an " "existing selection." msgstr "" #: ../../tutorials/flat-coloring.rst:232 msgid "" "You can also edit the selection if you have :menuselection:`Select --> Show " "Global Selection Mask` turned on. Then you can select the global selection " "mask, and paint on it. (Above with the alternative selection mode, activated " "in the lower-left corner of the stats bar)" msgstr "" #: ../../tutorials/flat-coloring.rst:234 msgid "" "When done, select the color you want to fill it with and press :kbd:`Shift` " "+ `backspace`." msgstr "" #: ../../tutorials/flat-coloring.rst:239 msgid "" "You can save selections in selection masks by |mouseright| a layer, and then " "going to :menuselection:`Add --> Local Selection`. You first need to " "deactivate a selection by pressing the circle before adding a new selection." msgstr "" #: ../../tutorials/flat-coloring.rst:241 msgid "" "This can serve as an alternative way to split out different parts of the " "image, which is good for more painterly pieces:" msgstr "" #: ../../tutorials/flat-coloring.rst:249 msgid "A bit more precise than filling." msgstr "" #: ../../tutorials/flat-coloring.rst:254 msgid "Previewing your color isn't as easy." msgstr "" #: ../../tutorials/flat-coloring.rst:257 msgid "Geometric tools" msgstr "" #: ../../tutorials/flat-coloring.rst:259 msgid "" "So you have a tool for making rectangles or circles. And in the case of " "Krita, a tool for bezier curves. Select the path tool (|path tool|), and set " "the tool options to fill=foreground and outline=none. Make sure that your " "opacity is set to 1.00 (fully opaque)." msgstr "" #: ../../tutorials/flat-coloring.rst:262 msgid "" ".. image:: images/icons/bezier_curve.svg\n" " :alt: path tool" msgstr "" #: ../../tutorials/flat-coloring.rst:264 msgid "" "By clicking and holding, you can influence how curvy a line draw with the " "path tool is going to be. Letting go of the mouse button confirms the " "action, and then you’re free to draw the next point." msgstr "" #: ../../tutorials/flat-coloring.rst:269 msgid "" "You can also erase with a geometric tool. Just press :kbd:`E` or the eraser " "button." msgstr "" #: ../../tutorials/flat-coloring.rst:277 msgid "" "Quicker than using the brush or selections. Also decent with lineart that " "contains gaps." msgstr "" #: ../../tutorials/flat-coloring.rst:282 msgid "" "Fiddly details aren’t easy to fill in with this. So I recommend skipping " "those and filling them in later with a brush." msgstr "" #: ../../tutorials/flat-coloring.rst:285 msgid "Colorize Mask" msgstr "Inkleurmasker" #: ../../tutorials/flat-coloring.rst:287 msgid "" "So, this is a bit of an odd one. In the original tutorial, you'll see I'm " "suggesting using G'Mic, but that was a few years ago, and g'mic is a little " "unstable on windows. Therefore, the Krita developers have been attempting to " "make an internal tool doing the same." msgstr "" #: ../../tutorials/flat-coloring.rst:289 msgid "" "It is disabled in 3.1, but if you use 4.0 or later, it is in the toolbox. " "Check the Colorize Mask for more information." msgstr "" #: ../../tutorials/flat-coloring.rst:291 msgid "So it works like this:" msgstr "" #: ../../tutorials/flat-coloring.rst:293 msgid "Select the colorize mask tool." msgstr "" #: ../../tutorials/flat-coloring.rst:294 msgid "Tick the layer you're using." msgstr "" #: ../../tutorials/flat-coloring.rst:295 msgid "Paint the colors your want to use on the colorize mask" msgstr "" #: ../../tutorials/flat-coloring.rst:296 msgid "Click update to see the results:" msgstr "" #: ../../tutorials/flat-coloring.rst:301 msgid "" "When you are satisfied, |mouseright| the colorize mask, and go to :" "menuselection:`Convert --> Paint Layer`. This will turn the colorize mask to " "a generic paint layer. Then, you can fix the last issues by aking the " "lineart semi-transparent and painting the flaws away with a pixel art brush." msgstr "" #: ../../tutorials/flat-coloring.rst:306 msgid "" "Then, when you are done, split the layers via :menuselection:`Layers --> " "Split --> Split Layer`. There's a few options you can choose, but the " "following should be fine:" msgstr "" #: ../../tutorials/flat-coloring.rst:311 msgid "" "Finally, press **Ok** and you should get the following. Each color patch it " "on a different layer, named by the palette in the menu and alpha locked, so " "you can start painting right away!" msgstr "" #: ../../tutorials/flat-coloring.rst:319 msgid "" "Works with anti aliased lineart. Really quick to get the base work done. Can " "auto-close gaps." msgstr "" #: ../../tutorials/flat-coloring.rst:324 msgid "" "No anti aliasing of it’s own. You have to choose between getting details " "right or the gaps auto-closed." msgstr "" #: ../../tutorials/flat-coloring.rst:327 msgid "Conclusion" msgstr "Conclusie" #: ../../tutorials/flat-coloring.rst:329 msgid "" "I hope this has given you a good idea of how to fill in flats using the " "various techniques, as well as getting a hand of different Krita features. " "Remember that a good flat filled lineart is better than a badly shaded one, " "so keep practising to get the best out of these techniques!" msgstr "" diff --git a/locale/nl/LC_MESSAGES/user_manual/loading_saving_brushes.po b/locale/nl/LC_MESSAGES/user_manual/loading_saving_brushes.po index 6cc417ff3..14eecc448 100644 --- a/locale/nl/LC_MESSAGES/user_manual/loading_saving_brushes.po +++ b/locale/nl/LC_MESSAGES/user_manual/loading_saving_brushes.po @@ -1,950 +1,950 @@ # 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-03-12 03:34+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-03-01 11:12+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" #: ../../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 "" "Gedetailleerde gids over de penseelinstellingendialoog in Krita evenals hoe " "uw eigenn penselen te maken en hoe ze te delen." #: ../../user_manual/loading_saving_brushes.rst:17 msgid "Loading and Saving Brushes" msgstr "Penselen laden en opslaan" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:37 msgid "The Brush settings dropdown" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:44 msgid "" "When you open Brush Settings Editor panel you will see something like this:" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:48 msgid "Tour of the brush settings dropdown" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:53 msgid "The brush settings drop down is divided into six areas," msgstr "" #: ../../user_manual/loading_saving_brushes.rst:56 msgid "Section A - General Information" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:79 msgid "Engine" msgstr "Engine" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:94 msgid "Reloading" msgstr "Opnieuw inlezen" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:101 msgid "Saving a preset" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:103 msgid "" "On the right, there's :guilabel:`Save New Brush Preset` and :guilabel:" "`Overwrite Brush`." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:108 msgid "Overwrite Brush" msgstr "Penseel overschrijven" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:113 msgid "Save New Brush Preset" msgstr "Nieuw voorinstellingen van penseel opslaan" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:119 msgid ".. image:: images/en/Krita_4_0_Save_New_Brush_Preset_Dialog.png" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:125 msgid "Brush Name" msgstr "Penseelnaam" #: ../../user_manual/loading_saving_brushes.rst:127 msgid "Load Existing Thumbnail" msgstr "Bestande miniatuur laden" #: ../../user_manual/loading_saving_brushes.rst:128 msgid "This will load the existing thumbnail inside the preset." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:130 msgid "Load scratch pad thumbnail" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:132 msgid "Load Image" msgstr "Afbeelding Inlezen" #: ../../user_manual/loading_saving_brushes.rst:133 msgid "With this you can choose an image from disk to load as a thumbnail." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:134 msgid "Load from Icon Library" msgstr "Uit pictogrambiblioteek laden" #: ../../user_manual/loading_saving_brushes.rst:135 msgid "This opens up the icon library." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:137 msgid "Clear Thumbnail" msgstr "Miniatuur wissen" #: ../../user_manual/loading_saving_brushes.rst:137 msgid "This will make the mini scratch pad white." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:140 msgid "The Icon Library" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:142 msgid "To make making presets icons faster, Krita got an icon library." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:145 msgid ".. image:: images/en/Krita_4_0_Preset_Icon_Library_Dialog.png" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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, ad the lowest slider is a super simple levels filter. " +"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 "" #: ../../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." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:167 msgid "Section B - The Preset Chooser" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:169 msgid "" "The preset chooser is much the same as the preset docker and the preset " "dropdown 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 "" #: ../../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 "" #: ../../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 "" #: ../../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 for that " -"engine." +"list of Krita's engines. Selecting an engine from the list will show the " +"brushes for that engine." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:185 msgid "" -"The trashcan icon does the same as it does in the preset docker: delete , or " +"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 "" #: ../../user_manual/loading_saving_brushes.rst:189 msgid "Section C - The Scratch pad" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:202 msgid "The scratch pad has five buttons underneath it. These are in order for:" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:204 msgid "Showing the current brush image" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:206 msgid "Adding a gradient to the scratch pad (useful for smudge brushes)" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:207 msgid "Filling with the background color" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:208 msgid "Clearing everything on the scratch pad." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:211 msgid "Section D - The Options List" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:227 msgid "Section E - Option Configuration Widget" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:233 msgid "Using sensor curves" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:260 msgid "Underneath the curve widget there are two more options:" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:264 msgid "Share Curves across all settings" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:271 msgid "Multiply" msgstr "Vermenigvuldigen" #: ../../user_manual/loading_saving_brushes.rst:272 msgid "Will multiply the two values, 0.5\\*0.7 = 0.35" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:274 msgid "Addition" msgstr "Optelling" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:277 msgid "Maximum" msgstr "Maximum" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:280 msgid "Minimum" msgstr "Minimum" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:283 msgid "Will subtract the smallest value from the largest, so 0.7-0.5 = 0.2" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:284 msgid "Curves Calculation Mode" msgstr "Rekenmodus van krommen" #: ../../user_manual/loading_saving_brushes.rst:284 msgid "Difference" msgstr "Verschil" #: ../../user_manual/loading_saving_brushes.rst:286 msgid "It's maybe better to see with the following example:" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:289 msgid ".. image:: images/en/Krita_4_0_brush_curve_calculation_mode.png" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:290 msgid "" "The first two are regular, the rest with different multiplication types." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:292 msgid "Is a brush with size set to the distance sensor." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:293 msgid "Is a brush with the size set to the fade sensor." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:294 msgid "The size is calculated from the fade and distance sensors multiplied." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:297 msgid "" "The size takes the maximum value from the values of the fade and distance " "sensors." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:299 msgid "" -"The size takes the minimum value from the values of the face and distance " +"The size takes the minimum value from the values of the fade and distance " "sensors." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:305 msgid "Section F - Miscellaneous options" msgstr "" #: ../../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, the revert to default. " "Dirtied presets can be recognized by the icon in the top-left of the preset." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:316 msgid "Temporarily Save Tweaks to Preset (Dirty Presets)" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:319 msgid "Eraser Switch Size" msgstr "Gom schakelt grootte om" #: ../../user_manual/loading_saving_brushes.rst:319 msgid "" "This switches the brush to a separately stored size when using the :kbd:`E` " "key." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:321 msgid "Eraser Switch Opacity" msgstr "Gom schakelt dekking om" #: ../../user_manual/loading_saving_brushes.rst:322 msgid "Same as above, but then with Eraser opacity." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:330 msgid "Instant Preview" msgstr "Instant vooruitblik" #: ../../user_manual/loading_saving_brushes.rst:333 msgid "The On-canvas brush settings" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:347 msgid "Making a Brush Preset" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:349 msgid "Now, let's make a simple brush to test the waters with:" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:352 msgid "Getting a default for the brush engine." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:354 msgid "First, open the settings with :kbd:`F5`." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:361 msgid "Example: Making an inking brush" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:370 -msgid "Uncheck the :guilabel:`enable pen settings` checkbox." +msgid "Uncheck the :guilabel:`Enable Pen Settings` checkbox." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:377 msgid "" -"Uncheck the :guilabel:`enable pen settings` checkbox here as well. Test " +"Uncheck the :guilabel:`Enable Pen Settings` checkbox here as well. Test " "again." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:401 msgid "Saving the new Brush" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:403 msgid "" "When you're satisfied, go to the upper left and select :guilabel::`Save new " "preset`." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:414 msgid "Finally press :guilabel:`Save`, and your brush should be done." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:416 msgid "You can further modify your inking brush by..." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:422 msgid "Making the fine lines look even softer by using the flow option." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:422 msgid "" "To do this, select the flow option, and turn back on the 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 "" #: ../../user_manual/loading_saving_brushes.rst:425 msgid "Sharing Brushes" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:438 msgid "Sharing a single preset" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:440 msgid "There are three types of resources a single preset can take:" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:446 msgid "A Pattern file: this is when you are using textures." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:452 msgid "" "To find those resources, go to :menuselection:`Settings --> Manage Resources " "--> Open Resource Folder`." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:458 msgid "Importing a single KPP file." msgstr "" #: ../../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 "" #: ../../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 " "dropdown (: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 "" #: ../../user_manual/loading_saving_brushes.rst:471 msgid "Sharing via ZIP (old-fashioned)" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:477 msgid "Using a ZIP with the relevant files." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:479 msgid "" "Go to :menuselection:`Settings --> Manage Resources --> Open Resource " "Folder` to open the resource folder." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:480 msgid "Then, open up the zip file." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:484 msgid "Restart Krita" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:485 msgid "Enjoy your brushes!" msgstr "" diff --git a/locale/nl/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po b/locale/nl/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po index e2daa1c7d..709d3e8e4 100644 --- a/locale/nl/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po +++ b/locale/nl/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po @@ -1,289 +1,289 @@ # 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-03-06 03:37+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-03-01 11:21+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" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:1 msgid "Introduction to using Krita's python plugin API." msgstr "Introductie tot de python-plug-in-API van Krita gebruiken." #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:18 msgid "Introduction to Python Scripting" msgstr "Introductie tot scripts maken in Python" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:22 msgid "" "When we offered python scripting as one of Kickstarter Stretchgoals we could " "implement next to vectors and text, it won the backer vote by a landslide. " "Some people even only picked python and nothing else. So what exactly is " "python scripting?" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:25 msgid "What is Python Scripting?" msgstr "Wat is scripts maken in Python?" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:27 msgid "" "Python is a scripting language, that can be used to automate tasks. What " "python scripting in Krita means is that we added an API to krita, which is a " "bit of programming that allows python to access to parts of Krita. With this " "we can make dockers, perform menial tasks on a lot of different files and " "even write our own exporters. People who work with computer graphics, like " "VFX and video game artists use python a lot to make things like sprite " "sheets, automate parts of export and more." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:29 msgid "" "It is outside the scope of this manual to teach you python itself. However, " "as python is an extremely popular programming language and great for " "beginners, there's tons of learning material around that can be quickly " "found with a simple 'learn python' internet search." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:31 msgid "" "This manual will instead focus on how to use python to automate and extend " "Krita. For that we'll first start with the basics: How to run Python " "commands in the scripter." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:35 msgid "How to Enable the Scripter Plugin" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:37 msgid "" "The scripter plugin is not necessary to use python, but it is very useful " "for testing and playing around with python. It is a python console, written " "in python, which can be used to write small scripts and execute them on the " "fly." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:39 msgid "" "To open the scripter, navigate to :menuselection:`Tools --> Scripts --> " "Scripter`. If you don't see it listed, go to :menuselection:`Settings --> " "Configure Krita --> Python Plugin Manager` and toggle \"Scripter\" in the " "list to enable it. If you don't see the scripter plugin, make sure you are " "using an up-to-date version of Krita." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:41 msgid "" "The scripter will pop up with a text editor window on top and an output " "window below. Input the following in the text area:" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:48 msgid "" "Press the big play button or press :kbd:`Ctrl + R` to run the script. Then, " "below, in the output area the following should show up::" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:53 msgid "" "Now we have a console that can run functions like print() from the Python " "environment - but how do we use it to manage Krita?" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:56 msgid "Running basic Krita commands" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:58 msgid "" "To allow Python to communicate with Krita, we will use the Krita module. At " "the top of every script, we will write: ``from krita import *``" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:60 msgid "" "This allows us to talk to Krita through ``Krita.instance()``. Let's try to " "double our coding abilities with Python." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:68 msgid "" "You should see a second scripter window open. Pretty neat! Here is a " "slightly more advanced example." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:77 msgid "" "This will open up a new document. Clearly Python gives you quite a lot of " "control to automate Krita. Over time we expect the community to write all " "kinds of scripts that you can use simply by pasting them in the scripter." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:79 msgid "" "But what if you want to write new commands for yourself? The best place to " "start is very simple: search for examples written by other people! You can " "save a lot of time if someone else has written code that you can base your " "work on. It's also worth looking through the python plugins, which are " "located in /share/krita/pykrita. There's also a step by step guide for :ref:" "`krita_python_plugin_howto` here in the manual." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:81 msgid "" "But it's likely that you need more information. For that, we will need see " "what's hidden behind the asterisk when you ``import * from Krita``. To learn " "what Krita functions that are available and how to use them, you will want " "to go for Krita API reference documentation." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:84 msgid "Krita's API" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:86 msgid "" "`LibKis API Overview `_" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:87 msgid "" "`Krita class documentation `_" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:89 msgid "" "Those pages may look like a lot of jargon at first. This is because Krita's " "API documentation comes from the underlying C++ language that Krita is " "written in. The magic happens because of a Python tool called SIP, which " "makes it possible for python speak in C++ and talk to Krita. The end result " "is that when we ``import krita`` and call functions, we're actually using " "the C++ methods listed in that documentation." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:91 msgid "" "Let's see how this stuff works in more detail. Let's take a look at the " "second link, the `Krita class reference `_. There we can see all the " "functions available to the Krita instance. If you type dir(Krita.instance()) " "in Python, it should match this page very closely - you can view the " "documentation of the functions createDocument(), activeWindow(), and " "action() which we used above." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:93 msgid "" "One of the more confusing things is seeing all the C++ classes that Krita " -"uses, including the Qt classes that start with Q. But here is the beauty fo " +"uses, including the Qt classes that start with Q. But here is the beauty of " "SIP: it tries to make the translation from these classes into Python as " "simple and straightforward as possible. For example, you can see that the " "function filters() returns a QStringList. However, SIP converts those " "QStringLists into regular python list of strings!" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:101 msgid "Outputs as ::" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:112 msgid "However, sometimes the conversion doesn't go quite as smoothly." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:120 msgid "gives something like this::" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:127 msgid "" "It is a list of something, sure, but how to use it? If we go back to the " "Krita apidocs page and look at the function, documents() we'll see there's " "actually a clickable link on the 'Document' class. `If you follow that link " "`_, you'll see that the document has a function called " "name() which returns the name of the document, and functions width() and " "height() which return the dimensions. So if we wanted to generate an info " "report about the documents in Krita, we could write a script like this:" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:137 msgid "we get an output like::" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:147 msgid "" "Hopefully this will give you an idea of how to navigate the API docs now." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:149 msgid "" "Krita's API has many more classes, you can get to them by going to the top-" "left class list, or just clicking their names to get to their API docs. The " "functions print() or dir() are your friends here as well. This line will " "print out a list of all the actions in Krita - you could swap in one of " "these commands instead of 'python_scripter' in the example above." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:155 msgid "" "The Python module ``inspect`` was designed for this sort of task. Here's a " "useful function to print info about a class to the console." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:167 msgid "" "Finally, in addition to the LibKis documentation, the Qt documentation, " "since Krita uses PyQt to expose nearly all of the Qt API to Python. You can " "build entire windows with buttons and forms this way, using the very same " "tools that Krita is using! You can read the `Qt documentation `_ and the `PyQt documentation `_ for more info about this, and also definitely study the included plugins " "as well to see how they work." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:171 msgid "Technical Details" msgstr "Technische details" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:177 msgid "Python Scripting on Windows" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:179 msgid "" "To get Python scripting working on Windows 7/8/8.1, you will need to install " "the `Universal C Runtime from Microsoft's website `_. (Windows 10 already comes with it.)" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:182 msgid "Python 2 and 3" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:184 msgid "By default Krita is compiled for python 3." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:186 msgid "" "However, it is possible to compile it with python 2. To do so, you will need " "to add the following to the cmake configuration line::" 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 e042adc25..73184ce34 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,866 +1,866 @@ # 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-03-12 03:34+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-02-19 09:58+0000\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" #: ../../: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 "" - #: ../../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 "Conteúdo" #: ../../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 it's 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 "Imagens" #: ../../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 "Listas" #: ../../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 "Tabela" #: ../../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 "amarelo" #: ../../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 "verde" #: ../../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 "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 "Definição" #: ../../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 "Tabelas" #: ../../contributors_manual/krita_manual_conventions.rst:310 msgid "Purpose" msgstr "Objectivo" #: ../../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ó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 "" #: ../../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 "Aspas" #: ../../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/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 73e7b3f86..055f32bbc 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,1059 +1,1059 @@ # 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-03-13 03:40+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-02-19 09:58+0000\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" -#: ../../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 ".. 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 "" #: ../../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 colour " "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 colour." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:71 msgid "" "Finally, group 4 has Vermillion red, citron yellow and cerulean blue. Their " "colours 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 colour 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 " "colour translate properly between color devices." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:82 msgid "" "It usually works by attempting to covert a colour to the reference colour " "space XYZ. XYZ is a coordinate system that has a spot for all colours 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 colour 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:88 msgid "" "To give a crude estimate, ICC profiles deal with keeping colours consistent " "over many interpretations of devices (screens, printers) by using a " "reference space, and OCIO deals with manipulating the interpretation of said " "colours." 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 grey it produces. Using " "these and several other measurements it creates an icc profile unique to " "your screen. You set these in Krita's colour 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 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-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.)" 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 colour 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 colorspace 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 "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 colour reproduction. Use this if you want to " "see all colours 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 colours at whatever cost, which may result in awful looking " "colours. 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étrica Relativa" #: ../../general_concepts/colors/color_managed_workflow.rst:180 msgid "" "A in between solution between perceptual and absolute, relative will try to " "fit whatever colours it can match between colour 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 "Saturação" #: ../../general_concepts/colors/color_managed_workflow.rst:183 msgid "" "Does anything to retain colourfulness, 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 '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." 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 colour 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 colour 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 colour 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 " "customly 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 colour maths, often concerning the blending of colours. " "This colour maths works best in linear colour space, and linear colour 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 colour 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 " "colour 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 "A exportar" #: ../../general_concepts/colors/color_managed_workflow.rst:265 msgid "" "when you have finished your image and are ready to export it, you can modify " "the color space to optimize it:" msgstr "" #: ../../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's 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 colours actually look strange: This is a " "bug in Firefox, which is because its `color management system is incomplete " "`_, save your png, jpg or tiff without an embedded profile to work " "around this." 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 "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 "" #: ../../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 " "bitdepth 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 "Resultado" #: ../../general_concepts/colors/color_managed_workflow.rst:322 msgid "" "sRGB, icc version 2, sRGB trc for the internet, and a specialised 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, mypaint, mangastudio, 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, mangastudio " "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 optimisers. 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 "Imprimir" #: ../../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 "" "Specialised 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 --> 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." msgstr "" #: ../../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 "" #: ../../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 optimised content, and it's recommended to " "stay within 8bit, future screens may have higher bitdepths, 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 optimise 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 "" "`Visualising the XYZ colorspace `_" 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 colormanagement from argylcms manual `_" msgstr "" diff --git a/locale/pt_PT/LC_MESSAGES/general_concepts/projection/orthographic_oblique.po b/locale/pt_PT/LC_MESSAGES/general_concepts/projection/orthographic_oblique.po index 2e3da5dd2..fa6c0c55a 100644 --- a/locale/pt_PT/LC_MESSAGES/general_concepts/projection/orthographic_oblique.po +++ b/locale/pt_PT/LC_MESSAGES/general_concepts/projection/orthographic_oblique.po @@ -1,312 +1,313 @@ # 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-03-04 03:37+0100\n" -"PO-Revision-Date: 2019-02-19 09:58+0000\n" +"PO-Revision-Date: 2019-03-14 14:27+0000\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: en projectionanimation projection Krita\n" #: ../../general_concepts/projection/orthographic_oblique.rst:None msgid ".. image:: images/en/category_projection/projection-cube_01.svg" -msgstr "" +msgstr ".. image:: images/en/category_projection/projection-cube_01.svg" #: ../../general_concepts/projection/orthographic_oblique.rst:None msgid ".. image:: images/en/category_projection/projection-cube_02.svg" -msgstr "" +msgstr ".. image:: images/en/category_projection/projection-cube_02.svg" #: ../../general_concepts/projection/orthographic_oblique.rst:None msgid ".. image:: images/en/category_projection/projection-cube_03.svg" -msgstr "" +msgstr ".. image:: images/en/category_projection/projection-cube_03.svg" #: ../../general_concepts/projection/orthographic_oblique.rst:None msgid ".. image:: images/en/category_projection/projection-cube_04.svg" -msgstr "" +msgstr ".. image:: images/en/category_projection/projection-cube_04.svg" #: ../../general_concepts/projection/orthographic_oblique.rst:None msgid ".. image:: images/en/category_projection/projection-cube_05.svg" -msgstr "" +msgstr ".. image:: images/en/category_projection/projection-cube_05.svg" #: ../../general_concepts/projection/orthographic_oblique.rst:None msgid ".. image:: images/en/category_projection/projection-cube_06.svg" -msgstr "" +msgstr ".. image:: images/en/category_projection/projection-cube_06.svg" #: ../../general_concepts/projection/orthographic_oblique.rst:None msgid ".. image:: images/en/category_projection/projection_image_01.png" -msgstr "" +msgstr ".. image:: images/en/category_projection/projection_image_01.png" #: ../../general_concepts/projection/orthographic_oblique.rst:None msgid ".. image:: images/en/category_projection/projection_image_02.png" -msgstr "" +msgstr ".. image:: images/en/category_projection/projection_image_02.png" #: ../../general_concepts/projection/orthographic_oblique.rst:None msgid ".. image:: images/en/category_projection/projection_image_03.png" -msgstr "" +msgstr ".. image:: images/en/category_projection/projection_image_03.png" #: ../../general_concepts/projection/orthographic_oblique.rst:None msgid ".. image:: images/en/category_projection/projection_image_04.png" -msgstr "" +msgstr ".. image:: images/en/category_projection/projection_image_04.png" #: ../../general_concepts/projection/orthographic_oblique.rst:None msgid ".. image:: images/en/category_projection/projection_image_05.png" -msgstr "" +msgstr ".. image:: images/en/category_projection/projection_image_05.png" #: ../../general_concepts/projection/orthographic_oblique.rst:None msgid ".. image:: images/en/category_projection/projection_image_06.png" -msgstr "" +msgstr ".. image:: images/en/category_projection/projection_image_06.png" #: ../../general_concepts/projection/orthographic_oblique.rst:None msgid ".. image:: images/en/category_projection/projection_image_07.png" -msgstr "" +msgstr ".. image:: images/en/category_projection/projection_image_07.png" #: ../../general_concepts/projection/orthographic_oblique.rst:None msgid ".. image:: images/en/category_projection/projection_image_08.png" -msgstr "" +msgstr ".. image:: images/en/category_projection/projection_image_08.png" #: ../../general_concepts/projection/orthographic_oblique.rst:None msgid ".. image:: images/en/category_projection/projection_image_09.png" -msgstr "" +msgstr ".. image:: images/en/category_projection/projection_image_09.png" #: ../../general_concepts/projection/orthographic_oblique.rst:None msgid ".. image:: images/en/category_projection/projection_image_10.png" -msgstr "" +msgstr ".. image:: images/en/category_projection/projection_image_10.png" #: ../../general_concepts/projection/orthographic_oblique.rst:None msgid ".. image:: images/en/category_projection/projection_image_11.png" -msgstr "" +msgstr ".. image:: images/en/category_projection/projection_image_11.png" #: ../../general_concepts/projection/orthographic_oblique.rst:None msgid ".. image:: images/en/category_projection/projection_image_12.png" -msgstr "" +msgstr ".. image:: images/en/category_projection/projection_image_12.png" #: ../../general_concepts/projection/orthographic_oblique.rst:None msgid ".. image:: images/en/category_projection/projection_image_13.png" -msgstr "" +msgstr ".. image:: images/en/category_projection/projection_image_13.png" #: ../../general_concepts/projection/orthographic_oblique.rst:None msgid ".. image:: images/en/category_projection/projection_image_14.png" -msgstr "" +msgstr ".. image:: images/en/category_projection/projection_image_14.png" #: ../../general_concepts/projection/orthographic_oblique.rst:None msgid ".. image:: images/en/category_projection/projection_animation_01.gif" -msgstr "" +msgstr ".. image:: images/en/category_projection/projection_animation_01.gif" #: ../../general_concepts/projection/orthographic_oblique.rst:1 msgid "Orthographics and oblique projection." -msgstr "" +msgstr "Ortografia e projecção oblíqua." #: ../../general_concepts/projection/orthographic_oblique.rst:10 msgid "So let's start with the basics..." -msgstr "" +msgstr "Bem, vamos começar pelo básico..." #: ../../general_concepts/projection/orthographic_oblique.rst:16 msgid "Orthographic" msgstr "Ortográfica" #: ../../general_concepts/projection/orthographic_oblique.rst:18 msgid "" "Despite the fancy name, you probably know what orthographic is. It is a " "schematic representation of an object, draw undeformed. Like the following " "example:" -msgstr "" +msgstr "Apesar do nome bonito, provavelmente já sabe o que é a ortográfica. É uma representação em esquema de um objecto, desenhada sem deformações. Como o seguinte exemplo:" #: ../../general_concepts/projection/orthographic_oblique.rst:23 msgid "" "This is a rectangle. We have a front, top and side view. Put into " "perspective it should look somewhat like this:" -msgstr "" +msgstr "Isto é um rectângulo. Temos a vista frontal, de topo e lateral. Colocando em perspectiva, deverá ficar algo semelhante a isto:" #: ../../general_concepts/projection/orthographic_oblique.rst:28 msgid "" "While orthographic representations are kinda boring, they're also a good " "basis to start with when you find yourself in trouble with a pose. But we'll " "get to that in a bit." -msgstr "" +msgstr "Embora as representações ortográficas sejam um pouco aborrecidas, são também uma boa base para começar quando se deparar com problemas numa pose. Mas iremos lá chegar daqui a pouco." #: ../../general_concepts/projection/orthographic_oblique.rst:33 msgid "Oblique" msgstr "Oblíquo" #: ../../general_concepts/projection/orthographic_oblique.rst:35 msgid "" "So, if we can say that the front view is the viewer looking at the front, " "and the side view is the viewer directly looking at the side. (The " "perpendicular line being the view plane it is projected on)" -msgstr "" +msgstr "Por isso, se pudermos afirmar que a vista frontal é o observador a olhar para a parte da frente, e a vista lateral é o observador a olhar directamente para um dos lados. (A linha perpendicular é o plano de observação sobre o qual está projectado)" #: ../../general_concepts/projection/orthographic_oblique.rst:40 msgid "Then we can get a half-way view from looking from an angle, no?" -msgstr "" +msgstr "Assim podemos obter uma vista a meio-caminho para observar a partir de um dado ângulo, não?" #: ../../general_concepts/projection/orthographic_oblique.rst:45 msgid "If we do that for a lot of different sides…" -msgstr "" +msgstr "Se o fizermos para uma variedade de lados diferentes…" #: ../../general_concepts/projection/orthographic_oblique.rst:50 msgid "And we line up the sides we get a…" -msgstr "" +msgstr "E alinharmos os lados, iremos obter um…" #: ../../general_concepts/projection/orthographic_oblique.rst:55 msgid "" "But cubes are boring. I am suspecting that projection is so ignored because " "no tutorial applies it to an object where you actually might NEED " "projection. Like a face." -msgstr "" +msgstr "Mas os cubos são aborrecidos. Suspeito que essa projecção é assim ignorada, porque nenhum tutorial a aplica a um objecto onde realmente PRECISA da projecção. Como uma cara." #: ../../general_concepts/projection/orthographic_oblique.rst:57 msgid "First, let's prepare our front and side views:" -msgstr "" +msgstr "Primeiro, vamos preparar as nossas vistas frontal e laterais:" #: ../../general_concepts/projection/orthographic_oblique.rst:62 msgid "" "I always start with the side, and then extrapolate the front view from it. " "Because you are using Krita, set up two parallel rulers, one vertical and " "the other horizontal. To snap them perfectly, drag one of the nodes after " "you have made the ruler, and press :kbd:`Shift` to snap it horizontal or " "vertical. In 3.0, you can also snap them to the image borders if you have :" "menuselection:`Snap to image borders` active via :kbd:`Shift` + :kbd:`S`" -msgstr "" +msgstr "O autor começa sempre pelo lado, extrapolando depois a vista frontal a partir dela. Como está a usar o Krita, configure duas réguas paralelas, uma vertical e a outra horizontal. Para as ajustar perfeitamente, desenhe um dos nós após ter criado a régua e depois carregue em :kbd:`Shift` para a ajustar na horizontal ou na vertical. No 3.0, também poderá ajustá-las aos contornos das imagnes, caso tenha a opção :menuselection:`Ajustar aos contornos das imagens` com a opção :kbd:`Shift` + :kbd:`S`" #: ../../general_concepts/projection/orthographic_oblique.rst:64 msgid "" "Then, by moving the mirror to the left, you can design a front-view from the " "sideview, while the parallel preview line helps you with aligning the eyes " "(which in the above screenshot are too low)." -msgstr "" +msgstr "Depois, ao mover o espelho para a esquerda, poderá desenhar uma vista frontal a partir da vista lateral, enquanto a linha de antevisão paralela o ajuda a alinhar os olhos (que na imagem acima estão muito baixos)." #: ../../general_concepts/projection/orthographic_oblique.rst:66 msgid "Eventually, you should have something like this:" -msgstr "" +msgstr "Eventualmente, deverá ter algo do género:" #: ../../general_concepts/projection/orthographic_oblique.rst:71 msgid "And of course, let us not forget the top, it's pretty important:" -msgstr "" +msgstr "E, obviamente, não nos esqueçamos do topo, que é bastante importante:" #: ../../general_concepts/projection/orthographic_oblique.rst:78 msgid "" "When you are using Krita, you can just use transform masks to rotate the " "side view for drawing the top-view." -msgstr "" +msgstr "Quando estiver a usar o Krita, poderá simplesmente usar máscaras de transformação para rodar a vista lateral para desenhar a vista de topo." #: ../../general_concepts/projection/orthographic_oblique.rst:80 msgid "" "The top view works as a method for debugging your orthos as well. If we take " "the red line to figure out the orthographics from, we see that our eyes are " "obviously too inset. Let's move them a bit more forward, to around the nose." -msgstr "" +msgstr "A vista de topo funciona como um método para depuração das suas ortografias. Se usarmos a linha vermelha para descobrir a ortografia, veremos que os nossos olhos estão demasiado para dentro. Vamos avançá-los um pouco mais, para perto do nariz." #: ../../general_concepts/projection/orthographic_oblique.rst:85 msgid "" "If you want to do precision position moving in the tool options docker, just " "select 'position' and the input box for the X. Pressing down then moves the " "transformed selection left. With Krita 3.0 you can just use the move tool " "for this and the arrow keys. Using transform here can be more convenient if " "you also have to squash and stretch an eye." -msgstr "" +msgstr "Se quiser movimentos com precisão na área de opções da ferramenta, basta seleccionar 'posição'e o campo de texto do X. Se carregar para baixo, move a selecção transformada para a esquerda. Com o Krita 3.0, poderá simplesmente usar a ferramenta de movimento para isto, em conjunto com as teclas de cursores. O uso da transformação aqui pode ser mais conveniente se também tiver de esmagar ou esticar um olho." #: ../../general_concepts/projection/orthographic_oblique.rst:90 msgid "We fix the top view now. Much better." -msgstr "" +msgstr "Corrigimos agora a vista de topo. Muito melhor." #: ../../general_concepts/projection/orthographic_oblique.rst:92 msgid "" "For faces, the multiple slices are actually pretty important. So important " "even, that I have decided we should have these slices on separate layers. " "Thankfully, I chose to colour them, so all we need to do is go to :" "menuselection:`layers --> split layer` ." -msgstr "" +msgstr "Para as caras, as várias fatias são de facto bastante importantes. Tão importantes que decidimos que essas fatias devem estar em camadas separadas. Felizmente, optámos por colori-las, pelo que tudo o que é necessário fazer é ir a :menuselection:`camadas --> dividir a camada` ." #: ../../general_concepts/projection/orthographic_oblique.rst:98 msgid "" "This'll give you a few awkwardly named layers… rename them by selecting all " "and mass changing the name in the properties editor:" -msgstr "" +msgstr "Isto irá gerar algumas camadas com nomes estranhos… mude o nome delas, seleccionando-as todas e mudando o nome em lote no editor de propriedades:" #: ../../general_concepts/projection/orthographic_oblique.rst:103 msgid "So, after some cleanup, we should have the following:" -msgstr "" +msgstr "Assim, depois de alguma limpeza, deveremos ter o seguinte:" #: ../../general_concepts/projection/orthographic_oblique.rst:108 msgid "Okay, now we're gonna use animation for the next bit." -msgstr "" +msgstr "Ok, agora iremos usar a animação para o próximo pedaço." #: ../../general_concepts/projection/orthographic_oblique.rst:110 msgid "Set it up as follows:" -msgstr "" +msgstr "Configure-o como se segue:" #: ../../general_concepts/projection/orthographic_oblique.rst:115 msgid "" "Both frontview and sideview are set up as 'visible in timeline' so we can " "always see them." -msgstr "" +msgstr "Tanto a vista frontal como a lateral estão configuradas como `visíveis na linha temporal`, pelo que podemos vê-las sempre." #: ../../general_concepts/projection/orthographic_oblique.rst:116 msgid "" "Frontview has its visible frame on frame 0 and an empty-frame on frame 23." -msgstr "" +msgstr "A vista frontal tem a sua imagem visível na imagem 0 e uma imagem vazia na imagem 23." #: ../../general_concepts/projection/orthographic_oblique.rst:117 msgid "" "Side view has its visible frame on frame 23 and an empty view on frame 0." -msgstr "" +msgstr "A vista lateral tem a sua imagem visível na imagem 23 e uma imagem vazia na imagem 0." #: ../../general_concepts/projection/orthographic_oblique.rst:118 msgid "The end of the animation is set to 23." -msgstr "" +msgstr "O fim da animação está configurado como 23." #: ../../general_concepts/projection/orthographic_oblique.rst:123 msgid "" "Krita can't animate a transformation on multiple layers on multiple frames " "yet, so let's just only transform the top layer. Add a semi-transparent " "layer where we draw the guide-lines." -msgstr "" +msgstr "O Krita ainda não consegue animar uma transformação em várias camadas com várias imagens, pelo que iremos apenas transformar a camada de topo. Adicione uma camada semi-transparente onde são desenhadas as linhas-guias." #: ../../general_concepts/projection/orthographic_oblique.rst:125 msgid "" "Now, select frame 11 (halfway), add new frames from frontview, sideview and " "the guide-lines. And turn on the onion skin by toggling the lamp symbols. We " "copy the frame for the top-view and use the transform tool to rotate it 45°." -msgstr "" +msgstr "Agora, seleccione a imagem 11 (a meio-caminho), adicione novas imagens da vista frontal, da vista lateral e das linhas-guias. Depois, active a 'pele de cebola', ligando todos os símbolos de lâmpadas. Iremos copiar a imagem para a vista de topo e iremos usar a ferramenta de transformação para a rodar em 45°." #: ../../general_concepts/projection/orthographic_oblique.rst:130 msgid "So, we draw our vertical guides again and determine a in-between..." -msgstr "" +msgstr "Assim, desenhamos as nossas guias verticais de novo e determinar um ponto intermédio..." #: ../../general_concepts/projection/orthographic_oblique.rst:135 msgid "" "This is about how far you can get with only the main slice, so rotate the " "rest as well." -msgstr "" +msgstr "Isto é o máximo que consegue obter apenas com a fatia principal, portanto rode o resto também." #: ../../general_concepts/projection/orthographic_oblique.rst:140 msgid "And just like with the cube, we do this for all slices…" -msgstr "" +msgstr "E tal como acontece com o cubo, fazemos isso para todas as fatias…" #: ../../general_concepts/projection/orthographic_oblique.rst:145 msgid "" "Eventually, if you have the top slices rotate every frame with 15°, you " "should be able to make a turn table, like this:" -msgstr "" +msgstr "Eventualmente, se tivermos as fatias de topo a rodar em 15° por cada imagem, deverá conseguir fazer uma rotação completa, como a seguinte:" #: ../../general_concepts/projection/orthographic_oblique.rst:150 msgid "" "(Because our boy here is fully symmetrical, you can just animate one side " "and flip the frames for the other half) (While it is not necessary to follow " "all the steps in the theory section to understand the tutorial, I do " "recommend making a turn table sometime. It teaches you a lot about drawing " "3/4th faces." -msgstr "" +msgstr "(Dado que o nosso rapaz aqui é completamente simétrico, podemos simplesmente animar um lado e inverter as imagens para o outro lado) (Embora não seja necessário seguir todos os passos da secção teórica para compreender o tutorial, recomenda-se que crie uma imagem rotativa em alguma altura. Ensina-lhe bastante sobre o desenho de caras em 3/4." #: ../../general_concepts/projection/orthographic_oblique.rst:153 msgid "How about… we introduce the top view into the drawing itself?" -msgstr "" +msgstr "E agora… se introduzíssemos a vista de topo no desnho em si?" diff --git a/locale/pt_PT/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po b/locale/pt_PT/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po index 2ca88b7cd..e68e30003 100644 --- a/locale/pt_PT/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po +++ b/locale/pt_PT/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po @@ -1,226 +1,226 @@ # 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-02-23 03:24+0100\n" -"PO-Revision-Date: 2019-02-28 17:35+0000\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" +"PO-Revision-Date: 2019-03-14 11:50+0000\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: Kritadeformbrushuseundeformed optionsize en\n" "X-POFile-SpellExtra: liquifymode deformbrush icons optiondeform image\n" "X-POFile-SpellExtra: optionrotation optionopacitynflow optionbrushtip Bi\n" "X-POFile-SpellExtra: Kritadeformbrushcolordeform blendingmodes\n" "X-POFile-SpellExtra: Kritadeformbrushexamples images ref\n" "X-POFile-SpellExtra: Kritadeformbrushbilinear optionairbrush\n" #: ../../:1 msgid "Use Undeformed Image" msgstr "Usar uma Imagem Não-Deformada" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:1 msgid "The Deform Brush Engine manual page." msgstr "A página de manual do Motor de Pincéis por Deformação." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:16 msgid "Deform Brush Engine" msgstr "Motor de Pincéis por Deformação" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:19 msgid ".. image:: images/icons/deformbrush.svg" msgstr ".. image:: images/icons/deformbrush.svg" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:20 msgid "" "The Deform Brush is a brush that allows you to pull and push pixels around. " "It's quite similar to the :ref:`liquify_mode`, but where liquify has higher " "quality, the deform brush has the speed." msgstr "" "O Pincel de Deformação é um pincel que lhe permite empurrar e puxar os " "pixels à volta. É bastante semelhante ao :ref:`liquify_mode`, mas onde a " "liquidificação tem melhor qualidade, o pincel de deformação tem a velocidade." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:24 msgid "Options" msgstr "Opções" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:26 msgid ":ref:`option_brush_tip`" msgstr ":ref:`option_brush_tip`" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:27 msgid ":ref:`option_deform`" msgstr ":ref:`option_deform`" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:28 msgid ":ref:`blending_modes`" msgstr ":ref:`blending_modes`" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:29 msgid ":ref:`option_opacity_n_flow`" msgstr ":ref:`option_opacity_n_flow`" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:30 msgid ":ref:`option_size`" msgstr ":ref:`option_size`" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:31 msgid ":ref:`option_rotation`" msgstr ":ref:`option_rotation`" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:32 msgid ":ref:`option_airbrush`" msgstr ":ref:`option_airbrush`" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:38 msgid "Deform Options" msgstr "Opções de Deformação" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:42 msgid ".. image:: images/en/Krita_deform_brush_examples.png" msgstr ".. image:: images/en/Krita_deform_brush_examples.png" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:42 msgid "" "1: undeformed, 2: Move, 3: Grow, 4: Shrink, 5: Swirl Counter Clock Wise, 6: " "Swirl Clockwise, 7: Lens Zoom In, 8: Lens Zoom Out" msgstr "" "1: não deformado, 2: Mover, 3: Crescer, 4: Encolher, 5: Enrolar no Sentido " "Anti-Horário, 6: Enrolar no Sentido Horário, 7: Ampliação da Lente, 8: " "Redução da Lenta" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:44 msgid "These decide what strangeness may happen underneath your brush cursor." msgstr "" "Isto decide qual o efeito estranho que poderá acontecer debaixo do cursor do " "seu pincel." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:46 msgid "Grow" msgstr "Crescer" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:47 msgid "This bubbles up the area underneath the brush-cursor." msgstr "Isto borbulha a área por baixo do cursor." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:48 msgid "Shrink" msgstr "Encolher" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:49 msgid "This pinches the Area underneath the brush-cursor." msgstr "Isto pica a área por baixo do cursor." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:50 msgid "Swirl Counter Clock Wise" msgstr "Enrolar no Sentido Anti-Horário" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:51 msgid "Swirls the area counter clock wise." msgstr "Enrola a área no sentido contrário aos ponteiros do relógio." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:52 msgid "Swirl Clock Wise" msgstr "Enrolar no Sentido Horário" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:53 msgid "Swirls the area clockwise." msgstr "Enrola a área no sentido dos ponteiros do relógio." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:54 msgid "Move" msgstr "Mover" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:55 msgid "Nudges the area to the painting direction." msgstr "Desvia a área na direcção da pintura." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:56 msgid "Color Deformation" msgstr "Deformação das Cores" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:57 -msgid "This seems to randomly rearrange the pixels underneath the brush," +msgid "This seems to randomly rearrange the pixels underneath the brush." msgstr "" "Isto parece reorganizar de forma aleatória os pixels por baixo do pincel." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:58 msgid "Lens Zoom In" msgstr "Ampliação da Lente" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:59 msgid "Literally paints a enlarged version of the area." msgstr "Pinta literalmente uma versão alargada da área." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:61 msgid "Lens Zoom Out" msgstr "Redução da Lente" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:61 msgid "Paints a minimized version of the area." msgstr "Pinta uma versão minimizada da área." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:65 msgid ".. image:: images/en/Krita_deform_brush_colordeform.png" msgstr ".. image:: images/en/Krita_deform_brush_colordeform.png" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:65 msgid "Showing color deform." msgstr "Demonstração da deformação das cores." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:68 msgid "Deform Amount" msgstr "Quantidade de Deformação" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:68 msgid "Defines the strength of the deformation." msgstr "Define a potência da deformação." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:72 msgid ".. image:: images/en/Krita_deform_brush_bilinear.png" msgstr ".. image:: images/en/Krita_deform_brush_bilinear.png" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:72 #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:74 msgid "Bilinear Interpolation" msgstr "Interpolação Bi-linear" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:75 msgid "Smoothens the result. This causes calculation errors in 16bit." msgstr "Suaviza o resultado. Isto provoca erros de cálculo a 16 bits." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:77 msgid "Use Counter" msgstr "Usar um Contador" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:77 msgid "Slows down the deformation subtlety." msgstr "Desacelera de forma subtil a deformação." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:81 msgid ".. image:: images/en/Krita_deform_brush_useundeformed.png" msgstr ".. image:: images/en/Krita_deform_brush_useundeformed.png" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:81 msgid "Without 'use undeformed' to the left and with to the right" -msgstr "Sem a opção 'usar a não-deformada' à esquerda ae com ela à direita" +msgstr "Sem a opção 'usar a não-deformada' à esquerda e com ela à direita" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:84 msgid "" "Samples from the previous version of the image instead of the current. This " "works better with some deform options than others. Move for example seems to " "almost stop working, but it works really well with Grow." msgstr "" "Cria amostras da versão anterior da imagem em vez da actual. Isto funciona " "melhor com algumas opções de deformação que com outras. O movimento, por " "exemplo, parece que deixa de funcionar, mas resulta realmente bem com o " "Crescimento." diff --git a/locale/pt_PT/LC_MESSAGES/reference_manual/brushes/brush_engines/hatching_brush_engine.po b/locale/pt_PT/LC_MESSAGES/reference_manual/brushes/brush_engines/hatching_brush_engine.po index 593807244..c241511cc 100644 --- a/locale/pt_PT/LC_MESSAGES/reference_manual/brushes/brush_engines/hatching_brush_engine.po +++ b/locale/pt_PT/LC_MESSAGES/reference_manual/brushes/brush_engines/hatching_brush_engine.po @@ -1,307 +1,396 @@ # 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-02-22 03:25+0100\n" "PO-Revision-Date: 2019-03-13 17:54+0000\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: hatchingbrush icons guilabel image Moiré Pentalis\n" "X-POFile-SpellExtra: Moire images subpixel\n" #: ../../:1 msgid ".. image:: images/en/Krita-tutorial8-A.II.png" msgstr ".. image:: images/en/Krita-tutorial8-A.II.png" #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:1 msgid "The Hatching Brush Engine manual page." msgstr "A página de manual do Motor de Pincéis Tracejados." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:17 msgid "Hatching Brush Engine" msgstr "Motor de Pincéis Tracejado" #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:21 msgid ".. image:: images/icons/hatchingbrush.svg" msgstr ".. image:: images/icons/hatchingbrush.svg" #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:22 msgid "" "When I first tried this brush, my impression of it was \"plain parallel lines" "\" (and the award for most boring brush goes to...). Fortunately, existing " "presets gave me an idea of the possibilities of this brush." -msgstr "Quando o autor experimentou este pincel pela primeira vez, a primeira impressão foi \"linhas paralelas simples\" (o que parecia um pouco aborrecido...). Felizmente, as predefinições existentes dão uma ideia das possibilidades deste pincel." +msgstr "" +"Quando o autor experimentou este pincel pela primeira vez, a primeira " +"impressão foi \"linhas paralelas simples\" (o que parecia um pouco " +"aborrecido...). Felizmente, as predefinições existentes dão uma ideia das " +"possibilidades deste pincel." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:25 msgid "Settings" msgstr "Configuração" #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:28 msgid "Brush tip" msgstr "Ponta do pincel" #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:30 msgid "" "The brush tip simply defines the area where the hatching will be rendered." -msgstr "A ponta do pincel simplesmente define a área onde será desenhado o padrão tracejado." +msgstr "" +"A ponta do pincel simplesmente define a área onde será desenhado o padrão " +"tracejado." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:32 msgid "" "Transparent brush tip areas give more transparent hatching, but as with a " "normal brush, passing over the area again will increase opacity." -msgstr "As áreas das pontas de pincéis transparentes geram um um tracejado mais transparente, mas como acontece com um pincel normal, a passagem sobre a área de novo irá aumentar a opacidade." +msgstr "" +"As áreas das pontas de pincéis transparentes geram um um tracejado mais " +"transparente, mas como acontece com um pincel normal, a passagem sobre a " +"área de novo irá aumentar a opacidade." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:33 msgid "" "The hatching itself is mostly fixed in location, so drawing with a hatching " "brush usually acts more like \"revealing\" the hatching underneath than " "drawing with brushes of parallel lines. The exception is for :guilabel:" "`Moiré pattern` with :guilabel:`Crosshatching` dynamics on." -msgstr "O tracejado em si está principalmente fixo a nível da localização, pelo que o desenho com um pincel tracejado funciona mais como se revelasse o padrão tracejado atrás, do que propraimente desenhar com pincéis de linhas paralelas. A excepção é o :guilabel:`Padrão Moiré` com o parâmetro dinâmico de :guilabel:`Cruzamento` ligado." +msgstr "" +"O tracejado em si está principalmente fixo a nível da localização, pelo que " +"o desenho com um pincel tracejado funciona mais como se revelasse o padrão " +"tracejado atrás, do que propraimente desenhar com pincéis de linhas " +"paralelas. A excepção é o :guilabel:`Padrão Moiré` com o parâmetro dinâmico " +"de :guilabel:`Cruzamento` ligado." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:34 msgid "" "Vary the brush shape or texture for a variety of effects. Decreasing the " "density of the autobrush will give a grainy texture to your hatching, for " "example." -msgstr "Varia a forma ou textura do pincel para uma grande variedade de efeitos. Se diminuir a densidade do pincel automático, irá obter uma textura granulada para o seu tracejado, por exemplo." +msgstr "" +"Varia a forma ou textura do pincel para uma grande variedade de efeitos. Se " +"diminuir a densidade do pincel automático, irá obter uma textura granulada " +"para o seu tracejado, por exemplo." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:35 msgid "" "The :guilabel:`Size` dynamic affects the brush tip, not the hatching " "thickness." -msgstr "A opção dinâmica :guilabel:`Tamanho` afecta a ponta do pincel, não a espessura do tracejado." +msgstr "" +"A opção dinâmica :guilabel:`Tamanho` afecta a ponta do pincel, não a " +"espessura do tracejado." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:38 msgid ".. image:: images/en/Krita-tutorial8-A.I.1.png" msgstr ".. image:: images/en/Krita-tutorial8-A.I.1.png" #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:40 msgid "Hatching preferences" msgstr "Preferências do cruzamento" #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:42 msgid "" "Before going on: at the time of this writing, there is a bug that causes " "line thickness to not vary on default settings. To get around this, go to :" "guilabel:`Hatching preferences` and check :guilabel:`Antialiased Lines`. " "Pentalis is aware of this issue so the bug may get fixed soon." -msgstr "Antes de prosseguir: na altura em que isto foi escrito, existia um erro que fazia com que a espessura da linha não variasse com a configuração por omissão. Para dar a volta a isto, vá às :guilabel:`Preferências do cruzamento` e assinale as :guilabel:`Linhas Suavizadas`. O Pentalis está a par deste problema, pelo que o erro poderá ser corrigido em breve." +msgstr "" +"Antes de prosseguir: na altura em que isto foi escrito, existia um erro que " +"fazia com que a espessura da linha não variasse com a configuração por " +"omissão. Para dar a volta a isto, vá às :guilabel:`Preferências do " +"cruzamento` e assinale as :guilabel:`Linhas Suavizadas`. O Pentalis está a " +"par deste problema, pelo que o erro poderá ser corrigido em breve." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:44 msgid "The three options are:" msgstr "As três opções são:" #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:46 msgid "" ":guilabel:`Antialiased lines`: This controls aliasing. If changing line " "thickness isn't working, check this option and it should work, because it " "switches to a different algorithm." -msgstr ":guilabel:`Linhas suavizadas`: Isto controla a suavização ou não das linhas. Se a mudança da espessura não funcionar, assinale esta opção para que a mesma funcione, dado que muda para um algoritmo diferente." +msgstr "" +":guilabel:`Linhas suavizadas`: Isto controla a suavização ou não das linhas. " +"Se a mudança da espessura não funcionar, assinale esta opção para que a " +"mesma funcione, dado que muda para um algoritmo diferente." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:47 msgid "" ":guilabel:`Subpixel precision`: I'm guessing this affects the rendering " "quality, but you won't see much of a difference. Check this if you want to." -msgstr ":guilabel:`Precisão ao subpixel`: Assume-se que isto afecta a qualidade do desenho, mas não irá ver grande diferença. Assinale isto se quiser." +msgstr "" +":guilabel:`Precisão ao subpixel`: Assume-se que isto afecta a qualidade do " +"desenho, mas não irá ver grande diferença. Assinale isto se quiser." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:48 msgid "" ":guilabel:`Color background`: Checking this will color in the background at " "the back of the hatching." -msgstr ":guilabel:`Fundo de cor`: Se assinalar isto, irá colorir no fundo do tracejado." +msgstr "" +":guilabel:`Fundo de cor`: Se assinalar isto, irá colorir no fundo do " +"tracejado." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:50 msgid "" "The output is slightly different depending on whether the first two options " "are checked, but the difference isn't enough for you to worry about. I " "recommend just keeping the first two options checked." -msgstr "O resultado é ligeiramente diferente, dependendo se as primeiras duas opções estão assinaladas, mas a diferença não é suficiente para se preocupar. Recomenda-se que deixe as primeiras duas opções assinaladas." +msgstr "" +"O resultado é ligeiramente diferente, dependendo se as primeiras duas opções " +"estão assinaladas, mas a diferença não é suficiente para se preocupar. " +"Recomenda-se que deixe as primeiras duas opções assinaladas." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:53 msgid ".. image:: images/en/Krita-tutorial8-A.I.2.png" msgstr ".. image:: images/en/Krita-tutorial8-A.I.2.png" #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:55 msgid "Hatching options" msgstr "Opções de cruzamento" #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:57 msgid "This is where the main hatching options go. They're intuitive enough:" -msgstr "Aqui é onde a opções principais do tracejado se encontram. São suficientemente intuitivas:" +msgstr "" +"Aqui é onde a opções principais do tracejado se encontram. São " +"suficientemente intuitivas:" #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:59 msgid "Angle: The angle of the hatching." msgstr "Ângulo: O ângulo do padrão tracejado." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:60 msgid "Separation: This is the distance between the centers of the lines." msgstr "Separação: Esta é a distância entre os centros das linhas." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:62 msgid "" "Use a value of 2 pixels or higher, or the lines won't be distinct anymore." -msgstr "Use um valor de 2 pixels ou superior, caso contrário as linhas não serão mais distintas." +msgstr "" +"Use um valor de 2 pixels ou superior, caso contrário as linhas não serão " +"mais distintas." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:63 msgid "" "The Separations dynamic doesn't actually assign random values to Separation, " "instead it will take the value in \"Input-based intervals\" to divide the " "grid further. \"Input-based intervals\" can take values between 2 and 7." -msgstr "O valor dinâmico Separações não atribui de facto valores aleatórios à Separação; em vez disso, irá usar o valor em \"Intervalos de entrada\" para dividir ainda mais a grelha. Os \"Intervalos de entrada\" podem receber valores entre 2 e 7." +msgstr "" +"O valor dinâmico Separações não atribui de facto valores aleatórios à " +"Separação; em vez disso, irá usar o valor em \"Intervalos de entrada\" para " +"dividir ainda mais a grelha. Os \"Intervalos de entrada\" podem receber " +"valores entre 2 e 7." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:65 msgid "Thickness: The line thickness." msgstr "Espessura: A espessura da linha." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:67 msgid "" "Actually, this is the thickness of the line + blank area, so the line itself " "has a thickness of half this value." -msgstr "De facto, esta é a espessura da linha + área em branco, pelo que a linha em si tem uma espessura correspondente a metade deste valor." +msgstr "" +"De facto, esta é a espessura da linha + área em branco, pelo que a linha em " +"si tem uma espessura correspondente a metade deste valor." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:68 msgid "" "If you use the same separation value and the same line thickness value, then " "the lines and the area between them will be of the same thickness." -msgstr "Se usar o mesmo valor de separação e da espessura da linha, então as linhas e a área entre elas terá a mesma espessura." +msgstr "" +"Se usar o mesmo valor de separação e da espessura da linha, então as linhas " +"e a área entre elas terá a mesma espessura." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:69 msgid "You can vary this value dynamically with the Thickness dynamics." -msgstr "Poderá variar este valor de forma dinâmica com o parâmetro dinâmico Espessura." +msgstr "" +"Poderá variar este valor de forma dinâmica com o parâmetro dinâmico " +"Espessura." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:70 msgid "" "If the line thickness isn't changing for you, go to Hatching Preferences and " "check \"Antialiased Lines.\"" -msgstr "Se a espessura da linha não variar o suficiente para si, vá às Preferências do Cruzamento e assinale as \"Linhas Suavizadas.\"" +msgstr "" +"Se a espessura da linha não variar o suficiente para si, vá às Preferências " +"do Cruzamento e assinale as \"Linhas Suavizadas.\"" #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:72 msgid "" "Origin X and Origin Y: The hatching has a fixed location, painting acts as " "though you're revealing the existing hatching underneath. To nudge the " "hatching, you can tweak these two values. You can get various grid effects " "this way." -msgstr "X e Y da Origem: O padrão tracejado tem uma localização fixa, sendo que a pintura funciona como se estivesse a revelar o padrão tracejado atrás. Para desviar o tracejado, poderá afinar estes dois valores. Poderá obter diversos efeitos de grelha desta forma." +msgstr "" +"X e Y da Origem: O padrão tracejado tem uma localização fixa, sendo que a " +"pintura funciona como se estivesse a revelar o padrão tracejado atrás. Para " +"desviar o tracejado, poderá afinar estes dois valores. Poderá obter diversos " +"efeitos de grelha desta forma." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:75 msgid ".. image:: images/en/Krita-tutorial8-A.I.3-1.png" msgstr ".. image:: images/en/Krita-tutorial8-A.I.3-1.png" #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:76 msgid "Finally, we have the hatching styles:" msgstr "Finalmente, temos os estilos tracejados:" #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:78 msgid "No crosshatching: basic parallel lines" msgstr "Sem cruzamento: linhas paralelas básicas" #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:79 msgid "Perpendicular plane only: grid lines" msgstr "Apenas no plano perpendicular: linhas de grelha" #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:80 msgid "-45 degrees plane then +45 degrees plane: see example." msgstr "Plano a -45 graus e depois plano a +45 graus: veja o exemplo." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:81 msgid "" "+45 degrees plane then -45 degrees plane: see example, actually not much " "different from the above, it's mostly the order that changes when using " "dynamics." -msgstr "Plano a +45 graus e depois plano a -45 graus: veja o exemplo. De facto, não é muito diferente do anterior, sendo mais relevante a ordem que muda, usando os parâmetros dinâmicos." +msgstr "" +"Plano a +45 graus e depois plano a -45 graus: veja o exemplo. De facto, não " +"é muito diferente do anterior, sendo mais relevante a ordem que muda, usando " +"os parâmetros dinâmicos." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:82 msgid "Moiré pattern: See example." msgstr "Padrão Moiré: Veja o exemplo." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:84 msgid "" "The Crosshatching dynamic only works if you have already chosen a " "crosshatching style. When that happens, the crosshatching only gets drawn " "according to the conditions of the dynamics (pressure, speed, angle...)." -msgstr "O parâmetro dinâmico de Cruzamento só funciona se já tiver escolhido um estilo de cruzamento. Quando isso acontece, o cruzamento só é desenhado de acordo com as condições dos parâmetros dinâmicos (pressão, velocidade, ângulo...)." +msgstr "" +"O parâmetro dinâmico de Cruzamento só funciona se já tiver escolhido um " +"estilo de cruzamento. Quando isso acontece, o cruzamento só é desenhado de " +"acordo com as condições dos parâmetros dinâmicos (pressão, velocidade, " +"ângulo...)." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:86 msgid "" "With most hatching styles, using crosshatching dynamics basically gets you " "the same hatching style, minus the occasional line." -msgstr "Com a maioria dos estilos tracejados, o uso de parâmetros de cruzamento basicamente gera-lhe o mesmo padrão tracejado, exceptuando as linhas ocasionais." +msgstr "" +"Com a maioria dos estilos tracejados, o uso de parâmetros de cruzamento " +"basicamente gera-lhe o mesmo padrão tracejado, exceptuando as linhas " +"ocasionais." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:87 msgid "The exception is with Moire, which will produce a different pattern." -msgstr "A excepção acontece com o Moire, o qual irá produzir um padrão diferente." +msgstr "" +"A excepção acontece com o Moire, o qual irá produzir um padrão diferente." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:90 msgid ".. image:: images/en/Krita-tutorial8-A.I.3-2.png" msgstr ".. image:: images/en/Krita-tutorial8-A.I.3-2.png" #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:92 msgid "Use cases" msgstr "Casos de uso" #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:94 msgid "" "If you don't want the edges to be fuzzy, go to Brush Tip and set the Fade " "values to 1.00. I recommended doing the hatching on a separate layer, then " "erasing the extra areas." -msgstr "Se não quiser que as arestas fiquem difusas, vá à Ponta do Pincel e configure os valores de Desvanecimento como 1,00. Recomenda-se o uso do tracejado numa camada separada, apagando depois as áreas a mais." +msgstr "" +"Se não quiser que as arestas fiquem difusas, vá à Ponta do Pincel e " +"configure os valores de Desvanecimento como 1,00. Recomenda-se o uso do " +"tracejado numa camada separada, apagando depois as áreas a mais." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:96 msgid "Now for the uses:" msgstr "Agora para as utilizações em si:" #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:98 msgid "" "You can, of course, just use this for completely normal hatching. In " "versions I'm using, the default Separation is 1, which is too low, so " "increase Separation to a value between 2 to 10." -msgstr "Poderá, como é óbvio, usar isto apenas para padrões tracejados completamente normais. Nas versões usadas pelo autor da documentação, a Separação predefinida é 1, que é mais demasiado baixa; por isso, aumente a Separação para um valor entre 2 e 10." +msgstr "" +"Poderá, como é óbvio, usar isto apenas para padrões tracejados completamente " +"normais. Nas versões usadas pelo autor da documentação, a Separação " +"predefinida é 1, que é mais demasiado baixa; por isso, aumente a Separação " +"para um valor entre 2 e 10." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:99 msgid "" "If you find normal hatching too boring, increase the Thickness and set the " "Thickness dynamic to either Pressure (if you have a tablet) or Speed (if " "you're using a mouse). Doesn't that look more natural? (When using a mouse, " "pass over the areas where you want thicker lines again while drawing faster)" -msgstr "Se achar que o padrão tracejado é demasiado aborrecido, aumente a Espessura e configure o parâmetro dinâmico de Espessura com base na Pressão (se tiver uma tablete) ou na Velocidade (se tiver um rato). Não lhe parece mais natural? (Ao usar um rato, passe mais depressa sobre as áreas onde deseja ter linhas mais grossas ao desenhar)" +msgstr "" +"Se achar que o padrão tracejado é demasiado aborrecido, aumente a Espessura " +"e configure o parâmetro dinâmico de Espessura com base na Pressão (se tiver " +"uma tablete) ou na Velocidade (se tiver um rato). Não lhe parece mais " +"natural? (Ao usar um rato, passe mais depressa sobre as áreas onde deseja " +"ter linhas mais grossas ao desenhar)" #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:100 msgid "" "Grittier texture: add some density and/or randomness to your autobrush for a " "grittier texture." -msgstr "Textura arenosa: adicione alguma densidade e/ou aleatoriedade ao seu pincel automático para obter uma textura arenosa." +msgstr "" +"Textura arenosa: adicione alguma densidade e/ou aleatoriedade ao seu pincel " +"automático para obter uma textura arenosa." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:101 msgid "" "You can also set Painting Mode to Build up, and Mode to Multiply, to make " "some colors have more depth. (see my grid example)" -msgstr "Também poderá configurar o Modo de Pintura para Composição e o Modo para Multiplicação, para fazer com que algumas cores tenham mais profundidade. (ver o exemplo da grelha)" +msgstr "" +"Também poderá configurar o Modo de Pintura para Composição e o Modo para " +"Multiplicação, para fazer com que algumas cores tenham mais profundidade. " +"(ver o exemplo da grelha)" #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:102 msgid "Vary Origin X and Origin Y while using the same patterns." msgstr "Varie o X e o Y da Origem ao usar os mesmos padrões." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:103 msgid "" "Use the Separations dynamic for more complex patterns. Add in Line Thickness " "and other dynamics for more effect." -msgstr "Use o parâmetro dinâmico de Separações para obter padrões mais complexos. Adicione a Espessura da Linha e outros parâmetros para obter mais efeitos." +msgstr "" +"Use o parâmetro dinâmico de Separações para obter padrões mais complexos. " +"Adicione a Espessura da Linha e outros parâmetros para obter mais efeitos." #: ../../reference_manual/brushes/brush_engines/hatching_brush_engine.rst:104 msgid "" "Now, the Moiré pattern is quite boring on its own, but it is much more " "interesting with Crosshatching dynamics set on Fuzzy.** For more texture, " "set Line Thickness to Fuzzy, decrease Density a bit and increase Randomness " "and you get a nice gritty texture." -msgstr "Agora, o padrão Moiré é bastante aborrecido por si só, mas fica muito ais interessante com o padrão de Cruzamento configurado como Difuso.** Para mais textura, configure a Espessura da Linha como Difusa, diminua um pouco a Densidade e aumente a Aleatoriedade para obter uma textura arenosa mais agradável." +msgstr "" +"Agora, o padrão Moiré é bastante aborrecido por si só, mas fica muito ais " +"interessante com o padrão de Cruzamento configurado como Difuso.** Para mais " +"textura, configure a Espessura da Linha como Difusa, diminua um pouco a " +"Densidade e aumente a Aleatoriedade para obter uma textura arenosa mais " +"agradável." diff --git a/locale/pt_PT/LC_MESSAGES/reference_manual/layers_and_masks/layer_styles.po b/locale/pt_PT/LC_MESSAGES/reference_manual/layers_and_masks/layer_styles.po index 007facc34..7442c208c 100644 --- a/locale/pt_PT/LC_MESSAGES/reference_manual/layers_and_masks/layer_styles.po +++ b/locale/pt_PT/LC_MESSAGES/reference_manual/layers_and_masks/layer_styles.po @@ -1,68 +1,66 @@ # 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-02-19 03:36+0100\n" -"PO-Revision-Date: 2019-02-26 11:12+0000\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" +"PO-Revision-Date: 2019-03-14 11:49+0000\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: Krita Fx program menuselection Photoshop\n" +"X-POFile-SpellExtra: Krita Fx program menuselection Photoshop guilabel\n" #: ../../reference_manual/layers_and_masks/layer_styles.rst:1 msgid "How to use layer styles in Krita." msgstr "Como usar os estilos das camadas no Krita." #: ../../reference_manual/layers_and_masks/layer_styles.rst:17 msgid "Layer Styles" msgstr "Estilos da Camada" #: ../../reference_manual/layers_and_masks/layer_styles.rst:19 msgid "" "Layer styles are effects that are added on top of your layer. They are " "editable and can easily be toggled on and off. To add a layer style to a " "layer go to :menuselection:`Layer --> Layer Style`. You can also right-click " "a layer to access the layer styles." msgstr "" "Os estilos da camada são os efeitos que são aplicados sobre a sua camada. " "Eles são editáveis e podem ser facilmente activados ou desactivados. Para " "adicionar um estilo à camada, vá a :menuselection:`Camada --> Estilo da " "Camada`. Também poderá carregar com o botão direito sobre uma camada para " "aceder aos estilos da mesma." #: ../../reference_manual/layers_and_masks/layer_styles.rst:22 msgid "" -"When you have the layer styles window up, make sure that the \"Enable Effects" -"\" is checked." -msgstr "" -"Quando tiver visível a janela de estilos da camada, certifique-se que a " -"opção \"Activar os Efeitos\" está assinalada." +"When you have the layer styles window up, make sure that the :guilabel:" +"`Enable Effects` item is checked." +msgstr "Quando tiver visível a janela de estilos da camada, certifique-se que a opção :guilabel:`Activar os Efeitos` está assinalada." #: ../../reference_manual/layers_and_masks/layer_styles.rst:24 msgid "" "There are a variety of effects and styles you can apply to a layer. When you " "add a style, your layer docker will show an extra \"Fx\" icon. This allows " "you to toggle the layer style effects on and off." msgstr "" "Existe uma grande variedade de efeitos e estilos que poderá aplicar a uma " "camada. Quando adicionar um estilo, a sua área da camada irá mostrar um " "ícone \"Fx\" extra. Isto permite-lhe activar ou desactivar os efeitos do " "estilo da camada." #: ../../reference_manual/layers_and_masks/layer_styles.rst:30 msgid "" "This feature was added to increase support for :program:`Adobe Photoshop`. " "The features that are included mirror what that application supports." msgstr "" "Esta funcionalidade foi adicionada para aumentar o suporte para o :program:" "`Adobe Photoshop`. As funcionalidades que estão incluídas reflectem o que " "essa aplicação suporta." diff --git a/locale/pt_PT/LC_MESSAGES/reference_manual/render_animation.po b/locale/pt_PT/LC_MESSAGES/reference_manual/render_animation.po index 4f3c6f9c7..920921832 100644 --- a/locale/pt_PT/LC_MESSAGES/reference_manual/render_animation.po +++ b/locale/pt_PT/LC_MESSAGES/reference_manual/render_animation.po @@ -1,407 +1,416 @@ # 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-02-25 03:36+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-03-12 14:18+0000\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: FFMpeg Chrome guilabel Flash menuselection high MKV\n" "X-POFile-SpellExtra: palettegen export baseline OSX FFMPeg VLC gif usr bin\n" "X-POFile-SpellExtra: Keka FFMPEG exe ffmpeg Krita FFmpeg Player\n" #: ../../reference_manual/render_animation.rst:1 msgid "How to use the render animation command in Krita." msgstr "Como usar o comando para desenhar uma animação no Krita." #: ../../reference_manual/render_animation.rst:17 #: ../../reference_manual/render_animation.rst:42 msgid "Render Animation" msgstr "Desenhar a Animação" #: ../../reference_manual/render_animation.rst:19 msgid "" "Render animation allows you to render your animation to an image sequence, " "gif, mp4, mkv, or ogg file. It replaces :guilabel:`Export Animation` ." msgstr "" "O desenho da animação permite-lhe gerar uma sequência de imagens da sua " "animação para um ficheiro GIF, MP4, MKV ou OGG. Substitui a opção :guilabel:" "`Exportar a Animação` ." #: ../../reference_manual/render_animation.rst:21 msgid "" "For rendering to an animated fileformat, Krita will first render to a png " "sequence and then use FFMpeg, which is really good at encoding into video " "files, to render that sequence to an animated fileformat. The reason for " "this two-step process is that animation files can be really complex and " "really big, and this is the best way to allow you to keep control over the " "export process. For example, if your computer has a hiccup, and one frame " "saves out weird, first saving the image sequence allows you to only resave " "that one weird frame before rendering." msgstr "" "Para desenhar num formato de ficheiro animado, o Krita irá primeiro desenhar " "uma sequência de PNG's e depois irá usar o FFMpeg, que já é realmente bom na " "codificação de ficheiros de vídeo, para representar essa sequência num " "formato de ficheiros animado. A razão para esse processo em dois passos é " "que os ficheiros da animação podem ser realmente complexos e realmente " "grandes, sendo esta forma a que lhe permite manter melhor o controlo sobre o " "processo de exportação. Por exemplo, se o seu computador tiver um problema e " "uma imagem sair estranha, a gravação em primeiro lugar da sequência de " "imagens permite-lhe gravar de novo apenas essa imagem estragada antes de " "gerar a animação." #: ../../reference_manual/render_animation.rst:23 msgid "" "This means that you will need to find a good place to stick your frames " "before you can start rendering. If you only do throwaway animations, you can " "use a spot on your hard-drive with enough room and select :guilabel:`Delete " "Sequence After Rendering`" msgstr "" "Isto significa que terá de encontrar um bom local onde colocar as suas " "imagens antes de iniciar o desenho. Se só cria animações descartáveis, " "poderá usar um local no seu disco rígido com bastante espaço e seleccionar a " "opção :guilabel:`Apagar a Sequência Após o Desenho`" #: ../../reference_manual/render_animation.rst:26 msgid "Image Sequence" msgstr "Sequência de Imagens" #: ../../reference_manual/render_animation.rst:28 msgid "Base Name" msgstr "Nome de Base" #: ../../reference_manual/render_animation.rst:29 msgid "" "The base name of your image sequence. This will get suffixed with a number " "depending on the frame." msgstr "" "O nome de base da sua sequência de imagens. Isto irá obter um sufixo com um " "número que depende da imagem." #: ../../reference_manual/render_animation.rst:30 msgid "File Format" msgstr "Formato do Ficheiro" #: ../../reference_manual/render_animation.rst:31 msgid "" "The fileformat to export the sequence to. When rendering we enforce png. The " "usual export options can be modified with :guilabel:`...`." msgstr "" "O formato do ficheiro para o qual exportar a sequência. Ao desenhar, será " "forçado o uso do PNG. Podem-se modificar as opções de exportação normais com " "o :guilabel:`...`." #: ../../reference_manual/render_animation.rst:32 msgid "Render Location" msgstr "Localização do Desenho" #: ../../reference_manual/render_animation.rst:33 msgid "" "Where you render the image sequence to. Some people prefer to use a flash-" "drive or perhaps a harddrive that is fast." msgstr "" "Para onde será gravada a sequência de imagens. Algumas pessoas preferem usar " "um disco Flash ou um disco rígido que seja rápido." #: ../../reference_manual/render_animation.rst:34 msgid "First Frame" msgstr "Primeira Imagem" #: ../../reference_manual/render_animation.rst:35 msgid "" "The first frame of the range of frame you wish to adjust. Automatically set " "to the first frame of your current selection in the timeline. This is useful " "when you only want to re-render a little part." msgstr "" "A primeira imagem da gama de imagens que pretende ajustar. Configurada " "automaticamente com a primeira imagem da sua selecção actual na linha " "temporal. Isto é útil quando só pretende desenhar de novo uma pequena parte." #: ../../reference_manual/render_animation.rst:36 msgid "Last Frame" msgstr "Última Imagem" #: ../../reference_manual/render_animation.rst:37 msgid "" "As above, the last frame of the range of frame you wish to adjust. " "Automatically set to the last frame of your current selection in the " "timeline." msgstr "" "Como acontece acima, a última imagem da gama de imagens que pretende " "ajustar. Configurada automaticamente com a última imagem da sua selecção " "actual na linha temporal." #: ../../reference_manual/render_animation.rst:39 msgid "Naming Sequence starts with" msgstr "A Sequência de Nomes começa em" #: ../../reference_manual/render_animation.rst:39 msgid "" "The frames are named by using :guilabel:`Base Name` above and adding a " "number for the frame. This allows you to set where the frame number starts, " "so rendering from 8 to 10 with starting point 3 will give you images named " "11 and 15. Useful for programs that don't understand sequences starting with " "0, or for precision output." msgstr "" "As imagens terão um nome baseado no :guilabel:`Nome de Base` acima e " "adicionando o número da imagem. Isto permite-lhe definir onde começa o " "número da imagem, pelo que se desejar exportar a imagem 8 à 10, com um ponto " "inicial igual 3, irá ter as imagens de 11 a 13. É útil para os programas que " "não compreendam as sequências que comecem em 0 ou para resultados com " "precisão." #: ../../reference_manual/render_animation.rst:44 msgid "Render As" msgstr "Desenhar Como" #: ../../reference_manual/render_animation.rst:45 msgid "" "The file format to render to. All except gif have extra options that can be " "manipulated via :guilabel:`...`." msgstr "" "O formato do ficheiro que será gerado. Todos os formatos, excepto o GIF, têm " "opções extra que poderão ser manipuladas com o :guilabel:`...`." #: ../../reference_manual/render_animation.rst:46 msgid "File" msgstr "Ficheiro" #: ../../reference_manual/render_animation.rst:47 msgid "Location and name of the rendered animation." msgstr "A localização e o nome da animação desenhada." #: ../../reference_manual/render_animation.rst:48 msgid "FFMpeg" msgstr "FFMpeg" #: ../../reference_manual/render_animation.rst:49 msgid "" "The location where your have ffmpeg. If you don't have this, Krita cannot " "render an animation. For proper gif support, you will need ffmpeg 2.6, as we " "use its palettegen functionality." msgstr "" "A localização onde se encontra o 'ffmpeg'. Se não o tiver, o Krita não " "conseguirá desenhar uma animação. Para o suporte adequado para GIF, será " "necessário o FFMpeg 2.6, já que é usada a sua função 'palettegen'." #: ../../reference_manual/render_animation.rst:51 msgid "Delete Sequence After Rendering" msgstr "Apagar a Sequência Após o Desenho" #: ../../reference_manual/render_animation.rst:51 msgid "" "Delete the prerendered image sequence after done rendering. This allows you " "to choose whether to try and save some space, or to save the sequence for " "when encoding fails." msgstr "" "Apaga a sequência de imagens pré-desenhada após o desenho. Isto permite-lhe " "escolher se deseja experimentar e poupar algum espaço ou gravar a sequência " "quando a codificação falha." #: ../../reference_manual/render_animation.rst:55 msgid "" "None of the video formats support saving from images with a transparent " "background, so Krita will try to fill it with something. You should add a " "background color yourself to avoid it from using, say, black." msgstr "" "Nenhum dos formatos de vídeo suportam a gravação a partir de imagens com um " "fundo transparente, como tal o Krita irá tentar preenchê-lo com algo. Poderá " "adicionar você mesmo uma cor de fundo para evitar que seja usado, por " "exemplo, o preto." #: ../../reference_manual/render_animation.rst:58 msgid "Setting Up Krita for Exporting Animations" msgstr "Configuração do Krita para Exportar as Animações" #: ../../reference_manual/render_animation.rst:60 msgid "" "You will need to download an extra application and link it in Krita for it " "to work. The application is pretty big (50MB), so the Krita developers " "didn't want to bundle it with the normal application. The software that we " "will use is free and called FFMpeg. The following instructions will explain " "how to get it and set it up. The setup is a one-time thing so you won't have " "to do it again." msgstr "" "Terá de obter uma aplicação extra e associá-la ao Krita para funcionar. A " "aplicação é relativamente grande (50MB), sendo por isso que os programadores " "do Krita não o incluem com a aplicação normal. A aplicação que será usada é " "gratuita e chama-se FFMpeg. As seguintes instruções irão explicar como obtê-" "la e configurá-la. A configuração é algo que é feito uma única vez, sendo " "que não terá de o fazer de novo." #: ../../reference_manual/render_animation.rst:63 msgid "Step 1 - Downloading FFMpeg" msgstr "Passo 1 - Obter o FFMpeg" #: ../../reference_manual/render_animation.rst:66 #: ../../reference_manual/render_animation.rst:86 msgid "For Windows" msgstr "Para o Windows" #: ../../reference_manual/render_animation.rst:68 msgid "" "Go to the ffmpeg website (http://ffmpeg.org/download.html). The URL that had " "the link for me was here... https://ffmpeg.zeranoe.com/builds/" msgstr "" "Vá à página Web do FFMpeg (http://ffmpeg.org/download.html). O URL que tinha " "a ligação para o autor da documentação estava aqui... https://ffmpeg.zeranoe." "com/builds/" #: ../../reference_manual/render_animation.rst:70 +#, fuzzy +#| msgid "" +#| "Watch out for the extremely annoying google ad that looks like a download " +#| "button! There is no big button for what we need. Either get the 64-bit " +#| "STATIC version or 32-bit STATIC version that is shown later down the " +#| "page. If you bought a computer in the past 5 years, you probably want the " +#| "64-bit version. Make sure you get a exe file, if you hover over the " +#| "options they will give more information about what exactly you are " +#| "downloading." msgid "" -"Watch out for the extremely annoying google ad that looks like a download " +"Watch out for the extremely annoying google and that looks like a download " "button! There is no big button for what we need. Either get the 64-bit " "STATIC version or 32-bit STATIC version that is shown later down the page. " "If you bought a computer in the past 5 years, you probably want the 64-bit " "version. Make sure you get a exe file, if you hover over the options they " "will give more information about what exactly you are downloading." msgstr "" "Tenha atenção ao anúncio extremamente irritante da Google que parece um " "botão de transferência! Não existe nenhum botão grande para o que é " "necessário. Pode transferir a versão ESTÁTICA em 64 bits ou a versão " "ESTÁTICA em 32 bits que aparece mais abaixo na página. Se comprou um " "computador nos últimos 5 anos, provavelmente irá desejar a versão a 64 bits. " "Certifique-se que obtém um ficheiro .exe; caso passe o cursor sobre as " "opções, elas irão dar mais alguma informação sobre o que está a transferir " "ao certo." #: ../../reference_manual/render_animation.rst:73 #: ../../reference_manual/render_animation.rst:93 msgid "For OSX" msgstr "Para o OSX" #: ../../reference_manual/render_animation.rst:75 msgid "" "Please see the section above. However, FFmpeg is obtained from https://" "evermeet.cx/ffmpeg/ instead. Just pick the big green button on the left " "under the FFmpeg heading. You will also need an archiving utility that " "supports .7z, since ffmpeg provides their OSX builds in .7z format. If you " "don't have one, try something like Keka (http://www.kekaosx.com)." msgstr "" "Por favor, veja a secção acima. Contudo, o FFMpeg é obtido a partir do " "https://evermeet.cx/ffmpeg/ em alternativa. Basta escolher o pequeno botão " "verde à esquerda debaixo do cabeçalho do FFmpeg. Irá também necessitar de um " "utilitário de descompressão de pacotes que suporte o .7z, dado que o " "'ffmpeg' oferece as suas versões para OSX no formato .7z. Se não tiver um " "utilitário desses, experimente algum como o Keka (http://www.kekaosx.com)." #: ../../reference_manual/render_animation.rst:78 #: ../../reference_manual/render_animation.rst:98 msgid "For Linux" msgstr "Para o Linux" #: ../../reference_manual/render_animation.rst:80 msgid "" "FFMPeg can be installed from the repositories on most Linux systems. Version " "2.6 is required for proper gif support, as we use the palettegen " "functionality." msgstr "" "O FFMPeg pode ser instalado a partir dos repositórios das maior parte dos " "sistemas Linux. É necessária a versão 2.6 para o suporte adequado para " "GIF's, dado que é usada a funcionalidade 'palettegen'." #: ../../reference_manual/render_animation.rst:83 msgid "Step 2 - Unzipping and Linking to Krita" msgstr "Passo 2 - Descomprimir e Associar ao Krita" #: ../../reference_manual/render_animation.rst:88 msgid "" "Unzip the package that was just downloaded. Rename the long folder name to " "just ffmpeg. Let's put this folder in a easy to find location. go to your C:" "\\ and place it there. You can put it wherever you want, but that is where I " "put it." msgstr "" "Descomprima o pacote que acabou de transferir. Mude o nome comprido da pasta " "para apenas 'ffmpeg'. Coloque essa pasta num local fácil de encontrar. Vá à " "sua unidade C:\\ e coloque-a lá. Poderá colocá-la onde desejar, de qualquer " "forma, mas para o exemplo assume-se este local." #: ../../reference_manual/render_animation.rst:90 msgid "" "Open Krita back up and go to :menuselection:`File --> Render Animation`. " "Click the :guilabel:`Browse` button on the last item called FFMpeg. Select " "this file ``C:/ffmpeg/bin/ffmpeg.exe`` and click :guilabel:`OK` ." msgstr "" "Abra o Krita de novo e vá a :menuselection:`Ficheiro --> Desenhar a " "Animação`. Carregue no botão :guilabel:`Escolher` no último item chamado " "FFMpeg. Seleccione este ficheiro ``C:/ffmpeg/bin/ffmpeg.exe`` e carregue " "em :guilabel:`OK` ." #: ../../reference_manual/render_animation.rst:95 msgid "" "After downloading ffmpeg, you just need to extract it and then simply point " "to it in the FFMPEG location in Krita like ``/Users/user/Downloads/ffmpeg`` " "(assuming you downloaded and extracted the .7z file to /Users/user/" "Downloads)." msgstr "" "Depois de obter o FFMpeg, só precisa de o extrair e apontar para ele na " "localização do FFMPEG no Krita, como por exemplo ``/Utilizadores/utilizador/" "Transferências/ffmpeg`` (assumindo que transferiu e extraiu o ficheiro .7z " "para /Utilizadores/utilizador/Transferências)." #: ../../reference_manual/render_animation.rst:100 msgid "" "FFMpeg is, if installed from the repositories, usually found in ``/usr/bin/" "ffmpeg``" msgstr "" "O FFMpeg está, se tiver sido instalado a partir dos repositórios, localizado " "normalmente em ``/usr/bin/ffmpeg``" #: ../../reference_manual/render_animation.rst:103 msgid "Step 3 - Testing out an animation" msgstr "Passo 3 - Experimentar uma animação" #: ../../reference_manual/render_animation.rst:105 msgid "" "ffmpeg.exe is what Krita uses to do all of its animation export magic. Now " "that it is hooked up, let us test it out." msgstr "" "O 'ffmpeg.exe' é o que o Krita usa para fazer toda a sua magia de exportação " "de animações. Agora que isso está tudo configurado, vamos experimentar." #: ../../reference_manual/render_animation.rst:107 msgid "" "Let's make an animated GIF. in the Render Animation dialog, change the :" "guilabel:`Render As` field to \"GIF image\". Choose the file location where " "it will save with the \"File\" menu below. I just saved it to my desktop and " "called it \"export.gif\". When it is done, you should be able to open it up " "and see the animation." msgstr "" "Vamos criar um GIF animado. Na janela para Desenhar a Animação, mude o " "campo :guilabel:`Desenhar Como` como \"imagem GIF\". Escolha a localização " "do ficheiro onde será gravada com o menu \"Ficheiro\" abaixo. No caso do " "autor, foi gravado no ecrã e atribuiu-se o nome \"export.gif\". Quando " "terminar, deverá ser possível abri-lo e ver a animação." #: ../../reference_manual/render_animation.rst:111 msgid "" "By default, FFMPEG will render MP4 files with a too new codec, which means " "that windows media player won't be able to play it. So for windows, select " "\"baseline\" for the profile instead of \"high422\" before rendering." msgstr "" "Por omissão, o FFMPEG irá desenhar os ficheiros MP4 com um codificador " "bastante recente, o que significa que provavelmente o Windows Media Player " "não o conseguirá abrir. Por isso, no caso do Windows, seleccione o perfil " "\"baseline\" em vez do \"high422\" antes de o desenhar." #: ../../reference_manual/render_animation.rst:115 msgid "" "OSX does not come with any software to play MP4 and MKV files. If you use " "Chrome for your web browser, you can drag the video file into that and the " "video should play. Otherwise you will need to get a program like VLC to see " "the video." msgstr "" "O OSX não vem com qualquer aplicação para ler ficheiros MP4 e MKV. Se usar o " "Chrome como navegador Web, poderá arrastar o ficheiro do vídeo para dentro " "dele e o vídeo deverá começar a reproduzir. Caso contrário, irá precisar de " "um programa como o VLC para ver o vídeo." diff --git a/locale/pt_PT/LC_MESSAGES/reference_manual/resource_management/resource_gradients.po b/locale/pt_PT/LC_MESSAGES/reference_manual/resource_management/resource_gradients.po index c16918a22..d1c0c84d5 100644 --- a/locale/pt_PT/LC_MESSAGES/reference_manual/resource_management/resource_gradients.po +++ b/locale/pt_PT/LC_MESSAGES/reference_manual/resource_management/resource_gradients.po @@ -1,306 +1,312 @@ # 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-03-03 03:22+0100\n" -"PO-Revision-Date: 2019-03-13 17:58+0000\n" +"PO-Revision-Date: 2019-03-14 14:26+0000\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: Kritastopgradient en GradientToolbarPanel mouseright\n" +"X-POFile-SpellExtra: icons Krita Kritastopsuddenchange image\n" +"X-POFile-SpellExtra: Kritamouseleft Kritamouseright Kritagradienthsvcw\n" +"X-POFile-SpellExtra: Kritasegmentgradientoptions images Kritanewgradient\n" +"X-POFile-SpellExtra: alt mouseleft KritaEditingCustomGradient\n" +"X-POFile-SpellExtra: Kritagradientsegmentblending Kritamovestop\n" #: ../../:1 msgid "HSV counter-clock wise." msgstr "HSV anti-horário." #: ../../: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" #: ../../reference_manual/resource_management/resource_gradients.rst:None msgid ".. image:: images/en/Krita_new_gradient.png" msgstr ".. image:: images/en/Krita_new_gradient.png" #: ../../reference_manual/resource_management/resource_gradients.rst:None msgid ".. image:: images/en/Krita_stop_gradient.png" msgstr ".. image:: images/en/Krita_stop_gradient.png" #: ../../reference_manual/resource_management/resource_gradients.rst:None msgid ".. image:: images/en/Krita_move_stop.png" msgstr ".. image:: images/en/Krita_move_stop.png" #: ../../reference_manual/resource_management/resource_gradients.rst:None msgid ".. image:: images/en/Krita_stop_sudden_change.png" msgstr ".. image:: images/en/Krita_stop_sudden_change.png" #: ../../reference_manual/resource_management/resource_gradients.rst:None msgid ".. image:: images/en/Krita_segment_gradient_options.png" msgstr ".. image:: images/en/Krita_segment_gradient_options.png" #: ../../reference_manual/resource_management/resource_gradients.rst:None msgid ".. image:: images/en/Krita_gradient_segment_blending.png" msgstr ".. image:: images/en/Krita_gradient_segment_blending.png" #: ../../reference_manual/resource_management/resource_gradients.rst:None msgid ".. image:: images/en/Krita_gradient_hsv_cw.png" msgstr ".. image:: images/en/Krita_gradient_hsv_cw.png" #: ../../reference_manual/resource_management/resource_gradients.rst:1 msgid "Creating and managing gradients in Krita." msgstr "Criar e gerir os gradientes no Krita." #: ../../reference_manual/resource_management/resource_gradients.rst:16 msgid "Gradients" msgstr "Gradientes" #: ../../reference_manual/resource_management/resource_gradients.rst:19 msgid "Accessing a Gradient" msgstr "Aceder a um Gradiente" #: ../../reference_manual/resource_management/resource_gradients.rst:21 msgid "" "The Gradients configuration panel is accessed by clicking the Gradients icon " "(usually the icon next to the disk)." -msgstr "O painel de configuração dosd Gradientes é acedido ao carregar no ícone de Gradientes (normalmente o ícone a seguir ao disco)." +msgstr "O painel de configuração dos Gradientes é acedido ao carregar no ícone de Gradientes (normalmente o ícone a seguir ao disco)." #: ../../reference_manual/resource_management/resource_gradients.rst:24 msgid ".. image:: images/en/Gradient_Toolbar_Panel.png" msgstr ".. image:: images/en/Gradient_Toolbar_Panel.png" #: ../../reference_manual/resource_management/resource_gradients.rst:25 msgid "" "Gradients are configurations of blending between colors. Krita provides " "over a dozen preset dynamic gradients for you to choose from. In addition, " "you can design and save your own." -msgstr "" +msgstr "Os gradientes são configurações de mistura entre cores. O Krita oferece cerca de uma dúzia de gradientes dinâmicos predefinidos por onde escolher. Para além disso, poderá desenhar e criar os seus próprios." #: ../../reference_manual/resource_management/resource_gradients.rst:27 msgid "Some typical uses of gradients are:" msgstr "Alguns usos típicos dos gradientes são:" #: ../../reference_manual/resource_management/resource_gradients.rst:29 msgid "Fill for vector shapes." msgstr "Preenchimento de formas vectoriais." #: ../../reference_manual/resource_management/resource_gradients.rst:30 msgid "Gradient tool" msgstr "Ferramenta do gradiente" #: ../../reference_manual/resource_management/resource_gradients.rst:31 msgid "As a source of color for the pixel brush." msgstr "Como uma fonte de cores para o pincel de pixels." #: ../../reference_manual/resource_management/resource_gradients.rst:33 msgid "" "There is no gradients docker. They can only be accessed through the gradient " "\"quick-menu\" in the toolbar." -msgstr "Não existe nenhuma área de gradientes. Só poderá aceder aos mesmos através do \"menu rápido\" de gradientes na barra de ferramentas" +msgstr "Não existe nenhuma área de gradientes. Só poderá aceder aos mesmos através do \"menu rápido\" de gradientes na barra de ferramentas." #: ../../reference_manual/resource_management/resource_gradients.rst:36 msgid "Editing a Gradient" msgstr "Editar um Gradiente" #: ../../reference_manual/resource_management/resource_gradients.rst:38 msgid "Krita has two gradient types:" msgstr "O Krita tem dois tipos de gradientes:" #: ../../reference_manual/resource_management/resource_gradients.rst:40 msgid "" "Segmented Gradients, which are compatible with GIMP, have many different " "features but are also a bit complicated to make." -msgstr "" +msgstr "Os Gradientes Segmentados, que são compatíveis com o GIMP, têm muitas funcionalidades diferentes mas também são um pouco complicados de criar." #: ../../reference_manual/resource_management/resource_gradients.rst:41 msgid "" "Stop Gradients, which are saved as SVG files and similar to how most " "applications do their gradients, but has less features than the segmented " "gradient." -msgstr "" +msgstr "Os Gradientes com Paragens, que são gravados como ficheiros SVG e são semelhantes ao que a maioria das aplicações usa nos seus gradientes, mas que têm menos funcionalidades que os gradientes segmentados." #: ../../reference_manual/resource_management/resource_gradients.rst:43 msgid "" "Initially we could only make segmented gradients in Krita, but in 3.0.2 we " "can also make stop gradients." -msgstr "" +msgstr "Inicialmente, só era possível criar gradientes segmentados, mas no 3.0.2 passámos também a poder criar do outro tipo." #: ../../reference_manual/resource_management/resource_gradients.rst:48 msgid "" "You can make a new gradient by going into the drop-down and selecting the " "gradient type you wish to have. By default Krita will make a stop-gradient." -msgstr "" +msgstr "Poderá criar um novo gradiente se for à lista e seleccionar o tipo de gradiente que deseja ter. Por omissão, o Krita irá criar um gradiente com paragens." #: ../../reference_manual/resource_management/resource_gradients.rst:51 msgid "Stop Gradients" -msgstr "" +msgstr "Gradientes com Paragens" #: ../../reference_manual/resource_management/resource_gradients.rst:56 msgid "Stop gradients are very straight forward:" -msgstr "" +msgstr "Estes gradientes são bastante intuitivos:" #: ../../reference_manual/resource_management/resource_gradients.rst:58 msgid "|mouseleft| on the gradient to add a stop." -msgstr "" +msgstr "Use o |mouseleft| sobre o gradiente para adicionar uma paragem." #: ../../reference_manual/resource_management/resource_gradients.rst:59 msgid "|mouseleft| on the stops to select them, and drag to move them." -msgstr "" +msgstr "Use o |mouseleft| nas paragens para as seleccionar e arraste-as para as mover." #: ../../reference_manual/resource_management/resource_gradients.rst:60 msgid "" "|mouseright| on the stops to remove them. A stop gradient will not allow you " "to remove stops if there's only two left." -msgstr "" +msgstr "Use o |mouseright| sobre as paragens para as remover. Um gradiente com paragens não lhe permitirá remover paragens, caso já só existam duas." #: ../../reference_manual/resource_management/resource_gradients.rst:65 msgid "" "A selected stop can have its color and transparency changed using the color " "button and the opacity slider below." -msgstr "" +msgstr "Uma dada paragem poderá modificar a sua própria cor e transparência, usando o botão de cores e a barra de opacidade abaixo." #: ../../reference_manual/resource_management/resource_gradients.rst:70 msgid "" "As per SVG spec, you can make a sudden change between stops by moving them " "close together. The stops will overlap, but you can still drag them around." -msgstr "" +msgstr "De acordo com a norma SVG, poderá criar uma mudança brusca entre paragens, movendo umas para perto das outras. As paragens sobrepor-se-ão, mas poderá continuar a arrastá-las à mesma." #: ../../reference_manual/resource_management/resource_gradients.rst:73 msgid "Segmented Gradients" -msgstr "" +msgstr "Gradientes Segmentados" #: ../../reference_manual/resource_management/resource_gradients.rst:76 msgid ".. image:: images/en/Krita_Editing_Custom_Gradient.png" -msgstr "" +msgstr ".. image:: images/en/Krita_Editing_Custom_Gradient.png" #: ../../reference_manual/resource_management/resource_gradients.rst:77 msgid "" "Segmented gradients are a bit more tricky. Instead of going from color to " "color, it allows you to define segments, which each can have a begin and end " "color." -msgstr "" +msgstr "Os gradientes segmentados têm mais alguns truques. Em vez de irem de uma cor para outra, é permitida a definição de segmentos, onde cada qual poderá ter uma cor inicial e final." #: ../../reference_manual/resource_management/resource_gradients.rst:79 msgid "|mouseright| the gradient to call up this menu:" -msgstr "" +msgstr "Use o |mouseright| sobre o gradiente para invocar este menu:" #: ../../reference_manual/resource_management/resource_gradients.rst:84 msgid "Split Segment" msgstr "Separar o Segmento" #: ../../reference_manual/resource_management/resource_gradients.rst:85 msgid "" "This splits the current segment in two, using the white arrow, the segment " "middle as the place to split. It will also use the color at the white arrow " "to define the new colors in place in the new segments." -msgstr "" +msgstr "Isto separa o segmento actual em dois, usando a seta branca e com o centro do segmento como o local de divisão. Também irá usar a cor na seta branca para definir as novas cores no local dos novos segmentos." #: ../../reference_manual/resource_management/resource_gradients.rst:86 msgid "Duplicate segment" -msgstr "" +msgstr "Duplicar o segmento" #: ../../reference_manual/resource_management/resource_gradients.rst:87 msgid "" "Similar to split, but instead the two new segments are copies of the old one." -msgstr "" +msgstr "É semelhante à divisão, mas neste caso os dois novos segmentos são réplicas do antigo." #: ../../reference_manual/resource_management/resource_gradients.rst:88 msgid "Mirror segment." -msgstr "" +msgstr "Espelho do segmento." #: ../../reference_manual/resource_management/resource_gradients.rst:89 msgid "Mirrors the segment colors." -msgstr "" +msgstr "Cria um espelho das cores do segmento." #: ../../reference_manual/resource_management/resource_gradients.rst:91 msgid "Remove segment" -msgstr "" +msgstr "Remover o segmento" #: ../../reference_manual/resource_management/resource_gradients.rst:91 msgid "Removes the segment." -msgstr "" +msgstr "Remove o segmento." #: ../../reference_manual/resource_management/resource_gradients.rst:93 msgid "" "|mouseleft| + dragging the black arrows will resize the segments attaching " "to those arrows. |mouseleft| + dragging the white arrows will change the mid " "point of that segment, changing the way how the mixture is made." -msgstr "" +msgstr "Use o |mouseleft| + arraste as setas pretas para dimensionar os segmentos associados a essas setas. Use o |mouseleft| + arraste as setas brancas para modificar o ponto central desse segmento, mudando a forma como é feita a mistura." #: ../../reference_manual/resource_management/resource_gradients.rst:95 msgid "" "At the bottom, you can set the color and transparency of either part of the " "segment." -msgstr "" +msgstr "No fundo, poderá definir a cor e a transparência de qualquer parte do segmento." #: ../../reference_manual/resource_management/resource_gradients.rst:97 msgid "You can also set the blending. The first is the interpolation mode:" -msgstr "" +msgstr "Poderá também definir a mistura. A primeira opção é o modo de interpolação:" #: ../../reference_manual/resource_management/resource_gradients.rst:102 msgid "Linear - Does a linear blending between both segments." -msgstr "" +msgstr "Linear - Cria uma mistura linear entre ambos os segmentos." #: ../../reference_manual/resource_management/resource_gradients.rst:103 msgid "Curved - This causes the mix to ease-in and out faster." -msgstr "" +msgstr "Curvada - Isto faz com que exista uma aceleração ou desaceleração da mistura." #: ../../reference_manual/resource_management/resource_gradients.rst:104 msgid "" "Sine - Uses a sine function. This causes the mix to ease in and out slower." -msgstr "" +msgstr "Seno - Usa uma função sinusoidal. Isto faz com que a mistura acelere ou desacelere com uma progressão mais lenta." #: ../../reference_manual/resource_management/resource_gradients.rst:105 msgid "" "Sphere, increasing - This puts emphasis on the later color during the mix." -msgstr "" +msgstr "Esférica com aumento - Isto coloca alguma ênfase sobre a última cor, durante a mistura." #: ../../reference_manual/resource_management/resource_gradients.rst:106 msgid "" "Sphere, decreasing - This puts emphasis on the first color during the mix." -msgstr "" +msgstr "Esférica com diminuição - Isto coloca alguma ênfase sobre a primeira cor, durante a mistura." #: ../../reference_manual/resource_management/resource_gradients.rst:108 msgid "Finally, there's the model:" -msgstr "" +msgstr "Finalmente, aparece o modelo:" #: ../../reference_manual/resource_management/resource_gradients.rst:113 msgid "RGB" msgstr "RGB" #: ../../reference_manual/resource_management/resource_gradients.rst:114 msgid "Does the blending in RGB model." -msgstr "" +msgstr "Faz a mistura com base no modelo RGB." #: ../../reference_manual/resource_management/resource_gradients.rst:115 msgid "HSV clockwise" -msgstr "" +msgstr "HSV horário" #: ../../reference_manual/resource_management/resource_gradients.rst:116 msgid "" "Blends the two colors using the HSV model, and follows the hue clockwise " "(red-yellow-green-cyan-blue-purple). The above screenshot is an example of " "this." -msgstr "" +msgstr "Mistura as duas cores com base no modelo HSV, seguindo a tonalidade no sentido dos ponteiros do relógio (vermelho-amarelo-verde-cíano-azul-roxo). A imagem acima é um exemplo deste caso." #: ../../reference_manual/resource_management/resource_gradients.rst:118 msgid "Blends the color as the previous options, but then counter-clockwise." -msgstr "" +msgstr "Mistura a cor como nas opções acima, mas no sentido contrário aos ponteiros do relógio." diff --git a/locale/pt_PT/LC_MESSAGES/reference_manual/tools/colorize_mask.po b/locale/pt_PT/LC_MESSAGES/reference_manual/tools/colorize_mask.po index 84c3bc7af..1d4473b44 100644 --- a/locale/pt_PT/LC_MESSAGES/reference_manual/tools/colorize_mask.po +++ b/locale/pt_PT/LC_MESSAGES/reference_manual/tools/colorize_mask.po @@ -1,446 +1,446 @@ # 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-03-13 03:40+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-02-19 09:58+0000\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" #: ../../: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" #: ../../: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" #: ../../:60 msgid "" ".. image:: images/icons/colorizemask_tool.svg\n" " :alt: toolcolorizemask" msgstr "" -#: ../../reference_manual/tools/colorize_mask.rst:0 -msgid "" -".. image:: images/en/Krita_4_0_colorize_mask_show_output_edit_strokes.png" -msgstr "" - -#: ../../reference_manual/tools/colorize_mask.rst:0 -msgid ".. image:: images/en/Krita_4_0_colorize_mask_edge_detection.png" -msgstr "" - -#: ../../reference_manual/tools/colorize_mask.rst:0 -msgid ".. image:: images/en/Krita_4_0_colorize_mask_gap_close_hint.png" -msgstr "" - -#: ../../reference_manual/tools/colorize_mask.rst:0 -msgid ".. image:: images/en/Krita_4_0_colorize_mask_clean_up.png" -msgstr "" - #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_01.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_02.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_03.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_04.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_05.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_06.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_07.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_08.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_09.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_10.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_11.png" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:None msgid ".. image:: images/en/Krita_4_0_colorize_mask_usage_12.png" msgstr "" +#: ../../reference_manual/tools/colorize_mask.rst:0 +msgid "" +".. image:: images/en/Krita_4_0_colorize_mask_show_output_edit_strokes.png" +msgstr "" + +#: ../../reference_manual/tools/colorize_mask.rst:0 +msgid ".. image:: images/en/Krita_4_0_colorize_mask_edge_detection.png" +msgstr "" + +#: ../../reference_manual/tools/colorize_mask.rst:0 +msgid ".. image:: images/en/Krita_4_0_colorize_mask_gap_close_hint.png" +msgstr "" + +#: ../../reference_manual/tools/colorize_mask.rst:0 +msgid ".. image:: images/en/Krita_4_0_colorize_mask_clean_up.png" +msgstr "" + #: ../../reference_manual/tools/colorize_mask.rst:1 msgid "How to use the colorize mask in Krita." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:16 msgid "Colorize Mask" msgstr "Máscara de Coloração" #: ../../reference_manual/tools/colorize_mask.rst:18 msgid "|toolcolorizemask|" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:20 msgid "" "A tool for quickly coloring lineart, the Colorize Mask Editing tool can be " "found next to the gradient tool on your toolbox." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:22 msgid "" "This feature is technically already in 3.1, but disabled by default because " "we had not optimised the filling algorithm for production use yet. To enable " "it, find your krita configuration file, open it in notepad, and add " "\"disableColorizeMaskFeature=false\" to the top. Then restart Krita. Its " "official incarnation is in 4.0." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:26 msgid "Usage" msgstr "Utilização" #: ../../reference_manual/tools/colorize_mask.rst:28 msgid "" "This tool works in conjunction with the colorize mask, and the usage is as " "follows:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:30 msgid "" "For this example, we'll be using the ghost lady also used to explain masks " "on the basic concepts page." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:36 msgid "" "This image has the line art for the lady separated from the background, and " "what's more, the background is made up of two layers: one main and one for " "the details." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:38 msgid "" "First, select the colorize mask editing tool while having the lineart layer " "selected. |mouseleft| the canvas will add a colorize mask to the layer. You " "can also |mouseright| the line art layer, and then :menuselection:`Add --> " "Colorize Mask`. The line art will suddenly become really weird, this is the " "prefiltering which are filters through which we put the lineart to make the " "algorithm easier to use. The tool options overview below shows which options " "control that." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:45 msgid "" "Now, You make strokes with brush colors, press :guilabel:`Update` in the " "tool options, or tick the last icon of the colorize mask properties. In the " "layer docker, you will be able to see a little progress bar appear on the " "colorize mask indicating how long it takes. The bigger your file, the longer " "it will take." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:51 msgid "" "We want to have the blue transparent. In the tool options of the colorize " "editing tool you will see a small palette. These are the colors already " "used. You can remove colors here, or mark a single color as standing for " "transparent, by selecting it and pressing \"transparent\". Updating the mask " "will still show the blue stroke, but the result will be transparent:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:57 msgid "" "Because the colorize mask algorithm is slow, and we only need a part of our " "layer to be filled to fill the whole ghost lady figure, we can make use of :" "guilabel:`Limit to layer bounds`. This will limit Colorize Mask to use the " "combined size of the line art and the coloring key strokes. Therefore, make " "sure that the colorizing keystrokes only take up as much as they really need." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:63 msgid "" "Now the algorithm will be possibly a lot faster, allowing us to add strokes " "and press update in rapid succession:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:69 msgid "" "To see the final result, disable :guilabel:`Edit Key Strokes` or toggle the " "second to last icon on the colorize mask." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:75 msgid "" "If you want to edit the strokes again, re-enable :guilabel:`Edit Key " "Strokes`." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:77 msgid "" "Now, the colorize mask, being a mask, can also be added to a group of line " "art layers. It will then use the composition of the whole group as the line " "art. This is perfect for our background which has two separate line art " "layers. It also means that the colorize mask will be disabled when added to " "a group with pass-through enabled, because those have no final composition. " "You can recognise a disabled colorize mask because its name is stricken " "through." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:79 msgid "" "To add a colorize mask to a group, select the group and |mouseleft| the " "canvas with the Colorize Mask editing tool, or |mouseright| the layer to :" "menuselection:`Add --> Colorize Mask`." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:85 msgid "" "Now, we add strokes to the background quickly. We do not need to use the :" "menuselection:`Limit to Layer Bounds` because the background covers the " "whole image." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:91 msgid "" "For the record, you can use other brushes and tools also work on the " "colorize mask as long as they can draw. The Colorize Mask Editing tool is " "just the most convenient because you can get to the algorithm options." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:93 msgid "Out final result looks like this:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:99 msgid "" "Now we are done, |mouseright| the colorize mask and :menuselection:`Convert " "--> to Paint Layer`. Then, :menuselection:`Layer --> Split --> Split Layer`. " "This will give separate color islands that you can easily edit:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:105 msgid "" "This way we can very quickly paint the image. Due to the colorize mask going " "from the first image to the following took only 30 minutes, and would've " "taken quite a bit longer." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:111 msgid "" "The colorize masks are saved to the .kra file, so as long as you don't save " "and open to a different file format, nor convert the colorize mask to a " "paintlayer, you can keep working adjust the results." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:114 msgid "Tool Options" msgstr "Opções da Ferramenta" #: ../../reference_manual/tools/colorize_mask.rst:116 #: ../../reference_manual/tools/colorize_mask.rst:172 msgid "Update" msgstr "Actualizar" #: ../../reference_manual/tools/colorize_mask.rst:117 msgid "" "Run the colorize mask algorithm. The progress bar for updates on a colorize " "mask shows only in the layer docker." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:118 #: ../../reference_manual/tools/colorize_mask.rst:169 msgid "Edit key strokes" msgstr "Editar os traços-chave" #: ../../reference_manual/tools/colorize_mask.rst:119 msgid "" "Put the mask into edit mode. In edit mode, it will also show the 'pre-" "filtering' on the line-art, which is for example a blur filter for gap " "closing." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:121 msgid "" "Show the output of the colorize mask. If :guilabel:`Edit key strokes` is " "active, this will be shown semi-transparently, so it will be easy to " "recognise the difference between the strokes and the output." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:127 #: ../../reference_manual/tools/colorize_mask.rst:165 msgid "Show output" msgstr "Mostrar o resultado" #: ../../reference_manual/tools/colorize_mask.rst:127 msgid "" "On the **Left**: :guilabel:`Show Output` is on, :guilabel:`Edit Strokes` is " "off. In the **Middle**: :guilabel:`Show Output` and :guilabel:`Edit Strokes` " "are on. On the **Right**: :guilabel:`Show Output` is off and :guilabel:`Edit " "Strokes` is on.]]" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:129 msgid "Limit to layer bounds" msgstr "Limitar aos limites da camada" #: ../../reference_manual/tools/colorize_mask.rst:130 msgid "" "Limit the colorize mask to the combined layer bounds of the strokes and the " "line art it is filling. This can speed up the use of the mask on complicated " "compositions, such as comic pages." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:132 msgid "" "Activate this for line art with large solid areas, for example shadows on an " "object. For the best use, set the value to the thinnest lines on the image. " "In the image below, note how edge detection affects the big black areas:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:138 msgid "Edge detection" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:138 msgid "" "From left to right: an example with big black shadows on an object but no " "edge detection, the same example without the edit strokes enabled. Then the " "same example with edge detection enabled and set to 2px, and that same " "example with out edit strokes enabled." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:141 msgid "" "While the algorithm is pretty good against gaps in contours, this will " "improve the gap recognition. The higher this value is, the bigger the gaps " "it will try to close, but a too high value can lead to other errors. Note " "how the pre-filtered line art (that's the blurry haze) affects the color " "patches." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:146 msgid "Gap close hint" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:147 msgid "" "On the **Left**: :guilabel:`Gap close hint` is 0px. In the **Middle**: :" "guilabel:`Gap close hint` is 15px (the lines are 10px). On the **Right**: :" "guilabel:`Gap close hint` is 275px." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:149 msgid "" "This will attempt to handle messy strokes that overlap the line art where " "they shouldn't. At 0 no clean up is done, at 100% the clean-up is most " "aggressive." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:153 msgid "Clean-up strokes" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:155 msgid "Keystrokes" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:156 msgid "" "This palette keeps track of the colors used by the strokes. This is useful " "so you can switch back to colors easily. You can increase the swatch size by " "hovering over it with the mouse, and doing :kbd:`Ctrl +` |mousescroll|." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:158 msgid "Transparent" msgstr "Transparente" #: ../../reference_manual/tools/colorize_mask.rst:158 msgid "" "This button is under the keystrokes palette, you can mark the selected color " "to be interpreted a 'transparent' with this. In the clean-up screenshot " "above, cyan had been marked as transparent." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:161 msgid "Layer properties" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:163 msgid "" "The colorize mask layer has four properties. They are all the buttons on the " "right side of the layer:" msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:166 msgid "" "The first button, it allows you to toggle whether you'll see the output from " "the colorize algorithm." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:167 msgid "Lock" msgstr "Bloquear" #: ../../reference_manual/tools/colorize_mask.rst:168 msgid "Stops the mask from being edited." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:170 msgid "" "Whether the colorize mask is in edit mode. In edit mode it'll show the " "strokes, and the output will be semi-transparent." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:172 msgid "" "The last button will force the colorize mask to update, even when you're in " "a different tool." msgstr "" #: ../../reference_manual/tools/colorize_mask.rst:174 msgid "Colorize masks cannot be animated." msgstr "" diff --git a/locale/pt_PT/LC_MESSAGES/reference_manual/tools/dyna.po b/locale/pt_PT/LC_MESSAGES/reference_manual/tools/dyna.po index 921491368..878f87188 100644 --- a/locale/pt_PT/LC_MESSAGES/reference_manual/tools/dyna.po +++ b/locale/pt_PT/LC_MESSAGES/reference_manual/tools/dyna.po @@ -1,75 +1,73 @@ 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-02-19 16:23+0000\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" +"PO-Revision-Date: 2019-03-14 11:50+0000\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" "X-POFile-SpellExtra: Krita image icons tooldyna dynatool images\n" "X-POFile-SpellExtra: alt\n" "Plural-Forms: nplurals=2; plural=n != 1;\n" #: ../../:38 msgid "" ".. image:: images/icons/dyna_tool.svg\n" " :alt: tooldyna" msgstr "" ".. image:: images/icons/dyna_tool.svg\n" " :alt: ferramenta-dinâmica" #: ../../reference_manual/tools/dyna.rst:1 msgid "Krita's dynamic brush tool reference." msgstr "A referência à ferramenta de pincéis dinâmicos do Krita." #: ../../reference_manual/tools/dyna.rst:16 msgid "Dynamic Brush Tool" msgstr "Ferramenta de Pincel Dinâmico" #: ../../reference_manual/tools/dyna.rst:18 msgid "|tooldyna|" msgstr "|tooldyna|" #: ../../reference_manual/tools/dyna.rst:20 msgid "" "Add custom smoothing dynamics to your brush. This will give you similar " "smoothing results as the normal freehand brush. There are a couple options " "that you can change." msgstr "" "Adiciona alguma dinâmica de suavização personalizada ao seu pincel. Isto " "continuar-lhe-á a dar resultados de suavização semelhantes ao do pincel " "normal à mão livre. Existem algumas opções que poderá alterar." #: ../../reference_manual/tools/dyna.rst:22 msgid "Mass" msgstr "Massa" #: ../../reference_manual/tools/dyna.rst:23 msgid "" "Average your movement to make it appear smoother. Higher values will make " "your brush move slower." msgstr "" "Calcula uma média do seu movimento para o fazer parecer mais suave. Os " "valores mais altos farão com que o seu pincel se mova mais lentamente." #: ../../reference_manual/tools/dyna.rst:25 msgid "Drag" msgstr "Arrastamento" #: ../../reference_manual/tools/dyna.rst:25 msgid "" "A rubberband effect that will help your lines come back to your cursor. " -"lower values will make the effect more extreme." -msgstr "" -"Um efeito de elástico que faz com que as suas linhas regressem ao seu " -"cursor. Os valores mais baixos tornarão esse efeito ainda mais extremo." +"Lower values will make the effect more extreme." +msgstr "Um efeito de elástico que faz com que as suas linhas regressem ao seu cursor. Os valores mais baixos tornarão esse efeito ainda mais extremo." #: ../../reference_manual/tools/dyna.rst:27 msgid "Recommended values are around 0.02 Mass and 0.92 Drag." msgstr "" "Os valores recomendados encontram à volta de 0,02 de Massa e de 0,92 de " "Arrastamento." diff --git a/locale/pt_PT/LC_MESSAGES/tutorials/flat-coloring.po b/locale/pt_PT/LC_MESSAGES/tutorials/flat-coloring.po index f66f1e4ad..ed47910f7 100644 --- a/locale/pt_PT/LC_MESSAGES/tutorials/flat-coloring.po +++ b/locale/pt_PT/LC_MESSAGES/tutorials/flat-coloring.po @@ -1,764 +1,764 @@ # 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-03-12 03:34+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-02-19 09:59+0000\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" #: ../../: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" +#: ../../tutorials/flat-coloring.rst:0 +msgid "" +".. image:: images/en/flat-coloring/Krita_filling_lineart_selection_1.png" +msgstr "" + +#: ../../tutorials/flat-coloring.rst:0 +msgid "" +".. image:: images/en/flat-coloring/Krita_filling_lineart_selection_2.png" +msgstr "" + +#: ../../tutorials/flat-coloring.rst:0 +msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_1.png" +msgstr "" + +#: ../../tutorials/flat-coloring.rst:0 +msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_2.png" +msgstr "" + +#: ../../tutorials/flat-coloring.rst:0 +msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_3.png" +msgstr "" + #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart14.png\n" " :alt: layer structure for flatting in krita" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart1.png\n" " :alt: blend mode setup of lineart flat coloring" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart2.png\n" " :alt: effects of multiply blend mode" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/icons/fill_tool.svg\n" " :alt: fill-tool icon" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart7.png\n" " :alt: colors filled with fill tool" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart15.png\n" " :alt: selecting with selection tools for filling color" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart16.png\n" " :alt: selection mask in Krita" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart17.png\n" " :alt: filling color in selection" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart18.png\n" " :alt: result of coloring made with the help of selection tools" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart8.png\n" " :alt: filling color in lineart using path tool" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart9.png\n" " :alt: erasing with path tool" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart10.png\n" " :alt: coloring with colorise mask" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart11.png\n" " :alt: result from the colorise mask" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart12.png\n" " :alt: slitting colors into islands" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart13.png\n" " :alt: resulting color islands from split layers" msgstr "" -#: ../../tutorials/flat-coloring.rst:0 -msgid "" -".. image:: images/en/flat-coloring/Krita_filling_lineart_selection_1.png" -msgstr "" - -#: ../../tutorials/flat-coloring.rst:0 -msgid "" -".. image:: images/en/flat-coloring/Krita_filling_lineart_selection_2.png" -msgstr "" - -#: ../../tutorials/flat-coloring.rst:0 -msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_1.png" -msgstr "" - -#: ../../tutorials/flat-coloring.rst:0 -msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_2.png" -msgstr "" - -#: ../../tutorials/flat-coloring.rst:0 -msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_3.png" -msgstr "" - #: ../../tutorials/flat-coloring.rst:1 msgid "Common workflows used in Krita" msgstr "" #: ../../tutorials/flat-coloring.rst:13 msgid "Flat Coloring" msgstr "" #: ../../tutorials/flat-coloring.rst:15 msgid "" "So you've got a cool black on white drawing, and now you want to color it! " "The thing we’ll aim for in this tutorial is to get your lineart colored in " "with flat colors. So no shading just yet. We’ll be going through some " "techniques for preparing the lineart, and we’ll be using the layer docker to " "put each colour on a separate layer, so we can easily access each colour " "when we add shading." msgstr "" #: ../../tutorials/flat-coloring.rst:17 msgid "" "This tutorial is adapted from this `tutorial `_ by " "the original author." msgstr "" #: ../../tutorials/flat-coloring.rst:20 msgid "Understanding Layers" msgstr "" #: ../../tutorials/flat-coloring.rst:22 msgid "" "To fill lineart comfortably, it's best to take advantage of the layerstack. " "The layer stack is pretty awesome, and it's one of those features that make " "digital art super-convenient." msgstr "" #: ../../tutorials/flat-coloring.rst:24 msgid "" "In traditional art, it is not uncommon to first draw the full background " "before drawing the subject. Or to first draw a line art and then colour it " "in. Computers have a similar way of working." msgstr "" #: ../../tutorials/flat-coloring.rst:26 msgid "" "In programming, if you tell a computer to draw a red circle, and then " "afterwards tell it to draw a smaller yellow circle, you will see the small " "yellow circle overlap the red circle. Switch the commands around, and you " "will not see the yellow circle at all: it was drawn before the red circle " "and thus ‘behind’ it." msgstr "" #: ../../tutorials/flat-coloring.rst:28 msgid "" "This is referred to as the “drawing order”. So like the traditional artist, " "the computer will first draw the images that are behind everything, and " "layer the subject and foreground on top of it. The layer docker is a way for " "you to control the drawing order of multiple images, so for example, you can " "have your lineart drawn later than your colors, meaning that the lines will " "be drawn over the colors, making it easier to make it neat!" msgstr "" #: ../../tutorials/flat-coloring.rst:30 msgid "" "Other things that a layer stack can do are blending the colors of different " "layers differently with blending modes, using a filter in the layer stack, " "or using a mask that allows you to make parts transparent." msgstr "" #: ../../tutorials/flat-coloring.rst:32 msgid "" "Programmers talk about transparency as ''Alpha'', which is because the 'a' " "symbol is used to present transparency in the algorithms for painting one " "color on top of another. Usually when you see the word ''Alpha'' in a " "graphics program, just think of it as affecting the transparency." msgstr "" #: ../../tutorials/flat-coloring.rst:35 msgid "Preparing your line-art" msgstr "" #: ../../tutorials/flat-coloring.rst:37 msgid "" "Put the new layer underneath the layer containing the lineart (drag and drop " "or use the up/down arrows for that), and draw on it." msgstr "" #: ../../tutorials/flat-coloring.rst:42 msgid "" "…And notice nothing happening. This is because the white isn’t transparent. " "You wouldn’t really want it to either, how else would you make convincing " "highlights? So what we first need to do to colour in our drawing is prepare " "our lineart. There’s several methods of doing so, each with varying " "qualities." msgstr "" #: ../../tutorials/flat-coloring.rst:45 msgid "The Multiply Blending Mode" msgstr "" #: ../../tutorials/flat-coloring.rst:47 msgid "" "So, typically, to get a black and white lineart usable for colouring, you " "can set the blending mode of the lineart layer to Multiply. You do this by " "selecting the layer and going to the drop down that says **Normal** and " "setting that to **Multiply**." msgstr "" #: ../../tutorials/flat-coloring.rst:52 msgid "And then you should be able to see your colors!" msgstr "" #: ../../tutorials/flat-coloring.rst:54 msgid "" "Multiply is not a perfect solution however. For example, if through some " "image editing magic I make the lineart blue, it results into this:" msgstr "" #: ../../tutorials/flat-coloring.rst:59 msgid "" "This is because multiply literally multiplies the colors. So it uses maths!" msgstr "" #: ../../tutorials/flat-coloring.rst:61 msgid "" "What it first does is take the values of the RGB channels, then divides them " "by the max (because we're in 8bit, this is 255), a process we call " "normalising. Then it multiplies the normalised values. Finally, it takes the " "result and multiplies it with 255 again to get the result values." msgstr "" #: ../../tutorials/flat-coloring.rst:67 msgid "Pink" msgstr "Rosa" #: ../../tutorials/flat-coloring.rst:68 msgid "Pink (normalised)" msgstr "" #: ../../tutorials/flat-coloring.rst:69 ../../tutorials/flat-coloring.rst:87 msgid "Blue" msgstr "Azul" #: ../../tutorials/flat-coloring.rst:70 msgid "Blue (normalised)" msgstr "" #: ../../tutorials/flat-coloring.rst:71 msgid "Normalised, multiplied" msgstr "" #: ../../tutorials/flat-coloring.rst:72 msgid "Result" msgstr "Resultado" #: ../../tutorials/flat-coloring.rst:73 msgid "Red" msgstr "Vermelho" #: ../../tutorials/flat-coloring.rst:74 msgid "222" msgstr "" #: ../../tutorials/flat-coloring.rst:75 msgid "0.8705" msgstr "" #: ../../tutorials/flat-coloring.rst:76 msgid "92" msgstr "" #: ../../tutorials/flat-coloring.rst:77 msgid "0.3607" msgstr "" #: ../../tutorials/flat-coloring.rst:78 msgid "0.3139" msgstr "" #: ../../tutorials/flat-coloring.rst:79 msgid "80" msgstr "" #: ../../tutorials/flat-coloring.rst:80 msgid "Green" msgstr "Verde" #: ../../tutorials/flat-coloring.rst:81 msgid "144" msgstr "" #: ../../tutorials/flat-coloring.rst:82 msgid "0.5647" msgstr "" #: ../../tutorials/flat-coloring.rst:83 msgid "176" msgstr "" #: ../../tutorials/flat-coloring.rst:84 msgid "0.6902" msgstr "" #: ../../tutorials/flat-coloring.rst:85 msgid "0.3897" msgstr "" #: ../../tutorials/flat-coloring.rst:86 msgid "99" msgstr "" #: ../../tutorials/flat-coloring.rst:88 msgid "123" msgstr "" #: ../../tutorials/flat-coloring.rst:89 msgid "0.4823" msgstr "" #: ../../tutorials/flat-coloring.rst:90 msgid "215" msgstr "" #: ../../tutorials/flat-coloring.rst:91 msgid "0.8431" msgstr "" #: ../../tutorials/flat-coloring.rst:92 msgid "0.4066" msgstr "" #: ../../tutorials/flat-coloring.rst:93 msgid "103" msgstr "" #: ../../tutorials/flat-coloring.rst:95 msgid "" "This isn't completely undesirable, and a lot of artists use this effect to " "add a little richness to their colors." msgstr "" #: ../../tutorials/flat-coloring.rst:98 ../../tutorials/flat-coloring.rst:127 #: ../../tutorials/flat-coloring.rst:154 ../../tutorials/flat-coloring.rst:173 #: ../../tutorials/flat-coloring.rst:210 ../../tutorials/flat-coloring.rst:247 #: ../../tutorials/flat-coloring.rst:275 ../../tutorials/flat-coloring.rst:317 msgid "Advantages" msgstr "" #: ../../tutorials/flat-coloring.rst:100 msgid "" "Easy, can work to your benefit even with coloured lines by softening the " "look of the lines while keeping nice contrast." msgstr "" #: ../../tutorials/flat-coloring.rst:103 ../../tutorials/flat-coloring.rst:132 #: ../../tutorials/flat-coloring.rst:159 ../../tutorials/flat-coloring.rst:178 #: ../../tutorials/flat-coloring.rst:215 ../../tutorials/flat-coloring.rst:252 #: ../../tutorials/flat-coloring.rst:280 ../../tutorials/flat-coloring.rst:322 msgid "Disadvantages" msgstr "Desvantagens" #: ../../tutorials/flat-coloring.rst:105 msgid "Not actually transparent. Is a little funny with coloured lines." msgstr "" #: ../../tutorials/flat-coloring.rst:108 msgid "Using Selections" msgstr "" #: ../../tutorials/flat-coloring.rst:110 msgid "" "The second method is one where we'll make it actually transparent. In other " "programs this would be done via the channel docker, but Krita doesn't do " "custom channels, instead it uses Selection Masks to store custom selections." msgstr "" #: ../../tutorials/flat-coloring.rst:112 msgid "duplicate your lineart layer." msgstr "" #: ../../tutorials/flat-coloring.rst:114 msgid "" "convert the duplicate to a selection mask. |mouseright| the layer, then :" "menuselection:`Convert --> to Selection Mask`." msgstr "" #: ../../tutorials/flat-coloring.rst:118 msgid "" "Invert the selection mask. :menuselection:`Select --> Invert Selection`." msgstr "" #: ../../tutorials/flat-coloring.rst:120 msgid "" "Make a new layer, and do :menuselection:`Edit --> Fill with foreground " "color`." msgstr "" #: ../../tutorials/flat-coloring.rst:124 msgid "And you should now have the line art on a separate layer." msgstr "" #: ../../tutorials/flat-coloring.rst:129 msgid "Actual transparency." msgstr "" #: ../../tutorials/flat-coloring.rst:134 msgid "Doesn't work when the lineart is coloured." msgstr "" #: ../../tutorials/flat-coloring.rst:137 msgid "Using Masks" msgstr "" #: ../../tutorials/flat-coloring.rst:139 msgid "This is a simpler variation of the above." msgstr "" #: ../../tutorials/flat-coloring.rst:141 msgid "Make a filled layer underneath the lineart layer." msgstr "" #: ../../tutorials/flat-coloring.rst:145 msgid "" "Convert the lineart layer to a transparency mask |mouseright| the layer, " "then :menuselection:`Convert --> to Transparency Mask`." msgstr "" #: ../../tutorials/flat-coloring.rst:149 msgid "" "Invert the transparency mask by going to :menuselection:`Filter --> Adjust --" "> Invert`" msgstr "" #: ../../tutorials/flat-coloring.rst:156 msgid "" "Actual transparency. You can also very easily doodle a pattern on the filled " "layer where the mask is on without affecting the transparency." msgstr "" #: ../../tutorials/flat-coloring.rst:161 msgid "" "Doesn't work when the lineart is coloured already. We can still get faster." msgstr "" #: ../../tutorials/flat-coloring.rst:164 msgid "Using Color to Alpha" msgstr "" #: ../../tutorials/flat-coloring.rst:166 msgid "By far the fastest way to get transparent lineart." msgstr "" #: ../../tutorials/flat-coloring.rst:168 msgid "" "Select the line art layer and apply the color to alpha filter. :" "menuselection:`Filter --> Colors --> Color to Alpha`. The default values " "should be sufficient for lineart." msgstr "" #: ../../tutorials/flat-coloring.rst:171 msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart_color_to_alpha.png" msgstr "" #: ../../tutorials/flat-coloring.rst:175 msgid "" "Actual transparency. Works with coloured line art as well, because it " "removes the white specifically." msgstr "" #: ../../tutorials/flat-coloring.rst:180 msgid "" "You'll have to lock the layer transparency or separate out the alpha via the " "right-click menu if you want to easily color it." msgstr "" #: ../../tutorials/flat-coloring.rst:184 msgid "Colouring the image" msgstr "" #: ../../tutorials/flat-coloring.rst:186 msgid "" "Much like preparing the line art, there's many different ways of colouring a " "layer." msgstr "" #: ../../tutorials/flat-coloring.rst:188 msgid "" "You could for example fill in everything by hand, but while that is very " "precise it also takes a lot of work. Let's take a look at the other options, " "shall we?" msgstr "" #: ../../tutorials/flat-coloring.rst:191 msgid "Fill Tool" msgstr "Ferramenta de Preenchimento" #: ../../tutorials/flat-coloring.rst:196 msgid "" "In most cases the fill-tool can’t deal with the anti-aliasing (the soft edge " "in your lineart to make it more smooth when zoomed out) In Krita you have " "the grow-shrink option. Setting that to say… 2 expands the colour two pixels." msgstr "" #: ../../tutorials/flat-coloring.rst:198 msgid "" "Threshold decides when the fill-tool should consider a different colour " "pixel to be a border. And the feathering adds a extra soft border to the " "fill." msgstr "" #: ../../tutorials/flat-coloring.rst:200 msgid "" "Now, if you click on a gapless-part of the image with your preferred colour…" "(Remember to set the opacity to 1.0!)" msgstr "" #: ../../tutorials/flat-coloring.rst:202 msgid "" "Depending on your lineart, you can do flats pretty quickly. But setting the " "threshold low can result in little artifacts around where lines meet:" msgstr "" #: ../../tutorials/flat-coloring.rst:207 msgid "" "However, setting the threshold high can end with the fill not recognising " "some of the lighter lines. Besides these little artifacts can be removed " "with the brush easily." msgstr "" #: ../../tutorials/flat-coloring.rst:212 msgid "Pretty darn quick depending on the available settings." msgstr "" #: ../../tutorials/flat-coloring.rst:217 msgid "" "Again, not great with gaps or details. And it works best with aliased line-" "art." msgstr "" #: ../../tutorials/flat-coloring.rst:220 msgid "Selections" msgstr "Selecções" #: ../../tutorials/flat-coloring.rst:222 msgid "Selections work using the selection tools." msgstr "" #: ../../tutorials/flat-coloring.rst:227 msgid "" "For example with the :ref:`bezier_curve_selection_tool` you can easily " "select a curved area, and the with :kbd:`Shift` + |mouseleft| (not |" "mouseleft| + :kbd:`Shift`, there's a difference!) you can easily add to an " "existing selection." msgstr "" #: ../../tutorials/flat-coloring.rst:232 msgid "" "You can also edit the selection if you have :menuselection:`Select --> Show " "Global Selection Mask` turned on. Then you can select the global selection " "mask, and paint on it. (Above with the alternative selection mode, activated " "in the lower-left corner of the stats bar)" msgstr "" #: ../../tutorials/flat-coloring.rst:234 msgid "" "When done, select the color you want to fill it with and press :kbd:`Shift` " "+ `backspace`." msgstr "" #: ../../tutorials/flat-coloring.rst:239 msgid "" "You can save selections in selection masks by |mouseright| a layer, and then " "going to :menuselection:`Add --> Local Selection`. You first need to " "deactivate a selection by pressing the circle before adding a new selection." msgstr "" #: ../../tutorials/flat-coloring.rst:241 msgid "" "This can serve as an alternative way to split out different parts of the " "image, which is good for more painterly pieces:" msgstr "" #: ../../tutorials/flat-coloring.rst:249 msgid "A bit more precise than filling." msgstr "" #: ../../tutorials/flat-coloring.rst:254 msgid "Previewing your color isn't as easy." msgstr "" #: ../../tutorials/flat-coloring.rst:257 msgid "Geometric tools" msgstr "" #: ../../tutorials/flat-coloring.rst:259 msgid "" "So you have a tool for making rectangles or circles. And in the case of " "Krita, a tool for bezier curves. Select the path tool (|path tool|), and set " "the tool options to fill=foreground and outline=none. Make sure that your " "opacity is set to 1.00 (fully opaque)." msgstr "" #: ../../tutorials/flat-coloring.rst:262 msgid "" ".. image:: images/icons/bezier_curve.svg\n" " :alt: path tool" msgstr "" #: ../../tutorials/flat-coloring.rst:264 msgid "" "By clicking and holding, you can influence how curvy a line draw with the " "path tool is going to be. Letting go of the mouse button confirms the " "action, and then you’re free to draw the next point." msgstr "" #: ../../tutorials/flat-coloring.rst:269 msgid "" "You can also erase with a geometric tool. Just press :kbd:`E` or the eraser " "button." msgstr "" #: ../../tutorials/flat-coloring.rst:277 msgid "" "Quicker than using the brush or selections. Also decent with lineart that " "contains gaps." msgstr "" #: ../../tutorials/flat-coloring.rst:282 msgid "" "Fiddly details aren’t easy to fill in with this. So I recommend skipping " "those and filling them in later with a brush." msgstr "" #: ../../tutorials/flat-coloring.rst:285 msgid "Colorize Mask" msgstr "Máscara de Coloração" #: ../../tutorials/flat-coloring.rst:287 msgid "" "So, this is a bit of an odd one. In the original tutorial, you'll see I'm " "suggesting using G'Mic, but that was a few years ago, and g'mic is a little " "unstable on windows. Therefore, the Krita developers have been attempting to " "make an internal tool doing the same." msgstr "" #: ../../tutorials/flat-coloring.rst:289 msgid "" "It is disabled in 3.1, but if you use 4.0 or later, it is in the toolbox. " "Check the Colorize Mask for more information." msgstr "" #: ../../tutorials/flat-coloring.rst:291 msgid "So it works like this:" msgstr "" #: ../../tutorials/flat-coloring.rst:293 msgid "Select the colorize mask tool." msgstr "" #: ../../tutorials/flat-coloring.rst:294 msgid "Tick the layer you're using." msgstr "" #: ../../tutorials/flat-coloring.rst:295 msgid "Paint the colors your want to use on the colorize mask" msgstr "" #: ../../tutorials/flat-coloring.rst:296 msgid "Click update to see the results:" msgstr "" #: ../../tutorials/flat-coloring.rst:301 msgid "" "When you are satisfied, |mouseright| the colorize mask, and go to :" "menuselection:`Convert --> Paint Layer`. This will turn the colorize mask to " "a generic paint layer. Then, you can fix the last issues by aking the " "lineart semi-transparent and painting the flaws away with a pixel art brush." msgstr "" #: ../../tutorials/flat-coloring.rst:306 msgid "" "Then, when you are done, split the layers via :menuselection:`Layers --> " "Split --> Split Layer`. There's a few options you can choose, but the " "following should be fine:" msgstr "" #: ../../tutorials/flat-coloring.rst:311 msgid "" "Finally, press **Ok** and you should get the following. Each color patch it " "on a different layer, named by the palette in the menu and alpha locked, so " "you can start painting right away!" msgstr "" #: ../../tutorials/flat-coloring.rst:319 msgid "" "Works with anti aliased lineart. Really quick to get the base work done. Can " "auto-close gaps." msgstr "" #: ../../tutorials/flat-coloring.rst:324 msgid "" "No anti aliasing of it’s own. You have to choose between getting details " "right or the gaps auto-closed." msgstr "" #: ../../tutorials/flat-coloring.rst:327 msgid "Conclusion" msgstr "Conclusão" #: ../../tutorials/flat-coloring.rst:329 msgid "" "I hope this has given you a good idea of how to fill in flats using the " "various techniques, as well as getting a hand of different Krita features. " "Remember that a good flat filled lineart is better than a badly shaded one, " "so keep practising to get the best out of these techniques!" msgstr "" diff --git a/locale/pt_PT/LC_MESSAGES/user_manual/loading_saving_brushes.po b/locale/pt_PT/LC_MESSAGES/user_manual/loading_saving_brushes.po index 71fb6cb67..ba9b3e58a 100644 --- a/locale/pt_PT/LC_MESSAGES/user_manual/loading_saving_brushes.po +++ b/locale/pt_PT/LC_MESSAGES/user_manual/loading_saving_brushes.po @@ -1,945 +1,945 @@ # 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-03-12 03:34+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-02-19 09:58+0000\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" #: ../../user_manual/loading_saving_brushes.rst:0 msgid ".. image:: images/en/Krita_4_0_dirty_preset_icon.png" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:None msgid ".. image:: images/en/Krita_4_0_Brush_Settings_Layout.svg" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:17 msgid "Loading and Saving Brushes" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:37 msgid "The Brush settings dropdown" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:44 msgid "" "When you open Brush Settings Editor panel you will see something like this:" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:48 msgid "Tour of the brush settings dropdown" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:53 msgid "The brush settings drop down is divided into six areas," msgstr "" #: ../../user_manual/loading_saving_brushes.rst:56 msgid "Section A - General Information" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:79 msgid "Engine" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:94 msgid "Reloading" msgstr "A carregar de novo" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:101 msgid "Saving a preset" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:103 msgid "" "On the right, there's :guilabel:`Save New Brush Preset` and :guilabel:" "`Overwrite Brush`." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:108 msgid "Overwrite Brush" msgstr "Substituir o Pincel" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:113 msgid "Save New Brush Preset" msgstr "Gravar uma Nova Predefinição do Pincel" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:119 msgid ".. image:: images/en/Krita_4_0_Save_New_Brush_Preset_Dialog.png" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:125 msgid "Brush Name" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:127 msgid "Load Existing Thumbnail" msgstr "Carregar a Miniatura Existente" #: ../../user_manual/loading_saving_brushes.rst:128 msgid "This will load the existing thumbnail inside the preset." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:130 msgid "Load scratch pad thumbnail" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:132 msgid "Load Image" msgstr "Carregar a Imagem" #: ../../user_manual/loading_saving_brushes.rst:133 msgid "With this you can choose an image from disk to load as a thumbnail." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:134 msgid "Load from Icon Library" msgstr "Carregar da Biblioteca de Ícones" #: ../../user_manual/loading_saving_brushes.rst:135 msgid "This opens up the icon library." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:137 msgid "Clear Thumbnail" msgstr "Limpar a Miniatura" #: ../../user_manual/loading_saving_brushes.rst:137 msgid "This will make the mini scratch pad white." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:140 msgid "The Icon Library" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:142 msgid "To make making presets icons faster, Krita got an icon library." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:145 msgid ".. image:: images/en/Krita_4_0_Preset_Icon_Library_Dialog.png" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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, ad the lowest slider is a super simple levels filter. " +"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 "" #: ../../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." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:167 msgid "Section B - The Preset Chooser" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:169 msgid "" "The preset chooser is much the same as the preset docker and the preset " "dropdown 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 "" #: ../../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 "" #: ../../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 "" #: ../../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 for that " -"engine." +"list of Krita's engines. Selecting an engine from the list will show the " +"brushes for that engine." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:185 msgid "" -"The trashcan icon does the same as it does in the preset docker: delete , or " +"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 "" #: ../../user_manual/loading_saving_brushes.rst:189 msgid "Section C - The Scratch pad" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:202 msgid "The scratch pad has five buttons underneath it. These are in order for:" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:204 msgid "Showing the current brush image" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:206 msgid "Adding a gradient to the scratch pad (useful for smudge brushes)" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:207 msgid "Filling with the background color" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:208 msgid "Clearing everything on the scratch pad." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:211 msgid "Section D - The Options List" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:227 msgid "Section E - Option Configuration Widget" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:233 msgid "Using sensor curves" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:260 msgid "Underneath the curve widget there are two more options:" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:264 msgid "Share Curves across all settings" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:271 msgid "Multiply" msgstr "Multiplicar" #: ../../user_manual/loading_saving_brushes.rst:272 msgid "Will multiply the two values, 0.5\\*0.7 = 0.35" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:274 msgid "Addition" msgstr "Adição" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:277 msgid "Maximum" msgstr "Máximo" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:280 msgid "Minimum" msgstr "Mínimo" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:283 msgid "Will subtract the smallest value from the largest, so 0.7-0.5 = 0.2" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:284 msgid "Curves Calculation Mode" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:284 msgid "Difference" msgstr "Diferença" #: ../../user_manual/loading_saving_brushes.rst:286 msgid "It's maybe better to see with the following example:" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:289 msgid ".. image:: images/en/Krita_4_0_brush_curve_calculation_mode.png" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:290 msgid "" "The first two are regular, the rest with different multiplication types." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:292 msgid "Is a brush with size set to the distance sensor." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:293 msgid "Is a brush with the size set to the fade sensor." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:294 msgid "The size is calculated from the fade and distance sensors multiplied." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:297 msgid "" "The size takes the maximum value from the values of the fade and distance " "sensors." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:299 msgid "" -"The size takes the minimum value from the values of the face and distance " +"The size takes the minimum value from the values of the fade and distance " "sensors." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:305 msgid "Section F - Miscellaneous options" msgstr "" #: ../../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, the revert to default. " "Dirtied presets can be recognized by the icon in the top-left of the preset." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:316 msgid "Temporarily Save Tweaks to Preset (Dirty Presets)" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:319 msgid "Eraser Switch Size" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:319 msgid "" "This switches the brush to a separately stored size when using the :kbd:`E` " "key." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:321 msgid "Eraser Switch Opacity" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:322 msgid "Same as above, but then with Eraser opacity." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:330 msgid "Instant Preview" msgstr "Antevisão Instantânea" #: ../../user_manual/loading_saving_brushes.rst:333 msgid "The On-canvas brush settings" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:347 msgid "Making a Brush Preset" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:349 msgid "Now, let's make a simple brush to test the waters with:" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:352 msgid "Getting a default for the brush engine." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:354 msgid "First, open the settings with :kbd:`F5`." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:361 msgid "Example: Making an inking brush" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:370 -msgid "Uncheck the :guilabel:`enable pen settings` checkbox." +msgid "Uncheck the :guilabel:`Enable Pen Settings` checkbox." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:377 msgid "" -"Uncheck the :guilabel:`enable pen settings` checkbox here as well. Test " +"Uncheck the :guilabel:`Enable Pen Settings` checkbox here as well. Test " "again." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:401 msgid "Saving the new Brush" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:403 msgid "" "When you're satisfied, go to the upper left and select :guilabel::`Save new " "preset`." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:414 msgid "Finally press :guilabel:`Save`, and your brush should be done." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:416 msgid "You can further modify your inking brush by..." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:422 msgid "Making the fine lines look even softer by using the flow option." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:422 msgid "" "To do this, select the flow option, and turn back on the 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 "" #: ../../user_manual/loading_saving_brushes.rst:425 msgid "Sharing Brushes" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:438 msgid "Sharing a single preset" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:440 msgid "There are three types of resources a single preset can take:" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:446 msgid "A Pattern file: this is when you are using textures." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:452 msgid "" "To find those resources, go to :menuselection:`Settings --> Manage Resources " "--> Open Resource Folder`." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:458 msgid "Importing a single KPP file." msgstr "" #: ../../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 "" #: ../../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 " "dropdown (: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 "" #: ../../user_manual/loading_saving_brushes.rst:471 msgid "Sharing via ZIP (old-fashioned)" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:477 msgid "Using a ZIP with the relevant files." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:479 msgid "" "Go to :menuselection:`Settings --> Manage Resources --> Open Resource " "Folder` to open the resource folder." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:480 msgid "Then, open up the zip file." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:484 msgid "Restart Krita" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:485 msgid "Enjoy your brushes!" msgstr "" diff --git a/locale/pt_PT/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po b/locale/pt_PT/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po index b57e933f6..01f4793c1 100644 --- a/locale/pt_PT/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po +++ b/locale/pt_PT/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po @@ -1,337 +1,337 @@ # 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-03-06 03:37+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-03-11 11:33+0000\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" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:1 msgid "Introduction to using Krita's python plugin API." msgstr "Introdução à API de 'plugins' em Python do Krita." #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:18 msgid "Introduction to Python Scripting" msgstr "Introdução à Programaçẽo em Python" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:22 msgid "" "When we offered python scripting as one of Kickstarter Stretchgoals we could " "implement next to vectors and text, it won the backer vote by a landslide. " "Some people even only picked python and nothing else. So what exactly is " "python scripting?" msgstr "" "Quando oferecemos a programação em Python como um dos passatempos do " "Kickstarter, havia a hipótese de ser implementada a seguir aos vectores e ao " "texto, mas passou à frente de tudo na altura. Algumas pessoas até escolheram " "Python e mais nada. Por isso, o que é exactamente a programação em Python?" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:25 msgid "What is Python Scripting?" msgstr "O que é a Programação em Python?" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:27 msgid "" "Python is a scripting language, that can be used to automate tasks. What " "python scripting in Krita means is that we added an API to krita, which is a " "bit of programming that allows python to access to parts of Krita. With this " "we can make dockers, perform menial tasks on a lot of different files and " "even write our own exporters. People who work with computer graphics, like " "VFX and video game artists use python a lot to make things like sprite " "sheets, automate parts of export and more." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:29 msgid "" "It is outside the scope of this manual to teach you python itself. However, " "as python is an extremely popular programming language and great for " "beginners, there's tons of learning material around that can be quickly " "found with a simple 'learn python' internet search." msgstr "" "Está fora do âmbito deste manual ensinar-lhe o Python em si. Contudo, dado " "que o Python é uma linguagem de programação bastante popular e é óptima para " "principiantes, existem quantidades enormes de material de aprendizagem que " "pode encontrar rapidamente com uma pesquisa sobre 'aprender Python' na " "Internet." #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:31 msgid "" "This manual will instead focus on how to use python to automate and extend " "Krita. For that we'll first start with the basics: How to run Python " "commands in the scripter." msgstr "" "Este manual focar-se-á sim em como usar o Python para automatizar e estender " "o Krita. Para tal, iremos primeiro começar pelas bases: Como correr comandos " "em Python no programador." #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:35 msgid "How to Enable the Scripter Plugin" msgstr "Como Activar o 'Plugin' do Programador" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:37 msgid "" "The scripter plugin is not necessary to use python, but it is very useful " "for testing and playing around with python. It is a python console, written " "in python, which can be used to write small scripts and execute them on the " "fly." msgstr "" "O 'plugin' do programador não é necessário para usar o Python, mas é " "bastante útil para testar e brincar com o Python. É uma consola de Python, " "criada em Python, que pode ser usada para criar pequenos programas e executá-" "los na hora." #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:39 msgid "" "To open the scripter, navigate to :menuselection:`Tools --> Scripts --> " "Scripter`. If you don't see it listed, go to :menuselection:`Settings --> " "Configure Krita --> Python Plugin Manager` and toggle \"Scripter\" in the " "list to enable it. If you don't see the scripter plugin, make sure you are " "using an up-to-date version of Krita." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:41 msgid "" "The scripter will pop up with a text editor window on top and an output " "window below. Input the following in the text area:" msgstr "" "O programador irá aparecer com uma pequena janela de edição de texto no topo " "e uma janela de resultados em baixo. Introduza o seguinte na área de texto:" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:48 msgid "" "Press the big play button or press :kbd:`Ctrl + R` to run the script. Then, " "below, in the output area the following should show up::" msgstr "" "Carregue no botão grande de reprodução ou carregue em :kbd:`Ctrl + R` para " "executar o programa. Depois, em baixo, na área de resultados, deverá " "aparecer o seguinte::" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:53 msgid "" "Now we have a console that can run functions like print() from the Python " "environment - but how do we use it to manage Krita?" msgstr "" "Agora temos uma consola que consegue correr funções como o print() no " "ambiente de Python - mas como é que conseguimos usá-la para gerir o Krita?" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:56 msgid "Running basic Krita commands" msgstr "Executar comandos básicos do Krita" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:58 msgid "" "To allow Python to communicate with Krita, we will use the Krita module. At " "the top of every script, we will write: ``from krita import *``" msgstr "" "Para permitir ao Python comunicar com o Krita, iremos usar o módulo do " "Krita. No topo de cada programa, iremos escrever: ``from krita import *``" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:60 msgid "" "This allows us to talk to Krita through ``Krita.instance()``. Let's try to " "double our coding abilities with Python." msgstr "" "Isto permite-nos aceder ao ``Krita.instance()``. Vamos experimentar duplicar " "as nossas competências de programação em Python." #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:68 msgid "" "You should see a second scripter window open. Pretty neat! Here is a " "slightly more advanced example." msgstr "" "Deverá ver uma segunda janela do programador aberta. Muito bom! Agora está " "aqui um exemplo ligeiramente mais avançado." #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:77 msgid "" "This will open up a new document. Clearly Python gives you quite a lot of " "control to automate Krita. Over time we expect the community to write all " "kinds of scripts that you can use simply by pasting them in the scripter." msgstr "" "Isto irá agora abrir um novo documento. Claramente o Python dá-lhe um boa " "quantidade de controlo para automatizar o Krita. Com o tempo, esperamos que " "a comunidade crie todos os tipos de programas que possa usar, bastando para " "tal colá-los no programador." #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:79 msgid "" "But what if you want to write new commands for yourself? The best place to " "start is very simple: search for examples written by other people! You can " "save a lot of time if someone else has written code that you can base your " "work on. It's also worth looking through the python plugins, which are " "located in /share/krita/pykrita. There's also a step by step guide for :ref:" "`krita_python_plugin_howto` here in the manual." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:81 msgid "" "But it's likely that you need more information. For that, we will need see " "what's hidden behind the asterisk when you ``import * from Krita``. To learn " "what Krita functions that are available and how to use them, you will want " "to go for Krita API reference documentation." msgstr "" "Mas é provável que necessite de mais informações. Para tal, iremos ver o que " "está escondido atrás do asterisco quando executa ``import * from Krita``. " "Para saber quais as funções do Krita que estão disponíveis e como usá-las, " "irá querer ver directamente a documentação de referência da API do Krita." #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:84 msgid "Krita's API" msgstr "API do Krita" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:86 msgid "" "`LibKis API Overview `_" msgstr "" "`Introdução à API do LibKis `_" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:87 msgid "" "`Krita class documentation `_" msgstr "" "`Documentação da classe Krita `_" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:89 msgid "" "Those pages may look like a lot of jargon at first. This is because Krita's " "API documentation comes from the underlying C++ language that Krita is " "written in. The magic happens because of a Python tool called SIP, which " "makes it possible for python speak in C++ and talk to Krita. The end result " "is that when we ``import krita`` and call functions, we're actually using " "the C++ methods listed in that documentation." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:91 msgid "" "Let's see how this stuff works in more detail. Let's take a look at the " "second link, the `Krita class reference `_. There we can see all the " "functions available to the Krita instance. If you type dir(Krita.instance()) " "in Python, it should match this page very closely - you can view the " "documentation of the functions createDocument(), activeWindow(), and " "action() which we used above." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:93 msgid "" "One of the more confusing things is seeing all the C++ classes that Krita " -"uses, including the Qt classes that start with Q. But here is the beauty fo " +"uses, including the Qt classes that start with Q. But here is the beauty of " "SIP: it tries to make the translation from these classes into Python as " "simple and straightforward as possible. For example, you can see that the " "function filters() returns a QStringList. However, SIP converts those " "QStringLists into regular python list of strings!" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:101 msgid "Outputs as ::" msgstr "Devolve o resultado ::" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:112 msgid "However, sometimes the conversion doesn't go quite as smoothly." msgstr "Conutod, algumas vezes a conversão não corre assim tão bem." #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:120 msgid "gives something like this::" msgstr "dando-lhe algo como o seguinte::" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:127 msgid "" "It is a list of something, sure, but how to use it? If we go back to the " "Krita apidocs page and look at the function, documents() we'll see there's " "actually a clickable link on the 'Document' class. `If you follow that link " "`_, you'll see that the document has a function called " "name() which returns the name of the document, and functions width() and " "height() which return the dimensions. So if we wanted to generate an info " "report about the documents in Krita, we could write a script like this:" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:137 msgid "we get an output like::" msgstr "iremos obter um resultado como o seguinte::" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:147 msgid "" "Hopefully this will give you an idea of how to navigate the API docs now." msgstr "" "Esperamos que isto lhe dê uma ideia de como navegar pela documentação da API " "agora." #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:149 msgid "" "Krita's API has many more classes, you can get to them by going to the top-" "left class list, or just clicking their names to get to their API docs. The " "functions print() or dir() are your friends here as well. This line will " "print out a list of all the actions in Krita - you could swap in one of " "these commands instead of 'python_scripter' in the example above." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:155 msgid "" "The Python module ``inspect`` was designed for this sort of task. Here's a " "useful function to print info about a class to the console." msgstr "" "O módulo ``inspect`` do Python foi desenhado para este tipo de tarefas. Aqui " "está uma função útil para mostrar informações sobre uma classe na consola." #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:167 msgid "" "Finally, in addition to the LibKis documentation, the Qt documentation, " "since Krita uses PyQt to expose nearly all of the Qt API to Python. You can " "build entire windows with buttons and forms this way, using the very same " "tools that Krita is using! You can read the `Qt documentation `_ and the `PyQt documentation `_ for more info about this, and also definitely study the included plugins " "as well to see how they work." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:171 msgid "Technical Details" msgstr "Detalhes Técnicos" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:177 msgid "Python Scripting on Windows" msgstr "Programação em Python no Windows" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:179 msgid "" "To get Python scripting working on Windows 7/8/8.1, you will need to install " "the `Universal C Runtime from Microsoft's website `_. (Windows 10 already comes with it.)" msgstr "" "Para ter a programação em Python a funcionar no Windows 7/8/8.1, precisa de " "instalar o ambiente de execução `Universal C Runtime na página Web da " "Microsoft `_. (O Windows 10 já a traz de raiz.)" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:182 msgid "Python 2 and 3" msgstr "Python 2 e 3" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:184 msgid "By default Krita is compiled for python 3." msgstr "Por omissão, o Krita foi compilado para o Python 3." #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:186 msgid "" "However, it is possible to compile it with python 2. To do so, you will need " "to add the following to the cmake configuration line::" msgstr "" "Contudo, é possível compilá-lo com o Python 2. Para o fazer, terá de " "adicionar o seguinte à linha de configuração do CMake::" 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 896482523..e39b4aa00 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-03-12 03:34+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\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 it's 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 74aa3d6e3..1051cd307 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,1058 +1,1058 @@ # 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-03-13 03:40+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\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 colour " "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 colour." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:71 msgid "" "Finally, group 4 has Vermillion red, citron yellow and cerulean blue. Their " "colours 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 colour 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 " "colour translate properly between color devices." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:82 msgid "" "It usually works by attempting to covert a colour to the reference colour " "space XYZ. XYZ is a coordinate system that has a spot for all colours 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 colour 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:88 msgid "" "To give a crude estimate, ICC profiles deal with keeping colours consistent " "over many interpretations of devices (screens, printers) by using a " "reference space, and OCIO deals with manipulating the interpretation of said " "colours." 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 grey it produces. Using " "these and several other measurements it creates an icc profile unique to " "your screen. You set these in Krita's colour 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 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-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.)" 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 colour 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 colorspace 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 colour reproduction. Use this if you want to " "see all colours 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 colours at whatever cost, which may result in awful looking " "colours. 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 "" "A in between solution between perceptual and absolute, relative will try to " "fit whatever colours it can match between colour 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 colourfulness, 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 '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." 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 colour 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 colour 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 colour 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 " "customly 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 colour maths, often concerning the blending of colours. " "This colour maths works best in linear colour space, and linear colour 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 colour 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 " "colour 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's 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 colours actually look strange: This is a " "bug in Firefox, which is because its `color management system is incomplete " "`_, save your png, jpg or tiff without an embedded profile to work " "around this." 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 " "bitdepth 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 specialised 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, mypaint, mangastudio, 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, mangastudio " "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 optimisers. 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 "" "Specialised 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 --> 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." 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 optimised content, and it's recommended to " "stay within 8bit, future screens may have higher bitdepths, 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 optimise 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 "" "`Visualising the XYZ colorspace `_" 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 colormanagement from argylcms manual `_" msgstr "" diff --git a/locale/sk/LC_MESSAGES/reference_manual.po b/locale/sk/LC_MESSAGES/reference_manual.po index ed3bbc248..e7a7ae1d6 100644 --- a/locale/sk/LC_MESSAGES/reference_manual.po +++ b/locale/sk/LC_MESSAGES/reference_manual.po @@ -1,29 +1,28 @@ # translation of docs_krita_org_reference_manual.po to Slovak # Roman Paholik , 2019. msgid "" msgstr "" "Project-Id-Version: docs_krita_org_reference_manual\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-19 03:36+0100\n" "PO-Revision-Date: 2019-03-13 10:17+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" #: ../../reference_manual.rst:5 msgid "Reference Manual" msgstr "Referenčná príručka" #: ../../reference_manual.rst:7 msgid "A quick run-down of all of the tools that are available" msgstr "Rýchly prehľad všetkých dostupných nástrojov" #: ../../reference_manual.rst:9 msgid "Contents:" msgstr "Obsah:" - diff --git a/locale/sk/LC_MESSAGES/reference_manual/brushes.po b/locale/sk/LC_MESSAGES/reference_manual/brushes.po index b1fa8cd47..cf21185fd 100644 --- a/locale/sk/LC_MESSAGES/reference_manual/brushes.po +++ b/locale/sk/LC_MESSAGES/reference_manual/brushes.po @@ -1,29 +1,28 @@ # translation of docs_krita_org_reference_manual___brushes.po to Slovak # Roman Paholik , 2019. msgid "" msgstr "" "Project-Id-Version: docs_krita_org_reference_manual___brushes\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-19 03:36+0100\n" "PO-Revision-Date: 2019-03-13 10:19+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" #: ../../reference_manual/brushes.rst:5 msgid "Brushes" msgstr "Štetce" #: ../../reference_manual/brushes.rst:7 msgid "" -"One of the most important parts of a painting program, Krita has a very" -" extensive brush system." +"One of the most important parts of a painting program, Krita has a very " +"extensive brush system." msgstr "" -"Jedna z najdôležitejších častí kresliaceho programu Krita je veľmi rozsiahly" -" systém štetcov." - +"Jedna z najdôležitejších častí kresliaceho programu Krita je veľmi rozsiahly " +"systém štetcov." diff --git a/locale/sk/LC_MESSAGES/reference_manual/dockers.po b/locale/sk/LC_MESSAGES/reference_manual/dockers.po index 842cea331..f7953a11f 100644 --- a/locale/sk/LC_MESSAGES/reference_manual/dockers.po +++ b/locale/sk/LC_MESSAGES/reference_manual/dockers.po @@ -1,25 +1,24 @@ # translation of docs_krita_org_reference_manual___dockers.po to Slovak # Roman Paholik , 2019. msgid "" msgstr "" "Project-Id-Version: docs_krita_org_reference_manual___dockers\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-19 03:36+0100\n" "PO-Revision-Date: 2019-03-13 10:22+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" #: ../../reference_manual/dockers.rst:5 msgid "Dockers" msgstr "Dockery" #: ../../reference_manual/dockers.rst:7 msgid "All of the panels that exist in Krita and what they do." msgstr "Všetky panely, ktoré existujú v programe Krita a čo robia." - diff --git a/locale/sk/LC_MESSAGES/reference_manual/filters.po b/locale/sk/LC_MESSAGES/reference_manual/filters.po index 2a0dd664b..87ffa6776 100644 --- a/locale/sk/LC_MESSAGES/reference_manual/filters.po +++ b/locale/sk/LC_MESSAGES/reference_manual/filters.po @@ -1,51 +1,50 @@ # translation of docs_krita_org_reference_manual___filters.po to Slovak # Roman Paholik , 2019. msgid "" msgstr "" "Project-Id-Version: docs_krita_org_reference_manual___filters\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-03-09 03:31+0100\n" "PO-Revision-Date: 2019-03-13 10:24+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" #: ../../reference_manual/filters.rst:5 msgid "Filters" msgstr "Filtre" #: ../../reference_manual/filters.rst:7 msgid "" -"Filters are little scripts or operations you can run on your drawing. You can" -" visualise them as real-world camera filters that can make a photo darker or" -" blurrier. Or perhaps like a coffee filter, where only water and coffee gets" -" through, and the ground coffee stays behind." +"Filters are little scripts or operations you can run on your drawing. You " +"can visualise them as real-world camera filters that can make a photo darker " +"or blurrier. Or perhaps like a coffee filter, where only water and coffee " +"gets through, and the ground coffee stays behind." msgstr "" #: ../../reference_manual/filters.rst:9 msgid "" -"Filters are unique to digital painting in terms of complexity, and their part" -" of the painting pipeline. Some artists only use filters to adjust their" -" colours a little. Others, using Filter Layers and Filter Masks use them to" -" dynamically update a part of an image to be filtered. This way, they can" -" keep the original underneath without changing the original image. This is a" -" part of a technique called 'non-destructive' editing." +"Filters are unique to digital painting in terms of complexity, and their " +"part of the painting pipeline. Some artists only use filters to adjust their " +"colours a little. Others, using Filter Layers and Filter Masks use them to " +"dynamically update a part of an image to be filtered. This way, they can " +"keep the original underneath without changing the original image. This is a " +"part of a technique called 'non-destructive' editing." msgstr "" #: ../../reference_manual/filters.rst:11 msgid "" -"Filters can be accessed via the :guilabel:`Filters` menu. Krita has two types" -" of filters: Internal and G'MIC filters." +"Filters can be accessed via the :guilabel:`Filters` menu. Krita has two " +"types of filters: Internal and G'MIC filters." msgstr "" #: ../../reference_manual/filters.rst:13 msgid "" -"Internal filters are often multithreaded, and can thus be used with the" -" filter brush or the adjustment filters." +"Internal filters are often multithreaded, and can thus be used with the " +"filter brush or the adjustment filters." msgstr "" - diff --git a/locale/sk/LC_MESSAGES/reference_manual/main_menu.po b/locale/sk/LC_MESSAGES/reference_manual/main_menu.po index 2b094670f..8812d6e81 100644 --- a/locale/sk/LC_MESSAGES/reference_manual/main_menu.po +++ b/locale/sk/LC_MESSAGES/reference_manual/main_menu.po @@ -1,26 +1,25 @@ # translation of docs_krita_org_reference_manual___main_menu.po to Slovak # Roman Paholik , 2019. msgid "" msgstr "" "Project-Id-Version: docs_krita_org_reference_manual___main_menu\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-19 03:36+0100\n" "PO-Revision-Date: 2019-03-13 12:25+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" #: ../../reference_manual/main_menu.rst:5 msgid "Main Menu" msgstr "Hlavné menu" #: ../../reference_manual/main_menu.rst:7 msgid "" "A list of all of main menu actions and a short description on what they do." msgstr "Zoznam všetkých akcií hlavnej ponuky a krátky popis, čo robia." - diff --git a/locale/sk/LC_MESSAGES/reference_manual/maths_input.po b/locale/sk/LC_MESSAGES/reference_manual/maths_input.po index c776854be..433d2d3c6 100644 --- a/locale/sk/LC_MESSAGES/reference_manual/maths_input.po +++ b/locale/sk/LC_MESSAGES/reference_manual/maths_input.po @@ -1,236 +1,236 @@ # translation of docs_krita_org_reference_manual___maths_input.po to Slovak # Roman Paholik , 2019. msgid "" msgstr "" "Project-Id-Version: docs_krita_org_reference_manual___maths_input\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-03-11 03:34+0100\n" "PO-Revision-Date: 2019-03-13 12:23+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" #: ../../reference_manual/maths_input.rst:1 msgid "" -"Overview of maths operations that can be used in Krita spinboxes and number" -" inputs." +"Overview of maths operations that can be used in Krita spinboxes and number " +"inputs." msgstr "" #: ../../reference_manual/maths_input.rst:17 msgid "Maths Input" msgstr "Matematické vstupy" #: ../../reference_manual/maths_input.rst:19 msgid "" -"Also known as Numerical Input boxes. You can make Krita do simple maths for" -" you in the places where we have number input. Just select the number in a" -" spinbox, or right-click a slider to activate number input. It doesn't do" -" unit conversion yet, but this is planned." +"Also known as Numerical Input boxes. You can make Krita do simple maths for " +"you in the places where we have number input. Just select the number in a " +"spinbox, or right-click a slider to activate number input. It doesn't do " +"unit conversion yet, but this is planned." msgstr "" #: ../../reference_manual/maths_input.rst:22 msgid "Possible Functions" msgstr "Možné funkcie" #: ../../reference_manual/maths_input.rst:25 msgid "Just adds the numbers. Usage: ``50+100`` Output: ``150``" msgstr "" #: ../../reference_manual/maths_input.rst:26 msgid "Addition (Operator: + )" msgstr "" #: ../../reference_manual/maths_input.rst:29 msgid "" -"Just subtracts the last number from the first. Usage: ``50-100`` Output:" -" ``50``" +"Just subtracts the last number from the first. Usage: ``50-100`` Output: " +"``50``" msgstr "" #: ../../reference_manual/maths_input.rst:30 msgid "Subtraction (Operator: - )" msgstr "" #: ../../reference_manual/maths_input.rst:33 msgid "Just multiplies the numbers. Usage: ``50*100`` Output: ``5000``" msgstr "" #: ../../reference_manual/maths_input.rst:34 msgid "Multiplication (Operator: * )" msgstr "" #: ../../reference_manual/maths_input.rst:37 msgid "Just divides the numbers. Usage: ``50/100`` Output: ``0.5``" msgstr "" #: ../../reference_manual/maths_input.rst:38 msgid "Division (Operator: / )" msgstr "" #: ../../reference_manual/maths_input.rst:41 msgid "" -"Makes the last number the exponent of the first and calculates the result." -" Usage: ``2^8`` Output: ``256``" +"Makes the last number the exponent of the first and calculates the result. " +"Usage: ``2^8`` Output: ``256``" msgstr "" #: ../../reference_manual/maths_input.rst:42 msgid "Exponent (Operator: ^ )" msgstr "" #: ../../reference_manual/maths_input.rst:45 msgid "" "Gives you the sine of the given angle. Usage: ``sin(50)`` Output: ``0.76``" msgstr "" #: ../../reference_manual/maths_input.rst:46 msgid "Sine (Operator: sin() )" msgstr "" #: ../../reference_manual/maths_input.rst:49 msgid "" "Gives you the cosine of the given angle. Usage: ``cos(50)`` Output: ``0.64``" msgstr "" #: ../../reference_manual/maths_input.rst:50 msgid "Cosine (Operator: cos() )" msgstr "" #: ../../reference_manual/maths_input.rst:53 msgid "" "Gives you the tangent of the given angle. Usage: ``tan(50)`` Output: ``1.19``" msgstr "" #: ../../reference_manual/maths_input.rst:54 msgid "Tangent (Operator: tan() )" msgstr "" #: ../../reference_manual/maths_input.rst:57 msgid "" -"Inverse function of the sine, gives you the angle which the sine equals the" -" argument. Usage: ``asin(0.76)`` Output: ``50``" +"Inverse function of the sine, gives you the angle which the sine equals the " +"argument. Usage: ``asin(0.76)`` Output: ``50``" msgstr "" #: ../../reference_manual/maths_input.rst:58 msgid "Arc Sine (Operator: asin() )" msgstr "" #: ../../reference_manual/maths_input.rst:61 msgid "" -"Inverse function of the cosine, gives you the angle which the cosine equals" -" the argument. Usage: ``acos(0.64)`` Output: ``50``" +"Inverse function of the cosine, gives you the angle which the cosine equals " +"the argument. Usage: ``acos(0.64)`` Output: ``50``" msgstr "" #: ../../reference_manual/maths_input.rst:62 msgid "Arc Cosine (Operator: acos() )" msgstr "" #: ../../reference_manual/maths_input.rst:65 msgid "" -"Inverse function of the tangent, gives you the angle which the tangent equals" -" the argument. Usage: ``atan(1.19)`` Output: ``50``" +"Inverse function of the tangent, gives you the angle which the tangent " +"equals the argument. Usage: ``atan(1.19)`` Output: ``50``" msgstr "" #: ../../reference_manual/maths_input.rst:66 msgid "Arc Tangent (Operator: atan() )" msgstr "" #: ../../reference_manual/maths_input.rst:69 msgid "" "Gives you the value without negatives. Usage: ``abs(75-100)`` Output: ``25``" msgstr "" #: ../../reference_manual/maths_input.rst:70 msgid "Absolute (Operator: abs() )" msgstr "" #: ../../reference_manual/maths_input.rst:73 msgid "" -"Gives you given values using e as the exponent. Usage: ``exp(1)`` Output:" -" ``2.7183``" +"Gives you given values using e as the exponent. Usage: ``exp(1)`` Output: " +"``2.7183``" msgstr "" #: ../../reference_manual/maths_input.rst:74 msgid "Exponent (Operator: exp() )" msgstr "" #: ../../reference_manual/maths_input.rst:77 msgid "" -"Gives you the natural logarithm, which means it has the inverse functionality" -" to exp(). Usage: ``ln(2)`` Output: ``0.6931``" +"Gives you the natural logarithm, which means it has the inverse " +"functionality to exp(). Usage: ``ln(2)`` Output: ``0.6931``" msgstr "" #: ../../reference_manual/maths_input.rst:79 msgid "Natural Logarithm (Operator: ln() )" msgstr "" #: ../../reference_manual/maths_input.rst:81 msgid "The following are technically supported but bugged:" msgstr "" #: ../../reference_manual/maths_input.rst:84 msgid "" -"Gives you logarithms of the given value. Usage: ``log10(50)`` Output: ``0.64``" +"Gives you logarithms of the given value. Usage: ``log10(50)`` Output: " +"``0.64``" msgstr "" #: ../../reference_manual/maths_input.rst:86 msgid "Common Logarithm (Operator: log10() )" msgstr "" #: ../../reference_manual/maths_input.rst:89 msgid "Order of Operations." msgstr "" #: ../../reference_manual/maths_input.rst:91 msgid "" -"The order of operations is a globally agreed upon reading order for" -" interpreting mathematical expressions. It solves how to read an expression" -" like:" +"The order of operations is a globally agreed upon reading order for " +"interpreting mathematical expressions. It solves how to read an expression " +"like:" msgstr "" #: ../../reference_manual/maths_input.rst:93 msgid "``2+3*4``" msgstr "``2+3*4``" #: ../../reference_manual/maths_input.rst:95 msgid "" -"You could read it as 2+3 = 5, and then 5*4 =20. Or you could say 3*4 = 12 and" -" then 2+12 = 14." +"You could read it as 2+3 = 5, and then 5*4 =20. Or you could say 3*4 = 12 " +"and then 2+12 = 14." msgstr "" #: ../../reference_manual/maths_input.rst:97 msgid "" -"The order of operations itself is Exponents, Multiplication, Addition," -" Subtraction. So we first multiply, and then add, making the answer to the" -" above 14, and this is how Krita will interpret the above." +"The order of operations itself is Exponents, Multiplication, Addition, " +"Subtraction. So we first multiply, and then add, making the answer to the " +"above 14, and this is how Krita will interpret the above." msgstr "" #: ../../reference_manual/maths_input.rst:99 msgid "" -"We can use brackets to specify certain operations go first, so to get 20 from" -" the above expression, we do the following:" +"We can use brackets to specify certain operations go first, so to get 20 " +"from the above expression, we do the following:" msgstr "" #: ../../reference_manual/maths_input.rst:101 msgid "``( 2+3 )*4``" msgstr "``( 2+3 )*4``" #: ../../reference_manual/maths_input.rst:103 msgid "" "Krita can interpret the brackets accordingly and will give 20 from this." msgstr "" #: ../../reference_manual/maths_input.rst:106 msgid "Errors" msgstr "Chyby" #: ../../reference_manual/maths_input.rst:108 msgid "" -"Sometimes, you see the result becoming red. This means you made a mistake and" -" Krita cannot parse your maths expression. Simply click the input box and try" -" again." +"Sometimes, you see the result becoming red. This means you made a mistake " +"and Krita cannot parse your maths expression. Simply click the input box and " +"try again." msgstr "" - diff --git a/locale/sk/LC_MESSAGES/reference_manual/preferences.po b/locale/sk/LC_MESSAGES/reference_manual/preferences.po index 954e740c3..28807f6f9 100644 --- a/locale/sk/LC_MESSAGES/reference_manual/preferences.po +++ b/locale/sk/LC_MESSAGES/reference_manual/preferences.po @@ -1,61 +1,61 @@ # translation of docs_krita_org_reference_manual___preferences.po to Slovak # Roman Paholik , 2019. msgid "" msgstr "" "Project-Id-Version: docs_krita_org_reference_manual___preferences\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-19 03:36+0100\n" "PO-Revision-Date: 2019-03-13 12:22+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" #: ../../reference_manual/preferences.rst:1 msgid "Krita's settings and preferences options." msgstr "Voľby nastavení a predvolieb Krita." #: ../../reference_manual/preferences.rst:16 msgid "Preferences" msgstr "Nastavenia" #: ../../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." +"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 "" #: ../../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!" +"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 "" #: ../../reference_manual/preferences.rst:22 msgid "" -"If you have installed Krita through the Windows store, the kritarc file will" -" be in another location:" +"If you have installed Krita through the Windows store, the kritarc file will " +"be in another location:" msgstr "" #: ../../reference_manual/preferences.rst:24 msgid "" -":file:`%LOCALAPPDATA%\\\\Packages\\\\49800Krita_{RANDOM" -" STRING}\\\\LocalCache\\\\Local\\\\kritarc`" +":file:`%LOCALAPPDATA%\\\\Packages\\\\49800Krita_{RANDOM STRING}\\\\LocalCache" +"\\\\Local\\\\kritarc`" msgstr "" #: ../../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." +"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 "" - diff --git a/locale/sk/LC_MESSAGES/reference_manual/resource_management.po b/locale/sk/LC_MESSAGES/reference_manual/resource_management.po index 58c2aedf5..69c3bb076 100644 --- a/locale/sk/LC_MESSAGES/reference_manual/resource_management.po +++ b/locale/sk/LC_MESSAGES/reference_manual/resource_management.po @@ -1,287 +1,286 @@ # translation of docs_krita_org_reference_manual___resource_management.po to Slovak # Roman Paholik , 2019. msgid "" msgstr "" "Project-Id-Version: docs_krita_org_reference_manual___resource_management\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-03-08 03:41+0100\n" "PO-Revision-Date: 2019-03-13 12:35+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 "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: mouseleft" #: ../../:8 msgid "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" msgstr "" ".. image:: images/icons/Krita_mouse_scroll.png\n" " :alt: mousescroll" #: ../../reference_manual/resource_management.rst:None msgid ".. image:: images/en/Tags-krita.png" msgstr ".. image:: images/en/Tags-krita.png" #: ../../reference_manual/resource_management.rst:None msgid ".. image:: images/en/Manageresources.png" msgstr ".. image:: images/en/Manageresources.png" #: ../../reference_manual/resource_management.rst:1 msgid "Overview of Resource Management in Krita." msgstr "" #: ../../reference_manual/resource_management.rst:16 msgid "Resource Management" msgstr "Správa zdrojov" #: ../../reference_manual/resource_management.rst:18 msgid "" -"Resources are pluggable bits of data, like brush presets or patterns. Krita" -" has variety of resources and also has a good resource management starting" -" from 2.9, making it really easy for artists to share and collate all the" -" resources together" +"Resources are pluggable bits of data, like brush presets or patterns. Krita " +"has variety of resources and also has a good resource management starting " +"from 2.9, making it really easy for artists to share and collate all the " +"resources together" msgstr "" #: ../../reference_manual/resource_management.rst:21 msgid "Bundles" msgstr "" #: ../../reference_manual/resource_management.rst:23 msgid "" -"Starting from 2.9 Krita has a new format to manage resources it is called" -" ''Bundles'', a bundle is just a compressed file containing all the resources" -" together." +"Starting from 2.9 Krita has a new format to manage resources it is called " +"''Bundles'', a bundle is just a compressed file containing all the resources " +"together." msgstr "" #: ../../reference_manual/resource_management.rst:26 msgid "Tags" msgstr "Značky" #: ../../reference_manual/resource_management.rst:28 msgid "" -"Krita also has a robust tagging system for you to manage the resources on the" -" fly while painting.All Krita resources can be tagged. These tags can be" -" added via the resource manager, but also via the respective dockers such as" -" brush preset docker, pattern docker etc. you can |mouseleft| the plus icon" -" in the docker and add a tag name. in addition to adding you can rename and" -" delete a tag as well." +"Krita also has a robust tagging system for you to manage the resources on " +"the fly while painting.All Krita resources can be tagged. These tags can be " +"added via the resource manager, but also via the respective dockers such as " +"brush preset docker, pattern docker etc. you can |mouseleft| the plus icon " +"in the docker and add a tag name. in addition to adding you can rename and " +"delete a tag as well." msgstr "" #: ../../reference_manual/resource_management.rst:33 msgid "" -"Resources can belong to one or more tags. For example, you may have a Brush" -" Preset of a favorite **Ink Pen** variant and have it tagged so it shows in" -" up in your Inking, Painting, Comics and Favorites groups of brushes." +"Resources can belong to one or more tags. For example, you may have a Brush " +"Preset of a favorite **Ink Pen** variant and have it tagged so it shows in " +"up in your Inking, Painting, Comics and Favorites groups of brushes." msgstr "" #: ../../reference_manual/resource_management.rst:34 msgid "" -"Brushes in the \"Predefined\" tab of the Brush Settings Editor can be also" -" tagged and grouped for convenience." +"Brushes in the \"Predefined\" tab of the Brush Settings Editor can be also " +"tagged and grouped for convenience." msgstr "" #: ../../reference_manual/resource_management.rst:37 msgid "Filtering" msgstr "Filtrovanie" #: ../../reference_manual/resource_management.rst:40 msgid "" -"Some dockers, for example the brush preset docker as shown below, have a" -" resource filter, which functions like a powerful search bar for the resource" -" in question." +"Some dockers, for example the brush preset docker as shown below, have a " +"resource filter, which functions like a powerful search bar for the resource " +"in question." msgstr "" #: ../../reference_manual/resource_management.rst:43 msgid ".. image:: images/en/Brushpreset-filters.png" msgstr ".. image:: images/en/Brushpreset-filters.png" #: ../../reference_manual/resource_management.rst:44 msgid "" -"You can enter brush name, tag name to quickly pull up a list of brush preset" -" you want. When you select any tag from the tag dropdown and want to include" -" brush presets from other tags as well then you can add filters the following" -" way:" +"You can enter brush name, tag name to quickly pull up a list of brush preset " +"you want. When you select any tag from the tag dropdown and want to include " +"brush presets from other tags as well then you can add filters the following " +"way:" msgstr "" #: ../../reference_manual/resource_management.rst:46 msgid "" -"To filter based on the partial, case insensitive name of the resources you" -" can add ``partialname`` or ``!partialname``" +"To filter based on the partial, case insensitive name of the resources you " +"can add ``partialname`` or ``!partialname``" msgstr "" #: ../../reference_manual/resource_management.rst:47 msgid "" -"To include other Tags type the respective name of the tag in square brackets" -" like this ``[Tagname]`` or to exclude a tag type ``![Tagname]``." +"To include other Tags type the respective name of the tag in square brackets " +"like this ``[Tagname]`` or to exclude a tag type ``![Tagname]``." msgstr "" #: ../../reference_manual/resource_management.rst:48 msgid "" -"For case sensitive matching of preset name type ``\"Preset name\"`` or ``!" -" \"Preset name\"`` to exclude." +"For case sensitive matching of preset name type ``\"Preset name\"`` or ``! " +"\"Preset name\"`` to exclude." msgstr "" #: ../../reference_manual/resource_management.rst:51 msgid "An incredibly quick way to save a group or brushes into a tag is to:" msgstr "" #: ../../reference_manual/resource_management.rst:53 msgid "" -"Create a new tag by |mouseleft| on the green plus sign. This will empty out" -" the contents of the Brush Preset docker." +"Create a new tag by |mouseleft| on the green plus sign. This will empty out " +"the contents of the Brush Preset docker." msgstr "" #: ../../reference_manual/resource_management.rst:54 msgid "" -"Use the :guilabel:`Resource Filter` at the bottom of the :guilabel:`Brush" -" Presets` dock or :guilabel:`Brush Settings Editor` to type in what you want" -" to group. For instance: if you type **Pencil** in the filter box you will" -" get all Brush Presets with **Pencil** somewhere in their name. Now you have" -" all the Pencil-related Brush Presets together in one place." +"Use the :guilabel:`Resource Filter` at the bottom of the :guilabel:`Brush " +"Presets` dock or :guilabel:`Brush Settings Editor` to type in what you want " +"to group. For instance: if you type **Pencil** in the filter box you will " +"get all Brush Presets with **Pencil** somewhere in their name. Now you have " +"all the Pencil-related Brush Presets together in one place." msgstr "" #: ../../reference_manual/resource_management.rst:55 msgid "" -"To finish, click the :guilabel:`Save` button (small disk icon to the right of" -" the :guilabel:`Resource Filter` box) or press :kbd:`Enter` and all the items" -" will be saved with the new tag you created." +"To finish, click the :guilabel:`Save` button (small disk icon to the right " +"of the :guilabel:`Resource Filter` box) or press :kbd:`Enter` and all the " +"items will be saved with the new tag you created." msgstr "" #: ../../reference_manual/resource_management.rst:57 msgid "" -"Now, anytime you want to open up your \"digital pencil box\" and see what you" -" have to work with all you have to do is use the pull-down and select" -" '''Pencils'''. The Resource Filter works the same way in other parts of" -" Krita so be on the lookout for it!" +"Now, anytime you want to open up your \"digital pencil box\" and see what " +"you have to work with all you have to do is use the pull-down and select " +"'''Pencils'''. The Resource Filter works the same way in other parts of " +"Krita so be on the lookout for it!" msgstr "" #: ../../reference_manual/resource_management.rst:60 msgid "Resource Zooming" msgstr "" #: ../../reference_manual/resource_management.rst:60 msgid "" -"If you find the thumbnails of the resources such as color swatches brushes" -" and pattern to be small you can make them bigger or '''zoom in'''. All" -" resource selectors can be zoomed in and out of, by hovering over the" -" selector and using :kbd:`Ctrl +` |mousescroll|" +"If you find the thumbnails of the resources such as color swatches brushes " +"and pattern to be small you can make them bigger or '''zoom in'''. All " +"resource selectors can be zoomed in and out of, by hovering over the " +"selector and using :kbd:`Ctrl +` |mousescroll|" msgstr "" #: ../../reference_manual/resource_management.rst:63 msgid "Managing Resources" msgstr "" #: ../../reference_manual/resource_management.rst:65 msgid "" -"As mentioned earlier Krita has a flexible resource management system." -" Starting from version 2.9 you can share various resources mentioned above by" -" sharing a single compressed zip file created within Krita." +"As mentioned earlier Krita has a flexible resource management system. " +"Starting from version 2.9 you can share various resources mentioned above by " +"sharing a single compressed zip file created within Krita." msgstr "" #: ../../reference_manual/resource_management.rst:67 msgid "" -"The manage resources section in the settings was also revamped for making it" -" easy for the artists to prepare these bundle files. You can open manage" -" resource section by going to :menuselection:`Settings` then" -" :menuselection:`Manage Resources`" +"The manage resources section in the settings was also revamped for making it " +"easy for the artists to prepare these bundle files. You can open manage " +"resource section by going to :menuselection:`Settings` then :menuselection:" +"`Manage Resources`" msgstr "" #: ../../reference_manual/resource_management.rst:73 msgid "Importing Bundles" msgstr "" #: ../../reference_manual/resource_management.rst:75 msgid "" -"To import a bundle click on :guilabel:`Import Bundles/Resources` button on" -" the top right side of the dialog. Select .bundle file format from the file" -" type if it is not already selected, browse to the folder where you have" -" downloaded the bundle, select it and click open. Once the bundle is imported" -" it will be listed in the :guilabel:`Active Bundle` section, If you don't" -" need the bundle you can temporarily make it inactive by selecting it and" -" clicking on the arrow button, this will move it to the :guilabel:`Inactive`" -" section." +"To import a bundle click on :guilabel:`Import Bundles/Resources` button on " +"the top right side of the dialog. Select .bundle file format from the file " +"type if it is not already selected, browse to the folder where you have " +"downloaded the bundle, select it and click open. Once the bundle is imported " +"it will be listed in the :guilabel:`Active Bundle` section, If you don't " +"need the bundle you can temporarily make it inactive by selecting it and " +"clicking on the arrow button, this will move it to the :guilabel:`Inactive` " +"section." msgstr "" #: ../../reference_manual/resource_management.rst:79 msgid "Creating your own Bundle" msgstr "" #: ../../reference_manual/resource_management.rst:81 msgid "" -"You can create your own bundle from the resources of your choice. Click on" -" the :guilabel:`Create bundle` button, This will open a dialog box as shown" -" below" +"You can create your own bundle from the resources of your choice. Click on " +"the :guilabel:`Create bundle` button, This will open a dialog box as shown " +"below" msgstr "" #: ../../reference_manual/resource_management.rst:84 msgid ".. image:: images/en/Creating-bundle.png" msgstr ".. image:: images/en/Creating-bundle.png" #: ../../reference_manual/resource_management.rst:85 msgid "" -"The left hand section is for filling up information about the bundle like" -" author name, website, email , bundle icon, etc. the right hand side provides" -" a list of available resources. Choose the type of resource you wish to add" -" in to the bundle from the drop-down above and add it to the bundle by" -" selecting a resource and clicking on the arrow button." +"The left hand section is for filling up information about the bundle like " +"author name, website, email , bundle icon, etc. the right hand side provides " +"a list of available resources. Choose the type of resource you wish to add " +"in to the bundle from the drop-down above and add it to the bundle by " +"selecting a resource and clicking on the arrow button." msgstr "" #: ../../reference_manual/resource_management.rst:90 msgid "" -"Make sure you add brush tips for used in the respective paintop preset you" -" are adding to the bundle. If you don't provide the brush tips then the brush" -" presets loaded from this bundle will have a 'X' mark on the thumbnail" -" denoting that the texture is missing. And the brush preset won't be the same" +"Make sure you add brush tips for used in the respective paintop preset you " +"are adding to the bundle. If you don't provide the brush tips then the brush " +"presets loaded from this bundle will have a 'X' mark on the thumbnail " +"denoting that the texture is missing. And the brush preset won't be the same" msgstr "" #: ../../reference_manual/resource_management.rst:92 msgid "" -"Once you have added all the resources you can create bundle by clicking on" -" the save button, the bundle will be saved in the location you have" -" specified. You can then share this bundle with other artists or load it on" -" other workstations." +"Once you have added all the resources you can create bundle by clicking on " +"the save button, the bundle will be saved in the location you have " +"specified. You can then share this bundle with other artists or load it on " +"other workstations." msgstr "" #: ../../reference_manual/resource_management.rst:95 msgid "Deleting Backup files" msgstr "" #: ../../reference_manual/resource_management.rst:97 msgid "" -"When you delete a preset from Krita. Krita doesn't actually delete the" -" physical copy of the preset. It just adds it to a black list so that Next" -" time when you start Krita the presets from this list are not loaded. To" -" delete the brushes from this list click on delete backup files" +"When you delete a preset from Krita. Krita doesn't actually delete the " +"physical copy of the preset. It just adds it to a black list so that Next " +"time when you start Krita the presets from this list are not loaded. To " +"delete the brushes from this list click on delete backup files" msgstr "" #: ../../reference_manual/resource_management.rst:100 msgid "Deleting Imported Bundles" msgstr "" #: ../../reference_manual/resource_management.rst:102 msgid "" -"In-case you wish to delete the bundles you have imported permanently click on" -" the :guilabel:`Open Resource Folder` button in the :guilabel:`Manage" -" Resources` dialog. This will open the resource folder in your file manager /" -" explorer. Go inside the bundles folder and delete the bundle file which you" -" don't need any more. The next time you start Krita the bundle and its" -" associated resources will not be loaded." +"In-case you wish to delete the bundles you have imported permanently click " +"on the :guilabel:`Open Resource Folder` button in the :guilabel:`Manage " +"Resources` dialog. This will open the resource folder in your file manager / " +"explorer. Go inside the bundles folder and delete the bundle file which you " +"don't need any more. The next time you start Krita the bundle and its " +"associated resources will not be loaded." msgstr "" #: ../../reference_manual/resource_management.rst:105 msgid "Resource Types in Krita" msgstr "" - diff --git a/locale/sk/LC_MESSAGES/reference_manual/stroke_selection.po b/locale/sk/LC_MESSAGES/reference_manual/stroke_selection.po index 755e8f985..4df5e3b2f 100644 --- a/locale/sk/LC_MESSAGES/reference_manual/stroke_selection.po +++ b/locale/sk/LC_MESSAGES/reference_manual/stroke_selection.po @@ -1,73 +1,72 @@ # translation of docs_krita_org_reference_manual___stroke_selection.po to Slovak # Roman Paholik , 2019. msgid "" msgstr "" "Project-Id-Version: docs_krita_org_reference_manual___stroke_selection\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-19 03:36+0100\n" "PO-Revision-Date: 2019-03-13 12:33+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" #: ../../:1 msgid ".. image:: images/en/Stroke_Selection_4.png" msgstr ".. image:: images/en/Stroke_Selection_4.png" #: ../../reference_manual/stroke_selection.rst:1 msgid "How to use the stroke selection command in Krita." msgstr "" #: ../../reference_manual/stroke_selection.rst:15 msgid "Stroke Selection" msgstr "Výber ťahu" #: ../../reference_manual/stroke_selection.rst:17 msgid "" -"Sometimes, you want to add an even border around a selection. Stroke" -" Selection allows you to do this. It's under :menuselection:`Edit --> Stroke" -" Selection`" +"Sometimes, you want to add an even border around a selection. Stroke " +"Selection allows you to do this. It's under :menuselection:`Edit --> Stroke " +"Selection`" msgstr "" #: ../../reference_manual/stroke_selection.rst:19 msgid "First make a selection and call up the menu:" msgstr "" #: ../../reference_manual/stroke_selection.rst:22 msgid ".. image:: images/en/Krita_stroke_selection_1.png" msgstr ".. image:: images/en/Krita_stroke_selection_1.png" #: ../../reference_manual/stroke_selection.rst:23 msgid "" -"The main options are about using the current brush, or lining the selection" -" with an even line. You can use the current foreground color, the background" -" color or a custom color." +"The main options are about using the current brush, or lining the selection " +"with an even line. You can use the current foreground color, the background " +"color or a custom color." msgstr "" #: ../../reference_manual/stroke_selection.rst:25 msgid "Using the current brush allows you to use textured brushes:" msgstr "" #: ../../reference_manual/stroke_selection.rst:28 msgid ".. image:: images/en/Stroke_selection_2.png" msgstr ".. image:: images/en/Stroke_selection_2.png" #: ../../reference_manual/stroke_selection.rst:29 msgid "" -"Lining the selection also allows you to set the background color, on top of" -" the line width in pixels or inches:" +"Lining the selection also allows you to set the background color, on top of " +"the line width in pixels or inches:" msgstr "" #: ../../reference_manual/stroke_selection.rst:32 msgid ".. image:: images/en/Krita_stroke_selection_3.png" msgstr ".. image:: images/en/Krita_stroke_selection_3.png" #: ../../reference_manual/stroke_selection.rst:33 msgid "This creates nice silhouettes:" msgstr "" - diff --git a/locale/sk/LC_MESSAGES/reference_manual/tools.po b/locale/sk/LC_MESSAGES/reference_manual/tools.po index 47fb53025..52094c264 100644 --- a/locale/sk/LC_MESSAGES/reference_manual/tools.po +++ b/locale/sk/LC_MESSAGES/reference_manual/tools.po @@ -1,25 +1,24 @@ # translation of docs_krita_org_reference_manual___tools.po to Slovak # Roman Paholik , 2019. msgid "" msgstr "" "Project-Id-Version: docs_krita_org_reference_manual___tools\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-19 03:36+0100\n" "PO-Revision-Date: 2019-03-13 10:30+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" #: ../../reference_manual/tools.rst:5 msgid "Tools" msgstr "Nástroje" #: ../../reference_manual/tools.rst:7 msgid "The contents of the toolbox docker." msgstr "Obsah panelu nástrojov." - diff --git a/locale/sk/LC_MESSAGES/resources_page.po b/locale/sk/LC_MESSAGES/resources_page.po index daf2c77cc..eaad25f68 100644 --- a/locale/sk/LC_MESSAGES/resources_page.po +++ b/locale/sk/LC_MESSAGES/resources_page.po @@ -1,282 +1,281 @@ # translation of docs_krita_org_resources_page.po to Slovak # Roman Paholik , 2019. msgid "" msgstr "" "Project-Id-Version: docs_krita_org_resources_page\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-24 03:22+0100\n" "PO-Revision-Date: 2019-03-13 12:31+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" #: ../../resources_page.rst:0 msgid ".. image:: images/en/resource_packs/Resources-deevadBrushes.jpg" msgstr ".. image:: images/en/resource_packs/Resources-deevadBrushes.jpg" #: ../../resources_page.rst:0 msgid ".. image:: images/en/resource_packs/Resources-mirandaBrushes.jpg" msgstr ".. image:: images/en/resource_packs/Resources-mirandaBrushes.jpg" #: ../../resources_page.rst:0 msgid ".. image:: images/en/resource_packs/Resources-conceptBrushes.jpg" msgstr ".. image:: images/en/resource_packs/Resources-conceptBrushes.jpg" #: ../../resources_page.rst:0 msgid ".. image:: images/en/resource_packs/Resources-aldyBrushes.jpg" msgstr ".. image:: images/en/resource_packs/Resources-aldyBrushes.jpg" #: ../../resources_page.rst:0 msgid ".. image:: images/en/resource_packs/Resources-vascoBrushes.jpg" msgstr ".. image:: images/en/resource_packs/Resources-vascoBrushes.jpg" #: ../../resources_page.rst:0 msgid ".. image:: images/en/resource_packs/Resources-meemodrawsBrushes.jpg" msgstr ".. image:: images/en/resource_packs/Resources-meemodrawsBrushes.jpg" #: ../../resources_page.rst:0 msgid ".. image:: images/en/resource_packs/Resources-stalcryBrushes.jpg" msgstr ".. image:: images/en/resource_packs/Resources-stalcryBrushes.jpg" #: ../../resources_page.rst:0 msgid ".. image:: images/en/resource_packs/Resources-woltheraBrushes.jpg" msgstr ".. image:: images/en/resource_packs/Resources-woltheraBrushes.jpg" #: ../../resources_page.rst:0 msgid ".. image:: images/en/resource_packs/Resources-nylnook.jpg" msgstr ".. image:: images/en/resource_packs/Resources-nylnook.jpg" #: ../../resources_page.rst:0 msgid ".. image:: images/en/resource_packs/Resources-hushcoilBrushes.png" msgstr ".. image:: images/en/resource_packs/Resources-hushcoilBrushes.png" #: ../../resources_page.rst:0 msgid ".. image:: images/en/resource_packs/Resources-raghukamathBrushes.png" msgstr ".. image:: images/en/resource_packs/Resources-raghukamathBrushes.png" #: ../../resources_page.rst:0 msgid ".. image:: images/en/resource_packs/Resources-GDQuestBrushes.jpeg" msgstr ".. image:: images/en/resource_packs/Resources-GDQuestBrushes.jpeg" #: ../../resources_page.rst:0 msgid ".. image:: images/en/resource_packs/Resources-iForce73Brushes.png" msgstr ".. image:: images/en/resource_packs/Resources-iForce73Brushes.png" #: ../../resources_page.rst:0 msgid ".. image:: images/en/resource_packs/Resources-deevadTextures.jpg" msgstr ".. image:: images/en/resource_packs/Resources-deevadTextures.jpg" #: ../../resources_page.rst:0 msgid ".. image:: images/en/resource_packs/Resources-deevadTextures2.jpg" msgstr ".. image:: images/en/resource_packs/Resources-deevadTextures2.jpg" #: ../../resources_page.rst:0 msgid ".. image:: images/en/resource_packs/simon_pixel_art_course.png" msgstr ".. image:: images/en/resource_packs/simon_pixel_art_course.png" #: ../../resources_page.rst:1 msgid "Resource Packs for Krita." msgstr "Balíky zdrojov pre Krita." #: ../../resources_page.rst:18 msgid "Resources" msgstr "Zdroje" #: ../../resources_page.rst:21 msgid "Brush Packs" msgstr "Balíky štetcov" #: ../../resources_page.rst:28 ../../resources_page.rst:87 #: ../../resources_page.rst:91 msgid "David Revoy" msgstr "David Revoy" #: ../../resources_page.rst:32 msgid "Ramon Miranda" msgstr "Ramon Miranda" #: ../../resources_page.rst:36 msgid "Concept art & Illustration Pack" msgstr "" #: ../../resources_page.rst:40 msgid "Al-dy" msgstr "Al-dy" #: ../../resources_page.rst:44 msgid "Vasco Basqué" msgstr "Vasco Basqué" #: ../../resources_page.rst:48 msgid "Meemodraws" msgstr "" #: ../../resources_page.rst:52 msgid "Stalcry" msgstr "Stalcry" #: ../../resources_page.rst:56 msgid "Wolthera" msgstr "Wolthera" #: ../../resources_page.rst:60 msgid "Nylnook" msgstr "Nylnook" #: ../../resources_page.rst:64 msgid "Hushcoil" msgstr "" #: ../../resources_page.rst:68 msgid "Raghukamath" msgstr "" #: ../../resources_page.rst:72 msgid "GDQuest" msgstr "GDQuest" #: ../../resources_page.rst:80 msgid "Texture Packs" msgstr "Balíky textúr" #: ../../resources_page.rst:94 msgid "External tutorials" msgstr "" #: ../../resources_page.rst:101 msgid "Simón Sanchez' \"Learn to Create Pixel Art from Zero\" course on Udemy" msgstr "" #: ../../resources_page.rst:104 msgid "User-made Python Plugins" msgstr "" #: ../../resources_page.rst:105 msgid "" -"To install and manage your plugins, visit the" -" :ref:`krita_python_plugin_howto` area. See the second area on how to get" -" Krita to recognize your plugin." +"To install and manage your plugins, visit the :ref:" +"`krita_python_plugin_howto` area. See the second area on how to get Krita to " +"recognize your plugin." msgstr "" #: ../../resources_page.rst:107 msgid "Direct Eraser Plugin" msgstr "" #: ../../resources_page.rst:109 msgid "" "http://www.mediafire.com/file/sotzc2keogz0bor/Krita+Direct+Eraser+Plugin.zip" msgstr "" "http://www.mediafire.com/file/sotzc2keogz0bor/Krita+Direct+Eraser+Plugin.zip" #: ../../resources_page.rst:111 msgid "Tablet Controls Docker" msgstr "" #: ../../resources_page.rst:113 msgid "https://github.com/tokyogeometry/tabui" msgstr "https://github.com/tokyogeometry/tabui" #: ../../resources_page.rst:115 msgid "On-screen Canvas Shortcuts" msgstr "" #: ../../resources_page.rst:117 msgid "" -"https://github.com/qeshi/henriks-onscreen-krita-shortcut-buttons/tree/master/h" -"enriks_krita_buttons" +"https://github.com/qeshi/henriks-onscreen-krita-shortcut-buttons/tree/master/" +"henriks_krita_buttons" msgstr "" -"https://github.com/qeshi/henriks-onscreen-krita-shortcut-buttons/tree/master/h" -"enriks_krita_buttons" +"https://github.com/qeshi/henriks-onscreen-krita-shortcut-buttons/tree/master/" +"henriks_krita_buttons" #: ../../resources_page.rst:119 msgid "Spine File Format Export" msgstr "" #: ../../resources_page.rst:121 msgid "https://github.com/chartinger/krita-unofficial-spine-export" msgstr "https://github.com/chartinger/krita-unofficial-spine-export" #: ../../resources_page.rst:123 msgid "GDQuest - Designer Tools" msgstr "" #: ../../resources_page.rst:125 msgid "https://github.com/GDquest/Krita-designer-tools" msgstr "https://github.com/GDquest/Krita-designer-tools" #: ../../resources_page.rst:127 msgid "AnimLayers (Animate with Layers)" msgstr "" #: ../../resources_page.rst:129 msgid "https://github.com/thomaslynge/krita-plugins" msgstr "https://github.com/thomaslynge/krita-plugins" #: ../../resources_page.rst:131 msgid "Art Revision Control (using GIT)" msgstr "" #: ../../resources_page.rst:133 msgid "https://github.com/abeimler/krita-plugin-durra" msgstr "https://github.com/abeimler/krita-plugin-durra" #: ../../resources_page.rst:135 msgid "Krita Plugin generator" msgstr "" #: ../../resources_page.rst:137 msgid "https://github.com/cg-cnu/vscode-krita-plugin-generator" msgstr "https://github.com/cg-cnu/vscode-krita-plugin-generator" #: ../../resources_page.rst:139 msgid "Bash Action (works with OSX and Linux)" msgstr "" #: ../../resources_page.rst:141 msgid "" -"https://github.com/juancarlospaco/krita-plugin-bashactions#krita-plugin-bashac" -"tions" +"https://github.com/juancarlospaco/krita-plugin-bashactions#krita-plugin-" +"bashactions" msgstr "" -"https://github.com/juancarlospaco/krita-plugin-bashactions#krita-plugin-bashac" -"tions" +"https://github.com/juancarlospaco/krita-plugin-bashactions#krita-plugin-" +"bashactions" #: ../../resources_page.rst:143 msgid "Reference Image Docker (old style)" msgstr "" #: ../../resources_page.rst:145 msgid "https://github.com/antoine-roux/krita-plugin-reference" msgstr "https://github.com/antoine-roux/krita-plugin-reference" #: ../../resources_page.rst:147 msgid "Post images on Mastadon" msgstr "" #: ../../resources_page.rst:149 msgid "https://github.com/spaceottercode/kritatoot" msgstr "https://github.com/spaceottercode/kritatoot" #: ../../resources_page.rst:151 msgid "Python auto-complete for text editors" msgstr "" #: ../../resources_page.rst:153 msgid "https://github.com/scottpetrovic/krita-python-auto-complete" msgstr "https://github.com/scottpetrovic/krita-python-auto-complete" #: ../../resources_page.rst:157 msgid "See Something We Missed?" msgstr "" #: ../../resources_page.rst:158 msgid "" -"Have a resource you made and want to to share it with other artists? Let us" -" know in the forum or visit our chat room to discuss getting the resource" -" added to here." +"Have a resource you made and want to to share it with other artists? Let us " +"know in the forum or visit our chat room to discuss getting the resource " +"added to here." msgstr "" - diff --git a/locale/sk/LC_MESSAGES/tutorials.po b/locale/sk/LC_MESSAGES/tutorials.po index c6102555a..c34b29b5b 100644 --- a/locale/sk/LC_MESSAGES/tutorials.po +++ b/locale/sk/LC_MESSAGES/tutorials.po @@ -1,32 +1,31 @@ # translation of docs_krita_org_tutorials.po to Slovak # Roman Paholik , 2019. msgid "" msgstr "" "Project-Id-Version: docs_krita_org_tutorials\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-19 03:36+0100\n" "PO-Revision-Date: 2019-03-13 12:28+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" #: ../../tutorials.rst:5 msgid "Tutorials and Howto's" msgstr "Cvičenia a návody" #: ../../tutorials.rst:7 msgid "" "Learn through developer and user generated tutorials to see Krita in action." msgstr "" -"Učte sa pomocou cvičení, ktoré vytvorili vývojári a používatelia a pozrite si" -" Kritu v akcii." +"Učte sa pomocou cvičení, ktoré vytvorili vývojári a používatelia a pozrite " +"si Kritu v akcii." #: ../../tutorials.rst:9 msgid "Contents:" msgstr "Obsah:" - 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 b0ff0bee6..a362730a7 100644 --- a/locale/sv/LC_MESSAGES/contributors_manual/krita_manual_conventions.po +++ b/locale/sv/LC_MESSAGES/contributors_manual/krita_manual_conventions.po @@ -1,877 +1,877 @@ # 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-03-12 03:34+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-03-03 19:32+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 "" #: ../../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 "" "`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 "" #: ../../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 "" #: ../../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 "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 "" #: ../../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 "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 "" #: ../../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 "" #: ../../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 "" #: ../../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 it's link-text." msgstr "" #: ../../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 "" #: ../../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 "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 "" #: ../../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 "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 "" #: ../../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 "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 "" #: ../../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 ff30b9684..e95d6d689 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,1066 +1,1066 @@ # 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-03-13 03:40+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-03-03 19:52+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 colour " "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 colour." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:71 msgid "" "Finally, group 4 has Vermillion red, citron yellow and cerulean blue. Their " "colours 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 colour 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 " "colour translate properly between color devices." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:82 msgid "" "It usually works by attempting to covert a colour to the reference colour " "space XYZ. XYZ is a coordinate system that has a spot for all colours 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 colour 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:88 msgid "" "To give a crude estimate, ICC profiles deal with keeping colours consistent " "over many interpretations of devices (screens, printers) by using a " "reference space, and OCIO deals with manipulating the interpretation of said " "colours." 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 grey it produces. Using " "these and several other measurements it creates an icc profile unique to " "your screen. You set these in Krita's colour 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 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-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.)" 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 colour 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 colorspace 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 colour reproduction. Use this if you want to " "see all colours 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 colours at whatever cost, which may result in awful looking " "colours. 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 "" "A in between solution between perceptual and absolute, relative will try to " "fit whatever colours it can match between colour 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 colourfulness, 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 '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." 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 colour 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 colour 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 colour 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 " "customly 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 colour maths, often concerning the blending of colours. " "This colour maths works best in linear colour space, and linear colour 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 colour 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 " "colour 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's 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 colours actually look strange: This is a " "bug in Firefox, which is because its `color management system is incomplete " "`_, save your png, jpg or tiff without an embedded profile to work " "around this." 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 " "bitdepth 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 specialised 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, mypaint, mangastudio, 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, mangastudio " "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 optimisers. 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 "" "Specialised 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 --> 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." 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 optimised content, and it's recommended to " "stay within 8bit, future screens may have higher bitdepths, 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 optimise 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 "" "`Visualising the XYZ colorspace `_" 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 colormanagement from argylcms manual `_" msgstr "" diff --git a/locale/sv/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po b/locale/sv/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po index 805e2949a..5082b2334 100644 --- a/locale/sv/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po +++ b/locale/sv/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po @@ -1,207 +1,207 @@ # 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-02-23 03:24+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-03-10 11:45+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" #: ../../:1 msgid "Use Undeformed Image" msgstr "Använd oförvrängd bild" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:1 msgid "The Deform Brush Engine manual page." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:16 msgid "Deform Brush Engine" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:19 msgid ".. image:: images/icons/deformbrush.svg" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:20 msgid "" "The Deform Brush is a brush that allows you to pull and push pixels around. " "It's quite similar to the :ref:`liquify_mode`, but where liquify has higher " "quality, the deform brush has the speed." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:24 msgid "Options" msgstr "Alternativ" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:26 msgid ":ref:`option_brush_tip`" msgstr ":ref:`option_brush_tip`" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:27 msgid ":ref:`option_deform`" msgstr ":ref:`option_deform`" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:28 msgid ":ref:`blending_modes`" msgstr ":ref:`blending_modes`" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:29 msgid ":ref:`option_opacity_n_flow`" msgstr ":ref:`option_opacity_n_flow`" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:30 msgid ":ref:`option_size`" msgstr ":ref:`option_size`" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:31 msgid ":ref:`option_rotation`" msgstr ":ref:`option_rotation`" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:32 msgid ":ref:`option_airbrush`" msgstr ":ref:`option_airbrush`" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:38 msgid "Deform Options" msgstr "Förvrängningsalternativ" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:42 msgid ".. image:: images/en/Krita_deform_brush_examples.png" msgstr ".. image:: images/en/Krita_deform_brush_examples.png" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:42 msgid "" "1: undeformed, 2: Move, 3: Grow, 4: Shrink, 5: Swirl Counter Clock Wise, 6: " "Swirl Clockwise, 7: Lens Zoom In, 8: Lens Zoom Out" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:44 msgid "These decide what strangeness may happen underneath your brush cursor." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:46 msgid "Grow" msgstr "Öka" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:47 msgid "This bubbles up the area underneath the brush-cursor." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:48 msgid "Shrink" msgstr "Minska" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:49 msgid "This pinches the Area underneath the brush-cursor." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:50 msgid "Swirl Counter Clock Wise" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:51 msgid "Swirls the area counter clock wise." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:52 msgid "Swirl Clock Wise" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:53 msgid "Swirls the area clockwise." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:54 msgid "Move" msgstr "Flytta" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:55 msgid "Nudges the area to the painting direction." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:56 msgid "Color Deformation" msgstr "Färgförvrängning" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:57 -msgid "This seems to randomly rearrange the pixels underneath the brush," +msgid "This seems to randomly rearrange the pixels underneath the brush." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:58 msgid "Lens Zoom In" msgstr "Inzoomning av lins" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:59 msgid "Literally paints a enlarged version of the area." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:61 msgid "Lens Zoom Out" msgstr "Utzoomning av lins" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:61 msgid "Paints a minimized version of the area." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:65 msgid ".. image:: images/en/Krita_deform_brush_colordeform.png" msgstr ".. image:: images/en/Krita_deform_brush_colordeform.png" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:65 msgid "Showing color deform." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:68 msgid "Deform Amount" msgstr "Förvrängningsvärde" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:68 msgid "Defines the strength of the deformation." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:72 msgid ".. image:: images/en/Krita_deform_brush_bilinear.png" msgstr ".. image:: images/en/Krita_deform_brush_bilinear.png" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:72 #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:74 msgid "Bilinear Interpolation" msgstr "Bilinjär interpolering" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:75 msgid "Smoothens the result. This causes calculation errors in 16bit." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:77 msgid "Use Counter" msgstr "Använd räknare" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:77 msgid "Slows down the deformation subtlety." msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:81 msgid ".. image:: images/en/Krita_deform_brush_useundeformed.png" msgstr ".. image:: images/en/Krita_deform_brush_useundeformed.png" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:81 msgid "Without 'use undeformed' to the left and with to the right" msgstr "" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:84 msgid "" "Samples from the previous version of the image instead of the current. This " "works better with some deform options than others. Move for example seems to " "almost stop working, but it works really well with Grow." msgstr "" diff --git a/locale/sv/LC_MESSAGES/reference_manual/layers_and_masks/layer_styles.po b/locale/sv/LC_MESSAGES/reference_manual/layers_and_masks/layer_styles.po index 5c7f62b46..3181aa340 100644 --- a/locale/sv/LC_MESSAGES/reference_manual/layers_and_masks/layer_styles.po +++ b/locale/sv/LC_MESSAGES/reference_manual/layers_and_masks/layer_styles.po @@ -1,64 +1,68 @@ # 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-02-19 03:36+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-02-24 08:59+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" #: ../../reference_manual/layers_and_masks/layer_styles.rst:1 msgid "How to use layer styles in Krita." msgstr "Hur lagerstilar används i Krita." #: ../../reference_manual/layers_and_masks/layer_styles.rst:17 msgid "Layer Styles" msgstr "Lagerstilar" #: ../../reference_manual/layers_and_masks/layer_styles.rst:19 msgid "" "Layer styles are effects that are added on top of your layer. They are " "editable and can easily be toggled on and off. To add a layer style to a " "layer go to :menuselection:`Layer --> Layer Style`. You can also right-click " "a layer to access the layer styles." msgstr "" "Lagerstilar är effekter som läggs till ovanpå ett lager. De är redigerbara " "och kan enkelt sättas på eller stängas av. Gå till :menuselection:`Layer --> " "Layer Style` för att lägga till en lagerstil. Det går också att högerklicka " "på ett lager för att komma åt lagerstilarna." #: ../../reference_manual/layers_and_masks/layer_styles.rst:22 +#, fuzzy +#| msgid "" +#| "When you have the layer styles window up, make sure that the \"Enable " +#| "Effects\" is checked." msgid "" -"When you have the layer styles window up, make sure that the \"Enable Effects" -"\" is checked." +"When you have the layer styles window up, make sure that the :guilabel:" +"`Enable Effects` item is checked." msgstr "" "När fönstret med lagerstilar visas, säkerställ att \"Aktivera effekter\" är " "markerat." #: ../../reference_manual/layers_and_masks/layer_styles.rst:24 msgid "" "There are a variety of effects and styles you can apply to a layer. When you " "add a style, your layer docker will show an extra \"Fx\" icon. This allows " "you to toggle the layer style effects on and off." msgstr "" "Det finns en mängd olika effekter och stilar som man kan använda på ett " "lager. När en stil läggs till, visar lagerpanelen en extra \"Fx\" ikon. Det " "gör det möjligt att sätta på eller stänga av lagerstileffekterna." #: ../../reference_manual/layers_and_masks/layer_styles.rst:30 msgid "" "This feature was added to increase support for :program:`Adobe Photoshop`. " "The features that are included mirror what that application supports." msgstr "" "Funktionen har lagts till för att öka stöd för :program:`Adobe Photoshop`. " "Funktionerna som är inkluderade speglar vad det programmet stödjer." diff --git a/locale/sv/LC_MESSAGES/tutorials/flat-coloring.po b/locale/sv/LC_MESSAGES/tutorials/flat-coloring.po index 630c660b7..3d324e4cf 100644 --- a/locale/sv/LC_MESSAGES/tutorials/flat-coloring.po +++ b/locale/sv/LC_MESSAGES/tutorials/flat-coloring.po @@ -1,767 +1,767 @@ # 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-03-12 03:34+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-03-10 11:19+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" +#: ../../tutorials/flat-coloring.rst:0 +msgid "" +".. image:: images/en/flat-coloring/Krita_filling_lineart_selection_1.png" +msgstr "" + +#: ../../tutorials/flat-coloring.rst:0 +msgid "" +".. image:: images/en/flat-coloring/Krita_filling_lineart_selection_2.png" +msgstr "" + +#: ../../tutorials/flat-coloring.rst:0 +msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_1.png" +msgstr "" + +#: ../../tutorials/flat-coloring.rst:0 +msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_2.png" +msgstr "" + +#: ../../tutorials/flat-coloring.rst:0 +msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_3.png" +msgstr "" + #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart14.png\n" " :alt: layer structure for flatting in krita" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart1.png\n" " :alt: blend mode setup of lineart flat coloring" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart2.png\n" " :alt: effects of multiply blend mode" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/icons/fill_tool.svg\n" " :alt: fill-tool icon" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart7.png\n" " :alt: colors filled with fill tool" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart15.png\n" " :alt: selecting with selection tools for filling color" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart16.png\n" " :alt: selection mask in Krita" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart17.png\n" " :alt: filling color in selection" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart18.png\n" " :alt: result of coloring made with the help of selection tools" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart8.png\n" " :alt: filling color in lineart using path tool" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart9.png\n" " :alt: erasing with path tool" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart10.png\n" " :alt: coloring with colorise mask" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart11.png\n" " :alt: result from the colorise mask" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart12.png\n" " :alt: slitting colors into islands" msgstr "" #: ../../tutorials/flat-coloring.rst:None msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart13.png\n" " :alt: resulting color islands from split layers" msgstr "" -#: ../../tutorials/flat-coloring.rst:0 -msgid "" -".. image:: images/en/flat-coloring/Krita_filling_lineart_selection_1.png" -msgstr "" - -#: ../../tutorials/flat-coloring.rst:0 -msgid "" -".. image:: images/en/flat-coloring/Krita_filling_lineart_selection_2.png" -msgstr "" - -#: ../../tutorials/flat-coloring.rst:0 -msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_1.png" -msgstr "" - -#: ../../tutorials/flat-coloring.rst:0 -msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_2.png" -msgstr "" - -#: ../../tutorials/flat-coloring.rst:0 -msgid ".. image:: images/en/flat-coloring/Krita_filling_lineart_mask_3.png" -msgstr "" - #: ../../tutorials/flat-coloring.rst:1 msgid "Common workflows used in Krita" msgstr "Vanliga arbetsflöden som används i Krita" #: ../../tutorials/flat-coloring.rst:13 msgid "Flat Coloring" msgstr "" #: ../../tutorials/flat-coloring.rst:15 msgid "" "So you've got a cool black on white drawing, and now you want to color it! " "The thing we’ll aim for in this tutorial is to get your lineart colored in " "with flat colors. So no shading just yet. We’ll be going through some " "techniques for preparing the lineart, and we’ll be using the layer docker to " "put each colour on a separate layer, so we can easily access each colour " "when we add shading." msgstr "" #: ../../tutorials/flat-coloring.rst:17 msgid "" "This tutorial is adapted from this `tutorial `_ by " "the original author." msgstr "" #: ../../tutorials/flat-coloring.rst:20 msgid "Understanding Layers" msgstr "Förstå lager" #: ../../tutorials/flat-coloring.rst:22 msgid "" "To fill lineart comfortably, it's best to take advantage of the layerstack. " "The layer stack is pretty awesome, and it's one of those features that make " "digital art super-convenient." msgstr "" #: ../../tutorials/flat-coloring.rst:24 msgid "" "In traditional art, it is not uncommon to first draw the full background " "before drawing the subject. Or to first draw a line art and then colour it " "in. Computers have a similar way of working." msgstr "" #: ../../tutorials/flat-coloring.rst:26 msgid "" "In programming, if you tell a computer to draw a red circle, and then " "afterwards tell it to draw a smaller yellow circle, you will see the small " "yellow circle overlap the red circle. Switch the commands around, and you " "will not see the yellow circle at all: it was drawn before the red circle " "and thus ‘behind’ it." msgstr "" #: ../../tutorials/flat-coloring.rst:28 msgid "" "This is referred to as the “drawing order”. So like the traditional artist, " "the computer will first draw the images that are behind everything, and " "layer the subject and foreground on top of it. The layer docker is a way for " "you to control the drawing order of multiple images, so for example, you can " "have your lineart drawn later than your colors, meaning that the lines will " "be drawn over the colors, making it easier to make it neat!" msgstr "" #: ../../tutorials/flat-coloring.rst:30 msgid "" "Other things that a layer stack can do are blending the colors of different " "layers differently with blending modes, using a filter in the layer stack, " "or using a mask that allows you to make parts transparent." msgstr "" #: ../../tutorials/flat-coloring.rst:32 msgid "" "Programmers talk about transparency as ''Alpha'', which is because the 'a' " "symbol is used to present transparency in the algorithms for painting one " "color on top of another. Usually when you see the word ''Alpha'' in a " "graphics program, just think of it as affecting the transparency." msgstr "" #: ../../tutorials/flat-coloring.rst:35 msgid "Preparing your line-art" msgstr "" #: ../../tutorials/flat-coloring.rst:37 msgid "" "Put the new layer underneath the layer containing the lineart (drag and drop " "or use the up/down arrows for that), and draw on it." msgstr "" #: ../../tutorials/flat-coloring.rst:42 msgid "" "…And notice nothing happening. This is because the white isn’t transparent. " "You wouldn’t really want it to either, how else would you make convincing " "highlights? So what we first need to do to colour in our drawing is prepare " "our lineart. There’s several methods of doing so, each with varying " "qualities." msgstr "" #: ../../tutorials/flat-coloring.rst:45 msgid "The Multiply Blending Mode" msgstr "" #: ../../tutorials/flat-coloring.rst:47 msgid "" "So, typically, to get a black and white lineart usable for colouring, you " "can set the blending mode of the lineart layer to Multiply. You do this by " "selecting the layer and going to the drop down that says **Normal** and " "setting that to **Multiply**." msgstr "" #: ../../tutorials/flat-coloring.rst:52 msgid "And then you should be able to see your colors!" msgstr "" #: ../../tutorials/flat-coloring.rst:54 msgid "" "Multiply is not a perfect solution however. For example, if through some " "image editing magic I make the lineart blue, it results into this:" msgstr "" #: ../../tutorials/flat-coloring.rst:59 msgid "" "This is because multiply literally multiplies the colors. So it uses maths!" msgstr "" #: ../../tutorials/flat-coloring.rst:61 msgid "" "What it first does is take the values of the RGB channels, then divides them " "by the max (because we're in 8bit, this is 255), a process we call " "normalising. Then it multiplies the normalised values. Finally, it takes the " "result and multiplies it with 255 again to get the result values." msgstr "" #: ../../tutorials/flat-coloring.rst:67 msgid "Pink" msgstr "" #: ../../tutorials/flat-coloring.rst:68 msgid "Pink (normalised)" msgstr "" #: ../../tutorials/flat-coloring.rst:69 ../../tutorials/flat-coloring.rst:87 msgid "Blue" msgstr "" #: ../../tutorials/flat-coloring.rst:70 msgid "Blue (normalised)" msgstr "" #: ../../tutorials/flat-coloring.rst:71 msgid "Normalised, multiplied" msgstr "" #: ../../tutorials/flat-coloring.rst:72 msgid "Result" msgstr "Resultat" #: ../../tutorials/flat-coloring.rst:73 msgid "Red" msgstr "Röd" #: ../../tutorials/flat-coloring.rst:74 msgid "222" msgstr "222" #: ../../tutorials/flat-coloring.rst:75 msgid "0.8705" msgstr "0,8705" #: ../../tutorials/flat-coloring.rst:76 msgid "92" msgstr "92" #: ../../tutorials/flat-coloring.rst:77 msgid "0.3607" msgstr "0,3607" #: ../../tutorials/flat-coloring.rst:78 msgid "0.3139" msgstr "0,3139" #: ../../tutorials/flat-coloring.rst:79 msgid "80" msgstr "80" #: ../../tutorials/flat-coloring.rst:80 msgid "Green" msgstr "Grön" #: ../../tutorials/flat-coloring.rst:81 msgid "144" msgstr "144" #: ../../tutorials/flat-coloring.rst:82 msgid "0.5647" msgstr "0,5647" #: ../../tutorials/flat-coloring.rst:83 msgid "176" msgstr "176" #: ../../tutorials/flat-coloring.rst:84 msgid "0.6902" msgstr "0,6902" #: ../../tutorials/flat-coloring.rst:85 msgid "0.3897" msgstr "0,3897" #: ../../tutorials/flat-coloring.rst:86 msgid "99" msgstr "99" #: ../../tutorials/flat-coloring.rst:88 msgid "123" msgstr "123" #: ../../tutorials/flat-coloring.rst:89 msgid "0.4823" msgstr "0,4823" #: ../../tutorials/flat-coloring.rst:90 msgid "215" msgstr "215" #: ../../tutorials/flat-coloring.rst:91 msgid "0.8431" msgstr "0,8431" #: ../../tutorials/flat-coloring.rst:92 msgid "0.4066" msgstr "0,4066" #: ../../tutorials/flat-coloring.rst:93 msgid "103" msgstr "103" #: ../../tutorials/flat-coloring.rst:95 msgid "" "This isn't completely undesirable, and a lot of artists use this effect to " "add a little richness to their colors." msgstr "" #: ../../tutorials/flat-coloring.rst:98 ../../tutorials/flat-coloring.rst:127 #: ../../tutorials/flat-coloring.rst:154 ../../tutorials/flat-coloring.rst:173 #: ../../tutorials/flat-coloring.rst:210 ../../tutorials/flat-coloring.rst:247 #: ../../tutorials/flat-coloring.rst:275 ../../tutorials/flat-coloring.rst:317 msgid "Advantages" msgstr "Fördelar" #: ../../tutorials/flat-coloring.rst:100 msgid "" "Easy, can work to your benefit even with coloured lines by softening the " "look of the lines while keeping nice contrast." msgstr "" #: ../../tutorials/flat-coloring.rst:103 ../../tutorials/flat-coloring.rst:132 #: ../../tutorials/flat-coloring.rst:159 ../../tutorials/flat-coloring.rst:178 #: ../../tutorials/flat-coloring.rst:215 ../../tutorials/flat-coloring.rst:252 #: ../../tutorials/flat-coloring.rst:280 ../../tutorials/flat-coloring.rst:322 msgid "Disadvantages" msgstr "Nackdelar" #: ../../tutorials/flat-coloring.rst:105 msgid "Not actually transparent. Is a little funny with coloured lines." msgstr "" #: ../../tutorials/flat-coloring.rst:108 msgid "Using Selections" msgstr "Använda markeringar" #: ../../tutorials/flat-coloring.rst:110 msgid "" "The second method is one where we'll make it actually transparent. In other " "programs this would be done via the channel docker, but Krita doesn't do " "custom channels, instead it uses Selection Masks to store custom selections." msgstr "" #: ../../tutorials/flat-coloring.rst:112 msgid "duplicate your lineart layer." msgstr "" #: ../../tutorials/flat-coloring.rst:114 msgid "" "convert the duplicate to a selection mask. |mouseright| the layer, then :" "menuselection:`Convert --> to Selection Mask`." msgstr "" #: ../../tutorials/flat-coloring.rst:118 msgid "" "Invert the selection mask. :menuselection:`Select --> Invert Selection`." msgstr "" #: ../../tutorials/flat-coloring.rst:120 msgid "" "Make a new layer, and do :menuselection:`Edit --> Fill with foreground " "color`." msgstr "" #: ../../tutorials/flat-coloring.rst:124 msgid "And you should now have the line art on a separate layer." msgstr "" #: ../../tutorials/flat-coloring.rst:129 msgid "Actual transparency." msgstr "" #: ../../tutorials/flat-coloring.rst:134 msgid "Doesn't work when the lineart is coloured." msgstr "" #: ../../tutorials/flat-coloring.rst:137 msgid "Using Masks" msgstr "Använda masker" #: ../../tutorials/flat-coloring.rst:139 msgid "This is a simpler variation of the above." msgstr "" #: ../../tutorials/flat-coloring.rst:141 msgid "Make a filled layer underneath the lineart layer." msgstr "" #: ../../tutorials/flat-coloring.rst:145 msgid "" "Convert the lineart layer to a transparency mask |mouseright| the layer, " "then :menuselection:`Convert --> to Transparency Mask`." msgstr "" #: ../../tutorials/flat-coloring.rst:149 msgid "" "Invert the transparency mask by going to :menuselection:`Filter --> Adjust --" "> Invert`" msgstr "" #: ../../tutorials/flat-coloring.rst:156 msgid "" "Actual transparency. You can also very easily doodle a pattern on the filled " "layer where the mask is on without affecting the transparency." msgstr "" #: ../../tutorials/flat-coloring.rst:161 msgid "" "Doesn't work when the lineart is coloured already. We can still get faster." msgstr "" #: ../../tutorials/flat-coloring.rst:164 msgid "Using Color to Alpha" msgstr "" #: ../../tutorials/flat-coloring.rst:166 msgid "By far the fastest way to get transparent lineart." msgstr "" #: ../../tutorials/flat-coloring.rst:168 msgid "" "Select the line art layer and apply the color to alpha filter. :" "menuselection:`Filter --> Colors --> Color to Alpha`. The default values " "should be sufficient for lineart." msgstr "" #: ../../tutorials/flat-coloring.rst:171 msgid "" ".. image:: images/en/flat-coloring/Krita_filling_lineart_color_to_alpha.png" msgstr "" ".. image:: images/en/flat-coloring/Krita_filling_lineart_color_to_alpha.png" #: ../../tutorials/flat-coloring.rst:175 msgid "" "Actual transparency. Works with coloured line art as well, because it " "removes the white specifically." msgstr "" #: ../../tutorials/flat-coloring.rst:180 msgid "" "You'll have to lock the layer transparency or separate out the alpha via the " "right-click menu if you want to easily color it." msgstr "" #: ../../tutorials/flat-coloring.rst:184 msgid "Colouring the image" msgstr "Färglägga bilden" #: ../../tutorials/flat-coloring.rst:186 msgid "" "Much like preparing the line art, there's many different ways of colouring a " "layer." msgstr "" #: ../../tutorials/flat-coloring.rst:188 msgid "" "You could for example fill in everything by hand, but while that is very " "precise it also takes a lot of work. Let's take a look at the other options, " "shall we?" msgstr "" #: ../../tutorials/flat-coloring.rst:191 msgid "Fill Tool" msgstr "Fyllverktyg" #: ../../tutorials/flat-coloring.rst:196 msgid "" "In most cases the fill-tool can’t deal with the anti-aliasing (the soft edge " "in your lineart to make it more smooth when zoomed out) In Krita you have " "the grow-shrink option. Setting that to say… 2 expands the colour two pixels." msgstr "" #: ../../tutorials/flat-coloring.rst:198 msgid "" "Threshold decides when the fill-tool should consider a different colour " "pixel to be a border. And the feathering adds a extra soft border to the " "fill." msgstr "" #: ../../tutorials/flat-coloring.rst:200 msgid "" "Now, if you click on a gapless-part of the image with your preferred colour…" "(Remember to set the opacity to 1.0!)" msgstr "" #: ../../tutorials/flat-coloring.rst:202 msgid "" "Depending on your lineart, you can do flats pretty quickly. But setting the " "threshold low can result in little artifacts around where lines meet:" msgstr "" #: ../../tutorials/flat-coloring.rst:207 msgid "" "However, setting the threshold high can end with the fill not recognising " "some of the lighter lines. Besides these little artifacts can be removed " "with the brush easily." msgstr "" #: ../../tutorials/flat-coloring.rst:212 msgid "Pretty darn quick depending on the available settings." msgstr "" #: ../../tutorials/flat-coloring.rst:217 msgid "" "Again, not great with gaps or details. And it works best with aliased line-" "art." msgstr "" #: ../../tutorials/flat-coloring.rst:220 msgid "Selections" msgstr "Markeringar" #: ../../tutorials/flat-coloring.rst:222 msgid "Selections work using the selection tools." msgstr "" #: ../../tutorials/flat-coloring.rst:227 msgid "" "For example with the :ref:`bezier_curve_selection_tool` you can easily " "select a curved area, and the with :kbd:`Shift` + |mouseleft| (not |" "mouseleft| + :kbd:`Shift`, there's a difference!) you can easily add to an " "existing selection." msgstr "" #: ../../tutorials/flat-coloring.rst:232 msgid "" "You can also edit the selection if you have :menuselection:`Select --> Show " "Global Selection Mask` turned on. Then you can select the global selection " "mask, and paint on it. (Above with the alternative selection mode, activated " "in the lower-left corner of the stats bar)" msgstr "" #: ../../tutorials/flat-coloring.rst:234 msgid "" "When done, select the color you want to fill it with and press :kbd:`Shift` " "+ `backspace`." msgstr "" #: ../../tutorials/flat-coloring.rst:239 msgid "" "You can save selections in selection masks by |mouseright| a layer, and then " "going to :menuselection:`Add --> Local Selection`. You first need to " "deactivate a selection by pressing the circle before adding a new selection." msgstr "" #: ../../tutorials/flat-coloring.rst:241 msgid "" "This can serve as an alternative way to split out different parts of the " "image, which is good for more painterly pieces:" msgstr "" #: ../../tutorials/flat-coloring.rst:249 msgid "A bit more precise than filling." msgstr "" #: ../../tutorials/flat-coloring.rst:254 msgid "Previewing your color isn't as easy." msgstr "" #: ../../tutorials/flat-coloring.rst:257 msgid "Geometric tools" msgstr "Geometriska verktyg" #: ../../tutorials/flat-coloring.rst:259 msgid "" "So you have a tool for making rectangles or circles. And in the case of " "Krita, a tool for bezier curves. Select the path tool (|path tool|), and set " "the tool options to fill=foreground and outline=none. Make sure that your " "opacity is set to 1.00 (fully opaque)." msgstr "" #: ../../tutorials/flat-coloring.rst:262 msgid "" ".. image:: images/icons/bezier_curve.svg\n" " :alt: path tool" msgstr "" ".. image:: images/icons/bezier_curve.svg\n" " :alt: konturverktyg" #: ../../tutorials/flat-coloring.rst:264 msgid "" "By clicking and holding, you can influence how curvy a line draw with the " "path tool is going to be. Letting go of the mouse button confirms the " "action, and then you’re free to draw the next point." msgstr "" #: ../../tutorials/flat-coloring.rst:269 msgid "" "You can also erase with a geometric tool. Just press :kbd:`E` or the eraser " "button." msgstr "" #: ../../tutorials/flat-coloring.rst:277 msgid "" "Quicker than using the brush or selections. Also decent with lineart that " "contains gaps." msgstr "" #: ../../tutorials/flat-coloring.rst:282 msgid "" "Fiddly details aren’t easy to fill in with this. So I recommend skipping " "those and filling them in later with a brush." msgstr "" #: ../../tutorials/flat-coloring.rst:285 msgid "Colorize Mask" msgstr "Färgläggningsmask" #: ../../tutorials/flat-coloring.rst:287 msgid "" "So, this is a bit of an odd one. In the original tutorial, you'll see I'm " "suggesting using G'Mic, but that was a few years ago, and g'mic is a little " "unstable on windows. Therefore, the Krita developers have been attempting to " "make an internal tool doing the same." msgstr "" #: ../../tutorials/flat-coloring.rst:289 msgid "" "It is disabled in 3.1, but if you use 4.0 or later, it is in the toolbox. " "Check the Colorize Mask for more information." msgstr "" #: ../../tutorials/flat-coloring.rst:291 msgid "So it works like this:" msgstr "" #: ../../tutorials/flat-coloring.rst:293 msgid "Select the colorize mask tool." msgstr "" #: ../../tutorials/flat-coloring.rst:294 msgid "Tick the layer you're using." msgstr "" #: ../../tutorials/flat-coloring.rst:295 msgid "Paint the colors your want to use on the colorize mask" msgstr "" #: ../../tutorials/flat-coloring.rst:296 msgid "Click update to see the results:" msgstr "" #: ../../tutorials/flat-coloring.rst:301 msgid "" "When you are satisfied, |mouseright| the colorize mask, and go to :" "menuselection:`Convert --> Paint Layer`. This will turn the colorize mask to " "a generic paint layer. Then, you can fix the last issues by aking the " "lineart semi-transparent and painting the flaws away with a pixel art brush." msgstr "" #: ../../tutorials/flat-coloring.rst:306 msgid "" "Then, when you are done, split the layers via :menuselection:`Layers --> " "Split --> Split Layer`. There's a few options you can choose, but the " "following should be fine:" msgstr "" #: ../../tutorials/flat-coloring.rst:311 msgid "" "Finally, press **Ok** and you should get the following. Each color patch it " "on a different layer, named by the palette in the menu and alpha locked, so " "you can start painting right away!" msgstr "" #: ../../tutorials/flat-coloring.rst:319 msgid "" "Works with anti aliased lineart. Really quick to get the base work done. Can " "auto-close gaps." msgstr "" #: ../../tutorials/flat-coloring.rst:324 msgid "" "No anti aliasing of it’s own. You have to choose between getting details " "right or the gaps auto-closed." msgstr "" #: ../../tutorials/flat-coloring.rst:327 msgid "Conclusion" msgstr "Avslutning" #: ../../tutorials/flat-coloring.rst:329 msgid "" "I hope this has given you a good idea of how to fill in flats using the " "various techniques, as well as getting a hand of different Krita features. " "Remember that a good flat filled lineart is better than a badly shaded one, " "so keep practising to get the best out of these techniques!" msgstr "" diff --git a/locale/sv/LC_MESSAGES/user_manual/loading_saving_brushes.po b/locale/sv/LC_MESSAGES/user_manual/loading_saving_brushes.po index 45adf6950..ff45e9e90 100644 --- a/locale/sv/LC_MESSAGES/user_manual/loading_saving_brushes.po +++ b/locale/sv/LC_MESSAGES/user_manual/loading_saving_brushes.po @@ -1,945 +1,945 @@ # 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-03-12 03:34+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-03-03 17:15+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" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:17 msgid "Loading and Saving Brushes" msgstr "Läs in och spara penslar" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:37 msgid "The Brush settings dropdown" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:44 msgid "" "When you open Brush Settings Editor panel you will see something like this:" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:48 msgid "Tour of the brush settings dropdown" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:53 msgid "The brush settings drop down is divided into six areas," msgstr "" #: ../../user_manual/loading_saving_brushes.rst:56 msgid "Section A - General Information" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:79 msgid "Engine" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:94 msgid "Reloading" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:101 msgid "Saving a preset" msgstr "Spara en förinställning" #: ../../user_manual/loading_saving_brushes.rst:103 msgid "" "On the right, there's :guilabel:`Save New Brush Preset` and :guilabel:" "`Overwrite Brush`." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:108 msgid "Overwrite Brush" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:113 msgid "Save New Brush Preset" msgstr "Spara ny penselförinställning" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:125 msgid "Brush Name" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:127 msgid "Load Existing Thumbnail" msgstr "Läs in befintlig miniatyrbild" #: ../../user_manual/loading_saving_brushes.rst:128 msgid "This will load the existing thumbnail inside the preset." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:130 msgid "Load scratch pad thumbnail" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:132 msgid "Load Image" msgstr "Läs in bild" #: ../../user_manual/loading_saving_brushes.rst:133 msgid "With this you can choose an image from disk to load as a thumbnail." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:134 msgid "Load from Icon Library" msgstr "Läs in från ikonbibliotek" #: ../../user_manual/loading_saving_brushes.rst:135 msgid "This opens up the icon library." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:137 msgid "Clear Thumbnail" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:137 msgid "This will make the mini scratch pad white." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:140 msgid "The Icon Library" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:142 msgid "To make making presets icons faster, Krita got an icon library." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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, ad the lowest slider is a super simple levels filter. " +"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 "" #: ../../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." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:167 msgid "Section B - The Preset Chooser" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:169 msgid "" "The preset chooser is much the same as the preset docker and the preset " "dropdown 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 "" #: ../../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 "" #: ../../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 "" #: ../../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 for that " -"engine." +"list of Krita's engines. Selecting an engine from the list will show the " +"brushes for that engine." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:185 msgid "" -"The trashcan icon does the same as it does in the preset docker: delete , or " +"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 "" #: ../../user_manual/loading_saving_brushes.rst:189 msgid "Section C - The Scratch pad" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:202 msgid "The scratch pad has five buttons underneath it. These are in order for:" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:204 msgid "Showing the current brush image" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:206 msgid "Adding a gradient to the scratch pad (useful for smudge brushes)" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:207 msgid "Filling with the background color" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:208 msgid "Clearing everything on the scratch pad." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:211 msgid "Section D - The Options List" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:227 msgid "Section E - Option Configuration Widget" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:233 msgid "Using sensor curves" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:260 msgid "Underneath the curve widget there are two more options:" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:264 msgid "Share Curves across all settings" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:271 msgid "Multiply" msgstr "Multiplicera" #: ../../user_manual/loading_saving_brushes.rst:272 msgid "Will multiply the two values, 0.5\\*0.7 = 0.35" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:274 msgid "Addition" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:277 msgid "Maximum" msgstr "Maximum" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:280 msgid "Minimum" msgstr "Minimum" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:283 msgid "Will subtract the smallest value from the largest, so 0.7-0.5 = 0.2" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:284 msgid "Curves Calculation Mode" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:284 msgid "Difference" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:286 msgid "It's maybe better to see with the following example:" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:292 msgid "Is a brush with size set to the distance sensor." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:293 msgid "Is a brush with the size set to the fade sensor." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:294 msgid "The size is calculated from the fade and distance sensors multiplied." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:297 msgid "" "The size takes the maximum value from the values of the fade and distance " "sensors." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:299 msgid "" -"The size takes the minimum value from the values of the face and distance " +"The size takes the minimum value from the values of the fade and distance " "sensors." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:305 msgid "Section F - Miscellaneous options" msgstr "" #: ../../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, the revert to default. " "Dirtied presets can be recognized by the icon in the top-left of the preset." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:316 msgid "Temporarily Save Tweaks to Preset (Dirty Presets)" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:319 msgid "Eraser Switch Size" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:319 msgid "" "This switches the brush to a separately stored size when using the :kbd:`E` " "key." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:321 msgid "Eraser Switch Opacity" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:322 msgid "Same as above, but then with Eraser opacity." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:330 msgid "Instant Preview" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:333 msgid "The On-canvas brush settings" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:347 msgid "Making a Brush Preset" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:349 msgid "Now, let's make a simple brush to test the waters with:" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:352 msgid "Getting a default for the brush engine." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:354 msgid "First, open the settings with :kbd:`F5`." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:361 msgid "Example: Making an inking brush" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:370 -msgid "Uncheck the :guilabel:`enable pen settings` checkbox." +msgid "Uncheck the :guilabel:`Enable Pen Settings` checkbox." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:377 msgid "" -"Uncheck the :guilabel:`enable pen settings` checkbox here as well. Test " +"Uncheck the :guilabel:`Enable Pen Settings` checkbox here as well. Test " "again." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:401 msgid "Saving the new Brush" msgstr "Spara den nya penseln" #: ../../user_manual/loading_saving_brushes.rst:403 msgid "" "When you're satisfied, go to the upper left and select :guilabel::`Save new " "preset`." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:414 msgid "Finally press :guilabel:`Save`, and your brush should be done." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:416 msgid "You can further modify your inking brush by..." msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:422 msgid "Making the fine lines look even softer by using the flow option." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:422 msgid "" "To do this, select the flow option, and turn back on the 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 "" #: ../../user_manual/loading_saving_brushes.rst:425 msgid "Sharing Brushes" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:438 msgid "Sharing a single preset" msgstr "" #: ../../user_manual/loading_saving_brushes.rst:440 msgid "There are three types of resources a single preset can take:" msgstr "" #: ../../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 "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:446 msgid "A Pattern file: this is when you are using textures." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:452 msgid "" "To find those resources, go to :menuselection:`Settings --> Manage Resources " "--> Open Resource Folder`." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:458 msgid "Importing a single KPP file." msgstr "" #: ../../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 "" #: ../../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 " "dropdown (: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 "" #: ../../user_manual/loading_saving_brushes.rst:471 msgid "Sharing via ZIP (old-fashioned)" msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:477 msgid "Using a ZIP with the relevant files." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:479 msgid "" "Go to :menuselection:`Settings --> Manage Resources --> Open Resource " "Folder` to open the resource folder." msgstr "" #: ../../user_manual/loading_saving_brushes.rst:480 msgid "Then, open up the zip file." msgstr "" #: ../../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 "" #: ../../user_manual/loading_saving_brushes.rst:484 msgid "Restart Krita" msgstr "Starta om Krita" #: ../../user_manual/loading_saving_brushes.rst:485 msgid "Enjoy your brushes!" msgstr "" diff --git a/locale/sv/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po b/locale/sv/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po index 76c4f8d76..1aa6ac4a6 100644 --- a/locale/sv/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po +++ b/locale/sv/LC_MESSAGES/user_manual/python_scripting/introduction_to_python_scripting.po @@ -1,286 +1,286 @@ # 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-03-06 03:37+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-03-07 18:41+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" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:1 msgid "Introduction to using Krita's python plugin API." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:18 msgid "Introduction to Python Scripting" msgstr "Introduktion till Python-skript" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:22 msgid "" "When we offered python scripting as one of Kickstarter Stretchgoals we could " "implement next to vectors and text, it won the backer vote by a landslide. " "Some people even only picked python and nothing else. So what exactly is " "python scripting?" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:25 msgid "What is Python Scripting?" msgstr "Vad är Python-skript?" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:27 msgid "" "Python is a scripting language, that can be used to automate tasks. What " "python scripting in Krita means is that we added an API to krita, which is a " "bit of programming that allows python to access to parts of Krita. With this " "we can make dockers, perform menial tasks on a lot of different files and " "even write our own exporters. People who work with computer graphics, like " "VFX and video game artists use python a lot to make things like sprite " "sheets, automate parts of export and more." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:29 msgid "" "It is outside the scope of this manual to teach you python itself. However, " "as python is an extremely popular programming language and great for " "beginners, there's tons of learning material around that can be quickly " "found with a simple 'learn python' internet search." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:31 msgid "" "This manual will instead focus on how to use python to automate and extend " "Krita. For that we'll first start with the basics: How to run Python " "commands in the scripter." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:35 msgid "How to Enable the Scripter Plugin" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:37 msgid "" "The scripter plugin is not necessary to use python, but it is very useful " "for testing and playing around with python. It is a python console, written " "in python, which can be used to write small scripts and execute them on the " "fly." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:39 msgid "" "To open the scripter, navigate to :menuselection:`Tools --> Scripts --> " "Scripter`. If you don't see it listed, go to :menuselection:`Settings --> " "Configure Krita --> Python Plugin Manager` and toggle \"Scripter\" in the " "list to enable it. If you don't see the scripter plugin, make sure you are " "using an up-to-date version of Krita." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:41 msgid "" "The scripter will pop up with a text editor window on top and an output " "window below. Input the following in the text area:" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:48 msgid "" "Press the big play button or press :kbd:`Ctrl + R` to run the script. Then, " "below, in the output area the following should show up::" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:53 msgid "" "Now we have a console that can run functions like print() from the Python " "environment - but how do we use it to manage Krita?" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:56 msgid "Running basic Krita commands" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:58 msgid "" "To allow Python to communicate with Krita, we will use the Krita module. At " "the top of every script, we will write: ``from krita import *``" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:60 msgid "" "This allows us to talk to Krita through ``Krita.instance()``. Let's try to " "double our coding abilities with Python." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:68 msgid "" "You should see a second scripter window open. Pretty neat! Here is a " "slightly more advanced example." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:77 msgid "" "This will open up a new document. Clearly Python gives you quite a lot of " "control to automate Krita. Over time we expect the community to write all " "kinds of scripts that you can use simply by pasting them in the scripter." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:79 msgid "" "But what if you want to write new commands for yourself? The best place to " "start is very simple: search for examples written by other people! You can " "save a lot of time if someone else has written code that you can base your " "work on. It's also worth looking through the python plugins, which are " "located in /share/krita/pykrita. There's also a step by step guide for :ref:" "`krita_python_plugin_howto` here in the manual." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:81 msgid "" "But it's likely that you need more information. For that, we will need see " "what's hidden behind the asterisk when you ``import * from Krita``. To learn " "what Krita functions that are available and how to use them, you will want " "to go for Krita API reference documentation." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:84 msgid "Krita's API" msgstr "Kritas programmeringsgränssnitt" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:86 msgid "" "`LibKis API Overview `_" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:87 msgid "" "`Krita class documentation `_" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:89 msgid "" "Those pages may look like a lot of jargon at first. This is because Krita's " "API documentation comes from the underlying C++ language that Krita is " "written in. The magic happens because of a Python tool called SIP, which " "makes it possible for python speak in C++ and talk to Krita. The end result " "is that when we ``import krita`` and call functions, we're actually using " "the C++ methods listed in that documentation." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:91 msgid "" "Let's see how this stuff works in more detail. Let's take a look at the " "second link, the `Krita class reference `_. There we can see all the " "functions available to the Krita instance. If you type dir(Krita.instance()) " "in Python, it should match this page very closely - you can view the " "documentation of the functions createDocument(), activeWindow(), and " "action() which we used above." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:93 msgid "" "One of the more confusing things is seeing all the C++ classes that Krita " -"uses, including the Qt classes that start with Q. But here is the beauty fo " +"uses, including the Qt classes that start with Q. But here is the beauty of " "SIP: it tries to make the translation from these classes into Python as " "simple and straightforward as possible. For example, you can see that the " "function filters() returns a QStringList. However, SIP converts those " "QStringLists into regular python list of strings!" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:101 msgid "Outputs as ::" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:112 msgid "However, sometimes the conversion doesn't go quite as smoothly." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:120 msgid "gives something like this::" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:127 msgid "" "It is a list of something, sure, but how to use it? If we go back to the " "Krita apidocs page and look at the function, documents() we'll see there's " "actually a clickable link on the 'Document' class. `If you follow that link " "`_, you'll see that the document has a function called " "name() which returns the name of the document, and functions width() and " "height() which return the dimensions. So if we wanted to generate an info " "report about the documents in Krita, we could write a script like this:" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:137 msgid "we get an output like::" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:147 msgid "" "Hopefully this will give you an idea of how to navigate the API docs now." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:149 msgid "" "Krita's API has many more classes, you can get to them by going to the top-" "left class list, or just clicking their names to get to their API docs. The " "functions print() or dir() are your friends here as well. This line will " "print out a list of all the actions in Krita - you could swap in one of " "these commands instead of 'python_scripter' in the example above." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:155 msgid "" "The Python module ``inspect`` was designed for this sort of task. Here's a " "useful function to print info about a class to the console." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:167 msgid "" "Finally, in addition to the LibKis documentation, the Qt documentation, " "since Krita uses PyQt to expose nearly all of the Qt API to Python. You can " "build entire windows with buttons and forms this way, using the very same " "tools that Krita is using! You can read the `Qt documentation `_ and the `PyQt documentation `_ for more info about this, and also definitely study the included plugins " "as well to see how they work." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:171 msgid "Technical Details" msgstr "Teknisk detaljinformation" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:177 msgid "Python Scripting on Windows" msgstr "Python-skript på Windows" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:179 msgid "" "To get Python scripting working on Windows 7/8/8.1, you will need to install " "the `Universal C Runtime from Microsoft's website `_. (Windows 10 already comes with it.)" msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:182 msgid "Python 2 and 3" msgstr "Python 2 och 3" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:184 msgid "By default Krita is compiled for python 3." msgstr "" #: ../../user_manual/python_scripting/introduction_to_python_scripting.rst:186 msgid "" "However, it is possible to compile it with python 2. To do so, you will need " "to add the following to the cmake configuration line::" msgstr "" diff --git a/locale/uk_UA/LC_MESSAGES/KritaFAQ.po b/locale/uk_UA/LC_MESSAGES/KritaFAQ.po index 1ddd2366a..146d89089 100644 --- a/locale/uk_UA/LC_MESSAGES/KritaFAQ.po +++ b/locale/uk_UA/LC_MESSAGES/KritaFAQ.po @@ -1,1521 +1,1514 @@ # Translation of docs_krita_org_KritaFAQ.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_KritaFAQ\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-03-13 03:40+0100\n" "PO-Revision-Date: 2019-03-13 08:00+0200\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" #: ../../KritaFAQ.rst:27 msgid "Krita FAQ" msgstr "Поширені питання щодо Krita" #: ../../KritaFAQ.rst:29 msgid "" "This page contains common problems people have with Krita. Note that we " "assume that you are using the latest version of Krita. Please verify that to " "make sure." msgstr "" "На цій сторінці зібрано питання щодо типових проблем, які виникають у " "користувачів Krita. Зауважте, що у відповідях ми припускаємо, що ви " "користуєтеся найсвіжішою версією Krita. Будь ласка, перевірте, чи це так." #: ../../KritaFAQ.rst:31 msgid "Contents" msgstr "Зміст" #: ../../KritaFAQ.rst:34 msgid "General" msgstr "Загальне" #: ../../KritaFAQ.rst:36 msgid "General questions" msgstr "Загальні питання" #: ../../KritaFAQ.rst:39 msgid "What is Krita?" msgstr "Для чого призначено Krita?" #: ../../KritaFAQ.rst:41 msgid "This is our vision for the development of Krita:" msgstr "Ось наше бачення щодо розробки Krita:" #: ../../KritaFAQ.rst:43 msgid "" "Krita is a free and open source cross-platform application that offers an " "end-to-end solution for creating digital art files from scratch. Krita is " "optimized for frequent, prolonged and focused use. Explicitly supported " "fields of painting are illustrations, concept art, matte painting, textures, " "comics and animations. Developed together with users, Krita is an " "application that supports their actual needs and workflow. Krita supports " "open standards and interoperates with other applications." msgstr "" "Krita — вільна програма із відкритим початковим кодом, яка є повноцінним " "рішенням для створення файлів цифрових художніх творів з нуля. Krita " "оптимізовано для частого, тривалого та сконцентрованого використання. Явним " "чином підтримуваними програмами різновидами використання є створення " "ілюстрацій, концепт-арту, матового малювання, текстур, коміксів та анімацій. " "Програму розроблено у співпраці із користувачами програми. Krita — програма " "зорієнтована на справжні потреби користувачів та процедури користування. У " "Krita передбачено підтримку відкритих стандартів та взаємодії із іншими " "програмами." #: ../../KritaFAQ.rst:48 msgid "Is it possible to use Krita in my own language, not English?" msgstr "" "Чи можна користуватися Krita із інтерфейсом моєю рідною мовою, не " "англійською?" #: ../../KritaFAQ.rst:50 msgid "" "Krita should automatically use the system language. If that is not the case, " "please follow these steps:" msgstr "" "Krita має автоматично використовувати основну мову системи. Якщо цього не " "відбулося, будь ласка, виконайте такі дії:" #: ../../KritaFAQ.rst:52 msgid "" ":menuselection:`Settings --> Switch Application Language`. A small window " "will appear." msgstr "" "Виберіть пункт меню :menuselection:`Параметри --> Перемкнути мову програми`. " "У відповідь буде відкрито невеличке вікно." #: ../../KritaFAQ.rst:53 msgid "Click :guilabel:`Primary language` and select your language." msgstr "Натисніть пункт :guilabel:`Основна мова` і виберіть потрібну вам мову." #: ../../KritaFAQ.rst:54 msgid "Click :guilabel:`OK` to close the window." msgstr "Натисніть :guilabel:`Гаразд`, щоб закрити вікно." #: ../../KritaFAQ.rst:55 msgid "Restart krita and it will be displayed in your selected language!" msgstr "" "Перезапустіть krita. Інтерфейс має бути перекладено вибраною вами мовою!" #: ../../KritaFAQ.rst:57 msgid "" "If this doesn't work, you might have to add a fall-back language as well. " "This is a bug, but we haven't found the solution yet." msgstr "" "Якщо це не спрацює, ймовірно, вам слід додати і резервну мову. Це вада у " "бібліотеках, які використовує програма. Нам ще не вдалося усунути цю ваду." #: ../../KritaFAQ.rst:60 msgid "Does Krita have layer clip or clipping mask?" msgstr "Чи передбачено у Krita обрізання шарів та маску обрізання?" #: ../../KritaFAQ.rst:62 msgid "" "Krita has no clipping mask, but it has a clipping feature called inherit " "alpha. Let's see :ref:`this page ` and " "learn how to do clipping in Krita!" msgstr "" "У Krita не передбачено маски обрізання, але є можливість обрізання, яка має " "назву «успадкування прозорості». Ознайомтеся із вмістом :ref:`цієї сторінки " "`, щоб дізнатися про те, як виконати " "обрізання зображення у Krita!" #: ../../KritaFAQ.rst:67 msgid "Windows: OBS can't record the Krita OpenGL canvas" msgstr "Windows: OBS не може записувати дані з полотна OpenGL Krita" #: ../../KritaFAQ.rst:69 msgid "The possible workarounds for this is to do either of the following:" msgstr "Проблему можна обійти за допомогою одного із викладних нижче способів." #: ../../KritaFAQ.rst:71 msgid "" "Turn off OpenGL in :menuselection:`Settings --> Configure Krita --> Display`." msgstr "" "Вимкніть OpenGL за допомогою пункту меню :menuselection:`Параметри --> " "Налаштувати Krita --> Монітор`." #: ../../KritaFAQ.rst:72 msgid "" "Or don't use the hardware accelerated mode (game recording mode) in OBS, " "thus capturing the whole desktop instead of attempting to capture only Krita." msgstr "" "Не використовуйте режим із апаратним прискоренням (режим запису ігор) у OBS, " "захоплюючи усе зображення на моніторі, а не лише зображення у вікні Krita." #: ../../KritaFAQ.rst:76 msgid "" "You might also be able to work around the problem by using the ANGLE " "renderer instead of native OpenGL." msgstr "" "Також проблему можна обійти за допомогою використання засобу обробки " "зображення ANGLE замість природного OpenGL." #: ../../KritaFAQ.rst:79 msgid "Where are the configuration files stored?" msgstr "Де зберігаються файли налаштувань програми?" #: ../../KritaFAQ.rst:81 msgid "" "These are stored at the following places for the following operating systems:" msgstr "Ці файли зберігаються у таких місцях у різних операційних системах:" #: ../../KritaFAQ.rst:84 ../../KritaFAQ.rst:100 ../../KritaFAQ.rst:124 #: ../../KritaFAQ.rst:251 ../../KritaFAQ.rst:371 msgid "Linux" msgstr "Linux" #: ../../KritaFAQ.rst:85 ../../KritaFAQ.rst:101 msgid ":file:`$HOME/.config/kritarc`" msgstr ":file:`$HOME/.config/kritarc`" #: ../../KritaFAQ.rst:86 ../../KritaFAQ.rst:102 ../../KritaFAQ.rst:126 #: ../../KritaFAQ.rst:271 ../../KritaFAQ.rst:373 msgid "Windows" msgstr "Windows" #: ../../KritaFAQ.rst:87 msgid ":file:`%APPDATA%\\\\Local\\\\kritarc`" msgstr ":file:`%APPDATA%\\\\Local\\\\kritarc`" #: ../../KritaFAQ.rst:89 ../../KritaFAQ.rst:105 msgid "MacOS X" msgstr "MacOS X" #: ../../KritaFAQ.rst:89 ../../KritaFAQ.rst:105 msgid ":file:`$HOME/Library/Preferences/kritarc`" msgstr ":file:`$HOME/Library/Preferences/kritarc`" #: ../../KritaFAQ.rst:91 msgid "" "The kritarc file is the configuration file. Krita does not store settings in " "the Windows registry." msgstr "" "Файл kritarc є файлом налаштувань. Krita не зберігає параметри роботи у " "реєстрі Windows." #: ../../KritaFAQ.rst:94 msgid "Resetting Krita configuration" msgstr "Відновлення початкових налаштувань Krita" #: ../../KritaFAQ.rst:96 msgid "You can reset the Krita configuration in following way:" msgstr "Відновити початкові налаштування Krita можна так:" #: ../../KritaFAQ.rst:98 msgid "For Krita 3.0 and later: Delete/rename the kritarc file, found here:" msgstr "" "Для Krita 3.0 і новіших версій: вилучити або перейменувати файл kritarc, " "який зберігається тут:" #: ../../KritaFAQ.rst:103 msgid ":file:`%LOCALAPPDATA%\\\\kritarc`" msgstr ":file:`%LOCALAPPDATA%\\\\kritarc`" #: ../../KritaFAQ.rst:107 msgid "" "There can be two other files you might want to remove: kritaopenglrc and " "kritadisplayrc." msgstr "" "Може бути іще два файли, які, ймовірно, варто вилучити: kritaopenglrc і " "kritadisplayrc." #: ../../KritaFAQ.rst:110 msgid "" "If the configuration was causing a crash, don't delete the mentioned file, " "but instead rename and send it to us in order for us to figure what caused " "the crash." msgstr "" "Якщо через помилкові налаштування програма завершує роботу в аварійному " "режимі, не вилучайте згаданий вище файл, а просто перейменуйте його і " "надішліть розробникам, щоб ті могли встановити причину аварійного завершення " "і усунути її." #: ../../KritaFAQ.rst:113 msgid "" "If you have installed Krita through the Windows store, the kritarc file will " "be in another location" msgstr "" " Якщо ви встановили Krita за допомогою крамниці програм Windows, файл " "kritarc зберігатиметься у іншому місці:" #: ../../KritaFAQ.rst:115 msgid "" ":file:`%LOCALAPPDATA%\\\\Packages\\\\49800Krita_{RANDOM STRING}\\\\LocalCache" "\\\\Local\\\\kritarc`" msgstr "" ":file:`%LOCALAPPDATA%\\\\Packages\\\\49800Krita_{ВИПАДКОВИЙ РЯДОК}\\" "\\LocalCache\\\\Local\\\\kritarc`" #: ../../KritaFAQ.rst:117 msgid "The random string depends on your installation." msgstr "Випадковий рядок залежить від параметрів встановленої системи." #: ../../KritaFAQ.rst:119 msgid "" "Windows users have a habit of uninstalling and reinstalling applications to " "solve problems. Unless the problem is that the installation was corrupted by " "a virus scanner or drive failure, that will NOT work. Uninstalling Krita " "then reinstalling replaces the bytes on your drive with exactly the same " "bytes that were there before. It doesn't reset anything, least of all " "Krita's settings." msgstr "" "У користувачів Windows є звичка вилучати і перевстановлювати програми для " "вирішення проблем. Якщо проблему не було спричинено пошкодженням файлів під " "час встановлення антивірусом або у результаті виходу з ладу диска, " "перевстановлення Krita не спрацює. Якщо ви вилучите Krita, а потім знову " "встановите її, байти на диску буде замінено тими самими байтами. Ніяких " "відновлень початкового стану — усі параметри роботи Krita лишаться тими " "самими." #: ../../KritaFAQ.rst:122 msgid "Where are my resources stored?" msgstr "Де зберігаються дані ваших ресурсів?" #: ../../KritaFAQ.rst:125 ../../KritaFAQ.rst:372 msgid ":file:`$HOME/.local/share/krita/`" msgstr ":file:`$HOME/.local/share/krita/`" #: ../../KritaFAQ.rst:127 msgid ":file:`%APPDATA%\\\\krita\\\\`" msgstr ":file:`%APPDATA%\\\\krita\\\\`" #: ../../KritaFAQ.rst:129 msgid "Mac OS X" msgstr "Mac OS X" #: ../../KritaFAQ.rst:129 ../../KritaFAQ.rst:376 msgid ":file:`~/Library/Application Support/Krita/`" msgstr ":file:`~/Library/Application Support/Krita/`" #: ../../KritaFAQ.rst:132 msgid "" "If you installed Krita in the Windows Store, your custom resources will be " "in a location like:" msgstr "" "Якщо ви встановили Krita з крамниці Windows, ваші нетипові ресурси " "зберігатимуться у теках із такими назвами:" #: ../../KritaFAQ.rst:132 msgid "" ":file:`%LOCALAPPDATA%\\\\Packages\\\\49800Krita_{RANDOM STRING}\\\\LocalCache" "\\Roaming\\krita`" msgstr "" ":file:`%LOCALAPPDATA%\\\\Packages\\\\49800Krita_{ВИПАДКОВИЙ РЯДОК}\\" "\\LocalCache\\Roaming\\krita`" #: ../../KritaFAQ.rst:135 msgid "" "Krita tells me it can't find some files and then closes, what should I do?" msgstr "" "Krita повідомляє, що не знайдено якихось файлів і завершує роботу. Що робити?" #: ../../KritaFAQ.rst:137 msgid "Causes for this could be the following:" msgstr "Причин може бути декілька:" #: ../../KritaFAQ.rst:139 msgid "" "It might be that your download got corrupted and is missing files (common " "with bad wifi and bad internet connection in general), in that case, try to " "find a better internet connection before trying to download again. Krita " "should be around 80 to 100 MB in size when downloading." msgstr "" "Може так статися, що отриманий вами пакунок було пошкоджено або у ньому не " "вистачає файлів (типовою причиною є неякісне з'єднання wifi та інтернет-" "з'єднання загалом). У цьому випадку спробуйте знайти якісніше інтернет-" "з'єднання, перш ніж повторювати спробу отримати пакунок. Завантажений " "пакунок Krita повинен мати розмір близько 80 або 100 МБ." #: ../../KritaFAQ.rst:140 msgid "" "It might be that something went wrong during installation. Check whether " "your harddrive is full and reinstall Krita with at least 120 MB of empty " "space. If not, and the problem still occurs, there might be something odd " "going on with your device and it's recommended to find a computer expert to " "diagnose what is the problem." msgstr "" "Може так статися, що щось відбулося не так під час встановлення. Перевірте, " "чи достатньо вільного місця на диску і перевстановіть Krita. Для " "встановлення потрібно принаймні 120 вільного місця. Якщо вільного місця " "достатньо, але належно встановити програму не вдається, можливо, маєте якісь " "проблеми з комп'ютером. Рекомендуємо порадитися із експертом для визначення " "причини проблеми." #: ../../KritaFAQ.rst:141 msgid "" "Some unzippers don't unpack our zipfiles correctly. The native ones on " "Windows, OSX and most Linux distributions should be just fine, and we " "recommend using them." msgstr "" "Деякі програми для розпаковування архівів zip можуть розпаковувати програму " "некоректно. Вбудовані засоби Windows, OSX та більшості дистрибутивів Linux " "мають працювати як слід. Рекомендуємо використовувати саме ці засоби для " "розпаковування." #: ../../KritaFAQ.rst:142 msgid "" "You manually, using a file manager deleted or moved resources around, and " "thus Krita cannot find them anymore." msgstr "" "Ви вручну, за допомогою програми для керування файлами, вилучити або " "пересунули ресурси, тому Krita не може їх знайти." #: ../../KritaFAQ.rst:145 msgid "What Graphics Cards does Krita support?" msgstr "Підтримку яких графічних карток передбачено у Krita?" #: ../../KritaFAQ.rst:147 msgid "" "Krita can use OpenGL to accelerate painting and canvas zooming, rotation and " "panning. Nvidia and recent Intel GPUs give the best results. Make sure your " "OpenGL drivers support OpenGL 3.2 as the minimum. AMD/ATI GPU’s are known to " "be troublesome, especially with the proprietary drivers on Linux. However, " "it works perfectly with the Radeon free driver on Linux for supported AMD " "GPU. Try to get a graphics card that can support OpenGL 3.2 or above for the " "best results, some examples:" msgstr "" "Krita може використовувати OpenGL для пришвидшення обробки малювання та " "масштабування, обертання та панорамування полотна. Найкраще це працює на " "Nvidia та нових графічних процесорах Intel. Переконайтеся, що у встановлених " "драйверах OpenGL передбачено підтримку принаймні OpenGL 3.2. Відомо, що " "можуть виникати проблеми із графічними процесорами AMD/ATI, особливо якщо ви " "користуєтеся пропрієтарними драйверами у Linux. Втім, все працює ідеально зі " "вільним драйвером Radeon у Linux для підтримуваних у ньому графічних " "процесорів AMD. Вам знадобиться графічна картка із підтримкою OpenGL 3.2 та " "новіших версій. Ось приклади таких карток:" #: ../../KritaFAQ.rst:151 msgid "Intel" msgstr "Intel" #: ../../KritaFAQ.rst:152 msgid "" "Intel 3rd Generation HD Graphics, IvyBridge or Bay-Trail microarchitecture, " "released in 2012. Commonly available products: Celeron J1x00, N2x00, Celeron " "(G)1xx0, Pentium J2x00, N3500, Pentium (G)2xx0, Core i3/5/7-3xx0." msgstr "" "HD-графіка Intel 3-го покоління, мікроархітектура IvyBridge або Bay-Trail, " "випущено у 2012 році. Типові продукти: Celeron J1x00, N2x00, Celeron " "(G)1xx0, Pentium J2x00, N3500, Pentium (G)2xx0, Core i3/5/7-3xx0." #: ../../KritaFAQ.rst:153 msgid "AMD/ATI" msgstr "AMD/ATI" #: ../../KritaFAQ.rst:154 msgid "" "Radeon HD 2000 family, TeraScale 1 microarchitecture, Released in 2007. " "Commonly available products: Radeon HD 2400 PRO, Radeon HD 2600 PRO, etc." msgstr "" "Сімейство Radeon HD 2000, мікроархітектура TeraScale 1, випущено у 2007 " "році. Типові продукти: Radeon HD 2400 PRO, Radeon HD 2600 PRO тощо." #: ../../KritaFAQ.rst:156 msgid "Nvidia" msgstr "Nvidia" #: ../../KritaFAQ.rst:156 msgid "" "GeForce 8 family, Tesla microarchitecture, released in 2006. Commonly " "available products: GeForce 8400 GS, GeForce 8800 GTS, 9800 GTX, GTS 250, " "etc." msgstr "" "Сімейство GeForce 8, мікроархітектура Tesla, випущено у 2006 році. Типові " "продукти: GeForce 8400 GS, GeForce 8800 GTS, 9800 GTX, GTS 250 тощо." #: ../../KritaFAQ.rst:158 msgid "" "*For Krita 3.3 or later:* Krita on Windows can use Direct3D 11 for graphics " "acceleration (through ANGLE). This is enabled automatically on systems with " "an Intel GPU." msgstr "" "*Для Krita 3.3 і новіших версій:* у Krita для Windows можна використовувати " "Direct3D 11 для прискорення обробки графіки (на основі ANGLE). Ця можливість " "автоматично вмикається на системах із графічним процесором Intel." #: ../../KritaFAQ.rst:161 msgid "I can't edit text from PSD files created by Photoshop" msgstr "" "Маю проблеми із редагуванням тексту у файлах PSD, які було створено у " "Photoshop" #: ../../KritaFAQ.rst:163 msgid "" "There is no text support for psd file yet. The text will appear rasterized " "and converted into a paint layer." msgstr "" "У програмі ще не реалізовано підтримку тексту з файлів psd. Під час " "імпортування текст буде перетворено на растрове зображення і збережено у " "форматі шару малювання." #: ../../KritaFAQ.rst:166 msgid "How much memory does my image take?" msgstr "Скільки пам'яті потрібно для мого зображення?" #: ../../KritaFAQ.rst:168 msgid "" "For simple images, its easy to calculate: you multiply width \\* height \\* " "channels \\* size of the channels (so, for a 1000×1000 16 bit integer rgba " "image: 1000 x 1000 x 4 x 2). You multiply this by the number of layers plus " "two (one for the image, one for the display). If you add masks, filter " "layers or clone layers, it gets more complicated." msgstr "" "Для простих зображень об'єм файла порахувати доволі просто: слід помножити " "ширину \\* висоту \\* кількість каналів \\* розмір каналів (отже, формула " "кількості байтів для зображення 1000×1000, із 16-бітовою глибиною кольорів, " "прозорістю у просторі кольорів RGB буде такою: 1000 × 1000 × 4 × 2). Це " "число слід помножити на кількість шарів із додаванням двох (один для " "зображення і ще один для показу). Якщо ви додавали маски, шари фільтрування " "або шари клонування, точно усе порахувати буде дещо складніше." #: ../../KritaFAQ.rst:171 msgid "Why do I get a checkerboard pattern when I use the eraser?" msgstr "Чому ґумка лишає на полотні такі дивні картаті сліди?" #: ../../KritaFAQ.rst:173 msgid "" "You’re probably used to Gimp or Photoshop. The default background or first " "layer in these applications doesn’t have an alpha channel by default. Thus, " "on their background layer, the eraser paints in the background color." msgstr "" "Ймовірно, ви раніше користувалися Gimp або Photoshop. Типове тло або перший " "шар у цих програмах типово не має каналу прозорості. Тому у шарі тла ґумка " "лишає слід, який просто зафарбовано кольором тла." #: ../../KritaFAQ.rst:175 msgid "" "In Krita, all layers have an alpha channel, if you want to paint in the " "background color, you should simply do it in a layer above the first one " "(Layer 1), that would prevent you from erasing the white background color, " "making the checkerboard visible. You get the same effect in, say, gimp, if " "you create new image, add an alpha channel and then use the eraser tool. " "Most Krita users will actually start a sketch in Krita by adding a new blank " "layer first before doing anything else. (The :kbd:`Ins` key is a useful " "shortcut here). That doesn’t use extra memory, since a blank layer or a " "layer with a default color just takes one pixel worth of memory." msgstr "" "У Krita для усіх шарів передбачено канал прозорості. Якщо ви хочете малювати " "кольором тла, вам слід просто робити це у шарі над першим (Шаром 1). Це має " "запобігти витиранню білого кольору тла і появі видимого картатого замінника " "прозорості. Той самий ефект можна спостерігати, скажімо, у Gimp, якщо ви " "створите нове зображення, додасте канал прозорості, а потім скористаєтеся " "інструментом ґумки. Більшість користувачів Krita насправді починають з " "ескіза, додаючи новий порожній шар перед усіма іншими елементами малюнка. " "(Клавіша :kbd:`Ins` є корисним клавіатурним скороченням для додавання шару.) " "Додавання шару не призведе до додаткової витрати пам'яті, оскільки порожній " "шар або шар із типовим кольором займає у пам'яті рівно стільки, скільки " "займає один піксель." #: ../../KritaFAQ.rst:178 msgid "Windows: Can I use Krita with Sandboxie?" msgstr "Windows: Чи можна користуватися Krita у Sandboxie?" #: ../../KritaFAQ.rst:180 msgid "" "No, this is not recommended. Sandboxie causes stuttering and freezes due to " "the way it intercepts calls for resources on disk." msgstr "" "Ні, не рекомендуємо цього робити. Sandboxie призводить до нерівномірної " "роботи програми та зависань через спосіб, у який ця програма перехоплює " "виклики до ресурсів на диску." #: ../../KritaFAQ.rst:183 msgid "Windows: Krita cannot save" msgstr "Windows: Krita не зберігає дані на диск" #: ../../KritaFAQ.rst:185 msgid "" "If the message is \"File not found. Check the file name and try again.\", " "you probably have Controlled Folder Access enabled." msgstr "" "Якщо ви бачите повідомлення «Файл не знайдено. Перевірте назву файла і " "повторіть спробу» («File not found. Check the file name and try again.»), " "ймовірно, у системі увімкнено керування доступом до тек." #: ../../KritaFAQ.rst:187 msgid "Select :menuselection:`Start --> Settings`." msgstr "Виберіть :menuselection:`Пуск --> Параметри`." #: ../../KritaFAQ.rst:188 msgid "Choose :menuselection:`Update & security --> Windows Defender`." msgstr "Виберіть :menuselection:`Оновлення і безпека --> Захисник Windows`." #: ../../KritaFAQ.rst:189 msgid "Select :guilabel:`Open Windows Defender Security Center`." msgstr "Виберіть :guilabel:`Відкрити Центр безпеки Захисника Windows`." #: ../../KritaFAQ.rst:190 msgid "" "Select :guilabel:`Virus & threat protection`, and then choose :guilabel:" "`Virus & threat protection settings`." msgstr "" "Виберіть :guilabel:`Захист від вірусів і загроз`, а потім виберіть :guilabel:" "`Параметри захисту від вірусів і загроз`." #: ../../KritaFAQ.rst:191 msgid "Under :guilabel:`Controlled folder access`, turn it on or off." msgstr "" "На сторінці :guilabel:`Керований доступ до тек` позначте або зніміть " "позначку з пункту." #: ../../KritaFAQ.rst:193 msgid "" "You can also whitelist Krita, following `these instructions `_." msgstr "" "Крім того, ви можете додати Krita до «білого» списку за допомогою `цих " "настанов `_." #: ../../KritaFAQ.rst:196 msgid "Can krita work with 8 bit (indexed) images?" msgstr "Чи може Krita працювати із 8-бітовими (індексованими) зображеннями?" #: ../../KritaFAQ.rst:198 msgid "" "No. Krita has been designed from the ground up to use real colors, not " "indexed palettes. There are no plans to support indexed color images, " "although Krita can export to some indexed color image formats, such as GIF. " "However, it does not offer detailed control over pixel values." msgstr "" "Ні. Krita було від початку розроблено для використання справжніх кольорів, а " "не індексованих палітр. Планів щодо підтримки індексованих кольорових " "зображень немає, хоча Krita може експортувати дані до деяких форматів " "зображень із індексуванням кольорів, зокрема GIF. Втім, у програмі не " "передбачено можливості детального керування значеннями кольорів пікселів." #: ../../KritaFAQ.rst:202 msgid "How can I produce a backtrace on Windows?" msgstr "Як отримати дані зворотного трасування у Windows?" #: ../../KritaFAQ.rst:206 msgid ":ref:`Dr. Mingw debugger `" msgstr ":ref:`Засіб діагностики Dr. Mingw `" #: ../../KritaFAQ.rst:208 msgid "" "If you experience a crash on Windows, and can reproduce the crash, the bug " "report will be much more valuable if you can create a backtrace. A backtrace " "is somewhat akin to an airplane's blackbox, in that they tell what set of " "instructions your computer was running when it was crashing (where the crash " "happened), making it very useful to figure out why the crash happened." msgstr "" "Якщо програма аварійно завершує роботу у Windows, і ви можете відтворити " "аварійне завершення, звіт щодо вади буде набагато ціннішим, якщо ви зможете " "долучити до нього дані зворотне трасування. Зворотне трасування чимось схоже " "на чорну скриньку літака, у ньому зберігаються дані щодо набору інструкцій, " "які ваш комп'ютер виконував у момент аварійного завершення роботи. Ці дані " "дуже корисні для визначення причин аварійного завершення." #: ../../KritaFAQ.rst:210 msgid "" "The :ref:`Dr. Mingw debugger ` is bundled with Krita. Please visit " "the page :ref:`Dr. Mingw debugger ` for instructions on getting a " "backtrace with it." msgstr "" "До пакунка Krita включено :ref:`засіб діагностики Dr. Mingw `. Будь " "ласка, відвідайте сторінку :ref:`засобу діагностики Dr. Mingw `, " "щоб дізнатися більше про те, як отримати дані зворотного трасування." #: ../../KritaFAQ.rst:213 msgid "Where can I find older versions of Krita?" msgstr "Де знайти старі версії Krita?" #: ../../KritaFAQ.rst:215 msgid "" "All the older versions of Krita that are still available can be found here:" msgstr "Усі застарілі версії Krita, які усе ще є доступними, можна знайти тут:" #: ../../KritaFAQ.rst:217 msgid "`Very old builds `_" msgstr "`Дуже давні збірки `_" #: ../../KritaFAQ.rst:220 msgid "On Windows, the Krita User Interface is too small on my HiDPI screen" msgstr "" "У Windows інтерфейс користувача Krita є надто малим для екранів із високою " "роздільною здатністю" #: ../../KritaFAQ.rst:222 msgid "" "If you're using Windows, you can set the display scaling to 150% or 200%, " "and enable the experimental HiDPI support in the configurations:" msgstr "" "Якщо ви користуєтеся Windows, ви можете налаштувати масштабування дисплея на " "150% або 200% і увімкнути експериментальну підтримку високої роздільної " "здатності у налаштуваннях:" #: ../../KritaFAQ.rst:224 msgid "On the menu, select :menuselection:`Settings --> Configure Krita`" msgstr "" "У меню виберіть пункт :menuselection:`Параметри --> Налаштувати Krita`." #: ../../KritaFAQ.rst:225 msgid "On :guilabel:`General` page, switch to :guilabel:`Window` tab." msgstr "" "На сторінці :guilabel:`Загальне` перейдіть на вкладку :guilabel:`Вікно`." #: ../../KritaFAQ.rst:226 msgid "Check :guilabel:`Enable Hi-DPI support`" msgstr "Позначте пункт :guilabel:`Вмикання підтримки високої роздільності`" #: ../../KritaFAQ.rst:227 msgid "Restart Krita" msgstr "Перезапустіть Krita." #: ../../KritaFAQ.rst:229 msgid "" "You can also change the toolbox icon size by right-clicking on the toolbox " "and selecting a size." msgstr "" "Ви також можете змінити розмір піктограми набору інструментів, клацнувши " "правою кнопкою на панелі набору інструментів із наступним вибором розміру." #: ../../KritaFAQ.rst:233 msgid "Tablets" msgstr "Планшети" #: ../../KritaFAQ.rst:236 msgid "What tablets does Krita support?" msgstr "Підтримку яких планшетів передбачено у Krita?" #: ../../KritaFAQ.rst:238 msgid "" "Krita isn’t much fun without a pressure sensitive tablet. If the tablet has " "been properly configured, Krita should work out of the box." msgstr "" "Krita втрачає багато можливостей, якщо у вас немає планшета із чутливістю до " "тиску. Якщо планшет було налаштовано належним чином, Krita має працювати без " "будь-яких додаткових налаштовувань." #: ../../KritaFAQ.rst:240 msgid "" "On Windows, you need to either install the Wintab drivers for your tablet, " "or enable the :guilabel:`Windows 8+ Pointer Input` option in Krita's " "settings." msgstr "" "У Windows вам слід або встановити драйвери Wintab до вашого планшета, або " "увімкнути пункт :guilabel:`Введення з вказівника Windows 8+` у параметрах " "Krita." #: ../../KritaFAQ.rst:242 msgid "" "You can find a community curated list of tablets supported by krita :ref:" "`here `." msgstr "" "Ви можете знайти створений спільнотою список підтримуваних у Krita " "планшетів :ref:`тут `." #: ../../KritaFAQ.rst:244 msgid "" "If you're looking for information about tablets like the iPad or Android " "tablets, look :ref:`here `." msgstr "" "Якщо вам потрібні відомості щодо планшетів, подібних до iPad або планшетів " "під керуванням Android, пошукайте їх :ref:`тут `." #: ../../KritaFAQ.rst:248 msgid "What if your tablet is not recognized by Krita?" msgstr "Що, якщо планшет не розпізнається Krita?" #: ../../KritaFAQ.rst:253 msgid "We would like to see the full output of the following commands:" msgstr "Нам потрібні усі дані, які буде виведено у відповідь на такі команди:" #: ../../KritaFAQ.rst:255 msgid "``lsmod``" msgstr "``lsmod``" #: ../../KritaFAQ.rst:256 msgid "``xinput``" msgstr "``xinput``" #: ../../KritaFAQ.rst:257 msgid "``xinput list-props`` (id can be fetched from the item 2)" msgstr "``xinput list-props`` (ідентифікатор можна отримати з пункту 2)" #: ../../KritaFAQ.rst:258 msgid "Get the log of the tablet events (if applicable):" msgstr "Отримайте журнал подій на планшеті (якщо він потрібен):" #: ../../KritaFAQ.rst:260 msgid "Open a console application (e.g. Konsole on KDE)" msgstr "Відкрийте програму — емулятор консолі (наприклад Konsole у KDE)" #: ../../KritaFAQ.rst:261 msgid "" "Set the amount of scrollback to 'unlimited' (for :program:`Konsole`: :" "menuselection:`Settings --> Edit Current Profile --> Scrolling --> Unlimited " "Scrollback`)" msgstr "" "Встановіть для буфера гортання об'єм «без обмеження» (для :program:" "`Konsole`: :menuselection:`Параметри --> Редагувати поточний профіль --> " "Гортання --> Необмежений буфер гортання`)" #: ../../KritaFAQ.rst:262 msgid "Start Krita by typing 'krita' and create any document" msgstr "Запустіть Krita введенням команди «krita» і створіть якийсь документ" #: ../../KritaFAQ.rst:263 ../../KritaFAQ.rst:282 msgid "" "Press :kbd:`Ctrl + Shift + T`, you will see a message box telling the " "logging has started" msgstr "" "Натисніть :kbd:`Ctrl + Shift + T`. Ви побачите вікно із повідомленням щодо " "того, що розпочато ведення журналу" #: ../../KritaFAQ.rst:264 ../../KritaFAQ.rst:283 msgid "Try to reproduce your problem" msgstr "Спробуйте відтворити проблему" #: ../../KritaFAQ.rst:265 msgid "The console is now filled with the log. Attach it to a bug report" msgstr "" "Консоль буде заповнено повідомленнями журналу. Долучіть їх до звіту щодо вади" #: ../../KritaFAQ.rst:267 msgid "" "Attach all this data to a bug report using public paste services like paste." "kde.org" msgstr "" "Долучіть усі ці дані до звіту щодо вади за допомогою загальнодоступних служб " "зберігання даних, наприклад paste.kde.org" #: ../../KritaFAQ.rst:273 msgid "" "First check whether your tablet's driver is correctly installed. Often, a " "driver update, a Windows update or the installation of Razer gaming mouse " "driver breaks tablets." msgstr "" "Спочатку, перевірте чи правильно встановлено драйвер до вашого планшета. " "Часто оновлення драйвера, оновлення Windows або встановлення драйвера до " "ігрової миші Razer може зашкодити працездатності планшетів." #: ../../KritaFAQ.rst:275 msgid "" "Then check whether switching to the Windows 8 Pointer API makes a " "difference: :menuselection:`Settings --> Configure Krita --> Tablet`." msgstr "" "Далі, перевірте, чи перемикання програмного інтерфейсу вказівника у Windows " "8 може усе змінити: :menuselection:`Параметри --> Налаштувати Krita --> " "Планшет`." #: ../../KritaFAQ.rst:277 msgid "" "If you still have problems with Windows and your tablet, then we cannot help " "you without a tablet log." msgstr "" "Якщо у вас виникають проблеми із Windows і вашим планшетом, ми не зможемо " "вам допомогти без журналу планшета." #: ../../KritaFAQ.rst:279 msgid "" "Install `DebugView `_ from the official Microsoft site" msgstr "" "Встановіть `DebugView `_ з офіційного сайта Microsoft" #: ../../KritaFAQ.rst:280 msgid "Start :program:`DebugView`" msgstr "Запустіть :program:`DebugView`" #: ../../KritaFAQ.rst:281 msgid "Start :program:`Krita`" msgstr "Запустіть :program:`Krita`" #: ../../KritaFAQ.rst:284 msgid "" "Go back to DebugView and save its output to a file. Attach this file to a " "bug report or paste it using services like paste.kde.org." msgstr "" "Поверніться до DebugView і збережіть виведені дані до файла. Долучіть цей " "файл до звіту щодо вади або вставте до звіту посилання на викладені десь у " "вільному доступі, наприклад на paste.kde.org, дані." #: ../../KritaFAQ.rst:287 msgid "" "However, in 100\\% of the cases where Windows users have reported that their " "tablet didn't work over the past five years, the problem has been either a " "buggy driver or a broken driver installation, but not a bug in Krita." msgstr "" "Втім, в усіх випадках, коли користувачі Windows повідомляли про " "непрацездатність планшета протягом останніх п'яти років, проблема полягала " "або у неякісному драйвері, або у тому, що драйвер було встановлено " "неправильно. Жодної проблеми, яку було пов'язано із Krita, зафіксовано не " "було." #: ../../KritaFAQ.rst:291 msgid "How to fix a tablet offset on multiple screen setup on Windows" msgstr "" "Як виправити зсув позиції вказівника планшета у конфігурації із декількома " "екранами на Windows" #: ../../KritaFAQ.rst:293 msgid "" "If you see that your tablet pointer has an offset when working with Krita " "canvas, it might be highly probable that Krita got incorrect screen " "resolution from the system. That problem happens mostly when an external " "monitor is present and when either a monitor or a tablet was connected after " "the system boot." msgstr "" "Якщо ви бачите, що вказівник, яким ви керуєте з вашого планшета, має певний " "зсув під час роботи з полотном Krita. Дуже ймовірно, що Krita отримала " "помилкові дані щодо роздільної здатності екрана від операційної системи. " "Така проблема переважно трапляється, коли у системі є зовнішній монітор і " "коли монітор або планшет було з'єднано із комп'ютером вже після завантаження " "системи." #: ../../KritaFAQ.rst:295 msgid "You can fix this issue manually by:" msgstr "Ви можете усунути цю проблему вручну:" #: ../../KritaFAQ.rst:297 msgid "Put your stylus away from the tablet." msgstr "Приберіть стило подалі від планшета." #: ../../KritaFAQ.rst:298 msgid "" "Start Krita without using a stylus, that is using a mouse or a keyboard." msgstr "" "Запустіть Krita без використання стила, тобто з використання миші або " "клавіатури." #: ../../KritaFAQ.rst:299 msgid "Press :kbd:`Shift` key and hold it." msgstr "Натисніть і утримуйте клавішу :kbd:`Shift`." #: ../../KritaFAQ.rst:300 msgid "Touch a tablet with your stylus so Krita would recognize it." msgstr "Доторкніться стилом до планшета так, щоб Krita розпізнала планшет." #: ../../KritaFAQ.rst:302 msgid "" "You will see a special dialog asking for the real screen resolution. Choose " "the correct value or enter it manually and press :guilabel:`OK`." msgstr "" "Ви побачите спеціальне діалогове вікно, у якому вас проситимуть вказати " "справжню роздільну здатність екрана. Виберіть правильне значення або введіть " "його вручну і натисніть кнопку :guilabel:`Гаразд`." #: ../../KritaFAQ.rst:304 msgid "" "If you have a dual monitor setup and only the top half of the screen is " "reachable, you might have to enter the total width of both screens plus the " "double height of your monitor in this field." msgstr "" "Якщо ви працюєте за двома моніторами і можете користуватися лише верхньою " "частиною екрана, у цьому полі, ймовірно, слід вказати загальну ширину обох " "екранів плюс подвоєну висоту зображення на вашому моніторі." #: ../../KritaFAQ.rst:306 msgid "" "If this didn't work, and if you have a Wacom tablet, an offset in the canvas " "can be caused by a faulty Wacom preference file which is not removed or " "replaced by reinstalling the drivers." msgstr "" "Якщо це не спрацює і ви користуєтеся планшетом Wacom, зсув на полотні може " "бути спричинено помилками у файлі налаштувань Wacom, який не було вилучено " "або замінено під час перевстановлення драйверів." #: ../../KritaFAQ.rst:308 msgid "" "To fix it, use the “Wacom Tablet Preference File Utility” to clear all the " "preferences. This should allow Krita to detect the correct settings " "automatically." msgstr "" "Щоб виправити помилку, скористайтеся «Wacom Tablet Preference File Utility» " "для вилучення усіх налаштувань. Після цього Krita зможе визначити належні " "параметри роботи автоматично." #: ../../KritaFAQ.rst:311 msgid "" "This will reset your tablet's configuration, thus you will need to " "recalibrate/reconfigure it." msgstr "" "У результаті налаштування вашого планшета буде скинуто до типових, отже вам " "доведеться повторно виконати процедуру калібрування і налаштовування." #: ../../KritaFAQ.rst:313 msgid "" "*For Krita 3.3 or later:* You can try to :ref:`enable “Windows 8+ Pointer " "Input” `, but some features might not work with it." msgstr "" "*Для Krita 3.3 і новіших версій:* ви можете спробувати :ref:`увімкнути " "«Введення з вказівника Windows 8+» `, але це може призвести " "до непрацездатності деяких можливостей програми." #: ../../KritaFAQ.rst:316 msgid "Microsoft Surface Pro and N-Trig" msgstr "Microsoft Surface Pro та N-Trig" #: ../../KritaFAQ.rst:318 msgid "" "Krita 3.3.0 and later supports the Windows Pointer API (Windows Ink) " "natively. Your Surface Pro or other N-Trig enabled pen tablet should work " "out of the box with Krita after you enable Windows Ink in :menuselection:" "`Settings --> Configure Krita --> Tablet`." msgstr "" "У Krita 3.3.0 та новіших версіях передбачено вбудовану підтримку програмного " "інтерфейсу Windows Pointer (Windows Ink). Ваш планшет Surface Pro або інший " "планшет із пером та можливостями N-Trig має працювати без додаткових " "налаштувань у Krita після вмикання Windows Ink на сторінці :menuselection:" "`Параметри --> Налаштувати Krita --> Планшет`." #: ../../KritaFAQ.rst:321 msgid "Tablet Pro and the Surface Pro" msgstr "Tablet Pro та Surface Pro" #: ../../KritaFAQ.rst:323 msgid "" "Unlike Wacom's Companion, the Surface line of tablets doesn't have working " "hardware buttons. Tablet Pro is a (non-free) utility that puts virtual " "buttons on screen. Krita 3.1 and above will have predefined shortcut " "profiles to work with Tablet Pro." msgstr "" "На відміну від Companion від Wacom, лінійка планшетів Surface не має " "працездатних апаратних кнопок. Tablet Pro є (комерційною, не безкоштовною) " "програмою, яка розташовує віртуальні кнопки на екрані. У Krita 3.1 та " "новіших версіях передбачено попередньо визначені профілі клавіатурних " "скорочень для роботи з Tablet Pro." #: ../../KritaFAQ.rst:325 msgid "http://tabletpro.net/" msgstr "http://tabletpro.net/" #: ../../KritaFAQ.rst:327 msgid "See http://www.youtube.com/watch?v=WKXZgYqC3tI for instructions." msgstr "Настанови можна знайти тут: http://www.youtube.com/watch?v=WKXZgYqC3tI" #: ../../KritaFAQ.rst:330 msgid "" "Weird stuff happens on Windows, like ripples, rings, squiggles or " "poltergeists" msgstr "" "У Windows трапляються дивні речі, зокрема з'являються брижі, кільця, " "закарлюки або частини зображення рухаються без причин" #: ../../KritaFAQ.rst:332 msgid "" "Windows comes with a lot of settings to make it work with a pen. All these " "settings can be annoying. This tool can help you set the settings correctly " "when you're using a tablet:" msgstr "" "У Windows передбачено багато параметрів для налаштовування роботи системи з " "пером. Увесь цей набір параметрів може бути доволі складним для розуміння на " "налаштовування. Цей інструмент допоможе вам належним чином встановити " "параметри, якщо ви користуєтеся планшетом:" #: ../../KritaFAQ.rst:334 msgid "https://github.com/saveenr/Fix_My_Pen/releases" msgstr "https://github.com/saveenr/Fix_My_Pen/releases" #: ../../KritaFAQ.rst:337 msgid "Touch doesn't seem to work on Windows" msgstr "У Windows не працює сенсорне керування" #: ../../KritaFAQ.rst:339 msgid "" "You might have to disable and enable the touch driver: go to the device " "manager. (Click the :guilabel:`Start` button and type device manager). " "Choose HID (User interface devices or something like that). Choose Intel(R) " "Precise Touch Device. Right click, Disable it. Right click, Enable it." msgstr "" "Ймовірно, вам слід вимкнути і знову увімкнути драйвер сенсорної панелі. " "Скористайтеся для цього програмою для керування пристроями. Натисніть " "кнопку :guilabel:`Пуск` і введіть «device manager» або «диспетчер " "пристроїв». Виберіть «HID» («User interface devices», «Пристрої інтерфейсу " "користувача» або щось таке). Виберіть Intel® Precise Touch Device. Клацніть " "правою, виберіть «Вимкнути». Клацніть правою, виберіть «Увімкнути»." #: ../../KritaFAQ.rst:342 msgid "Toolbox" msgstr "Інструменти" #: ../../KritaFAQ.rst:345 msgid "Toolbox missing" msgstr "Програма не показує панелі інструментів" #: ../../KritaFAQ.rst:347 msgid "" "You can reset the Workspace by pressing the right most button on the " "toolbar, the Workspace switcher, and click on a desired Workspace from the " "list." msgstr "" "Ви можете відновити початковий стан робочого простору натисканням " "найправішої кнопки на панелі інструментів, перемикача робочих просторів, із " "наступним вибором бажаного робочого простору зі списку." #: ../../KritaFAQ.rst:349 msgid "" "Or you can right-click on any docker title bar or open space in any toolbar, " "and select Toolbox. It's the first option." msgstr "" "Крім того, ви можете клацнути правою кнопкою на смужці заголовка будь-якої з " "бічних панелей або на вільному місці будь-якої з панелей інструментів і " "вибрати пункт guilabel:`Інструменти`. Це перший пункт у списку." #: ../../KritaFAQ.rst:351 msgid "" "Also, you can check the :guilabel:`Settings` menu, it has got a lot of " "interesting stuff, then go to the Dockers menu and select :guilabel:" "`Toolbox`." msgstr "" "Ви також можете скористатися меню :guilabel:`Параметри`. У ньому ви знайдете " "багато цікавих пунктів. Далі, можете скористатися меню бічної панелі і " "вибрати у ньому пункт :guilabel:`Інструменти`." #: ../../KritaFAQ.rst:354 msgid "Tool icons size is too big" msgstr "Розмір піктограм на панелі інструментів є надто великим" #: ../../KritaFAQ.rst:356 msgid "Right click the toolbox to set the size." msgstr "" "Клацніть правою кнопкою миші на панелі інструментів і виберіть у " "контекстному меню пункт зміни розміру піктограм." #: ../../KritaFAQ.rst:359 msgid "Krita can't get maximized" msgstr "Не вдається максимізувати вікно Krita" #: ../../KritaFAQ.rst:361 msgid "" "This happens when your dockers are placed in such a way that the window " "cannot be made less high. Rearrange your Workspace." msgstr "" "Так трапляється, якщо бічні панелі розташовано так, що неможливо зменшити " "висоту вікна. Перевпорядкуйте ваш робочий простір." #: ../../KritaFAQ.rst:364 msgid "Resources" msgstr "Ресурси" #: ../../KritaFAQ.rst:367 msgid "" "Is there a way to restore a default brush that I have mistakenly overwritten " "with new settings to default?" msgstr "" "Чи можна якось відновити типовий пензель, який помилково було перезаписано " "пензлем із новими параметрами?" #: ../../KritaFAQ.rst:369 msgid "Yes. First go to the resource folder, which is in" msgstr "Так. Спочатку, перейдіть до теки ресурсів, яку розташовано за адресою" #: ../../KritaFAQ.rst:374 msgid "" ":file:`user\\\\Appdata\\\\Roaming\\\\krita\\\\` or :file:`%APPDATA%\\" "\\Roaming\\\\krita\\\\`" msgstr "" ":file:`user\\\\Appdata\\\\Roaming\\\\krita\\\\` або :file:`%APPDATA%\\" "\\Roaming\\\\krita\\\\`" #: ../../KritaFAQ.rst:376 msgid "OSX" msgstr "OSX" #: ../../KritaFAQ.rst:378 msgid "" "You can easily do this by going into :menuselection:`Settings --> Manage " "Resources --> Open Resource Folder`." msgstr "" "Зробити це просто можна за допомогою пункту меню :menuselection:`Параметри --" "> Керування ресурсами --> Відкрити теку ресурсів`." #: ../../KritaFAQ.rst:380 msgid "" "Then go into the *paintoppresets* folder and remove the latest created file " "that you made of your preset." msgstr "" "Далі, перейдіть до теки *paintoppresets* і вилучіть останній створений вами " "файл вашого набору пензлів." #: ../../KritaFAQ.rst:383 msgid "" "After that go back to the resources folder and edit the blacklist file to " "remove the previous paintoppreset so Krita will load it. (Yes, it is a bit " "of a convoluted system, but at the least you don't lose your brushes)" msgstr "" "Після цього поверніться до теки ресурсів, відкрийте для редагування файл " "blacklist і вилучіть попередній paintoppreset, оскільки Krita " "завантажуватиме його. (Так, це дещо складна система, але, принаймні, ви не " "втратите ваші пензлі.)" #: ../../KritaFAQ.rst:389 msgid "How do I set favorite presets?" msgstr "Як встановити улюблені набори пензлів?" #: ../../KritaFAQ.rst:391 msgid "" "Right-click a brush in the brush docker and assign it a tag. Then right-" "click on canvas to call popup palette, click the second right-most icon on " "the bottom-right of the palette, now you can pick the tag which contains the " "brush you assigned to it." msgstr "" "Клацніть правою кнопкою миші на пункті пензля на бічній панелі пензлів і " "призначте для пензля мітку. Далі, клацніть правою кнопкою на полотні для " "виклику контекстної палітри. Натисніть другу праворуч піктограму у нижній " "правій частині палітри. Ви зможете вибрати мітку, яку ви призначили для " "вашого пензля." #: ../../KritaFAQ.rst:394 msgid "Can Krita load Photoshop Brushes?" msgstr "Чи може Krita завантажувати пензлі Photoshop?" #: ../../KritaFAQ.rst:396 msgid "" "Yes, but there are limitations. You can load ABR files by using the :" "guilabel:`Import` button in the :guilabel:`Predefined brush` tab in the " "brush editor. Since Adobe hasn’t disclosed the file format specification, we " "depend on reverse-engineering to figure out what to load, and currently " "that’s limited to basic features." msgstr "" "Так, але із певними обмеженнями. Ви можете завантажувати файли ABR за " "допомогою кнопки :guilabel:`Імпортувати` на вкладці :guilabel:`Стандартний " "пензель` редактора пензлів. Оскільки Adobe не відкриває специфікації формату " "файлів, ми залежимо від зворотної інженерії у визначенні того, що " "завантажувати, тому у поточній версії обмежені базовими можливостями." #: ../../KritaFAQ.rst:399 msgid "Krita is slow" msgstr "Krita працює повільно" #: ../../KritaFAQ.rst:401 msgid "" "There is a myriad of reasons why this might be. Below is a short checklist." msgstr "Причин може бути безліч. Нижче наведено основні можливі причини." #: ../../KritaFAQ.rst:403 msgid "" "Something else is hogging the CPU or the memory: spotify and other electron " "apps have been known to do this." msgstr "" "Процесор або пам'ять навантажує якась інша програма: spotify та інші " "програми на основі electron відомі такою поведінкою." #: ../../KritaFAQ.rst:404 msgid "" "You are running Windows, and have 3rdparty security software like Sandboxie " "or Total Defender installed" msgstr "" "Ви працюєте у Windows і використовуєте стороннє захисне програмне " "забезпечення, зокрема Sandboxie або Total Defender." #: ../../KritaFAQ.rst:405 msgid "" "You are working on images that are too big for your hardware (dimensions, " "channel depth or number of layers)" msgstr "" "Ви працюєте із зображеннями, які є надто великими (розміри зображення, " "глибина каналів або кількість шарів) для вашого обладнання." #: ../../KritaFAQ.rst:406 msgid "You do not have canvas acceleration enabled" msgstr "У системі не увімкнено апаратне прискорення роботи із полотном." #: ../../KritaFAQ.rst:408 -#| msgid "Please also check `this page `_" msgid "Please also check `this page `__" msgstr "" "Будь ласка, ознайомтеся із вмістом `цієї сторінки `__" #: ../../KritaFAQ.rst:411 msgid "Slow start-up" msgstr "Програма повільно запускається" #: ../../KritaFAQ.rst:413 msgid "" "You probably have too many resources installed. Deactivate some bundles " "under :menuselection:`Settings --> Manage Resources`." msgstr "" "Ймовірно, встановлено забагато ресурсів. Вимкніть частину пакунків ресурсів " "за допомогою пункту меню :menuselection:`Параметри --> Керування ресурсами`." #: ../../KritaFAQ.rst:415 msgid "" "If you're using Windows with the portable zip file, Windows will scan all " "files every time you start Krita. That takes ages. Either use the installer " "or tell Microsoft Security Essentials to make an exception for Krita." msgstr "" "Якщо ви користуєтеся Windows і портативною версією програми з архіву zip. " "Під час кожного запуску Krita Windows виконуватиме сканування усіх файлів. " "Або скористайтеся звичайним пакунком для встановлення, або повідомте " "Microsoft Security Essentials, що слід зробити виключення для Krita." #: ../../KritaFAQ.rst:418 msgid "Slow Brushes" msgstr "Повільні пензлі" #: ../../KritaFAQ.rst:420 msgid "" "Check if you accidentally turned on the stabilizer in the tool options " "docker." msgstr "" "Перевірте, чи не було випадково увімкнено стабілізатор на панелі :guilabel:" "`Параметри інструмента`." #: ../../KritaFAQ.rst:421 msgid "" "Try another scaling mode like trilinear. :menuselection:`Settings --> " "Configure Krita --> Display`." msgstr "" "Спробуйте скористатися іншим режимом масштабування, наприклад трилінійним. :" "menuselection:`Параметри --> Налаштувати Krita --> Монітор`." #: ../../KritaFAQ.rst:422 msgid "Try a lower channel depth than 16-bit." msgstr "Спробуйте меншу глибину кольорів, ніж 16-бітова." #: ../../KritaFAQ.rst:423 msgid "For NVidia, try a 16-bit floating point color space." msgstr "" "Якщо користуєтеся графічною карткою NVidia, спробуйте скористатися простором " "16-бітових кольорів зі значеннями із рухомою крапкою." #: ../../KritaFAQ.rst:424 msgid "" "For older AMD CPU's (Krita 2.9.10 and above), turn off the vector " "optimizations that are broken on AMD CPUs. :menuselection:`Settings --> " "Configure Krita --> Performance`. This isn't needed if you've got an AMD " "Threadripper™ CPU." msgstr "" "Для застарілих процесорів AMD (у Krita 2.9.10 і новіших версіях) вимкніть " "векторну оптимізацію, яка просто не працює на процесорах AMD. :menuselection:" "`Параметри --> Налаштувати Krita --> Швидкодія`. Нічого вимикати не слід, " "якщо ви користуєтеся процесором AMD із Threadripper™." #: ../../KritaFAQ.rst:425 msgid "" "It's a fairly memory hungry program, so 2GB of RAM is the minimum, and 4GB " "is the preferable minimum." msgstr "" "Програма є доволі вимогливою до обсягів оперативної пам'яті, тому потрібно " "принаймні 2 ГБ оперативної пам'яті, а краще — взагалі не менше 4 ГБ." #: ../../KritaFAQ.rst:426 msgid "Check that nothing else is hogging your CPU" msgstr "Перевірте, чи ніякі інші програми не споживають увесь процесорний час." #: ../../KritaFAQ.rst:427 msgid "" "Check that Instant Preview is enabled if you're using bigger brushes (but " "for very small brushes, make sure is disabled)." msgstr "" "Перевірте, чи увімкнено негайний перегляд, якщо ви використовуєте великі " "пензлі (а для дуже малих пензлів вимкніть його)." #: ../../KritaFAQ.rst:428 msgid "Set brush precision to 3 or auto." msgstr "Встановіть точність пензля у значення 3 або «авто»." #: ../../KritaFAQ.rst:429 msgid "Use a larger value for brush spacing." msgstr "Використовуйте більше значення для інтервалу пензля." #: ../../KritaFAQ.rst:430 msgid "" "If all of this fails, record a video and post a link and description on the " "Krita forum." msgstr "" "Якщо жодна з цих порад не спрацює, запишіть відео і додайте посилання на " "нього разом із описом до вашого допису на форумі Krita." #: ../../KritaFAQ.rst:431 msgid "" "Check whether OpenGL is enabled, and if it isn't, enable it. If it is " "enabled, and you are on Windows, try the Angle renderer. Or disable it." msgstr "" "Перевірте, чи увімкнено OpenGL. Якщо не увімкнено, увімкніть. Якщо " "увімкнено, і ви працюєте у Windows, спробуйте режим обробки Angle. Або " "просто вимкніть апаратну обробку." #: ../../KritaFAQ.rst:434 msgid "Slowdown after a been working for a while" msgstr "Програма уповільнюється, попрацювавши у звичайному режимі певний час" #: ../../KritaFAQ.rst:436 msgid "" "Once you have the slowdown, click on the image-dimensions in the status bar. " "It will tell you how much RAM Krita is using, if it has hit the limit, or " "whether it has started swapping. Swapping can slow down a program a lot, so " "either work on smaller images or turn up the maximum amount of RAM in :" "menuselection:`Settings --> Configure Krita --> Performance --> Advanced " "Tab`." msgstr "" "Щойно почнете спостерігати уповільнення, клацніть на пункті розмірностей " "зображення на смужці стану вікна програми. Програма повідомить вам скільки " "оперативної пам'яті споживає Krita. Якщо оперативну пам'ять буде вичерпано, " "програма почне використовувати резервну пам'ять на диску. Використання " "пам'яті на диску значно уповільнює роботу програми, тому доведеться або " "зменшити розміри зображення, або увімкнути максимальний об'єм пам'яті за " "допомогою пункту :menuselection:`Параметри --> Налаштувати Krita --> " "Швидкодія --> вкладка «Додатково»`." #: ../../KritaFAQ.rst:439 msgid "Tools" msgstr "Інструменти" #: ../../KritaFAQ.rst:442 msgid "" "Why does the Transform Tool give a good result and then get blurry upon " "finalizing?" msgstr "" "Чому інструмент перетворення дає чудовий результат, який згодом, під час " "остаточної обробки, стає розмитим?" #: ../../KritaFAQ.rst:444 -#| msgid "" -#| "The transform tool makes a preview that you edit before computing the " -#| "finalized version. As this preview is using the screen resolution rather " -#| "than the image resolution, it may feel that the result is blurry compared " -#| "to the preview. See `this page `_ for more info." msgid "" "The transform tool makes a preview that you edit before computing the " "finalized version. As this preview is using the screen resolution rather " "than the image resolution, it may feel that the result is blurry compared to " "the preview. See `this page `__ for more info." msgstr "" "У інструменті перетворення передбачено попередній перегляд результатів, перш " "ніж ви накажете програмі створити остаточну версію. Оскільки для " "попереднього перегляду використовується роздільна здатність екрана, а не " "роздільна здатність зображення, може видатися, що результат є розмитим, " "порівняно із зображенням попереднього перегляду. Ознайомтеся із `цією " "сторінкою `__, щоб " "дізнатися більше." #: ../../KritaFAQ.rst:448 msgid "License, rights and the Krita Foundation" msgstr "Умови ліцензування, авторські права та Krita Foundation" #: ../../KritaFAQ.rst:451 msgid "Who owns Krita?" msgstr "Хто є власником Krita?" #: ../../KritaFAQ.rst:453 msgid "" "The Stichting Krita Foundation owns the Krita trademark. The copyright on " "the source code is owned by everyone who has worked on the source code." msgstr "" "Авторськими правами на торгову марку Krita володіє Stichting Krita " "Foundation. Авторськими правами на початковий код володіють усі, хто " "працював над цим початковим кодом." #: ../../KritaFAQ.rst:456 msgid "Who and what is Kiki?" msgstr "Хто така Кікі?" #: ../../KritaFAQ.rst:458 msgid "" "Kiki is a cybersquirrel. She’s our mascot and has been designed by Tyson " "Tan. We choose a squirrel when we discovered that ‘krita’ is the Albanian " "word for Squirrel." msgstr "" "Кікі — кібербілка. Вона — наш маскот, який було розроблено Тайсоном Таном " "(Tyson Tan). Ми вибрали білку, коли дізналися, що «krita» — албанська назва " "білки." #: ../../KritaFAQ.rst:461 msgid "Why is Krita Free?" msgstr "Чому Krita є вільною програмою?" #: ../../KritaFAQ.rst:463 msgid "" "Krita is developed as `free software `_ within the KDE " "community. We believe that good tools should be available for all artists. " "You can also buy Krita on the Windows Store if you want to support Krita's " "development or want to have automatic updates to newer versions." msgstr "" "Krita розроблено як `вільне програмне забезпечення `_ у " "межах спільноти KDE. Ми віримо у те, що якісні інструменти мають бути " "доступними для усіх художників. Ви також можете придбати Krita у Windows " "Store, якщо хочете підтримати розробку Krita або хочете отримувати " "автоматичні оновлення до новіших версій." #: ../../KritaFAQ.rst:466 msgid "Can I use Krita commercially?" msgstr "Чи можу я користуватися Krita з комерційною метою?" #: ../../KritaFAQ.rst:468 msgid "" "Yes. What you create with Krita is your sole property. You own your work and " "can license your art however you want. Krita’s GPL license applies to " "Krita’s source code. Krita can be used commercially by artists for any " "purpose, by studios to make concept art, textures, or vfx, by game artists " "to work on commercial games, by scientists for research, and by students in " "educational institutions." msgstr "" "Так. Усе створене вами за допомогою Krita є лише вашою власністю. Ви маєте " "усі права на вашу роботу і можете ліцензувати ваш твір у будь-який бажаний " "спосіб. Умови ліцензування Krita, GPL, стосуються коду самої програми Krita. " "Художники можуть використовувати Krita із комерційною метою для будь-якої " "мети. Її можуть використовувати студії для створення концепт-арту, текстур " "або vfx. Ігрові художники можуть скористатися програмою для роботи над " "комерційними іграми. Науковці — для досліджень, а студенти — з навчальною " "метою." #: ../../KritaFAQ.rst:470 msgid "" "If you modify Krita itself, and distribute the result, you have to share " "your modifications with us. Krita’s GNU GPL license guarantees you this " "freedom. Nobody is ever permitted to take it away." msgstr "" "Якщо ви внесете зміни до самої Krita і поширюватимете результат, вам слід " "поділитися вашими змінами із нами. Умови ліцензування Krita за GNU GPL " "гарантують вам можливість цих дій. Ніхто і ніколи не зможе просто забрати " "код і закрити його." #: ../../KritaFAQ.rst:476 msgid "Can I get Krita for iPad? for Android?" msgstr "Чи є версія Krita для iPad? А для Android?" #: ../../KritaFAQ.rst:478 msgid "Not at this point in time." msgstr "Ні, зараз немає." #: ../../KritaFAQ.rst:481 msgid "Who translates Krita" msgstr "Хто перекладає Krita?" #: ../../KritaFAQ.rst:483 msgid "" "Krita is a `KDE application `_ — and proud of it! That " "means that Krita’s translations are done by `KDE localization teams `_. If you want to help out, join the team for your language! " "There is another way you can help out making Krita look good in any " "language, and that is join the development team and fix issues within the " "code that make Krita harder to translate." msgstr "" "Krita є `програмою KDE `_ і пишається цим! Це означає, " "що переклади Krita здійснюються `командами з локалізації KDE `_. Якщо ви хочете допомогти у цьому, долучайтеся до команди вашої " "мови! Є іще один спосіб допомогти у тому, щоб зробити так, щоб Krita добре " "виглядала вашою рідною мовою — долучитися до команди розробників і виправити " "помилку у коді, які ускладнюють переклад Krita." #: ../../KritaFAQ.rst:486 msgid "Reference" msgstr "Посилання" #: ../../KritaFAQ.rst:488 msgid "https://answers.launchpad.net/krita-ru/+faqs" msgstr "https://answers.launchpad.net/krita-ru/+faqs" diff --git a/locale/uk_UA/LC_MESSAGES/contributors_manual/community.po b/locale/uk_UA/LC_MESSAGES/contributors_manual/community.po index e304b125d..e882c08a3 100644 --- a/locale/uk_UA/LC_MESSAGES/contributors_manual/community.po +++ b/locale/uk_UA/LC_MESSAGES/contributors_manual/community.po @@ -1,306 +1,306 @@ # Translation of docs_krita_org_contributors_manual___community.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___community\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-19 03:36+0100\n" "PO-Revision-Date: 2019-03-13 16:34+0200\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" #: ../../contributors_manual/community.rst:1 msgid "Guide to the Krita community" msgstr "Настанови щодо спільноти Krita" #: ../../contributors_manual/community.rst:16 msgid "The Krita Community" msgstr "Спільнота Krita" #: ../../contributors_manual/community.rst:18 msgid "" "Get in touch! Apart from the website at https://www.krita.org, the Krita " "project has three main communication channels:" msgstr "" "Виходьте на зв'язок! Окрім сайта за адресою https://www.krita.org, у проекту " "Krita є три основних канали обміну інформацією:" #: ../../contributors_manual/community.rst:20 msgid "Internet Relay Chat (IRC)" msgstr "Internet Relay Chat (IRC)" #: ../../contributors_manual/community.rst:21 msgid "The mailing list" msgstr "Список листування" #: ../../contributors_manual/community.rst:22 #: ../../contributors_manual/community.rst:73 msgid "Phabricator" msgstr "Phabricator" #: ../../contributors_manual/community.rst:24 msgid "" "While Krita developers and users are present on social media such as " "Twitter, Mastodon, Reddit, Google+, Tumblr or Facebook, those are not the " "place where we discuss new features, bugs, development or where we make " "plans for the future." msgstr "" #: ../../contributors_manual/community.rst:26 msgid "There are also the:" msgstr "Крім того, ми маємо такі ресурси:" #: ../../contributors_manual/community.rst:28 msgid "bug tracker" msgstr "система стеження за вадами" #: ../../contributors_manual/community.rst:29 msgid "development sprints" msgstr "спринти розробників" #: ../../contributors_manual/community.rst:31 msgid "" "You’ll find that there are a number of people are almost always around: the " "core team." msgstr "Декілька людей слідкують майже за усім — це основа команди." #: ../../contributors_manual/community.rst:33 msgid "" "Boudewijn (irc: boud): project maintainer, lead developer. Works full-time " "on Krita. Manages the Krita Foundation, triages bugs, does social media and " "admin stuff. Boudewijn is also on Reddit as boudewijnrempt." msgstr "" #: ../../contributors_manual/community.rst:34 msgid "Dmitry (irc: dmitryk_log): lead developer. Works full-time on Krita." msgstr "" "Dmitry (irc: dmitryk_log): провідний розробник. Працює над Krita повний " "робочий день." #: ../../contributors_manual/community.rst:35 msgid "" "Wolthera (irc: wolthera_laptop): developer, writes the manual and tutorials, " "triages bugs, helps people out" msgstr "" "Wolthera (irc: wolthera_laptop): розробник, автор підручника і настанов, " "вивчення вад, допомога людям." #: ../../contributors_manual/community.rst:36 msgid "Scott Petrovic (irc: scottyp): UX designer, developer, webmaster" msgstr "" "Scott Petrovic (irc: scottyp): розробник інтерфейсу, розробник коду, " "вебмайстер" #: ../../contributors_manual/community.rst:37 msgid "" "David Revoy (irc: deevad): expert user, creates Pepper & Carrot, maintains " "the preset bundle." msgstr "" "David Revoy (irc: deevad): досвідчений користувач, творець Pepper & Carrot, " "супровідник набору шаблонів." #: ../../contributors_manual/community.rst:38 msgid "Alvin Wong (irc: windragon): windows guru" msgstr "Alvin Wong (irc: windragon): знавець windows" #: ../../contributors_manual/community.rst:39 msgid "Ben Cooksley (irc: bcooksley): KDE system administrator." msgstr "Ben Cooksley (irc: bcooksley): системний адміністратор KDE." #: ../../contributors_manual/community.rst:41 msgid "" "Krita’s team spans the globe, but most development happens in Europe and " "Russia." msgstr "" "Розробники Krita живуть на усій земній кулі, але більшість з них мешкає у " "Європі та Росії." #: ../../contributors_manual/community.rst:43 msgid "" "Krita is part of the larger KDE community. The KDE® Community is a free " "software community dedicated to creating an open and user-friendly computing " "experience, offering an advanced graphical desktop, a wide variety of " "applications for communication, work, education and entertainment and a " "platform to easily build new applications upon. The KDE contributors guide " "is relevant for Krita contributors, too, and can be found here: http://" "archive.flossmanuals.net/kde-guide/ ." msgstr "" #: ../../contributors_manual/community.rst:45 msgid "" "The Krita Foundation was created to support development of Krita. The Krita " "Foundation has sponsored Dmitry’s work on Krita since 2013." msgstr "" #: ../../contributors_manual/community.rst:48 msgid "Internet Relay Chat" msgstr "Internet Relay Chat" #: ../../contributors_manual/community.rst:50 msgid "" "IRC is the main communication channel. There are IRC clients for every " "operating system out there, as well as a web client on the krita website." msgstr "" -"Основним каналом спілкування є IRC. Клієнтські програми IRC є для майже" -" будь-якої операційної системи. Крім того, можна скористатися вебклієнтом на" -" сайті krita." +"Основним каналом спілкування є IRC. Клієнтські програми IRC є для майже будь-" +"якої операційної системи. Крім того, можна скористатися вебклієнтом на сайті " +"krita." #: ../../contributors_manual/community.rst:52 msgid "" "Joining IRC: connect to irc.freenode.net, select a unique nickname and join " "the #krita and ##krita-chat channels. #krita is for on-topic talk, ##krita-" "chat for off-topic chat." msgstr "" -"Долучення до IRC: з'єднайтеся із irc.freenode.net, виберіть унікальний" -" псевдонім і долучайтеся до каналів #krita та ##krita-chat. Канал #krita" -" призначено для обговорення програми, канал ##krita-chat — для обговорення" -" інших тем." +"Долучення до IRC: з'єднайтеся із irc.freenode.net, виберіть унікальний " +"псевдонім і долучайтеся до каналів #krita та ##krita-chat. Канал #krita " +"призначено для обговорення програми, канал ##krita-chat — для обговорення " +"інших тем." #: ../../contributors_manual/community.rst:53 msgid "Don’t ask to ask: if you’ve got a question, just ask it ." msgstr "Не питайте, чи можна спитати: маєте питання — задайте його." #: ../../contributors_manual/community.rst:54 msgid "" "Don’t panic if several discussions happen at the same time. That’s normal in " "a busy channel." msgstr "" "Не панікуйте, якщо одразу відбувається декілька обговорень. Це звичайна " "практика для зайнятих каналів." #: ../../contributors_manual/community.rst:55 msgid "Talk to an individual by typing their nick and a colon." msgstr "" "Поспілкуватися із кимось окремо можна додавши перед повідомленням його чи її " "псевдонім із додаванням двокрапки." #: ../../contributors_manual/community.rst:56 msgid "" "Almost every Monday, at 14:00 CET or CEST, we have a meeting where we " "discuss what happened in the past week, what we’re doing, and everything " "that’s relevant for the project. The meeting notes are kept in google docs." msgstr "" #: ../../contributors_manual/community.rst:57 msgid "" "Activity is highest in CET or CEST daytime and evenings. US daytime and " "evenings are most quiet." msgstr "" #: ../../contributors_manual/community.rst:58 msgid "" "**IRC is not logged. If you close the channel, you will be gone, and you " "will not be able to read what happened when you join the channel again. If " "you ask a question, you have to stay around!**" msgstr "" #: ../../contributors_manual/community.rst:59 msgid "" "It is really irritating for other users and disrupting to conversations if " "you keep connecting and disconnecting." msgstr "" -"Якщо ви постійно встановлюватимете з'єднання із каналом і розриватимете його," -" це дратуватиме інших користувачів і заважатиме логічній послідовності" -" спілкування." +"Якщо ви постійно встановлюватимете з'єднання із каналом і розриватимете " +"його, це дратуватиме інших користувачів і заважатиме логічній послідовності " +"спілкування." #: ../../contributors_manual/community.rst:63 msgid "Mailing List" msgstr "Список листування" #: ../../contributors_manual/community.rst:65 msgid "" "The mailing list is used for announcements and sparingly for discussions. " "Everyone who wants to work on Krita one way or another should be subscribed " "to the mailing list." msgstr "" #: ../../contributors_manual/community.rst:67 msgid "" "`Mailing List Archives `_" msgstr "" "`Архів списку листування `_" #: ../../contributors_manual/community.rst:69 msgid "" "The mailing list is called \"kimageshop\", because that is the name under " "which the Krita project was started. Legal issues (surprise!) led to two " "renames, once to Krayon, then to Krita." msgstr "" #: ../../contributors_manual/community.rst:75 msgid "Phabricator serves the following purposes for the Krita team:" msgstr "Phabricator у команді Krita виконує такі ролі:" #: ../../contributors_manual/community.rst:77 msgid "" "Track what we are working on: https://phabricator.kde.org/maniphest/ This " "includes development tasks, designing new features and UX design, as well as " "tasks related to the website." msgstr "" #: ../../contributors_manual/community.rst:78 msgid "Review code submissions: https://phabricator.kde.org/differential/" msgstr "" "Подання латок до коду для рецензування: https://phabricator.kde.org/" "differential/" #: ../../contributors_manual/community.rst:79 msgid "" "Host the git repository: https://phabricator.kde.org/source/krita/ . Note " "that while there is a mirror of our git repository on Github, we do not use " "Github for Krita’s development." msgstr "" #: ../../contributors_manual/community.rst:81 msgid "" "**Do not** report bugs as tasks on Phabricator. Phabricator is where we " "organize our work." msgstr "" "**Не повідомляйте** про вади за допомогою завдань (tasks) на Phabricator. " "Phabricator призначено для упорядковування нашої роботи." #: ../../contributors_manual/community.rst:83 msgid "" "**Do** put all your code submissions (patches) on Phabricator. **Do not** " "attach patches to bugs in the bug tracker." msgstr "" "**Розміщуйте** усі ваші зміни у коді (латки) на Phabricator. **Не " "долучайте** латки до повідомлень щодо вад у системі стеження за вадами." #: ../../contributors_manual/community.rst:86 msgid "Bugzilla: the Bug Tracker" msgstr "Bugzilla: система стеження за вадами" #: ../../contributors_manual/community.rst:88 msgid "" "Krita shares the bug tracker with the rest of the KDE community. Krita bugs " "are found under the Krita product. There are two kinds of reports in the bug " "tracker: bugs and wishes. See the chapters on Bug Reporting and Bug Triaging " "on how to handle bugs. Wishes are feature requests. Do not report feature " "requests in bugzilla unless a developer has asked you to. See the chapter on " "Feature Requests for what is needed to create a good feature request." msgstr "" #: ../../contributors_manual/community.rst:91 msgid "Sprints" msgstr "Спринти" #: ../../contributors_manual/community.rst:93 msgid "" "Sometimes, core Krita developers and users come together, most often in " "Deventer, the Netherlands, to work together on our code design, UX design, " "the website or whatever needs real, face-to-face contact. Travel to sprints " "is usually funded by KDE e.V., while accommodation is funded by the Krita " "Foundation." 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 ad70cd493..d8c71716f 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,919 +1,919 @@ # 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-03-12 03:34+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-03-10 21:04+0200\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 "" #: ../../contributors_manual/krita_manual_conventions.rst:23 msgid "" "`Primer `_" msgstr "" "`Настанови `_" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "User Manual:" msgstr "Посібник користувача:" #: ../../contributors_manual/krita_manual_conventions.rst:24 msgid "" "`Quick Ref `_" msgstr "" "`Короткий довідник `_" #: ../../contributors_manual/krita_manual_conventions.rst:25 msgid "" "`Text Cheatsheet `_" msgstr "" "`Текстова шпаргалка `_" #: ../../contributors_manual/krita_manual_conventions.rst:27 msgid "" "`Introduction `_" msgstr "" "`Вступ `_" #: ../../contributors_manual/krita_manual_conventions.rst:28 msgid "" "`Markup `_" msgstr "" "`Розмітка `_" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "Reference Documentation:" msgstr "Довідкова документація:" #: ../../contributors_manual/krita_manual_conventions.rst:29 msgid "" "`Directives `_" msgstr "" "`Директиви `_" #: ../../contributors_manual/krita_manual_conventions.rst:30 msgid "`Roles `_" msgstr "`Ролі `_" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "Sphinx specific docs:" msgstr "Специфічна документація до Sphinx:" #: ../../contributors_manual/krita_manual_conventions.rst:32 msgid "" "`Sphinx' page on restructured text `_ -- This is useful for the specific " "sphinx directives and roles it uses to generate for example table of " "contents." msgstr "" #: ../../contributors_manual/krita_manual_conventions.rst:34 msgid "" "There are differences between the official reStructuredText and the sphinx " "docs multiple ways to do things. This document specifies the suggested " "conventions to go with." msgstr "" #: ../../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 "" #: ../../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 it's 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 "" "Посилання слід вказувати так: ``: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 "" #: ../../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 "" #: ../../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 "" #: ../../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 "" "Можна створювати :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 "" #: ../../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 "" "Це форматування для випадків, коли можлива втрата даних, зокрема через те, " "що дані не було збережено, або через те, що у додатках 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 "" #: ../../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 "Це можливості 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 "" diff --git a/locale/uk_UA/LC_MESSAGES/contributors_manual/optimising_images.po b/locale/uk_UA/LC_MESSAGES/contributors_manual/optimising_images.po index 14017d5d2..3da3e9d7f 100644 --- a/locale/uk_UA/LC_MESSAGES/contributors_manual/optimising_images.po +++ b/locale/uk_UA/LC_MESSAGES/contributors_manual/optimising_images.po @@ -1,604 +1,634 @@ # Translation of docs_krita_org_contributors_manual___optimising_images.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___optimising_images\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-03-03 03:22+0100\n" -"PO-Revision-Date: 2019-03-03 08:24+0200\n" +"PO-Revision-Date: 2019-03-14 15:22+0200\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" #: ../../contributors_manual/optimising_images.rst:1 msgid "How to make and optimise images for use in the manual." msgstr "" "Як створювати і оптимізувати зображення для використання у цьому підручнику." #: ../../contributors_manual/optimising_images.rst:15 msgid "Images for the Manual" msgstr "Зображення для підручника" #: ../../contributors_manual/optimising_images.rst:17 msgid "" "This one is a little bit an extension to :ref:`saving_for_the_web`. In " "particular it deals with making images for the manual, and how to optimise " "images." msgstr "" #: ../../contributors_manual/optimising_images.rst:19 msgid "Contents" msgstr "Зміст" #: ../../contributors_manual/optimising_images.rst:22 msgid "Tools for making screenshots" msgstr "Інструменти для створення знімків вікон" #: ../../contributors_manual/optimising_images.rst:24 msgid "" "Now, if you wish to make an image of the screen with all the dockers and " "tools, then :ref:`saving_for_the_web` won't be very helpful: It only saves " "out the canvas contents, after all!" msgstr "" #: ../../contributors_manual/optimising_images.rst:26 msgid "" "So, instead, we'll make a screenshot. Depending on your operating system, " "there are several screenshot utilities available." msgstr "" #: ../../contributors_manual/optimising_images.rst:29 #: ../../contributors_manual/optimising_images.rst:81 msgid "Windows" msgstr "Windows" #: ../../contributors_manual/optimising_images.rst:31 msgid "" "Windows has a build-in screenshot tool. It is by default on the :kbd:`PrtSc` " "key. On laptops you will sometimes need to use the :kbd:`Fn` key." msgstr "" "У Windows передбачено вбудований інструмент створення знімків вікон. Типово, " "його можна викликати натисканням клавіші :kbd:`PrtSc`. На ноутбуках вам " "іноді доведеться скористатися клавішею :kbd:`Fn`." #: ../../contributors_manual/optimising_images.rst:34 #: ../../contributors_manual/optimising_images.rst:88 #: ../../contributors_manual/optimising_images.rst:154 msgid "Linux" msgstr "Linux" #: ../../contributors_manual/optimising_images.rst:35 msgid "" "Both Gnome and KDE have decent screenshot tools showing up by default when " "using the :kbd:`PrtSc` key, as well do other popular desktop environments. " "If, for whatever reason, you have no" msgstr "" #: ../../contributors_manual/optimising_images.rst:38 msgid "With imagemagick, you can use the following command::" msgstr "Якщо користуватиметеся imagemagick, запам'ятайте таку команду::" #: ../../contributors_manual/optimising_images.rst:40 #: ../../contributors_manual/optimising_images.rst:219 #: ../../contributors_manual/optimising_images.rst:240 msgid "ImageMagick" msgstr "ImageMagick" #: ../../contributors_manual/optimising_images.rst:42 msgid "" "While we should minimize the amount of gifs in the manual for a variety of " "accessibility reasons, you sometimes still need to make gifs and short " "videos. Furthermore, gifs are quite nice to show off features with release " "notes." msgstr "" #: ../../contributors_manual/optimising_images.rst:44 msgid "For making short gifs, you can use the following programs:" msgstr "" "Для створення невеличких анімацій у gif можете скористатися такими " "програмами:" #: ../../contributors_manual/optimising_images.rst:46 msgid "" "`Peek `_ -- This one has an appimage and a very " "easy user-interface. Like many screenrecording programs it does show trouble " "on Wayland." msgstr "" #: ../../contributors_manual/optimising_images.rst:49 msgid "OS X" msgstr "OS X" #: ../../contributors_manual/optimising_images.rst:51 msgid "" "The Screenshot hotkey on OS X is :kbd:`Shift + Command + 3`, according to " "`the official apple documentation `_." msgstr "" +"Комбінацією клавіш для створення знімків вікон у OS X є :kbd:`Shift + Command" +" + 3`, відповідно до `офіційної документації Apple <" +"https://support.apple.com/en-us/HT201361>`_." #: ../../contributors_manual/optimising_images.rst:54 msgid "The appropriate file format for the job." msgstr "Формат файлів, який відповідає завданню." #: ../../contributors_manual/optimising_images.rst:56 msgid "" "Different file formats are better for certain types of images. In the end, " "we want to have images that look nice and have a low filesize, because that " "makes the manual easier to download or browse on the internet." msgstr "" +"Для різних типів зображень варто використовувати різні типи файлів. Нам" +" хочеться, щоб зображення виглядали красиво, а розмір файлів був якнайменшим," +" оскільки це спрощує отримання файла підручника та навігацію підручником у" +" інтернеті." #: ../../contributors_manual/optimising_images.rst:58 msgid "GUI screenshots" msgstr "Знімки графічного інтерфейсу" #: ../../contributors_manual/optimising_images.rst:59 msgid "This should use png, and if possible, in gif." msgstr "" "Такі зображення має бути збережено у форматі png і, якщо можливо, у gif." #: ../../contributors_manual/optimising_images.rst:60 msgid "Images that have a lot of flat colors." msgstr "Зображення, на яких багато одноколірних областей." #: ../../contributors_manual/optimising_images.rst:61 msgid "This should use png." msgstr "Для таких зображень слід використовувати формат png." #: ../../contributors_manual/optimising_images.rst:62 msgid "Grayscale images" msgstr "Зображення у відтінках сірого" #: ../../contributors_manual/optimising_images.rst:63 msgid "These should be gif or png." msgstr "Такі зображення слід зберігати у форматах gif та png." #: ../../contributors_manual/optimising_images.rst:64 msgid "Images with a lot of gradients" msgstr "Зображення із багатьма переходами кольорів" #: ../../contributors_manual/optimising_images.rst:65 msgid "These should be JPG." msgstr "Такі зображення слід зберігати у форматі JPG." #: ../../contributors_manual/optimising_images.rst:67 msgid "Images with a lot of transparency." msgstr "Зображення зі значними прозорими областями." #: ../../contributors_manual/optimising_images.rst:67 msgid "These should use PNG." msgstr "Для таких зображень слід використовувати PNG." #: ../../contributors_manual/optimising_images.rst:69 msgid "" "The logic is the way how each of these saves colors. Jpeg is ideal for " "photos and images with a lot of gradients because it :ref:`compresses " "differently `. However, contrasts don't do well in jpeg. " "PNG does a lot better with images with sharp contrasts, while in some cases " "we can even have less than 256 colors, so gif might be better." msgstr "" #: ../../contributors_manual/optimising_images.rst:71 msgid "" "Greyscale images, even when they have a lot of gradients variation, should " "be PNG. The reason is that when we use full color images, we are, depending " "on the image, using 3 to 5 numbers to describe those values, with each of " "those values having a possibility to contain any of 256 values. JPEG and " "other 'lossy' file formats use clever psychological tricks to cut back on " "the amount of values an image needs to show its contents. However, when we " "make grayscale images, we only keep track of the lightness. The lightness is " "only one number, that can have 256 values, making it much easier to just use " "gif or PNG, instead of jpeg which could have nasty artifacts. (And, it is " "also a bit smaller)" msgstr "" #: ../../contributors_manual/optimising_images.rst:73 msgid "**When in doubt, use PNG.**" msgstr "**Якщо маєте сумніви, використовуйте PNG.**" #: ../../contributors_manual/optimising_images.rst:76 msgid "Optimising Images in quality and size." msgstr "Оптимізація зображень за якістю та розміром." #: ../../contributors_manual/optimising_images.rst:78 msgid "" "Now, while most image editors try to give good defaults on image sizes, we " "can often make them even smaller by using certain tools." msgstr "" #: ../../contributors_manual/optimising_images.rst:83 msgid "" "The most commonly recommended tool for this on Windows is `IrfranView " "`_, but the dear writer of this document has no " "idea how to use it exactly." msgstr "" +"Рекомендованим інструментом для цієї мети у Windows є `IrfranView <" +"https://www.irfanview.com/>`_, але автор цього підручника не знає, що саме" +" слід для зробити для досягнення мети." #: ../../contributors_manual/optimising_images.rst:85 msgid "The other option is to use PNGCrush as mentioned in the linux section." msgstr "" "Крім того, можна скористатися PNGCrush, як про це згадується у розділі щодо " "linux." #: ../../contributors_manual/optimising_images.rst:91 msgid "Optimising PNG" msgstr "Оптимізація PNG" #: ../../contributors_manual/optimising_images.rst:92 msgid "" "There is a whole laundry list of `PNG optimisation tools `_ available on Linux. They come in two categories: Lossy " "(Using psychological tricks), and Lossless (trying to compress the data more " "conventionally). The following are however the most recommended:" msgstr "" #: ../../contributors_manual/optimising_images.rst:95 msgid "" "A PNG compressor using lossy techniques to reduce the amount of colors used " "in a smart way." msgstr "" "Засіб стискання PNG використовує методики зберігання зображення із втратою " "якості для розумного зменшення кількості кольорів." #: ../../contributors_manual/optimising_images.rst:97 msgid "To use PNGquant, go to the folder of choice, and type::" msgstr "" "Щоб скористатися PNGquant, перейдіть до вибраної вами теки і віддайте таку " "команду::" #: ../../contributors_manual/optimising_images.rst:101 msgid "`PNGQuant `_" msgstr "`PNGQuant `_" #: ../../contributors_manual/optimising_images.rst:101 msgid "" "Where *image* is replaced with the image file name. When you press enter, a " "new image will appear in the folder with the compressed results. PNGQuant " "works for most images, but some images, like the color selectors don't do " "well with it, so always double check that the resulting image looks good, " "otherwise try one of the following options:" msgstr "" #: ../../contributors_manual/optimising_images.rst:104 msgid "A lossless PNG compressor. Usage::" msgstr "Засіб стискання PNG без втрат. Користування::" #: ../../contributors_manual/optimising_images.rst:108 msgid "`PNGCrush `_" msgstr "`PNGCrush `_" #: ../../contributors_manual/optimising_images.rst:108 msgid "" "This will try the most common methods. Add ``-brute`` to try out all methods." msgstr "" +"Буде виконано спробу використатися найбільш типові методи. Додайте" +" ``-brute``, щоб наказати програмі спробувати усі методи." #: ../../contributors_manual/optimising_images.rst:111 msgid "" "Another lossless PNG compressor which can be run after using PNGQuant, it is " "apparently originally a fork of png crush. Usage::" msgstr "" +"Ще одним інструментом стискання PNG без втрат, яким можна скористатися після" +" використання PNGQuant, є відгалуження png crush. Користування::" #: ../../contributors_manual/optimising_images.rst:116 msgid "`Optipng `_" msgstr "`Optipng `_" #: ../../contributors_manual/optimising_images.rst:116 msgid "" "where image is the filename. OptiPNG will then proceed to test several " "compression algorithms and **overwrite** the image.png file with the " "optimised version. You can avoid overwriting with the ``--out imageout.png`` " "command." msgstr "" #: ../../contributors_manual/optimising_images.rst:119 msgid "Optimising GIF" msgstr "Оптимізація GIF" #: ../../contributors_manual/optimising_images.rst:121 msgid "`FFMPEG `_" msgstr "`FFMPEG `_" #: ../../contributors_manual/optimising_images.rst:122 msgid "`Gifski `_" msgstr "`Gifski `_" #: ../../contributors_manual/optimising_images.rst:123 msgid "`LossyGif `_" msgstr "`LossyGif `_" #: ../../contributors_manual/optimising_images.rst:126 msgid "Optimising JPEG" msgstr "Оптимізація JPEG" #: ../../contributors_manual/optimising_images.rst:128 msgid "" "Now, JPEG is really tricky to optimize properly. This is because it is a :" "ref:`lossy file format `, and that means that it uses " "psychological tricks to store its data." msgstr "" +"JPEG доволі важко оптимізувати як слід. Причина полягає у тому, що це" +" :ref:`формат зберігання із втратою даних `, а це означає," +" що для зберігання даних вже використовуються певні психологічні трюки." #: ../../contributors_manual/optimising_images.rst:130 msgid "" "However, tricks like these become very obvious when your image has a lot of " "contrast, like text. Furthermore, JPEGs don't do well when they are resaved " "over and over. Therefore, make sure that there's a lossless version of the " "image somewhere that you can edit, and that only the final result is in JPEG " "and gets compressed further." msgstr "" #: ../../contributors_manual/optimising_images.rst:135 msgid "MacOS/ OS X" msgstr "MacOS/ OS X" #: ../../contributors_manual/optimising_images.rst:137 msgid "" "`ImageOptim `_ -- A Graphical User Interface " "wrapper around commandline tools like PNGquant and gifski." msgstr "" "`ImageOptim `_ — графічний інтерфейс до засобів " "командного рядка, зокрема PNGquant та gifski." #: ../../contributors_manual/optimising_images.rst:140 msgid "Editing the metadata of a file" msgstr "Редагування метаданих файла" #: ../../contributors_manual/optimising_images.rst:142 msgid "" "Sometimes, personal information gets embedded into an image file. " "Othertimes, we want to embed information into a file to document it better." msgstr "" +"Іноді, до файлів зображення вбудовуються деякі особисті дані. А іноді, нам" +" самим потрібно вбудувати певні дані для поліпшення документування файла." #: ../../contributors_manual/optimising_images.rst:144 msgid "" "There are no less than 3 to 4 different ways of handling metadata, and " "metadata has different ways of handling certain files." msgstr "" +"Існує не менше 3-4 різних способів роботи з метаданими. Крім того, обробка" +" метаданих у різних типах файлів відбувається у різний спосіб." #: ../../contributors_manual/optimising_images.rst:146 msgid "" "The most commonly used tool to edit metadata is :program:`ExifTool`, another " "is to use :program:`ImageMagick`." msgstr "" +"Найпоширенішим інструментом для редагування метаданих є :program:`ExifTool`." +" Ще одним інструментом редагування є :program:`ImageMagick`." #: ../../contributors_manual/optimising_images.rst:149 msgid "Windows and OS X" msgstr "Windows та OS X" #: ../../contributors_manual/optimising_images.rst:151 msgid "" "To get exiftool, `just get it from the website `_." msgstr "" "Щоб встановити exiftool, `просто отримайте пакунок із сайта `_." #: ../../contributors_manual/optimising_images.rst:156 msgid "On Linux, you can also install exiftool." msgstr "У Linux ви можете встановити exiftool." #: ../../contributors_manual/optimising_images.rst:159 msgid "Debian/Ubuntu" msgstr "Debian/Ubuntu" #: ../../contributors_manual/optimising_images.rst:159 msgid "``sudo apt-get install libimage-exiftool-perl``" msgstr "``sudo apt-get install libimage-exiftool-perl``" #: ../../contributors_manual/optimising_images.rst:162 msgid "Viewing Metadata" msgstr "Перегляд метаданих" #: ../../contributors_manual/optimising_images.rst:164 msgid "" "Change the directory to the folder where the image is located and type::" msgstr "" "Перейдіть до каталогу, де зберігається зображення, і введіть таку команду::" #: ../../contributors_manual/optimising_images.rst:168 msgid "" "where image is the file you'd like to examine. If you just type exif tool in " "any given folder it will output all the information it can give about any " "file it comes across. If you take a good look at some images, you'll see " "they contain author or location metadata. This can be a bit of a problem " "sometimes when it comes to privacy, and also the primary reason all meta-" "data gets stripped." msgstr "" #: ../../contributors_manual/optimising_images.rst:170 msgid "" "You can also use `ImageMagick's identify `_::" msgstr "" "Ви можете скористатися `identify з ImageMagick `_::" #: ../../contributors_manual/optimising_images.rst:175 msgid "Stripping Metadata" msgstr "Вилучення метаданих" #: ../../contributors_manual/optimising_images.rst:177 msgid "" "Stripping metadata from the example ``image.png`` can be done as follows:" msgstr "" "Вилучити метадані, наприклад, з файла ``image.png``, можна такою командою:" #: ../../contributors_manual/optimising_images.rst:180 msgid "`exiftool -all= image.png`" msgstr "`exiftool -all= image.png`" #: ../../contributors_manual/optimising_images.rst:182 msgid "" "`ExifTool `_" msgstr "" "`ExifTool `_" #: ../../contributors_manual/optimising_images.rst:182 msgid "" "This empties all tags exiftool can get to. You can also be specific and only " "remove a single tag: `exiftool -author= image.png`" msgstr "" #: ../../contributors_manual/optimising_images.rst:185 msgid "OptiPNG" msgstr "OptiPNG" #: ../../contributors_manual/optimising_images.rst:185 msgid "`optipng -strip image.png` This will strip and compress the png file." msgstr "" "`optipng -strip image.png` Ця команда вилучить зайві дані і виконає " "стискання файла png." #: ../../contributors_manual/optimising_images.rst:188 msgid "" "`ImageMagick `_" msgstr "" "`ImageMagick `_" #: ../../contributors_manual/optimising_images.rst:188 msgid "`convert image.png --strip`" msgstr "`convert image.png --strip`" #: ../../contributors_manual/optimising_images.rst:191 msgid "Extracting metadata" msgstr "Видобування метаданих" #: ../../contributors_manual/optimising_images.rst:193 msgid "" "Sometimes we want to extract metadata, like an icc profile, before stripping " "everything. This is done by converting the image to the profile type:" msgstr "" #: ../../contributors_manual/optimising_images.rst:196 msgid "First extract the metadata to a profile by converting::" msgstr "Спочатку видобуваємо метадані до профілі перетворенням::" #: ../../contributors_manual/optimising_images.rst:200 msgid "Then strip the file and readd the profile information::" msgstr "Далі, вилучаємо з файла зайві дані і повторно додаємо дані з профілю::" #: ../../contributors_manual/optimising_images.rst:203 msgid "" "`ImageMagick's Convert `_" msgstr "" "`Convert з ImageMagick `_" #: ../../contributors_manual/optimising_images.rst:206 msgid "Embedding description metadata" msgstr "Вбудовування описових метаданих" #: ../../contributors_manual/optimising_images.rst:208 msgid "" "Description metadata is really useful for the purpose of helping people with " "screenreaders. Webbrowsers will often try to use the description metadata if " "there's no alt text to generate the alt-text. Another thing that you might " "want to embed is stuff like color space data." msgstr "" #: ../../contributors_manual/optimising_images.rst:210 msgid "ExifTool" msgstr "ExifTool" #: ../../contributors_manual/optimising_images.rst:213 msgid "Setting an exif value::" msgstr "Встановлення значення exif::" #: ../../contributors_manual/optimising_images.rst:217 msgid "Setting the PNG chunk for description::" msgstr "Встановлення фрагмента PNG для опису::" #: ../../contributors_manual/optimising_images.rst:222 msgid "Embedding license metadata" msgstr "Вбудовування метаданих щодо ліцензування" #: ../../contributors_manual/optimising_images.rst:224 msgid "" "In a certain way, embedding license metadata is really nice because it " "allows you to permanently mark the image as such. However, if someone then " "uploads it to another website, it is very likely the metadata is stripped " "with imagemagick." msgstr "" #: ../../contributors_manual/optimising_images.rst:227 msgid "Using Properties" msgstr "Використання властивостей" #: ../../contributors_manual/optimising_images.rst:229 msgid "" "You can use dcterms:license for defining the document where the license is " "defined." msgstr "" +"Ви можете скористатися полем dcterms:license для визначення документа із" +" умовами ліцензування." #: ../../contributors_manual/optimising_images.rst:232 msgid "For the GDPL::" msgstr "Для GDPL::" #: ../../contributors_manual/optimising_images.rst:236 msgid "This defines a shorthand name and then license text." msgstr "Це визначає стенографічну назву, а потім текст умов ліцензування." #: ../../contributors_manual/optimising_images.rst:238 msgid "For Creative Commons BY-SA 4.0::" msgstr "Для Creative Commons BY-SA 4.0::" #: ../../contributors_manual/optimising_images.rst:242 msgid "" "The problem with using properties is that they are a non-standard way to " "define a license, meaning that machines cannot do much with them." msgstr "" +"Проблема із використанням властивостей полягає у тому, що властивості не є" +" стандартним способом визначення умов ліцензування, тобто вони не підлягають" +" обов'язковій машинній обробці." #: ../../contributors_manual/optimising_images.rst:245 msgid "Using XMP" msgstr "Використання XMP" #: ../../contributors_manual/optimising_images.rst:247 msgid "" "The creative commons website suggest we `use XMP for this `_. You can ask the Creative Commons License " "choose to generate an appropriate XMP file for you when picking a license." msgstr "" #: ../../contributors_manual/optimising_images.rst:249 msgid "" "We'll need to use the `XMP tags for exiftool `_." msgstr "" +"Маємо скористатися `мітками XMP для exiftool `_." #: ../../contributors_manual/optimising_images.rst:251 msgid "So that would look something like this::" -msgstr "" +msgstr "Отже, це виглядатиме десь так::" #: ../../contributors_manual/optimising_images.rst:255 msgid "Another way of doing the marking is::" -msgstr "" +msgstr "Іншим способом виконати позначення є такий::" #: ../../contributors_manual/optimising_images.rst:260 msgid "First extract the data (if there is any)::" msgstr "Спочатку видобуваємо дані (якщо такі є)::" #: ../../contributors_manual/optimising_images.rst:264 msgid "Then modify the resulting file, and embed the image data::" msgstr "Далі, вносимо зміни до файла-результату і вбудовуємо дані зображення::" #: ../../contributors_manual/optimising_images.rst:266 msgid "With imagemagick you can use the profile option again." -msgstr "" +msgstr "У imagemagick ви можете знову скористатися параметром профілю." #: ../../contributors_manual/optimising_images.rst:268 msgid "" "The XMP definitions per license. You can generate an XMP file for the " "metadata on the creative commons website." msgstr "" diff --git a/locale/uk_UA/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po b/locale/uk_UA/LC_MESSAGES/general_concepts/colors/color_managed_workflow.po index b8a4a4bbc..619b95167 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,1093 +1,1093 @@ # 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-03-13 03:40+0100\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" "PO-Revision-Date: 2019-03-10 21:03+0200\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 "" #: ../../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 colour " "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 "" "Клас із 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 colour." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:71 msgid "" "Finally, group 4 has Vermillion red, citron yellow and cerulean blue. Their " "colours 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 colour 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 " "colour translate properly between color devices." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:82 msgid "" "It usually works by attempting to covert a colour to the reference colour " "space XYZ. XYZ is a coordinate system that has a spot for all colours 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 colour 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." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:88 msgid "" "To give a crude estimate, ICC profiles deal with keeping colours consistent " "over many interpretations of devices (screens, printers) by using a " "reference space, and OCIO deals with manipulating the interpretation of said " "colours." 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 grey it produces. Using " "these and several other measurements it creates an icc profile unique to " "your screen. You set these in Krita's colour 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 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 "" #: ../../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 "" ".. 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 "" #: ../../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-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.)" msgstr "" #: ../../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 "" #: ../../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 colour 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 "Профілі 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 "" #: ../../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 colorspace and their " "respective coordinates in a reference space. For CMYK this is typically L\\*A" "\\*B\\* and for the rest XYZ. These tables are tricky to make, which means " "these profiles are a lot rarer." msgstr "" #: ../../general_concepts/colors/color_managed_workflow.rst:169 msgid "cLUT profiles" msgstr "Профілі cLUT" #: ../../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 colour reproduction. Use this if you want to " "see all colours 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 colours at whatever cost, which may result in awful looking " "colours. 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 "" "A in between solution between perceptual and absolute, relative will try to " "fit whatever colours it can match between colour 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 colourfulness, 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 '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." 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 colour 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 colour 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 colour 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 "" #: ../../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 " "customly 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 "" "Налаштуйте ваші профілі екрана за допомогою пункту меню :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 "" #: ../../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 colour maths, often concerning the blending of colours. " "This colour maths works best in linear colour space, and linear colour 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 colour 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 " "colour 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's 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 colours actually look strange: This is a " "bug in Firefox, which is because its `color management system is incomplete " "`_, save your png, jpg or tiff without an embedded profile to work " "around this." 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 "Переглядач фотографій 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 "" #: ../../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 " "bitdepth 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 specialised 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, mypaint, mangastudio, 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, mangastudio " "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 optimisers. 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 "" "Specialised 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 --> 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." 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 optimised content, and it's recommended to " "stay within 8bit, future screens may have higher bitdepths, 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 optimise 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 "" "`Visualising the XYZ colorspace `_" 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 "" #: ../../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 colormanagement from argylcms manual `_" msgstr "" "`Базовий огляд керування кольорами з підручника з argylcms `_" diff --git a/locale/uk_UA/LC_MESSAGES/general_concepts/file_formats.po b/locale/uk_UA/LC_MESSAGES/general_concepts/file_formats.po index 52813472c..944dca2b9 100644 --- a/locale/uk_UA/LC_MESSAGES/general_concepts/file_formats.po +++ b/locale/uk_UA/LC_MESSAGES/general_concepts/file_formats.po @@ -1,153 +1,212 @@ # Translation of docs_krita_org_general_concepts___file_formats.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___file_formats\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-24 03:22+0100\n" -"PO-Revision-Date: 2019-03-09 11:21+0200\n" +"PO-Revision-Date: 2019-03-14 14:09+0200\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/file_formats.rst:1 msgid "The file formats category." msgstr "Категорія форматів файлів." #: ../../general_concepts/file_formats.rst:14 msgid "File Formats" msgstr "Формати файлів" #: ../../general_concepts/file_formats.rst:16 msgid "" "This category is for graphics file-formats. While most file-formats can be " "looked up on wikipedia, this doesn't always explain what the format can be " "used for and what its strengths and weaknesses are." msgstr "" +"У цій категорії зібрано дані щодо форматів файлів із графічними даними. Хоча" +" дані щодо більшості форматів файлів можна знайти у Вікіпедії, на відповідних" +" сторінках не завжди є пояснення того, для яких даних можна використовувати" +" той чи інший формат, та того, якими є переваги та недоліки формату." #: ../../general_concepts/file_formats.rst:18 msgid "" "In this category we try to describe these in a manner that can be read by " "beginners." msgstr "" "У цій категорії ми намагаємося описати ці формати файлів у спосіб, який буде " "зрозумілим для початківців." #: ../../general_concepts/file_formats.rst:20 msgid "" "Generally, there are the following features that people pay attention to in " "regards to fileformats:" msgstr "" +"Загалом, при обговоренні форматів файлів звертають увагу на такі можливості:" #: ../../general_concepts/file_formats.rst:23 msgid "Compression" msgstr "Стискання" #: ../../general_concepts/file_formats.rst:25 msgid "" "Compression is how the file-format tries to describe the image with as " "little data as possible, so that the resulting file is as small as it can " "get without losing quality." msgstr "" +"Стискання визначає спосіб, у який стандартом формату передбачено використання" +" для зображення якомога меншого місця на пристрої для зберігання даних, тобто" +" алгоритм, за яким дані у файлі певного формату роблять якомога меншими за" +" обсягом без втрати якості зображення." #: ../../general_concepts/file_formats.rst:27 msgid "" "What we generally see is that formats that are small on disk either lose " "image quality, or require the computer to spend a lot of time thinking about " "how the image should look." msgstr "" +"Загалом, можна зауважити, що використання форматів, які дають найменші за" +" розміром файли на диску, передбачає або втрату якості зображення, або" +" потребує значних обчислювальних потужностей для відновлення початкових даних" +" зображення, які запаковано до файла." #: ../../general_concepts/file_formats.rst:29 msgid "" "Vector file-formats like ``svg`` are a typical example of the latter. They " "are really small because the technology used to create them is based on " "mathematics, so it only stores maths-variables and can achieve very high " "quality. The downside is that the computer needs to spend a lot of time " "thinking about how it should look, and sometimes different programs have " "different ways of interpreting the values. Furthermore, vector file-formats " "imply vector graphics, which is a very different way of working than Krita " "is specialised in." msgstr "" +"Векторні формати файлів, зокрема ``svg``, є типовим прикладом другого" +" різновиду форматів. Файли у цих форматах є дуже малими за розміром, оскільки" +" технологію, яку використано для їхнього створення засновано на математиці," +" тому у файлах зберігаються лише значення математичних змінних, а якість" +" зображення близька до ідеальної. Недоліком є те, що комп'ютеру потрібно" +" доволі багато часу для визначення того, як має виглядати зображення. Крім" +" того, іноді різні програми у різний спосіб інтерпретують записані у файлі" +" значення. Крім того, векторні формати зберігають дані векторної графіки, яка" +" передбачає зовсім інший підхід до створення малюнків, ніж той, на якому" +" спеціалізується Krita." #: ../../general_concepts/file_formats.rst:31 msgid "" ":ref:`Lossy file formats `, like ``jpg`` or ``webp`` are " "an example of small on disk, but lowering the quality, and are best used for " "very particular types of images. Lossy thus means that the file format plays " "fast and loose with describing your image to reduce filesize." msgstr "" +":ref:`Формати файлів із втратою якості `, зокрема ``jpg``" +" або ``webp``, є прикладом форматів, які дають малі файли на диску, але" +" знижують якість зображення, а також пасують лише для зображень певного типу." +" Втрата якості означає, що стандартом формату передбачено швидкий і неточний" +" опис зображення з метою зменшення розміру файла, у якому зберігаються дані" +" зображення." #: ../../general_concepts/file_formats.rst:33 msgid "" ":ref:`Non-lossy or lossless formats `, like ``png``, " "``gif`` or ``bmp`` are in contrast, much heavier on disk, but much more " "likely to retain quality." msgstr "" +":ref:`Формати без втрати `, зокрема ``png``, ``gif``" +" або ``bmp``, навпаки, дають більші файли на диску, але із більшою" +" ймовірністю зберігають якість зображення." #: ../../general_concepts/file_formats.rst:35 msgid "" "Then, there's proper working file formats like Krita's ``.kra``, Gimp's " "``xcf``, Photoshop's ``psd``, but also interchange formats like ora and exr. " "These are the heaviest on the hard-drive and often require special programs " "to open them up, but on the other hand these are meant to keep your working " "environment intact, and keep all the layers and guides in them." msgstr "" +"Крім того, є суто робочі формати, зокрема формат Krita ``.kra``, формат GIMP" +" ``xcf``, формат Photoshop ``psd``, а також формати для обміну даними," +" зокрема ora та exr. Файли у цих форматах є найоб'ємнішими і часто потребують" +" для відкриття встановлення спеціалізованих програм, але, з іншого боку, вони" +" містять усі дані робочого середовища і зберігають усі шари та напрямні" +" зображення." #: ../../general_concepts/file_formats.rst:38 msgid "Metadata" msgstr "Метадані" #: ../../general_concepts/file_formats.rst:40 msgid "" "Metadata is the ability of a fileformat to contain information outside of " "the actual image contents. This can be human readable data, like the date of " "creation, the name of the author, a description of the image, but also " "computer readable data, like an icc-profile which tells the computer about " "the qualities of how the colors inside the file should be read." msgstr "" +"Метадані формату файлів — можливість формату зберігати дані, окрім самих" +" даних зображення. Метаданими можуть бути дані, які призначено для читання" +" людиною, зокрема дата створення зображення, ім'я автора, опис зображення," +" або дані, призначені для читання комп'ютером, зокрема профіль кольорів ICC," +" який визначає для комп'ютера спосіб, у який слід читати дані кольорів у" +" файлі." #: ../../general_concepts/file_formats.rst:43 msgid "Openness" msgstr "Відкритість" #: ../../general_concepts/file_formats.rst:45 msgid "" "This is a bit of an odd quality, but it's about how easy it to open or " "recover the file, and how widely it's supported." msgstr "" +"Це дещо нетипова якість. Її пов'язано із простотою відкриття або відновлення" +" даних у файлі та розповсюдженістю підтримки файлів певного формату." #: ../../general_concepts/file_formats.rst:47 msgid "" "Most internal fileformats, like PSD are completely closed, and it's really " "difficult for human outsiders to recover the data inside without opening " "photoshop. Other examples are camera raw files which have different " "properties per camera manufacturer." msgstr "" +"Більшість форматів для внутрішнього використання, подібних до PSD, є повністю" +" закритими. Наприклад, відновити дані у файлі PSD дуже складно, якщо у вас" +" немає встановленої відповідної версії Photoshop. Іншим прикладом таких" +" файлів є файли цифрових негативів (RAW) фотоапаратів, які мають у різних" +" виробників доволі різні властивості." #: ../../general_concepts/file_formats.rst:49 msgid "" "SVG, as a vector fileformat, is on the other end of the spectrum, and can be " "opened with any text-editor and edited." msgstr "" +"SVG, як формат файлів векторних даних, перебуває на іншому кінці спектра" +" відкритості. Його можна відкрити і редагувати у будь-якому текстовому" +" редакторі." #: ../../general_concepts/file_formats.rst:51 msgid "" "Most formats are in-between, and thus there's also a matter of how widely " "supported the format is. jpg and png cannot be read or edited by human eyes, " "but the vast majority of programs can open them, meaning the owner has easy " "access to them." msgstr "" +"Більшість форматів займають проміжне місце, тому вибір того чи іншого формату" +" також дуже впливає діапазон його підтримки у програмах. Людина не здатна" +" безпосередньо читати чи редагувати зображення у файлах jpg і png, але існує" +" безліч програм, які здатні відкривати ці файли, а це означає, що власник" +" таких файлів не матиме проблем із доступом до даних зображення." #: ../../general_concepts/file_formats.rst:53 msgid "Contents:" msgstr "Зміст:" diff --git a/locale/uk_UA/LC_MESSAGES/general_concepts/file_formats/file_gih.po b/locale/uk_UA/LC_MESSAGES/general_concepts/file_formats/file_gih.po index f1001cced..441f1cb98 100644 --- a/locale/uk_UA/LC_MESSAGES/general_concepts/file_formats/file_gih.po +++ b/locale/uk_UA/LC_MESSAGES/general_concepts/file_formats/file_gih.po @@ -1,151 +1,151 @@ # Translation of docs_krita_org_general_concepts___file_formats___file_gih.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___file_formats___file_gih" -"\n" +"Project-Id-Version: " +"docs_krita_org_general_concepts___file_formats___file_gih\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-25 03:36+0100\n" "PO-Revision-Date: 2019-03-13 20:11+0200\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/file_formats/file_gih.rst:1 msgid "The Gimp Image Hose file format in Krita." msgstr "Формат файлів футляра зображень GIMP (GIH) у Krita." #: ../../general_concepts/file_formats/file_gih.rst:15 msgid "\\*.gih" msgstr "\\*.gih" #: ../../general_concepts/file_formats/file_gih.rst:17 msgid "" "The GIMP image hose format. Krita can open and save these, as well as import " "via the :ref:`predefined brush tab `." msgstr "" -"Формат футляра зображень GIMP. Krita може відкривати і зберігати файли у" -" цьому форматі, а також імпортувати дані за допомогою :ref:`вкладки" -" стандартних пензлів `." +"Формат футляра зображень GIMP. Krita може відкривати і зберігати файли у " +"цьому форматі, а також імпортувати дані за допомогою :ref:`вкладки " +"стандартних пензлів `." #: ../../general_concepts/file_formats/file_gih.rst:19 msgid "" "Image Hose means that this fileformat allows you to store multiple images " "and then set some options to make it specify how to output the multiple " "images." msgstr "" -"«Футляр» означає, що у файлі цього формату можна зберігати декілька" -" зображень, встановлюючи певні параметри, які визначають спосіб виведення цих" -" зображень для показу." +"«Футляр» означає, що у файлі цього формату можна зберігати декілька " +"зображень, встановлюючи певні параметри, які визначають спосіб виведення цих " +"зображень для показу." #: ../../general_concepts/file_formats/file_gih.rst:25 msgid ".. image:: images/en/Gih-examples.png" msgstr ".. image:: images/en/Gih-examples.png" #: ../../general_concepts/file_formats/file_gih.rst:25 msgid "From top to bottom: Incremental, Pressure and Random" msgstr "Згори вниз: «Доповнювальний», «Тиск» і «Випадковий»" #: ../../general_concepts/file_formats/file_gih.rst:27 msgid "Gimp image hose format options:" msgstr "Варіанти формату футляра зображень GIMP:" #: ../../general_concepts/file_formats/file_gih.rst:29 msgid "Constant" msgstr "Сталий" #: ../../general_concepts/file_formats/file_gih.rst:30 msgid "This'll use the first image, no matter what." msgstr "Цей варіант означає «перше зображення», байдуже яке." #: ../../general_concepts/file_formats/file_gih.rst:31 msgid "Incremental" msgstr "Доповнювальний" #: ../../general_concepts/file_formats/file_gih.rst:32 msgid "" "This'll paint the image layers in sequence. This is good for images that can " "be strung together to create a pattern." msgstr "" -"Цей варіант означає «малювати шари зображення як послідовність». Цей варіант" -" є придатним для зображень, які можна накласти одне на одне для створення" -" візерунка." +"Цей варіант означає «малювати шари зображення як послідовність». Цей варіант " +"є придатним для зображень, які можна накласти одне на одне для створення " +"візерунка." #: ../../general_concepts/file_formats/file_gih.rst:33 msgid "Pressure" msgstr "Тиск" #: ../../general_concepts/file_formats/file_gih.rst:34 msgid "" "This'll paint the images depending on pressure. This is good for brushes " "imitating the hairs of a natural brush." msgstr "" -"Цей варіант передбачає малювання зображень залежно від тиску. Придатний для" -" пензлів, які імітують волосинки справжнього пензля." +"Цей варіант передбачає малювання зображень залежно від тиску. Придатний для " +"пензлів, які імітують волосинки справжнього пензля." #: ../../general_concepts/file_formats/file_gih.rst:35 msgid "Random" msgstr "Випадковий" #: ../../general_concepts/file_formats/file_gih.rst:36 msgid "" "This'll draw the images randomly. This is good for image-collections used in " "speedpainting as well as images that generate texture. Or perhaps more " "graphical symbols." msgstr "" -"Цей варіант передбачає випадкове малювання зображень. Придатний для збірок" -" зображень, які використовуються у малюванні на швидкість, а також зображень" -" для створення текстури, або, можливо, більш графічних символів." +"Цей варіант передбачає випадкове малювання зображень. Придатний для збірок " +"зображень, які використовуються у малюванні на швидкість, а також зображень " +"для створення текстури, або, можливо, більш графічних символів." #: ../../general_concepts/file_formats/file_gih.rst:38 msgid "Angle" msgstr "Кут" #: ../../general_concepts/file_formats/file_gih.rst:38 msgid "This'll use the dragging angle to determine with image to draw." msgstr "" -"Цей варіант використовує кут інерції для визначення зображення, яке слід" -" намалювати." +"Цей варіант використовує кут інерції для визначення зображення, яке слід " +"намалювати." #: ../../general_concepts/file_formats/file_gih.rst:40 msgid "" "When exporting a krita file as a .gih, you will also get the option to set " "the default spacing, the option to set the name (very important for looking " "it up in the UI) and the ability to choose whether or not to generate the " "mask from the colors." msgstr "" -"При експортуванні файла Krita у форматі .gih, ви також зможете встановити" -" типовий інтервал, назву (дуже важливо для пошуку зображення у графічному" -" інтерфейсі) та можливість визначити, чи слід створювати маску з кольорів." +"При експортуванні файла Krita у форматі .gih, ви також зможете встановити " +"типовий інтервал, назву (дуже важливо для пошуку зображення у графічному " +"інтерфейсі) та можливість визначити, чи слід створювати маску з кольорів." #: ../../general_concepts/file_formats/file_gih.rst:43 msgid "Use Color as Mask" msgstr "Використовувати колір як маску" #: ../../general_concepts/file_formats/file_gih.rst:43 msgid "" "This'll turn the darkest values of the image as the ones that paint, and the " "whitest as transparent. Untick this if you are using colored images for the " "brush." msgstr "" -"За допомогою цього пункту можна перетворити найтемніші кольори зображення на" -" повністю непрозорі ділянки, а найбіліші — на прозорі. Позначте цей пункт," -" якщо використовуєте розфарбовані зображення для пензля." +"За допомогою цього пункту можна перетворити найтемніші кольори зображення на " +"повністю непрозорі ділянки, а найбіліші — на прозорі. Позначте цей пункт, " +"якщо використовуєте розфарбовані зображення для пензля." #: ../../general_concepts/file_formats/file_gih.rst:45 msgid "" "We have a :ref:`Krita Brush tip page ` on how to " "create your own gih brush." msgstr "" -"Ми присвятили спеціальний :ref:`розділ підказок «Кінчики пензлів Krita» <" -"brush_tip_animated_brush>` тому, як створити власний пензель gih." +"Ми присвятили спеціальний :ref:`розділ підказок «Кінчики пензлів Krita» " +"` тому, як створити власний пензель gih." diff --git a/locale/uk_UA/LC_MESSAGES/general_concepts/file_formats/file_tif.po b/locale/uk_UA/LC_MESSAGES/general_concepts/file_formats/file_tif.po index 770bdc11a..073f4a413 100644 --- a/locale/uk_UA/LC_MESSAGES/general_concepts/file_formats/file_tif.po +++ b/locale/uk_UA/LC_MESSAGES/general_concepts/file_formats/file_tif.po @@ -1,62 +1,62 @@ # Translation of docs_krita_org_general_concepts___file_formats___file_tif.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___file_formats___file_tif" -"\n" +"Project-Id-Version: " +"docs_krita_org_general_concepts___file_formats___file_tif\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-19 03:36+0100\n" "PO-Revision-Date: 2019-03-13 19:47+0200\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/file_formats/file_tif.rst:1 msgid "The Tagged Image file format in Krita." msgstr "Формат файлів зображень із мітками (TIFF) у Krita." #: ../../general_concepts/file_formats/file_tif.rst:16 msgid "\\*.tiff" msgstr "\\*.tiff" #: ../../general_concepts/file_formats/file_tif.rst:18 msgid "" ".tiff, or Tagged Image File Format, is a raster interchange format that was " "originally designed to be a common format generated by scanners and used by " "printers." msgstr "" -".tiff або Tagged Image File Format (формат файлів зображень із мітками) є" -" растровим форматом обміну даними, який від початку було розроблено як" -" спільний формат зображень для сканерів і який використовувався для принтерів." +".tiff або Tagged Image File Format (формат файлів зображень із мітками) є " +"растровим форматом обміну даними, який від початку було розроблено як " +"спільний формат зображень для сканерів і який використовувався для принтерів." #: ../../general_concepts/file_formats/file_tif.rst:20 msgid "" "It can support multiple color spaces, and even layers. However, the latter " "is a bit odd, as the official specs, owned by Adobe, have a different way of " "saving layers to tiff than Photoshop, also owned by Adobe." msgstr "" -"У форматі передбачено підтримку декількох просторів кольорів і навіть шарів." -" Втім, останню реалізовано дещо дивно, оскільки у офіційній специфікації," -" власником якої є компанія Adobe, визначено зовсім інший спосіб зберігання" -" шарів до tiff, ніж у програмі Photoshop, власником якої теж є компанія Adobe." +"У форматі передбачено підтримку декількох просторів кольорів і навіть шарів. " +"Втім, останню реалізовано дещо дивно, оскільки у офіційній специфікації, " +"власником якої є компанія Adobe, визначено зовсім інший спосіб зберігання " +"шарів до tiff, ніж у програмі Photoshop, власником якої теж є компанія Adobe." #: ../../general_concepts/file_formats/file_tif.rst:22 msgid "" "As an interchange format, .tiff is not meant for sharing on the internet, " "and you will not find many websites that do accept it. However, printhouses " "know the file format, and will likely accept it." msgstr "" -"Як формат обміну даними, .tiff не було призначено для оприлюднення зображень" -" у інтернеті. Знайдеться зовсім небагато сайтів, де приймають зображення у" -" цьому форматі. Втім, це відомий видавничий формат, який, найімовірніше, є" -" прийнятним для друкарень." +"Як формат обміну даними, .tiff не було призначено для оприлюднення зображень " +"у інтернеті. Знайдеться зовсім небагато сайтів, де приймають зображення у " +"цьому форматі. Втім, це відомий видавничий формат, який, найімовірніше, є " +"прийнятним для друкарень." diff --git a/locale/uk_UA/LC_MESSAGES/general_concepts/projection/axonometric.po b/locale/uk_UA/LC_MESSAGES/general_concepts/projection/axonometric.po index 4d52e6a49..3dfe5d4f5 100644 --- a/locale/uk_UA/LC_MESSAGES/general_concepts/projection/axonometric.po +++ b/locale/uk_UA/LC_MESSAGES/general_concepts/projection/axonometric.po @@ -1,373 +1,373 @@ # Translation of docs_krita_org_general_concepts___projection___axonometric.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___projection___axonometric" -"\n" +"Project-Id-Version: " +"docs_krita_org_general_concepts___projection___axonometric\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-28 03:20+0100\n" "PO-Revision-Date: 2019-03-13 16:40+0200\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/projection/axonometric.rst:None msgid ".. image:: images/en/category_projection/projection-cube_07.svg" msgstr ".. image:: images/en/category_projection/projection-cube_07.svg" #: ../../general_concepts/projection/axonometric.rst:None msgid ".. image:: images/en/category_projection/projection-cube_08.svg" msgstr ".. image:: images/en/category_projection/projection-cube_08.svg" #: ../../general_concepts/projection/axonometric.rst:None msgid ".. image:: images/en/category_projection/projection-cube_09.svg" msgstr ".. image:: images/en/category_projection/projection-cube_09.svg" #: ../../general_concepts/projection/axonometric.rst:None msgid ".. image:: images/en/category_projection/projection-cube_10.svg" msgstr ".. image:: images/en/category_projection/projection-cube_10.svg" #: ../../general_concepts/projection/axonometric.rst:None msgid ".. image:: images/en/category_projection/projection-cube_11.svg" msgstr ".. image:: images/en/category_projection/projection-cube_11.svg" #: ../../general_concepts/projection/axonometric.rst:None msgid ".. image:: images/en/category_projection/projection_image_15.png" msgstr ".. image:: images/en/category_projection/projection_image_15.png" #: ../../general_concepts/projection/axonometric.rst:None msgid ".. image:: images/en/category_projection/projection_image_16.png" msgstr ".. image:: images/en/category_projection/projection_image_16.png" #: ../../general_concepts/projection/axonometric.rst:None msgid ".. image:: images/en/category_projection/projection_image_17.png" msgstr ".. image:: images/en/category_projection/projection_image_17.png" #: ../../general_concepts/projection/axonometric.rst:None msgid ".. image:: images/en/category_projection/projection_image_18.png" msgstr ".. image:: images/en/category_projection/projection_image_18.png" #: ../../general_concepts/projection/axonometric.rst:None msgid ".. image:: images/en/category_projection/projection_image_19.png" msgstr ".. image:: images/en/category_projection/projection_image_19.png" #: ../../general_concepts/projection/axonometric.rst:None msgid ".. image:: images/en/category_projection/projection_image_20.png" msgstr ".. image:: images/en/category_projection/projection_image_20.png" #: ../../general_concepts/projection/axonometric.rst:None msgid ".. image:: images/en/category_projection/projection_image_21.png" msgstr ".. image:: images/en/category_projection/projection_image_21.png" #: ../../general_concepts/projection/axonometric.rst:None msgid ".. image:: images/en/category_projection/projection_image_22.png" msgstr ".. image:: images/en/category_projection/projection_image_22.png" #: ../../general_concepts/projection/axonometric.rst:None msgid ".. image:: images/en/category_projection/projection_image_23.png" msgstr ".. image:: images/en/category_projection/projection_image_23.png" #: ../../general_concepts/projection/axonometric.rst:None msgid ".. image:: images/en/category_projection/projection_image_24.png" msgstr ".. image:: images/en/category_projection/projection_image_24.png" #: ../../general_concepts/projection/axonometric.rst:None msgid ".. image:: images/en/category_projection/projection_image_25.png" msgstr ".. image:: images/en/category_projection/projection_image_25.png" #: ../../general_concepts/projection/axonometric.rst:None msgid ".. image:: images/en/category_projection/projection_image_26.png" msgstr ".. image:: images/en/category_projection/projection_image_26.png" #: ../../general_concepts/projection/axonometric.rst:None msgid ".. image:: images/en/category_projection/projection_image_27.png" msgstr ".. image:: images/en/category_projection/projection_image_27.png" #: ../../general_concepts/projection/axonometric.rst:None msgid ".. image:: images/en/category_projection/projection_image_28.png" msgstr ".. image:: images/en/category_projection/projection_image_28.png" #: ../../general_concepts/projection/axonometric.rst:None msgid ".. image:: images/en/category_projection/projection_image_29.png" msgstr ".. image:: images/en/category_projection/projection_image_29.png" #: ../../general_concepts/projection/axonometric.rst:None msgid ".. image:: images/en/category_projection/projection_animation_02.gif" msgstr ".. image:: images/en/category_projection/projection_animation_02.gif" #: ../../general_concepts/projection/axonometric.rst:None msgid ".. image:: images/en/category_projection/projection_image_30.png" msgstr ".. image:: images/en/category_projection/projection_image_30.png" #: ../../general_concepts/projection/axonometric.rst:1 msgid "Axonometric projection." msgstr "Аксонометрична проекція." #: ../../general_concepts/projection/axonometric.rst:10 msgid "" "This is a continuation of :ref:`the orthographic and oblique tutorial " "`, be sure to check it out if you get confused!" msgstr "" -"Це продовження сторінки щодо :ref:`ортографічної та похилої проекцій <" -"projection_orthographic>`. Щоб уникнути непорозумінь, спочатку ознайомтеся із" -" попередніми сторінками!" +"Це продовження сторінки щодо :ref:`ортографічної та похилої проекцій " +"`. Щоб уникнути непорозумінь, спочатку ознайомтеся " +"із попередніми сторінками!" #: ../../general_concepts/projection/axonometric.rst:16 msgid "Axonometric" msgstr "Аксонометрична" #: ../../general_concepts/projection/axonometric.rst:18 msgid "So, the logic of adding the top is still similar to that of the side." msgstr "" #: ../../general_concepts/projection/axonometric.rst:23 msgid "" "Not very interesting. But it gets much more interesting when we use a side " "projection:" msgstr "" -"Не дуже цікаво. Але усе стає набагато цікавішим, якщо ми скористаємося бічною" -" проекцією:" +"Не дуже цікаво. Але усе стає набагато цікавішим, якщо ми скористаємося " +"бічною проекцією:" #: ../../general_concepts/projection/axonometric.rst:28 msgid "" "Because our cube is red on both front-sides, and blue on both left and right " "side, we can just use copies, this simplifies the method for cubes a lot. We " "call this form of axonometric projection 'dimetric' as it deforms two " "parallel lines equally." msgstr "" #: ../../general_concepts/projection/axonometric.rst:30 msgid "" "Isometric is sorta like dimetric where we have the same angle between all " "main lines:" msgstr "" #: ../../general_concepts/projection/axonometric.rst:35 msgid "" "True isometric is done with a 90-54.736=35.264° angle from ground plane:" msgstr "" #: ../../general_concepts/projection/axonometric.rst:40 msgid "" "(as you can see, it doesn't line up perfectly, because Inkscape, while more " "designed for making these kinds of diagrams than Krita, doesn't have tools " "to manipulate the line's angle in degrees)" msgstr "" #: ../../general_concepts/projection/axonometric.rst:42 msgid "" "This is a bit of an awkward angle, and on top of that, it doesn't line up " "with pixels sensibly, so for videogames an angle of 30° from the ground " "plane is used." msgstr "" #: ../../general_concepts/projection/axonometric.rst:47 msgid "Alright, so, let's make an isometric out of our boy then." msgstr "" #: ../../general_concepts/projection/axonometric.rst:49 msgid "We make a new document, and add a vector layer." msgstr "Ми створимо документ і додамо векторний шар." #: ../../general_concepts/projection/axonometric.rst:51 msgid "" "On the vector layer, we select the straight line tool, start a line and then " "hold :kbd:`Shift` to make it snap to angles. This'll allow us to make a 30° " "setup like above:" msgstr "" #: ../../general_concepts/projection/axonometric.rst:56 msgid "" "We then import some of the frames from the animation via :menuselection:" "`Layers --> Import/Export --> Import layer`." msgstr "" #: ../../general_concepts/projection/axonometric.rst:59 msgid "" "Then crop it by setting the crop tool to :guilabel:`Layer`, and use :" "menuselection:`Filters --> Colors --> Color to alpha`" msgstr "" #: ../../general_concepts/projection/axonometric.rst:59 msgid "" "to remove any background. I also set the layers to 50% opacity. We then " "align the vectors to them:" msgstr "" #: ../../general_concepts/projection/axonometric.rst:64 msgid "" "(Tip, to resize a vector but keep its angle, you just select it with the " "shape handling tool (the white arrow) drag on the corners of the bounding " "box to start moving them, and then press :kbd:`Shift` to constrain the " "ratio. This'll allow you to keep the angle)" msgstr "" #: ../../general_concepts/projection/axonometric.rst:66 msgid "" "The lower image is 'the back seen from the front', we'll be using this to " "determine where the ear should go." msgstr "" #: ../../general_concepts/projection/axonometric.rst:68 msgid "" "Now, we obviously have too little space, so select the crop tool, select " "'image' and tick 'grow' and do the following:" msgstr "" #: ../../general_concepts/projection/axonometric.rst:73 msgid "" "Grow is a more practical way of resizing the canvas in width and height " "immediately." msgstr "" #: ../../general_concepts/projection/axonometric.rst:75 msgid "" "Then we align the other heads and transform them by using the transform tool " "options:" msgstr "" #: ../../general_concepts/projection/axonometric.rst:80 msgid "(330° here is 360°-30°)" msgstr "(330° тут це 360°-30°)" #: ../../general_concepts/projection/axonometric.rst:83 msgid "" "Our rectangle we'll be working in slowly becomes visible. Now, this is a bit " "of a difficult angle to work at, so we go to :menuselection:`image --> " "rotate --> custom rotation`" msgstr "" #: ../../general_concepts/projection/axonometric.rst:83 msgid "and fill in 30° clockwise:" msgstr "" #: ../../general_concepts/projection/axonometric.rst:90 msgid "" "(of course, we could've just rotated the left two images 30°, this is mostly " "to be less confusing compared to the cube)" msgstr "" #: ../../general_concepts/projection/axonometric.rst:92 msgid "" "So, we do some cropping, some cleanup and add two parallel assistants like " "we did with the orthographic:" msgstr "" #: ../../general_concepts/projection/axonometric.rst:97 msgid "" "So the idea here is that you draw parallel lines from both sides to find " "points in the drawing area. You can use the previews of the assistants for " "this to keep things clean, but I drew the lines anyway for your convenience." msgstr "" #: ../../general_concepts/projection/axonometric.rst:102 msgid "" "The best is to make a few sampling points, like with the eyebrows here, and " "then draw the eyebrow over it." msgstr "" #: ../../general_concepts/projection/axonometric.rst:108 msgid "Alternative axonometric with the transform tool" msgstr "Альтернативна аксонометрія із інструментом перетворення" #: ../../general_concepts/projection/axonometric.rst:110 msgid "" "Now, there's an alternative way of getting there that doesn't require as " "much space." msgstr "" #: ../../general_concepts/projection/axonometric.rst:112 msgid "" "We open our orthographic with 'open existing document as untitled document' " "so that we don't save over it." msgstr "" #: ../../general_concepts/projection/axonometric.rst:114 msgid "" "Our game-safe isometric has its angle at two pixels horizontal is one pixel " "vertical. So, we shear the ortho graphics with transform masks to -.5/+.5 " "pixels (this is proportional)" msgstr "" #: ../../general_concepts/projection/axonometric.rst:119 msgid "" "Use the grid to setup two parallel rulers that represent both diagonals (you " "can snap them with the :kbd:`Shift + S`):" msgstr "" #: ../../general_concepts/projection/axonometric.rst:124 msgid "Add the top view as well:" msgstr "" #: ../../general_concepts/projection/axonometric.rst:129 msgid "if you do this for all slices, you get something like this:" msgstr "" #: ../../general_concepts/projection/axonometric.rst:134 msgid "" "Using the parallel rulers, you can then figure out the position of a point " "in 3d-ish space:" msgstr "" #: ../../general_concepts/projection/axonometric.rst:139 msgid "As you can see, this version both looks more 3d as well as more creepy." msgstr "" #: ../../general_concepts/projection/axonometric.rst:141 msgid "" "That's because there are less steps involved as the previous version -- " "We're deriving our image directly from the orthographic view -- so there are " "less errors involved." msgstr "" #: ../../general_concepts/projection/axonometric.rst:143 msgid "" "The creepiness is because we've had the tiniest bit of stylisation in our " "sideview, so the eyes come out HUGE. This is because when we stylise the " "side view of an eye, we tend to draw it not perfectly from the side, but " "rather slightly at an angle. If you look carefully at the turntable, the " "same problem crops up there as well." msgstr "" #: ../../general_concepts/projection/axonometric.rst:145 msgid "" "Generally, stylised stuff tends to fall apart in 3d view, and you might need " "to make some choices on how to make it work." msgstr "" #: ../../general_concepts/projection/axonometric.rst:147 msgid "" "For example, we can just easily fix the side view (because we used transform " "masks, this is easy.)" msgstr "" #: ../../general_concepts/projection/axonometric.rst:152 msgid "And then generate a new drawing from that…" msgstr "" #: ../../general_concepts/projection/axonometric.rst:157 msgid "" "Compare to the old one and you should be able to see that the new result’s " "eyes are much less creepy:" msgstr "" #: ../../general_concepts/projection/axonometric.rst:162 msgid "" "It still feels very squashed compared to the regular parallel projection " "above, and it might be an idea to not just skew but also stretch the orthos " "a bit." msgstr "" #: ../../general_concepts/projection/axonometric.rst:164 msgid "Let's continue with perspective projection in the next one!" msgstr "" diff --git a/locale/uk_UA/LC_MESSAGES/reference_manual/audio_for_animation.po b/locale/uk_UA/LC_MESSAGES/reference_manual/audio_for_animation.po index 1698a0051..d21e7d416 100644 --- a/locale/uk_UA/LC_MESSAGES/reference_manual/audio_for_animation.po +++ b/locale/uk_UA/LC_MESSAGES/reference_manual/audio_for_animation.po @@ -1,155 +1,168 @@ # Translation of docs_krita_org_reference_manual___audio_for_animation.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_reference_manual___audio_for_animation\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-28 03:20+0100\n" -"PO-Revision-Date: 2019-02-20 11:24+0200\n" +"PO-Revision-Date: 2019-03-14 19:27+0200\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 18.12.1\n" +"X-Generator: Lokalize 19.03.70\n" #: ../../reference_manual/audio_for_animation.rst:1 msgid "The audio playback with animation in Krita." msgstr "Звуковий супровід із анімацією у Krita." #: ../../reference_manual/audio_for_animation.rst:17 msgid "Audio for Animation" msgstr "Звук у анімації" #: ../../reference_manual/audio_for_animation.rst:21 msgid "" "Audio for animation is an unfinished feature. It has multiple bugs and may " "not work on your system." msgstr "" +"Можливість додавання звукового супроводу до анімацій є можливістю, яка" +" перебуває у розробці. Відомі декілька вад у реалізації, усе описане може не" +" працювати у вашій системі." #: ../../reference_manual/audio_for_animation.rst:23 msgid "" "You can add audio files to your animation to help sync lips or music. This " "functionality is available in the timeline docker." msgstr "" +"Ви можете додати звукові файли до вашої анімації для синхронізації руху губ" +" або музичного супроводу. Доступ до цієї можливості можна отримати за" +" допомогою бічної панелі монтажного столу." #: ../../reference_manual/audio_for_animation.rst:26 msgid "Importing Audio Files" msgstr "Імпортування звукових файлів" #: ../../reference_manual/audio_for_animation.rst:28 msgid "" "Krita supports MP3, OGM, and WAV audio files. When you open up your timeline " "docker, there will be a speaker button in the top left area." msgstr "" +"У Krita передбачено підтримку файлів звукових даних у форматах MP3, OGM та" +" WAV. Доступ до завантаження звукових даних відкриває кнопка із зображенням" +" гучномовця у верхньому лівому куті бічної панелі монтажного столу." #: ../../reference_manual/audio_for_animation.rst:30 msgid "" "If you press the speaker button, you will get the available audio options " "for the animation." msgstr "" +"Якщо ви натиснете цю кнопку, програма покаже доступні можливості звукового" +" супроводу анімації." #: ../../reference_manual/audio_for_animation.rst:32 msgid "Open" msgstr "Відкрити" #: ../../reference_manual/audio_for_animation.rst:33 msgid "Mute" msgstr "Вимкнути звук" #: ../../reference_manual/audio_for_animation.rst:34 msgid "Remove audio" msgstr "Вилучити звук" #: ../../reference_manual/audio_for_animation.rst:35 msgid "Volume slider" msgstr "Повзунок гучності" #: ../../reference_manual/audio_for_animation.rst:37 msgid "" "Krita saves the location of your audio file. If you move the audio file or " "rename it, Krita will not be able to find it. Krita will tell you the file " "was moved or deleted the next time you try to open the Krita file up. Using " "Audio" msgstr "" #: ../../reference_manual/audio_for_animation.rst:40 msgid "" "After you import the audio, you can scrub through the timeline and it will " "play the audio chunk at the time spot. When you press the Play button, the " "entire the audio file will playback as it will in the final version. There " "is no visual display of the audio file on the screen, so you will need to " "use your ears and the scrubbing functionality to position frames." msgstr "" #: ../../reference_manual/audio_for_animation.rst:44 msgid "Exporting with Audio" msgstr "Експортування даних зі звуком" #: ../../reference_manual/audio_for_animation.rst:46 msgid "" "To get the audio file included when you are exporting, you need to include " "it in the Render Animation options. In the :menuselection:`File --> Render " "Animation` options there is a checkbox :guilabel:`Include Audio`. Make sure " "that is checked before you export and you should be good to go." msgstr "" #: ../../reference_manual/audio_for_animation.rst:49 msgid "Packages needed for Audio on Linux" -msgstr "" +msgstr "Пакунки, які слід встановити для уможливлення роботи зі звуком у Linux" #: ../../reference_manual/audio_for_animation.rst:51 msgid "" "The following packages are necessary for havng the audio support on Linux:" msgstr "" +"Для реалізації підтримки звукового супроводу у Linux необхідними є такі" +" пакунки:" #: ../../reference_manual/audio_for_animation.rst:54 msgid "For people who build Krita on Linux:" -msgstr "" +msgstr "Для тих, хто збирає Krita у Linux:" #: ../../reference_manual/audio_for_animation.rst:56 msgid "libasound2-dev" msgstr "libasound2-dev" #: ../../reference_manual/audio_for_animation.rst:57 msgid "libgstreamer1.0-dev gstreamer1.0-pulseaudio" msgstr "libgstreamer1.0-dev gstreamer1.0-pulseaudio" #: ../../reference_manual/audio_for_animation.rst:58 msgid "libgstreamer-plugins-base1.0-dev" msgstr "libgstreamer-plugins-base1.0-dev" #: ../../reference_manual/audio_for_animation.rst:59 msgid "libgstreamer-plugins-good1.0-dev" msgstr "libgstreamer-plugins-good1.0-dev" #: ../../reference_manual/audio_for_animation.rst:60 msgid "libgstreamer-plugins-bad1.0-dev" msgstr "libgstreamer-plugins-bad1.0-dev" #: ../../reference_manual/audio_for_animation.rst:62 msgid "For people who use Krita on Linux:" msgstr "Для тих, хто користується Krita у Linux:" #: ../../reference_manual/audio_for_animation.rst:64 msgid "libqt5multimedia5-plugins" msgstr "libqt5multimedia5-plugins" #: ../../reference_manual/audio_for_animation.rst:65 msgid "libgstreamer-plugins-base1.0" msgstr "libgstreamer-plugins-base1.0" #: ../../reference_manual/audio_for_animation.rst:66 msgid "libgstreamer-plugins-good1.0" msgstr "libgstreamer-plugins-good1.0" #: ../../reference_manual/audio_for_animation.rst:67 msgid "libgstreamer-plugins-bad1.0" msgstr "libgstreamer-plugins-bad1.0" diff --git a/locale/uk_UA/LC_MESSAGES/reference_manual/blending_modes/darken.po b/locale/uk_UA/LC_MESSAGES/reference_manual/blending_modes/darken.po index 4d52179fb..7c91c3e75 100644 --- a/locale/uk_UA/LC_MESSAGES/reference_manual/blending_modes/darken.po +++ b/locale/uk_UA/LC_MESSAGES/reference_manual/blending_modes/darken.po @@ -1,264 +1,283 @@ # Translation of docs_krita_org_reference_manual___blending_modes___darken.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_reference_manual___blending_modes___darken\n" +"Project-Id-Version: docs_krita_org_reference_manual___blending_modes___darken" +"\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-19 03:36+0100\n" -"PO-Revision-Date: 2019-03-03 14:07+0200\n" +"PO-Revision-Date: 2019-03-14 19:55+0200\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" #: ../../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 "" "Сторінка, яку присвячено режимам злиття із затемненням у Krita: затемнення, " "вигоряння, затемнення кольору, затемнення гами та лінійне вигоряння." #: ../../reference_manual/blending_modes/darken.rst:15 #: ../../reference_manual/blending_modes/darken.rst:52 msgid "Darken" msgstr "Затемнення" #: ../../reference_manual/blending_modes/darken.rst:22 msgid "Burn" msgstr "Вигоряння" #: ../../reference_manual/blending_modes/darken.rst:24 msgid "A variation on Divide, sometimes called 'Color Burn' in some programs." msgstr "" +"Різновид «Ділення», іноді називається «Вигоряння кольору» у деяких програмах." #: ../../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 "" #: ../../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_Темно-сірий(0.4, 0.4, 0.4)] / Світло-сірий(0.5, 0.5, 0.5)} = (-0.2, " +"-0.2, -0.2) → Чорний(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 "Ліворуч: **звичайне змішування**. Праворуч: **Вигоряння**." #: ../../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_Світло-синій(0.1608, 0.6274, 0.8274)] / Помаранчевий(1, 0.5961," +" 0.0706)} = " +"(0.1608, 0.3749, -1.4448) → Зелений(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 "" #: ../../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 "" +"Чи Світло-сірий(0.5, 0.5, 0.5) темніший за Темно-сірий(0.4, 0.4, 0.4)? = " +"(ні, ні, ні) → Темно-сірий(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 "Ліворуч: **звичайне змішування**. Праворуч: **Затемнення**." #: ../../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 "" +"Чи Помаранчевий(1, 0.5961, 0.0706) темніший за Світло-синій(0.1608, 0.6274," +" 0.8274)? " +"= (ні, так, так) → Зелений(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 "Затемнення кольору" #: ../../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 "Ліворуч: **звичайне змішування**. Праворуч: **Затемнення кольору**." #: ../../reference_manual/blending_modes/darken.rst:90 msgid "Gamma Dark" msgstr "Затемнення гами" #: ../../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 "" #: ../../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 "" +"Темно-сірий(0.4, 0.4, 0.4)^[1 / Світло-сірий(0.5, 0.5, 0.5)] =" +" Ще-темніший-сірий(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 "Ліворуч: **звичайне змішування**. Праворуч: **Затемнення гами**." #: ../../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 "" +"Світло-синій(0.1608, 0.6274, 0.8274)^[1 / Помаранчевий(1, 0.5961, 0.0706)] =" +" Зелений(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 "Лінійне вигоряння" #: ../../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 "" "Обчислює суму значень у двох шарах і віднімає від отриманого значення 1. " "Здається, дає той самий результат, що і :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 "" +"[Темно-сірий(0.4, 0.4, 0.4) + Світло-сірий(0.5, 0.5, 0.5)]_1 = (-0.1000, " +"-0.1000, -0.1000) → Чорний(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 "" +msgstr "Ліворуч: **звичайне змішування**. Праворуч: **Лінійне вигоряння**." #: ../../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 "" +"[Світло-синій(0.1608, 0.6274, 0.8274) + Помаранчевий(1, 0.5961, 0.0706)]_1 =" +" (0.1608, 0.2235, -0.1020) → Темно-зелений(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/uk_UA/LC_MESSAGES/reference_manual/brushes/brush_engines/clone_engine.po b/locale/uk_UA/LC_MESSAGES/reference_manual/brushes/brush_engines/clone_engine.po index edad2a1b8..8ec76660f 100644 --- a/locale/uk_UA/LC_MESSAGES/reference_manual/brushes/brush_engines/clone_engine.po +++ b/locale/uk_UA/LC_MESSAGES/reference_manual/brushes/brush_engines/clone_engine.po @@ -1,155 +1,155 @@ # Translation of docs_krita_org_reference_manual___brushes___brush_engines___clone_engine.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_reference_manual___brushes___brush_engines_" -"__clone_engine\n" +"Project-Id-Version: " +"docs_krita_org_reference_manual___brushes___brush_engines___clone_engine\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-25 03:36+0100\n" "PO-Revision-Date: 2019-03-13 16:29+0200\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" #: ../../:1 msgid "Clone from all visible layers." msgstr "Клонування з усіх видимих шарів." #: ../../:2 msgid "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: mouseleft" msgstr "" ".. image:: images/icons/Krita_mouse_left.png\n" " :alt: mouseleft" #: ../../reference_manual/brushes/brush_engines/clone_engine.rst:1 #: ../../reference_manual/brushes/brush_engines/clone_engine.rst:18 msgid "The Clone Brush Engine manual page." msgstr "Розділ підручника щодо рушія пензлів клонування." #: ../../reference_manual/brushes/brush_engines/clone_engine.rst:16 msgid "Clone Brush Engine" msgstr "Рушій пензлів клонування" #: ../../reference_manual/brushes/brush_engines/clone_engine.rst:30 msgid ".. image:: images/icons/clonebrush.svg" msgstr ".. image:: images/icons/clonebrush.svg" #: ../../reference_manual/brushes/brush_engines/clone_engine.rst:31 msgid "" "The clone brush is a brush engine that allows you to paint with a " "duplication of a section of a paint-layer. This is useful in manipulation of " "photos and textures. You have to select a source and then you can paint to " "copy or clone the source to a different area. Other applications normally " "have a separate tool for this, Krita has a brush engine for this." msgstr "" -"Пензель клонування — рушій пензлів, за допомогою якого ви можете намалювати" -" дублікат якоїсь ділянки на шарі малювання. Цей пензель корисний для обробки" -" фотографій та створення текстур. Ви можете позначити початкову ділянку, а" -" потім намалювати її копію або клон у іншому місці зображення. У інших" -" програмах для цього є окремий інструмент, але у Krita можна просто" -" скористатися відповідним рушієм пензлів." +"Пензель клонування — рушій пензлів, за допомогою якого ви можете намалювати " +"дублікат якоїсь ділянки на шарі малювання. Цей пензель корисний для обробки " +"фотографій та створення текстур. Ви можете позначити початкову ділянку, а " +"потім намалювати її копію або клон у іншому місці зображення. У інших " +"програмах для цього є окремий інструмент, але у Krita можна просто " +"скористатися відповідним рушієм пензлів." #: ../../reference_manual/brushes/brush_engines/clone_engine.rst:34 msgid "Usage and Hotkeys" msgstr "Користування та клавіатурні скорочення" #: ../../reference_manual/brushes/brush_engines/clone_engine.rst:36 msgid "" "To see the source, you need to set the brush-cursor settings to brush " "outline." msgstr "" "Щоб бачити джерело, вам слід налаштувати у параметрах вказівника-пензля " "показ ескіза пензля." #: ../../reference_manual/brushes/brush_engines/clone_engine.rst:38 msgid "" "The clone tool can now clone from the projection and it's possible to change " "the clone source layer. Press :kbd:`Ctrl + Alt +` |mouseleft| to select a " "new clone source on the current layer. :kbd:`Ctrl +` |mouseleft| to select a " "new clone source point on the layer that was active when you selected the " "clone op." msgstr "" -"Інструмент клонування може клонувати дані з проекції, також можна змінити шар" -" початкового зображення для клону. Натисніть комбінацію :kbd:`Ctrl + Alt +`" -" |mouseleft|, щоб вибрати нове джерело для клонування на поточному шарі." -" Комбінацією :kbd:`Ctrl +` |mouseleft| можна скористатися для вибору нової" -" точки джерела клонування на шарі, який був активним, коли ви вибрали пензель" -" клонування." +"Інструмент клонування може клонувати дані з проекції, також можна змінити " +"шар початкового зображення для клону. Натисніть комбінацію :kbd:`Ctrl + Alt " +"+` |mouseleft|, щоб вибрати нове джерело для клонування на поточному шарі. " +"Комбінацією :kbd:`Ctrl +` |mouseleft| можна скористатися для вибору нової " +"точки джерела клонування на шарі, який був активним, коли ви вибрали пензель " +"клонування." #: ../../reference_manual/brushes/brush_engines/clone_engine.rst:42 msgid ":kbd:`Ctrl + Alt +` |mouseleft| is temporarily disabled on 2.9.7" msgstr ":kbd:`Ctrl + Alt +` |mouseleft| тимчасово вимкнено з версії 2.9.7" #: ../../reference_manual/brushes/brush_engines/clone_engine.rst:45 msgid "Settings" msgstr "Параметри" #: ../../reference_manual/brushes/brush_engines/clone_engine.rst:47 msgid ":ref:`option_size`" msgstr ":ref:`option_size`" #: ../../reference_manual/brushes/brush_engines/clone_engine.rst:48 msgid ":ref:`blending_modes`" msgstr ":ref:`blending_modes`" #: ../../reference_manual/brushes/brush_engines/clone_engine.rst:49 msgid ":ref:`option_opacity_n_flow`" msgstr ":ref:`option_opacity_n_flow`" #: ../../reference_manual/brushes/brush_engines/clone_engine.rst:52 msgid "Painting mode" msgstr "Режим малювання" #: ../../reference_manual/brushes/brush_engines/clone_engine.rst:54 msgid "Healing" msgstr "Лікування" #: ../../reference_manual/brushes/brush_engines/clone_engine.rst:55 msgid "" "This turns the clone brush into a healing brush: often used for removing " "blemishes in photo retouching, and maybe blemishes in painting." msgstr "" "Перетворює пензель клонування у лікувальний пензель. Часто використовується " "для вилучення дефектів при ретушуванні фотографії. Може бути використано для " "усування дефектів при малюванні." #: ../../reference_manual/brushes/brush_engines/clone_engine.rst:57 msgid "Only works when there's a perspective grid visible." msgstr "Працює, лише якщо є видимою ґратка перспективи." #: ../../reference_manual/brushes/brush_engines/clone_engine.rst:59 msgid "Perspective correction" msgstr "Виправлення перспективи" #: ../../reference_manual/brushes/brush_engines/clone_engine.rst:60 msgid "This feature is currently disabled" msgstr "Цю можливість у поточній версії вимкнено." #: ../../reference_manual/brushes/brush_engines/clone_engine.rst:61 msgid "Source Point move." msgstr "Пересування початкової точки." #: ../../reference_manual/brushes/brush_engines/clone_engine.rst:62 msgid "" "This will determine whether you will replicate the source point per dab or " "per stroke. Can be useful when used with the healing brush." msgstr "" "Цей параметр визначає, відтворюватиметься початкова точка мазка чи штриха. " "Може бути корисним, якщо використовується у поєднанні із лікувальним пензлем." #: ../../reference_manual/brushes/brush_engines/clone_engine.rst:64 msgid "" "Tick this to force cloning of all layers instead of just the active one." msgstr "Позначте цей пункт, якщо клонувати слід усі шари, а не лише активний." diff --git a/locale/uk_UA/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po b/locale/uk_UA/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po index 66d3fa528..aaec220a1 100644 --- a/locale/uk_UA/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po +++ b/locale/uk_UA/LC_MESSAGES/reference_manual/brushes/brush_engines/deform_brush_engine.po @@ -1,227 +1,228 @@ # Translation of docs_krita_org_reference_manual___brushes___brush_engines___deform_brush_engine.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_reference_manual___brushes___brush_engines___deform_brush_engine\n" +"Project-Id-Version: docs_krita_org_reference_manual___brushes___brush_engines_" +"__deform_brush_engine\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2019-02-23 03:24+0100\n" -"PO-Revision-Date: 2019-03-12 17:18+0200\n" +"POT-Creation-Date: 2019-03-14 03:27+0100\n" +"PO-Revision-Date: 2019-03-14 07:10+0200\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" #: ../../:1 msgid "Use Undeformed Image" msgstr "Використати недеформоване зображення" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:1 msgid "The Deform Brush Engine manual page." msgstr "Сторінка підручника щодо рушія пензлів викривлення." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:16 msgid "Deform Brush Engine" msgstr "Рушій пензлів викривлення" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:19 msgid ".. image:: images/icons/deformbrush.svg" msgstr ".. image:: images/icons/deformbrush.svg" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:20 msgid "" "The Deform Brush is a brush that allows you to pull and push pixels around. " "It's quite similar to the :ref:`liquify_mode`, but where liquify has higher " "quality, the deform brush has the speed." msgstr "" "Пензель викривлення — це пензель, який надає вам змогу притягувати і " "розштовхувати пікселі на зображенні. Його робота подібна до :ref:" "`liquify_mode`, але інструмент розплавлення дає якісніші результати, хоча " "пензель деформування працює швидше." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:24 msgid "Options" msgstr "Параметри" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:26 msgid ":ref:`option_brush_tip`" msgstr ":ref:`option_brush_tip`" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:27 msgid ":ref:`option_deform`" msgstr ":ref:`option_deform`" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:28 msgid ":ref:`blending_modes`" msgstr ":ref:`blending_modes`" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:29 msgid ":ref:`option_opacity_n_flow`" msgstr ":ref:`option_opacity_n_flow`" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:30 msgid ":ref:`option_size`" msgstr ":ref:`option_size`" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:31 msgid ":ref:`option_rotation`" msgstr ":ref:`option_rotation`" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:32 msgid ":ref:`option_airbrush`" msgstr ":ref:`option_airbrush`" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:38 msgid "Deform Options" msgstr "Параметри викривлення" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:42 msgid ".. image:: images/en/Krita_deform_brush_examples.png" msgstr ".. image:: images/en/Krita_deform_brush_examples.png" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:42 msgid "" "1: undeformed, 2: Move, 3: Grow, 4: Shrink, 5: Swirl Counter Clock Wise, 6: " "Swirl Clockwise, 7: Lens Zoom In, 8: Lens Zoom Out" msgstr "" "1: Недеформоване зображення, 2: Пересування, 3: Збільшення, 4: Зменшення, 5: " "Викривлення вихором проти годинникової стрілки, 6: Викривлення вихором за " "годинниковою стрілкою, 7: Збільшення об'єктивом, 8: Зменшення об'єктивом" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:44 msgid "These decide what strangeness may happen underneath your brush cursor." msgstr "Ці варіанти визначають, якою буде деформація під вказівником миші." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:46 msgid "Grow" msgstr "Збільшити" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:47 msgid "This bubbles up the area underneath the brush-cursor." msgstr "Цей варіант збільшує область під пензлем-вказівником." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:48 msgid "Shrink" msgstr "Зменшити" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:49 msgid "This pinches the Area underneath the brush-cursor." msgstr "Цей варіант стягує область під пензлем-вказівником." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:50 msgid "Swirl Counter Clock Wise" msgstr "Вихор проти годинникової стрілки" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:51 msgid "Swirls the area counter clock wise." msgstr "Закручує область під вказівником вихором проти годинникової стрілки." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:52 msgid "Swirl Clock Wise" msgstr "Вихор за годинниковою стрілкою" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:53 msgid "Swirls the area clockwise." msgstr "Закручує область під вказівником вихором за годинниковою стрілкою." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:54 msgid "Move" msgstr "Пересунути" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:55 msgid "Nudges the area to the painting direction." msgstr "Виштовхує область у напрямку малювання." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:56 msgid "Color Deformation" msgstr "Викривлення кольорів" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:57 -msgid "This seems to randomly rearrange the pixels underneath the brush," +#| msgid "This seems to randomly rearrange the pixels underneath the brush," +msgid "This seems to randomly rearrange the pixels underneath the brush." msgstr "" "Якщо використано цей варіант, програма випадково переставить пікселі під " "пензлем." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:58 msgid "Lens Zoom In" msgstr "Збільшення об’єктива" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:59 msgid "Literally paints a enlarged version of the area." msgstr "Буквально малює збільшену версію ділянки." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:61 msgid "Lens Zoom Out" msgstr "Зменшення об’єктива" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:61 msgid "Paints a minimized version of the area." msgstr "Вмальовує зменшену версію області." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:65 msgid ".. image:: images/en/Krita_deform_brush_colordeform.png" msgstr ".. image:: images/en/Krita_deform_brush_colordeform.png" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:65 msgid "Showing color deform." msgstr "Показ деформації кольору." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:68 msgid "Deform Amount" msgstr "Величина викривлення" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:68 msgid "Defines the strength of the deformation." msgstr "Визначає потужність викривлення." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:72 msgid ".. image:: images/en/Krita_deform_brush_bilinear.png" msgstr ".. image:: images/en/Krita_deform_brush_bilinear.png" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:72 #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:74 msgid "Bilinear Interpolation" msgstr "Білінійна інтерполяція" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:75 msgid "Smoothens the result. This causes calculation errors in 16bit." msgstr "" "Згладжує результат. Спричиняє помилки обчислення на 16-бітових зображеннях." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:77 msgid "Use Counter" msgstr "Використати лічильник" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:77 msgid "Slows down the deformation subtlety." msgstr "Дещо сповільнює деформування." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:81 msgid ".. image:: images/en/Krita_deform_brush_useundeformed.png" msgstr ".. image:: images/en/Krita_deform_brush_useundeformed.png" #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:81 msgid "Without 'use undeformed' to the left and with to the right" msgstr "" "Без позначеним пунктом «Використати недеформоване зображення» ліворуч і без " "позначення пункту праворуч." #: ../../reference_manual/brushes/brush_engines/deform_brush_engine.rst:84 msgid "" "Samples from the previous version of the image instead of the current. This " "works better with some deform options than others. Move for example seems to " "almost stop working, but it works really well with Grow." msgstr "" "Зразки з попередньої версії зображення, замість поточної. Із деякими " "параметрами деформування це працює краще, ніж з іншими. Наприклад, " "«Пересунути» майже припиняє працювати, але «Збільшити» працює насправді " "добре." diff --git a/locale/uk_UA/LC_MESSAGES/reference_manual/brushes/brush_engines/dyna_brush_engine.po b/locale/uk_UA/LC_MESSAGES/reference_manual/brushes/brush_engines/dyna_brush_engine.po index 86ca97f8c..4f247e69d 100644 --- a/locale/uk_UA/LC_MESSAGES/reference_manual/brushes/brush_engines/dyna_brush_engine.po +++ b/locale/uk_UA/LC_MESSAGES/reference_manual/brushes/brush_engines/dyna_brush_engine.po @@ -1,182 +1,194 @@ # Translation of docs_krita_org_reference_manual___brushes___brush_engines___dyna_brush_engine.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_reference_manual___brushes___brush_engines___dyna_brush_engine\n" +"Project-Id-Version: docs_krita_org_reference_manual___brushes___brush_engines_" +"__dyna_brush_engine\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-25 03:36+0100\n" -"PO-Revision-Date: 2019-03-12 19:36+0200\n" +"PO-Revision-Date: 2019-03-14 13:19+0200\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" #: ../../:1 msgid "Paint Connection" msgstr "З’єднання малюнка" #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:1 msgid "The Dyna Brush Engine manual page." msgstr "Розділ підручника щодо рушія динамічних пензлів." #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:15 msgid "Dyna Brush Engine" msgstr "Рушій динамічних пензлів" #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:18 msgid ".. image:: images/icons/dynabrush.svg" msgstr ".. image:: images/icons/dynabrush.svg" #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:19 msgid "" "Dyna brush uses dynamic setting like mass and drag to draw strokes. The " "results are fun and random spinning strokes.To experiment more with this " "brush you can play with values in 'dynamic settings' section of the brush " "editor under Dyna Brush." msgstr "" +"У динамічному пензлі для визначення характеристик мазкі використовуються" +" динамічні параметри, зокрема маса та інерція. Результатом малювання ним є" +" цікаві мазки із випадковим обертанням. Поекспериментувати з пензлем можна за" +" допомогою значень у розділі :guilabel:`Динамічні параметри` редактора" +" пензлів для динамічного пензля." #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:23 msgid "" "This brush engine has been removed in 4.0. This engine mostly had smoothing " "results that the dyna brush tool has in the toolbox. The stabilizer settings " "can also give you further smoothing options from the tool options." msgstr "" +"Цей рушій пензлів було вилучено у версії 4.0. Здебільшого, його використання" +" давало ті самі результати, що і інструмент динамічного пензля на панелі" +" інструментів. Крім того, нові параметри стабілізації у параметрах" +" інструмента надають вам ширші можливості зі згладжування." #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:26 msgid "Options" msgstr "Параметри" #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:28 msgid ":ref:`option_size_dyna`" msgstr ":ref:`option_size_dyna`" #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:29 msgid ":ref:`blending_modes`" msgstr ":ref:`blending_modes`" #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:30 msgid ":ref:`option_opacity_n_flow`" msgstr ":ref:`option_opacity_n_flow`" #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:31 msgid ":ref:`option_airbrush`" msgstr ":ref:`option_airbrush`" #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:36 msgid "Brush Size (Dyna)" msgstr "Розмір пензля" #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:39 msgid "Dynamics Settings" msgstr "Динамічні параметри" #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:41 msgid "Initial Width" msgstr "Початкова ширина" #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:42 msgid "Initial size of the dab." msgstr "Початковий розмір мазка." #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:43 msgid "Mass" msgstr "Маса" #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:44 msgid "How much energy there is in the satellite like movement." msgstr "Енергія супутнього руху." #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:45 msgid "Drag" msgstr "Перетягування" #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:46 msgid "How close the dabs follow the position of the brush-cursor." msgstr "" "Наскільки близько розташовуватимуться мазки щодо позиції вказівника-пензля." #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:48 msgid "Width Range" msgstr "Діапазон ширини" #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:48 msgid "How much the dab expands with speed." msgstr "Наскільки розширюється мазок зі зростанням швидкості." #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:51 msgid "Shape" msgstr "Форма" #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:53 msgid "Diameter" msgstr "Діаметр" #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:54 msgid "Size of the shape." msgstr "Розмір форми." #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:55 msgid "Angle" msgstr "Кут" #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:56 msgid "Angle of the shape. Requires Fixed Angle active to work." msgstr "" "Кут форми. Для того, щоб можна було скористатися, слід увімкнути :guilabel:" "`Фіксований кут`." #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:57 msgid "Circle" msgstr "Коло" #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:58 msgid "Make a circular dab appear." msgstr "Зробити мазок круговим." #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:59 msgid "Two" msgstr "Два" #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:60 msgid "Draws an extra circle between other circles." msgstr "Малювати додаткове коло між іншими колами." #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:61 msgid "Line" msgstr "Лінія" #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:62 msgid "" "Connecting lines are drawn next to each other. The number boxes on the right " "allows you to set the spacing between the lines and how many are drawn." msgstr "" +"З'єднання ліній, які намальовано поряд одна з одною. За допомогою числових" +" полів, розташованих праворуч, ви можете встановити інтервал між лініями та" +" їхню кількість." #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:63 msgid "Polygon" msgstr "Багатокутник" #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:64 msgid "Draws a black polygon as dab." msgstr "Малювати чорний багатокутник як мазок." #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:65 msgid "Wire" msgstr "Дріт" #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:66 msgid "Draws the wireframe of the polygon." msgstr "Малювати каркас багатокутника." #: ../../reference_manual/brushes/brush_engines/dyna_brush_engine.rst:68 msgid "Draws the connection line." msgstr "Малювати лінію з'єднання." diff --git a/locale/uk_UA/LC_MESSAGES/reference_manual/brushes/brush_engines/spray_brush_engine.po b/locale/uk_UA/LC_MESSAGES/reference_manual/brushes/brush_engines/spray_brush_engine.po index 1e20fcc84..3de0875a5 100644 --- a/locale/uk_UA/LC_MESSAGES/reference_manual/brushes/brush_engines/spray_brush_engine.po +++ b/locale/uk_UA/LC_MESSAGES/reference_manual/brushes/brush_engines/spray_brush_engine.po @@ -1,346 +1,346 @@ # Translation of docs_krita_org_reference_manual___brushes___brush_engines___spray_brush_engine.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_reference_manual___brushes___brush_engines_" -"__spray_brush_engine\n" +"Project-Id-Version: " +"docs_krita_org_reference_manual___brushes___brush_engines___spray_brush_engine\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-03-02 03:22+0100\n" "PO-Revision-Date: 2019-03-13 16:38+0200\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" #: ../../:1 msgid "Mix with background color." msgstr "Змішування із кольором тла." #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:1 msgid "The Spray Brush Engine manual page." msgstr "Сторінка підручника щодо рушія пензлів-пульверизаторів." #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:16 msgid "Spray Brush Engine" msgstr "Рушій пензля-пульверизатора" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:19 msgid ".. image:: images/icons/spraybrush.svg" msgstr ".. image:: images/icons/spraybrush.svg" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:20 msgid "A brush that can spray particles around in its brush area." msgstr "Пензель, який може розбризкувати частки у області малювання." #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:23 msgid "Options" msgstr "Параметри" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:25 msgid ":ref:`option_spray_area`" msgstr ":ref:`option_spray_area`" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:26 msgid ":ref:`option_spray_shape`" msgstr ":ref:`option_spray_shape`" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:27 msgid ":ref:`option_brush_tip` (Used as particle if spray shape is not active)" msgstr "" ":ref:`option_brush_tip` (використовується як частка, якщо форма " "розбризкування є неактивною)" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:28 msgid ":ref:`option_opacity_n_flow`" msgstr ":ref:`option_opacity_n_flow`" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:29 msgid ":ref:`option_size`" msgstr ":ref:`option_size`" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:30 msgid ":ref:`blending_modes`" msgstr ":ref:`blending_modes`" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:31 msgid ":ref:`option_shape_dyna`" msgstr ":ref:`option_shape_dyna`" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:32 msgid ":ref:`option_color_spray`" msgstr ":ref:`option_color_spray`" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:33 msgid ":ref:`option_rotation`" msgstr ":ref:`option_rotation`" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:34 msgid ":ref:`option_airbrush`" msgstr ":ref:`option_airbrush`" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:39 msgid "Spray Area" msgstr "Забризкати область" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:41 msgid "The area in which the particles are sprayed." msgstr "Області, у якій має бути розбризкано частки." #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:43 msgid "Diameter" msgstr "Діаметр" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:44 msgid "The size of the area." msgstr "Розмір області." #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:45 msgid "Aspect Ratio" msgstr "Співвідношення розмірів" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:46 msgid "It's aspect ratio: 1.0 is fully circular." msgstr "Співвідношення розмірів: 1.0 — ідеально круглий." #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:47 msgid "Angle" msgstr "Кут" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:48 msgid "" "The angle of the spray size: works nice with aspect ratios other than 1.0." msgstr "" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:49 msgid "Scale" msgstr "Масштабувати" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:50 msgid "Scales the diameter up." msgstr "Збільшує діаметр." #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:52 msgid "Spacing" msgstr "Інтервал" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:52 msgid "Increases the spacing of the diameter's spray." msgstr "" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:55 msgid "Particles" msgstr "Частки" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:57 msgid "Count" msgstr "Число" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:58 msgid "Use a specified amount of particles." msgstr "Використати вказану кількість часток." #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:59 msgid "Density" msgstr "Щільність" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:60 msgid "Use a % amount of particles." msgstr "Вміст часток у відсотках." #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:61 msgid "Jitter Movement" msgstr "Зміщення розсіювання" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:62 msgid "Jitters the spray area around for extra randomness." msgstr "" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:64 msgid "Gaussian Distribution" msgstr "Гаусовий розподіл" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:64 msgid "" "Focuses the particles to paint in the center instead of evenly random over " "the spray area." msgstr "" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:69 msgid "Spray Shape" msgstr "Форма плями розбризкувача" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:71 msgid "" "If activated, this will generate a special particle. If not, the brush-tip " "will be the particle." msgstr "" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:74 msgid "Can be..." msgstr "Може бути…" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:76 msgid "Ellipse" msgstr "Еліпс" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:77 msgid "Rectangle" msgstr "Прямокутник" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:78 msgid "Anti-aliased Pixel" msgstr "Згладжування пікселів" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:79 msgid "Pixel" msgstr "Піксель" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:80 msgid "Shape" msgstr "Форма" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:80 msgid "Image" msgstr "Зображення" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:82 msgid "Width & Height" msgstr "Ширина, висота" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:83 msgid "Decides the width and height of the particle." msgstr "Визначає ширину і висоту окремої частки." #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:84 msgid "Proportional" msgstr "Пропорційний" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:85 msgid "Locks Width & Height to be the same." msgstr "Фіксує однакове значення ширини і висоти." #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:87 msgid "Texture" msgstr "Текстура" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:87 msgid "Allows you to pick an image for the :guilabel:`Image shape`." msgstr "Надає вам зомгу вибрати зображення для :guilabel:`Форми зображення`." #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:92 msgid "Shape Dynamics" msgstr "Динаміка форми" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:94 msgid "Random Size" msgstr "Випадковий розмір" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:95 msgid "" "Randomizes the particle size between 1x1 px and the given size of the " "particle in brush-tip or spray shape." msgstr "" -"Встановити випадковий розмір частки від 1x1 пікселів до вказаного розміру для" -" кінчика пензля або форми плями аерографа." +"Встановити випадковий розмір частки від 1x1 пікселів до вказаного розміру " +"для кінчика пензля або форми плями аерографа." #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:96 msgid "Fixed Rotation" msgstr "Фіксоване обертання" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:97 msgid "Gives a fixed rotation to the particle to work from." msgstr "Визначити фіксоване обертання частки." #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:98 msgid "Randomized Rotation" msgstr "Випадкове обертання" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:99 msgid "Randomizes the rotation." msgstr "Робить кут обертання випадковим." #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:100 msgid "Follow Cursor Weight" msgstr "Вага слідування за вказівником" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:101 msgid "" "How much the pressure affects the rotation of the particles. At 1.0 and high " "pressure it'll seem as if the particles are exploding from the middle." msgstr "" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:103 msgid "Angle Weight" msgstr "Вага кута" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:103 msgid "How much the spray area angle affects the particle angle." msgstr "" -"Визначає, наскільки кут області розбризкування аерографа впливає на кут" -" обертання частки." +"Визначає, наскільки кут області розбризкування аерографа впливає на кут " +"обертання частки." #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:108 msgid "Color Options" msgstr "Параметри кольорів" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:110 msgid "Random HSV" msgstr "Випадкова HSV" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:111 msgid "" "Randomize the HSV with the strength of the sliders. The higher, the more the " "color will deviate from the foreground color, with the direction indicating " "clock or counter clockwise." msgstr "" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:112 msgid "Random Opacity" msgstr "Випадкова непрозорість" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:113 msgid "Randomizes the opacity." msgstr "Робить непрозорість випадковою." #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:114 msgid "Color Per Particle" msgstr "Колір на частку" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:115 msgid "Has the color options be per particle instead of area." msgstr "Містить параметри кольору для окремих часток, а не області." #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:116 msgid "Sample Input Layer." msgstr "Шар зразка." #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:117 msgid "" "Will use the underlying layer as reference for the colors instead of the " "foreground color." msgstr "" -"Використовувати як основу для кольорів підлеглий шар, а не шар переднього" -" плану." +"Використовувати як основу для кольорів підлеглий шар, а не шар переднього " +"плану." #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:118 msgid "Fill Background" msgstr "Заповнити тло" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:119 msgid "Fills the area before drawing the particles with the background color." msgstr "" #: ../../reference_manual/brushes/brush_engines/spray_brush_engine.rst:121 msgid "" "Gives the particle a random color between foreground/input/random HSV and " "the background color." msgstr "" diff --git a/locale/uk_UA/LC_MESSAGES/reference_manual/brushes/brush_settings/tablet_sensors.po b/locale/uk_UA/LC_MESSAGES/reference_manual/brushes/brush_settings/tablet_sensors.po index c6aa0187b..c54a06690 100644 --- a/locale/uk_UA/LC_MESSAGES/reference_manual/brushes/brush_settings/tablet_sensors.po +++ b/locale/uk_UA/LC_MESSAGES/reference_manual/brushes/brush_settings/tablet_sensors.po @@ -1,191 +1,189 @@ # Translation of docs_krita_org_reference_manual___brushes___brush_settings___tablet_sensors.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_reference_manual___brushes___brush_settings" -"___tablet_sensors\n" +"Project-Id-Version: " +"docs_krita_org_reference_manual___brushes___brush_settings___tablet_sensors\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-19 03:36+0100\n" "PO-Revision-Date: 2019-03-13 16:23+0200\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" #: ../../:1 msgid "Tangential Pressure" msgstr "Дотичний тиск" #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:1 msgid "Tablet sensors in Krita." msgstr "Датчики планшета у Krita." #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:16 msgid "Sensors" msgstr "Датчики" #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:18 msgid "Pressure" msgstr "Тиск" #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:19 msgid "Uses the pressure in and out values of your stylus." msgstr "Використовує значення початкового і кінцевого тиску для вашого стила." #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:20 msgid "PressureIn" msgstr "Вхідний натиск" #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:21 msgid "" "Uses only pressure in values of your stylus. Previous pressure level in same " "stroke is overwritten *only* by applying more pressure. Lessening the " "pressure doesn't affect PressureIn." msgstr "" -"Використовує лише тиск у значеннях вашого стила. Попередній рівень тиску у" -" тому самому штриху буде перезаписано, *лише* якщо тиск буде збільшено." -" Зменшення тиску не впливає на вхідний натиск." +"Використовує лише тиск у значеннях вашого стила. Попередній рівень тиску у " +"тому самому штриху буде перезаписано, *лише* якщо тиск буде збільшено. " +"Зменшення тиску не впливає на вхідний натиск." #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:22 msgid "X-tilt" msgstr "Нахил за X" #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:23 #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:25 msgid "How much the brush is affected by stylus angle, if supported." msgstr "Рівень впливу кута нахилу стила, якщо такий реєструється, на пензель." #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:24 msgid "Y-tilt" msgstr "Нахил за Y" #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:26 msgid "Tilt-direction" msgstr "Напрямок ухилу" #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:27 msgid "" "How much the brush is affected by stylus direction. The pen point pointing " "towards the user is 0°, and can vary from -180° to +180°." msgstr "" "Рівень впливу напрямку руху стила, якщо такий реєструється, на пензель. Кут " "пера, яке спрямовано на користувача, вважається рівним 0°. Діапазоном зміни " "кута є значення від -180° до +180°." #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:28 msgid "Tilt-elevation" msgstr "Підвищення ухилу" #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:29 msgid "" "How much the brush is affected by stylus perpendicularity. 0° is the stylus " "horizontal, 90° is the stylus vertical." msgstr "" "Рівень впливу кута підвищення стила щодо поверхні планшета на пензель. 0° — " "стило розташовано горизонтально, 90° — стило розташовано вертикально." #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:30 msgid "Speed" msgstr "Швидкість" #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:31 msgid "How much the brush is affected by the speed at which you draw." msgstr "Вплив швидкості малювання на пензель." #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:32 msgid "Drawing Angle" msgstr "Кут малювання" #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:33 msgid "" "How much the brush is affected by which direction you are drawing in. :" "guilabel:`Lock` will lock the angle to the one you started the stroke with. :" "guilabel:`Fan corners` will try to smoothly round the corners, with the " "angle being the angles threshold it'll round. :guilabel:`Angle offset` will " "add an extra offset to the current angle." msgstr "" -"Рівень впливу напрямку, у якому ви малюєте на пензель." -" :guilabel:`Заблокувати` фіксує кут, з якого було розпочато малювання штриха." -" :" -"guilabel:`Віялоподібні кути` — намагатися плавно заокруглити кути, «Кут»" -" визначає порогові кути для заокруглення. За допомогою параметра" -" :guilabel:`Кутове зміщення` можна додати додаткове зміщення для поточного" -" кута." +"Рівень впливу напрямку, у якому ви малюєте на пензель. :guilabel:" +"`Заблокувати` фіксує кут, з якого було розпочато малювання штриха. :guilabel:" +"`Віялоподібні кути` — намагатися плавно заокруглити кути, «Кут» визначає " +"порогові кути для заокруглення. За допомогою параметра :guilabel:`Кутове " +"зміщення` можна додати додаткове зміщення для поточного кута." #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:34 msgid "Rotation" msgstr "Обертання" #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:35 msgid "" "How much a brush is affected by how the stylus is rotated, if supported by " "the tablet." msgstr "Рівень впливу кута обертання, якщо такий реєструється, на пензель." #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:36 msgid "Distance" msgstr "Відстань" #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:37 msgid "How much the brush is affected over length in pixels." msgstr "Вплив довжини малювання у пікселях на пензель." #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:38 msgid "Time" msgstr "Час" #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:39 msgid "How much a brush is affected over drawing time in seconds.." msgstr "Як впливає на пензель час малювання у секундах." #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:40 msgid "Fuzzy (Dab)" msgstr "Нечіткий мазок" #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:41 msgid "Basically the random option." msgstr "Загалом, випадковий параметр." #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:42 msgid "Fuzzy Stroke" msgstr "Нечіткий мазок" #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:43 msgid "" "A randomness value that is per stroke. Useful for getting color and size " "variation in on speed-paint brushes." msgstr "" "Значення випадковості для кожного мазка. Корисно для впровадження варіації " "кольору і розміру для пензлів для малювання на швидкість." #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:44 msgid "Fade" msgstr "Згасання" #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:45 msgid "" "How much the brush is affected over length, proportional to the brush tine." msgstr "" "Вплив довжини малювання, пропорційно до руху вістря пензля, на пензель." #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:46 msgid "Perspective" msgstr "Перспектива" #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:47 msgid "How much the brush is affected by the perspective assistant." msgstr "Вплив допоміжного інструмента перспективи на пензель." #: ../../reference_manual/brushes/brush_settings/tablet_sensors.rst:49 msgid "" "How much the brush is affected by the wheel on airbrush-simulating stylii." msgstr "Вплив коліщатка на стилах, які імітують аерограф, на пензель." diff --git a/locale/uk_UA/LC_MESSAGES/reference_manual/dr_minw_debugger.po b/locale/uk_UA/LC_MESSAGES/reference_manual/dr_minw_debugger.po index d48f2d73e..389363060 100644 --- a/locale/uk_UA/LC_MESSAGES/reference_manual/dr_minw_debugger.po +++ b/locale/uk_UA/LC_MESSAGES/reference_manual/dr_minw_debugger.po @@ -1,190 +1,207 @@ # Translation of docs_krita_org_reference_manual___dr_minw_debugger.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_reference_manual___dr_minw_debugger\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2019-02-24 03:22+0100\n" -"PO-Revision-Date: 2019-02-22 15:45+0200\n" +"PO-Revision-Date: 2019-03-14 08:31+0200\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" #: ../../reference_manual/dr_minw_debugger.rst:0 msgid ".. image:: images/en/Mingw-crash-screen.png" msgstr ".. image:: images/en/Mingw-crash-screen.png" #: ../../reference_manual/dr_minw_debugger.rst:0 msgid ".. image:: images/en/Mingw-explorer-path.png" msgstr ".. image:: images/en/Mingw-explorer-path.png" #: ../../reference_manual/dr_minw_debugger.rst:0 msgid ".. image:: images/en/Mingw-crash-log-start.png" msgstr ".. image:: images/en/Mingw-crash-log-start.png" #: ../../reference_manual/dr_minw_debugger.rst:0 msgid ".. image:: images/en/Mingw-crash-log-end.png" msgstr ".. image:: images/en/Mingw-crash-log-end.png" #: ../../reference_manual/dr_minw_debugger.rst:0 msgid ".. image:: images/en/Mingw-dbg7zip.png" msgstr ".. image:: images/en/Mingw-dbg7zip.png" #: ../../reference_manual/dr_minw_debugger.rst:0 msgid ".. image:: images/en/Mingw-dbg7zip-dir.png" msgstr ".. image:: images/en/Mingw-dbg7zip-dir.png" #: ../../reference_manual/dr_minw_debugger.rst:1 msgid "How to get a backtrace in Krita using the dr. MinW debugger." msgstr "" "Як створити дані зворотного трасування у Krita using the dr. MinW debugger." #: ../../reference_manual/dr_minw_debugger.rst:18 msgid "Dr. MinW Debugger" msgstr "Засіб діагностики Dr. MinW" #: ../../reference_manual/dr_minw_debugger.rst:22 msgid "" "The information on this page applies only to the Windows release of Krita " "3.1 Beta 3 (3.0.92) and later." msgstr "" +"Відомості з цієї сторінки стосуються лише випусків Krita для Windows версії" +" 3.1 Beta 3 (3.0.92) та новіших версій." #: ../../reference_manual/dr_minw_debugger.rst:26 msgid "Getting a Backtrace" msgstr "Отримання даних зворотного трасування" #: ../../reference_manual/dr_minw_debugger.rst:28 msgid "" "There are some additions to Krita which makes getting a backtrace much " "easier on Windows." msgstr "" +"Існують додаткові до Krita програми, які значно спрощують отримання даних" +" трасування у Windows." #: ../../reference_manual/dr_minw_debugger.rst:32 msgid "" "When there is a crash, Krita might appear to be unresponsive for a short " "time, ranging from a few seconds to a few minutes, before the crash dialog " "appears." msgstr "" +"Після аварії Krita може не відповідати на запити протягом певного часу, від" +" декількох секунд до декількох хвилин, перш ніж ви побачите діалогове вікно" +" повідомлення щодо аварійного завершення роботи." #: ../../reference_manual/dr_minw_debugger.rst:36 msgid "An example of the crash dialog" msgstr "Приклад вікна аварійного завершення роботи" #: ../../reference_manual/dr_minw_debugger.rst:38 msgid "" "If Krita keeps on being unresponsive for more than a few minutes, it might " "actually be locked up, which may not give a backtrace. In that situation, " "you have to close Krita manually. Continue to follow the following " "instructions to check whether it was a crash or not.
" msgstr "" #: ../../reference_manual/dr_minw_debugger.rst:40 msgid "" "Open Windows Explorer and type ``%LocalAppData%`` (without quotes) on the " "address bar and press Enter." msgstr "" +"Відкрийте Провідник Windows, введіть ``%LocalAppData%`` (без лапок) у смужці" +" адреси і натисніть клавішу :kbd:`Enter`." #: ../../reference_manual/dr_minw_debugger.rst:44 msgid "" "Find the file ``kritacrash.log`` (it might appear as simply ``kritacrash`` " "depending on your settings.)" msgstr "" +"Знайдіть файл ``kritacrash.log`` (може мати назву ``kritacrash``, залежно від" +" параметрів роботи програми)" #: ../../reference_manual/dr_minw_debugger.rst:45 msgid "" "Open the file with Notepad and scroll to the bottom, then scroll up to the " "first occurrence of “Error occurred on