xmlroff-list — xmlroff XSL formatter discussion list

[xmlroff] xmlroff release is delayed

[Tony G. <Ton...@Su...>]

But if you've been looking for it, you'd have realised that already.

I had a bad sector on my Linux partition, so I moved to a Linux on a
different partition, but now I have a font problem:

------------------------------------------------------------
./xmlroff xmlroff.fo

(process:6569): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed

(process:6569): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed

** (process:6569): CRITICAL **: _pango_engine_shape_shape: assertion `PANGO_IS_FONT (font)' failed

** ERROR **: file shape.c: line 75 (pango_shape): assertion failed: (glyphs->num_glyphs > 0)
aborting...
Aborted
------------------------------------------------------------

It makes it a bit hard to test xmlroff.

Regards,


Tony.

Re: [xmlroff] Probably newbie problem

[Tony G. <Ton...@Su...>]

Misty Stanley-Jones <mi...@bo...> writes:
> Hi all,

Welcome to the xmlroff list.

> I have just installed xmlroff from source.  I have a set of docbook files that 

From xmlroff 0.3.3 or from CVS?

> I am able to generate HTML from, with xsltproc.  Now I would like to create a 
> PDF of them.  When I run the following command:
>
> xmlroff -o index.pdf 
> index.docbook /usr/share/xml/docbook/stylesheet/nwalsh/current/eclipse/eclipse.xsl
>
> I get the output from the stylesheet, and then at the very end I get the 
> following error:
>
> (process:16005): libfo-CRITICAL **: file result-to-fo.c: line 973 
> (fo_xml_doc_to_fo_and_area_trees): assertion `res->children != NULL' failed
> libfo-Message: Error: No area tree present
>
> I am at a loss what to do.  Please help me debug this.

You haven't given much to go on.

Can you email me 'index.docbook' and 'eclipse.xsl' (or a pointer to
where to get eclipse.xsl)?

Have you tried running the libfo-compat.xsl stylesheet to remove many
things that xmlroff would find to be problematic?

Regards,


Tony.

[xmlroff] Probably newbie problem

[Misty Stanley-J. <mi...@bo...>]

Hi all,

I have just installed xmlroff from source.  I have a set of docbook files that 
I am able to generate HTML from, with xsltproc.  Now I would like to create a 
PDF of them.  When I run the following command:

xmlroff -o index.pdf 
index.docbook /usr/share/xml/docbook/stylesheet/nwalsh/current/eclipse/eclipse.xsl

I get the output from the stylesheet, and then at the very end I get the 
following error:

