Puppy documentation needs updated or replaced

[user1234]

BTW, I have made a new issue in my fork of woof-CE that displays files remaining to be updated:- https://github.com/lakshayrohila/woof-CE/issues/16.

[bigpup]

@user1234

You seem to have the writing style down better than me

So, when you get one completed.
Post it.

I will be happy to look it over and see if anything got missed or may need to be added/corrected.

But these documents are talking about stuff I do not use much, so not sure if my help is going to be the best for them.

[user1234]

@user1234

You seem to have the writing style down better than me

So, when you get one completed.
Post it.

I will be happy to look it over and see if anything got missed or may need to be added/corrected.

But these documents are talking about stuff I do not use much, so not sure if my help is going to be the best for them.

What about HOWTO-multimedia.htm I posted? Any comments?

[bigpup]

Looks good.

Only thing I think it should clearly state at the beginning top of page, that not all these programs are going to be in a Puppy version.

My suggestion:

These are some of the possible programs you could use in Puppy Linux.

Puppy Linux versions will usually have several of these programs already installed, with at least one program for each media type.

Note that you can install your favorite package through Puppy Package Manager (or other package manager, like apt or slapt, if present in your Puppy).

The links are to "online help" pages on each program.

[user1234]

@bigpup:-

HOWTO-multimedia.htm.tar.gz

(5.5 KiB) Downloaded 60 times

[bigpup]

Looks good.

Good work!

[user1234]

Still have /usr/share/doc/Pudd.htm and samba-printing.htm, but haven't looked at them for years.
Hmm, Pudd.htm was last edited in Feb. 2013 and samba-printing.htm in Jan. 2013.

@BarryK, are they the same revisions as are currently in woof-CE? Can you please post those files so that I could match them with the ones in woof-CE, and if they are newer then we could start out with those ones

Thanks

[BarryK]

Still have /usr/share/doc/Pudd.htm and samba-printing.htm, but haven't looked at them for years.
Hmm, Pudd.htm was last edited in Feb. 2013 and samba-printing.htm in Jan. 2013.

@BarryK, are they the same revisions as are currently in woof-CE? Can you please post those files so that I could match them with the ones in woof-CE, and if they are newer then we could start out with those ones

Thanks

Here they are, gzipped, appended.

[user1234]

First of all, thank you @BarryK for the files. I have taken a look at both. samba_printing.htm is a bit different in woof-CE, but Pudd.htm was all the same. I have just edited Pudd.htm to improve its styling. @bigpup, @williwaw, please review:-

Pudd.htm.tar.bz2

(1.67 KiB) Downloaded 39 times

Also, @bigpup, I need you to update the samba_printing.htm. Every time I read it, everything just goes over my head .

I have currently started with HOWTO-internationalization.htm.

Thanks

[bigpup]

Also, @bigpup, I need you to update the samba_printing.htm. Every time I read it, everything just goes over my head

Sorry, cannot help with that one.

I have never used samba_printing and have no idea if the info is good or bad.

[bigpup]

Pudd.htm seems to be OK to me.

Looks good!

I have never used Pudd, but the info seems to be understandable and clear to me.

[user1234]

@williwaw, @bigpup, can you please provide screenshot of MoManager? I needed it for updating HOWTO_internationalization.htm.

[bigpup]

I cannot run Momanager.
I am setup for English and it will not run for me.

Have to be using a non-English language.

[user1234]

@bigpup, I have updated nearly the whole file, but am not sure about the maintainers' names, so leaving them as is. I was searching around for momanager and I found https://bkhome.org/news/202301/automati ... nager.html, which puzzles me a bit whether I should put the info in HOWTO-internationalization.htm or not.

@BarryK, @dimkr, I also wanted to ask you the same.

[user1234]

@bigpup, here is the updated HOWTO file + momanager screenshot I could get on fossa64 (will try to take it on jammy64 and update the image later on):

HOWTO-internationalization.tar.bz2

(78.44 KiB) Downloaded 43 times

EDIT: momanager seems to be same (lookwise) in jammy64 as well. Not changing the image, except for trying to compress it a bit.

[bigpup]

Any info you find on Barry K's news is most likely stuff he has done for Easy OS. (not a Puppy Linux)

He is not actively supporting anything in Puppy Linux anymore.

Only way to know for sure is send him a PM asking about this post in his Barry News.

Any references to Barry News should be removed.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
I do not think there is really anyone assigned to be maintainers anymore.

Looking at the list of names:

these are the maintainers:
da Danish --maans
de German --L18L
el Greek --kounelii
es Spanish --vicmz
fr French --esmourguit
it Italian --vicmz (temporary)
nl Dutch --Bert
pl Polish --robwoj44
pt Portuguese --vicmz
ru Russian rodin.s

