App G. Localization

[tajmone]

Polish text and add new contents to Appendix G. Localization:

• Provide some general guidelines on how to approach localizing Alan to new languages.
• Explain how to exploit noise Player-Words and Synonyms in i18n to handle articles variations in languages with grammatical gender.
• Add "Useful Links" section at the end.
• Annotate problems and TODOs (via comments).
• Update "G.5. Word Order" (TBD): provide answers to annotated questions regarding the possibility of using Syntaxes with param in first position. Update TBD admonition note accordingly. (See #61)
• Rebuild HTML & PDF Manual.

Change document revremark to "Beta7 Ed. work".

---

Live Preview links

These links point to the AppG-i18n-squash branch, and will work even after force-pushing to the PR:

• HTML Manual
• PDF Manual

[tajmone]

App. G is far from complete, but at least this commit provides some new contents on the topic.

I'd like to keep this squashed as a single-commit, so if we do make some further changes I'll like to squash all commits before merging into branch Beta7-prep.

I thought that adding to this Appendix a "Useful Links" section made sense, and started by providing links to the Alan Italian project, the sections on natural language of the Inform Designer Manual, as well as some key linguistic topics on Wikipedia.

The creations of a links section prompted me to fix the XSL Template so that no URL-footnotes would be created for inline-links (See #64). That might have been useful for printed books, where links are not actively click-able, but I thought that ultimately the PDF docs of this project are destined for screen-reading only (if we ever need to cater for a printable edition, we can always find a workaround for preserving URL footnotes in a sperate PDF).

---

• [ ] Before merging, squash into a single commit any further commits from reviewing.
• [ ] After merging:
  • [ ] delete AppG-i18 branch.
  • [ ] delete AppG-i18n-squash branch.
  • [ ] review and merge PR #69.

[tajmone]

Branch Info Not Updating After Force Push

@thoni56, I've rebased the branch of this PR on the cleaned up beta7-prep branch: but for some reason the info of this PR hasn't been updated after my forced push — it's still showing 29 commits and 154 changed files, whereas the new branch has only 1 commit and 4 changed files.

This is the first PR that should be merged (for some reason that I can't remember, but have annotated it so), so that after we can then rebase the other PRs on the updated beta7-prep.

I'm not sure what to do with the fact that GH is not updating the branch info... Could this lead to problems? Is the PR somehow stuck to previous versions of the branch, and ignoring the force push?

Should we just open a new PR from the updated branch?

[tajmone]

Maybe I should just merge this branch manually, and close the PR — after all, it was reviewed and approved.

I just have a bad feeling about the outdated branch info, and would rather fix this with a manual merge.

[tajmone]

PR Manually Merged

Due to the problems with the PR info not being updated after the force push, I've opted to manually merge the PR branch and close this PR.

The issue of GH not updating is a known problem, so in this case I deemed it safer to drop the PR procedure.