headers
Dan Eble | 1 Jan 2009 15:56
Picon

wrong number of arguments to font-file-as-ps-string

2.12.1 on PowerPC on Mac OS X 10.5.6...

(process:31063): Pango-WARNING **: Error loading GDEF table 28333

(process:31063): Pango-WARNING **: Error loading GSUB table 28333

(process:31063): Pango-WARNING **: Error loading GPOS table 28333
/Applications/LilyPond.app/Contents/Resources/share/lilypond/current/
scm/framework-ps.scm:293:28: In procedure font-file-as-ps-string in 
expression (font-file-as-ps-string name full-name):
/Applications/LilyPond.app/Contents/Resources/share/lilypond/current/
scm/framework-ps.scm:293:28: Wrong number of arguments to #<procedure
 font-file-as-ps-string (name file-name font-index)>
Permalink | Reply | 3 comments |
headers
codesite-noreply | 2 Jan 2009 00:08
Picon
Favicon

Issue 719 in lilypond: New Version statement not accepted

Status: New
Owner: ----

New issue 719 by sineneg1: New Version statement not accepted
http://code.google.com/p/lilypond/issues/detail?id=719


We recommend that users report bugs to
http://post.gmane.org/post.php?group=gmane.comp.gnu.lilypond.bugs


Please DO NOT add issues directly to this tracker unless
you are certain that they correspond to our preferred
format.


What steps will reproduce the problem?

(Please attach or insert a small .ly fragment to duplicate)

What is the expected output?

I expect my music to be compatible and readable. In stead I receive an  
error saying that ≤  syntax error, unexpected DIGIT
\version "
           2.12.0"  % necessary for upgrading to future LilyPond versions.  ≥


What do you see instead?

No changes are made to the document.
(Continue reading)

Permalink | Reply | 1 comment |
headers
codesite-noreply | 2 Jan 2009 00:37
Picon
Favicon

Issue 719 in lilypond: New Version statement not accepted

Updates:
	Status: Invalid

Comment #1 on issue 719 by reinhold.kainhofer: New Version statement not  
accepted
http://code.google.com/p/lilypond/issues/detail?id=719

The problem is not the version statement, but rather that you started a  
string with " a
few lines before, but never closed that string...

\new Staff {
\set Staff.instrumentName = "Markup \center-column {
Bassoon 1
}

As you can see, that instrumentName string is never closed. I suspect that  
you intended
to write \markup\center-column{...} (i.e. no double quotes)? (Or  
simply "Bassoon 1",
which is not centered, though).

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
Permalink | Reply | 0 comments |
headers
codesite-noreply | 2 Jan 2009 01:01
Picon
Favicon

Issue 719 in lilypond: New Version statement not accepted


Comment #2 on issue 719 by gpermus: New Version statement not accepted
http://code.google.com/p/lilypond/issues/detail?id=719

sineneg1,

You quoted a message telling you NOT to add material directly to the  
tracker, but did
so anyway.  How could we make this warning more clear?

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
Permalink | Reply | 2 comments |
headers
Villum Sejersen | 2 Jan 2009 09:43
Picon

Re: Strange parsing of define output-suffix "AA"

Happy New Year

Today I tried both the 32 bit and the 64-bit versions of version 
2.12.1-1, but still producing the unwanted filename.

Could the answer lie in the language settings on this debian-box? 
(excerpts of set and env):

MM_CHARSET=ISO-8859-1
SHELL=/bin/bash
LANG=da_DK
LESSCHARSET=latin1
LANGUAGE=da_DK:da:en_GB:en

BASH_VERSINFO=([0]="3" [1]="1" [2]="17" [3]="1" [4]="release" 
[5]="x86_64-pc-linux-gnu")
BASH_VERSION='3.1.17(1)-release'
HOSTTYPE=x86_64
MACHTYPE=x86_64-pc-linux-gnu
SHELLOPTS=braceexpand:emacs:hashall:histexpand:history:interactive-comments:monitor

Is the cause perhaps a variation of what happens to the text output if 
you accidentally forget to save a .ly file as UTF-8?

Does /bin/bash and/or the parser/lexer read the UTF-8 formatted 
output-suffix as ISO-8859-1, thus getting confused?

