livecode · livecodepanos · Sep 18, 2019 · May 24, 2019 · May 30, 2019 · May 30, 2019
diff --git a/buildbot.mk b/buildbot.mk
@@ -98,7 +98,7 @@ buildtool_command = $(LIVECODE) -ui $(BUILDTOOL_STACK) \
 # Settings for upload
 RSYNC ?= rsync
 SHA1SUM ?= sha1sum
-UPLOAD_SERVER ?= meg.on-rev.com
+UPLOAD_SERVER ?= molly.livecode.com
 UPLOAD_PATH = staging/$(BUILD_LONG_VERSION)/$(GIT_VERSION)
 UPLOAD_MAX_RETRIES = 50
 

diff --git a/docs/dictionary/command/mobileControlCreate.lcdoc b/docs/dictionary/command/mobileControlCreate.lcdoc
@@ -71,6 +71,14 @@ To read a property of a native control use: <mobileControlGet>
 
 To control the behavior of a native control use: <mobileControlDo> 
 
+>*Note:* If a player is created with an invalid filename or if the file is
+> missing, the video controller will display incorrectly. To check if a 
+> player is set up correctly, the following code could be used:
+
+    if mobileControlGet(sPlayerID, "duration") < 0 then
+        answer "Player is not initialised correctly"
+    end if
+
 References: mobileControlDelete (command), mobileControlDo (command),
 mobileControlSet (command),
 mobileControlGet (function), mobileControlTarget (function),

diff --git a/docs/dictionary/command/mobileControlSet.lcdoc b/docs/dictionary/command/mobileControlSet.lcdoc
@@ -191,6 +191,14 @@ directionalLockEnabled property). This is a boolean value.
 - "filename": The filename of URL of the media to play. Setting the
 filename of the player automatically 'prepares' the movie for playback.
 
+>*Note:* If the filename set for a player is invalid or the file is missing, 
+> the video controller will display incorrectly. To check if a player is 
+> set up correctly, the following code could be used:
+
+    if mobileControlGet(sPlayerID, "duration") < 0 then
+        answer "Player is not initialised correctly"
+    end if
+
 - "showController": Determines whether the controller is displayed over
 the content. This is a boolean value.
 

diff --git a/docs/dictionary/command/mobilePickDate.lcdoc b/docs/dictionary/command/mobilePickDate.lcdoc
@@ -67,8 +67,6 @@ Android is "date"
 
 - "datetime" (default on iOS) (iOS only): display a native picker to
   choose the date and time
-
-
 -   "date" (default on Android): display a native picker to choose the
     date 
 -   "time": display a native picker to choose the time

diff --git a/docs/dictionary/command/mobileSetFullScreenRectForOrientations.lcdoc b/docs/dictionary/command/mobileSetFullScreenRectForOrientations.lcdoc
@@ -53,4 +53,5 @@ the <mobileAllowedOrientations>.
 References: mobileLockOrientation (command), mobileSetAllowedOrientations (command),
 mobileUnlockOrientation (command), mobileAllowedOrientations (function),
 mobileDeviceOrientation (function), mobileOrientation (function),
-orientationChanged (message), resizeStack (message)
+orientationChanged (message), resizeStack (message),
+fullscreenMode (property)
diff --git a/docs/dictionary/command/mobileSetLocationHistoryLimit.lcdoc b/docs/dictionary/command/mobileSetLocationHistoryLimit.lcdoc
@@ -70,6 +70,6 @@ mobileStartTrackingSensor (command),
 mobileGetLocationHistory (function),
 mobileGetLocationHistoryLimit (function),
 mobileSensorAvailable (function), mobileSensorReading (function),
-mobileLocationAuthorizationStatus (function),
+mobileLocationAuthorizationStatus (function), function (glossary),
 locationChanged (message), trackingError (message)
 
diff --git a/docs/dictionary/command/pop.lcdoc b/docs/dictionary/command/pop.lcdoc
@@ -37,10 +37,10 @@ If you specify a container, the long <ID> of the <card> is placed in the
 change. 
 
 If the list is empty when you use the <pop> <command>, LiveCode goes to
