[ 
https://issues.apache.org/jira/browse/TIKA-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14599736#comment-14599736
 ] 

Tim Allison edited comment on TIKA-1662 at 6/24/15 4:58 PM:
------------------------------------------------------------

To confirm, the issue is that there's an inconsistency in how we're marking up 
ppt vs. pptx?  Or is the issue with the specific file that you attached vs. 
other pptx?

PPT:
{noformat}
<body>
  <div class="slideShow">
    <div class="slide">
      <div class="slide-master-content" />
      <p class="slide-content">Header<br />
        Text<br />
      </p>
    </div>
  </div>
</body>
{noformat}

vs PPTX:
{noformat}
<body>
  <p>Header</p>
  <p>Text</p>
</body>
{noformat}


was (Author: talli...@mitre.org):
To confirm, the issue is that there's an inconsistency in how we're parsing ppt 
vs. pptx?  Or is the issue with the specific file that you attached vs. other 
pptx?

PPT:
{noformat}
<body>
  <div class="slideShow">
    <div class="slide">
      <div class="slide-master-content" />
      <p class="slide-content">Header<br />
        Text<br />
      </p>
    </div>
  </div>
</body>
{noformat}

vs PPTX:
{noformat}
<body>
  <p>Header</p>
  <p>Text</p>
</body>
{noformat}

> Some PPTX is parsed wrong
> -------------------------
>
>                 Key: TIKA-1662
>                 URL: https://issues.apache.org/jira/browse/TIKA-1662
>             Project: Tika
>          Issue Type: Bug
>          Components: parser
>    Affects Versions: 1.2, 1.4, 1.8
>         Environment: Java 1.8
>            Reporter: Sergey Kozlov
>
> I use tika parser to get all text from slides. Most of presentations are 
> parsed as follows: tika parser maps slide to <div> and each text parapraph to 
> <p>. But http://vk.com/doc50470295_403042266 is treated as two <p> without 
> any <div>. I have reproduced this with versions 1.2, 1.4 and 1.8; 1.0 works 
> great. This is the cause I have to use 1.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to