openboe/oboe
2
0
Fork 0
Code Issues 146 Pull Requests 4 Actions Packages Projects Releases Wiki Activity

Mass fix use of curly quotes in dialogs

Browse Source
This commit is contained in:
Celtic Minstrel
2015-06-24 15:56:47 -04:00
parent 4934bb220a
commit 8a4e7a7a72
19 changed files with 33 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
rsrc/dialogs/data-dump-confirm.xml
View File

@@ -5,7 +5,7 @@
<button name='cancel' type='regular' def-key='esc' top='74' left='190'>Cancel</button>
<pict type='dlog' num='16' top='6' left='6'/>
<text top='6' left='49' width='271' height='66'>
Lists of all the terrain types, monster types, and item types in your scenario are about to be put in a file called ‘Scenario data’.
Lists of all the terrain types, monster types, and item types in your scenario are about to be put in a file called 'Scenario data'.
You can then print out this file to ast as a handy reference while designing your scenario.
</text>
</dialog>

4
rsrc/dialogs/delete-town-confirm.xml
View File

@@ -5,9 +5,9 @@
<button name='cancel' type='regular' def-key='esc' top='143' left='187'>Cancel</button>
<pict type='dlog' num='16' top='6' left='6'/>
<text top='6' left='49' width='271' height='66'>
You are about to delete the last town in your scenario’s town list
You are about to delete the last town in your scenario's town list
(so if you have 10 towns in your scenario, the tenth will disappear).
This change will immediately be saved, and can’t be undone.
This change will immediately be saved, and can't be undone.
</text>
<text top='127' left='49' width='268' height='14'>Are you sure you want to do this?</text>
<text top='73' left='49' width='276' height='53'>

2
rsrc/dialogs/edit-boats.xml
View File

@@ -35,7 +35,7 @@
There can be up to 24 boats in your scenario,
each of which must start in some town.
The boats can start as the parties property, if you want.
If the town is left at -1, the boat won’t exist.
If the town is left at -1, the boat won't exist.
</text>
<text top='70' left='199' width='106' height='14'>Town to start in</text>
<text top='64' left='310' width='76' height='25'>X Location in town</text>

4
rsrc/dialogs/edit-horses.xml
View File

@@ -37,8 +37,8 @@
Leave the town at -1 to make the horse not exist.
</text>
<text top='65' left='50' width='439' height='41'>
Note that horses can’t walk over certain terrain types (like floors).
Be careful not to place horses where they’re stuck and can’t get out.
Note that horses can't walk over certain terrain types (like floors).
Be careful not to place horses where they're stuck and can't get out.
This makes them sad.
</text>
<text top='113' left='199' width='106' height='14'>Town to start in</text>

2
rsrc/dialogs/edit-intro.xml
View File

@@ -14,7 +14,7 @@
<text size='large' top='6' left='50' width='156' height='17'>Scenario Details</text>
<text top='22' left='50' width='300' height='40'>
This is where you can write the text that is displayed to the player upon starting the scenario.
You can also pick your scenario’s icon.
You can also pick your scenario's icon.
</text>
<text size='large' top='63' left='50' width='120' height='14'>Introductory text:</text>
<text top='22' left='360' width='149' height='14'>Scenario icon number:</text>

2
rsrc/dialogs/edit-outdoor-encounter.xml
View File

@@ -71,5 +71,5 @@
<text top='240' left='352' width='194' height='14'>Special called when party winds</text>
<text top='283' left='352' width='194' height='14'>Special called if party flees</text>
<text top='326' left='352' width='103' height='33'>Stuff done flag to eliminate encounter</text>
<text top='168' left='364' width='170' height='27'>Note: Ignore these if you aren’t sure what they do.</text>
<text top='168' left='364' width='170' height='27'>Note: Ignore these if you aren't sure what they do.</text>
</dialog>

2
rsrc/dialogs/edit-scenario-events.xml
View File

@@ -37,7 +37,7 @@
<text top='97' left='239' width='131' height='28'>Scenario special node to call.</text>
<text top='246' left='2' width='119' height='106'>
Note: If you leave the time between calls at 0, no special node is called.
Don’t have special nodes called too often ... it slows the game down.
Don't have special nodes called too often ... it slows the game down.
</text>
<button name='edit1' type='large' top='131' left='324'>Create/Edit</button>
<button name='edit2' type='large' top='159' left='324'>Create/Edit</button>

2
rsrc/dialogs/edit-sign.xml
View File

