Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Undocumented AHF Properties #101

Closed
shaneataylor opened this issue Jun 2, 2016 · 4 comments
Closed

Undocumented AHF Properties #101

shaneataylor opened this issue Jun 2, 2016 · 4 comments
Assignees
Labels
coverage Incomplete information in existing topics
Milestone

Comments

@shaneataylor
Copy link
Contributor

Raised originally in #81 by @markgif

I have since also found out about two undocumented command line parameters for enabling the use of Antenna House:

ahf.dir
The directory where AH is installed.

ahf.cmd
The path to AHFCmd.exe in that directory. (I'm using Windows 7, not sure about other OSes)

@jelovirt
Copy link
Member

The ahf.dir doesn't exist. The other property is axf.cmd and that specified the AHF executable that is used to run AHF from the command line.

jelovirt added a commit to dita-ot/dita-ot that referenced this issue Aug 29, 2016
@infotexture infotexture added the coverage Incomplete information in existing topics label Aug 29, 2016
@infotexture infotexture added this to the 3.0 milestone Aug 29, 2016
@markgif
Copy link
Contributor

markgif commented Aug 29, 2016

I have two questions related to this.

  1. How does the OT access Antenna House when you tell it to use it with
    the command line parameter? I assume the OT does not use this AH command
    line executable. What does it use?
  2. Is the answer different for 1.8 and 2.x OT versions?

@drmacro
Copy link
Member

drmacro commented Aug 29, 2016

The OT uses the command line executable. This is in pdf2/build_axf.xml:

<target name="transform.fo2pdf.ah.nooption" unless="has.axf.option">
<exec executable="${axf.cmd}" resultproperty="errCode" logerror="true">
      <arg value="-d"/>
      <arg value="${pdf2.temp.dir}/topic.fo"/>
      <arg value="-o"/>
      <arg value="${outputFile}"/>
      <arg value="-p"/>
      <arg value="${axf.formatter.output-format}"/>
      <arg value="-extlevel"/>
      <arg value="4"/>
      <arg value="-peb"/>
      <arg value="1"/>
    </exec>
 </target>
  <target name="transform.fo2pdf.ah.hasoption" if="has.axf.option">
    <exec executable="${axf.cmd}" resultproperty="errCode" logerror="true">
      <arg value="-d"/>
      <arg value="${pdf2.temp.dir}/topic.fo"/>
      <arg value="-o"/>
      <arg value="${outputFile}"/>
      <arg value="-p"/>
      <arg value="${axf.formatter.output-format}"/>
      <arg value="-extlevel"/>
      <arg value="4"/>
      <arg value="-peb"/>
      <arg value="1"/>
      <arg value="-i"/>
      <arg value="${env.AXF_OPT}"/>
    </exec>
  </target>

@markgif
Copy link
Contributor

markgif commented Aug 29, 2016

Well I'll be darned! That's the way I've done it in a couple plugins and
I figured I was doing a hack. I had the idea there would be some Java
class the OT would access or something. No wonder I could not find it
when I looked for it. Thanks Eliot.

jelovirt added a commit to dita-ot/org.dita.pdf2.axf that referenced this issue Jul 1, 2021
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
coverage Incomplete information in existing topics
Projects
None yet
Development

No branches or pull requests

5 participants