You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@echarts.apache.org by sh...@apache.org on 2019/12/02 03:08:57 UTC
[incubator-echarts-doc] branch master updated: Corrected 'discribe'
to 'describe'
This is an automated email from the ASF dual-hosted git repository.
shenyi pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-echarts-doc.git
The following commit(s) were added to refs/heads/master by this push:
new 7628ac8 Corrected 'discribe' to 'describe'
new 49ee969 Merge pull request #79 from sbalajime/master
7628ac8 is described below
commit 7628ac85a30eb1d24ff287c06941e82c6d2e67b8
Author: Balaji S <sb...@protonmail.com>
AuthorDate: Sat Nov 30 13:55:22 2019 +0530
Corrected 'discribe' to 'describe'
---
en/option/component/aria.md | 2 +-
public/documents/en/option.json | 2 +-
public/en/documents/en/option.json | 2 +-
public/en/documents/en/option_description.json | 2 +-
public/zh/documents/en/option.json | 2 +-
public/zh/documents/en/option_description.json | 2 +-
6 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/en/option/component/aria.md b/en/option/component/aria.md
index 7b5e952..7f3d51a 100644
--- a/en/option/component/aria.md
+++ b/en/option/component/aria.md
@@ -54,7 +54,7 @@ Whether to enable ARIA. When enabled, there should be an `aria-label` label.
By default, the description is generated by our algorithm based on charts. If user want to set the description totally, `description` should be set to the whole description.
-This is useful when single data values cannot represent what the chart means. For example, if the chart is a map containing many scatter points. Default description can only show the data, but the users may find it hard to understand what the user mean. In this case, `description` should be set to discribe the meaning of chart.
+This is useful when single data values cannot represent what the chart means. For example, if the chart is a map containing many scatter points. Default description can only show the data, but the users may find it hard to understand what the user mean. In this case, `description` should be set to describe the meaning of chart.
## general(Object)
diff --git a/public/documents/en/option.json b/public/documents/en/option.json
index 322bead..d39dab2 100644
--- a/public/documents/en/option.json
+++ b/public/documents/en/option.json
@@ -1 +1 @@
-{"$schema":"http://echarts.baidu.com/doc/json-schem","option":{"type":"Object","properties":{"title":{"type":["Object"],"description":"<p>Title component, including main title and subtitle.</p>\n<p>In ECharts 2.x, a single instance of ECharts could contains one title component at most. However, in ECharts 3, there could be one or more than one title components. It is more useful when multiple diagrams in one instance all need titles.</p>\n<p><strong>Here are some instances of different a [...]
\ No newline at end of file
+{"$schema":"http://echarts.baidu.com/doc/json-schem","option":{"type":"Object","properties":{"title":{"type":["Object"],"description":"<p>Title component, including main title and subtitle.</p>\n<p>In ECharts 2.x, a single instance of ECharts could contains one title component at most. However, in ECharts 3, there could be one or more than one title components. It is more useful when multiple diagrams in one instance all need titles.</p>\n<p><strong>Here are some instances of different a [...]
\ No newline at end of file
diff --git a/public/en/documents/en/option.json b/public/en/documents/en/option.json
index 322bead..d39dab2 100644
--- a/public/en/documents/en/option.json
+++ b/public/en/documents/en/option.json
@@ -1 +1 @@
-{"$schema":"http://echarts.baidu.com/doc/json-schem","option":{"type":"Object","properties":{"title":{"type":["Object"],"description":"<p>Title component, including main title and subtitle.</p>\n<p>In ECharts 2.x, a single instance of ECharts could contains one title component at most. However, in ECharts 3, there could be one or more than one title components. It is more useful when multiple diagrams in one instance all need titles.</p>\n<p><strong>Here are some instances of different a [...]
\ No newline at end of file
+{"$schema":"http://echarts.baidu.com/doc/json-schem","option":{"type":"Object","properties":{"title":{"type":["Object"],"description":"<p>Title component, including main title and subtitle.</p>\n<p>In ECharts 2.x, a single instance of ECharts could contains one title component at most. However, in ECharts 3, there could be one or more than one title components. It is more useful when multiple diagrams in one instance all need titles.</p>\n<p><strong>Here are some instances of different a [...]
\ No newline at end of file
diff --git a/public/en/documents/en/option_description.json b/public/en/documents/en/option_description.json
index f388411..fb98445 100644
--- a/public/en/documents/en/option_description.json
+++ b/public/en/documents/en/option_description.json
@@ -1 +1 @@
-{"option":{"properties":{"title":{"properties":{"id":{"description":"<p>Component ID, not specified by default. If specified, it can be used to refer the component in option or API.</p>\n"},"show":{"description":"<p>It specifies whether to show the title component.</p>\n"},"text":{"description":"<p>The main title text, supporting for <code>\\n</code> for newlines.</p>\n"},"link":{"description":"<p>The hyper link of main title text.</p>\n"},"target":{"description":"<p>Open the hyper link [...]
\ No newline at end of file
+{"option":{"properties":{"title":{"properties":{"id":{"description":"<p>Component ID, not specified by default. If specified, it can be used to refer the component in option or API.</p>\n"},"show":{"description":"<p>It specifies whether to show the title component.</p>\n"},"text":{"description":"<p>The main title text, supporting for <code>\\n</code> for newlines.</p>\n"},"link":{"description":"<p>The hyper link of main title text.</p>\n"},"target":{"description":"<p>Open the hyper link [...]
\ No newline at end of file
diff --git a/public/zh/documents/en/option.json b/public/zh/documents/en/option.json
index ab55441..4d52872 100644
--- a/public/zh/documents/en/option.json
+++ b/public/zh/documents/en/option.json
@@ -1 +1 @@
-{"$schema":"http://echarts.baidu.com/doc/json-schem","option":{"type":"Object","properties":{"title":{"type":["Object"],"description":"<p>Title component, including main title and subtitle.</p>\n<p>In ECharts 2.x, a single instance of ECharts could contains one title component at most. However, in ECharts 3, there could be one or more than one title components. It is more useful when multiple diagrams in one instance all need titles.</p>\n<p><strong>Here are some instances of different a [...]
\ No newline at end of file
+{"$schema":"http://echarts.baidu.com/doc/json-schem","option":{"type":"Object","properties":{"title":{"type":["Object"],"description":"<p>Title component, including main title and subtitle.</p>\n<p>In ECharts 2.x, a single instance of ECharts could contains one title component at most. However, in ECharts 3, there could be one or more than one title components. It is more useful when multiple diagrams in one instance all need titles.</p>\n<p><strong>Here are some instances of different a [...]
\ No newline at end of file
diff --git a/public/zh/documents/en/option_description.json b/public/zh/documents/en/option_description.json
index f388411..fb98445 100644
--- a/public/zh/documents/en/option_description.json
+++ b/public/zh/documents/en/option_description.json
@@ -1 +1 @@
-{"option":{"properties":{"title":{"properties":{"id":{"description":"<p>Component ID, not specified by default. If specified, it can be used to refer the component in option or API.</p>\n"},"show":{"description":"<p>It specifies whether to show the title component.</p>\n"},"text":{"description":"<p>The main title text, supporting for <code>\\n</code> for newlines.</p>\n"},"link":{"description":"<p>The hyper link of main title text.</p>\n"},"target":{"description":"<p>Open the hyper link [...]
\ No newline at end of file
+{"option":{"properties":{"title":{"properties":{"id":{"description":"<p>Component ID, not specified by default. If specified, it can be used to refer the component in option or API.</p>\n"},"show":{"description":"<p>It specifies whether to show the title component.</p>\n"},"text":{"description":"<p>The main title text, supporting for <code>\\n</code> for newlines.</p>\n"},"link":{"description":"<p>The hyper link of main title text.</p>\n"},"target":{"description":"<p>Open the hyper link [...]
\ No newline at end of file
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@echarts.apache.org
For additional commands, e-mail: commits-help@echarts.apache.org