Comments (15)
http://cn.eslint.org/ is available now
from archive-website.
If we are talking specifically about Chinese translation, then as far as I understand, offer implied maintaining a separate repository and a completely separate site. I don't think it would be great idea to merge translations into this repository and use our existing site for it, since we would need to do a release every time translations are updated.
from archive-website.
Yes, that's what the offer was, I'm looking at additional options. I want to make sure we are considering all possibilities before diving in.
from archive-website.
Well, I think I definitely wouldn't want to keep rule documentation translations in eslint main repository, since it would require release for publishing every time and would in general create a bunch of commits unrelated to the core project.
Keeping it in this repository vs. having a separate repository doesn't seem to make much of a difference, other then, with a separate repository, merges can be done with somebody who actually knows the language, instead of us just guessing. Separate repository implies separate site (unless we create some scripts to copy content from one repository to another, which doesn't seem all that necessary)
from archive-website.
I'm not opposed to having a separate repo,, but what would we do about share CSS, images, etc? Manually copy them whenever they changed?
from archive-website.
Good point, I'm actually not 100% sure what to do about those. Doesn't Github allow for nested repositories somehow? I though I saw something like that. Could we possibly use that?
from archive-website.
Node.js seems to have repositories for localization: e.g. https://github.com/nodejs?utf8=%E2%9C%93&query=ja
I image that "gensite" script takes localization contents from those repositories.
At the time, the script inserts a note "this translated content might be old" if the localization content is older than original.
from archive-website.
Okay, so we can start with a separate repo.
from archive-website.
Well, vuejs has the same characteristic, with separated repo and new branches.
it seems that there is not a better solution than this for now .
Actually, in the past three weeks, with the efforts of my teammates, the translation is basically completed without proofreading, and has been published to a temporary site mixing Chinese and English.
In my plan, after the completion of proofreading, the final Chinese version of ESLint will be born in the coming weeks。
So, may it be possible to be published to http://cn.eslint.org or http://eslint.cn ?
from archive-website.
Yes, if I setup a repo for cn.ESLint.org, can you use that?
from archive-website.
I setup a repo for cn.eslint.org. @molee1905 I've given you permission to push to that repo. Please let me know who else should have permission.
from archive-website.
Very thanks.
Now the mixed version eslint-zh forked from eslint.github.io is on smocean, i will move it to the new repo after preliminary proofreading to eliminate typos, inaccurate or obscure statement in Chinese , and work on the new repo, to let more people take part in.
from archive-website.
I've setup cn.eslint.org CNAME, so it's now using the new repo: http://cn.eslint.org/
from archive-website.
Awesome!
from archive-website.
Closing this since the work for this specific task is done. Further discussion is occurring here.
from archive-website.
Related Issues (20)
- Example for linter.defineParser uses old "parse" API HOT 1
- More documentation on conflicting fixes HOT 4
- Update fetch sponsors script
- Missing Substack logo HOT 1
- Add date posted for blog posts HOT 9
- Add a way to manually add sponsors HOT 1
- Docs: Add emoji and notice to indicate which rules provide suggestions HOT 1
- Proposal: Split up website HOT 2
- Cleanup the rules list in Rules Configuration of Demo HOT 7
- add ecmaversion "latest" in demo HOT 1
- Update: Add authors to newer blog posts
- Update blog post front matter HOT 12
- Add warning for suggested changes to rule docs HOT 10
- Make sure every blog post has a teaser HOT 7
- Disable anonymous proxy HOT 2
- Search results are not scrollable HOT 1
- Authors not displayed on blog posts with more than 1 author HOT 2
- Fix blog post authors HOT 2
- Build broken HOT 2
- Please provide documentation in yml format as well 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 archive-website.