OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [docbook] DocBook on the Web


I just brought it up in Explorer 6.0 and it looks good there, too.
Nice job Jon and Ken.

Dick Hamilton
rlhamilton@frii.com

> Hi everyone,
>
>   Since the question came up, I thought I would announce that the OASIS
> UBL 2.0 Specification has been migrated to DocBook and is available as
> both HTML and XML (DocBook). I can load it fine locally in Firefox, but
> can't display via the web. IE(7), however, seems to be happy to chew on
> it until it can be dislayed:
> http://docs.oasis-open.org/ubl/cs-UBL-2.0/UBL-2.0.xml
> (produced by Jon Bosak and Ken Holman)
>
> Regards,
>
> Mary
>
> ---------------------------------------------------
> Mary P McRae
> Manager of TC Administration, OASIS
> email: mary.mcrae@oasis-open.org
> web: www.oasis-open.org
> phone: 603.232.9090
>
> Register for OASIS Adoption Forum:
> "Managing Secure Interactions in Sector Applications"
> 28 - 29 Nov 2006, London
> www.oasis-open.org/events/adoptionforum2006/
>
>
>
>> -----Original Message-----
>> From: Elliotte Harold [mailto:elharo@metalab.unc.edu]
>> Sent: Wednesday, November 01, 2006 5:51 AM
>> To: docbook@lists.oasis-open.org
>> Subject: [docbook] DocBook on the Web
>>
>> Reading Norm's latest post
>> <http://norman.walsh.name/2006/10/30/openMind> I wondered, has anyone
>> tried publishing straight DocBook on the Web? i.e.
>> sending  real DocBook XML + (CSS | XSLT) to the client; not doing the
>> conversion server side or earlier and sending HTML to the client? If
>> so, what were your experiences.
>>
>> My suspicion is that even assuming client side support there are
>> several
>> problems:
>>
>> 1. There are no straight CSS stylesheets for DocBook.
>>
>> 2. The XSLT stylesheets are too complex to reasonably render client
>> side. They also likely rely on extension functions browser engines
>> don't have.
>>
>> 3. Anything beyond an article is too large for one page, and it's not
>> really possible to chunk pages on the client side.
>>
>> Are these fixable? Is it worth fixing them? Or is it just that
>> prerendering to HTML simply is the better option and we should stop
>> worrying about it?
>>
>> --
>> ´╗┐Elliotte Rusty Harold  elharo@metalab.unc.edu Java I/O 2nd Edition
>> Just Published!
>> http://www.cafeaulait.org/books/javaio2/
>> http://www.amazon.com/exec/obidos/ISBN=0596527500/ref=nosim/ca
>> feaulaitA/
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: docbook-unsubscribe@lists.oasis-open.org
>> For additional commands, e-mail: docbook-help@lists.oasis-open.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: docbook-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: docbook-help@lists.oasis-open.org
>
>




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]