Variable substitution documentation not up to date

[UweOhse]

The documentation mentions these substitutions:

$(TITLE)                   title from metadata
$(DESCRIPTION)             description from metadata
$(CREATOR)                 creator from metadata
$(PUBLISHER)               publisher from metadata
$(RIGHTS)                  rights from metadata

They got removed in revision 9892165f44f09187bd10cd745a5fb85907b9aa2d ("handle metadata in variables", 2024-12-11).
Since then you have to access the same information like this:

$(Xmp.dc.title)                   title from metadata
$(Xmp.dc.description)             description from metadata
$(Xmp.dc.creator)                 creator from metadata
$(Xmp.dc.publisher)               publisher from metadata
$(Xmp.dc.rights)                  rights from metadata

Please update the documentation so that the next poor soul doesn't waste hours wondering which part of their toolchain broke.

Regards, Uwe

[paperdigits]

Can you please make an attempt to update it yourself and submit a pull request?

…

On August 28, 2025 10:25:57 AM PDT, Uwe Ohse ***@***.***> wrote: UweOhse created an issue (darktable-org/dtdocs#777) The documentation mentions these substitutions: ``` $(TITLE) title from metadata $(DESCRIPTION) description from metadata $(CREATOR) creator from metadata $(PUBLISHER) publisher from metadata $(RIGHTS) rights from metadata ``` They got removed in revision 9892165f44f09187bd10cd745a5fb85907b9aa2d ("handle metadata in variables", 2024-12-11). Since then you have to access the same information like this: ``` $(Xmp.dc.title) title from metadata $(Xmp.dc.description) description from metadata $(Xmp.dc.creator) creator from metadata $(Xmp.dc.publisher) publisher from metadata $(Xmp.dc.rights) rights from metadata ``` Please update the documentation so that the next poor soul doesn't waste hours wondering which part of their toolchain broke. Regards, Uwe -- Reply to this email directly or view it on GitHub: #777 You are receiving this because you are subscribed to this thread. Message ID: ***@***.***>

[elstoc]

This is already fixed in #775