Re: Spacing for s4

2016-12-02 Thread PMA

On 12/02/2016 08:36 PM, PMA wrote:

On 12/02/2016 07:08 PM, Simon Albrecht wrote:

On 02.12.2016 23:39, PMA wrote:

Hi All!

I notice that the spacer command (e.g., "s4"), though
always accounting rightly for the TIME it commandeers
(here a quarter-note's worth), does not always insert
ACTUAL HORIZONTAL SPACE in the score.

How can I ensure that it'll do that too?  (I.e., what
score-setup spec would have disabled it?)




Since there is no visible output for s-rests, they don’t technically
_need_ to take up space. Some ideas:

– Adjust line breaks or use the paper variables system-count, page-count
 to achieve generally looser spacing.
– Try proportional notation.

Both should be easily found in the docs.

HTH, Simon



Hi Simon!

If they NEVER visibly output horizontal space
(the amount that rests instead would take up),



I wouldn't be wondering.  Anyway...

The score setup already calls for proportional
notation.  I'll pursue your other leads now.

Thanks,
Pete


Got it! --
\override Rest.transparent = ##t
Looks dory-hunky.
Thanks again!

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Spacing for s4

2016-12-02 Thread PMA

On 12/02/2016 07:08 PM, Simon Albrecht wrote:

On 02.12.2016 23:39, PMA wrote:

Hi All!

I notice that the spacer command (e.g., "s4"), though
always accounting rightly for the TIME it commandeers
(here a quarter-note's worth), does not always insert
ACTUAL HORIZONTAL SPACE in the score.

How can I ensure that it'll do that too?  (I.e., what
score-setup spec would have disabled it?)




Since there is no visible output for s-rests, they don’t technically
_need_ to take up space. Some ideas:

– Adjust line breaks or use the paper variables system-count, page-count
 to achieve generally looser spacing.
– Try proportional notation.

Both should be easily found in the docs.

HTH, Simon



Hi Simon!

If they NEVER visibly output horizontal space
(the amount that rests instead would take up),
I wouldn't be wondering.  Anyway...

The score setup already calls for proportional
notation.  I'll pursue your other leads now.

Thanks,
Pete

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Issues with combined parts and repeat percent

2016-12-02 Thread Garrett Fitzgerald
Mark, that's true, and it's possible I may end up going that way. I'm using
percents in the parts at the moment to help differentiate between repeated
measures and similar-looking changed measures. I'll also try the code from
http://lists.gnu.org/archive/html/lilypond-user/2016-11/msg01162.html to
see if I can unfold only the percents, leaving the voltas intact.

But I did want to address the disappearing rest and solo designation
specifically, because either of those might be considered bugs.

On Fri, Dec 2, 2016 at 6:44 PM, Mark Stephen Mrotek 
wrote:

> Garrett,
>
>
>
> When I replace “percent” with “unfold” everything appears as you want.
>
>
>
> Mark
>
>
>
> *From:* lilypond-user [mailto:lilypond-user-bounces+carsonmark=
> ca.rr@gnu.org] *On Behalf Of *Garrett Fitzgerald
> *Sent:* Friday, December 02, 2016 3:42 PM
> *To:* lilypond-user@gnu.org
> *Subject:* Issues with combined parts and repeat percent
>
>
>
> Evening, all. I'm trying to write individual horn parts for a march, but
> combine them in the score to save vertical space. However, I'm running into
> problems with percent repeats where Horn 2 plays the same notes longer than
> Horn 1 does.
>
>
>
> \version "2.18.2"
>
>
>
> hornOne = \relative c'' { r8 a a r a a | r8 g g r g g | }
>
> hornTwo = \relative c'' { \repeat percent 2 { r8 e, e r e e | } }
>
>
>
> \new Staff  {
>
>   \time 6/8
>
>   \partcombine \hornOne \hornTwo
>
> }
>
>
>
> \new Staff {
>
>   \time 6/8
>
>   << \hornOne \\
>
>  \hornTwo >>
>
> }
>
>
>
> [image: Inline image 1]
>
>
>
> In the first example, we lose the first rest altogether, and we get a
> marked "Solo" where there shouldn't be one. In both examples, the percent
> clashes with the upper part.
>
>
>
> It's likely I can deal with this using the unfold-percent-only code that
> was posted the other day, but it would be nice if the handling could be
> fixed to print the first rest and lose the solo notation. It would be
> wonderful if the percent could be automatically slipped downward to not
> clash, but I suspect that would be a bit harder to deal with. Thanks!
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: tag - midi

