Shorewall devel - Dec 2003 - Re: Shorewall-devel Digest, Vol 11, Issue 4

Hiya,

> Ok with me -- if I get too frustrated with DocBook, I''ll just
start
> editing the HTML again.
> 
> -Tom
> 
Well the fact that VIM is supported by Docbook is a plus .. But I still
think the Wiki idea is well .. Lets get the doc at a CVS and Docbook
stage .. Walking before running .. plz plz .. 

Francesca

PS: I have thrown Windoze out the Window here (Pardon The Pun Bill) and
switched to Linux on my Laptop ... So I am starting over .. But amazing
.. its like in Turbo mode .. Like using VI (Designed For Lazy
Developers) .. :-)

I too have mentioned my hesitation with a wiki.
Tom has done a wonderful job with the existing site.
I wonder what the requirements were that indicate a wiki based system is 
the answer?

But don''t get me wrong, I am very glad to see other people helping Tom 
improve Shorewall and the site.

Thanks,

-- 
Steve Herber	herber@thing.com		work: 206-221-7262
Security Engineer, UW Medicine, IT Services	home: 425-454-2399

On Sun, 7 Dec 2003, Francesca C. Smith wrote:
> Hiya,
> 
> 
> > Ok with me -- if I get too frustrated with DocBook, I''ll just
start
> > editing the HTML again.
> > 
> > -Tom
> > 
> 
> Well the fact that VIM is supported by Docbook is a plus .. But I still
> think the Wiki idea is well .. Lets get the doc at a CVS and Docbook
> stage .. Walking before running .. plz plz .. 
> 
> Francesca
> 
> PS: I have thrown Windoze out the Window here (Pardon The Pun Bill) and
> switched to Linux on my Laptop ... So I am starting over .. But amazing
> .. its like in Turbo mode .. Like using VI (Designed For Lazy
> Developers) .. :-)
> 
> _______________________________________________
> Shorewall-devel mailing list
> Shorewall-devel@lists.shorewall.net
> https://lists.shorewall.net/mailman/listinfo/shorewall-devel
>

On Sun, 7 Dec 2003, Steve Herber wrote:
> I too have mentioned my hesitation with a wiki.
> Tom has done a wonderful job with the existing site.
> I wonder what the requirements were that indicate a wiki based system is 
> the answer?
> 
> But don''t get me wrong, I am very glad to see other people helping
Tom
> improve Shorewall and the site.
> 
I too am glad that Alex and Mike have offered to help. But I don''t
fully
understand why we need to change the format of the documentation. Mike 
and Alex are also proponents of converting all of the documentation to 
DocBook XML.

This reminds me of 30 years ago when we typeed marked-up text then ran
that text through a translator to produce the final (printed) product
(then went back and modified the marked-up text and translated; still
didn''t look right, ...).

The first time that I used FrameMaker, I thought I had died and gone to
heaven; no more galley and it''s successors. What I saw on the screen
was
what my document looked like; it was like magic. Now the XML juggernaught
seems to be trying to convince us that the old model is somehow new.

The tools don''t appear to be mature yet so there is a significant
effort
required to re-learn to do something that is already intuitive using
existing WYSIWYG tools (XXE is *not* intuitive, at least to me).

Hopefully this old troglodyte is missing something. But then maybe Alex 
and Mike should understand that trying to teach 60-year old dogs new 
tricks doesn''t always work either...

-Tom
-- 
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ teastep@shorewall.net

On Sun, 2003-12-07 at 19:50, Steve Herber wrote:
> I too have mentioned my hesitation with a wiki.
> Tom has done a wonderful job with the existing site.
> I wonder what the requirements were that indicate a wiki based system is 
> the answer?
Steve,
Wiki''s are a substitute for CVS and DocBook. They lower the bar to
contributions. I''m only recommending a Wiki for the FAQs that Tom
stated
the community should support.

-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs

On Mon, 2003-12-08 at 08:53, Mike Noyes wrote:
> On Sun, 2003-12-07 at 19:50, Steve Herber wrote:
> > I too have mentioned my hesitation with a wiki.
> > Tom has done a wonderful job with the existing site.
> > I wonder what the requirements were that indicate a wiki based system
is
> > the answer?
> 
> Steve,
> Wiki''s are a substitute for CVS and DocBook. They lower the bar to
> contributions. I''m only recommending a Wiki for the FAQs that Tom
stated
> the community should support.
Example TOC [HomePage]
http://wiki.rettc.com/index.php/ShorewallFaqFormat

Example FAQ 1
http://wiki.rettc.com/index.php/BetaFaqNumber1

    Note: the new DlStyleTables model in PhpWiki is less than stellar.
    :-(

-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs

Please note that this wiki will be down until after the 14th.
Sorry,
Alex

Mike Noyes wrote:
> On Mon, 2003-12-08 at 08:53, Mike Noyes wrote:
> 
>>On Sun, 2003-12-07 at 19:50, Steve Herber wrote:
>>
>>>I too have mentioned my hesitation with a wiki.
>>>Tom has done a wonderful job with the existing site.
>>>I wonder what the requirements were that indicate a wiki based
system is
>>>the answer?
>>
>>Steve,
>>Wiki''s are a substitute for CVS and DocBook. They lower the bar
to
>>contributions. I''m only recommending a Wiki for the FAQs that
Tom stated
>>the community should support.
> 
> 
> Example TOC [HomePage]
> http://wiki.rettc.com/index.php/ShorewallFaqFormat
> 
> Example FAQ 1
> http://wiki.rettc.com/index.php/BetaFaqNumber1
> 
>     Note: the new DlStyleTables model in PhpWiki is less than stellar.
>     :-(
>

On Mon, 2003-12-08 at 12:07, Alex Martin wrote:
> Please note that this wiki will be down until after the 14th.
Alex,
It''s working now. Did it self repair?

-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs

Hmm. It is working. Have you been populating the wiki?
Excellent. As long as it holds up till next week, I guess this will be a 
  fine host.

Have you looked at batch exportation from (cvs, xml, html, etc) into a wiki?

I have not considered this. Manual or not, I think that this is a 
reasonable way to mirror the cvs faq and allow the public to make 
additions / suggestions to be considered for integration into the cvs tree.

-Alex


Mike Noyes wrote:
> On Mon, 2003-12-08 at 12:07, Alex Martin wrote:
> 
>>Please note that this wiki will be down until after the 14th.
> 
> 
> Alex,
> It''s working now. Did it self repair?
>

On Mon, 2003-12-08 at 12:41, Alex Martin wrote:
> Hmm. It is working. Have you been populating the wiki?
Alex,
Yes. I ran into the problem on Fri. when trying to add FAQ1 to
ShorewallFaqFormat. PhpWiki apparently does content checking, and found
a similar page. It then refused to make the new one, and hung. Strange.

    RecentEdits
    http://wiki.rettc.com/index.php/RecentEdits
> Excellent. As long as it holds up till next week, I guess this will be a 
>   fine host.
> 
> Have you looked at batch exportation from (cvs, xml, html, etc) into a
wiki?
Standards for XML im/export are being worked on. wt2db is available for
MediaWiki export. Moinmoin can display XML (note: there are security
issues with this feature).

    Wiki Text to DocBook
    http://www.tldp.org/wt2db/
    http://www.tldp.org/downloads/wt2db-0.6.tar.gz

    Wikitext standard
    http://meta.wikipedia.org/wiki/Wikitext_standard
    
    Wikipedia DTD
    http://meta.wikipedia.org/wiki/Wikipedia_DTD

> I have not considered this. Manual or not, I think that this is a 
> reasonable way to mirror the cvs faq and allow the public to make 
> additions / suggestions to be considered for integration into the cvs tree.
Agreed.

-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs

On Sun, 2003-12-07 at 20:59, Tom Eastep wrote:
> I too am glad that Alex and Mike have offered to help. But I don''t
fully
> understand why we need to change the format of the documentation. Mike 
> and Alex are also proponents of converting all of the documentation to 
> DocBook XML.
WhyDocBook
http://www.docbook.org/wiki/moin.cgi/WhyDocBook
> This reminds me of 30 years ago when we typeed marked-up text then ran
> that text through a translator to produce the final (printed) product
> (then went back and modified the marked-up text and translated; still
> didn''t look right, ...).
> 
> The first time that I used FrameMaker, I thought I had died and gone to
> heaven; no more galley and it''s successors. What I saw on the
screen was
> what my document looked like; it was like magic. Now the XML juggernaught
> seems to be trying to convince us that the old model is somehow new.
Tom,
I think I understand your hesitation now. You remember the old pre press
systems like TeX.
> The tools don''t appear to be mature yet so there is a significant
effort
> required to re-learn to do something that is already intuitive using
> existing WYSIWYG tools (XXE is *not* intuitive, at least to me).
Q: What happens in a WYSIWYG environment when you change the target
device?

    A: The document format changes, and rarely for the better.
    

The tools are mature, but I didn''t think you wanted to pay for
something
like FrameMaker. The version below has supported DocBook for a long
time.

    Adobe FrameMaker + SGML
    http://www.adobe.com/products/framemaker/sgmlkeyfeature7.html

> Hopefully this old troglodyte is missing something. But then maybe Alex 
> and Mike should understand that trying to teach 60-year old dogs new 
> tricks doesn''t always work either...
Yes. XML is different from the old pre press systems in a major way. It
separates content from presentation. Think of XML as a database for
content, and XSL as an abstraction layer that is able to serve many
clients.

Here is a VERY SIMPLE illustration of the benefits.

HTML Example:
    Original:
        <h1>abc</h1>
        <p>abc</p>
        <h2>def</h2>
        <p>def</p>
    Edit:
        <h1>def</h1>
        <p>def</p>
        <h2>abc</h2>
        <p>abc</p>
        
DocBook XML Example:
Original:
    <section>
    <title>abc</title>
    <para>abc</para>
        <section>
        <title>def</title>
        <para>def</para>
        </section>
    </section>

Edit:
    <section>
    <title>def</title>
    <para>def</para>
        <section>
        <title>abc</title>
        <para>abc</para>
        </section>
    </section>


Note: all that changed in the DocBook example was content position,
while in the HTML example a change to presentation was required.


An example of a whole website built from XML with a simple make script.

http://cvs.sourceforge.net/viewcvs.py/docbook/sourceforge-webpages/
    Result: http://docbook.sourceforge.net/

-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs

On Mon, 2003-12-08 at 09:30, Mike Noyes wrote:
> XML is different from the old pre press systems in a major way. It
> separates content from presentation. Think of XML as a database for
> content, and XSL as an abstraction layer that is able to serve many
> clients.
Also see:

    XML
    http://en.wikipedia.org/wiki/XML
    
    XSL
    http://en.wikipedia.org/wiki/XSL
    
    DTD
    http://en.wikipedia.org/wiki/Document_Type_Definition

-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs

On Mon, 2003-12-08 at 17:09, Mike Noyes wrote:
> On Mon, 2003-12-08 at 09:30, Mike Noyes wrote:
> > XML is different from the old pre press systems in a major way. It
> > separates content from presentation. Think of XML as a database for
> > content, and XSL as an abstraction layer that is able to serve many
> > clients.
> 
> Also see:
> 
>     XML
>     http://en.wikipedia.org/wiki/XML
>     
>     XSL
>     http://en.wikipedia.org/wiki/XSL
>     
>     DTD
>     http://en.wikipedia.org/wiki/Document_Type_Definition
Also see:

DocBook
http://en.wikipedia.org/wiki/DocBook

-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs

Tom,

Tom Eastep wrote:

[...]
> This reminds me of 30 years ago when we typeed marked-up text then ran
> that text through a translator to produce the final (printed) product
> (then went back and modified the marked-up text and translated; still
> didn''t look right, ...).
>
> The first time that I used FrameMaker, I thought I had died and gone to
> heaven; no more galley and it''s successors. What I saw on the
screen was
> what my document looked like; it was like magic. Now the XML juggernaught
> seems to be trying to convince us that the old model is somehow new.
>
> The tools don''t appear to be mature yet so there is a significant
effort
> required to re-learn to do something that is already intuitive using
> existing WYSIWYG tools (XXE is *not* intuitive, at least to me).
>
> Hopefully this old troglodyte is missing something. But then maybe Alex
> and Mike should understand that trying to teach 60-year old dogs new
> tricks doesn''t always work either...
>
I''m a bit of a lurker, but have asked for assistance
in the past on this list and gotten excellent help.
Tom, you can make me laugh *and* cry. ;) In this
case, you really struck a nerve of deja vu. I could
not agree with you more having also been in the
industry for 20+ years. (I remember when the Wang
word processor was all the rage.)

Not that I don''t mind progress mind you. I just have
found as I got older I keep thinking I have seen the
"latest thing" somewhere before. I usually attribute
it to the beginnings of senility so it is good to
know I have company. ;)

And by the way...I also appreciate the efforts of
others in their contributions to improve shorewall
and give you a little bit of breathing room.

mjp

On Monday 08 December 2003 09:30 am, Mike Noyes wrote:
>
> Yes. XML is different from the old pre press systems in a major way. It
> separates content from presentation. Think of XML as a database for
> content, and XSL as an abstraction layer that is able to serve many
> clients.
>
Ok -- let''s give it a go. I''ve played with XXE enough to
convince myself that
it may get my blood pressure up for a while but probably isn''t a threat
to my
life.

How do you propose that we do the conversion? 

-Tom
-- 
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ teastep@shorewall.net

Subject was: Re: [Shorewall-devel] Re: Shorewall-devel Digest, Vol 11,
Issue 4

On Tue, 2003-12-09 at 08:03, Tom Eastep wrote:
> Ok -- let''s give it a go. I''ve played with XXE enough to
convince myself that
> it may get my blood pressure up for a while but probably isn''t a
threat to my
> life.
> 
> How do you propose that we do the conversion? 
Tom,
I volunteer for the initial conversion. I know DocBook XML fairly well,
and can probably do the conversion faster with less frustration than
you. You can then cleanup any conversion mistakes I make. I''ll try to
stick to the Simplified DocBook elements where possible, but all DTDs
will be for the full XML version.

I''ll need write access to Shorewall-docs. After, I commit a DocBook XML
version you''ll need to use it for future edits. Total conversion (60+
docs) will take at least a couple of weeks.

        BTW, I think there is a stale lock in Shorewall-docs. I wasn''t
        able to get a pserver checkout of Shorewall-docs.

    During the conversion phase, we can use XXE and Tidy for DocBook to
    HTML for website updates. It will be a little inconvenient. I''m
open
    to alternatives (xsltproc?) here. 
    
    Also, do you want the HTML moved to the Attic (deleted) when the
    DocBook XML is committed?

While the conversion is underway, you need to decide on a build system
to use. Also, you''ll need to decide if documents should be combined,
separated, etc. Finally, you''ll need to decide if symlinks to the old
file names are necessary.


DocBook website system
http://docbook.sourceforge.net/
http://cvs.sourceforge.net/viewcvs.py/docbook/sourceforge-webpages/

    Note 1: this would cure the W3C WAI guideline problems the current
    site has. View shorewall.net and docbook.shourceforge.net with lynx
    to see the issue.
    
    Note 2: This system looks slick, but I''m not very familiar with it.

LEAF project auto-build (daily.sh)
http://leaf-project.org/doc/
http://cvs.sourceforge.net/viewcvs.py/leaf/devel/mhnoyes/sf-admin/
http://cvs.sourceforge.net/viewcvs.py/leaf/doc/

-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs

Mike,

On Tuesday 09 December 2003 10:15 am, Mike Noyes wrote:
>
> I volunteer for the initial conversion. I know DocBook XML fairly well,
> and can probably do the conversion faster with less frustration than
> you. You can then cleanup any conversion mistakes I make. I''ll try
to
> stick to the Simplified DocBook elements where possible, but all DTDs
> will be for the full XML version.
Thanks!
>
> I''ll need write access to Shorewall-docs.
Please send me by private post your preferred user name and a hashed password 
(as described on the CVS access page).
> After, I commit a DocBook XML 
> version you''ll need to use it for future edits. Total conversion
(60+
> docs) will take at least a couple of weeks.
That''s fine -- I''ll plan tentatively on releasing the new
versions with
Shorewall 1.4.9. I think I''ll probably separate the documentation from
the
code at that point and release them separately.
>
>         BTW, I think there is a stale lock in Shorewall-docs. I
wasn''t
>         able to get a pserver checkout of Shorewall-docs.
>
It was a permission problem -- solved now.
>
>     During the conversion phase, we can use XXE and Tidy for DocBook to
>     HTML for website updates. It will be a little inconvenient.
I''m open
>     to alternatives (xsltproc?) here.
Today, publishing on the web site is rather a manual process. I''ll
handle
that.
>
>     Also, do you want the HTML moved to the Attic (deleted) when the
>     DocBook XML is committed?
Yes -- let''s only keep XML in the active CVS repository (except for the
home
page and the content on lists.shorewall.net).
>
> While the conversion is underway, you need to decide on a build system
> to use. Also, you''ll need to decide if documents should be
combined,
> separated, etc. Finally, you''ll need to decide if symlinks to the
old
> file names are necessary.
If you just do a one-to-one conversion, I''ll fool around with setting
up a way
to publish to the website.
>
>
> DocBook website system
> http://docbook.sourceforge.net/
> http://cvs.sourceforge.net/viewcvs.py/docbook/sourceforge-webpages/
>
>     Note 1: this would cure the W3C WAI guideline problems the current
>     site has. View shorewall.net and docbook.shourceforge.net with lynx
>     to see the issue.
>
>     Note 2: This system looks slick, but I''m not very familiar
with it.
>
> LEAF project auto-build (daily.sh)
> http://leaf-project.org/doc/
> http://cvs.sourceforge.net/viewcvs.py/leaf/devel/mhnoyes/sf-admin/
> http://cvs.sourceforge.net/viewcvs.py/leaf/doc/
Thanks again, Mike.

-Tom
-- 
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ teastep@shorewall.net

On Tue, 2003-12-09 at 10:48, Tom Eastep wrote:
> > I''ll need write access to Shorewall-docs.
> 
> Please send me by private post your preferred user name and a hashed
password
> (as described on the CVS access page).
Tom,
Done. Email sent off-list.
> > While the conversion is underway, you need to decide on a build system
> > to use. Also, you''ll need to decide if documents should be
combined,
> > separated, etc. Finally, you''ll need to decide if symlinks to
the old
> > file names are necessary.
> 
> If you just do a one-to-one conversion, I''ll fool around with
setting up a way
> to publish to the website.
Will do.

-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs

On Tuesday 09 December 2003 08:02 am, Matt Perry wrote:
>
> Not that I don''t mind progress mind you. I just have
> found as I got older I keep thinking I have seen the
> "latest thing" somewhere before. I usually attribute
> it to the beginnings of senility so it is good to
> know I have company. ;)
>
Likewise :-)
> And by the way...I also appreciate the efforts of
> others in their contributions to improve shorewall
> and give you a little bit of breathing room.
>
As do I!

-Tom
-- 
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ teastep@shorewall.net

Subject was: Re: [Shorewall-devel] Re: Shorewall-devel Digest, Vol 11,
Issue 4

On Mon, 2003-12-08 at 12:41, Alex Martin wrote:
> I have not considered this. Manual or not, I think that this is a 
> reasonable way to mirror the cvs faq and allow the public to make 
> additions / suggestions to be considered for integration into the cvs tree.
Alex,
Do you think you can get InterWiki working on PhpWiki? If so, do you
think we can work around the broken table model. If not, I''ll wait for
you to install MediaWiki before wikifying the FAQs.

    InterWiki
    http://phpwiki.sourceforge.net/phpwiki/InterWiki

