mirror of
https://github.com/ganelson/inform.git
synced 2024-07-01 06:24:58 +03:00
quote fixes initial commit
This commit is contained in:
parent
6c42df5bc4
commit
45bf2689a8
|
@ -290,7 +290,7 @@ means "always display three times its normal size", whereas
|
|||
= (text as Blurb)
|
||||
picture "backdrop/png" scale min 1/10 max 8/1
|
||||
=
|
||||
means"you can display this anywhere between one tenth normal size and
|
||||
means "you can display this anywhere between one tenth normal size and
|
||||
eight times normal size, but if possible it ought to be just its normal
|
||||
size".
|
||||
|
||||
|
|
|
@ -65,7 +65,7 @@ int Symbols::perform_ifdef(text_stream *cond) {
|
|||
}
|
||||
|
||||
@ There is an expression grammar here, which we apply correctly if the
|
||||
condition is well-formed; if it"s a mess, we try to return 0, but don"t go
|
||||
condition is well-formed; if it's a mess, we try to return 0, but don't go
|
||||
to any trouble to report errors.
|
||||
|
||||
Any condition can be bracketed; otherwise we have the unary operator |^|
|
||||
|
|
|
@ -39,7 +39,7 @@ Otherwise, of course, we need to make an images folder alongside the HTML
|
|||
we produce. It will be called |images|, so relative to the HTML, the URL
|
||||
would then be |images/orange.png|.
|
||||
|
||||
However, it"s also possible that the book"s instructions tell us to use
|
||||
However, it's also possible that the book's instructions tell us to use
|
||||
images from an already-existing location instead.
|
||||
|
||||
Note that each time the URL of an image is looked up, we make a note of it,
|
||||
|
|
|
@ -446,7 +446,7 @@ see below.
|
|||
{*}A ball is in the bag.
|
||||
The bag is on the kitchen table.
|
||||
|
||||
This single sentence doesn"t make much of a simulation. Let"s add:
|
||||
This single sentence doesn't make much of a simulation. Let's add:
|
||||
|
||||
{**}The stitched seam is part of the ball.
|
||||
=
|
||||
|
|
|
@ -235,7 +235,7 @@ int PropertyInferences::either_or_state(inference_subject *subj, property *prn)
|
|||
}
|
||||
|
||||
@ And this is a variant which does not inherit: e.g. if the kind "bird" has
|
||||
the property "flightless" but Orville, an individual instance of"bird" has no
|
||||
the property "flightless" but Orville, an individual instance of "bird" has no
|
||||
inference about this property, then we would return |LIKELY_CE| if asked about
|
||||
"bird", but |UNKNOWN_CE| if asked Orville. The previous function would return
|
||||
|LIKELY_CE| to both because Orville ordinarily inherits from his kind.
|
||||
|
|
Loading…
Reference in a new issue