| LPEX and DocBook [message #10871] |
Mon, 14 January 2002 05:03  |
Eclipse User |
|
|
|
When my wife (who was an IBMer) announced LPEX for OS/2 in the UK it was
on her desk not as a development tool but as an editor for Script due to
its parsing and formatting capabilities. She was in the Office Marketting
group at the time.
I am currently updating some HOWTO documents from the LinuxDoc project
and it struck me that the java LPEX in CDT might be handy. How easy would
it be to take the old scripts from LPEX for OS/2 and convert them to CDT
LPEX, or even better has anyone already done this? Then I could update
them to follow DocBook(the XML version I suspect) rather then the older
SGML code that the old LPEX had.
Then there would be a good development tool for DocBook, which seems
to be something that I can not find eaasily currently. Most of it seems
to be done by hand using vi or emacs and a few macros.
|
|
|
|
|
| Re: LPEX and DocBook [message #10928 is a reply to message #10913] |
Mon, 14 January 2002 11:32  |
| Eclipse User |
|
|
|
adrian wrote:
> 1.- The LPEX API is available (though not very visible):
>
>
http://64.38.235.23/tools/cdt/downloads/0.5.0/com.ibm.cpp.do cs.user/Lpex/api/index.html
>
> In a future release, LPEX will have a documentation plugin, and all be
> more visible.
>
> 2.- This version of LPEX doesn't have the gml (Bookie) document parsers
> from that ol' LPEX, or appropriate support for it.
>
> Peter Manahan wrote:
>>
>> Do you mean the parsing scripts? Or custom scripts you had created? Or
>> the actual sgml parser itself ?
>>
>> The java version of LPEX had all the core rewritten and the the way the
>> parsers work is different (also they are written in java :) ). The
>> scripts to setup the macros and parsers were REXX based. The current
>> incarnation is extensible using java. For example say you want to add a
>> new command or parser you just code it up and and hook it in. Then it
>> can be used just like anyother command.
>>
>> Hmm, I notice that the online docs for JLPEX don't have the programming
>> guides for the editor itself (I was looking for them to point you to. )
>> I imagine they will be made open source along with the editor but just
>> haven't made it in yet.
>>
>> Peter
Well I have gotten a little further. I have added .sgml as a file type
for LPEX and pointed it at the XML parser. Does this parser know about
DTDs, and if so how do I map a URN type DTD name to a real file? What
I am then missing is the "turn off all the tags and render it" function
that LPEX used to have. How that I can live without by adding a .PDF or
..PS type and pointing XPDF or GV at it, and by using the make stuff
go through jade etc to build the DocBook source into something readable.
BTW, a nice to have. When I defined the file type, it did not propagate
to the Eclipse file type stuff, so I had to define it twice. I guess this
is because of the lack of an API for you to use, but from a usability point
of view it would be good if you were to ask, get and implment such a
strategy.
|
|
|
|
| Re: LPEX and DocBook [message #10949 is a reply to message #10928] |
Mon, 14 January 2002 17:10 |
| Eclipse User |
|
|
|
Originally posted by: adrianstoristeanu.sympatico.ca
David Goodenough wrote:
> Well I have gotten a little further. I have added .sgml as a file type
> for LPEX and pointed it at the XML parser. Does this parser know about
> DTDs, and if so how do I map a URN type DTD name to a real file?
The XML document parser could be extended to handle this. Right now it
only does basic syntax highlighting of the file...
> What I am then missing is the "turn off all the tags and render it" function
> that LPEX used to have.
Sorry, this is not available in the Java version of LPEX. Another
[non-editable] view of the document could be instantiated, which would
display no tags!?
> How that I can live without by adding a .PDF or
> .PS type and pointing XPDF or GV at it, and by using the make stuff
> go through jade etc to build the DocBook source into something readable.
>
> BTW, a nice to have. When I defined the file type, it did not propagate
> to the Eclipse file type stuff, so I had to define it twice. I guess this
> is because of the lack of an API for you to use, but from a usability point
> of view it would be good if you were to ask, get and implment such a
> strategy.
Thanks for the suggestion, I will open an Eclipse feature 'bug' for
this. There are quite a few things that cannot be defined dynamically
in Eclipse, but only via the plugin.xml...
|
|
|
| Re: LPEX and DocBook [message #14159 is a reply to message #10940] |
Tue, 29 January 2002 14:00 |
| Eclipse User |
|
|
|
Originally posted by: gfaircl.us.ibm.com
And don't discount Emacs so quickly. The newer versions have all the
wonderful Windows GUI things we've grown to depend upon. I don't know if it
can be made pluggable into Eclipse (i sure hope so), but here is a wonderful
article to get you up-and-running with Emacs and SGML:
http://www-106.ibm.com/developerworks/library/x-emacs/
Yes.. PSGML works for both XML and SGML and it does recognize DTDs quite
well.
(Not quite on topic, but I had to share..) :-)
-g-
"dion" <trongus@yahoo.com> wrote in message
news:3C435083.9070203@yahoo.com...
> David Goodenough wrote:
>
> > When my wife (who was an IBMer) announced LPEX for OS/2 in the UK it was
> > on her desk not as a development tool but as an editor for Script due to
> > its parsing and formatting capabilities. She was in the Office
Marketting
> > group at the time.
> >
> > I am currently updating some HOWTO documents from the LinuxDoc project
> > and it struck me that the java LPEX in CDT might be handy. How easy
would
> > it be to take the old scripts from LPEX for OS/2 and convert them to CDT
> > LPEX, or even better has anyone already done this? Then I could update
> > them to follow DocBook(the XML version I suspect) rather then the older
> > SGML code that the old LPEX had.
> >
> > Then there would be a good development tool for DocBook, which seems
> > to be something that I can not find eaasily currently. Most of it seems
> > to be done by hand using vi or emacs and a few macros.
>
> I use XMLMind's XML editor (XXE) for DocBook stuff - pretty good....
>
> see http://www.xmlmind.com/xmleditor/
>
> dIon
>
|
|
|
Powered by
FUDForum. Page generated in 0.04866 seconds
Home