Re: Starting off a new community book project

[Jacques Menu]

Le 25 juin 2015 à 13:07, Urs Liska <address@hidden> a écrit :



Am 25.06.2015 um 08:02 schrieb Jacques Menu:

Hello Urs,

Great idea!

I can contribute with contents such as the attached.

You mean with directions how to achieve such material?
That would be fine, just make a suggestion how to fit it in an outline
(doesn't matter if it would still be out of context).

That could be kind of a case study of some size.

It would show the use of bash, LaTeX and lilypond-book to typeset a bassoon or oboe/english horn fingerings table (I have both), and targeting readers with some knowledge of these tools.

The idea is to iterate on the generation of LP code for all notes on the instrument from templates, in which __*__ models are replaced with actual values.

The graphics thus produced by lilypond-book are then used in a regular LaTeX file to obtain the document.

Some extracts follow (would have to be fined-tuned and totally adapted to English of course, I wrote all this some time ago).

I also attach a view of the oboe stuff.

HTH!

JM

------------

address@hidden:~/Documents/LaTeX/DoigtesDeBasson > cat ModeleDeNote_bass.tex
\documentclass[a4paper]{article} 
\begin{document} 

\begin[fragment,staffsize=16,notime]{lilypond} % quote,
%\version "2.13.63"  % necessary for upgrading to future LilyPond versions.

\clef bass
\relative c__RELATIVITE_EN_CLE_DE_FA__
{
__NOTE__
}

\end{lilypond}
\end{document}

------------

address@hidden:~/Documents/LaTeX/DoigtesDeBasson > cat ToutSynthetiser
#!//bin/bash

set -x

GENRE_DE_FRAGMENT=bass_tenor_treble
#GENRE_DE_FRAGMENT=bass_tenor
#GENRE_DE_FRAGMENT=bass
#GENRE_DE_FRAGMENT=tenor
#GENRE_DE_FRAGMENT=treble

FICHIER_MODELE_DE_NOTE=ModeleDeNote_${GENRE_DE_FRAGMENT}.tex

SOURCE_DIR=lilysource_${GENRE_DE_FRAGMENT}

LOG_FILE=$0.log


if [ -d ${SOURCE_DIR} ]; then
rm -r ${SOURCE_DIR}
fi

mkdir ${SOURCE_DIR}

cd ${SOURCE_DIR}


for OCTAVE in 0 1 2 3; do

for NOTE in c cis des d dis ees e f fis ges g gis aes a ais bes b; do

MODELE=${PWD}/../${FICHIER_MODELE_DE_NOTE}
TEX_FILE=${PWD}/${NOTE}${OCTAVE}.tex
EPS_FILE=${PWD}/${NOTE}${OCTAVE}.eps

echo "==> $0 MODELE = ${MODELE} TEX_FILE = ${TEX_FILE} EPS_FILE = ${EPS_FILE}"
pwd
echo ""

../SynthetiserFichierTeX ${NOTE} ${OCTAVE} ${MODELE} > ${TEX_FILE}

../LilypondIt ${TEX_FILE} # >> ${LOG_FILE} 2&>1

ls -sal ${EPS_FILE}

done 

done

cd ..


echo ""
echo "--> Fichiers EPS synthetises :"
ls -sal ${SOURCE_DIR}/*.eps
echo ""

------------

address@hidden:~/Documents/LaTeX/DoigtesDeBasson > cat LilypondIt
#!/bin/bash

#set -x

USAGE="--> Usage: $0 sourceFileName"

if [ $# -ne 1 ]; then
echo ${USAGE}
exit
fi

SOURCE_FILE=$1
SOURCE_FILE_SANS_SUFFIXE=${SOURCE_FILE/.tex/}
WORK_DIR=lilywork
EPS_RESULTING_FILE="${SOURCE_FILE_SANS_SUFFIXE}.eps"


if [ -d ${WORK_DIR} ]; then
rm -r ${WORK_DIR}
fi

mkdir ${WORK_DIR}


lilypond-book --output=$WORK_DIR ${SOURCE_FILE_SANS_SUFFIXE}.tex
echo ""

set -x

EPS_FILE=${WORK_DIR}/*/*-1.eps
ls -salt ${EPS_FILE}
echo ""

cp -p ${EPS_FILE} ${EPS_RESULTING_FILE}

echo "--> Fichier resultant :"
ls -salt ${EPS_RESULTING_FILE}
echo ""

Urs

JM

Le 24 juin 2015 à 21:41, Urs Liska <address@hidden
<mailto:address@hidden>> a écrit :

Hello fellow LilyPonders,

recently Federico raised my attention by pointing out the release of a
new book on "Mastering MuseScore". After some discussion, consideration
and poking around I decided to lay the foundation for a new community
book about a) LilyPond and b) the "plain text" complex with LilyPond,
LaTeX and Git.

Actually it's not a new idea but one that was already in the back of my
mind when I started the "openLilyLib tutorials" and the respective type
of posts on Scores of Beauty. There always was the wish to gather this
sort of information to a more or less coherent entity like a book.

So what I have by now is not "presentable" but it's in a state that I
can (and have to) announce it in the form of a "call for contribution".

The idea of the "book" is to focus on those topics that the mailing list
reveals to be regular stumbling blocks for new (or sometimes also
seasoned) users. We want to assist them by gently going into great depth
where the official documentation has to remain concise and
reference-like. What I'm most interested in personally is that step from
the needs of occasional or regular users to the more involved but also
more exciting things, talking about aspects like getting into the spirit
of using Scheme, or best practice suggestions to organize larger projects.

For quite some time this "book" will have more empty than written pages,
and it doesn't have to aim at becoming a coherent "textbook". But I hope
that we may achieve something that is comprehensive in the sense that it
helps people diving more deeply in the LilyPond world.

The book is authored in Markdown using GitBook
(https://github.com/GitbookIO/gitbook), a Node.js application that
builds the book as a statically served HTML site.
The official URL (where you can already have a first glimpse) is
http://book.openlilylib.org, and the development repository is at
https://git.ursliska.de/openlilylib/book.
There is another location where unmerged branches will be automatically
built to when pushed, for example
http://bookbranches.openlilylib.org/scheme-tutorials.
It will be possible to edit the pages online or locally, with the local
way being somewhat more flexible but requiring the installation of a few
tools and dependencies.

Now I'm asking for contribution in several fields:
1)
Improving the infrastructure and appearance. The most urgent issue is
adding a CSS stylesheet for the table of contents. The regular TOC is
always expanded, and it is clear that the TOC of that book will soon
become inacceptably long. So we need a foldable/expandable navigation
bar where initially most items are folded.
Probably there's room for other improvments in the styling of the book,
but that's not that urgent.
There are other things on the functionality side where I'd be happy not
to be alone with. These would involve some Node.js, Python and bash
programming.

2)
General discussion about potential contents, i.e. working on the outline
of un-written chapters

3)
Content contribution. One thing that might be attractive to start with
is integrating existing posts from Scores of Beauty. This may be trivial
in some cases, in other cases one has to do significant rearrangements.

As development and deployment take place on my personal server I can't
fully open up the access, which means that anyone who wants to
contribute has to ask me explicitly for an account.

Best wishes
Urs

-- 
Urs Liska
www.openlilylib.org <http://www.openlilylib.org>

_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user