[darktable-dev] Translators: what tools are you using to translate?

[Mica Semrick]

Hi translators,

I've been working towards migrating the user guide into a more friendly format 
than docbook. I've come to the point where I need to define a translation 
workflow and was wondering what tooling everyone is using, so I can take that 
into account.

From my understanding, I'll need to generate a translation memory from the 
current user manual PO files, as the segments may change slight in the new XML 
format.

Thanks, 
Mica
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Reporting two Bugs - that may be related

[Mica Semrick]

Have you checked against the latest release version 3.0.2? 

2.4.x is really old.

On July 13, 2020 10:56:40 AM PDT, "Ramnarayan.K"  wrote:
>Hi
>
>I am using darktable 2.4.2 on Linux Mint 19 Tara \n \l
>
>Have been using this for some years.
>
>However earlier because I was not exporting images for use on a site
>that
>uses exif data to organize the pictures the "bugs" did not bother me -
>now
>they do
>
>*First Bug - Random change in exif date*
>Specifically the bug seems to be that Darktable randomly changes the
>exif
>date (and time) of when the picture was taken.
>
>I shoot in Nikon raw format (.nef) and have usually been exporting
>images
>to jpeg using the naming format as below
>$(EXIF_YEAR)$(EXIF_MONTH)$(EXIF_DAY)_foo_name_$(FILE_NAME)
>
>This is when I started realizing that Darktable was messing up the
>dates.
>Two files taken in a sequence are set many months apart with the wrong
>date
>set randomly to some period earlier.
>
>I normally work directly on the SD Card for immediate processing and
>later
>work of my external Hard Drive for more careful processing and
>organizing .
>
>Googling, for this error, does not throw up any results - but maybe I
>did
>not google the correct terms.
>
>*Second Bug - Darktable keeps showing old deleted files in the
>darktable
>browser.*
>The reference environment is the same. However while working from / on
>the
>sd card darktable seems to pick up long deleted files - and shows many
>of
>them some from more than a year ago.
>
>I have formatted the SD cards multiple times - I have deleted the
>thumbnails and darktable caches from the Linux system - but these ghost
>files keep appearing - they appear as blanks on the lighttable - but
>there
>are 100's and to get to the actual files with content I have to scroll
>quite far down.
>
>***
>Last
>*I really like Darktable *- it is my favorite go to software and has
>made
>life very easy for post processing and exporting to easily
>distributable
>formats.
>
>So thank you very much
>
>kind regards
>ram
>
>___
>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] First darktable 3.2 article ready in english

[Mica Semrick]

Would you prefer a proof read as a PR on top of your PR, or as a series of 
review comments on the PR?

On July 19, 2020 6:05:29 AM PDT, Nicolas Auffray  
wrote:
>Hi,
>
>I'm please to inform you that I just finish the english version that 
>present the future 3.2. Be careful: it's just a first version, I don't 
>read it again by now and will do that ASAP, so you will certainly see 
>some mistakes and maybe some sentences to rewrite.
>
>You could find the article (and english screenshots) on this draft PR: 
>https://github.com/darktable-org/dtorg/pull/111
>
>Feel free to review it (and propose corrections) but please don't
>change 
>anything else that just correct my english. This english version is 
>based on a french article. So the original is that french article and i
>
>had been reviewed by some users and it's completely over and validate. 
>But also, I know that german translation, made by @bilddateien, is 
>nearly done.
>
>Maurizio, if you read that, I hope you will have time to do the italian
>
>one as always.
>
>Of course, if someone else want to translate it in another language, it
>
>will be great. Just think about inform me to the language and future 
>article link to add them on top of the article (by now, french, italian
>
>and german links are already there but of course could be updated if 
>needed).
>
>Hope to see some of your reviews on that PR.
>
>Best regards,
>
>Nicolas Auffray (Nilvus)
>
>
>___
>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] Upgrade from 3.0.2 to 3.2.1 destroys order of modules

[Mica Semrick]

Hi, 

You can still use the old, ordered processing pipeline with base curve and all 
that. You just need to select it from the modules menu.

Your workflow sounds very nonstandard though, I'd think most start with global 
adjustments and work toward local adjustments at the end of the edit.

- m

On August 12, 2020 11:15:32 AM PDT, Andreas Herold  
wrote:
>Hi,
>
>some feedback from a User who made currently the upgrade from 3.0.2 to
>3.2.1.
>
>In my workflow I’m using very often modules, which are using parametric
>masks. I’m applying moduIes with parametric masks very early in
>processing. I do this, to have stable masks, that are not depend on
>other modules. E.g. if I want to change brightness and contrast of the
>sky, I’m doing this before changing overall brightness. This way the
>mask of the sky does not depend on overall brightness.
>After upgrade from 3.0.2 to 3.2.1 I now see, that the order of modules
>has changed. For example, now the overall brightness is applied before
>the module, that was changing the sky. Since I had used a parametric
>mask, this mask became invalid. It is not the same selection I
>originally chosed. In the result, the processing is destroyed for
>hundreds of images.
>
>Best regards
>Andreas
>Herold___
>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] White-ish 1px border around selected photos in lighttable

[Mica Semrick]

Seriously, you two have to stop. It is embarrassing.

On 10/7/20 8:43 PM, Timur Irikovich Davletshin wrote:

Speak for yourself. I'm sure others can express their feelings about
such letters without your help. Gosh, man, lecturing every new person
on good manners after receiving mail attachment? Patrick, adjust your
attitude, don't act like an old fart.

On Wed, 2020-10-07 at 17:36 -0400, Patrick Shanahan wrote:


Ah, yes, doesn't exist for YOU.  Have some consideration for others
that
yourself.  I believe there is a word for that, ...



___
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] White-ish 1px border around selected photos in lighttable

[Mica Semrick]

Instead of being so smug, Timur, you could follow the one rule you 
should be following already:


1. Be an adult

I guess I need a mail rule to move your message into the trash though, 
so I can avoid having my inbox flooded by such childish nonsense.


On 10/7/20 10:59 PM, Timur Irikovich Davletshin wrote:

Mica, solution is simple:

1. Don't be embarrassed to express you ideas about people abusing their
rights of using email attachments. Discuss the issue.
2. Make it into "law" - https://www.darktable.org/ (how to get in
contact section) and probably mailing list footer.
3. Punish - strip off attachments of bigger size.
4. Forget about the issue.

On Wed, 2020-10-07 at 22:21 -0700, Mica Semrick wrote:

Seriously, you two have to stop. It is embarrassing.




___
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] Introducing dtdocs

[Mica Semrick]

On 10/16/20 2:12 PM, Moritz Moeller wrote:

THB I think Markdown is a tad limited for docs like this.


Have you had a look at the site yet?
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Introducing dtdocs

[Mica Semrick]

You have specifically pointed out where you think markdown is falling 
short in this case.


Feedback is welcome, but please try to make it actionable. We're aiming 
for improvement.


On 10/16/20 4:38 PM, Moritz Moeller wrote:

On 17.10.20 01:30, Mica Semrick wrote:

On 10/16/20 2:12 PM, Moritz Moeller wrote:

THB I think Markdown is a tad limited for docs like this.


Have you had a look at the site yet?


Yes I did.

Though I don't understand how that relates to the part of my reply you 
quoted.


.mm
___
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] Introducing dtdocs

[Mica Semrick]

Sorry, I must not have explained myself well enough. For dtdocs, we have 
pretty much chosen our tool chain, and we intentionally did not announce 
anything to avoid this type of bike shedding.


While markdown has its negatives, the positive is that if you've written 
a comment on the internet in the last several years, you've probably 
written markdown, if you know so or not.


By "actionable criticism," I meant please make sure your criticism is 
applicable and actionable on the current dtdocs project. I don't think 
we're interested in generalized markup discussion, tool chain 
discussions, or any thing else of that sort. Again, the decisions have 
been made. If you feel we've absolutely made the wrong decision with 
markdown, you're free to fork the repo, convert it to the markup flavor 
that suits you, and edit the content there.


We won't use RTD since the point is that we host the documentation 
ourselves. Hugo gives us a pretty simple and straight forward way to 
publish things, the dependencies are very minimal, and it integrates 
well into CI systems. If you feel that things are missing, please open 
an issue, but the sentiment of "eventually it'll be missing something 
because tool XYZ is better" isn't really helpful.


For context: my profession is documentation and has been for the last 12 
years. I've maintained large documentation sets in LaTeX, docbook, DITA 
XML, FrameMaker, and more. I've maintained docs using just git and I've 
maintained them using proprietary systems that cost millions of dollars. 
I've architected new documentation sets that covered hundreds of 
products and customized the publishing pipeline around them.


- mica

On 10/16/20 5:13 PM, Moritz Moeller wrote:

On 17.10.20 01:41, Mica Semrick wrote:
You have specifically pointed out where you think markdown is falling 
short in this case.


For me MD vs Sphinx is mostly about roles, extensions, citations, line 
comments, footnotes etc. that you have in Sphinx but not in MD.
MD was designed for writing texts on the Web. ReST + Sphinx was designed 
for writing documentation.


Here is a longer version of that, written by someone else:
https://eli.thegreenplace.net/2017/restructuredtext-vs-markdown-for-technical-documentation/ 



With that said: I prefer MD syntax over ReST any day as long as it 
doesn't take anything away I think is standard for good documentation.

E.g. being able to have an index auto-generated.

Sadly it does. Worst, there is no real standard in MD.
CommonMarkdown is different everywhere. Maybe a feature you grew fond of 
when using MD in Jupyter Notebooks' MD is not available on GiHub's MD etc.


 > Feedback is welcome, but please try to make it actionable. We're
 > aiming for improvement.

With the above in mind – if I were to start a documentation project now 
I'd probably use this:

https://myst-parser.readthedocs.io/en/latest/

Which is kinda ReST + MD having a baby. :)

It would mean all the work you done could be used, mostly as-is.
But you would have all the bonuses of ReST + Spinx on top that MD + 
Sphinx would not give you. Even if you switched from MD + Hugo to MD + 
Sphinx.


Oh, and use readthedocs to handle building and serving.

Because, again, that is an ecosystem build for serving documentation as 
static pages online.

Hugo is nice but it was meant to build static websites.
Which surely represent a superset, containing static online 
documentation, but broad enough that it will leave many things to be 
desired, sooner or later.


And btw: https://darktable.readthedocs.io/ is available. ;)


Beers,

.mm


P.S.: For context:
I wrote software documentation in MD several times during the last decade.
I wrote software documentation in ReST using Sphinx several time (that 
was before Sphinx added MD support).

I also have BG writing docs in LaTex from way before.

With that being said I feel entitled to be opinionated about the subject.
And mind you, I am talking about the perspective of the writer, not the 
user.

___
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] Introducing dtdocs

[Mica Semrick]

Before we open translations on weblate, I will take the current PO 
files, for both the application strings and the user guide, and make 
translation memory files out of them. I can then import them into 
weblate (PO editor also supports TMX files in recent versions), and if 
possible, translated segments from the old manual will be suggested in 
the dtdocs translation. I don't have high hopes for a lot of matches, 
since quite a bit of dtdocs has been rewritten, and translations just 
don't work like that.


The other possibility is that we use machine translation for the first 
round, then let translators edit that translation. We did machine 
translation from one of AP's French articles to English, and I was not 
impressed with the quality of the translation, but hey, we can always 
give it another shot.


On 10/17/20 3:12 PM, jys wrote:

On Sat, Oct 17, 2020, at 09:34, Pascal Obry wrote:


Probably a good move and I understand that rewording was needed but
that it is tad harsh for translators.


I may be optimistic/wrong here, but the situation for translators may not be 
quite as bad as it sounds. From the parts of the re-worked docs that I looked 
at, the emphasis has been on making the language resemble compact native 
English. Assuming that translators tend to do the same when writing their own 
native language, there may not be much need for changes overall. Translators 
would need to scan for *semantic* changes, and hopefully most of these would be 
related to updated information, which they would already need to deal with 
anyway.


That's my main concerns. Having the doc "away" from main repo will not
help. I don't know why exactly, but I've seen that on different
projects. Maybe because the doc is away it feels less part of the
project and there is less incentive to care for it?


Again, possibly optimistic, but the new setup has a distinct advantage in that text can 
now be easily edited even within the github web interface itself, reducing the need for 
contributors to maintain a local git repository just to "scratch an itch" 
regarding updates or other improvements. In a sense, some technical burden has been 
shifted to the maintainers of the repo, who will need to sift through (possibly many) 
issue reports and accept (or not) PRs, perform any needed copy editing, etc... but they 
seem willing to do this. :-)


___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Re: Introducing dtdocs

[Mica Semrick]

Hey Torsten,

Minimalism is a basic tenant of technical writing. We should strive to 
convey the "thing" in question using the fewest words and image to (1) 
reduce the maintenance overhead and (2) more words/images generally do 
not make the "thing" clearer, in fact, quite the opposite. It often 
muddies the picture.


The current documentation has a colloquial verbosity to it that (I feel) 
doesn't enhance the understanding of the reader. Similarly, there are 
images that don't enhance the readers understand either, for instance in 
the current documentation there is a image of every since module just 
ahead of the textual description of that module. In the new docs, we've 
split out module references into their own section and we assume you 
have darktable open in front of you (or you know what a module generally 
looks like) and thus we omit the image.


If there are specific instances where you think not enough is written, 
you are encouraged to open an issue.


Hope that makes sense.

-mica

On 10/18/20 7:18 PM, Torsten Bronger wrote:

Hallöchen!

