I thus need to to
+I thus need to
--create the content type Index: openacs-4/packages/acs-content-repository/www/doc/guide/file-system.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/www/doc/guide/file-system.html,v diff -u -r1.2 -r1.3 --- openacs-4/packages/acs-content-repository/www/doc/guide/file-system.html 7 Aug 2017 23:47:47 -0000 1.2 +++ openacs-4/packages/acs-content-repository/www/doc/guide/file-system.html 28 Sep 2018 08:37:58 -0000 1.3 @@ -17,7 +17,7 @@
- A freshly installed content repository consists of a single "root" folder (analogous to the root directory / in UNIX or an - empty partition in Windows or MacOS). + empty partition in Windows or macOS).
- You organize items by creating subfolders under the root. @@ -83,7 +83,7 @@
- Content management systems can take advantage of the folder structure to implement an intuitive user interface analogous to familiar desktop - tools (Windows Explorer, MacOS Finder, etc.). + tools (Windows Explorer, macOS Finder, etc.).
- You can use the content repository API to constraint the type of content that a folder may contain (except for the index page). @@ -101,7 +101,7 @@ might wish to store the content for each instance in its own content root. Creating your own content (and template) root also has the advantage that you will not accidentally access another package's - content nor will another package access your content. Not that that + content nor will another package access your content. Not that could do any harm, because you have secured all your content through appropriate permissions. Index: openacs-4/packages/acs-tcl/tcl/apm-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-tcl/tcl/apm-procs.tcl,v diff -u -r1.112 -r1.113 --- openacs-4/packages/acs-tcl/tcl/apm-procs.tcl 25 Jul 2018 18:17:51 -0000 1.112 +++ openacs-4/packages/acs-tcl/tcl/apm-procs.tcl 28 Sep 2018 08:40:15 -0000 1.113 @@ -640,7 +640,7 @@ apm_load_libraries -force_reload=$force_reload_p -init -packages $unique_packages } - # Load up the Automated Tests initialisation scripts if necessary + # Load up the Automated Tests initialization scripts if necessary if {$load_tests_p} { apm_load_libraries -force_reload=$force_reload_p -packages $packages_to_load -test_init } Index: openacs-4/packages/acs-tcl/tcl/http-client-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-tcl/tcl/http-client-procs.tcl,v diff -u -r1.26 -r1.27 --- openacs-4/packages/acs-tcl/tcl/http-client-procs.tcl 28 Aug 2018 13:02:38 -0000 1.26 +++ openacs-4/packages/acs-tcl/tcl/http-client-procs.tcl 28 Sep 2018 08:40:15 -0000 1.27 @@ -366,7 +366,7 @@ # # (C) If neither A or B apply (e.g., because an invalid charset # name was given to the charset parameter), we default to - # "binary". This corresponds to the behaviour of + # "binary". This corresponds to the behavior of # [ns_encodingfortype]. Also note, that the RFCs 3023 and 2616 do # not state any procedure when "invalid" charsets etc. are # identified. I assume, RFC-compliant clients have to ignore them Index: openacs-4/packages/forums/lib/message/post.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/forums/lib/message/post.tcl,v diff -u -r1.29 -r1.30 --- openacs-4/packages/forums/lib/message/post.tcl 27 Jun 2018 17:09:07 -0000 1.29 +++ openacs-4/packages/forums/lib/message/post.tcl 28 Sep 2018 08:42:02 -0000 1.30 @@ -90,7 +90,7 @@ -form $form_elements \ -new_request { ############################## - # Form initialisation + # Form initialization # if {$parent_id eq ""} { set parent_id "" Index: openacs-4/packages/news/tcl/test/news-db-test-init.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/news/tcl/test/news-db-test-init.tcl,v diff -u -r1.16 -r1.17 --- openacs-4/packages/news/tcl/test/news-db-test-init.tcl 9 Jul 2018 10:03:30 -0000 1.16 +++ openacs-4/packages/news/tcl/test/news-db-test-init.tcl 28 Sep 2018 08:42:02 -0000 1.17 @@ -704,7 +704,7 @@ aa_log "News node_id :$_news_node_id" aa_log "News package_id :$_news_package_id" } else { - aa_error "Error from initialiser: $_news_package_mounted_err" + aa_error "Error from initializer: $_news_package_mounted_err" } } @@ -725,7 +725,7 @@ set news_id -1 if {!$_news_package_mounted_p} { - aa_error "News package not mounted, error from initialiser: $_news_package_mounted_err" + aa_error "News package not mounted, error from initializer: $_news_package_mounted_err" } else { # # Attempt to create the article @@ -854,7 +854,7 @@ set news_id -1 if {!$_news_package_mounted_p} { - aa_error "News package not mounted, error from initialiser: $_news_package_mounted_err" + aa_error "News package not mounted, error from initializer: $_news_package_mounted_err" } else { # # Create the article @@ -1006,7 +1006,7 @@ set news_id -1 if {!$_news_package_mounted_p} { - aa_error "News package not mounted, error from initialiser: $_news_package_mounted_err" + aa_error "News package not mounted, error from initializer: $_news_package_mounted_err" } else { # # Attempt to create the article @@ -1108,7 +1108,7 @@ set news_id -1 if {!$_news_package_mounted_p} { - aa_error "News package not mounted, error from initialiser: $_news_package_mounted_err" + aa_error "News package not mounted, error from initializer: $_news_package_mounted_err" } else { # # Create the article @@ -1263,7 +1263,7 @@ set news_id -1 if {!$_news_package_mounted_p} { - aa_error "News package not mounted, error from initialiser: $_news_package_mounted_err" + aa_error "News package not mounted, error from initializer: $_news_package_mounted_err" } else { # # Create the article Index: openacs-4/packages/xotcl-core/tcl/http-client-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/xotcl-core/tcl/http-client-procs.tcl,v diff -u -r1.37 -r1.38 --- openacs-4/packages/xotcl-core/tcl/http-client-procs.tcl 5 Aug 2018 21:16:25 -0000 1.37 +++ openacs-4/packages/xotcl-core/tcl/http-client-procs.tcl 28 Sep 2018 08:43:01 -0000 1.38 @@ -253,7 +253,7 @@ # # (C) If neither A or B apply (e.g., because an invalid charset # name was given to the charset parameter), we default to - # "binary". This corresponds to the behaviour of + # "binary". This corresponds to the behavior of # [ns_encodingfortype]. Also note, that the RFCs 3023 and 2616 do # not state any procedure when "invalid" charsets etc. are # identified. I assume, RFC-compliant clients have to ignore them @@ -759,7 +759,7 @@ # TLS/SSL support # # Perform HTTPS requests via TLS (does not require nsopenssl) - # - requires tls 1.5.0 to be compiled into
/lib/ ... + # - requires tls 1.5.0 to be compiled into /lib/ ... # - - - - - - - - - - - - - - - - - - # - see http://www.ietf.org/rfc/rfc2246.txt # - http://wp.netscape.com/eng/ssl3/3-SPEC.HTM Index: openacs-4/packages/xowiki/tcl/xowiki-utility-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/xowiki/tcl/xowiki-utility-procs.tcl,v diff -u -r1.56 -r1.57 --- openacs-4/packages/xowiki/tcl/xowiki-utility-procs.tcl 21 Jul 2018 11:56:37 -0000 1.56 +++ openacs-4/packages/xowiki/tcl/xowiki-utility-procs.tcl 28 Sep 2018 08:43:01 -0000 1.57 @@ -547,7 +547,7 @@ # Another possibility: not ago, but "Today 10:00", "Yesterday 10:00", within a # week: "Thursday 10:00", older than about 30 days "13 May 2005" and - # if anything else (ie. > 7 and < 30 days) it shows date and time "13-Oct 2005 10:00". + # if anything else (i.e. > 7 and < 30 days) it shows date and time "13-Oct 2005 10:00". if {![info exists timestamp_base]} {set timestamp_base [clock seconds]} set age_seconds [expr {$timestamp_base - $timestamp}]