-Welcome to your wiki! This is the default page we've installed for your convenience. Go ahead and edit it.
-This wiki uses the [[http://www.wikicreole.org/|Creole]] syntax, and is fully compatible with the 1.0 specification.
-The wiki itself is actually a hg repository, which means you can clone it, edit it locally/offline, add images or any other file type, and push it back to us. It will be live immediately.
-$ hg clone http://bitbucket.org/gpiancastelli/hgbook-it/wiki/
-Wiki pages are normal files, with the .wiki extension. You can edit them locally, as well as creating new ones.
-=== Syntax highlighting ===
-You can also highlight snippets of text, we use the excellent [[http://www.pygments.org/|Pygments]] library.
-Here's an example of some Python code:
- formatter = lambda t: "funky"+t
-You can check out the source of this page to see how that's done, and make sure to bookmark [[http://pygments.org/docs/lexers/|the vast library of Pygment lexers]], we accept the 'short name' or the 'mimetype' of anything in there.
+Welcome to the wiki for the Italian translation of "Mercurial: The Definitive Guide".
+The translation is still a work in progress. As soon as it's finished, I'll point to a URL where you can read the online version of the book.
+This wiki describes the challenges faced and explains the choices made during the translation of this technical book. As such, is aimed at other translators of technical books from English into Italian, especially those who work on books dealing with Version Control and related tools (Subversion, git, and so on). The wiki will definitely contain text in English and Italian; however, all the pages are written in English unless otherwise noted.
+=== Translating the Mercurial book ===
+"Mercurial: The Definitive Guide" is written in DocBook (coming from LaTeX, really) and uses a mixture of shell scripting, Python, and some graphic programs (Graphviz and Inkscape) to build itself in a readable form, e.g. HTML. In particular, the book features //live examples//, which are a primary challenge for translators.
+Images are crafted in SVG, graphs are specified using the DOT format from Graphviz, all text-based. This is just... great. PNG is the final format which images and graphs are converted to, and also the preferred format for screenshots and icons throughout the book.
+Sometimes a translator has to slightly adjust part of the content, add footnotes, and so on. Everything that differs from the original content should be collected in a document and made available to interested people.
+One of the tasks that a technical translator naturally faces is building a technical vocabulary in the target language, sometimes translating technical terms, other times preserving the original terms. Publishing such a vocabulary helps translators dealing with the same conceptual space or similar tools to collectively build a shared terminology.