(process:16005): libfo-CRITICAL **: file result-to-fo.c: line 973 
(fo_xml_doc_to_fo_and_area_trees): assertion `res->children != NULL' failed
libfo-Message: Error: No area tree present

I am at a loss what to do.  Please help me debug this.

Misty

[xmlroff] Close xmlroff Wiki?

[Tony G. <Ton...@Su...>]

The SourceForge folks are about to make the xmlroff web site read-only
on the SourceForge web servers, which is going to break the current
Wiki configuration.

Since the Wiki is dormant (to put it politely), is there any reason to
keep the Wiki?

How many of you have read at least part of the Wiki?

For any of you, did it increase your interest in the xmlroff project?

For any of you, did it decrease it?

Regards,


Tony.

[xmlroff] Re: Next for xmlroff?

[Tony G. <Ton...@Su...>]

(Bringing a side discussion back to the list, with Julian's
permission.)

Julian Rosse <gn...@th...> writes:
>> Now that xmlroff 0.3.3 is out, are you able to keep working on
>> xmlroff?
>
> Sure.

Great.

>> If so, is there anything in particular that you want to work on?
>
> Not really.  I still have to do a fair amount of code-reading, etc. to get
> to the point of really being able to contribute.  I'd guess I'll start putting
> in that time soon.

That would be good, but don't feel pressured to contribute.

>> The parts that I want to see implemented are graphics support and
>> static content, but I'm also feeling that I should spend time
>> documenting how xmlroff works.  What do you see as the priorities for
>> xmlroff?
>
> Those sound good.  The SVG support still intrigues me.  I personally want to
> get to a point with the codebase such that I can take on more significant tasks.
> But I'm happy to help out wherever required - I can certainly do web page stuff,
> etc.

If you are interested in SVG, then please work on it.

There's two immediate applications for SVG in xmlroff:

 - As an output format.

   I noticed yesterday that GNOME Print supports SVG output, so it may
   be as simple as replacing one string in fo-doc-gp.c.

 - As an instream-foreign-object

Are you able to take on one or both of those tasks (with my help as
needed and with no deadline attached)?

> The cairo stuff sounds interesting.  If it's the "way of the future" (sorry,
> I hate unnecessary double quotes), will xmlroff want a cairo backend?

If the rest of GNOME-like things are going that way, I expect xmlroff
will too.

Regards,


Tony.

[xmlroff] Fixing memory leaks

[Tony G. <Ton...@Su...>]

FYI, I've been running valgrind and fixing memory leaks, and for the
xmlroff currently in CVS, the memory lost when formatting 'xmlroff.fo'
is less than half what it was when I started.

Fixing memory leaks is something almost anyone can do: all it requires
is valgrind, a bit of patience, and a bit of C knowledge.  Memory leak
patches are more than welcome.

On the more ambitious side of things, it would be useful to modify
xmlroff.c so it can run the same input multiple times to show up the
leaks that increase versus those that are constant and to modify the
testing framework so it has an option to collect and compare valgrind
results.

Regards,


Tony.

[xmlroff] ANN: Julian Rosse is xmlroff committer

[Tony G. <Ton...@Su...>]

I am pleased to announce that Julian Rosse has accepted developer
status on the xmlroff project.  Actually, Julian has had the status
for a while, and has used it to good effect in developing the
border-related shorthands support that went into xmlroff 0.3.3.

Regards,


Tony.

[xmlroff] ANN: xmlroff 0.3.3 released

[Tony G. <Ton...@Su...>]

xmlroff 0.3.3 is now available from SourceForge:
http://sourceforge.net/projects/xmlroff

The biggest change is the addition of the border-related shorthands
thanks to Julian Rosse.  Tim Waugh contributed some build-related
fixes.

The xmlroff website is yet to be updated, and the release needs to be
announced on the XSL-related mailing lists.  Any takers?

Regards,


Tony.

NEWS
====

Changes between 0.3.2 and 0.3.3

* Added support for 'border', 'border-left', 'border-right',
  'border-top', 'border-bottom', 'border-style', 'border-width', and
  'border-color' properties (Julian Rosse)
* Removed border-related properties and 'padding'from libfo-compat.xsl
* Corrected whitespace handling in libfo-compat.xsl
* Added removal of more unsupported properties in libfo-compat.xsl
* Corrected drawing 'dashed', 'dotted', 'groove', and 'hidden' border
  styles
* Partially re-implemented fo:external-graphic support
* Build fixes to work with latest GCC


ChangeLog
=========

2005-05-01  Tony Graham  <ton...@us...>

	* === Released 0.3.3 ===

	* NEWS: Updated for 0.3.3.

	* fo-context-util.c: Added a g_object_unref() to try to solve a
	memory leak.  No effect.

	* fo-object.c: Minor changes to fo_object_sprintf() and
	fo_object_debug_sprintf() messages.

	* libfo-compat.xsl: Removed border-related template rules since
	border shorthands now supported by xmlroff.

2005-04-25  Tony Graham  <ton...@us...>

	* expr/fo-expr-eval.c: Added handling 'border' property
	expressions with one to three tokens.  Reindented two functions.

	* libfo/fo-xsl-formatter.c: Corrected initial comment.

	* fo/fo-root.c: Forcing 'media-usage' value to 'paginate' since
	that's all that's supported.

	* property/fo-property-util.c: fo_property_util_resolve_wsc_enum()
	returns FoWsc, not individual component since its type can be
	ambiguous.

2005-04-07  Julian Rosse  <gn...@th...>

	* fo-context.c, fo-context.h, fo-context-private.h,
	fo-context-util.c, property/Makefile.am,
	property/fo-all-property.h, property/fo-property-border.c,
	property/fo-property-border.h,
	property/fo-property-border-left.c,
	property/fo-property-border-left.h,
	property/fo-property-border-right.c,
	property/fo-property-border-right.h,
	property/fo-property-border-top.c,
	property/fo-property-border-top.h,
	property/fo-property-border-bottom.c,
	property/fo-property-border-bottom.h,
	property/fo-property-eval.c:
	Added code for 'border', 'border-left', 'border-right', 'border-top',
	and 'border-bottom' properties.

2005-03-31  Tony Graham  <ton...@us...>

	* libfo/fo-doc-gp.c: Added fo_doc_gp_do_callbacks(),
	fo_doc_gp_do_line_callbacks(), and fo_doc_gp_do_run_callbacks() to
	handle PangoXSL 'callback' attributes after GNOME Print has
	rendered the text of the layout.

	* fo/fo-root.c: Added fo_root_resolve_media_usage() to force
	acceptable 'media-usage' value.

	* fo/fo-fo.c, fo/fo-fo.h: Added FO_FO_ERROR_DATATYPE_REPLACE error
	message.

	* fo/fo-external-graphic.c: Commented out a g_assert_not_reached()
	since is reached by half-implemented graphics support.

	* expr/fo-expr-eval.c: Moved an fo_expr_context_push_stack() to
	stop warnings.

2005-03-20  Tony Graham  <ton...@us...>

	* datatype/fo-wsc.c: Allowed FoWsc components to be NULL.

2005-03-18  Tony Graham  <ton...@us...>

	* libfo-compat.xsl: Removed message about normalizing text nodes.

	* libfo-compat.xsl: Removed 'text()' template rule that did
	normalize-space() on all text.  It has been unneeded since
	addition of <xsl:preserve-space>.

2005-03-17  Tony Graham  <ton...@us...>

	* expr/fo-expr-eval.c: Partially completed evaluating
	width-style-color expressions.

	* property/fo-property-util.c: Added checking specific width and
	style enums when validating width and style.

	* libfo-compat.xsl: Added removal of many more unsupported
	properties.

2005-03-16  Tony Graham  <ton...@us...>

	* README: Added note about compatibility and libfo-compat.xsl.

	* area-to-pdf.c: Corrected (hopefully) drawing of 'dash',
	'dotted', and 'groove' border styles.

	* fo-context-util.c (fo_context_util_border_resolve): Handling
	'hidden' style equivalent to 'none' (but will be different for
	tables!).

2005-03-15  Tony Graham  <ton...@us...>

	* libfo-compat.xsl: Added 'margin' to set of properties removed by
	stylesheet.

	* expr/fo-expr-eval.c: Moved a fo_expr_context_push_stack() to
	where it is needed.

	* libfo/fo-doc-gp.c (fo_doc_gp_setdash): Set segment count to zero
	when solid.

2005-03-11  Tony Graham  <ton...@us...>

	* configure.in: Zeroed interface age and binary age since FoObject
	changed.

	* xmlroff.spec.in: Build fixes (Tim Waugh).

	* datatype/fo-tblr.c: Removed some unused includes.

	* property/fo-property-util.h, expr/fo-expr-eval.h,
	property/fo-property-util.c, expr/fo-expr-eval.c,
	datatype/Makefile.am, fo-all-datatype.h, datatype/fo-wsc.c,
	datatype/fo-wsc.h: Added FoWsc datatype for 'width-style-color'
	for 'border' shorthands.

2005-03-10  Tony Graham  <ton...@us...>

	* property/fo-property.c, datatype/fo-length-bp-ip-d.c,
	datatype/fo-length-conditional.c, datatype/fo-length-range.c,
	datatype/fo-length.c, datatype/fo-name.c, datatype/fo-number.c,
	datatype/fo-pcw.c, datatype/fo-percentage.c, datatype/fo-space.c,
	datatype/fo-string.c, datatype/fo-tblr.c, datatype/fo-unknown.c,
	datatype/fo-uri-specification.c, fo/fo-fo.c,
	datatype/fo-boolean.c, datatype/fo-char.c, datatype/fo-color.c,
	datatype/fo-enum.c, datatype/fo-error.c, datatype/fo-expression.c,
	datatype/fo-id.c, datatype/fo-integer.c, datatype/fo-keep.c,
	area/fo-area.c, fo-object.h, fo-node.c, fo-object.c, fo-token.c:
	Renamed FoObject.sprintf to print_sprintf to avoid problems when
	compiling with -D_FORTIFY_SOURCE=2.

	* fo-context.c, fo-context.h, fo-context-private.h,
	fo-context-util.c, property/Makefile.am,
	property/fo-all-property.h, property/fo-property-border-style.c,
	property/fo-property-border-style.h,
	property/fo-property-border-width.c,
	property/fo-property-border-width.h, property/fo-property-eval.c:
	Added 'border-style' and 'border-width' properties (Julian Rosse).

	* Makefile.am: Made XML data directory track the xmlroff version
	number.

	* libfo-compat.xsl: Rewrote message for '@height' template so
	message is correct no matter which attribute is being matched,
	making it easier to add more unsupported properties that will be
	stripped.

	* libfo-compat.xsl: Added xsl:preserve-space for all FOs with
	#PCDATA in their content model.  Removed 'padding' template since
	'padding' supported by xmlroff.  Added
	'fo:region-body/@region-name' template rule (Tim Waugh).

2005-03-06  Tony Graham  <ton...@us...>

	* expr/fo-expr-eval.c, expr/fo-expr-eval.h: Added
	fo_property_eval_border_style() for 'border-style' property.

2005-03-05  Tony Graham  <ton...@us...>

	* fo-context-util.c: fo_context_util_border_resolve(): Added
	resolving 'border-color' (Julian Rosse).

	* configure.in: Upped version to 0.3.3.

2005-03-03  Tony Graham  <ton...@us...>

	* datatype/fo-pcw.c, datatype/fo-pcw.h, datatype/fo-tblr.c,
	datatype/fo-tblr.h: Made initial comments a bit more indicative of
	purpose of datatype.

Re: [xmlroff] Re: xmlroff-list digest, Vol 1 #147 - 1 msg

[Tony G. <Ton...@Su...>]

Bruno Sadiez <bru...@ya...> writes:
...
> Do you confirm that hearders/footers are not supported
> for the moment ? 

No, they are not supported at the moment.

> Do you think I can achieve a descent invoice with
> xmlroff or do you think I'd better find another
> solution?   

If your output depends on headers and footers, then xmlroff is not the
correct choice at this time.

While I and others on this list would appreciate it if you were able
to help out with getting headers and footers working in xmlroff, I
certainly understand that that's not the answer that you were looking
for.

In the event that you do not continue with xmlroff, I wish you well in
your use of XSL and hope that you will continue to keep an eye on
xmlroff developments.

Regards,


Tony.

Re: [xmlroff] Re: I've run into build errors compiling xmlroff

[Tony G. <Ton...@Su...>]

Bruno Sadiez <bru...@ya...> writes:
> Hello James,
>
> have you installed pango-xsl ?

Although 'configure' (using 'pkg-config') could find the pkg-config
configuration for PangoXSL, the headers don't appear to be installed
where the pkg-config configuration file says they are.  Is there a
'pangoxsl' directory at
/home/prologic/var/cwd/local/projects/crux/tmp/pangoxsl/work/pkg/usr/=
include/pangoxsl?

Regards,


Tony.

> regards
> Bruno
>
>> Message: 3
>> Date: Sat, 9 Apr 2005 02:29:08 +1000
>> From: James Mills <pro...@sh...>
>> To: xml...@li...
>> Subject: [xmlroff] xmlroff build errors
>>=20
>>=20
>> --uAKRQypu60I7Lcqm
>> Content-Type: text/plain; charset=3Dus-ascii
>> Content-Disposition: inline
>>=20
>> HI,
>>=20
>> I've run into build errors compiling xmlroff,
>> wondering if anyone can
>> help solve this ?
>>=20
>> See attached log file.
>>=20
>> Using gcc:
>> gcc version 3.3.4 (CRUX)
>>=20
>> cheers
>> James
>
>
>
> =09
>
> =09
> =09=09
> __________________________________________________________________
> D=C3=A9couvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage=
 pour vos mails !=20
> Cr=C3=A9ez votre Yahoo! Mail sur http://fr.mail.yahoo.com/
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real u=
sers.
> Discover which products truly live up to the hype. Start reading no=
w.
> http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
> _______________________________________________
> xmlroff-list mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlroff-list

--=20
Tony Graham
Sun Microsystems Ireland                           Phone: +353 1 8199=
708
East Point Business Park, Dublin 3                   Internal: (70)19=
708

[xmlroff] Re: I've run into build errors compiling xmlroff

[Bruno S. <bru...@ya...>]

Hello James,

have you installed pango-xsl ?

regards
Bruno

> Message: 3
> Date: Sat, 9 Apr 2005 02:29:08 +1000
> From: James Mills <pro...@sh...>
> To: xml...@li...
> Subject: [xmlroff] xmlroff build errors
> 
> 
> --uAKRQypu60I7Lcqm
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> 
> HI,
> 
> I've run into build errors compiling xmlroff,
> wondering if anyone can
> help solve this ?
> 
> See attached log file.
> 
> Using gcc:
> gcc version 3.3.4 (CRUX)
> 
> cheers
> James



	

	
		
__________________________________________________________________
Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails ! 
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/

[xmlroff] xmlroff build errors

[James M. <pro...@sh...>]

HI,

I've run into build errors compiling xmlroff, wondering if anyone can
help solve this ?

See attached log file.

Using gcc:
gcc version 3.3.4 (CRUX)

cheers
James

-- 
--
-"Problems are Solved by Method"
-

[xmlroff] Re: xmlroff-list digest, Vol 1 #147 - 1 msg

[Bruno S. <bru...@ya...>]

hello Tony,

there is nothing to do with Valgring. Just launch it
with the desired option.

I would love to help you on this project, but I fear I
do not have the required skills. I began C programming
3 month ago and I hardly know linux.
Do you confirm that hearders/footers are not supported
for the moment ? 
Do you think I can achieve a descent invoice with
xmlroff or do you think I'd better find another
solution?   

Regards
Bruno



	

	
		
__________________________________________________________________
Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails ! 
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/

Re: [xmlroff] Re: xmlroff-list digest, Vol 1 #146 - 3 msgs

[Tony G. <Ton...@Su...>]

Bruno Sadiez <bru...@ya...> writes:
> Good news: it works and it works screamingly fast !
> 112 invoices per minutes on a pentium 1.6 Ghz laptop
> which is really great. (compared to 15-20 invoices per
> minute with FOP)

Cool!

> 1) As expected there seems to be memory leaks.
>
> here's an very small excerpt of what Valgrind is
> reporting:

What did you have to do to set up xmlroff to run with valgrind?

> 2)The  invoices are really bigger than those obtained
> with FOP.  63,7 KB compared to  5.6 KB for the same
> invoice.

The fonts are embedded in the PDF.

I have an impression that recent libgnomeprint has some control for
not embedding fonts, but I haven't had time to follow up on the idea.

> 3) Some features seem to be unsupported. No
> header/footer and some of the information has vanished
> (name and address of the customer for instance). I'll
> check on the web site for the unsupported features.
> I hope there is a way to solve those problems.

Patches are welcome.

If you want help understanding any part of xmlroff, just ask.

> Thank you Stefan and Tony for your help.

No problem.

Regards,


Tony.

[xmlroff] Re: xmlroff-list digest, Vol 1 #146 - 3 msgs

[Bruno S. <bru...@ya...>]

hello

Good news: it works and it works screamingly fast !
112 invoices per minutes on a pentium 1.6 Ghz laptop
which is really great. (compared to 15-20 invoices per
minute with FOP)

1) As expected there seems to be memory leaks.

here's an very small excerpt of what Valgrind is
reporting:
==4489== 160632 (129028 direct, 31604 indirect) bytes
in 8613 blocks are definitely lost in loss record 110
of 116
==4489==    at 0x1B90459D: malloc
(vg_replace_malloc.c:130)
==4489==    by 0x1BFF9A46: g_malloc (gmem.c:137)
==4489==    by 0x1C009A78: g_strdup (gstrfuncs.c:90)
==4489==    by 0x1BD418AE: fo_string_get_value
(fo-string.c:264)
==4489==    by 0x1BC44A33: fo_block_area_new
(fo-block-area.c:315)
==4489==    by 0x1BC4517D: fo_block_area_new2
(fo-block-area.c:496)
==4489==    by 0x1BC491B6: fo_fo_area_new2
(fo-fo.c:1078)
==4489==    by 0x1BC617F4:
fo_block_layout_children_properties_resolve
(fo-block-layout.c:152)
==4489==    by 0x1BC490BD:
fo_fo_children_properties_resolve (fo-fo.c:1029)
==4489==    by 0x1BC48FD4:
fo_fo_children_properties_resolve_default
(fo-fo.c:979)
==4489==    by 0x1BC490BD:
fo_fo_children_properties_resolve (fo-fo.c:1029)
==4489==    by 0x1BD222AA:
fo_table_part_children_properties_resolve
(fo-table-part.c:272)
==4489==
==4489==
==4489== 834570 (620236 direct, 214334 indirect) bytes
in 22483 blocks are definitely lost in loss record 114
of 116
==4489==    at 0x1B904F75: calloc
(vg_replace_malloc.c:175)
==4489==    by 0x1BFF9ACE: g_malloc0 (gmem.c:154)
==4489==    by 0x1BFB8B75: g_type_create_instance
(gtype.c:1576)
==4489==    by 0x1BFA58FE: ??? (gobject.c:1045)
==4489==    by 0x1BFA50CD: g_object_newv
(gobject.c:942)
==4489==    by 0x1BFA574F: g_object_new_valist
(gobject.c:1026)
==4489==    by 0x1BFA4DBA: g_object_new
(gobject.c:823)
==4489==    by 0x1BC247DD:
fo_context_util_spaces_resolve (fo-context-util.c:635)
==4489==    by 0x1BC27581:
fo_fo_resolve_property_attributes_default
(result-to-fo.c:927)
==4489==    by 0x1BC48DF6:
fo_fo_resolve_property_attributes (fo-fo.c:904)
==4489==    by 0x1BC092D9:
fo_node_g_node_traverse_func (fo-node.c:840)
==4489==    by 0x1BFFDC17: ??? (gnode.c:519)
 
2)The  invoices are really bigger than those obtained
with FOP.  63,7 KB compared to  5.6 KB for the same
invoice.

3) Some features seem to be unsupported. No
header/footer and some of the information has vanished
(name and address of the customer for instance). I'll
check on the web site for the unsupported features.
I hope there is a way to solve those problems.

Thank you Stefan and Tony for your help.
Regards
Bruno


	

	
		
__________________________________________________________________
Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails ! 
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/

Re: [xmlroff] Re: xmlroff-list digest, Vol 1 #145 - 2 msgs

[Tony G. <Ton...@Su...>]

Stefan Seefeld <se...@sy...> writes:
> Bruno Sadiez wrote:
>> hello Tony,
>> thank you for the fast reply.
>> I've tried to do as you said. I cannot get past this
>> error message:
>>  variable `fo_invoice_result_tree' has initializer but
>> incomplete type
>> error: storage size of `fo_invoice_result_tree' isn't
>> known
>> fo_invoice_result_tree is declared as a FoXmlDoc.
>
> This usually means the type has been forward-declared,
> i.e. some #include may be missing to expose a real
> declaration to the code using it.

Stefan is correct.

The problem may be in the two lines of code in my previous post where
I omitted a '*'.  I should have used a FoXmlDoc*, not a FoXmlDoc:

   FoXmlDoc *result_tree = fo_xml_doc_new ();
   fo_xml_doc_set_xml_doc (result_tree, your_xml_doc_ptr);

If that is not the problem, please post the function containing the
problem and the complete compiler error message so we have a better
chance of working out the problem.  Please note, however, that I am
very short of time for the rest of this week and I will have limited
email ability next week.

Regards,


Tony.

Re: [xmlroff] Re: xmlroff-list digest, Vol 1 #145 - 2 msgs

[Stefan S. <se...@sy...>]

Bruno Sadiez wrote:
> hello Tony,
> 
> thank you for the fast reply.
> 
> I've tried to do as you said. I cannot get past this
> error message:
>  variable `fo_invoice_result_tree' has initializer but
> incomplete type
> error: storage size of `fo_invoice_result_tree' isn't
> known
> 
> fo_invoice_result_tree is declared as a FoXmlDoc.

This usually means the type has been forward-declared,
i.e. some #include may be missing to expose a real
declaration to the code using it.

Regards,
		Stefan

[xmlroff] Re: xmlroff-list digest, Vol 1 #145 - 2 msgs

[Bruno S. <bru...@ya...>]

hello Tony,

thank you for the fast reply.

I've tried to do as you said. I cannot get past this
error message:
 variable `fo_invoice_result_tree' has initializer but
