Hi Gil,
*great*! Looking forward to your solution (and +1 for using a temporary directory allowing to do all
sorts of pre-process steps without affecting the svn version)!
---rony
On 03.07.2022 03:43, Gilbert Barmwater wrote:
On 7/2/2022 3:07 PM, Gilbert Barmwater wrote:
On 7/2/2022 2:48 PM, Rony G. Flatscher wrote:
When creating a pdf book the current script "docprep.cmd" copies the files from
"oorexx/trunc/oorexx/en-US" to "oorexx/trunc/{book}/en-US/Commons_Content". Not sure why this
happens as it should be possible to refer to "oorexx/en-US" files with relative paths (e.g.
changing "Common_Content" with "../../oorexx/en-US".
Indeed it is possible and I have implemented such a mechanism in the never-finished rewrite of
the scripts to use ooRexx. The coding was complete but the documentation wasn't and there was no
testing in non-Windows environments. The current mechanism was merely a work-around for things
done under the covers by Publican that would not break anything.
Also "docprep.cmd" copies "fop.cfg" to "oorexx/trunc/{book}/en-US/Commons_Content" and
"fo2pdf.cmd" then sets the environment variable "fopcfg" to point to it ("set
fopcfg=%docpath%\%whichdoc%\en-US\Common_Content\fop.cfg"). This would not be necessary if
having "fop.cfg" in "oorexx/trunc/oorexx/en-US" and setting "fopcfg" to point to it.
I can't remember off the top if I also addressed this in my newer version of
the scripts.
I have now verified that this issue is also handled by the new version.
In order to prevent the re-invention of the wheel, so to speak, I am going to commit the working
parts of the new scripts shortly. This will allow them to be studied and tested on non-Windows
systems by folks with expertise and resources to do so. As time permits, I will attempt to add
the documentation files as well. These files will be in their own folder and will not replace
anything currently available. They will simply be an addition, FWIW.
Would it be o.k. to change that (not copying anymore, changing the references accordingly in all
the books) or is there something non-obvious to "Common_Content"?
The scripts I have created take the working copy files, copy them to a separate folder where the
changes are made dynamically and then use those new files as input to the document build process.
This allows the files on SF in SVN to remain unchanged. One may argue that this is unnecessary
but I prefer to not make changes that might someday have to be undone. Just my philosophy on how
change management should be done. YMMV.
Gil B.
---rony
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
