section info class library
0 views
Skip to first unread message
Ashok Hariharan
May 13, 2009, 6:41:09 AM5/13/09
to akomantoso-dev
Hi Luca,
you can find the class library source for the section info extractor
at this link in svn:
<http://bungeni-editor.googlecode.com/svn/plugins/ExtractSections>
(required libraries are odfdom / xerces and log4j , you can find the
correct versions of those
libraries under here :
http://bungeni-editor.googlecode.com/svn/external_libs/ )
It outputs the required information as a string ...
Let me know if this meets your requirements
Ashok
Luca Cervone
May 13, 2009, 6:42:29 AM5/13/09
to akomant...@googlegroups.com
Thank you ashok, I'll try it soon.
Ciao
Luca
mobile phone: 0039 348 26 27 545
home phone: 0039 051 199 82 854
skype: cervoneluca
Ashok Hariharan
May 15, 2009, 2:56:42 AM5/15/09
to akomant...@googlegroups.com
Hello Luca,
Did you update the error translator with the library i sent you ?
Also some markup has changed since when you last updated the
translator -- so i am going to update a couple of the mini-xslts in
the translator ...i hope you are ok with that ? I will branch the
xslts i change so the original is not touched.
Ashok
Did you update the error translator with the library i sent you ?
Also some markup has changed since when you last updated the
translator -- so i am going to update a couple of the mini-xslts in
the translator ...i hope you are ok with that ? I will branch the
xslts i change so the original is not touched.
Ashok
Luca Cervone
May 15, 2009, 6:29:08 AM5/15/09
to akomant...@googlegroups.com
Ashok, I'm working on it but I have the flu so I'm working very slow.
Of course you can update the miniXLST but alert me when you finish so I can remember to update the code from the SVN.
Thank you and sorry for the delay.
Ciao
Luca
Ashok Hariharan
May 19, 2009, 2:28:51 AM5/19/09
to akomant...@googlegroups.com
Hello Luca,
Did you make any progress on the error reporting using the library i
had sent ... ?
Secondly, I don't quite understand how you intend to use the section
information that the library returns to pin-point the error ... since
a section can encompass quite a large part of the document and span
multiple pages ... If you intend to approximate to the nearest parent
node from where the error originates, perhaps a better approach is to
use both the section information and the n-th paragraph ... something
like :
//text:section[@text-name='sectioncontainingerror']/text:p[33] (i.e
error in paragraph 33 in section called 'sectioncontainingerror' ...
Ashok
Did you make any progress on the error reporting using the library i
had sent ... ?
Secondly, I don't quite understand how you intend to use the section
information that the library returns to pin-point the error ... since
a section can encompass quite a large part of the document and span
multiple pages ... If you intend to approximate to the nearest parent
node from where the error originates, perhaps a better approach is to
use both the section information and the n-th paragraph ... something
like :
//text:section[@text-name='sectioncontainingerror']/text:p[33] (i.e
error in paragraph 33 in section called 'sectioncontainingerror' ...
Ashok
Luca Cervone
May 19, 2009, 3:48:59 AM5/19/09
to akomant...@googlegroups.com
Dear Ashok,
I'm just returned at work. Later in the day I'll give you something so you can see how I intend to use the sections.
Did you modify some mini-XSLT?
Reply all
Reply to author
Forward
0 new messages