> From: Bruce Dubbs <[email protected]>
> Date: Sun, 14 May 2017 01:15:12 -0500
>
> Bruce Dubbs wrote:
> > William Harrington wrote:
> >> https://pypi.python.org/pypi/misspellings
> >>
> >> I've used this a lot with our CLFS book. It may help with the LFS book.
> >
> > Thanks, Tried it and it seems to work well.
>
> I just fixed all the identified misspellings in both LFS and BLFS.
> Actually I was surprised how few there were considering the size of the
> books. Several were in xml comments that will never be seen by users and
> several more in archived files. Lots in the stylesheets but I'm going to
> ignore those as most are not really ours are are invalid.
>
> Editors: Install this package with:
>
> sudo python setup.py install
>
> Use as (from the base of LFS or BLFS BOOK/ diretory:
((
diretory
->
directory
))
>
> find . -name \*.xml | misspellings -f -|grep -v style
It's likely preferred to, automatically:
--
* skip .svn dirs.
* skip stylesheets dirs.
* proc txt but not binary.
* proc ~all-else, under resp b/lfs 'trunk' dirs.
--
Across b/lfs, filename extensions, or names of files w/o extensions, are:
==
[...]
8 README
8 ent
12 sh
13 txt
15 conf
18 png
29 php
42 md5
48 service
49 wget
1547 xml
==
This, plus some grep/inspection, indicates omitting .png & maybe also
.md5 .
Have also, as ref, got:
----
$ ls -aCF ./{,b}lfs/curr/trunk/
./blfs/curr/trunk/:
./ ../ .svn/ BOOK/ auxfiles/ bootscripts/ edguide/ scripts/
systemd-units/
./lfs/curr/trunk/:
./ ../ .svn/ BOOK/ OLD_BRANCHES_AND_TAGS editor-manual/
$
----
So, overall, may want the find() to be, at core, for each of b/lfs dirtrees:
====
find -P ./trunk \
\( \( -name .svn -o -name stylesheets \) -prune \) \
-o \
\( -type f ! -name '*.png' -print \)
=====
Although that may seem to cast the net unnecessarily wide, it's really
the spellchecker opts/dicts/rules that you'd want to narrow things
down further. (And o/c the system can 'learn').
As this is o/c a repeat-process, so it's useful that there is used the
~usual type of setup/structure:
----
* a report/summary and ready-made patch, are generated automatically,
periodically via cron/&c, at master repo side;
* there is an "apply-or-don't-apply" flag that is aut set to
default="don't-apply";
* the/any patch gets aut-sent-to/reviewed/adj-if-nec, by a human;
* the flag is if nec adj to 'apply', or left at default "don't-apply";
* and a later cron-job does the apply-or-not, acc to flag status;
* cron-jobs' outputs get mailed as nec to persons/lists.
----
akh
--
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
