Re: UTF-8 characters in filenames with Lilypond 2.23

On Wed, 2022-05-25 at 13:24 -0600, David F. wrote: > > > On May 25, 2022, at 11:21 AM, Jonas Hahnfeld wrote: > > > > On Sat, 2022-05-21 at 15:20 -0600, David F. wrote: > > > System: Intel-based macOS > > > > > > I make extensive use of

Re: UTF-8 characters in filenames with Lilypond 2.23

On Sat 21 May 2022 at 23:36:26 (-0600), David F. wrote: > > On May 21, 2022, at 5:01 PM, Jean Abou Samra wrote: > > Le 21/05/2022 à 23:20, David F. a écrit : > >> System: Intel-based macOS > >> > >> I make extensive use of UTF-8 characters in the filenames

Re: UTF-8 characters in filenames with Lilypond 2.23

> On May 25, 2022, at 11:21 AM, Jonas Hahnfeld wrote: > > On Sat, 2022-05-21 at 15:20 -0600, David F. wrote: >> System: Intel-based macOS >> >> I make extensive use of UTF-8 characters in the filenames of my Lilypond >> files. This works in Lilypond up th

Re: UTF-8 characters in filenames with Lilypond 2.23

Am 25.05.22 um 19:21 schrieb Jonas Hahnfeld via LilyPond user discussion: On Sat, 2022-05-21 at 15:20 -0600, David F. wrote: System: Intel-based macOS I make extensive use of UTF-8 characters in the filenames of my Lilypond files. This works in Lilypond up through version 2.22. But Lilypond

Re: UTF-8 characters in filenames with Lilypond 2.23

On Sat, 2022-05-21 at 15:20 -0600, David F. wrote: > System: Intel-based macOS > > I make extensive use of UTF-8 characters in the filenames of my Lilypond > files. This works in Lilypond up through version 2.22. But Lilypond 2.23 > cannot handle UTF-8 characters in filenames

Re: UTF-8 characters in filenames with Lilypond 2.23