2016-12-02 Thread Darren Modra
Hi Bart, 
I think you'll find that if you don't save your work in freescobaldi before 
running it, it will put the PDF and midi files into a temporary folder. 

Cheers,
DM

--
This message may include free added typos, which you may use for your 
entertainment, courtesy of Apple autocorrect.

> On 3 Dec. 2016, at 07:23, bart deruyter - bart.deruy...@gmail.com 
>  wrote:
> 
> Sorry for this, but it does not work, I made another mistake, applied the tag 
> to the score too.. so my question does still stand.
> 
> 
> http://www.bartart3d.be/
> On Twitter
> On Identi.ca
> On Google+
> 
> 2016-12-02 21:51 GMT+01:00 bart deruyter :
>> Hi all,
>> disregard this mail.. it does work.. :-)
>> What made it work is : save the file first. Apparently frescobaldi 
>> re-renders unsaved work into pdf's, but not midi-files...
>> 
>> thx anyway.
>> 
>> Bart
>> 
>> http://www.bartart3d.be/
>> On Twitter
>> On Identi.ca
>> On Google+
>> 
>> 2016-12-02 21:44 GMT+01:00 bart deruyter :
>>> Hi all,
>>> 
>>> I did some experimentation with the \tag command. It is great for different 
>>> editions of printed music of course, but I tried it in the midi block 
>>> without luck.
>>> 
>>> I'm trying to create some music dictation exercises and want to separate 
>>> the midi file for the student in parts of each 2 bars, so I enclosed each 
>>> two bars in separate tags, like this: 
>>> 
>>> \tag #'A {c'2 | g |} \tag #'B {e'4 d | c2 }|
>>> 
>>> hoping it would work if I'd write something like this int he midi block: 
>>> 
>>> \midi { \keepWithTag #'A \altoVoice }
>>> 
>>> But no luck.. is it a bug, or simply not implemented (which is my guess)? 
>>> And is there a possible solution to get the wanted result?
>>> 
>>> thx,
>>> Bart
>>> 
>>> http://www.bartart3d.be/
>>> On Twitter
>>> On Identi.ca
>>> On Google+
>> 
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Spacing for s4

2016-12-02 Thread Simon Albrecht

On 02.12.2016 23:39, PMA wrote:

Hi All!

I notice that the spacer command (e.g., "s4"), though
always accounting rightly for the TIME it commandeers
(here a quarter-note's worth), does not always insert
ACTUAL HORIZONTAL SPACE in the score.

How can I ensure that it'll do that too?  (I.e., what
score-setup spec would have disabled it?)


Since there is no visible output for s-rests, they don’t technically 
_need_ to take up space. Some ideas:


– Adjust line breaks or use the paper variables system-count, page-count 
 to achieve generally looser spacing.

– Try proportional notation.

Both should be easily found in the docs.

HTH, Simon

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


RE: Issues with combined parts and repeat percent

2016-12-02 Thread Mark Stephen Mrotek
Garrett,

 

When I replace “percent” with “unfold” everything appears as you want.

 

Mark

 

From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] 
On Behalf Of Garrett Fitzgerald
Sent: Friday, December 02, 2016 3:42 PM
To: lilypond-user@gnu.org
Subject: Issues with combined parts and repeat percent

 

Evening, all. I'm trying to write individual horn parts for a march, but 
combine them in the score to save vertical space. However, I'm running into 
problems with percent repeats where Horn 2 plays the same notes longer than 
Horn 1 does.

 

\version "2.18.2"

 

hornOne = \relative c'' { r8 a a r a a | r8 g g r g g | }

hornTwo = \relative c'' { \repeat percent 2 { r8 e, e r e e | } }

 

\new Staff  { 

  \time 6/8

  \partcombine \hornOne \hornTwo

}

 

\new Staff {

  \time 6/8

  << \hornOne \\

 \hornTwo >>

}

 



 

In the first example, we lose the first rest altogether, and we get a marked 
"Solo" where there shouldn't be one. In both examples, the percent clashes with 
the upper part.

 

It's likely I can deal with this using the unfold-percent-only code that was 
posted the other day, but it would be nice if the handling could be fixed to 
print the first rest and lose the solo notation. It would be wonderful if the 
percent could be automatically slipped downward to not clash, but I suspect 
that would be a bit harder to deal with. Thanks!

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Issues with combined parts and repeat percent

