@item
The bibliography in Community->Publications is generated automatically
-from @file{@/.bib} files; formatting is done automatically by
-@file{texi@/-web@/.bst}.
+from @file{.bib} files; formatting is done automatically by
+@file{texi-web.bst}.
@item
@dots{}
@subheading Initial setup
-You should symlink your own @file{@/~/lilypond/} to
-@file{@/~graham/@/lilypond/}
+You should symlink your own @file{~/lilypond/} to
+@file{~graham/lilypond/}
If this directory does not exist, make it. Git master should go
-in @file{@/~/lilypond/@/lilypond@/-git/} but make sure you enable:
+in @file{~/lilypond/lilypond-git/} but make sure you enable:
@example
git config core.filemode false
@end example
-If you have created any files in @file{@/~graham/@/lilypond/} then
+If you have created any files in @file{~graham/lilypond/} then
please run:
@example
@end example
To reduce the CPU burden on the shared host (as well as some
-security concerns), the @file{Documentation/@/pictures/} and
-@file{Documentation/@/web/@/ly@/-examples/} directories are
+security concerns), the @file{Documentation/pictures/} and
+@file{Documentation/web/ly-examples/} directories are
@strong{not} compiled. You need to upload them, and if they ever
change, a user in the @code{lilypond} group must upload them to
-@file{@/~graham/@/lilypond@/media} on the host.
+@file{~graham/lilypond/media} on the host.
Upload latest pictures/ and ly-examples/ (local script):
@end verbatim
Check for any updates to trusted scripts / files:
-
+@smallexample
@verbatim
### check-git.sh
#!/bin/sh
cp $GIT/Documentation/web/server/lilypond.org.htaccess $DEST/lilypond.org.htaccess
cp $GIT/Documentation/web/server/website-dir.htaccess $DEST/website-dir.htaccess
@end verbatim
+@end smallexample
Build the website:
@subsubheading Additional information
Some information about the website is stored in
-@file{~graham/@/lilypond/@/*.txt}; this information should not be
+@file{~graham/lilypond/*.txt}; this information should not be
shared with people without trusted access to the server.
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
-@file{out@/-website} directory and run @code{make website} again.
+@file{out-website} directory and run @code{make website} again.
@item
Some of the translation infrastructure is defined in python files;
@item
Translations are not included by default in @code{make website}.
To test your translation, edit the @code{WEB_LANGS} line in
-@file{make/@/website@/.make}. Do not submit a patch to add your language
+@file{make/website.make}. Do not submit a patch to add your language
to this file unless @code{make website} completes with less than 5
warnings.