RealRaven2000 / QuickFolders

Thunderbird Add-on: QuickFolders
http://quickfolders.org/
Other
48 stars 9 forks source link

Typos in documentation... #43

Open fredstluka opened 4 years ago

fredstluka commented 4 years ago

Axel, when I reported some typos in the docs, you said in your 6/9/2002 4:43pm email reply:

ok, I fixed the other ones and pushed to github!

I was poking around just now, trying to find the fixes, but can't see them at GitHub. Is all the code in the "chrome" folder? There doesn't seem to be much in the other files or folders. In fact, it pretty much all seems to be in chrome/content. I searched the Git log via the History button at:

Didn't find any hint that the typos were fixed. So I'm submitting them as bugs:

Hmmm... I think all except the "_Others" typo are now fixed in the public web page. Maybe you're not keeping the public web pages in GitHub?

Anyhow, here are some more typos that I had not yet reported:

QF version 4.18.1 TB version 68.9.0 Mac OS X version 10.11.6 --Fred

fredstluka commented 4 years ago

Also:

--Fred

fredstluka commented 4 years ago

Also:

--Fred

RealRaven2000 commented 4 years ago

Hmmm... I think all except the "_Others" typo are now fixed in the public web page. Maybe you're not keeping the public web pages in GitHub?

Well the main reason is that I don't usually commit until I release (most of the stuff). But I usually do some commits on the language resources.

The main reason for waiting with the commit is that I commit on release and then double check my planned change log against the diff. Trying to keep the change sets small, as much as I can. And I didn't really have many collaborators so far so I didn't need to keep it up to date "in realtime". Just consider your suggestions as WIP / shelved. I usually release on ATN, commit to github and then close the issues all on the same day, usually within the same hour.

RealRaven2000 commented 4 years ago

Didn't find any hint that the typos were fixed. So I'm submitting them as bugs:

* http://quickfolders.org/

  * [x]  mailsand --> mails and
  * [x]  pleasee --> please
  * [ ]  "_Others" --> "Others" (or use _Others also later in the
    same paragraph)
  * [x]  "alread" --> "already"
  * [x]  "maile" --> "mail"
  * [x]  "ar" --> "are"

Hmmm... I think all except the "_Others" typo are now fixed in the public web page. Maybe you're not keeping the public web pages in GitHub?

documentation is in the gh-pages branch - see:

https://github.com/RealRaven2000/QuickFolders/blob/gh-pages/index.html

on my other Add-on githubs I commit to web/src and eleventy then compiles and pushed to gh-pages.

fredstluka commented 4 years ago

Well the main reason is that I don't usually commit until I release (most of the stuff). But I usually do some commits on the language resources.

OK. Makes sense.

The main reason for waiting with the commit is that I commit on release and then double check my planned change log against the diff.

Yeah, makes sense. I've written some scripts, as I've used various VCS systems over the yeas (VAX CMS, Unix sccs, Unix rcs, MS VSS, PVCS, CVS, and then Git) to show the diffs since the last release, so that I could write up an accurate set of release notes.

Trying to keep the change sets small, as much as I can. And I didn't really have many collaborators so far so I didn't need to keep it up to date "in realtime".

Yeah, on a one-man team, you can almost get away without any VCS at all.

Just consider your suggestions as WIP / shelved. I usually release on ATN, commit to github and then close the issues all on the same day, usually within the same hour.

OK.

--Fred