Re: Setting font families for entire document in LilyPond version 2.18.2.

[Simon Albrecht]

Hi Mirosław,

On 20.12.2016 20:25, Mirosław Doroszewski wrote:

Setting font families for entire document is not possible in template
added to document with \include.


Yes, it is. Just use something like this in your \include file:

\paper {
  fonts = #(make-pango-font-tree
"Linux Libertine O"
"Ubuntu"
"Ubuntu Mono"
(/ (* staff-height pt) 2.5))
}

and be sure to include the file _after_ using #(set-global-staff-size #!!#).

Best, Simon

PS. Maybe ask on the lilypond-u...@gnu.org list first, if you’re not 
completely sure the feature is missing.


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

Re: Setting font families for entire document in LilyPond version 2.18.2.

[Alexander Kobel]

Hi Miroslaw,

not sure if I understand correctly what you mean.
It is perfectly possible to write a file CustomTemplate.ly with a 
content like that:


\paper  {
  #(define fonts
(make-pango-font-tree "Times New Roman"
  "Nimbus Sans,Nimbus Sans L"
  "Luxi Mono"
  (/ staff-height pt 20)))
}

and include it with the command you mentioned. For reference on the 
command used herein, see


http://lilypond.org/doc/v2.18/Documentation/notation/fonts#entire-document-fonts

If you need further adjustments, e.g. for the font size of the lyrics, 
you can also have global layout blocks in that file:


\layout {
  \context {
\Lyrics
\override LyricText.font-size = #0
  }
}

or similar overrides.


HTH,
Alexander


On 2016-12-20 20:25, Mirosław Doroszewski wrote:

Setting font families for entire document in LilyPond version 2.18.2.

Setting font families for entire document is not possible in template
added to document with \include. If is many documents in a book, there
is necessary to set font families in each document separately. But
this solution not always working. And if there is 500 documents in a
song book?
So, please, make solution: setting font families be possible by adding
single template with \include to document.
For instance:

\version "2.18.2"
\include "CustomTemplate.ly"
{...}

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



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

Setting font families for entire document in LilyPond version 2.18.2.

[Mirosław Doroszewski]

Setting font families for entire document in LilyPond version 2.18.2.

Setting font families for entire document is not possible in template
added to document with \include. If is many documents in a book, there
is necessary to set font families in each document separately. But
this solution not always working. And if there is 500 documents in a
song book?
So, please, make solution: setting font families be possible by adding
single template with \include to document.
For instance:

\version "2.18.2"
\include "CustomTemplate.ly"
{...}

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

Re: ‘\note’ DURATION (string) DIR (number)

[Simon Albrecht]

Hi Sylvius,

there is no bug involved. If you don’t understand something, it’s better 
to ask on the user list. Help will be gladly given.



On 20.12.2016 20:10, Sylvius Pold wrote:

Hi,

I seem to have some problems understanding the manuals.  In 
lilypond-notation (instrument specific markup) I read:



‘\note’ DURATION (string) DIR (number)

 This produces a note with a stem pointing in DIR direction, with
 the DURATION for the note head type and augmentation dots. For
 example, ‘\note #"4." #-0.75’ creates a dotted quarter note, with a
 shortened down stem.


This description says that the \note markup command takes _two_ 
_mandatory_ arguments.
The first is for the duration, which, as shown in the doc string 
example, can include one or more augmentation dots.
The second is for the stem direction _and_ length. #UP evaluates to 1, 
#DOWN evaluates to -1. Positive numbers make the stem go up, negative 
numbers make it go down, the absolute amount is a factor for the length. 
So using #0.2 gives you a very short up stem, #-10 gives you a very long 
down stem.






It's not clear to me how to achieve e.g. a dotted quarter note, with a 
shortened *up* stem. This does not work:


