Prepare for translation

developer/building/development-workflow.md

@@ -1,23 +1,23 @@
 ---
+lang: en
 layout: doc
-title: Development Workflow
 permalink: /doc/development-workflow/
 redirect_from:
 - /en/doc/development-workflow/
 - /doc/DevelopmentWorkflow/
 - /wiki/DevelopmentWorkflow/
+ref: 66
+title: Development Workflow
 ---
 
-Development Workflow
-====================
+# Development Workflow
 
 A workflow for developing Qubes OS+
 
 First things first, setup [QubesBuilder](/doc/qubes-builder/). This guide
 assumes you're using qubes-builder to build Qubes.
 
-Repositories and committing Code
---------------------------------
+# Repositories and committing Code
 
 Qubes is split into a bunch of git repos. This are all contained in the
 `qubes-src` directory under qubes-builder. Subdirectories there are separate
@@ -149,21 +149,20 @@ RPMS will appear in qubes-src/linux-kernel/pkgs/fc20/x86\_64:
 
 ### Useful [QubesBuilder](/doc/qubes-builder/) commands
 
-1.  `make check` - will check if all the code was committed into repository and
+1. `make check` - will check if all the code was committed into repository and
 if all repository are tagged with signed tag.
-2.  `make show-vtags` - show version of each component (based on git tags) -
+2. `make show-vtags` - show version of each component (based on git tags) -
 mostly useful just before building ISO. **Note:** this will not show version
 for components containing changes since last version tag
-3.  `make push` - push change from **all** repositories to git server. You must
+3. `make push` - push change from **all** repositories to git server. You must
 set proper remotes (see above) for all repositories first.