A question from a prospective reader rather than author: Why do you
want to keep the number of words and images to a minimum?  FWIW, I
find both very helpful when reading about complex matters.

Regards,
Torsten.


___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Introducing dtdocs

[Mica Semrick]

Hi Jeronimo,

Thank you for your all your work; last I had looked br_PT was the most 
up-to-date.


We haven't really defined exactly what the translation workflow will 
look like, but if we get feedback from translators that they still want 
to work with PO files, I know we can certainly accommodate that.


Weblate can do nice things like use and keep a translation memory, 
leverage machine translation, and who knows what else; I haven't had 
time to fully dive into it yet. I am not aware of what emacs can do.


I think a decent portion of the manual would need to be retranslated, as 
a good chunk of it has been rewritten. As I mentioned previously, I can 
make translation memories from the current PO files and import them into 
weblate or make them available to you via some other means. Since there 
are a lot of new writings, I don't think that the old translations will 
match up very well. I'm open to exploring machine translation for a 
first pass if you'd like to do that.


I'm also open to any other suggestions you may have.

Best,
Mica


On 10/19/20 3:44 AM, Jeronimo Pellegrini wrote:

Hello,

(I sent this from an email address different from the one
  registered in the mailing list and it didn't seem to be
  sent, so I'm sendingit again from the correct email. Sorry
  for any duplicates)

I have been working on the pt_BR translation (of both darktable and
its manual).  I usually translate using po-mode in Emacs, but of
course I can adapt to some extent. :)

How much of my workflow would change? One thing that would be difficult
for me is to translate directly on a web browser. I may be
old-fashioned, but really, I never got to do any reasonable work
on web interfaces. Will it still be possible to use an editor
to do translation work?

Also - would the darktable manual translation need to be re-entered
or reworked? You mentioned that translated segments would be suggested,
so I suppose the whole document would need to be entered again in
weblate -- is this correct?

Thanks,
Jeronimo

Mica Semrick  writes:


Before we open translations on weblate, I will take the current PO
files, for both the application strings and the user guide, and make
translation memory files out of them. I can then import them into
weblate (PO editor also supports TMX files in recent versions), and if
possible, translated segments from the old manual will be suggested in
the dtdocs translation. I don't have high hopes for a lot of matches,
since quite a bit of dtdocs has been rewritten, and translations just
don't work like that.

The other possibility is that we use machine translation for the first
round, then let translators edit that translation. We did machine
translation from one of AP's French articles to English, and I was not
impressed with the quality of the translation, but hey, we can always
give it another shot.

On 10/17/20 3:12 PM, jys wrote:

On Sat, Oct 17, 2020, at 09:34, Pascal Obry wrote:


Probably a good move and I understand that rewording was needed but
that it is tad harsh for translators.


I may be optimistic/wrong here, but the situation for translators may not be 
quite as bad as it sounds. From the parts of the re-worked docs that I looked 
at, the emphasis has been on making the language resemble compact native 
English. Assuming that translators tend to do the same when writing their own 
native language, there may not be much need for changes overall. Translators 
would need to scan for *semantic* changes, and hopefully most of these would be 
related to updated information, which they would already need to deal with 
anyway.


That's my main concerns. Having the doc "away" from main repo will not
help. I don't know why exactly, but I've seen that on different
projects. Maybe because the doc is away it feels less part of the
project and there is less incentive to care for it?


Again, possibly optimistic, but the new setup has a distinct advantage in that text can 
now be easily edited even within the github web interface itself, reducing the need for 
contributors to maintain a local git repository just to "scratch an itch" 
regarding updates or other improvements. In a sense, some technical burden has been 
shifted to the maintainers of the repo, who will need to sift through (possibly many) 
issue reports and accept (or not) PRs, perform any needed copy editing, etc... but they 
seem willing to do this. :-)


___
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] Re: Introducing dtdocs

[Mica Semrick]

On 10/19/20 12:12 AM, juli...@i2pmail.org wrote:
There's a saying, "Sorry I didn't have time to write less." :)

Indeed that is true! Glad you see the need.

About the choice between Hugo or Jekyll, 


The choice is Hugo, Jekyll was not a consideration.


I realize that some may like the speed of Hugo, but Jekyll does have 
incremental builds (I read that Hugo doesn't have that). In my experience 
working on sites with thousands of pages, by using the incremental build tag 
and limiting the number of languages on my local end, I would have a site I can 
re-test in a second or two.


Jekyll needs incremental builds because ruby is slow as hell. If you 
want to take a look at some benchmarks: 
https://forestry.io/blog/hugo-vs-jekyll-benchmark/


Hugo doesn't need incremental builds, because it is fast.


Hugo is written in Go also. That might be obvious from the name, Hu"go", but it 
probably isn't to most. So I suppose those who might want to do the documentation would 
need to access whether they want to use a Go binary over Ruby.


The Go binary is way easier. You can download the binary directly from 
the hugo project, it has almost everything you need. The only other 
dependency is yarn to grab some NPM packages. I started on Jekyll, then 
moved to middleman becaue Jekyll focused too much on blogging, then 
eventually to Hugo when ruby proved to be too brittle and too much 
upkeep. You can observe a similar problem with python and the 
darktable.org website, which still uses pelican from python 2.7.


-mica



J

On 2020-10-19 02:44 UTC Mica Semrick  wrote:

Hey Torsten,

Minimalism is a basic tenant of technical writing. We should strive to
convey the "thing" in question using the fewest words and image to (1)
reduce the maintenance overhead and (2) more words/images generally do
not make the "thing" clearer, in fact, quite the opposite. It often
muddies the picture.

The current documentation has a colloquial verbosity to it that (I feel)
doesn't enhance the understanding of the reader. Similarly, there are
images that don't enhance the readers understand either, for instance in
the current documentation there is a image of every since module just
ahead of the textual description of that module. In the new docs, we've
split out module references into their own section and we assume you
have darktable open in front of you (or you know what a module generally
looks like) and thus we omit the image.

If there are specific instances where you think not enough is written,
you are encouraged to open an issue.

Hope that makes sense.


Hey Torsten,


Minimalism is a basic tenant of technical writing. We should strive to
convey the "thing" in question using the fewest words and image to (1)
reduce the maintenance overhead and (2) more words/images generally do
not make the "thing" clearer, in fact, quite the opposite. It often
muddies the picture.

The current documentation has a colloquial verbosity to it that (I feel)
doesn't enhance the understanding of the reader. Similarly, there are
images that don't enha



___
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] git master - all images are black

[Mica Semrick]

Nobody is forcing microsoft and github on anyone. You don't have to use 
it, and clearly you don't.


But it also isn't very nice to expect someone else to pick your bugs out 
of the mailing list, put them in the issues tracker, provide the extra 
information needed to reproduce the bug, follow up with developers, test 
the fix, and track all of that information, then (maybe) post a status 
update back to you on the mailing list.


As paka already said, this isn't the best way, though maybe it works 
sometimes.


-m

On 11/9/20 11:52 PM, Peter Harde wrote:

Am 09.11.20 um 11:37 schrieb juli...@i2pmail.org:
Maybe instead of saying "you should report this [at Microsoft 
Github]". Say "I've copied this to [Microsoft Github]".


... not all people will want to expose themselves to Microsoft


I completely agree.

Best regards

Peter Harde

___
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] Planning 3.4

[Mica Semrick]

Issues can be reported on github now: 
https://github.com/darktable-org/darktable/issues

On December 1, 2020 8:00:21 PM PST, Alexander Rabtchevich 
 wrote:
>Hello
>
>Couldn't submit a bug to redmine due to expired certificate and than
>502
>error, so I'm writing here.
>
>1. When importing tiff, darktable complies "history problem detected".
>Any further action with such file comes along with the same complain.
>
>2. Orientation isn't copied or applied via Ctr+C - Ctrl+V.
>
>git master, Linux Mint Mate 20 x64.
>
>With respect,
>Alexander Rabtchevich
>
>
>
>___
>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-dev] 3.4 blog post PR is now available for comment

[Mica Semrick]

The version 3.4 blog post that accompanies the upcoming release has now 
been pushed to the github PR:

https://github.com/darktable-org/dtorg/pull/116

If you have minor changes, please comment in the PR thread, but if you 
have major changes, please provide a patch, make a PR, or get in contact 
with me about submitting changes via email or IRC.


It should be reasonably safe for any translators to begin translation, 
but there will be some change before posting.


Thanks!

-m
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] different meanings of "feather" in darktable

[Mica Semrick]

"Feather size" is still awkward. It could be changed to "feathering" as well.

-m

On January 5, 2021 5:34:02 AM PST, Andrew Greig  wrote:
>Jeronimo
>
>In a mask, the feather is fall off, a weakening of the effect at the 
>edges of the mask. It disguises the fact that a mask is in use. In the 
>retouch module the feather does the same, sometimes I use a large 
>feather, and sometimes not, it depends on what I am retouching, but the
>
>effect is the same. Panel beaters and plasterers also refer to 
>tapering 
>the edge of their filling material as "feathering off" making it 
>invisisble to the eye but in their case, also to the touch.
>
>Andrew
>
>On 6/1/21 12:22 am, Jeronimo Pellegrini wrote:
>> Hello,
>>
>> There is "feathering", used in mask refinement, which adapts
>> a mask's edge to edges detected in image.
>>
>> And recently, when updating the translation, I saw "feather size"
>> referring to the radius of the outer circle (or ellipsis) when
>> creating drawn masks.
>>
>> But those are not exactly the same... The latter seems more
>> like a smoothing/gradient area around the mask, not depending on
>> image features, while the former changes the effect of a mask in
>> a non-uniform way using image features (whatershed detection, or
>> something else? -- I'm not an expert in image processing).
>>
>> So -- is this intentional, and the same name was menat to be used
>> in both cases? If so, then I probably misunderstood something
>> (could someone help me understand why?)
>>
>> I ask in order to decide if I translate them to the same words
>> or not.
>>
>> Thanks!
>> Jeronimo
>>
>___
>> 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] Reproducable crash in culling mode

[Mica Semrick]

The most appropriate place to report this would be github.

-m

On January 5, 2021 7:45:59 AM PST, Tobias Krause  wrote:
>Hi,
>
>darktable 3.4 on Win 10 crashes reproducable when
>- culling mode with dynamic zoom is active
>- changing the filter criteria causes currently selected/shown pictures
>to be filter out
>
>Error message: darktable.exe caused an Access Violation at location
>637C6382 in module libdarktable.dll Reading from location
>.
>
>Detailed error bug report attached.
>
>Regards
>Toby
>
>
>___
>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] Import from camera/ memory card: some probleems

[Mica Semrick]

If you'd like to suggest what needs to be added to the manual instead of being 
vague, please do so. 

Opening an issue would be the best way to do that.

-m

On January 6, 2021 12:21:59 PM PST, Peter Harde  
wrote:
>I build from git current master, gphoto2 is available and recognized at
>build process. Nevertheless the buttton is not shown, even if I connect
>my
>camera (Sony alpha 77). This camera does not support tethering, so I
>assume
>this could be the reason for dt to hide the 'import from camera'
>button.
>The only way to load images directly from this camera is to mount it as
>block device. Also my build-in card reader is not recognized as
>'camera'.
>Unfortunately the manual (
>https://darktable-org.github.io/dtdocs/module-reference/utility-modules/lighttable/import/)
>does not give detailed info regarding the requirements a camera or card
>reader must fullfill to be recognized.
>Peter
>
>
>August Schwerdfeger  schrieb am Mi., 6. Jan.
>2021, 17:52:
>
>> The thumbnails do not show up when importing from a folder, only when
>> importing from a device using the 'gphoto2' library. If you see only
>two
>> buttons in the import module (and not the "scan for devices" button)
>then
>> your copy of Darktable was not compiled with 'gphoto2' support.
>>
>> I would not recommend using folder import for images on an SD card:
>if you
>> import such images and do not promptly move them *off* the SD card,
>you
>> will lose access to them as soon as the card is unmounted.
>>
>> --
>> August Schwerdfeger
>> aug...@schwerdfeger.name
>>
>>
>>>
>>>
>>>
>___
>>> 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] CAN NOT OPEN FOLDERS

[Mica Semrick]

The location of the lock files are given in the screenshots they attached.

-m

On February 11, 2021 9:10:42 AM PST, Patrick Shanahan  wrote:
>* susana gastelumendi  [02-11-21
>10:01]:
>> Hi,
>> 
>> I would like to ask for a solution for this problem.
>> 
>> I was working very well with Darktable and it began to happen this:
>> I can not open folders, it stays processing. I send you a screen shot
>> Then this notification opened, to delete this files LOCK. I send you
>screen shot
>> I did it. But it was not possible to open folders.
>> 
>> I unintastalled the app.
>> I reboot the computer.
>> Install again Darktable.
>> I can not open folder.
>> Again the the notification to delete files.
>> 
>> My technitian and also I asked Microsoft to see if it is a problem of
>Windows. It is not.
>> They told me I have to ask the developers.
>> 
>> Please, I would like to know the link where to see your answer.
>
>not a dev, but
>
>sounds like you have stopped darktable improperly, crashed, or ... and
>the
>library.db and data.db are still locked.  you can remove the locks by
>going to the directory where they are located, show hidden files and
>remove the two lock files.  only the lock files, not the library.db or
>data.db.  I do not run windows and do not know where these files are on
>you system.  your windows search-files might help.
>
>
>-- 
>(paka)Patrick Shanahan   Plainfield, Indiana, USA 
>@ptilopteri
>http://en.opensuse.orgopenSUSE Community Member   
>facebook/ptilopteri
>Photos: http://wahoo.no-ip.org/piwigo  paka @ IRCnet freenode
>___
>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-dev] Review: Translating the new darktable documentation

