I've pushed a few more commits to my htexdoc branch.
5fd285c use ViewportPage1 instead of mobius
543677f transform "\lispmemolink{X}{Y}" to "[X]"
e4a7fe9 remove redundant .help files
9c102be remove unused .ht files
2eb8343 XVFB runs concurrently
> I am definitely against removing "Stand-alone Viewport" for such a
> (non)reason.
See commit 5fd285c.
The only problem now is that when I go to
Topics -> Graphics -> Old Framework -> Viewports
and click on "ViewButton" in section "Creating Viewport Buttons", the
console shows
(1) -> viewAlone called with argc=2
viewAlone called with
argv[1]=/home/hemmecke/g/fricas-bisect/install/lib/fricas/target/x86_64-unknown-linux/bin/viewAlone
viewAlone called with
argv[2]=/home/hemmecke/g/fricas-bisect/install/lib/fricas/target/x86_64-unknown-linux/share/viewports/ViewportPage1
filename =
/home/hemmecke/g/fricas-bisect/install/lib/fricas/target/x86_64-unknown-linux/share/viewports/ViewportPage1.VIEW/data
viewType = 1
calling spoonView3D
viewAlone:
/home/hemmecke/g/fricas-bisect/fricas/src/graph/viewAlone/spoonComp.c:208:
makeView3DFromFileData: Assertion `fricas_sprintf_actual_size >= 0 &&
fricas_sprintf_actual_size < fricas_sprintf_buffer_size' failed.
>> I'll also go over the src/hyper/pages/*.ht files. Many of them are
>> now redundant.
> I prefer to separate changes to build process and changes to the
> content.
Oh, I haven't made considerable changes to the content. Up to now it's
mainly fixing typos. I've backported your changes from the .ht files to
the .htex files. So the generated .ht files should basically be the same.
The real change would be to go over the two "What's new" sections.
Maybe the resulting files are not in the same directories, but filenames
should be the same.
> I think it is worth looking at tex4ht.
Yes and no. I've done aldor-combinat with tex4ht and know how it works,
but it's quite some work to make the pages look nice. I'm rather
thinking of pandoc. tex4ht would only be an intermediate solution. But I
would have to generate the .tex version first. However, the latter is
unrealistic until your release date.
> I would rather avoid tex4ht as a runtime dependency, but it could be
> useful for generating .html version form .htex -- this could be done
> when creating release tarball, so there would be no requirement for
> tex4ht when building releases.
Are you insisting on HyperDoc? I'd rather be in favour of using pandoc
to make a one-time transformation from .htex (which is nearly .tex) into
.rst (restructured text). That is almost ASCII, so hopefully even
readable without webbrowser. From .rst it's easy to produce nicely
looking webpages via Sphinx.
My main usage of HyperDoc is the API browser. HyperDoc will still exist
for some more time, since I have not yet any idea to generate an API
documentation which even works on the fly as HyperDoc does now.
Ralf
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" 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/fricas-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