On Tue 24 May 2022 at 20:59:18 (-0700), Curt McDowell wrote: > I get that same error if running under Docker, if LANG is set to > en_US.UTF-8, but where en_US.UTF-8 does not exist in the output of > "locale -a". > >./out/bin/lilypond scheme-sandbox /(Lilypond 2.23.0, Guile 2.2.7, >Ubuntu 2

Re: UTF-8 characters in filenames with Lilypond 2.23

I get that same error if running under Docker, if LANG is set to en_US.UTF-8, but where en_US.UTF-8 does not exist in the output of "locale -a". ./out/bin/lilypond scheme-sandbox /(Lilypond 2.23.0, Guile 2.2.7, Ubuntu 20.04)/ (open-input-file "tést.ly") In procedure open-file: No su

Re: UTF-8 characters in filenames with Lilypond 2.23

Thomas Morley writes: > Am So., 22. Mai 2022 um 07:36 Uhr schrieb David F. : >> >> >> >> > On May 21, 2022, at 5:01 PM, Jean Abou Samra wrote: >> > >> > Le 21/05/2022 à 23:20, David F. a écrit : >> >> System: Intel-based macOS

Re: UTF-8 characters in filenames with Lilypond 2.23

Am So., 22. Mai 2022 um 07:36 Uhr schrieb David F. : > > > > > On May 21, 2022, at 5:01 PM, Jean Abou Samra wrote: > > > > Le 21/05/2022 à 23:20, David F. a écrit : > >> System: Intel-based macOS > >> > >> I make extensive use of UTF-8 charact

Re: UTF-8 characters in filenames with Lilypond 2.23

> On May 21, 2022, at 5:01 PM, Jean Abou Samra wrote: > > Le 21/05/2022 à 23:20, David F. a écrit : >> System: Intel-based macOS >> >> I make extensive use of UTF-8 characters in the filenames of my Lilypond >> files. This works in Lilypond up through

Re: UTF-8 characters in filenames with Lilypond 2.23

Le 21/05/2022 à 23:20, David F. a écrit : System: Intel-based macOS I make extensive use of UTF-8 characters in the filenames of my Lilypond files. This works in Lilypond up through version 2.22. But Lilypond 2.23 cannot handle UTF-8 characters in filenames. Filename: tést.ly \version

UTF-8 characters in filenames with Lilypond 2.23

System: Intel-based macOS I make extensive use of UTF-8 characters in the filenames of my Lilypond files. This works in Lilypond up through version 2.22. But Lilypond 2.23 cannot handle UTF-8 characters in filenames. Filename: tést.ly \version "2.22" { c' } Under v

Re: UTF-8 unicode use in \markup

you can also do > ##xa7 as well as simply 167 (which is the decimal numeric value for hex A7). > > Thus char basically takes a number and gives us that unicode character. > > Cheers, > Valentin > > Am Montag, 29. November 2021, 01:27:37 CET schrieb ming tsang: >> Hi

Re: UTF-8 unicode use in \markup

Am Montag, 29. November 2021, 01:27:37 CET schrieb ming tsang: > Hi Valentin Petzel, > Thank you for your reply. I found a > UTF-8 encoding table and Unicode characters > https://www.utf8-chartable.de/unicode-utf8-table.pl?utf8=0x > Now I can look up the U+00a7 and then use \markup

Re: UTF-8 unicode use in \markup

Hi Valentin Petzel, Thank you for your reply. I found a UTF-8 encoding table and Unicode characters https://www.utf8-chartable.de/unicode-utf8-table.pl?utf8=0x Now I can look up the U+00a7 and then use \markup { \char ##x00a7 ) to display it. for \char I cannot use unicode U+00a7. I was hoping

Re: UTF-8 unicode use in \markup

Hello Ming, I do not understand your exact problem. If you want to have € in markup you can either directly put € in the markup, or use \char ##20ac. Valentin Am Sonntag, 28. November 2021, 22:42:47 CET schrieb ming tsang: > Hi lilyponder, > > I would like to use \markup to display € using U

UTF-8 unicode use in \markup

Hi lilyponder, I would like to use \markup to display € using U+20AC. I can use \markup { \char ##x2197 } to display / print / output to pdf. ##x2197 is [image: image.png] Your help is appreciated. Shalom, yMing -- ming (lyndon) tsang

Re: utf-8 file name in lilypond

lypond2.19.82 it produces desired file infomation. >> Then I rename the file as test_中文.ly (UTF-8 Chinese characters) and execute >> and the following error occurs: >> Starting lilypond-windows.exe 2.19.82 [test_中文.ly]... >> warning: cannot find file: `C:/Users/yming/Document

Re: utf-8 file name in lilypond

On Wed 30 Jan 2019 at 16:42:22 (+), MING TSANG wrote: > http://lsr.di.unimi.it/LSR/Snippet?id=197 > > I copy the above snippet and name it test_file-name_info.ly and run with > fracobaldi3.01 + lilypond2.19.82 it produces desired file infomation. > Then I rename the file as te

utf-8 file name in lilypond

http://lsr.di.unimi.it/LSR/Snippet?id=197 I copy the above snippet and name it test_file-name_info.ly and run with fracobaldi3.01 + lilypond2.19.82 it produces desired file infomation. Then I rename the file as test_中文.ly (UTF-8 Chinese characters) and execute and the following error occurs

Re: UTF-8-aware backwards string searching in Guile, or: fixing centered lyrics ignoring punctuation

Gosh, once again I'm flabbergasted about the expertise and helpfulness of the folks on this list. Thanks a ton! As far as I can tell, your corrected version works like a charm (and even fixed a minor misalignment of the "à" syllable that I did not spot earlier). And IIUC, the only drawback o

Re: UTF-8-aware backwards string searching in Guile, or: fixing centered lyrics ignoring punctuation

On 2018-10-30 9:23 pm, Aaron Hill wrote: Here's a quick-n-dirty patch to address the issue. \version "2.19.82" \include "center-lyrics-ignoring-punctuation.ily" { d'4 4 4 } \addlyrics { Å Ɓ† «Ḉ…» } Agh, I goofed. I forgot the logic is that you want to trim the "space" characters fr

Re: UTF-8-aware backwards string searching in Guile, or: fixing centered lyrics ignoring punctuation

On 2018-10-30 4:56 pm, Aaron Hill wrote: On 2018-10-30 10:01 am, Alexander Kobel wrote: Does anyone have a hint how to approach this one? (Or is the answer just: be patient and hope for Guile v2?) The only hint here is to replace the built-in functions with ones which understand UTF8 encoding

Re: UTF-8-aware backwards string searching in Guile, or: fixing centered lyrics ignoring punctuation

On 2018-10-30 10:01 am, Alexander Kobel wrote: This makes me wonder whether the problem is in the backwards string-search in string-skip-right or in the substring routine used in the make-center-on-word-callback; the only reason I can imagine why this pops up is that some blind-to-Unicode slicing

UTF-8-aware backwards string searching in Guile, or: fixing centered lyrics ignoring punctuation

19.82" \include "center-lyrics-ignoring-punctuation.ily" { d4 } \addlyrics { à } GNU LilyPond 2.19.82 Processing `test.ly' Parsing... Interpreting music... Preprocessing graphical objects... (process:2528): Pango-WARNING **: 17:49:34.874: Invalid UTF-8 string passed to pango_layou

Re: UTF-8 in MIDI Lyrics

7 { @ U T F 8 } > >> And lobby AMEI/MMA to adopt an official UTF8 position. > > > > Could be good, but why just not capitalize on the BOM and just use > > utf8. ... > OK, the UTF-8 BOM is 0x EF BB BF > But given that the MIDI file is not a "text file" but a

Re: UTF-8 in MIDI Lyrics

; I stand corrected. >> But if we are going to use a "private standard", we might as well >> imitate the "official" standard and insert something like >> FF 05 07 { @ U T F 8 } >> And lobby AMEI/MMA to adopt an official UTF8 position. > > Could b

Re: UTF-8 in MIDI Lyrics

sorry, last mail wrong from header. Joe Austen: > > Am 24.02.2017 um 02:15 schrieb Joseph Austin: > >> This raises another question. I'm working with MIDI files, > >> and it's not clear how to encode UTF-8 text in MIDI. > >> There must be some convent

Re: UTF-8 in MIDI Lyrics

Joe Austen: > > Am 24.02.2017 um 02:15 schrieb Joseph Austin: > >> This raises another question. I'm working with MIDI files, > >> and it's not clear how to encode UTF-8 text in MIDI. > >> There must be some convention, but I haven't f

Re: UTF-8 in MIDI Lyrics

> On Feb 24, 2017, at 7:47 AM, lilypond-user-requ...@gnu.org wrote: > > Am 24.02.2017 um 02:15 schrieb Joseph Austin: >> This raises another question. I'm working with MIDI files, >> and it's not clear how to encode UTF-8 text in MIDI. >> There must be so

Re: UTF-8 in MIDI lyrics

Simon Albrecht: > Am 24.02.2017 um 02:15 schrieb Joseph Austin: > > This raises another question. I'm working with MIDI files, > > and it's not clear how to encode UTF-8 text in MIDI. > > There must be some convention, but I haven't found an official

Re: UTF-8 in MIDI lyrics

Am 24.02.2017 um 02:15 schrieb Joseph Austin: This raises another question. I'm working with MIDI files, and it's not clear how to encode UTF-8 text in MIDI. There must be some convention, but I haven't found an official RP for it. Personally, I have no idea. Does Lily not do

Re: UTF-8 chars in included filenames on Windows 10 revisited

Reposted as Saturday night's email failed to post here and Sunday morning's did. (Their Bccs have both crossed the Atlantic in a timely manner.) On Sat 14 Jan 2017 at 11:17:17 (+0100), Michael Gerdau wrote: > it appears UTF-8 character in filenames on Windows seems to be a > rec

Re: UTF-8 chars in included filenames on Windows 10 revisited

On Sat 14 Jan 2017 at 11:17:17 (+0100), Michael Gerdau wrote: > it appears UTF-8 character in filenames on Windows seems to be a > recurring theme. I didn't know windows used UTF-8 at all in file names. I was under the impression that it used UTF-16, though I've no idea which en

UTF-8 chars in included filenames on Windows 10 revisited

Hi list, it appears UTF-8 character in filenames on Windows seems to be a recurring theme. The attached files placed into the same directory won't properly run on Windows 10 or Windows 7 while there is no problem at all on Linux (I suspect no problem on OSX either but haven't checked)

Re: (lilypond-windows.exe:6216): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()

On Thu 17 Nov 2016 at 02:56:01 (+), MING TSANG wrote: > Andrew,I have been using Chinese character in lyrics and there is no problem. > I only giving me trouble when I try to use Chinese characters in file > name.PDF , frecobaldi, lilypond all display Chinese characters without > problem.  I

Re: (lilypond-windows.exe:6216): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()

On Thu 17 Nov 2016 at 01:35:36 (+), MING TSANG wrote: > David, > Thank you for the link.I forgot about it. it seems not the same to me. > previous:(lilypond.exe:1892): > Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() > warning: no glyph for character U+

Re: (lilypond-windows.exe:6216): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()

  From: Andrew Bernard To: 'MING TSANG' ; lilypond-user@gnu.org Sent: Wednesday, November 16, 2016 8:59 PM Subject: RE: (lilypond-windows.exe:6216): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() #yiv8425948074 #yiv8425948074 -- _filtered #yiv8425948

RE: (lilypond-windows.exe:6216): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()

[mailto:lilypond-user-bounces+andrew.bernard=gmail@gnu.org] On Behalf Of MING TSANG Sent: Thursday, 17 November 2016 12:36 PM To: lilypond-user@gnu.org Subject: Re: (lilypond-windows.exe:6216): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() David, Thank you for the

Re: (lilypond-windows.exe:6216): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()

David, Thank you for the link.I forgot about it. it seems not the same to me. previous:(lilypond.exe:1892): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()warning: no glyph for character U+FFFD in font `C:/Windows/fonts/times.ttf' current:(lilypond-windows.exe

Re: (lilypond-windows.exe:6216): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()

On Wed 16 Nov 2016 at 21:38:45 (+), MING TSANG wrote: > Hi lilyponders, > I am running window 10 with lilypond v2.19.50 and frecobaldi 2.19.0 > 1. What is that mean? 2. Am I missing pango fonts?3. I search notation.pdf > 2.19.50 and cannot find a list of error message or warning + explaination

(lilypond-windows.exe:6216): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()

Hi lilyponders, I am running window 10 with lilypond v2.19.50 and frecobaldi 2.19.0 1. What is that mean? 2. Am I missing pango fonts?3. I search notation.pdf 2.19.50 and cannot find a list of error message or warning + explaination help appreciated. Immanuel,Ming__

Re: Invalid UTF-8 string passed to pango_layout_set_text()

rsing... > Interpreting music... > Preprocessing graphical objects... > Finding the ideal number of pages... > (lilypond.exe:1892): Pango-WARNING **: Invalid UTF-8 string passed to > pango_layout_set_text() > warning: no glyph for character U+FFFD in font `C:/Windows/fonts/times.ttf&

Re: Invalid UTF-8 string passed to pango_layout_set_text()

Hi Ming, On 12.11.2015 15:53, MING TSANG wrote: Hi, lilyponders: I ran the attach file and got the following. Question: can this be solved? How? It works fine if you don’t use any non-ASCII characters in the file name. I hope this is no problem for you. Else, there won’t be much we can do,

Invalid UTF-8 string passed to pango_layout_set_text()

ideal number of pages...(lilypond.exe:1892): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text()warning: no glyph for character U+FFFD in font `C:/Windows/fonts/times.ttf'warning: no glyph for character U+FFFD in font `C:/Windows/fonts/times.ttf'warning: no glyph

Re: "+" & utf-8 characters on file name

On Wednesday, March 19, 2014 3:36:42 AM, Wilbert Berendsen wrote: Excuse me for top-quoing, my phone forces me.  LilyPond intentionally changes non-alphanumeric characters to the underscore for the output-suffix. It doesn't do that for \bookOutputName, however.  I recently got bitten by

Re: "+" & utf-8 characters on file name

Excuse me for top-quoing, my phone forces me.  LilyPond intentionally changes non-alphanumeric characters to the underscore for the output-suffix. It doesn't do that for \bookOutputName, however.  I recently got bitten by this too and changed Frescobaldi so that it recognizes the changed charac

Re: "+" & utf-8 characters on file name

On Tuesday, March 18, 2014 5:58:51 PM, Simon Albrecht wrote: Am 18.03.2014 21:05, schrieb Fredrik Wallberg: Hi Ming, someone with more knowledge about Unicode (and Windows) could perhaps explain why that happens, but since you also asked for a workaround: Instead of using \bookOutSuffi

Re: "+" & utf-8 characters on file name

Am 18.03.2014 21:05, schrieb Fredrik Wallberg: Hi Ming, someone with more knowledge about Unicode (and Windows) could perhaps explain why that happens, but since you also asked for a workaround: Instead of using \bookOutSuffix, you could try with \bookOutputName, like this: \book { \bookOu

Re: "+" & utf-8 characters on file name

gt; > I was anticipating that the 2nd pdf file name to be > "test_utf-8_filename-SA+TB.pdf" Instead it generates > "test_utf-8_filename-SA_TB.pdf". > > Is it that lilypond cannot generate utf-8 character in the file name? > Any work around? > Emmanuel, > M

Re: "+" & utf-8 characters on file name

"test_utf-8_filename-SA_TB.pdf".  Is it that lilypond cannot generate utf-8 character in the file name? Any work around? Emmanuel, Ming  Additional info: I change the bookOutSuffix to utf-8 character "男女" and I got the following error: Starting lilypond-windows.exe 2.19.3 [test_ut

"+" & utf-8 characters on file name

The attached .ly file generate two pdf files.   1. test_utf-8_filename.pdf  2. test_uft-8_filename-SA_TB.pdf I was anticipating that the 2nd pdf file name to be  "test_utf-8_filename-SA+TB.pdf"  Instead it generates  "test_utf-8_filename-SA_TB.pdf".  Is it that lilypond c

utf-8 characters in file name.

ot the following warning error. I don't under what is the conflict copy. How can I find it in window 7?  The file name printed on the .pdf does not contain utf-8 character. On window 7 explorer (file manager) can show utf-8 character on directory name and file name, but lilypond cannot

UTF-8 error

This is supposed to be a reply to the posting about UTF-8 encoding and/or lilypond problems. Unfortunately I deleted the original thread. I want to reply to the message that had a test.zip attached including a problematic(?) test.ly tiny example and a bad(?) test.pdf file. I am running

Re: UTF-8 character - inverted quotation marks

The two quotation marks used in Hungarian are „ and ” U+201E and U+201D, to begin and end. Bert On Thu, Feb 10, 2011 at 1:40 PM, Werner LEMBERG wrote: > > DOUBLE LOW-9 QUOTATION MARK > > > > 201E (8222) > > This number is correct. The two quotation characters as used in > Germany are „ (U+201E

Re: UTF-8 character - inverted quotation marks

Quoting Ralph Palmer (palmer.r.vio...@gmail.com): > I'm transcribing some Bartok for my personal use. Apparently, Hungarian uses > inverted opening quotation marks, like ,,Title". I cannot find inverted > double quotation marks in the UTF-8 character sets online. Can anyone tel

Re: UTF-8 character - inverted quotation marks

> DOUBLE LOW-9 QUOTATION MARK > > 201E (8222) This number is correct. The two quotation characters as used in Germany are „ (U+201E) and “ (U+201C). In X, on my GNU/Linux box, I get those characters by pressing and respectively. However, I don't know where , the compose key, is m

Re: UTF-8 character - inverted quotation marks

Ralph Palmer writes: > I'm transcribing some Bartok for my personal use. Apparently, Hungarian uses > inverted opening quotation marks, like ,,Title". I cannot find inverted > double quotation marks in the UTF-8 character sets online. For these purposes I use the GNOME Charac

RE: UTF-8 character - inverted quotation marks

Ralph, From: lilypond-user-bounces+james.lowe=datacore@gnu.org [mailto:lilypond-user-bounces+james.lowe=datacore@gnu.org] On Behalf Of Ralph Palmer Sent: 10 February 2011 12:02 To: lilypond-user Mailinglist Subject: UTF-8 character - inverted quotation marks Greetings - I&#

UTF-8 character - inverted quotation marks

Greetings - I'm transcribing some Bartok for my personal use. Apparently, Hungarian uses inverted opening quotation marks, like ,,Title". I cannot find inverted double quotation marks in the UTF-8 character sets online. Can anyone tell me the code for inverted quotation marks? Thanks

Re: how to add a utf-8 character to the title

At 09:47 on 19 Jul 2009, Brian Kidd wrote: > > Are you sure you are saving your file in UTF-8? > > Not entirely. > > > Which editor are you using? > > Vim. :set encoding=utf-8 fileencodings= -- Mark Knoop ___ lilypond

Re: how to add a utf-8 character to the title

Brian Kidd wrote: On Jul 19, 2009, at 9:40 AM, Federico Bruni wrote: Are you sure you are saving your file in UTF-8? Not entirely. Which editor are you using? Vim. I guess you are a coder ;-) You may try other editors that have better support for Lilypond. jEdit with the Lilytool

Re: how to add a utf-8 character to the title

ond 2.12.1). Are you sure you are saving your file in UTF-8? Not entirely. Which editor are you using? Vim. Federico Thanks for the response. -brian ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: how to add a utf-8 character to the title

long way, but would be interested in knowing how to fix the problem with the short way. thanks, -brian Hi Brian, I can't help you with the error message.. Anyway, your snippet works fine in my PC (I use lilypond 2.12.1). Are you sure you are saving your file in UTF-8? Which editor are

Re: how to add a utf-8 character to the title

thanks to all who suggested using the short way. unfortunately, my system does not seem to be configured for this easy solution. when i run lilypond on the simple file below, i get the following error and the title is SintIntro instead of Sinté Intro. i'm happy using the long way, but would

Re: how to add a utf-8 character to the title

2009/7/19 Brian Kidd : > the long way worked. thanks! Use the short way, it's much shorter and comfortable e.g. for lyrics -- Francisco Vila. Badajoz (Spain) www.paconet.org ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mai

Re: how to add a utf-8 character to the title

Brian Kidd wrote: > i can create the variable > accentE = #(ly:export (ly:wide-char->utf-8 #x00e9)) > > and then i've tried > > i've tried: > \header{ > title = "Sint" \accentE " Intro" > } > > however, this doesn't work.

Re: how to add a utf-8 character to the title

On 19.07.2009, at 09:23, Brian Kidd wrote: hello, this seems like a simple thing, but i've been unable to find anything in the archives and the documentation. basically, i'd like to add a title that contains an accented character (unicode = 00e9). outside of lilypond the title would be:

Re: how to add a utf-8 character to the title

the long way worked. thanks! On Jul 19, 2009, at 12:33 AM, Mark Polesky wrote: Brian Kidd wrote: i can create the variable accentE = #(ly:export (ly:wide-char->utf-8 #x00e9)) and then i've tried i've tried: \header{ title = "Sint" \accentE " Intro" } ho

Re: how to add a utf-8 character to the title

If you're using a UTF-8 aware editor it should be a simple matter to simply enter your accented 'e' in your input file and have it appear in the output. Is your editor UTF-8 aware/capable and are you saving the file as UTF-8? -David Brian Kidd wrote: hello, this seems like

how to add a utf-8 character to the title

te the variable accentE = #(ly:export (ly:wide-char->utf-8 #x00e9)) and then i've tried i've tried: \header{ title = "Sint" \accentE " Intro" } however, this doesn't work. how can i concatenate these strings and utf-8

Re: Lilypondtool 2.12-r2 and UTF-8

, but although I have the default file encoding in jEdit set to UTF-8, it still insists on saving ly files as UTF-8Y. This only happens with ly files: I can open or create other types of file using UTF-8 encoding and they remain UTF-8 on saving.

Lilypondtool 2.12-r2 and UTF-8

I updated to this version of LPT a few days ago. It fixes the problem with jPedal and jEdit locking up if jPedal is not showing the first page of the PDF when rebuilding the ly file, but although I have the default file encoding in jEdit set to UTF-8, it still insists on saving ly files as UTF-8Y

Re: utf-8 characters

thanks, this also solves the problem which was mentioned by James that Apple mail converts >> at the beginning of a line to two levels of quoted text... ole Am 25.01.2009 um 20:50 schrieb Hans Aberg: One way around it is to select View -> Message -> Original Content (--U), and then copy.

Re: utf-8 characters

I have seen it - it seems to be a bug in Mail. Report it on apple.com/ feedback/ (with example) if you so want. One way around it is to select View -> Message -> Original Content (--U), and then copy. This might be a way around the other problem. Otherwise, Mail has Format -> Indentation,

Re: utf-8 characters

the mails look like this when they are seen in the mail previev (colored double lines instead of >>) ole <> Am 25.01.2009 um 14:45 schrieb Hans Aberg: On 25 Jan 2009, at 13:19, James E. Bailey wrote: Out of curiosity, do you know a way to stop apple mail from converting >> at the begi

Re: utf-8 characters

On 25 Jan 2009, at 18:03, Ole Schmidt wrote: I'am using Lilypond 2.12.1-1 which lives in the application folder. When I copy the same example as before and paste it into the terminal via cat method, it looks normal when use the less command. This is good - it means that you got UNIX line en

Re: utf-8 characters

I'am using Lilypond 2.12.1-1 which lives in the application folder. When I copy the same example as before and paste it into the terminal via cat method, it looks normal when use the less command. When I try to compile it with lilypond, I get the errorwarning below...(as before)... when I c

Re: utf-8 characters

On 25 Jan 2009, at 13:35, Ole Schmidt wrote: when I try the "cat" method and then compile directly from the terminal I get the same error warning as before. I'am on Mac OS 10.5.6. using the latest Lilypond... What LilyPond are you using? - I'm using the one put into / Applications/. And

Re: utf-8 characters

On 25 Jan 2009, at 13:19, James E. Bailey wrote: Out of curiosity, do you know a way to stop apple mail from converting >> at the beginning of a line to two levels of quoted text? So, << {c'1} {a1} >> can be copied properly I don't have any problems with that; I tried 'cat

Re: utf-8 characters

when I try the "cat" method and then compile directly from the terminal I get the same error warning as before. I'am on Mac OS 10.5.6. using the latest Lilypond... Am 25.01.2009 um 13:00 schrieb Hans Aberg: On 25 Jan 2009, at 11:58, Ole Schmidt wrote: the screenshot was from Smultron. The p

Re: utf-8 characters

Am 25.01.2009 um 10:38 schrieb Hans Aberg: On 24 Jan 2009, at 12:35, Ole Schmidt wrote: when I choose in the preferences "show invisible characters", my file look like this: it seems like a copy & paste promblem from my mail-client (Apple "Mail"). Does anyone know how to fix this? Wh

Re: utf-8 characters

On 25 Jan 2009, at 11:58, Ole Schmidt wrote: the screenshot was from Smultron. The problem is attached, when I copy & paste from Mail to Smultron/jedit/Terminal and try to compile, I get the following error warnings (see Pict.2), when I changed the tabs/spaces like in the third picture it w

Re: utf-8 characters

On 24 Jan 2009, at 12:35, Ole Schmidt wrote: when I choose in the preferences "show invisible characters", my file look like this: it seems like a copy & paste promblem from my mail-client (Apple "Mail"). Does anyone know how to fix this? What editor did you use - it is showing probably

Re: utf-8 characters

On 1/24/09 4:36 AM, "James E. Bailey" wrote: > Oh yeah, that's a problem. Apparently it's been fixed, it's just not > in the distributed binary. There's a thread on the list that shows > how to fix it. > You can also find the fix on issue 735 at the bug tracker, thanks to James:

Re: utf-8 characters

James E. Bailey googlemail.com> writes: > > { > > \mark \markup \rounded-box { > > \small { > > \concat { 4\char ##x2032 } > > } > > } c'2 > > } > > > > error: > > > > (process:440): Pango-WARNING **: Error loading GDEF table 28333 > > > > ...

Re: utf-8 characters

Oh yeah, that's a problem. Apparently it's been fixed, it's just not in the distributed binary. There's a thread on the list that shows how to fix it. Am 24.01.2009 um 12:26 schrieb Tom Hall: James E. Bailey googlemail.com> writes: Hello James I also get an error as follows when trying

Re: utf-8 characters

when I choose in the preferences "show invisible characters", my file look like this: <> it seems like a copy & paste promblem from my mail-client (Apple "Mail"). Does anyone know how to fix this? ole Am 24.01.2009 um 12:23 schrieb James E. Bailey: { \mark \markup \rounded-box {

Re: utf-8 characters

James E. Bailey googlemail.com> writes: Hello James > > I also get an error as follows when trying the code below: > > > > Regards > > > > Tom > > > > > > error: syntax error, unexpected SCM_TOKEN > > \concat { 4/char > > ##x2032 } >

Re: utf-8 characters

Am 24.01.2009 um 11:44 schrieb Tom Hall: James E. Bailey googlemail.com> writes: { \mark \markup \rounded-box { \small { 4′33″ } } c'2 } Hmm, trying the code directly above, gives me the following error (3 times) (pr

Re: utf-8 characters

James E. Bailey googlemail.com> writes: > > There may be an easier way. In osx, you have utf-8 on by default. So > you don't need to use the lilypond special of inserting utf-8 > characters. Which, by the way, mark's way I don't understand, it uses > sche

Re: utf-8 characters

There may be an easier way. In osx, you have utf-8 on by default. So you don't need to use the lilypond special of inserting utf-8 characters. Which, by the way, mark's way I don't understand, it uses scheme. The easier way is to just use \markup \concat { 4/char ##x2032 } Bu

utf-8 characters

rs, like 中, for example, it doesn't seem possible to cut and paste these struck out letters into the lily editor. Excuse this basic question, but I can't spot references to this issue in the lily docs. Regards Tom min = \markup { %% 2032 = PRIME #(ly:export (format "~

Re: insertion of UTF-8 characters

2008/10/14 Trevor Daniels <[EMAIL PROTECTED]>: > I'll change the new examples I added today to > use it, as you suggest. And remove the Scheme hack. Thanks. Thanks for the fix, Trevor. I'll flesh out the the \char example in the appendices a bit to demonstrate its usage better. Regards, Neil

Re: insertion of UTF-8 characters

, October 14, 2008 9:33 PM Hi Trevor, 2008/10/14 Trevor Daniels <[EMAIL PROTECTED]>: Tom It has to be within a \markup and not in quotes. And xc2a9 should be 00a9. Try c'4^\markup { #(ly:export (ly:wide-char->utf-8 #x00a9)) } or just \markup { "Copyright 2008" #(ly:e

Re: insertion of UTF-8 characters

Neil Puttock wrote Tuesday, October 14, 2008 9:33 PM Hi Trevor, 2008/10/14 Trevor Daniels <[EMAIL PROTECTED]>: Tom It has to be within a \markup and not in quotes. And xc2a9 should be 00a9. Try c'4^\markup { #(ly:export (ly:wide-char->utf-8 #x00a9)) } or just \marku

Re: insertion of UTF-8 characters

Hi Trevor, 2008/10/14 Trevor Daniels <[EMAIL PROTECTED]>: > Tom > > It has to be within a \markup and not in quotes. And xc2a9 should be 00a9. > > Try > > c'4^\markup { #(ly:export (ly:wide-char->utf-8 #x00a9)) } > > or just > > \markup { &q

Re: insertion of UTF-8 characters

Tom It has to be within a \markup and not in quotes. And xc2a9 should be 00a9. Try c'4^\markup { #(ly:export (ly:wide-char->utf-8 #x00a9)) } or just \markup { "Copyright 2008" #(ly:export (ly:wide-char->utf-8 #x00a9)) } outside the score block to place i

Re: insertion of UTF-8 characters

Try copying this character in there: © I tried the way the docs say, as well, and never got it to work. I found that if I just copied an actual copyright symbol into my files and made sure the editor was saving in utf-8 encoding, it all worked fine. Jon Tom Cloyd wrote: forgot this: I&#

Re: insertion of UTF-8 characters

forgot this: I'm running Ly 2.11.60, on Kubuntu Linux 8.04.1 Tom Cloyd wrote: The documentation [/Lilypond notation reference.pdf/, “3.3.3 Text encoding”, pdf p. 318.] states that UTF-8 coding is used in Ly and that UTF-8 hex codes can be inserted into text. An example is given, and I sh

  1   2   >