Add link to combat instructions for solo/coop scenarios

[captain-yoshi]

Fixes #728.

[captain-yoshi]

Rebased with master. Is there something to add for localisation ?

[qwrtln]

Rebased with master. Is there something to add for localisation ?

Yes, you have to run po4a po4a.cfg. It will update the localization files.

[captain-yoshi]

Got this errror when running:

$ po4a po4a.cfg
sections/ai_rules.tex:53: (po4a::tex)
               unmatched end of environment 'multicols*'
po4a: Couldn't determine the input document's charset. Please specify it on the command line. (non-ASCII char at sections/all_map_locations.tex:38)

The non-ASCII char is the em dash from all_map_locations.tex at line 38

    \svg{gold}/\svg{building_materials}/\svg{valuablegreater} —

What would be the correct charset to use ?
https://linux.die.net/man/1/po4a

[qwrtln]

We're using Unicode here, since LaTeX supports it at least since 2018. The workflow uses version po4a==0.73. If your distro ships with po4a<=0.69, you might encounter problems. You have two options:

1. Download the latest po4a from GitHub: https://github.com/mquinson/po4a
2. Create a PR in your fork targeting combat-setup branch, and type a comment po4a commit in there. A bot in the workflow will commit the necessary changes. After merging them, they'll be reflected here.

[qwrtln]

Charset fixed by #731

[qwrtln]

It shouldn't have changed that many files. As #731 was merged, try removing the latest commit, rebasing, and running again.

[qwrtln]

You probably still have local po4a version mismatch (which one do you have, BTW?). Try the workflow approach.

[captain-yoshi]

Removed, rebased and run po4a cfg. It still seem to change a lot of files Using version po4a version 0.74-alpha. Maybe I should use a release version instead. What version do you use ?

[qwrtln]

0.73

[captain-yoshi]

Had an error when building po4a but showed new version when installed...:

Malformed encoding while writing to file /home/captain-yoshi/ws/dev/po4a/blib/man/ca/man3/Locale::Po4a::Xml.3pm.pod with charset UTF-8: "\x{fffd}" does not map to UTF-8 at lib/Locale/Po4a/TransTractor.pm line 
542.
If UTF-8 is not the expected charset, you need to configure the right one with with --localized-charset or other similar flags.
Close with partial character at lib/Locale/Po4a/TransTractor.pm line 566.
Died at Po4aBuilder.pm line 191.

Anyway generated the localisation update through the action workflow and rebased.

[captain-yoshi]

The CS printing gives 57 pages instead of 56 which might be normal. The strange thing is that this PR section has not been translated ?

[qwrtln]

That's what po4a does. If there's an update to a part of the text (the bullet points in this case), it marks the translation as fuzzy, and uses the original as fallback. Every language will do that, that's why your change is rolled out to 8 po files. I think it should be parked until 1.3 release, as it's not a critical change, so as not to trouble translators.