bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug report: U+3000 IDEOGRAPHIC SPACE isn't treated as whitespace


From: Werner LEMBERG
Subject: Re: Bug report: U+3000 IDEOGRAPHIC SPACE isn't treated as whitespace
Date: Wed, 14 Feb 2018 22:34:04 +0100 (CET)

>> Basically, when entering data in \lyricmode, U+0020 SPACE correctly
>> breaks syllables, but U+3000 IDEOGRAPHIC SPACE (which is the
>> default space on Japanese keyboard layouts) does not: the syllables
>> separated with that character all wind up on one note.  Shouldn't
>> we break syllables on *any* Unicode whitespace character (except
>> for the nonbreaking spaces, which I believe have different Unicode
>> character properties)?
> 
> \lyricmode does not mean "Paste arbitrary text here".
> 
> LilyPond intentionally uses exclusively the ASCII character range
> for syntactic purposes.  Everything else can be part of identifiers
> or words.  That makes LilyPond documents robust against changes in
> Unicode.

I second that.  Additionally, it's trivial to search and replace all
Unicode whitespace with ASCII whitespace in case this is what the user
wants.


    Werner



reply via email to

[Prev in Thread] Current Thread [Next in Thread]