fix redirection

README.md

@@ -356,3 +356,52 @@ contents of the_category_.json files:
 Translate commit (dry-run) — pour prévisualiser
 Translate commit (apply + commit) — pour appliquer et committer
 4. Coller le SHA du commit quand demandé
+
+5. ## GRAM
+
+| Character | r value |
+|----------|---------|
+| B | a_bool |
+| X | noarg |
+| A | a_text |
+| S | _AnyText |
+| a | _AnyText |
+| R | _ETENDU |
+| l | _LONGENTIER |
+| L | _AnyNum |
+| D | a_date |
+| T | a_temps |
+| o | a_object |
+| U | a_pointe |
+| u | _PtrNum |
+| E | a_expr |
+| e | a_expr |
+| v | a_var |
+| V | a_var |
+| $ | a_var |
+| C | a_champ |
+| y | a_champouvar |
+| Y | a_champouvar |
+| W | a_ficouchamp |
+| F | a_fichier |
+| f | a_fichierstrict |
+| * | a_etoile |
+| # | a_dif |
+| & | a_et |
+| ! | a_ou |
+| = | a_egal |
+| Z | a_restant |
+| j | a_collection |
+| p | a_picture |
+| b | a_blob |
+| > | a_sup / a_supegal / a_supouinf |
+| < | a_inf / a_infegal |
+| + | a_fourch |
+| % | a_contient_keyword |
+| 179 (³) | a_supegal |
+| 178 (²) | a_infegal |
+| 177 (±) | a_fourch |
+| 199 (Ç) | a_supouinf |
+| 164 (¤) | a_contient_keyword |
+| default | (assert) |
+

docs/Develop/async.md

@@ -15,16 +15,18 @@ Synchronous execution is used when:
 - Task execution must follow a strict order.
 - Performance impact is minimal (e.g., quick operations).
 - Running in a single-threaded context where blocking is acceptable.
-- Synchronous execution blocks the UI and is best suited for quick, ordered tasks where blocking is acceptable.
+
+
+Synchronous execution blocks the UI and is best suited for quick, ordered tasks where blocking is acceptable.
 
 #### Asynchronous Execution
 
-Asynchronous execution is **event-driven** and allows tasks other operations to complete. It relies on **callbacks**, **workers**, and **event handlers** to manage execution flow.
+Asynchronous execution is **event-driven** and allows other operations to complete. It relies on **callbacks**, **workers**, and **event handlers** to manage execution flow.
 
 Asynchronous execution is used when:
 - An operation takes a long time (e.g., waiting for a server response).
 - Responsiveness is critical (e.g., UI interactions).
-- Performing background tasks, network communication, or parallel processing.
+- Background tasks, network communication, or parallel processing are performed.
 
 Choosing Between Synchronous and Asynchronous Execution:
 
@@ -110,7 +112,7 @@ Several 4D classes support asynchronous processing:
 - [`WebSocket`](../API/WebSocketClass.md) – Manages WebSocket client connections.
 - [`WebSocketServer`](../API/WebSocketServerClass.md) – Manages WebSocket server connections.
 
-All these classes follow the same rules regarding asynchronous execution. Their constructor accepts an *options* parameter that is used to configure your asynchronous object. It is recommended that the *options* object is a [user class](../Concepts/classes.md) instance which has callback functions. For example, you can create an `onResponse()` function in the class, it will be automatically called asychronously when a *reponse* event is fired.
+All these classes follow the same rules regarding asynchronous execution. Their constructor accepts an *options* parameter that is used to configure your asynchronous object. It is recommended that the *options* object is a [user class](../Concepts/classes.md) instance which has callback functions. For example, you can create an `onResponse()` function in the class, it will be automatically called asynchronously when a *response* event is fired.
 
 We recommend the following sequence:
 

docs/language-legacy/HTTP/http-get.md

@@ -5,17 +5,17 @@ slug: /commands/http-get
 displayed_sidebar: docs
 ---
 
-<!--REF #_command_.HTTP Get.Syntax-->**HTTP Get** ( *url* : Text ; *response* : Text, Blob, Picture, Object {; *headerNames* : Text array ; *headerValues* : Text array}{; *} ) : Integer<!-- END REF-->
+<!--REF #_command_.HTTP Get.Syntax-->**HTTP Get** ( *url* : Text ; *response* : Text, Blob, Picture, Object, Collection {; *headerNames* : Text array ; *headerValues* : Text array}{; *} ) : Integer<!-- END REF-->
 <!--REF #_command_.HTTP Get.Params-->
 <div class="no-index">
 
 | Parameter | Type |  | Description |
 | --- | --- | --- | --- |
 | url | Text | &#8594;  | URL to which to send the request |
-| response | Text, Blob, Picture, Object | &#8592; | Result of request |
+| response | Text, Blob, Picture, Object, Collection | &#8592; | Result of request |
 | headerNames | Text array | &#8596;  | *in:* Header names of the request<br/> *out:* Returned header names |
 | headerValues | Text array | &#8596;  | *in:* Header values of the request<br/> *out:* Returned header values  |
