imazen/folioxml

Folio Flat File to XML/HTML/Lucene conversion framework

folioxml's Issues

Implement command-line wrapper

Add .idea project files

Create public-domain query set

We need a set of public-domain folio queries to test our parser and execution engine against.

We support contents|field|group|highlighter|level|popup|note queries, but not headings|partition|rank|weight|server.

Queries involving the latter are still appreciated for future use if they are stored in a separate file (one line per query).

Add travis integration

Add maven configuration to restore dependencies

Dependency erros

Hi!
Thanks for sharing this library. I cloned the repository on NetBeans and now Im having issues with dependencies. The error I get when I try to run it is:
Failed to execute goal on project folioxml-commandline: Could not resolve dependencies for project folioxml:folioxml-commandline:jar:0.0.1-SNAPSHOT: Could not find artifact folioxml:folioxml-lucene:jar:0.0.1-SNAPSHOT -> [Help 1]

Any idea on how to fix this problem?

Thanks

Overlapping Fields

Hi, thanks for making this tool available! We have been testing this out and came across the following.

I have overlapping fields in my source flat file; using the folioxml tool, the output is well-formed but the applied field boundaries are not the same as was in the source.

Thanks for your time.

Darryl

example source fff
<RD>
<FD:"field 1"><FD:"field 2">field 1 and field 2 </FD:"field 1"> field 1</FD:"field 2">
<FD:"field 1"> field 1 <FD:"field 2"> field 1 and field 2</FD:"field 1"> field 2</FD:"field 2">

output (xml)
<record>
<span class="field1" type="field 1"><span class="field2" type="field 2">field 1 and field 2 field 1</span>
<span class="field1" type="field 1"> field 1 <span class="field2" type="field 2">field 1 and field 2 field 2</span>

</span>
</span>
</record>

Can you upload this to Maven Central?

Hi!
Thanks for sharing this library. I'm planning to use this soon, so it will be nice to be able to add to my dependiencies directly from Maven Central. Can you put it there?
Again, thanks!

Cannot handle level names that include commas

Replace .properties configuration for test data with something else. (say YAML?)

SLX not does not output file in Maven test.

Fails to compile with test error in TEST-folioxml.slx.SlxTransformerTest.xml:

error message="C:...\folioxml-master\files\folio-help\export\Translation.slx (The system cannot find the path specified)" type="java.io.FileNotFoundException"![CDATA[java.io.FileNotFoundException: C:...\folioxml-master\files\folio-help\export\Translation.slx (The system cannot find the path specified)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.(FileOutputStream.java:213)
at java.io.FileOutputStream.(FileOutputStream.java:162)
at folioxml.slx.SlxTransformerTest.XmlExport(SlxTransformerTest.java:29)
at folioxml.slx.SlxTransformerTest.FolioHelp(SlxTransformerTest.java:21)
]]
/error

Create public-domain test infobase

We currently use a private test infobase (the folio help file), which prevents our CI servers from passing, and makes it difficult for others from contributing to the project. It's also not terribly complete.

We want to create a test infobase that

• Contains only public-domain content
• Has a consistent appearance, so that the corresponding (exported) HTML can be visually compared with relative ease, and issues quickly spotted.
• Is small (preferably 500kb or less). This is for speed, which matters when you run tests millions of times.
• Exercises all modern (and legacy) folio flat file features.

Exercises

• Tables (including header rows, columns, cells, spacing, padding, borders, colors, and spans)
• Tab stops (including left, center, right, dot/dash/alternating leaders, and custom series)
• Fonts, spacing, margins, justification
• Cross-infobase queries and links (this will require a 2nd infobase)
• Headings
• Bookmarks, jump destinations
• Popups, named popups, notes
• Fields, including overlapping field applications
• Hidden text
• Underlining, strikeout, italics
• Levels, hierarchies, including skipping levels
• Objects and object links (including all image formats - bitmap, png, gif, jpeg)
• Data links (pdfs, spreadsheets, etc)
• Program links
• Highlighters, link styles, and character styles
• Web links
• Query links (including level, field, and group queries). Text indexing rules (we want to verify that we mimic the Folio search algorithm 100% when resolving these).
• Groups

And all the esoteric, undocumented (or supposedly invalid) flat file codes that we've encountered over the years, like:

• TS (empty tab stop with no parameters)
• [add here, or comment]