> Am 16.11.2019 um 21:38 schrieb Erich Steinböck <[email protected]>:
>
>
> I have followed this howto
> The publican installation that we use to build ooRexx docs is be no means
> "standard", it's in fact something that has almost become completely lost.
> I believe the only way to install it is to follow what was discussed in
> thread https://sourceforge.net/p/oorexx/mailman/message/36501684/
> <https://sourceforge.net/p/oorexx/mailman/message/36501684/>
> Be warned - this is an major pain.
I know :-( bin there - done that
>
> If you could set out the commands you use to build the entire documentation
> The command is publican build --formats=pdf --langs=en-US
> --common_content=".." with the current directory being
> docs\trunk\{docname-eg-rexxref} (not in en_US)
> I don't build using the makefile, but use a Windows batch file, because there
> are so many issues - please read the thread.
>
Here is an example of how it looks like, it looks good/reasonable for some time
and then get stuck on the „brand stuff"
C:\Users\po\workspace\publican\publican-oorexx>publican build --formats=pdf
--langs=en-US --common_content=".."
Setting up en-US
Processing file tmp/en-US/xml_tmp/Feedback.xml ->
tmp/en-US/xml/Feedback.xml
Processing file tmp/en-US/xml_tmp/Legal_Notice.xml ->
tmp/en-US/xml/Legal_Notice.xml
Beginning work on en-US
Starting pdf
Use of uninitialized value in concatenation (.) or string at
Publican/Builder.pm line 947, <FH> line 13.
Use of uninitialized value in concatenation (.) or string at
Publican/Builder.pm line 947, <FH> line 13.
Use of uninitialized value in concatenation (.) or string at
Publican/Builder.pm line 955, <FH> line 13.
Use of uninitialized value in concatenation (.) or string at
Publican/Builder.pm line 955, <FH> line 13.
Can't locate required file: tmp/en-US/xml/brand_Info.xml at script/publican
line 884
But from what I have seen I am not THAT far away, am I? I tried to find the
Builder.pm file but it was not there. I could find it in a tempdir so I guess
it created as Publican go along.
I have the information I need for now, I will let you know if there is further
progress.
> Putting together a complete list of steps how to install this special
> publican would be handy, so you might want to take notes exactly how you did
> it (it's difficult because you'll stumble from issue to issue and lose track
> - at least this is what happened to Rick and me).
I have documented my steps as good as I could, If I can make it work I will
send them to you. But most likely moving to another tool, like Pandoc will be
more future proof.
>
> On Sat, Nov 16, 2019 at 8:55 PM P.O. Jonsson <[email protected]
> <mailto:[email protected]>> wrote:
>
>> Am 16.11.2019 um 20:27 schrieb Erich Steinböck <[email protected]
>> <mailto:[email protected]>>:
>>
>> Can I download the common contents from Sourceforge?
>> Just check out https://svn.code.sf.net/p/oorexx/code-0/docs/trunk
>> <https://svn.code.sf.net/p/oorexx/code-0/docs/trunk>
>> This checks out all ooRexx docs and also the oorexx directory, which is the
>> common content
>
> I just did, tnx.
>
>>
>> There are no *.spec files in the Publican directory at all.
>> Did you follow the thread from January how to install our Publican on
>> Windows?
>
> Yes, but I also had to overwrite some of the content to make it run, but the
> installation DO run and I can generate simple test files.
>
> I have followed this howto
>
> https://jfearn.fedorapeople.org/en-US/Publican/3.0/html/Users_Guide/index.html
>
> <https://jfearn.fedorapeople.org/en-US/Publican/3.0/html/Users_Guide/index.html>
>
> In chapter 5 there is the documentation of the Branding, I understood this to
> be mandatory
> Assuming the checked out documentation is in C:/workspace/oorexxdoc on a win
> machine, If you could set out the commands you use to build the entire
> documentation it would be great.
>
> I have not figured out how to use the makefile, any info is appreciated.
>
> Per Aspera ad Astra
>
>> _______________________________________________
>> Oorexx-devel mailing list
>> [email protected]
>> <mailto:[email protected]>
>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
>> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel>
>
> _______________________________________________
> Oorexx-devel mailing list
> [email protected] <mailto:[email protected]>
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel>
> _______________________________________________
> Oorexx-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