1. \markup { \note #"4" #UP #0.75 }
2. \markup { \note #"4" #UP #-0.75 }


The function doesn’t take a third argument.



It's also not clear to me why it is necessary to define a DIR 
direction in order to get a whole note.


First way to answer: Technically, whole notes do have stems, only they 
are invisible. Though that’s really just an internal detail.
Second way: The function just isn’t implemented such as to have an 
optional argument, so you always need to give both arguments, even for 
whole notes.


HTH, Simon

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

Re: Putting marks over bar lines in LilyPond version 2.18.2.

[Simon Albrecht]

Hello again,

this is a question for the -user list just the same.

Best, Simon


On 20.12.2016 20:49, Mirosław Doroszewski wrote:

\version "2.18.2"
\include "deutsch.ly"

%{
Putting marks over bar lines in LilyPond version 2.18.2.

1. When mark is put over bar line, it is placed centrally by default.
But sometimes there is need to place the mark left or right aligned,
i.e. in repeats.
2. I tried do so according to manuals (\left-align, right-align), but
without effect.
3. It happens that the mark is printed at the begining of next line,
instead of the end of the same line.
4. Solution by manual: treat mark as rehearsal mark and use overriding for it:
a) if the mark is not at the end of line:
\once \override Score.RehearsalMark.self-alignment-X = #RIGHT
\mark \markup { \italic \small "3x" }
b) if the mark is at the end of line:
\once \override Score.RehearsalMark.break-visibility = 
#end-of-line-visible
\once \override Score.RehearsalMark.self-alignment-X = #RIGHT
\mark \markup { \italic \small "3x" }
5. If the mark is not at the end of line, it is not possible to use
universal way by putting settings as described above in b), because
then is nothing printed. So it is necessary to manually put first or
second solution, as described above in a) and b).
6. At the end of score there is no need to put second solution, as above in b).
%}

mark-not-at-the-end-of-line = {
\once \override Score.RehearsalMark.self-alignment-X = #RIGHT
\mark \markup { \italic \small "3x" }
}
mark-at-the-end-of-line = {
\once \override Score.RehearsalMark.break-visibility = 
#end-of-line-visible
\once \override Score.RehearsalMark.self-alignment-X = #RIGHT
\mark \markup { \italic \small "3x" }
}

\paper {
#(set-paper-size "a6" 'portrait)
indent = 0\mm
ragged-bottom = ##t
ragged-last-bottom = ##t
top-margin = 1 \cm
bottom-margin = 1 \cm
line-width = 8.8 \cm
tagline = ##f
print-all-headers = ##t
markup-system-spacing = #'((basic-distance . 5) (padding . 1)
(stretchability . 30))
}
#(set-global-staff-size 12.0)

\score {
\layout {
\context { \Staff \remove "Time_signature_engraver" }
ragged-last = ##t
}
\relative c' {
\transpose e d' {
\key e \minor
\time 1/8   
\autoBeamOff
\cadenzaOn  
\bar ".|:" e8 e dis4 e \bar "'" e8 e dis4 e \bar "'"
g8 g g4 fis8 e fis4 fis \bar "'"
fis8 fis g e dis!4 e \noBreak \bar ":|.|:"
\mark-not-at-the-end-of-line
\bar ":|.|:" e8 fis g g g g g fis e fis4 fis \bar "'"
fis g8[ fis] e dis!4 e \bar ":|.|:"
\mark-not-at-the-end-of-line
\bar ":|.|:" e8[ fis] g g g g g fis e fis4 fis \bar "'"
fis8 fis g[ fis] e dis!4 e \bar ":|."
\mark-at-the-end-of-line
\cadenzaOff
}
}
\addlyrics {
Świę- ty Bo- że, Świę- ty moc- ny,
Świę- ty, a nie- śmier- tel- ny,
zmi- łuj się nad na- mi!
Od po- wie- trza, gło- du, o- gnia i woj- ny
wy- baw nas, Pa- nie!
Od na- głej, a nie- spo- dzia- nej, śmier- ci
za- cho- waj nas, Pa- nie!
}
}


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



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

Re: Scaling global staff size without scaling Lyrics in LilyPond version 2.18.2.

[Simon Albrecht]

Hi Mirosław,

I will not answer this e-mail, because it definitely has no place on the 
bug list. Please refer to the user list at .



On 20.12.2016 20:48, Mirosław Doroszewski wrote:

4. So, please, make solution and describe it in manual.


