>> [*] Currently, HTML output is handled by an ancient version of
>> `texi2html' that doesn't understand `@sortas' at all; I'm going
>> to add a dummy macro replacement to fix that. As a
>> consequence, the index of the HTML output will stay inferior to
>> both the info and PDF v
Le 14/03/2020 à 21:34, Torsten Hämmerle a écrit :
Apart from the fact that it's super-inelegant, you can use raw code within
your @ifhtml branch to get a real superscript even in HTML, as in:
… and fastidious in matter of typing,and don't forget to add a space
before the next word:
@ifnothtm
Jean-Charles Malahieude-2 wrote
> Furthermore, texi2html doesn't honor French typographic rules regarding
> ordinals: you can't use @sup{letter} like 1^er for 1st and I have to type
>
> @ifnothtml
> 256@sup{e}, 512@sup{e} et 1024@sup{e}
> @end ifnothtml
> @ifhtml
> 256e, 512e et 1024e
> @end ifht
Le 31/08/2019 à 21:11, Werner LEMBERG a écrit :
To have both `!' and `\!' (and similar `\foo' command and `foo'
property entries) in the index of the info and PDF version of the NR
it is necessary to tag corresponding entries with `@sortas'
directives[*]
https://sourceforge.net/p/testlilyiss
To have both `!' and `\!' (and similar `\foo' command and `foo'
property entries) in the index of the info and PDF version of the NR
it is necessary to tag corresponding entries with `@sortas'
directives[*]
https://sourceforge.net/p/testlilyissues/issues/5551/
https://sourceforge.net/p/testli
On 20 déc. 2012, at 08:36, Jan Nieuwenhuizen wrote:
> Ben Rudiak-Gould writes:
>
>> On Wed, Dec 19, 2012 at 1:43 AM, David Kastrup wrote:
>>> "m...@mikesolomon.org" writes:
...it seems like the
question is why we don't download the binaries directly and bundle
them with LilyPon
Ben Rudiak-Gould writes:
> On Wed, Dec 19, 2012 at 1:43 AM, David Kastrup wrote:
>> "m...@mikesolomon.org" writes:
>>> ...it seems like the
>>> question is why we don't download the binaries directly and bundle
>>> them with LilyPond.
>>
>> Because then all bets are off concerning comparable res
On Wed, Dec 19, 2012 at 1:43 AM, David Kastrup wrote:
> "m...@mikesolomon.org" writes:
>> ...it seems like the
>> question is why we don't download the binaries directly and bundle
>> them with LilyPond.
>
> Because then all bets are off concerning comparable results.
Not if you bundled the same
"m...@mikesolomon.org" writes:
> On 19 déc. 2012, at 10:18, David Kastrup wrote:
>
>> Ben Rudiak-Gould writes:
>>
>>> On Windows and OS X, I mean; on Linux and FreeBSD I think you could
>>> just demand installation of the appropriate packages.
>>>
>>> I don't understand what's so unusual abou
On 19 déc. 2012, at 10:18, David Kastrup wrote:
> Ben Rudiak-Gould writes:
>
>> On Windows and OS X, I mean; on Linux and FreeBSD I think you could
>> just demand installation of the appropriate packages.
>>
>> I don't understand what's so unusual about LilyPond's use of Python
>> that it req
Ben Rudiak-Gould writes:
> On Windows and OS X, I mean; on Linux and FreeBSD I think you could
> just demand installation of the appropriate packages.
>
> I don't understand what's so unusual about LilyPond's use of Python
> that it requires a custom build.
Nothing unusual. Neither is there any
On Windows and OS X, I mean; on Linux and FreeBSD I think you could
just demand installation of the appropriate packages.
I don't understand what's so unusual about LilyPond's use of Python
that it requires a custom build.
-- Ben
___
lilypond-devel mai
On Fri, Oct 22, 2010 at 10:21:58PM +0200, Matthias Kilian wrote:
> On Tue, Oct 19, 2010 at 12:07:29AM +0100, Graham Percival wrote:
> > Anything that's used to build the website (as opposed to the html
> > version of the docs) cannot rely on configure. This affects
> > scripts/build/ create-*.py w
On Tue, Oct 19, 2010 at 12:07:29AM +0100, Graham Percival wrote:
> >> python/ yes, since it's not something that people call manually.
> >> But stuff in scripts/build/ shouldn't have @PYTHON@, otherwise
> >> it'll bork if you call it manually.
> >
> > But are those scripts supposed to be used witho
On Tue, Oct 19, 2010 at 8:02 AM, John Mandereau
wrote:
> Il giorno lun, 18/10/2010 alle 09.20 -0700, Patrick McCarty ha scritto:
>> On Mon, Oct 18, 2010 at 9:17 AM, John Mandereau
>> wrote:
>> > I don't understand the issue; can't you just set PYTHON=python2 when
>> > calling configure, and in ca
Il giorno lun, 18/10/2010 alle 09.20 -0700, Patrick McCarty ha scritto:
> On Mon, Oct 18, 2010 at 9:17 AM, John Mandereau
> wrote:
> > I don't understand the issue; can't you just set PYTHON=python2 when
> > calling configure, and in case you need some scripts in auxiliar call
> > them by prependi
(unlurking, i didn't spend much time on lilypond recently)
On Mon, Oct 18, 2010 at 01:59:15AM +0100, Graham Percival wrote:
> > --) Two scripts still have "/usr/bin/python" lines
> > (python/auxiliar/manuals_definitions.py, and scripts/build/pytt.py).
> > Those should be changed to "@PYTHON@", rig
On Mon, Oct 18, 2010 at 11:57 PM, Matthias Kilian
wrote:
> (unlurking, i didn't spend much time on lilypond recently)
>
>> python/ yes, since it's not something that people call manually.
>> But stuff in scripts/build/ shouldn't have @PYTHON@, otherwise
>> it'll bork if you call it manually.
>
> B
On Mon, Oct 18, 2010 at 9:17 AM, John Mandereau
wrote:
> Il giorno lun, 18/10/2010 alle 09.02 -0700, Patrick McCarty ha scritto:
>> Yes, but unfortunately, LilyPond needs special sed treatment, since
>> many substitutions are made *after* configure time. I will need to
>> file a bug report...
>>
Il giorno lun, 18/10/2010 alle 09.02 -0700, Patrick McCarty ha scritto:
> Yes, but unfortunately, LilyPond needs special sed treatment, since
> many substitutions are made *after* configure time. I will need to
> file a bug report...
>
> Specifically, I am looking for a way to make life easier wh
On Sun, Oct 17, 2010 at 5:59 PM, Graham Percival
wrote:
> On Sun, Oct 17, 2010 at 05:38:20PM -0700, Patrick McCarty wrote:
>> --) Two scripts still have "/usr/bin/python" lines
>> (python/auxiliar/manuals_definitions.py, and scripts/build/pytt.py).
>> Those should be changed to "@PYTHON@", right?
On Sun, Oct 17, 2010 at 11:19 PM, Mark Polesky wrote:
> Patrick McCarty wrote:
>> Huh. I've been following the Arch Linux development list
>> for a while, but it didn't occur to me that they were
>> doing something radically different than the recommended
>> policy.
>>
>> This is the procedure th
t
>> know if Arch Linux is the first distribution upgrading to Python 3,
>> but this migration will be happening any day now.
>
> I'm not sure if you're subscribed to Arch mailing lists, but it seems
> to be causing a bloody mess amongst users and contributors. (I'm
On Mon, Oct 18, 2010 at 2:38 AM, Patrick McCarty wrote:
> Arch Linux will be migrating to Python 3 very soon, and I'm trying to
> figure out what to do with regard to LilyPond's build system. I don't
> know if Arch Linux is the first distribution upgrading to Python 3,
&
Patrick McCarty wrote:
> Huh. I've been following the Arch Linux development list
> for a while, but it didn't occur to me that they were
> doing something radically different than the recommended
> policy.
>
> This is the procedure they are following, and I think they
> are nearly finished with t
On Sun, Oct 17, 2010 at 8:30 PM, Benjamin Peterson wrote:
> Patrick McCarty gmail.com> writes:
>>
>> Arch Linux will be migrating to Python 3 very soon,
>
> What does this mean? "$ python" will give Python 3?
Yes.
> If so, that's no good. "python3" is supposed to be the name of the Python 3
> e
Benjamin Peterson python.org> writes:
> time in memoriam.
Hmm, that is a curious think-o. I meant "time immemorial" of course.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Patrick McCarty gmail.com> writes:
>
> Hello,
>
> Arch Linux will be migrating to Python 3 very soon,
What does this mean? "$ python" will give Python 3?
If so, that's no good. "python3" is supposed to be the name of the Python 3
executable for time in memoriam.
>
> The distribution-wide po
On Sun, Oct 17, 2010 at 05:38:20PM -0700, Patrick McCarty wrote:
> --) Two scripts still have "/usr/bin/python" lines
> (python/auxiliar/manuals_definitions.py, and scripts/build/pytt.py).
> Those should be changed to "@PYTHON@", right?
python/ yes, since it's not something that people call manual
Hello,
Arch Linux will be migrating to Python 3 very soon, and I'm trying to
figure out what to do with regard to LilyPond's build system. I don't
know if Arch Linux is the first distribution upgrading to Python 3,
but this migration will be happening any day now.
The distribut
> "LC" == Laura Conrad <[EMAIL PROTECTED]> writes:
ES> Attached is a patch that fixes the key signature problem.
LC> Thanks. It works.
Except that there's a piece of the patch to make chords work that
doesn't seem to have made it to 2.5. Patch attached
Index: ChangeLog
==
> "ES" == Erik Sandberg <[EMAIL PROTECTED]> writes:
ES> Attached is a patch that fixes the key signature problem.
Thanks. It works.
--
Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ )
(617) 661-8097 fax: (501) 641-5011
233 Broadway, Cambridge, MA 02139
___
Op do, 21-04-2005 te 01:45 +0200, schreef Erik Sandberg:
>
> Attached is a patch that fixes the key signature problem.
please commit.
--
Han-Wen Nienhuys - [EMAIL PROTECTED]
LilyPond Software Design - http://www.lilypond-design.com
___
lilypond-de
On Wednesday 20 April 2005 20.33, Laura Conrad wrote:
> > "JN" == Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
>
> JN> Laura Conrad writes:
> >> I use it. It isn't possible for me to switch to 2.4 (or 2.5 in its
> >> current state) because abc2ly is broken in a major way. (It
>
Sorry, it went to the bad list.
Bert
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
I've attached Joshua (zz85)'s lilymode.xml
My notes:
I think that when notes are colored then all notes in all languages should
be colored but nothing in lyrics. I think that this is impossible to
achieve, so I wouldn't colorize note names. However, having the rests and
skips be emphasized and th
[EMAIL PROTECTED] writes:
> > I also ran 1.5.58 on ancient-font.ly, and there are some things that
> > look pretty wierd to me. Specifically, I would guess that the
> > squiggles in the second staff of the third system should line up
> > differently with the stems.
> >
>
> I will have a look for
[EMAIL PROTECTED] writes:
>
> However, this approach requires major changes, and I guess that Han-Wen
> and others will vote for defering this to 1.7. So, I fear the only way to
> fix this is to add some preliminary hack, that switches between feta
> and parmesan font in a hard-coded way. Curre
On 27 May 2002, Laura Conrad wrote:
> ...
> Juergen> Unfortunately, this currently does not work for
> Juergen> TimeSignature for some internal reasons of lily (to be
> Juergen> more precise, alist font selection in scm/font.scm);
> Juergen> i.e. mensural time signatures currentl
> "Han-Wen" == Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
Han-Wen> And how is input/test/ancient-time.ly ?
It doesn't test very much, but it doesn't look like anything I've ever
seen in any of my facsimiles. Which doesn't mean it isn't a perfectly
good notation for 4/4 in some notatio
[EMAIL PROTECTED] writes:
> Juergen> i.e. mensural time signatures currently do not work at
> Juergen> all. This should be fixed until 1.6.
>
> It looks to me (from running 1.5.58 on time.ly) that this
> still doesn't work. This means that 1.5 is not feature complete from
> my point of
> "Han-Wen" == Han-Wen <[EMAIL PROTECTED]> writes:
Han-Wen> [EMAIL PROTECTED] writes:
>> As far as I know, there is no fixed date for 1.6.0, but it
>> should appear fairly soon.
Han-Wen> Personally, I think we only have to fix
Han-Wen> 1) the way kneed beams are typeset
42 matches
Mail list logo