--

-- 
med venlig hilsen  Villum Sejersen
Nørregade  1 A
(Continue reading)

Permalink | Reply | 0 comments |
headers
sdfgsdhdshd | 2 Jan 2009 14:13
Picon
Favicon

Re: Issue 719 in lilypond: New Version statement not accepted


codesite-noreply wrote:
> 
> I expect my music to be compatible and readable. In stead I receive an  
> error saying that ≤  syntax error, unexpected DIGIT
> \version "
>            2.12.0"  % necessary for upgrading to future LilyPond versions. 
> ≥
> 
> 

In your code you wrote
"Markup

instead of
\markup

i don't know your keyboard, maybe you pressed Shift by mistake?

--

-- 
View this message in context: http://www.nabble.com/Issue-719-in-lilypond%3A-New-Version-statement-not-accepted-tp21245845p21251245.html
Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com.
Permalink | Reply | 0 comments |
headers
Carl D. Sorensen | 2 Jan 2009 18:55

Re: Issue 719 in lilypond: New Version statement not accepted


On 1/1/09 5:01 PM, "codesite-noreply <at> google.com"
<codesite-noreply <at> google.com> wrote:

> 
> 
> Comment #2 on issue 719 by gpermus: New Version statement not accepted
> http://code.google.com/p/lilypond/issues/detail?id=719
> 
> sineneg1,
> 
> You quoted a message telling you NOT to add material directly to the
> tracker, but did
> so anyway.  How could we make this warning more clear?

I'd suggest that the warning be changed to

Please DO NOT add issues directly to this tracker unless
you have received permission to do so.  Instead, send an
email to bug-lilypond <at> gnu.org with the following information:

IMO, the warning as currently stated gives me permission to add an issue if
I'm careful about the format, but that's not the way we want to have it,
IIRC.

Carl
Permalink | Reply | 1 comment |
headers
Mats Bengtsson | 2 Jan 2009 23:46
Picon
Picon
Favicon

Re: text missing

James E. Bailey wrote:
> Apparently lilypond is a little too smart with delayed ties.
Is this perhaps even worth a bug report?

   /Mats
> You have a ~ in the first measure which isn't completed until the 
> third measure. Get rid of it, and you should have what you want.
> Am 02.01.2009 um 21:12 schrieb Nikolay Kirov:
>
>> Hi!
>>
>> Can anybody answer me, why there is no text corresponding to the 
>> second bar ?
>>
>> (text is in Bulgarian; folk music)
>>
>> Nikolay Kirov
>>
>>
>> %{
>> TD_171_1_06
>> %}
>>
>> \version "2.11.65"
>>
>> \score {
>> \relative c'' {
>>  \tempo 4 = 192
>>   \time 7/16
>>  g8~( g16[ f)] f16.~\prall( e) | d4~( d16.[ c)] |  f8\noBeam g16([
(Continue reading)

Permalink | Reply | 3 comments |
headers
James E. Bailey | 3 Jan 2009 00:26

Re: text missing


Am 02.01.2009 um 23:46 schrieb Mats Bengtsson:

> James E. Bailey wrote:
>> Apparently lilypond is a little too smart with delayed ties.
> Is this perhaps even worth a bug report?

The one thing I've learned with lilypond is that I don't know what a  
bug is.
Permalink | Reply | 0 comments |
headers
Graham Percival | 3 Jan 2009 02:53
Picon
Favicon

Re: Issue 719 in lilypond: New Version statement not accepted

On Fri, Jan 02, 2009 at 10:55:15AM -0700, Carl D. Sorensen wrote:
> 
> I'd suggest that the warning be changed to
> 
> Please DO NOT add issues directly to this tracker unless
> you have received permission to do so.  Instead, send an
> email to bug-lilypond <at> gnu.org with the following information:

Thanks, done.

> IMO, the warning as currently stated gives me permission to add an issue if
> I'm careful about the format, but that's not the way we want to have it,
> IIRC.

Huh, you're right.  And now that I think about it, most invalid
bug reports *did* carefully answer the questions in the order
provided.

Cheers,
- Graham
Permalink | Reply | 0 comments |

Gmane