Jan Nieuwenhuizen wrote:
Graham Percival writes:
We currently use `makeinfo --html' to build the online documentation.
Makeinfo is the normal way to create texinfo docs, but it lacks many
useful features. Most importantly, it can't create HTML pages split
into subsections; it only creates spli
If you write (or significantly modify) any lilypond examples, be careful
about the limited spacing in the manual. Specifically, all examples in
the manual are created with this block:
\paper {
#(define dump-extents #t)
line-width = 160\mm - 2.0 * 0.4\in
ragged-right = ##t
indent = 0\m
Ralph Little <[EMAIL PROTECTED]> writes:
> Hi,
> Ah, sorry, I should have made myself clearer - I meant in Lilypond
> source code. :D
>
> 2 spaces it is..
2 spaces, but "C-x h M-x tabify"ed.
nicolas
___
lilypond-devel mailing list
lilypond-devel@gnu.
Hi,
Sorry, I should also have officially mentioned that I am tackling the
*long* promised Braille output option for Lilypond. This is a *serious*
effort to get this done.
I currently have some scheme and C++ code for manipulating Braille.
Also, I have modified a recent git pull to replicate th
Hi,
Ah, sorry, I should have made myself clearer - I meant in Lilypond
source code. :D
2 spaces it is..
Regards,
Ralph
Graham Percival wrote:
Ralph Little wrote:
I have looked at the GNU coding style recommendations, but could not
see a preference for the use of tab characters in code.
Do
Hi,
Sorry, some more coding questions. I've made quite a few mods to about
30 or so files and created a few of my own in my local git pull of
Lilypond. It occurs to me that I should start doing it properly now ;)
Should I get permission to create a new branch?
For new files, what is the situa
Ralph Little wrote:
I have looked at the GNU coding style recommendations, but could not see
a preference for the use of tab characters in code.
Do we use tabs in Lilypond code, or 2 spaces?
In the documentation, we use two spaces. That's mentioned in the README
for doc writers. For your o
Hi,
I have looked at the GNU coding style recommendations, but could not see
a preference for the use of tab characters in code.
Do we use tabs in Lilypond code, or 2 spaces?
Regards,
Ralph
___
lilypond-devel mailing list
lilypond-devel@gnu.org
htt
Le mercredi 26 septembre 2007 à 15:47 -0700, Graham Percival a écrit :
> John, sorry to add another thing to your plate, but could you
> investigate this?
Fixed in GDP. There was nothing to investigate, it was simply one of
those ugly ad-hoc constructs that need to be updated each time you split
Ok, formatting helpers, I've finalized things.
http://opihi.cs.uvic.ca/~gperciva/gdp/
Your source files are in:
doc-src/
Instructions are in:
helper-begin.txt
readme.txt
With more info about texinfo in the texinfo-*.txt files.
Try to have fun, and feel free to email me as often as possible --
Graham Percival writes:
> We currently use `makeinfo --html' to build the online documentation.
> Makeinfo is the normal way to create texinfo docs, but it lacks many
> useful features. Most importantly, it can't create HTML pages split
> into subsections; it only creates split output based on no
11 matches
Mail list logo
