Git Product home page Git Product logo

progit2-nl's Introduction

Pro Git, 1st Edition

This is the source for the 1st edition of the Pro Git book. The second edition has since been released and is what will be maintained and published going forward. Please suggest any changes to that version instead.

You can find the new edition at:

https://github.com/progit/progit2

If you're looking for the original README content, it can be found in the README.original.md file.

progit2-nl's People

Contributors

amacfie avatar bartbroere avatar ben avatar carlosmn avatar casmo avatar cdwilson avatar cpt-xx avatar damz avatar dependabot[bot] avatar harupong avatar jnavila avatar jorrit avatar justinclift avatar louiseeditor avatar madhead avatar masoudfallahpour avatar mbolivar avatar metabr avatar miketlive avatar mminer avatar mrlucmorin avatar nobozo avatar pableu avatar paveljanik avatar pborreli avatar pmiossec avatar schacon avatar tacker66 avatar tritemio avatar zigarn avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

progit2-nl's Issues

Aligned the Dutch translation, however not visible

Hi, I've (finally) aligned the Dutch translation to the 2.1.75 version of the English master version. I've removed most of the referral issues reported by the mobi builder (some of them are really strange, everything seems to be pointing correctly).

However on https://git-scm.com/book/nl/v2 this newer version is not visible.

Is there something else I need to do besides merging to master? Or is there something you, Ben or Jean-Noel needs to trigger?

Build issue

Atlas build system is throwing this:

The following errors were encountered parsing the HTML files in this project: book/03-git-branching/1-git-branching.asc:782: parser error : attributes construct error

How to get the corrections in?

Hi Scott,

I've got a starter question for you: I've made a lot of corrections and translated a few more chapters. Now I've got them pushed into the Cpt-xx/progit2 master and I thought I could create a pull request and point it to progit/progit2-nl. However, that doesn't fly, even though the SHA-1 is equal to the one of progit2-nl. How do I get the modifications in?
Do I:

  • Fork the progit/progit2-nl, and drop the changes in (somehow... I'll have to figure that one out) locally and push them up to the new fork and then create a pull request from there
  • Change the base ref of my local copy to progit/progit2-nl (not sure whether that would work correctly)
  • Wait for your answer before I damage the progit/progit2-nl repo?

Thanks for your patience.

Cor

Continuous integration seems to have stopped for the screen, not the PDF contents

Hi Scott,

I think that because of an UTF-8 encoding issue (which I have already resolved) the CI robot (Jenkins/Hudson/Bamboo/Other brands are available) might have stopped and hasn't restarted. I still see that a quite old version of the repo is used in the transformation to PDF.

Could you check why the transformations seem to have stopped and see if you can start it up again?

I haven't had any signal that the transformation has halted, so I couldn't react earlier.

Thanks for the effort.

Kind regards,

Cor

EDIT:
It seems that the issue is a bit more strange: the information shown on http://git-scm.com/book/nl/v2 does not equal the information shown when clicking on the pdf-link. The PDF is actually up to date with the latest contents of the repository, whereas the screen still shows something from the past.

I hope this addition helps in the resolving of the issue.

EDIT 2:
On https://progit.org/translations/lang/nl multiple check-ins are reported to be building, some of them seem to be running for more than 15 days, which is a bit long in my view.

My guesstimate is that this has to do with the encoding problem that seems to be a recurring event on my environment. I have tried to keep the encoding on ISO8859-1, however there seem to be conflicting characters (true UTF-8??) in various files in the original English version and sometimes my translated files seem to spontaneously change from ISO8859-1 to UTF-8. The latter may have to do with the editor I'm using, and I'm keeping a close eye on that and will keep you posted on this.

EDIT 3:
I have found the culprits in the text and have reverted everything back to UTF-8, and the Atlas builds seem to run fine now, the PDFs, e-pub, mobi and presumably the html version of the site are generated with this latest version. The site on http://git-scm.com/book/nl/v2 however is still showing a (very) earlier version of the html, in which not all pages are translated. How can this be?

English sentence in text

In chapter 7.11 Git Tools - Submodules there is still an English sentence present. In section 'Beginnen met submodules' there is the following sentence 'This is how other people who clone this project know where to get the submodule projects from.'. The translated text is already written.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo 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.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.