On mardi 14 mars 2023 18:29:23 CET Frank J. wrote:
> Hi,
> I want to use the “description” metadata from darktable [1] as caption
> in WordPress.
> In german language there are some characters which are not in ASCII but
> in Unicode/UTF-8.
> Umlaute: ä ö ü ß  ->  HTML: ä ö ü ß
> 
> When a raw-picture is exported as JPG from darktable, then the
> “description” metadata is embedded into the exif-data:
> 
> - description whithout “umlaute” is written to EXIF ImageDescription
> field (ascii).
> 
> - description WHITH “umlaute” is written to EXIF UserComment field
> (unicode).
> 
> I try the Plugins "Exif Caption" und "Exif Details" for import into
> wordpress.
> 
> As written in [2] the UserComment should be imported to wordpress:
> 
>      [“caption”]
>      (string) Set to a non-empty value of one of the following fields:
>      …
>      EXIF UserComment field if [“title”] is unset AND
> EXIF:ImageDescription is less than 80 characters
> 
> But for pictures with “umlaute” the caption in wordpress stay empty. The
> description is lost.
Iirc, EXIF can only store ASCII characters, so umlauts (and things like éèà) 
are not allowed there. That may make the library used for reading the data 
discard the text as invalid.

 But that concerns the "real" EXIF metadata, not the equivalent fields in 
XMP(*). IPTC also allows non-ASCII. So if at all possible, you may be better 
off using XMP or IPTC metadata.

Remco

(*: There are three "types" of image metadata: EXIF, IPTC and XMP, which 
differ in the way they are stored in the file, the character sets used, and 
the maximum field lengths. The fields in the EXIF and IPTC sections can also 
be stored as XMP fields, but that doesn't mean they will be read when you ask 
for an EXIF or IPTC field). 


____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

Reply via email to