xmlroff-list — xmlroff XSL formatter discussion list

Re: [xmlroff] SourceForge RSS

[Tony G. <Ton...@Su...>]

Stefan Seefeld <se...@sy...> writes:
> Tony Graham wrote:
>> (Replying to part of Stefan's message)
>> Stefan Seefeld <se...@sy...> writes:
>
>>>Sorry, no. Doing a build locally, I get the content wrapped in
>>>'<div class="rss">'. Is it the same <div> you see, just empty ?
>> That is what I see.
>> I'm using the 2.5 version of the website stylesheets.
>
> huh ? The first statement inside the custom-website.xsl file reads
>
>    <xsl:import href="http://docbook.sourceforge.net/release/website/2.4.1/xsl/tabular.xsl"/>

That's what's in the catalog for the DocBook website files that I
downloaded, so I used that.

> Are you not using this file ? But anyways, even if I replace '2.4.1' there by '2.5.0'
> I get a 'correct' news listing.

And there's a reason for that:  as you surmised, I had missed your
custom-stylesheet.xsl patch.  It works for me now.  Thank you and
sorry for the mix-up.

...
>> The first step would be to copy the template for the <rss> element
>> into the custom stylesheet and tweak the namespaces on the "select"
>> and "match" attributes to make it work.
>
> I thought that was what I had been doing all the time :-)
> Is it possible that you forgot to apply the patch to the custom-website.xsl file ?
>
>> Second step would be to submit a bug report or enhancement request to
>> the DocBook project.
>
> Yeah, I did that some weeks ago.

I'm glad that we think alike in this.

I think I would have done better if my mailer hadn't inlined both of
your patches one after the other.  Sorry about that.

The patch is applied and checked in, and the website has been
updated.  We now have multitudinous logos and, more importantly, RSS.
Thank you for that.

Regards,


Tony.

Re: [xmlroff] SourceForge RSS [Was: xmlroff website help wanted]

[Stefan S. <se...@sy...>]

Tony Graham wrote:
> (Replying to part of Stefan's message)
> 
> Stefan Seefeld <se...@sy...> writes:

>>Sorry, no. Doing a build locally, I get the content wrapped in
>>'<div class="rss">'. Is it the same <div> you see, just empty ?
> 
> 
> That is what I see.
> 
> I'm using the 2.5 version of the website stylesheets.

huh ? The first statement inside the custom-website.xsl file reads

   <xsl:import href="http://docbook.sourceforge.net/release/website/2.4.1/xsl/tabular.xsl"/>

Are you not using this file ? But anyways, even if I replace '2.4.1' there by '2.5.0'
I get a 'correct' news listing.

> Looking at the stylesheets and the SourceForge RSS, it appears that
> the stylesheets are expecting the RSS to use namespaced elements and
> the SourceForge RSS doesn't.

yeah, you are talking about the 'rss.xsl' file that's shipped with the db-website
xsl distribution, right ? That appears indeed to be written for rss 1.0, while
sf.net provides rss 2.0 feeds. That's why I don't use the xsl templates from Norm,
but my own, which don't use the rss namespace.
I'm a bit lost now. Let me try on sf.net...

> SourceForge claims all sorts of wonderful compatibility and testing
> for correctness for its RSS feeds, so I don't know who's right and
> who's wrong about namespaces for RSS.

the docbook website xsl says it provides support for rss 1.0 (0.9x) feeds,
while sf.net provides rss 2.0 feeds. They may both be correct.

> The first step would be to copy the template for the <rss> element
> into the custom stylesheet and tweak the namespaces on the "select"
> and "match" attributes to make it work.

I thought that was what I had been doing all the time :-)
Is it possible that you forgot to apply the patch to the custom-website.xsl file ?

> Second step would be to submit a bug report or enhancement request to
> the DocBook project.

Yeah, I did that some weeks ago.

Regards,
		Stefan

[xmlroff] ANN: Stefan Seefeld is xmlroff developer

