Ok, it compiles, but the intrinsic attribute substitutes to the empty
string.
Also, if I try to use {docname} in the title (first line of the file) I get
an error message:
asciidoc: ERROR: test.txt: line 2: undefined attribute in manpage title
asciidoc: FAILED: test.txt: line 2: unexpected error:
asciidoc: ------------------------------------------------------------
Traceback (most recent call last):
File "../asciidoc-8.6.9/asciidoc.py", line 5944, in asciidoc
has_header = document.parse_header(doctype,backend)
File "../asciidoc-8.6.9/asciidoc.py", line 1592, in parse_header
Header.parse()
File "../asciidoc-8.6.9/asciidoc.py", line 1822, in parse
if mantitle == mantitle.upper():
AttributeError: 'NoneType' object has no attribute 'upper'
Attached is the .txt file I used.
The version of asciidoc I used is 8.6.9.
This is the command I used:
asciidoc.py -o test.xml -b docbook -d manpage test.txt
Best Regards, Magnus
Den fredagen den 6:e juni 2014 kl. 11:53:58 UTC+2 skrev Lex Trotman:
>
> Works for me.
>
> Please post a *minimal* example that fails, the version of asciidoc
> and the command(s) you run.
>
> Cheers
> Lex
>
> On 6 June 2014 18:19, Magnus Höglund <[email protected] <javascript:>>
> wrote:
> > I have a very specific problem regarding the manpage document type.
> >
> > I try to use the {docname} intrinsic (or any other attribute which holds
> the
> > name of the .txt-file) to set the name title to the same as the file
> name of
> > the asciidoc source file.
> >
> > The reason I want to do this is because I have a lot of commands to
> write
> > man pages for, and therefore I wish to automate the process a little by
> > inserting the file name (without the .txt extension) from attributes.
> >
> > I know that the NAME section has very specific requirements, but why
> can't I
> > put attributes in the title paragraph?
> >
> > However, it seems I can use the {sys:<command>} intrinsic, but why not
> any
> > other?
> >
> > Best Regards, Magnus
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups
> > "asciidoc" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an
> > email to [email protected] <javascript:>.
> > To post to this group, send email to [email protected]
> <javascript:>.
> > Visit this group at http://groups.google.com/group/asciidoc.
> > For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"asciidoc" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/asciidoc.
For more options, visit https://groups.google.com/d/optout.
ft_fpga(1)
===========
NAME
----
{docname} - Reads or writes EPB2 FPGA registers
SYNOPSIS
--------
*{docname}* ['OPTIONS'] 'FILE'
DESCRIPTION
-----------
The {docname} command reads or writes EPB2 FPGA registers via SPI
interface. The SPI interface is only connected to the primary T4240
so this command will not work on the secondary processor.
OPTIONS
-------
*-c, --dump-conf*::
Dump configuration to stdout.
*--version*::
Print program version number.
[[X1]]
PLUGIN COMMANDS
---------------
EXIT STATUS
-----------
*0*::
Success
*1*::
Failure (syntax or usage error;
unexpected error).
BUGS
----
See the ft_fpga distribution BUGS file.
AUTHOR
------
ft_fpga was originally written by Magnus Undin.
RESOURCES
---------
Main web site: <http://ft-fpga.org/>
COPYING
-------
Copyright \(C) 2014 Magnus Undin. Free use of this software is
granted under the terms of the GNU General Public License (GPL).
