2009/8/13 Patrick Schmidt :
> From my point of view it would be more intuitive if it were possible to set
> glissandi in chords just the way ties are set, e.g.: \glissando a>
> resulting in one glissando mark for each voice in chords. But this is
> probably hard to implement ...
Yes, we already ha
2009/8/13 Patrick Schmidt :
> quite handy (and logical) if it were possible to apply << {} \\ {} >> to
> tabVoice if it's in a tabStaff context (especially when the piece doesn't
> contain an awful lot of polyphonic bars).
Note to myself:
Marc has a patch about this on
http://lists.gnu.org/archive
Updates:
Status: Started
Cc: pnorcks
Comment #1 on issue 832 by v.villenave: Wrong UTF-8 encoded filenames
passed to gs
http://code.google.com/p/lilypond/issues/detail?id=832
Please also read the discussion on
http://lists.gnu.org/archive/html/bug-lilypond/2009-08/msg00137.htm
On 2009-08-20, Reinhold Kainhofer wrote:
> Am Donnerstag, 20. August 2009 11:47:52 schrieb Reinhold Kainhofer:
> > Am Donnerstag, 20. August 2009 11:37:55 schrieb Patrick McCarty:
> > > On 2009-08-20, Reinhold Kainhofer wrote:
> > > > To me this seems like guile is not able to properly handle wide
Am Donnerstag, 20. August 2009 11:47:52 schrieb Reinhold Kainhofer:
> Am Donnerstag, 20. August 2009 11:37:55 schrieb Patrick McCarty:
> > On 2009-08-20, Reinhold Kainhofer wrote:
> > > To me this seems like guile is not able to properly handle wide UTF-8
> > > characters properly and messes up the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Donnerstag, 20. August 2009 11:37:55 schrieb Patrick McCarty:
> On 2009-08-20, Reinhold Kainhofer wrote:
> > Am Donnerstag, 20. August 2009 10:48:09 schrieb Reinhold Kainhofer:
> > > Yes, I think that's the case here. It seems that gs is well able
>
On 2009-08-20, Reinhold Kainhofer wrote:
> Am Donnerstag, 20. August 2009 10:48:09 schrieb Reinhold Kainhofer:
> > Yes, I think that's the case here. It seems that gs is well able
> > to handle 16- bit unicode characters, but it needs the correct
> > file name.
> >
> > A little more playing around
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Donnerstag, 20. August 2009 10:48:09 schrieb Reinhold Kainhofer:
> Yes, I think that's the case here. It seems that gs is well able to handle
> 16- bit unicode characters, but it needs the correct file name.
>
> A little more playing around shows th
Status: Accepted
Owner: v.villenave
CC: reinhold.kainhofer
Labels: Type-Defect Usability gs
New issue 832 by v.villenave: Wrong UTF-8 encoded filenames passed to gs
http://code.google.com/p/lilypond/issues/detail?id=832
Although Ghostscript is able to handle special characters in filenames,
Lily
2009/8/20 Reinhold Kainhofer :
> So, basically, lilypond messes up the proper UTF-8 encoding of the external
> utility calls.
OK, that is now in the tracker as
http://code.google.com/p/lilypond/issues/detail?id=832
Regards,
Valentin
___
bug-lilypond m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Donnerstag, 20. August 2009 03:41:57 schrieb ian_hulin:
> I've just been investigating this a bit more and have finally managed to
> install ghostscript 8.70 on my system.
I have ghostscript 8.64 installed on my kubuntu system.
> If I compile a .l
11 matches
Mail list logo