incomplete type
error: storage size of `fo_invoice_result_tree' isn't
known

fo_invoice_result_tree is declared as a FoXmlDoc.

Any idea ?




 --- xml...@li... a
écrit : 
> Send xmlroff-list mailing list submissions to
> 	xml...@li...
> 
> To subscribe or unsubscribe via the World Wide Web,
> visit
> 
>
https://lists.sourceforge.net/lists/listinfo/xmlroff-list
> or, via email, send a message with subject or body
> 'help' to
> 	xml...@li...
> 
> You can reach the person managing the list at
> 	xml...@li...
> 
> When replying, please edit your Subject line so it
> is more specific
> than "Re: Contents of xmlroff-list digest..."
> 
> 
> Today's Topics:
> 
>    1. hello (Bruno Sadiez)
>    2. Re: hello (Tony Graham)
> 
> --__--__--
> 
> Message: 1
> Date: Tue, 5 Apr 2005 19:26:11 +0200 (CEST)
> From: Bruno Sadiez <bru...@ya...>
> To: xml...@li...
> Subject: [xmlroff] hello
> 
> I'm currently working  on a project for a
> philanthropic organization. I need to write an
> invoicing application in C. I am not a professional
> developer. 
> What I need to do is fetch data from a database and
> issue PDF invoices.
> I'm using Daniel Veillard's Libxml2 library and I
> can
> issue XML data files with all the required billing
> details. I have written an XSL file with formating
> objects. 
> As this project is supposed to issue many thousand
> invoices at the end of each month, performance is a
> concern. I would like to be able to
> 		Load my XSLFO file only once
> 		Apply it to many thousand dynamically created XML
> data trees.
> 
> 
> 		my code goes:
> 
> 		xmlDocPtr invoice_doc = NULL;
> 		(..... )
> 
> 		invoice_doc = xmlNewDoc(BAD_CAST "1.0");
>  		invoice_root_node = xmlNewNode(NULL, BAD_CAST
> "invoice");
>  		xmlDocSetRootElement(invoice_doc,
> invoice_root_node);
> 
> then I populate the tree with the required billing
> details.
> 
> How is it possible to dynamically transform that
> memory tree into a PDF. I would like to avoid
> writing
> xml data files to disk.
> 
> I hope I'm being clear.
> 
> Thanks in advance
> 
> 
> 	
> 
> 	
> 		
>
__________________________________________________________________
> Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace
> de stockage pour vos mails ! 
> Créez votre Yahoo! Mail sur
> http://fr.mail.yahoo.com/
> 
> 
> --__--__--
> 
> Message: 2
> Date: Wed, 06 Apr 2005 04:26:56 +0100
> From: Tony Graham <Ton...@Su...>
> Subject: Re: [xmlroff] hello
> To: xml...@li...
> 
> Welcome to the xmlroff-list, and thank you for your
> interest in
> xmlroff.
> 
> Bruno Sadiez <bru...@ya...> writes:
> > I'm currently working  on a project for a
> > philanthropic organization. I need to write an
> > invoicing application in C. I am not a
> professional
> > developer. 
> > What I need to do is fetch data from a database
> and
> > issue PDF invoices.
> > I'm using Daniel Veillard's Libxml2 library and I
> can
> > issue XML data files with all the required billing
> > details. I have written an XSL file with formating
> > objects. 
> > As this project is supposed to issue many thousand
> > invoices at the end of each month, performance is
> a
> > concern. I would like to be able to
> > 		Load my XSLFO file only once
> > 		Apply it to many thousand dynamically created
> XML
> > data trees.
> >
> >
> > 		my code goes:
> >
> > 		xmlDocPtr invoice_doc = NULL;
> > 		(..... )
> >
> > 		invoice_doc = xmlNewDoc(BAD_CAST "1.0");
> >  		invoice_root_node = xmlNewNode(NULL, BAD_CAST
> > "invoice");
> >  		xmlDocSetRootElement(invoice_doc,
> > invoice_root_node);
> >
> > then I populate the tree with the required billing
> > details.
> >
> > How is it possible to dynamically transform that
> > memory tree into a PDF. I would like to avoid
> writing
> > xml data files to disk.
> >
> > I hope I'm being clear.
> 
> Yes, you are.
> 
> The short answer is that you can do what you want.
> 
> The public interfaces for the libfo library work on
> filenames for the
> XML input and the XSLT stylesheet (if any) so
> someone using the
> library doesn't have to know or care about libxml2
> or libxslt.
> 
> The public interfaces work on either strings or
> FoXmlDoc objects that
> are really just GObject wrappers of libxml2.
> 
> The FoXSLTFormatter wrapper for libxslt currently
> requires a string
> for the filename for the XSLT stylesheet, which is
> possibly
> shortsighted of me.
> 
> You can, however, do the transformation yourself
> using libxslt and
> then create a FoXmlDoc from the result of your
> transformation using
> fo_xml_doc_set_xml_doc() from fo-xml-doc-private.h:
> 
>    FoXmlDoc result_tree = fo_xml_doc_new ();
>    fo_xml_doc_set_xml_doc (result_tree,
> your_xml_doc_ptr);
> 
> You can then use your 'result_tree' with an
> FoXSLFormatter as in
> xmlroff-libfo.c from the libfo-examples package.
> 
> The other thing to look at is using fo_libfo_init2()
> and supplying
> your own malloc, etc. so that libfo and libxslt use
> the same heap.
> 
> You are trying something that AFAIK hasn't been
> tried before, so I'm
> interested to know how you get on.  I do expect that
> you will find
> that xmlroff has memory leaks, but if you can
> identify them, we can
> look to fixing them.
> 
> Regards,
> 
> 
> Tony.
> 
> 
> 
> 
> --__--__--
> 
> 
=== message truncated === 


	

	
		
__________________________________________________________________
Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails ! 
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/

Re: [xmlroff] hello

[Tony G. <Ton...@Su...>]

Welcome to the xmlroff-list, and thank you for your interest in
xmlroff.

Bruno Sadiez <bru...@ya...> writes:
> I'm currently working  on a project for a
> philanthropic organization. I need to write an
> invoicing application in C. I am not a professional
> developer. 
> What I need to do is fetch data from a database and
> issue PDF invoices.
> I'm using Daniel Veillard's Libxml2 library and I can
> issue XML data files with all the required billing
> details. I have written an XSL file with formating
> objects. 
> As this project is supposed to issue many thousand
> invoices at the end of each month, performance is a
> concern. I would like to be able to
> 		Load my XSLFO file only once
> 		Apply it to many thousand dynamically created XML
> data trees.
>
>
> 		my code goes:
>
> 		xmlDocPtr invoice_doc = NULL;
> 		(..... )
>
> 		invoice_doc = xmlNewDoc(BAD_CAST "1.0");
>  		invoice_root_node = xmlNewNode(NULL, BAD_CAST
> "invoice");
>  		xmlDocSetRootElement(invoice_doc,
> invoice_root_node);
>
> then I populate the tree with the required billing
> details.
>
> How is it possible to dynamically transform that
> memory tree into a PDF. I would like to avoid writing
> xml data files to disk.
>
> I hope I'm being clear.

Yes, you are.

The short answer is that you can do what you want.

The public interfaces for the libfo library work on filenames for the
XML input and the XSLT stylesheet (if any) so someone using the
library doesn't have to know or care about libxml2 or libxslt.

The public interfaces work on either strings or FoXmlDoc objects that
are really just GObject wrappers of libxml2.

The FoXSLTFormatter wrapper for libxslt currently requires a string
for the filename for the XSLT stylesheet, which is possibly
shortsighted of me.

You can, however, do the transformation yourself using libxslt and
then create a FoXmlDoc from the result of your transformation using
fo_xml_doc_set_xml_doc() from fo-xml-doc-private.h:

   FoXmlDoc result_tree = fo_xml_doc_new ();
   fo_xml_doc_set_xml_doc (result_tree, your_xml_doc_ptr);

You can then use your 'result_tree' with an FoXSLFormatter as in
xmlroff-libfo.c from the libfo-examples package.

The other thing to look at is using fo_libfo_init2() and supplying
your own malloc, etc. so that libfo and libxslt use the same heap.

You are trying something that AFAIK hasn't been tried before, so I'm
interested to know how you get on.  I do expect that you will find
that xmlroff has memory leaks, but if you can identify them, we can
look to fixing them.

Regards,


Tony.

[xmlroff] hello

[Bruno S. <bru...@ya...>]

I'm currently working  on a project for a
philanthropic organization. I need to write an
invoicing application in C. I am not a professional
developer. 
What I need to do is fetch data from a database and
issue PDF invoices.
I'm using Daniel Veillard's Libxml2 library and I can
issue XML data files with all the required billing
details. I have written an XSL file with formating
objects. 
As this project is supposed to issue many thousand
invoices at the end of each month, performance is a
concern. I would like to be able to
		Load my XSLFO file only once
		Apply it to many thousand dynamically created XML
data trees.


		my code goes:

		xmlDocPtr invoice_doc = NULL;
		(..... )

		invoice_doc = xmlNewDoc(BAD_CAST "1.0");
 		invoice_root_node = xmlNewNode(NULL, BAD_CAST
"invoice");
 		xmlDocSetRootElement(invoice_doc,
invoice_root_node);

then I populate the tree with the required billing
details.

How is it possible to dynamically transform that
memory tree into a PDF. I would like to avoid writing
xml data files to disk.

I hope I'm being clear.

Thanks in advance


	

	
		
__________________________________________________________________
Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails ! 
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/

[xmlroff] fo:external-graphic

[Tony G. <Ton...@Su...>]

I've done half the work to get fo:external-graphic working with the
GNOME Print backend, but I don't know how to proceed for the other
half.

The callback for the external graphic is being called okay, but I
don't know what library, let alone what library functions, to use to
get from the string for a filename to the rgba array needed by
libgnomeprint.

Any suggestions?

Regards,


Tony.

[xmlroff] Off to Australia

[Tony G. <Ton...@Su...>]

FYI, I leave on Monday for about four weeks of interspersed vacation
and work in Australia and Hong Kong.

I do expect that the next xmlroff (and PangoXSL) release will still be
released on time, i.e., "on or about the first of the month".

The next xmlroff release which will contain several improvements,
including some from Julian Rosse, as well as build fixes from Tim
Waugh.

Regards,


Tony.

Re: [xmlroff] DocBook to PDF with xmlroff

[Tony G. <Ton...@Su...>]

Tony Graham <Ton...@Su...> writes:
> Tim Waugh <tw...@re...> writes:
>> On Thu, Mar 10, 2005 at 04:41:49PM +0000, Tony Graham wrote:
> ..
>> Oh, now that I look more closely, it's the fo:external-graphic ones I
>> wanted.  The background-image things were for 'draft'-type watermarks,
>> and they come from docbook-xsl.
>>
>> So is that more difficult?
>
> Oh, yes.
>
> The simple answer:

For the record...

>  - Implement the graphic handing in FoDocGP that used to be in
>    FoDocPDF.

I.e., implement these commands from libfo/fo-doc-commands.h for
FoDocGP:

void          fo_doc_place_image     (FoDoc        *fo_doc,
				      gint          image,
				      gfloat        x,
				      gfloat        y,
				      gfloat        scale);
gint          fo_doc_open_image_file (FoDoc        *fo_doc,
				      const char   *imagetype,
				      const char   *filename,
				      const char   *stringparam,
				      gint          intparam);
void          fo_doc_close_image     (FoDoc        *fo_doc,
				      gint          image);

In practice, it would be okay to modify the fo-doc-commands.h commands
since these were based on PDFlib functions and PDFlib is no longer
used.

>  - Modify PangoXSL to walk the PangoLayout after it's been rendered
>    and call the callback for each graphic.

Actually, modify fo_doc_gp_render_layout_lines() to add something
similar to pangopdf_layout_lines() after the
gnome_print_pango_layout() call to iterate through each PangoAttribute
of each run of each line of fo_area_layout_get_layout (area_layout) to
find any callback attributes similarly to what was done in
pangopdflib.c in the PangoPDF project:

	  if (attr_type == pango_attr_callback_get_type ())
	    {
	      GValue values[1] = { { 0, } };

	      g_value_init (&values[0], G_TYPE_POINTER);
	      g_value_set_pointer (&values[0], pdf_doc);

#if 0
	      g_message ("Got a callback: callback: %p",
			 ((PangoAttrPointer *) attr)->pointer);
#endif

	      PDF_translate (pdf_doc,
			     ((float) x) / PANGO_SCALE,
			     ((float) y) / PANGO_SCALE);

	      g_closure_invoke (((GClosure *) ((PangoAttrPointer *) attr)->pointer),
				NULL,
				1,
				values,
				NULL);
	      PDF_translate (pdf_doc,
			     - (((float) x) / PANGO_SCALE),
			     - (((float) y) / PANGO_SCALE));
	    }

(See
http://cvs.sourceforge.net/viewcvs.py/pangopdf/pangopdf/pango/pangopdflib.c?rev=1.6&view=auto)

Regards,


Tony.

Re: [xmlroff] 'border-style' and 'border-width' properties

[Tony G. <Ton...@Su...>]

Julian Rosse <gn...@th...> writes:
...
>   Another thing - in my test cases, when I used "border-width", it gave me
> a number of warning messages equal to the number of tokens in border-width's
> value about datatype != NULL failing in fo_expr_context_push_stack().  Looking
> at eval_border_style_expr(), I'm pretty sure you just have an extra
>
> fo_expr_context_push_stack (context, intermediate_value);
>
> where you don't want it - it looks like eval_enum() actually does the
> pushing earlier in the function and intermediate_value doesn't get set if
> parse_ncname() succeeds, thus the error indicating that intermediate_value
> is NULL.  It was working nonetheless, I guess because eval_enum() was
> successfully pushing the tokens onto the stack, but letting you know.

Fixed, thanks.

I found that I couldn't view PDF that had any visible border style
other than "solid" -- but I had the same problem with
border-left-style, etc., too.  Did you have that problem?  I've
patched fo-doc-gp.c.

Regards,


Tony.

[xmlroff] Literal result element as stylesheet?

[Tony G. <Ton...@Su...>]

Before he joined the list, Phil Casidy submitted a bug report about a
stylesheet that sends xmlroff into an endless loop.  It does, but only
after you run it on itself.

The stylesheet, shown below, is not in the form of a literal result
element but rather in the form of its equivalent stylesheet.

I don't quite understand whether Phil is saying that he can use this
stylesheet as the single argument with other XSL formatters.  (Is that
the case, Phil?).

Whether or not I understand this stylesheet, it does raise the
question of whether or not xmlroff should support a literal result
element as stylesheet.  Should it?

Regards,


Tony.

------------------------------------------------------------
<?xml version="1.0" encoding="iso-8859-15"?>

<xsl:stylesheet version="1.0"
  xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
  xmlns:fo="http://www.w3.org/1999/XSL/Format"
  xmlns:rx="http://www.renderx.com/XSL/Extensions"
  >

  <xsl:template match="/">
    
    <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format">

      <fo:layout-master-set>
        <fo:simple-page-master master-name="mainPage" >
          <fo:region-body margin="1in"/>
        </fo:simple-page-master>
      </fo:layout-master-set>

      <fo:page-sequence master-reference="mainPage">
        <fo:flow flow-name="xsl-region-body">
          <fo:block>Hello, world!</fo:block>
        </fo:flow>
      </fo:page-sequence>
    </fo:root>
  </xsl:template>

</xsl:stylesheet>
------------------------------------------------------------