Re: [docbook-apps] Re: [docbook] DocBook Slides 5.0 beta1 available for testing
Hi Justus, thank you for the valuable comments! Em 17-08-2012 16:40, justus-b...@piater.name escreveu: - dbs3-upgrade.xsl contains a typo: xsl:template name=slidesinfo|foilgroupinfo|foilinfo should probably read xsl:template match=slidesinfo|foilgroupinfo|foilinfo Yes, seems a trivial error. - dbs3-upgrade.xsl does not conserve attributes (such as id, which should incidentally be translated to xml:id) on dbs-namespaced elements, due to limitations in the process.content named template. I will fix this soon, too. - The generated HTML is invalid (at least with respect to the XHTML schema I use) due to various empty attribute values (xml:lang, lang, xmlns, class). Hmm, yes, although they are not especially harmful, empty attributes shouldn't be there. Will have a look. - Multiple mediaobject children appear all to be rendered, although only one of them should be. How can this happen? I would think that this is handeled by the stock DB stylesheets, not by anything specific to Slides. (I see this in informalequation/mediaobject, where I have textobjects containing LaTeX and auto-generated MathML, respectively.) I think I modified the template for this. If only one should be rendered why does the schema allow more? DB Slides uses this possibility to allow more imageobject's inside. - On my wishlist: speakernotes are currently only possible in specific places within slides, foilgroup and foil (as they were in DB5 I think). However, I see no reason to impose such restrictions. Why not allow attaching speakernotes to just about anything? Here is what I have done for ages, and what I would like the stock DB Slides to adopt: local.divcomponent.mix = speakernotes local.component.mix= speakernotes local.example.mix = speakernotes (The use of local.* is of course my personal customization hack; this just to indicate where I think speakernotes should be allowed, at least.) I then render speakernotes into my personal view of the slides (see https://iis.uibk.ac.at/public/piater/talks/speaker/speaker.xhtml, which I plan to adapt to the new Slidy output). My own point of view is that one slide is one logical unit with limited content so I would write one speakernote (but possibly more paragraphs) about one slide, trying to summarize what I want to tell with that slide. But I have no strong opinion on this so if you prefer scatter your notes among real content elements, I don't object to such change. I'll add this to my todo list. I'll also have to modify the stylesheets so that you customize it. - Also on my wishlist: Target HTML5 output. I'd like my movies to be rendered by video elements, without my having to fiddle with stylesheets :-) I'm also thinking of such. - There are various sizing and spacing problems involving SVG graphics, but I do not have the time right now to investigate whether they are caused by your transformations or by weirdnesses in my own XML coding. I also noticed some strangeness, especially in pdf but the FO markup seemed right so I think it may be something in FOP. I don't have license to any commercial FO renderer so I cannot check if they perform better. Gabor - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Re: [docbook] DocBook Slides 5.0 beta1 available for testing
Gabor Kovesdan ga...@kovesdan.org wrote on Sat, 18 Aug 2012 19:18:49 +0200: - Multiple mediaobject children appear all to be rendered, although only one of them should be. How can this happen? I would think that this is handeled by the stock DB stylesheets, not by anything specific to Slides. (I see this in informalequation/mediaobject, where I have textobjects containing LaTeX and auto-generated MathML, respectively.) I think I modified the template for this. If only one should be rendered why does the schema allow more? DB Slides uses this possibility to allow more imageobject's inside. This violates the spec; see The Definitive Guide (http://www.docbook.org/tdg51/en/html/mediaobject.html): The primary purpose of the mediaobject is to provide a wrapper around a set of alternative presentations of the same information. - On my wishlist: speakernotes are currently only possible in specific places within slides, foilgroup and foil (as they were in DB5 I think). However, I see no reason to impose such restrictions. Why not allow attaching speakernotes to just about anything? ... ... But I have no strong opinion on this so if you prefer scatter your notes among real content elements, I don't object to such change. I'll add this to my todo list. I'll also have to modify the stylesheets so that you customize it. Great, thanks! This is important to me because I use speakernotes for material that I do not show on the slides but develop on the board and/or in dialog with students (which, I think, is well within the semantics of speaker notes). Anywhere speakernotes allow me to place the content exactly where it belongs. I also produce booklet output from the slides for the students that do include the speakernotes; thus, it is very important that the content appear in the right place. Justus - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Re: [docbook] DocBook Slides 5.0 beta1 available for testing
Em 18-08-2012 20:13, justus-b...@piater.name escreveu: This is important to me because I use speakernotes for material that I do not show on the slides but develop on the board and/or in dialog with students (which, I think, is well within the semantics of speaker notes). Anywhere speakernotes allow me to place the content exactly where it belongs. I also produce booklet output from the slides for the students that do include the speakernotes; thus, it is very important that the content appear in the right place. Isn't handoutnotes more appropriate for that? Currently, it is defined like speakernotes but the semantical meaning is different. I'll modify the schema to allow both scattered. Gabor - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Re: [docbook] DocBook Slides 5.0 beta1 available for testing
Gabor Kovesdan ga...@kovesdan.org wrote on Sat, 18 Aug 2012 20:18:54 +0200: Em 18-08-2012 20:13, justus-b...@piater.name escreveu: This is important to me because I use speakernotes for material that I do not show on the slides but develop on the board and/or in dialog with students (which, I think, is well within the semantics of speaker notes). Anywhere speakernotes allow me to place the content exactly where it belongs. I also produce booklet output from the slides for the students that do include the speakernotes; thus, it is very important that the content appear in the right place. Isn't handoutnotes more appropriate for that? Currently, it is defined like speakernotes but the semantical meaning is different. I'll modify the schema to allow both scattered. Sounds perfect to me! Justus - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
[docbook-apps] Re: [docbook] DocBook Slides 5.0 beta1 available for testing
Hi, I sent this announcement the last week and I only got one feedback. Nobody else tried it or just didn't experience any problems to report? Gabor - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
[docbook-apps] Re: [docbook] DocBook Slides 5.0 beta1 available for testing
Hi Gabor, I have not been able to took a deeper look, and won't be for another few weeks, but I aim to use it in production from the end of September onwards. So, after a quick look at the Slidy transformation: - Fantastic! This is looking very promising. - dbs3-upgrade.xsl contains a typo: xsl:template name=slidesinfo|foilgroupinfo|foilinfo should probably read xsl:template match=slidesinfo|foilgroupinfo|foilinfo - dbs3-upgrade.xsl does not conserve attributes (such as id, which should incidentally be translated to xml:id) on dbs-namespaced elements, due to limitations in the process.content named template. - The generated HTML is invalid (at least with respect to the XHTML schema I use) due to various empty attribute values (xml:lang, lang, xmlns, class). - Multiple mediaobject children appear all to be rendered, although only one of them should be. How can this happen? I would think that this is handeled by the stock DB stylesheets, not by anything specific to Slides. (I see this in informalequation/mediaobject, where I have textobjects containing LaTeX and auto-generated MathML, respectively.) - On my wishlist: speakernotes are currently only possible in specific places within slides, foilgroup and foil (as they were in DB5 I think). However, I see no reason to impose such restrictions. Why not allow attaching speakernotes to just about anything? Here is what I have done for ages, and what I would like the stock DB Slides to adopt: local.divcomponent.mix = speakernotes local.component.mix= speakernotes local.example.mix = speakernotes (The use of local.* is of course my personal customization hack; this just to indicate where I think speakernotes should be allowed, at least.) I then render speakernotes into my personal view of the slides (see https://iis.uibk.ac.at/public/piater/talks/speaker/speaker.xhtml, which I plan to adapt to the new Slidy output). - Also on my wishlist: Target HTML5 output. I'd like my movies to be rendered by video elements, without my having to fiddle with stylesheets :-) - There are various sizing and spacing problems involving SVG graphics, but I do not have the time right now to investigate whether they are caused by your transformations or by weirdnesses in my own XML coding. Great work, keep it up! Justus - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
[docbook-apps] Re: [docbook] DocBook Slides 5.0 beta1 available for testing
Em 08-08-2012 15:17, Thomas Schraitle escreveu:
So one of the first steps that I usually do when I encounter a new
schema is to load the schema and play with them in my XML editor. As a
new user, it is a lot more convenient, obvious, and user-friendly to
get some hints during writing. That allows me to browse through the
list, read the tool tip and to get an idea about this element or
attribute. Luckily, if a schema contains such annotations, it is
displayed as a tool tip in my XML editor.
For example, here is a snippet for DocBook's chapter element (the
annotation is the indented line starting with ##):
db.chapter =
## A chapter, as of a book
# [... Schematron rules omitted ...]
element chapter {
db.chapter.attlist, db.chapter.info, db.component.contentmodel
}
Unfortunately, annotations are not supported by Emacs/nXML if I'm not
mistaken. However, oXygen and others display them as a tool tip etc.
I think it will not be very hard to extend the Slides schema and add
these annotations.
Apart from this minor detail, it is really impressive. Keep up the good
work! :-)
Thank you Thomas for your review, I'll add such annotations soon and you
they will be available in the next beta or final release.
Gabor
-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
[docbook-apps] Re: [docbook] DocBook Slides 5.0 beta1 available for testing
Hi Gabor,
On Wed, 08 Aug 2012 13:32:37 +0200
Gabor Kovesdan ga...@kovesdan.org wrote:
[...]
This beta version can be downloaded from here:
http://kovesdan.org/files/slides-5.0-beta1.tar.gz
After downloading, please start at the BETATEST file.
Please at this point now report all inconveniences or bugs that you
encounter.
Congratulations for your first beta! :-)
I haven't used the DocBook slides schema before, so I my experiences
are limited. I can only give you a comment about an issue in your
Slides schema at this current state.
One issue that is really underestimated (even for officially released
schemas by other organizations) are annotations. Most schemas that I've
seen doesn't contain them which is really unfortunate. That makes it a
lot harder for inexperienced users. Fortunately, DocBook is a positive
exception.
So one of the first steps that I usually do when I encounter a new
schema is to load the schema and play with them in my XML editor. As a
new user, it is a lot more convenient, obvious, and user-friendly to
get some hints during writing. That allows me to browse through the
list, read the tool tip and to get an idea about this element or
attribute. Luckily, if a schema contains such annotations, it is
displayed as a tool tip in my XML editor.
For example, here is a snippet for DocBook's chapter element (the
annotation is the indented line starting with ##):
db.chapter =
## A chapter, as of a book
# [... Schematron rules omitted ...]
element chapter {
db.chapter.attlist, db.chapter.info, db.component.contentmodel
}
Unfortunately, annotations are not supported by Emacs/nXML if I'm not
mistaken. However, oXygen and others display them as a tool tip etc.
I think it will not be very hard to extend the Slides schema and add
these annotations.
Apart from this minor detail, it is really impressive. Keep up the good
work! :-)
--
Gruß/Regards,
Thomas Schraitle
-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
