iptc | Liest IPTC Felder aus PNG und JPG | Addon library

Use Promise.all, this will resolve after all exifr.parse promises have resolved.

This is the general function that you are looking for.

I cannot promise it will work because I don't have that plugin available.

The original function you are referencing assumes that a $user object is being passed to it, but I'm not seeing that in your implementation, so I'm just going to assume the current logged in user, if they exist.

I pulled all of the globals that I could find. There's also a bunch of functions that are from the plugin that I can't guarantee will be loaded/available, but you should at least get an error than.

Rename the function as you need to, obviously.

It seams PIL and crop has some problems with LZW compression. Removing the compression with Photoshop makes the script running like expected.

The likely reason is with the library you are using or the way you use it. There is one obvious hazard: You use multiple threads to work on the same chain and table but you do not use a mutex to protect access to them.

Try something like this:

Your XML elements are bound to the namespace http://iptc.org/std/nar/2006-10-01/, but your XPath is not using any namespace-prefixes, so /newsItem/itemMeta is asking for elements that are bound to no namespace.

You could address them by just the local-name():

Using v-model together with checked doesn't make much sense since v-model sets checked itself. Read the Vue documentation on checkboxes: https://vuejs.org/v2/guide/forms.html#Checkbox-1

Instead of checked you need to use the true-value and false-value attributes, so in your case true-value="active" and depending what you want to use, for example, false-value="" for an empty string, or :false-value="null" for null (notice the : or you'll get a string "null" instead).

Here is an working example: https://jsfiddle.net/kgewf04d/1/

The basic command would be
exiftool -ext png -TagsFromFile %d%f.jpg -Title -XMP:Headline -Subject -Description /path/to/PNGS/

You don't mention the OS, but the long dash may cause problems under Windows as CMD/PS have problems with unicode characters, at least in regards to exiftool. See exiftool FAQ #18 and this StackOverflow answer for workarounds.

The -ext (-extension) option is used to limit processing to PNG files so you don't waste time copying the jpg data back into the jpg.

This command will copy the XMP-dc:Title, XMP-photoshop:Headline, XMP-dc:Description, and XMP-dc:Subject tags (of which the last holds "Keywords") from the jpg file to the png file in the same directory that has the same base name. The Title and Subject tags have a preferred location in the XMP group so the names can be kept simple but since Headline can be in the IPTC IIM/Legacy group as well as XMP, it needs a leading group name to make sure it's copied to the correct location.

To expand this command to add additional IPTC Core/Ext tags, look for the appropriate tag name on the exiftool XMP tags page, prefix the tag name with -XMP:, and add it to the command someplace after -TagsFromFile %d%f.jpg. The addition of -XMP: may not be necessary for many tags, as not all XMP tags have tags with the same name in other groups.

There is the possibility, depending upon the app you are using to look at the data, that some of the data may show up as IPTC Core/Ext, but may be located in the IPTC IIM/Legacy or EXIF groups. This is because many apps will display data collected from the corresponding tags in other groups. The above command will not copy data from those other groups to the corresponding IPTC Core/Ext tags, as that is a more complex operation.

This command creates backup files. Add -overwrite_original to suppress the creation of backup files. Add -r to recurse into subdirectories.

One final detail to take note of is that metadata support in PNG files is very limited in most apps. While exiftool will copy this data correctly, your app of choice may not display it in a PNG. Windows, for example, will not show any of the above data in the Properties->Details window.

Firstly, the message Errors were reported during stylesheet compilation means what it says. There's a detailed error message somewhere, and you're not seeing it, because it's been logged or reported to some destination that you're not seeing. You need to look at how you are invoking the stylesheet compilation (via API or command line) and where you are directing the error messages.

Pasting the stylesheet into Oxygen immediately reveals the error "Namespace prefix 'ns1' has not been declared". But your comments above say that the code you posted isn't your real code (which makes me wonder why you bothered posting it), and if you don't post your real code then we can't tell you what's wrong with it.

Once you get your stylesheet to compile, there are a few errors in its logic:

• The variable var1_map_of_newsMessage will contain a single string because there is only one body element. I think you probably wanted a string for each paragraph. Or perhaps you wanted the paragraph elements themselves, since you say you want to retain the markup.

• You can replace the predicate [(fn:position() = xs:integer('1'))] with the predicate [1].

• The variable declaration of bodyContent is creating an unnecessary copy of a large amount of data. To avoid the copy, either (a) declare the variable type as="node()*", or (b) use an xsl:variable element with a select attribute and no child elements.

Using exiftool, you could use this command

For Windows CMD
exiftool "-Title<${Title}..." /path/to/files/

For other shells
exiftool '-Title<${Title}...' /path/to/files/

This command creates backup files. Add -overwrite_original to suppress the creation of backup files. Add -r to recurse into subdirectories.