Menu
▾
▴
[phpwiki-checkins] SF.net SVN: phpwiki:[9859] trunk/pgsrc
|
From: <var...@us...> - 2016-07-07 13:59:32
|
Revision: 9859
http://sourceforge.net/p/phpwiki/code/9859
Author: vargenau
Date: 2016-07-07 13:59:29 +0000 (Thu, 07 Jul 2016)
Log Message:
-----------
Wikicreole syntax; smart quotes
Modified Paths:
--------------
trunk/pgsrc/Help%2FAdvice%20for%20Mediawiki%20users
trunk/pgsrc/Help%2FAnalyseAccessLogSqlPlugin
trunk/pgsrc/Help%2FPagePermissions
trunk/pgsrc/Help%2FWabiSabi
Modified: trunk/pgsrc/Help%2FAdvice%20for%20Mediawiki%20users
===================================================================
--- trunk/pgsrc/Help%2FAdvice%20for%20Mediawiki%20users 2016-06-25 19:47:28 UTC (rev 9858)
+++ trunk/pgsrc/Help%2FAdvice%20for%20Mediawiki%20users 2016-07-07 13:59:29 UTC (rev 9859)
@@ -1,4 +1,4 @@
-Date: Thu, 10 Dec 2015 18:48:03 +0000
+Date: Thu, 7 Jul 2016 15:54:03 +0000
Mime-Version: 1.0 (Produced by PhpWiki 1.5.5)
Content-Type: application/x-phpwiki;
pagename=Help%2FAdvice%20for%20Mediawiki%20users;
@@ -16,8 +16,8 @@
* Italics are ##//## (but you can also use ##''## like in Wikipedia)
* Bold is ##~*~*## (you //cannot use// ##'''## like in Wikipedia)
* Line break is ##~\~\## in Wikicreole, ##~<br />## in Mediawiki
-* There is **no automatic capitalisation** of first character of page name. Pages *<samp>~[~[foo~]~]</samp>* and *<samp>~[~[Foo~]~]</samp>* are different.
-* A space in a page name in not equivalent to an underscore. Pages *<samp>~[~[foo bar~]~]</samp>* and *<samp>~[~[foo_bar~]~]</samp>* are different. We recommend to use a space in the page names.
+* There is **no automatic capitalisation** of first character of page name. Pages **<samp>~[~[foo~]~]</samp>** and **<samp>~[~[Foo~]~]</samp>** are different.
+* A space in a page name in not equivalent to an underscore. Pages **<samp>~[~[foo bar~]~]</samp>** and **<samp>~[~[foo_bar~]~]</samp>** are different. We recommend to use a space in the page names.
* Many things that are built-in in Mediawiki use plug-ins in Phpwiki (table of contents, redirections, back links, etc.).
* Redirections are less sophisticated in Phpwiki (e.g. backlinks do not show redirected pages)
Modified: trunk/pgsrc/Help%2FAnalyseAccessLogSqlPlugin
===================================================================
--- trunk/pgsrc/Help%2FAnalyseAccessLogSqlPlugin 2016-06-25 19:47:28 UTC (rev 9858)
+++ trunk/pgsrc/Help%2FAnalyseAccessLogSqlPlugin 2016-07-07 13:59:29 UTC (rev 9859)
@@ -1,4 +1,4 @@
-Date: Thu, 10 Dec 2015 18:48:03 +0000
+Date: Thu, 7 Jul 2016 15:54:03 +0000
Mime-Version: 1.0 (Produced by PhpWiki 1.5.5)
Content-Type: application/x-phpwiki;
pagename=Help%2FAnalyseAccessLogSqlPlugin;
@@ -13,7 +13,7 @@
A small number of queries that may (or might not) use the ~MySQL
specific dialect of SQL are provided in ##lib/plugin/~AnalyseAccessLogSql.php##.
-For more information, please see the section *Adding new queries* below.
+For more information, please see the section **Adding new queries** below.
== Usage ==
@@ -32,15 +32,15 @@
! Default value
|-
| **mode**
-| The name of the query to execute. See *Adding new queries* below. Required parameter.
+| The name of the query to execute. See **Adding new queries** below. Required parameter.
| referring_domains
|-
| **period**
-| Use in combination with the _count_ parameter. The type of history period to retrieve from the SQL access log. Blank (the default) for all history, or one of "*weeks*", "*days*", "*hours*", or "*minutes*".
+| Use in combination with the //count// parameter. The type of history period to retrieve from the SQL access log. Blank (the default) for all history, or one of “**weeks**”, “**days**”, “**hours**”, or “**minutes**”.
|
|-
| **count**
-| Use in combination with the _period_ parameter. Must be a number. The number of periods to retrieve from the access log.
+| Use in combination with the //period// parameter. Must be a number. The number of periods to retrieve from the access log.
| 0
|-
| **caption**
@@ -56,7 +56,7 @@
|
|-
| **user**
-| Blank (the default) to retrieve all users, or a specific user, or "*<NONE>*" for SQL access log entries with no user.
+| Blank (the default) to retrieve all users, or a specific user, or “**<NONE>**” for SQL access log entries with no user.
|
|-
| **host**
@@ -64,7 +64,7 @@
|
|-
| **referrer**
-| Blank (the default) to retrieve all referrers, "*<NONE>*" to retrieve entries with no referrer, otherwise any referrer that matches this parameter, truncating longer referrers before matching. So a parameter of referrer='~http://localhost' will match '~http://localhost/wiki/index.php', '~http://localhost/wiki/index.php/~HomePage' etc.
+| Blank (the default) to retrieve all referrers, “**<NONE>**” to retrieve entries with no referrer, otherwise any referrer that matches this parameter, truncating longer referrers before matching. So a parameter of referrer='~http://localhost' will match '~http://localhost/wiki/index.php', '~http://localhost/wiki/index.php/~HomePage' etc.
|
|-
| **local_referrers**
@@ -77,7 +77,7 @@
The file ##lib/plugin/~AnalyseAccessLogSql.php## contains a default set of queries against the SQL access log.
Feel free to change this file to suit your own needs, but please note that this requires filesystem access to the web server where ~PhpWiki is running.
In particular, this file may need to be modified to correctly query databases other than MySQL.
-The queries supplied by default are: "*Referring URLs*", "*Referring Domains*", "*Remote Hosts*", "*Users*" and "*Host Users*".
+The queries supplied by default are: “**Referring URLs**”, “**Referring Domains**”, “**Remote Hosts**”, “**Users**” and “**Host Users**”.
To add a new query, add a new section towards the end of the file, using one of the existing queries as a template. An example of an existing query is:
<pre>
@@ -95,27 +95,27 @@
== API for ~AnalyseAccessLogSql ==
* input arguments:
- - *$mode* contains the name of the query requested in the plugin parameters.
- - *$accesslog* contains the qualified name of the accesslog table, which may or may not be equal to "accesslog".
- - *$whereConditions* contains the conditions (specific user, etc.) requested in the plugin parameters.
+ - **$mode** contains the name of the query requested in the plugin parameters.
+ - **$accesslog** contains the qualified name of the accesslog table, which may or may not be equal to “accesslog”.
+ - **$whereConditions** contains the conditions (specific user, etc.) requested in the plugin parameters.
* output:
- - *$query* must contain the final SQL query to be executed.
+ - **$query** must contain the final SQL query to be executed.
* conventions:
- While constructing the query string,
* each clause is on a separate line and
* each clause contains the required trailing punctuation or space.
- The mode parameter is, by default, displayed as the caption in the final output, so please choose a user friendly name.
- - The column names displayed on the wiki page are generated from the SQL column names defined in the queries, so please choose user friendly names. MySQL allows column names to include spaces. If spaces are not allowed, then "*_*" is probably the next best choice.
+ - The column names displayed on the wiki page are generated from the SQL column names defined in the queries, so please choose user friendly names. MySQL allows column names to include spaces. If spaces are not allowed, then “**_**” is probably the next best choice.
* language hints for PHP newbies - please remember:
- - terminate statements with "*;*",
- - assignment uses "*=*" and comparison uses "*==*",
- - concatenate strings using the "*.*" operator,
- - the parentheses around the expression "*=($whereConditions ? 'WHERE '.$whereConditions : '' )=*" are essential,
+ - terminate statements with “**;**”,
+ - assignment uses “**=**” and comparison uses “**==**”,
+ - concatenate strings using the “**.**” operator,
+ - the parentheses around the expression “**=($whereConditions ? 'WHERE '.$whereConditions : '' )=**” are essential,
- strings enclosed in single quotes may not contain substrings enclosed in single quotes (actually the truth is more complex but let's leave it like that here), and
- - strings enclosed in double quotes will evaluate and replace variable names so that, for example, *"FROM $accesslog "* might be evaluated to *"FROM phpwiki_accesslog "*.
+ - strings enclosed in double quotes will evaluate and replace variable names so that, for example, **"FROM $accesslog"** might be evaluated to **"FROM phpwiki_accesslog"**.
== Authors ==
* Charles Corrigan
Modified: trunk/pgsrc/Help%2FPagePermissions
===================================================================
--- trunk/pgsrc/Help%2FPagePermissions 2016-06-25 19:47:28 UTC (rev 9858)
+++ trunk/pgsrc/Help%2FPagePermissions 2016-07-07 13:59:29 UTC (rev 9859)
@@ -1,4 +1,4 @@
-Date: Thu, 10 Dec 2015 18:48:03 +0000
+Date: Thu, 7 Jul 2016 15:54:03 +0000
Mime-Version: 1.0 (Produced by PhpWiki 1.5.5)
Content-Type: application/x-phpwiki;
pagename=Help%2FPagePermissions;
@@ -55,15 +55,15 @@
list in PageList => list
}}}
-For simplicity we also map the ACL to the posix-style _owner_, _group_ and _world_ groups
-and _read_, _write_, _execute_ perms, in cygwin fashion.
+For simplicity we also map the ACL to the posix-style //owner//, //group// and //world// groups
+and //read//, //write//, //execute// perms, in cygwin fashion.
== Groups - definition of group membership ==
See ~WikiGroup how to enable and where to store user-specific group membership.
Group methods: database, file, ldap, wikipage, none
-To do: _explain better._
+To do: //explain better.//
The following special groups are always predefined, even if no other group methods are provided:
* _EVERY
@@ -85,7 +85,7 @@
== Perms - mapping of actions to permissions ==
~PhpWiki supports individual actions, the default is browse. To simplify ACL's these
-actions are mapped to some special permissions (vulgo _'perms'_).
+actions are mapped to some special permissions (vulgo //'perms'//).
We currently support the following permissions which can be stored in every page, for every group.
Modified: trunk/pgsrc/Help%2FWabiSabi
===================================================================
--- trunk/pgsrc/Help%2FWabiSabi 2016-06-25 19:47:28 UTC (rev 9858)
+++ trunk/pgsrc/Help%2FWabiSabi 2016-07-07 13:59:29 UTC (rev 9859)
@@ -1,4 +1,4 @@
-Date: Thu, 10 Dec 2015 18:48:03 +0000
+Date: Thu, 7 Jul 2016 15:54:03 +0000
Mime-Version: 1.0 (Produced by PhpWiki 1.5.5)
Content-Type: application/x-phpwiki;
pagename=Help%2FWabiSabi;
@@ -10,26 +10,25 @@
aesthetic system, it is difficult to explain precisely in western
terms. According to Leonard Koren, wabi-sabi is the most conspicuous
and characteristic feature of what we think of as traditional Japanese
-beauty and it //"occupies roughly the same position in the Japanese
+beauty and it //“occupies roughly the same position in the Japanese
pantheon of aesthetic values as do the Greek ideals of beauty and
-perfection in the West."//
+perfection in the West.”//
-_"Wabi-sabi is a beauty of things imperfect, impermanent, and_
-_incomplete._
+//“Wabi-sabi is a beauty of things imperfect, impermanent, and incomplete.”//
-_"It is the beauty of things modest and humble._
+//“It is the beauty of things modest and humble.”//
-_"It is the beauty of things unconventional."_
+//“It is the beauty of things unconventional.”//
-(quoted from "[WABI-SABI: FOR ARTISTS,DESIGNERS, POETS & PHILOSOPHERS | http://www.amazon.com/exec/obidos/tg/detail/-/1880656124/qid=1054098290/sr=1-1/ref=sr_1_1/104-9834820-5562358?v=glance&s=books]," 1994, Leonard Koren)
+(quoted from “[[http://www.amazon.com/exec/obidos/tg/detail/-/1880656124/qid=1054098290/sr=1-1/ref=sr_1_1/104-9834820-5562358?v=glance&s=books|WABI-SABI: FOR ARTISTS,DESIGNERS, POETS & PHILOSOPHERS]],” 1994, Leonard Koren)
The concepts of wabi-sabi correlate with the concepts of Zen Buddhism,
as the first Japanese involved with wabi-sabi were tea masters,
priests, and monks who practiced Zen. Zen Buddhism originated in
India, traveled to China in the 6th century, and was first introduced
-in Japan around the 12th century. Zen emphasizes //"direct, intuitive
+in Japan around the 12th century. Zen emphasizes //“direct, intuitive
insight into transcendental truth beyond all intellectual
-conception."// At the core of wabi-sabi is the importance of
+conception.”// At the core of wabi-sabi is the importance of
transcending ways of looking and thinking about things/existence.
* All things are impermanent
@@ -38,14 +37,14 @@
(also taken from WABI-SABI: FOR ARTISTS,DESIGNERS, POETS & PHILOSOPHERS, 1994, Leonard Koren):
-_Material characteristics of wabi-sabi:_
+//Material characteristics of wabi-sabi://
-* _suggestion of natural process_
-* _irregular_
-* _intimate_
-* _unpretentious_
-* _earthy_
-* _simple_
+* //suggestion of natural process//
+* //irregular//
+* //intimate//
+* //unpretentious//
+* //earthy//
+* //simple//
For more about wabi-sabi, see [[http://c2.com/cgi/wiki?WabiSabi]].
This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.
|