-the Home <card>. If you are running in the LiveCode <development
-environment>, this is the first <card> of the "license.rev" <stack>,
-which is the splash screen that appears when you start up LiveCode.
-(Click this card to close the stack.) If you are running in a
+the Home <card>. If you are running in the LiveCode 
+<development environment>, this is the first <card> of the "license.rev" 
+<stack>, which is the splash screen that appears when you start up 
+LiveCode. (Click this card to close the stack.) If you are running in a
 <standalone application>, the Home <card> is the first <card> of the
 <standalone application|standalone's> <main stack>.
 

diff --git a/docs/dictionary/command/popup-widget.lcdoc b/docs/dictionary/command/popup-widget.lcdoc
@@ -34,18 +34,28 @@ end mouseDown
 
 Parameters:
 kind: The unique identifier of the widget to use for the popup.
-location: A point or expression that evaluates to a point. Two integers separated by a comma.
-properties:	An expression that evaluates to an array. For each key of the array, the popup widget will be initialized by setting that property to the value for that key.
+location: A point or expression that evaluates to a point. Two integers 
+separated by a comma.
+properties: An expression that evaluates to an array. For each key of the 
+array, the popup widget will be initialized by setting that property to 
+the value for that key.
 
-The result: If the user dismisses the popup, the it variable is set to empty, and the result function returns "Cancel".
+The result: If the user dismisses the popup, the it variable is set to 
+empty, and the result function returns "Cancel".
 
-It: The <popup widget> command places the widget return value in the it variable.
+It: The <popup widget> command places the widget return value in the it 
+variable.
 
 Description:
-Use to display a widget within a popup window, for example as a tooltip or picker dialog.
+Use to display a widget within a popup window, for example as a tooltip 
+or picker dialog.
 
-The popup appears with its top left corner at the <location>. If no <location> is specified, the popup's top left corner is at the <mouse location>. While the popup widget is displayed, the handler pauses.
+The popup appears with its top left corner at the <location>. If no 
+<location> is specified, the popup's top left corner is at the 
+<mouseLoc|mouse location>. While the popup widget is displayed, the 
+handler pauses.
 
-References: mouseDown (message), mouseDown message (message), mouseUp message (message), popup (keyword), clickLoc (function), mouse location (function), result (function), it (keyword)
+References: mouseDown (message), mouseUp (message), popup (keyword), 
+clickLoc (function), mouseLoc (function), result (function), it (keyword)
 
 Tags: widget
diff --git a/docs/dictionary/command/popup.lcdoc b/docs/dictionary/command/popup.lcdoc
@@ -55,7 +55,7 @@ clicked control in the stack (for a stack menu). The button or stack
 menu handles the menu choice.
 
 If you use a button to hold the contents of the menu, the contents of
-the button's <menuItem Keyword> is displayed in the popup.
+the button's <menuItem> is displayed in the popup.
 
 **Important:**  If you use a button to hold the contents of the menu,
 the following properties must be set:
@@ -82,8 +82,8 @@ parameter of the <mouseDown(message)> message, as described above.
 References: pulldown (command), clickLoc (function), mouseLoc (function),
 menu item (glossary), popup menu (glossary), button (keyword),
 menuItem (keyword), popup (keyword), menuPick (message),
-mouseDown (message), mouseDown (message), mouseUp (message), message (glossary),
-stack (object), button (object), style property (property),
+mouseDown (message), mouseDown (message), mouseUp (message), 
+message (glossary), stack (object), button (object), style (property),
 toolTip (property), menuMode (property), visible (property),
 menuMouseButton (property)
 

diff --git a/docs/dictionary/command/post.lcdoc b/docs/dictionary/command/post.lcdoc
@@ -5,7 +5,7 @@ Type: command
 Syntax: post <data> to URL <destinationURL>
 
 Summary:
-Sends data to a <web server> using the POST action of <HTTP>.
+Sends data to a <web server> using the POST action of <http|HTTP>.
 
 Associations: internet library
 
@@ -120,11 +120,13 @@ function (control structure), result (function), URLStatus (function),
 URLEncode (function), libURLFormData (function), URLDecode (function),
 libURLMultipartFormAddPart (function), libURLMultipartFormData (function),
 variable (glossary), command (glossary), 
-Livecode custom library (glossary), property (glossary),
+LiveCode custom library (glossary), property (glossary),
 standalone application (glossary), blocking (glossary), 
 web server (glossary), command (glossary), expression (glossary), 
 syntax (glossary), server (glossary), upload (glossary), 
