search

computerline1z / okapi

Automatically exported from code.google.com/p/okapi
0 stars 0 forks source link

Text that is typed along a path in IDML files is not extracted into XLIFF #194

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Run the Tikal tool on each of the attached files.  I've tried using and not 
using the IDML filter.
  - Windows example = tikal -x "idml\Polygon - TextPath.idml"
  - Windows example = tikal -x -fc okf_idml "idml\Polygon - TextPath.idml"
2. Open the newly created XLIFF file in a text editor

What is the expected output? What do you see instead?
When looking at the Spread XML files, okapi successfully extracts text that is 
associated with text blocks that use the <TextFrame> element.  But InDesign 
also allows text to be typed along the path of a shape including ovals, lines, 
polygons, etc.  I expect that text to be extracted as well since that kind of 
text is just as visible as text inside of regular blocks (see screenshot).  It 
looks like okapi isn't recognizing the <TextPath> elements inside of other 
objects such as <GraphicLine>, <Polygon>, and <Oval> and then looking at the 
associated Story XML file to extract the text.  Am I missing some configuration 
options in the extraction process or am I not using okapi correctly?

What version of the product are you using? On what operating system?
Adobe InDesign CS4
Mac OS X 10.6.8
Okapi Tikal - Version: 2.0.14 for Windows 64bit

Please provide any additional information below.
I have attached a few sample files that demonstrate text drawn along various 
shapes.  The photobook sample is based on one of the templates provided by CS4 
and contains the text in the screenshot.  The sample files include the source 
IDML files and the generated XLIFF files when using the IDML filter.

Original issue reported on code.google.com by mval...@lingotek.com on 11 Nov 2011 at 5:20

Attachments:

GoogleCodeExporter commented 9 years ago 
Bug verified.
Thanks for the sample files.

Original comment by yves.sav...@gmail.com on 11 Nov 2011 at 11:51

GoogleCodeExporter commented 9 years ago 
It seems it was an easy one to fix.
The next snapshot available at http://okapi.opentag.com/snapshots will have the 
fix
(in about 45mn from the time of this post).

Original comment by yves.sav...@gmail.com on 11 Nov 2011 at 12:22

GoogleCodeExporter commented 9 years ago 
That was fast work!  I tried out the latest snapshot and it now correctly 
extracts text out of the text paths.  Thanks again.

Original comment by mval...@lingotek.com on 11 Nov 2011 at 5:16