Warning, /documentation/digikam-doc/locale/lt/LC_MESSAGES/color_management/camera_profiles.po is written in an unsupported language. File is not indexed.
0001 # Lithuanian translations for Digikam Manual package. 0002 # Copyright (C) licensed under the <a href="https://spdx.org/licenses/GFDL-1.2-or-later.html">licensed under the terms of the GNU Free Documentation License 1.2+</a> unless stated otherwise 0003 # This file is distributed under the same license as the Digikam Manual package. 0004 # Automatically generated, 2023. 0005 # 0006 msgid "" 0007 msgstr "" 0008 "Project-Id-Version: Digikam Manual 8.0.0\n" 0009 "Report-Msgid-Bugs-To: \n" 0010 "POT-Creation-Date: 2023-12-02 00:35+0000\n" 0011 "PO-Revision-Date: 2023-01-30 00:50+0000\n" 0012 "Last-Translator: Automatically generated\n" 0013 "Language-Team: none\n" 0014 "Language: lt\n" 0015 "MIME-Version: 1.0\n" 0016 "Content-Type: text/plain; charset=UTF-8\n" 0017 "Content-Transfer-Encoding: 8bit\n" 0018 "Plural-Forms: nplurals=4; plural=(n==1 ? 0 : n%10>=2 && (n%100<10 || n" 0019 "%100>=20) ? 1 : n%10==0 || (n%100>10 && n%100<20) ? 2 : 3);\n" 0020 0021 #: ../../color_management/camera_profiles.rst:1 0022 msgid "Color Management and Camera Profiles" 0023 msgstr "" 0024 0025 #: ../../color_management/camera_profiles.rst:1 0026 msgid "" 0027 "digiKam, documentation, user manual, photo management, open source, free, " 0028 "learn, easy, image editor, color management, icc, profile, camera" 0029 msgstr "" 0030 0031 #: ../../color_management/camera_profiles.rst:14 0032 msgid "The Camera Profiles" 0033 msgstr "" 0034 0035 #: ../../color_management/camera_profiles.rst:17 0036 msgid "Using Camera Profile" 0037 msgstr "" 0038 0039 #: ../../color_management/camera_profiles.rst:19 0040 msgid "" 0041 "Many excellent professional and amateur photographers save all their images " 0042 "as in-camera JPEGs and work exclusively in the sRGB color space. But if you " 0043 "want to work in a larger color space, or if you want to work with RAW files " 0044 "(even if you output sRGB image files from your RAW files), read on." 0045 msgstr "" 0046 0047 #: ../../color_management/camera_profiles.rst:21 0048 msgid "" 0049 "If you are reading this manual you probably are shooting RAW images with a " 0050 "digital dSLR and you are hoping that somewhere in the arcane waters of color " 0051 "management lies the answer to how to get a nice picture from your RAW image " 0052 "file. The next thing you need is the right camera profile for developing " 0053 "your RAW image. But first let's answer the question you really might have " 0054 "been asking." 0055 msgstr "" 0056 0057 #: ../../color_management/camera_profiles.rst:27 0058 msgid "digiKam RAW Preview Using **Embedded JPEG Image**." 0059 msgstr "" 0060 0061 #: ../../color_management/camera_profiles.rst:33 0062 msgid "" 0063 "digiKam RAW Preview Using an Half Sized Demosaiced in 8 bits and " 0064 "**Bilinear** Method." 0065 msgstr "" 0066 0067 #: ../../color_management/camera_profiles.rst:39 0068 msgid "" 0069 "digiKam RAW Import Tool from Image Editor Loading RAW file Demosaiced in 16-" 0070 "bit and **AHD** method." 0071 msgstr "" 0072 0073 #: ../../color_management/camera_profiles.rst:41 0074 msgid "" 0075 "Why doesn't the image produced by RAW converters like `Libraw <https://www." 0076 "libraw.org/>`_ look like the embedded preview displayed by digiKam? All " 0077 "digital camera images start out as RAW files, whether or not the camera " 0078 "allows the user the option to save the image as a RAW file. When you ask the " 0079 "camera to save JPEGs instead of RAW files, the camera uses its on-board " 0080 "processor to convert the RAW file to a JPEG. That embedded preview is what " 0081 "your final image would have looked like if you had set your camera to save " 0082 "JPEGs instead of RAW files." 0083 msgstr "" 0084 0085 #: ../../color_management/camera_profiles.rst:43 0086 msgid "" 0087 "Canon for example offers the user several picture styles - neutral, " 0088 "standard, portrait, landscape, and so forth - that determine what kind of " 0089 "processing will be done to the RAW image file to produce the final image, " 0090 "whether or not the processing is done *in-camera* or later, using the " 0091 "proprietary Canon software. This processing software does give the user " 0092 "additional control, but still manipulates the RAW image file in accordance " 0093 "with the chosen picture style. Most of the Canon picture styles add a heavy " 0094 "S-curve and extra color saturation to give the picture more *pop*. Even if " 0095 "you choose the *neutral* picture style (the Canon picture style that gives " 0096 "you the least modified tonality); and select *less contrast*, *less " 0097 "saturation*, *no noise reduction*, and *no sharpening* in the Cannon RAW " 0098 "development software, you will find, if you know what to look for, that an S-" 0099 "curve and also shadow de-noising has been applied to your image." 0100 msgstr "" 0101 0102 #: ../../color_management/camera_profiles.rst:45 0103 msgid "" 0104 "Libraw which digiKam uses to convert RAW files to image files doesn't add an " 0105 "S-curve to your image tonality. Libraw gives you the lights and darks that " 0106 "are actually recorded by the camera sensor. Libraw is one of only a handful " 0107 "of RAW developers that actually gives you the *scene-referred* tonality. And " 0108 "the Libraw scene-referred image is flat-looking, because the camera sensor " 0109 "records light linearly, whereas our eyes are constantly interacting with our " 0110 "brain to accommodate dim and bright areas in a scene, meaning our brain to " 0111 "some extent *applies an S-curve* to the scene to enable us to better focus " 0112 "in on the areas of particular interest as we look around." 0113 msgstr "" 0114 0115 #: ../../color_management/camera_profiles.rst:47 0116 msgid "" 0117 "The embedded JPEG preview looks so much nicer than Libraw's output. What is " 0118 "the value in scene-referred tonality? When you take a picture, presumably " 0119 "you have an idea of what you want the final image to look like. It is much " 0120 "easier to achieve that final image if you don't have to *undo* stuff that " 0121 "has already been done to your image. Once Canon (or Nikon, or Sony, etc.) " 0122 "has applied their proprietary S-curves and shadow de-noising, sharpening, " 0123 "etc. to your image, then your shadows, highlights, edge detail, etc. are " 0124 "already squashed, clipped, chopped, and otherwise altered and mangled. " 0125 "You've thrown information away and you cannot get it back. Especially in the " 0126 "shadows, even with 16-bit images (actually, 12- or 14-bits, depending on the " 0127 "camera, but it's encoded as 16-bits for the computer's convenience), there " 0128 "just isn't that much information to begin with." 0129 msgstr "" 0130 0131 #: ../../color_management/camera_profiles.rst:53 0132 msgid "" 0133 "digiKam Raw Import Tool from Image Editor Allows to Post Process Exposures " 0134 "and Curves just After the Demosaicing." 0135 msgstr "" 0136 0137 #: ../../color_management/camera_profiles.rst:55 0138 msgid "" 0139 "It seems to me that the heart and soul of image processing is the deliberate " 0140 "manipulation of image tonality, color, selective sharpening, and so forth, " 0141 "such that the viewer focuses in on what you, the photographer, found of " 0142 "particular interest when you took the picture. Why give the art of image " 0143 "processing over to some proprietary RAW processing software? In other words, " 0144 "*flat is good* if you'd rather give your images your own artistic " 0145 "interpretation. The alternative is to let the canned, proprietary algorithms " 0146 "produced by Canon, Nikon, Sony, etc. interpret your images for you. On the " 0147 "other hand, there is no denying that for many images, those canned " 0148 "algorithms are really pretty good." 0149 msgstr "" 0150 0151 #: ../../color_management/camera_profiles.rst:57 0152 msgid "" 0153 "You can see the value in starting my image-editing with a scene-referred " 0154 "rendition instead of the eye-popping rendition that you see in the embedded " 0155 "JPEG. But the images produced by digiKam and Libraw look a little bit " 0156 "different. If the image looks very dark, then you asked Libraw to output a " 0157 "16-bit file and you have run into a problem with Libraw not applying a gamma " 0158 "transform before outputting the image file. You can use the Image Editor to " 0159 "apply the appropriate gamma transform to the image file produced by Libraw. " 0160 "Or you can find or make a camera profile with a gamma of 1." 0161 msgstr "" 0162 0163 #: ../../color_management/camera_profiles.rst:59 0164 msgid "" 0165 "If your image has pink highlights, check your **White Balance** settings in " 0166 "the RAW Import tool, especially the **highlights** options." 0167 msgstr "" 0168 0169 #: ../../color_management/camera_profiles.rst:65 0170 msgid "" 0171 "digiKam Raw Import Tool from Image Editor Allows to Tune Many Options about " 0172 "the Camera Colorimetric Values." 0173 msgstr "" 0174 0175 #: ../../color_management/camera_profiles.rst:67 0176 msgid "" 0177 "If the image isn't dark but it looks really weird, probably you made some " 0178 "injudicious choices in the Raw Import user-interface from Image Editor. The " 0179 "Libraw interface conveniently allows you to *dial in* options. However, " 0180 "convenience always comes at a price. First, the interface might not provide " 0181 "access to all the options. And second, to get the most from the Libraw " 0182 "interface, you have to know what the buttons, sliders, etc. in the interface " 0183 "actually do." 0184 msgstr "" 0185 0186 #: ../../color_management/camera_profiles.rst:70 0187 msgid "Camera Profile Specificity" 0188 msgstr "" 0189 0190 #: ../../color_management/camera_profiles.rst:72 0191 msgid "" 0192 "Why are the Canon and Nikon colors better than the colors produced by " 0193 "Libraw? Color rendition is one place where the Canon (and presumably Nikon) " 0194 "proprietary RAW developing software does a really good job." 0195 msgstr "" 0196 0197 #: ../../color_management/camera_profiles.rst:74 0198 msgid "" 0199 "The proprietary RAW processing software is coupled with camera profiles that " 0200 "are specific to RAW images coming from your make and model of camera, when " 0201 "processed using your make and model camera's proprietary RAW processing " 0202 "software. With digikam's Libraw user interface, you can apply Canon's camera " 0203 "model picture style specific color profile to the Libraw output during the " 0204 "RAW development process, and the colors will still not be exactly the same " 0205 "as what Canon produces." 0206 msgstr "" 0207 0208 #: ../../color_management/camera_profiles.rst:76 0209 msgid "" 0210 "Digital cameras have an array of millions of little light sensors inside, " 0211 "making up either a CCD or a CMOS chip. These light-sensing pixels are color-" 0212 "blind - they only record the amount, not the color, of light falling on " 0213 "them. So to allow pixels to record color information, each pixel is capped " 0214 "by a transparent red, green, or blue lens, usually alternating in what is " 0215 "called a Bayer array (except for Sigma Faveon sensors, which work " 0216 "differently). A RAW image is nothing more than an array of values indicating " 0217 "*how much light* passed through the red, blue, or green lens cap to reach " 0218 "the sensor." 0219 msgstr "" 0220 0221 #: ../../color_management/camera_profiles.rst:78 0222 msgid "" 0223 "Clearly, pixel response to light is the result of lots of camera specific " 0224 "factors including: the nature of the sensor array itself, the precise " 0225 "coloring/transmissive qualities of the lens caps, and the particular analog " 0226 "to digital conversion and post-conversion processing that happens inside the " 0227 "camera to produce the RAW image that gets stored on the card." 0228 msgstr "" 0229 0230 #: ../../color_management/camera_profiles.rst:81 0231 msgid "Analog to Digital Conversion" 0232 msgstr "" 0233 0234 #: ../../color_management/camera_profiles.rst:83 0235 msgid "" 0236 "*Analog* means continuously varying, like how much water you can put in a " 0237 "glass. *Digitizing* an analog signal means that the continuously changing " 0238 "levels from the analog signal source are *rounded* to discrete quantities " 0239 "convenient to the binary numbers used by computers. The analog to digital " 0240 "conversion that takes place inside the camera is necessary because the light-" 0241 "sensing pixels are analog in nature - they collect a charge proportionate to " 0242 "the amount of light that reaches them." 0243 msgstr "" 0244 0245 #: ../../color_management/camera_profiles.rst:85 0246 msgid "" 0247 "The accumulated charge on each pixel is then turned into a discrete, digital " 0248 "quantity by the camera's analog to digital converter. Which by the way " 0249 "explains why a 14-bit converter is better than a 12-bit converter - more " 0250 "precision in the conversion output means less information is thrown away in " 0251 "the conversion process." 0252 msgstr "" 0253 0254 #: ../../color_management/camera_profiles.rst:87 0255 msgid "" 0256 "Especially in pictures taken with low light conditions, a noise is " 0257 "integrated while the analog to digital conversion. digiKam and Libraw " 0258 "interface provides a **Noise Reduction** correction based on wavelets which " 0259 "can be applied while demosaicing." 0260 msgstr "" 0261 0262 #: ../../color_management/camera_profiles.rst:93 0263 msgid "" 0264 "digiKam Raw Import Tool from Image Editor Allows Wavelets Noise Reduction " 0265 "While Demosaicing." 0266 msgstr "" 0267 0268 #: ../../color_management/camera_profiles.rst:96 0269 msgid "Camera Profile and RAW Treatment" 0270 msgstr "" 0271 0272 #: ../../color_management/camera_profiles.rst:98 0273 msgid "" 0274 "The whole point of interpolation using demosaicing algorithms such as " 0275 "`Libraw <https://www.libraw.org/>`_'s default AHD is to guess what color and " 0276 "intensity of light actually fell on any given pixel by interpolating " 0277 "information gathered from that single pixel plus its neighboring pixels. " 0278 "Every RAW processing program makes additional assumptions such as when is it " 0279 "signal and when is it background noise, or at what point has the sensor well " 0280 "reached full saturation. The resulting output of all these algorithms and " 0281 "assumptions that RAW processing software makes is a trio of RGB values for " 0282 "each pixel in the image. Given the same RAW file, different RAW processors " 0283 "will output different RGB values." 0284 msgstr "" 0285 0286 #: ../../color_management/camera_profiles.rst:104 0287 msgid "" 0288 "digiKam Raw Import Tool from Image Editor Allow to Tune the Color Profile to " 0289 "Apply While Demosaicing." 0290 msgstr "" 0291 0292 #: ../../color_management/camera_profiles.rst:107 0293 msgid "Generic Camera Profile" 0294 msgstr "" 0295 0296 #: ../../color_management/camera_profiles.rst:109 0297 msgid "" 0298 "This website section has information on where to find ready-made camera " 0299 "profiles. If you poke around the digiKam users forum archives, you'll find " 0300 "additional advice. If you keep hunting and experimenting, likely you will " 0301 "find a generic profile that works *well enough*. However, as stated above, " 0302 "it's an unfortunate fact of digital imaging that the camera profiles " 0303 "supplied by Canon, Nikon, and the like don't work as well with RAW " 0304 "converters other than each camera manufacturer's own proprietary RAW " 0305 "converter. Which is why proprietary programs, have to make their own " 0306 "profiles for all the cameras that they support. So eventually you may decide " 0307 "that you want a camera profile that is specific to your camera, your " 0308 "lighting conditions, and your RAW processing workflow." 0309 msgstr "" 0310 0311 #: ../../color_management/camera_profiles.rst:115 0312 msgid "The Draft of Color Management Logic While a RAW Workflow Processing." 0313 msgstr "" 0314 0315 #: ../../color_management/camera_profiles.rst:118 0316 msgid "Lighting Conditions and RAW Workflow" 0317 msgstr "" 0318 0319 #: ../../color_management/camera_profiles.rst:120 0320 msgid "" 0321 "Many commercial services provide profiling services, for a fee, of course. " 0322 "Or you can use `Argyll <http://www.argyllcms.com/>`_ to profile your camera " 0323 "yourself. If you want to profile your own camera, you will need an `IT8 " 0324 "target <https://en.wikipedia.org/wiki/IT8#Targets>`_, that is, an image " 0325 "containing squares of known colors. Along with the IT8 target, you will " 0326 "receive the appropriate set of known values for each square of color on the " 0327 "target." 0328 msgstr "" 0329 0330 #: ../../color_management/camera_profiles.rst:122 0331 msgid "" 0332 "If you plan to use Argyll to profile your camera, check the documentation " 0333 "for a list of recommended targets. To profile your camera, you photograph " 0334 "the IT8 target under specified lighting conditions (for example, in " 0335 "daylight, usually taken to mean noon on a sunny day in the summer, with " 0336 "nothing nearby that might cast shadows or reflect color casts) and save the " 0337 "image as a RAW file. Then you process the RAW file using your particular RAW " 0338 "processing software+settings and run the resulting image file through the " 0339 "profiling software. The profiling software compares the RGB values in the " 0340 "image produced by your camera+lighting conditions+RAW processing routine " 0341 "with the RGB values in the original target and then produces your camera " 0342 "(icc) profile." 0343 msgstr "" 0344 0345 #: ../../color_management/camera_profiles.rst:124 0346 msgid "" 0347 "Profiling a camera is exactly analogous to profiling a monitor. When " 0348 "profiling a monitor, the profiling software tells the graphics card to send " 0349 "squares of color with particular RGB values to the screen. The " 0350 "spectrophotometer measures the actual color that is produced on the screen. " 0351 "When profiling a camera, the known colors are the RGB colors in the original " 0352 "patches on the IT8 target, which the profiling software compares to the " 0353 "colors produced by the digital image of the target, which was photographed " 0354 "in selected lighting conditions, saved as RAW, then processed with specific " 0355 "RAW processing software plus settings." 0356 msgstr "" 0357 0358 #: ../../color_management/camera_profiles.rst:126 0359 msgid "" 0360 "How to apply a camera profile to the 16-bit image file produced by my open " 0361 "source RAW processing software? If you are using the `Libraw <https://www." 0362 "libraw.org/>`_ interface from digiKam, here is how to tell digiKam which " 0363 "camera profile to use." 0364 msgstr "" 0365 0366 #: ../../color_management/camera_profiles.rst:132 0367 msgid "" 0368 "The digiKam Batch Queue Manager Raw Converter has also the Same Noise " 0369 "Reduction and Color Profiles Options than Image Editor" 0370 msgstr "" 0371 0372 #: ../../color_management/camera_profiles.rst:135 0373 msgid "Profiles Point to Real Colors" 0374 msgstr "" 0375 0376 #: ../../color_management/camera_profiles.rst:137 0377 msgid "" 0378 "A color profile describes the color gamut of the device or space to which it " 0379 "belongs by specifying what real color in the real world corresponds to each " 0380 "trio of RGB values in the color space of the device (camera, monitor, " 0381 "printer) or working space." 0382 msgstr "" 0383 0384 #: ../../color_management/camera_profiles.rst:139 0385 msgid "" 0386 "With a camera profile, for every RGB trio of values associated with every " 0387 "pixel in the image file produced from the RAW file by the RAW processing " 0388 "software, this RGB image file trio corresponds to real color as seen by a " 0389 "real observer in the real world (or rather, as displayed on the IT8 target " 0390 "if you produced your own camera profile, but it amounts to the same thing - " 0391 "the goal of profiling your camera is to make the picture of the target look " 0392 "like the target)." 0393 msgstr "" 0394 0395 #: ../../color_management/camera_profiles.rst:141 0396 msgid "" 0397 "You cannot see an image by looking at its RGB values. Rather you see an " 0398 "image by displaying it on a monitor or by printing it. When you profile your " 0399 "monitor, you produce a monitor profile which RGB trio of values that the " 0400 "graphics card sends to the screen will produce on the screen with real color " 0401 "as seen by a real observer in the real world." 0402 msgstr "" 0403 0404 #: ../../color_management/camera_profiles.rst:143 0405 msgid "" 0406 "What the monitor profile and the camera profile have in common is the part " 0407 "about that real color as seen by a real observer in the real world. " 0408 "Different trios of RGB numbers in, respectively, the monitor and camera " 0409 "color spaces point to the same real, visible color in the real world. Real " 0410 "colors in the real world provide the reference point for translating between " 0411 "all the color profiles your image will ever encounter on its way from camera " 0412 "to screen to editing program to print or the web." 0413 msgstr "" 0414 0415 #: ../../color_management/camera_profiles.rst:145 0416 msgid "" 0417 "Real people don't even see the same colors when they look at the world, do " 0418 "they? A long time ago (1931, although refinements continue to be made), the " 0419 "International Color Consortium decided to map out and mathematically " 0420 "describe all the colors visible to real people in the real world. So they " 0421 "showed a whole bunch of people a whole bunch of colors and asked them to say " 0422 "when this color matched that color, where the two visually matching colors " 0423 "were in fact produced by differing combinations of wavelengths. What was the " 0424 "value of such a strange procedure? Human color perception depends on the " 0425 "fact that we have three types of cone receptors with peak sensitivity to " 0426 "light at wavelengths of approximately 430, 540, and 570 nm, but with " 0427 "considerable overlap in sensitivity between the different cone types. One " 0428 "consequence of how we see color is that many different combinations of " 0429 "differing wavelengths of light will look like the same color." 0430 msgstr "" 0431 0432 #: ../../color_management/camera_profiles.rst:147 0433 msgid "" 0434 "The ICC produced the `CIE-XYZ color space <https://en.wikipedia.org/wiki/" 0435 "CIE_1931_color_space>`_ s which mathematically describes and models all the " 0436 "`colors visible to an ideal human <https://en.wikipedia.org/wiki/" 0437 "Color_vision>`_ observer (*ideal* in the sense of modeling the tested " 0438 "responses of lots of individual humans). This color space is not a color " 0439 "profile in the normal sense of the word. Rather it provides an absolute " 0440 "**Profile Connecting Space** (PCS) for translating color RGB values from one " 0441 "color space to another." 0442 msgstr "" 0443 0444 #: ../../color_management/camera_profiles.rst:149 0445 msgid "" 0446 "CIE-XYZ is not the only Profile Connection Space. Another commonly used " 0447 "Profile Connection Space is `CIE-Lab <https://en.wikipedia.org/wiki/" 0448 "Lab_color_space>`_, which is mathematically derived from the CIE-XYZ space. " 0449 "CIE-Lab is intended to be **perceptually uniform**, meaning a change of the " 0450 "same amount in a color value should produce a change of about the same " 0451 "visual importance." 0452 msgstr "" 0453 0454 #: ../../color_management/camera_profiles.rst:151 0455 msgid "" 0456 "The three coordinates of CIE-Lab represent the lightness of the color (**L = " 0457 "0** yields black and **L = 100** indicates diffuse white; specular white may " 0458 "be higher), its position between red/magenta and green (**a**, negative " 0459 "values indicate green while positive values indicate magenta) and its " 0460 "position between yellow and blue (**b**, negative values indicate blue and " 0461 "positive values indicate yellow)." 0462 msgstr "" 0463 0464 #: ../../color_management/camera_profiles.rst:153 0465 msgid "" 0466 "To be useful, color profiles need to be coupled with software that performs " 0467 "the translation from one color space to another via the Profile Connection " 0468 "Space. In digiKam, translation from one color space to another usually is " 0469 "done by `Lcms <https://www.littlecms.com/>`_, the **Little Color Management " 0470 "Software**." 0471 msgstr ""