-statement (glossary), handler (glossary), URL (keyword), ftp (keyword), 
+statement (glossary), handler (glossary), 
+Standalone Application Settings (glossary),
+URL (keyword), ftp (keyword), 
 http (keyword), Internet library (library), urlProgress (message), 
 httpHeaders (property), HTTPProxy (property)
 
diff --git a/docs/dictionary/command/request.lcdoc b/docs/dictionary/command/request.lcdoc
@@ -34,18 +34,14 @@ omit the zone. If the other program is running on the same computer, you
 can omit both the zone and the computer name.
 
 It:
-If the program supports this <Apple Event>, it evaluates the expression
-and sends the result back to LiveCode, which places it in the <it>
-<variable>. The <request> <command> sends aneval <Apple Event> to the
+The <request> <command> sends an eval <Apple Event> to the
 <programAddress>. If the program supports this <Apple Event>, it
 evaluates the expression and sends the result back to LiveCode, which
 places it in the <it> <variable>.
 
 The result:
-If the program supports this <Apple event>, it evaluates the expression
-and sends the result back to LiveCode, which places it in the <it>
-<variable>. If the program sends back an error message, it is placed in
-the result <function>.
+If the program sends back an error message, it is placed in the result 
+<function>.
 
 Description:
 Use the <request> <command> to obtain data from another application via

diff --git a/docs/dictionary/command/revXMLRPC_SetSocket.lcdoc b/docs/dictionary/command/revXMLRPC_SetSocket.lcdoc
@@ -52,6 +52,6 @@ revXMLRPC_CreateRequest (function), return (glossary),
 XML-RPC (glossary), Standalone Application Settings (glossary),
 socket (glossary), standalone application (glossary), function (glossary),
 command (glossary), LiveCode custom library (glossary),
-XML-RPC library (library), XML-RPC document (library)
+XML-RPC document (glossary), XML-RPC library (library) 
 
 Tags: networking
diff --git a/docs/dictionary/command/rotate.lcdoc b/docs/dictionary/command/rotate.lcdoc
@@ -62,14 +62,15 @@ the <angle> <property> affects only the screen display of the
 <image(keyword)>, not the actual picture data in it, so setting it
 repeatedly does not introduce distortion.
 
->*Note:*Rotating an image using good or best <resizeQuality> might
+>*Note:* Rotating an image using good or best <resizeQuality> might
 > cause the mask to be promoted to an alpha channel.
 
 >*Note:* As rotate is an image editing operation, the target image needs
 > to be on the currently visible card of an open stack to function.
 
->*Important:* The rotate <command> cannot be used on a <referenced
-> control|referenced image>. Doing so will cause an <execution error>.
+>*Important:* The rotate <command> cannot be used on a 
+> <referenced control|referenced image>. Doing so will cause an 
+> <execution error>.
 > To turn a <referenced control|referenced image>, set the
 > <image(object)|image's><angle (property)> <property> instead.
 

diff --git a/docs/dictionary/command/send.lcdoc b/docs/dictionary/command/send.lcdoc
@@ -117,10 +117,10 @@ It is a parse error to specify a time when using the `script` form.
 > <message> is sent.
 
 >*Note:*  Using the <send> <command> is slower than directly
-> <execute|executing> the <command|commands> using the normal <message
-> path>. For best efficiency, use the <send> <command> only when you
-> want to delay the <message> or when the <handler> you want to execute
-> is not in the <message path>.
+> <execute|executing> the <command|commands> using the normal 
+> <message path>. For best efficiency, use the <send> <command> only when 
+> you want to delay the <message> or when the <handler> you want to 
+> execute is not in the <message path>.
 
 References: debugDo (command), dispatch (command), call (command),
 cancel (command), function (control structure), result (function),

diff --git a/docs/dictionary/command/show.lcdoc b/docs/dictionary/command/show.lcdoc
@@ -64,7 +64,7 @@ References: hide (command), answer effect (command),
 show groups (command), show cards (command), show taskbar (command),
 visual effect (command), object (glossary), command (glossary), 
 property (glossary), QuickTime (glossary), black (keyword), 
-dontUserQT (property), dontUseQTEffects(property), showPict (property), 
+dontUseQT (property), dontUseQTEffects(property), showPict (property), 
 toolTip (property), imageSource (property), showInvisibles (property), 
 visible (property)
 

