LilyPond Contributor's Guide: 6.4 Translating the website

[ << Website work ]	[Top][Contents][Index][ ? ]			[ LSR work >> ]
[ < Debugging website and docs locally ]		[ Up : Website work ]	[ LSR work > ]

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_LANGUAGES = line in ‘python/langdefs.py’. You will need to copy this updated script to $LILYPOND_BUILD_DIR/python/out.
Do not submit a patch to add your language to this file unless make website completes with fewer 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).

[ << Website work ]	[Top][Contents][Index][ ? ]			[ LSR work >> ]
[ < Debugging website and docs locally ]		[ Up : Website work ]	[ LSR work > ]