Re: Office 2007, XSL-FO, and the Adobe "Save as PDF"

"JFOR, an open source XSL-FO to RTF converter has been integrated into
Apache FOP. This will create an RTF (rich text format) document that
will attempt to contain as much information from the fo document as
possible. The RTF output follows Microsoft's RTF specifications and
produces best results on Microsoft Word."

Well, guess theres no need to consider this for GSOC for next year...
:)  Although theres got to be at least a few XSL* and/or other related
transformation/processing engines that could use some touch up work
that the community as a whole could benefit from.

Anybody happen to know of any off hand that would be useful if
finished off and as such could benefit from the GSOC program?

Aren't they integrating it with FOP?

http://xmlgraphics.apache.org/fop/0.92/output.html#rtf

This is for the development version of FOP.

M. David Peterson wrote:

> It seems the last release date/version number suggests this is a "dead
> in the water" project...
>
> jfor      V0.7.2rc1      July 16, 2003
>
> That's too bad... it seems it could be quite a useful tool if it was
> completed...
>
> Of course the source is sitting there wide open and ready to be
> finished off...  Too late as a Google Summer of Code project, but
> theres always next year.  It seems like it could be a good candidate
> for the right college student to come along and propose in about nine
> months or so from now when next years "proposal season" opens up...
> Something to keep in mind for any students out there that this might
> find some interest with...
>
> Would also require a mentor to guide the development...  Again,
> something to keep in mind for next year if acting as the mentor for a
> project like this interests any of you that have this level of
> expertise.
>
> On 6/4/06, Kamal Bhatt <kbhatt@xxxxxxxxx> wrote:
>
>>
>> Thanks, I was thinking about using it instead of FOP. Thanks for saving
>> me the hassle :).
>> Winchel 'Todd' Vincent III wrote:
>>
>> >The JFOR tool is the only tool that we could find that claims to do
>> XML --> XSL-FO --> RTF.  We found that it did not meet our needs.
>> (We evaluated it twice, once about a year ago and then again about 3
>> or 4 months ago.)  As I recall, I believe the XSL-FO implementation
>> is too limited for our use (more limited than Apache FOP), so there
>> were XSL-FO features that we were using that JFOR did not support.
>> >
>> >Todd
>> >
>> >-----Original Message-----
>> >
>> >
>> >>From: Kamal Bhatt <kbhatt@xxxxxxxxx>
>> >>Sent: Jun 4, 2006 9:09 PM
>> >>To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
>> >>Subject: Re:  Office 2007, XSL-FO, and the Adobe "Save as PDF"
>> (non)native-support...
>> >>
>> >>
>> >>Winchel 'Todd' Vincent III wrote:
>> >>
>> >>
>> >>
>> >>>XML[1] --> XSL-FO[1] --> Apache FOP --> PDF
>> >>>XML[1] --> XSL-FO[1] --> ?Tool? --> RTF
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>Never used it, but :
>> >>
>> >>http://sourceforge.net/projects/jfor
>> >>
>> >>--
>> >>Kamal Bhatt
>> >>
>> >>
>> >>--
>> >>Disclaimer: This email is confidential and may contain privileged
>> information for the sole use of the person or business to which it is
>> addressed. If you are not the intended recipient, please notify the
>> sender by return e-mail or phone as you must not view, disseminate,
>> distribute or copy this email without our consent. We do not accept
>> any liability in connection with any computer virus, data corruption,
>> incompleteness, or unauthorised amendment of this email. It is the
>> sole responsibility of the receiver to scan for viruses before opening.
>> >
>> >
>> >
>> >
>>
>>
>> --
>> Kamal Bhatt
>>
>>
>> --
>> Disclaimer: This email is confidential and may contain privileged
>> information for the sole use of the person or business to which it is
>> addressed. If you are not the intended recipient, please notify the
>> sender by return e-mail or phone as you must not view, disseminate,
>> distribute or copy this email without our consent. We do not accept
>> any liability in connection with any computer virus, data corruption,
>> incompleteness, or unauthorised amendment of this email. It is the
>> sole responsibility of the receiver to scan for viruses before opening.
>>
>>
>
>

--
Kamal Bhatt

--
Disclaimer: This email is confidential and may contain privileged information for the sole use of the person or business to which it is addressed. If you are not the intended recipient, please notify the sender by return e-mail or phone as you must not view, disseminate, distribute or copy this email without our consent. We do not accept any liability in connection with any computer virus, data corruption, incompleteness, or unauthorised amendment of this email. It is the sole responsibility of the receiver to scan for viruses before opening.

--
<M:D/>

M. David Peterson
http://www.xsltblog.com/