#3107 Website: translated PDF of web manuals are not generated and links to web PDF are often broken

[Anonymous]

Originally created by: *anonymous

Originally created by: fedel...@gmail.com

Problem discussed on lilypond-devel:
http://lists.gnu.org/archive/html/lilypond-devel/2013-01/msg00108.html

It seems that only the english web manual is generated as PDF. This occurred also in previous versions, as you can see here (change to 2.14 and 2.13 also):
http://lilypond.org/doc/v2.15/Documentation/

We would expect 'make doc' to generate also translated PDF files, only if the manual has been translayed: web-xx.pdf

Another problem is the links to PDF of website.
This is a bit confusing since the link may be to web.pdf or web-xx.pdf depending on the language. But even in the same language the link may be different in these two pages:
http://lilypond.org/website/web.html
http://lilypond.org/website/development.html

For example, check the spanish pages. In the first page the link is to web.pdf (english), in the development page the link is to web.es.pdf (spanish, and missing file).

[Google Importer]

Originally posted by: PhilEHol...@googlemail.com

One point of information to help fix this.  The files that are built in the translated languages are *.tely files.  There are also top-level *.texi files - e.g. contributor and web.  These don't appear to be built with their translations.

[Federico Bruni]

I'm marking this as a duplicate of issue [#5083], which fixes the generation of web-xx.pdf files.
There's no problem with links. Translators should append their language code (e.g.: -es or -fr) to the macro links, in order to have the correct link.