Re: Moving documentation to git

On Wed, Jun 14, 2017 at 12:51 PM, Oliver Albers <olli@3.1415926.org> wrote: > Hello Andreas, > > the git idea has been floating around for a while. The problem with it is > that the translation process for the documentation is very much using > automatic svn keyword substitution for the file’s revision to check if a > version of the translation is up to date or not (see > http://doc.php.net/revcheck.php for example). In my opinion > there needs > to be a workaround for that. For this, I suggest not trying to save the revision id inside the english files. Something like this: 1. In en/, in each directory, use `git log -n 1 --pretty=format:%H -- file.xml` to obtain the last commit hash of each file, and generate a local, ignored .git.hashs file. 2. In translations, the id in revision tags is now the last commit hash. 3. In tools, now it's compare the two ids to see what files need translations and to generate diffs (from revision tag hash to .git.hashs hash). André