Also, please note that LilyPond is entirely run by volunteers in their 
spare time. It won’t help to demand a solution, as if you had paid and 
received a guarantee for anything. You might have read in the license 
that LilyPond comes with absolutely no warranty whatsoever, so moderate 
your tone.


Best, Simon

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

Re: Moving of lyrics in LilyPond version 2.18.2.

[Simon Albrecht]

Same here.


On 20.12.2016 20:51, Mirosław Doroszewski wrote:

\version "2.18.2"
\include "deutsch.ly"

%{
Moving of lyrics in LilyPond version 2.18.2.

1. In song books sometimes after each verse of lyrics is put asterisk
(*). Using it implies that syllable is moved left too much.
2. I have not find solution for it in manuals.
3. My solution not perfect: putting three (sometimes two or four)
linked underscores befor syllable not separately, i.e.: "syl-
___lable_*". If done, placment of syllables and staff objects are
printed correctly.
4. With this solution lyric text is moved only right: putting
underscores after syllable is without effect.
5. Moving same lyric text is without correct effect.
6. So, please, describe or make solution: moving lyrics with staff objects.
%}

t = { \bar "" }
lewe = { \once \override LyricText.self-alignment-X = #LEFT }

globalne = { \key es \major \time 4/4 \autoBeamOff }

głos = \relative c'' {
\repeat volta 2 {
g2 g b b es, es g g
c2 f, b es,4( as) g2( f4.) es8 es2. r4
}
\cadenzaOn
es8 \t g \t b\breve \t as8 \t b \t c4 \t b
b\breve \t c8 \t as \t b[ \t as] \t g4
\bar "|."
\cadenzaOff
}
tekst = \lyricmode {
\set stanza = #"Ref.: "
Chry- stus Wo- dzem, Chry- stus Kró- ___lem,_*
Chry- stus, Chry- stus Wład- cą ___nam!_*
\set stanza = #" 1. "
Bo- ga \lewe naszego_chwalcie wszyst- kie zie- ___mie,_*
\lewe Daj_Mu_cześć_winną_całe ludz- kie ple- mię.
}
\score {
\new Staff <<
\new Voice = "1-melodiiI" { \transpose es c { \globalne \głos } 
}
\new Lyrics \lyricsto "1-melodiiI" { \tekst }
>>
}


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



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

‘\note’ DURATION (string) DIR (number)

[Sylvius Pold]

Hi,

I seem to have some problems understanding the manuals.  In 
lilypond-notation (instrument specific markup) I read:



‘\note’ DURATION (string) DIR (number)

 This produces a note with a stem pointing in DIR direction, with
 the DURATION for the note head type and augmentation dots.  For
 example, ‘\note #"4." #-0.75’ creates a dotted quarter note, with a
 shortened down stem.


It's not clear to me how to achieve e.g. a dotted quarter note, with a 
shortened *up* stem. This does not work:


1. \markup { \note #"4" #UP #0.75 }
2. \markup { \note #"4" #UP #-0.75 }

It's also not clear to me why it is necessary to define a DIR direction 
in order to get a whole note. Example:


\markup { \note #"1" #UP }

Strange syntax but compiles fine with LP 2.19.50.

I'd expect to be able to write

\markup { \note #"1" }

in order to get a whole note but this results in the following error:

syntax error, unexpected STRING, expecting LOOKUP_IDENTIFIER or 
SCM_FUNCTION or SCM_IDENTIFIER or SCM_TOKEN


Is this a (tiny) bug or just an inconvenience and is it possible to 
alter the lengths of up stems in the context of the \note command?


Thanks for your help!

Sylvius


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

Putting marks over bar lines in LilyPond version 2.18.2.

[Mirosław Doroszewski]

\version "2.18.2"
\include "deutsch.ly"

%{
Putting marks over bar lines in LilyPond version 2.18.2.

1. When mark is put over bar line, it is placed centrally by default.
But sometimes there is need to place the mark left or right aligned,
i.e. in repeats.
2. I tried do so according to manuals (\left-align, right-align), but
without effect.
3. It happens that the mark is printed at the begining of next line,
instead of the end of the same line.
4. Solution by manual: treat mark as rehearsal mark and use overriding for it:
a) if the mark is not at the end of line:
\once \override Score.RehearsalMark.self-alignment-X = #RIGHT
\mark \markup { \italic \small "3x" }
b) if the mark is at the end of line:
\once \override Score.RehearsalMark.break-visibility = 
#end-of-line-visible
\once \override Score.RehearsalMark.self-alignment-X = #RIGHT
\mark \markup { \italic \small "3x" }
5. If the mark is not at the end of line, it is not possible to use
universal way by putting settings as described above in b), because
then is nothing printed. So it is necessary to manually put first or
second solution, as described above in a) and b).
6. At the end of score there is no need to put second solution, as above in b).
%}

