Re: User Types
Hi Andy, what kind of user are you? ...strange question... I do all the stuff, programming the server, creating the procedures to retrieve data from the database, writing the stylesheets for fo, converting from xml to edi, from csv to xml from to... We don't have any technichal authors, because for our kind of documents we do not need one... Holger Am Mittwoch, 9. August 2006 16:40 schrieb [EMAIL PROTECTED]: > I'd be interested to know what types of people are using the FOP engine to > generate documents. > > Could you indicate whether your setup has a dedicated programmer, or team > of programmers, individual author, technical author etc. > > Does the same person who writes the content setup your FOP transformations. > > thanks > > Andy R > > -- > This message was sent on behalf of [EMAIL PROTECTED] at > openSubscriber.com > http://www.opensubscriber.com/messages/fop-users@xmlgraphics.apache.org/top >ic.html > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: User Types
That sounds a lot like what I'm doing for my current client, Glen. I love Ant. Jay Bryant Bryant Communication Services - Original Message - From: "Glen Mazza" <[EMAIL PROTECTED]> To: Sent: Wednesday, August 09, 2006 11:50 AM Subject: Re: User Types > We use XSL/XSLT for reports and for Docbook. > > Docbook: Tech Writer creates the XML documents that will be fed through > the Docbook stylesheets. Uses Eclipse WTP for this. The developer > creates an Ant script that automates all of the tech writer's doc > generation and publishing-to-web-server tasks so the writer only needs > to know how to call Ant tasks from the script for these chores. (Over > time, our tech writer has also learned to modify and add new tasks in.) > > Docbook Maintenance: Tech Writer enters the documentation changes > (after getting information from developers) and republishes them via Ant > scripts. > > XSL/XSLT Reports: Very nice separation of data from presentation > chores. Developer first defines the input format of the XML document > that will have the report's data. The tech writer creates the > stylesheet that will layout the report, usually leveraging previously > created stylesheets, and also creates sample XML documents with dummy > data for testing the stylesheets. Tech writer also maintains any header > stylesheets that will be imported by multiple document stylesheets. > Developer creates the SQL, SAX Event generation, etc. that generate the > XML document. > > For a non-programming tech writer, XSLT coding presents a pleasantly > not-very-steep but continuous learning curve--simple stuff can be done > without any training at all (i.e., change the title in an already > existing document from FOO to BAR -- anyone with a text editor can S & R > on FOO to do this without needing to know a thing about XSLT) with more > complex tasks (XSLT templates and functions and the like) gradually > added in over time. > > XSL/XSLT Reports Maintenance: Tech Writer is responsible for making > stylesheet/reports look "nice" and presentation/layout change requests, > developer is responsible for bringing in new/different data elements > from the SQL, as well as overall maintenance of the web application. > > The main thing when doing Docbook and XSL/XSLT in production, especially > with non-programming employees is: Ant, Ant, Ant! Keep everything > automated and defined (classpaths, working directories, web servers to > FTP to, etc.) within Ant and outside local IDEs/computer environment > variables. (Among other benefits, if some developers prefer this IDE > and others another IDE, it won't matter, because everything is > configured within the Ant build file.) The second most important thing > is CVS/SVN, CVS/SVN, CVS/SVN! Eclipse makes it easy to immediately > commit new changes. > > Glen > > [EMAIL PROTECTED] wrote: > > >I'd be interested to know what types of people are using the FOP engine to generate documents. > > > >Could you indicate whether your setup has a dedicated programmer, or team of programmers, individual author, technical author etc. > > > >Does the same person who writes the content setup your FOP transformations. > > > >thanks > > > >Andy R > > > >-- > >This message was sent on behalf of [EMAIL PROTECTED] at openSubscriber.com > >http://www.opensubscriber.com/messages/fop-users@xmlgraphics.apache.org/top ic.html > > > >- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: User Types
We use XSL/XSLT for reports and for Docbook. Docbook: Tech Writer creates the XML documents that will be fed through the Docbook stylesheets. Uses Eclipse WTP for this. The developer creates an Ant script that automates all of the tech writer's doc generation and publishing-to-web-server tasks so the writer only needs to know how to call Ant tasks from the script for these chores. (Over time, our tech writer has also learned to modify and add new tasks in.) Docbook Maintenance: Tech Writer enters the documentation changes (after getting information from developers) and republishes them via Ant scripts. XSL/XSLT Reports: Very nice separation of data from presentation chores. Developer first defines the input format of the XML document that will have the report's data. The tech writer creates the stylesheet that will layout the report, usually leveraging previously created stylesheets, and also creates sample XML documents with dummy data for testing the stylesheets. Tech writer also maintains any header stylesheets that will be imported by multiple document stylesheets. Developer creates the SQL, SAX Event generation, etc. that generate the XML document. For a non-programming tech writer, XSLT coding presents a pleasantly not-very-steep but continuous learning curve--simple stuff can be done without any training at all (i.e., change the title in an already existing document from FOO to BAR -- anyone with a text editor can S & R on FOO to do this without needing to know a thing about XSLT) with more complex tasks (XSLT templates and functions and the like) gradually added in over time. XSL/XSLT Reports Maintenance: Tech Writer is responsible for making stylesheet/reports look "nice" and presentation/layout change requests, developer is responsible for bringing in new/different data elements from the SQL, as well as overall maintenance of the web application. The main thing when doing Docbook and XSL/XSLT in production, especially with non-programming employees is: Ant, Ant, Ant! Keep everything automated and defined (classpaths, working directories, web servers to FTP to, etc.) within Ant and outside local IDEs/computer environment variables. (Among other benefits, if some developers prefer this IDE and others another IDE, it won't matter, because everything is configured within the Ant build file.) The second most important thing is CVS/SVN, CVS/SVN, CVS/SVN! Eclipse makes it easy to immediately commit new changes. Glen [EMAIL PROTECTED] wrote: I'd be interested to know what types of people are using the FOP engine to generate documents. Could you indicate whether your setup has a dedicated programmer, or team of programmers, individual author, technical author etc. Does the same person who writes the content setup your FOP transformations. thanks Andy R -- This message was sent on behalf of [EMAIL PROTECTED] at openSubscriber.com http://www.opensubscriber.com/messages/fop-users@xmlgraphics.apache.org/topic.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: User Types
When I first started using FOP, I was a technical writer (often called technical author in places where they speak the Queen's rather than the President's English). I was fed up with both Word and FrameMaker, so I implemented an XML-based documentation system, which included FOP. I no longer write. Instead, I spend all of my time setting up similar systems for various clients. So, I guess I have been two kinds of users: a technical writer (or technical author, if you prefer) and a consulting developer. I am also aware of companies (Intel, for one) that have developers dedicated to document production (though they also work on authoring tools and content management). FWIW Jay Bryant Bryant Communication Services - Original Message - From: <[EMAIL PROTECTED]> To: Sent: Wednesday, August 09, 2006 9:40 AM Subject: User Types > I'd be interested to know what types of people are using the FOP engine to generate documents. > > Could you indicate whether your setup has a dedicated programmer, or team of programmers, individual author, technical author etc. > > Does the same person who writes the content setup your FOP transformations. > > thanks > > Andy R > > -- > This message was sent on behalf of [EMAIL PROTECTED] at openSubscriber.com > http://www.opensubscriber.com/messages/fop-users@xmlgraphics.apache.org/topic.html > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
User Types
I'd be interested to know what types of people are using the FOP engine to generate documents. Could you indicate whether your setup has a dedicated programmer, or team of programmers, individual author, technical author etc. Does the same person who writes the content setup your FOP transformations. thanks Andy R -- This message was sent on behalf of [EMAIL PROTECTED] at openSubscriber.com http://www.opensubscriber.com/messages/fop-users@xmlgraphics.apache.org/topic.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
