Warning, /documentation/digikam-doc/locale/es/LC_MESSAGES/asset_management/data_protection.po is written in an unsupported language. File is not indexed.
0001 # Spanish translations for docs_digikam_org_asset_management___data_protection.po package. 0002 # Copyright (C) licensed under the <a href="https://creativecommons.org/licenses/by-sa/4.0/">Creative Commons License SA 4.0</a> unless stated otherwise 0003 # This file is distributed under the same license as the Digikam Manual package. 0004 # 0005 # Automatically generated, 2022. 0006 # Eloy Cuadra <ecuadra@eloihr.net>, 2022, 2023. 0007 msgid "" 0008 msgstr "" 0009 "Project-Id-Version: docs_digikam_org_asset_management___data_protection\n" 0010 "Report-Msgid-Bugs-To: \n" 0011 "POT-Creation-Date: 2023-12-30 00:35+0000\n" 0012 "PO-Revision-Date: 2023-04-12 22:27+0200\n" 0013 "Last-Translator: Eloy Cuadra <ecuadra@eloihr.net>\n" 0014 "Language-Team: Spanish <kde-l10n-es@kde.org>\n" 0015 "Language: es\n" 0016 "MIME-Version: 1.0\n" 0017 "Content-Type: text/plain; charset=UTF-8\n" 0018 "Content-Transfer-Encoding: 8bit\n" 0019 "Plural-Forms: nplurals=2; plural=n != 1;\n" 0020 "X-Generator: Lokalize 23.03.90\n" 0021 0022 #: ../../asset_management/data_protection.rst:1 0023 msgid "Protect Your Images from Data Corruption and Loss" 0024 msgstr "Proteja sus imágenes de la pérdida y corrupción de datos" 0025 0026 #: ../../asset_management/data_protection.rst:1 0027 msgid "" 0028 "digiKam, documentation, user manual, photo management, open source, free, " 0029 "learn, easy, disk errors, disk failures, power surges, ECC, transmission " 0030 "errors, storage media deterioration, recovery, redundancy, disaster " 0031 "prevention, lifetime, temperature, data size, common myths, metadata, IPTC " 0032 "stored in image files, XMP files associated, keep the originals, storage, " 0033 "scalability, media, retrieval of images and metadata, copying image data " 0034 "over to the next generation of media, applications, operating systems, " 0035 "virtualization, viewing device, use of the www, ZFS, BTRFS" 0036 msgstr "" 0037 0038 #: ../../asset_management/data_protection.rst:14 0039 msgid "Data Corruption and Loss" 0040 msgstr "Pérdida y corrupción de datos" 0041 0042 #: ../../asset_management/data_protection.rst:16 0043 msgid "Contents" 0044 msgstr "Contenido" 0045 0046 #: ../../asset_management/data_protection.rst:19 0047 msgid "Main Factors of Digital Data Loss" 0048 msgstr "Factores principales de la pérdida de datos digitales" 0049 0050 #: ../../asset_management/data_protection.rst:21 0051 msgid "" 0052 "Of course we're not talking about losing Blue-rays on the road or in a fire " 0053 "- that kind of loss is just the same as traditional paper copies or " 0054 "negatives. We are talking about problems with the so called *New Media*." 0055 msgstr "" 0056 "Por supuesto, no nos referimos a la pérdida de un Blu-ray durante un viaje o " 0057 "en un incendio (ese tipo de pérdidas son idénticas a las de las " 0058 "tradicionales copias en papel o a las de los negativos. Aludimos a los " 0059 "problemas que afectan a los *nuevos medios*." 0060 0061 #: ../../asset_management/data_protection.rst:23 0062 msgid "" 0063 "Problems with digital data can roughly be categorized into the following " 0064 "areas of concern:" 0065 msgstr "" 0066 "Los problemas con los datos digitales se pueden clasificar aproximadamente " 0067 "en las siguientes fuentes de problemas:" 0068 0069 #: ../../asset_management/data_protection.rst:25 0070 msgid "" 0071 "The physical deterioration of the media (all media deteriorate at different " 0072 "time scales)." 0073 msgstr "" 0074 "El deterioro físico de los medios (todos los soportes físicos se deterioran " 0075 "en diferentes escalas de tiempo)." 0076 0077 #: ../../asset_management/data_protection.rst:27 0078 msgid "Undetected transmission errors during data transfer." 0079 msgstr "" 0080 "Errores de transmisión no detectados durante la transferencia de datos." 0081 0082 #: ../../asset_management/data_protection.rst:29 0083 msgid "" 0084 "The lack of support for long-date, undoubtedly proprietary, digital formats." 0085 msgstr "" 0086 "La falta de soporte para formatos digitales indiscutiblemente propietarios a " 0087 "largo plazo." 0088 0089 #: ../../asset_management/data_protection.rst:31 0090 msgid "Ancient hardware." 0091 msgstr "Hardware antiguo." 0092 0093 #: ../../asset_management/data_protection.rst:33 0094 msgid "" 0095 "Kroll Ontrack, the worlds largest data recovery firm, have some interesting " 0096 "statistics on what actually causes data loss." 0097 msgstr "" 0098 "Kroll Ontrack, la empresa más grande de recuperación de datos, muestra " 0099 "algunas interesantes estadísticas sobre qué es lo que produce pérdida de " 0100 "datos." 0101 0102 #: ../../asset_management/data_protection.rst:36 0103 msgid "Cause of data loss" 0104 msgstr "Causa de la pérdida de datos" 0105 0106 #: ../../asset_management/data_protection.rst:36 0107 msgid "Perception" 0108 msgstr "Percepción" 0109 0110 #: ../../asset_management/data_protection.rst:36 0111 msgid "Reality" 0112 msgstr "Realidad" 0113 0114 #: ../../asset_management/data_protection.rst:38 0115 msgid "Hardware or system problem" 0116 msgstr "Problemas de hardware o del sistema" 0117 0118 #: ../../asset_management/data_protection.rst:38 0119 msgid "78%" 0120 msgstr "78%" 0121 0122 #: ../../asset_management/data_protection.rst:38 0123 msgid "56%" 0124 msgstr "56%" 0125 0126 #: ../../asset_management/data_protection.rst:39 0127 msgid "Human error" 0128 msgstr "Error humano" 0129 0130 #: ../../asset_management/data_protection.rst:39 0131 msgid "11%" 0132 msgstr "11%" 0133 0134 #: ../../asset_management/data_protection.rst:39 0135 msgid "26%" 0136 msgstr "26%" 0137 0138 #: ../../asset_management/data_protection.rst:40 0139 msgid "Software corruption or problem" 0140 msgstr "Daños o problemas del software" 0141 0142 #: ../../asset_management/data_protection.rst:40 0143 msgid "7%" 0144 msgstr "7%" 0145 0146 #: ../../asset_management/data_protection.rst:40 0147 msgid "9%" 0148 msgstr "9%" 0149 0150 #: ../../asset_management/data_protection.rst:41 0151 msgid "Computer viruses" 0152 msgstr "Virus informáticos" 0153 0154 #: ../../asset_management/data_protection.rst:41 0155 msgid "2%" 0156 msgstr "2%" 0157 0158 #: ../../asset_management/data_protection.rst:41 0159 msgid "4%" 0160 msgstr "4%" 0161 0162 #: ../../asset_management/data_protection.rst:42 0163 msgid "Disaster" 0164 msgstr "Desastre" 0165 0166 #: ../../asset_management/data_protection.rst:42 0167 msgid "1-2%" 0168 msgstr "1-2%" 0169 0170 #: ../../asset_management/data_protection.rst:45 0171 msgid "So let us analyze those cases step by step." 0172 msgstr "De modo que pasaremos a analizar estos casos paso a paso." 0173 0174 #: ../../asset_management/data_protection.rst:50 0175 msgid "Storage Deterioration" 0176 msgstr "Deterioro del almacenamiento" 0177 0178 #: ../../asset_management/data_protection.rst:52 0179 msgid "" 0180 "Devices listed below are sorted by data speed access feature, from the less " 0181 "faster to the most faster." 0182 msgstr "" 0183 0184 #: ../../asset_management/data_protection.rst:55 0185 msgid "Magnetic Media" 0186 msgstr "Medios magnéticos" 0187 0188 #: ../../asset_management/data_protection.rst:57 0189 msgid "" 0190 "Magnetic tapes are used in backup systems, much more in professional " 0191 "environments than in home use. Tapes have issues with data retention and " 0192 "changing technology, but they are safer in one aspect than optical drives: " 0193 "they are less exposed to scratches and dirt and writing deficiencies. On the " 0194 "other hand they are susceptible to magnetic fields. Throw a magnet next to a " 0195 "tape and it's gone. Tapes should be re-copied every 5-8 years, otherwise too " 0196 "many bits will fail and escape the checksum protection. The downside of " 0197 "magnetic tapes is often the recorder price and the restore time (20x longer " 0198 "than from HDD). Tape backup system have seen their best days." 0199 msgstr "" 0200 0201 #: ../../asset_management/data_protection.rst:60 0202 msgid "Optical Drives" 0203 msgstr "Unidades ópticas" 0204 0205 #: ../../asset_management/data_protection.rst:62 0206 msgid "" 0207 "Physical deterioration of the media happens more rapidly with paper and CD-" 0208 "Rs than the average of film. Yet while film lasts longer (sometimes decades " 0209 "longer) than other forms of media, the right kind of backup of digital media " 0210 "never loses anything. Film decays - digital 1's and 0's do not, and film " 0211 "starts to decay the moment it's created and developed. It will never have " 0212 "the same color, contrast, etc. that it did have a moment before. Digital " 0213 "doesn't do that. However, digital is susceptible to corruption. And yes, " 0214 "physical media such as floppies and magnetic hard drives are also " 0215 "susceptible to the decay of the medium, just like CDs are. They just last " 0216 "longer." 0217 msgstr "" 0218 0219 #: ../../asset_management/data_protection.rst:64 0220 msgid "" 0221 "To combat the problem of optical drives, they need to be properly cared for " 0222 "and not trusted for more than a few years. Thankfully you can purchase " 0223 "archive-quality CDs and DVDs which last longer, though they are much more " 0224 "difficult to obtain and are much more expensive. There are offers out there " 0225 "for gold-plated optical drive, few euros a piece claiming 100 years storage " 0226 "life (if you care to believe it)." 0227 msgstr "" 0228 0229 #: ../../asset_management/data_protection.rst:66 0230 msgid "" 0231 "Optical disks may become unreadable, but you can reduce the risk using good " 0232 "disks and a good recorder, and storing them in a correct way. The best " 0233 "optical drive recorders are not much more expensive than the cheapest, but " 0234 "they write in a much more reliable way. It's a matter of choosing the right " 0235 "one." 0236 msgstr "" 0237 0238 #: ../../asset_management/data_protection.rst:68 0239 msgid "" 0240 "Essentially, optical drives are very prone to errors, even in a freshly " 0241 "written state. That's why they are heavily protected with a checksum " 0242 "mechanism (75% of data are effective data, the rest is formatting and " 0243 "checksum overhead). But even with that massive amount of protection they " 0244 "will suffer deterioration from chemical aging, ultra-violet exposure, " 0245 "scratches, dust, etc." 0246 msgstr "" 0247 0248 #: ../../asset_management/data_protection.rst:70 0249 msgid "" 0250 "For damaged optical drives, Wikipedia `list all common applications <https://" 0251 "en.wikipedia.org/wiki/Data_recovery#List_of_data_recovery_software>`_ " 0252 "designed to get data from damaged floppies, hard drives, flash media such as " 0253 "camera memory and USB drives, and so forth." 0254 msgstr "" 0255 0256 #: ../../asset_management/data_protection.rst:72 0257 msgid "" 0258 "Dual-layer optical media Blu-ray disk can store 50 GB, almost six times the " 0259 "capacity of a dual layer DVD at 8.5 GB. Everything that has been said about " 0260 "CDs/DVDs applies to Blu-ray disks as well." 0261 msgstr "" 0262 0263 #: ../../asset_management/data_protection.rst:74 0264 msgid "" 0265 "Best practice: burn them slowly with a good recorder on archive quality " 0266 "media in an open, non-proprietary format, read the data back to verify, " 0267 "label them with some descriptive text + date & author, lock them away where " 0268 "it is clean, dark, animal safe and dry. And do not forget to copy them over " 0269 "to the next generation of media before you throw away your last piece of " 0270 "hardware or software able to read them." 0271 msgstr "" 0272 0273 #: ../../asset_management/data_protection.rst:77 0274 msgid "Hard Disks" 0275 msgstr "Discos duros" 0276 0277 #: ../../asset_management/data_protection.rst:79 0278 msgid "" 0279 "Hard Disk (HDD) manufacturers keep their statistics to themselves. A " 0280 "manufacturer guaranty buys you a new disk, but no data. Google for One has " 0281 "done a large scale study on `HDD <https://en.wikipedia.org/wiki/" 0282 "Hard_disk_drive>`_ failure mechanisms: `Disk Failures study <https://" 0283 "research.google.com/archive/disk_failures.pdf>`_." 0284 msgstr "" 0285 0286 #: ../../asset_management/data_protection.rst:81 0287 msgid "" 0288 "In a nutshell: Disks run longest when operating between 35°C and 45°C, at " 0289 "lower temperatures the error rates increases dramatically. Controller parts " 0290 "(electronics) are the foremost sources of failure, SMART does not diagnose " 0291 "any of this. Some `SMART <https://en.wikipedia.org/wiki/Self-Monitoring," 0292 "_Analysis_and_Reporting_Technology>`_ errors are indicative of imminent " 0293 "failure, in particular scan errors and relocation counts. Lifetime " 0294 "expectancy is 4-5 years." 0295 msgstr "" 0296 0297 #: ../../asset_management/data_protection.rst:83 0298 msgid "" 0299 "In general and contrary to intuition or ecological considerations, running a " 0300 "hard drive permanently results in a longer lifetime than switching it on and " 0301 "off all the time. It has even been reported that aggressive power management " 0302 "spinning down the drive can harm it quickly. Making it working hard shortens " 0303 "the lifetime somewhat. The worst factors for HDD probably are vibrations, " 0304 "shocks, and cold temperatures." 0305 msgstr "" 0306 0307 #: ../../asset_management/data_protection.rst:85 0308 msgid "" 0309 "If your disk is making weird noises, normal file recovery software isn’t " 0310 "going to work. Do a quick backup if that is going to happen to you. (Use dd " 0311 "utility if possible, not a normal file backup since dd reads in a smooth, " 0312 "spiraling stream from beginning to end and doesn't stress the mechanics). " 0313 "There are specialist companies that can recover data from otherwise " 0314 "destroyed drive, but they are very expensive." 0315 msgstr "" 0316 0317 #: ../../asset_management/data_protection.rst:87 0318 msgid "" 0319 "Linux `SmartMonTools <https://en.wikipedia.org/wiki/Smartmontools>`_ suite " 0320 "allows to query the storage hardware devices for future failure. We highly " 0321 "recommend to use this kind of tool on your computer." 0322 msgstr "" 0323 0324 #: ../../asset_management/data_protection.rst:90 0325 msgid "Solid State Drives" 0326 msgstr "Unidades de estado sólido" 0327 0328 #: ../../asset_management/data_protection.rst:92 0329 msgid "" 0330 "`SSDs <https://en.wikipedia.org/wiki/Solid-state_drive>`_ are mechanically " 0331 "more robust than HDDs and suffer much less on that front when they are " 0332 "plugged into the computer. They will replace HDD in time as capacity, " 0333 "robustest, and price become more and more a good solution as permanent data " 0334 "storage devices." 0335 msgstr "" 0336 0337 #: ../../asset_management/data_protection.rst:94 0338 msgid "" 0339 "In case of use as external device, one major cause for data loss (often " 0340 "recoverable) is the unsafe removal of SSDs from a computer. Before data is " 0341 "saved from a computer memory to any attached device, it remains for some " 0342 "time in buffers. In hard drives this means seconds at most, whereas with " 0343 "SSDs it can be tens of minutes. Therefore, before you disconnect a flash " 0344 "device, always activate data flushing through software (often called *safely " 0345 "remove device*)." 0346 msgstr "" 0347 0348 #: ../../asset_management/data_protection.rst:97 0349 msgid "Non-Volatile Memory" 0350 msgstr "Memoria no volátil" 0351 0352 #: ../../asset_management/data_protection.rst:99 0353 msgid "" 0354 "`NVM Express (NVMe) <https://en.wikipedia.org/wiki/NVMe>`_ for Non-Volatile " 0355 "Memory is a logical-device interface for accessing a computer's non-volatile " 0356 "storage media attached PCI Express (PCIe) bus. It use same very fast NAND " 0357 "flash memory used in SSDs, but use the M.2 cards interface instead the " 0358 "slower mSATA used with older HDDs." 0359 msgstr "" 0360 0361 #: ../../asset_management/data_protection.rst:101 0362 msgid "" 0363 "NVMe allows host hardware and software to fully exploit the levels of " 0364 "parallelism possible in modern SSDs. NVMe reduces I/O overhead and brings " 0365 "various performance improvements relative to previous SSDs. mSATA interface " 0366 "protocols were developed for use with far slower HDDs where a very lengthy " 0367 "delay exists between a request and data transfer, where data speeds are much " 0368 "slower than RAM speeds." 0369 msgstr "" 0370 0371 #: ../../asset_management/data_protection.rst:103 0372 msgid "" 0373 "For a viability viewpoint, as NVMe devices uses the same hardware than SSDs " 0374 "to store data, the robustness must be the same." 0375 msgstr "" 0376 0377 #: ../../asset_management/data_protection.rst:107 0378 msgid "" 0379 "**In all cases SSDs or NVMe as internal devices are the more modern and " 0380 "efficient solution to host the digiKam databases and the collections.**" 0381 msgstr "" 0382 0383 #: ../../asset_management/data_protection.rst:110 0384 msgid "Power Supply Failures" 0385 msgstr "Fallos de suministro eléctrico" 0386 0387 #: ../../asset_management/data_protection.rst:113 0388 msgid "Power Surges" 0389 msgstr "Sobretensiones" 0390 0391 #: ../../asset_management/data_protection.rst:115 0392 msgid "" 0393 "As much as 1% of all computers are affected by lightning and power surges " 0394 "every year." 0395 msgstr "" 0396 0397 #: ../../asset_management/data_protection.rst:117 0398 msgid "" 0399 "This is about total data loss due to power surges. Of course you can have " 0400 "the occasional data loss due to power loss before saving files. But those " 0401 "losses can normally be restored without major difficulty." 0402 msgstr "" 0403 0404 #: ../../asset_management/data_protection.rst:119 0405 msgid "" 0406 "You don’t have to wait for the next thunderstorm to be concerned about how a " 0407 "sudden fluctuation in electric power may affect your computer system. Recent " 0408 "statistics have shown that as much as 63 percent of all electronics " 0409 "casualties are due to power problems, and most computers are subject to two " 0410 "or more power anomalies a day. Since power surges or blackouts can occur " 0411 "anywhere and at any time, it only makes sense to protect your computer by " 0412 "investing in some sort of surge protection device." 0413 msgstr "" 0414 0415 #: ../../asset_management/data_protection.rst:122 0416 msgid "How Surges Happen" 0417 msgstr "Cómo ocurre una sobretensión" 0418 0419 #: ../../asset_management/data_protection.rst:124 0420 msgid "" 0421 "A power surge occurs when the power line voltage increases over nominal " 0422 "values for more than 10 milliseconds. Sixty percent of all power surges are " 0423 "caused from within the home or office, generally when a device with a motor " 0424 "(such as a hair dryer, refrigerator, or water pump) shuts off and the power " 0425 "it was using is diverted elsewhere as excess voltage. The remaining 40 " 0426 "percent of power surges are generated by factors such as lightning, utility " 0427 "grid switching, line slapping, poor wiring, and so on." 0428 msgstr "" 0429 0430 #: ../../asset_management/data_protection.rst:126 0431 msgid "" 0432 "While most average electricity-using devices are not affected by power " 0433 "surges, devices relying on computer chips and high-speed microprocessors are " 0434 "susceptible to serious damage. For your computer, power anomalies can result " 0435 "in keyboard lockup, complete data loss, hardware degradation, damaged " 0436 "motherboards, and more. Failure to protect yourself from the inevitable can " 0437 "result in a loss of both time and money." 0438 msgstr "" 0439 0440 #: ../../asset_management/data_protection.rst:129 0441 msgid "Surge Protectors" 0442 msgstr "Protectores de sobretensiones" 0443 0444 #: ../../asset_management/data_protection.rst:131 0445 msgid "" 0446 "The most common defense against power surges is a surge protector or " 0447 "suppressor, a device that works by absorbing some of the excess energy and " 0448 "diverting the rest of it to the ground. These are usually found in the form " 0449 "of a power strip (one of those long devices that have six or so outlets and " 0450 "a single, grounded plug). Bear in mind, however, that not every power strip " 0451 "serves as a surge protector." 0452 msgstr "" 0453 0454 #: ../../asset_management/data_protection.rst:133 0455 msgid "" 0456 "When selecting your surge protector, you want to be sure it is listed as " 0457 "meeting the UL 1449 standard, which guarantees a certain minimum of " 0458 "protection. You should also look for one that offers protection against " 0459 "lightning (not every one does) and provides insurance for equipment that is " 0460 "properly attached." 0461 msgstr "" 0462 0463 #: ../../asset_management/data_protection.rst:135 0464 msgid "" 0465 "Because a power surge can follow any path to your computer, be sure that " 0466 "each peripheral connected to your system is protected. This includes your " 0467 "phone line or cable modem, as power can surge through these routes as well. " 0468 "A number of manufacturers are now producing surge suppressors that feature a " 0469 "phone jack for your modem along with the electrical outlets, while others " 0470 "have coaxial cable jacks for those who use a cable modem or TV tuner card." 0471 msgstr "" 0472 0473 #: ../../asset_management/data_protection.rst:137 0474 msgid "" 0475 "If you have a notebook computer, you will want to carry a surge suppressor " 0476 "as well. A variety of suppressors designed specifically for notebooks are " 0477 "available, small in size and possessing both electric and phone outlets that " 0478 "make them ideal for use on the road." 0479 msgstr "" 0480 0481 #: ../../asset_management/data_protection.rst:140 0482 msgid "Uninterruptible Power Supply" 0483 msgstr "Suministro de alimentación ininterrumpida" 0484 0485 #: ../../asset_management/data_protection.rst:142 0486 msgid "" 0487 "While a surge suppressor will protect your system from minor fluctuations in " 0488 "the power lines, it won’t help you if the power should black out completely. " 0489 "Even an outage of just a few seconds can result in the loss of valuable " 0490 "data, so you might find it worthwhile to invest in an **Uninterruptible " 0491 "Power Supply** (UPS)." 0492 msgstr "" 0493 0494 #: ../../asset_management/data_protection.rst:144 0495 msgid "" 0496 "Besides serving as surge suppressors, these devices automatically switch to " 0497 "battery power when a power outage occurs, giving you the opportunity to save " 0498 "data and shut down your system. Some models will even allow you to keep " 0499 "working until power is restored. When purchasing a UPS, be sure that it has " 0500 "the same qualities that you would seek in a surge suppressor, but also check " 0501 "out the battery life and included software." 0502 msgstr "" 0503 0504 #: ../../asset_management/data_protection.rst:146 0505 msgid "" 0506 "Considering the potential risk to your computing system, ensuring its safety " 0507 "from power disturbances is a worthwhile investment. A quality surge " 0508 "suppressor or a 500W UPS are not too expensive for the peace of mind you’ll " 0509 "gain knowing your computer is well protected. In the very least pull all " 0510 "lines to your computer when you go on holidays." 0511 msgstr "" 0512 0513 #: ../../asset_management/data_protection.rst:149 0514 msgid "Safeguarding Policy" 0515 msgstr "" 0516 0517 #: ../../asset_management/data_protection.rst:152 0518 msgid "Web Storage Services" 0519 msgstr "Servicios de almacenamiento web" 0520 0521 #: ../../asset_management/data_protection.rst:154 0522 msgid "" 0523 "Amazon Web Services includes S3 - Simple Storage Service. With appropriate " 0524 "configuration, you can mount S3 as a drive on Linux, Mac, and Windows " 0525 "systems, allowing you to use it as a backup destination for your favorite " 0526 "software. Google Shared Storage is another popular offer where one can store " 0527 "infinite amount of data." 0528 msgstr "" 0529 0530 #: ../../asset_management/data_protection.rst:156 0531 msgid "" 0532 "It is expensive compared to hard drives at home. And you have to transfer " 0533 "the images over the (a comparatively slow) Internet." 0534 msgstr "" 0535 0536 #: ../../asset_management/data_protection.rst:158 0537 msgid "" 0538 "We think as a safeguard against localized data loss of the most essential " 0539 "images it's not a bad idea at all, but it is not a general backup solution, " 0540 "much too slow for that." 0541 msgstr "" 0542 0543 #: ../../asset_management/data_protection.rst:160 0544 msgid "" 0545 "Google Photo, and Flickr provide online storage services specialist on " 0546 "photographie. Their free space is limited and you don't want to have full " 0547 "resolution images online. But the pro-accounts offer more." 0548 msgstr "" 0549 0550 #: ../../asset_management/data_protection.rst:162 0551 msgid "" 0552 "In terms of data retention the web space solution is probably pretty safe. " 0553 "Transmission errors are corrected (thanks to the TCP protocol) and the big " 0554 "companies usually have backup included plus distributed storage so that they " 0555 "are disaster proof within themselves." 0556 msgstr "" 0557 0558 #: ../../asset_management/data_protection.rst:168 0559 msgid "digiKam Provide a Tool to Export Items to iNaturalist Web Service" 0560 msgstr "" 0561 0562 #: ../../asset_management/data_protection.rst:171 0563 msgid "Transmission Errors" 0564 msgstr "Errores de transmisión" 0565 0566 #: ../../asset_management/data_protection.rst:173 0567 msgid "" 0568 "Data does not only get lost from storage devices, it also gets lost when " 0569 "traveling inside the computer or across networks (although the network " 0570 "traffic itself via TCP is error protected). Errors occur on buses and in " 0571 "memory spaces. Consumer hardware has no protection against those bit errors, " 0572 "whereas it is worthwhile to look into such. You can buy ECC (error code " 0573 "correction) protected memory (which is expensive, granted). With `ECC RAM " 0574 "<https://en.wikipedia.org/wiki/ECC_memory>`_ at least the memory will be " 0575 "scrubbed for single bit errors and corrected. Double bit errors would escape " 0576 "that scheme but they occur too infrequently." 0577 msgstr "" 0578 0579 #: ../../asset_management/data_protection.rst:179 0580 msgid "The Data Workflow Between Application and Storage Media" 0581 msgstr "" 0582 0583 #: ../../asset_management/data_protection.rst:181 0584 msgid "" 0585 "This diagram depicts the transmission chain elements in a computer, all " 0586 "transitions are susceptible to transmission errors. The Linux `ZFS <https://" 0587 "en.wikipedia.org/wiki/ZFS>`_ and `BTRFS <https://en.wikipedia.org/wiki/" 0588 "Btrfs>`_ file system at least ensure the OS to disk path of data integrity " 0589 "under Linux." 0590 msgstr "" 0591 0592 #: ../../asset_management/data_protection.rst:183 0593 msgid "" 0594 "The Byte Error Rate (BER) for memory and transmission channels is in the " 0595 "order of 1 in 10 Million (10E-7 bit). That just means that 1 in 3000 images " 0596 "has an error only due to transmission problems. Now how dramatic that is for " 0597 "an image is left to chance, it could mean that the image is destroyed or " 0598 "that a pixel somewhere changed its value, due to the compression used on " 0599 "almost all images one cannot predict the gravity of a single bit error " 0600 "impact. Often one sees some partial images instead of the full image." 0601 msgstr "" 0602 0603 #: ../../asset_management/data_protection.rst:185 0604 msgid "" 0605 "The worst of all that is that nobody tells you when a transmission error " 0606 "occurs, not your hardware. All those glitches go down unheard until one day " 0607 "you open the photograph, and to your surprise it's broken. It is quite " 0608 "worrisome that there should be no protection within a computer, nobody seems " 0609 "to have thought of it. The Internet (TCP protocol) is much saver as a data " 0610 "path than inside a computer." 0611 msgstr "" 0612 0613 #: ../../asset_management/data_protection.rst:187 0614 msgid "" 0615 "Flaky power supplies are another source of transmission losses because they " 0616 "create interference with the data streams. With normal files systems those " 0617 "errors go unnoticed." 0618 msgstr "" 0619 0620 #: ../../asset_management/data_protection.rst:193 0621 msgid "The Storage Media Number of Failure Per Year" 0622 msgstr "" 0623 0624 #: ../../asset_management/data_protection.rst:195 0625 msgid "" 0626 "Even if you are not overly concerned today with transmission problems, have " 0627 "a look into the future at illustration. Already in 2010 we'll see thousands " 0628 "of errors per year." 0629 msgstr "" 0630 0631 #: ../../asset_management/data_protection.rst:198 0632 msgid "Future of File-systems" 0633 msgstr "El futuro de los sistemas de archivos" 0634 0635 #: ../../asset_management/data_protection.rst:200 0636 msgid "" 0637 "`ZFS <https://en.wikipedia.org/wiki/ZFS>`_ from Oracle seems to be one of " 0638 "two candidates to deal with disk errors on a low level, and it is highly " 0639 "scalable. It is Open Source, heavily patented, comes with an GPL " 0640 "incompatible license, and is available on Linux and macOS." 0641 msgstr "" 0642 0643 #: ../../asset_management/data_protection.rst:202 0644 msgid "" 0645 "Oracle has also started an initiative with its `BTRFS <https://en.wikipedia." 0646 "org/wiki/Btrfs>`_ file system. It employs the same protection technique as " 0647 "**ZFS** does, and it's available on Linux." 0648 msgstr "" 0649 0650 #: ../../asset_management/data_protection.rst:205 0651 msgid "Human Errors" 0652 msgstr "Errores humanos" 0653 0654 #: ../../asset_management/data_protection.rst:208 0655 msgid "Theft And Accidents" 0656 msgstr "Robo y accidentes" 0657 0658 #: ../../asset_management/data_protection.rst:210 0659 msgid "" 0660 "Do not underestimate it. Those two factor account for 86% of notebook and " 0661 "46% for desktop system data losses. For notebooks, theft counts for 50% " 0662 "alone." 0663 msgstr "" 0664 0665 #: ../../asset_management/data_protection.rst:213 0666 msgid "Malware" 0667 msgstr "Malware" 0668 0669 #: ../../asset_management/data_protection.rst:215 0670 msgid "" 0671 "Data loss due to viruses is less grave than common wisdom make you believe. " 0672 "It accounts for less damage than theft or re-installations, for example. And " 0673 "it is limited to Microsoft OS users. Apple users experience very few viruses " 0674 "and under Linux they haven't been around for quite some time now." 0675 msgstr "" 0676 0677 #: ../../asset_management/data_protection.rst:218 0678 msgid "Human and Data Loss" 0679 msgstr "" 0680 0681 #: ../../asset_management/data_protection.rst:220 0682 msgid "" 0683 "Human error, as in everything, is a major problem in data loss. Take a deep " 0684 "breath and stop. Panic is a common reaction, and people do really stupid " 0685 "things. Experienced users will pull the wrong drive from a `RAID <https://en." 0686 "wikipedia.org/wiki/RAID>`_ array or reformat a drive, destroying all their " 0687 "information. Acting without thinking is dangerous to your data. Stop " 0688 "stressing about the loss and don’t do anything to the disk. Better yet, stop " 0689 "using the computer until you have a plan. Sit down and explain you plan to a " 0690 "laymen or better, laywoman. You will be amazed how many stupid ideas you'll " 0691 "discover yourself in such an exercise." 0692 msgstr "" 0693 0694 #: ../../asset_management/data_protection.rst:222 0695 msgid "" 0696 "If your disk is making weird noises, normal file recovery software isn’t " 0697 "going to work. Do a quick backup if that is going to happen to you. If the " 0698 "drive is still spinning and you can’t find your data, look for a data " 0699 "recovery utility and backup to another computer or drive. An Universal and " 0700 "powerful solution can be to use `CloneZilla open-source suite <https://en." 0701 "wikipedia.org/wiki/Clonezilla>`_. The important thing is to download them " 0702 "onto another drive, either on another computer, or onto a USB thumb drive or " 0703 "hard disk. It is good practice to save the recovered data to another disk. " 0704 "`dd tool <https://en.wikipedia.org/wiki/Dd_(Unix)>`_ is your friend on Linux " 0705 "systems." 0706 msgstr "" 0707 0708 #: ../../asset_management/data_protection.rst:225 0709 msgid "Common Myths Dispelled" 0710 msgstr "" 0711 0712 #: ../../asset_management/data_protection.rst:227 0713 msgid "We would like to dispel some common myths:" 0714 msgstr "" 0715 0716 #: ../../asset_management/data_protection.rst:229 0717 msgid "" 0718 "Open Source file systems are less prone to data loss than proprietary " 0719 "systems: Wrong, NTFS is rather a tiny notch better than ext4, ReiserFs, JFS, " 0720 "XFS, to name just the most popular file systems that often come as default " 0721 "storage format disk used by distributions." 0722 msgstr "" 0723 0724 #: ../../asset_management/data_protection.rst:231 0725 msgid "" 0726 "Journalize files systems prevent data corruption/loss: Wrong, they only " 0727 "speed up the scan process in case of a sudden interrupt during operation and " 0728 "prevent ambiguous states. But if a file was not entirely saved before the " 0729 "mishap, it'll be lost." 0730 msgstr "" 0731 0732 #: ../../asset_management/data_protection.rst:233 0733 msgid "" 0734 "`RAID <https://en.wikipedia.org/wiki/RAID>`_ systems prevent data corruption/" 0735 "loss: Mostly wrong, **RAID 0 and 1** prevent you from nothing, **RAID 5** " 0736 "can prevent data loss due to disk-failures (but not from disk or file system " 0737 "errors). Many low-end RAID controllers (most mother board controllers are) " 0738 "don’t report problems, figuring you’ll never notice. If you do notice, " 0739 "months later, what is the chance that you’ll know it was the controller’s " 0740 "fault? One insidious problem is corruption of **RAID 5** parity data. It is " 0741 "pretty simple to check a file by reading it and matching the metadata. " 0742 "Checking parity data is much more difficult, so you typically won’t see " 0743 "parity errors until a rebuild. Then, of course, it is too late." 0744 msgstr "" 0745 0746 #: ../../asset_management/data_protection.rst:235 0747 msgid "" 0748 "Viruses are the biggest thread to digital data: Wrong. Theft, and human " 0749 "errors are the primary cause of data loss." 0750 msgstr "" 0751 0752 #: ../../asset_management/data_protection.rst:238 0753 msgid "Storage Volume Estimation" 0754 msgstr "Estimación del volumen de almacenamiento" 0755 0756 #: ../../asset_management/data_protection.rst:240 0757 msgid "" 0758 "Digital camera sensors are 1-2 aperture stops away from fundamental physical " 0759 "limitations. What we mean is this: as technology evolves, there is a natural " 0760 "limit to its progress. Sensitivity and noise characteristics for any kind of " 0761 "light sensor are not far from that limit." 0762 msgstr "" 0763 0764 #: ../../asset_management/data_protection.rst:242 0765 msgid "" 0766 "Today's cameras tend towards 50 mega pixels sensors, although this " 0767 "resolution is already too high for compact cameras and deteriorates the end " 0768 "result. Given the sensor size and quality of optics, 12 mega pixels are " 0769 "optimum for compact cameras. Even DSLR cameras run into their limits at " 0770 "20-24 mega pixels, for higher resolutions one has to go for full frame " 0771 "sensors (24x36mm) or even bigger formats." 0772 msgstr "" 0773 0774 #: ../../asset_management/data_protection.rst:244 0775 msgid "" 0776 "So, taking into account the manufacturer mega pixel propaganda it seems save " 0777 "to say that the bulk of future cameras will see less than 30 mega pixels. " 0778 "This gives us an estimation for the necessary storage space per photograph " 0779 "in the long run: <40 MB per image. Even if file versioning will be " 0780 "introduced (grouping of variations of a photograph under one file " 0781 "reference), the trend is to implement scripting of changes so that a small " 0782 "overhead will be recorded only and not a whole different image per version. " 0783 "With faster hardware this concept will see it's maturity quite soon." 0784 msgstr "" 0785 0786 #: ../../asset_management/data_protection.rst:246 0787 msgid "" 0788 "In order to estimate the amount of storage space you have to plan for, " 0789 "simply determine the number of photographs you take per year (easy with :ref:" 0790 "`digiKam's timeline sidebar tab <timeline_view>`) and multiply it by 40 MB. " 0791 "Most users will keep less than 2000 pictures per year which requires less " 0792 "than 80 GB/year. Assuming that you will change your hard disk (or whatever " 0793 "media in the future) every 4-5 years, the natural increase in storage " 0794 "capacity will suffice to keep you afloat." 0795 msgstr "" 0796 0797 #: ../../asset_management/data_protection.rst:248 0798 msgid "" 0799 "The more ambitious ones out there will need more space, much more maybe. " 0800 "Think of buying a file server, Giga-Ethernet comes integrated into " 0801 "motherboards today and it's a flick to fetch the files over the local " 0802 "network. Speaking about modern mobos: they now the capability to SATA media " 0803 "through an USB connectors. This makes it really a trifle to buy an external " 0804 "SATA drive and hook it up to your machine. 4000 GB drives will hit the " 0805 "market in 2020. These are terrific compact storage containers for backup " 0806 "swapping: keep one drive at home and one somewhere else." 0807 msgstr "" 0808 0809 #: ../../asset_management/data_protection.rst:251 0810 msgid "Backup and Recover" 0811 msgstr "" 0812 0813 #: ../../asset_management/data_protection.rst:253 0814 msgid "" 0815 "A 4 TB HDD is not very expensive today. Do not blame anybody else for data " 0816 "loss. 6% of all PCs will suffer an episode of data loss in any given year. " 0817 "Backup your data often according to a plan, and back it up and test the " 0818 "backup before you do anything dramatic like re-installing your OS, changing " 0819 "disks, resizing partitions and so on." 0820 msgstr "" 0821 0822 #: ../../asset_management/data_protection.rst:256 0823 msgid "Disaster Prevention" 0824 msgstr "Prevención de desastres" 0825 0826 #: ../../asset_management/data_protection.rst:258 0827 msgid "" 0828 "Say, you religiously do your backups every day on a external SATA drive. " 0829 "Then comes the day where lightning strikes. Happy you if the external drive " 0830 "was not connected at that moment." 0831 msgstr "" 0832 0833 #: ../../asset_management/data_protection.rst:260 0834 msgid "" 0835 "Disasters strike locally and destroy a lot. Forget about airplane crashes: " 0836 "fire, water, electricity, kids and theft are dangerous enough to our data. " 0837 "They usually cover a whole room or house." 0838 msgstr "" 0839 0840 #: ../../asset_management/data_protection.rst:262 0841 msgid "" 0842 "Therefore disaster control means de-localized storage. Move your backups " 0843 "upstairs, next house, to your bureau (and vise versa), whatever." 0844 msgstr "" 0845 0846 #: ../../asset_management/data_protection.rst:264 0847 msgid "" 0848 "There is another good aspect to the physical separation: as said above, " 0849 "panic is often the cause of destroying data, even the backup data. Having a " 0850 "backup not at hand right away may safe your ass one day." 0851 msgstr "" 0852 0853 #: ../../asset_management/data_protection.rst:267 0854 msgid "Backup Technicalities" 0855 msgstr "" 0856 0857 #: ../../asset_management/data_protection.rst:269 0858 msgid "" 0859 "**Full Backup**: A complete backup of all the files being backed up. It is a " 0860 "snapshot without history, it represents a full copy at one point in time." 0861 msgstr "" 0862 0863 #: ../../asset_management/data_protection.rst:271 0864 msgid "" 0865 "**Differential Backup**: A backup of only the files that have changed since " 0866 "the last full backup. Constitutes a full snapshot of two points in time: the " 0867 "full backup and the last differential one." 0868 msgstr "" 0869 0870 #: ../../asset_management/data_protection.rst:273 0871 msgid "" 0872 "**Incremental Backup**: A backup of only the files that have changed since " 0873 "last whatever backup. Constitutes multiple snapshots. You can recreate the " 0874 "original state at any point in time such a backup was made. This comes " 0875 "closest to a versioning system except that it is only sampled and not " 0876 "continuous." 0877 msgstr "" 0878 0879 #: ../../asset_management/data_protection.rst:276 0880 msgid "Backup The Data" 0881 msgstr "" 0882 0883 #: ../../asset_management/data_protection.rst:278 0884 msgid "The Best practice at all is to backup the data:" 0885 msgstr "" 0886 "La mejor práctica de todas es hacer una copia de seguridad de los datos:" 0887 0888 #: ../../asset_management/data_protection.rst:280 0889 msgid "Do a **full backup** in a external storage device." 0890 msgstr "" 0891 "Haga una **copia de seguridad completa** en un dispositivo de almacenamiento " 0892 "externo." 0893 0894 #: ../../asset_management/data_protection.rst:282 0895 msgid "Verify its **data integrity** and put it away (disaster control)." 0896 msgstr "" 0897 "Verifique la **integridad de los datos** copiados y póngalos en un lugar " 0898 "distante (control de desastres)." 0899 0900 #: ../../asset_management/data_protection.rst:284 0901 msgid "Have another storage device for **frequent backups**." 0902 msgstr "" 0903 "Disponga de otro dispositivo de almacenamiento para **copias de seguridad " 0904 "frecuentes**." 0905 0906 #: ../../asset_management/data_protection.rst:286 0907 msgid "" 0908 "**Swap the devices** every other month after having verified data integrity." 0909 msgstr "" 0910 "**Intercambie los dispositivos** cada mes tras verificar la integridad de " 0911 "los datos que contienen." 0912 0913 #: ../../asset_management/data_protection.rst:289 0914 msgid "A Useful Tool to Backups" 0915 msgstr "Una herramienta útil para copias de seguridad" 0916 0917 #: ../../asset_management/data_protection.rst:291 0918 msgid "" 0919 "Linux `rsync <https://en.wikipedia.org/wiki/Rsync>`_ is a wonderful little " 0920 "utility that's amazingly easy to set up on your machines. Rather than have a " 0921 "scripted FTP session, or some other form of file transfer script - rsync " 0922 "copies only the differences of files that have actually changed, compressed " 0923 "and through ssh if you want to for security. That's a mouthful." 0924 msgstr "" 0925 0926 #: ../../asset_management/data_protection.rst:293 0927 msgid "A reasonable backup approach for images could be this one:" 0928 msgstr "" 0929 "Una aproximación razonable para hacer copias de seguridad de sus imágenes " 0930 "podría ser la siguiente:" 0931 0932 #: ../../asset_management/data_protection.rst:295 0933 msgid "" 0934 "Backup important images right away (after dumping them to a computer) to " 0935 "optical media." 0936 msgstr "" 0937 "Haga copia de seguridad de la imágenes importantes inmediatamente (tras " 0938 "volcarlas a su equipo) en un medio óptico." 0939 0940 #: ../../asset_management/data_protection.rst:297 0941 msgid "Do daily incremental backup of the work space." 0942 msgstr "" 0943 "Haga cada día una copia de seguridad incremental de su espacio de trabajo." 0944 0945 #: ../../asset_management/data_protection.rst:299 0946 msgid "" 0947 "Do a weekly differential backup and delete integral backups of week-2 (two " 0948 "weeks ago)." 0949 msgstr "" 0950 "Haga cada semana una copia de seguridad diferencial y borre las copias de " 0951 "seguridad integrales de la semana 2 (de hace dos semanas)." 0952 0953 #: ../../asset_management/data_protection.rst:301 0954 msgid "Do a monthly differential backup and delete backup of month-2." 0955 msgstr "" 0956 "Haga cada mes una copia de seguridad diferencial y borre la copia de " 0957 "seguridad del mes 2." 0958 0959 #: ../../asset_management/data_protection.rst:303 0960 msgid "" 0961 "If not physically separated already, separate it now (swapping-in another " 0962 "backup drive)." 0963 msgstr "" 0964 "Si no están ya separadas físicamente, sepárelas ahora (usando otra unidad de " 0965 "copia de seguridad)." 0966 0967 #: ../../asset_management/data_protection.rst:305 0968 msgid "" 0969 "This protocol tries to leave you enough time to spot losses and to recover " 0970 "fully at the same time keeping the backup volume at <130% of the working " 0971 "space. You end up with a daily version of the last 7-14 days, a weekly " 0972 "snapshot for at least one month, and a snapshot of every month. Any more " 0973 "thinning should be done by hand after a full verification. Preserve your " 0974 "images through the changes of technology and owners" 0975 msgstr "" 0976 0977 #: ../../asset_management/data_protection.rst:308 0978 msgid "" 0979 "In order for your valuable images to **survive the next 40 years** or so " 0980 "(because that's about the time that you will become really interested to " 0981 "revisit those nice old photographs of you as a child, adolescent etc.) there " 0982 "are two strategies to be observed:" 0983 msgstr "" 0984 0985 #: ../../asset_management/data_protection.rst:310 0986 msgid "" 0987 "**Keep up with technology**, don't lag behind more than a couple of years." 0988 msgstr "" 0989 0990 #: ../../asset_management/data_protection.rst:312 0991 msgid "Save your photos in an open, **non-proprietary standard**." 0992 msgstr "Guarde sus fotos en un estándar abierto y **no propietario**." 0993 0994 #: ../../asset_management/data_protection.rst:315 0995 msgid "Keep Up With Technology" 0996 msgstr "Manténgase al día con la tecnología" 0997 0998 #: ../../asset_management/data_protection.rst:317 0999 msgid "" 1000 "As the future is unforeseeable by nature, everything said today is to be " 1001 "taken with caution, and to be reviewed as we advance. Unfortunately there is " 1002 "no shortcut possible to some basic vigilance. Every 5-8 years at least one " 1003 "should ask oneself the question of backwards compatibility of current " 1004 "systems. The less variants we used in the past the less questions are to be " 1005 "answered in the future." 1006 msgstr "" 1007 1008 #: ../../asset_management/data_protection.rst:319 1009 msgid "" 1010 "Of course every time you change your computer system (machine, operating " 1011 "system, applications, DRM) you have to ask yourself the same questions. " 1012 "Today, if you want to switch to Windows, you have to ask yourself three " 1013 "times if you still can import your pictures, and, more important so, if you " 1014 "are ever able to move them onto some other system or machine. Chances are " 1015 "good that you cannot. We see many people struggling around us, because " 1016 "Windows enforces a strict DRM regime. How can you proof to Windows that you " 1017 "are actually the owner of your pictures copyright?" 1018 msgstr "" 1019 1020 #: ../../asset_management/data_protection.rst:321 1021 msgid "" 1022 "Basically the questions should be answered along the line explained in this " 1023 "document: use and change to open standards supported by a manifold of " 1024 "applications." 1025 msgstr "" 1026 1027 #: ../../asset_management/data_protection.rst:323 1028 msgid "" 1029 "Virtualization becomes available now for everybody. So if you have an old " 1030 "system that is important for reading your images, keep it, install it as a " 1031 "virtual machine for later." 1032 msgstr "" 1033 1034 #: ../../asset_management/data_protection.rst:325 1035 msgid "" 1036 "Otherwise the advice is quite simple: every time you change your computer " 1037 "architecture, your storage and backup technology, your file format, check it " 1038 "out, go through your library and convert to a newer standard if necessary. " 1039 "And keep to open standards." 1040 msgstr "" 1041 1042 #: ../../asset_management/data_protection.rst:328 1043 msgid "Scalability" 1044 msgstr "Escalabilidad" 1045 1046 #: ../../asset_management/data_protection.rst:330 1047 msgid "" 1048 "Scalability is the tech-geek expression of the (easy) capability of a system " 1049 "to be resized, which always means up-sized." 1050 msgstr "" 1051 1052 #: ../../asset_management/data_protection.rst:332 1053 msgid "" 1054 "Lets assume you planned for scalability and dedicated the container you want " 1055 "to increase to a separate disk or partition. On Linux system you then can " 1056 "copy and resize the container to the new disk." 1057 msgstr "" 1058 1059 #: ../../asset_management/data_protection.rst:337 1060 msgid "Use Open File Formats" 1061 msgstr "Use formatos de archivos abiertos" 1062 1063 #: ../../asset_management/data_protection.rst:339 1064 msgid "" 1065 "The short history of the digital era in the past 20 years has proven over " 1066 "and over again that proprietary formats are not the way to go when you want " 1067 "your data to be intelligible 10 years into the future. Microsoft is " 1068 "certainly the well known culprit of that sort because of its domineering " 1069 "market share. But other companies are actually (if inadvertently) worse " 1070 "since they may not stay long enough in the market at all or have a small " 1071 "user/contributor base only. In the case of Microsoft one has at least the " 1072 "advantage of many people sharing the same problems. Finding a solution has " 1073 "therefore much more success. Still, in some cases Microsoft is using Open " 1074 "Source documentation to understand their own systems, so badly maintained " 1075 "have been their own documentation. Usually with any given MSoffice suite one " 1076 "cannot properly read a document created with the same application two major " 1077 "versions earlier." 1078 msgstr "" 1079 1080 #: ../../asset_management/data_protection.rst:341 1081 msgid "" 1082 "Image formats have had a longer live time than office documents and are a " 1083 "bit less affected by obsolescence." 1084 msgstr "" 1085 1086 #: ../../asset_management/data_protection.rst:343 1087 msgid "" 1088 "Open Source standards have the huge advantage of having an open " 1089 "specification. Even if one day in the future there'll be no software to read " 1090 "it anymore, one can recreate such software, a task becoming simpler every " 1091 "year." 1092 msgstr "" 1093 1094 #: ../../asset_management/data_protection.rst:349 1095 msgid "digiKam Image Editor Default Save Settings For Common Image Formats" 1096 msgstr "" 1097 1098 #: ../../asset_management/data_protection.rst:351 1099 msgid "" 1100 "**JPEG** has been around for a while now, and whilst it's a lossy format " 1101 "losing a bit every time you make a modification and save it, it is " 1102 "ubiquitous, supports JFIF, Exif, IPTC and XMP metadata, has good compression " 1103 "ratios and can be read by all imaging software. Because of its metadata " 1104 "limitation, lossy nature, absence of transparency and 8 bit color channel " 1105 "depth, we do not recommend it. JPEG2000 is better, can be employed lossless, " 1106 "but lacks in user base." 1107 msgstr "" 1108 1109 #: ../../asset_management/data_protection.rst:353 1110 msgid "" 1111 "**GIF** is a proprietary. patented format and slowly disappearing from the " 1112 "market. Don't use it." 1113 msgstr "" 1114 1115 #: ../../asset_management/data_protection.rst:355 1116 msgid "" 1117 "**PNG** has been invented as a Open Source standard to replace GIF, but it " 1118 "does much more. It is lossless, supports XMP, Exif and IPTC metadata, 16 bit " 1119 "color encoding and full transparency. PNG can store gamma and chromaticity " 1120 "data for improved color matching on heterogeneous platforms. Its drawback " 1121 "are a relatively big footprints (but smaller than TIFF) and slow " 1122 "compression. We recommend it." 1123 msgstr "" 1124 1125 #: ../../asset_management/data_protection.rst:357 1126 msgid "" 1127 "**TIFF** has been widely accepted as an image format. TIFF can exist in " 1128 "uncompressed form or in a container using a lossless compression algorithm " 1129 "(Deflate). It maintains high image quality but at the expense of much larger " 1130 "file sizes. Some cameras let you save your images in this format. The " 1131 "problem is that the format has been altered by so many people that there are " 1132 "now 50 or more flavors and not all are recognizable by all applications." 1133 msgstr "" 1134 1135 #: ../../asset_management/data_protection.rst:359 1136 msgid "" 1137 "**PGF** for Progressive Graphics File is another not so known but open file " 1138 "image format. Wavelet-based, it allows lossless and lossy data compression. " 1139 "PGF compares well with **JPEG 2000** but it was developed for speed " 1140 "(compression/decompression) rather than to be the best at compression ratio. " 1141 "At the same file size a PGF file looks significantly better than a JPEG one, " 1142 "while remaining very good at progressive display too. PGF format is used " 1143 "internally in digiKam to store compressed thumbnails in the database. For " 1144 "more information about the PGF format see the `libPGF homepage <https://" 1145 "libpgf.org/>`_" 1146 msgstr "" 1147 1148 #: ../../asset_management/data_protection.rst:365 1149 msgid "digiKam Image Editor Raw Import Tool" 1150 msgstr "Herramienta de importación RAW del editor de imágenes digiKam" 1151 1152 #: ../../asset_management/data_protection.rst:367 1153 msgid "" 1154 "**RAW** format. Some, typically more expensive, cameras support RAW format " 1155 "shooting. The RAW format is not really an image standard at all, it is a " 1156 "container format which is different for every brand and camera model. RAW " 1157 "format images contain minimally processed data from the image sensor of a " 1158 "digital camera or image scanner. Raw image files are sometimes called " 1159 "digital negatives, as they fulfill the same role as film negatives in " 1160 "traditional chemical photography: that is, the negative is not directly " 1161 "usable as an image, but has all of the information needed to create an " 1162 "image. Storing photographs in a camera's RAW format provides for higher " 1163 "dynamic range and allows you to alter settings, such as white balance, after " 1164 "the photograph has been taken. Most professional photographers use RAW " 1165 "format, because it offers them maximum flexibility. The downside is that RAW " 1166 "image files can be very large indeed." 1167 msgstr "" 1168 1169 #: ../../asset_management/data_protection.rst:369 1170 msgid "" 1171 "We recommend clearly to **abstain from archiving in RAW format** (as opposed " 1172 "to shooting in RAW format, which we recommend). It has all bad ingredients: " 1173 "many varieties and proprietary nature. It is clear that in a few years time " 1174 "you cannot use your old RAW files anymore. We have already seen people " 1175 "changing camera, losing their color profiles and having great difficulty to " 1176 "treat their old RAW files correctly. Better change to DNG format." 1177 msgstr "" 1178 1179 #: ../../asset_management/data_protection.rst:371 1180 msgid "" 1181 "**DNG** or Digital Negative file format is a royalty free and open RAW image " 1182 "format designed by Adobe Systems. DNG was a response to demand for a " 1183 "unifying camera raw file format. It is based on the TIFF/EP format, and " 1184 "mandates use of metadata. A handful of camera manufacturers have adopted DNG " 1185 "already, let's hope that the main contenders Canon and Nikon will use it one " 1186 "day. `Apple ProRAW <https://support.apple.com/en-us/HT211965>`_ format " 1187 "available since the iPhone 12 Pro Max is based on DNG." 1188 msgstr "" 1189 1190 #: ../../asset_management/data_protection.rst:377 1191 msgid "" 1192 "digiKam Provide a Tool to Convert in Batch RAW to DNG in :ref:`Batch Queue " 1193 "Manager <dng_converter>`" 1194 msgstr "" 1195 1196 #: ../../asset_management/data_protection.rst:379 1197 msgid "" 1198 "We strongly recommend converting RAW files to DNG for archiving. Despite the " 1199 "fact that DNG was created by Adobe, it is an open standard and widely " 1200 "embraced by the Open Source community (which is usually a good indicator of " 1201 "perennial properties). Some manufacturers have already adopted DNG as RAW " 1202 "format. And last not least, Adobe is the most important source of graphical " 1203 "software today, and they of course support their own invention. It is an " 1204 "ideal archival format, the raw sensor data will be preserved as such in TIFF " 1205 "format inside DNG, so that the risk associated with proprietary RAW formats " 1206 "is alleviated. All of this makes migration to another operating system a no-" 1207 "brainer." 1208 msgstr "" 1209 1210 #: ../../asset_management/data_protection.rst:385 1211 msgid "" 1212 "digiKam Provide Tools to Convert RAW to DNG during :ref:`Download from " 1213 "Camera <camera_dngconvert>`" 1214 msgstr "" 1215 1216 #: ../../asset_management/data_protection.rst:387 1217 msgid "" 1218 "**XML** for Extensible Mark-up Language or **RDF** for Resource Description " 1219 "Framework. XML is like HTML, but where HTML is mostly concerned with the " 1220 "presentation of data, XML is concerned with the *representation* of data. On " 1221 "top of that, XML is non-proprietary, operating-system-independent, fairly " 1222 "simple to interpret, text-based and cheap. RDF is the WC3's solution to " 1223 "integrate a variety of different applications such as library catalogs, " 1224 "world-wide directories, news feeds, software, as well as collections of " 1225 "music, images, and events using XML as an interchange syntax. Together the " 1226 "specifications provide a method that uses a lightweight ontology based on " 1227 "the Dublin Core which also supports the \"Semantic Web\" (easy exchange of " 1228 "knowledge on the Web)." 1229 msgstr "" 1230 1231 #: ../../asset_management/data_protection.rst:390 1232 msgid "IPTC Goes XMP" 1233 msgstr "IPTC se convierte en XMP" 1234 1235 #: ../../asset_management/data_protection.rst:392 1236 msgid "" 1237 "That's probably one of the reasons why, around 2001, that Adobe introduced " 1238 "its XML based XMP technology to replace the *Image Resource Block* " 1239 "technology of the nineties. XMP stands for **Extensible Metadata Platform**, " 1240 "a mixture of XML and RDF. It is a labeling technology that lets users embed " 1241 "data about a file in the file itself, the file info is saved using the " 1242 "extension :file:`*.xmp*` (signifying the use of XML/RDF)." 1243 msgstr "" 1244 1245 #: ../../asset_management/data_protection.rst:394 1246 msgid "" 1247 "`XMP <https://en.wikipedia.org/wiki/Extensible_Metadata_Platform>`_: As much " 1248 "as ODF will be readable forever (since its containing text is written in " 1249 "clear text), XMP will preserve your metadata in a clearly understandable " 1250 "format XML. No danger here of not being able to read it later. It can be " 1251 "embedded into the image files or as a separate accompanying file " 1252 "(**Sidecar** concept). XMP can be used in PDF, JPEG, JPEG2000, GIF, PNG, " 1253 "HTML, TIFF, Adobe Illustrator, PSD, Postscript, Encapsulated Postscript, and " 1254 "video files. In a typical edited JPEG file, XMP information is typically " 1255 "included alongside Exif and IPTC data." 1256 msgstr "" 1257 1258 #: ../../asset_management/data_protection.rst:400 1259 msgid "digiKam can display XMP Contents from Image and Video" 1260 msgstr "" 1261 1262 #: ../../asset_management/data_protection.rst:402 1263 msgid "" 1264 "Embedding metadata in files allows easy sharing and transfer of files across " 1265 "products, vendors, platforms, customers, without metadata getting lost. The " 1266 "most common metadata tags recorded in XMP data are those from the Dublin " 1267 "Core Metadata Initiative, which include things like title, description, " 1268 "creator, and so on. The standard is designed to be extensible, allowing " 1269 "users to add their own custom types of metadata into the XMP data. XMP " 1270 "generally does not allow binary data types to be embedded. This means that " 1271 "any binary data one wants to carry in XMP, such as thumbnail images, must be " 1272 "encoded in some XML-friendly format, such as Base-64." 1273 msgstr "" 1274 1275 #: ../../asset_management/data_protection.rst:404 1276 msgid "" 1277 "Many photographers prefer keeping an original of their shots (mostly RAW) " 1278 "for the archive. XMP suits that approach as it keeps metadata separate from " 1279 "the image file. We do not share this point of view. There could be problems " 1280 "linking metadata file and image file, and as said above, RAW formats will " 1281 "become obsolete. We recommend using DNG as a container and putting " 1282 "everything inside." 1283 msgstr "" 1284 1285 #: ../../asset_management/data_protection.rst:406 1286 msgid "" 1287 "The `Dublin Core Metadata Initiative <https://www.dublincore.org/>`_ is an " 1288 "open organization engaged in the development of interoperable online " 1289 "metadata standards that support a broad range of purposes and business " 1290 "models. DCMI's activities include work on architecture and modeling, " 1291 "discussions and collaborative work in DCMI Communities and DCMI Task Groups, " 1292 "annual conferences and workshops, standards liaison, and educational efforts " 1293 "to promote widespread acceptance of metadata standards and practices." 1294 msgstr "" 1295 1296 #: ../../asset_management/data_protection.rst:412 1297 msgid "digiKam Support Sidecar Files With many Options From Settings Panel" 1298 msgstr "" 1299 1300 #: ../../asset_management/data_protection.rst:415 1301 msgid "Protect Your Data" 1302 msgstr "Proteja sus datos" 1303 1304 #: ../../asset_management/data_protection.rst:417 1305 msgid "Use surge protectors (UL 1449 standard), possibly combined with a UPS." 1306 msgstr "" 1307 "Use protectores de sobretensiones (compatibles con el estándar UL 1449), " 1308 "posiblemente combinados con un SAI." 1309 1310 #: ../../asset_management/data_protection.rst:419 1311 msgid "" 1312 "Use ECC memory to verify correct data transmission (even just saving files)." 1313 msgstr "" 1314 "Use memoria ECC para verificar la correcta transmisión de datos (incluso al " 1315 "guardar archivos)." 1316 1317 #: ../../asset_management/data_protection.rst:421 1318 msgid "Watch your hard drives (temperature, noise...), make backups." 1319 msgstr "" 1320 "Vigile sus discos duros (temperatura, ruidos...), haga copias de seguridad." 1321 1322 #: ../../asset_management/data_protection.rst:423 1323 msgid "Keep backups at another location, locked up, use web storage space." 1324 msgstr "" 1325 "Guarde las copias de seguridad en otra ubicación, bajo llave, use espacio de " 1326 "almacenamiento web." 1327 1328 #: ../../asset_management/data_protection.rst:425 1329 msgid "Use archival media and burners." 1330 msgstr "" 1331 1332 #: ../../asset_management/data_protection.rst:427 1333 msgid "" 1334 "Don't panic in case of data loss, explain your recovery plan to a layperson." 1335 msgstr "" 1336 1337 #: ../../asset_management/data_protection.rst:429 1338 msgid "" 1339 "Choose you file system, partitions, folders to cater for easy scalability." 1340 msgstr "" 1341 "Elija su sistema de archivos, particiones y carpetas para facilitar la " 1342 "escalabilidad." 1343 1344 #: ../../asset_management/data_protection.rst:431 1345 msgid "Use open, non-proprietary standards to manage and save photographs." 1346 msgstr "" 1347 "Use estándares abiertos y no propietarios para guardar y gestionar " 1348 "fotografías." 1349 1350 #: ../../asset_management/data_protection.rst:433 1351 msgid "Do a technology/migration review at least every 5 years." 1352 msgstr "Realice una revisión de tecnología/migración al menos cada 5 años." 1353 1354 #~ msgid "CD, DVD, Blue Ray, Optical Drives" 1355 #~ msgstr "CD, DVD, Blue Ray, unidades ópticas"