[Tony G. <Ton...@Su...>]

I'm pleased to announce that Stefan Seefeld has agreed to become a
developer on the xmlroff project.

As you will be aware from the traffic on this list, Stefan is
interested in updating, and easing the updating of, the xmlroff
project website since it is the public face of the project.  Right now
he is working on bringing the website into the current millenium by
using the project's RSS feed in the "news" page.

The project has benefited from his contributions to date, and we look
forward to similarly benefiting from his future contributions.
Welcome, Stefan.

Regards,


Tony.

[xmlroff] Test result summary page [Was: xmlroff website help wanted]

[Tony G. <Ton...@Su...>]

Stefan Seefeld <se...@sy...> writes:
...
>>>Just so that occasional visitors that want to watch the progress
>>>in terms of feature coverage could get a quick impression.
>> A good idea, certainly.  Would the static test result summary page
>> suffice for starters?
>
> Sure. As long as it is not too much out of sync. One thing I hope we
> could improve over the current website is to make sure the information
> correctly reflects the current status, i.e. at least the state from
> the current release, may be even from current 'snapshots'. Having to
> update lots of different places is annoying for you, so I hope with
> some scripts we can automatize that.
> Running the tests should be something that can be done automatically,
> and so should be the generation of a little report (html, xml, rss, whatever).

I'm attaching a copy of the current summary page.  The tests are run
and the report is generated using a combination of shell scripts, Perl
scripts, and XSLT stylesheets.

Regards,


Tony.

[xmlroff] SourceForge RSS [Was: xmlroff website help wanted]

[Tony G. <Ton...@Su...>]