2016-12-02 Thread Garrett Fitzgerald
Evening, all. I'm trying to write individual horn parts for a march, but
combine them in the score to save vertical space. However, I'm running into
problems with percent repeats where Horn 2 plays the same notes longer than
Horn 1 does.

\version "2.18.2"

hornOne = \relative c'' { r8 a a r a a | r8 g g r g g | }
hornTwo = \relative c'' { \repeat percent 2 { r8 e, e r e e | } }

\new Staff  {
  \time 6/8
  \partcombine \hornOne \hornTwo
}

\new Staff {
  \time 6/8
  << \hornOne \\
 \hornTwo >>
}

[image: Inline image 1]

In the first example, we lose the first rest altogether, and we get a
marked "Solo" where there shouldn't be one. In both examples, the percent
clashes with the upper part.

It's likely I can deal with this using the unfold-percent-only code that
was posted the other day, but it would be nice if the handling could be
fixed to print the first rest and lose the solo notation. It would be
wonderful if the percent could be automatically slipped downward to not
clash, but I suspect that would be a bit harder to deal with. Thanks!
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: tag - midi

2016-12-02 Thread Flaming Hakama by Elaine
Bart,

I did some experimentation with the \tag command. It is great for different
> editions of printed music of course, but I tried it in the midi block
> without luck.
>
> I'm trying to create some music dictation exercises and want to separate
> the midi file for the student in parts of each 2 bars, so I enclosed each
> two bars in separate tags, like this:
>
> \tag #'A {c'2 | g |} \tag #'B {e'4 d | c2 }|
>
> hoping it would work if I'd write something like this int he midi block:
>
> \midi { \keepWithTag #'A \altoVoice }
>
> But no luck.. is it a bug, or simply not implemented (which is my guess)?
> And is there a possible solution to get the wanted result?
>
> thx,
> Bart
>


Tags work in midi.

Could you please explain what you mean by "I' ... want to separate the midi
file for the student in parts of each 2 bars"?

Do you want one midi file with 2 voices, or 2 midi files each with one
voice?

If you could supply a more complete example to demonstrate your intent
(even if it isn't working), that might help.


Thanks,

David Elaine Alt
415 . 341 .4954   "*Confusion is
highly underrated*"
ela...@flaminghakama.com
self-immolation.info
skype: flaming_hakama
Producer ~ Composer ~ Instrumentalist
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Bad-Schemer syndrome

2016-12-02 Thread PMA

Oops.  Ignore the Subject line here, and the whole
lower message.  I forgot to erase them.  Mea culpa!

On 12/02/2016 05:39 PM, PMA wrote:

Hi All!

I notice that the spacer command (e.g., "s4"), though
always accounting rightly for the TIME it commandeers
(here a quarter-note's worth), does not always insert
ACTUAL HORIZONTAL SPACE in the score.

How can I ensure that it'll do that too?  (I.e., what
score-setup spec would have disabled it?)

Thanks,
Pete


On 11/03/2016 03:41 PM, PMA wrote:

Hi LP Gurus!

I have a score (see "Original" below) full of note events
like "gs 3", whose duration is MEANT always to be realized
as *one triplet half-note*.

Original = { gs 3  a 3g 2   a 3 }
Replaced = { \TR gs\TR a  g 2   \TR a }

So, I'm trying to concoct a function that, for any event
of original duration '3', will input the pitch name only
(reading from "Replaced") and embed that string in the
command "\tuplet 3/2  2".

TR =
#(define-music-function (parser location offset) (?)
   #{
  \tuplet 3/2 offset 2
   #})

But I'm stymied trying to whittle its Scheme, especially
re two questions: what variable type will work for the
the define-line ending "(?)" - "string" doesn't; and
what extra syntax might the "\tuplet..." command need to
handle the "offset" in its innards?

Hope this is clear.
Thanks in advance.
Pete



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Bad-Schemer syndrome

2016-12-02 Thread PMA

Hi All!

I notice that the spacer command (e.g., "s4"), though
always accounting rightly for the TIME it commandeers
(here a quarter-note's worth), does not always insert
ACTUAL HORIZONTAL SPACE in the score.

How can I ensure that it'll do that too?  (I.e., what
score-setup spec would have disabled it?)

Thanks,
Pete


On 11/03/2016 03:41 PM, PMA wrote:

Hi LP Gurus!

I have a score (see "Original" below) full of note events
like "gs 3", whose duration is MEANT always to be realized
as *one triplet half-note*.

Original = { gs 3  a 3g 2   a 3 }
Replaced = { \TR gs\TR a  g 2   \TR a }

So, I'm trying to concoct a function that, for any event
of original duration '3', will input the pitch name only
(reading from "Replaced") and embed that string in the
command "\tuplet 3/2  2".

TR =
#(define-music-function (parser location offset) (?)
   #{
  \tuplet 3/2 offset 2
   #})

But I'm stymied trying to whittle its Scheme, especially
re two questions: what variable type will work for the
the define-line ending "(?)" - "string" doesn't; and
what extra syntax might the "\tuplet..." command need to
handle the "offset" in its innards?

Hope this is clear.
Thanks in advance.
Pete



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: New LilyPond website

2016-12-02 Thread Graham Percival
I understand.  My apologies for being slow to get going; I only
re-joined LilyPond on Wednesday, in part because I suspected how
this was going to play out.  I plan to improve the process for new
contributors, but it will likely be 4-6 months before we have the
technical and social capability in place.

Cheers,
- Graham

On Fri, Dec 02, 2016 at 03:29:58PM -0500, John Roper wrote:
> This has turned into quite a bigger problem than I expected. I understand your
> reasons, but as a more modernistic designer and developer, I don't agree with
> most of your descisions no offense or problem. I just don't think I am the 
> best
> person for the job.
> 
> On Dec 2, 2016 2:19 PM, "Graham Percival"  wrote:
> 
> Hi John,
> 
> Thanks for your interest in helping LilyPond!  I wonder if you
> might be interested in having a dedicated mentor to help you
> navigate our development process.  We are more than 20 years old,
> and our process is aimed at allowing us to keep things rolling as
> smoothly as possible.
> 
> I've taken the liberty of uploading your latest (I think) css file
> and adding comments here:
> https://codereview.appspot.com/313170043/
> 
> As mentioned before, I strongly recommend that you begin by only
> making a small change; this CSS file includes a few changes at
> once, and that makes it harder to view how this file has changed
> over time.  Would you be willing to send a file which only changes
> the navbar, for example?
> 
> Cheers,
> - Graham
> 
> On Wed, Nov 30, 2016 at 09:38:32PM -0500, John Roper wrote:
> > And another fix for links.
> >
> 
> 

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: tag - midi

2016-12-02 Thread bart deruyter
Sorry for this, but it does not work, I made another mistake, applied the
tag to the score too.. so my question does still stand.


http://www.bartart3d.be/
On Twitter 
On Identi.ca 
On Google+ 

2016-12-02 21:51 GMT+01:00 bart deruyter :

> Hi all,
> disregard this mail.. it does work.. :-)
> What made it work is : save the file first. Apparently frescobaldi
> re-renders unsaved work into pdf's, but not midi-files...
>
> thx anyway.
>
> Bart
>
> http://www.bartart3d.be/
> On Twitter 
> On Identi.ca 
> On Google+ 
>
> 2016-12-02 21:44 GMT+01:00 bart deruyter :
>
>> Hi all,
>>
>> I did some experimentation with the \tag command. It is great for
>> different editions of printed music of course, but I tried it in the midi
>> block without luck.
>>
>> I'm trying to create some music dictation exercises and want to separate
>> the midi file for the student in parts of each 2 bars, so I enclosed each
>> two bars in separate tags, like this:
>>
>> \tag #'A {c'2 | g |} \tag #'B {e'4 d | c2 }|
>>
>> hoping it would work if I'd write something like this int he midi block:
>>
>> \midi { \keepWithTag #'A \altoVoice }
>>
>> But no luck.. is it a bug, or simply not implemented (which is my guess)?
>> And is there a possible solution to get the wanted result?
>>
>> thx,
>> Bart
>>
>> http://www.bartart3d.be/
>> On Twitter 
>> On Identi.ca 
>> On Google+ 
>>
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: tag - midi

2016-12-02 Thread bart deruyter
Hi all,
disregard this mail.. it does work.. :-)
What made it work is : save the file first. Apparently frescobaldi
re-renders unsaved work into pdf's, but not midi-files...

thx anyway.

Bart

http://www.bartart3d.be/
On Twitter 
On Identi.ca 
On Google+ 

2016-12-02 21:44 GMT+01:00 bart deruyter :

> Hi all,
>
> I did some experimentation with the \tag command. It is great for
> different editions of printed music of course, but I tried it in the midi
> block without luck.
>
> I'm trying to create some music dictation exercises and want to separate
> the midi file for the student in parts of each 2 bars, so I enclosed each
> two bars in separate tags, like this:
>
> \tag #'A {c'2 | g |} \tag #'B {e'4 d | c2 }|
>
> hoping it would work if I'd write something like this int he midi block:
>
> \midi { \keepWithTag #'A \altoVoice }
>
> But no luck.. is it a bug, or simply not implemented (which is my guess)?
> And is there a possible solution to get the wanted result?
>
> thx,
> Bart
>
> http://www.bartart3d.be/
> On Twitter 
> On Identi.ca 
> On Google+ 
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


tag - midi

2016-12-02 Thread bart deruyter
Hi all,

I did some experimentation with the \tag command. It is great for different
editions of printed music of course, but I tried it in the midi block
without luck.

I'm trying to create some music dictation exercises and want to separate
the midi file for the student in parts of each 2 bars, so I enclosed each
two bars in separate tags, like this:

\tag #'A {c'2 | g |} \tag #'B {e'4 d | c2 }|

hoping it would work if I'd write something like this int he midi block:

\midi { \keepWithTag #'A \altoVoice }

But no luck.. is it a bug, or simply not implemented (which is my guess)?
And is there a possible solution to get the wanted result?

thx,
Bart

http://www.bartart3d.be/
On Twitter 
On Identi.ca 
On Google+ 
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: New LilyPond website

2016-12-02 Thread John Roper
This has turned into quite a bigger problem than I expected. I understand
your reasons, but as a more modernistic designer and developer, I don't
agree with most of your descisions no offense or problem. I just don't
think I am the best person for the job.

On Dec 2, 2016 2:19 PM, "Graham Percival"  wrote:

> Hi John,
>
> Thanks for your interest in helping LilyPond!  I wonder if you
> might be interested in having a dedicated mentor to help you
> navigate our development process.  We are more than 20 years old,
> and our process is aimed at allowing us to keep things rolling as
> smoothly as possible.
>
> I've taken the liberty of uploading your latest (I think) css file
> and adding comments here:
> https://codereview.appspot.com/313170043/
>
> As mentioned before, I strongly recommend that you begin by only
> making a small change; this CSS file includes a few changes at
> once, and that makes it harder to view how this file has changed
> over time.  Would you be willing to send a file which only changes
> the navbar, for example?
>
> Cheers,
> - Graham
>
> On Wed, Nov 30, 2016 at 09:38:32PM -0500, John Roper wrote:
> > And another fix for links.
> >
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: New LilyPond website

2016-12-02 Thread Graham Percival
Hi John,

Thanks for your interest in helping LilyPond!  I wonder if you
might be interested in having a dedicated mentor to help you
navigate our development process.  We are more than 20 years old,
and our process is aimed at allowing us to keep things rolling as
smoothly as possible.

I've taken the liberty of uploading your latest (I think) css file
and adding comments here:
https://codereview.appspot.com/313170043/

As mentioned before, I strongly recommend that you begin by only
making a small change; this CSS file includes a few changes at
once, and that makes it harder to view how this file has changed
over time.  Would you be willing to send a file which only changes
the navbar, for example?

Cheers,
- Graham

On Wed, Nov 30, 2016 at 09:38:32PM -0500, John Roper wrote:
> And another fix for links.
> 


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: New LilyPond website

2016-12-02 Thread Jean-Charles Malahieude

Le 02/12/2016 à 02:10, Paul a écrit :

Hi Carl,

On 12/01/2016 12:44 PM, Carl Sorensen wrote:

One thing that is note mentioned in your quote is that texinfo separates
semantics from appearance.  It is this precise separation that allows one
to make big but consistent changes in the appearance of the website with
changes in the CSS.  I'm a firm believer in the principle of separating
semantics from presentation (and we do that with LilyPond, by the way,
which is one of its strengths IMO).


I totally agree about the value of separating semantics and appearance.
Using texinfo does enforce that in a strict way, although well-written
HTML also follows this principle.  HTML for content and CSS for style.
(E.g. one could just write directly the HTML that is generated from
texinfo.)  Maybe I'm missing something or maybe the strict enforcement
is the point?  At any rate, my intention is not to engage in argument or
advocate for anything.



I remember the "traffic" I had to do when the site was in full HTML 
(back in 2005) and we began with John Mandereau t translate it. 
Fortunately, I found a macro to use with emacs that "un-htmlized' for 
the time I typed the French text and "re-htmlized" before pushing any 
patch. It' hard to read at first sight:


Ces plaques taient encres et les reliefs 
crs par les poinons et

les dcoupes retenaient l'encre.




Upgrading to the latest version of texi2any[0] and/or using Haunt would
help, but those are non-trivial endeavors.  The current setup certainly
introduces friction for website work, especially for those who are used
to working directly with HTML.

I believe that we want to avoid working directly with HTML because of its
mixture of semantics and presentation.


I just wish that working with texinfo (for the website) was more
intuitive for contributors who know HTML but not texinfo.  For example,
an HTML element with an id and also a number of classes, all used for
styling it with CSS.  I don't know if you can generate that HTML element
(with both id and classes) from texinfo with our current setup.  If so I
haven't figured it out yet.  Maybe upgrading to the latest texi2any
would help.  Maybe someday I'll have the time to work on it.



I've already given it a try, but get stopped by some errors I don't know 
how to resolve (I've no knowledge about perl). Three patches are 
available for anybody willing to help me… I can compile the English 
version, except that I don't get the TOC sidebar.


Once lilypond-texi2html-init amended, I cannot deal with

Useless use of hash element in void context
Texi2HTML::Config::generate_ly_toc_entries() called too early to check 
prototype

Prototype mismatch: sub main::normalise_node: none vs ($)
Use of uninitialized value $Texi2HTML::Config::SPLIT in string eq

and tons of warnings, one for each @ref{} encountered, like

out-www/changes.texi:1174: warning: @vindex should only appear at the 
beginning of a line (possibly involving @rlearning)


comming from the rMANUAL macro definition.

What I do is:
1- uninstall texi2html.1.82

2- create a symlink
  cd ~/bin
  ln -s /usr/bin/texi2any texi2html

In a final stage, occurrences of texi2html might be replaced by texi2any.

3- try building the docs in my local branch dev/texi2any
  make doc LANGS=''

no way until now to build the translations!


4- erase my symlink and reinstall texi2html for usual work on 
translation branch.


Cheers,
Jean-Charles

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: New LilyPond website

2016-12-02 Thread Paul

On 12/01/2016 02:40 PM, John Roper wrote:


My css file is a proposed inclusion into the website.


Hi John, I tried your CSS file (just using Firefox developer tools) and 
made a couple of screenshots (uploaded to that same directory mentioned 
earlier in this thread), but the "Cabin" font is not being loaded and 
another font is substituted.


Can you give us a screenshot with the right font shown?  (I use the 
'Nimbus screenshot' add-on for Firefox, which works well for capturing 
the whole page.)


Also, I'm seeing gaps in the secondary navigation menu -- shown in the 
screenshot for the "Introduction" page.


-Paul

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: New LilyPond website

2016-12-02 Thread Carl Sorensen


On 12/1/16 6:10 PM, "Paul"  wrote:

>Hi Carl,
>
>On 12/01/2016 12:44 PM, Carl Sorensen wrote:
>> One thing that is note mentioned in your quote is that texinfo separates
>> semantics from appearance.  It is this precise separation that allows
>>one
>> to make big but consistent changes in the appearance of the website with
>> changes in the CSS.  I'm a firm believer in the principle of separating
>> semantics from presentation (and we do that with LilyPond, by the way,
>> which is one of its strengths IMO).
>
>I totally agree about the value of separating semantics and appearance.
>Using texinfo does enforce that in a strict way, although well-written
>HTML also follows this principle.  HTML for content and CSS for style.
>(E.g. one could just write directly the HTML that is generated from
>texinfo.)  Maybe I'm missing something or maybe the strict enforcement
>is the point?  At any rate, my intention is not to engage in argument or
>advocate for anything.

Yes.  In my opinion, strict enforcement is the point.

It is possible to separate semantics from presentation in Microsoft Word
using styles, but in any writing project involving multiple authors, my
experience is that the separation is not maintained.  Somebody will mimic
formatting without using the style, and that's the end of the semantic
marking.

I agree that HTML *can* provide the separation, but it doesn't require it.
 And that's why I agree with the decision not to have the website created
directly in HTML.

Thanks,

Carl


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


Re: Distance between Lyrics and Dynamics context

2016-12-02 Thread Kieren MacMillan
Hi Urs,

> For the record: I was somehow fixed on moving the whole context
> (which I still want to know about).

Yes.

> But in my actual case which is a two-system music example it turned out
> to move things around by simply overriding their extra-offset …

As I indicated, that’s what I often end up doing. I even have syntactic sugar 
for the “multi-item” cases (e.g., lyrics, which include LyricText, LyricHyphen, 
LyricExtender, etc.).

Glad it worked out!
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user