On 11/11/2011 06:09 PM, Peekay Ex wrote:
Hello,
2011/11/12 Paul Scott:
..
The text representation of f sharp in germany and austria is fis. When
you want to describe a note in text, that's how you do it. In english, we
write "f sharp";
In a book probably. In an email F#.
Based on that answ
On 12 Nov 2011, at 17:44, Carl Sorensen wrote:
>>> It's not exactly a bug, more like a feature request :)
>>>
>>> I have noticed that convert-ly removes the \encoding and converts
>>> everything to UTF-8.
>>
>> I hacked together some code, scm/define-note-names.scm, with a language
>> "unicode"
On 11/12/11 6:29 AM, "Hans Aberg" wrote:
>On 11 Nov 2011, at 23:04, Pavel Roskin wrote:
>
>> It's not exactly a bug, more like a feature request :)
>>
>> I have noticed that convert-ly removes the \encoding and converts
>> everything to UTF-8.
>
>I hacked together some code, scm/define-note-na
- Original Message -
> From: David Kastrup
> To: Hans Aberg
> Cc: bug-lilypond@gnu.org
> Sent: Saturday, November 12, 2011 4:19 AM
> Subject: Re: Using Unicode symbols for accidentals
>
> Hans Aberg writes:
>
>> On 12 Nov 2011,
On 12 Nov 2011, at 15:31, Pavel Roskin wrote:
>> I hacked together some code, scm/define-note-names.scm, with a language
>> "unicode" added.
>
> I wish I looked at that file before starting this thread. Even though
> Unicode symbols are international, the note names are not. The English B is
Quoting Hans Aberg :
I hacked together some code, scm/define-note-names.scm, with a
language "unicode" added.
I wish I looked at that file before starting this thread. Even though
Unicode symbols are international, the note names are not. The
English B is not the same as the German B.
On 12 Nov 2011, at 10:19, David Kastrup wrote:
>>> Unfortunately, it is just programmers and not musicians who have a
>>> reasonable chance of being able to figure out how to produce ♯ on a
>>> computer keyboard.
>>
>> One approach is having an editor which can provide replacements for
>> input t
Hans Aberg writes:
> On 12 Nov 2011, at 05:38, David Kastrup wrote:
>
>> Unfortunately, it is just programmers and not musicians who have a
>> reasonable chance of being able to figure out how to produce ♯ on a
>> computer keyboard.
>
> One approach is having an editor which can provide replaceme
On 12 Nov 2011, at 05:38, David Kastrup wrote:
> Unfortunately, it is just programmers and not musicians who have a
> reasonable chance of being able to figure out how to produce ♯ on a
> computer keyboard.
One approach is having an editor which can provide replacements for input text.
So one ju
On 11 Nov 2011, at 23:04, Pavel Roskin wrote:
> It's not exactly a bug, more like a feature request :)
>
> I have noticed that convert-ly removes the \encoding and converts
> everything to UTF-8. So I hoped I could use some Unicode symbols to
> make the sources more compact and readable:
>
> \v
Pavel Roskin writes:
> On Fri, 11 Nov 2011 23:21:42 +0100 (CET)
> Werner LEMBERG wrote:
>
>>
>> > f♯ is shorter and more readable than fsharp, let alone fis.
>>
>> In Germany and Austria, f♯ is *never* used. Only fis and nothing
>> else.
>
> I'm sure the signs for accidentals are used in the
Quoting Carl Sorensen :
I think the point Werner was making is that accidentals are used on a
staff. The graphical representation of f sharp is a notehead on the f
line or space (depending on which staff, and which octave) with a sharp
symbol either before the note (an accidental) or in the key
Hello,
2011/11/12 Paul Scott :
..
>> The text representation of f sharp in germany and austria is fis. When
>> you want to describe a note in text, that's how you do it. In english, we
>> write "f sharp";
>
> In a book probably. In an email F#.
Based on that answer, how do _you_ write 'b flat'
On 11/11/2011 04:31 PM, Carl Sorensen wrote:
>
> On 11/11/11 4:49 PM, "Pavel Roskin" wrote:
>
>> On Fri, 11 Nov 2011 23:21:42 +0100 (CET)
>> Werner LEMBERG wrote:
>>
f♯ is shorter and more readable than fsharp, let alone fis.
>>> In Germany and Austria, f♯ is *never* used. Only fis and noth
On 11/11/11 4:49 PM, "Pavel Roskin" wrote:
>On Fri, 11 Nov 2011 23:21:42 +0100 (CET)
>Werner LEMBERG wrote:
>
>>
>> > f♯ is shorter and more readable than fsharp, let alone fis.
>>
>> In Germany and Austria, f♯ is *never* used. Only fis and nothing
>> else.
>
>I'm sure the signs for acciden
>> > f♯ is shorter and more readable than fsharp, let alone fis.
>>
>> In Germany and Austria, f♯ is *never* used. Only fis and nothing
>> else.
>
> [...]
>
> Using those signs in a text file would be a new thing. Maybe
> accidentals should be written before the notes, as in the score
> (♯f), bu
On Fri, 11 Nov 2011 23:21:42 +0100 (CET)
Werner LEMBERG wrote:
>
> > f♯ is shorter and more readable than fsharp, let alone fis.
>
> In Germany and Austria, f♯ is *never* used. Only fis and nothing
> else.
I'm sure the signs for accidentals are used in the musical scores, even
in Germany :)
> f♯ is shorter and more readable than fsharp, let alone fis.
In Germany and Austria, f♯ is *never* used. Only fis and nothing
else.
Werner
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Hello!
It's not exactly a bug, more like a feature request :)
I have noticed that convert-ly removes the \encoding and converts
everything to UTF-8. So I hoped I could use some Unicode symbols to
make the sources more compact and readable:
\version "2.14.2"
\score {
\new Staff { d♭8 f♯ }
\l
19 matches
Mail list logo
