@cfxjs/sirius-next-i18n 0.2.11 → 0.2.13

package/.turbo/turbo-build.log

@@ -1,4 +1,4 @@
 
-> @cfxjs/sirius-next-i18n@0.2.11 build /home/runner/work/sirius-next/sirius-next/packages/i18n
+> @cfxjs/sirius-next-i18n@0.2.13 build /home/runner/work/sirius-next/sirius-next/packages/i18n
 > tsc
 

package/cspace/en/translation.json

@@ -286,7 +286,10 @@
       "tupleArray": "Please enter a valid tuple (JSON array or object that conforms to the parameter order and format) array",
       "notSupport": "{{type}} support will be coming soon"
     },
-    "tupleFormat": "Tuple type：<code>{{type}}</code><br />Parameter name：<code>{{params}}</code><br />Tuple parameter array：<code>{{paramsArray}}</code><br />Tuple parameter object：<code>{{paramsObject}}</code>",
+    "tupleType": "Tuple type：",
+    "tupleParameterName": "Parameter name：",
+    "tupleParameterArray": "Tuple parameter array：",
+    "tupleParameterObject": "Tuple parameter object：",
     "tupleTips": "Remark: You can refer to <code>Tuple parameter array</code> or <code>Tuple parameter object</code> for tuple input.<br />Tuple input format should be a <code>JSON array or object</code> that is legal and conforms to the order and format of the parameters. For example, tuple is declared as <code>{ uint num; string str; }</code>, then the tuple input format should be: <code>[1, \"text\"]</code> or <code>{ \"num\": 1, \"str\": \"text\" }</code>. <br />For nested tuples, the input format should be <code>nested JSON array or object</code> that are legal and conform to the parameter order and format. For example, tuples declared as <code>struct A { string name; uint age; } struct B { uint id; A a; }</code>, the tuple B input format should be: <code>[1, [\"Tom\", 28]]</code> or <code>{ \"id\": 1, \"a\": {\"name\": \"Tom\", \"age\": 28 }}</code>.",
     "query": "Query",
     "write": "Write",

package/cspace/zh_cn/translation.json

@@ -285,7 +285,10 @@
       "tupleArray": "请输入有效的元组（符合参数顺序和格式的 json 数组或对象）数组",
       "notSupport": "{{type}} 即将支持，敬请期待"
     },
-    "tupleFormat": "元组类型：<code>{{type}}</code><br />参数名称：<code>{{params}}</code><br />元组参数数组：<code>{{paramsArray}}</code><br />元组参数对象：<code>{{paramsObject}}</code>",
+    "tupleType": "元组类型：",
+    "tupleParameterName": "参数名称：",
+    "tupleParameterArray": "元组参数数组：",
+    "tupleParameterObject": "元组参数对象：",
     "tupleTips": "提示：可以参考 <code>元组参数数组</code> 或 <code>元组参数对象</code> 进行元组参数输入。<br />元组输入格式应为合法并符合参数顺序和格式的 <code>JSON 数组或对象</code>，例如：元组声明为 <code>{ uint num; string str; }</code>，则元组输入格式应为：<code>[1, \"text\"]</code> 或 <code>{ \"num\": 1, \"str\": \"text\" }</code>。<br />对于嵌套的元组，输入格式应为合法并符合参数顺序和格式的 <code>嵌套的 JSON 数组或对象</code>，例如：元组声明为 <code>struct A { string name; uint age; } struct B { uint id; A a; }</code>，则元组 B 输入格式应为：<code>[1, [\"Tom\", 28]]</code> 或 <code>{ \"id\": 1, \"a\": {\"name\": \"Tom\", \"age\": 28 }}</code>。",
     "query": "读取",
     "write": "写入",

package/dist/cspace/en/translation.json

@@ -286,7 +286,10 @@
             "tupleArray": "Please enter a valid tuple (JSON array or object that conforms to the parameter order and format) array",
             "notSupport": "{{type}} support will be coming soon"
         },
