lilypond-user
[Top][All Lists]
Advanced

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

Snippet 888 string, was Re: Lyric centre-on-word / ignore-punctuation bu


From: David Wright
Subject: Snippet 888 string, was Re: Lyric centre-on-word / ignore-punctuation bug
Date: Sat, 24 Feb 2018 09:18:10 -0600
User-agent: Mutt/1.5.21 (2010-09-15)

On Sat 24 Feb 2018 at 11:06:20 (+0100), David Kastrup wrote:
> Thomas Morley <address@hidden> writes:
> 
> > 2018-02-24 3:45 GMT+01:00 Kieren MacMillan <address@hidden>:
> >> Hi all,
> >>
> >> When a lyric syllable begins with a typographer’s single quote
> >> (e.g., ’cause, ’ll, etc.), the "ignore-punctuation" hack doesn't
> >> work. Any hints on how to fix this would be appreciated.
> >>
> >> Thanks,
> >> Kieren.
> >>
> >> %%%  SNIPPET BEGINS
> >> \version "2.19"
> >>
> >
> > Only characters from `space-set' are respected by `center-on-word'.
> > Extend the given string with "’"
> >
> >> #(define space-set
> >>   (list->char-set
> >>     (string->list "—.?-;,:“†‘’–— */()[]{}|<>!`~&…")))
> >
> > #(define space-set
> >   (list->char-set
> >     (string->list "’—.?-;,:“†‘’–— */()[]{}|<>!`~&…")))
> >
> > works for me.
> 
> Doesn't really look like dealing sensibly with utf-8.

AFAICT the string in the original snippet is

—.?-;,:“”‘’–— */()[]{}|<>!`~&…

What I haven't figured out is why there are two long dashes; perhaps
someone added the one at the beginning because they couldn't see
the one in the middle. And why the space after the latter?

The following gives the hex in case this message is garbled.

$ ucount.py /tmp/the-string 
   10       a    1       1      LF  
   32      20    1       1      SPC 
   33      21    1       1      !   
   38      26    1       1      &   
   40      28    1       1      (   
   41      29    1       1      )   
   42      2a    1       1      *   
   44      2c    1       1      ,   
   45      2d    1       1      -   
   46      2e    1       1      .   
   47      2f    1       1      /   
   58      3a    1       1      :   
   59      3b    1       1      ;   
   60      3c    1       1      <   
   62      3e    1       1      >   
   63      3f    1       1      ?   
   91      5b    1       1      [   
   93      5d    1       1      ]   
   96      60    1       1      `   
  123      7b    1       1      {   
  124      7c    1       1      |   
  125      7d    1       1      }   
  126      7e    1       1      ~   
 8211    2013    1       1      –   
 8212    2014    2       1      —   
 8216    2018    1       1      ‘   
 8217    2019    1       1      ’   
 8220    201c    1       1      “   
 8221    201d    1       1      ”   
 8230    2026    1       1      …   
Scanned 31 Unicode characters with 0 problems
$ 

Cheers,
David.

Attachment: the-string
Description: Text document


reply via email to

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