-
-
Notifications
You must be signed in to change notification settings - Fork 930
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
Add translation to Spanish #457
Conversation
Link LC as for SWC and DC
Unify Library Carpentry logo
by run ~~~ $ find _includes -type f -exec sed -i "s/page.carpentry/site.carpentry/g" {} \; $ find _layouts -type f -exec sed -i "s/page.carpentry/site.carpentry/g" {} \; $ find _extras -type f -exec sed -i "s/page.carpentry/site.carpentry/g" {} \; $ find _episodes -type f -exec sed -i "s/page.carpentry/site.carpentry/g" {} \; $ find bin -type f -exec sed -i "s/page.carpentry/site.carpentry/g" {} \; $ find assets -type f -exec sed -i "s/page.carpentry/site.carpentry/g" {} \; ~~~
Fix logo at navbar
Add Library Carpentry SVG logo
Output episode figures in correct order
SWC uses block inline attribute lists for e.g. code blocks, but I think this HTML tag is much simpler and more understandable than <pre>*Enter*{:.keyboard} ...</pre>
Building `md` from `Rmd` in a script like this will break if the `methods` package is not called and the code includes class object routines. See r-spatial/sf#478
Load methods package
By doing this, when a page is heavily zoomed in (e.g. 500%) the navbar icons stay in the same row, rather than breaking onto two different rows.
…apping Fix episode nav wrapping
Se agregó el archivo de traducción del cápitulo 3.
Se agrega el archivo de traducción
Leccion 5: History. Traducción al español, perimera versión.
Hay que estandarizar las cabeceras y verificar si podemos convertir las claves YAML sin afectar la generación de HTML.
Complete translation
update CONTRIBUTING language
@ErinBecker Can you create https://github.com/swcarpentry/git-novice-es, move this PR to that repository and close this pull request? Thanks. |
@rgaiacs - I don't have admin access in the swcarpentry GitHub org.
Currently working with @jduckles and @maneesha to get the repository
transferred.
…On Feb 20, 2018 12:16 PM, "Raniere Silva" ***@***.***> wrote:
@ErinBecker <https://github.com/erinbecker> Can you create
https://github.com/swcarpentry/git-novice-es, move this PR to that
repository and close this pull request? Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#457 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ASSbf5sh3kzUT2hnui1_NFsqGI53xdrsks5tWpuUgaJpZM4Q8Szr>
.
|
@ErinBecker now has admin access to https://github.com/swcarpentry/git-novice-es |
Are you sure moving to a new repo is the best way to go? Have we decided which is the best way to deal with traslations? (Sorry, if I missed it). |
Hi Ivan, thanks for raising the question. Communication around how
translations are being handled hasn't been very clear. We're testing out
the workflow on these two lessons (git and shell) to see how we need to
adjust the process in the future. For some background on the conversations
so far, please see carpentries/styles#210 and the
issues in the carpentries-es/board repo discussing whether to use a single
or separate repos. Very happy to have you involved with the new
Spanish-language Maintainers and with planning for future translations.
…On Feb 20, 2018 3:57 PM, "Ivan Gonzalez" ***@***.***> wrote:
Are you sure moving to a new repo is the best way to go? Have we decided
which is the best way to deal with traslations? (Sorry, if I missed it).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#457 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ASSbf82neOYnGQt3dWklbU49TeyEnn-Sks5tWs9UgaJpZM4Q8Szr>
.
|
Not 100% sure but is the faster way to have the translation live somewhere. There are a lot of people interested in translating but not a lot o people interested to work on the infrastructure behind it so for now we will use a separate repo. If in the future we decide to merge the repositories it should require run
No one to blame for the bad communication but the great number of channels only make the communication worse. |
I'm closing this in favor of the new repo for the Spanish translation: https://github.com/swcarpentry/git-novice-es/. Please send further PRs/issues there. |
No description provided.