LilyPond strings and \markup

[Mark Polesky]

\version "2.13.4"

%%%%%%%%%%%%
% QUESTION 1

% "quoted string" is STRING
strA = "quoted string"

% #"hash-quoted string" is SCM_TOKEN
strB = #"hash-quoted string"

% these are both 'unexpected STRING_IDENTIFIER's:
% \strA \strB

% Why isn't \strB an 'unexpected SCM_IDENTIFIER'?


%%%%%%%%%%%%
% QUESTION 2

% A valid LilyPond unquoted 'STRING':
% 1) must be entirely alphabetic, and
% 2) cannot be interpreted as a number, pitch, rest, or operator.

% So, without quotes, these are all invalid LilyPond 'STRING's:
% 3 f r + big-pr0bl3m!

% but \markup accepts all of these seamlessly:
\markup { 3 f r + n0-pr0bl3m! }

% It's as if, behind the scenes, the parser silently adds quotes.
% So how exactly does that happen? And does the parser read
% them as LilyPond 'STRING's or as a Scheme strings?

% Thanks!
% - Mark