Progress® Telerik® UI for WPF Feedback Portal
Back to Feed
Request a Feature Report a Bug
Declined
Last Updated: 22 Feb 2017 12:37 by ADMIN
Mi
Created on: 15 Oct 2014 08:04
Category: UI for WPF
Type: Feature Request
4
Moved to TDP: Support for metadata streams (XMP metadata)
To bring RadPDFProcessing to the next level you should support XMP metadata. This would extremely help to use pdf files from RadPDFProcessing in digital workflows.

Reference: http://www.adobe.com/devnet/xmp.html
This item is migrated to the Telerik Document Processing portal: 
http://feedback.telerik.com/Project/184/Feedback/Details/190024 
Please use the new item for commenting, voting and subscribing instead of this one.
8 comments
ADMIN
Boby
Posted on: 03 May 2016 10:52 
@mhaasl: This item is migrated to the Telerik Document Processing portal: 
http://feedback.telerik.com/Project/184/Feedback/Details/190024 
Please use the new item for commenting, voting and subscribing instead of this one.
Mi
Posted on: 03 May 2016 10:48 
What does "Moved to TDP:" mean?

And why is it declined?
Mi
Posted on: 02 Feb 2016 20:41 
For everybody who is waiting for full XMP support from Telerik, should take a look at this open source project: https://github.com/drewnoakes/xmp-core-dotnet

Quote from it:
----
This library is a port of Adobe's XMP SDK to .NET.

The API should be familiar to users of Adobe's XMPCore 5.1.2, though it has been modified in places to better suit .NET development.
----

It is under BSD license, so it should be possible for Telerik to incorporate this library!
ADMIN
Boby
Posted on: 17 Nov 2015 13:18 
I am reopening the item, as it was not implemented as part of the "Implement support for meta tags" item ( http://feedback.telerik.com/Project/143/Feedback/Details/131527-implement-support-for-meta-tags ).
ADMIN
Petya
Posted on: 05 Dec 2014 12:43 
Hi Mike, 
We've had multiple requests for PDF/A support which is why the request is treated with high priority. However, since XMP metadata is a subset of the feature I'm going to decline it as all needed details already are in our backlog.
Mi
Posted on: 01 Dec 2014 21:17 
Hi Petya,

thanks for responding. I just was wondering, why the other suggestions where accepted and this one not. I hoped more people will look for xmp and vote this up, so I added this too. But I think most of the people don't realize what PDF support especially PDF/A-1 or PDF/A-3 support really means.
ADMIN
Petya
Posted on: 01 Dec 2014 14:23 
Hi Mike,

I'm sorry for the delay, the reason this item has been under review for so long is that our specialists needed to thoroughly investigate the request. 

In fact, we are very confused, since you've already created two other items concerning the same topic, both of which have been approved. We committed to implementing PDF/A support http://feedback.telerik.com/Project/143/Feedback/Details/131524-implement-pdf-a-support and metadata http://feedback.telerik.com/Project/143/Feedback/Details/131527-implement-support-for-meta-tags , so my suggestion is to either add any additional details on the matter to one of those items or if this request concerns something else, provide more information.
Mi
Posted on: 28 Nov 2014 20:16 
Hi! I wonder what takes six weeks to decide to accept or decline a feature request?

Just to push you to the right direction: XMP support is crucial for enterprises. Every document you send should be a PDF/A-1 or better a PDF/A-3 document. XMP is a requirement for PDF/A-1 documents. To be able to archive invoices one must support PDF/A-1. 

Keep up your promises for enterprise ready components and make it happen.
Create an account Log In
View
Type
Status
Category