Changeset 32051 for gs3-extensions/gs-icecite/GS-Icecite-README

Timestamp:

2017-10-20T21:33:01+13:00 (7 years ago)

Author:

ak19

Message:

Fixes to get icecite to convert PDFs to txt on Windows. See added sections in the GS-Icecite-README file committed

File:

• gs3-extensions/gs-icecite/GS-Icecite-README (modified) (2 diffs)

gs3-extensions/gs-icecite/GS-Icecite-README

@@ -20 +20 @@
 1. In order to compile up Icecite, you will have to set up the environment for JDK8:
 
-    export JAVA_HOME=/opt/java8/
+    export JAVA_HOME=/opt/java8
     export PATH=$JAVA_HOME/bin:$PATH
 
@@ -138 +138 @@
 Since we provide the absolute path to the jar nested within pdf-cli, we no longer need to cd into pdf-cli first to run the jar executable.
 
+
+4. In order to get IceCite built on Linux to work on Windows, to convert PDF to txt, make the following 2 changes to both the following java files both found in icecite/commons/src/main/java/de/freiburg/iif/path/
+
+- PathUtils.java
+- LineReader.java
+
+Changes to make:
+a. Add the import statement
+   import java.net.URISyntaxException;
+
+b. Replace
+    Path jarFile = Paths.get(codeSource.getLocation().getPath());
+with
+    // GREENSTONE MOD:
+    // The following line causes problem on Windows with parsing
+    // the cmdline args when running pdf-cli jar:
+    //Path jarFile = Paths.get(codeSource.getLocation().getPath());
+    // See https://stackoverflow.com/questions/43972777/exception-in-thread-main-java-nio-file-invalidpathexception-illegal-char
+    // for the error message and solution    
+    Path jarFile = null;
+    try {
+    String jarPath = Paths.get(codeSource.getLocation().toURI()).toString();
+    jarFile = Paths.get(jarPath);
+    } catch(URISyntaxException e) {
+    System.err.println("**** URISyntaxException. Couldn't convert CodeSource URL to URI: " + codeSource.getLocation());
+    // fallback to old way that works on linux, since declaring this method as
+    // "throws URISyntaxException" will require dealing with that bubbled up
+    // exception in all calling methods. As this appears to be a common utility
+    // method, that could make for a lot of calling code that needs editing
+    jarFile = Paths.get(codeSource.getLocation().getPath()); 
+    }
+
+c. When running on either Linux or Windows, provide the full filepaths to both input and output files. Using ~/ in filepaths on Linux, to denote home folders, is alright.
+A windows command looks as follows, note double quotes in place of single ones around the classpath value, and the Windows PATH separator in classpath. But the backslashes in classpath also work if they're forward slashes:
+
+    java -classpath "C:\Path\to\GS3\ext\icecite\gs-installed-jars\*;C:\Path\to\GS3\icecite\pdf-cli\target\pdf-cli-0.0.1-SNAPSHOT-jar-with-dependencies.jar" cli.PdfParserCommandLine --format txt --feature words C:\Path\to\24.pdf C:\Path\to\24converted.txt