Keith Fahlgren | 1 Aug 20:48 2010
Picon

The next formal DocBook-XSL release

Hi,

It has been an extremely long time since the last release. I think  
that users of DocBook-XSL are underserved by the rarity of releases.  
Should we plan on consolidating the Google SoC work and other bugfixes  
some time late this month?

If so, what are the 5 most critical open bugs that we should be sure  
to resolve?

I'd say we get all the changes in by the 27th, release 1.76.0 the  
following week, do three weeks of bugfixes, then 1.76.1 in mid-Sept.

Thanks,
Keith

--
Typed with thumbs
Bob Stayton | 2 Aug 00:33 2010
Picon

Re: The next formal DocBook-XSL release

Hi Keith,
I agree it has been too long, and we should do a release per your schedule.  I'll take 
a look at the bug list.

Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net

----- Original Message ----- 
From: "Keith Fahlgren" <abdelazer <at> gmail.com>
To: "Docbook Apps" <docbook-apps <at> lists.oasis-open.org>
Sent: Sunday, August 01, 2010 11:48 AM
Subject: [docbook-apps] The next formal DocBook-XSL release

> Hi,
>
> It has been an extremely long time since the last release. I think  that users of 
> DocBook-XSL are underserved by the rarity of releases.  Should we plan on 
> consolidating the Google SoC work and other bugfixes  some time late this month?
>
> If so, what are the 5 most critical open bugs that we should be sure  to resolve?
>
> I'd say we get all the changes in by the 27th, release 1.76.0 the  following week, 
> do three weeks of bugfixes, then 1.76.1 in mid-Sept.
>
>
> Thanks,
> Keith
>
> --
(Continue reading)

Cramer, David W (David | 2 Aug 02:09 2010

RE: The next formal DocBook-XSL release

We should also plan for a post-GSOC release that incorporates the work of our students this summer. 

David

-----Original Message-----
From: Bob Stayton [mailto:bobs <at> sagehill.net] 
Sent: Sunday, August 01, 2010 5:33 PM
To: Keith Fahlgren; Docbook Apps
Subject: Re: [docbook-apps] The next formal DocBook-XSL release

Hi Keith,
I agree it has been too long, and we should do a release per your schedule.  I'll take 
a look at the bug list.

Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net

----- Original Message ----- 
From: "Keith Fahlgren" <abdelazer <at> gmail.com>
To: "Docbook Apps" <docbook-apps <at> lists.oasis-open.org>
Sent: Sunday, August 01, 2010 11:48 AM
Subject: [docbook-apps] The next formal DocBook-XSL release

> Hi,
>
> It has been an extremely long time since the last release. I think  that users of 
> DocBook-XSL are underserved by the rarity of releases.  Should we plan on 
> consolidating the Google SoC work and other bugfixes  some time late this month?
>
(Continue reading)

Keith Fahlgren | 2 Aug 03:12 2010
Picon

Re: The next formal DocBook-XSL release

What do you think would be the best time for that release? Should we  
wait and combine?

--
Typed with thumbs

On Aug 1, 2010, at 5:09 PM, "Cramer, David W (David)" <dcramer <at> motive.com 
 > wrote:

> We should also plan for a post-GSOC release that incorporates the  
> work of our students this summer.
>
> David
>
> -----Original Message-----
> From: Bob Stayton [mailto:bobs <at> sagehill.net]
> Sent: Sunday, August 01, 2010 5:33 PM
> To: Keith Fahlgren; Docbook Apps
> Subject: Re: [docbook-apps] The next formal DocBook-XSL release
>
> Hi Keith,
> I agree it has been too long, and we should do a release per your  
> schedule.  I'll take
> a look at the bug list.
>
> Bob Stayton
> Sagehill Enterprises
> bobs <at> sagehill.net
>
>
(Continue reading)

Cramer, David W (David | 2 Aug 03:43 2010

RE: The next formal DocBook-XSL release

Oh, just saw you mentioned already gsoc in your original post :-) 

I'm confident Kasun will have things ready to go by pencils down (August 16), but I don't know what we need to
do to be integrated into the build. Let me figure that out and get back to you on when we'll be ready.

Thanks,
David 

-----Original Message-----
From: Keith Fahlgren [mailto:abdelazer <at> gmail.com] 
Sent: Sunday, August 01, 2010 8:12 PM
To: Cramer, David W (David)
Cc: Bob Stayton; Docbook Apps
Subject: Re: [docbook-apps] The next formal DocBook-XSL release

What do you think would be the best time for that release? Should we  
wait and combine?

--
Typed with thumbs

On Aug 1, 2010, at 5:09 PM, "Cramer, David W (David)" <dcramer <at> motive.com 
 > wrote:

> We should also plan for a post-GSOC release that incorporates the  
> work of our students this summer.
>
> David
>
> -----Original Message-----
(Continue reading)

Jochen Hayek | 2 Aug 21:36 2010

Re: DocBook Website / style of the generated HTML

>>>>> Sina K Heshmati writes:

> "Jochen Hayek" said:

>> Tonight at the Berlin Mongers' Meeting 
>> I got my first feedback regarding my new web-sites,
>> which I all set up using DocBook Website.

In the meantime I experienced more rather un-nice bashing.
Which I partially suppress with lawful threats ;-)
There was really quite some unacceptable critic.
Actually also because I mixed "some mild advertising" into certain announcements.

