-
Notifications
You must be signed in to change notification settings - Fork 291
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Translation: FAQ > Virtual DOM and Internals [Ready for review] #133
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very good, really good start! I just fixed a typo in «arbol -> árbol» and changed de use of «UI» for «IU» as it is the term we are using everywhere for consistency among articles. I didn't just merge because of the issue with the title. I made some suggestions. Tell me what you think.
- Es cierto que el título no funciona bien tal y como está. Quizá podría ser «DOM virtual y elementos internos», «DOM virtual y detalles internos» o «DOM virtual y detalles de implementación». La última es la traducción más libre y quizá no encaja del todo en el espíritu del título.
- Creo que mantener Shadow DOM no es un problema al ser una tecnología que no está asociada a React y que hasta ahora no se utiliza para ella una traducción (por ejemplo en MDN utilizan el término sin cambiar).
Thank you! :) About your suggestions for the title, |
Ok, very good! Ready to merge |
The translation is ready for any feedback that you can provide @dmoralesm, @carburo, and @alejandronanez.
I'm not really happy with these points:
Internals
, I thought on something likeDOM virtual y la implementación de React
, do you think that it is more accurate that the current one?Shadow DOM
untranslated, becauseDOM sombra
doesn't sound really good to me. On the other handVirtual DOM
is translated toDOM Virtual
, which is a bit incosistent. Do you want to keep both of them untranslated or have any other idea for this?Relates to issue #4.