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

Book cover in other languages #594

Closed
andres-mancera opened this issue Apr 13, 2016 · 6 comments
Closed

Book cover in other languages #594

andres-mancera opened this issue Apr 13, 2016 · 6 comments

Comments

@andres-mancera
Copy link
Member

Folks: I recently merged a pull request made by @jamj2000 that contained an update to the book/cover.png image for the Spanish translation of the book. I believe there have been at least 2 successful builds after that, but the book cover does not seem to change and it still uses the old English version. This is the latest build. Any idea why this is happening? Cheers!

@YueLinHo
Copy link
Contributor

See issue #585.

@andres-mancera
Copy link
Member Author

@YueLinHo : I don't get it. Can you please provide some context?

@YueLinHo
Copy link
Contributor

YueLinHo commented Apr 15, 2016

Can you please provide some context?

Someone reported #585, and I checked the auto-build for some translations here: https://progit.org/translations
Found that en and zh-tw stop to build downloads around 3/20.

And I knew Atlas said something here: http://forum.atlas.oreilly.com/
(Effective March 2016, the Atlas forum is no longer available.)

So I guess that progit2 including translating repositoies rely Atlas for auto-building downloads, and Atlas stops to support that unfortunately.

For es version, the last good build is progit/progit2-es@ea7f645 which is on 3/23.
You can tell that by the link you provided:
https://progit2.s3.amazonaws.com/es/2016-03-23-ea7f6/progit-es.1091.pdf
Say 2016-03-23 and ea7f6.
The next commit which is a merge commit and not built is progit/progit2-es@59f78f3 which is on 3/30.

tortoisegitproc

@ben Do I guess right?

@jnavila
Copy link
Member

jnavila commented Apr 15, 2016

Well, if you're right, then neither git-scm.com nor the pdf are updated with our changes, which means that we are working for nothing at the moment.

@andres-mancera
Copy link
Member Author

Good info, thanks for sharing. Perhaps @ben or @schacon can chime in and shed some light on this?

@andres-mancera
Copy link
Member Author

andres-mancera commented Jul 18, 2016

Alright, so it seems like the issue with Atlas has finally gotten enought attention that @ben has opened an issue to keep track of it (#625). Therefore, I am closing this old issue as it's been opened for ~3 months. Cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants