-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

The file Documentation/user/install.itely contains the comment:

~~~~~~~~~~~~~~~~~~~~~~~
@c TRANSLATORS:
@c   Please **do not** translate anything below this line.  Users
@c   should not be compiling LilyPond themselves; if they really
@c   want to do so, they should be able to read the English docs,
@c   because they'll probably need to ask questions in English
@c   on the -devel list.   -gp

@node Compiling from source
@section Compiling from source
~~~~~~~~~~~~~~~~~~~~~~~


I understand the reasons and I agree, too. However, it's not clear to me how 
the following sections should look like in the translations. Shall we simply 
replace all of section 1.2 by something like:

~~~~~~~~~~~~~~~~~~~~~~~
@node Compiling from source
@section Compiling from source

You can also compile LilyPond directly from the source-code in the git 
repository. As this definitely requires some basic knowledge of English, we 
only refer to the [[link to english Compiling-from-source.html|English 
documentation]] for the instructions.
~~~~~~~~~~~~~~~~~~~~~~~

I would prefer this to directly inserting english text in the translated 
documentation. However, what I'm missing is a way to create a link to the 
corresponding English section... How can I do this?

Cheers,
Reinhold

- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: [EMAIL PROTECTED], http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
 * K Desktop Environment, http://www.kde.org, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFIx7pHTqjEwhXvPN0RAmOSAKCk99/FvniBb0ponCgtFaGJ6KmxpACfW/UT
jCHxe/rCpko5duFEROKhpmM=
=fVc6
-----END PGP SIGNATURE-----


_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Reply via email to