Skip to content
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: Spanish translation for the new master.next content #20

Open
nestorrojas opened this issue Mar 30, 2012 · 9 comments
Open

Comments

@nestorrojas
Copy link
Contributor

No spanish version publicly available despite it is already translated. :-?

@ghost ghost assigned jaredwilli Mar 30, 2012
@rcherny
Copy link
Contributor

rcherny commented Dec 6, 2012

Please see issue #12.

This is a work in progress. It's going to come in "spurts" as we have time ... hoping sooner rather than later.

@nestorrojas
Copy link
Contributor Author

Just announce when it is ready, I would be please to translate it.

@rcherny
Copy link
Contributor

rcherny commented Dec 10, 2012

Thanks man, appreciate it. What is probably going to happen is once we reconcile the Master and GH Pages (hoping this week) is there will be some updates needed to the already created Spanish content based on the updates that had been made in both branches. Unfortunately what happened was we had to redeploy the live docs to Github rather quickly and things got out of sync. And, we were in the middle of recreating a build process at the time, which didn't help.

@rcherny
Copy link
Contributor

rcherny commented Jan 28, 2013

Hey, so we've done a number of updates to the English versions of the content, which probably needs porting over to the Spanish. Not the least of which includes all references to "Isobar" are now "Roundarch Isobar" to represent our new brand. That said, some content has been updated.

So a quick review of the content under /sections/es may be in order in the near future. That said, and I know it's almost a broken record, but the content is facing more updates in the near future.

So, this comment on this ticket is just a heads up that the Spanish is (1) out of date, and could be brought up to date, and ultimately there will be (2) more to come soon (ish).

@nestorrojas
Copy link
Contributor Author

Great. As soon as I'll have some spare time I'll work on it. Probably next
weekend.

I had a harddisk disaster so I turned off side projects for some time. But
I´m back.

On Mon, Jan 28, 2013 at 3:48 PM, Rob Cherny notifications@github.comwrote:

Hey, so we've done a number of updates to the English versions of the
content, which probably needs porting over to the Spanish. Not the least of
which includes all references to "Isobar" are now "Roundarch Isobar" to
represent our new brand. That said, some content has been updated.

So a quick review of the content under /sections/es may be in order in the
near future. That said, and I know it's almost a broken record, but the
content is facing more updates in the near future.

So, this comment on this ticket is just a heads up that the Spanish is (1)
out of date, and could be brought up to date, and ultimately there will be
(2) more to come soon (ish).


Reply to this email directly or view it on GitHubhttps://github.com//issues/20#issuecomment-12782288.

@rcherny
Copy link
Contributor

rcherny commented Nov 8, 2013

New build process is real close. Have a branch with it working! Does both English and Spanish, and can handle more languages and markdown (also soon).

@rcherny
Copy link
Contributor

rcherny commented Nov 9, 2013

https://github.com/rcherny/code-standards/tree/assemble-build

This new build process supports multiple languages and should be incorporated soon.

@rcherny
Copy link
Contributor

rcherny commented Nov 8, 2014

@nestorrojas Sorry to do this but the new Master.next branch will feature content that is effectively a rewrite. So we will really need what amounts to a new translation. Please keep an eye on that branch, ok? Thanks.

@rcherny rcherny changed the title No spanish live docs Translation: Spanish translation for the new master.next content Nov 8, 2014
@rcherny rcherny modified the milestone: Standards.Future Aug 25, 2015
@rcherny
Copy link
Contributor

rcherny commented Aug 25, 2015

Note master.next has been merged into master. Not sure if this is still something someone wants to do, but we will keep this open for the time being.

@rcherny rcherny removed their assignment Aug 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants