Commits

Shlomi Fish committed 1d42329

More spell checkings.

  • Participants
  • Parent commits a105060

Comments (0)

Files changed (14)

File bin/spell-checker-iface.sh

 #!/bin/bash
 find dest/t2-homepage/ -name '*.html' -or -name '*.xhtml' |
     ( LC_ALL=C sort  ) |
-    perl -lne 'print if 1..m#lecture/Gimp/index#'|
+    perl -lne 'print if 1..m#lecture/LAMP/slides/what-serve/media#'|
     grep -vP 'guide2ee/undergrad' |
     grep -vP '(?:humour/TheEnemy/(?:The-Enemy-(?:English-)?rev|TheEnemy))' |
     grep -vP '(?:humour/by-others/(?:English-is-a-Crazy-Language|darien|hitchhiker|how-many-newsgroup-readers|oded-c|s-stands-for-simple|technion-bit-1|top-12-things-likely|was-the-death-star-attack|grad-student-jokes-from-jnoakes))' |

File lib/docbook/4/xml/case-for-file-swapping-rev3.xml

                 Act of 1790</ulink> granted the originator of a text “the
             sole liberty of printing, reprinting, publishing and vending” of
             a work. Note that it does not talk about mere duplication. Printing
-            and reprinting were at the time very costy operations, produced
+            and reprinting were at the time very costly operations, produced
             works of good quality, and required a non-negligible amount of
             money to perform. On the other hand, if a person was to copy the
             work by hand, it would not have fallen under this law.

File lib/docbook/4/xml/what-makes-software-high-quality-rev2.xml

             one: PHP 4 was not compatible with PHP 3 and PHP 5 was not
             compatible with PHP 4. Furthermore, sometimes existing user-land
             code was broken in minor-digit releases. As such, maintaining
-            PHP code into the future is a very costy process, especially if
+            PHP code into the future is a very costly process, especially if
             you want it to work with a range of versions.
         </para>
 
             pleasing. Aesthetics in this context, does not necessarily mean
             very “artsy” or having a breath-taking style. But we may have
             run into software (usually one for internal use or one
-            of those very costy, bad-quality, niche, software) that seemed
+            of those very costly, bad-quality, niche, software) that seemed
             very ugly and badly designed, with a horrible user-interface,
             etc.
         </para>

File lib/hunspell/whitelist1.txt

 Feynman
 rpm
 prepend
+kilometrage
+resizable
 
 ====dest/t2-homepage/index.html,dest/t2-homepage/old-news.html
 Owch
 ndevilla
 sunsite
 