[Mica Semrick]

Hi all,

I've made a pull request that will integrate the necessary scripts to 
enable translation for the new markdown-based documentation.


Please provide any feedback you may have by reviewing the PR: 
https://github.com/darktable-org/dtdocs/pull/221


Due to the nature of translation, it will not be trivial to change the 
process after this. Please make your comments heard now by leaving 
comments on the PR.


Thanks!

-m
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] dtdocs now available to translate

[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/


Please let me know if you have any questions.

-m
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] dtdocs now available to translate

[Mica Semrick]

Hi Kevin,

You can see the HTML at https://darktable-org.github.io/dtdocs 

-m

On February 24, 2021 5:16:57 AM PST, Kevin Vermassen  
wrote:
>Hi
>
>I’m trying to figure out how this works for a Dutch translation. I see
>that the English ‘translation’ is finished. Where can I see the
>finished file as pdf or html? 
>
>I find it quite difficult to translate without context when I only see
>random words/sentences (similar problem as in the normal translation).
>
>Kevin
>
>> Op 24 feb. 2021, om 08:18 heeft Mica Semrick
> het volgende geschreven:
>> 
>> 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/
>> 
>> Please let me know if you have any questions.
>> 
>> -m
>>
>___
>> 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] Would partial translations of the manual be OK?

[Mica Semrick]

Hi,

This is controlled by weblate actually, and it doesn't go live until the file 
is 100% translated, I believe.

We can set that to whatever we'd like. What would be the advantage of having a 
partial translation go live?

-m

On March 5, 2021 5:27:51 AM PST, Jeronimo Pellegrini  wrote:
>Hello,
>
>I strated translating the darktable manual into pt_BR
>using the .po files directly and realized that, differently from when
>docbook was used, now translations go live as soon as they're commited
>(am I wrong?)
>
>I also see that the default po4a "80%" default value as the minimum
>for the translation to be used was not modified.
>
>But I was wondering if partial translations would be OK or not.
>Would it be OK to have only some sections of the manual translated?
>What about a section partially translated (say, 85%)?
>
>Thanks!
>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

Re: [darktable-dev] Would partial translations of the manual be OK?

[Mica Semrick]

Oh, OK, that's good then.

If you want to see where you're at, you can download the PO file from weblate 
and run the generated-translations.sh in the tools folder, then run Hugo to 
build the translated site.

-m

On March 5, 2021 8:13:18 AM PST, Jeronimo Pellegrini  wrote:
>Hi!
>
>I actually think it wouldn't be good, that's why I asked...
>
>So I keep translating, and it'll be up when it's 100% -- sounds
>good!
>
>Thanks,
>J.
>
>Mica Semrick  writes:
>
>> Hi,
>>
>> This is controlled by weblate actually, and it doesn't go live until
>the file is 100% translated, I believe.
>>
>> We can set that to whatever we'd like. What would be the advantage of
>having a partial translation go live?
>>
>> -m
>>
>> On March 5, 2021 5:27:51 AM PST, Jeronimo Pellegrini
> wrote:
>>>Hello,
>>>
>>>I strated translating the darktable manual into pt_BR
>>>using the .po files directly and realized that, differently from when
>>>docbook was used, now translations go live as soon as they're
>commited
>>>(am I wrong?)
>>>
>>>I also see that the default po4a "80%" default value as the minimum
>>>for the translation to be used was not modified.
>>>
>>>But I was wondering if partial translations would be OK or not.
>>>Would it be OK to have only some sections of the manual translated?
>>>What about a section partially translated (say, 85%)?
>>>
>>>Thanks!
>>>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] segfault ( newbie playing with crop/level )

[Mica Semrick]

Are you open to building the flatpak?

On March 18, 2021 5:03:12 PM PDT, Postmaster  wrote:
>Is there a way to build dARKTABLE without all the c/c++ optimizations?
>
>On 3/18/21 12:16 PM, William Ferguson wrote:
>> This should be reported at 
>> https://github.com/darktable-org/darktable/issues 
>> 
>> 
>> On Thu, Mar 18, 2021 at 11:56 AM Postmaster > > wrote:
>> 
>> Still playing with rotate. Still segfaulting. At least i did a
>gdb first
>> 
>>  > command name abbreviations are allowed if unambiguous.
>>  > (gdb) bt
>>  > #0  0x77af1532 in __memmove_avx_unaligned_erms () at
>> /lib64/libc.so.6
>>  > #1  0x77d9ba05 in memcpy (__len=,
>> __src=, __dest=) at
>> /usr/include/bits/string_fortified.h:34
>>  > #2  _default_process_tiling_roi._omp_fn.1 () at
>>
>/home/darktable/rpmbuild/BUILD/darktable-3.4.1/src/develop/tiling.c:1143
>>  > #3  0x777fcdce in gomp_thread_start () at
>/lib64/libgomp.so.1
>>  > #4  0x77973432 in start_thread () at
>/lib64/libpthread.so.0
>>  > #5  0x77a8d913 in clone () at /lib64/libc.so.6
>>  > (gdb)
>> 
>___
>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] Bug : dt git master exports in wrong order

[Mica Semrick]

> Just copy/pasting my bug report to github would take less time.

Reporting the bug is the beginning of the process and work, which others are 
now doing for you, not the end of it.

- m

On March 24, 2021 12:15:31 AM PDT, Peter Harde  
wrote:
>> I think you should not abuse the developers' time to raise issues on
>> your behalf, expecting them to do something that you feel violates
>> privacy (even if they were already foolish enough to have sold their
>> souls to the Devil so they can develop software for you and for me).
>
>Ironical remaks do not help anyone.
>
>> You could easily register an email account (e.g. on Protonmail or
>> Tutanota) that you do not use for anything else,
>I already have such an email address, that's not the problem.
>> use the private mode
>> of a browser you do not use for anything else, and access Github that
>> way, to protect your privacy if you are so concerned about it.
>
>Browsers private mode is not a solution. It does not protect against 
>tracking and many other technologies used to identify users. And if I 
>create a github account I have to agree to the "Terms of Service" of 
>microsoft/github. I've read this document, and all it's references. And
>
>I don't agree. I take care of privacy as a result of extremely negative
>
>experiences in the past.
>
>One last remark: It's surprising how many people spent time trying to 
>"guide me back on the right track". Just copy/pasting my bug report to 
>github would take less time.
>
>___
>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] News about darktable 3.6

[Mica Semrick]

Dear Pascal,

After reviewing copious amounts of user feedback, I would suggest we also 
remove the filmic module and recommend the Base Curve. New users will be so 
underwhelmed by the lack of options and sliders in Base Curve that surely 
darktable would soon overtake lightroom in terms of popularity, leaving all of 
us involved rich and famous.

- m

On April 1, 2021 7:49:05 AM PDT, Pascal Obry  wrote:
>
>Hello!
>
>Some news about darktable positioning.
>
>The good news is darktable binary is now half the size of previous
>release. Thanks to the removal of most superfluous modules that almost
>nobody uses like velvia, tone curves, liquify... The GUI is now lighter
>than ever. 
>
>Some views have also been removed like Map, Tethering, Slideshow to
>keep the most important ones. 
>
>All remaining modules have also been revamped to remove many controls
>and keep them usable by beginners (most dev modules have now one or two
>sliders), the others parameters have good defaults or computed based on
>the others. This will be a good ground to attract beginners, for hard-
>core people it is highly advised to keep 3.4.1.
>
>These decisions are been made because the dev community is too small
>and we cannot at this stage support all the base code. We have decided
>to keep Windows for now but the MacOS port will be removed.
>
>The 3.6 release is still plan for end of June or very early in July.
>
>Regards,
>
>-- 
>  Pascal Obry /  Magny Les Hameaux (78)
>
>  The best way to travel is by means of imagination
>
>  http://www.obry.net
>
>  gpg --keyserver keys.gnupg.net --recv-key F949BD3B
>
>___
>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] Apparently the removal of the XMP file still causes darktable to crash ...

[Mica Semrick]

Everything that is in the XMP is held in the db as well.

On April 7, 2021 6:30:59 AM PDT, Postmaster  wrote:
>Which leads me to think that the history of the picture is being kept
>in 
>an alternate place. Like somewhere in .cache. Maybe a .db?
>OR is it my imagination that something more is happening to me.
>___
>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] Re: [darktable-user] Plan for dt 3.6

[Mica Semrick]

When you perpetuate the perceived rudeness and negativity, you are part of the 
problem. If darktable doesn't work for you, and if you have such concerns about 
the quality, then please stop using it. 

If you're going to be insulting here, then please don't participate here.

Nobody is going to want to fix your issue if this is how you act.

- m

On April 12, 2021 8:19:50 PM PDT, Postmaster  wrote:
>one day you will learn how to read.
>
>1) patrick shanahan is in the business of making noise
>2) At this moment, create and support does not exist. There is just no 
>explanation as to why release after release has the same issues. Any
>one 
>for QA. I dont see it. Do you? the rotate and clip issue(s)are in
>3.4.1, 
>3.4.1.1, as well in 3.6 . Why would anyone use darktable, if it behaves
>
>erratically, inconsistently, and just dies at any moment. Rotate and 
>clip should be rock solid by now. xmp files should be rock solid by
>now. 
>the 500 or so issues should be eliminated. Then again, see #1 .
>
>anyway, my orig question is anyone working on the rotate and clip
>issues?
>
>On 4/12/21 8:44 PM, darkta...@911networks.com wrote:
>> On Mon, 12 Apr 2021 18:00:48 -0400
>> Postmaster  wrote:
>> 
>>> Is there some reason why you are making so much noise? Is this how
>>> u do business on the internet? go do your own research.
>> 
>> 1. This is not a business.
>> 2. It's a group of volunteers that create and support darktable in
>> their spare time.
>> 
>___
>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-dev] Collecting for a gift for the exiv2 maintainer

[Mica Semrick]

Hey all,

Robin Mills, of the exiv2, is retiring from the project (after having 
already been retired from his regular job) after ensuring that we get 
the necessary bits for supporting CR3 files.


Robin has been working on exiv2 for a long time (~10 years) and exiv2 is 
a library that a ton of applications use, including digikam and darktable.


If you'd like to chip in for a gift, the paypal is 
https://www.paypal.com/pools/c/8yLNZzNUSj


If you can't or don't want to contribute, please ignore this message. 
Since this is going to multiple mailing lists, please don't reply.


You contribution is appreciated!

- mica
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Translation tips

[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

Re: [darktable-dev] Translation tips

[Mica Semrick]

Hi Peter,

I think the original mail was talking about translating the strings for 
darktable itself, not dtsocs, which is the user manual. The strings for 
darktable itself do not use weblate, while the user manual does.

For the user manual, you will not find every string of text in the application, 
since we are telling people how to use it.

I find flatpak to be an easy way to build the master branch of the darktable 
application.

As for the technicality of the material, just do the best you can. The cool 
thing about weblate is that it makes it easy for multiple people to contribute, 
so perhaps someone else can help out as well.

Hope that helps.

-m

On April 22, 2021 2:13:10 AM PDT, Peter Schlaufer  wrote:
>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 Weblate   Tab 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

Re: [darktable-dev] documentation: primary and secondary sort order

[Mica Semrick]

Hi,

That's awesome, can you submit the patch as a PR on github? 
https://github.com/darktable-org/dtdocs

-m

On April 26, 2021 12:36:06 PM PDT, Solarer  wrote:
>Hi there,
>I created a patch for the documentation because there was some weird
>behaviour that could not be explained with the current documentation
>(see: https://github.com/darktable-org/darktable/issues/7573).
>
>TLDR: If you sort by star rating and two pictures have the same rating,
>a secondary (hidden) sort function decides the final order. This makes
>images jump around if you change the color label... so people might
>think they found a bug.
>
>This update to the documentation might help a lot already, but in my
>opinion this secondary sort order should be visible and selectable via
>a
>drop down menu aswell.
>
>Best, Jan
>
>
>___
>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] Bug: dt git master does not start anymore

[Mica Semrick]

Vibrancergb has been removed. Clean your build and source directory and rebuild.

On April 30, 2021 7:45:13 AM PDT, Peter Harde  
wrote:
>Hi developers,
>
>just downloaded release-3.5.0-1954-gbdbc7ede5. This version aborts with
>
>error message when trying to launch:
>
>*[dt_ioppr_check_so_iop_order] missing iop_order for module
>vibrancergb**
>**ERROR: iop order looks bad, aborting.*
>
>Tried also with empty configdir, same behaviour.
>
>Platform
>
>* darktable version : 3.5.0-1954-gbdbc7ede5
>* OS    : Linux - kernel 5.4.0-72.80
>* Linux - Distro    : Ubuntu 20.04
>* Memory    : 4 GB
>* Graphics card : NVIDIA GeForce GT435M
>* Graphics driver   : NVIDIA driver 390.143
>* OpenCL installed  : yes
>* OpenCL activated  : yes
>* Xorg  : 1.20.9-2ubuntu1.2~20.04.1
>* Desktop   : LXQt
>* GTK+  : 3.24.20-0ubuntu1
>* gcc   : gcc 9.3.0-1ubuntu2
>
>Best regards
>
>Peter Harde
>
>___
>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] Difference between RAW image as seen on Nikon DSLR screen and after Import

[Mica Semrick]

Hi, this page explains what is going on quite well:
http://rawpedia.rawtherapee.com/Editor#Eek.21_My_Raw_Photo_Looks_Different_than_the_Camera_JPEG

