Multiple choices, whether variables or options text, need to be coded in such a way that Pathagoras can tell where each choice starts and ends. The beginning of the first choice is pretty easy to figure out:

 It will be the boundary marker, either the [ or the { or the <<*Options* command.

Likewise, the end of last choices will be the closing boundary marker, ']', '}' or '>>'

 The separators between the intervening choices are the 'challenge,' but really it won't be hard once you understand the concept and the reasons for the exceptions

 In most cases, the separator will be a simple forward slash: '/', as in [apples/banana/strawberries]

 But what if the choice itself has a slash as part of its 'normal presentation. E.g.,

 Further, what if the parent choice has child elements that themselves contain choices.

 To maintain the 'plain text' approach that Pathagoras has adopted, we added additional separators to make these 'problems' NOT problems.

       CaratOR and PercentOR separators: To determine the proper scope of a particular option within an <<*Options* . . .> block, where the choices were indicated by a simple slash (/), Pathagoras must convert nested options and variables that may also contain 'slashes' into other characters. That way, only 'relevant' slashes are seen. The process is quick and typically unnoticeable. However, the complex and heavily nested documents that many users have been able to create presented a 'problem.' They were beyond our wildest imaginations when we first undertook to write the program.) The process of converting those slashes was still just seconds, but those seconds began to add up. By adding these 'Super Separators'  (%OR and ^OR, 'capital' 5 and 6 on your keyboard) as a divider for top (parent) level options, Pathagoras can parse out large swaths of text (keeping or deleting the text as appropriate) without converting an sub-level slashes.This will dramatically improve processing speed.