Hi,
Two of the Windows help files are generated dynamically from within
openvpn-build/windows-nsis/openvpn.nsi:
FileOpen $R0 "$INSTDIR\config\README.txt" w
FileWrite $R0 "This directory should contain ${PACKAGE_NAME}
configuration files$\r$\n"
FileWrite $R0 "each having an extension of .${OPENVPN_CONFIG_EXT}$\r$\n"
FileWrite $R0 "$\r$\n"
FileWrite $R0 "When ${PACKAGE_NAME} is started as a service, a
separate ${PACKAGE_NAME}$\r$\n"
FileWrite $R0 "process will be instantiated for each configuration
file.$\r$\n"
FileClose $R0
--- snip ---
FileOpen $R0 "$INSTDIR\log\README.txt" w
FileWrite $R0 "This directory will contain the log files for
${PACKAGE_NAME}$\r$\n"
FileWrite $R0 "sessions which are being run as a service.$\r$\n"
FileClose $R0
I don't particularly like this approach - primarily because it hides
part of the OpenVPN documentation inside an installer script. It also
makes it harder to maintain a localized versions of the documentation,
and there could be issues with non-ascii characters.
Anyways, I think these help files are semi-useful at best, a bit like
the "tls-remote" warning. I think we could safely move their contents to
openvpn/INSTALL-win32.txt, or put them into static files under openvpn/doc.
Any opinions?
--
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc
irc freenode net: mattock
