xml management and publishing

Next topic

Author	Message
Terje J. Hanssen	Wednesday 20 April 2005 7:25:39 pm As far as I have read, eZ publish applies in priciple xml "formatting" tags on the content, combined with CSS stylesheets and special "templates" to format, render and layout text content for web (xhtml) and correspondingly for pdf. The dedicated xml way however, to publish "real" xml structured source documents like e.g DocBook xml, makes use of XSL instead, that is typical: a) XSLT stylesheet and XSLT processor to generate XHTML b) XSL-FO and FOP to generate PDF 1) I wonder if eZ publish is planned to move into the direction of the XSL way above? 2) Next I wonder if eZ publish is planned to be able to manage, doing intelligent indexing, searching and sorting and lastly publish documents that is fully xml tagged ("real" xml custom applications)? From earlier discussions on the OOo xml-dev list, some clever people pointed on a trick to place "styles" onto the OOo xml elements. This combined with an external XSLT filter would produce the desired target xml with the structure intended, e.g <text:span style:auto-style="keyword">Data</text:span> could then be <keyword>Data</keyword>. Terje J. Hanssen

Author

Message

Wednesday 20 April 2005 7:25:39 pm

As far as I have read, eZ publish applies in priciple xml "formatting" tags on the content, combined with CSS stylesheets and special "templates" to format, render and layout text content for web (xhtml) and correspondingly for pdf.

The dedicated xml way however, to publish "real" xml structured source documents like e.g DocBook xml, makes use of XSL instead, that is typical:
a) XSLT stylesheet and XSLT processor to generate XHTML
b) XSL-FO and FOP to generate PDF

1) I wonder if eZ publish is planned to move into the direction of the XSL way above?

2) Next I wonder if eZ publish is planned to be able to manage, doing intelligent indexing, searching and sorting and lastly publish documents that is fully xml tagged ("real" xml custom applications)?

From earlier discussions on the OOo xml-dev list, some clever people pointed on a trick to place "styles" onto the OOo xml elements. This combined with an external XSLT filter would produce the desired target xml with the structure intended, e.g <text:span style:auto-style="keyword">Data</text:span> could then be <keyword>Data</keyword>.

Terje J. Hanssen

eZ debug

Timing:	Jan 18 2025 16:15:52
Script start
Timing:	Jan 18 2025 16:15:52
Module start 'layout'
Timing:	Jan 18 2025 16:15:52
Module start 'content'
Timing:	Jan 18 2025 16:15:52
Module end 'content'
Timing:	Jan 18 2025 16:15:52
Script end

Main resources:

Total runtime	0.0130 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0047	587.9141	152.6250
Module start 'layout'	0.0047	0.0027	740.5391	39.4453
Module start 'content'	0.0074	0.0040	779.9844	85.2109
Module end 'content'	0.0114	0.0016	865.1953	30.3047
Script end	0.0130		895.5000

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0021	16.5092	14	0.0002
Check MTime	0.0010	7.3713	14	0.0001
Mysql Total
Database connection	0.0005	4.1773	1	0.0005
Mysqli_queries	0.0024	18.6373	3	0.0008
Looping result	0.0000	0.0862	1	0.0000
Template Total	0.0013	10.0	1	0.0013
Template load	0.0006	4.8322	1	0.0006
Template processing	0.0007	5.1239	1	0.0007
Override
Cache load	0.0004	3.4013	1	0.0004
General
dbfile	0.0003	1.9410	8	0.0000
String conversion	0.0000	0.0550	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs