Warning, /documentation/digikam-doc/locale/fr/LC_MESSAGES/color_management/working_space.po is written in an unsupported language. File is not indexed.
0001 # 0002 msgid "" 0003 msgstr "" 0004 "Project-Id-Version: Digikam Manual 8.0.0\n" 0005 "Report-Msgid-Bugs-To: \n" 0006 "POT-Creation-Date: 2023-12-02 00:35+0000\n" 0007 "PO-Revision-Date: 2023-01-14 18:31+0100\n" 0008 "Last-Translator: KDE Francophone <kde-francophone@kde.org>\n" 0009 "Language-Team: French <kde-francophone@kde.org>\n" 0010 "Language: fr\n" 0011 "MIME-Version: 1.0\n" 0012 "Content-Type: text/plain; charset=UTF-8\n" 0013 "Content-Transfer-Encoding: 8bit\n" 0014 "Plural-Forms: nplurals=2; plural=(n > 1);\n" 0015 0016 #: ../../color_management/working_space.rst:1 0017 msgid "Color Management and Working Space" 0018 msgstr "" 0019 0020 #: ../../color_management/working_space.rst:1 0021 msgid "" 0022 "digiKam, documentation, user manual, photo management, open source, free, " 0023 "learn, easy, image editor, color management, icc, profile, working space" 0024 msgstr "" 0025 0026 #: ../../color_management/working_space.rst:14 0027 msgid "The Working Space" 0028 msgstr "" 0029 0030 #: ../../color_management/working_space.rst:17 0031 msgid "Color Workflow" 0032 msgstr "" 0033 0034 #: ../../color_management/working_space.rst:19 0035 msgid "" 0036 "So we told digiKam where to find my monitor profile and we have a camera " 0037 "profile that we applied to the image file produced by my RAW processing " 0038 "software. What's the next step in color management?" 0039 msgstr "" 0040 0041 #: ../../color_management/working_space.rst:21 0042 msgid "" 0043 "You need to choose a working color space so you can edit your image. `Lcms " 0044 "<https://www.littlecms.com/>`_ will transform your image from your camera " 0045 "color space to your chosen working space, via the **Profile Connection " 0046 "Space** specified by your camera color profile. Why cannot to just edit " 0047 "images in the color space described by the camera profile?" 0048 msgstr "" 0049 0050 #: ../../color_management/working_space.rst:23 0051 msgid "" 0052 "After all, the camera profile should provide the best *fit* to the colors " 0053 "recorded by my camera, as processed by my RAW processing procedure, right? " 0054 "Working spaces, such as sRGB or Adobe RGB, are color spaces that facilitate " 0055 "good results while editing. For instance, pixels with equal values of RGB " 0056 "should appear neutral. This just want means that for any given pixel in an " 0057 "image that has been converted to a suitable working space, if R=G=B you " 0058 "should see grey or black or white on your screen. Many camera profiles " 0059 "violate this *neutral* condition." 0060 msgstr "" 0061 0062 #: ../../color_management/working_space.rst:29 0063 msgid "" 0064 "digiKam Image Editor has a Menu to Switch Quickly an Image from a Color " 0065 "Space to Another one" 0066 msgstr "" 0067 0068 #: ../../color_management/working_space.rst:31 0069 msgid "" 0070 "However, there is one other good reason to not want to edit your image in " 0071 "your camera profile color space. If you look at the size of a typical camera " 0072 "profile, it is on the order of a quarter to a half a megabyte or more. It's " 0073 "got a lot of information about all the changes that need to be made at " 0074 "different regions of color and tonality in the original scene, to get " 0075 "accurate color rendition from the RGB values that come out of the RAW " 0076 "processor. The camera profile is accurate (at least for colors in the " 0077 "original target) but not particularly mathematically smooth. Working space " 0078 "color profiles, on the other hand, are very small in size (half a kilobyte " 0079 "instead of half a megabyte) because they describe a color gamut in terms of " 0080 "smooth, continuous mathematical functions. Working space profiles don't need " 0081 "to make allowances for the *messiness* of real world sensors, so the " 0082 "mathematical manipulations performed during image editing will go much more " 0083 "smoothly and accurately than if you try to edit your image while it is still " 0084 "in the camera color space." 0085 msgstr "" 0086 0087 #: ../../color_management/working_space.rst:33 0088 msgid "Working Space Profiles are characterized by:" 0089 msgstr "" 0090 0091 #: ../../color_management/working_space.rst:35 0092 msgid "" 0093 "**Gamma** transfer function, which dictates how much the original linear " 0094 "intensity values captured by the camera sensor are altered to make editing " 0095 "easier or more precise. These values from the camera are subjected to the in-" 0096 "camera A-to-D conversion, then interpolated by the RAW processing program to " 0097 "produce the image file." 0098 msgstr "" 0099 0100 #: ../../color_management/working_space.rst:37 0101 msgid "" 0102 "RGB primaries which dictate the range of colors, that is, the color " 0103 "**Gamut**, covered by a given profile." 0104 msgstr "" 0105 0106 #: ../../color_management/working_space.rst:39 0107 msgid "" 0108 "**White point**, usually D50 or D65 though other values may be used, which " 0109 "specifies the white point color temperature of the working space." 0110 msgstr "" 0111 0112 #: ../../color_management/working_space.rst:42 0113 msgid "Confusions Terminology" 0114 msgstr "" 0115 0116 #: ../../color_management/working_space.rst:44 0117 msgid "" 0118 "Before talking more about working spaces, some confusions and confusing " 0119 "terminology needs to be cleared up:" 0120 msgstr "" 0121 0122 #: ../../color_management/working_space.rst:46 0123 msgid "" 0124 "sRGB is both a working color space and an output color space for images " 0125 "intended for the web and for monitor display. If you have a spiffy new " 0126 "monitor with a gamut larger than the gamut covered by sRGB, obviously you " 0127 "might want to reconsider what output profile to use to best take advantage " 0128 "of your wonderful and hopefully calibrated and profiled monitor, but please " 0129 "convert your image to sRGB before sending it on to your friends. sRGB is " 0130 "also the color space that a lot of home and mass-production commercial " 0131 "printers expect image files to be in when sent to the printer. It is also " 0132 "the color space that most programs assume if an image does not have an " 0133 "embedded color profile telling the program what color space should be used " 0134 "to interpret (translate) the RGB numbers. So if you choose to not use color-" 0135 "management, your color-management choices are simple - set everything to " 0136 "sRGB." 0137 msgstr "" 0138 0139 #: ../../color_management/working_space.rst:48 0140 msgid "" 0141 "All JPEGs coming straight out of a camera (even if produced by point-and-" 0142 "shoots cameras that don't allow you to save a RAW file) start life inside " 0143 "the camera as a RAW file produced by the camera's A to D converter. The " 0144 "processor inside the camera interpolates the RAW file, assigns a camera " 0145 "profile, translates the resulting RGB numbers to a working space (usually " 0146 "sRGB but sometimes you can choose AdobeRGB, depending on the camera), does " 0147 "the JPEG compression, and stores the JPEG file on your camera card. So JPEGs " 0148 "from your camera never need to be assigned a camera or input profile which " 0149 "is then translated to a working space via a Profile Connection Space. JPEGs " 0150 "from a camera are already in a working space." 0151 msgstr "" 0152 0153 #: ../../color_management/working_space.rst:50 0154 msgid "" 0155 "In case anyone is unsure on this point, note that an interpolated RAW file " 0156 "is no longer a RAW file - it has been interpolated and then output as a TIFF " 0157 "whose RGB values need to be translated to a working space, using the camera " 0158 "profile, the Profile Connection Space, and Lcms." 0159 msgstr "" 0160 0161 #: ../../color_management/working_space.rst:52 0162 msgid "" 0163 "To introduce a bit of commonly heard color-management terminology here - the " 0164 "camera profile and your printer's color profile are both device dependent, " 0165 "whereas the working space will be device-independent - it can be used with " 0166 "any image, with any properly color-managed software, without regard for " 0167 "where the image originated." 0168 msgstr "" 0169 0170 #: ../../color_management/working_space.rst:54 0171 msgid "" 0172 "Above we have used the words translate and translation as a descriptive " 0173 "metaphor for what Lcms does when it translates RGB values from one color " 0174 "space to another via the Profile Connection Space. The usual and correct " 0175 "terminology is convert and conversion. The four methods of conversion from " 0176 "one color space to another are: perceptual, relative colorimetric, absolute " 0177 "colorimetric, and saturation. Which method of conversion you should use for " 0178 "any given image processing step from RAW file to final output image is " 0179 "beyond the scope of this manual. The standard advice is: when in doubt, use " 0180 "perceptual." 0181 msgstr "" 0182 0183 #: ../../color_management/working_space.rst:56 0184 msgid "" 0185 "Assign a profile means change the meaning of the RGB numbers in an image by " 0186 "embedding a new profile without changing the actual RGB numbers associated " 0187 "with each pixel in the image; convert means embed a new profile, but also " 0188 "change the RGB numbers at the same time so that the meaning of the RGB " 0189 "values - that is, the real-world visible color represented by the trio of " 0190 "RGB numbers associated with each pixel in an image - remains the same before " 0191 "and after the conversion from one space to another. You should be able to do " 0192 "multiple conversions of an image from one working space to another, and with " 0193 "a properly color-managed image editor, even though all the RGB numbers in " 0194 "the image will change with each conversion, the image on your screen should " 0195 "look the same (leaving aside the usually unnoticeable small but inevitable " 0196 "changes from accumulated gamut mismatches and mathematical rounding errors). " 0197 "However, every time you assign a new working space profile rather than " 0198 "convert to a new working space, the appearance of the image should more or " 0199 "less drastically change." 0200 msgstr "" 0201 0202 #: ../../color_management/working_space.rst:58 0203 msgid "" 0204 "Color management is not only relevant if you shoot RAW. Color management " 0205 "affects every stage of the image processing pipeline, whether you start with " 0206 "a RAW file that you, yourself interpolate and translate into a TIFF, or if " 0207 "you start with a JPEG or TIFF produced by your camera." 0208 msgstr "" 0209 0210 #: ../../color_management/working_space.rst:61 0211 msgid "Selecting a Working Space" 0212 msgstr "" 0213 0214 #: ../../color_management/working_space.rst:63 0215 msgid "" 0216 "Which working space do you need to use in digiKam? Working spaces, such as " 0217 "sRGB or Adobe RGB, are color spaces that facilitate good results while " 0218 "editing. For instance, pixels with equal values of RGB should appear " 0219 "neutral. Using a large gamut working space will lead to posterization, while " 0220 "using a small working space will lead to clipping. This trade-off is a " 0221 "consideration for the Image Editor." 0222 msgstr "" 0223 0224 #: ../../color_management/working_space.rst:65 0225 msgid "Most working space profiles are characterized by:" 0226 msgstr "" 0227 0228 #: ../../color_management/working_space.rst:67 0229 msgid "" 0230 "The place of the gamut into the **Diagram** `(1)` of all colors visible to " 0231 "the average human eyes." 0232 msgstr "" 0233 0234 #: ../../color_management/working_space.rst:69 0235 msgid "" 0236 "The **Gamut** `(2)` triangle to define the range of RGB colors of the " 0237 "profile. Red point is on the bottom right corner, Green is on the top, Blue " 0238 "is on the left bottom. Values given around the edge of the gamut passing " 0239 "from the blue, the green and the red points, are the spectral colors in " 0240 "nanometers." 0241 msgstr "" 0242 0243 #: ../../color_management/working_space.rst:71 0244 msgid "" 0245 "The **White point** `(3)` to define the total dynamic range of the profile." 0246 msgstr "" 0247 0248 #: ../../color_management/working_space.rst:73 0249 msgid "" 0250 "The **Gamma** to define the transfer function of the profile (not displayed " 0251 "in the gamut)." 0252 msgstr "" 0253 0254 #: ../../color_management/working_space.rst:79 0255 msgid "The Color Profile Details of CIE Chromaticity Diagram Show in digiKam" 0256 msgstr "" 0257 0258 #: ../../color_management/working_space.rst:81 0259 msgid "" 0260 "The practical consequences that result from using different RGB primaries, " 0261 "leading to larger or smaller working spaces, are discussed below. The " 0262 "practical consequences for different choices for the working space white " 0263 "point are beyond the scope of this manual. Here we will talk a little bit " 0264 "about the practical consequences of the working space gamma." 0265 msgstr "" 0266 0267 #: ../../color_management/working_space.rst:83 0268 msgid "" 0269 "The gamma of a color profile dictates what power transform needs to take " 0270 "place to properly convert from an image's embedded color profile (perhaps " 0271 "your working color space) to another color profile with a different gamma, " 0272 "such as (i) the display profile used to display the image on the screen or " 0273 "(ii) perhaps to a new working space, or (iii) perhaps from your working " 0274 "space to your printer's color space." 0275 msgstr "" 0276 0277 #: ../../color_management/working_space.rst:87 0278 msgid "" 0279 "Mathematically speaking, for a power transform you normalize the RGB numbers " 0280 "and raise the resulting numbers to an appropriate power depending on the " 0281 "respective gammas of the starting and ending color space, then re-normalize " 0282 "the results to a new set of RGB numbers. `Lcms <https://www.littlecms.com/" 0283 ">`_ does this for you when there is a need to convert from one color space " 0284 "to another in your workflow." 0285 msgstr "" 0286 0287 #: ../../color_management/working_space.rst:89 0288 msgid "" 0289 "One practical consequence of the gamma of a working space is that the higher " 0290 "the gamma, the more tones are available for editing in the shadows, with " 0291 "consequently fewer tones available in the highlights. So theoretically, if " 0292 "you are working on a very dark-toned (low key) image you might want a " 0293 "working space with a higher gamma. And if you are working on a high key " 0294 "image, say a picture taken in full noon sunlight of a wedding dress with " 0295 "snow as a backdrop, you might want to choose a working space with a lower " 0296 "gamma, so you have more available tonal gradations in the highlights. But in " 0297 "the real world of real image editing, almost everyone uses working spaces " 0298 "with either gamma 1.8 or 2.2." 0299 msgstr "" 0300 0301 #: ../../color_management/working_space.rst:91 0302 msgid "" 0303 "Some people are trying to standardize on gamma 2.0. sRGB and LStar-RGB are " 0304 "not gamma-based working spaces. Rather, sRGB uses a hybrid gamma, and LStar-" 0305 "RGB uses a luminosity-based tonal response curve instead of a gamma value." 0306 msgstr "" 0307 0308 #: ../../color_management/working_space.rst:93 0309 msgid "" 0310 "In addition to gamma 1.8 and gamma 2.2 the only other gamma for a working " 0311 "space that gets much mention or use is gamma 1.0, also called linear gamma. " 0312 "Linear gamma is used in HDR (high dynamic range) imaging and also if one " 0313 "wants to avoid introducing gamma-induced errors into one's regular low " 0314 "dynamic range editing. Gamma-induced errors is a topic outside the scope of " 0315 "this manual, but see Gamma errors in picture scaling, for gamma-induced " 0316 "color shifts." 0317 msgstr "" 0318 0319 #: ../../color_management/working_space.rst:95 0320 msgid "" 0321 "Unfortunately and despite their undeniable mathematical advantages, linear " 0322 "gamma working spaces have so few tones in the shadows that they are " 0323 "impossible to use for editing if one is working in 8-bits, and still " 0324 "problematic at 16-bits. When the day comes when we are all doing our editing " 0325 "on 32-bit files produced by our HDR cameras on our personal supercomputers, " 0326 "we predict that we will all be using working spaces with gamma 1." 0327 msgstr "" 0328 0329 #: ../../color_management/working_space.rst:101 0330 msgid "" 0331 "Depending of the Settings digiKam Can Ask you to Convert to Working Space " 0332 "When Loading in Image Editor" 0333 msgstr "" 0334 0335 #: ../../color_management/working_space.rst:104 0336 msgid "Large or Small Gamut" 0337 msgstr "" 0338 0339 #: ../../color_management/working_space.rst:106 0340 msgid "" 0341 "One major consideration in choosing a working space is that some working " 0342 "spaces are bigger than others, meaning they cover more of the visible " 0343 "spectrum (and perhaps even include some imaginary colors - mathematical " 0344 "constructs that don't really exist). These bigger spaces offer the advantage " 0345 "of allowing you to keep all the colors captured by your camera and preserved " 0346 "by the Lcms conversion from your camera profile to the really big profile " 0347 "connection space." 0348 msgstr "" 0349 0350 #: ../../color_management/working_space.rst:112 0351 msgid "" 0352 "For the Left to Right: sRGB, AbodeRGB, WideGammutRGB, and ProPhotoRGB Color " 0353 "Profile Show in digiKam" 0354 msgstr "" 0355 0356 #: ../../color_management/working_space.rst:114 0357 msgid "" 0358 "But keeping all the possible colors comes at a price. It seems that any " 0359 "given digital image (pictures of daffodils with saturated yellows being one " 0360 "common exception) likely only contains a small subset of all the possible " 0361 "visible colors that your camera is capable of capturing. This small subset " 0362 "is easily contained in one of the smaller working spaces. Using a very large " 0363 "working space mean that editing your image (applying curves, saturation, " 0364 "etc.) can easily produce colors that your eventual output device (printer, " 0365 "monitor) simply cannot display." 0366 msgstr "" 0367 0368 #: ../../color_management/working_space.rst:116 0369 msgid "" 0370 "So the conversion from your working space to your output device space (say " 0371 "your printer) will have to remap the out of gamut colors in your edited " 0372 "image, some of which might even be totally imaginary, to your printer color " 0373 "space with its much smaller gamut, leading to inaccurate colors at best and " 0374 "at worst to banding (posterization - gaps in what should be a smooth color " 0375 "transition, say, across an expanse of blue sky) and clipping (your carefully " 0376 "crafted muted transitions across delicate shades of red, for example, might " 0377 "get remapped to a solid block of dull red after conversion to your printer's " 0378 "color space)." 0379 msgstr "" 0380 0381 #: ../../color_management/working_space.rst:118 0382 msgid "" 0383 "In other words, large gamut working spaces, improperly handled, can lead to " 0384 "lost information on output. Small gamut working spaces can clip information " 0385 "on input. Here is some oft-repeated advice:" 0386 msgstr "" 0387 0388 #: ../../color_management/working_space.rst:120 0389 msgid "For images intended for the web, use sRGB." 0390 msgstr "" 0391 0392 #: ../../color_management/working_space.rst:122 0393 msgid "" 0394 "For the most accuracy in your image editing (that is, making the most of " 0395 "your *bits* with the least risk of banding or clipping when you convert your " 0396 "image from your working space to an output space), use the smallest working " 0397 "space that includes all the colors in the scene that you photographed, plus " 0398 "a little extra room for those new colors you intentionally produce as you " 0399 "edit." 0400 msgstr "" 0401 0402 #: ../../color_management/working_space.rst:124 0403 msgid "" 0404 "If you are working in 8-bits rather than 16-bits, choose a smaller space " 0405 "rather than a larger space." 0406 msgstr "" 0407 0408 #: ../../color_management/working_space.rst:126 0409 msgid "" 0410 "For archival purposes, convert your RAW file to a 16-bit TIFF with a large " 0411 "gamut working space to avoid loosing color information. Then convert this " 0412 "archival TIFF to your working space of choice (saving the converted working " 0413 "TIFF under a new name, of course). See here for more details." 0414 msgstr "" 0415 0416 #: ../../color_management/working_space.rst:132 0417 msgid "digiKam Queue Manager Allows to Batch Convert Color Space" 0418 msgstr "" 0419 0420 #: ../../color_management/working_space.rst:135 0421 msgid "Gamma Properties" 0422 msgstr "" 0423 0424 #: ../../color_management/working_space.rst:137 0425 msgid "" 0426 "The gamma of a color profile dictates what power transform needs to take " 0427 "place to properly convert from an image's embedded color profile (perhaps " 0428 "your working color space or your camera color profile) to another color " 0429 "profile with a different gamma, such as your chosen working space, or the " 0430 "display profile used to display the image on the screen or perhaps from one " 0431 "working space to another, or perhaps from your working space to your " 0432 "printer's color space. `Libraw <https://www.libraw.org/>`_ outputs a 16-bit " 0433 "image with a linear gamma, which means that a histogram of the resulting " 0434 "image file shows the actual amount of light that each pixel on the camera " 0435 "sensor captured during the exposure (paraphrasing this page). (Which is why " 0436 "at present applying a camera profile to the Libraw output also requires " 0437 "applying an appropriate gamma transform to get to the desired working space, " 0438 "unless the camera profile also uses gamma=1.)" 0439 msgstr "" 0440 0441 #: ../../color_management/working_space.rst:139 0442 msgid "" 0443 "One practical consequence of the gamma of a working space is that the higher " 0444 "the gamma, the more discrete tones are available for editing in the shadows, " 0445 "with consequently fewer tones available in the highlights. Changing the " 0446 "gamma of an image redistributes the number of tones available in the lighter " 0447 "and darker areas of an image. Theoretically, if you are working on a very " 0448 "dark-toned (low key) image you might want a working space with a higher " 0449 "gamma. And if you are working on a high key image, say a picture taken in " 0450 "full noon sunlight of a wedding dress with snow as a backdrop, you might " 0451 "want to choose a working space with a lower gamma, so you have more " 0452 "available tonal gradations in the highlights." 0453 msgstr "" 0454 0455 #: ../../color_management/working_space.rst:141 0456 msgid "" 0457 "Theory aside, in the real world of real image editing, almost everyone uses " 0458 "working spaces with either a gamma of either 1.8 or 2.2. sRGB and L*-RGB are " 0459 "two notable exceptions." 0460 msgstr "" 0461 0462 #: ../../color_management/working_space.rst:143 0463 msgid "" 0464 "sRGB uses a transfer function close to that of a CRT (and thus not " 0465 "necessarily relevant to image editing or to display on an LCD). Unlike most " 0466 "other RGB color spaces the sRGB gamma can not be expressed as a single " 0467 "numerical value. The overall gamma is approximately 2.2, consisting of a " 0468 "linear (gamma 1.0) section near black, and a non-linear section elsewhere " 0469 "involving a 2.4 exponent and a gamma (slope of log output versus log input) " 0470 "changing from 1.0 through about 2.3, which makes for some complicated math " 0471 "during image processing." 0472 msgstr "" 0473 0474 #: ../../color_management/working_space.rst:145 0475 msgid "" 0476 "L*-RGB uses as its transfer function the same perceptually uniform transfer " 0477 "function as the CIELab color space. *When storing colors in limited " 0478 "precision values* using a perceptually uniform transfer function *can " 0479 "improve the reproduction of tones*." 0480 msgstr "" 0481 0482 #: ../../color_management/working_space.rst:147 0483 msgid "" 0484 "In addition to gamma=1.8 and gamma=2.2, the only other gamma for a working " 0485 "space that gets much mention or use is linear gamma, or gamma=1.0. As noted " 0486 "above, `Libraw <https://www.libraw.org/>`_ outputs linear gamma files if you " 0487 "ask for 16-bit output. Linear gamma is used in HDR (high dynamic range) " 0488 "imaging and also if one wants to avoid introducing gamma-induced errors into " 0489 "one's regular low dynamic range editing." 0490 msgstr "" 0491 0492 #: ../../color_management/working_space.rst:149 0493 msgid "" 0494 "**Gamma-induced errors** is a topic outside the scope of this manual but " 0495 "it's commonly-encountered that gamma-induced error that is caused by " 0496 "incorrectly calculating luminance in a nonlinear RGB working space. And in a " 0497 "similar vein, the calculations involved in mixing colors together to produce " 0498 "new colors (such as using a digital filter to add warmth to an image) result " 0499 "in gamma errors unless the new colors are calculated by first transforming " 0500 "all the relevant values back to their linear values." 0501 msgstr "" 0502 0503 #: ../../color_management/working_space.rst:151 0504 msgid "" 0505 "Unfortunately and despite their undeniable mathematical advantages, linear " 0506 "gamma working spaces have so few tones in the shadows that they are " 0507 "impossible to use for editing if one is working in 8-bit, and still " 0508 "problematic at 16-bit. When the day comes when we are all doing our editing " 0509 "on 32-bit files produced by our HDR cameras on our personal supercomputers, " 0510 "We can predict that we will all be using working spaces with gamma=1." 0511 msgstr "" 0512 0513 #: ../../color_management/working_space.rst:154 0514 msgid "Tonal Steps and Gamut Size" 0515 msgstr "" 0516 0517 #: ../../color_management/working_space.rst:156 0518 msgid "" 0519 "How many discrete tonal steps are there in a digital image? In an 8-bit " 0520 "image, you have 256 tonal steps from solid black to solid white. In a 16-bit " 0521 "image theoretically you have 65536 steps. But remember, those 16-bit started " 0522 "out as either 10-bit (=1024 steps), 12-bit (=4096 steps), or 14-bit (=16384 " 0523 "steps) as produced by the camera's A-to-D converter - the extra bits to " 0524 "reach 16-bit start out as just padding. The available tones are not " 0525 "distributed evenly from light to dark. In linear gamma mode (as the camera " 0526 "sensor sees things), there's a whole lot more tones in the highlights than " 0527 "in the shadows. Hence the advice, if you shoot RAW, to expose to the right " 0528 "but don't blow the highlights." 0529 msgstr "" 0530 0531 #: ../../color_management/working_space.rst:158 0532 msgid "" 0533 "One major consideration in choosing a working space is that some working " 0534 "spaces are bigger than others, meaning they cover more of the visible " 0535 "spectrum (and as a consequence include some imaginary colors - mathematical " 0536 "constructs that don't really exist). These bigger spaces offer the advantage " 0537 "of allowing you to keep all the colors captured by your camera and preserved " 0538 "by the `Lcms <https://www.littlecms.com/>`_ conversion from your camera " 0539 "profile to the super-wide-gamut profile connection space and out again to " 0540 "your chosen working space." 0541 msgstr "" 0542 0543 #: ../../color_management/working_space.rst:160 0544 msgid "" 0545 "But keeping all the possible colors comes at a price, as explained below. " 0546 "And it seems that any given digital image likely only contains a small " 0547 "subset of all the possible visible colors that your camera is capable of " 0548 "capturing. This small subset is easily contained in one of the smaller " 0549 "working spaces." 0550 msgstr "" 0551 0552 #: ../../color_management/working_space.rst:162 0553 msgid "" 0554 "Using a very large working space means that editing your image (applying " 0555 "curves, increasing saturation, etc.) can easily produce colors that your " 0556 "eventual output device (printer, monitor) simply cannot reproduce (you " 0557 "cannot see these colors while you're editing, either). So the conversion " 0558 "from your working space to your output device space (say your printer) will " 0559 "have to remap the out-of-gamut colors in your edited image, some of which " 0560 "might even be totally imaginary, to your printer color space with its much " 0561 "smaller color gamut." 0562 msgstr "" 0563 0564 #: ../../color_management/working_space.rst:164 0565 msgid "" 0566 "This remapping process will lead to inaccurate colors and loss of saturation " 0567 "at best. Even worse, the remapping can easily lead to banding (posterization " 0568 "- gaps in what should be a smooth color transition, across an expanse of " 0569 "blue sky) and clipping (e.g. your carefully crafted muted transitions across " 0570 "delicate shades of red, for example, might get remapped to a solid block of " 0571 "dull red after conversion to your printer's color space). Also, the experts " 0572 "say that 8-bit images just don't have enough tones to stretch across a wide " 0573 "gamut working space without banding and loss of saturation, even before " 0574 "conversion to an output space. So if you choose a large gamut working space, " 0575 "make sure you start with a 16-bit image." 0576 msgstr "" 0577 0578 #: ../../color_management/working_space.rst:171 0579 msgid "" 0580 "The digiKam Color Profile Properties Dialog Displaying BestRGB Information" 0581 msgstr "" 0582 0583 #: ../../color_management/working_space.rst:173 0584 msgid "" 0585 "To summarize, large gamut working spaces, improperly handled, can lead to " 0586 "lost information on output. Small gamut working spaces can clip information " 0587 "on input. Medium-sized gamut working spaces try to strike a happy medium." 0588 msgstr "" 0589 0590 #: ../../color_management/working_space.rst:175 0591 msgid "Here are some oft-repeated bits of advice on choosing a working space:" 0592 msgstr "" 0593 0594 #: ../../color_management/working_space.rst:177 0595 msgid "" 0596 "For images intended for the web, use (or at least convert the final image " 0597 "to) sRGB." 0598 msgstr "" 0599 0600 #: ../../color_management/working_space.rst:179 0601 msgid "" 0602 "For the most accuracy in your image editing (that is, making the most of " 0603 "your limited *bits* with the least risk of banding or clipping when you " 0604 "convert your image from your working space to an output space), use the " 0605 "smallest working space that includes all the colors in the scene that you " 0606 "photographed, plus a little extra room for those new colors you " 0607 "intentionally produce as you edit." 0608 msgstr "" 0609 0610 #: ../../color_management/working_space.rst:181 0611 msgid "" 0612 "If you are working in 8-bits rather than 16-bits, choose a smaller rather " 0613 "than a larger working space to avoid clipping and banding." 0614 msgstr "" 0615 0616 #: ../../color_management/working_space.rst:183 0617 msgid "" 0618 "For archival purposes, convert your RAW file to a 16-bit TIFF with a large " 0619 "gamut working space to avoid loosing color information. Then convert this " 0620 "archival TIFF to your medium-gamut or large-gamut working space of choice " 0621 "(saving the converted working TIFF under a new name, of course)." 0622 msgstr ""