diff --git a/docs/en/1.10.x/api-pages.html b/docs/en/1.10.x/api-pages.html index 5125e906e6..db922600d6 100644 --- a/docs/en/1.10.x/api-pages.html +++ b/docs/en/1.10.x/api-pages.html @@ -142,9 +142,9 @@ MyPage.description = 'My Custom Description';
Example:
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ MyPage.description = 'My Custom Description';<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ MyPage.description = 'My Custom Description';When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js
file. E.g. The URL for a French page of website/pages/en/help.js
would be found at ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. e.g.,
<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/en/1.10.x/api-pages/index.html b/docs/en/1.10.x/api-pages/index.html
index 5125e906e6..db922600d6 100644
--- a/docs/en/1.10.x/api-pages/index.html
+++ b/docs/en/1.10.x/api-pages/index.html
@@ -142,9 +142,9 @@ MyPage.description = 'My Custom Description';
Example:
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ MyPage.description = 'My Custom Description';
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ MyPage.description = 'My Custom Description';
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js
file. E.g. The URL for a French page of website/pages/en/help.js
would be found at ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. e.g.,
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/en/1.10.x/doc-markdown.html b/docs/en/1.10.x/doc-markdown.html
index 92bb3be7f7..4dce858bdd 100644
--- a/docs/en/1.10.x/doc-markdown.html
+++ b/docs/en/1.10.x/doc-markdown.html
@@ -214,13 +214,13 @@ ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('roo
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/en/1.10.x/doc-markdown/index.html b/docs/en/1.10.x/doc-markdown/index.html
index 92bb3be7f7..4dce858bdd 100644
--- a/docs/en/1.10.x/doc-markdown/index.html
+++ b/docs/en/1.10.x/doc-markdown/index.html
@@ -214,13 +214,13 @@ ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('roo
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/en/1.10.x/translation.html b/docs/en/1.10.x/translation.html
index 29aa7ea556..014fd9fc41 100644
--- a/docs/en/1.10.x/translation.html
+++ b/docs/en/1.10.x/translation.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>This header will be translated</translate>
-</h2>
+<h2>
+ <translate>This header will be translated</translate>
+</h2>
...
You can also include an optional description attribute to give more context to a translator about how to translate the string:
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
The <translate>
tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation>
tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate>
tags amongst the pure substrings of that string.
diff --git a/docs/en/1.10.x/translation/index.html b/docs/en/1.10.x/translation/index.html
index 29aa7ea556..014fd9fc41 100644
--- a/docs/en/1.10.x/translation/index.html
+++ b/docs/en/1.10.x/translation/index.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>This header will be translated</translate>
-</h2>
+<h2>
+ <translate>This header will be translated</translate>
+</h2>
...
You can also include an optional description attribute to give more context to a translator about how to translate the string:
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
The <translate>
tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation>
tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate>
tags amongst the pure substrings of that string.
diff --git a/docs/en/1.11.x/api-pages.html b/docs/en/1.11.x/api-pages.html
index 13a5e68116..138c8b0554 100644
--- a/docs/en/1.11.x/api-pages.html
+++ b/docs/en/1.11.x/api-pages.html
@@ -142,9 +142,9 @@ MyPage.description = 'My Custom Description';
Example:
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ MyPage.description = 'My Custom Description';
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ MyPage.description = 'My Custom Description';
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js
file. E.g. The URL for a French page of website/pages/en/help.js
would be found at ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. e.g.,
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/en/1.11.x/api-pages/index.html b/docs/en/1.11.x/api-pages/index.html
index 13a5e68116..138c8b0554 100644
--- a/docs/en/1.11.x/api-pages/index.html
+++ b/docs/en/1.11.x/api-pages/index.html
@@ -142,9 +142,9 @@ MyPage.description = 'My Custom Description';
Example:
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ MyPage.description = 'My Custom Description';
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ MyPage.description = 'My Custom Description';
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js
file. E.g. The URL for a French page of website/pages/en/help.js
would be found at ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. e.g.,
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/en/1.11.x/doc-markdown.html b/docs/en/1.11.x/doc-markdown.html
index 664756fb35..7478a24f30 100644
--- a/docs/en/1.11.x/doc-markdown.html
+++ b/docs/en/1.11.x/doc-markdown.html
@@ -214,13 +214,13 @@ ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('roo
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/en/1.11.x/doc-markdown/index.html b/docs/en/1.11.x/doc-markdown/index.html
index 664756fb35..7478a24f30 100644
--- a/docs/en/1.11.x/doc-markdown/index.html
+++ b/docs/en/1.11.x/doc-markdown/index.html
@@ -214,13 +214,13 @@ ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('roo
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/en/1.11.x/translation.html b/docs/en/1.11.x/translation.html
index 2f72073aaf..d0bf471ef6 100644
--- a/docs/en/1.11.x/translation.html
+++ b/docs/en/1.11.x/translation.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>This header will be translated</translate>
-</h2>
+<h2>
+ <translate>This header will be translated</translate>
+</h2>
...
You can also include an optional description attribute to give more context to a translator about how to translate the string:
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
The <translate>
tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation>
tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate>
tags amongst the pure substrings of that string.
diff --git a/docs/en/1.11.x/translation/index.html b/docs/en/1.11.x/translation/index.html
index 2f72073aaf..d0bf471ef6 100644
--- a/docs/en/1.11.x/translation/index.html
+++ b/docs/en/1.11.x/translation/index.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>This header will be translated</translate>
-</h2>
+<h2>
+ <translate>This header will be translated</translate>
+</h2>
...
You can also include an optional description attribute to give more context to a translator about how to translate the string:
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
The <translate>
tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation>
tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate>
tags amongst the pure substrings of that string.
diff --git a/docs/en/1.12.0/api-pages.html b/docs/en/1.12.0/api-pages.html
index ea76a3347b..46604d27ee 100644
--- a/docs/en/1.12.0/api-pages.html
+++ b/docs/en/1.12.0/api-pages.html
@@ -142,9 +142,9 @@ MyPage.description = 'My Custom Description';
Example:
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ MyPage.description = 'My Custom Description';
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ MyPage.description = 'My Custom Description';
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js
file. E.g. The URL for a French page of website/pages/en/help.js
would be found at ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. e.g.,
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/en/1.12.0/api-pages/index.html b/docs/en/1.12.0/api-pages/index.html
index ea76a3347b..46604d27ee 100644
--- a/docs/en/1.12.0/api-pages/index.html
+++ b/docs/en/1.12.0/api-pages/index.html
@@ -142,9 +142,9 @@ MyPage.description = 'My Custom Description';
Example:
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ MyPage.description = 'My Custom Description';
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ MyPage.description = 'My Custom Description';
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js
file. E.g. The URL for a French page of website/pages/en/help.js
would be found at ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. e.g.,
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/en/1.12.0/doc-markdown.html b/docs/en/1.12.0/doc-markdown.html
index ae4f48b9e9..7782a99998 100644
--- a/docs/en/1.12.0/doc-markdown.html
+++ b/docs/en/1.12.0/doc-markdown.html
@@ -214,13 +214,13 @@ ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('roo
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/en/1.12.0/doc-markdown/index.html b/docs/en/1.12.0/doc-markdown/index.html
index ae4f48b9e9..7782a99998 100644
--- a/docs/en/1.12.0/doc-markdown/index.html
+++ b/docs/en/1.12.0/doc-markdown/index.html
@@ -214,13 +214,13 @@ ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('roo
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/en/1.12.0/translation.html b/docs/en/1.12.0/translation.html
index 76f87c7863..1e867cf36a 100644
--- a/docs/en/1.12.0/translation.html
+++ b/docs/en/1.12.0/translation.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>This header will be translated</translate>
-</h2>
+<h2>
+ <translate>This header will be translated</translate>
+</h2>
...
You can also include an optional description attribute to give more context to a translator about how to translate the string:
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
The <translate>
tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation>
tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate>
tags amongst the pure substrings of that string.
diff --git a/docs/en/1.12.0/translation/index.html b/docs/en/1.12.0/translation/index.html
index 76f87c7863..1e867cf36a 100644
--- a/docs/en/1.12.0/translation/index.html
+++ b/docs/en/1.12.0/translation/index.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>This header will be translated</translate>
-</h2>
+<h2>
+ <translate>This header will be translated</translate>
+</h2>
...
You can also include an optional description attribute to give more context to a translator about how to translate the string:
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
The <translate>
tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation>
tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate>
tags amongst the pure substrings of that string.
diff --git a/docs/en/1.13.0/api-pages.html b/docs/en/1.13.0/api-pages.html
index 6a819662d3..832e991ece 100644
--- a/docs/en/1.13.0/api-pages.html
+++ b/docs/en/1.13.0/api-pages.html
@@ -142,9 +142,9 @@ MyPage.description = 'My Custom Description';
Example:
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ MyPage.description = 'My Custom Description';
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ MyPage.description = 'My Custom Description';
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js
file. E.g. The URL for a French page of website/pages/en/help.js
would be found at ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. e.g.,
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/en/1.13.0/api-pages/index.html b/docs/en/1.13.0/api-pages/index.html
index 6a819662d3..832e991ece 100644
--- a/docs/en/1.13.0/api-pages/index.html
+++ b/docs/en/1.13.0/api-pages/index.html
@@ -142,9 +142,9 @@ MyPage.description = 'My Custom Description';
Example:
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ MyPage.description = 'My Custom Description';
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ MyPage.description = 'My Custom Description';
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js
file. E.g. The URL for a French page of website/pages/en/help.js
would be found at ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. e.g.,
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/en/1.13.0/doc-markdown.html b/docs/en/1.13.0/doc-markdown.html
index 7f96ed49b9..45b9a31223 100644
--- a/docs/en/1.13.0/doc-markdown.html
+++ b/docs/en/1.13.0/doc-markdown.html
@@ -214,13 +214,13 @@ ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('roo
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/en/1.13.0/doc-markdown/index.html b/docs/en/1.13.0/doc-markdown/index.html
index 7f96ed49b9..45b9a31223 100644
--- a/docs/en/1.13.0/doc-markdown/index.html
+++ b/docs/en/1.13.0/doc-markdown/index.html
@@ -214,13 +214,13 @@ ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('roo
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/en/1.13.0/translation.html b/docs/en/1.13.0/translation.html
index 773f2cdf3b..36e8cb6955 100644
--- a/docs/en/1.13.0/translation.html
+++ b/docs/en/1.13.0/translation.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>This header will be translated</translate>
-</h2>
+<h2>
+ <translate>This header will be translated</translate>
+</h2>
...
You can also include an optional description attribute to give more context to a translator about how to translate the string:
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
The <translate>
tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation>
tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate>
tags amongst the pure substrings of that string.
diff --git a/docs/en/1.13.0/translation/index.html b/docs/en/1.13.0/translation/index.html
index 773f2cdf3b..36e8cb6955 100644
--- a/docs/en/1.13.0/translation/index.html
+++ b/docs/en/1.13.0/translation/index.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>This header will be translated</translate>
-</h2>
+<h2>
+ <translate>This header will be translated</translate>
+</h2>
...
You can also include an optional description attribute to give more context to a translator about how to translate the string:
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
The <translate>
tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation>
tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate>
tags amongst the pure substrings of that string.
diff --git a/docs/en/1.9.x/api-pages.html b/docs/en/1.9.x/api-pages.html
index f7be5e0e1b..5c0e42f8e8 100644
--- a/docs/en/1.9.x/api-pages.html
+++ b/docs/en/1.9.x/api-pages.html
@@ -142,9 +142,9 @@ MyPage.description = 'My Custom Description';
Example:
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ MyPage.description = 'My Custom Description';
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ MyPage.description = 'My Custom Description';
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js
file. E.g. The URL for a French page of website/pages/en/help.js
would be found at ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. e.g.,
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/en/1.9.x/api-pages/index.html b/docs/en/1.9.x/api-pages/index.html
index f7be5e0e1b..5c0e42f8e8 100644
--- a/docs/en/1.9.x/api-pages/index.html
+++ b/docs/en/1.9.x/api-pages/index.html
@@ -142,9 +142,9 @@ MyPage.description = 'My Custom Description';
Example:
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ MyPage.description = 'My Custom Description';
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ MyPage.description = 'My Custom Description';
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js
file. E.g. The URL for a French page of website/pages/en/help.js
would be found at ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. e.g.,
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/en/1.9.x/doc-markdown.html b/docs/en/1.9.x/doc-markdown.html
index 53314bbf3c..421c4b9a70 100644
--- a/docs/en/1.9.x/doc-markdown.html
+++ b/docs/en/1.9.x/doc-markdown.html
@@ -214,13 +214,13 @@ ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('roo
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/en/1.9.x/doc-markdown/index.html b/docs/en/1.9.x/doc-markdown/index.html
index 53314bbf3c..421c4b9a70 100644
--- a/docs/en/1.9.x/doc-markdown/index.html
+++ b/docs/en/1.9.x/doc-markdown/index.html
@@ -214,13 +214,13 @@ ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('roo
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/en/1.9.x/translation.html b/docs/en/1.9.x/translation.html
index 48ae7ae5fa..d5293dda73 100644
--- a/docs/en/1.9.x/translation.html
+++ b/docs/en/1.9.x/translation.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>This header will be translated</translate>
-</h2>
+<h2>
+ <translate>This header will be translated</translate>
+</h2>
...
You can also include an optional description attribute to give more context to a translator about how to translate the string:
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
The <translate>
tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation>
tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate>
tags amongst the pure substrings of that string.
diff --git a/docs/en/1.9.x/translation/index.html b/docs/en/1.9.x/translation/index.html
index 48ae7ae5fa..d5293dda73 100644
--- a/docs/en/1.9.x/translation/index.html
+++ b/docs/en/1.9.x/translation/index.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>This header will be translated</translate>
-</h2>
+<h2>
+ <translate>This header will be translated</translate>
+</h2>
...
You can also include an optional description attribute to give more context to a translator about how to translate the string:
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
The <translate>
tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation>
tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate>
tags amongst the pure substrings of that string.
diff --git a/docs/en/api-pages.html b/docs/en/api-pages.html
index 5dd492b3a6..a9f8eb0c24 100644
--- a/docs/en/api-pages.html
+++ b/docs/en/api-pages.html
@@ -142,9 +142,9 @@ MyPage.description = 'My Custom Description';
Example:
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ MyPage.description = 'My Custom Description';
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ MyPage.description = 'My Custom Description';
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js
file. E.g. The URL for a French page of website/pages/en/help.js
would be found at ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. e.g.,
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/en/api-pages/index.html b/docs/en/api-pages/index.html
index 5dd492b3a6..a9f8eb0c24 100644
--- a/docs/en/api-pages/index.html
+++ b/docs/en/api-pages/index.html
@@ -142,9 +142,9 @@ MyPage.description = 'My Custom Description';
Example:
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ MyPage.description = 'My Custom Description';
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ MyPage.description = 'My Custom Description';
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js
file. E.g. The URL for a French page of website/pages/en/help.js
would be found at ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. e.g.,
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/en/doc-markdown.html b/docs/en/doc-markdown.html
index 2328108e4d..01b4220979 100644
--- a/docs/en/doc-markdown.html
+++ b/docs/en/doc-markdown.html
@@ -217,13 +217,13 @@ ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('roo
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/en/doc-markdown/index.html b/docs/en/doc-markdown/index.html
index 2328108e4d..01b4220979 100644
--- a/docs/en/doc-markdown/index.html
+++ b/docs/en/doc-markdown/index.html
@@ -217,13 +217,13 @@ ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('roo
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/en/next/api-pages.html b/docs/en/next/api-pages.html
index a29505d4c2..f5b87967e8 100644
--- a/docs/en/next/api-pages.html
+++ b/docs/en/next/api-pages.html
@@ -142,9 +142,9 @@ MyPage.description = 'My Custom Description';
Example:
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ MyPage.description = 'My Custom Description';
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ MyPage.description = 'My Custom Description';
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js
file. E.g. The URL for a French page of website/pages/en/help.js
would be found at ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. e.g.,
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/en/next/api-pages/index.html b/docs/en/next/api-pages/index.html
index a29505d4c2..f5b87967e8 100644
--- a/docs/en/next/api-pages/index.html
+++ b/docs/en/next/api-pages/index.html
@@ -142,9 +142,9 @@ MyPage.description = 'My Custom Description';
Example:
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ MyPage.description = 'My Custom Description';
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ MyPage.description = 'My Custom Description';
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js
file. E.g. The URL for a French page of website/pages/en/help.js
would be found at ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. e.g.,
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/en/next/doc-markdown.html b/docs/en/next/doc-markdown.html
index 53bc3435e4..76d12f3ecf 100644
--- a/docs/en/next/doc-markdown.html
+++ b/docs/en/next/doc-markdown.html
@@ -217,13 +217,13 @@ ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('roo
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/en/next/doc-markdown/index.html b/docs/en/next/doc-markdown/index.html
index 53bc3435e4..76d12f3ecf 100644
--- a/docs/en/next/doc-markdown/index.html
+++ b/docs/en/next/doc-markdown/index.html
@@ -217,13 +217,13 @@ ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('roo
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/en/next/translation.html b/docs/en/next/translation.html
index a02df5a425..64432bc8e0 100644
--- a/docs/en/next/translation.html
+++ b/docs/en/next/translation.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>This header will be translated</translate>
-</h2>
+<h2>
+ <translate>This header will be translated</translate>
+</h2>
...
You can also include an optional description attribute to give more context to a translator about how to translate the string:
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
The <translate>
tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation>
tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate>
tags amongst the pure substrings of that string.
diff --git a/docs/en/next/translation/index.html b/docs/en/next/translation/index.html
index a02df5a425..64432bc8e0 100644
--- a/docs/en/next/translation/index.html
+++ b/docs/en/next/translation/index.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>This header will be translated</translate>
-</h2>
+<h2>
+ <translate>This header will be translated</translate>
+</h2>
...
You can also include an optional description attribute to give more context to a translator about how to translate the string:
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
The <translate>
tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation>
tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate>
tags amongst the pure substrings of that string.
diff --git a/docs/en/translation.html b/docs/en/translation.html
index e373831c68..55c22150c5 100644
--- a/docs/en/translation.html
+++ b/docs/en/translation.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>This header will be translated</translate>
-</h2>
+<h2>
+ <translate>This header will be translated</translate>
+</h2>
...
You can also include an optional description attribute to give more context to a translator about how to translate the string:
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
The <translate>
tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation>
tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate>
tags amongst the pure substrings of that string.
diff --git a/docs/en/translation/index.html b/docs/en/translation/index.html
index e373831c68..55c22150c5 100644
--- a/docs/en/translation/index.html
+++ b/docs/en/translation/index.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>This header will be translated</translate>
-</h2>
+<h2>
+ <translate>This header will be translated</translate>
+</h2>
...
You can also include an optional description attribute to give more context to a translator about how to translate the string:
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
The <translate>
tag generally works well on pure strings. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation>
tag around that entire string will cause issues because of the markdown linking, etc. Your options are to not translate those strings, or spread a bunch of <translate>
tags amongst the pure substrings of that string.
diff --git a/docs/fr/1.10.x/api-pages.html b/docs/fr/1.10.x/api-pages.html
index 2a5795146a..6e21e1f0f4 100644
--- a/docs/fr/1.10.x/api-pages.html
+++ b/docs/fr/1.10.x/api-pages.html
@@ -142,9 +142,9 @@ module.exports = MyPage;
Exemple :
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ module.exports = MyPage;
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ module.exports = MyPage;
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. Les URLs pour les pages non-anglophones utiliseront leurs tags de langue comme indiqué dans le fichier languages.js
. Par exemple, l'URL d'une page française de website/pages/en/help.js
se trouve à ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. Par exemple :
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/fr/1.10.x/api-pages/index.html b/docs/fr/1.10.x/api-pages/index.html
index 2a5795146a..6e21e1f0f4 100644
--- a/docs/fr/1.10.x/api-pages/index.html
+++ b/docs/fr/1.10.x/api-pages/index.html
@@ -142,9 +142,9 @@ module.exports = MyPage;
Exemple :
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ module.exports = MyPage;
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ module.exports = MyPage;
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. Les URLs pour les pages non-anglophones utiliseront leurs tags de langue comme indiqué dans le fichier languages.js
. Par exemple, l'URL d'une page française de website/pages/en/help.js
se trouve à ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. Par exemple :
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/fr/1.10.x/doc-markdown.html b/docs/fr/1.10.x/doc-markdown.html
index 10178578d6..9fe6d626ed 100644
--- a/docs/fr/1.10.x/doc-markdown.html
+++ b/docs/fr/1.10.x/doc-markdown.html
@@ -214,13 +214,13 @@ usePrism: ['jsx']
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/fr/1.10.x/doc-markdown/index.html b/docs/fr/1.10.x/doc-markdown/index.html
index 10178578d6..9fe6d626ed 100644
--- a/docs/fr/1.10.x/doc-markdown/index.html
+++ b/docs/fr/1.10.x/doc-markdown/index.html
@@ -214,13 +214,13 @@ usePrism: ['jsx']
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/fr/1.10.x/translation.html b/docs/fr/1.10.x/translation.html
index 6e781507f6..7ab0856d84 100644
--- a/docs/fr/1.10.x/translation.html
+++ b/docs/fr/1.10.x/translation.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>Cette entête sera traduite</translate>
-</h2>
+<h2>
+ <translate>Cette entête sera traduite</translate>
+</h2>
...
Vous pouvez également inclure un attribut de description facultatif pour donner plus de contexte à un traducteur sur la façon de traduire la chaîne :
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
La balise <translate>
fonctionne généralement bien sur des chaînes de caractères pures. Si vous avez une chaîne comme "Docusaurus fournit actuellement un support pour aider votre site à utiliser translations", encapsuler la balise <translation>
autour de cette chaîne entière causera des problèmes à cause du lien markdown, etc. Vos possibilités sont de ne pas traduire ces chaînes de caractères, ou de disséminer un tas de balises <translate>
parmi les chaînes de caractères pures de cette chaîne.
diff --git a/docs/fr/1.10.x/translation/index.html b/docs/fr/1.10.x/translation/index.html
index 6e781507f6..7ab0856d84 100644
--- a/docs/fr/1.10.x/translation/index.html
+++ b/docs/fr/1.10.x/translation/index.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>Cette entête sera traduite</translate>
-</h2>
+<h2>
+ <translate>Cette entête sera traduite</translate>
+</h2>
...
Vous pouvez également inclure un attribut de description facultatif pour donner plus de contexte à un traducteur sur la façon de traduire la chaîne :
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
La balise <translate>
fonctionne généralement bien sur des chaînes de caractères pures. Si vous avez une chaîne comme "Docusaurus fournit actuellement un support pour aider votre site à utiliser translations", encapsuler la balise <translation>
autour de cette chaîne entière causera des problèmes à cause du lien markdown, etc. Vos possibilités sont de ne pas traduire ces chaînes de caractères, ou de disséminer un tas de balises <translate>
parmi les chaînes de caractères pures de cette chaîne.
diff --git a/docs/fr/1.11.x/api-pages.html b/docs/fr/1.11.x/api-pages.html
index 97ca953502..0a8dfd2390 100644
--- a/docs/fr/1.11.x/api-pages.html
+++ b/docs/fr/1.11.x/api-pages.html
@@ -142,9 +142,9 @@ module.exports = MyPage;
Exemple :
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ module.exports = MyPage;
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ module.exports = MyPage;
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. Les URLs pour les pages non-anglophones utiliseront leurs tags de langue comme indiqué dans le fichier languages.js
. Par exemple, l'URL d'une page française de website/pages/en/help.js
se trouve à ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. Par exemple :
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/fr/1.11.x/api-pages/index.html b/docs/fr/1.11.x/api-pages/index.html
index 97ca953502..0a8dfd2390 100644
--- a/docs/fr/1.11.x/api-pages/index.html
+++ b/docs/fr/1.11.x/api-pages/index.html
@@ -142,9 +142,9 @@ module.exports = MyPage;
Exemple :
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ module.exports = MyPage;
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ module.exports = MyPage;
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. Les URLs pour les pages non-anglophones utiliseront leurs tags de langue comme indiqué dans le fichier languages.js
. Par exemple, l'URL d'une page française de website/pages/en/help.js
se trouve à ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. Par exemple :
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/fr/1.11.x/doc-markdown.html b/docs/fr/1.11.x/doc-markdown.html
index 2b48d7b0b4..8329e6809b 100644
--- a/docs/fr/1.11.x/doc-markdown.html
+++ b/docs/fr/1.11.x/doc-markdown.html
@@ -214,13 +214,13 @@ usePrism: ['jsx']
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/fr/1.11.x/doc-markdown/index.html b/docs/fr/1.11.x/doc-markdown/index.html
index 2b48d7b0b4..8329e6809b 100644
--- a/docs/fr/1.11.x/doc-markdown/index.html
+++ b/docs/fr/1.11.x/doc-markdown/index.html
@@ -214,13 +214,13 @@ usePrism: ['jsx']
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/fr/1.11.x/translation.html b/docs/fr/1.11.x/translation.html
index 18c3787394..fbde987656 100644
--- a/docs/fr/1.11.x/translation.html
+++ b/docs/fr/1.11.x/translation.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>Cette entête sera traduite</translate>
-</h2>
+<h2>
+ <translate>Cette entête sera traduite</translate>
+</h2>
...
Vous pouvez également inclure un attribut de description facultatif pour donner plus de contexte à un traducteur sur la façon de traduire la chaîne :
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
La balise <translate>
fonctionne généralement bien sur des chaînes de caractères pures. Si vous avez une chaîne comme "Docusaurus fournit actuellement un support pour aider votre site à utiliser translations", encapsuler la balise <translation>
autour de cette chaîne entière causera des problèmes à cause du lien markdown, etc. Vos possibilités sont de ne pas traduire ces chaînes de caractères, ou de disséminer un tas de balises <translate>
parmi les chaînes de caractères pures de cette chaîne.
diff --git a/docs/fr/1.11.x/translation/index.html b/docs/fr/1.11.x/translation/index.html
index 18c3787394..fbde987656 100644
--- a/docs/fr/1.11.x/translation/index.html
+++ b/docs/fr/1.11.x/translation/index.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>Cette entête sera traduite</translate>
-</h2>
+<h2>
+ <translate>Cette entête sera traduite</translate>
+</h2>
...
Vous pouvez également inclure un attribut de description facultatif pour donner plus de contexte à un traducteur sur la façon de traduire la chaîne :
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
La balise <translate>
fonctionne généralement bien sur des chaînes de caractères pures. Si vous avez une chaîne comme "Docusaurus fournit actuellement un support pour aider votre site à utiliser translations", encapsuler la balise <translation>
autour de cette chaîne entière causera des problèmes à cause du lien markdown, etc. Vos possibilités sont de ne pas traduire ces chaînes de caractères, ou de disséminer un tas de balises <translate>
parmi les chaînes de caractères pures de cette chaîne.
diff --git a/docs/fr/1.12.0/api-pages.html b/docs/fr/1.12.0/api-pages.html
index 391ae9f0f7..ee364b9dcf 100644
--- a/docs/fr/1.12.0/api-pages.html
+++ b/docs/fr/1.12.0/api-pages.html
@@ -142,9 +142,9 @@ module.exports = MyPage;
Exemple :
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ module.exports = MyPage;
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ module.exports = MyPage;
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. Les URLs pour les pages non-anglophones utiliseront leurs tags de langue comme indiqué dans le fichier languages.js
. Par exemple, l'URL d'une page française de website/pages/en/help.js
se trouve à ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. Par exemple :
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/fr/1.12.0/api-pages/index.html b/docs/fr/1.12.0/api-pages/index.html
index 391ae9f0f7..ee364b9dcf 100644
--- a/docs/fr/1.12.0/api-pages/index.html
+++ b/docs/fr/1.12.0/api-pages/index.html
@@ -142,9 +142,9 @@ module.exports = MyPage;
Exemple :
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ module.exports = MyPage;
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ module.exports = MyPage;
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. Les URLs pour les pages non-anglophones utiliseront leurs tags de langue comme indiqué dans le fichier languages.js
. Par exemple, l'URL d'une page française de website/pages/en/help.js
se trouve à ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. Par exemple :
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/fr/1.12.0/doc-markdown.html b/docs/fr/1.12.0/doc-markdown.html
index 923272c9c3..ccc8026362 100644
--- a/docs/fr/1.12.0/doc-markdown.html
+++ b/docs/fr/1.12.0/doc-markdown.html
@@ -214,13 +214,13 @@ usePrism: ['jsx']
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/fr/1.12.0/doc-markdown/index.html b/docs/fr/1.12.0/doc-markdown/index.html
index 923272c9c3..ccc8026362 100644
--- a/docs/fr/1.12.0/doc-markdown/index.html
+++ b/docs/fr/1.12.0/doc-markdown/index.html
@@ -214,13 +214,13 @@ usePrism: ['jsx']
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/fr/1.12.0/translation.html b/docs/fr/1.12.0/translation.html
index 1b1a8fa483..41057d59d0 100644
--- a/docs/fr/1.12.0/translation.html
+++ b/docs/fr/1.12.0/translation.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>Cette entête sera traduite</translate>
-</h2>
+<h2>
+ <translate>Cette entête sera traduite</translate>
+</h2>
...
Vous pouvez également inclure un attribut de description facultatif pour donner plus de contexte à un traducteur sur la façon de traduire la chaîne :
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
La balise <translate>
fonctionne généralement bien sur des chaînes de caractères pures. Si vous avez une chaîne comme "Docusaurus fournit actuellement un support pour aider votre site à utiliser translations", encapsuler la balise <translation>
autour de cette chaîne entière causera des problèmes à cause du lien markdown, etc. Vos possibilités sont de ne pas traduire ces chaînes de caractères, ou de disséminer un tas de balises <translate>
parmi les chaînes de caractères pures de cette chaîne.
diff --git a/docs/fr/1.12.0/translation/index.html b/docs/fr/1.12.0/translation/index.html
index 1b1a8fa483..41057d59d0 100644
--- a/docs/fr/1.12.0/translation/index.html
+++ b/docs/fr/1.12.0/translation/index.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>Cette entête sera traduite</translate>
-</h2>
+<h2>
+ <translate>Cette entête sera traduite</translate>
+</h2>
...
Vous pouvez également inclure un attribut de description facultatif pour donner plus de contexte à un traducteur sur la façon de traduire la chaîne :
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
La balise <translate>
fonctionne généralement bien sur des chaînes de caractères pures. Si vous avez une chaîne comme "Docusaurus fournit actuellement un support pour aider votre site à utiliser translations", encapsuler la balise <translation>
autour de cette chaîne entière causera des problèmes à cause du lien markdown, etc. Vos possibilités sont de ne pas traduire ces chaînes de caractères, ou de disséminer un tas de balises <translate>
parmi les chaînes de caractères pures de cette chaîne.
diff --git a/docs/fr/1.13.0/api-pages.html b/docs/fr/1.13.0/api-pages.html
index 8ec6e8195d..10dee31b94 100644
--- a/docs/fr/1.13.0/api-pages.html
+++ b/docs/fr/1.13.0/api-pages.html
@@ -142,9 +142,9 @@ module.exports = MyPage;
Exemple :
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ module.exports = MyPage;
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ module.exports = MyPage;
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. Les URLs pour les pages non-anglophones utiliseront leurs tags de langue comme indiqué dans le fichier languages.js
. Par exemple, l'URL d'une page française de website/pages/en/help.js
se trouve à ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. Par exemple :
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/fr/1.13.0/api-pages/index.html b/docs/fr/1.13.0/api-pages/index.html
index 8ec6e8195d..10dee31b94 100644
--- a/docs/fr/1.13.0/api-pages/index.html
+++ b/docs/fr/1.13.0/api-pages/index.html
@@ -142,9 +142,9 @@ module.exports = MyPage;
Exemple :
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ module.exports = MyPage;
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ module.exports = MyPage;
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. Les URLs pour les pages non-anglophones utiliseront leurs tags de langue comme indiqué dans le fichier languages.js
. Par exemple, l'URL d'une page française de website/pages/en/help.js
se trouve à ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. Par exemple :
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/fr/1.13.0/doc-markdown.html b/docs/fr/1.13.0/doc-markdown.html
index 7539c69d64..4bf8c090c0 100644
--- a/docs/fr/1.13.0/doc-markdown.html
+++ b/docs/fr/1.13.0/doc-markdown.html
@@ -214,13 +214,13 @@ usePrism: ['jsx']
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/fr/1.13.0/doc-markdown/index.html b/docs/fr/1.13.0/doc-markdown/index.html
index 7539c69d64..4bf8c090c0 100644
--- a/docs/fr/1.13.0/doc-markdown/index.html
+++ b/docs/fr/1.13.0/doc-markdown/index.html
@@ -214,13 +214,13 @@ usePrism: ['jsx']
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/fr/1.13.0/translation.html b/docs/fr/1.13.0/translation.html
index 48f211d19e..3253e79ee3 100644
--- a/docs/fr/1.13.0/translation.html
+++ b/docs/fr/1.13.0/translation.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>Cette entête sera traduite</translate>
-</h2>
+<h2>
+ <translate>Cette entête sera traduite</translate>
+</h2>
...
Vous pouvez également inclure un attribut de description facultatif pour donner plus de contexte à un traducteur sur la façon de traduire la chaîne :
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
La balise <translate>
fonctionne généralement bien sur des chaînes de caractères pures. Si vous avez une chaîne comme "Docusaurus fournit actuellement un support pour aider votre site à utiliser translations", encapsuler la balise <translation>
autour de cette chaîne entière causera des problèmes à cause du lien markdown, etc. Vos possibilités sont de ne pas traduire ces chaînes de caractères, ou de disséminer un tas de balises <translate>
parmi les chaînes de caractères pures de cette chaîne.
diff --git a/docs/fr/1.13.0/translation/index.html b/docs/fr/1.13.0/translation/index.html
index 48f211d19e..3253e79ee3 100644
--- a/docs/fr/1.13.0/translation/index.html
+++ b/docs/fr/1.13.0/translation/index.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>Cette entête sera traduite</translate>
-</h2>
+<h2>
+ <translate>Cette entête sera traduite</translate>
+</h2>
...
Vous pouvez également inclure un attribut de description facultatif pour donner plus de contexte à un traducteur sur la façon de traduire la chaîne :
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
La balise <translate>
fonctionne généralement bien sur des chaînes de caractères pures. Si vous avez une chaîne comme "Docusaurus fournit actuellement un support pour aider votre site à utiliser translations", encapsuler la balise <translation>
autour de cette chaîne entière causera des problèmes à cause du lien markdown, etc. Vos possibilités sont de ne pas traduire ces chaînes de caractères, ou de disséminer un tas de balises <translate>
parmi les chaînes de caractères pures de cette chaîne.
diff --git a/docs/fr/1.9.x/api-pages.html b/docs/fr/1.9.x/api-pages.html
index 29d72ae906..33717fa0bd 100644
--- a/docs/fr/1.9.x/api-pages.html
+++ b/docs/fr/1.9.x/api-pages.html
@@ -142,9 +142,9 @@ module.exports = MyPage;
Exemple :
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ module.exports = MyPage;
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ module.exports = MyPage;
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. Les URLs pour les pages non-anglophones utiliseront leurs tags de langue comme indiqué dans le fichier languages.js
. Par exemple, l'URL d'une page française de website/pages/en/help.js
se trouve à ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. Par exemple :
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/fr/1.9.x/api-pages/index.html b/docs/fr/1.9.x/api-pages/index.html
index 29d72ae906..33717fa0bd 100644
--- a/docs/fr/1.9.x/api-pages/index.html
+++ b/docs/fr/1.9.x/api-pages/index.html
@@ -142,9 +142,9 @@ module.exports = MyPage;
Exemple :
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ module.exports = MyPage;
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ module.exports = MyPage;
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. Les URLs pour les pages non-anglophones utiliseront leurs tags de langue comme indiqué dans le fichier languages.js
. Par exemple, l'URL d'une page française de website/pages/en/help.js
se trouve à ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. Par exemple :
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/fr/1.9.x/doc-markdown.html b/docs/fr/1.9.x/doc-markdown.html
index e3ae5d11dd..840b5fb6ec 100644
--- a/docs/fr/1.9.x/doc-markdown.html
+++ b/docs/fr/1.9.x/doc-markdown.html
@@ -214,13 +214,13 @@ usePrism: ['jsx']
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/fr/1.9.x/doc-markdown/index.html b/docs/fr/1.9.x/doc-markdown/index.html
index e3ae5d11dd..840b5fb6ec 100644
--- a/docs/fr/1.9.x/doc-markdown/index.html
+++ b/docs/fr/1.9.x/doc-markdown/index.html
@@ -214,13 +214,13 @@ usePrism: ['jsx']
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/fr/1.9.x/translation.html b/docs/fr/1.9.x/translation.html
index b19c1a6298..206601e548 100644
--- a/docs/fr/1.9.x/translation.html
+++ b/docs/fr/1.9.x/translation.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>Cette entête sera traduite</translate>
-</h2>
+<h2>
+ <translate>Cette entête sera traduite</translate>
+</h2>
...
Vous pouvez également inclure un attribut de description facultatif pour donner plus de contexte à un traducteur sur la façon de traduire la chaîne :
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
La balise <translate>
fonctionne généralement bien sur des chaînes de caractères pures. Si vous avez une chaîne comme "Docusaurus fournit actuellement un support pour aider votre site à utiliser translations", encapsuler la balise <translation>
autour de cette chaîne entière causera des problèmes à cause du lien markdown, etc. Vos possibilités sont de ne pas traduire ces chaînes de caractères, ou de disséminer un tas de balises <translate>
parmi les chaînes de caractères pures de cette chaîne.
diff --git a/docs/fr/1.9.x/translation/index.html b/docs/fr/1.9.x/translation/index.html
index b19c1a6298..206601e548 100644
--- a/docs/fr/1.9.x/translation/index.html
+++ b/docs/fr/1.9.x/translation/index.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>Cette entête sera traduite</translate>
-</h2>
+<h2>
+ <translate>Cette entête sera traduite</translate>
+</h2>
...
Vous pouvez également inclure un attribut de description facultatif pour donner plus de contexte à un traducteur sur la façon de traduire la chaîne :
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
La balise <translate>
fonctionne généralement bien sur des chaînes de caractères pures. Si vous avez une chaîne comme "Docusaurus fournit actuellement un support pour aider votre site à utiliser translations", encapsuler la balise <translation>
autour de cette chaîne entière causera des problèmes à cause du lien markdown, etc. Vos possibilités sont de ne pas traduire ces chaînes de caractères, ou de disséminer un tas de balises <translate>
parmi les chaînes de caractères pures de cette chaîne.
diff --git a/docs/fr/api-pages.html b/docs/fr/api-pages.html
index 018749d979..3005458251 100644
--- a/docs/fr/api-pages.html
+++ b/docs/fr/api-pages.html
@@ -142,9 +142,9 @@ module.exports = MyPage;
Exemple :
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ module.exports = MyPage;
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ module.exports = MyPage;
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. Les URLs pour les pages non-anglophones utiliseront leurs tags de langue comme indiqué dans le fichier languages.js
. Par exemple, l'URL d'une page française de website/pages/en/help.js
se trouve à ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. Par exemple :
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/fr/api-pages/index.html b/docs/fr/api-pages/index.html
index 018749d979..3005458251 100644
--- a/docs/fr/api-pages/index.html
+++ b/docs/fr/api-pages/index.html
@@ -142,9 +142,9 @@ module.exports = MyPage;
Exemple :
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ module.exports = MyPage;
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ module.exports = MyPage;
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. Les URLs pour les pages non-anglophones utiliseront leurs tags de langue comme indiqué dans le fichier languages.js
. Par exemple, l'URL d'une page française de website/pages/en/help.js
se trouve à ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. Par exemple :
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/fr/doc-markdown.html b/docs/fr/doc-markdown.html
index 77c3548b10..7a429f1a22 100644
--- a/docs/fr/doc-markdown.html
+++ b/docs/fr/doc-markdown.html
@@ -232,13 +232,13 @@ ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('roo
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/fr/doc-markdown/index.html b/docs/fr/doc-markdown/index.html
index 77c3548b10..7a429f1a22 100644
--- a/docs/fr/doc-markdown/index.html
+++ b/docs/fr/doc-markdown/index.html
@@ -232,13 +232,13 @@ ReactDOM.render(<h1>Hello, world!</h1>, document.getElementById('roo
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/fr/next/api-pages.html b/docs/fr/next/api-pages.html
index c49d883212..0f049eebbd 100644
--- a/docs/fr/next/api-pages.html
+++ b/docs/fr/next/api-pages.html
@@ -142,9 +142,9 @@ module.exports = MyPage;
Exemple :
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ module.exports = MyPage;
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ module.exports = MyPage;
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. Les URLs pour les pages non-anglophones utiliseront leurs tags de langue comme indiqué dans le fichier languages.js
. Par exemple, l'URL d'une page française de website/pages/en/help.js
se trouve à ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. Par exemple :
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/fr/next/api-pages/index.html b/docs/fr/next/api-pages/index.html
index c49d883212..0f049eebbd 100644
--- a/docs/fr/next/api-pages/index.html
+++ b/docs/fr/next/api-pages/index.html
@@ -142,9 +142,9 @@ module.exports = MyPage;
Exemple :
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ module.exports = MyPage;
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ module.exports = MyPage;
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. Les URLs pour les pages non-anglophones utiliseront leurs tags de langue comme indiqué dans le fichier languages.js
. Par exemple, l'URL d'une page française de website/pages/en/help.js
se trouve à ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. Par exemple :
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/fr/next/doc-markdown.html b/docs/fr/next/doc-markdown.html
index d1361ead33..951fd49720 100644
--- a/docs/fr/next/doc-markdown.html
+++ b/docs/fr/next/doc-markdown.html
@@ -217,13 +217,13 @@ usePrism: ['jsx']
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/fr/next/doc-markdown/index.html b/docs/fr/next/doc-markdown/index.html
index d1361ead33..951fd49720 100644
--- a/docs/fr/next/doc-markdown/index.html
+++ b/docs/fr/next/doc-markdown/index.html
@@ -217,13 +217,13 @@ usePrism: ['jsx']
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/fr/next/translation.html b/docs/fr/next/translation.html
index d6d4867db5..f186d813f3 100644
--- a/docs/fr/next/translation.html
+++ b/docs/fr/next/translation.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>Cette entête sera traduite</translate>
-</h2>
+<h2>
+ <translate>Cette entête sera traduite</translate>
+</h2>
...
Vous pouvez également inclure un attribut de description facultatif pour donner plus de contexte à un traducteur sur la façon de traduire la chaîne :
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
La balise <translate>
fonctionne généralement bien sur des chaînes de caractères pures. Si vous avez une chaîne comme "Docusaurus fournit actuellement un support pour aider votre site à utiliser translations", encapsuler la balise <translation>
autour de cette chaîne entière causera des problèmes à cause du lien markdown, etc. Vos possibilités sont de ne pas traduire ces chaînes de caractères, ou de disséminer un tas de balises <translate>
parmi les chaînes de caractères pures de cette chaîne.
diff --git a/docs/fr/next/translation/index.html b/docs/fr/next/translation/index.html
index d6d4867db5..f186d813f3 100644
--- a/docs/fr/next/translation/index.html
+++ b/docs/fr/next/translation/index.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>Cette entête sera traduite</translate>
-</h2>
+<h2>
+ <translate>Cette entête sera traduite</translate>
+</h2>
...
Vous pouvez également inclure un attribut de description facultatif pour donner plus de contexte à un traducteur sur la façon de traduire la chaîne :
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
La balise <translate>
fonctionne généralement bien sur des chaînes de caractères pures. Si vous avez une chaîne comme "Docusaurus fournit actuellement un support pour aider votre site à utiliser translations", encapsuler la balise <translation>
autour de cette chaîne entière causera des problèmes à cause du lien markdown, etc. Vos possibilités sont de ne pas traduire ces chaînes de caractères, ou de disséminer un tas de balises <translate>
parmi les chaînes de caractères pures de cette chaîne.
diff --git a/docs/fr/translation.html b/docs/fr/translation.html
index f2a001a4c4..b419282ac8 100644
--- a/docs/fr/translation.html
+++ b/docs/fr/translation.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>This header will be translated</translate>
-</h2>
+<h2>
+ <translate>This header will be translated</translate>
+</h2>
...
Vous pouvez également inclure un attribut de description facultatif pour donner plus de contexte à un traducteur sur la façon de traduire la chaîne :
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
La balise <translate>
fonctionne généralement bien sur des chaînes de caractères pures. Si vous avez une chaîne comme "Docusaurus fournit actuellement un support pour aider votre site à utiliser translations", encapsuler la balise <translation>
autour de cette chaîne entière causera des problèmes à cause du lien markdown, etc. Vos possibilités sont de ne pas traduire ces chaînes de caractères, ou de disséminer un tas de balises <translate>
parmi les chaînes de caractères pures de cette chaîne.
diff --git a/docs/fr/translation/index.html b/docs/fr/translation/index.html
index f2a001a4c4..b419282ac8 100644
--- a/docs/fr/translation/index.html
+++ b/docs/fr/translation/index.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>This header will be translated</translate>
-</h2>
+<h2>
+ <translate>This header will be translated</translate>
+</h2>
...
Vous pouvez également inclure un attribut de description facultatif pour donner plus de contexte à un traducteur sur la façon de traduire la chaîne :
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
La balise <translate>
fonctionne généralement bien sur des chaînes de caractères pures. Si vous avez une chaîne comme "Docusaurus fournit actuellement un support pour aider votre site à utiliser translations", encapsuler la balise <translation>
autour de cette chaîne entière causera des problèmes à cause du lien markdown, etc. Vos possibilités sont de ne pas traduire ces chaînes de caractères, ou de disséminer un tas de balises <translate>
parmi les chaînes de caractères pures de cette chaîne.
diff --git a/docs/ko/1.10.x/api-pages.html b/docs/ko/1.10.x/api-pages.html
index 6c2132c010..b482fee34c 100644
--- a/docs/ko/1.10.x/api-pages.html
+++ b/docs/ko/1.10.x/api-pages.html
@@ -142,9 +142,9 @@ MyPage.description = 'My Custom Description';
예제:
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ MyPage.description = 'My Custom Description';
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ MyPage.description = 'My Custom Description';
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js
file. E.g. The URL for a French page of website/pages/en/help.js
would be found at ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. 아래와 같이 적용할 수 있습니다.
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/ko/1.10.x/api-pages/index.html b/docs/ko/1.10.x/api-pages/index.html
index 6c2132c010..b482fee34c 100644
--- a/docs/ko/1.10.x/api-pages/index.html
+++ b/docs/ko/1.10.x/api-pages/index.html
@@ -142,9 +142,9 @@ MyPage.description = 'My Custom Description';
예제:
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ MyPage.description = 'My Custom Description';
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ MyPage.description = 'My Custom Description';
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js
file. E.g. The URL for a French page of website/pages/en/help.js
would be found at ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. 아래와 같이 적용할 수 있습니다.
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/ko/1.10.x/doc-markdown.html b/docs/ko/1.10.x/doc-markdown.html
index 5bbe1b2d53..52b8abfb28 100644
--- a/docs/ko/1.10.x/doc-markdown.html
+++ b/docs/ko/1.10.x/doc-markdown.html
@@ -214,13 +214,13 @@ usePrism: ['jsx']
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/ko/1.10.x/doc-markdown/index.html b/docs/ko/1.10.x/doc-markdown/index.html
index 5bbe1b2d53..52b8abfb28 100644
--- a/docs/ko/1.10.x/doc-markdown/index.html
+++ b/docs/ko/1.10.x/doc-markdown/index.html
@@ -214,13 +214,13 @@ usePrism: ['jsx']
class Example extends React.Component {
render() {
return (
- <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
- <Text>Docusaurus</Text>
- <Button
+ <View style={{flex: 1, alignItems: 'center', justifyContent: 'center'}}>
+ <Text>Docusaurus</Text>
+ <Button
title="Click me"
onPress={() => this.props.navigation.push('Docusaurus')}
- />
- </View>
+ />
+ </View>
);
}
}
diff --git a/docs/ko/1.10.x/translation.html b/docs/ko/1.10.x/translation.html
index 2a00b8af9c..a418ed44ea 100644
--- a/docs/ko/1.10.x/translation.html
+++ b/docs/ko/1.10.x/translation.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>This header will be translated</translate>
-</h2>
+<h2>
+ <translate>This header will be translated</translate>
+</h2>
...
문자열을 어떻게 번역해야 하는지 추가 정보를 제공하기 위해 옵션 항목으로 설명을 추가할 수도 있습니다.
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
<translate>
태그는 일반 문자열인 경우에는 적절하게 동작합니다. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation>
tag around that entire string will cause issues because of the markdown linking, etc. 이런 경우에는 번역하지 않을 문자열을 지정하거나 문자열 사이에 번역할 대상만 <translate>
태그로 지정하는 방법을 사용할 수 있습니다.
diff --git a/docs/ko/1.10.x/translation/index.html b/docs/ko/1.10.x/translation/index.html
index 2a00b8af9c..a418ed44ea 100644
--- a/docs/ko/1.10.x/translation/index.html
+++ b/docs/ko/1.10.x/translation/index.html
@@ -112,16 +112,16 @@ languages.js
...
const translate = require('../../server/translate.js').translate;
...
-<h2>
- <translate>This header will be translated</translate>
-</h2>
+<h2>
+ <translate>This header will be translated</translate>
+</h2>
...
문자열을 어떻게 번역해야 하는지 추가 정보를 제공하기 위해 옵션 항목으로 설명을 추가할 수도 있습니다.
-<p>
- <translate desc="flower, not verb">Rose</translate>
-<p>
-
+<p>
+ <translate desc="flower, not verb">Rose</translate>
+<p>
+
<translate>
태그는 일반 문자열인 경우에는 적절하게 동작합니다. If you have a string like "Docusaurus currently provides support to help your website use translations", wrapping the <translation>
tag around that entire string will cause issues because of the markdown linking, etc. 이런 경우에는 번역하지 않을 문자열을 지정하거나 문자열 사이에 번역할 대상만 <translate>
태그로 지정하는 방법을 사용할 수 있습니다.
diff --git a/docs/ko/1.11.x/api-pages.html b/docs/ko/1.11.x/api-pages.html
index 43d17a8c27..5491cc1bb1 100644
--- a/docs/ko/1.11.x/api-pages.html
+++ b/docs/ko/1.11.x/api-pages.html
@@ -142,9 +142,9 @@ MyPage.description = 'My Custom Description';
예제:
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ MyPage.description = 'My Custom Description';
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ MyPage.description = 'My Custom Description';
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js
file. E.g. The URL for a French page of website/pages/en/help.js
would be found at ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. 아래와 같이 적용할 수 있습니다.
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
- </translate>
-</a>
+ </translate>
+</a>
Add the following require statement as well:
const translate = require('../../server/translate.js').translate;
diff --git a/docs/ko/1.11.x/api-pages/index.html b/docs/ko/1.11.x/api-pages/index.html
index 43d17a8c27..5491cc1bb1 100644
--- a/docs/ko/1.11.x/api-pages/index.html
+++ b/docs/ko/1.11.x/api-pages/index.html
@@ -142,9 +142,9 @@ MyPage.description = 'My Custom Description';
예제:
const MarkdownBlock = CompLibrary.MarkdownBlock;
-<MarkdownBlock>
- [Markdown syntax for a link](http://www.example.com)
-</MarkdownBlock>;
+<MarkdownBlock>
+ [Markdown syntax for a link](http://www.example.com)
+</MarkdownBlock>;
CompLibrary.Container
A React container component using Docusaurus styles. Has optional padding and background color props that you can configure.
@@ -163,9 +163,9 @@ MyPage.description = 'My Custom Description';
<Container
padding={['bottom', 'top']}
background="light"
- className="myCustomClass">
- ...
-</Container>
+ className="myCustomClass">
+ ...
+</Container>
CompLibrary.GridBlock
A React component to organize text and images.
@@ -225,16 +225,16 @@ MyPage.description = 'My Custom Description';
Translating Strings
When translations are enabled, any pages inside website/pages/en
will be translated for all enabled languages. URLs for non-English pages will use their language tags as specified in the languages.js
file. E.g. The URL for a French page of website/pages/en/help.js
would be found at ${baseUrl}fr/help.html
.
When writing pages that you wish to translate, wrap any strings to be translated inside a <translate>
tag. 아래와 같이 적용할 수 있습니다.
-<p>
- <translate>I like translations</translate>
-</p>
+<p>
+ <translate>I like translations</translate>
+</p>
You can also provide an optional description attribute to provide context for translators. e.g,
-<a href="/community">
- <translate desc="Footer link to page referring to community GitHub and Slack">
+<a href="/community">
+ <translate desc="Footer link to page referring to community GitHub and Slack">
Community
-