In message [EMAIL PROTECTED], Jonathan Henkelman
[EMAIL PROTECTED] writes
Mats Bengtsson mats.bengtsson at ee.kth.se writes:
You are mistaken. ASCII only defines character codes up to 127, see for
example http://www.asciitable.com/.
What your table shows is probably Latin1 (ISO 8859-1).
well it was an approximation (due to the previously mentionned lack
of vocabulary)
Do you mean that your English isn't sufficient to describe the things
correctly or that the issue itself is difficult to describe?
ISO 2022 (as well as SHIFT-JIS and other japaneses encoding of the
same type)
Ok ;-) Please do a replace-all for non-ascii to accented and special :-)
Bert
Go ahead:
http://lilypond.org/web/devel/participating/documentation-adding
- Graham
___
lilypond-user mailing list
lilypond-user@gnu.org
Hello,
I began with lilypond (2.11.12) last sunday (21.01.07) and I also had some
trouble with accents à la française and deutsche Umlaute.
On Linux :
(x)emacs was too difficult (for me) to configure utf-8 output,
[xemacs it is the editor whose short cuts I know the best]
but it is easy to
You could also try jEdit (http://www.jedit.org). It doesn't need
configuration, and has the LilyPondTool plugin (installable from Plugin
Manager)
There is also an emacs emulation package for jEdit:
http://www.clapper.org/software/jedit/ if you'd like to get the same
shortcuts.
Bert
On Linux, the easiest way to get UTF-8 output in xemacs is to simply
start it from a shell where you have specified the locale using
export LANG en_GB.utf-8
(or 'setenv LANG en_GB.utf-8' if you use (t)csh).
Of course, for you living in France, you may want
fr_FR.utf8 instead of en_GB.utf-8.
In message [EMAIL PROTECTED], Bertalan Fodor
[EMAIL PROTECTED] writes
Because most accented European characters can not be accessed within
ascii
My ascii table shows all French, Norwegian, Danish characters as well
as most spanish, and german (can't profess to be an expert there) see
Mats Bengtsson mats.bengtsson at ee.kth.se writes:
You are mistaken. ASCII only defines character codes up to 127, see for
example http://www.asciitable.com/.
What your table shows is probably Latin1 (ISO 8859-1).
/Mats
Mats: FYI I am using an ascii table in my little black pocket
On Fri, 26 Jan 2007 17:31:24 + (UTC), Jonathan Henkelman wrote:
On my machine I can write a single ascii text document (using the
full table)
that is in german, spanish, danish, norwegian, french, english.
Jonathan - the whole point of what he was just telling you is that what you're
David Gippner davidgippner at googlemail.com writes:
I've got problems with german umlauts in Lilypond 2.11.13-1. Wherever
there is one, I just get blanks.
Would something like:
\markup { \override #'(word-space . 0) \line {(f \char #252 r 1 oder 2
Manuale)} }
solve your problem.
BTW I
BTW I don't understand all this unicode business. Most european characters
can be accessed within ascii. Why should we have to go to unicode to get them?
Because most accented European characters can not be accessed within
ascii :-)
It greatly simplifies things, you know that everything
Jonathan Henkelman wrote:
BTW I don't understand all this unicode business. Most european characters
can be accessed within ascii. Why should we have to go to unicode to get them?
If you search the mailing list archives from the time before we introduced
unicode support, you will be
Mats Bengtsson mats.bengtsson at ee.kth.se writes:
If you search the mailing list archives from the time before we introduced
unicode support, you will be surprised how many questions there are related
to Russian or Hebrew or Mandarin or ...
/Mats
It wasn't intended to be a stupid
You are mistaken. ASCII only defines character codes up to 127, see for
example http://www.asciitable.com/.
What your table shows is probably Latin1 (ISO 8859-1).
/Mats
Quoting Jonathan Henkelman [EMAIL PROTECTED]:
Mats Bengtsson mats.bengtsson at ee.kth.se writes:
If you search the
Because most accented European characters can not be accessed within
ascii
My ascii table shows all French, Norwegian, Danish characters as well as most
spanish, and german (can't profess to be an expert there) see characters 191-
255 (xBF - xff). Are these accessable in a non-unicode
Well, since charsets issue is my hobby ... I can write a short explanation
(try to... my shortage of english vocabulary could be an issue)
After having defined a 128 character table (0 -127 on 8 bits, well one zero
+ 7bits) covering only the English characters and some signs, called the
ASCII
After having defined a 128 character table (0 -127 on 8 bits, well
one zero + 7bits) covering only the English characters and some
signs, called the ASCII table; has been defined many extended tables
using the 128 - 255 range to store some regional character. There
are around 10 extended
Actually, there are much more. If I'm not mistaken, the ISO 2022
registry has designed IDs to over 100 different 8bit character sets!
`assigned', of course.
Werner
___
lilypond-user mailing list
lilypond-user@gnu.org
well it was an approximation (due to the previously mentionned lack of
vocabulary)
ISO 2022 (as well as SHIFT-JIS and other japaneses encoding of the same
type) use indeed artificial 8bit characters.
The 0-127 range is always almost compatible with ASCII and there is 2
escaping character which
Bertalan Fodor wrote:
Because most accented European characters can not be accessed within
ascii
My ascii table shows all French, Norwegian, Danish characters as well
as most spanish, and german (can't profess to be an expert there) see
characters 191-
255 (xBF - xff). Are these
No, it is not. Is there another possibility than just encode the whole
thing as UTF-8?
Yours,
David Gippner
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
It's nothing difficult, just a matter of telling your text editor to
save the file
using UTF-8 encoding. If you cannot figure it out yourself, just send a
question
to the mailing list, telling what text editor you are using.
/Mats
David Gippner wrote:
No, it is not. Is there another
When using any convert option of WinEdt with UTF-8, the File cannot be
compiled and is corrupted.
Yours,
David
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
then you should go shopping for a better editor IMO
/S
On 1/24/07, David Gippner [EMAIL PROTECTED] wrote:
When using any convert option of WinEdt with UTF-8, the File cannot be
compiled and is corrupted.
Yours,
David
___
lilypond-user mailing list
/mailman/listinfo/lilypond-user
--
View this message in context:
http://www.nabble.com/problems-with-german-umlauts-tf3065236.html#a8571510
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
___
lilypond-user mailing list
Now a good version of LilyPondTool is released in the Plugin Manager of
jEdit, so you can safely install from there.
So just download jEdit 4.3pre9 (http://www.jedit.org - get the latest
development version), go to Plugin Manager Install LilyPondTool.
Check the Plugin options after install
Dear list,
I've got problems with german umlauts in Lilypond 2.11.13-1. Wherever
there is one, I just get blanks.
What can I do against that?
Yours sincerely
David Gippner
P.S.: If this is useful, I can provide a PDF of what I mean. Requests to
[EMAIL PROTECTED] please
Is your .ly file UTF-8 encoded?
Uwe Nagel
David Gippner wrote:
Dear list,
I've got problems with german umlauts in Lilypond 2.11.13-1. Wherever
there is one, I just get blanks.
What can I do against that?
Yours sincerely
David Gippner
P.S.: If this is useful, I can provide
28 matches
Mail list logo
