Update sources after switching to po4a v0.62

Signed-off-by: Jean-Noël Avila <jn.avila@free.fr>

ci/install_po4a.sh

 #!/bin/sh
 
 git clone https://github.com/mquinson/po4a.git
-cd po4a && git checkout v0.56 && cd ..
+cd po4a && git checkout v0.62 && cd ..

en/config.txt

@@ -120,8 +120,8 @@ are:
 The .git location may be auto-discovered, or come from `$GIT_DIR`
 environment variable. If the repository is auto discovered via a .git
 file (e.g. from submodules, or a linked worktree), the .git location
-would be the final location where the .git directory is, not where
-the .git file is.
+would be the final location where the .git directory is, not where the
+.git file is.
 +
 The pattern can contain standard globbing wildcards and two additional
 ones, `**/` and `/**`, that can match multiple path components. Please
@@ -240,14 +240,12 @@ boolean::
        When a variable is said to take a boolean value, many
        synonyms are accepted for 'true' and 'false'; these are all
        case-insensitive.
-+
-true;;
-  Boolean true literals are `yes`, `on`, `true`,
+
+	true;; Boolean true literals are `yes`, `on`, `true`,
 		and `1`.  Also, a variable defined without `= <value>`
 		is taken as true.
 
-false;;
-  Boolean false literals are `no`, `off`, `false`,
+	false;; Boolean false literals are `no`, `off`, `false`,
 		`0` and the empty string.
 +
 When converting a value to its canonical form using the `--type=bool` type

en/git-init.txt

@@ -20,8 +20,9 @@ DESCRIPTION
 
 This command creates an empty Git repository - basically a `.git`
 directory with subdirectories for `objects`, `refs/heads`,
-`refs/tags`, and template files.  An initial `HEAD` file that
-references the HEAD of the master branch is also created.
+`refs/tags`, and template files.  An initial branch without any
+commits will be created (see the `--initial-branch` option below
+for its name).
 
 If the `$GIT_DIR` environment variable is set then it specifies a path
 to use instead of `./.git` for the base of the repository.
@@ -73,8 +74,10 @@ If this is reinitialization, the repository will be moved to the specified path.
 -b <branch-name>::
 --initial-branch=<branch-name>::
 
-Use the specified name for the initial branch in the newly created repository.
-If not specified, fall back to the default name: `master`.
+Use the specified name for the initial branch in the newly created
+repository.  If not specified, fall back to the default name (currently
+`master`, but this is subject to change in the future; the name can be
+customized via the `init.defaultBranch` configuration variable).
 
 --shared[=(false|true|umask|group|all|world|everybody|0xxx)]::
 

en/git-rebase.txt

@@ -663,7 +663,7 @@ In addition, the following pairs of options are incompatible:
  * --fork-point and --root
 
 BEHAVIORAL DIFFERENCES
------------------------
+----------------------
 
 git rebase has two primary backends: apply and merge.  (The apply
 backend used to be known as the 'am' backend, but the name led to

sources.txt

@@ -106,7 +106,6 @@ git-p4.txt
 git-pack-objects.txt
 git-pack-redundant.txt
 git-pack-refs.txt
-git-parse-remote.txt
 git-patch-id.txt
 git-prune-packed.txt
 git-prune.txt