xmlroff-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] xmlroff release is delayed

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

Tony Graham wrote:
> But if you've been looking for it, you'd have realised that already.

Indeed. :-)

I'm in the middle of a release of my own right now (synopsis 0.8), and
I was trying to build pdf documentation, which reminded me. :-)

What should we expect from the next release ? How is the work on
external graphics going ? While fop does support them, there are all
kinds of issues with scaling and bounding box calculation (or something
similar), so I was hoping that xmlroff would get to that soon. (I'm
looking for support for external png and svg, in particular.)

Good luck with your system !

Stefan

Re: [xmlroff] xmlroff release is delayed

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

Stefan Seefeld <se...@sy...> writes:
> Tony Graham wrote:
>> But if you've been looking for it, you'd have realised that already.
>
> Indeed. :-)

It's nice to know that someone is looking for it.

> I'm in the middle of a release of my own right now (synopsis 0.8), and
> I was trying to build pdf documentation, which reminded me. :-)
>
> What should we expect from the next release ? How is the work on

That depends on whether I get my system working soon and package what
I have as the next release or wait until next month and somehow find
some time to work on xmlroff.

The only changes so far are plugged memory leaks: formatting
xmlroff.fo leaks less than 50% of what it used to.  There's still a
lot of leaks and a lot of unreleased memory to go, however.

> external graphics going ? While fop does support them, there are all

The simple answer, which I didn't have before, is
gdk_pixbuf_new_from_file().

Once the miminum of having graphics again actually works, then as you
note, there's all the interrelated graphics properties to take care
of.

> kinds of issues with scaling and bounding box calculation (or something
> similar), so I was hoping that xmlroff would get to that soon. (I'm
> looking for support for external png and svg, in particular.)
>
> Good luck with your system !

Thanks.

Regards,


Tony.

Re: [xmlroff] xmlroff release is delayed

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

Tony Graham wrote:

> The simple answer, which I didn't have before, is
> gdk_pixbuf_new_from_file().
> 
> Once the miminum of having graphics again actually works, then as you
> note, there's all the interrelated graphics properties to take care
> of.

I can't wait !!

Regards,
		Stefan

Re: [xmlroff] xmlroff release is delayed

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

Stefan Seefeld <se...@sy...> writes:
> Tony Graham wrote:
>> The simple answer, which I didn't have before, is
>> gdk_pixbuf_new_from_file().
>> Once the miminum of having graphics again actually works, then as you
>> note, there's all the interrelated graphics properties to take care
>> of.
>
> I can't wait !!

So you're volunteering?

Regards,


Tony.

Re: [xmlroff] xmlroff release is delayed

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

Stefan Seefeld wrote:
> Tony Graham wrote:
> 
>> But if you've been looking for it, you'd have realised that already.
> 
> 
> Indeed. :-)
> 
> I'm in the middle of a release of my own right now (synopsis 0.8), and
> I was trying to build pdf documentation, which reminded me. :-)

Speaking of which, do you have a tool to generate documentation from your
source code ? Synopsis has a new C parser and I'm looking for a victim... :-)

(see http://synopsis.fresco.org/boost/ for documentation I generated from
the boost python library (C++) )

Regards,
		Stefan

Re: [xmlroff] xmlroff release is delayed

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

Stefan Seefeld <se...@sy...> writes:
> Stefan Seefeld wrote:
>> Tony Graham wrote:
>>
>>> But if you've been looking for it, you'd have realised that already.
>> Indeed. :-)
>> I'm in the middle of a release of my own right now (synopsis 0.8),
>> and
>> I was trying to build pdf documentation, which reminded me. :-)
>
> Speaking of which, do you have a tool to generate documentation from your
> source code ? Synopsis has a new C parser and I'm looking for a victim... :-)

gtk-doc.

Can Synopsis parse gtk-doc comments?

Can Synopsis included "static" documentation and annotations to the
generated documentation in the way that gtk-doc can?

