[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 1454 in lilypond: lilybuntu 3

From: Carl Sorensen
Subject: Re: Issue 1454 in lilypond: lilybuntu 3
Date: Wed, 26 Jan 2011 12:11:21 -0700

On 1/26/11 11:21 AM, "Keith OHara" <address@hidden> wrote:

>  <lilypond <at> googlecode.com> writes:
>> Comment #17 on issue 1454 by address@hidden: lilybuntu 3
>> http://code.google.com/p/lilypond/issues/detail?id=1454
>> There's already a ps line like this:
>>    application/postscript     ps ai eps epsi epsf eps2 eps3
>> Should there be a text/postscript line too? If so please post exact text
>> and I'll add it.
> I advise leaving postscript as-is.
> Python returns a single mime-type for a file, and I expect the existing
> postscript mime-type is depended on for something somewhere.
> LilyPond has only two, short, postscript files in the source tree, so losing
> the side-by-side diff should not be a big problem.  I tried to find a hanwenn
> patch with a failed .ps files, but the closest I found were -ps.scm files,
> which should be uploaded once they get a mime-type text/x-script.scheme
> Maybe changing ~/.mime.types would be more tidy, but I changed my global
> /etc/mime-types because I felt I was more likely to want to consider Scheme
> as text under another user name, than to post or email a lotus screencam file.
> -Keith

I haven't been able to find the commit I was referring to, so I withdraw my
suggestion for ps.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]