@@ -4,7 +4,7 @@
<!-- OK button -->
<field name='text' top='34' left='55' width='293' height='98'/>
<button name='cancel' type='regular' top='141' left='222' def-key='esc'>Cancel</button>
<text top='142' left='7' width='198' height='15'>Use a ‘|’ to indicate a line break.</text>
<text top='142' left='7' width='198' height='15'>Use a '|' to indicate a line break.</text>
<text name='num' top='8' left='287' width='37' height='14'/>
<pict name='pic' type='dlog' num='16' top='8' left='12'/>
<text size='large' top='6' left='50' width='138' height='17'>Editing Sign</text>

2
rsrc/dialogs/edit-town-events.xml
View File

@@ -30,7 +30,7 @@
<text top='88' left='244' width='118' height='25'>Town special node to call.</text>
<text top='216' left='4' width='106' height='120'>
Note: If you leave the time between calls at 0, no special node is called.
Don’t have special nodes called too often ... it slows the game down.
Don't have special nodes called too often ... it slows the game down.
</text>
<button name='edit1' type='large' top='119' left='325'>Create/Edit</button>
<button name='edit2' type='large' top='147' left='325'>Create/Edit</button>

8
rsrc/dialogs/help-contest.xml
View File

@@ -20,15 +20,15 @@
Second Prize - $300.
Third prize - $200.
Fourth through Tenth Place -
Free copies of Spiderweb Software’s games.
Free copies of Spiderweb Software's games.
</text>
<text top='121' left='50' width='412' height='40'>
To get the full facts (and solid advice) on the contest, read the file “Scenario Design Contest”.
To get the full facts (and solid advice) on the contest, read the file "Scenario Design Contest".
The deadline for entries is November 1, 1998 (good scenario design takes time).
</text>
<text top='162' left='50' width='417' height='40'>
Finally, if you’re reading this too late to take part, be sure to drop by www.spidweb.com.
If this contest gets good entries, we’ll be sure to immediately hold another one right afterwards.
Finally, if you're reading this too late to take part, be sure to drop by www.spidweb.com.
If this contest gets good entries, we'll be sure to immediately hold another one right afterwards.
</text>
<text top='4' left='50' width='312' height='16'>THE BLADES OF EXILE SCENARIO DESIGN CONTEST!</text>
</dialog>

10
rsrc/dialogs/help-distributing.xml
View File

@@ -7,18 +7,18 @@
<button name='okay' type='regular' top='284' left='403'>OK</button>
<pict type='dlog' num='16' top='6' left='6'/>
<text top='22' left='50' width='413' height='56'>
When you’ve completed your scenario, you probably want to give other people the chance to play through it.
It’s a big kick letting other people run around in your own fantasy world, get stuck at your puzzles, and kill your creations.
When you've completed your scenario, you probably want to give other people the chance to play through it.
It's a big kick letting other people run around in your own fantasy world, get stuck at your puzzles, and kill your creations.
</text>
<text top='79' left='50' width='414' height='54'>
The easiest way to release a scenario is to send it over to Spiderweb Software.
Go to www.spidweb.com.
There’s a scenario upload area there.
There's a scenario upload area there.
Alternately, mail it to us on disk (PO Box 85659, Seattle, WA 98145).
</text>
<text top='134' left='50' width='412' height='40'>
Before you send a scenario, however, be sure to read the License Agreement (in the file Blades of Exile License).
It says a lot of big no-no’s and describes your (and our) rights for your scenario.
It says a lot of big no-no's and describes your (and our) rights for your scenario.
</text>
<text top='175' left='50' width='418' height='54'>
Also look for information on the Blades of Exile Scenario Contest.
@@ -27,7 +27,7 @@
</text>
<text top='230' left='50' width='418' height='52'>
Finally, if your scenario is really, really good, we might like to sell it as a stand-alone.
If we’re interested, you can actually make money from your work!
If we're interested, you can actually make money from your work!
To take a shot at this, just send us your scenario before releasing it.
</text>
<text top='4' left='50' width='312' height='16'>BLADES OF EXILE - DISTRIBUTING YOUR SCENARIO</text>

4
rsrc/dialogs/help-editing.xml
View File

@@ -21,11 +21,11 @@
This section will give you a quick, easy start.
</text>
<text top='162' left='50' width='418' height='40'>
Once you’ve mastered the basics, using this section, skim through the documentation.
Once you've mastered the basics, using this section, skim through the documentation.
Unfortunately, this is not a program you will be able to get the best use out of without using the instructions.
</text>
<text top='203' left='50' width='418' height='41'>
Finally, if you’re stuck and need ideas, go to http://www.spidweb.com.
Finally, if you're stuck and need ideas, go to http://www.spidweb.com.
There is a Scenario Editor forum there, which has all kinds of hints, tips, and answers for better scenario design.
</text>
<text top='4' left='50' width='265' height='16'>BLADES OF EXILE - GETTING STARTED</text>

10
rsrc/dialogs/help-testing.xml
View File

