actions macro is a little inflexible

Comments

• TheMadExile

  September 2014

  You didn't say what story format you were using.  However, if you're using SugarCube, then you could use the wiki link syntax, which is allowed in all macros that take link arguments, like so:

  
/%
% [[passage]] style. The passages titles for these would be (exactly, all quotes included):
% "A' ain't gonna do it, an' that's final!"
% "Well, a' suppose I could. Just this once, ya' un'erstand?"
%/
<<actions [["\"A' ain't gonna do it, an' that's final!\""]] [["\"Well, a' suppose I could. Just this once, ya' un'erstand?\""]]>>

/%
% [[linktext|passage]] style. I prefer this one, since the passage titles aren't laced with quotes, just the link text.
%/
<<actions [["\"A' ain't gonna do it, an' that's final!\""|Daisy refuses]] [["\"Well, a' suppose I could. Just this once, ya' un'erstand?\""|Daisy agrees]]>>


  I've also updated SugarCube to unescape all string literals used as macro arguments.  So, this will also work after the next update:

  
<<actions "\"A' ain't gonna do it, an' that's final!\"" "\"Well, a' suppose I could. Just this once, ya' un'erstand?\"">>


  
  If you're not using SugarCube, then I'm sure the vanilla headers will get updated for this sooner or later.
• AteYourLembas

  September 2014

  Interesting issue. I suspect you could work around it by using the ASCII for the character instead of the character itself. It wouldn't disrupt the parser, and the browser would deliver the right character to the reader.
  
  http://www.ascii.cl/htmlcodes.htm
  
  e.g.
  
  " --> "
  ' --> '
  
  Makes reading the code annoying, I realize, but it's an option.