`mk euclidean`: calculates the [Euclidean distance](./VectorClass.md#euclideandistance) between vectors. |
+| threshold | Real | 任意(デフォルト: 0.5)。 選択された"metric"に従って、コサイン、ドット、またはユークリッド類似度に基づいたベクトル比較をフィルタリングするために使用されるしきい値。 最適な結果を得るためには、特定の用途に最適な類似度のしきい値をきちんと選択することが強く推奨されます。 |
**comparator** 記号の、一部のみがサポートされます。 これらの比較記号は、結果としきい値を比較するのに使用されるという点に注意してください:
@@ -1241,8 +1241,8 @@ $es:=ds.Movie.query("roles.actor.lastName = :1 AND roles.actor{2}.lastName = :2"
```4d
var $myVector : 4D.Vector
-$myVector := getVector //(例: 4D.AIKit などから)ベクトルを取得するメソッド
-var $comparisonVector := {vector: $myVector; metric: mk euclidean; threshold: 1.2}
+$myVector := getVector //method to get a vector, e.g. from 4D.AIKit
+var $comparisonVector := {vector: $myVector; metric: mk cosine; threshold: 1.2}
var $results := ds.MyClass.query("myVectorField <= :1"; $comparisonVector)
```
@@ -1250,20 +1250,24 @@ var $results := ds.MyClass.query("myVectorField <= :1"; $comparisonVector)
```4d
var $results := ds.MyClass.query("myVectorField > :1 order by myVectorField desc"; $comparisonVector)
- //the first entity is the most similar
+ //$results.first() entity is the most similar
```
:::note
-The default order is ascending, although a descending order is usually the most useful for vector similarity queries. Thus, you will usually have to add the `desc` keyword in your vector similarity query strings.
+You will generally want vector similarity query results to be sorted from "most similar" to "least similar." By default, results returned with an **order by** clause are sorted in ascending order. Depending on the similarity metric used, you may need to adjust the sorting direction to obtain the correct ranking:
+
+- for [**cosine**](./VectorClass.md#cosinesimilarity) and [**dot**](./VectorClass.md#dotsimilarity) similarity, higher values indicate greater similarity. Therefore, you will typically need to include the `desc` keyword in the query string.
+- for [**euclidean distance**](./VectorClass.md#euclideandistance) similarity, lower values indicate greater similarity. In this case, the default ascending order (or explicitly using the `asc` keyword) is appropriate.
:::
-同じベクトルがクエリ文字列内に複数回出現した場合、order by は最初のものの結果に適用されます。例:
+You can only order on a single vector field. 同じベクトルがクエリ文字列内に複数回出現した場合、order by は最初のものの結果に適用されます。例:
```4d
var $results := ds.MyClass.query("myVectorField > :1 and myVectorField > :2 order by myVectorField desc"; /
- {vector : $myVector1 };{vector : $myVector2 }) //myVectorField > :1 is used for the order by
+ {vector : $myVector1 };{vector : $myVector2 })
+ //myVectorField > :1 is used for the order by
```
詳細については[以下の例題](#例題-4-2)を参照してください (例題 4 と 5)。
@@ -1271,6 +1275,7 @@ var $results := ds.MyClass.query("myVectorField > :1 and myVectorField > :2 orde
:::tip 関連したblog 記事
- [4D AI: Searching Entities by Vector Similarity in 4D](https://blog.4d.com/4d-ai-searching-entities-by-vector-similarity-in-4d)
+- [4D AI: Sorting Query Results by Vector Similarity](https://blog.4d.com/4d-ai-sorting-query-results-by-vector-similarity/)
- [Why Your Search Stack Feels Broken — and How Vector Search Fixes It](https://blog.4d.com/why-your-search-stack-feels-broken-and-how-vector-search-fixes-it)
:::
@@ -1637,30 +1642,29 @@ var $client:=cs.AIKit.OpenAI.new("my api key")
var $result:=$client.embeddings.create("my long text to search"; "text-embedding-ada-002")
var $vector:=$result.vector
- // embedding 属性は4D.Vector クラスオブジェクトを格納した4D フィールドに基づいています
- // デフォルトのmetric (コサイン)での検索
-var $employees:=ds.Employee.query("embedding > :1"; {vector : $vector})
- // ユークリッド計量での検索
-var $employees:=ds.Employee.query("embedding > :1"; {vector: $vector; metric: mk euclidean})
- // 明示的にコサイン計量を指定し、カスタムのしきい値を用いた検索
-var $employees:=ds.Employee.query("embedding > :1"; {vector: $vector; metric: mk cosine; threshold: 0.9})
- // フォーミュラを使用した検索
-var $employees:=ds.Employee.query(Formula(This.embedding.cosineSimilarity($vector)>0.9))
+ //embedding attribute is based upon a 4D field storing 4D.Vector class objects
+
+ //search with default metric (cosine)
+var $employees:=ds.Employee.query("embedding > :1 order by embedding desc"; {vector : $vector})
+
+ //search with euclidean metric
+var $employees:=ds.Employee.query("embedding < :1 order by embedding"; {vector: $vector; metric: mk euclidean})
+
+ //search with explicit cosine metric and custom threshold
+var $employees:=ds.Employee.query("embedding > :1 order by embedding desc"; {vector: $vector; metric: mk cosine; threshold: 0.9})
+
+ //search with a formula
+var $employees:=ds.Employee.query(Formula(This.embdedding.cosineSimilarity($vector)>0.9))
```
#### 例題 5
-異なるメトリックでのベクトルを使用したベクトル類似度によるクエリを実行し、コサイン類似度で結果を並べ替えたい場合を考えます:
+Vector-based semantic ordering can be combined with traditional ORDA filters in the same query.
```4d
- // 比較ベクトルを作成
-var $vector1Comparison:={vector: $myvector; metric: mk cosine; threshold: 0.4}
-var $vector2Comparison:={vector: $myvector; metric: mk euclidean; threshold:1}
-
- // embedding 属性は、4D.Vector クラスオブジェクトを格納している4D フィールドに基づいています
-ds.VectorTable.query("embedding>:1 and embedding<:2";$vector1Comparison;$vector2Comparison)\
- .orderByFormula(Formula(This.embedding.cosineSimilarity($vector1Comparison)))
+var $comparisonVector := {vector: $myVector; metric: mk cosine; threshold: 0.4}
+var $results := ds.MyTable.query("myVectorField <= :1 AND salary>100000 order by myVectorField, salary desc"; $comparisonVector)
```
#### 参照
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/Notes/updates.md b/i18n/ja/docusaurus-plugin-content-docs/current/Notes/updates.md
index b945f1f60e7a6a..9cf663b1de6f06 100644
--- a/i18n/ja/docusaurus-plugin-content-docs/current/Notes/updates.md
+++ b/i18n/ja/docusaurus-plugin-content-docs/current/Notes/updates.md
@@ -9,7 +9,8 @@ Read [**What’s new in 4D 21 R4**](https://blog.4d.com/whats-new-in-4d-21-r4/),
#### ハイライト
-- New [`defer`](../commands/defer) command to declare some code to be always executed at method or function exit.
+- Multi-level list style sheets are now [supported in 4D Write Pro Interface](../WritePro/writeprointerface.md#multi-level-style-sheets), allowing users to create and manage structured multi-level lists directly from the toolbar and sidebar.
+- New [`defer`](../commands/defer) command to declare some code to be always executed at method or function exit; new [`Deferred formulas`](../commands/deferred-formulas) command to get the list of deferred formulas.
## 4D 21 R3
@@ -18,7 +19,7 @@ Read [**What’s new in 4D 21 R4**](https://blog.4d.com/whats-new-in-4d-21-r4/),
#### ハイライト
- [`JSON Validate`](../commands/json-validate) コマンドは、JSON スキーマドラフト 2020-12 をサポートするようになりました。
-- 4D Write Pro は[階層リストスタイルシート](../WritePro/user-legacy/stylesheets.md#hierarchical-list-style-sheets) サポートするようになり、これにより自動ナンバリングつきの、構造化された[マルチレベルのリスト](../WritePro/user-legacy/using-a-4d-write-pro-area.md#multi-level-lists) の作成と管理が可能になりました。
+- 4D Write Pro now supports [multi-level list style sheets](../WritePro/user-legacy/stylesheets.md#multi-level-list-style-sheets), enabling the creation and management of structured [multi-level lists](../WritePro/user-legacy/using-a-4d-write-pro-area.md#multi-level-lists) with automatic numbering.
- [`HTTPRequest`](../API/HTTPRequestClass.md#4dhttprequestnew) および [`HTTPAgent`](../API/HTTPAgentClass.md#4dhttpagentnew) クラスにおいて、ローカル証明書フォルダの代わりにmacOS キーチェーンからのカスタムの証明書を使用できるようになりました。
- テキストソースから4D メソッドを作成し実行するための[`4D.Method` クラス](../API/MethodClass.md)。 [`METHOD Get path`](../commands/method-get-path) および [`METHOD RESOLVE PATH`](../commands/method-resolve-path) コマンドは新しい`path volatile method` 定数 (128) をサポートするようになりました。
- IMAP transporter は、[4D.IMAPNotifier](../API/IMAPNotifierClass.md) クラスの、[notifier オブジェクト](../API/IMAPTransporterClass.md#notifier) を通して、IDLE プロトコルを使用したメールボックスイベント通知イベントをサポートするようになりました。またこのクラスは [IMAP New transporter](../commands/imap-new-transporter) の `listener` プロパティを通して設定することができます。
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user/user-new.md b/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user/user-new.md
index 4f4be24c89075f..9c82afff8390cb 100644
--- a/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user/user-new.md
+++ b/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/user/user-new.md
@@ -10,7 +10,7 @@ to import
## リスト
-4D Write Pro supports flat lists (single-level) and hierarchical lists (multi-level).
+4D Write Pro supports flat lists (single-level) and multi-level lists.
### Single-level lists
@@ -39,7 +39,7 @@ When the list is created using [the WP SET ATTRIBUTE command](../commands-legacy
### Multi-level lists
-Multi-level lists are based on [hierarchical list style sheets](../user-legacy/stylesheets.md#hierarchical-list-style-sheets). Multi-level lists contain a root-level style sheet and one or more sub-level style sheet(s). Each level is attached to a hierarchical list style sheet and represents a depth in the list (level 1, level 2, level 3, etc.).
+Multi-level lists are based on [multi-level list style sheets](../user-legacy/stylesheets.md#multi-level-list-style-sheets). Multi-level lists contain a root-level style sheet and one or more sub-level style sheet(s). Each level is attached to a multi-level list style sheet and represents a depth in the list (level 1, level 2, level 3, etc.).
When a new sub-level is created, the level numbering restarts at 1. When you add or remove an element in your multi-level list, the numbers are automatically adjusted.
@@ -55,30 +55,30 @@ Multi-level lists can be managed using:
:::tip 関連したblog 記事
-[4D Write Pro – Creating Multi-level Bullet or Numbered Lists Using Hierarchical list Style Sheets](https://blog.4d.com/4d-write-pro-creating-multi-level-bullet-or-numbered-lists-using-hierarchical-paragraph-style-sheets)
+[4D Write Pro – Creating Multi-level Bullet or Numbered Lists Using Multi-level list Style Sheets](https://blog.4d.com/4d-write-pro-creating-multi-level-bullet-or-numbered-lists-using-multi-level-paragraph-style-sheets)
:::
-
+
-## Hierarchical list style sheets
+## Multi-level list style sheets
-Hierarchical list style sheets are used to create [multi-level lists](../user-legacy/using-a-4d-write-pro-area.md#multi-level-lists).
+Multi-level list style sheets are used to create [multi-level lists](../user-legacy/using-a-4d-write-pro-area.md#multi-level-lists).
-To create a hierarchical list style sheet, use [WP New style sheet](../commands/wp-new-style-sheet.md) and pass in *listLevelCount* the desired number of levels. You then define a hierarchy of related paragraph style sheets: one **root-level** style sheet and one or more **sub-level** style sheets linked to it. Each level represents a depth in the list (level 1, level 2, level 3, etc.) and is automatically named "root-level name + lvl + index", for example "Mylist lvl 2".
+To create a multi-level list style sheet, use [WP New style sheet](../commands/wp-new-style-sheet.md) and pass in *listLevelCount* the desired number of levels. You then define a hierarchy of related paragraph style sheets: one **root-level** style sheet and one or more **sub-level** style sheets linked to it. Each level represents a depth in the list (level 1, level 2, level 3, etc.) and is automatically named "root-level name + lvl + index", for example "Mylist lvl 2".
-To customize hierarchical list styles, the paragraph style sheet object can be customized using [style sheet attributes](../commands-legacy/4d-write-pro-attributes.md#style-sheets).
+To customize multi-level list styles, the paragraph style sheet object can be customized using [style sheet attributes](../commands-legacy/4d-write-pro-attributes.md#style-sheets).
-Hierarchical list style sheets are fully supported by the following commands: [`WP Get style sheet`](../commands/wp-get-style-sheet.md), [`WP SET ATTRIBUTES`](../commands/wp-set-attributes.md), [`WP DELETE STYLE SHEET`](../commands/wp-delete-style-sheet.md).
+Multi-level list style sheets are fully supported by the following commands: [`WP Get style sheet`](../commands/wp-get-style-sheet.md), [`WP SET ATTRIBUTES`](../commands/wp-set-attributes.md), [`WP DELETE STYLE SHEET`](../commands/wp-delete-style-sheet.md).
### 例題
-The following example creates a three-level hierarchical list style sheet and applies it to paragraphs.
+The following example creates a three-level multi-level list style sheet and applies it to paragraphs.
```4d
-// Create 3 hierarchical list style sheets
+// Create 3 multi-level list style sheets
WP New style sheet(wpArea; wk type paragraph; "MyList"; 3)
// Retrieve each level
@@ -92,7 +92,7 @@ WP SET ATTRIBUTES($level1; {listStyleType: wk upper latin; fontBold: wk true})
WP SET ATTRIBUTES($level2; {listConcatStringFormat: True})
WP SET ATTRIBUTES($level3; {listStringFormatLtr: "(#)"})
-// Apply hierarchical style sheets to paragraphs
+// Apply multi-level style sheets to paragraphs
var $paragraphs : Collection
$paragraphs:=WP Get elements(wpArea; wk type paragraph)
@@ -103,7 +103,7 @@ WP SET ATTRIBUTES($paragraphs[2]; wk style sheet; $level3)
result:
-
+
To delete the first sub-leve:
@@ -113,11 +113,11 @@ WP DELETE STYLE SHEET(wpArea; "MyList"; 2)
result:
-
+
### Predefined attribute values
-When created, hierarchical list style sheets use predefined values:
+When created, multi-level list style sheets use predefined values:
- `wk margin left` = 0.75 cm \* (number of previous levels) or 0.25 inches \* (number of previous levels), depending on current layout unit
- `wk list type` = `wk decimal`
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/writeprointerface.md b/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/writeprointerface.md
index 1064babdefb8e9..b5b567f7753c9e 100644
--- a/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/writeprointerface.md
+++ b/i18n/ja/docusaurus-plugin-content-docs/current/WritePro/writeprointerface.md
@@ -1,8 +1,8 @@
----
+d---
id: writeprointerface
-title: 4D WritePro インターフェース
+title: 4D Write Pro Interface
slug: /WritePro/write-pro-interface
----
+---------------------------------------------------
4D WritePro インターフェースは、エンドユーザーが 4D Write Proドキュメントを簡単にカスタマイズできるパレットを提供します。
@@ -414,3 +414,154 @@ AI に質問を送信するためには、送信ボタンをクリックしま
消去ボタンを使用すると全てのやりとりを消去しウィンドウ全体をリセットすることができます。 これはAI ダイアログボックスを閉じて再度開くのと同じです。
+## Multi-level list style sheets
+
+4D Write Pro Interface allows users to create and manage [multi-level lists](./user-legacy/using-a-4d-write-pro-area.md#multi-level-lists) directly from both the toolbar and widget sidebar.
+
+**Toolbar:**
+
+
+
+**Sidebar:**
+
+
+
+To manage multi-level list style sheets, click the  multi-level list button.
+
+When the multi-level list mode is enabled, the Style Sheets panel displays the [multi-level list style sheets](./user-legacy/stylesheets.md#multi-level-list-style-sheets) defined in the document as well as [predefined templates](#predefined-templates).
+
+
+
+### Managing multi-level style sheets
+
+The Style Sheets panel allows you in general to:
+
+-  Create a new style sheet.
+-  Delete a style sheet.
+-  Update a style sheet.
+
+Once a multi-level list style sheet is selected, the panel provides also tools to manage the hierarchy and numbering of the list:
+
+-  Increase the list level of selected paragraphs.
+-  Decrease the list level of selected paragraphs.
+-  Append a level to the list and create a new sub-level.
+-  Modify numbering formats.
+-  Concatenate numbering markers between levels.
+
+### Creating a style sheet
+
+To create a multi-level list style sheet you can either:
+
+- Select and apply one of the predefined templates to the paragraph(s), the selected template and all it sub-levels are then displayed on the top part of the sytle sheets panel. You can customize its levels and formatting (such as numbering styles, colors, fonts, or hierarchy), and then create a new style sheet based on the resulting selection.
+
+- Duplicate one of the existing style sheets via the Duplicate option in the  bottom menu.
+
+- Click the  button and then "New style sheet based on selection" after having selected paragraph(s) to use for the style sheet according to the following:
+ - If the selected paragraph(s) use(s) a list marker, a new multi-level list style sheet made of one level is created based on the current formatting.
+ - If the selected paragraph(s) already use(s) a root-level or a sub-level of a multi-level list style sheet, the complete hierarchy is duplicated.
+
+:::note
+
+For detailed information about creating and configuring multi-level list style sheets by programming, see [Multi-level list style sheets](./user-legacy/stylesheets.md#multi-level-list-style-sheets).
+
+:::
+
+### Applying a multi-level list
+
+You can apply either a multi-level list style sheet defined in the document or one of the predefined templates to the selected paragraphs using the Style Sheets panel:
+
+
+
+### Predefined templates
+
+The interface provides the following predefined multi-level list templates:
+
+**Technical Blueprint**
+
+Level 1: 1
+Level 2: 1.1
+Level 3: 1.1.1
+Level 4: 1.1.1.1
+Level 5: 1.1.1.1.1
+
+**Legal & Governance**
+
+Level 1: I.
+Level 2: A.
+Level 3: 1.
+Level 4: a)
+Level 5: (1)
+Level 6: (a)
+Level 7: (i)
+
+**Educational Material**
+
+Level 1: I.
+Level 2: 1.
+Level 3: 1.1.
+Level 4: a.
+Level 5: ●
+
+**Meeting Minutes**
+
+Level 1: 1.
+Level 2: ●
+
+**Visual Hierarchy**
+
+Level 1: ♣ (Club)
+Level 2: ♦ (Diamond)
+Level 3: ■ (Square)
+Level 4: □ (Hollow Square)
+Level 5: ● (Disc)
+Level 6: ○ (Circle)
+Level 7: – (Dash)
+
+### Customizing predefined templates
+
+You can customize the available templates to provide users with predefined multi-level lists that match the needs of your application.
+
+The predefined multi-level list templates are defined in a JSON file named `multiLevelStyles.json`. This file is located in the 4D Write Pro Interface component Resources folder.
+
+You can customize the available templates by adding your own `multiLevelStyles.json` file in either:
+
+- the project's local Resources folder directly,
+- a `4D WritePro Interface` folder located within the project Resources folder.
+
+If a `multiLevelStyles.json` file is present in both locations, the file located in the `4D WritePro Interface` folder takes precedence.
+
+Each template definition includes:
+
+- a template name,
+- one or more list levels,
+- the 4D Write Pro attributes applied to each level. Any 4D Write Pro attribute can be used in a template definition.
+
+You can use either the attribute names or the corresponding 4D Write Pro constants as JSON keys and values.
+For example, the following definitions are equivalent:
+
+- `"listStyleType": "wk upper roman"`
+- `"wk list style type": "wk upper roman"`
+
+#### 例題
+
+Example of a customized JSON file:
+
+```json
+{
+ "predefinedMultiLevelLists": [
+ {
+ "name": "Technical Blue Print Updated",
+ "levels": [
+ { "listStyleType": "wk decimal" },
+ { "listStyleType": "wk decimal", "listConcatStringFormat": true }
+ ]
+ }
+ ]
+}
+```
+
+### 参照
+
+- [Related blog post: Multi-Level Style Sheets in 4D Write Pro: Now With a Dedicated UI](https://blog.4d.com/multi-level-style-sheets-in-4d-write-pro-now-with-a-dedicated-ui)
+- [multi-level list style sheets](./user-legacy/stylesheets.md#multi-level-list-style-sheets)
+- [multi-level lists](.user-legacy/using-a-4d-write-pro-area.md#multi-level-lists)
\ No newline at end of file
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button.png
new file mode 100644
index 00000000000000..5f8e7ee323f616
Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button.png differ
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button1.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button1.png
new file mode 100644
index 00000000000000..07da3e87098960
Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button1.png differ
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button2.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button2.png
new file mode 100644
index 00000000000000..088e4c64ed531e
Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button2.png differ
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button3.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button3.png
new file mode 100644
index 00000000000000..ddda09768ac90f
Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button3.png differ
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button4.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button4.png
new file mode 100644
index 00000000000000..aadcadc4745659
Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button4.png differ
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button5.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button5.png
new file mode 100644
index 00000000000000..7de845916f4a1f
Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button5.png differ
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button6.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button6.png
new file mode 100644
index 00000000000000..636cb5780823cd
Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button6.png differ
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button8.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button8.png
new file mode 100644
index 00000000000000..0d5031837e8773
Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-button8.png differ
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-panel.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-panel.png
new file mode 100644
index 00000000000000..652d71520d5fe7
Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-panel.png differ
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-panel2.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-panel2.png
new file mode 100644
index 00000000000000..6e3c56f16b0d7a
Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-panel2.png differ
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-stylesheets1.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-stylesheets1.png
new file mode 100644
index 00000000000000..10c1d6e47429a9
Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-stylesheets1.png differ
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-stylesheets2.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-stylesheets2.png
new file mode 100644
index 00000000000000..a0d750f5bd4f62
Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list-stylesheets2.png differ
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list7.png b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list7.png
new file mode 100644
index 00000000000000..646a3d751ced01
Binary files /dev/null and b/i18n/ja/docusaurus-plugin-content-docs/current/assets/en/WritePro/wp-multi-level-list7.png differ
diff --git a/i18n/ja/docusaurus-plugin-content-docs/version-20/API/Directory.md b/i18n/ja/docusaurus-plugin-content-docs/version-20/API/Directory.md
index eea6ebadfc7b5a..b07068bb3e2f90 100644
--- a/i18n/ja/docusaurus-plugin-content-docs/version-20/API/Directory.md
+++ b/i18n/ja/docusaurus-plugin-content-docs/version-20/API/Directory.md
@@ -401,12 +401,12 @@ Windows 上においては、`.isPackage` は常に **false** を返します。
-|Parameter|Type||Description|
+|引数|型||説明|
|---------|--- |:---:|------|
-|destinationFolder |4D.Folder |->|Destination folder|
-|newName|Text|->|Name for the copy|
-|overwrite|Integer|->|`fk overwrite` to replace existing elements|
-|Result|4D.Folder|<-|Copied file or folder|
+|destinationFolder |4D.Folder |->|コピー先フォルダ|
+|newName|Text|->|コピーの新しい名前|
+|overwrite|Integer|->|既存の要素を上書きするためには `fk overwrite`|
+|戻り値|4D.Folder|<-|Copied file or folder|
@@ -458,10 +458,10 @@ $copiedImages:=$userImages.copyTo(Folder(fk database folder);fk overwrite)
-|Parameter|Type||Description|
+|引数|型||説明|
|---|----|---|---|
-|path|Text|->|Relative POSIX file pathname|
-|Result|4D.File|<-|`File` object (null if invalid path)|
+|path|Text|->|相対 POSIX ファイルパス名|
+|戻り値|4D.File|<-|`File` object (null if invalid path)|
@@ -502,10 +502,10 @@ $myPDF:=Folder(fk documents folder).file("Pictures/info.pdf")
-|Parameter|Type||Description|
+|引数|型||説明|
|---|----|---|---|
-|options|Integer|->|File list options|
-|Result|Collection|<-|Collection of children file objects|
+|options|Integer|->|ファイルリスト用のオプション|
+|戻り値|Collection|<-|Collection of children file objects|
@@ -567,10 +567,10 @@ $myPDF:=Folder(fk documents folder).file("Pictures/info.pdf")
-|Parameter|Type||Description|
+|引数|型||説明|
|---|----|---|---|
-|path|Text|->|Relative POSIX file pathname|
-|Result|4D.Folder|<-|Created folder object (null if invalid *path*)|
+|path|Text|->|相対 POSIX ファイルパス名|
+|戻り値|4D.Folder|<-|Created folder object (null if invalid *path*)|
@@ -611,10 +611,10 @@ $myPDF:=Folder(fk documents folder).file("Pictures/info.pdf")
-|Parameter|Type||Description|
+|引数|型||説明|
|---|----|---|---|
-|options|Integer|->|Folder list options|
-|Result|Collection|<-|Collection of children folder objects|
+|options|Integer|->|フォルダリスト用のオプション|
+|戻り値|Collection|<-|Collection of children folder objects|
@@ -662,10 +662,10 @@ $myPDF:=Folder(fk documents folder).file("Pictures/info.pdf")
-|Parameter|Type||Description|
+|引数|型||説明|
|---|----|---|---|
-|size|Integer|->|Side length for the returned picture (pixels)|
-|Result|Picture|<-|Icon|
+|size|Integer|->|返されるピクチャーの一辺の長さ(ピクセル単位)|
+|戻り値|Picture|<-|Icon|
diff --git a/i18n/ja/docusaurus-plugin-content-docs/version-20/API/Document.md b/i18n/ja/docusaurus-plugin-content-docs/version-20/API/Document.md
index 4a9bb1f3283150..7b78e2f7df711c 100644
--- a/i18n/ja/docusaurus-plugin-content-docs/version-20/API/Document.md
+++ b/i18n/ja/docusaurus-plugin-content-docs/version-20/API/Document.md
@@ -397,12 +397,12 @@ title: Document クラス
-|Parameter|Type||Description|
+|引数|型||説明|
|---------|--- |:---:|------|
-|destinationFolder | 4D.Folder |->|Destination folder|
-|newName|Text|->|Name for the copy|
-|overwrite|Integer|->|`fk overwrite` to replace existing elements|
-|Result|4D.File|<-|Copied file|
+|destinationFolder | 4D.Folder |->|コピー先フォルダ|
+|newName|Text|->|コピーの新しい名前|
+|overwrite|Integer|->|既存の要素を上書きするためには `fk overwrite`|
+|戻り値|4D.File|<-|Copied file|
@@ -497,10 +497,10 @@ $copy:=$source.copyTo(Folder("/PACKAGE");fk overwrite)
-|Parameter|Type||Description|
+|引数|型||説明|
|---|----|---|---|
-|size|Integer|->|Side length for the returned picture (pixels)|
-|Result|Picture|<-|Icon|
+|size|Integer|->|返されるピクチャーの一辺の長さ(ピクセル単位)|
+|戻り値|Picture|<-|Icon|
diff --git a/i18n/ja/docusaurus-plugin-content-docs/version-21-R3/API/DataClassClass.md b/i18n/ja/docusaurus-plugin-content-docs/version-21-R3/API/DataClassClass.md
index 78284f4af38967..e2ab97c1a83c3d 100644
--- a/i18n/ja/docusaurus-plugin-content-docs/version-21-R3/API/DataClassClass.md
+++ b/i18n/ja/docusaurus-plugin-content-docs/version-21-R3/API/DataClassClass.md
@@ -1222,11 +1222,11 @@ $es:=ds.Movie.query("roles.actor.lastName = :1 AND roles.actor{2}.lastName = :2"
この場合、*value* 引数は、以下のプロパティを格納した**比較ベクトルオブジェクト** である必要があります:
-| プロパティ | 型 | 説明 |
-| --------- | -------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| vector | [4D.Vector](../API/VectorClass.md) | 必須設定です。 比較するベクトル |
-| metric | Text | 任意。 クエリに使用する[ベクトル計算](../API/VectorClass.md#ことなるベクトル計算を理解する)。 以下の(テキスト)定数のいずれか一つを使用できます: