-
-
Notifications
You must be signed in to change notification settings - Fork 503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation in additional format #38412
Comments
PR to add support for additional formats would be welcome. I think |
Is there a way to run sage_docbuild without building all of sage? I have run into issues building sage from source, see #38424 The repository checkout has a sage executable but
complains that,
|
I have managed to install sage and I am trying to build html documentation to test the waters. Some observations:
|
See #21734 for an old attempt. I would be extremely grateful for that! |
I tried searching for a previous issue but I didn't find it. Since the other issue has many more details, I will close this one comment on the other one. |
Problem Description
I was looking to build sage documentation in a way that I can work easily with in Emacs. The page https://doc.sagemath.org/html/en/developer/sage_manuals.html#building-the-manuals states that
However,
results in an error,
And,
tell me that,
so texinfo is probably not supported.
However, it would be nice to support it. I can run
sphinx-build -M info /path/to/doc/en/references outputdir
, but that doesn't build a complete manual since it doesn't process the nested directories.Is there a reasonable way to build an info manual out of sage documentation? With some pointers I can look into it myself.
Proposed Solution
A way to build an info manual using sage --docbuild.
Alternatives Considered
An alternative is to use the devhelp format. Since Emacs has packages that support that. However, passing devhelp as the format results in the same error as texinfo.
Additional Information
No response
Is there an existing issue for this?
The text was updated successfully, but these errors were encountered: