Merge pull request #65 from Gallaecio/gl

[Galician Translation] Update
New bigmap and journey markers for DiD.
pot-update (preparing for 1.11.6)
Remove a C-style-cast.
bumped version to 1.11.6
pot-update, now really preparing for 1.11.6
post release version bump to 1.11.6+dev
Bumped XCode projfile version string
Use NULL instead of 0.
Refactor how game events are pumped.

game_events::pump() now records the events in the event queue at
the time it is called. This isolates those events from any that
might be fired within one of the events (e.g. with [fire_event]).
For an example of what was happening, see bug #21031.

Fixes bug #21031.
Have pump() no longer pump events raised while it is running.

The main way I know of for getting into this situation is hitting
the recursion maximum within pump(), and if that happens you probably
have runaway WML. So it should be better to move on instead of
continuing to process events.
(Normally, events raised within an event handler are pumped before
that event handler exits, so would not be affected by this change.)

I think the old behavior is an artifact of the old implementation,
but I'm making this a separate commit in case removing this causes
problems (easier to diagnose, especially if I'm not the one diagnosing).
Eliminate a variable by inlining a function call.
Bump Doxyfile version number
change introduction's reference to checking out wmllint from 1.4 branch, to wmllint-1.4
wmllint: bugfix missing "stringfreeze" long argument in getopt, and correct help description

According to the introduction, stringfreeze does *not* suppress the warning, and the code bears this out.

I wonder how often this option is actually used.
wmllint: add switch -K --known for suppresing consistency_check()

I used "inconsistency" for the actual variable name, because "known" seems more likely to be accidentally reused.

I pondered whether to allow the scenario check to go forward, but decided to just make a clean break.

Note that this does not prevent any of the information-gathering for the consistency check, just the check itself.

Why would you want to use this option? Of course, you should run the consistency check at some point. But if you simply want to recheck if you've fixed all the bugs in your campaign, you might not want to have wmllint slog through data/core again.
additions to wmllint help

Here's the rationale for these additions:

* There is so much focus on wmllint's role in conversion, that many people may not think of it as a validator also (I didn't). So often, stumped authors ask in the forums about problems that would have been fixed or pointed out if they'd run wmllint. I want to encourage awareness of wmllint as a validator.

* Folded a line to fit normal 80-width CLI.

* Help contained no mention of this rather redundant option.

* How many people don't realize that ESR's long introduction is there?

* Some users may not understand why they're being dumped back to wmllint's help.
wmllint: extend scenario check to include first scenario

Some newbie authors run into trouble at this point!
Restrict some .gitignore patterns to the root of the working tree

This is necessary so files with similar names which are actually
versioned and important aren't matched by these patterns, otherwise
only intended to match build output files.
Remove a .gitignore file that is not a .gitignore file

This thing was introduced in 492efa7b4bf687cada5d125d2fc4ab1c9ab097db
(from SVN r35965) due to a misapplication of a SVN property manipulation
command. I don't know what it is, but since it's part of the
decommissioned stats.w.o codebase and with the wrong filename to begin
with, I doubt anyone will miss it much.