thank you for your work!!
So one by one:
By the way, with this one, the link is not actually broken. It still works, because your browser adds the missing forward slash automatically. Nonetheless, I've committed a fix to make it technically syntactically correct.
With the above commit there several links. I suppose you mean the internal one: it is so, yes, but for the convenience of my stupid script..., but let me explain:
Some people, when confronted with a problem, think
“I know, I'll use regular expressions.”
Now they have two problems.
[...] other people's articles linking to the official Qubes OS documentation would be broken, since I do not think that there is a proxy to handle such requests and redirects? Or there is a simpler way?I don't understand why links would get broken. Let's use a concrete example to help me understand. Take this page, for example: https://www.qubes-os.org/doc/how-to-update/ After the migration to RtD, wouldn't this still be the same URL for that page? Why would it be any different? If you're saying it has to be a different URL for some reason, what would the new URL look like?
The new url when generated will look like:
foo.bar/user/how-to-guides/how-to-update.html from rst will look
like :doc:` foo </user/how-to-guides/how-to-update>`
Domain dependent or whatever...
Wouldn't converting all Markdown files to RST result in still using the _doc submodule, just with all the files converted? Maybe I'm not understanding something here.This could be a possibility yes, perhaps with a sphinx plugin for redirects. It exists, haven't tried it yet.Why only "a possibility"? I figured that would be the obvious thing to do, but clearly I am missing something. If there is a good reason to do otherwise, then that's totally fine! It's just not clear to me what that reason might be.
Nope, you are abs right!
My motivation behind this solution (meaning leave the docs as they are but empty etc.) was take it one step at a time w/o necessarily drain time in fixing possible broken links. Till the documentation is on RTD
and afterwards the website can be dealt with and properly cleared
of any redundant information (such as in _includes research.html,
cause i blank out translated it
into flat markdown or rst),
also than use the sphinx redirect extension, these all are nice to have and can be done afterwards.
The possibility was not the right word in this context...
The HCL and Downloads thus can be addressed later :)
About the pull requests I will look into it latest tomorrow, render and say if smth is 'missing'
One thing though which I did not think about:
But maybe that's okay, since once we migrate to RtD, we'll no longer be relying on custom scripts like this to populate the table of contents.
Yes!! Hopefully there will be a lot less clutter :))
git clone -b new-master --recursive https://github.com/maiska/qubesos.github.io.rtd.git
So, how do I serve the site locally after doing this? Can you provide step-by-step instructions?
All the best,
On a fedora VM:
sudo dnf install ruby ruby-devel openssl-devel redhat-rpm-config @development-tools;
gem install jekyll bundler;
find . -name gem; #(in my case it was /home/user/.local/share/gem/)
git clone -b new-master --recursive https://github.com/maiska/qubesos.github.io.rtd.git; cd qubesos.github.io.rtd/
bundle config set --local path '/home/user/.local/share/gem/'
(if there is some sort of error with webrick, just try: bundle add webrick; bundle exec jekyll serve)
bundle exec jekyll serve
All the best,
You received this message because you are subscribed to the Google Groups "qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qubes-devel...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/d1d7a758-b879-4ee2-6ab7-e7ac92deaf04%40maiski.net.
On 9/26/22 00:01, Marek Marczykowski-Górecki wrote:
In fact, I'm working on translation-utilz right now too. Marta used her
google-foo and found this gem:
this looks very nice!! :) Thanks Marta! :)
So, I replaced most of the qubesrstwriter2.py with just this thing and
it's almost flawless (especially tables, images etc work out of the
OK, thanks for the PR, I'll merge into and get rid of the
obsolete stuff from my branch this days.
I have some weird customized fixes all over, but this should work.
One question though:
have you had success with parsing admin-api.rst (as converted by pandoc from md?)
I get the error when parsing with docutils in order to post-process it for qubes:
docutils.utils.SystemMessage: /home/user/testingfilez/admin-api.rst:74: (SEVERE/4) Unexpected section title
and it cannot get over the table as it is...:/
all the best,