To do that, select the CompositeScene prototype with the Text Inspector open, and the Text tab selected.
If you leave it on, you will find that single and double quotation marks will be converted automatically to their typographic forms, which do not work with the markup scheme in Storyspace. One other useful trick is to turn off Smart Quotes in the CompositeScene prototype, which will make it much easier for me to enter the straight "" double-quotation marks for include and Stretchtext references.
#Storyspace cambridge Patch#
The best way to do this here is to select the writing space in the Map view, in Edit mode, select all the text, then in the Text inspector change the colour set for the text, and click on the colour patch (to bring up the colour selector), and click on the OK button in that selector. I would also have needed to make the writing spaces of each story from a different prototype. Setting text colour should be something that I can do in the prototype, but this doesn’t always work perfectly. As I’m going to include the text from the respective TextSource writing spaces to preface each section of included text, I revise those and set them in a smaller, contrasting font, in green. This is a good time to check through the text content of each writing space to ensure that it uses the same font, to add any emphasis, and generally prepare each text item for the reader. To add to the visual contrast, I set the text in the two different stories using different colours: a dark blue for the story from Mark, and red for that from Wilde’s play. I also want to make the writing spaces in this composite narrative quite distinct, so I create a new prototype for them, with different coloured tiles and a different badge at the top right of the tile. John in prison in the Wilde story is renamed John in prison (W). Where I have common names, I append a locational qualifier, e.g. If two or more writing spaces have the same name, citing that name in an include or Stretchtext will result in Storyspace fetching the text from the first writing space with that name, which is probably not what I expect. ^stretch("This is anchor text.","/notepath")īefore doing this, I need to make an important check, that all my writing spaces have unique names, which they don’t.
#Storyspace cambridge full#
These can be worked around using Stretchtext, in which a short anchor text is displayed normally, and is replaced by the full text when the reader clicks on the anchor In some scenes from the play, I have included long quotations from the script which would be likely to disrupt the context. In this context, I think that this works very well so long as the scenes are short, maybe no more than a few lines. The simplest form is to include the text of the two corresponding versions of a scene in a single writing space, using the markup Storyspace provides several powerful tools for this, a text substitution. This is preferable to linking equivalent scenes in the two stories, as switching between the versions will change context.
To retain context, the reader will be able to consider the two versions of each scene side by side in a single writing space. To facilitate their comparison, I am going to create a chain of writing spaces which present both stories in composite. A reader can now work their way through each text from the start writing space. Each consists of a chain of writing spaces describing individual scenes, linked together using plain links. In the last article, I laid out the two main stories concerning Herod, Herodias, Salome, and John the Baptist: that from the Gospels, and that given in Wilde’s play.
0 kommentar(er)