+====dest/t2-homepage/lecture/LAMP/index.html,dest/t2-homepage/lecture/LAMP/slides/cms/content-generating.html,dest/t2-homepage/lecture/LAMP/slides/cms/index.html,dest/t2-homepage/lecture/LAMP/slides/cms/server-installed.html,dest/t2-homepage/lecture/LAMP/slides/compatibility/embellishments.html,dest/t2-homepage/lecture/LAMP/slides/compatibility/index.html,dest/t2-homepage/lecture/LAMP/slides/compatibility/non-msie.html,dest/t2-homepage/lecture/LAMP/slides/compatibility/standards.html,dest/t2-homepage/lecture/LAMP/slides/compatibility/words-of-wisdom.html,dest/t2-homepage/lecture/LAMP/slides/databases/compatibility.html,dest/t2-homepage/lecture/LAMP/slides/databases/index.html,dest/t2-homepage/lecture/LAMP/slides/databases/necessity.html,dest/t2-homepage/lecture/LAMP/slides/databases/non-sql.html,dest/t2-homepage/lecture/LAMP/slides/databases/sql.html,dest/t2-homepage/lecture/LAMP/slides/index.html,dest/t2-homepage/lecture/LAMP/slides/intro/A.html,dest/t2-homepage/lecture/LAMP/slides/intro/L.html,dest/t2-homepage/lecture/LAMP/slides/intro/M.html,dest/t2-homepage/lecture/LAMP/slides/intro/P.html,dest/t2-homepage/lecture/LAMP/slides/intro/index.html,dest/t2-homepage/lecture/LAMP/slides/intro/order_of_importance.html,dest/t2-homepage/lecture/LAMP/slides/legal-notes/gpl.html,dest/t2-homepage/lecture/LAMP/slides/legal-notes/index.html,dest/t2-homepage/lecture/LAMP/slides/server-technologies/how-much.html,dest/t2-homepage/lecture/LAMP/slides/server-technologies/index.html,dest/t2-homepage/lecture/LAMP/slides/server-technologies/sss-overview/index.html,dest/t2-homepage/lecture/LAMP/slides/server-technologies/sss-overview/other/JSP.html,dest/t2-homepage/lecture/LAMP/slides/server-technologies/sss-overview/other/c-cgi.html,dest/t2-homepage/lecture/LAMP/slides/server-technologies/sss-overview/other/extensions.html,dest/t2-homepage/lecture/LAMP/slides/server-technologies/sss-overview/other/index.html,dest/t2-homepage/lecture/LAMP/slides/server-technologies/sss-overview/other/ocaml.html,dest/t2-homepage/lecture/LAMP/slides/server-technologies/sss-overview/other/ruby.html,dest/t2-homepage/lecture/LAMP/slides/server-technologies/sss-overview/other/servelets.html,dest/t2-homepage/lecture/LAMP/slides/server-technologies/sss-overview/other/tcl.html,dest/t2-homepage/lecture/LAMP/slides/server-technologies/sss-overview/other/web-server.html,dest/t2-homepage/lecture/LAMP/slides/server-technologies/sss-overview/perl.html,dest/t2-homepage/lecture/LAMP/slides/server-technologies/sss-overview/php.html,dest/t2-homepage/lecture/LAMP/slides/server-technologies/sss-overview/python.html,dest/t2-homepage/lecture/LAMP/slides/web-browsers/index.html,dest/t2-homepage/lecture/LAMP/slides/web-browsers/khtml.html,dest/t2-homepage/lecture/LAMP/slides/web-browsers/mozilla.html,dest/t2-homepage/lecture/LAMP/slides/web-browsers/msie.html,dest/t2-homepage/lecture/LAMP/slides/web-browsers/nn4.html,dest/t2-homepage/lecture/LAMP/slides/web-browsers/opera.html,dest/t2-homepage/lecture/LAMP/slides/what-serve/css/index.html,dest/t2-homepage/lecture/LAMP/slides/what-serve/css/layout.html,dest/t2-homepage/lecture/LAMP/slides/what-serve/dynamic-html.html,dest/t2-homepage/lecture/LAMP/slides/what-serve/flash.html,dest/t2-homepage/lecture/LAMP/slides/what-serve/frames.html,dest/t2-homepage/lecture/LAMP/slides/what-serve/html.html,dest/t2-homepage/lecture/LAMP/slides/what-serve/images.html,dest/t2-homepage/lecture/LAMP/slides/what-serve/index.html,dest/t2-homepage/lecture/LAMP/slides/what-serve/java-script.html,dest/t2-homepage/lecture/LAMP/slides/what-serve/java.html,dest/t2-homepage/lecture/LAMP/slides/what-serve/media.html
+
+alt
+Amazonware
+AOLserver
+apps
+AxKit
+Bricolage
+CMS
+CMSes
+CSS2-based
+CSS-d
+cygwin
+DHTML
+div
+Dreamweaver
+ECMAScript
+Enhydra
+Etc
+FastCGI
+Firebird
+FrontPage
+GDBM
+Enhydra
+Etc
+FastCGI
+Firebird
+FrontPage
+GDBM
+JBoss
+jsp
+JSP
+KHTML
+Macromedia
+mal-formed
+marketshare
+markup
+MaxDB
+Midgard
+mis-features
+mod_perl
+mod_php
+MPEG
+MSIE
+MSIE-only
+namespaces
+Netapp
+non-MSIE
+Non-SQL
+NTs
+O'Caml
+Oggs
+OpenACS
+Perl's
+PHPBB
+PostNuke
+PotgreSQL
+Roxen
+SAP-DB
+scriptable
+Servelets
+Smalltalk
+Solaris
+Squishdot
+Tcl
+Tcl-enabled
+tech-savvy
+thttpd
+TikiWiki
+Tk
+todate
+toolkit
+TUX
+Unixes
+ViaWeb
+W3C
+weblets
+WebSphere
+whitespace
+Wiki-like
+Win32-based
+XBase
+XDBM
+Zope
+HP-UX
+IE
+libsvn_fs_fs
+gizmos

File lib/presentations/qp/web-publishing-with-LAMP/src/cms/server-installed.html.wml

 technologies. GPLed.
 </li>
 <li>
-<a href="http://www.squishdot.org/">Squisdot</a> for Zope - similar to
+<a href="http://www.squishdot.org/">Squishdot</a> for Zope - similar to
 Slash only based on Zope.
 </li>
 <li>
 framework.
 </li>
 <li>
