It has been suggested that I split off the build process so that the
archetecture dependant parts of the program can be built without building
the
documentation each time.
If I were you, I'd just convert the .doc to a .pdf. Likewise, your
programmer can do that in seconds with a
On Thursday, February 09, 2012 04:37:55 PM Savvas Radevic wrote:
If I were you, I'd just convert the .doc to a .pdf. Likewise, your
programmer can do that in seconds with a
pluginhttp://www.microsoft.com/download/en/details.aspx?id=7(and
file save as.. or export?) or a
On Thu, Feb 09, 2012 at 05:21:55PM -0600, Paul Elliott wrote:
Unfortunately the .doc file is the source, so everything must be rebuilt from
source i.e. the .doc file as part of the build process.
What kind of documentation are we talking about? If it’s just a reference
manual of some sort,
On Thu, 09 Feb 2012 16:00:55 -0600, Paul Elliott wrote:
The untimate source of my project is a windows programer who GPLed. He
thought
it would be a good idea to write the documentation in windows word .doc file!
Bad move.
The only free program that I can find to convert this document
4 matches
Mail list logo
