Comments (5)
@yinsel are you using
docusaurus start
ordocusaurus build
?The dev server init template hardcodes
en
as a language:<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <meta name="generator" content="Docusaurus"> <title><%= htmlWebpackPlugin.options.title %></title> <%= htmlWebpackPlugin.options.headTags %> <%= htmlWebpackPlugin.tags.headTags %> </head> <body> <%= htmlWebpackPlugin.options.preBodyTags %> <div id="__docusaurus"></div> <%= htmlWebpackPlugin.tags.bodyTags %> <%= htmlWebpackPlugin.options.postBodyTags %> </body> </html>
This is later updated by the JS code. It has never been a big deal so far. The prod build should not have langauge
en
.If this annoys you locally, you'd rather ask Edge to never prompt you to translate content of
localhost:3000
Thank you for your reply!
from docusaurus.
I've setup a repro and I get <html lang="zh_CN">
or maybe I'm missing something ?
Same result when testing locally
from docusaurus.
Thanks
Can confirm it works on the repro, so @yinsel please show us a runnable repro where we can see this bug in action. Most likely you did a mistake, so until a repro is provided I'm closing this issue.
Note the lang attribute is supposed to be a BCP47 locale:
https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/lang#language_tag_syntax
zh CN
or zh_CN
are not valid BCP47 codes, only zh
or zh-CN
is.
from docusaurus.
I've setup a repro and I get
<html lang="zh_CN">
or maybe I'm missing something ?Same result when testing locally
You are right, but when using the right mouse button to view the webpage source code, it is<html lang="en">
, and after JS processing, it is correct when pressingF12
to view the elements. I raised this question because I found that even though the page is in Chinese, Edge still prompts me to translate it into Chinese. Perhaps this is also a small bug or a point that needs optimization?
from docusaurus.
@yinsel are you using docusaurus start
or docusaurus build
?
The dev server init template hardcodes en
as a language:
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="generator" content="Docusaurus">
<title><%= htmlWebpackPlugin.options.title %></title>
<%= htmlWebpackPlugin.options.headTags %>
<%= htmlWebpackPlugin.tags.headTags %>
</head>
<body>
<%= htmlWebpackPlugin.options.preBodyTags %>
<div id="__docusaurus"></div>
<%= htmlWebpackPlugin.tags.bodyTags %>
<%= htmlWebpackPlugin.options.postBodyTags %>
</body>
</html>
This is later updated by the JS code.
It has never been a big deal so far.
The prod build should not have langauge en
.
If this annoys you locally, you'd rather ask Edge to never prompt you to translate content of localhost:3000
from docusaurus.
Related Issues (20)
- Invalid hook call when using react class component in MDX HOT 12
- RangeError: Invalid string length when building with a very large number of blogs HOT 7
- Broken link in a-tag not detected HOT 7
- Navbar: Menu Item: Caret / Arrow Is Invisible When Deployed On Azure SWA (using MSAL) HOT 2
- Duplicated whole page when accessing site by your-domain.com/index.html HOT 4
- [Accessibility]: Page looses focus after Search modal gets closed HOT 1
- Please Block the "Bruce's Wiki" at show case since contain the Malicious links HOT 2
- Place screenshots in the themes documentation page in the site HOT 3
- Passing custom props to IdealImage HOT 2
- Spaces are no longer valid in links HOT 4
- Cannot load docs from outside local package root when running as a Yarn workspace HOT 8
- Mermaid diagram shift page when opening a link with anchor HOT 1
- An error occurred when importing a global component. The component cannot be found HOT 1
- Error messages set to `vfile` by Remark plugins are not reported. HOT 1
- Use pure examples in github action deployment examples HOT 1
- When multiple i18n are configured, the plug-in will report an error when using the Link tag. HOT 1
- Can't find component when using NX and NPM Workspaces HOT 2
- Add comparison to vitepress HOT 2
- Module not found: Error: Can't resolve 'react-loadable' in '.../node_modules/@docusaurus/core/lib/client/exports' HOT 1
- BrowserOnly, lazy, and useHistory result in infinite re-rendering HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from docusaurus.