diff --git a/docs/dictionary/function/URLDecode.lcdoc b/docs/dictionary/function/URLDecode.lcdoc
@@ -41,13 +41,25 @@ the next two characters as <hexadecimal> digits. (If one of the
 number is converted to its <character> equivalent, using the 
 <character set> currently in use.
 
+>*Note:* Non-ASCII characters, such as Unicode, that appear in the URL 
+> string to be decoded will have been encoded as UTF-8 (as per standard 
+> convention), requiring the use of the <textDecode> <function(glossary)> 
+> after urlDecode. For example, the following code:
+
+    local tEncodedText
+    put "%D1%81%D0%BA%D0%BE%D1%80%D0%BE%D1%81%D1%88%D0%B8%D0" & \
+          "%B2%D0%B0%D1%82%D0%B5%D0%BB%D1%8C" into tCodedText
+    put textDecode(urlDecode(tEncodedText),"UTF-8")
+
+> produces the word "скоросшиватель".
+
 References: post (command), function (control structure),
 decompress (function), macToISO (function), arrayDecode (function),
-charToNum (function), baseConvert (function), decode (glossary),
-return (glossary), sign (glossary), encode (glossary),
+charToNum (function), baseConvert (function), textDecode (function),
+decode (glossary), return (glossary), sign (glossary), encode (glossary),
 character set (glossary), hexadecimal (glossary), server (glossary),
-URL (keyword), characters (keyword), character (keyword), http (keyword),
-httpHeaders (property)
+function (glossary), URL (keyword), characters (keyword), 
+character (keyword), http (keyword), httpHeaders (property)
 
 Tags: networking
 
diff --git a/docs/dictionary/function/URLEncode.lcdoc b/docs/dictionary/function/URLEncode.lcdoc
@@ -62,7 +62,13 @@ appears in the formString, it is converted to "%7E".
         return pString
     end urlEncodeRFC
 
+>*Note:* Non-ASCII characters, such as Unicode, that appear in the string
+> to be encoded must first be encoded as UTF-8 (as per standard 
+> convention), requiring the use of the <textEncode> <function(glossary)>.
+> The code example given above can perform this task.
+
 References: post (command), function (control structure),
+textEncode (function), function (glossary),
 hexadecimal (glossary), encode (glossary), ASCII (glossary), 
 return (glossary), server (glossary), URL (keyword), 
 character (keyword), http (keyword), string (keyword)

diff --git a/docs/dictionary/function/mobileSensorReading.lcdoc b/docs/dictionary/function/mobileSensorReading.lcdoc
@@ -38,19 +38,21 @@ false
 
 
 Returns:
-Location -  a comma separated list of the latitude, longitude and
+-   Location -  a comma separated list of the latitude, longitude and
 altitude of the device. If any of these readings are not available, an
 empty item will be returned in its place. If <detailed> is true an array
 containing the keys latitude, longitude, altitude, timestamp, horizontal
-accuracy and vertical accuracy is returned. Heading - the heading of the
+accuracy and vertical accuracy is returned. 
+-   Heading - the heading of the
 device in degrees. If <detailed> is true an array containing the keys
 heading, magnetic heading, true heading, timestamp, x, y, z and accuracy
-is returned. Acceleration - a comma separated list of the acceleration
+is returned. 
+-   Acceleration - a comma separated list of the acceleration
 in the x, y and z axes. If <detailed> is true an array containing the
-keys x, y, z and timestamp is returned. Rotation Rate - a comma
-separated list of the rate of rotation around the x, y and z axes. If
-<detailed> is true an array containin the keys x, y, z and timestamp is
-returned. 
+keys x, y, z and timestamp is returned. 
+-   Rotation Rate - a comma separated list of the rate of rotation 
+around the x, y and z axes. If <detailed> is true an array containing 
+the keys x, y, z and timestamp is returned. 
 
 Description:
 Use the <mobileSensorReading> function to fetch a reading from the named

diff --git a/docs/dictionary/function/mouseChunk.lcdoc b/docs/dictionary/function/mouseChunk.lcdoc
@@ -43,8 +43,8 @@ the first <character> of the <word>, and the endChar is the last
 To get the text of the word or text group, use the mouseText <function>.
 
 >*Important:*  Words are defined a little differently by the
-> <mouseChunk> <function> than the way they are used in <chunk
-> expression|chunk expressions>. A word, for purposes of the
+> <mouseChunk> <function> than the way they are used in 
+> <chunk expression|chunk expressions>. A word, for purposes of the
 > <mouseChunk>, is any text delimited by spaces, tabs, returns, or
 > punctuation. If the mouse pointer is over a punctuation <character>,
 > only that <character> is returned.

diff --git a/docs/dictionary/function/mouseControl.lcdoc b/docs/dictionary/function/mouseControl.lcdoc
@@ -52,7 +52,7 @@ References: function (control structure), within (function),
 mouseCharChunk (function), property (glossary), mouse pointer (glossary),
 return (glossary), string (keyword), control (keyword), graphic (keyword),
 mouseEnter (message), mouseLeave (message), stack (object),
-control (object), graphic (object), filled (property), layer (property)
+graphic (object), filled (property), layer (property)
 
 Tags: ui
 
diff --git a/docs/dictionary/function/param.lcdoc b/docs/dictionary/function/param.lcdoc
@@ -62,9 +62,13 @@ to assign it a name:
 
 
 LiveCode evaluates the parameters before passing them. So if you call
-myHandler with the following statement: myHandler 1+1,"A","Hello" &&
-"world" the parameters returned by the <param> <function> are 2, A,
-and "Hello World".
+myHandler with the following statement: 
+
+     myHandler 1+1,"A","Hello" && "world" 
+
+the parameters returned by the <param> <function> are 
+
+    2, A, and "Hello World".
 
 References: function (control structure), paramCount (function),
 pass (glossary), handler (glossary), parameter (glossary),

diff --git a/docs/dictionary/function/params.lcdoc b/docs/dictionary/function/params.lcdoc
@@ -75,11 +75,16 @@ If you call "myFunction" with the following statement:
 
     get myFunction("red","green","blue")
 
-the value returned by the <params> function is "myFunction("red","green","blue")".
+the value returned by the <params> function is 
+
+    "myFunction("red","green","blue")".
 
 LiveCode evaluates the parameters before passing them. So if you call
-myHandler with the following statement: myHandler 1+1,"A","Hello" &&
-"world" the value returned by the <params> <function> is
+myHandler with the following statement: 
+
+    myHandler 1+1,"A","Hello" && "world" 
+
+the value returned by the <params> <function> is 
 
     myHandler "2","A","Hello world"
 

diff --git a/docs/dictionary/function/revXMLRPC_CreateRequest.lcdoc b/docs/dictionary/function/revXMLRPC_CreateRequest.lcdoc
@@ -50,25 +50,25 @@ positive <integer>. If the function encounters an error while parsing
 the data, it returns an error message beginning with "xmlrpcerr".
 
 Description:
-Use the <revXMLRPC_CreateRequest> <function> to create an <XML-RPC
-document> that you can use with other <XML-RPC library>
+Use the <revXMLRPC_CreateRequest> <function> to create an 
+<XML-RPC document> that you can use with other <XML-RPC library>
 <command|commands> and <function|functions>. <XML-RPC> is a
 remote procedure call (RPC) protocol which uses XML to encode its
 calls via a <HTTP> transport mechanism.
 
-If the <host> is empty, the <revXMLRPC_CreateRequest> <function>
+If the <RPChost> is empty, the <revXMLRPC_CreateRequest> <function>
 defaults the request host to be the computer running the application,
 also known as "localhost"
 
-If the <port> is empty, the <revXMLRPC_CreateRequest> <function>
+If the <RPCport> is empty, the <revXMLRPC_CreateRequest> <function>
 defaults the request port to 80, which is the default port for <HTTP>
 connections.
 
-If the <path> is empty, the <revXMLRPC_CreateRequest> <function>
+If the <filePath> is empty, the <revXMLRPC_CreateRequest> <function>
 defaults the request path to "RPC2", which is the standard path for
 <XML-RPC> server resources.
 
-If the <protocol> is empty, the <revXMLRPC_CreateRequest> <function>
+If the <connProtocol> is empty, the <revXMLRPC_CreateRequest> <function>
 defaults the request protocol to <HTTP> connections.
 
 If the <revXMLRPC_CreateRequest> <function> encounters an error, it