Re: [docbook-apps] danger admonition

2018-10-26 Thread Bob Stayton 
Yes, danger will be added to DocBook 5.2.  There is not yet a scheduled 
release date for 5.2.  There is a recent beta release of 5.2 on 
docbook.org if you want to try it out.


https://docbook.org/schemas/5x.html

Bob Stayton
Sagehill Enterprises
b...@sagehill.net

On 10/26/2018 1:55 AM, Matteo Regazzo wrote:


Hi everybody,

I’ve read that the  admonition should be added to the others 
(tip, note, caution, …) with the 5.2 version of DocBook.


Is it true?

If it is, in the docbook.org website the newest available version is 5.1.

Is there a scheduled date for the release of the 5.2 version?

Thank you,

Matteo



Matteo Regazzo

Email: matteo.rega...@cmz.it| Web: www.cmz.it
Tel: +39 0422 447446|   CMZ Sistemi Elettronici srl
Via dell'Artigianato, 21
Vascon di Carbonera (TV)
31050 ITALY 




*NOVEMBER 01-02 WE ARE CLOSED FOR RELIGIOUS HOLIDAY*

The information transmitted, including attachments, is intended only 
for the person(s) or entity to which it is addressed and may contain 
confidential and/or privileged material. Any review, retransmission, 
dissemination or other use of, or taking of any action in reliance 
upon this information by persons or entities other than the intended 
recipient is prohibited. If you received this in error please contact 
the sender and destroy any copies of this information.

Re: [docbook-apps] DocBook content review process/tools?

2018-10-26 Thread David Cramer 
Hi Peter,

Good question. Here are a few ideas:

* Add a "Log a bug" link to each page that links to your bug tracking
system. It's usually easy to add a few query parameters that prepopulate
the new bug with contextual information (url, version, component, build
date, etc). Then the users only has to fill in a description and title.
With some more effort, you could add some code that queries the bug
tracking system and displays a list of open bugs against a give
chapter/section at the bottom of the page.

* Add some kind of commenting mechanism to the output. That
annotatorjs.org thing that Camille pointed out looks cool. I'm going to
have to check that out. Oxygen has a Webhelp with feedback chunked html
format. If security isn't a concern, then there are solutions like
Disqus that will add commenting to a page with just a little JavaScript.
Or there are open source and commercial commenting systems, usually
php-based, you can host.

* Oxygen XML has a "Content Fusion" product. I've only ever read the web
page and played with their online demo, but it uses a web-based version
of Oxygen to let users enter changes with track changes on. This looks
really cool, but if some of your content is generated programmatically
from more primitive sources, then you'd have to adapt the workflow to
merge changes to that content back into its original source.

* If pdf is your primary output format, Adobe has a feedback collection
system. I believe Acrobat Pro has to be involved. Perhaps this could be
automated if you produce postscript from your fo renderer and generate a
pdf from that using Acrobat Pro?

Regards,
David

On 10/23/18 11:53 AM, Peter Desjardins wrote:
> Hi! Does anyone have a document content review process you can
> recommend? One that allows non-DocBook users to easily provide input
> and see each other's comments?
> 
> My team uses Google docs for content review because reviewers can
> comment easily and see each other's input (this is at a company that
> uses Google email/docs). It's error-prone and tedious to transform
> DocBook content to Google documents though. I would love to find a
> better solution.
> 
> We keep content in GitHub and I love the pull request content review
> tools there. Most of our subject matter experts do not use GitHub
> though, and it's not practical to review all DocBook content by
> reading the source XML.
> 
> The conversion to Google doc format that works the best for us (so
> far) is DocBook > HTML > LibreOffice OpenDocument > Upload to Google
> drive and convert to Google doc format. We lose important formatting
> like bold for guilabel elements and bullet characters for
> itemizedlists disappear. Preparing a document for review is painful.
> 
> Do you have a great DocBook-based review process?
> 
> Thanks!
> 
> Peter
> 
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
> 
> 

-
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] DocBook content review process/tools?

2018-10-26 Thread Jirka Kosek 
On 23.10.2018 18:53, Peter Desjardins wrote:
> Do you have a great DocBook-based review process?

oXygen Web Author

https://www.oxygenxml.com/xml_web_author.html

provides editing, revision tracking and commenting features running in
the browser. They have also git backend. Recently they have introduced
tool that handles whole review workflow:

https://www.oxygenxml.com/content_fusion.html


Jirka

-- 
--
  Jirka Kosek  e-mail: ji...@kosek.cz  http://xmlguru.cz
--
 Professional XML and Web consulting and training services
DocBook/DITA customization, custom XSLT/XSL-FO document processing
--
Bringing you XML Prague conferencehttp://xmlprague.cz
--



signature.asc
Description: OpenPGP digital signature

[docbook-apps] danger admonition

2018-10-26 Thread Matteo Regazzo 
Hi everybody,

I’ve read that the  admonition should be added to the others (tip, 
note, caution, …) with the 5.2 version of DocBook.
Is it true?

If it is, in the docbook.org website the newest available version is 5.1.
Is there a scheduled date for the release of the 5.2 version?

Thank you,
Matteo





Matteo Regazzo

Email: matteo.rega...@cmz.it | Web: www.cmz.it
Tel: +39 0422 447446 |  CMZ Sistemi Elettronici srl
Via dell'Artigianato, 21
Vascon di Carbonera (TV)
31050 ITALY
[cid:imageb61ae9.PNG@3b1aedd5.47a779d5]
[cid:image2fdda7.PNG@5f22007f.49b85756]


NOVEMBER 01-02 WE ARE CLOSED FOR RELIGIOUS HOLIDAY

 The information transmitted, including attachments, is intended only for the 
person(s) or entity to which it is addressed and may contain confidential 
and/or privileged material. Any review, retransmission, dissemination or other 
use of, or taking of any action in reliance upon this information by persons or 
entities other than the intended recipient is prohibited. If you received this 
in error please contact the sender and destroy any copies of this information.

Re: [docbook-apps] DocBook content review process/tools?

2018-10-26 Thread Tony Graham 

On 26/10/2018 02:32, Peter Desjardins wrote:

Thank you, all! Your ideas are extremely helpful!


I've never used it, but you could look at Content Fusion from oXygen:

https://www.oxygenxml.com/content_fusion.html

Its byline is "Web collaboration solution for any XML documentation
review workflow".

Regards,


Tony Graham.
--
Senior Architect
XML Division
Antenna House, Inc.

Skerries, Ireland
tgra...@antenna.co.jp

-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org