-<a href="http://openacs.org/">OpenACS</a> - based on AOLServer, Tcl and
+<a href="http://openacs.org/">OpenACS</a> - based on AOLserver, Tcl and
 PostgreSQL/Oracle (only).
 </li>
 <li>

File lib/presentations/qp/web-publishing-with-LAMP/src/compatibility/embellishments.html.wml

 
 <points>
 <li>
-One can write standards-compliant sites that are full of Javascript games,
+One can write standards-compliant sites that are full of JavaScript games,
 Dynamic HTML, and other monsters like that. It is usually a bad idea.
 </li>
 <li>
-Getting Javascript code to work properly on all browsers is more difficult
+Getting JavaScript code to work properly on all browsers is more difficult
 than getting a static HTML to do so. (or at least it can never be easier).
 </li>
 <li>
-Most Javascript code is unnecessary. It adds more gizmos to the site, but
+Most JavaScript code is unnecessary. It adds more gizmos to the site, but
 not more functionality.
 </li>
 <li>
 By adding unnecessary embellishments to the site, you make them more prone
 to browser bugs, and mis-features; you make the site harder (and more
-costy) to maintain and you usually don't add much to the user experience
+costly) to maintain and you usually don't add much to the user experience
 to be worth it.
 </li>
 <li>
 An extreme example of this are pages that use HTML 4.x markup without any
-CSS or other visual embelishments. If you do this, I guarantee you that your
+CSS or other visual embellishments. If you do this, I guarantee you that your
 portability problems are over.
 </li>
 <li>

File lib/presentations/qp/web-publishing-with-LAMP/src/intro/M.html.wml

 friends.
 </li>
 <li>
-No datbase at all (see what <a href="http://www.paulgraham.com/">Paul Graham</a>
+No database at all (see what <a href="http://www.paulgraham.com/">Paul Graham</a>
 says in his <a href="http://www.paulgraham.com/vwfaq.html">ViaWeb FAQ</a>)
 </li>
 </points>

File lib/presentations/qp/web-publishing-with-LAMP/src/intro/index.html.wml

 <p>
 This does not means setting it up and maintaining the site will not cost a
 thing. It will. But there is evidence that such configurations are generally
-more robust, configurable and less costy to maintain than the equivalent
+more robust, configurable and less costly to maintain than the equivalent
 commercial ones.
 </p>
 

File lib/presentations/qp/web-publishing-with-LAMP/src/server-technologies/sss-overview/other/servelets.html.wml

 the server side.
 </li>
 <li>
-Quite problematic to write and maintain due to compulsary compilation stage
+Quite problematic to write and maintain due to compulsory compilation stage
 and the inherent verbosity of Java, and its many required protocols.
 </li>
 </points>

File lib/presentations/qp/web-publishing-with-LAMP/src/web-browsers/msie.html.wml

 
 <li>
 Can no longer be upgraded except as part of the OS, so its continued
-userbase will remain a problem, unless it diminishes.
+user-base will remain a problem, unless it diminishes.
 </li>
 </points>
 <h2>Verdict</h2>
 <points>
 <li>
 If you are running a site which appeals to a large (mainly not tech-savvy)
-userbase, you still need to support it.
+user-base, you still need to support it.
 </li>
 <li>
 By keeping your site clean of unnecessary problematic embellishments (which

File lib/presentations/qp/web-publishing-with-LAMP/src/web-browsers/nn4.html.wml

 As a result, it tends to break under many pages.
 </li>
 <li>
-Very small (and descreasing) use percentage, but can still be found in
+Very small (and decreasing) use percentage, but can still be found in
 god-forsaken (mainly old) installations.
 </li>
 <li>

File lib/presentations/qp/web-publishing-with-LAMP/src/what-serve/css/index.html.wml

 Don't pick colours that are hard to distinguish.
 </li>
 <li>
-Try not to make links unrecognizable.
+Try not to make links unrecognisable.
 </li>
 <li>
 Use each tag for its logical purpose. (the site should also look good with

File lib/presentations/qp/web-publishing-with-LAMP/src/what-serve/dynamic-html.html.wml

 Can cause more potential problems than static HTML.
 </li>
 <li>
-Generlly, unneeded for most serious uses.
+Generally, unneeded for most serious uses.
 </li>
 </points>

File lib/presentations/qp/web-publishing-with-LAMP/src/what-serve/java-script.html.wml

 
 <points>
 <li>
-JavaScript (now standarized as
+JavaScript (now standardised as
 <a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm">ECMAScript</a>) can be used to script the contents of pages,
 change their appearance, or control their various on-place widgets.
 </li>