{"id":18974538,"url":"https://github.com/m7a/bp-d5man-legacy","last_synced_at":"2026-04-08T15:30:20.073Z","repository":{"id":164554579,"uuid":"225728193","full_name":"m7a/bp-d5man-legacy","owner":"m7a","description":"Ma_Sys.ma D5Man Legacy Distribution: Provides a way to export (legacy) D5I files to PDF","archived":false,"fork":false,"pushed_at":"2024-04-28T19:34:48.000Z","size":246,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":2,"default_branch":"master","last_synced_at":"2025-01-01T09:08:16.978Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"Java","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/m7a.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2019-12-03T22:17:54.000Z","updated_at":"2024-04-28T19:34:52.000Z","dependencies_parsed_at":"2024-04-28T20:42:33.193Z","dependency_job_id":null,"html_url":"https://github.com/m7a/bp-d5man-legacy","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/m7a%2Fbp-d5man-legacy","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/m7a%2Fbp-d5man-legacy/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/m7a%2Fbp-d5man-legacy/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/m7a%2Fbp-d5man-legacy/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/m7a","download_url":"https://codeload.github.com/m7a/bp-d5man-legacy/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":239972088,"owners_count":19727305,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-08T15:15:22.489Z","updated_at":"2026-04-08T15:30:20.009Z","avatar_url":"https://github.com/m7a.png","language":"Java","funding_links":[],"categories":[],"sub_categories":[],"readme":"---\nsection: 32\nx-masysma-name: d5man/legacy\ntitle: D5Man Legacy Distribution\ndate: 2019/11/28 09:30:31\nlang: en-US\nauthor: [\"Linux-Fan, Ma_Sys.ma (Ma_Sys.ma@web.de)\"]\nkeywords: [\"d5man\", \"legacy\", \"d5manexport\", \"d5man2xml\", \"format\", \"d5man/format\"]\nx-masysma-version: 1.0.0\nx-masysma-repository: https://www.github.com/m7a/bp-d5man-legacy\nx-masysma-website: https://masysma.net/32/d5man_legacy.xhtml\nx-masysma-owned: 1\nx-masysma-copyright: |\n  Copyright (c) 2014--2019 Ma_Sys.ma.\n  For further info send an e-mail to Ma_Sys.ma@web.de.\n---\nOverview\n========\n\nThis is the D5Man Legacy Distribution. It contains a subset of the programs and\nscripts developed for the first attempt on realizing a comprehensive information\nstorage system.\n\nThis distribution focuses on the old system's LaTeX/PDF export capabilities and\nincludes a new script `d5manlegacyconvert.pl` to conveniently invoke the\nexport functions automatically generating the necessary D5Man configuration for\nexporting a given file. Not all functions were retained for the following\nreasons:\n\n * Simplifying compilation and invocation (all database-related parts and\n   external library dependencies have been ellided).\n * Removing features which are very likely not useful\n * Removing overly incomplete/very instable features\n\nThe primary reason for giving up on the old D5Man's development was exactly the\nhigh complexity and instability of features, thus this legacy distribution\naims at reducing the complexity and providing only features with some extent\nof stability such as to conserve a means of processing legacy documents.\n\nThe following functions are provided:\n\n * PDF export of a single page\n * XHTML export of a single page\n * XSLT stylesheet application for a single page\n * automatic attachment conversion using the `rsvg-convert` command.\n * D5Man legacy format to XML conversion using `d5man2xml`\n\nThe following functionality is still present but not exposed through any\nconvenient interface:\n\n * `d5manioresolve` utility to locate a D5Man file based on its page name\n * `d5manexport` utility including the code for mass-exporting multiple pages\n\nThe following functions were available and removed from the distribution:\n\n * `d5manserver` for live-serving exported pages\n * `d5manmirror` for uploading exported pages via FTP\n * `d5mandb*` commands for managing the D5Man database.\n * `d5manui` and `d5manquery` commands for querying the D5Man database\n   (interactively)\n * `d5manview` VIM plugin for syntax highlighting, generation of headings and\n   automatic invocation of `d5mandbsync` on page save.\n * `d5mandetach` for operating D5Man in a separate temporary environment.\n   This is the default mode of operation for the functionality provided by this\n   repository.\n\nThe following functions were never completed and are thus not available in\nthe distribution either:\n\n * `d5manvalidate` for mass-checking syntax and metadata consistency of all\n   pages\n * `d5manimport` for importing large pieces of information (e.g. JDK API\n   Documentation) into the D5Man system by converting all source pages to D5Man\n   pages.\n\nCompilation and Dependencies\n============================\n\n## Dependencies\n\n### Building\n  * Ant\n  * GCC (C89 compilation)\n\n### Building and Running\n  * Java 7 (or higher, tested with Java 8)\n\n### Running\n  * POSIX `make`\n  * LaTeX\n  * Perl\n\n## Compilation\n\nCompile as follows:\n\n\t$ ant\n\nInstall by building a package (works on Debian with `debuild`):\n\n\t$ ant package\n\nRun the installed package by invoking\n\n\t$ d5manlegacyconvert\n\nIf the package is to be run without being installed, provide the following lines\nin `d5manlegacyconvert.pl`:\n\n~~~{.perl}\nmy %conf = (\n\tcommon_res      =\u003e \"./d5manlegacycommonres\",\n\tcompl_a         =\u003e \"$newr/root\", # XML: io_compl_a / io_compl_b\n\tcompl_b         =\u003e \"$newr/root\",\n\td5man2xml       =\u003e \"./d5manlegacy2xml/d5manlegacy2xml\",\n\tdb_search       =\u003e \"$newr/d5man.conf\", # XML: dbloc_real\n\tdb_sync         =\u003e \":\",\n\tfile_root       =\u003e \"$newr/root\",\n\tio_resolver     =\u003e \"./d5manlegacyioresolve/d5manlegacyioresolve\",\n\tmedia_converter =\u003e \"/usr/bin/rsvg-convert -f pdf /dev/stdin\",\n\tvim             =\u003e \"/usr/bin/vim\",\n\tvim_plugin      =\u003e \"$newr/d5man.conf\",\n);\n~~~\n\nThis shows a definition of the binaries relative to the present working\ndirectory which may suffice if `d5manlegacyconvert.pl` is invoked from the\nrepository's directory. Although never tested, replacing the calls to\n`/usr/bin/vim` etc. with suitable Windows paths may make this functionality\navailable on Windows as well (`vim` is only ever called for XHTML exports).\n\n## Usage\n\nAlthough there might be little point in running such a “legacy” software, one\ncan test the functionality of the program by providing a sample page (e.g.\n`test.d5i` and invoking it as follows. See the _Legacy D5Man Format and Design_\nsection for an example file.\n\n\t$ d5manlegacyconvert test.d5i\n\nThis should produce file `test.pdf` corresponding to the input file.\n\nLegacy D5Man Format and Design\n==============================\n\nThis section captures the definition of the legacy D5Man format in its original\ntext which includes some reasoning about why the specific format was chosen.\nThe part about the use of D5Man sections has been removed due to being\ninconsistent.\n\n## Motivation\n\nManpages can be considered one of the most efficient, useful and most reliable\nway of storing textual information. Their features, however, are severely\nlimited making Manpages a bad choice for information to be displayed online or\nin print form. Also, Manpages are designed to be distributed as part of a\nprogram package which means that there is no workflow to edit them immediately\nand efficiently.\n\nApart from Manpages there are LaTeX and XHTML documents each of which is\ndesigned to be either used for printing or for the web. Although both of those\nare useful means of storing information, especially XHTML as webbrowsers are\nalmost omnipresent, they remain limited to specific target devices and have\ntheir own disadvantages.\n\nThe D5Man format has been designed to overcome many of the existing limitations.\nFor each format, the major disadvantages are listed below\n\n### Manpages\n  * limited formatting options\n  * not to be edited by the user\n  * unreadable markup language\n  * sections are designed to be used specifically with UNIX systems\n\n### Websites (XHTML+CSS)\n  * no simple means of rendering (Webbrowser with 300 MiB or more RAM required)\n  * focuses too hard on layout, too little on content\n  * the markup is not nice to read\n\n### LaTeX\n  * rendering on textual devices is theorethically possible but there exist few\n    tools to handle this situation\n  * not useful for web based applications\n  * difficult to process automatically (consider multiple pdfLaTeX runs for\n    instance)\n\nConcerning the difficult readability of known markup formats, many alternatives\nhave emerged. Among the most popular is Markdown which is focused on websites.\nAmong the best of these formats are\n[reStructuredText](http://docutils.sourceforge.net/rst.html) and\n[Grutatxt](http://triptico.com/docs/grutatxt_markup.html). While both of them\nare really good, there are minor disadvantages: reStructuredText can become\ndifficult to read once links are involved and Grutatxt is a bit too simple for\nthe task.\n\nExtracting the best experiences from all these formats, the D5Man format has\nbeen developed.\n\nThe following ideas have been taken from the other formats\n\n * a readable markup language (mainly taken from Grutatxt)\n * a means of controlling typographic specialities like half spaces and forced\n   spaces (from LaTeX)\n * a predefined document structure (inspired by Manpages)\n * sectioning after topic (taken from the Manpages)\n * advanced metadata (taken from XHTML compare `\u003cmeta .../\u003e`)\n\nUsing this combination, the following new features have become possible\n\n * D5Man Pages can be rendered nicely in\n    * Browsers (like XHTML)\n    * Terminals (like Manpages)\n    * and printed on paper (like LaTeX)\n * D5Man Pages can be edited WYSIWYG as the format is so readable the user can\n   be trusted to view it directly.\n    * This is further enhanced using syntax highlighting\n * Unlike Manpages or anything else, we do not even need an own program to read\n   the files: VIM can do the job very well and if it is not at hand, any text\n   editor may do.\n\n## Main Elements\n\nThe D5Man format supports the following constructs.\n\nMetadata\n:   A D5-Manpage starts with metadata in a key-value syntax with a tab\n    separator. Tabs can be repeated as is necessary for a suitable\n    representation in your editor. Configure your editor to use 8 spaces per\n    tab.\nText\n:   Text can be entered without special attention. `\\`` can be used to\n    encode inline code, commands and filenames (just about any single words\n    you would typeset in teletype font). Quotation is entered the same way\n    as in LaTeX.\nEscaping\n:   `\\` is used to escape characters if necessary. This allows “`{`” and\n    similar characters to be entered directly. Be aware that escaping\n    basically tells the parser to just “ignore” any functionality this\n    character might have. Thus, if you want to write a text and make\n    an immediate note in parenthes you only need to excape the\n    first character, because that is the one the parser uses to find links.\n    Example: “`HTML\\(5) expert`”.\nExternal Markup\n:   Although often unreadable, a plaintext-like markup format can not avoid\n    interfacing with other markup languages: Using the “LaTeX”-Brackets\n    `{` and `}` one can encapsulate LaTeX and XML using `{\u003c ` and ` \u003e}`\n    (note that the first has a trailing, the second a leading space). If\n    the TeX Math-Mode is entered immediately after the opening bracket,\n    it can also be processed for website generation.\nRaw text (“Code”)\n:   Text which is indented from the left and not part of a list or table is\n    considered raw text. The initial level of indentation will be removed\n    and the text will otherwise be left untouched.\nLinks\n:   Links can be made in several forms. You can either link to a D5-Manpage\n    by entering the name and section in parentheses without a separating\n    space. Otherwise you enter the text you want to link and then give the\n    URL in parentheses and as a third possibility you can just use\n    `url(http://...)` to link to a specific URL.\nLists\n:   There are four types of lists which can be nested, except for\n    description lists: You can create unordered lists prepending the `*`\n    character to your text. Lists are nested via suitable indentation.\n    Numbered lists use numbers and a `.` to number the elements just like\n    expect them to be used and definition lists are simply a term followed\n    by a newline and an indented description. The fourth type of list is a\n    so-called “pro-contra” list which you create by using appropriate `+`\n    and `-` signs as your list bullet. Nesting description lists with a\n    single element and unordered lists is so common that such lists are\n    specially treated and called ``titled'' lists. All list types except for\n    description lists have to be indented.\nTables\n:   Tables use `o` to mark the top and bottom rule and `+` to create a mid\n    line. Fields are separated with two spaces.\nSections\n:   A section consists of `-` signs from the very beginning of a line then\n    a `[`, a space, the section title another space and a terminating\n    `]--\\n`. You can also create one level of subsections by creating a\n    line of text which is underlined with dashes (just like the old\n    Ma_Sys.ma Note Format).\nEmphasizing\n:   Put emphasis on important text by surrounding it with underscores (`_`).\n    Emphasis is not recognized _inside_ a word because you need to be able\n    to enter things like “Dev_Swap”, “Ma_Zentral” or “Ma_Sys.ma”\nShortcuts\n:   Whenever keyboard shortcuts are to be entered, the necessary keys can\n    be encoded like `[CTRL]-[X]` to display them as key symbols.\nSubstitution\n:   Special words and parts of text are automatically replaced whith nicer\n    symbols for rendering. The table “Symbol replacement” lists all common\n    substitutions.\nSpace control\n:   Just like in LaTeX, you can enter forced half spaces using `\\,` and\n    forced spaces using `~`.\n\n### Symbol replacement\n\nText         LaTeX            Symbol\n-----------  ---------------  ----------\n`...`        `\\dots`          ...\n`=\u003e`         `$\\Rightarrow$`  ⇒\n`-\u003e`         `$\\rightarrow$`  →\n`\u003c-`         `$\\leftarrow$`   ←\n`2^3`        `$2^3$`          2³\n` :) `       (smiley)         :)\n`3 e {4,5}`  `$3\\in\\{3,5\\}$`  3 ∈ \\{3,5\\}\n\n## Universal External Markup\n\nThe external markup described in this section is recognized by all renderers\nexcept for WYSIWYG.\n\n`{\\\\img{file}{caption}}`\n:   Inserts the image attachment file `file` and associates the textual\n    caption `caption`\n`{\\\\code{language}}`\n:   Helps the renderer to understand the source code language of following\n    codes, i.e. enables syntax highlighting.\n`{$...$}`\n:   Math-mode-only is also specially recognized.\n\n## Meta fields\n\nAfter the fields, a meta section may contain any number of LaTeX commands\nwhich are executed before any other LaTeX is processed. If the commands are\nall written between `\u003c` and `\u003e` symbols, they are processed as XHTML instead.\n\n`name` (REQ)\n:   An internal name for the page. Use `[0-9a-z_/]+` only.\n    Imported pages are allowed to also use upper case letters, dots and\n    hyphens.\n`section` (REQ)\n:   A numeric meta field to define the `d5man` section. Use `-1` for TBD.\n`description` (REQ)\n:   A plaintext description which may not contain control sequences.\n`tags` (REQ)\n:   Associates tags (form `[0-9a-z_]+`) separated with spaces.\n    Tags are used to find the document through the different D5Man search\n    functions like the UI, generated websites and `d5manquery`.\n`encoding` (RC)\n:   Either `utf8` (`UTF-8`, `utf-8`) or `ascii` (`ASCII`). Defaults to\n    `utf8`. _WARNING_ The field exists for future usage and reader\n    information but is not evaluated by any D5Man applications which are all\n    programmed to support UTF-8 and UTF-8 only\n`compliance` (REQ)\n:   One of (becoming more and more public) `qqvx`, `qqv`, `secret`,\n    `restricted`, `confidential`, `personal`, `internal`, `prerelease`,\n    `informal`, `public`. Informal and public texts are allowed to be\n    published on the internet. Prerelease texts are designed to be published\n    sooner or later, internal texts may be shared but not be publicly\n    available on the internet, personal texts might be shared but should not\n    be included in IAL or Ma_Zentral DVDs, restricted texts are not to be\n    shared, secret texts need special care and the two levels below _must_\n    be encrypted.\n    Repeat: public and informal are online, internal are in Ma_Zentral and\n    MDVL, the rest not.\n`lang` (REQ)\n:   The language the text is written in. This may either be `en` for English\n:   or `de` for German. The possibility to use `it` and `fr` is planned.\n`creation` (RC)\n:   Time of creation (`YYYY[/MM[/DD [HH:mm[:ss]]]]`).\n`copyright` (OPT)\n:   A copyright statement. The copyright statement may span across multiple\n    lines (with the same indentation).\n`version` (OPT)\n:   Version information in any application-specific format.\n`expires` (OPT)\n:   Expiration date. Expiration is not defined as the document becoming\n    automatically obsolete, but rather intended to be a sort of\n    “review required”. Interpretation and usage are up to the user.\n    Expired documents can be queried with `d5manquery -e`\n`location` (OPT)\n:   Redirects D5Man to another page. This may be a `file://` URL which is\n    then opened with the default browser.\n    (_This field was never implemented in legacy D5Man, but the new\n    D5Man processes `x-masysma-redirect` fields with similar semantics_).\n`attachments` (OPT)\n:   Space separated list of files considered attachments. These may be\n    useful for enhancing websites and LaTeX targets w/ resource files.\n`web_freq` (OPT)\n:   Change Frequency (always, hourly, daily, weekly, monthly, yearly, never)\n    for website XML-sitemaps.\n`web_priority`\n:   Page priority ]0;1[ for website XML-sitemaps.\n\n## Download Fields\n\nIn addition to the fields listed above, there are some fields which are\nspecially designed to be used in conjunction with the Website export to\nspecify a “download” attached to a page. Unlike an `attachment`, these\ndownloads are given by URL and not by relative resource. Thus, these fields\nare useful for external mirror links as well. Download URLs may not contain\nspaces (use URL-encoding if spaces are required).\n\nFinally, pages can support multiple downloads by giving them numbers starting\nfrom 0 or 1 (a digit appended to all download field names, like e.g. `download1`\nand `dlink1` for the second download etc.). If this feature is used, all\ndownloads must be ordered by their number, i.e. all fields for `download1`\noccur before any field for `download2` etc. As download numbers are digits,\na maximum of ten downloads (0-9) is supported per page. If the number is\nomitted (as is useful for only a single download), the number 0 is assumed.\n\nDownloads can also be “imported/linked” from other pages by referencing their\npage name and the download name (as given in the table). These references'\nnumbers are ignored and they do not count to the limit of ten downloads per\npage.\n\n### Additional Fields for Website Downloads\n\nField       Description\n----------  -----------------------------------------------------\n`dref`      Reference other download in form `page(section)/name`\n`download`  Declares a download (internal name)\n`ddescr`    Download description / title (UI name)\n`dlink`     Target URL (or JavaScript link etc.)\n`dsize`     Download size in KiB\n`dchck`     Time last checked (format like `creation` field)\n`dver`      Download version (human readable format)\n`dchcksm`   SHA-256 of download contents\n\n## Example Document\n\nThis section shows a typical legacy D5Man document as a more intuitive\ndescription in addition to the format as described above.\n\n~~~\n--------------------------------------------------------------[ Meta ]--\n\nname\t\ttest\nsection\t\t42\ndescription\tD5Man Test Document\ntags\t\td5man detached legacy\ncompliance\tpublic\nlang\t\ten\ncreation\t2019/11/29 09:06:28\nversion\t\t1.0.0\n\n--------------------------------------------------------------[ Test ]--\n\nThis is a D5Man Legacy Format example showing some use of the features.\nFor the repository see url(https://github.com/m7a/bp-d5man-legacy).\n\nAdvantages of the Legacy Format\n + Allows for automatic symbol replacement: -\u003e is an arrow.\n + Allows for generation of quotation marks: ``quoted text''\n + Supports efficient inclusion of inline math:\n   {$f(x)=m\\cdot x+b$}\n + D5Man supports keyboard shortcuts in documentation. Press [CTRL]-[S]\n   to stop terminal output and [CTRL]-[Q] to resume.\n\nProblems with the Legacy Format\n - It is incredibly hard to parse\n - Nested lists are supported but need to strictly follow the syntax.\n   Odd things like numbered lists with more than 9 entries needing\n   leading zeroes to have all numerals being equally wide for instance.\n - There are some bugs in d5man conversion.\n - `e` for replacement by the ``in'' symbol was possibly not the\n   smartest choice. There used to be `E` for ``exists'' as well!\n\nFinally, this test document concludes with a table:\n\n        Overview on the executables in D5Man Legacy and New\n      ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo\n        Legacy Original       Legacy Distribution     New Distribution\n      +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n        `d5manui`             ~                       `d5mantui`\n        `d5manserver`         ~                       `d5manapi`\n        `d5man2xml`           `d5manlegacy2xml`       ~\n        `d5mancompliancedup`  ~                       ~\n        `d5mandbdelete`       ~                       ~\n        `d5mandbinit`         ~                       ~\n        `d5mandbsync`         ~                       ~\n        `d5mandelete`         ~                       ~\n        `d5mandetach`         ~                       ~\n        `d5manexport`         `d5manlegacyconvert`    `d5manexportpdf`\n        ~                     ~                       `d5manexporthtml`\n        `d5manexportautoftp`  ~                       ~\n        `d5manimport`         ~                       ~\n        `d5manioresolve`      `d5manlegacyioresolve`  ~\n        `d5manmassdelete`     ~                       ~\n        `d5manmirror`         ~                       ~\n        `d5manquery`          ~                       ~\n        `d5manvalidate`       ~                       ~\n      ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo\n~~~\n\nStructure of the Legacy Distribution\n====================================\n\nThis repository is structured as follows:\n\n`d5manlegacy2xml`\n:   Legacy `d5man2xml` application which takes as input a D5Man text\n    and produces in output a proprietary XML format for processing by other\n    D5Man-related tools (see\n    `d5manlegacyexport/ma/d5man/lib/dtd/d5manxml.dtd` for the associated\n    DTD including).\n`d5manlegacycommonres`\n:   Provides logos and resources needed for the export. File\n    `template.tex` is the LaTeX template used for the PDF export and\n    `website_fs_override` contains a template XML used for the XHTML\n    export.\n`d5manlegacyexport`\n:   Contains all Java parts of this distribution. This includes large parts\n    of the old `d5manexport` Java implementation and the `libd5manexport`\n    library. Parts relying on external components (such as SnuggleTex for\n    LaTeX to MathML conversion) have been removed.\n`d5manlegacyioresolve`\n:   Legacy `d5manioresolve` application for converting D5Man page names\n    to file names. This is retained because it is invoked by the D5Man\n    export to find the file names associated to input files.\n`stylesheets`\n:   Some sample XSLT styles to transform D5Man proprietary XML to\n    other text formats. These have been intended to be used in conjunction\n    with systems that in turn convert the text formats to HTML. As such, it\n    does not produce a _nice_ textual representation but one that will be\n    displayed correctly. Some of these conversions require manual\n    post-processing for optimal results.\n`d5manlegacyconvert.pl`\n:   Script to invoke the legacy export without needing to explicitly provide\n    all the D5Man file structure, database and configuration file\n    (configuration files and file structure are generated on-the-fly).\n\n`d5manlegacyconvert.pl`\n=======================\n\n## Name\n\n`d5manlegacyconvert` -- export legacy D5Man files to (mainly) PDF.\n\n## Synopsis\n\n\td5manlegacyconvert file.d5i [opt]\n\td5manlegacyconvert file.d5i xslt  style.xsl\n\td5manlegacyconvert file.d5i xhtml outdir    [opt]\n\n## Description\n\nOne and two argument invocation\n:   This script reads `file.d5i` and exports it to file.pdf. It implements a\n    functionality provided by legacy D5Man which is relevant for large\n    pieces of text which should remain exportable even after legacy\n    D5Man has been uninstalled. It simplifies the interface to the legacy\n    D5Man very much by performing all required actions (query, export, make)\n    in a single invocation.\nThree and four argument invocation\n:   This exposes the other parts export functionality. It is retained to be\n    able to invoke the XSLT transformation for legacy README-files and to\n    be able to simplify the transition of website contents.\n\n`[opt]` allows for optional arguments to be passed to the `d5manexport` process.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fm7a%2Fbp-d5man-legacy","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fm7a%2Fbp-d5man-legacy","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fm7a%2Fbp-d5man-legacy/lists"}