If we''re going to stick with PhpWiki, I''d like you to send me
the admin
login off-list, so I can do some major work. Thanks.

-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs

Development on this server cannot be done untill I repair it. This will 
be around the 15th hopefully.

I will post back here as soon as it is repaired.

I am happy to install MediaWiki, this seems to be the best way to go.

So I would lay off any Wiki work. I think once I have it up running, it 
will take me no time to wikify the faq in the format you have outlined 
on the current wiki.

-Alex

Mike Noyes wrote:
> Subject was: Re: [Shorewall-devel] Re: Shorewall-devel Digest, Vol 11,
> Issue 4
> 
> On Mon, 2003-12-08 at 12:41, Alex Martin wrote:
> 
>>I have not considered this. Manual or not, I think that this is a 
>>reasonable way to mirror the cvs faq and allow the public to make 
>>additions / suggestions to be considered for integration into the cvs
tree.
> 
> 
> Alex,
> Do you think you can get InterWiki working on PhpWiki? If so, do you
> think we can work around the broken table model. If not, I''ll wait
for
> you to install MediaWiki before wikifying the FAQs.
> 
>     InterWiki
>     http://phpwiki.sourceforge.net/phpwiki/InterWiki
> 
> If we''re going to stick with PhpWiki, I''d like you to
send me the admin
> login off-list, so I can do some major work. Thanks.
>

On Tue, 2003-12-09 at 15:47, Alex Martin wrote:
> I am happy to install MediaWiki, this seems to be the best way to go.
> 
> So I would lay off any Wiki work. I think once I have it up running, it 
> will take me no time to wikify the faq in the format you have outlined 
> on the current wiki.
Alex,
This sounds good. I''ll concentrate my efforts on the DocBook
conversion.

-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs

On 9 Dec 2003, Mike Noyes wrote:
> On Tue, 2003-12-09 at 15:47, Alex Martin wrote:
> > I am happy to install MediaWiki, this seems to be the best way to go.
> > 
> > So I would lay off any Wiki work. I think once I have it up running,
it
> > will take me no time to wikify the faq in the format you have outlined
> > on the current wiki.
> 
> Alex,
> This sounds good. I''ll concentrate my efforts on the DocBook
conversion.
> 
In the mean time, the FAQ page generated from FAQ.xml has been published 
to the web site.

-Tom 
-- 
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ teastep@shorewall.net

Slick!

I will catch up to you guys soon.
This used to work:

$ cvs -d :pserver:alex@cvs.shorewall.net:/usr/local/cvs \
release Shorewall-docs
cvs release: no such directory: Shorewall-docs

Will the xml and xsl be stored in cvs? (my terminology may be off)

I would like to work on the xml to html translation layer. I hope to do 
future websites in this manner.

Maybe I just need to read back through all of the posts before I ask 
such questions.

Untill finals pass,

Alex


Tom Eastep wrote:
> On 9 Dec 2003, Mike Noyes wrote:
> 
> 
>>On Tue, 2003-12-09 at 15:47, Alex Martin wrote:
>>
>>>I am happy to install MediaWiki, this seems to be the best way to
go.
>>>
>>>So I would lay off any Wiki work. I think once I have it up running,
it
>>>will take me no time to wikify the faq in the format you have
outlined
>>>on the current wiki.
>>
>>Alex,
>>This sounds good. I''ll concentrate my efforts on the DocBook
conversion.
>>
> 
> 
> In the mean time, the FAQ page generated from FAQ.xml has been published 
> to the web site.
> 
> -Tom

Sorry my error on the cvs question, I meant to "checkout" not
"release".