-4.  `make prepare-merge` - fetch changes from remote repositories (can be
+4. `make prepare-merge` - fetch changes from remote repositories (can be
 specified on commandline via GIT\_SUBDIR or GIT\_REMOTE vars), (optionally)
 verify tags and show the changes. This do not merge the changes - there are
 left for review as FETCH\_HEAD ref. You can merge them using `git merge
 FETCH_HEAD` (in each repo directory). Or `make do-merge` to merge all of them.
 
-Copying Code to dom0
---------------------
+## Copying Code to dom0
 
 When developing it is convenient to be able to rapidly test changes. Assuming
 you're developing Qubes on Qubes, you should be working in a special VM for
@@ -309,7 +308,6 @@ to `testbuilder` VM. Otherwise it creates remote pointing at github account of
 the same name. In any case it points at repository matching current directory
 name.
 
-
 ## Sending packages to different VM
 
 Other useful script(s) can be used to setup local package repository hosted in
@@ -421,10 +419,10 @@ Remember to also import gpg public key using `rpm --import`.
 
 Steps are mostly the same as in the case of yum repo. The only details that differ:
 
- - use [linux-deb] instead of [linux-yum] as a base - both in source and target VM
- - use different `update_repo.sh` script in source VM (below)
- - use `local.UpdateApt` qrexec service in target VM (code below)
- - in target VM additionally place `update-local-repo.sh` script in repository dir (code below)
+- use [linux-deb] instead of [linux-yum] as a base - both in source and target VM
+- use different `update_repo.sh` script in source VM (below)
+- use `local.UpdateApt` qrexec service in target VM (code below)
+- in target VM additionally place `update-local-repo.sh` script in repository dir (code below)
 
 `update_repo.sh` script:
 

developer/building/qubes-builder-details.md

@@ -1,11 +1,13 @@
 ---
+lang: en
 layout: doc
-title: Qubes Builder Details
 permalink: /doc/qubes-builder-details/
 redirect_from:
 - /en/doc/qubes-builder-details/
 - /doc/QubesBuilderDetails/
 - /wiki/QubesBuilderDetails/
+ref: 65
+title: Qubes Builder Details
 ---
 
 [QubesBuilder](/doc/qubes-builder/) "API"
@@ -18,28 +20,28 @@ Components Makefile.builder file
 
 Variables for Linux build:
 
--   `RPM_SPEC_FILES` List (space separated) of spec files for RPM package build. Path should be relative to component root directory. [QubesBuilder](/doc/qubes-builder/) will install all BuildRequires (in chroot environment) before the build. In most Qubes components all spec files are kept in *rpm\_spec* directory. This is mainly used for Fedora packages build.
--   `ARCH_BUILD_DIRS` List (space separated) of directories with PKGBUILD files for Archlinux package build. Similar to RPM build, [QubesBuilder](/doc/qubes-builder/) will install all makedepends, then build the package.
+- `RPM_SPEC_FILES` List (space separated) of spec files for RPM package build. Path should be relative to component root directory. [QubesBuilder](/doc/qubes-builder/) will install all BuildRequires (in chroot environment) before the build. In most Qubes components all spec files are kept in *rpm\_spec* directory. This is mainly used for Fedora packages build.
+- `ARCH_BUILD_DIRS` List (space separated) of directories with PKGBUILD files for Archlinux package build. Similar to RPM build, [QubesBuilder](/doc/qubes-builder/) will install all makedepends, then build the package.
 
 Most components uses *archlinux* directory for this purpose, so its good to keep this style.
 
 Variables for Windows build:
 
--   `WIN_COMPILER` Choose which compiler should be used for this component, thus which build scripts. Currently two options available:
-    -   `WDK` - Windows Driver Kit (default). Command used to build: *build -cZg*.
-    -   `mingw` - MinGW (Windows gcc port). Command used to build: *make all*
--   `WIN_SOURCE_SUBDIRS` List of directories in which above command should be run. In most cases it will be only one entry: current directory (*.*).
--   `WIN_PREBUILD_CMD` Command to run before build, mostly useful for WDK build (in mingw case, you can use makefile for this purpose). Can be used to set some variables, preprocess some files etc.
--   `WIN_SIGN_CMD` Command used to sign resulting binaries. Note that default value is *sign.bat*. If you don't want to sign binaries, specify some placeholder here (eg. *true*). Check existing components (eg. vmm-xen-windows-pvdrivers) for example scripts. This command will be run with certain environment variables:
-    -   `CERT_FILENAME` Path to key file (pfx format)
-    -   `CERT_PASSWORD` Key password
-    -   `CERT_PUBLIC_FILENAME` Certificate path in the case of self-signed cert
-    -   `CERT_CROSS_CERT_FILENAME` Certificate path in the case of correct autheticode cert
-    -   `SIGNTOOL` Path to signtool
--   `WIN_PACKAGE_CMD` Command used to produce installation package (msi or msm). Default value is *wix.bat*, similar to above - use *true* if you don't want this command.
--   `WIN_OUTPUT_HEADERS` Directory (relative to `WIN_SOURCE_SUBDIRS` element) with public headers of the package - for use in other components.
--   `WIN_OUTPUT_LIBS` Directory (relative to `WIN_SOURCE_SUBDIRS` element) with libraries (both DLL and implib) of the package - for use in other components. Note that [QubesBuilder](/doc/qubes-builder/) will copy files specified as *\$(WIN\_OUTPUT\_LIBS)/\*/\** to match WDK directory layout (*\<specified directory\>/\<arch directory\>/\<actual libraries\>*), so you in mingw build you need to place libraries in some additional subdirectory.
--   `WIN_BUILD_DEPS` List of components required to build this one. [QubesBuilder](/doc/qubes-builder/) will copy files specified with `WIN_OUTPUT_HEADERS` and `WIN_OUTPUT_LIBS` of those components to some directory and provide its path with `QUBES_INCLUDES` and `QUBES_LIBS` variables. Use those variables in your build scripts (*sources* or *Makefile* - depending on selected compiler). You can assume that the variables are always set and directories always exists, even if empty.
+- `WIN_COMPILER` Choose which compiler should be used for this component, thus which build scripts. Currently two options available:
+  - `WDK` - Windows Driver Kit (default). Command used to build: *build -cZg*.
+  - `mingw` - MinGW (Windows gcc port). Command used to build: *make all*
+- `WIN_SOURCE_SUBDIRS` List of directories in which above command should be run. In most cases it will be only one entry: current directory (*.*).
+- `WIN_PREBUILD_CMD` Command to run before build, mostly useful for WDK build (in mingw case, you can use makefile for this purpose). Can be used to set some variables, preprocess some files etc.
+- `WIN_SIGN_CMD` Command used to sign resulting binaries. Note that default value is *sign.bat*. If you don't want to sign binaries, specify some placeholder here (eg. *true*). Check existing components (eg. vmm-xen-windows-pvdrivers) for example scripts. This command will be run with certain environment variables:
+  - `CERT_FILENAME` Path to key file (pfx format)
+  - `CERT_PASSWORD` Key password
+  - `CERT_PUBLIC_FILENAME` Certificate path in the case of self-signed cert
+  - `CERT_CROSS_CERT_FILENAME` Certificate path in the case of correct autheticode cert
+  - `SIGNTOOL` Path to signtool
+- `WIN_PACKAGE_CMD` Command used to produce installation package (msi or msm). Default value is *wix.bat*, similar to above - use *true* if you don't want this command.
+- `WIN_OUTPUT_HEADERS` Directory (relative to `WIN_SOURCE_SUBDIRS` element) with public headers of the package - for use in other components.
+- `WIN_OUTPUT_LIBS` Directory (relative to `WIN_SOURCE_SUBDIRS` element) with libraries (both DLL and implib) of the package - for use in other components. Note that [QubesBuilder](/doc/qubes-builder/) will copy files specified as *\$(WIN\_OUTPUT\_LIBS)/\*/\** to match WDK directory layout (*\<specified directory\>/\<arch directory\>/\<actual libraries\>*), so you in mingw build you need to place libraries in some additional subdirectory.
+- `WIN_BUILD_DEPS` List of components required to build this one. [QubesBuilder](/doc/qubes-builder/) will copy files specified with `WIN_OUTPUT_HEADERS` and `WIN_OUTPUT_LIBS` of those components to some directory and provide its path with `QUBES_INCLUDES` and `QUBES_LIBS` variables. Use those variables in your build scripts (*sources* or *Makefile* - depending on selected compiler). You can assume that the variables are always set and directories always exists, even if empty.
 
 builder.conf settings
 ---------------------