ifhub/inform7
1
0
Fork 0
mirror of https://github.com/ganelson/inform.git synced 2024-06-28 21:14:57 +03:00
Code Issues Projects Releases Wiki Activity

name update

Browse source
This commit is contained in:
Zed Lopez 2023-07-27 07:26:20 -07:00
parent db88b3da8d
commit 723e2bcb89
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
resources/Documentation/The Recipe Book.txt
View file

@ -40,7 +40,7 @@ Thanks also go to ^{@Nick Montfort} for several conversations during the develop
^{@Jeff Nyman} provided extensive feedback about using <i>Writing with Inform</i> in workshops of aspiring IF authors from both programming and conventional fiction writing backgrounds. His observations about the concerns of conventional writers first encountering IF were especially useful, and had a great influence on the organization of the <i>Recipe Book</i>. While the results may not meet all the needs he identified, we hope to have taken a step in the right direction.
A few examples were contributed by denizens of rec.arts.int-fiction: ^{@Jesse McGrew}, ^{@Jon Ingold}, ^{@Mike Tarbert}, ^{@Eric Rossing}, and ^{@Kate McKee} offered such elegant implementations of various tasks that we have folded their contributions (with permission) into the <i>Recipe Book</i>.
A few examples were contributed by denizens of rec.arts.int-fiction: ^{@Tara McGrew}, ^{@Jon Ingold}, ^{@Mike Tarbert}, ^{@Eric Rossing}, and ^{@Kate McKee} offered such elegant implementations of various tasks that we have folded their contributions (with permission) into the <i>Recipe Book</i>.
Finally, these pages owe much to the questions and suggestions of Inform users on rec.arts.int-fiction and ifMUD.

2
resources/Documentation/Writing with Inform.txt
View file

@ -17409,7 +17409,7 @@ When Inform needs to find an extension, it looks here first, then in the install
Extensions are identified by author and by name, so that a given author can produce their own range of extensions, and need only ensure that these are named differently from each other. If John Smith and Mary Brown each want to write an extension called "Following People", there is no conflict.
The name of an extension, and of an author, should be written in Sentence Capitalisation: that is, upper case for the first letter in each word. (Inform uses this to minimise problems on machines where filenames are read with case sensitivity.) It is permitted for author names to include upper-case letters within words, as with the "G" in "^{@Jesse McGrew}". In general it is best to avoid accented or unusual letters in titles and author names, but the standard ISO Latin-1 characters should be allowed - for instance,
The name of an extension, and of an author, should be written in Sentence Capitalisation: that is, upper case for the first letter in each word. (Inform uses this to minimise problems on machines where filenames are read with case sensitivity.) It is permitted for author names to include upper-case letters within words, as with the "G" in "^{@Tara McGrew}". In general it is best to avoid accented or unusual letters in titles and author names, but the standard ISO Latin-1 characters should be allowed - for instance,
Étude Pour La Fênetre by Françoise Gauß begins here.