@@ -8,7 +8,7 @@
<pict type='dlog' num='16' top='6' left='6'/>
<text top='22' left='50' width='413' height='52'>
If you want other people to play your scenario, it is vitally important that you test it.
Otherwise, lots of people might waste lots of hours playing a scenairo that is unwinnable or otherwise doesn’t work.
Otherwise, lots of people might waste lots of hours playing a scenairo that is unwinnable or otherwise doesn't work.
</text>
<text top='75' left='50' width='414' height='54'>
To run your scenario, copy it into the Blades of Exile Scenarios folder and start it using the Custom Scenario button on the game title screen.
@@ -16,14 +16,14 @@
</text>
<text top='130' left='50' width='412' height='53'>
When testing your scenario, one useful feature is debug mode.
While playing the game, type ‘D’.
While playing the game, type 'D'.
This will put you in Debug Mode.
Monsters will no longer move or attack you, and you will be able to play much faster.
</text>
<text top='184' left='50' width='417' height='54'>
When you make a change in a town, before testing it, be sure to leave the town and type ‘>’.
This causes the game to forget everything you’ve done in that town.
If you don’t do this, your corrections may not be remembered properly.
When you make a change in a town, before testing it, be sure to leave the town and type '>'.
This causes the game to forget everything you've done in that town.
If you don't do this, your corrections may not be remembered properly.
</text>
<text top='239' left='50' width='418' height='41'>
Finally, if you edit your scenario while playing in it, whenever you save a change go back to the game and reload your save file.

2
rsrc/dialogs/leave-scenario.xml
View File

@@ -4,7 +4,7 @@
<button name='okay' type='regular' top='84' left='251'>OK</button>
<pict top='8' left='8' type='dlog' num='16'/>
<text top='3' left='52' width='257' height='79'>
Selecting this option removes your party from the scenario they’re currently in.
Selecting this option removes your party from the scenario they're currently in.
All of their progress in that adventure is forgotten ...
if you want to play it again, you will need to start over from the very beginning.
</text>

2
rsrc/dialogs/make-scenario1.xml
View File

@@ -12,7 +12,7 @@
<text top='32' left='52' width='292' height='40'>
What is the name of your new scenario?
(max. length 30 characters) <br/>
Examples: ‘Hammer of Thor’, ‘Dragon’s Quest’
Examples: 'Hammer of Thor', 'Dragon's Quest'
</text>
<pict type='dlog' num='16' top='8' left='8'/>
<button name='cancel' type='regular' top='205' left='358' def-key='esc'>Cancel</button>

2
rsrc/dialogs/make-scenario2.xml
View File

@@ -33,7 +33,7 @@
<text top='295' left='117' width='181' height='15'>Number of small towns:</text>
<text size='large' top='331' left='59' width='235' height='16'>Place a starter town?</text>
<text top='348' left='70' width='383' height='53'>
If this option is selected, Town number 0 in your scenario is ‘Warrior’s Grove,’ a predesigned town with shops, inns, etc.
If this option is selected, Town number 0 in your scenario is 'Warrior's Grove,' a predesigned town with shops, inns, etc.
This is a GREAT place to start for beginner scenario designers, and lets you put off designing characters.
</text>
<text top='406' left='119' width='134' height='15'>Include starter town</text>

2
rsrc/dialogs/not-at-edge.xml
View File

@@ -3,5 +3,5 @@
<dialog defbtn='okay'>
<button name='okay' type='regular' top='37' left='256'>OK</button>
<pict type='dlog' num='16' top='6' left='6'/>
<text top='6' left='49' width='272' height='28'>You can’t place a sign or special encounter at the edge of an outdoor section.</text>
<text top='6' left='49' width='272' height='28'>You can't place a sign or special encounter at the edge of an outdoor section.</text>
</dialog>

2
rsrc/dialogs/set-start-loc.xml
View File

@@ -10,7 +10,7 @@
<text top='25' left='50' width='371' height='41'>
Enter the town the party will start the scenario in.
Also enter the x-y location in the town to place the party at.
Don’t forget to place that town somewhere in your scenario.
Don't forget to place that town somewhere in your scenario.
</text>
<text size='large' top='6' left='50' width='256' height='17'>Starting Location</text>
<text top='105' left='50' width='120' height='14'>Start location: X =</text>

2
rsrc/dialogs/text-dump-confirm.xml
View File

@@ -7,7 +7,7 @@
<text top='6' left='49' width='271' height='66'>
This features takes all of the text in your scenario
(all dialogue, all special messages, all signs, etc.)
and puts them into a file called ‘Scenario text’.
and puts them into a file called 'Scenario text'.
All this text can then be easily spell-checked and proofread.
</text>
<text top='73' left='49' width='271' height='29'>