Those are some very old names and I think they are no longer working on supporting Puppy.
That maintaining language packs, for specific languages, has basically stopped being done.

I would remove that maintainer info.

You can see by what is posted in the forum section Internationalization, not much being done on producing language packs for Puppy.
viewforum.php?f=186

[bigpup]

You will also see in the MoManager window, a button to generate a "langpack" PET package. If you would like to translate Puppy for a particular language, this button is very nice. It will gather up all the translations you have created/modified for your language and will put them into a PET package, which you can then send to BarryK, through PuppyLinux Forum, and he may place it along with the other langpacks at ibiblio.org. See the existing langpacks at pet_packages-noarch sub-directory of PuppyLinux directory under ibiblio.org

This needs another PM to Barry K asking if he will do this.

He is no longer active in Puppy Linux support and is only working with his Easy OS.

You would think someone in Puppy Linux, that has ability to add files to Puppy repository at ibiblio.org, would do this.
But I have no idea who that would be.

01micko is suppose to be the Puppy Master, but he does nothing in this forum.
Only seems to support stuff at Woof-CE.

Maybe a need to PM him.
He is at least a forum member.

[user1234]

You will also see in the MoManager window, a button to generate a "langpack" PET package. If you would like to translate Puppy for a particular language, this button is very nice. It will gather up all the translations you have created/modified for your language and will put them into a PET package, which you can then send to BarryK, through PuppyLinux Forum, and he may place it along with the other langpacks at ibiblio.org. See the existing langpacks at pet_packages-noarch sub-directory of PuppyLinux directory under ibiblio.org

This needs another PM to Barry K asking if he will do this.

He is no longer active in Puppy Linux support and is only working with his Easy OS.

You would think someone in Puppy Linux, that has ability to add files to Puppy repository at ibiblio.org, would do this.
But I have no idea who that would be.

01micko is suppose to be the Puppy Master, but he does nothing in this forum.
Only seems to support stuff at Woof-CE.

Maybe a need to PM him.
He is at least a forum member.

I had put there the same information that I got on older mo manager. But, maybe first I check the information in newer momanager, whether its changed.

[dimkr]

Anything that needs to be in sync with woof-CE (documentation, translations) but is maintained outside of woof-CE, will rot quickly as contributors come and go. I think it would be best to make documentation and translations an integral part of woof-CE instead of using manually-built .pet packages without any version control.

[user1234]

Anything that needs to be in sync with woof-CE (documentation, translations) but is maintained outside of woof-CE, will rot quickly as contributors come and go. I think it would be best to make documentation and translations an integral part of woof-CE instead of using manually-built .pet packages without any version control.

We'll need to update momanager script itself then . Note that I am testing momanager on jammy64 built nearly a month ago also provides the outdated maintainers info. So I think momanager itself needs a update first, then I'll update the HOWTO later on.

Let's update momanager first.

EDIT: I also think that automatic translation generator is a good thing to be in momanager.

[user1234]

@bigpup, @dimkr I have recently opened a PR for addition of BDRV documentation here. Here is the documentation file:

bdrv.html.tar.bz2

(1.43 KiB) Downloaded 53 times

EDIT: @bigpup, Please inform me whether the file was okay or it needed some changes .

Thanks.

[bigpup]

I looked it over and looks good.

However, this is all new to me about having a bdrv.sfs setup this way.

The link about Synaptic documentation did not open, but that is probably because I do not have this bdrv.sfs and have it loaded.

Where is this bdrv.sfs to try it out and use it?

I like the idea of this.

[user1234]

I looked it over and looks good.

However, this is all new to me about having a bdrv.sfs setup this way.

The link about Synaptic documentation did not open, but that is probably because I do not have this bdrv.sfs and have it loaded.

Where is this bdrv.sfs to try it out and use it?

I like the idea of this.

Don't know whether your puppy provides bdrv, but it can be added during the build process; and jammy64 does have it present in its iso, thanks to @dimkr.

More information

This bdrv doc file will be added to the puppy if and only if the puppy is built with bdrv.

And yes, synaptic+apt will be present only if you have bdrv loaded.

Also, when bdrv is loaded, the link in index.html that points to PPM documentation is also replaced with the link to this file. So, if @dimkr also approves the PR and merges it into woof-CE, every next build will gonna have this change (but currently not the other documentation files' update - only bdrv.html will be added).

[bigpup]

Do not know if you know about this.

F96-CE has been released and it is using the updated doc files, this topic has produced.

I asked for any feedback good or bad here:
https://forum.puppylinux.com/viewtopic.php?t=7922

[peebee]

The new documentation from @user1234 is now included in the new builds 240208 at:

https://sourceforge.net/projects/pb-gh-releases/files/