- m

On May 1, 2021 8:50:12 AM PDT, "Ramnarayan.K"  wrote:
>Hi
>
>Am a basic user of Darktable.
>
>Pictures imported as usually Nikon NEF format raw files taken on a
>D3300 SLR
>
>I have not changed any of the defaults in darktable
>
>The functions I use are
>Histogram to adjust brightness , Exposure
>Crop
>and Export to Jpeg
>
>However for sometime now and getting frustrated between the difference
>in
>pictures as seen on the DSLR LCD screen and what I see on Darktable
>
>The DSLR screen pcitures are usually brighter, richer and seem to be in
>focus and sharp.
>
>On Darktable the pictures are almost invariably duller and a touch out
>of
>focus (enough to not be nice anymore.
>
>My system specs are  ( Linux Mint System on Thinkpad E14) Darktable
>version
>3.0.1
>
>Am wondering if there is some setup or add on that I am missing ?
>
>your suggestions and advice please
>
>thanks
>ram
>
>___
>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] Difference between RAW image as seen on Nikon DSLR screen and after Import

[Mica Semrick]

> However is there a way to "replicate " what the camera is doing through dark 
> table

Technically yes, but you'll need a color target, which is pricey.

There is so much possibility with the raw file that it'd be a waste for 
darktable to just try and approximate the in-camera jpeg. 

If you just want the camera jpeg, then shoot in only jpeg or raw + jpeg.

-m

On May 1, 2021 10:43:09 AM PDT, "Ramnarayan.K"  wrote:
>Hi Berhard
>
>On Sat, 1 May 2021 at 22:59, Bernhard 
>wrote:
>
>>
>> this is simple: what you see in-camera is the in-camera-jpg provided
>by
>> the in-camera-engine.
>> These in-camera-jpg are embedded in the raw also and can be extracted
>> using exiftool
>>
>> https://exiftool.org/examples.html
>>
>> exiftool -b -JpgFromRaw -w _JFR.JPG -ext NEF -r .
>>
>>
>> darktable reads the raw data and expects YOU to work with them
>>
>> Thanks - so 1 method would be to extract the JPEG and use that
>avoiding
>all the Raw processing
>
>or maybe my bad photography skills are being hidden by the camera :-)
>
>will read up the inks
>
>However is there a way to "replicate " what the camera is doing through
>dark table
>
>ram
>
>___
>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-dev] 3.6 blog post time!

[Mica Semrick]

Hi all,

As we move towards another fantastic release, it is time to draft the blog post!

To ease the initial authoring experience, we're using hackmd again.

You can contribute to the post here: 
https://hackmd.io/4Y6kfnGFT9OXSM1wZ7ljMw?both

Thanks!

-m
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] 3.6 blog post time!

[Mica Semrick]

Hopefully we'll be far enough along in about two weeks for translators to start.

-m

On May 9, 2021 1:25:10 PM PDT, Bernhard  wrote:
>
>
>Mica Semrick schrieb am 09.05.21 um 21:57:
>> Hi all,
>>
>> As we move towards another fantastic release, it is time to draft the
>blog post!
>>
>> To ease the initial authoring experience, we're using hackmd again.
>>
>> You can contribute to the post here:
>https://hackmd.io/4Y6kfnGFT9OXSM1wZ7ljMw?both
>>
>Thanks for this note, is there already a plan for a deadline date so 
>that the translators can start?
>
>-- 
>
>regards
>Bernhard
>
>https://www.bilddateien.de
>
>___
>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] Problems trying to test new noise profiles

[Mica Semrick]

If you open the json file and look at the camera name, it need to match what 
darktable says the camera name is in the info panel.

-m

On May 15, 2021 11:25:47 PM PDT, Terry Duell  wrote:
>Hello,
>I have generated a set of noise profiles for the Pentax K-3 III, and
>attempted
>to test them by starting darktable using the command line;
> 
>'darktable --noiseprofiles  presets.json'
>
>When editing K-3 III imported images, and selecting 'denoise
>(profiled)' there
>is no 'found match for ISO...', so I'm wondering if darktable is
>recognising the
>data in presets.json as applicable to the images.
>Are there any additional checks/tests that I can do to provide
>confidence that
>darktable is using the new generated noise profiles (presets.json) for
>the
>camera?
>I'd like to have some confidence that the profiles are OK before
>submitting
>them.
>
>Cheers,
>-- 
>Terry Duell 
>
>___
>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-dev] Thanks to those who donated to Robin's retirement!

[Mica Semrick]

Thanks to everyone who donated to exiv2's maintainer Robin Mills retirement 
gift fund!

He received euphonium lessons with his favorite musician and several bottles of 
nice looking whiskey.

He sent message: https://hackmd.io/3O0XYA6GQHmI2gAeTLZ-WA?view

Thanks!

-m
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Manual translation workflow, new contributors

[Mica Semrick]

Hi J,

The instructions on the dtdocs are still valid.

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.

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.

-m

On June 1, 2021 11:02:57 AM PDT, Jeronimo Pellegrini  wrote:
>Hello,
>
>I have been focusing more on the translation of darktable itself, and
>when I was about to give more attention to the manual, I incidentally
>got messages from a few pt_BR users that said they'd like to contribute
>I thought it would be nice to have more people involved (it would also
>make the pt_BR dt user community stronger).
>
>What I was planning to do is to use the workflow in the REAMDE at
>https://github.com/darktable-org/dtdocs but I do remember there was the
>intention of using a web-based system like weblate.
>Although it's not the best tool for me (I don't always have a browser
>open, and sometimes work disconnected), certainly the other pt_BR users
>would like to use something like weblate.
>
>So -- what are the posible workflow options currently for the manual
>translation, considering that there will be more people working (so
>if the need to coordinate a team could be avoided, it would be nice)?
>
>Are the instructions on the dtdocs repo still valid? And are they the
>only option?
>
>Also -- Pascal jsut sent a schedule for the 3.6 release, but it wasn't
>clear to me if the manual translation should fit the same schedule or
>not.
>
>Thank you!
>Jeronimo
>___
>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] Manual translation workflow, new contributors

[Mica Semrick]

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

Re: [darktable-dev] darktable community and freenode

[Mica Semrick]

Freenode does seem to be tanking currently, but there has not been an official 
move from freenode to somewhere else.

However, there is now #darktable on OFTC and libera, in case we do want to move 
somewhere.

OFTC seems like the logical choice, as it's been around a while with a 
governance structure that is clear, but that's just my 2 cents.

-m

On June 3, 2021 10:34:29 AM PDT, Jeronimo Pellegrini  wrote:
>Hello,
>
>One translator asked me about a part of the manual that
>mentions channel #darktable at freenode -- he wants to know
>if this is outdated, since everybody is moving away form freenode.
>
>Is the IRC channel not being used anymore, and hence the information
>could perhaps be removed from the manual? Or was a new channel
>created at some other srever (libera.chat maybe)?
>
>Thanks,
>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-dev] Official IRC channel moved to OFTC

[Mica Semrick]

Hi everyone, 

We have moved our official support channel to OFTC after deciding that the 
actions of the freenode admins are not in keeping with the spirit of free 
software.

Please join us in #darktable on OFTC, hope to see you soon!

- m
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] version 3.6 blog post available for review

[Mica Semrick]

Hi all,

The 3.6 release blog post is available for review at 
https://github.com/darktable-org/dtorg/pull/143


PRs are much preferred to comments. If you're going to suggest a lot of 
changes, please make a PR, as github's comment system isn't great for a 
lot of small changes.


-m
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Call for User Manual translations

[Mica Semrick]

Hi all, we have updated the PO files in Weblate (https://weblate.pixls.us) and 
would like to request that translators update the strings so we can tag 3.6.x 
release, then move forward to the 3.8 release text.

We will export from weblate for 3.6.x in approximately two weeks. Please 
communicate quickly if that time line does not work for you.

-m
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Call for User Manual translations

[Mica Semrick]

Hi Lukasz,

You can download your po file from weblate once you've translated some strings, 
stick that file in the PO folder, then follow 
https://darktable-org.github.io/dtdocs/special-topics/translating/#generating-translated-files
to generate the translated files, then build the output with Hugo.

-m

On August 18, 2021 3:26:41 AM PDT, "Łukasz Karcz"  wrote:
>Hello, I translated Polish dt 3.4 manual an epoch ago and finally found
>some time to come to weblate to start translating within the new system. Is
>there a way to obtain a snapshot / working copy of my translation, i.e. to
>see a copy of the *online* manual with partially translated strings, like
>it was previously possible with PDF translations for versions up to 3.4?
>
>I do translations directly via weblate UI.
>
>Regards, ŁK.
>
>czw., 5 sie 2021 o 18:26 Mica Semrick  napisał(a):
>
>> Hi all, we have updated the PO files in Weblate (https://weblate.pixls.us)
>> and would like to request that translators update the strings so we can tag
>> 3.6.x release, then move forward to the 3.8 release text.
>>
>> We will export from weblate for 3.6.x in approximately two weeks. Please
>> communicate quickly if that time line does not work for you.
>>
>> -m
>> ___
>> 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] Doubts about dtdocs translation

[Mica Semrick]

Hi, I'm responsible for updating the POT and PO files. We do so periodically, 
and the process is currently manual, and I think it will probably stay that 
way, since I keep up reasonably well with docs development and docs 
contributors chat frequently in the chatroom. We don't want to pass churn in 
the English docs on to translators because that is a waste of your time. We 
usually synchronize when we feel the English docs are in a good enough state 
that translation can start. We welcome feedback about this process, of course.

If you want to proof your translations, I suggest you checkout the commit where 
I last updated the pot and po files. If your language isn't complete in that 
commit, you can download the pot file for your language from weblate and 
replace the pot file locally, then run Hugo. po4a, the tool we use to convert 
po to localized markdown, currently has a threshold of 80% of the file 
translated in order to create a markdown file. You can change that locally as 
well of need be.

On September 19, 2021 2:38:36 PM PDT, Marcus Gama  wrote:
>Hi,
>
>I'm translating and reviewing the darktable manual in Brazilian Portuguese
>and I've been doing the local generation of the translated files and
>running hugo server. All links that reference an _index.md file when
>clicked return "page not found" on hugo server. Links pointing to other
>pages work perfectly. The same happens at
>https://darktable-org.github.io/dtdocs/. The English original works
>correctly. The translated one has an error. If I remove the '_index.md'
>from the link (pointing to the page's root directory), the link works. Is
>this right? Do I have to fix the link by removing the '_index.md' in the
>translated file?
>
>Another point is about synchronizing the weblate with github. About 2 weeks
>ago the message that the weblate repository has many changes compared to
>the upstream has been appearing. Is there a periodicity when the weblate is
>updated (pot file updated)? When generating the manual for review, several
>pages and some excerpts from pages do not appear as translated, possibly as
>a result of this lack of sync (since the translation into Portuguese is
>100% complete), which makes the review difficult. I know we have a long way
>to go until version 3.8 is released. But if the manual developers have a
>plan, I'd like to know.
>
>Thanks for the excellent open source photography workflow application and
>raw developer!
>
>Marcus
>
>___
>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] Incorrect online help URLs in current git master

[Mica Semrick]

We are aware of the issue, thanks!

On October 31, 2021 12:56:51 AM PDT, Peter Harde  
wrote:
>Hi developers :
>
>dt 3.7.0+1354~g70862d835
>
>All URLs of the online help function are incorrect, example (error 404 : 
>file not found):
>
>*https://darktable-org.github.io/dtdocs/module-reference/processing-modules/contrast-equalizer/*
>
>The correct URL must be
>
>*https://darktable-org.github.io/dtdocs/en-us/module-reference/processing-modules/contrast-equalizer/*
>
>so actually *en-us/* is missing. Tried german end english localization 
>with same result. An a second hint : at 
>https://darktable-org.github.io/dtdocs/en-us/ the "Search" field (top 
>right) does not provide results any more when entering a search keyword.
>
>Best regards
>
>Peter Harde
>
>
>
>___
>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-dev] Help translate the User Manual!

[Mica Semrick]

It'd be awesome to have a few more languages translated for the 3.8 release!

The web app we use to translate is here: 
https://weblate.pixls.us/projects/darktable/dtdocs/


Thank you to all translators!

-m

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Double-click / ctrl-click / shift-click on folder or Film roll

[Mica Semrick]

Thanks for following up!

On November 17, 2021 2:48:34 PM PST, "Sébastien Chaurin" 
 wrote:
>For the sake of keeping tracks of issues AND resolution, here is what I’ve 
>found.
>
>With the help of an active member on the fb group, I created a brand new 
>configdir using CLI, and found easily that the issue came from the darktablerc 
>file.
>From that point a quick diff showed that one line was particularly interesting 
>:
>
>plugins/lighttable/collect/mode0=0
>
>Compared to my file supposed to be corrupted :
>
>plugins/lighttable/collect/mode0=2
>
>No idea how I managed to change that setting from the GUI nor what does this 
>mode do exactly apart from excluding exactly what you select as a collection. 
>There is probably a good reason for it to be there, it just did not jump at me 
>as to why :)
>
>Cheers
>
>> On 17 Nov 2021, at 07:33, Sébastien Chaurin  
>> wrote:
>> 
>> Hi,
>> 
>> Yesterday while trying to apply a style to a small batch of pictures, DT 
>> segfaulted. 3 times.
>> Not sure about what was going on, I realised that I was running 3.6.0 and 
>> not 3.6.1 and so I upgraded upon closing the program properly. At that time 
>> it asked for a db maintenance which I allowed.
>> 
>> Once the upgrade was done (I am running on macOS, and so DT 3.6.1.6 now) 
>> Everything seemed to be fine except that the filtering attributes were not 
>> functioning as it should. I usually use the folder option first where, from 
>> the documentation you have some options :
>> folder
>> The folder (file path) where the image file is located. Click on a folder 
>> while holding Ctrl+Shift to switch to the corresponding film roll. 
>> Right-click to remove the collection or tell darktable that its location has 
>> changed in the file system. Double-click to show only the images in the 
>> selected folder; Ctrl+click to show only the images from any sub-folders; 
>> Shift+click to show the images from the current folder plus all sub-folders.
>> The behavior that I have now is the following :
>> - double-click shows only the subfolder content instead of just the 
>> currently selected folder
>> - shift-click show only the currently selected folder (instead of that 
>> content + any subfolder)
>> - ctrl-click shows no images
>> 
>> I don't care about my library.db as I usually process and then remove the 
>> images to always have a small library. I keep the xmp.file along with the 
>> originals so I don't care about re-importing from time to time.
>> I backed up my library manually and restarted darktable, reimporting the 
>> folder which contains several subfolders, and the issue is still here.
>> It's also confusing things up with film roll e.g. when I double click a film 
>> roll for a subfolder, i have the same issue - that is consistent in a way...
>> 
>> Has anyone experienced the same thing ? What am I missing ?
>> 
>> Since I now have the issue to display just the images I want, I did not try 
>> to reapply the style to see if 3.6.1.6 solved the initial issue.
>> 
>> Thanks ahead of time for your help
>> Cheers
>
>
>___
>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-dev] dtdocs are frozen for translation!

[Mica Semrick]

Hi all,

dtdocs are now frozen in the English version and ready for translation. 
You can log into the weblate instance to translate the user manual: 
https://weblate.pixls.us/projects/darktable/dtdocs/



Thanks!

-m

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Lighttable: Preload / pre-caching of full previews

[Mica Semrick]

Its all or nothing, you can select which ones you want. Adjust the thumbnail 
size to your liking, and then run dark tables generated cache.

-m

On January 3, 2022 11:29:38 AM PST, Christian Birzer 
 wrote:
>Hello,
>
>you are not alone with this request. I also would like to have a easy 
>way to generate the previews. I'd like to select the images I want to 
>generate and then hit a button or menu entry to generate the full size 
>preview for these. Then you could ctrl-a in your last import, start 
>generation, drink a coffee and begin sorting your pictures.
>
>Doing this with an external tool works, but is not so convenient, of 
>course. And I don't know how to select the images that shall be 
>recalculated. It's not required to regenerate all thumbnails, just the 
>last import to work faster with them.
>
>
>-- 
>Christian Birzer
>christ...@christianbirzer.de
>www.ChristianBirzer.de
>www.500px.com/ChristianBirzer
>www.flickr.com/ChristianBirzer
>www.facebook.com/Birzer.Christian
>www.instagram.com/birzer.christian
>
>Am 03.01.2022 um 18:30 schrieb Jørn Villesen Christensen:
>> Hi there,
>>
>> First off: Thank you for a great application. I enjoy using darktable 
>> very much, and I feel that (with the latest 3.8) it got both better 
>> and faster on my machine. Thank you! :-)
>>
>> I have a feature request, though. If it is already implemented, then 
>> maybe I need a pointer to a place in the documentation :-D But, the 
>> request is: The ability (within lighttable mode) to enable preload / 
>> pre-caching of full previews.
>>
>> To put some more words on my work situation: When I am culling images 
>> in lighttable mode, I go to full preview mode (shortcut 'w' or 'f') 
>> and flick through the images. Whenever darktable encounters a "new" 
>> image, it takes a second to render a full screen preview (or more if I 
>> have already done some edits). It then caches it so the next time 
>> (within same session) I show that image, it is shown immediately. This 
>> delay, however, is a bit annoying when I flick through the images for 
>> comparison. I therefor often find myself scrolling fast 10 to 20 
>> images ahead, triggering a preview-generation, for then to go back to 
>> "start" and actually viewing the images.
>>
>> I would love it, if i did not have to do the little scroll back and 
>> forth dance, but that darktable would just start generating previews 
>> whenever I went into full preview mode.
>>
>> I know there are some open questions (How many previews to generate? 
>> What happens if the cached images hits the cache limit? What then when 
>> you zoom in on a photo?) which I would be happy to discuss, but first 
>> step would be to check in whether a) I am the only one with this 
>> request? b) Is this already implemented (and I just haven't found the 
>> feature)?
>>
>> BR
>> Jørn
>>
>>
>> ___ 
>>
>> 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] Help wanted in developing extreme dynamic range

[Mica Semrick]

Hi, the best place to get good responses is probably the Play Raw category at 
https://discuss.pixls.us

You can post your raw file there, and people will edit it and post the sidecar 
file for you to inspect.

-m

On January 4, 2022 11:26:37 AM PST, Christian Birzer 
 wrote:
>Hello to all dt image development experts (and all others!)
>
>When I try to develop some of my most problematic images with high 
>highlights and dark shadows in dt I could not get any acceptable result 
>so far. The same image developed in LR needs just two sliders to their 
>extreme and everything is fine (at least in my eyes, others might have 
>other prefrences of course). I guess it is possible to get the same 
>results in dt too but I could not figure out how.
>
>So my wish: Maybe someone can try to get a equal result in dt and let me 
>know how. This also could be of interest to other users, so it may be a 
>good info for the website/blog or documentation. Some kind of how-to (or 
>"look what we can do")? Of course, only if the results are good :-)
>
>On the other hand, it could be fine image to do some testing or 
>improvments of the algorithms if needed.
>
>The original dng raw file and a LR-developed jpeg are here:
>
>https://my.hidrive.com/share/htk4.24xpg
>
>Of course, please feel free to use the images to test, document etc. or 
>whatever you want.
>
>Thanks a lot!
>Christian
>
>-- 
>Christian Birzer
>christ...@christianbirzer.de
>www.ChristianBirzer.de
>www.500px.com/ChristianBirzer
>www.flickr.com/ChristianBirzer
>www.facebook.com/Birzer.Christian
>www.instagram.com/birzer.christian
>
>___
>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-dev] User Manual text is still frozen for translations!

[Mica Semrick]

Hi, 

Just a reminder that if you want to translate the User manual for 3.8 that the 
English is frozen for another few weeks!

The translation is done on weblate: https://weblate.pixls.us

-m
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] pull request translation dutch

[Mica Semrick]

I will merge it when I have a free moment. Time has been short lately, sorry.

- m

On January 20, 2022 6:28:10 AM PST, Ger Siemerink  wrote:
>Nice to see, your willing and effort, Nick. Hope to see the manual online.
>Greetz Ger
>
>Op ma 17 jan. 2022 om 23:14 schreef Nick Alderweireldt <
>nickalderweireldt...@gmail.com>:
>
>> Dear,
>>
>> Can you please enable the dutch translation of darktable ? The translation
>> file nl.po is in annex. I followed the rules that I found on the darktable
>> page for translators. Hence this mail. Can you let me know what I have to
>> do if this is not the correct way. It is my first time. I downloaded the
>> nl.po file from darktable git as well as the .pot file and edited the
>> translation with poedit with the .pot as catalogue.
>> mr Kevin Vermassen made the previous translation (july 2021). I made the
>> translation of 3.8 after having communicated and agreed with Kevin.
>>
>> I also translated the darktable 3.8 manual to dutch via Weblate. Can you
>> please make this translation available on the darktable manual 3.8 page in
>> the other language links ?
>>
>> Can you please adapt the credits of dutch translator. Ger Siemerinck
>> stopped translating (I communicated with him as well).
>>
>> Thanks
>> --
>> Nick
>>
>>
>>
>> ___
>> darktable developer mailing list to unsubscribe send a mail to
>> darktable-dev+unsubscr...@lists.darktable.org
>>
>
>
>-- 
>met vriendelijke groet / kind regards Ger
>mailto:g.siemer...@gmail.com
>
>___
>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] Ubuntu21-10 build exiv2 dependency - is it necessary?

[Mica Semrick]

If you remove the Ubuntu version of exiv2 and add the repo instead of just 
downloading the deb, you'll get exiv2 as well as darktable.

-m

On February 3, 2022 3:34:08 AM PST, Wiktor Nowak  wrote:
>I've found that Ubuntu build linked in projec page:
>
>https://software.opensuse.org/download.html?project=graphics:darktable&package=darktable
>
>currently fails to install on Ubuntu 21-10 because of exiv2 lower than 
>2-27.5. Currently Ubuntu doesn't integrated new exiv2 and it will almost 
>certainly not be integrated until next release.
>
>I've found a package downloaded in 25'th December from the same place 
>and it installs fluently without exiv2 dependency fail.
>
>It's now actually blocking new users from using darktable 3.8 on Ubuntu 
>for no reason I think because darktable works fine on older exiv2 only 
>lacking a cr3 support. There is no point of providing a build for Ubuntu 
>which can't be installed on Ubuntu.
>___
>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] Ubuntu21-10 build exiv2 dependency - is it necessary?

[Mica Semrick]

Your system is your responsibility. The project publishes the source code, and 
that's pretty much it. We can't make assumptions about what packages your 
distro has or does not have. There are too many distros and too many package 
versions.

If you want a mostly pain-free solution, get the flatpak from flathub.

On February 4, 2022 1:40:20 AM PST, Wiktor Nowak  wrote:
>Thanks for mentioning this option to build darktable but project page 
>still doesn't say a word. Regular users struggling to get darktable 
>should have an andvice on install page,not in devs thread as probably 
>not many will see it.
>
>W dniu 04.02.2022 o 10:26, David Houlder pisze:
>> On 3/2/22 22:34, Wiktor Nowak wrote:
>>> I've found that Ubuntu build linked in projec page:
>>>
>>> https://software.opensuse.org/download.html?project=graphics:darktable&package=darktable
>>>  
>>>
>>>
>>> currently fails to install on Ubuntu 21-10 because of exiv2 lower than 
>>> 2-27.5. Currently Ubuntu doesn't integrated new exiv2 and it will 
>>> almost certainly not be integrated until next release.
>> 
>> For what it's worth I've opened a bug report to request exiv2 0.27.5 for 
>> Ubuntu 22.04.
>> https://bugs.launchpad.net/debian/+source/exiv2/+bug/1959508
>> Doesn't solve your immediate problem though :-/.
>> 
>> While I'm here, if anyone wants to build darktable 3.8 from source 
>> against libexiv2 that's installed in /usr/local _and_ you also have an 
>> older libexiv2 installed by a system package, you can do this:
>> 
>> mkdir build
>> cd build
>> export CMAKE_PREFIX_PATH=/usr/local/
>> cmake -DCMAKE_INSTALL_PREFIX=/opt/darktable 
>> -DCMAKE_INSTALL_RPATH_USE_LINK_PATH=TRUE    ..
>> 
>> That will make sure darktable is both built with and runs with the 
>> library in /usr/local (or wherever you put it).
>> 
>> 
>> 
>> ___ 
>> 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] Ubuntu21-10 build exiv2 dependency - is it necessary?

[Mica Semrick]

> So: the choice between plague and Colera

So the "batteries included" flatpak is a disease, and the distro *you* choose 
to run is also a disease. 

There is no pleasing people.

On February 4, 2022 8:23:38 AM PST, Bernhard  
wrote:
>Mica Semrick schrieb am 04.02.22 um 16:30:
>> Your system is your responsibility. The project publishes the source code, 
>> and that's pretty much it. We can't make assumptions about what packages 
>> your distro has or does not have. There are too many distros and too many 
>> package versions.
>>
>> If you want a mostly pain-free solution, get the flatpak from flathub.
>
>
>Patrick Shanahan schrieb am 04.02.22 um 16:41:
>> or utilize the ready made package your distro provides.
>which immediately causes further problems:
>In many cases, old versions can be found there, because not everyone goes 
>through the hassle of a rolling release distribution. And on a question e.g. 
>here or in a forum then the answer comes prayer mill-like: But THAT is an old 
>version, get a new one, then you can ask again.
>
>So: the choice between plague and Colera
>
>No question, I understand why developers especially in the open source area 
>argue and work exactly like this: it is simply impossible to test every 
>program version against every operating system version, especially for 
>backwards compatibility.
>
>The problem then has the user - and I understand this as follows: how can we 
>point out the user with such a foreseeable problem (this exiv2 is just brand 
>new, and because that is so, it is also in the OBS repo as described above) 
>more specifically than is the case so far?
>
>-- 
>
>regards
>Bernhard
>
>https://www.bilddateien.de
>
>___
>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] Ubuntu21-10 build exiv2 dependency - is it necessary?

[Mica Semrick]

In order to read metadata from cr3 files, you need exiv2 0.27.5. Without that 
version, darktable cannot read the metadata to demoasic the cr3 file.

If you don't need cr3 support, then what your distro ships for exiv2 is 
probably fine and darktable will work fine.

On February 5, 2022 12:59:57 AM PST, Wiktor Nowak  wrote:
>Let's say I would agree if it would be a discussion why user gets cr3 
>support or not. But it's a hard dependency to even install dartkrable 
>when darktable itself runs smoothly with older exiv2 so why this 
>artificial dependency is even there? You said project can't make 
>assumption on what is in user's system but actually that assumption has 
>been made and causes problem.
>
>
>
>W dniu 04.02.2022 o 16:30, Mica Semrick pisze:
>> Your system is your responsibility. The project publishes the source 
>> code, and that's pretty much it. We can't make assumptions about what 
>> packages your distro has or does not have. There are too many distros 
>> and too many package versions.
>> 
>> If you want a mostly pain-free solution, get the flatpak from flathub.
>> 
>> On February 4, 2022 1:40:20 AM PST, Wiktor Nowak  wrote:
>> 
>> Thanks for mentioning this option to build darktable but project page
>> still doesn't say a word. Regular users struggling to get darktable
>> should have an andvice on install page,not in devs thread as probably
>> not many will see it.
>> 
>> W dniu 04.02.2022 o 10:26, David Houlder pisze:
>> 
>> On 3/2/22 22:34, Wiktor Nowak wrote:
>> 
>> I've found that Ubuntu build linked in projec page:
>> 
>> 
>> https://software.opensuse.org/download.html?project=graphics:darktable&package=darktable
>> 
>> <https://software.opensuse.org/download.html?project=graphics:darktable&package=darktable>
>> 
>> 
>> 
>> currently fails to install on Ubuntu 21-10 because of exiv2
>> lower than
>> 2-27.5. Currently Ubuntu doesn't integrated new exiv2 and it
>> will
>> almost certainly not be integrated until next release.
>> 
>> 
>> For what it's worth I've opened a bug report to request exiv2
>> 0.27.5 for
>> Ubuntu 22.04.
>> https://bugs.launchpad.net/debian/+source/exiv2/+bug/1959508
>> <https://bugs.launchpad.net/debian/+source/exiv2/+bug/1959508>
>> Doesn't solve your immediate problem though :-/.
>> 
>> While I'm here, if anyone wants to build darktable 3.8 from source
>> against libexiv2 that's installed in /usr/local _and_ you also
>> have an
>> older libexiv2 installed by a system package, you can do this:
>> 
>> mkdir build
>> cd build
>> export CMAKE_PREFIX_PATH=/usr/local/
>> cmake -DCMAKE_INSTALL_PREFIX=/opt/darktable
>> -DCMAKE_INSTALL_RPATH_USE_LINK_PATH=TRUE    ..
>> 
>> That will make sure darktable is both built with and runs with the
>> library in /usr/local (or wherever you put it).
>> 
>> 
>> 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
>

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Ubuntu21-10 build exiv2 dependency - is it necessary?

[Mica Semrick]

In the time it took you to write two emails of several paragraph each, you 
could've instead opened a pull request against the website repo which corrects 
your perceived mistakes or amended the description in the OBS repo.

On February 5, 2022 7:26:42 AM PST, Bernhard  
wrote:
>> then what your distro ships for exiv2 is probably fine and darktable will 
>> work fine.
>This is simply not true in that common form.
>I use Debian. I downloaded 3.8 from OBS on Christmas Day - it installed fine.
>Few weeks later I suggested this to a friend - he also downloaded and could 
>not install because of exiv2.
>
>I compared the .deb from my download with the version (same version number, 
>same os) he downloaded and in the meantime the dependencies had been changed 
>between Dec. 24 and sometime in January in that .deb file.
>He included the complete OBS repo then and it installed. In the meantime I 
>still use the Christmas version without repo and exiv2 and this also works.
>So you *may* be right under certain circumstances only - always depending on 
>the binary you use.
>
>What I suggest is simply to give a note somewhere on the webpage or in OBS 
>about this so people have a root to go along and not simply get lost.
>At least I will put a note on my webpage.
>
>Mica Semrick schrieb am 05.02.22 um 14:59:
>> In order to read metadata from cr3 files, you need exiv2 0.27.5. Without 
>> that version, darktable cannot read the metadata to demoasic the cr3 file.
>>
>> If you don't need cr3 support, then what your distro ships for exiv2 is 
>> probably fine and darktable will work fine.
>>
>> On February 5, 2022 12:59:57 AM PST, Wiktor Nowak  wrote:
>>> Let's say I would agree if it would be a discussion why user gets cr3
>>> support or not. But it's a hard dependency to even install dartkrable
>>> when darktable itself runs smoothly with older exiv2 so why this
>>> artificial dependency is even there? You said project can't make
>>> assumption on what is in user's system but actually that assumption has
>>> been made and causes problem.
>>>
>>>
>>>
>>> W dniu 04.02.2022 o 16:30, Mica Semrick pisze:
>>>> Your system is your responsibility. The project publishes the source
>>>> code, and that's pretty much it. We can't make assumptions about what
>>>> packages your distro has or does not have. There are too many distros
>>>> and too many package versions.
>>>>
>>>> If you want a mostly pain-free solution, get the flatpak from flathub.
>>>>
>>>> On February 4, 2022 1:40:20 AM PST, Wiktor Nowak  wrote:
>>>>
>>>>  Thanks for mentioning this option to build darktable but project page
>>>>  still doesn't say a word. Regular users struggling to get darktable
>>>>  should have an andvice on install page,not in devs thread as probably
>>>>  not many will see it.
>>>>
>>>>  W dniu 04.02.2022 o 10:26, David Houlder pisze:
>>>>
>>>>  On 3/2/22 22:34, Wiktor Nowak wrote:
>>>>
>>>>  I've found that Ubuntu build linked in projec page:
>>>>
>>>>  
>>>> https://software.opensuse.org/download.html?project=graphics:darktable&package=darktable
>>>>  
>>>> <https://software.opensuse.org/download.html?project=graphics:darktable&package=darktable>
>>>>
>>>>
>>>>
>>>>  currently fails to install on Ubuntu 21-10 because of exiv2
>>>>  lower than
>>>>  2-27.5. Currently Ubuntu doesn't integrated new exiv2 and it
>>>>  will
>>>>  almost certainly not be integrated until next release.
>>>>
>>>>
>>>>  For what it's worth I've opened a bug report to request exiv2
>>>>  0.27.5 for
>>>>  Ubuntu 22.04.
>>>>  https://bugs.launchpad.net/debian/+source/exiv2/+bug/1959508
>>>>  <https://bugs.launchpad.net/debian/+source/exiv2/+bug/1959508>
>>>>  Doesn't solve your immediate problem though :-/.
>>>>
>>>>  While I'm here, if anyone wants to build darktable 3.8 from source
>>>>  against libexiv2 that's installed in /usr/local _and_ you also
>>>>  have an
>>>>  older libexiv2 installed by a system package, you can d

Re: [darktable-dev] The perspective correction module is not working correctly

[Mica Semrick]

If you think you have a bug, please open an issue on github. Be as detailed as 
possible.

On February 16, 2022 1:07:00 PM PST, Lorenzo Fontanella 
 wrote:
>Yes, I have always used it set to "as original".
>
>In fact, with the same parameters and the same settings, the perspective
>correction tool, in DT >3.8 worked perfectly, even in the most complicated
>situations, now it no longer works as it should.
>
>Lorenzo Fontanella
>
>Il mer 16 feb 2022, 21:49 Martin Straeten  ha
>scritto:
>
>> there’s a parameter ‚aspect adjust‘ you can use to control the behaviour
>>
>> Am 16.02.2022 um 21:41 schrieb Lorenzo Fontanella <
>> fontanellalore...@gmail.com>:
>>
>> 
>> Good morning,
>> I would like to point out that the perspective correction module, in the
>> automatic version, does not seem to work correctly.
>>
>> In previous versions of DT >3.8, the module worked, but now it corrects
>> the perspective but stretches it.
>>
>> Lorenzo Fontanella
>>
>> ___
>> 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] Why is the next version 4.0

[Mica Semrick]

I don't think there is a policy. In the chat room, the question was posed, "is 
the next release 3.10 or 4.0" and 4.0 sounded cool.

There are a bunch of 4.0 worhty features too.

On February 17, 2022 12:08:46 AM PST, Mikko Rasa  wrote:
>I don't know of Darktable's specific policy with version numbers, but in 
>the general case version numbers should not be treated as decimal 
>numbers, but rather as integer sequences.  For example the latest Linux 
>kernel release is 5.16.10, and it's a later version than 5.9.14, because 
>5 == 5 and then 16 > 9.
>
>I have seen some software using the decimal number approach, but those 
>usually have only one dot in the version number.  Darktable already has 
>precedent of more than one dot, like 3.8.1.
>
>Mikko
>
>On 17.2.2022 1.33, Matt Maguire wrote:
>> It’s basic maths — you want version numbers to be strictly monotonously 
>> increasing:
>> 3.10 = 3.1 < 3.8 < 4.0
>> 
>> -
>> MATTHEW MAGUIRE
>> 
>> M.Teach Candidate
>> 
>> 
>> 
>> Sydney School of Education and Social Work
>> 
>> Faculty of Arts and Social Sciences
>> 
>> The University of Sydney
>> 
>> 
>> 
>> Tel: +61 457 750 214
>> 
>> Email: mmag5...@uni.sydney.edu.au
>> 
>> 
>> From: Solarer 
>> Sent: Thursday, February 17, 2022 10:12:28 AM
>> To: darktable-dev@lists.darktable.org 
>> Subject: [darktable-dev] Why is the next version 4.0
>> 
>> Was just asking myself why the next version of darktable is 4.0 and not 3.10?
>> Will there be a major change to the software or do we just prefer shorter 
>> numbers?
>> Best regards, Jan
>> 
>> ___ 
>> 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] - image duplicate BUG(?!?)

[Mica Semrick]

I'd start by updating to the latest stable version, 3.8.1 and seeing if you can 
reproduce the issue. I don't think anyone wants to support 3.4.1.

-m

On May 5, 2022 9:46:22 AM PDT, Zener  wrote:
>Hi everybody!
>
>When I create a duplicate of a selected image in lighttable and then modify it 
>in darkroom making a crop size, then in lighttable I can see two different 
>images (the original one and the duplicate cropped one) correctly.
>
>But... when I export them I find stored two identical images jpeg (so the 
>duplicate image whitout cropping like the original one).
>
>Is that a bug?
>
>How to get exported two image with different elaboration (e.g. cropping)?
>
>I'm using ver. 3.4.1
>
>Thanks.
>
>___
>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] script_manager.lua on ver.3.8 [Re: [darktable-dev] - image duplicate BUG(?!?)]

[Mica Semrick]

You'll need to provide some details about how you installed, what the output is 
starting from the CLI with -d lua, etc etc

Help us help you.

On May 5, 2022 11:12:25 AM PDT, Zener  wrote:
>I've updated to ver.3.8 but now script_manager doesn't start!!
>
>I run on Linux Debian 11.
>
>Help me, please....
>
>Il 05/05/22 19:12, Mica Semrick ha scritto:
>> I'd start by updating to the latest stable version, 3.8.1 and seeing if you 
>> can reproduce the issue. I don't think anyone wants to support 3.4.1.
>> 
>> -m
>> 
>> On May 5, 2022 9:46:22 AM PDT, Zener  wrote:
>> 
>> Hi everybody!
>> 
>> When I create a duplicate of a selected image in lighttable and then 
>> modify it in darkroom making a crop size, then in lighttable I can see two 
>> different images (the original one and the duplicate cropped one) correctly.
>> 
>> But... when I export them I find stored two identical images jpeg (so 
>> the duplicate image whitout cropping like the original one).
>> 
>> Is that a bug?
>> 
>> How to get exported two image with different elaboration (e.g. cropping)?
>> 
>> I'm using ver. 3.4.1
>> 
>> Thanks.
>> 
>> darktable developer mailing list
>> to unsubscribe send a mail 
>> todarktable-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] script_manager.lua on ver.3.8 [Re: [darktable-dev] - image duplicate BUG(?!?)]

[Mica Semrick]

Lua must be 5.4 for this version of darktable.



On May 5, 2022 11:40:38 AM PDT, Zener  wrote:
>|apt install darktable/bullseye-backports reboot |darktable -d lua
>||
>
>Il 05/05/22 20:36, Mica Semrick ha scritto:
>> You'll need to provide some details about how you installed, what the output 
>> is starting from the CLI with -d lua, etc etc
>> 
>> Help us help you.
>> 
>> On May 5, 2022 11:12:25 AM PDT, Zener  wrote:
>> 
>> I've updated to ver.3.8 but now script_manager doesn't start!!
>> 
>> I run on Linux Debian 11.
>> 
>> Help me, please
>> 
>> Il 05/05/22 19:12, Mica Semrick ha scritto:
>>> I'd start by updating to the latest stable version, 3.8.1 and
>>> seeing if you can reproduce the issue. I don't think anyone wants
>>> to support 3.4.1.
>>> 
>>> -m
>>> 
>>> On May 5, 2022 9:46:22 AM PDT, Zener  wrote:
>>> 
>>> Hi everybody!
>>> 
>>> When I create a duplicate of a selected image in lighttable and 
>>> then modify it in darkroom making a crop size, then in lighttable I can see 
>>> two different images (the original one and the duplicate cropped one) 
>>> correctly.
>>> 
>>> But... when I export them I find stored two identical images jpeg 
>>> (so the duplicate image whitout cropping like the original one).
>>> 
>>> Is that a bug?
>>> 
>>> How to get exported two image with different elaboration (e.g. 
>>> cropping)?
>>> 
>>> I'm using ver. 3.4.1
>>> 
>>> Thanks.
>>> 
>>> 
>>> darktable developer mailing list
>>> to unsubscribe send a mail 
>>> todarktable-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
>___
>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] Missing OBS package

[Mica Semrick]

Hi Bob,

The darktable project does not provide binaries for *nix platforms. The 
OBS repo is maintained by the community, mostly by darix and asn. I know 
asn is busy, and I spoke with darix about it the other day. If either 
has the time and energy to provide a fix, I'm sure they will. Otherwise 
the community should step in and provide a fix.


-m

On 5/31/22 18:50, Bob Tregilus wrote:

Hi -

I've notice the following for a few weeks now.

https://software.opensuse.org/download.html?project=graphics:darktable&package=darktable

Ubuntu > Add repository and install manually >

The only packages (and binaries) available are for:
For xUbuntu 22.04
For xUbuntu 21.10
For xUbuntu 21.04

The package and binary for 20.04, an LTS release (supported until
April 2025), is missing.

I run Linux Mint 20.3, Mint's latest release, which is based on Ubuntu 20.04.

Is this something y'all can handle, or should I ping opensuse about
the problem, or if I need to reinstall do I need to install from
source?

Thanks!


___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Start translating the user manual f!

[Mica Semrick]

Hi,

I've updated our weblate instance with the last changes and now would be 
an excellent time to begin translating!


https://weblate.pixls.us/projects/darktable/dtdocs/ is the weblate project.

https://darktable-org.github.io/dtdocs/en/special-topics/translating/ is 
the docs for translating the docs


Thanks!

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] OBS packages for xUbuntu

[Mica Semrick]

This answer is a bit rude and doesn't answer the original query.

There is an unmet dependency in Ubuntu 20.04 and the latest release can no 
longer be built. See 
https://discuss.pixls.us/t/what-happened-with-the-obs-builds/33588/2?u=darix 
for more information.

You can always try the flatpak.

-m

On January 4, 2023 1:58:37 AM PST, Matthias Andree  
wrote:
>Am 04.01.23 um 04:51 schrieb Bob Tregilus:
>> Hi -
>> 
>> I'm not sure who I should alert to this issue, someone on this dev
>> list or should I write to OBS support?
>> 
>> On the openSUSE contributors OBS they list the following four 4.2.0
>> darktable builds for Unbuntu based distros (I added the support
>> information):
>> 
>> xUbuntu 22.10 is supported to 2023-07.
>> 
>> xUbuntu 22.04 (LTS) is supported to 2027-04-21.
>> 
>> xUbuntu 21.10 support *ended* 2022-07-14.
>> 
>> xUbuntu 21.04 support *ended* 2022-01-20.
>> 
>> But now missing is a 4.2.0 build for the older:
>> 
>> xUbuntu 20.04 (LTS) which is supported to 2025-04-23.
>
>Who cares?
>
>The proper answer is: Do not use older Ubuntu distros on desktops,
>Ubuntu are only maintaining a very small subset of packages in the LTS
>context (and understandably so because it's redundant effort), and
>please do not ask to encourage people shooting themselves in the foot
>with that by providing new packages on older distros. Instead, teach
>desktop users to stay updated.
>
>> $ ubuntu-security-status
>> 989 packages installed, of which:
>> 859 receive package updates with LTS until 4/2025
>
>Meaning 130 packages without any security updates (this is xubuntu 20.04
>that I use as mostly-headless build server for mail-related software),
>and on typical desktop installs, it's usually much worse. Ubuntu's "LTS"
>tag, for desktops, is window dressing.
>
>Only main/restricted aka base packages receive "support".
>https://ubuntu.com/about/release-cycle but not many of community
>packages which I found make up considerable parts of desktop installs.
>
>___
>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] OBS packages for xUbuntu

[Mica Semrick]

You're making a lot of assumptions here. Seems like you have some deeper issue 
than someone asking a simple question about support. Maybe a break from the 
computer is in order.

Happy new year
-m

On January 4, 2023 7:33:59 AM PST, Matthias Andree  
wrote:
>Am 04.01.23 um 15:58 schrieb Mica Semrick:
>> This answer is a bit rude and doesn't answer the original query.
>
>It may be rude if you consider "who cares" rude, and prevents people
>from wasting their time while pointing out the actual issue, which is
>"old distro" which is too old to build darktable 4.2.
>
>> There is an unmet dependency in Ubuntu 20.04 and the latest release
>> can no longer be built. See
>> https://discuss.pixls.us/t/what-happened-with-the-obs-builds/33588/2?u=darix 
>> for
>> more information.
>
>Thanks for mass-confirming what I was writing.
>
>And scared users in that thread posted in November 2022, 7 months after
>release, that they still considered Ubuntu "new", when 22.04.1 was out
>and from-LTS-to-next-LTS upgrades had been enabled. Exactly the kind of
>support open-source maintainers want to be distracted with. I haven't
>even looked whether the OBS people are the same as the darktable people,
>but you'd think it best to move things forward rather than tying them up
>in the past.
>
>The thing is you can't have the cake and eat it, so everyone please stop
>pretending they could.
>
>Ubuntu 20.04 (code-named focal fossa) shipped darktable 3.0, and
>darktable being in the "universe" community-unmaintained package set...
>being stuck with older darktable is a choice that people made by NOT
>upgrading their Ubuntu LTS in the past three months.
>https://packages.ubuntu.com/search?suite=focal&searchon=names&keywords=darktable
>
>And it's also either you choose a Ubuntu LTS distro and live with
>whatever unmaintained ("universe") package came with it, and be stuck
>with it, or you pick something that installs an app and all its distro
>deps redundantly in a distro (snap or flatpack, if available) with all
>the drawbacks of its isolation and bulk, or you need to move to a distro
>that is up to speed if your interest is "new software" and integrates
>such quickly. Rolling or frequent releases and distros exist, but that's
>not Ubuntu LTS, and possibly no Debian-based distro at all.
>
>Having said that, Fedora 37 or FreeBSD 13.1 built darktable 4.2 nicely
>for me.
>
>I wonder why all the world can expect everyone to maintain every new
>package for their museum piece of desktop distro install and NOT be
>considered rude. Expecting someone to maintain software or packages
>thereof for older distros, on a voluntary basis, free of charge, is what
>I consider egoistic and rude. It is an enormous waste of resources.
>
>
>___
>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] OBS packages for xUbuntu

[Mica Semrick]

Can you not just be polite though? Do we want the default reply here to be 
"gruff with loosely associated facts?"

Essentially the question of "what happened to xxx package" was met with a multi 
paragraph rant about LTS and Ubuntu and whatever. It didn't provide the answer 
but instead veered off on it's own direction.

Not a great way to start the new year, if I'm honest.

-m

On January 4, 2023 9:57:39 AM PST, "ja...@activimetrics.com" 
 wrote:
>For what its worth, I read Matthias Andree's responses as perfectly
>reasonable.  Yes the words were not exceedingly polite, but the
>gruffness was backed with explanation.  I certainly did not read any
>ad hominem attacks.
>
>I was always of the opinion that if you stick with an LTS version of a
>distro, you are stuck with *exactly* what the distro decides is worthy
>of LTS support.
>
>Especially in this new world of flatpaks.
>
>For the record, I run slackware since forever, so building code from
>source as a package is something I have to do now and then.  I would
>never dream of asking the darktable devs to maintain a slackware
>SlackBuild, let alone an installable package.
>
>And when Mr. Volkerding and the inner slackware cabal decide that it
>is time to release a new version, one upgrades shortly thereafter.
>
>Regards, and back to lurking,
>
>James
>
>On Wed, Jan 04, 2023 at 07:43:10AM -0800, Mica Semrick wrote:
>> You're making a lot of assumptions here. Seems like you have some deeper 
>> issue than someone asking a simple question about support. Maybe a break 
>> from the computer is in order.
>>
>> Happy new year
>> -m
>>
>> On January 4, 2023 7:33:59 AM PST, Matthias Andree  
>> wrote:
>> >Am 04.01.23 um 15:58 schrieb Mica Semrick:
>> >> This answer is a bit rude and doesn't answer the original query.
>> >
>> >It may be rude if you consider "who cares" rude, and prevents people
>> >from wasting their time while pointing out the actual issue, which is
>> >"old distro" which is too old to build darktable 4.2.
>> >
>> >> There is an unmet dependency in Ubuntu 20.04 and the latest release
>> >> can no longer be built. See
>> >> https://discuss.pixls.us/t/what-happened-with-the-obs-builds/33588/2?u=darix
>> >>  for
>> >> more information.
>> >
>> >Thanks for mass-confirming what I was writing.
>> >
>> >And scared users in that thread posted in November 2022, 7 months after
>> >release, that they still considered Ubuntu "new", when 22.04.1 was out
>> >and from-LTS-to-next-LTS upgrades had been enabled. Exactly the kind of
>> >support open-source maintainers want to be distracted with. I haven't
>> >even looked whether the OBS people are the same as the darktable people,
>> >but you'd think it best to move things forward rather than tying them up
>> >in the past.
>> >
>> >The thing is you can't have the cake and eat it, so everyone please stop
>> >pretending they could.
>> >
>> >Ubuntu 20.04 (code-named focal fossa) shipped darktable 3.0, and
>> >darktable being in the "universe" community-unmaintained package set...
>> >being stuck with older darktable is a choice that people made by NOT
>> >upgrading their Ubuntu LTS in the past three months.
>> >https://packages.ubuntu.com/search?suite=focal&searchon=names&keywords=darktable
>> >
>> >And it's also either you choose a Ubuntu LTS distro and live with
>> >whatever unmaintained ("universe") package came with it, and be stuck
>> >with it, or you pick something that installs an app and all its distro
>> >deps redundantly in a distro (snap or flatpack, if available) with all
>> >the drawbacks of its isolation and bulk, or you need to move to a distro
>> >that is up to speed if your interest is "new software" and integrates
>> >such quickly. Rolling or frequent releases and distros exist, but that's
>> >not Ubuntu LTS, and possibly no Debian-based distro at all.
>> >
>> >Having said that, Fedora 37 or FreeBSD 13.1 built darktable 4.2 nicely
>> >for me.
>> >
>> >I wonder why all the world can expect everyone to maintain every new
>> >package for their museum piece of desktop distro install and NOT be
>> >considered rude. Expecting someone to maintain software or packages
>> >thereof for older distros, on a voluntary basis, free of cha

Re: [darktable-dev] OBS packages for xUbuntu

[Mica Semrick]

Hi Bob,

You can get displaycal in a flatpak or there is a python3 port of it 
that you can install using pip.


-m

On 1/4/23 17:38, Bob Tregilus wrote:

Hi -

My apologies for causing a kerfuffle.

I am not a dev, just a user, albeit from SuSE 6.0.

I did not understand why there were packages for newer unsupported
xUbuntu versions and not for an older supported version. But now I
know: dependencies.

I always do fresh installs. I realize there are upgrade paths these
days, but I'm old school, I guess.

Therefore, with Mint, I wait for the version x.3 LTS before doing a
fresh install.

I'll just go ahead and install 21.1.

My biggest worry, however, is dispcalGUI being a dead project. I hope
it still works with xUbuntu 22.04.1? Guess I will find out. I need a
calibrated monitor. It will be a lot of work to figure out how to
calibrate from the command line with Argyll CMS.

Thanks for enlightening an old dopey user.

Bob



On 1/4/23, Mica Semrick  wrote:

Can you not just be polite though? Do we want the default reply here to be
"gruff with loosely associated facts?"

Essentially the question of "what happened to xxx package" was met with a
multi paragraph rant about LTS and Ubuntu and whatever. It didn't provide
the answer but instead veered off on it's own direction.

Not a great way to start the new year, if I'm honest.

-m

On January 4, 2023 9:57:39 AM PST, "ja...@activimetrics.com"
 wrote:

For what its worth, I read Matthias Andree's responses as perfectly
reasonable.  Yes the words were not exceedingly polite, but the
gruffness was backed with explanation.  I certainly did not read any
ad hominem attacks.

I was always of the opinion that if you stick with an LTS version of a
distro, you are stuck with *exactly* what the distro decides is worthy
of LTS support.

Especially in this new world of flatpaks.

For the record, I run slackware since forever, so building code from
source as a package is something I have to do now and then.  I would
never dream of asking the darktable devs to maintain a slackware
SlackBuild, let alone an installable package.

And when Mr. Volkerding and the inner slackware cabal decide that it
is time to release a new version, one upgrades shortly thereafter.

Regards, and back to lurking,

James

On Wed, Jan 04, 2023 at 07:43:10AM -0800, Mica Semrick wrote:

You're making a lot of assumptions here. Seems like you have some deeper
issue than someone asking a simple question about support. Maybe a break
from the computer is in order.

Happy new year
-m

On January 4, 2023 7:33:59 AM PST, Matthias Andree
 wrote:

Am 04.01.23 um 15:58 schrieb Mica Semrick:

This answer is a bit rude and doesn't answer the original query.

It may be rude if you consider "who cares" rude, and prevents people

>from wasting their time while pointing out the actual issue, which is

"old distro" which is too old to build darktable 4.2.


There is an unmet dependency in Ubuntu 20.04 and the latest release
can no longer be built. See
https://discuss.pixls.us/t/what-happened-with-the-obs-builds/33588/2?u=darix for
more information.

Thanks for mass-confirming what I was writing.

And scared users in that thread posted in November 2022, 7 months after
release, that they still considered Ubuntu "new", when 22.04.1 was out
and from-LTS-to-next-LTS upgrades had been enabled. Exactly the kind of
support open-source maintainers want to be distracted with. I haven't
even looked whether the OBS people are the same as the darktable
people,
but you'd think it best to move things forward rather than tying them
up
in the past.

The thing is you can't have the cake and eat it, so everyone please
stop
pretending they could.

Ubuntu 20.04 (code-named focal fossa) shipped darktable 3.0, and
darktable being in the "universe" community-unmaintained package set...
being stuck with older darktable is a choice that people made by NOT
upgrading their Ubuntu LTS in the past three months.
https://packages.ubuntu.com/search?suite=focal&searchon=names&keywords=darktable

And it's also either you choose a Ubuntu LTS distro and live with
whatever unmaintained ("universe") package came with it, and be stuck
with it, or you pick something that installs an app and all its distro
deps redundantly in a distro (snap or flatpack, if available) with all
the drawbacks of its isolation and bulk, or you need to move to a
distro
that is up to speed if your interest is "new software" and integrates
such quickly. Rolling or frequent releases and distros exist, but
that's
not Ubuntu LTS, and possibly no Debian-based distro at all.

Having said that, Fedora 37 or FreeBSD 13.1 built darktable 4.2 nicely
for me.

I wonder why all the world can expect everyone to maintain every new
package for their museum piece of desktop distro install and NOT be
considered rude. Expecting some

Re: [darktable-dev] OBS packages for xUbuntu

[Mica Semrick]

On 1/4/23 18:10, Matthias Andree wrote:

You are considering my earlier messages rude and now you are insinuating
I had a "deeper issue"?


Your 12 paragraph response that didn't answer the question does indeed 
point to you having a bad day, at the very least. Taking that out on 
other people isn't nice.



Have I just broke your delusions of Ubuntu LTS or what's up?


No and I don't use ubuntu anyway.


The solution is "you want to run up-to-date software, you get to upgrade
your distro first".­


Except that is not at all true. Besides OBS, which does build for quite 
a few "out of date" distros, there are also flatpaks and snaps, which 
will run a whole bunch of places where an otherwise up-to-date darktable 
package isn't available.



___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Updated manual on website?

[Mica Semrick]

Weblate will be updated when the English 4.2 manual is complete. Ant help with 
updating the English is appreciated.

-m

On January 24, 2023 2:34:14 AM PST, Marcus Gama  wrote:
>The manual is not yet available for translation on the weblate. Any
>predictions on when it will be available?
>
>
>Em ter., 24 de jan. de 2023 às 07:03, Bruce Williams 
>escreveu:
>
>> Hi devs,
>> I just noticed that the current version of the manual on darktable.org is
>> still for v4.0.
>> Does anyone have a link to the 4.2 version, please?
>>
>> Cheers,
>> Bruce Williams
>> --
>> Owner, Creator and co-host
>>
>> Shutters Inc podcast , the world's
>> best-loved photography podcast
>> Creator
>>
>> Understanding darktable
>>  on youtube
>> Other places to find me
>>
>> e-mail  | Instagram
>>  |
>> Twitter  | LinkedIn
>>  | Facebook
>>  | Soundcloud
>>  | Quora
>> 
>>
>> ___
>> 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] HELP: Release Notes entries for your PR

[Mica Semrick]

It'd be an extra bonus that if your PR changes functionality that is documented 
that you provide some explanation as to what changed and how it functions.

Having to "just figure it out" to write the docs isn't very much fun.

-m

On February 25, 2023 10:43:36 AM PST, Pascal Obry  wrote:
>
>Hi devs,
>
>If you have proposed a PR to be merged on 4.4 then I need your help.
>
>Please check this link listing all PR merged for 4.4:
>
>https://github.com/darktable-org/darktable/pulls?q=is%3Apr+is%3Aclosed+label%3A%22release+notes%3A+pending%22+milestone%3A4.4
>
>If you have one of your PR can you add a comment at the end with a
>paragraph (or two or more) that I can add into the RELEASE_NOTES?
>
>For all new PR I'll now asked for an entry for the RELEASE_NOTES and
>I'll try to keep the RELEASE_NOTES as up to date as possible to help
>our daily testers to check the new stuff.
>
>Thanks in advance,
>
>-- 
>  Pascal Obry /  Magny Les Hameaux (78)
>
>  The best way to travel is by means of imagination
>
>  http://photos.obry.net
>
>  gpg --keyserver keys.gnupg.net --recv-key F949BD3B
>
>___
>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] Plan for darktable 4.4

[Mica Semrick]

Thanks Pascal!

As per ususal, we could really use help with the docs.

If you've ever said "I can't code, how can I help the project?" This your 
chance!

-m

On May 16, 2023 10:39:34 AM PDT, pas...@obry.net wrote:
>
>Hello devs!
>
>As you know now the next release (4.4) will be on June 21st. 
>
>We have entered feature freeze yesterday.
>
>The next step is string freeze end-May, so time is now to fix the
>remaining issues.
>
>A list can be found there:
>
>https://github.com/darktable-org/darktable/issues?q=is%3Aopen+is%3Aissue+label%3A%22bug%3A+pending%22+milestone%3A4.4
>
>As a reminder the steps are:
>
>    string freeze : end-May
>    no more strings changed in the code
>    the translators can start the final translation of all strings
>
>    full freeze : mid-June
>    no more changes to the code or translations
>    the branch for the release is created
>    incomplete translations are removed
>    a tarball is created
>    the packagers can start building the binaries
>    (Linux, Windows, MacOS)
>
>    final release : June 21st (summer release)
>
>The description for release cycle is there:
>
>https://github.com/darktable-org/darktable/wiki/Releases-cycle
>
>Have a nice day,
>
>___
>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] Photos failing to export

[Mica Semrick]

Howdy,

Sounds like you're running out of memory. What are your system specs like?

-m

On May 25, 2023 6:45:50 PM PDT, Brendan Markovich  
wrote:
>G'day all,
>
>I'm hoping someone can help me with a weird issue I'm having when I attempt
>to export my photos from the lighttable. I was having issues with the color
>calibration module and trying to adjust the white balance, so in my
>settings I changed auto-apply chromatic adaptation defaults to legacy and
>left the pixel workflow on scene-referred. I've then updated my style to
>remove the color calibration module, reapplied with overwrite to my images
>and then made any necessary adjustments. When I go to export my photos in
>bulk, darktable doesn't produce any output but I can still edit photos in
>the darkroom. If I restart my PC I can export a single photo but after that
>the exports fail even for a single photo and I have to reboot again. The
>strange thing is, I swear I could export 3 single photos last week before
>it stopped working.
>
>I've reset my settings by renaming the settings file, created and checked
>the log file and I can't see anything obvious in there that needs fixing.
>Darktable never crashes so I can't give you an error message. Would you
>like me to generate another log file for you and send it through? Is there
>any other info that you need?
>
>Thanks,
>
>Brendan
>
>___
>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] Documentation

[Mica Semrick]

Hi, we are having some issues with the punishing automation. I've been working 
on it but haven't found the solution yet.

-m

On June 19, 2023 1:38:20 PM PDT, Heiko Bauke  wrote:
>Hi,
>
>I am wondering what happened to the dt manuals.  The manuals for dt 3.8, 4.0, 
>4.2 on https://www.darktable.org/resources/ are empty.
>
>
>Regards,
>
>Heiko
>
>
>-- 
>-- Number Crunch Blog @ https://www.numbercrunch.de
>--  Cluster Computing @ https://www.clustercomputing.de
>--  Social Networking @ https://www.researchgate.net/profile/Heiko_Bauke
>___
>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] Documentation

[Mica Semrick]

Howdy,

I believe the docs are fixed now.


On June 20, 2023 12:35:42 PM PDT, Heiko Bauke  wrote:
>Hi,
>
>Am 19.06.23 um 23:13 schrieb Mica Semrick:
>> Hi, we are having some issues with the punishing automation. I've been 
>> working on it but haven't found the solution yet.
>
>I already suspected that it might be an automation issue. Good to know that 
>you are aware of this and already working on it.
>
>
>
>Regards,
>
>Heiko
>
>
>-- 
>-- Number Crunch Blog @ https://www.numbercrunch.de
>--  Cluster Computing @ https://www.clustercomputing.de
>--  Social Networking @ https://www.researchgate.net/profile/Heiko_Bauke
>
>___
>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] proposal about AI

[Mica Semrick]

If you're throwing all of AI/ML out the window, I think you're missing the 
point. 

There are already lua plugins that let you use AI/ML, like photils and 
face_recognize. The uses of AI can be helpful and reduce the amount of handwork 
needed to maintain your photo library.

The problem for darktable is that a lot of the new hotness AI/ML is (1) too 
slow, (2) requires massive compute infrastructure, (3) is mostly python so it 
won't fit well inside darktable, and (4) the major models do not use a free 
license.

Photography is a technological process and always has been. Embrace the 
technology and use it where it makes sense. 

If you think shooting film somehow excludes you from technology, you're fooling 
yourself.

-m

On September 22, 2023 7:42:39 AM PDT, "Paolo Niccolò Giubelli" 
 wrote:
>The problem is that AI is the natural outcome of digital photography. Until
>now, digital photography was like film photography by other means: light
>flowing into the lens, hitting a sensor instead of film emulsion,
>postprocessing... and voilà. Digital always evolves to convergence:
>computation comes into play and photography is becoming something different
>(this is why I started practicing film photography 2 years ago). I agree
>with you AI in photography is bad, for many reasons, but this is not about
>photography anymore.
>Paolo
>
>
>Il giorno ven 22 set 2023 alle ore 15:03 Bernhard <
>darkta...@intervalsignals.org> ha scritto:
>
>> I'm not sure how to differentiate AI and ML (machine learning) and and
>> according to the manual the WB mechanisms in color calibration are using ML
>> ... so is the claim intended here realy 100% true?
>>
>> https://docs.darktable.org/usermanual/4.2/en/module-reference/processing-modules/color-calibration/#cat-tab-workflow
>>
>> Graham White schrieb am 22.09.23 um 13:44:
>> > I'm not too happy with supporting this, but I'm also not happy about the
>> > gung ho approach to AI which seems
>> > so common these days. I don't think that what people now call AI could be
>> > called AI worthy of the name, but I still think it's possibly useful,
>> maybe
>> > (though I think mostly it's either catastrophically boring or not
>> actually
>> > artificial intelligence). But what one might call it
>> > (algorithmic image manipulation, for example, or information theoretic
>> > image manipulation) might be interesting and/or useful. Just don't call
>> it
>> > AI.
>> >
>> > On Fri, Sep 22, 2023 at 11:47 AM Jason Polak  wrote:
>> >
>> >> Dear darktable devs,
>> >>
>> >> I am not sure how well this will be received, but I have a proposal.
>> >> Probably everyone knows that AI and particularly generative AI is taking
>> >> the world by storm. Adobe and many other Raw developers embed it into
>> their
>> >> products.
>> >>
>> >> One of the great things about darktable is that it does not offer any AI
>> >> tools. This is amazing because people can use it as a product without
>> >> supporting AI (simply using AI is supporting its development).
>> >>
>> >> I was wondering what the devs thought about this?
>> >>
>> >> My thinking is that AI takes us out of the realm of free-functioning
>> >> creativity by making creative decisions for us. It's a mechanization of
>> >> photography and it ultimately harms it.
>> >>
>> >> So, IF you agree with this, I was wondering if the darktable team would
>> >> like to make a stand with me against AI, by stating that darktable will
>> not
>> >> use AI in the future, or offer any AI tools? I know this email may seem
>> >> rather strange to all of you but I think AI poses a real danger to
>> >> humanity. I am creating a sort of informal coalition of artists and
>> people
>> >> who do not use AI.
>> >>
>> >> I have a YouTube channel and I already put "AI Free" on my YouTube
>> >> channel. I attached an example of the button I created in Inkscape for
>> this
>> >> and I provided an SVG for some ideas. I know this sounds rather radical,
>> >> and I am not trying to force anything on anyone. Everyone has to make
>> their
>> >> own choice about AI.
>> >>
>> >> Again, I know I'm a bit strange but please at least consider this
>> message.
>> >> The  more people that actively advocate against AI, the better. So, IF
>> >> anyone reading this has any qualms about AI and there is some sort of
>> >> consensus, please consider my proposal.
>> >>
>> >> Thanks,
>> >> Jason Polak -- A long time darktable user and person who loves
>> >> photography, "human style"
>> >>
>> ___
>> >> darktable developer mailing list
>> >> to unsubscribe send a mail to
>> >> darktable-dev+unsubscr...@lists.darktable.org
>> >
>> >
>>
>> --
>>
>> regards
>> Bernhard
>>
>> https://www.bilddateien.de
>>
>>
>> ___
>> darktable developer mailing list
>> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.or
>
>

[darktable-dev] Weblate for documentation is up-to-date and ready for 4.6 translation

[Mica Semrick]

Hey everyone,

Chris (mostly) and I were able to get weblate updated and its (mostly) 
ready for 4.6 translations!


Have at it!

Best,

Mica

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Re: mailing list cleanup

[Mica Semrick]

Hi!

On January 8, 2024 4:46:53 PM PST, Germano Massullo 
 wrote:
>Il 20/12/23 23:57, Germano Massullo ha scritto:
>> Hello, everytime I send an email to this mailing list, I get an email from 
>> supp...@alyce.com
>> Perhaps a cleanup of the mailing list participants is needed..
>Hello!?!?
>___
>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] Installation Darktable

[Mica Semrick]

I saw you posted in the pixls.us forums, that is a fine place to get help, just 
be a bit patient.

-m

On February 8, 2024 3:57:42 PM PST, susana gastelumendi 
 wrote:
>Hi.
>I have problems with the installation of DARKTABLE.
>I would like to know which is the correct email to ask about and solve the 
>problem.
>Thank ypu.
>
>Susana Gastelumendi
>
>
>
>___
>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