All -
I have added all the missing sections to the sample rxsock document. In
addition I tweaked a bunch of things to make the documents more
polished.
There are still some page break problems but as I stated in a previous
email we will have to live with those.
The documents are available at
It sounds acceptable to me. Do the changes to the source files make them
compatible with various XML editing tools? Are there any WYSIWYG editors
that can be used to write the docs? To me, that was always the biggest
deficiency when writing docs...I spent way more time wrestling with the
markup
David,
It's acceptable to me. The reasons you stated for making the change seem valid.
I have the same general questions as Rick. With the additional
question of exactly what needs to be done to use Publican on Windows?
If it is fairly easy to set up on Windows, that adds a plus for me.
--
Yeah, working on Windows is also a major plus for me too.
Rick
On Thu, Aug 9, 2012 at 12:12 PM, Mark Miesfeld miesf...@gmail.com wrote:
David,
It's acceptable to me. The reasons you stated for making the change seem
valid.
I have the same general questions as Rick. With the additional
A brief search suggests the free XML Copy Editor might work with these
files. There's a Windows version too.
Rick
On Thu, Aug 9, 2012 at 12:12 PM, Mark Miesfeld miesf...@gmail.com wrote:
David,
It's acceptable to me. The reasons you stated for making the change seem
valid.
I have the
Editing the xml files should now be VERY easy with just about any xml
editor. Publican REQUIRES that all xml files have a DTD declaration at
the top. This should make every file acceptable to any xml editor.
Windows installation is very easy. the instructions are at
David,
Thanks for the info.
Just browsing through the User manual, I see that they have an
installer for Debian. That's another plus for me, I could never get
the current Doc build to work on any debian based system. The fact
that they have a .deb installer suggests that Publican will work on
Developer Mailing List
oorexx-devel@lists.sourceforge.net
Kopia:
Datum: torsdag, 09 augusti 2012 17:55
Ämne: Re: [Oorexx-devel] Possible Documentation Change
All -
I have added all the missing sections to the sample rxsock document. In
addition I tweaked a bunch of things to make the documents
-
Ursprungligt Meddelande:
Från: David Ashley w.david.ash...@gmail.com
Till: Open Object Rexx Developer Mailing List
oorexx-devel@lists.sourceforge.net
Kopia:
Datum: tisdag, 07 augusti 2012 23:02
Ämne: Re: [Oorexx-devel] Possible Documentation Change
I have refreshed the documents
All -
After over a year of struggle and tries, I finally got the Publican
system to compile one of our documents, The output is simply too good to
be true. The document looks outstanding!
You can find the document on the Build Server at
release_candidates/rxsock.pdf.
There are some problems
Interesting.
You can find the document on the Build Server at
release_candidates/rxsock.pdf.
URL for that?
Mike
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
Bit of a hiccough there :-), but thanks -- gotit.
-Original Message-
From: David Ashley [mailto:w.david.ash...@gmail.com]
Sent: 07 August 2012 19:48
To: Open Object Rexx Developer Mailing List
Subject: Re: [Oorexx-devel] Possible Documentation Change
http://http
2012 19:48
To: Open Object Rexx Developer Mailing List
Subject: Re: [Oorexx-devel] Possible Documentation Change
http://http://build.oorexx.org/builds/release-candidates/
David Ashley
On Tue, 2012-08-07 at 19:42 +0100, Mike Cowlishaw wrote:
Interesting.
You can find
David Ashley w.david.ash...@gmail.com wrote:
The document looks outstanding!
It's certainly polished, in places. I just looked at some pages at random
though and found one problem, where the shaded box around a syntax diagram
straddles a page break - for 5.18 SockRecv at the foot of page 24.
-Original Message-
From: David Ashley [mailto:w.david.ash...@gmail.com]
Sent: 07 August 2012 20:13
To: Open Object Rexx Developer Mailing List
Subject: Re: [Oorexx-devel] Possible Documentation Change
There are a lot of really cool things I like about the
Publican system
I put the HTML documentation in the same location on the Build Server.
It has some additional content not in the PDF. I will refresh everything
at the end of the day.
David Ashley
On Tue, 2012-08-07 at 20:42 +0100, Mike Cowlishaw wrote:
Definitely looks good at first skim through (will take a
I have refreshed the documents on the Build Server. I created a new
brand so now the doc references the correct license. I think this is
pretty close to as finished as I can make it.
As to the formatting issues, the Publican system uses CSS formatting. As
you may or may not know CSS is very weak
17 matches
Mail list logo
