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 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 http://build.oorexx.org/builds/release-candidates/. Publican is a really nice system once you get past the initial learning curve. And now that I know how to deal with it it will be easy help others get started. The other nice thing about the system is that it runs on both Windows and Linux without any source code changes. The whole point with this exercise is that I am very concerned about the future of the DocBook/DSSL system we use now. DSSL is not being maintained and everyone is moving in other directions. Publican offers the advantages of it being a DocBook/CSS system, it is maintained by Red Hat, it is their strategic direction, and it is portable across multiple platforms including Windows. And last, it does not take much effort to fix up our documents to conform to Publican. So please let me know if this is an acceptable direction for us to take. David Ashley ooRexx Team -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Possible Documentation Change
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 than I did writing the actual words. If I could write the text without having to deal with the markup, things would go a lot faster. Rick On Thu, Aug 9, 2012 at 11:55 AM, David Ashley w.david.ash...@gmail.comwrote: 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 http://build.oorexx.org/builds/release-candidates/. Publican is a really nice system once you get past the initial learning curve. And now that I know how to deal with it it will be easy help others get started. The other nice thing about the system is that it runs on both Windows and Linux without any source code changes. The whole point with this exercise is that I am very concerned about the future of the DocBook/DSSL system we use now. DSSL is not being maintained and everyone is moving in other directions. Publican offers the advantages of it being a DocBook/CSS system, it is maintained by Red Hat, it is their strategic direction, and it is portable across multiple platforms including Windows. And last, it does not take much effort to fix up our documents to conform to Publican. So please let me know if this is an acceptable direction for us to take. David Ashley ooRexx Team -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Possible Documentation Change
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. -- Mark Miesfeld On Thu, Aug 9, 2012 at 8:55 AM, David Ashley w.david.ash...@gmail.com wrote: 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 http://build.oorexx.org/builds/release-candidates/. Publican is a really nice system once you get past the initial learning curve. And now that I know how to deal with it it will be easy help others get started. The other nice thing about the system is that it runs on both Windows and Linux without any source code changes. The whole point with this exercise is that I am very concerned about the future of the DocBook/DSSL system we use now. DSSL is not being maintained and everyone is moving in other directions. Publican offers the advantages of it being a DocBook/CSS system, it is maintained by Red Hat, it is their strategic direction, and it is portable across multiple platforms including Windows. And last, it does not take much effort to fix up our documents to conform to Publican. So please let me know if this is an acceptable direction for us to take. David Ashley ooRexx Team -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Possible Documentation Change
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 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. -- Mark Miesfeld On Thu, Aug 9, 2012 at 8:55 AM, David Ashley w.david.ash...@gmail.com wrote: 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 http://build.oorexx.org/builds/release-candidates/. Publican is a really nice system once you get past the initial learning curve. And now that I know how to deal with it it will be easy help others get started. The other nice thing about the system is that it runs on both Windows and Linux without any source code changes. The whole point with this exercise is that I am very concerned about the future of the DocBook/DSSL system we use now. DSSL is not being maintained and everyone is moving in other directions. Publican offers the advantages of it being a DocBook/CSS system, it is maintained by Red Hat, it is their strategic direction, and it is portable across multiple platforms including Windows. And last, it does not take much effort to fix up our documents to conform to Publican. So please let me know if this is an acceptable direction for us to take. David Ashley ooRexx Team -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Possible Documentation Change
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 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. -- Mark Miesfeld On Thu, Aug 9, 2012 at 8:55 AM, David Ashley w.david.ash...@gmail.com wrote: 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 http://build.oorexx.org/builds/release-candidates/. Publican is a really nice system once you get past the initial learning curve. And now that I know how to deal with it it will be easy help others get started. The other nice thing about the system is that it runs on both Windows and Linux without any source code changes. The whole point with this exercise is that I am very concerned about the future of the DocBook/DSSL system we use now. DSSL is not being maintained and everyone is moving in other directions. Publican offers the advantages of it being a DocBook/CSS system, it is maintained by Red Hat, it is their strategic direction, and it is portable across multiple platforms including Windows. And last, it does not take much effort to fix up our documents to conform to Publican. So please let me know if this is an acceptable direction for us to take. David Ashley ooRexx Team -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Possible Documentation Change
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 http://jfearn.fedorapeople.org/en-US/Publican/2.7/html/Users_Guide/chap-Users_Guide-Installing_Publican.html#sect-Users_Guide-Installing_Publican-Windows_operating_systems. I can help you with the terminology. There are only about 3-4 terms that you have to understand and some things about how the system works. Then you can be off and running. What I will do is to create a snapshot of the documentation trunk and set it up on SVN. As I work through converting each document we can coordinate the conversion. I will build a sandbox today or tomorrow. David Ashley On Thu, 2012-08-09 at 12:22 -0400, Rick McGuire wrote: 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 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. -- Mark Miesfeld On Thu, Aug 9, 2012 at 8:55 AM, David Ashley w.david.ash...@gmail.com wrote: 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 http://build.oorexx.org/builds/release-candidates/. Publican is a really nice system once you get past the initial learning curve. And now that I know how to deal with it it will be easy help others get started. The other nice thing about the system is that it runs on both Windows and Linux without any source code changes. The whole point with this exercise is that I am very concerned about the future of the DocBook/DSSL system we use now. DSSL is not being maintained and everyone is moving in other directions. Publican offers the advantages of it being a DocBook/CSS system, it is maintained by Red Hat, it is their strategic direction, and it is portable across multiple platforms including Windows. And last, it does not take much effort to fix up our documents to conform to Publican. So please let me know if this is an acceptable direction for us to take. David Ashley ooRexx Team -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the
Re: [Oorexx-devel] Possible Documentation Change
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 debian based systems. -- Mark Miesfeld On Thu, Aug 9, 2012 at 9:44 AM, David Ashley w.david.ash...@gmail.com wrote: 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 http://jfearn.fedorapeople.org/en-US/Publican/2.7/html/Users_Guide/chap-Users_Guide-Installing_Publican.html#sect-Users_Guide-Installing_Publican-Windows_operating_systems. I can help you with the terminology. There are only about 3-4 terms that you have to understand and some things about how the system works. Then you can be off and running. What I will do is to create a snapshot of the documentation trunk and set it up on SVN. As I work through converting each document we can coordinate the conversion. I will build a sandbox today or tomorrow. David Ashley On Thu, 2012-08-09 at 12:22 -0400, Rick McGuire wrote: 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 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. -- Mark Miesfeld On Thu, Aug 9, 2012 at 8:55 AM, David Ashley w.david.ash...@gmail.com wrote: 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 http://build.oorexx.org/builds/release-candidates/. Publican is a really nice system once you get past the initial learning curve. And now that I know how to deal with it it will be easy help others get started. The other nice thing about the system is that it runs on both Windows and Linux without any source code changes. The whole point with this exercise is that I am very concerned about the future of the DocBook/DSSL system we use now. DSSL is not being maintained and everyone is moving in other directions. Publican offers the advantages of it being a DocBook/CSS system, it is maintained by Red Hat, it is their strategic direction, and it is portable across multiple platforms including Windows. And last, it does not take much effort to fix up our documents to conform to Publican. So please let me know if this is an acceptable direction for us to take. David Ashley ooRexx Team -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net
Re: [Oorexx-devel] Possible Documentation Change
Looked at the latest created rxsock pdf and see that, every odd page number, text is more indented then the text on even page numbers ! Any thoughts about the font used ? /hex - 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: 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 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 http://build.oorexx.org/builds/release-candidates/. Publican is a really nice system once you get past the initial learning curve. And now that I know how to deal with it it will be easy help others get started. The other nice thing about the system is that it runs on both Windows and Linux without any source code changes. The whole point with this exercise is that I am very concerned about the future of the DocBook/DSSL system we use now. DSSL is not being maintained and everyone is moving in other directions. Publican offers the advantages of it being a DocBook/CSS system, it is maintained by Red Hat, it is their strategic direction, and it is portable across multiple platforms including Windows. And last, it does not take much effort to fix up our documents to conform to Publican. So please let me know if this is an acceptable direction for us to take. David Ashley ooRexx Team -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Possible Documentation Change
Personally I don't like the font used in the text parts and the lack of page-breaks. Also the class object pictures is to low-res compared to the running text. Maybe I have read to many IBM manuals, that has an easy reading font and mostly, page-breaks at a suitable place. /hex - 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 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 in formatting multi-page output for PDF documents. This because it primary use is for HTML pages which have no multi-page concerns. The result can be some odd page breaks in your PDF outout. There is not much you can do about this and anything you do will probably make the situation worse either now or in the future. But for the most part we can live with these issues as long as the content does not go missing completely. David Ashley On Tue, 2012-08-07 at 20:41 +0100, Jeremy Nicoll - ml sourceforge wrote: 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. Similarly (though not as bad) see 7.2.16 state at the foot of p55. And at the foot of p36 there's a where that's not connected with the text it introduces. I've never used XML or DocBook, but did long ago use IBM's DCF/Script package, writing macros for quite complex 3-pass processing of documents (where the macros did different things on different passes). Script had control words (dot commands) for bracketing sections of text that should not be broken up, and others eg to force a page break if there was insufficient space at the foot of one page to start a new section of a document. (These things only got used if one wrote macros that issued them with appropriate arguments in appropriate places.) The output from this system looks a lot like it's created nice looking text but just poured it onto a series of pages without taking page-breaks into account. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
[Oorexx-devel] Possible Documentation Change
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 with this document. 1. I used the common brand in compiling the document. This refers to the Creative Commons license so you will see that referenced in the document. We will need to create our own brand to refer to the CPL. 2. Not all the content from the original document is there. That was just me being lazy. 3. Some of the images are not showing up. I need to look into that. If you are interested in what Publican is and how it relates to Docbook refer to https://fedorahosted.org/publican/. Please let me know what you think. David Ashley ooRexx Team -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Possible Documentation Change
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 threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Possible Documentation Change
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://build.oorexx.org/builds/release-candidates/ David Ashley On Tue, 2012-08-07 at 19:42 +0100, Mike Cowlishaw wrote: 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 threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Possible Documentation Change
Very handsome! I particularly like the note headers. Well done David! On 7 August 2012 19:53, Mike Cowlishaw m...@speleotrove.com wrote: 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://build.oorexx.org/builds/release-candidates/ David Ashley On Tue, 2012-08-07 at 19:42 +0100, Mike Cowlishaw wrote: 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 threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Possible Documentation Change
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. Similarly (though not as bad) see 7.2.16 state at the foot of p55. And at the foot of p36 there's a where that's not connected with the text it introduces. I've never used XML or DocBook, but did long ago use IBM's DCF/Script package, writing macros for quite complex 3-pass processing of documents (where the macros did different things on different passes). Script had control words (dot commands) for bracketing sections of text that should not be broken up, and others eg to force a page break if there was insufficient space at the foot of one page to start a new section of a document. (These things only got used if one wrote macros that issued them with appropriate arguments in appropriate places.) The output from this system looks a lot like it's created nice looking text but just poured it onto a series of pages without taking page-breaks into account. -- Jeremy Nicoll - my opinions are my own -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Possible Documentation Change
Definitely looks good at first skim through (will take a more careful look in the morning). I guess the 'proof of the pudding' would be: can the modified source still produce good output with other formatters, or does this make [oo]Rexx documentation dependent on the one particular system? Mike -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. And the defaults for the systems are very nice. But it took a while to get everything organized like the system requires. Here are some of the changes I had to make to the original source. 1. All the images were moved to their own subdirectory. That was not required but it was highly suggested. It certainly cleaned up the tree. 2. Every imagedata tag had to have multiple changes. All the changes were not unexpected as the old DSSL system was not fully compliant concerning the imagesdata tag. 3. I had to add a new declaration header to every xml file. This also was not unexpected as all the xml file have to have a declaration in the Publican system. 4. Had to reorganize the files somewhat. This was the hardest part but once it is done the source is much better organized. And now that I know what I am doing the rest of the documents will be much easier. David Ashley On Tue, 2012-08-07 at 19:59 +0100, Sahananda (Jon) Wolfers wrote: Very handsome! I particularly like the note headers. Well done David! -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Possible Documentation Change
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 more careful look in the morning). I guess the 'proof of the pudding' would be: can the modified source still produce good output with other formatters, or does this make [oo]Rexx documentation dependent on the one particular system? Mike -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
Re: [Oorexx-devel] Possible Documentation Change
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 in formatting multi-page output for PDF documents. This because it primary use is for HTML pages which have no multi-page concerns. The result can be some odd page breaks in your PDF outout. There is not much you can do about this and anything you do will probably make the situation worse either now or in the future. But for the most part we can live with these issues as long as the content does not go missing completely. David Ashley On Tue, 2012-08-07 at 20:41 +0100, Jeremy Nicoll - ml sourceforge wrote: 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. Similarly (though not as bad) see 7.2.16 state at the foot of p55. And at the foot of p36 there's a where that's not connected with the text it introduces. I've never used XML or DocBook, but did long ago use IBM's DCF/Script package, writing macros for quite complex 3-pass processing of documents (where the macros did different things on different passes). Script had control words (dot commands) for bracketing sections of text that should not be broken up, and others eg to force a page break if there was insufficient space at the foot of one page to start a new section of a document. (These things only got used if one wrote macros that issued them with appropriate arguments in appropriate places.) The output from this system looks a lot like it's created nice looking text but just poured it onto a series of pages without taking page-breaks into account. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
