tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris A. Mattmann (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (TIKA-18) "Office" interface should be renamed "MSOffice".
Date Tue, 18 Sep 2007 22:08:46 GMT

     [ https://issues.apache.org/jira/browse/TIKA-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Chris A. Mattmann resolved TIKA-18.

    Resolution: Fixed

Keith I was unable to apply your patch (was rejected by my patch utility) to the latest trunk.
So, i had to cut/paste the changes myself.

Renamed "Office" interface to "MSOffice"
Updated Metadata to implement "MSOffice" I/F

> "Office" interface should be renamed "MSOffice".
> ------------------------------------------------
>                 Key: TIKA-18
>                 URL: https://issues.apache.org/jira/browse/TIKA-18
>             Project: Tika
>          Issue Type: Improvement
>          Components: general
>    Affects Versions: 0.1-incubator
>            Reporter: Keith R. Bennett
>            Assignee: Chris A. Mattmann
>            Priority: Minor
>             Fix For: 0.1-incubator
>         Attachments: tika-18.patch
> The org.apache.tika.metadata.Office interface should be renamed MSOffice to make clear
to the reader that it applies to Microsoft Office and not (necessarily) OpenOffice.
> According to Chris Mattmann, the author of this interface:
> "Basically it [the Office interface] applies to whatever office met fields
> are made available via the Jakarta POI library, which is where we got the
> list of met keys from while using the interface on Apache Nutch.
> "Each one of the interfaces in the org.apache.tika.metadata package are
> collections of met keys that we found used in commonplace throughout the
> Nutch code, and that we tried to generalize into a canonical source. The
> Office interface, were properties that we saw used in the parse-msword,
> parse-msexcel/etc. plugins, which all rely on Jakarta POI I believe."
> Patch coming...

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message