-        "tupleFormat": "Tuple type：<code>{{type}}</code><br />Parameter name：<code>{{params}}</code><br />Tuple parameter array：<code>{{paramsArray}}</code><br />Tuple parameter object：<code>{{paramsObject}}</code>",
+        "tupleType": "Tuple type：",
+        "tupleParameterName": "Parameter name：",
+        "tupleParameterArray": "Tuple parameter array：",
+        "tupleParameterObject": "Tuple parameter object：",
         "tupleTips": "Remark: You can refer to <code>Tuple parameter array</code> or <code>Tuple parameter object</code> for tuple input.<br />Tuple input format should be a <code>JSON array or object</code> that is legal and conforms to the order and format of the parameters. For example, tuple is declared as <code>{ uint num; string str; }</code>, then the tuple input format should be: <code>[1, \"text\"]</code> or <code>{ \"num\": 1, \"str\": \"text\" }</code>. <br />For nested tuples, the input format should be <code>nested JSON array or object</code> that are legal and conform to the parameter order and format. For example, tuples declared as <code>struct A { string name; uint age; } struct B { uint id; A a; }</code>, the tuple B input format should be: <code>[1, [\"Tom\", 28]]</code> or <code>{ \"id\": 1, \"a\": {\"name\": \"Tom\", \"age\": 28 }}</code>.",
         "query": "Query",
         "write": "Write",

package/dist/evm/base/en/translation.json

@@ -276,7 +276,10 @@
             "tupleArray": "Please enter a valid tuple (JSON array or object that conforms to the parameter order and format) array",
             "notSupport": "{{type}} support will be coming soon"
         },
-        "tupleFormat": "Tuple type：<code>{{type}}</code><br />Parameter name：<code>{{params}}</code><br />Tuple parameter array：<code>{{paramsArray}}</code><br />Tuple parameter object：<code>{{paramsObject}}</code>",
+        "tupleType": "Tuple type：",
+        "tupleParameterName": "Parameter name：",
+        "tupleParameterArray": "Tuple parameter array：",
+        "tupleParameterObject": "Tuple parameter object：",
         "tupleTips": "Remark: You can refer to <code>Tuple parameter array</code> or <code>Tuple parameter object</code> for tuple input.<br />Tuple input format should be a <code>JSON array or object</code> that is legal and conforms to the order and format of the parameters. For example, tuple is declared as <code>{ uint num; string str; }</code>, then the tuple input format should be: <code>[1, \"text\"]</code> or <code>{ \"num\": 1, \"str\": \"text\" }</code>. <br />For nested tuples, the input format should be <code>nested JSON array or object</code> that are legal and conform to the parameter order and format. For example, tuples declared as <code>struct A { string name; uint age; } struct B { uint id; A a; }</code>, the tuple B input format should be: <code>[1, [\"Tom\", 28]]</code> or <code>{ \"id\": 1, \"a\": {\"name\": \"Tom\", \"age\": 28 }}</code>.",
         "query": "Query",
         "write": "Write",

package/evm/base/en/translation.json

@@ -276,7 +276,10 @@
       "tupleArray": "Please enter a valid tuple (JSON array or object that conforms to the parameter order and format) array",
       "notSupport": "{{type}} support will be coming soon"
     },
-    "tupleFormat": "Tuple type：<code>{{type}}</code><br />Parameter name：<code>{{params}}</code><br />Tuple parameter array：<code>{{paramsArray}}</code><br />Tuple parameter object：<code>{{paramsObject}}</code>",
+    "tupleType": "Tuple type：",
+    "tupleParameterName": "Parameter name：",
+    "tupleParameterArray": "Tuple parameter array：",
+    "tupleParameterObject": "Tuple parameter object：",
     "tupleTips": "Remark: You can refer to <code>Tuple parameter array</code> or <code>Tuple parameter object</code> for tuple input.<br />Tuple input format should be a <code>JSON array or object</code> that is legal and conforms to the order and format of the parameters. For example, tuple is declared as <code>{ uint num; string str; }</code>, then the tuple input format should be: <code>[1, \"text\"]</code> or <code>{ \"num\": 1, \"str\": \"text\" }</code>. <br />For nested tuples, the input format should be <code>nested JSON array or object</code> that are legal and conform to the parameter order and format. For example, tuples declared as <code>struct A { string name; uint age; } struct B { uint id; A a; }</code>, the tuple B input format should be: <code>[1, [\"Tom\", 28]]</code> or <code>{ \"id\": 1, \"a\": {\"name\": \"Tom\", \"age\": 28 }}</code>.",
     "query": "Query",
     "write": "Write",