mark-not-at-the-end-of-line = {
\once \override Score.RehearsalMark.self-alignment-X = #RIGHT
\mark \markup { \italic \small "3x" }
}
mark-at-the-end-of-line = {
\once \override Score.RehearsalMark.break-visibility = 
#end-of-line-visible
\once \override Score.RehearsalMark.self-alignment-X = #RIGHT
\mark \markup { \italic \small "3x" }
}

\paper {
#(set-paper-size "a6" 'portrait)
indent = 0\mm
ragged-bottom = ##t
ragged-last-bottom = ##t
top-margin = 1 \cm
bottom-margin = 1 \cm
line-width = 8.8 \cm
tagline = ##f
print-all-headers = ##t
markup-system-spacing = #'((basic-distance . 5) (padding . 1)
(stretchability . 30))
}
#(set-global-staff-size 12.0)

\score {
\layout {
\context { \Staff \remove "Time_signature_engraver" }
ragged-last = ##t
}
\relative c' {
\transpose e d' {
\key e \minor
\time 1/8   
\autoBeamOff
\cadenzaOn  
\bar ".|:" e8 e dis4 e \bar "'" e8 e dis4 e \bar "'"
g8 g g4 fis8 e fis4 fis \bar "'"
fis8 fis g e dis!4 e \noBreak \bar ":|.|:"
\mark-not-at-the-end-of-line
\bar ":|.|:" e8 fis g g g g g fis e fis4 fis \bar "'"
fis g8[ fis] e dis!4 e \bar ":|.|:"
\mark-not-at-the-end-of-line
\bar ":|.|:" e8[ fis] g g g g g fis e fis4 fis \bar "'"
fis8 fis g[ fis] e dis!4 e \bar ":|."
\mark-at-the-end-of-line
\cadenzaOff
}
}
\addlyrics {
Świę- ty Bo- że, Świę- ty moc- ny,
Świę- ty, a nie- śmier- tel- ny,
zmi- łuj się nad na- mi!
Od po- wie- trza, gło- du, o- gnia i woj- ny
wy- baw nas, Pa- nie!
Od na- głej, a nie- spo- dzia- nej, śmier- ci
za- cho- waj nas, Pa- nie!
}
}


Putting marks over bar lines.pdf
Description: Adobe PDF document
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Staff breaking in unmetered music in LilyPond version 2.18.2.

[Simon Albrecht]

On 21.12.2016 00:02, Thomas Morley wrote:

\set Score.defaultBarType = #""
\set Score.barAlways = ##t


Wow, I wasn’t aware of the barAlways property! That’s exactly what’s needed.

Best, Simon

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

Setting font families for entire document.

[Mirosław Doroszewski]

Setting font families for entire document in LilyPond version 2.18.2.

Setting font families for entire document is not possible in template
added to document with \include. If is many documents in a book, there
is necessary to set font families in each document separately. But
this solution not always working. And if there is 500 documents in a
song book?
So, please, make solution: setting font families be possible by adding
single template with \include to document.
For instance:

\version "2.18.2"
\include "CustomTemplate.ly"
{...}

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

Re: Staff breaking in unmetered music in LilyPond version 2.18.2.

[Simon Albrecht]

On 20.12.2016 20:45, Mirosław Doroszewski wrote:

In unmetered music staff breaking is not calculated automatically


I think that is a valid feature request, and I couldn’t find any tracker 
issue.


