LilyPond Contributor's Guide: 6.4 Translating the website

## 6.4 Translating the website

As it has much more audience, the website should be translated before the documentation; see Translating the documentation.

In addition to the normal documentation translation practices, there are a few additional things to note:

- Build the website with:

  >     make website

  however, please note that this command is not designed for being run multiple times. If you see unexpected output (mainly the page footers getting all messed up), then delete your ‘`out-website`’ directory and run `make website` again.

- Some of the translation infrastructure is defined in python files; you must look at the `### translation data` sections in:

  >     scripts/build/create-weblinks-itexi.py
  >     scripts/build/website_post.py

- Translations are not included by default in `make website`. To test your translation, edit the `WEB_LANGS` line in ‘`make/website.make`’. Do not submit a patch to add your language to this file unless `make website` completes with less than 5 warnings.
- Links to manuals are done with macros like `@manualDevelLearningSplit`. To get translated links, you must change that to `@manualDevelLearningSplit-es` (for es/Spanish translations, for example).

#### LilyPond — Contributor’s Guide