Página inicial Explorar Ajuda
Entrar
bn
/
se
2
0
Fork 0
Arquivos Issues 0 Pull Requests 0 Wiki
Tree: c8927bb461
Branches Tags
se
/
SE
/
schema
/
WPS_Functions
/
dita-ot
/
dita-ot-3.5
/
doc
/
parameters
/
dita-command-arguments.html

dita-command-arguments.html 25 KB
Histórico Raw

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402 
  1. <!DOCTYPE html
    2. 

  2.   SYSTEM "about:legacy-compat">
    3. 

  3. <html lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><meta charset="UTF-8"><meta name="copyright" content="(C) Copyright 2020"><meta name="DC.rights.owner" content="(C) Copyright 2020"><meta name="DC.type" content="reference"><meta name="description" content="The dita command takes mandatory arguments to process DITA content. Subcommands can be used to manage plug-ins, or print information about the current configuration. A series of options are available to modify the command behavior or specify additional configuration parameters."><meta name="DC.subject" content="filters, command, dita, command, arguments list, arguments, installing, uninstalling, artlbl, args.artlbl"><meta name="keywords" content="filters, command, dita, command, arguments list, arguments, installing, uninstalling, artlbl, args.artlbl"><meta name="DC.relation" scheme="URI" content="../parameters/index.html"><meta name="DC.relation" scheme="URI" content="../topics/build-using-dita-command.html"><meta name="DC.relation" scheme="URI" content="../parameters/parameters_intro.html"><meta name="DC.relation" scheme="URI" content="../parameters/internal-ant-properties.html"><meta name="DC.relation" scheme="URI" content="../topics/using-dita-properties-file.html"><meta name="DC.format" content="HTML5"><meta name="DC.identifier" content="dita-command-properties"><meta name="DC.language" content="en"><link rel="stylesheet" type="text/css" href="../css/commonltr.css"><link rel="stylesheet" type="text/css" href="../css/dita-ot-doc.css"><title>Arguments and options for the dita command</title></head><body id="dita-command-properties"><header role="banner"><div class="header">
    4. 

  4.   <p>DITA Open Toolkit</p>
    5. 

  5.   <hr>
    6. 

  6. </div></header><nav role="toc"><ul><li><a href="../index.html">DITA Open Toolkit 3.5</a></li><li><a href="../release-notes/index.html">Release Notes</a></li><li><a href="../topics/installing-client.html">Installing DITA-OT</a></li><li><a href="../topics/building-output.html">Building output</a></li><li><a href="../topics/input-formats.html">Authoring formats</a></li><li><a href="../topics/output-formats.html">Output formats</a></li><li><a href="../parameters/index.html">Parameters</a><ul><li class="active"><a href="../parameters/dita-command-arguments.html">DITA command arguments</a></li><li><a href="../parameters/parameters_intro.html">DITA-OT parameters</a></li><li><a href="../parameters/configuration-properties.html">Configuration properties</a></li></ul></li><li><a href="../topics/html-customization.html">Customizing HTML</a></li><li><a href="../topics/pdf-customization.html">Customizing PDF</a></li><li><a href="../topics/adding-plugins.html">Adding plug-ins</a></li><li><a href="../topics/custom-plugins.html">Creating plug-ins</a></li><li><a href="../topics/troubleshooting-overview.html">Troubleshooting</a></li><li><a href="../reference/index.html">Reference</a></li><li><a href="../topics/dita-and-dita-ot-resources.html">Resources</a></li></ul></nav><main role="main"><article role="article" aria-labelledby="ariaid-title1">
    7. 

  7.   <h1 class="title topictitle1" id="ariaid-title1">Arguments and options for the <span class="keyword cmdname">dita</span> command</h1>
    8. 

  8.   
    9. 

  9.   
    10. 

  10.   
    11. 

  11.   <div class="body refbody"><p class="shortdesc">The <span class="keyword cmdname">dita</span> command takes mandatory arguments to process DITA content. Subcommands can be
    12. 

  12.     used to manage plug-ins, or print information about the current configuration. A series of options are available to
    13. 

  13.     modify the command behavior or specify additional configuration parameters.</p>
    14. 

  14.     <section class="section"><h2 class="title sectiontitle">Usage</h2>
    15. 

  15.       
    16. 

  16.       <p class="p">To convert content from one format to another, specify the file to transform and the desired output format. If
    17. 

  17.         necessary, you can set additional configuration parameters with options.</p>
    18. 

  18.       <div style="display: block; border: 1 black solid; padding: 2pt; color: maroon; margin-bottom: 6pt;">
    19. 

  19.         <div><a name=""></a>
    20. 

  20.           <blockquote> 
    21. 

  21.             <kbd><b>dita</b></kbd>
    22. 

  22.             <kbd><b>--input</b></kbd>
    23. 

  23.             <kbd class="ph oper">=</kbd>
    24. 

  24.             <var>file</var>
    25. 

  25.             <kbd><b>--format</b></kbd>
    26. 

  26.             <kbd class="ph oper">=</kbd>
    27. 

  27.             <var>name</var>
    28. 

  28.              [ 
    29. 

  29.               <var>options</var>
    30. 

  30.              ] 
    31. 

  31.            </blockquote>
    32. 

  32.         </div>
    33. 

  33.         <div><a name=""></a>
    34. 

  34.           <blockquote> 
    35. 

  35.             <kbd><b>dita</b></kbd>
    36. 

  36.             <kbd><b>--project</b></kbd>
    37. 

  37.             <kbd class="ph oper">=</kbd>
    38. 

  38.             <var>file</var>
    39. 

  39.              [ 
    40. 

  40.               <var>options</var>
    41. 

  41.              ] 
    42. 

  42.            </blockquote>
    43. 

  43.         </div>
    44. 

  44.       </div>
    45. 

  45.       <div class="note note note_note"><span class="note__title">Note:</span> Most <span class="keyword cmdname">dita</span> command options support several syntax alternatives. All options can be
    46. 

  46.         specified with a GNU-style option keyword preceded by two hyphens. In many cases, Unix-style single-letter
    47. 

  47.         options (preceded by a single hyphen) are also available for brevity and backwards compatibility.</div>
    48. 

  48.       <p class="p">The <span class="keyword cmdname">dita</span> command also supports a series of subcommands that can be used to manage plug-ins,
    49. 

  49.         or print information about the current configuration or version.</p>
    50. 

  50.       <div style="display: block; border: 1 black solid; padding: 2pt; color: maroon; margin-bottom: 6pt;">
    51. 

  51.         <div><a name=""></a>
    52. 

  52.           <blockquote> 
    53. 

  53.             <kbd><b>dita</b></kbd>
    54. 

  54.             <kbd><b>deliverables</b></kbd>
    55. 

  55.             <var>file</var>
    56. 

  56.            </blockquote>
    57. 

  57.         </div>
    58. 

  58.         <div><a name=""></a>
    59. 

  59.           <blockquote> 
    60. 

  60.             <kbd><b>dita</b></kbd>
    61. 

  61.             <kbd><b>install</b></kbd>
    62. 

  62.              [ { 
    63. 

  63.               <var>ID</var>
    64. 

  64.               <var> | URL</var>
    65. 

  65.               <var> | file</var>
    66. 

  66.              } ] 
    67. 

  67.            </blockquote>
    68. 

  68.         </div>
    69. 

  69.         <div><a name=""></a>
    70. 

  70.           <blockquote> 
    71. 

  71.             <kbd><b>dita</b></kbd>
    72. 

  72.             <kbd><b>plugins</b></kbd>
    73. 

  73.            </blockquote>
    74. 

  74.         </div>
    75. 

  75.         <div><a name=""></a>
    76. 

  76.           <blockquote> 
    77. 

  77.             <kbd><b>dita</b></kbd>
    78. 

  78.             <kbd><b>transtypes</b></kbd>
    79. 

  79.            </blockquote>
    80. 

  80.         </div>
    81. 

  81.         <div><a name=""></a>
    82. 

  82.           <blockquote> 
    83. 

  83.             <kbd><b>dita</b></kbd>
    84. 

  84.             <kbd><b>uninstall</b></kbd>
    85. 

  85.             <var>ID</var>
    86. 

  86.            </blockquote>
    87. 

  87.         </div>
    88. 

  88.         <div><a name=""></a>
    89. 

  89.           <blockquote> 
    90. 

  90.             <kbd><b>dita</b></kbd>
    91. 

  91.             <kbd><b>version</b></kbd>
    92. 

  92.            </blockquote>
    93. 

  93.         </div>
    94. 

  94.       </div>
    95. 

  95.       <div class="note attention note_attention"><span class="note__title">Attention:</span> Prior to DITA-OT 3.5, subcommands were specified with the double-hyphen option syntax,
    96. 

  96.         which is still supported for backwards compatibility. (For example, <span class="keyword cmdname">dita</span>
    97. 

  97.         <span class="keyword parmname">--install</span> will still work.)</div>
    98. 

  98.     </section>
    99. 

  99. 

  100.     <section class="section"><h2 class="title sectiontitle">Arguments</h2>
    101. 

  101.       
    102. 

  102.       
    103. 

  103.       
    104. 

  104.       
    105. 

  105.       
    106. 

  106.       <p class="p">Each transformation requires you to specify at least the file to transform and the desired output format.</p>
    107. 

  107.       <dl class="dl parml">
    108. 

  108.         
    109. 

  109.           <dt class="dt pt dlterm">
    110. 

  110.             <span class="keyword parmname">--input</span>=<var class="keyword varname">file</var></dt>
    111. 

  111.           <dt class="dt pt dlterm">
    112. 

  112.             <span class="keyword parmname">-i</span>
    113. 

  113.             <var class="keyword varname">file</var>
    114. 

  114.           </dt>
    115. 

  115.           <dd class="dd pd" id="dita-command-properties__args.input.desc">Specifies the master file for your documentation project. This argument corresponds
    116. 

  116.             to the common parameter <span class="keyword parmname">args.input</span>. Typically this is a DITA map, however it also can
    117. 

  117.             be a DITA topic if you want to transform a single DITA file. The path can be absolute, relative to
    118. 

  118.               <span class="keyword parmname">args.input.dir</span>, or relative to the current directory if
    119. 

  119.               <span class="keyword parmname">args.input.dir</span> is not defined.</dd>
    120. 

  120.         
    121. 

  121.         
    122. 

  122.           <dt class="dt pt dlterm">
    123. 

  123.             <span class="keyword parmname">--format</span>=<var class="keyword varname">name</var></dt>
    124. 

  124.           <dt class="dt pt dlterm">
    125. 

  125.             <span class="keyword parmname">-f</span>
    126. 

  126.             <var class="keyword varname">name</var>
    127. 

  127.           </dt>
    128. 

  128.           <dd class="dd pd">Specifies the output format (transformation type).</dd>
    129. 

  129.           <dd class="dd pd ddexpand">This argument corresponds to the common parameter <span class="keyword parmname">transtype</span>.</dd>
    130. 

  130.           <dd class="dd pd ddexpand">To list the formats that are currently available in your environment, use <span class="keyword cmdname">dita
    131. 

  131.               transtypes</span>.</dd>
    132. 

  132.           <dd class="dd pd ddexpand">
    133. 

  133.             <div class="p">You can create plug-ins to add new output formats; by default, the following values are
    134. 

  134.                 available:
    135. 

  135.                 
    136. 

  136.                 <ul class="ul">
    137. 

  137.                   <li class="li"><span class="keyword option">dita</span></li>
    138. 

  138.                   <li class="li"><span class="keyword option">eclipsehelp</span></li>
    139. 

  139.                   <li class="li"><span class="keyword option">html5</span></li>
    140. 

  140.                   <li class="li"><span class="keyword option">htmlhelp</span></li>
    141. 

  141.                   <li class="li"><span class="keyword option">markdown</span>, <span class="keyword option">markdown_gitbook</span>, and
    142. 

  142.                     <span class="keyword option">markdown_github</span></li>
    143. 

  143.                   <li class="li"><span class="keyword option">pdf</span></li>
    144. 

  144.                   <li class="li"><span class="keyword option">xhtml</span></li>
    145. 

  145.                 </ul>
    146. 

  146.                 <div class="note tip note_tip"><span class="note__title">Tip:</span> See
    147. 

  147.                   <a class="xref" href="../topics/output-formats.html" title="DITA Open Toolkit ships with several core transformations that convert DITA content to different output formats. Additional formats are available from the plug-in registry at dita-ot.org/plugins.">DITA-OT transformations (output formats)</a> for sample command line syntax and more information on each
    148. 

  148.                   transformation. </div>
    149. 

  149.               </div>
    150. 

  150.           </dd>
    151. 

  151.         
    152. 

  152.       </dl>
    153. 

  153.     </section>
    154. 

  154. 

  155.     <section class="section"><h2 class="title sectiontitle">Subcommands</h2>
    156. 

  156.       
    157. 

  157.       
    158. 

  158.       
    159. 

  159.       
    160. 

  160.       
    161. 

  161.       
    162. 

  162.       
    163. 

  163.       
    164. 

  164.       
    165. 

  165.       
    166. 

  166.       
    167. 

  167.       
    168. 

  168.       
    169. 

  169.       
    170. 

  170.       <dl class="dl parml">
    171. 

  171.         
    172. 

  172.           <dt class="dt pt dlterm">
    173. 

  173.             <span class="keyword parmname">deliverables</span>
    174. 

  174.             <var class="keyword varname">file</var></dt>
    175. 

  175.           <dd class="dd pd">Show a list of the available deliverables in the specified project <var class="keyword varname">file</var>.</dd>
    176. 

  176.         
    177. 

  177.         
    178. 

  178.           <dt class="dt pt dlterm">
    179. 

  179.             <span class="keyword parmname">install</span>
    180. 

  180.             <var class="keyword varname">{ ID | URL | file }</var></dt>
    181. 

  181.           <dt class="dt pt dlterm">
    182. 

  182.             <span class="keyword parmname">--install</span>=<var class="keyword varname">{ ID | URL | file }</var></dt>
    183. 

  183.           <dd class="dd pd">Install a single plug-in <var class="keyword varname">ID </var>from the registry at
    184. 

  184.             <a class="xref" href="https://www.dita-ot.org/plugins" target="_blank" rel="external noopener">dita-ot.org/plugins</a> (or a local registry), from a remote <var class="keyword varname">URL</var>, or a
    185. 

  185.             local ZIP <var class="keyword varname">file</var>.</dd>
    186. 

  186.         
    187. 

  187.         
    188. 

  188.           <dt class="dt pt dlterm">
    189. 

  189.             <span class="keyword parmname">install</span>
    190. 

  190.           </dt>
    191. 

  191.           <dt class="dt pt dlterm">
    192. 

  192.             <span class="keyword parmname">--install</span>
    193. 

  193.           </dt>
    194. 

  194.           <dd class="dd pd"><span class="ph">If no <var class="keyword varname">ID</var>, <var class="keyword varname">URL</var>, or
    195. 

  195.                     <var class="keyword varname">file</var> argument is provided, the installation process reloads the current set of
    196. 

  196.                   plug-ins from the <span class="ph filepath">plugins</span> directory. This approach can be used to add or remove
    197. 

  197.                   multiple plug-ins at once, or any individual plug-ins you have already copied to (or removed from) the
    198. 

  198.                     <span class="ph filepath">plugins</span> directory. Any plug-ins added or removed in the process will be listed
    199. 

  199.                   by their plug-in ID.</span></dd>
    200. 

  200.         
    201. 

  201.         
    202. 

  202.           <dt class="dt pt dlterm">
    203. 

  203.             <span class="keyword parmname">uninstall</span>
    204. 

  204.             <var class="keyword varname">ID</var>
    205. 

  205.           </dt>
    206. 

  206.           <dt class="dt pt dlterm">
    207. 

  207.             <span class="keyword parmname">--uninstall</span>=<var class="keyword varname">ID</var>
    208. 

  208.           </dt>
    209. 

  209.           <dd class="dd pd">
    210. 

  210.             <p class="p">Remove the plug-in with the specified <var class="keyword varname">ID</var>.</p>
    211. 

  211.           </dd>
    212. 

  212.           <dd class="dd pd ddexpand">For a list of the currently installed plug-in IDs, use <span class="keyword cmdname">dita plugins</span>.</dd>
    213. 

  213.           <dd class="dd pd ddexpand">
    214. 

  214.             <div class="note attention note_attention"><span class="note__title">Attention:</span> The <span class="keyword cmdname">uninstall</span> subcommand also
    215. 

  215.                   removes the corresponding plug-in directory from the <span class="ph filepath">plugins</span> folder.
    216. 

  216.                   </div>
    217. 

  217.           </dd>
    218. 

  218.         
    219. 

  219.         
    220. 

  220.           <dt class="dt pt dlterm">
    221. 

  221.             <span class="keyword parmname">plugins</span>
    222. 

  222.           </dt>
    223. 

  223.           <dt class="dt pt dlterm">
    224. 

  224.             <span class="keyword parmname">--plugins</span>
    225. 

  225.           </dt>
    226. 

  226.           <dd class="dd pd">Show a list of the currently installed plug-ins.</dd>
    227. 

  227.         
    228. 

  228.         
    229. 

  229.           <dt class="dt pt dlterm">
    230. 

  230.             <span class="keyword parmname">transtypes</span>
    231. 

  231.           </dt>
    232. 

  232.           <dt class="dt pt dlterm">
    233. 

  233.             <span class="keyword parmname">--transtypes</span>
    234. 

  234.           </dt>
    235. 

  235.           <dd class="dd pd">Show a list of the available output formats (transformation types).</dd>
    236. 

  236.           <dd class="dd pd ddexpand">The entries in this list may be passed as values to the <span class="keyword parmname">--format</span> argument.</dd>
    237. 

  237.         
    238. 

  238.         
    239. 

  239.           <dt class="dt pt dlterm">
    240. 

  240.             <span class="keyword parmname">version</span>
    241. 

  241.           </dt>
    242. 

  242.           <dt class="dt pt dlterm">
    243. 

  243.             <span class="keyword parmname">--version</span>
    244. 

  244.           </dt>
    245. 

  245.           <dd class="dd pd">Print version information and exit.</dd>
    246. 

  246.         
    247. 

  247.       </dl>
    248. 

  248.     </section>
    249. 

  249.     <section class="section"><h2 class="title sectiontitle">Options</h2>
    250. 

  250.       
    251. 

  251.       
    252. 

  252.       
    253. 

  253.       
    254. 

  254.       
    255. 

  255.       
    256. 

  256.       
    257. 

  257.       
    258. 

  258.       
    259. 

  259.       
    260. 

  260.       
    261. 

  261.       
    262. 

  262.       
    263. 

  263.       
    264. 

  264.       
    265. 

  265.       
    266. 

  266.       
    267. 

  267.       
    268. 

  268.       <dl class="dl parml" id="dita-command-properties__dita_build_options">
    269. 

  269.         
    270. 

  270.           <dt class="dt pt dlterm">
    271. 

  271.             <span class="keyword parmname">--debug</span></dt>
    272. 

  272.           <dt class="dt pt dlterm">
    273. 

  273.             <span class="keyword parmname">-d</span>
    274. 

  274.           </dt>
    275. 

  275.           <dd class="dd pd">Debug logging prints considerably more additional information. The debug log includes all information from
    276. 

  276.             the verbose log, plus details on Java classes, additional Ant properties and overrides, preprocessing
    277. 

  277.             filters, parameters, and stages, and the complete build sequence. Debug logging requires additional
    278. 

  278.             resources and can slow down the build process, so it should only be enabled when further details are
    279. 

  279.             required to diagnose problems.</dd>
    280. 

  280.         
    281. 

  281.         
    282. 

  282.           <dt class="dt pt dlterm">
    283. 

  283.             <span class="keyword parmname">--output</span>=<var class="keyword varname">dir</var></dt>
    284. 

  284.           <dt class="dt pt dlterm">
    285. 

  285.             <span class="keyword parmname">-o</span>
    286. 

  286.             <var class="keyword varname">dir</var>
    287. 

  287.           </dt>
    288. 

  288.           <dd class="dd pd" id="dita-command-properties__output.dir.desc">
    289. 

  289.             <p class="p">Specifies the path of the output directory; the path can be absolute or relative to the current
    290. 

  290.               directory.</p>
    291. 

  291.             <p class="p">This argument corresponds to the common parameter <span class="keyword parmname">output.dir</span>. By default, the output
    292. 

  292.               is written to the <span class="ph filepath">out</span> subdirectory of the current directory.</p>
    293. 

  293.           </dd>
    294. 

  294.         
    295. 

  295.         
    296. 

  296.           <dt class="dt pt dlterm">
    297. 

  297.             <span class="keyword parmname">--filter</span>=<var class="keyword varname">files</var>
    298. 

  298.           </dt>
    299. 

  299.           <dd class="dd pd">Specifies filter file(s) used to include, exclude, or flag content. </dd>
    300. 

  300.           <dd class="dd pd ddexpand">
    301. 

  301.             <p class="p">This argument corresponds to the common parameter <span class="keyword parmname">args.filter</span>. Relative paths are
    302. 

  302.               resolved against the current directory and internally converted to absolute paths.</p>
    303. 

  303.             <div class="note note note_note"><span class="note__title">Note:</span> 
    304. 

  304.               <p class="p">To specify multiple filter files, use the system path separator character to delimit individual file
    305. 

  305.                 paths (semicolon ‘<code class="ph codeph">;</code>’ on Windows, and colon ‘<code class="ph codeph">:</code>’ on macOS and Linux) and
    306. 

  306.                 wrap the value in quotes:</p>
    307. 

  307.               <p class="p"><code class="ph codeph">--filter="filter1.ditaval;filter2.ditaval;filter3.ditaval"</code></p>
    308. 

  308.               <p class="p">DITAVAL files are evaluated in the order specified, so conditions specified in the first file take
    309. 

  309.                 precedence over matching conditions specified in later files, just as conditions at the start of a
    310. 

  310.                 DITAVAL document take precedence over matching conditions later in the same document.</p>
    311. 

  311.             </div>
    312. 

  312.           </dd>
    313. 

  313.         
    314. 

  314.         
    315. 

  315.           <dt class="dt pt dlterm">
    316. 

  316.             <span class="keyword parmname">--force</span>
    317. 

  317.           </dt>
    318. 

  318.           <dd class="dd pd">Force-install an existing plug-in.</dd>
    319. 

  319.           <dd class="dd pd ddexpand">Passed as an additional option to the installation subcommand: <span class="keyword cmdname">dita
    320. 

  320.               install</span>&nbsp;<var class="keyword varname">plug-in-zip</var>&nbsp;<span class="keyword parmname">--force</span></dd>
    321. 

  321.         
    322. 

  322.         
    323. 

  323.           <dt class="dt pt dlterm">
    324. 

  324.             <span class="keyword parmname">--help</span></dt>
    325. 

  325.           <dt class="dt pt dlterm">
    326. 

  326.             <span class="keyword parmname">-h</span>
    327. 

  327.           </dt>
    328. 

  328.           <dd class="dd pd">Print a list of available arguments, options, and subcommands.</dd>
    329. 

  329.         
    330. 

  330.         
    331. 

  331.           <dt class="dt pt dlterm">
    332. 

  332.             <span class="keyword parmname">--logfile</span>=<var class="keyword varname">file</var></dt>
    333. 

  333.           <dt class="dt pt dlterm">
    334. 

  334.             <span class="keyword parmname">-l</span>
    335. 

  335.             <var class="keyword varname">file</var>
    336. 

  336.           </dt>
    337. 

  337.           <dd class="dd pd">Write logging messages to a file.</dd>
    338. 

  338.         
    339. 

  339.         
    340. 

  340.           <dt class="dt pt dlterm">
    341. 

  341.             <span class="keyword parmname">--parameter</span>=<var class="keyword varname">value</var></dt>
    342. 

  342.           <dt class="dt pt dlterm">
    343. 

  343.             <span class="keyword parmname">-D</span><var class="keyword varname">parameter</var>=<var class="keyword varname">value</var>
    344. 

  344.           </dt>
    345. 

  345.           <dd class="dd pd">Specify a value for a DITA-OT or Ant build parameter.
    346. 

  346.             <p class="p">The GNU-style <span class="keyword parmname">--parameter</span>=<var class="keyword varname">value</var> form is only available for
    347. 

  347.               parameters that are configured in the plug-in configuration file; the Java-style <span class="keyword parmname">-D</span>
    348. 

  348.               form can also be used to specify additional non-configured parameters or set system properties.</p>
    349. 

  349.             <p class="p">Parameters not implemented by the specified transformation type or referenced in a
    350. 

  350.                 <span class="ph filepath">.properties</span> file are ignored.</p>
    351. 

  351.             <div class="note tip note_tip"><span class="note__title">Tip:</span> If you are building in different environments where the location of the input
    352. 

  352.         files is not consistent, set <span class="keyword option">args.input.dir</span> with the <span class="keyword cmdname">dita</span> command and
    353. 

  353.         reference its value with <code class="ph codeph">${args.input.dir}</code> in your <span class="ph filepath">.properties</span> file.
    354. 

  354.         
    355. 

  355.         
    356. 

  356.       </div></dd>
    357. 

  357.         
    358. 

  358.         
    359. 

  359.           <dt class="dt pt dlterm">
    360. 

  360.             <span class="keyword parmname">--propertyfile</span>=<var class="keyword varname">file</var>
    361. 

  361.           </dt>
    362. 

  362.           <dd class="dd pd">Use build parameters defined in the referenced <span class="ph filepath">.properties</span> file.
    363. 

  363.             <p class="p">Build parameters specified on the command line override those set in the <span class="ph filepath">.properties</span>
    364. 

  364.               file.</p></dd>
    365. 

  365.         
    366. 

  366.         
    367. 

  367.           <dt class="dt pt dlterm">
    368. 

  368.             <span class="keyword parmname">--resource</span>=<var class="keyword varname">file</var>
    369. 

  369.           </dt>
    370. 

  370.           <dt class="dt pt dlterm">
    371. 

  371.             <span class="keyword parmname">-r</span>
    372. 

  372.             <var class="keyword varname">file</var>
    373. 

  373.           </dt>
    374. 

  374.           <dd class="dd pd">Process input with additional resources.
    375. 

  375.             <div class="p">For example, to process a single topic file with a map that contains key definitions, use a command like
    376. 

  376.               this:
    377. 

  377.               <pre class="pre codeblock"><code><span class="keyword cmdname">dita</span> <span class="keyword parmname">--input</span>=<span class="ph filepath">topic.dita</span> <span class="keyword parmname">--resource</span>=<span class="ph filepath">keys.ditamap</span> <span class="keyword parmname">--format</span>=<span class="keyword option">html5</span></code></pre>
    378. 

  378.             </div></dd>
    379. 

  379.         
    380. 

  380.         
    381. 

  381.           <dt class="dt pt dlterm">
    382. 

  382.             <span class="keyword parmname">--temp</span>=<var class="keyword varname">dir</var></dt>
    383. 

  383.           <dt class="dt pt dlterm">
    384. 

  384.             <span class="keyword parmname">-t</span>
    385. 

  385.             <var class="keyword varname">dir</var>
    386. 

  386.           </dt>
    387. 

  387.           <dd class="dd pd">Specifies the location of the temporary directory.</dd>
    388. 

  388.           <dd class="dd pd ddexpand">This argument corresponds to the common parameter <span class="keyword parmname">dita.temp.dir</span>.</dd>
    389. 

  389.         
    390. 

  390.         
    391. 

  391.           <dt class="dt pt dlterm">
    392. 

  392.             <span class="keyword parmname">--verbose</span></dt>
    393. 

  393.           <dt class="dt pt dlterm">
    394. 

  394.             <span class="keyword parmname">-v</span>
    395. 

  395.           </dt>
    396. 

  396.           <dd class="dd pd">Verbose logging prints additional information to the console, including directory settings, effective
    397. 

  397.             values for Ant properties, input/output files, and informational messages to assist in troubleshooting.</dd>
    398. 

  398.         
    399. 

  399.       </dl>
    400. 

  400.     </section>
    401. 

  401.   </div>
    402. 

  402. <nav role="navigation" class="related-links"><div class="familylinks"><div class="parentlink"><strong>Parent topic:</strong> <a class="link" href="../parameters/index.html" title="You can adjust DITA Open Toolkit behavior via dita command arguments and options, DITA-OT parameter settings, and configuration properties.">DITA Open Toolkit parameters</a></div></div><div class="linklist reltasks"><strong>Related tasks</strong><br><ul class="linklist"><li class="linklist"><a class="link" href="../topics/build-using-dita-command.html" title="You can generate output using the dita command-line tool. Build parameters can be specified on the command line or with .properties files.">Building output using the dita command</a></li><li class="linklist"><a class="link" href="../topics/using-dita-properties-file.html" title="Usually, DITA builds require setting a number of parameters that do not change frequently. You can reference a set of build parameters defined in a .properties file when building output with the dita command. If needed, you can override any parameter by specifying it explicitly as an argument to the dita command.">Setting build parameters with .properties files</a></li></ul></div><div class="linklist relref"><strong>Related reference</strong><br><ul class="linklist"><li class="linklist"><a class="link" href="../parameters/parameters_intro.html" title="Certain parameters apply to all DITA-OT transformations. Other parameters are common to the HTML-based transformations. Some parameters apply only to specific transformation types. These parameters can be passed as options to the dita command using the --parameter=value syntax or included in build scripts as Ant properties.">DITA-OT parameters</a></li><li class="linklist"><a class="link" href="../parameters/internal-ant-properties.html" title="Reference list of Ant properties used by DITA-OT internally.">Internal Ant properties</a></li></ul></div></nav></article></main></body></html>
    403.