Add Texinfo support #1408
Add Texinfo support #1408
Conversation
support/docbook-xsl/texinfo/docbook.xsl can be used to transform a limited subset of Docbook into Texinfo.
By default, we now build the specification in texinfo format in addition to PDF, HTML, and single HTML. In addition to that, the lang.docinfo.install target can be used to install the specification into the system's info directory.
|
NB: for this to work you need to have |
|
Is that not installed by default on most Linuxes? |
|
It wasn't on mine (Fedora 21) |
|
btw to test I had to type |
|
so you didn’t install it? |
seems to be part of the |
I ran the "ant" command just as you describe above |
This one should install it in your global info directory. Needs |
|
I don't think the "sudo" command got executed at all |
|
Does it ask you for credentials when you run that task? |
|
yes |
|
Wtf? IT's because you put But then why does it even get to the doc generation? |
|
…oops :D sorry, but does it work with |
|
yup |
|
ok good I should probably do something in |
|
Although I'm thinking of just doing an |
| depends="lang.docinfo" | ||
| if="hasInfo"> | ||
|
|
||
| <exec executable="sudo" dir="${build.dir}/${lang}/info/"> |
There was a problem hiding this comment.
You guys are not seriously considering running sudo in a build file, are you? That's a big veto from me.
There was a problem hiding this comment.
You need root permissions to install the info file. Same as the ancient
./configure
make
sudo make install
There was a problem hiding this comment.
Is there a MANPATH analog, like INFOPATH, that can be used instead? Seems like this should go in the dist folder, along side bin.
There was a problem hiding this comment.
Well, do you notice how it should be the user who explicitly runs sudo and not make?
Not only that, but I'd want to install to my user info path, not the system, like we do for the rest of the publish commands.
There was a problem hiding this comment.
@jvasileff yes, it’s actually called INFOPATH :) however, if it’s unset, info falls back to a compile-time default (usually /usr/share/info), which I don’t think we can determine.
@FroMage Is there a user info path? I can’t find it. Of course, you can make it yourself with INFOPATH, but it doesn’t seem to be intended in info’s design.
There was a problem hiding this comment.
Indeed. For now I removed the use of sudo and added a check for root rights to the install task
There was a problem hiding this comment.
@lucaswerkmeister best open an issue in ceylon-dist so we don't forget to add this to the debian/redhat packages
There was a problem hiding this comment.
Alright, thanks.
There was a problem hiding this comment.
There was a problem hiding this comment.
In the end I decided to remove the install task entirely, it just has no business being there ^^
I wrote some XSLT stylesheets that transform the spec’s Docbook into Texinfo.
To test it, run:
and then you can view the specification with
or
We could also add Texinfo→HTML and Texinfo→PDF transformation, but that’s kinda pointless, since we already have those two formats, and the Texinfo version looks worse.
Note: this pull request also contains the commit from #1407 (closes #1407), since it’s required for this to work (all nodes need to have IDs).