I personally prefer the third person “one can” and use the non-gendered pronoun they/their (which is not plural in that case) as much as possible.
A lot of the Natron doc would have to corrected that way, but if we can at least follow these diversity & inclusion rules for new doc that’s already great.
Great work!
Sorry I was too busy today to contribute, daily work
Can I help with some gifs or what else is needed ?
Maybe a section on how to check if the image sequence has errors, with pngcheck or with the amazing DJV tool…
@hellocatfood: are you on discord, signal, telegram to communicate in realtime ?
Same, got busy with other stuff (I work odd hours of the day). I’m just pushing the changes to the document to the repo but I can be available tomorrow for realtime editing.
I checked your profile here and see that you time zone is an hour ahead of me (I’m in the UK). I’ll be online all day tomorrow so let’s coordinate. (same goes out to anyone else too!)
I find it a huge time killer to write the doc in .rst format on Github with forking and stuff.
Its very hard to collaborate. Simple tasks like adding a dot or a picture are taking huge amount of clicking, confirming, etc.
I’d love to help on the docs, but is there another way of doing so, a more “non-coder” way, so we could focus on the actual content instead of how to create an outline or a header… ?
If you want to continue using the Google Doc I created (or indeed start your own) please do.
When it comes time to adding it to the repository you can create your own fork and do a pull request or do as @devernay suggested and send the doc to him.
@TamerGester@El_Artista the Natron documentation is already hosted on Read The Docs. When you try and edit a page from there it actually redirects/links to Github
Download the docx file and put it into a new folder. Rename the file without any space. @hellocatfood please rename the doc without space or use ‘_’ undersocre. It will be easy for rst compile as well.
now extract the docx file in terminal:
cd ‘your docx director’
lnx/osx: unzip natron_docu.docx
win: unzip .\natron_docu.docx
You will get a “media” folder inside the word folder. This contains images. copy the media folder and paste it in the docx folder you are working on.
now in the terminal type:
win: pandoc.exe -f docx natron_docu.docx -t rst -o natron.rst
linux/OSX pandoc -f docx natron_docu.docx -t rst -o natron.rst
Big thanks for your help.
He added me as a contributor on his fork, so we can avoid creating 1000 of forks.
then we solved the task via discord communication and the ReText tool.
However, just followed your recommendation about the visual studio plugin, this now looks like its the way we could work! I think we are getting into it, its just a massive steep learning curve…
Check the label at the top of the .rst file that you want to link to. It’ll be something like .. _documentlabel:
And then to create the link in the document you’re writing write :ref:Link name ` (that should have a backtick on each end but I don’t know how to escape a backtick here)
@magdesign@hellocatfood
Folks I have talked with ffmpeg folks and had to change some doc codes. Please see the update. Usually we go straight for tiff. Seems PNG and Tiff have some different algorithm preference issue. Have changed all in the doc. Please update those.
Thanks and sorry for the hassle.