Hi,
I wanted to start submitting patches for the following and would like your
input on that:
Create one Core Properties interface for the Metadata class which contains
just the keys for the properties which should be directly addressable through
the Metadata class in the future. Those are
On Fri, 4 May 2012, Joerg Ehrlich wrote:
Create one Core Properties interface for the Metadata class which
contains just the keys for the properties which should be directly
addressable through the Metadata class in the future. Those are all
DublinCore plus copyright and a bit of other
On Fri, 4 May 2012, Joerg Ehrlich wrote:
Create one Core Properties interface for the Metadata class which
contains just the keys for the properties which should be directly
addressable through the Metadata class in the future. Those are all
DublinCore plus copyright and a bit of other
Hi Jörg,
On May 4, 2012, at 6:43 AM, Joerg Ehrlich wrote:
Hi,
I wanted to start submitting patches for the following and would like your
input on that:
Create one Core Properties interface for the Metadata class which contains
just the keys for the properties which should be directly
Chris Wilson created TIKA-912:
-
Summary: Response charset encoding not declared, and depends on
host OS (Windows/Linux)
Key: TIKA-912
URL: https://issues.apache.org/jira/browse/TIKA-912
Project: Tika
[
https://issues.apache.org/jira/browse/TIKA-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Wilson updated TIKA-912:
--
Attachment: TikaResource-utf8-response.patch
Response charset encoding not declared, and depends on
On Fri, 4 May 2012, Joerg Ehrlich wrote:
The keys will always link to properties of other namespace interfaces like:
String Title = DublinCore.Title.getName(); String Author =
DublinCore.Creator.getName();
Won't that break existing parsers and consumers though? As Title will
suddenly change
