Merge pull request #440 from doc4d/main

updates and translations

Author: arnaud4d

docs/API/DataClassClass.md

@@ -184,7 +184,7 @@ In the optional *settings* parameter, you can pass an object containing addition
 <!-- REF #DataClassClass.clearRemoteCache().Syntax -->**.clearRemoteCache()**<!-- END REF -->
 
 
-<!-- REF #DataStoreClass.clearRemoteCache().Params -->
+<!-- REF #DataClassClass.clearRemoteCache().Params -->
 |Parameter|Type||Description|
 |---------|--- |:---:|------|
 ||||Does not require any parameters|

docs/API/EntityClass.md

@@ -928,7 +928,12 @@ A record locked by `.lock()` is unlocked:
 * when the [`unlock()`](#unlock) function is called on a matching entity in the same process
 * automatically, when it is no longer referenced by any entities in memory. For example, if the lock is put only on one local reference of an entity, the entity is unlocked when the function ends. As long as there are references to the entity in memory, the record remains locked.
 
-> An entity can also be [locked by a REST session](../REST/$lock.md), in which case it can only be unlocked by the session.
+:::note Notes
+
+- [`unlock()`](#unlock) must be called as many times as `lock()` was called in the same process for the entity to be actually unlocked.
+- An entity can also be [locked by a REST session](../REST/$lock.md), in which case it can only be unlocked by the session.
+
+:::
 
 By default, if the *mode* parameter is omitted, the function will return an error (see below) if the same entity was modified (i.e. the stamp has changed) by another process or user in the meantime.
 
@@ -1725,7 +1730,7 @@ The `.unlock()` function <!-- REF #EntityClass.unlock().Summary -->removes the p
 
 A record is automatically unlocked when it is no longer referenced by any entities in the locking process (for example: if the lock is put only on one local reference of an entity, the entity and thus the record is unlocked when the process ends).
 
->When a record is locked, it must be unlocked from the locking process and on the entity reference which put the lock. For example:
+When a record is locked, it must be unlocked from the locking process and on the entity reference which put the lock. For example:
 
 ```4d
  $e1:=ds.Emp.all()[0]
@@ -1735,6 +1740,13 @@ A record is automatically unlocked when it is no longer referenced by any entiti
  $res:=$e1.unlock() //$res.success=true
 ```
 
+:::note
+
+`unlock()` must be called as many times as [`lock()`](#lock) was called in the same process for the entity to be actually unlocked.
+
+:::
+
+
 **Result**
 
 The object returned by `.unlock()` contains the following property:

docs/FormObjects/properties_Object.md

@@ -101,32 +101,15 @@ You can use an [expression](Concepts/quick-tour.md#expressions) as data source f
 You can leave it up to 4D to create variables associated with your form objects (buttons, enterable variables, check boxes, etc.) dynamically and according to your needs. To do this, simply leave the "Variable or Expression" property (or `dataSource` JSON field) blank.
 
 When a variable is not named, when the form is loaded, 4D creates a new variable for the object, with a calculated name that is unique in the space of the process variables of the interpreter (which means that this mechanism can be used even in compiled mode). This temporary variable will be destroyed when the form is closed.
-In order for this principle to work in compiled mode, it is imperative that dynamic variables are explicitly typed. There are two ways to do this:
 
-- You can set the type using the [Expression type](#expression-type) property.
-- You can use a specific initialization code when the form is loaded that uses, for example, the `VARIABLE TO VARIABLE` command:
+To get or set the value of form objects that use dynamic variables, you just need to call [`OBJECT Get value`](../commands-legacy/object-get-value.md) and [`OBJECT SET VALUE`](../commands-legacy/object-set-value.md) commands. For example:
 
 ```4d
- If(Form event code=On Load)
-    var $init : Text
-    $Ptr_object:=OBJECT Get pointer(Object named;"comments")
-    $init:=""
-    VARIABLE TO VARIABLE(Current process;$Ptr_object->;$init)
- End if
+ var $value : Variant
+ $value:=OBJECT Get value("comments")
+ OBJECT SET VALUE("comments";$value+10) 
 ```
 
-In the 4D code, dynamic variables can be accessed using a pointer obtained with the `OBJECT Get pointer` command. For example:
-
-```4d
-  // assign the time 12:00:00 to the variable for the "tstart" object
- $p :=OBJECT Get pointer(Object named;"tstart")
- $p->:=?12:00:00?
-```
-
-There are two advantages with this mechanism:
-
-- On the one hand, it allows the development of "subform" type components that can be used several times in the same host form. Let us take as an example the case of a datepicker subform that is inserted twice in a host form to set a start date and an end date. This subform will use objects for choosing the date of the month and the year. It will be necessary for these objects to work with different variables for the start date and the end date. Letting 4D create their variable with a unique name is a way of resolving this difficulty.
-- On the other hand, it can be used to limit memory usage. In fact, form objects only work with process or inter-process variables. However, in compiled mode, an instance of each process variable is created in all the processes, including the server processes. This instance takes up memory, even when the form is not used during the session. Therefore, letting 4D create variables dynamically when loading the forms can save memory.
 
 ### Array List Box
 

docs/Notes/updates.md

@@ -15,6 +15,10 @@ Read [**What’s new in 4D 20 R10**](https://blog.4d.com/en-whats-new-in-4d-20-R
 - 4D Language:
 	- For consistency, [`Create entity selection`](../commands/create-entity-selection.md) and [`USE ENTITY SELECTION`](../commands/use-entity-selection.md) commands have been moved from the ["4D Environment"](../commands/theme/4D_Environment.md) to the ["Selection"](../commands/theme/Selection.md) themes.
 
+#### Behavior changes
+
+- On Windows, current printer fonts intended only for printing (i.e. not usable on screen) are no longer loaded by 4D at startup. 
+
 
 ## 4D 20 R9
 

docs/commands-legacy/get-pasteboard-data-type.md

@@ -11,7 +11,7 @@ displayed_sidebar: docs
 | --- | --- | --- | --- |
 | 4Dsignatures | Text array | ← | 4D signatures of data types |
 | nativeTypes | Text array | ← | Native data types |
-| formatNames | Text array | ← | Format names (Windows only), empty strings under Mac OS |
+| formatNames | Text array | ← | Format names or descriptions |
 
 <!-- END REF-->
 
@@ -26,7 +26,7 @@ This command returns the data types in several different forms via two (or three
    * Under Mac OS, native types are expressed as UTIs (Uniform Type Identifier).  
    * Under Windows, native types are expressed as numbers, with each number being associated with a format name. The *nativeTypes* array contains these numbers in the form of strings (“3”, “12”, and so on). If you want to use more explicit labels, it is recommended to use the optional *formatNames* array, which contains the format names of the native types under Windows.  
 The *nativeTypes* array lets any type of data found in the pasteboard to be supported, including data whose type is not referenced by 4D.
-* Under Windows, you can also pass the *formatNames* array, which receives the names of the data types found in the pasteboard. The values returned in this array can be used, for example, to build a format selection pop-up menu. Under Mac OS, the *formatNames* array returns empty strings.
+* You can also pass the *formatNames* array, which receives the names or descriptions of the data types found in the pasteboard. The values returned in this array can be used, for example, to build a format selection pop-up menu.
 
 For more information about the data types supported, please refer to the *Managing Pasteboards* section. 
 

docs/commands-legacy/listbox-get-row-color-as-number.md

@@ -34,7 +34,7 @@ In *row*, pass the number of the row whose color you want to get.
 
 **Note:** The command does not take any hidden/visible states of the list box rows into account.
 
-In the *colorType* parameter, you can pass either the lk background color or lk font color constant ("*List Box*" theme) in order to find out the background or font color for the row. If you omit this parameter, the font color is returned.
+In the *colorType* parameter, you can pass either the `lk background color`  or `lk font color`  constant ("*List Box*" theme) in order to find out the background or font color for the row. If you omit this parameter, the font color is returned.
 
 **Warning:** a color assigned to a row is not necessarily displayed in every cell of the row (see example). If conflicting color values are set using properties for list boxes or list box columns, an order of priority is applied. For more information, refer to the *Design Reference* manual.
 

docs/commands-legacy/listbox-get-row-color.md

@@ -34,7 +34,7 @@ In *row*, pass the number of the row whose color you want to get.
 
 **Note:** The command does not take any hidden/visible states of the list box rows into account.
 
-In the *colorType* parameter, you can pass either the lk background color or lk font color constant ("*List Box*" theme) in order to find out the background or font color for the row. If you omit this parameter, the font color is returned.
+In the *colorType* parameter, you can pass either the `lk background color`  or `lk font color`  constant ("*List Box*" theme) in order to find out the background or font color for the row. If you omit this parameter, the font color is returned.
 
 **Warning:** A color assigned to a row is not necessarily displayed in every cell of the row (see example). If conflicting color values are set using properties for list boxes or list box columns, an order of priority is applied. For more information, refer to the *Design Reference* manual.
 

docs/commands-legacy/listbox-set-row-color.md

@@ -34,9 +34,9 @@ In *row*, pass the number of the row where you want to apply the new color.
 
 **Note:** The command does not take any hidden/visible states of the list box rows into account.
 
-In *color*, pass an RGB color value. For more information about RGB colors, refer to the description of the [OBJECT SET RGB COLORS](object-set-rgb-colors.md) command. If you want the row to inherit the color set for the higher level, you can pass the lk inherited constant in *color*.
+In *color*, pass an RGB color value. For more information about RGB colors, refer to the description of the [OBJECT SET RGB COLORS](object-set-rgb-colors.md) command. If you want the row to inherit the color set for the higher level, you can pass the`lk inherited` constant in *color*.
 
-In the *colorType* parameter, pass the lk background color or lk font color constants to indicate whether you want to apply the color as the background or the font color of the row. If you omit this parameter, the color is applied as the font color. 
+In the *colorType* parameter, pass the `lk background color`  or `lk font color`  constants to indicate whether you want to apply the color as the background or the font color of the row. If you omit this parameter, the color is applied as the font color. 
 
 This command modifies values found in the array of colors that may have been defined for the column or list box. If these arrays are not already defined, the command dynamically creates arrays that you can access using the [LISTBOX Get array](listbox-get-array.md) command. 
 

docs/commands-legacy/web-send-blob.md

@@ -26,50 +26,7 @@ The type of data contained in the BLOB is indicated by *type*. This parameter ca
 
 **Note:** For more information about MIME types, refer to the page: <http://www.iana.org/assignments/media-types>.
 
-Here is a list of the most common MIME types:
-
-| **Extension** | **Mime/Type**            |
-| ------------- | ------------------------ |
-| .htm          | text/html                |
-| .html         | text/html                |
-| .shtml        | text/html                |
-| .shtm         | text/html                |
-| .css          | text/css                 |
-| .pdf          | application/pdf          |
-| .rtf          | application/rtf          |
-| .ps           | application/postscript   |
-| .eps          | application/postscript   |
-| .hqx          | application/mac-binhex40 |
-| .js           | application/javascript   |
-| .json         | application/json         |
-| .txt          | text/plain               |
-| .text         | text/plain               |
-| .gif          | image/gif                |
-| .jpg          | image/jpeg               |
-| .jpeg         | image/jpeg               |
-| .jpe          | image/jpeg               |
-| .jfif         | image/jpeg               |
-| .pic          | image/pict               |
-| .pict         | image/pict               |
-| .tif          | image/tiff               |
-| .tiff         | image/tiff               |
-| .mpeg         | video/mpeg               |
-| .mpg          | video/mpeg               |
-| .mov          | video/quicktime          |
-| .moov         | video/quicktime          |
-| .aif          | audio/aiff               |
-| .aiff         | audio/aiff               |
-| .wav          | audio/wav                |
-| .ram          | audio/x-pn-realaudio     |
-| .sit          | application/x-stuffit    |
-| .bin          | application/x-stuffit    |
-| .xml          | application/xml          |
-| .z            | application/x-zip        |
-| .zip          | application/x-zip        |
-| .gz           | application/x-gzip       |
-| .tar          | application/x-tar        |
-
-**Note:** The list of MIME types supported by the 4D HTTP server is saved in the "MimeTypes.xml" file found in the following folder of the 4D application: *\[Contents\]\\Native components\\HTTPServer.bundle\\Contents\\Resources*. 
+The list of MIME types and their file extensions supported by the 4D HTTP server is saved in the "MimeTypes.xml" file found in the "Resources" folder of the 4D application.
 
 The references to 4D variables and *4DSCRIPT* type tags in the page are always parsed.
 

i18n/es/docusaurus-plugin-content-docs/current/API/DataClassClass.md

@@ -181,7 +181,7 @@ En el parámetro opcional *settings* se puede pasar un objeto que contenga opcio
 
 <!-- REF #DataClassClass.clearRemoteCache().Syntax -->**.clearRemoteCache()**<!-- END REF -->
 
-<!-- REF #DataStoreClass.clearRemoteCache().Params -->
+<!-- REF #DataClassClass.clearRemoteCache().Params -->
 
 | Parámetros | Tipo |     | Descripción                  |
 | ---------- | ---- | :-: | ---------------------------- |