package/evm/base/zh_cn/translation.json

@@ -275,7 +275,10 @@
       "tupleArray": "请输入有效的元组（符合参数顺序和格式的 json 数组或对象）数组",
       "notSupport": "{{type}} 即将支持，敬请期待"
     },
-    "tupleFormat": "元组类型：<code>{{type}}</code><br />参数名称：<code>{{params}}</code><br />元组参数数组：<code>{{paramsArray}}</code><br />元组参数对象：<code>{{paramsObject}}</code>",
+    "tupleType": "元组类型：",
+    "tupleParameterName": "参数名称：",
+    "tupleParameterArray": "元组参数数组：",
+    "tupleParameterObject": "元组参数对象：",
     "tupleTips": "提示：可以参考 <code>元组参数数组</code> 或 <code>元组参数对象</code> 进行元组参数输入。<br />元组输入格式应为合法并符合参数顺序和格式的 <code>JSON 数组或对象</code>，例如：元组声明为 <code>{ uint num; string str; }</code>，则元组输入格式应为：<code>[1, \"text\"]</code> 或 <code>{ \"num\": 1, \"str\": \"text\" }</code>。<br />对于嵌套的元组，输入格式应为合法并符合参数顺序和格式的 <code>嵌套的 JSON 数组或对象</code>，例如：元组声明为 <code>struct A { string name; uint age; } struct B { uint id; A a; }</code>，则元组 B 输入格式应为：<code>[1, [\"Tom\", 28]]</code> 或 <code>{ \"id\": 1, \"a\": {\"name\": \"Tom\", \"age\": 28 }}</code>。",
     "query": "读取",
     "write": "写入",
@@ -1466,9 +1469,9 @@
       "aaHash": "AA 交易哈希",
       "bundleHash": "Bundle 交易哈希",
       "signature": "签名",
-      "bundler": "Bundler",
+      "bundler": "打包器",
       "entryPoint": "入口合约",
-      "paymaster": "Paymaster",
+      "paymaster": "代付方",
       "initCode": "初始化代码",
       "transactionFee": "AA 交易费",
       "gasUsed": "燃料限制 | 燃料用量"
@@ -1676,7 +1679,9 @@
       "transactionHash": "交易哈希是一个唯一的66字符的标识符，该标识符在每次交易执行时都会生成。",
       "aaTransactionHash": "账户抽象（AA）交易哈希是在每次执行账户抽象交易时生成的唯一的 66 个字符标识符。",
       "bundleTransactionHash": "该账户抽象交易被打包进的那笔交易的交易哈希。",
+      "bundler": "一种第三方角色，负责在链下处理一个或多个账户抽象交易（User Ops），并通过 Entry Point合约将它们打包成单笔交易提交到链上。",
       "entryPoint": "用于创建该账户抽象交易的入口合约。",
+      "paymaster": "一种第三方角色，代替终端用户赞助（垫付）执行账户抽象交易（User Op）所需的 gas 费用。",
       "initCode": "创建新的智能合约账户时使用的初始化字节码。",
       "executedEpoch": "交易被实际执行的纪元。",
       "proposedEpoch": "交易发送者希望该笔交易被执行的纪元。交易只能在与期望被执行纪元相差不超过 100,000 的纪元中执行。",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cfxjs/sirius-next-i18n",
-  "version": "0.2.11",
+  "version": "0.2.13",
   "files": [
     "*/**"
   ],