You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Ian Atkin <ia...@blueyonder.co.uk> on 2002/07/22 18:39:11 UTC
scratchpad won't compile, help!
hello people,
just got the source, tried to ./build.sh docs as the readme said and
something called "scratchpad" won't compile with loads on deprecation errors
- this is something to do with cocoon isn't it (i'm way behind, sorry)?
- i'm running jdk 1.4 on winXP (yeah i know ...), do i need to use v1.3.1?
if so are there any obvious gotcha's running both jdk versions other
than the JAVA_HOME env var?
thanks
PS
- my main interest is to integrate forrest and docbook, maybe come up
with an 'apachebook' or something
- i've always hated the 'chunking' parts of docbook (for sets, books and
alike) but i highly rate the block-level markup, paramterised/modular
DTD's and stylesheets
- not interested in shoving docbook down anyone's throats, but docbook
is mature and i see no reason to re-invent the wheel, perhaps trim it
down or steal the best practise by the bucket
- any ideas on how to approach this? anything forrest really needs more
urgently while i learn the codebase?
Re: scratchpad won't compile, help!
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Ian Atkin wrote:
...
> PS
Pure Speculation?
Pretty Solution?
Plain Samples?
;-))
> - my main interest is to integrate forrest and docbook, maybe come up
> with an 'apachebook' or something
Forrest DTD is meant to be a kind of ApacheBook.
It still needs stuff, and your help can be... of help ;-)
> - i've always hated the 'chunking' parts of docbook (for sets, books and
> alike) but i highly rate the block-level markup, paramterised/modular
> DTD's and stylesheets
Good, it seems you had to work with it, it's great news :-)
> - not interested in shoving docbook down anyone's throats, but docbook
> is mature and i see no reason to re-invent the wheel, perhaps trim it
> down or steal the best practise by the bucket
Yup.
Call it DocBookXP maybe ;-)
> - any ideas on how to approach this? anything forrest really needs more
> urgently while i learn the codebase?
A glossary. Forrest should be able to add automatic links to words that
are in a glossary, but first we need the glossary format ;-)
Anyway, let me warn you that discussion on Forrest about DocBook /could/
become difficult, mainly because of ignorance. DocBook advocates don't
know Forrest, and Forrest advocates mainly don't understand DocBook.
That said, let me say that I promise I'll be helpful, because this
DocBook question is becoming more and more frequent, and there is
evidently something we're missing.
I think it would be really *fantastic* (honestly) if you could come up
with a reasoned comparison, so that we can finally make reasoned decisions.
These are the point that you should take into account:
1) DocBook is for books, Forrest is mainly for sites or technical books
2) DocBook is more difficult to understand than Forrest, which is
basically a cleaned and enhanced XHTML.
3) Users will always ask why we don't use DocBook; we need a good reply
4) Forrest DTD lacks many useful features that DocBook has, while
DocBook has also many features that Forrest users would never use.
5) We should be able to convert one to the other, even if not with 100%
accuracy.
6) any suggestion welcome
If you will write technical comparisons with possibly some
suggestions, you will find us very eager to listen.
Thanks :-)
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: scratchpad won't compile, help!
Posted by Ian Atkin <ia...@blueyonder.co.uk>.
great, what you did worked!
i'll now fathom the thing and see where i can be useful, once i've
figured out how to do something maybe a "how to"?
i'll research docbook integration and mail again later in the week
thanks for the speed, i'm a :-) bunny now...
Steven Noels wrote:
> Ian Atkin wrote:
>
>> no problem,
>>
>> how can i get round it?
>>
>> how can i help?
>
>
> please re-update your local copy now and try a "./build.{sh|bat} clean
> docs"
>
> do not look at the depreciation messages, and tell us whether that
> worked :-)
>
> Thanks,
>
> </Steven>
Re: scratchpad won't compile, help!
Posted by Steven Noels <st...@outerthought.org>.
Ian Atkin wrote:
> no problem,
>
> how can i get round it?
>
> how can i help?
please re-update your local copy now and try a "./build.{sh|bat} clean docs"
do not look at the depreciation messages, and tell us whether that
worked :-)
Thanks,
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
stevenn@outerthought.org stevenn@apache.org
Re: scratchpad won't compile, help!
Posted by Ian Atkin <ia...@blueyonder.co.uk>.
no problem,
how can i get round it?
how can i help?
Steven Noels wrote:
> Ian Atkin wrote:
>
>> hello people,
>>
>> just got the source, tried to ./build.sh docs as the readme said and
>> something called "scratchpad" won't compile with loads on deprecation
>> errors
>
>
> cvs is in heavy flux right now - bear with us for some hours :-|
>
> normally however, the depreciation errors won't hurt and eventually
> will get fixed
>
> </Steven>
Re: scratchpad won't compile, help!
Posted by Steven Noels <st...@outerthought.org>.
Ian Atkin wrote:
> hello people,
>
> just got the source, tried to ./build.sh docs as the readme said and
> something called "scratchpad" won't compile with loads on deprecation
> errors
cvs is in heavy flux right now - bear with us for some hours :-|
normally however, the depreciation errors won't hurt and eventually will
get fixed
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
stevenn@outerthought.org stevenn@apache.org
Re: scratchpad won't compile, help!
Posted by Steven Noels <st...@outerthought.org>.
Ian Atkin wrote:
(some more time now - happy to hear you're up & running now)
> PS
> - my main interest is to integrate forrest and docbook, maybe come up
> with an 'apachebook' or something
a popular question these days
> - i've always hated the 'chunking' parts of docbook (for sets, books and
> alike) but i highly rate the block-level markup, paramterised/modular
> DTD's and stylesheets
there's still plenty to be done on the DTDs, I haven't been able to put
in as much time as I wanted to do
> - not interested in shoving docbook down anyone's throats, but docbook
> is mature and i see no reason to re-invent the wheel, perhaps trim it
> down or steal the best practise by the bucket
well, some of our potential users have already docs in docbook format,
so a nice transition/integration path would be welcome
> - any ideas on how to approach this? anything forrest really needs more
> urgently while i learn the codebase?
serious contributors ;-)
seriously: I still want to reshuffle the elems/attrs across the DTD
modules in a more balanced way, moving more of them into
common-elems-v10.mod instead of keeping them inside document-v11.mod
if you manage to grasp the modularity of docbook, I'm pretty sure this
isn't much of a challenge for you, then ;-)
welcome!
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
stevenn@outerthought.org stevenn@apache.org