Handle abjad.MetronomeMark.textual_indication literally

[trevorbaca]

Abjad 3.13 wraps abjad.MetronomeMark.textual_indication with an extra pair of double quotes when textual_indication contains whitespace:

>>> mark = abjad.MetronomeMark(textual_indication="Allegro")
>>> string = abjad.lilypond(mark)
>>> print(string)
\tempo Allegro

>>> mark = abjad.MetronomeMark(textual_indication="Allegro ma")
>>> string = abjad.lilypond(mark)
>>> print(string)
\tempo "Allegro ma"

The behavior was designed to be helpful (the second example above does make good LilyPond input), but is at odds with the literal (WYSIWYG) way of working with abjad.Markup, and almost all other objects in Abjad.

The right way to produce \tempo "Allegro ma" should be with text_indication='"Allegro ma"', but this results in a redundant pair of double quotes in Abjad 3.13:

>>> mark = abjad.MetronomeMark(textual_indication='"Allegro ma"')
>>> string = abjad.lilypond(mark)
>>> print(string)
\tempo ""Allegro ma""

Abjad 3.14 removes this behavior and outputs the contents of textual_indication exactly as entered by the user:

>>> mark = abjad.MetronomeMark(textual_indication="Allegro")                                  
>>> string = abjad.lilypond(mark)                                                             
>>> print(string)
\tempo Allegro
                                                                             
>>> mark = abjad.MetronomeMark(textual_indication="Allegro ma")                               
>>> string = abjad.lilypond(mark)                                                             
>>> print(string)
\tempo Allegro ma
                                                                             
>>> mark = abjad.MetronomeMark(textual_indication='"Allegro ma"')                             
>>> string = abjad.lilypond(mark)                                                             
>>> print(string)      
\tempo "Allegro ma"                  

[trevorbaca]

@martin-ribot

[martin-ribot]

Great! Thank you. Sorry for not having opened the issue here as I said I would!