Closed sunderme closed 1 year ago
there are a few points i want to achieve and maybe someone can help.
destroyed my bookmark chapter, please fix:
https://github.com/texstudio-org/texstudio/pull/2607#issuecomment-1257010002 , furo looks interesting. For now the usermanual_en.md is written as markdown. Let's see what is the best way to get a html out of it.
your images look quite oversized. Ex. quickstartwizard is 1050 pixels wide, more than half of a FullHD display. Image info shows 144dpi. It should be rendered at about 96dpi (67%).
#2607 (comment) , furo looks interesting. For now the usermanual_en.md is written as markdown. Let's see what is the best way to get a html out of it.
Here is a proof of concept with (a minimal configuration of) Sphinx-doc
as documentation generator and usermanual_en.md
as source file (as it is: could be improved):
Furo
as theme): https://dbitouze.gitlab.io/texstudio-manual/usermanual_en.html
usermanual_en.md
as source file (as it is: could be improved)
I meant, from the Sphinx-doc
point of view.
I also forgot to give the link to the source: https://gitlab.com/dbitouze/texstudio-manual
I tried to use sphinx here. Apparently it is a bit tricky on ubuntu (20.04) as the extensions are not present and it failed. I can get a very similar output with pandoc alone which is less complicated. So for now, I will generate the helpfile this way, but that does not mean we can't change it later as the source is the same anyway.
I tried to use sphinx here. Apparently it is a bit tricky on ubuntu (20.04) as the extensions are not present and it failed.
Here is a procedure that worked for me in a VM with Ubuntu 22.04:
sudo apt-get install python3-pip python3-dev python3-setuptools apache2 -y
pip3 install --upgrade pip
pip3 install sphinx
pip3 install myst_parser
pip3 install sphinx_comments
pip3 install sphinx_design
pip3 install sphinxext.opengraph
pip3 install furo
mkdir ~/tmp
cd ~/tmp
wget https://gitlab.com/dbitouze/texstudio-manual/-/archive/main/texstudio-manual-main.tar.bz2
tar xvfj texstudio-manual-main.tar.bz2
mkdir texstudio-manual
cd texstudio-manual
~/.local/bin/sphinx-quickstart # Answer `y` at the first question and whatever you want
# at the subsequent questions (the answers will be erased by the
# configuration file I provide).
mv -f ~/tmp/texstudio-manual-main/source/* source/
sed -E -i 's#sphinx-build#~/.local/bin/sphinx-build#g' Makefile
make html
xdg-open build/html/usermanual_en.html
for whatever reason, pip install failed here.
But from what I see, it is not really necessary to run sphinx more than once. The only important part seem the template for pandoc and the css file (and js possibly).
My current approach is an adaptation of https://github.com/Mushiyo/pandoc-toc-sidebar and this seems to be sufficient.
With pandoc present, you only have to call convertToHTML.sh
in texstudio/utilities/manual
.
Here is a procedure that worked for me in a VM with Ubuntu 22.04:
I forgot the process for the PDF output format::
cd ~/tmp/texstudio-manual
make latexpdf
xdg-open build/latex/texstudio.pdf
My current approach is an adaptation of https://github.com/Mushiyo/pandoc-toc-sidebar and this seems to be sufficient.
But, this way, you cannot get PDF output format.
for whatever reason, pip install failed here.
Probably easy to fix.
pandoc can deliver pdf as well (via latex) and it looks okay. The important part is to have a markdown source file, that we can transform in all outputs, one way or another. For html output, I would prefer a pandoc only approach as set-up seems to be easy enough on any system. You can still let run sphinx for a more fancy output.
pip upgrade did the trick
@dbitouze building the html locally, there is a second toc to the right. That is actually quite useful as it is more detailed than the one on the left. However it does not scroll with the text, i.e. when the entry is outside of the current view, it does not scroll there. This may or may not be desirable ? Anyway, the search box seems to be pretty useless for single page document. The comment function should not be there as it links to an external site. Otherwise looks quite nice.
@dbitouze building the html locally, there is a second toc to the right.
Interestingly, my local build doesn't provide such a local ToC but, indeed, there are provided for another project (a French LaTeX FAQ), e.g. https://dbitouze.gitlab.io/test-faq-fr/3_composition/tableaux/tableau_sur_plusieurs_pages.html
That is actually quite useful as it is more detailed than the one on the left. However it does not scroll with the text, i.e. when the entry is outside of the current view, it does not scroll there. This may or may not be desirable ?
In the link above, you can see that the local ToC does scroll with the text.
Anyway, the search box seems to be pretty useless for single page document.
There could be two versions of the manual: one with a single page embedded with TXS, and another one, online, with several pages (more friendly IMO).
The comment function should not be there as it links to an external site.
Again, could be useful for an online manual.
Otherwise looks quite nice.
OK.
I have split the help file and put everything together in https://github.com/sunderme/texstudio/tree/manual Maybe you can have a look ?
I have put it on github pages to test: https://sunderme.github.io/getting_started.html
I have put it on github pages to test: https://sunderme.github.io/getting_started.html
Very nice, thanks!
Some minor remarks after a quick overview:
\hline, %\s?[A-Z][A-Z_-]+
, etc.),IMO, sphinx-comments
is still useful since, used with e.g. https://web.hypothes.is/:
the whole manual is static with local resources, only the comments would break that. Especially as the manual is also installed locally on the user's computers.
the whole manual is static with local resources, only the comments would break that.
Is it a big deal?
Especially as the manual is also installed locally on the user's computers.
This would concern only the online version of the manual.
there is no "online" version of the manual, it is the same on the computer and on pages. In Germany, there was a successful law-suit that loading google fonts from google in the webpage was a violation of privacy, so I stay away from that as much as possible.
In Germany, there was a successful law-suit that loading google fonts from google in the webpage was a violation of privacy, so I stay away from that as much as possible.
AFAICS, no Google Font here.
./build/html/
, getiting_started.html
as entry point." of file Readme.mdRemarks on chapter Configuring TeXstudio:
Chapter Advanced features:
Chapter Background information:
Chapter Editing a Tex Document, section Formatting your text right at the beginning:
@sunderm I still wonder if the title should rather be "Welcome to TeXstudio's Manual" or "Welcome to TeXstudio's documentation". Current title seems to be a mixture of both. Is it intended?
[x] The image showing the context menu of the inline preview shows Clear In...e Preview instead of
[ ] The preview pane and it's context menu could be described/presented.
add to previous post:
The stop symbol is not a square, but it is in the images of chapter Getting started.
in my opinion, the main update work is done.
@sunderme Which of the following changes/additions to the manual do you (not) want to have? These are from my task lists above. Please leave comments:
And what about this? The texstudio.org page still shows user manual with link to old manual.
Thx
@sunderme Which of the following changes/additions to the manual do you (not) want to have? These are from my task lists above. Please leave comments:
1. As the group is called _Menus_ the section should be _Configuring the Menus_. Seems to be reasonable since configuration of all menus is possible, not only math and latex. 2. As the group is called _Toolbars_ the section should be _Configuring the Toolbars_. Seems to be reasonable since configuration of all toolbars is possible, not only for custom toolbar. 3. Add a note that changing shortcuts is a little bit different for Editor/Basic Key Mapping: Only _Current Shortcut_ can be changed, no _Additional Shortcut_ is possible.
And what about this? The texstudio.org page still shows user manual with link to old manual.
Thx
I have implemented the changes. texstudio.org will be updated with the next release.
[x] One "be" to much in
The appropriate item can be be directly edited by double-clicking on them.
(s. Configuring the Menu).
[x] You typically write toolbar in one word, for example in the heading (s. parentheses at the end here) or in the first sentence, but not in "user tool bar":
TeXstudio can adapt all toolbars with actions from the menus. A “user tool bar” is empty by default
(s. Configuring the Toolbar). Is it intended?
s. here
@sunderme Shouldn't there be a md file for each html file, as it is for configuration.html? 8066ab7075c7a6205dcacc113974b092eea0a799
I think that these files will be overwritten when the manual is generated the next time.
@sunderme In chapter Editing a TeX Document -> Special Commands -> Rename Environment:
there is no "online" version of the manual, it is the same on the computer and on pages. In Germany, there was a successful law-suit that loading google fonts from google in the webpage was a violation of privacy, so I stay away from that as much as possible.
A drawback of not providing an online manual is that the one coming with TXS has a search box which doesn't work.
And TXS would be I guess the single software in the world that doesn't provide an online version of its manual...
there is an online version of the manual (https://texstudio-org.github.io/getting_started.html), it simply is not the only one.
The user manual seems to be more and more outdated. I have started to convert the manual to markdown and reordered it. (https://github.com/texstudio-org/texstudio/blob/master/utilities/manual/usermanual_en.md) Help is welcome, especially for the parts which are annotated todo . Target audience are users who are getting started and are looking for new features or trying to solve issues.