(Replying to part of Stefan's message)

Stefan Seefeld <se...@sy...> writes:
> Tony Graham wrote:
>> I've added a new item (partly so you can see what I've been working on
>> when I didn't reply yesterday), but when I generate news.html, all I
>> get is an empty <div>.  Any ideas?
>
> Sorry, no. Doing a build locally, I get the content wrapped in
> '<div class="rss">'. Is it the same <div> you see, just empty ?

That is what I see.

I'm using the 2.5 version of the website stylesheets.

Looking at the stylesheets and the SourceForge RSS, it appears that
the stylesheets are expecting the RSS to use namespaced elements and
the SourceForge RSS doesn't.

SourceForge claims all sorts of wonderful compatibility and testing
for correctness for its RSS feeds, so I don't know who's right and
who's wrong about namespaces for RSS.

The first step would be to copy the template for the <rss> element
into the custom stylesheet and tweak the namespaces on the "select"
and "match" attributes to make it work.

Second step would be to submit a bug report or enhancement request to
the DocBook project.

Ideally the templates in the rss.xsl file in the website stylesheets
would have "name" attributes so you can call the right template from
your customisation even if you're working with not-quite-correct RSS.
It might also require that the website templates be more relaxed about
namespaces (e.g., use "*:title|title" instead of "rss:title") in their
"select" attributes since the structure of the RSS is likely to be
correct even when the namespace isn't.

>> It shouldn't be a proxy problem, since I'm no longer getting the error
>> message that I used to get before I had my proxy set up.
>
> may be a <xsl:message> put into the xslt file to 'debug' the process
> will reveal whether the rss feed could be accessed correctly.

You get text in the output HTML when you can't access the URL for the
RSS.  That's what I used to get before I correctly set my http_proxy
environment variable.

Regards,


Tony.

Re: [xmlroff] Re: xmlroff website help wanted

[Stefan S. <se...@sy...>]

Tony Graham wrote:

> I've added a new item (partly so you can see what I've been working on
> when I didn't reply yesterday), but when I generate news.html, all I
> get is an empty <div>.  Any ideas?

Sorry, no. Doing a build locally, I get the content wrapped in
'<div class="rss">'. Is it the same <div> you see, just empty ?

> It shouldn't be a proxy problem, since I'm no longer getting the error
> message that I used to get before I had my proxy set up.

may be a <xsl:message> put into the xslt file to 'debug' the process
will reveal whether the rss feed could be accessed correctly.

> If I'd answered yesterday, I would have said that it would be
> comparatively easy to generate a version of the test results report
> that didn't link to the cgi scripts for updating the result summaries.
> 
> Today, it seems to me that an occasional visitor would be more
> impressed if there was a graph showing number of tests and percentage
> of passed tests (increasing) over time.  Now, that would be more work.

yeah, you'd have to keep a log of the tests.
Well, if I'm interested in the evolution of the project, I'd track the
'news'. If I want to get an idea of the 'current status', I'd look at
the feature coverage (i.e. both the static matrix you generate manually
as well as a possible automatically generated test report).

>>Just so that occasional visitors that want to watch the progress
>>in terms of feature coverage could get a quick impression.
> 
> 
> A good idea, certainly.  Would the static test result summary page
> suffice for starters?

Sure. As long as it is not too much out of sync. One thing I hope we
could improve over the current website is to make sure the information
correctly reflects the current status, i.e. at least the state from
the current release, may be even from current 'snapshots'. Having to
update lots of different places is annoying for you, so I hope with
some scripts we can automatize that.
Running the tests should be something that can be done automatically,
and so should be the generation of a little report (html, xml, rss, whatever).

Regards,
		Stefan

[xmlroff] pangopdf module name?

[Tony G. <Ton...@Su...>]

I am contemplating making a new CVS module for the current PangoPDF
code since removing the 90% of files that are now obsolete would still
leave a lot of directories that would still be created on a CVS
checkout.

I'm considering either getting the current 'pangopdf' module renamed
to 'pangopdf-pre1.6' or making a new 'pangoxsl' module since a new
name would better reflect what PangoPDF is currently trying to do.

Any thoughts?

Regards,


Tony.

Re: [xmlroff] Re: xmlroff website help wanted

[Tony G. <Ton...@Su...>]

Stefan Seefeld <se...@sy...> writes:
> Tony Graham wrote:
>> The version currently in CVS adds some logos at the bottom of the
>> navigation bar.
>
> fine. Though the website doesn't appear to be updated from this new
> source. I was ready to investigate when I realized that a simple build
> fixed the site locally. Don't you regenerate the website automatically
> either per crontab or per checkin ?

SourceForge crontabs are currently disabled, and setting everything up
to regenerate the html on checkin might be a bit much to do.

The Makefile for the actual DocBook web pages has a better-developed
use of ssh for getting pages onto the SourceForge site than the ways
that I've played with so far.

I didn't update the web site because I was intending to come back and
do a better customization than at present.  I don't like the fact that
the current logos also add extra whitespace in the body of the page.

>> It would look better if a 'rowspan="2"' deep inside the DocBook
>> website stylesheets were 'rowspan="3"', but that was more than I
>> wanted to customise at this time of night.
>> I'll leave the RSS stuff up to you, Stefan.
>
> The attached patch replaces the current 'news.html' content by the
> rss news feed from sf.net. The styling still needs a lot of work,

Thank you.

> but as that can all be done via css customization, I'll keep that
> issue open for the moment.
> Please add some news (on the sf.net) so we can all see the rss feed
> working :-)

I've added a new item (partly so you can see what I've been working on
when I didn't reply yesterday), but when I generate news.html, all I
get is an empty <div>.  Any ideas?

It shouldn't be a proxy problem, since I'm no longer getting the error
message that I used to get before I had my proxy set up.

> I'd still like to see the website give a more accurate impression of
> the current status of the project. I'm not sure though how feasable that
> is without more manual work (from your part). Can't the unit tests
> be run automatically and some status page generated from that ?

If I'd answered yesterday, I would have said that it would be
comparatively easy to generate a version of the test results report
that didn't link to the cgi scripts for updating the result summaries.

Today, it seems to me that an occasional visitor would be more
impressed if there was a graph showing number of tests and percentage
of passed tests (increasing) over time.  Now, that would be more work.

> Just so that occasional visitors that want to watch the progress
> in terms of feature coverage could get a quick impression.

A good idea, certainly.  Would the static test result summary page
suffice for starters?

Regards,


Tony.

Re: [xmlroff] Re: xmlroff website help wanted

[Stefan S. <se...@sy...>]

Tony Graham wrote:

> The version currently in CVS adds some logos at the bottom of the
> navigation bar.

fine. Though the website doesn't appear to be updated from this new
source. I was ready to investigate when I realized that a simple build
fixed the site locally. Don't you regenerate the website automatically
either per crontab or per checkin ?

> It would look better if a 'rowspan="2"' deep inside the DocBook
> website stylesheets were 'rowspan="3"', but that was more than I
> wanted to customise at this time of night.
> 
> I'll leave the RSS stuff up to you, Stefan.

The attached patch replaces the current 'news.html' content by the
rss news feed from sf.net. The styling still needs a lot of work,
but as that can all be done via css customization, I'll keep that
issue open for the moment.
Please add some news (on the sf.net) so we can all see the rss feed
working :-)

I'd still like to see the website give a more accurate impression of
the current status of the project. I'm not sure though how feasable that
is without more manual work (from your part). Can't the unit tests
be run automatically and some status page generated from that ?

Just so that occasional visitors that want to watch the progress
in terms of feature coverage could get a quick impression.

Any suggestions ?

Kind regards,
		Stefan

Re: [xmlroff] Re: xmlroff website help wanted

[Tony G. <Ton...@Su...>]

Stefan Seefeld <se...@sy...> writes:
> you mean by modifying the stylesheets (xslt or css) ? I hope so !
> I believe the sf.net logo should go on the bottom of the navigation
> bar (together with the 'docbook website' logo, similar to
> http://nwalsh.com/docbook/index.html), so it's just a matter of
> setting up the xslt templates correctly.

The version currently in CVS adds some logos at the bottom of the
navigation bar.

It would look better if a 'rowspan="2"' deep inside the DocBook
website stylesheets were 'rowspan="3"', but that was more than I
wanted to customise at this time of night.

I'll leave the RSS stuff up to you, Stefan.

Regards,


Tony.

Re: [xmlroff] Re: xmlroff website help wanted

[Tony G. <Ton...@Su...>]

Stefan Seefeld <se...@sy...> writes:
> Tony Graham wrote:
>> The logo is back.  I should look at how to get it on every page so we
>> get more brownie points with SourceForge's broken project-ranking system.
>> Please let me know whether or not you can create HTML without having
>> to modify anything.
>
> you mean by modifying the stylesheets (xslt or css) ? I hope so !
> I believe the sf.net logo should go on the bottom of the navigation
> bar (together with the 'docbook website' logo, similar to
> http://nwalsh.com/docbook/index.html), so it's just a matter of
> setting up the xslt templates correctly.

My thoughts exactly, even down to the inclusion of the docbook website
logo.

It should just need an addition to custom-website.xsl.

>>>Otherwise modifications that I apply to embedd a 'news' headline into the
>>>frontpage won't validate any more (which might not be a problem, if you
>>>process the stuff only with 'xsltproc --novalid').
>> It's worse than that: I've started using nXML mode in Emacs, which
>> means I'll need a RNG version of the DTD customization if nXML is
>> going to validate on the fly.
>
> ok, so we need to adjust the rng and generate the dtd from it if we
> want to validate. Sounds like a good occasion to get familiar with
> relaxng :-)

Well-formed is good enough for starters.

Regards,


Tony.

Re: [xmlroff] Re: xmlroff website help wanted

[Stefan S. <se...@sy...>]

Tony Graham wrote:

> The logo is back.  I should look at how to get it on every page so we
> get more brownie points with SourceForge's broken project-ranking system.
> 
> Please let me know whether or not you can create HTML without having
> to modify anything.

you mean by modifying the stylesheets (xslt or css) ? I hope so !
I believe the sf.net logo should go on the bottom of the navigation
bar (together with the 'docbook website' logo, similar to
http://nwalsh.com/docbook/index.html), so it's just a matter of
setting up the xslt templates correctly.

>>Otherwise modifications that I apply to embedd a 'news' headline into the
>>frontpage won't validate any more (which might not be a problem, if you
>>process the stuff only with 'xsltproc --novalid').
> 
> 
> It's worse than that: I've started using nXML mode in Emacs, which
> means I'll need a RNG version of the DTD customization if nXML is
> going to validate on the fly.

ok, so we need to adjust the rng and generate the dtd from it if we
want to validate. Sounds like a good occasion to get familiar with
relaxng :-)

Regards,
		Stefan

Re: [xmlroff] Re: xmlroff website help wanted

[Tony G. <Ton...@Su...>]

Stefan Seefeld <sse...@ar...> writes:

Stefan, you posted from an address that is not subscribed to this list.

> Tony Graham wrote:
>>There's a few rough spots -- No Sourceforge logo at present (my fault)
>>and still no documentation or development content -- but finally its
>>up.

The logo is back.  I should look at how to get it on every page so we
get more brownie points with SourceForge's broken project-ranking system.

Please let me know whether or not you can create HTML without having
to modify anything.

> yeah, I'm still looking into these issues. Unfortunately the docbook-website
> xsl stuff only supports rss 1.0 out of the box (sf.net feeds version 2.0),
> so
> I have to rewrite the templates. Second, the website dtd doesn't appear
> to support the injection of headlines from rss (nor other restrictions such
> as 'first item only').
> I'v filed an RFE for it, but in the mean time: since you already ship the
> website dtd, shouldn't we add local modifications that allow new attributes
> for the 'rss' element such as 'from' and 'to' ?

I don't "ship the website DTD", but I expect that it's possible to
make a local customization that refers to the standard website DTD.
This is DocBook (and Norm's handiwork), after all.

custom-website.xsl is now back in use, so you could put any XSL
customizations in there.

> Otherwise modifications that I apply to embedd a 'news' headline into the
> frontpage won't validate any more (which might not be a problem, if you
> process the stuff only with 'xsltproc --novalid').

It's worse than that: I've started using nXML mode in Emacs, which
means I'll need a RNG version of the DTD customization if nXML is
going to validate on the fly.

Regards,


Tony.

Re: [xmlroff] Re: xmlroff website help wanted

[Stefan S. <sse...@ar...>]

Tony Graham wrote:


>I downloaded the current DocBook Website files and then updated the
>DOCTYPE declarations in all the XML files to match.  Once I added the
>Website catalog to the system catalogs, it just worked.  Amazing.

Great.

>There's a few rough spots -- No Sourceforge logo at present (my fault)
>and still no documentation or development content -- but finally its
>up.

yeah, I'm still looking into these issues. Unfortunately the docbook-website
xsl stuff only supports rss 1.0 out of the box (sf.net feeds version 2.0),
so
I have to rewrite the templates. Second, the website dtd doesn't appear
to support the injection of headlines from rss (nor other restrictions such
as 'first item only').
I'v filed an RFE for it, but in the mean time: since you already ship the
website dtd, shouldn't we add local modifications that allow new attributes
for the 'rss' element such as 'from' and 'to' ?
Otherwise modifications that I apply to embedd a 'news' headline into the
frontpage won't validate any more (which might not be a problem, if you
process the stuff only with 'xsltproc --novalid').

Regards,
		Stefan

Re: [xmlroff] Re: xmlroff website help wanted

[Tony G. <Ton...@Su...>]

Stefan Seefeld <se...@sy...> writes:
> Attached is a little patch that provides a reorganized menu. It's actually
> more a direction than a final result. I notably regrouped some items into
> a 'documentation' item, and others into 'development' (documentation containing
> everything from user manual to API reference, development everything from
> status to task tracker). Thus there are much less items on the main page,
> but those that are there are of general use.

Committed, finally.  Thank you.

I downloaded the current DocBook Website files and then updated the
DOCTYPE declarations in all the XML files to match.  Once I added the
Website catalog to the system catalogs, it just worked.  Amazing.

There's a few rough spots -- No Sourceforge logo at present (my fault)
and still no documentation or development content -- but finally its
up.

Thank you again.

Regards,


Tony.

Re: [xmlroff] Documentation wishlist

[Tony G. <Ton...@Su...>]

Steve Cheng <g3c...@cd...> writes:
> On Mon, 13 Sep 2004, Tony Graham wrote:
>
>> Did you see <http://xmlroff.org/phpwiki/index.php/DesignNotes>?
>>
>> It hasn't been added to recently since there's been no indication of
>> people reading it.
>
> Oh, sorry, didn't see that. (Thought it would be in the same
> place as the code documentation.)

The theory was that that stuff would be drafted in the Wiki and then
put in the code documentation when it was stable.

That intention also predates the nominally monthly release schedule.
With regular releases, there's now less lag time between updating the
DocBook documentation and publishing it in a release.

>> Then ask where to start.  Either ask for suggestions on how to do what
>> you want to do or ask for suggestions for simple things that you can
>> do.  There's also the bug reports and enhancement requests on the
>> SourceForge project site.
>
> (When I get my head around the design, I'll try something.
> I think I reasonably understand the XSL-FO spec now.)

I bet that if you transcribed the Wiki documentation into DocBook and
put it in the code documentation, you'd know a lot more about the
design than you do now.

Regards,


Tony.

Re: [xmlroff] Does xmlroff use code generation?

[Tony G. <Ton...@Su...>]

Steve Cheng <g3c...@cd...> writes:
> On Mon, 13 Sep 2004, Tony Graham wrote:
>
>> The problem is that the generated code is really just a starting
>> point, sometimes because there's stuff that the XSLT stylesheets don't
>> handle yet and sometimes because you can make optimisations for
>> particular properties or FO.
>
> Okay, but I doubt you really enjoy the maintainence nightmare
> of keeping track which files have been hand-modified or not,
> or typing those g_object_ things ...

I don't, which is why dump-info.xml and the stylesheets keep getting
more complex.

Regards,


Tony.

Re: [xmlroff] Documentation wishlist

[Steve C. <g3c...@cd...>]

On Mon, 13 Sep 2004, Tony Graham wrote:

> Did you see <http://xmlroff.org/phpwiki/index.php/DesignNotes>?
>
> It hasn't been added to recently since there's been no indication of
> people reading it.

Oh, sorry, didn't see that. (Thought it would be in the same
place as the code documentation.)

> Then ask where to start.  Either ask for suggestions on how to do what
> you want to do or ask for suggestions for simple things that you can
> do.  There's also the bug reports and enhancement requests on the
> SourceForge project site.

(When I get my head around the design, I'll try something.
I think I reasonably understand the XSL-FO spec now.)

Thanks for your patience,
-- 
Steve Cheng
&#x912D;&#x541B;&#x535A;

docbook2X: <URL:http://docbook2x.sourceforge.net/>

Re: [xmlroff] Does xmlroff use code generation?

[Steve C. <g3c...@cd...>]

On Mon, 13 Sep 2004, Tony Graham wrote:

> The problem is that the generated code is really just a starting
> point, sometimes because there's stuff that the XSLT stylesheets don't
> handle yet and sometimes because you can make optimisations for
> particular properties or FO.

Okay, but I doubt you really enjoy the maintainence nightmare
of keeping track which files have been hand-modified or not,
or typing those g_object_ things ...

-- 
Steve Cheng
鄭君博

docbook2X: <URL:http://docbook2x.sourceforge.net/>

Re: [xmlroff] Documentation wishlist

[Tony G. <Ton...@Su...>]

Steve Cheng <g3c...@cd...> writes:

> I hope I'm not demanding too much ...
>
> Tony, I think it will be better if you write a (short) bird's eye
> overview of how libfo works --- the package is large, and I'm pretty
> sure all the things are interconnected in some way[*] that is not
> obvious at all reading the code comments.

Did you see <http://xmlroff.org/phpwiki/index.php/DesignNotes>?

It hasn't been added to recently since there's been no indication of
people reading it.

> [*] If you have read the docbook2X mailing list, I am trying to
> implement XSL-FO with groff (as a way to warm up :)  There, it's
> not obvious to me, for example, how to implement keeps,
> or floats, and if I were to try to something in libfo I wouldn't
> know where to even start.

Then ask where to start.  Either ask for suggestions on how to do what
you want to do or ask for suggestions for simple things that you can
do.  There's also the bug reports and enhancement requests on the
SourceForge project site.

Regards,


Tony.

Re: [xmlroff] Does xmlroff use code generation?

[Tony G. <Ton...@Su...>]

Steve Cheng <g3c...@cd...> writes:
> On Sun, 12 Sep 2004, Steve Cheng wrote:
>> Is any of the xmlroff code automatically generated?
>> Seems to be, but I don't see the sources for it.
>
> Never mind, I found it in the spec-dump module.
> (Although I think, for serious development, it really
> should be integrated in the xmlroff source.)

The problem is that the generated code is really just a starting
point, sometimes because there's stuff that the XSLT stylesheets don't
handle yet and sometimes because you can make optimisations for
particular properties or FO.

The styles for generating properties have had a lot more attention
recently than have the styles for generating FOs.

I sometimes think that generating code can be a hindrance as much as a
help: spec-dump used to generate wonderfully neat, clean, regular code
that does everything for one property all in one file, but the enums
for all properties have all moved to datatype/fo-enum.[ch] and some of
the property validation code has coalesced in fo-property-util.c
rather than repeat the same stuff in multiple files.

spec-dump started out as a single stylesheet that dumped the names of
the FOs and properties, and it's expanded from there.

Regards,


Tony.

Re: [xmlroff] Does xmlroff use code generation?

[Steve C. <g3c...@cd...>]

On Sun, 12 Sep 2004, Steve Cheng wrote:

> Is any of the xmlroff code automatically generated?
> Seems to be, but I don't see the sources for it.

Never mind, I found it in the spec-dump module.
(Although I think, for serious development, it really
should be integrated in the xmlroff source.)

-- 
Steve Cheng
鄭君博

docbook2X: <URL:http://docbook2x.sourceforge.net/>

[xmlroff] Does xmlroff use code generation?

[Steve C. <g3c...@cd...>]

Tony,

Is any of the xmlroff code automatically generated?
Seems to be, but I don't see the sources for it.

(Please don't tell me that those zillions of g_object_new() things
manually; it's bad enough that C is so low-level ...)

-- 
Steve Cheng
鄭君博

docbook2X: <URL:http://docbook2x.sourceforge.net/>

[xmlroff] Documentation wishlist

[Steve C. <g3c...@cd...>]

I hope I'm not demanding too much ...

Tony, I think it will be better if you write a (short) bird's eye
overview of how libfo works --- the package is large, and I'm pretty
sure all the things are interconnected in some way[*] that is not
obvious at all reading the code comments.

[*] If you have read the docbook2X mailing list, I am trying to
implement XSL-FO with groff (as a way to warm up :)  There, it's
not obvious to me, for example, how to implement keeps,
or floats, and if I were to try to something in libfo I wouldn't
know where to even start.

-- 
Steve Cheng
鄭君博

docbook2X: <URL:http://docbook2x.sourceforge.net/>

[xmlroff] Next xmlroff after 10th September

[Tony G. <Ton...@Su...>]

Releasing "on or about the first of the month" has had a liberal
interpretation recently.  It's being stretched again this month since
I need to write a paper for XML 2004 before the 10th.  I'll have some
spare time for xmlroff after then.

Regards,


Tony.