>> [...]
>> So is that a general and well-know critical view at the HTML generated from
>> DocBook Website?

> Indeed, Jochen.
> Generating clean HTML markup is one of the main objectives 
> of our re-implementation of DocBook Website [1].

Aha, this is SinDoc's work, I am getting an idea.

John New also pointed me to his variation of "example.css" at BeagleBytes.com,
which I quite like.

Well, a couple of questions are actually these:

(1) What timescale do you have for your re-implementation?
(2) Does is make sense, to let a designer improve the CSS for my purpose?
(Continue reading)

Sina K. Heshmati | 3 Aug 01:00 2010

RE: Re: DocBook Website / style of the generated HTML

"Jochen Hayek" <Jochen+oasis-open <at> Hayek.name> said:
>>>>>> Sina K Heshmati writes:
>> "Jochen Hayek" said:

<snipped/>

>>> So is that a general and well-know critical view at the HTML generated from
>>> DocBook Website?
> 
>> Indeed, Jochen.
>> Generating clean HTML markup is one of the main objectives
>> of our re-implementation of DocBook Website [1].
> 
> Aha, this is SinDoc's work, I am getting an idea.
> 
> John New also pointed me to his variation of "example.css" at BeagleBytes.com,
> which I quite like.
> 
> Well, a couple of questions are actually these:
> 
> (1) What timescale do you have for your re-implementation?

It's hard to tell. We'll hopefully have a working version by November but it might take months until we could
release something that people could use for production.

> (2) Does is make sense, to let a designer improve the CSS for my purpose?

It depends on what you mean by improving CSS.

If you want to generate a table-less HTML layout, given your DocBook Website source files and website
(Continue reading)

Cramer, David W (David | 3 Aug 01:37 2010

RE: Importing titlepage.xsl breaks section heading level in html

Hi Bob,
I see now that I do also have a separate titlepage file that I generated using the titlepage templates
mechanism. They do look similar inside so I don't feel so bad about having gotten confused :-)

This came up as a result of the way I do my customization layer: If I want to change a template in the stock xsls,
I first copy the entire file that contains the template to my customization layer directory. I then make
any changes to the template(s) in it. Now, when it comes time to upgrade, I do a three way diff comparing the
unmodified xsl from the old base version, my modified version of it, and the latest version. This lets me
see if I've changed a template that also changed between DocBook xsl releases so I can carefully merge my
changes in with the changes in the stock xsls. 

In this case, I modified some templates in titlepage.xsl some time ago (perhaps I should have done that work
within the titlepage templates mechanism) and eventually noticed that I wasn't getting anything but
<h1>s in my html output. In chunked html, it's not so noticeable since you don't see a heading and a
subheading on the same page. 

I'll be sure that I import titlepage.xsl before I import my generated titlepage-templates.xsl file from
now on. 

Thanks,
David

-----Original Message-----
From: Bob Stayton [mailto:bobs <at> sagehill.net] 
Sent: Saturday, July 31, 2010 4:15 PM
To: Cramer, David W (David); docbook-apps <at> lists.oasis-open.org
Subject: Re: [docbook-apps] Importing titlepage.xsl breaks section heading level in html

Hi David,
I'm not sure you have the right titlepages file.  In the xhtml directory the 
(Continue reading)

Jochen Hayek | 3 Aug 16:09 2010

Re: DocBook Website / style of the generated HTML

>>>>> Sina K Heshmati <sina <at> khakbaz.com> writes:

> "Jochen Hayek" <Jochen+oasis-open <at> Hayek.name> said:
>>>>>>> Sina K Heshmati writes:
>>> "Jochen Hayek" said:
>>>>>>>>> Sina K Heshmati writes:
>>>>> "Jochen Hayek" said:

>>>> (2) Does is make sense, to let a designer improve the CSS for my purpose?
>> 
>>> It depends on what you mean by improving CSS.
>> 
>> Achieving something as neat as BeagleBytes.com as opposed to the "default
>> Website".

> Could you not just grab the style [3] of that website and apply them to yours?

I see, SinDoc, you are a rather smart guy!!

That's exactly, what I planned to do short-term,
actually I wanted to let that get done by a friend,
but she is not as DocBook-minded as I am, so that looks a little difficult.
Artist, a little main-stream web-designer, ...

> The CSS customization to this website doesn't seem to be very deep. 
> I mean, the markup is the same table-rich HTML.

>>> If you want to generate a table-less HTML layout,
>>> given your DocBook Website source files and website layout,
>>> you might want to take a look at SilkPage [2].
(Continue reading)

Sina K. Heshmati | 3 Aug 21:32 2010

RE: Re: DocBook Website / style of the generated HTML

"Jochen Hayek" <Jochen+oasis-open <at> Hayek.name> said:
>>>>>> Sina K Heshmati <sina <at> khakbaz.com> writes:
>> "Jochen Hayek" <Jochen+oasis-open <at> Hayek.name> said:
>>>>>>>> Sina K Heshmati writes:
>>>> "Jochen Hayek" said:
>>>>>>>>>> Sina K Heshmati writes:
>>>>>> "Jochen Hayek" said:

Thanks for the kind words, Jochen :)

> How can we speed up the re-implementation? :-)

The strategy is to develop a lightweight version first and add new features afterwards. This way, we'll be
able to see for ourselves how the code grows along the way. Once the basic version is out, it would be
interesting to receive feedback from both other developers and early users.

Kind regards,
SinDoc

Gmane