Am 02.11.23 um 19:25 schrieb mm:
Hey Tobi,
Hey m,
thank you for your email and the re-aliving the thread! :)
So, the current status is - the final rehearsal for the conversion of
the documentation from markdown to rst was I think 2 weeks ago? It went
well, meaning, at least from my pov
Hi, folks,
after a long time of silence (sorry for that!), I'd like to participate
in the translation issue again. :-)
What is the current state? What is already there and what is still missing?
I don't know what you think, but for me it's hard to see the whole. The
translation issue
On 11/28/22 8:05 AM, Marek Marczykowski-Górecki wrote:
> On Tue, Nov 01, 2022 at 12:45:33PM +0100, mm wrote:
>> Hi Marek, hi Andrew, hi Tobias,
>
>> Marek, I merged your pull request, also merged your changes into master and
>> added some enhancements and created a pull request.
>
>> Here you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, Nov 01, 2022 at 12:45:33PM +0100, mm wrote:
> Hi Marek, hi Andrew, hi Tobias,
>
> Marek, I merged your pull request, also merged your changes into master and
> added some enhancements and created a pull request.
>
> Here you could review
On 11/1/22 13:43, Marek Marczykowski-Górecki wrote:
On Tue, Nov 01, 2022 at 12:45:33PM +0100, mm wrote:
> Hi Marek, hi Andrew, hi Tobias,
> Marek, I merged your pull request, also merged your changes into
master and
> added some enhancements and created a pull request.
> Here you could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, Nov 01, 2022 at 12:45:33PM +0100, mm wrote:
> Hi Marek, hi Andrew, hi Tobias,
>
> Marek, I merged your pull request, also merged your changes into master and
> added some enhancements and created a pull request.
>
> Here you could review
Hi Marek, hi Andrew, hi Tobias,
Marek, I merged your pull request, also merged your changes into master
and added some enhancements and created a pull request.
Here you could review it
https://github.com/maiska/qubes-translation-utilz/pull/2
Either way, one could try it out, there should
Hi Marek,
The current status is as follows:
I dummy merged rst-writer branch, doing no refactoring at all.
I am using my implementation as crude as it is, as i am always directly
writing to the body.
But as you said, it must be done only one time and I think the current
results are
Hi, m,
Am 25.09.22 um 23:31 schrieb mm:
Hey Tobias,
I do not know unfortunately what you are referring to?
I mean the objective is to convert the markdown documentation to rst asap
Unfortunately it did not work out out of the box, due to docutils niceties.
background: I refuse to publish
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
Thanks for the update. Don't worry about the schedule - while we do want
to finish this soon, it doesn't need to be yesterday.
On Tue, Oct 04, 2022 at 06:54:45AM +0200, mm wrote:
> Hello Marek, hello Andrew,
>
> I can have spare time
Hello Marek, hello Andrew,
I can have spare time starting Sunday to focus & reply.
(Please, Marek, recall that i have pointed out mid September that I am out off
the map
basically from 15.09 till 8.10.)
Nevertheless tried to fix different issues in some spare time, such as
embedding videos,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, Sep 27, 2022 at 01:15:56AM +0200, Marek Marczykowski-Górecki wrote:
> On Mon, Sep 26, 2022 at 11:33:22PM +0200, mm wrote:
> > Hi Marek,
> >
> >
> > On 9/26/22 00:01, Marek Marczykowski-Górecki wrote:
> > > Hi M,
> > >
> > > In fact, I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, Sep 26, 2022 at 11:33:22PM +0200, mm wrote:
> Hi Marek,
>
>
> On 9/26/22 00:01, Marek Marczykowski-Górecki wrote:
> > Hi M,
> >
> > In fact, I'm working on translation-utilz right now too. Marta used her
> > google-foo and found this gem:
Hi Marek,
On 9/26/22 00:01, Marek Marczykowski-Górecki wrote:
Hi M,
In fact, I'm working on translation-utilz right now too. Marta used her
google-foo and found this gem:
https://github.com/SamWilsn/docutils-rst-writer
this looks very nice!! :) Thanks Marta! :)
So, I replaced most of the
On 9/9/22 12:52 PM, mm wrote:
> Hey Andrew,
>
>
> thank you for your work!!
>
Thank *you*! :)
> So one by one:
>
> https://github.com/maiska/qubes-doc.rtd/commit/0b8529a026da0523355eec55c57c1da2aa110d07
>
>> By the way, with this one, the link is not actually broken. It still works,
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi M,
In fact, I'm working on translation-utilz right now too. Marta used her
google-foo and found this gem:
https://github.com/SamWilsn/docutils-rst-writer
So, I replaced most of the qubesrstwriter2.py with just this thing and
it's almost
Hey Tobias,
I do not know unfortunately what you are referring to?
I mean the objective is to convert the markdown documentation to rst asap
Unfortunately it did not work out out of the box, due to docutils niceties.
background: I refuse to publish my regular-expressions-monster-convert
Hi, m,
thank you for all the work!
As far as I can remember, you talked with Marek about i18n and l10n on
the Qubes OS summit 2022. Could you (or Marek) please give us a summary
of the results of those talks?
Thank you!
Tobias
--
You received this message because you are subscribed to the
I forgot somehting
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
Hey Andrew,
thank you for your work!!
So one by one:
https://github.com/maiska/qubes-doc.rtd/commit/0b8529a026da0523355eec55c57c1da2aa110d07
By the way, with this one, the link is not actually broken. It still works,
because your browser adds the missing forward slash automatically.
On 9/8/22 6:15 PM, Andrew David Wong wrote:
> On 9/8/22 6:14 PM, Andrew David Wong wrote:
>> On 9/8/22 6:00 PM, Andrew David Wong wrote:
>>> On 9/7/22 6:30 PM, mm wrote:
[...]
>>> The following files will be retained at this stage, due to liquid
>>> templating
>>> (needs some
On 9/7/22 6:30 PM, mm wrote:
> and the clone should go recursive if you want to try it out locally
>
> 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?
On 9/8/22 6:14 PM, Andrew David Wong wrote:
> On 9/8/22 6:00 PM, Andrew David Wong wrote:
>> On 9/7/22 6:30 PM, mm wrote:
>>> [...]
>> The following files will be retained at this stage, due to liquid
>> templating
>> (needs some tweeking if
>> one wishes to work with sphinx
On 9/8/22 6:00 PM, Andrew David Wong wrote:
> On 9/7/22 6:30 PM, mm wrote:
>> [...]
> The following files will be retained at this stage, due to liquid
> templating
> (needs some tweeking if
> one wishes to work with sphinx templating) and also these are perhaps also
> just
On 9/7/22 6:45 PM, mm wrote:
> Hello again,
>
> here in a clear manner some suggestions.
>
> What do you think?
>
>>>
>>> Qubes builder -- probably a subpage linked from a main page
> is actually Qubes builder details, could be hosted in the Building section?
>
>>> Join -- intentionally hidden
On 9/7/22 6:30 PM, mm wrote:
> [...]
https://github.com/maiska/qubes-doc.rtd/commit/0b8529a026da0523355eec55c57c1da2aa110d07
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
Hello again,
here in a clear manner some suggestions.
What do you think?
Qubes builder -- probably a subpage linked from a main page
is actually Qubes builder details, could be hosted in the Building section?
Join -- intentionally hidden when active recruiting stopped (to be
unhidden
Hello Marek, hello Andrew,
thank you for your input!! Sorry for answering this late!
As a disclaimer: the talk in an ideal world will be packed and last 20
min, so that there would be 10 min for discussion.
On 9/8/22 00:34, Andrew David Wong wrote:
On 9/5/22 4:55 AM, Marek
On 9/5/22 4:55 AM, Marek Marczykowski-Górecki wrote:
> On Sun, Sep 04, 2022 at 10:05:42PM +0200, mm wrote:
>> Hello Marek,
>
>
>> thank you for resurrecting the thread. I wanted to write like a week ago,
>
>> but yet, it lasted longer.
>
>> I am glad to announce that the initial hurdle for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, Sep 04, 2022 at 10:05:42PM +0200, mm wrote:
> Hello Marek,
>
>
> thank you for resurrecting the thread. I wanted to write like a week ago,
>
> but yet, it lasted longer.
>
> I am glad to announce that the initial hurdle for Qubes OS docs
Hello Marek,
thank you for resurrecting the thread. I wanted to write like a week ago,
but yet, it lasted longer.
I am glad to announce that the initial hurdle for Qubes OS docs
RST-conversion,
localization, hosting on RtD is behind us and you can see a preliminary
result on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, Dec 21, 2021 at 08:57:27PM +0100, mm wrote:
> Hello all,
>
> in September there was a thread about migrating the documentation to another
> platform,
> and the silent winner was RTD.
> Let me say up front: For me localization, release
Hi again
On 12/26/21 13:46, Manuel Amador (Rudd-O) wrote:
aps things changed and is a straightforward easy to use idk.
It's very straightforward to use now.
ok, nice to hear that
Plone supports Markdown out of the box.
good
automation of translation/localization wrt to transifex and
On December 25, 2021 10:37:04 PM GMT+01:00, mm wrote:
>
>On 12/25/21 21:16, Manuel Amador (Rudd-O) wrote:
>>
>> Honestly if I were directing the project I would set up a Plone instance,
>> and use its excellent i18n to write docs. Additionally, if wanted, I would
>> set up two way sync
On 12/25/21 21:16, Manuel Amador (Rudd-O) wrote:
Honestly if I were directing the project I would set up a Plone instance, and
use its excellent i18n to write docs. Additionally, if wanted, I would set up
two way sync between a github repo and the site. Ask me for more details if
Honestly if I were directing the project I would set up a Plone instance, and
use its excellent i18n to write docs. Additionally, if wanted, I would set up
two way sync between a github repo and the site. Ask me for more details if
interested.
--
You received this message because you are
On 12/21/21 11:57 AM, mm wrote:
Hello all,
in September there was a thread about migrating the documentation to
another platform,
and the silent winner was RTD.
Let me say up front: For me localization, release specific docs,
automation & easy and transparent maintenance of the documentation
Hello all,
in September there was a thread about migrating the documentation to
another platform,
and the silent winner was RTD.
Let me say up front: For me localization, release specific docs,
automation & easy and transparent maintenance of the documentation
are one of the most important
38 matches
Mail list logo