If you can modify configure.in to enable Synopsis documentation
generation (with no ill-effect if Synopsis is not present) just as
--enable-gtk-doc enables gtk-doc documentation, then you can check it
in.

Synopsis would have to be an option alongside gtk-doc, and for the
moment at least, the xmlroff distributions would still ship with
gtk-doc documentation.

Regards,


Tony.

Re: [xmlroff] xmlroff release is delayed

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

Tony Graham wrote:

>>Speaking of which, do you have a tool to generate documentation from your
>>source code ? Synopsis has a new C parser and I'm looking for a victim... :-)
> 
> 
> gtk-doc.
> 
> Can Synopsis parse gtk-doc comments?

yes, you can teach it to parse comments as you want, by means of python
modules.

> Can Synopsis included "static" documentation and annotations to the
> generated documentation in the way that gtk-doc can?

I'm not sure what you mean in detail, but it is certainly possible
to either include links to external docs, or even mix in existing
documents into a single generated document.

Synopsis can also be used to create a cross-referenced view of the
source code itself, so you can navigate through the code by clicking
on variables and function calls, taking you to their respective
declaration/definition.

> If you can modify configure.in to enable Synopsis documentation
> generation (with no ill-effect if Synopsis is not present) just as
> --enable-gtk-doc enables gtk-doc documentation, then you can check it
> in.
> 
> Synopsis would have to be an option alongside gtk-doc, and for the
> moment at least, the xmlroff distributions would still ship with
> gtk-doc documentation.

I'll have a look. If gtk-doc is already doing a fine job for what
you want it to do there is no reason to change / add anything.

Regards,
		Stefan

Re: [xmlroff] xmlroff release is delayed

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

Stefan Seefeld <se...@sy...> writes:
> Tony Graham wrote:
>>>Speaking of which, do you have a tool to generate documentation from your
>>>source code ? Synopsis has a new C parser and I'm looking for a victim... :-)
>> gtk-doc.
>> Can Synopsis parse gtk-doc comments?
>
> yes, you can teach it to parse comments as you want, by means of python
> modules.

I'm sure someone could.  Once done, it would of course be usable by
any GTK+/GNOME-like project.

>> Can Synopsis included "static" documentation and annotations to the
>> generated documentation in the way that gtk-doc can?
>
> I'm not sure what you mean in detail, but it is certainly possible
> to either include links to external docs, or even mix in existing
> documents into a single generated document.

I hope that you have looked at the generated documentation at some
point...

The sections under "Things to know" are "static" documentation
generated from DocBook documents in the 'docs' directory.

The files in docs/tmpl are initially generated by gtk-doc, but it's
possible to add snippets of DocBook markup to them, and the snippets
will be included in the appropriate place in the generated HTML.

...
>> If you can modify configure.in to enable Synopsis documentation
>> generation (with no ill-effect if Synopsis is not present) just as
>> --enable-gtk-doc enables gtk-doc documentation, then you can check it
>> in.
>> Synopsis would have to be an option alongside gtk-doc, and for the
>> moment at least, the xmlroff distributions would still ship with
>> gtk-doc documentation.
>
> I'll have a look. If gtk-doc is already doing a fine job for what
> you want it to do there is no reason to change / add anything.

Synopsis appears to have some interesting features, and I'd be more
inclined to use it if all it took was a make target.

Regards,


Tony.

Re: [xmlroff] xmlroff release is delayed

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

Tony Graham wrote:

> Synopsis appears to have some interesting features, and I'd be more
> inclined to use it if all it took was a make target.

Point taken.

Regards,
		Stefan

[xmlroff] No xmlroff release this month [Was: xmlroff release is delayed]

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

Tony Graham <Ton...@Su...> writes:
> 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.

Problem solved.  I recompiled and re-installed Pango 1.6.0 and the
problem went away.

However, since it is already the middle of this month, I will delay
the next release until "on or about" the first of next month.

Anyone wishing to use the recent memory leak fixes can do so by
getting the current code from CVS.

Regards,


Tony.