Re: [darktable-dev] darktable 3.6 released
thank you for this fantastic work peter switzerland > Am 03.07.2021 um 10:14 schrieb Pascal Obry : > > We're proud to announce the new feature release of darktable, 3.6.0! > > The github release is here: > [https://github.com/darktable-org/darktable/releases/tag/release-3.6.0](https://github.com/darktable-org/darktable/releases/tag/release-3.6.0) > . > > As always, please don't use the autogenerated tarball provided by > github, but only our tar.xz file. the checksums are: > > ``` > $ sha256sum darktable-3.6.0.tar.xz > 86bcd0184af38b93c3688dffd3d5c19cc65f268ecf9358d649fa11fe26c70a39 > darktable-3.6.0.tar.xz > $ sha256sum darktable-3.6.0.3.dmg > 12c9319d68dac5b1b5602bf470254467b90f5c5b9d2e93ea081d42884cfd4f80 > darktable-3.6.0.3.dmg > $ sha256sum darktable-3.6.0-win64.exe > aad925988545ff3c50f54243520e8481c695b38b209daa808a490113f6400374 > darktable-3.6.0-win64.exe > ``` > > When updating from the currently stable 3.4.x series, please bear in > mind that your edits will be preserved during this process, but the new > library and configuration will not be usable with 3.4.x any more. > > You are strongly advised to take a backup first. > > Important note: to make sure that darktable can keep on supporting > the raw file format for your camera, *please* read [this > post](https://discuss.pixls.us/t/raw-samples-wanted/5420?u=lebedevri) > on how/what raw samples you can contribute to ensure that we have the > *full* raw sample set for your camera under CC0 license! > > - Almost 2680 commits to darktable+rawspeed since 3.4 > - 954 pull requests handled > - 290 issues closed > > ## The Big Ones > > - Full rework of the import module. The new module allows you to see > thumbnails of your images before import and makes it easier to handle > multiple import tasks. The same dialog is now used for importing > from disk, card or camera. > > When importing "in-place", images that are already present in > darktable > are flagged and can be automatically excluded from the import. > > Importing from a local drive won't use gphoto and so should work more > reliably on Windows. > > - A vector-scope is added to complement the current histogram, > waveform and parade views. > > - A new default demosaic algorithm (RCD) has been introduced, which > should provide > better quality than the current default (PPG) without the long run- > times > of AMaZE. the order of the demosaic algorithms has also been adjusted > for clarity. > > - Support for "dual demosaic" has also been added, allowing you to > combine > "RCD + VNG4" and "AMaZE + VNG4" for bayer sensors, for xtrans sensors > there is > "Markesteijn 3-pass + VNG". This allows you to use an algorithm > better resolving > fine detail and another one delivering smoother output depending on > local image content. > > - You can now create an opacity mask based on the sharpness of the > image. This uses > a similar algorithm to that used in dual demosaic. > > - Drawn shapes are drawn on the original RAW image and then distorted > through > the pixelpipe. This previously led to, for example, circles becoming > ellipses > (due to lens distortion) after being placed on the image. All drawn > shapes can > now be pre-visualized and moved prior to placement, with full > deformation > applied. This makes the editing of masks easier fully WYSIWYG. > > - A new Color Balance RGB module has been added. This can be used as a > one stop module > for all color grading work. > > - A new censorize module has been added. This allows you to hide parts > of the image by adding > a blur/pixelization. > > - A new crop module has been added. This new module has been added late > in the > pixelpipe and makes it possible to use cropped parts of the image for > source spots > in the retouch module, for example. > > - A new section has been added to the color calibration module to allow > you to calibrate > colors using a color checker chart. > > - The map module has been enhanced in a number of ways: > - When importing a GPX the trace can be displayed. > - Location can be set using polygons and directly created from > information >reported by Open Street Map. As a reminder, all locations >create tags automatically for images placed into the area. > > - The basic adjustments module has been replaced with the quick access > panel, which > can be used to group controls from multiple different modules in one > place. Currently, > only non-graphical controls (sliders, comboboxes etc.) can be used. > > ## Other New Features And Changes > > - The various lighttable modes can now be accessed via clear and > descriptive icons > at the bottom of the screen. These should be easier to use than the > existing drop-down > selection. > > - The export module is now also accessible on the left-hand panel of > the > darkroom view. > > - The mix control in the contrast equalizer module is now retained as > module parameter. This means that no data is lost
Re: [darktable-dev] Manual translation workflow, new contributors
Hi to All, especially German-Speakers I am doing the translation of the manual into since something like 10 weeks and I would highly appreciate some help. If anyone needs advice, I am looking forward to help or do some coordination. Mit freundlichem Gruss Peter Schlaufer Landenbergstrasse 19 CH-6005 Luzern pe...@schlaufer.ch <mailto:pe...@schlaufer.ch> > Am 01.06.2021 um 23:55 schrieb Jeronimo Pellegrini : > > Hi Mica! > Thanks a lot -- but I didn't see pt_BR in the language list (actually, > not even pt from Portugal). The list there is: > > English > Esperando > French > Galician > German > Italian > Polish > Spanish > Ukranian > > I believe I am not able to include another language there myself... > > J. > > Mica Semrick writes: > >> Hi J, >> >> Not sure which version of the docs you're reading, but >> https://darktable-org.github.io/dtdocs/special-topics/translating/ does >> mention it. >> >> If all one wants to do is translate, then go to our weblate instance, create >> an account or login, select a language (pt_BR is already there) and start >> translating. >> >> -m >> >> On June 1, 2021 11:56:23 AM PDT, Jeronimo Pellegrini >> wrote: >>> Mica Semrick writes: >>>> Hi J, >>> >>> Hi! >>> >>>> The instructions on the dtdocs are still valid. >>> >>> Ok! >>> >>>> Weblate is the only option and will allow multiple contributors to >>>> work at the same time, so if everyone is using weblate, there doesn't >>>> not need to be any coordination, as weblate takes care of it. >>> >>> But the instructions on the README at >>> https://github.com/darktable-org/dtdocs >>> don't mention weblate -- I'm not sure I understood the workflow then. >>> >>>> For the schedule, we will release the docs on the day of the >>>> release. Because the docs are decoupled from the code now, we don't >>>> need to work with the code freeze dates, and instead we can keep >>>> working until the time of the release. >>> >>> Okay, understood! >>> >>> Thank you! >>> J. >>> ___ >>> darktable developer mailing list >>> to unsubscribe send a mail to >>> darktable-dev+unsubscr...@lists.darktable.org >> >> ___ >> darktable developer mailing list >> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org > ___ > darktable developer mailing list > to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org > ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
Re: [darktable-dev] Translation tips
Hello After having translated 30% of the dtdocs into german I am now a bit confused, because I started the translation-work in Weblate, as per the Mail from Mica Semrick: The new documentation written in markdown is ready to be translated. We're using Weblate to manage the translation. You can find the dtdocs project here: https://weblate.pixls.us/projects/darktable/dtdocs/ <https://weblate.pixls.us/projects/darktable/dtdocs/> Please let me know if you have any questions. -m I am not sure, what these mails are about on Poedit and Flatpak. As mentioned above I have translated +/- 30%. My setup for translation is normally: Tab1 WeblateTab 2 the user manual 3.4 Tab 3 a technical dictonary Tab 4 https://darktable.gitlab.io/doc/de/ plus of course darktable in the background Meanwhile I have happily terminated the translation of the module "color calibration“ to which I would like to raise some questions: Some positions of the Weblate text of this module I was not able to find in the program, especially all the stuff on making ones own generic Color Profiles using color-checkers.(Positions in Weblate around 950 to 1030) Furthermore I think, that this passages are so very technical, that even I as a trained engineer and in photography for more than 50 years could not follow the entire context, especially not the passages, which I was not able to find and verfify in the program. As mentioned I terminated that part and I go on with other modules. I have to say that I am doing my work on MacOs Thank you Peter Schlaufer Switzerland > Am 21.04.2021 um 17:39 schrieb Mica Semrick : > > You can do this easily with flatpak, you just need to name the manifest > differently. > > -m > > On April 21, 2021 8:26:07 AM PDT, i...@kevinvermassen.be wrote: > Hi > > I'm looking for some translation tips. Until now, I just used Poedit to > translate one line at a time. But I find it more clear to have darktable > opened to see which string in English translate to which string in Dutch (I'm > new to translating darktable) because I think there are some inconsistencies > int the translation and I want to improve the quality a bit. > > But it is rather annoying to open darktable in English, change it to Dutch, > restart darktable, read the Dutch translation, go back to the English > translation, reboot, ... > > Is there a way to have the snapshot of the master branch installed twice, so > I can have one instance in Dutch and another in English and I can just use > ALT+TAB? How are other translators doing this? Do you have any other tips? > > Thanks! > > Kevin > > ___ > darktable developer mailing list to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > > ___ > darktable developer mailing list to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org ___ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