Maybe there should be a third option for 
Score.NonMusicalPaperColumn.line-break-permission, with the current 
default renamed to #'bar-lines-only and #'allow instead allowing breaks 
even without barlines? Surely that’s a performance issue?


I’d like for some more opinions on this one, then I’ll open an issue.

Best, Simon

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

Re: Staff breaking in unmetered music in LilyPond version 2.18.2.

[Thomas Morley]

2016-12-20 23:17 GMT+01:00 Simon Albrecht :
> On 20.12.2016 20:45, Mirosław Doroszewski wrote:
>>
>> In unmetered music staff breaking is not calculated automatically
>
>
> I think that is a valid feature request, and I couldn’t find any tracker
> issue.
>
> Maybe there should be a third option for
> Score.NonMusicalPaperColumn.line-break-permission, with the current default
> renamed to #'bar-lines-only and #'allow instead allowing breaks even without
> barlines? Surely that’s a performance issue?
>
> I’d like for some more opinions on this one, then I’ll open an issue.



One could already do (pseudo-code):

\cadenzaOn
\set Score.defaultBarType = #""
\set Score.barAlways = ##t

...

\set Score.defaultBarType = #"|"
\set Score.barAlways = ##f
\cadenzaOff

Do we really need more?

Cheers,
  Harm

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

Slurs and ties — most difficult to make: developer has to think about them before his work.

[Mirosław Doroszewski]

Slurs and ties — most difficult to make: developer has to think about
them before his work.

1. I have noticed in main web site of LilyPond beautiful image of music.
2. The image shows correct breaking of ties between (two) systems.
3. But when I was rewriting songs, it happend that breaking ties or
slurs between (two) systems made ugly print, not like in professional
music notation books shopped.
4. Why the image from main web site of LilyPond has correct shaping
ties after breaking in two systems and my work accordingly to manuals
creats ugly shaping of slurs and ties?
5. When developer thinks to make project of music notation software,
he has to decide, what interface will be using by future software. He
has to be sure that his future software will do with beautiful slurs
and ties.
6. I think that LilyPond is not "music notation for everyone" but only
for specialists. Per analogiam: there are softwares with graphical
interface like office packages for any customers; and there are some
software with none graphical interface like TeX, for specialists
(there is a LyX, a graphical interface for TeX, Latex, AMSTeX etc.).
7. So, please, answer the question in point 4. as above.

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

Lyric hyphens in LilyPond version 2.18.2.

[Mirosław Doroszewski]

Lyric hyphens in LilyPond version 2.18.2.

