Comments (12)
/cc @jlord it would be great to figure out a way to support translated docs on the site
from electronjs.org-old.
@keithduncan In Github OSS projects, is there any project which has translated docs ?
from electronjs.org-old.
My biggest concern is maintenance - it would be a shame if only the English docs stayed up-to-date.
from electronjs.org-old.
@thedaniel I also think I want to avoid confusing.
from electronjs.org-old.
@sotayamashita—@kevinsawicki mentioned in conversation that perhaps having some guides translated would be good because they'll change less than API docs.
What would be your top picks from the docs to be translated?
from electronjs.org-old.
@kevinsawicki mentioned in conversation that perhaps having some guides translated would be good because they'll change less than API docs.
I got it.
What would be your top picks from the docs to be translated?
I think these guides should be translated first below:
I also want to translate some tutorials. If there is Japanese one, they can get started with it easily.
from electronjs.org-old.
@jlord What do you think?
from electronjs.org-old.
@sotayamashita I think that sounds great!
I'm currently working on having the documentation on the site here, but it will all be sourced from the docs
directory in atom/electron
. Whenever you're ready you could start a PR for those tutorials over on that repo ✨
from electronjs.org-old.
I'm currently working on having the documentation on the site here, but it will all be sourced from the docs directory in atom/electron. Whenever you're ready you could start a PR for those tutorials over on that repo
OK. I got it.
By the way, How should I translate ? Should I create a directory like docs-ja
under atom/electron
?
from electronjs.org-old.
@sotayamashita We'll want to keep everything within the docs
directory in atom/electron
because that's what we pull out for the website. I think actually just creating a duplicate markdown file of the english one would be fine. Like so:
# original
docs/tutorial/using-native-node-modules.md
# translated
docs/tutorial/using-native-node-modules-jp.md
How does that sound? Then we'll add a link to the English version letting people know there is a translated option as well.
from electronjs.org-old.
Sound good. I am going to start to translate docs. Thanks for everything.
from electronjs.org-old.
✨
Awesome! Will close it here and we'll use the atom/electron
issue now 👍
from electronjs.org-old.
Related Issues (20)
- Changelog for 11.4.7? HOT 1
- When I was loading external Web links using Browser Window, I ran into a tricky problem HOT 1
- subproject sites are inaccessible through normal navigation
- fiddle site does not use max-width like the rest of the website HOT 2
- Misleading Fenced code block markings
- navigation bar coloring HOT 1
- child_process.exec in electron doesn't work HOT 1
- German Translation translates Class and Identifier Names HOT 1
- Link to quick start guide on community page is broken in english HOT 2
- new releases are not being shown in releases/ HOT 2
- Error ENOENT src not found in .... HOT 1
- Is it so difficult to write a documentation properly ?! – .pageRanges for printToPDF HOT 3
- How to handle deeplink arguments for windows and app opens for first time? HOT 1
- Encountered a lil bug on the Electron Fiddle Page HOT 3
- electronjs.org/images CORS blocks electron-app-store HOT 1
- Add menu button for homepage HOT 6
- Unable to use jquery virtual keyboard
- Theme changes don't work on homepage HOT 2
- Deep linking no working on Windows not working
- How would an API look like? This would be impossible with `contextIsolation` (you cannot pass an `HTMLElement` around). Your first problem with cropping could be solved by passing `rect` to `capturePage`, e.g. via `getBoundingClientRect` which can be safely obtained in the renderer and serialized. What's left is that you seem to have issues with transparency not being conserved. I assume because you want to capture only a given element without things like the background color of the `body` being rendered as well? Or in the case of `getBoundingClientRect` you wouldn't want elements that overlap it (e.g. position: fixed) to also be captured?
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 electronjs.org-old.