-| * | Operator | &#8594;  | If passed, connection is maintained (keep-alive)If omitted, connection is closed automatically |
+| * | Operator | &#8594;  | If passed, connection is maintained (keep-alive)<br/>If omitted, connection is closed automatically |
 | Function result | Integer | &#8592; | HTTP status code |
 </div>
 <!-- END REF-->
@@ -51,7 +51,15 @@ http://[{user}:[{password}]@]host[:{port}][/{path}][?{queryString}]
 For example, you can pass the following strings:  
 
 ```RAW
-    http://www.myserver.com    http://www.myserver.com/path    http://www.myserver.com/path?name="jones"    https://www.myserver.com/login (*)    http://123.45.67.89:8083    http://john:smith@123.45.67.89:8083    http://[2001:0db8:0000:0000:0000:ff00:0042:8329]    http://[2001:0db8:0000:0000:0000:ff00:0042:8329]:8080/index.html (**)
+http://www.myserver.com    
+http://www.myserver.com/path    
+http://www.myserver.com/path?name="jones"        
+https://www.myserver.com/login (*)    
+http://123.45.67.89:8083     
+http://john:smith@123.45.67.89:8083   
+http://[2001:0db8:0000:0000:0000:ff00:0042:8329]    
+http://[2001:0db8:0000:0000:0000:ff00:0042:8329]:8080/index.html (**)
+
 ```
 
 *(\*)* During HTTPS requests, authority of the certificate is not checked.   

docs/language-legacy/HTTP/http-request.md

@@ -17,7 +17,7 @@ displayed_sidebar: docs
 | response | Text, Blob, Picture, Object, Collection | ← | Result of request |
 | headerNames | Text array | &#8596;  | *in:* Header names of the request<br/>*out:* Returned header names |
 | headerValues | Text array | &#8596;  | *in:* Header values of the request<br/>*out:* Returned header values |
-| * | Operator | &#8594;  | If passed, connection is maintained (keep-alive)If omitted, connection is closed automatically |
+| * | Operator | &#8594;  | If passed, connection is maintained (keep-alive)<br/>If omitted, connection is closed automatically |
 | Function result | Integer | &#8592; | HTTP status code |
 </div>
 <!-- END REF-->
@@ -65,7 +65,15 @@ http://[{user}:[{password}]@]host[:{port}][/{path}][?{queryString}]
 For example, you can pass the following strings:  
 
 ```
-    http://www.myserver.com    http://www.myserver.com/path    http://www.myserver.com/path?name="jones"    https://www.myserver.com/login (*)    http://123.45.67.89:8083    http://john:smith@123.45.67.89:8083    http://[2001:0db8:0000:0000:0000:ff00:0042:8329]    http://[2001:0db8:0000:0000:0000:ff00:0042:8329]:8080/index.html (**)
+http://www.myserver.com    
+http://www.myserver.com/path    
+http://www.myserver.com/path?name="jones"        
+https://www.myserver.com/login (*)    
+http://123.45.67.89:8083     
+http://john:smith@123.45.67.89:8083   
+http://[2001:0db8:0000:0000:0000:ff00:0042:8329]    
+http://[2001:0db8:0000:0000:0000:ff00:0042:8329]:8080/index.html (**)
+
 ```
 
 *(\*)* During HTTPS requests, authority of the certificate is not checked.   

i18n/es/code.json

