https://sourceware.org/bugzilla/show_bug.cgi?id=32003
Jan Beulich <jbeulich at suse dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jbeulich at suse dot com
--- Comment #4 from Jan Beulich <jbeulich at suse dot com> ---
(In reply to H.J. Lu from comment #3)
> One possibility is to treat "\comma" as ','.
Yet introducing another escape character would come with further complexity. It
also looks to me as if the %-encoding of double-quotes dominated that of commas
in the example provided.
I'm inclined to suggest to extend the %-encoding scheme instead; that way
what's going to be in 2.43 is not at risk of subtle breakage when support
further escaping sequences is added. All that needs to be made sure is for
existing escaping sequences to retain their original meaning.
What the best scheme here would be is likely better determined by people who
make active use of the feature (knowing what set of characters it is that
frequently would need escaping one way or the other). I'd be inclined to borrow
naming e.g. from HTML's Named Character References, and then use, say,
"%[comma]" or "%comma;" to have proper delimiting on both ends.
--
You are receiving this mail because:
You are on the CC list for the bug.
