On Thu 04 Jul 2024 at 21:11:29 (+0100), Raphael Mankin wrote:
> On 04/07/2024 16:48, Jean Abou Samra wrote:
> > Le jeudi 04 juillet 2024 à 15:21 +0100, Raphael Mankin a écrit :
> > Anyhow, I persist in my opinion that facilitating the input of accented
> > characters is
>> As you mention 'snippet': The right place for this is the LSR, I
>> believe.
>
> Definitely, yes. But I don’t dislike the idea of having some more or
> less standard LSR snippets for people who want something like this.
Having a 'standard LSR snippet' is certainly a good thing since we
then c
Am Donnerstag, 4. Juli 2024, 18:52:22 MESZ schrieb Werner LEMBERG:
> >> Certainly! However, this shouldn't become part of LilyPond IMHO;
> >> it's opening a can of worms since all those sets are essentially
> >> open-ended – "why is character 'fronz with grmpf above' not part of
> >> this or that
On 04/07/2024 16:48, Jean Abou Samra wrote:
Le jeudi 04 juillet 2024 à 15:21 +0100, Raphael Mankin a écrit :
Anyhow, I persist in my opinion that facilitating the input of accented
characters is best done at a level different than LilyPond.
I don't disagree with you. Using a compose
>> Certainly! However, this shouldn't become part of LilyPond IMHO;
>> it's opening a can of worms since all those sets are essentially
>> open-ended – "why is character 'fronz with grmpf above' not part of
>> this or that set?"
>
> Yes, but here the extensibility comes into play. If you want to
Am Donnerstag, 4. Juli 2024, 18:41:56 MESZ schrieb Werner LEMBERG:
> > And so while I do agree that if the problem can be solved before
> > Lilypond actually matter, then great. But if this does not work out
> > to you, then nothings wrong with getting Lilypond to help you out.
>
>
> Certainly!
> And so while I do agree that if the problem can be solved before
> Lilypond actually matter, then great. But if this does not work out
> to you, then nothings wrong with getting Lilypond to help you out.
Certainly! However, this shouldn't become part of LilyPond IMHO; it's
opening a can of wor
Am Donnerstag, 4. Juli 2024, 17:48:12 MESZ schrieb Jean Abou Samra:
> Anyhow, I persist in my opinion that facilitating the input of accented
> characters is best done at a level different than LilyPond.
I do agree only partially. Yes, if we reduce the problem of special characters
to inpu
> Anyhow, I persist in my opinion that facilitating the input of
> accented characters is best done at a level different than LilyPond.
+1
Werner
pinion that facilitating the input of accented
characters is best done at a level different than LilyPond.
Best
Jean
signature.asc
Description: This is a digitally signed message part
On 04/07/2024 09:57, Jean Abou Samra wrote:
Le jeudi 04 juillet 2024 à 08:09 +0100, Raphael Mankin a écrit :
I already use these, but they are incomplete.
Thanks to all who replied; I obviously struck a nerve, and i10n is still
an issue in spite of utf8.
I beg to differ. IMHO, entering sp
On 04.07.24 11:14, N. Andrew Walsh wrote:
I suppose it'd be also possible if you're wrapping your .ly file
inside some latex-ly .tex file to use LaTeX's syntax for accented
characters
Certainly the reason why #(include-special-characters) was developed,
see my other repl
On 04.07.24 09:09, Raphael Mankin wrote:
https://lilypond.org/doc/v2.25/Documentation/notation/ascii-aliases
https://lilypond.org/doc/v2.25/Documentation/notation/list-of-special-characters
I already use these, but they are incomplete.
Assuming that you are referring to French characters w
depends on just how
frequently you need accented characters).
I suppose it'd be also possible if you're wrapping your .ly file inside
some latex-ly .tex file to use LaTeX's syntax for accented characters, but
that's not something with which I have any real experience.
Hope that help
Le jeudi 04 juillet 2024 à 08:09 +0100, Raphael Mankin a écrit :
> I already use these, but they are incomplete.
>
> Thanks to all who replied; I obviously struck a nerve, and i10n is still
> an issue in spite of utf8.
I beg to differ. IMHO, entering special characters is an OS-level problem;
p
On 03/07/2024 20:33, Simon Albrecht wrote:
Hi Valentin,
On 03.07.24 14:31, Valentin Petzel wrote:
I’ve taken some time to create a function for decoding html-style
entities.
wow, that’s a great bit of initiative! I’m really sorry that only upon
seeing this I remembered the text-replacemen
Hi Valentin,
On 03.07.24 14:31, Valentin Petzel wrote:
I’ve taken some time to create a function for decoding html-style entities.
wow, that’s a great bit of initiative! I’m really sorry that only upon
seeing this I remembered the text-replacements function already in
LilyPond which does pre
Thank you. That sounds like just the ticket.
Is your update a standard part of 2.24.3, or do I have to download an
extra file or two?
On 03/07/2024 13:47, Valentin Petzel wrote:
Also for Lyrics you can then do
\score {
\new Lyrics \with {
\override LyricText.before-line-breaking =
Although that one does not work out perfectly, as the tied-lyrics logic will
only be applied if the text is a basic string. What would be necessary is a
way to specify string-transformers for a grobs default properties, which would
require something like
https://gitlab.com/lilypond/lilypond/-/i
Also for Lyrics you can then do
\score {
\new Lyrics \with {
\override LyricText.before-line-breaking =
#(lambda (grob)
(ly:grob-set-property! grob 'text (htmldecode (ly:grob-property grob
'text
} \lyricmode {
Thìs ïs â téşt
}
}
Cheers,
Valentin
Am Mittwoch, 3. Juli
Hello,
I’ve taken some time to create a function for decoding html-style entities. So
instead of entering
\markup { á è ç â ... }
you can do
\markup\htmldecode { á è ç â ... }
or
\markup\htmldecode { "á" "è" "ç" "â" ... }
or
\markup\htmldecode { &:xE1; &:xE8; &:xE7; &:xE2; ... }
(I’ve add
Il giorno mer 3 lug 2024 alle ore 09:27 Raphael Mankin
ha scritto:
> character picking is a PITA. I shall have to add a French keyboard to my
> layouts.
>
On a GNU/Linux system you have 2 other possibilities:
1) Ctrl + Shift + u followed by the hex unicode code (for example 00e7 for
ç);
2) Usin
Le mercredi 03 juillet 2024 à 08:26 +0100, Raphael Mankin a écrit :
> Thank you. The obvious is what generally escapes one. But character
> picking is a PITA. I shall have to add a French keyboard to my layouts.
> AZERTY :-(
Have you tried a Compose key?
At least under a GNOME Linux desktop, th
On 02/07/2024 22:25, Jean Abou Samra wrote:
I have tried all sorts of things, but how do I get French accented
characters in lyrics and markup?
Uh… just write them directly:
\version "2.24.2"
\markup { Quelques caractères accentués }
\lyrics { É à û Ï }
Thank you. The
> I have tried all sorts of things, but how do I get French accented
> characters in lyrics and markup?
Uh… just write them directly:
\version "2.24.2"
\markup { Quelques caractères accentués }
\lyrics { É à û Ï }
Jean
signature.asc
Description: This is a digitall
I have tried all sorts of things, but how do I get French accented
characters in lyrics and markup?
--
On Mon, Sep 03, 2007 at 02:43:17PM +0200, Mats Bengtsson wrote:
> Just make sure that your text editor is configured to save the file using
> UTF-8 encoding, and everything should work without problems.
Thank you for the reply. When the system is all Latin-1 (iso-8859-1),
setting it utf-8 is a bit
2007/9/3, vwf <[EMAIL PROTECTED]>:
> Hello,
>
> I would like to use accented characters in lyrics (French), but I cannot
> get it working: (process:4373): Pango-CRITICAL **: pango_coverage_get:
> assertion `index >= 0' failed
Hi,
you might be interested in knowing th
on
web page for your version of LilyPond.
/Mats
vwf wrote:
Hello,
I would like to use accented characters in lyrics (French), but I cannot
get it working: (process:4373): Pango-CRITICAL **: pango_coverage_get:
assertion `index >= 0' failed
Is there a (minimal) example code that sh
Hello,
I would like to use accented characters in lyrics (French), but I cannot
get it working: (process:4373): Pango-CRITICAL **: pango_coverage_get:
assertion `index >= 0' failed
Is there a (minimal) example code that shows how to do it?
T
30 matches
Mail list logo