1. Making hyphens accordingly to manuals is not correct, because when
syllables inside words are calculated to be print without hyphens,
there is too much space created between them. Confer correct
"calculation" of text editors which place not any space between
letters in a single word. LilyPond creates ugly space between
syllables in a single word, when it calculates to not engrave a
hyphen.
2. My solution is perfect but not universal: using simple hyphenation
like in gregorian chant, i.e. "Ky- ri- e, e- le- i- son." (not "Ky --
ri -- e, e -- le -- i -- son.", as described in manuals). That way
there are no tiny or teeny or smallest spaces between syllables of a
single word what is ugly.
3. Besides, calculation of putting shorter hyphens makes not beautiful
sight. Maybe it does not disturb meny people. But I have not seen in
any song book putting shorter hyphens: or hyphens are printed full, or
hyphens are not put.

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

Re: Lyric hyphens in LilyPond version 2.18.2.

[Thomas Morley]

Hi Miroslow,

2016-12-21 0:28 GMT+01:00 Mirosław Doroszewski :
> Lyric hyphens in LilyPond version 2.18.2.
>
> 1. Making hyphens accordingly to manuals is not correct, because when
> syllables inside words are calculated to be print without hyphens,
> there is too much space created between them. Confer correct
> "calculation" of text editors which place not any space between
> letters in a single word. LilyPond creates ugly space between
> syllables in a single word, when it calculates to not engrave a
> hyphen.

A known issue:
https://sourceforge.net/p/testlilyissues/issues/2458/

-Harm

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

Re: Slurs and ties — most difficult to make: developer has to think about them before his work.

[Simon Albrecht]

Hi Miroslaw,

again: this is not a very good bug report as described on our website: 
. Please be specific, report one 
well-defined problem and not a major rant of seven items. As Thomas 
already said – code examples are quasi-mandatory, except for very 
special cases.


On 21.12.2016 00:24, Mirosław Doroszewski wrote:

4. Why the image from main web site of LilyPond has correct shaping
ties after breaking in two systems and my work accordingly to manuals
creats ugly shaping of slurs and ties?


LilyPond’s automatic formatting is very good, but it doesn’t work 
equally well in every possible case. For that, tweaks are available, 
like \shape. (You’ll find that in the manuals.)



5. When developer thinks to make project of music notation software,
he has to decide, what interface will be using by future software.


I can assure you that a lot of thought has gone into the development of 
LilyPond… and some really good thought, as well, I daresay.



  He
has to be sure that his future software will do with beautiful slurs
and ties.


I don’t think LilyPond needs to hide from its competition, even in that 
respect.



6. I think that LilyPond is not "music notation for everyone" but only
for specialists.


Well, if you don’t like it, nobody forces you to keep with it…

Best, Simon

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

Re: Slurs and ties — most difficult to make: developer has to think about them before his work.

[Thomas Morley]

2016-12-21 0:24 GMT+01:00 Mirosław Doroszewski :
> Slurs and ties — most difficult to make: developer has to think about
> them before his work.
>
> 1. I have noticed in main web site of LilyPond beautiful image of music.
> 2. The image shows correct breaking of ties between (two) systems.
> 3. But when I was rewriting songs, it happend that breaking ties or
> slurs between (two) systems made ugly print, not like in professional
> music notation books shopped.
> 4. Why the image from main web site of LilyPond has correct shaping
> ties after breaking in two systems and my work accordingly to manuals
> creats ugly shaping of slurs and ties?
> 5. When developer thinks to make project of music notation software,
> he has to decide, what interface will be using by future software. He
> has to be sure that his future software will do with beautiful slurs
> and ties.
> 6. I think that LilyPond is not "music notation for everyone" but only
> for specialists. Per analogiam: there are softwares with graphical
> interface like office packages for any customers; and there are some
> software with none graphical interface like TeX, for specialists
> (there is a LyX, a graphical interface for TeX, Latex, AMSTeX etc.).
> 7. So, please, answer the question in point 4. as above.



Nobody can tell without looking at your code.
Anyway, there is indeed enough room to improve. Patches are welcome.

-Harm

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

Nous ne serons jamais assez nombreux pour signer cette pétition

[daviau ewen]

Salut à Tous ,

J'ai pas l'habitude d'embêter mes amis, mais la ça craint ! Saviez vous que
l'état veut filer 11 vaccins à tous les nourissons (contre 3 actuellement).


Nous ne serons jamais assez nombreux pour signer cette pétition, faites
suivre à toutes vos relations,  il s’agit de l’avenir de tous les enfants
de France


Voici le lien à faire circuler :
*http://petitions.ipsn.eu/mobilisation-vaccins-enfants/index.php?src=pv*



Sensibilisez chaque personne que vous rencontrez !
Nous ne laisserons pas l’État nous arracher ainsi nos libertés les plus
fondamentales.

Pour avoir une vraie force de frappe, la vague de soulèvement doit tout
emporter. La force viendra de la diffusion de ces informations au plus
grand nombre, et si nous sommes plusieurs centaines de milliers, voire plus
d’un million à signer alors je vous garantis que les choses iront dans le
bon sens.

Nous n’avons plus le temps de tergiverser, il faut agir !
Faîtes un maximum de bruit !

Pour rappel, voici le lien à faire circuler par tous moyens :

*http://petitions.ipsn.eu/mobilisation-vaccins-enfants/index.php?src=pv*


Partagez, partagez, partagez...

Si chaque parent signait la pétition, nous serions déjà plusieurs millions !
Nous atteindrions très rapidement un nombre sans précédent de signataires
et pourrions ainsi avoir une influence historique !

Toutes les familles de France vous remercient de votre action !

Bravo et merci pour votre soutien !


L’équipe de l’IPSN



Ewen d'Aviau
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond