Matt, Thanks again for your help. I haven't gotten it to work yet, but I am still plugging away at it.
As a developer in the healthcare industry, I can understand your curiousity. My company handles the archival of millions of records at UPMC. Essentially, we parse disparate data and archive it so that users can access data from different systems in one place. Great idea...huh? We have a subsidiary company which offers a transcription service, Scribes Online. It is an Internet-based transcription service for which I developed the interim solution for the online retrieval of their physician's dictations. There is currently now a small team of us who are wrapping up development of the replacement to my interim solution. The only road block seems to be the linefeed-preserve issue. I can't get into details without breeching non-disclosure agreements and such, but here it is... A Physican dictates a report via phone The Medical Trancriptionist transcribes the document into an application which feeds into Oracle. We pull the document from Oracle using JSP and servlets. The XML is generated on the fly with JSP. (Up until this point I am not involved in development) I am on the Web GUI side where I create stylesheets that enable the physician to edit, view a "read only" copy and/or print a final PDF copy of the document. We also offer a batch printing, sorting and searching capabilities. After a certain period of time specified by the client, we archive the data and can do very detailed and advanced analysis for the client. We would sincerely appreciate any more help with this issue. It would be a terrible shame for us and FOP for the project to go BUST. Thanks again! Rachael Matt Savino wrote: > I work for a giant healthcare company, and it's still hard for me to > imagine how the data comes from --somewhere-- then is inserted into an > fo: document with no chance for any text manipulation. Not saying I > don't believe it, Id just love to hear the situation. > > So what about some kind of quick n' dirty little extension to do the > work until linespace-treatment="preserve" is implemented. (Is it in the > plans to attempt to implement everything in the FO spec?) I haven't > started on my table-header with (Cont) extension yet, but when I do I'll > let the group know how it goes. > > Arved Sandstrom wrote: > > > > At 09:52 AM 11/2/01 -0800, you wrote: > > >Our application also needs linefeeds preserved in certain cases. We > > >convert them at the stylesheet level. Here's how we do it: > > [ SNIP ] > > >Like I said, I have no idea if you're even using stylesheets. I have a > > >feeling if you're talking with Arved, this avenue has already been > > >explored. But I figured I'd throw it out there just in case. By the way > > >if anyone knows of a slicker method to do what I'm doing above (ie some > > >sort of Perl-style replace, or Java-style string tokenizer > > >functionality), please chime in. > > > > This possibility, or something essentially similar, came up. That is, I > > suggested a workaround. Rachael explained the production scenario, and it > > appears to make sense to me that extra processing of the content before it > > gets to the formatter is not acceptable. So unless something has changed we > > are definitely talking about source code changes. > > > > I did Rachael a disservice by underestimating the scope of the fix (I looked > > at the FOP code and started working on this, and it wasn't so > > straightforward) and overestimating the amount of time I had available to do > > something about it. Work at my last company was pretty crazy for a lot of > > this year, and I should have taken that into account, and I apologize for > > being naively optimistic. In any case that last company has now folded and > > at the moment I am _not_ in a position to assist. :-) > > > > Regards, > > Arved Sandstrom > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, email: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
