This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
start [2010/04/10 21:31] sam |
start [2016/09/04 15:43] (current) sam |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | {{ :yagsbook-large.png?nolink&300|}} | ||
+ | |||
====== Yagsbook ====== | ====== Yagsbook ====== | ||
- | {{:yagsbook-small.png |}} | + | **Yagsbook** is an XML format specifically designed for the mark up of roleplaying game content. It was originally based on [[http://www.docbook.org|DocBook]] which does much the same for technical documentation. A **Yagsbook** document can support multiple types of game systems (allowing d20 and GURPS content to be included side by side for example) and potentially rendered to multiple output formats - currently only PDF is fully supported. Support for HTML is pretty much deprecated. |
- | **Yagsbook** is an XML format specifically designed for the mark up of roleplaying game content. It was originally based on [[http://www.docbook.org|DocBook]] which does much the same for technical documentation. A **Yagsbook** document can support multiple types of game systems (allowing d20 and GURPS content to be included side by side for example) and rendered to multiple output formats - currently HTML and PDF are supported. | + | |
The purpose of **Yagsbook** is that document content can be //structured// in such a way that accessing and manipulating it becomes easy. If a set of rules is written in //Microsoft Office//, then a chapter listing skills is just a sequence of text, possibly with some fancy headings. It is very difficult to do anything useful with that text - for example pull out a list of skills sorted by group, or filtered according to genre. With **Yagsbook** this becomes possible. | The purpose of **Yagsbook** is that document content can be //structured// in such a way that accessing and manipulating it becomes easy. If a set of rules is written in //Microsoft Office//, then a chapter listing skills is just a sequence of text, possibly with some fancy headings. It is very difficult to do anything useful with that text - for example pull out a list of skills sorted by group, or filtered according to genre. With **Yagsbook** this becomes possible. | ||
- | The best example of **Yagsbook** output is probably the rules for **Yags** itself. This can be downloaded at [[http://yags.glendale.org.uk/download.jsp]] | + | The best example of **Yagsbook** output is probably the rules for **YAGS** itself. This can be downloaded at [[http://yags.glendale.org.uk/]] |
Note that information is still in the process of being moved across from the old [[http://yagsbook.sourceforge.net/oldindex.html|Sourceforge]] hosted website. Much of the documentation is still on there, and needs to be moved into wiki form. | Note that information is still in the process of being moved across from the old [[http://yagsbook.sourceforge.net/oldindex.html|Sourceforge]] hosted website. Much of the documentation is still on there, and needs to be moved into wiki form. | ||
Line 16: | Line 17: | ||
* [[equipment | Equipment Lists]] | * [[equipment | Equipment Lists]] | ||
- | ===== News ===== | ||
- | {{blog>[news]?[5]&firstseconly}} |