@@ -858,7 +858,7 @@
     "description": "The text before tool call"
   },
   "theme.SearchModal.askAiScreen.duringToolCallText": {
-    "message": "Searching for ",
+    "message": "Buscar por ",
     "description": "The text during tool call"
   },
   "theme.SearchModal.askAiScreen.afterToolCallText": {
@@ -870,7 +870,7 @@
     "description": "The submit question text for footer"
   },
   "theme.SearchModal.footer.backToSearchText": {
-    "message": "Back to search",
+    "message": "Volver a buscar",
     "description": "The back to search text for footer"
   },
   "REST API": {

i18n/es/docusaurus-plugin-content-docs/current.json

@@ -1292,11 +1292,11 @@
     "description": "The label for the doc item 'Sessions' in sidebar 'docs', linking to the doc Desktop/desktop-sessions"
   },
   "sidebar.docs.category.Exploring Projects": {
-    "message": "Exploring Projects",
+    "message": "Explorar los proyectos",
     "description": "The label for category 'Exploring Projects' in sidebar 'docs'"
   },
   "sidebar.docs.category.Database Structure": {
-    "message": "Database Structure",
+    "message": "Estructura de la base de datos",
     "description": "The label for category 'Database Structure' in sidebar 'docs'"
   },
   "sidebar.docs.category.Methods & Classes": {

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

@@ -3,7 +3,7 @@ id: ClassClass
 title: Class
 ---
 
-Cuando una clase usuario es [definida](Concepts/classes.md#class-definition) en el proyecto, se carga en el entorno del lenguaje 4D. Una clase es un objeto en sí mismo, de la clase "Class", que tiene propiedades y una función.
+Cuando una clase usuario es [definida](../Project/code-overview.md#creating-classes) en el proyecto, se carga en el entorno del lenguaje 4D. Una clase es un objeto en sí mismo, de la clase "Class", que tiene propiedades y una función.
 
 ### Resumen
 

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

@@ -855,7 +855,7 @@ Cuando se crea un objeto `Session`, la propiedad `.storage` está vacía. Esta p
 
 En cliente/servidor, el objeto `.storage` de la sesión de usuario remota **no** es el mismo en el servidor y en el cliente.
 
-When a remote user session and a web session are [shared using an OTP](../Desktop/sessions.md#sharing-a-desktop-session-for-web-accesses), they also share the same `.storage` object on the server, even if the OTP was [created](#createotp) from the session on the client side.
+When a remote user session and a web session are [shared using an OTP](../Desktop/sessions.md#sharing-a-remote-session-for-web-accesses), they also share the same `.storage` object on the server, even if the OTP was [created](#createotp) from the session on the client side.
 
 :::tip
 

i18n/es/docusaurus-plugin-content-docs/current/Admin/data-collect.md

@@ -124,7 +124,7 @@ También se recogen algunos datos a intervalos regulares.
 | totalExecutionTime                                                                                                | Number                                     | Tiempo total de ejecución de la CPU: suma de todos los tipos de peticiones                                                |
 | totalRequests                                                                                                     | Number                                     | Total requests: sum of web, REST, SOAP, SQL, and internal traffic                                                         |
 | webServer                                                                                                         | Object                                     | Objeto que contiene información sobre el servidor web                                                                                     |
-| webServer.bytesIn                                                                                 | Number                                     | Bytes received by the Web server                                                                                                          |
+| webServer.bytesIn                                                                                 | Number                                     | Bytes recibidos por el servidor web                                                                                                       |
 | webServer.bytesOut                                                                                | Number                                     | Bytes sent by the Web server                                                                                                              |
 | webServer.hits                                                                                    | Number                                     | Number of hits on the Web server                                                                                                          |
 | webServer.executionTime                                                                           | Number                                     | Tiempo de ejecución de la CPU para el servidor Web                                                                                        |

i18n/es/docusaurus-plugin-content-docs/current/Concepts/classes.md

@@ -67,7 +67,7 @@ Las clases disponibles son accesibles desde sus class stores. Hay dos class stor
 </div>
 <!-- END REF -->
 
-El comando `cs` <!-- REF #_command_.cs.Summary -->devuelve el almacén de clases de usuario para el proyecto o componente actual<!-- END REF -->. Devuelve todas las clases de usuario [definidas](#class-definition) en el proyecto o componente abierto. Por defecto, sólo las [clases ORDA](ORDA/ordaClasses.md) están disponibles.
+El comando `cs` <!-- REF #_command_.cs.Summary -->devuelve el almacén de clases de usuario para el proyecto o componente actual<!-- END REF -->. Devuelve todas las clases de usuario [definidas](../Project/code-overview.md#creating-classes) en el proyecto o componente abierto. Por defecto, sólo las [clases ORDA](ORDA/ordaClasses.md) están disponibles.
 
 #### Ejemplo
 
@@ -844,7 +844,7 @@ $myList := cs.ItemInventory.me.itemList
 
 :::
 
-## `local` and `server`
+## `local` y `server`
 
 In [client/server architecture](../Desktop/clientServer.md), `local` and `server` keywords allow you to specify where you want the function to be executed: client-side, or server-side. Controlling the execution location is useful for performance reasons or to implement business logic features.
 
@@ -930,7 +930,7 @@ The `server` keyword is useless for [ORDA data model functions](../ORDA/ordaClas
 
 `server` function parameters and result must be [**streamable**](./dt_object.md#streaming-support). For example, [4D.Datastore](../API/DataStoreClass.md), [File handle](../API/FileHandleClass.md), or [WebServer](../API/WebServerClass.md) are non-streamable classes but [4D.File](../API/FileClass.md) is streamable.
 
-This feature is particularly useful in the context of [remote user sessions](../Desktop/sessions.md#remote-user-sessions), allowing you to implement the business logic in a [session singleton](#shared-or-session-singleton-functions) to share it accross all the processes of the session, thus extending the functionalities of the [`Session`](../commands/session) command. In this case, you might want the relevant business logic to be executed **on the server** so that all the session information is gathered on the server.
+This feature is particularly useful in the context of [remote user sessions](../Desktop/sessions.md#remote-user-sessions), allowing you to implement the business logic in a [session singleton](../Concepts/classes.md#session-singleton) to share it accross all the processes of the session, thus extending the functionalities of the [`Session`](../commands/session) command. In this case, you might want the relevant business logic to be executed **on the server** so that all the session information is gathered on the server.
 
 By default, shared or session singleton functions are executed locally. Adding the `server` keyword in the class function definition makes 4D use the singleton instance on the server. Note that this can result of an instantiation of the singleton on the server if no instance exists yet.