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 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

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 { \bookOutputName "+中国曲子+" Which works fine over here (vers

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

On Tuesday, March 18, 2014 12:58:13 PM, MING TSANG wrote: 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_fil

"+" & 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 cannot generate utf-8 char

utf-8 characters in file name.

%%lily code  file name Test_中文.ly \version "2.19.2" #(define (footnote-filename) (define (periodize i l) (if (null? l) i (periodize (string-append i "." (car l)) (cdr l (let* ((comml (object->string (command-line))) (loc (+ (string-rindex comml #\space) 2)) (commllen (- (string-length comml) 2)

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

Hello List I understand the way to put special characters into markup is as below (from Mark's reply to the stopwach question below - although missing the struck out letters - read on). But how do I strike out the "char" part in LilyPond (Mac X.4.11)? Unlike, other charcters, like 中, for example

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

Good lord above, yes! THIS is immediately understandable if one has experience with a multitude of other programming languages, whereas that other approach is exasperating nonsense. Thanks, fellows, for chasing this one to ground. t. Trevor Daniels wrote: Neil Puttock wrote Tuesday, October

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 \markup { "Copyright

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 { "Copyright 2008" #(ly:export (ly:wide-char->utf-8 #x00

Re: insertion of UTF-8 characters

t in text, or for the copyright line, try copyright = \markup { #(ly:export (ly:wide-char->utf-8 #x00a9)) "2008" } . Trevor - Original Message - From: "Tom Cloyd" <[EMAIL PROTECTED]> To: "Lilypond" Sent: Tuesday, October 14, 2008 2:08 AM Subject:

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'm r

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 show it

insertion of UTF-8 characters

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 show it here using the code of interest to me - that for the Copyright sign: #(ly:expo