That list sounds fair enough to me. Companies have specific toolchains for documentation, and translating, for example, a LibreOffice file to asciidoc (which we use internally) is a very long-winded process, so it's much easier to have the work done in the right format in the first place.The documenting process itself. First they have to accept you as translator, documenting. Next they insist you have to use program X,Y and last you have to upload it in form ZX or so. I'm okay to install ONE program to do the job, not for every program a new program for documenting. Next, it is almost impossible to be accepted as a translator or so. Don't say its not true, I tried and I'm done with it. Had in mind to translate Libreoffice and upgrade it with missing bits and bytes and some other programs. Of course it will be first in Dutch and then English and may be then German, but I need than a proof reading with a native German speaking user.3. This stuff isn't closed source. What's stopping any of you from documenting what you have learned and sharing that with the rest of us?
More on topic, I have written a whitepaper on the audio systems on Pis, probably not as detailed as what some people are looking for as its just an overview. Needs copy editing internally before I can release it.
Statistics: Posted by jamesh — Tue Aug 13, 2024 3:13 pm