Alex Martin wrote:
> Slick!
> 
> I will catch up to you guys soon.
> This used to work:
> 
> $ cvs -d :pserver:alex@cvs.shorewall.net:/usr/local/cvs \
> release Shorewall-docs
> cvs release: no such directory: Shorewall-docs
> 
> Will the xml and xsl be stored in cvs? (my terminology may be off)
> 
> I would like to work on the xml to html translation layer. I hope to do 
> future websites in this manner.
> 
> Maybe I just need to read back through all of the posts before I ask 
> such questions.
> 
> Untill finals pass,
> 
> Alex
> 
> 
> Tom Eastep wrote:
> 
>> On 9 Dec 2003, Mike Noyes wrote:
>>
>>
>>> On Tue, 2003-12-09 at 15:47, Alex Martin wrote:
>>>
>>>> I am happy to install MediaWiki, this seems to be the best way
to go.
>>>>
>>>> So I would lay off any Wiki work. I think once I have it up
running,
>>>> it will take me no time to wikify the faq in the format you
have
>>>> outlined on the current wiki.
>>>
>>>
>>> Alex,
>>> This sounds good. I''ll concentrate my efforts on the
DocBook conversion.
>>>
>>
>>
>> In the mean time, the FAQ page generated from FAQ.xml has been 
>> published to the web site.
>>
>> -Tom 
> 
> 
> _______________________________________________
> Shorewall-devel mailing list
> Shorewall-devel@lists.shorewall.net
> https://lists.shorewall.net/mailman/listinfo/shorewall-devel

On Tuesday 09 December 2003 04:57 pm, Mike Noyes wrote:
> 
> This sounds good. I''ll concentrate my efforts on the DocBook
conversion.
Mike,

A couple of things about the DocBook versions of the documents:

a) They lack a copyright notice.
b) When I generate HTML from the XML using XXE, the image references are being 
change from "image/foo.png" to "resources/foo.png"; I assume
there is
something that I''m doing wrong?

-Tom
-- 
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ teastep@shorewall.net

On Wednesday 10 December 2003 06:45 am, Tom Eastep
wrote:
> On Tuesday 09 December 2003 04:57 pm, Mike Noyes wrote:
> > This sounds good. I''ll concentrate my efforts on the DocBook
conversion.
>
> Mike,
>
> A couple of things about the DocBook versions of the documents:
>
> a) They lack a copyright notice.
> b) When I generate HTML from the XML using XXE, the image references are
> being change from "image/foo.png" to
"resources/foo.png"; I assume there is
> something that I''m doing wrong?
>
I''ve added copyrights to 6to4.xml and FAQ.xml and have checked in the
changes.

-Tom
-- 
Tom Eastep    \ Nothing is foolproof to a sufficiently talented fool
Shoreline,     \ http://shorewall.net
Washington USA  \ teastep@shorewall.net

On Wed, 2003-12-10 at 06:45, Tom Eastep wrote:
> A couple of things about the DocBook versions of the documents:
> 
> a) They lack a copyright notice.
Tom,
I''ll make sure they are included. Sorry.
> b) When I generate HTML from the XML using XXE, the image references are
being
> change from "image/foo.png" to "resources/foo.png"; I
assume there is
> something that I''m doing wrong?
I just verified this strange behavior. It''s something XXE is doing. I
guess to be helpful. :-(

    xsltproc doesn''t do this. Example
    http://leaf-project.org/doc/howto/proxyarp.xml
    http://leaf-project.org/doc/howto/proxyarp.html

I guess there are two choices.
    a) Manually edit xxe output.
    b) Setup xsltproc for processing.

B is better long term, as I believe it''s the best XSLT engine out there
for DocBook. It may already be on your Linux box. If not, I can walk you
through the install via IRC or email. Your choice.

    bash$ which xsltproc
    bash$ which xmllint
    bash$ ls /etc/xml  <-- catalog files
    bash$ ls /usr/share/sgml <-- DTD & catalog files

-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs

On Tue, 2003-12-09 at 15:47, Alex Martin wrote:
> Development on this server cannot be done untill I repair it. This will 
> be around the 15th hopefully.
> 
> I will post back here as soon as it is repaired.
Alex,
How are you progressing with this task?
> I am happy to install MediaWiki, this seems to be the best way to go.
-- 
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: ffl, leaf, phpwebsite, phpwebsite-comm, sitedocs