[Freeciv-Dev] [bug #24871] Missing man pages in Windows distributions

Follow-up Comment #6, bug #24871 (project freeciv): > Ubuntu subsystem on win10 Yes, but I declined the MS offer to _"upgrade"_ my Windows 7 for various reasons: A five years old laptop with an AMD mobile Radeon. DirectX 11.1 is as far as this box ever gets, no DirectX 12. Sony wisely decided

[Freeciv-Dev] [bug #24871] Missing man pages in Windows distributions

Follow-up Comment #5, bug #24871 (project freeciv): > freeciv-client.6.in '.in' means it's input file for configure to produce final 'freeciv-client.6' at build time. It fills in things like current bug reporting address. ___ Reply to

[Freeciv-Dev] [bug #24871] Missing man pages in Windows distributions

Follow-up Comment #4, bug #24871 (project freeciv): >> The most bizarre idea I found with Google was to run docker to sandbox a Linux to run a man2pdf tool. I also tested some gnuwin32 groff.exe, but that was another FAIL. U have Ubuntu subsystem on win10 or something like that.

[Freeciv-Dev] [bug #24871] Missing man pages in Windows distributions

Follow-up Comment #3, bug #24871 (project freeciv): Allegedly groff can output HTML, and defaults to -tPS (postscript) output. I tested something claiming to be a polyglotman `rman.exe` in different versions. That was interesting, but sadly ended as FAIL, it did not grok UR..UE for an URL, and it

[Freeciv-Dev] [bug #24871] Missing man pages in Windows distributions

Follow-up Comment #2, bug #24871 (project freeciv): Man pages contain Unix-specific information, so would not be appropriate to distribute with Windows builds. Real problem is that the _PATH environment variables are only documented for Unix despite being applicable to Windows builds too. Which

[Freeciv-Dev] [bug #24871] Missing man pages in Windows distributions

URL: Summary: Missing man pages in Windows distributions Project: Freeciv Submitted by: dunnoob Submitted on: Sat 23 Jul 2016 06:44:55 PM UTC Category: None Severity: 3 -