I have to make some form of documentation of the projects I did , along with screenshots etc , and I'd like to make it less plain , so I tried adding CSS to my file , but it didn't work . After some browsing I found out that XSL or XSLT would be needed for this , which I never used , and couldn't find any good tutorial / documentation / examples.
How to customize Docbook with stylesheet ? Where do I find good resources?
491 Views Asked by gameerik At
1
There are 1 best solutions below
Related Questions in DOCBOOK
- Overlapping UICollectionView in storyboard
- Cannot pod spec lint because of undeclared type errors
- Is the transactionReceipt data present in dataWithContentsOfURL?
- UIWebView Screen Fitting Issue
- ZXingObjC encoding issues
- iOS: None of the valid provisioning profiles allowed the specific entitlements
- How to hide "Now playing url" in control center
- CloudKit: Preventing Duplicate Records
- Slow performance on ipad erasing image
- Swift code with multiple NSDateFormatter - optimization
Related Questions in DOCBOOK-XSL
- Overlapping UICollectionView in storyboard
- Cannot pod spec lint because of undeclared type errors
- Is the transactionReceipt data present in dataWithContentsOfURL?
- UIWebView Screen Fitting Issue
- ZXingObjC encoding issues
- iOS: None of the valid provisioning profiles allowed the specific entitlements
- How to hide "Now playing url" in control center
- CloudKit: Preventing Duplicate Records
- Slow performance on ipad erasing image
- Swift code with multiple NSDateFormatter - optimization
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular # Hahtags
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
You have to distinguish different parts of DocBook - authoring and processing (output result).
Authoring
DocBook authoring is quite straigthforward - to get the best result use special GUI XML editors like XMLMind XML Editor or OxygenXML Author instead of plain text editors (I'm not affiliated in any way with XMLMind or Oxygen). Of course, you can ask, why I mentioned the authoring tools instead of customization itself and how these tools are related to customization? The answer is: any XML editor itself can be fully customized in a way, you need it for a productive work. There are mostly nothing related to DocBook XSL Stylesheets there but any editor can be customized to get the most appropriate result for authoring. And many parts of this customization are related to XSLT/XPath.
Processing
This part fully depends on your knowledge of XSLT field and, in the same time, what result you want to get (expect). DocBook stylesheets were designed to get a result (output files) irrespective of your XSLT knowledge BUT the result complexity will be fully depend on the level of your knowledge. Here are a simple list to get know you where you need to go:
If you know nothing about XSLT - you get the default result out of box.
If you are ready to make a tiny dig into DocBook parameters and tune them - you get the result more suitable for your needs. I.e. you can tune your page font for PDF (
body.font.master
), choose, what document headings include in TOC (generate.toc
), etc. You need only one file to tune:<docbook-xsl-distro-dir>/<output_type>/param.xsl
, wheredocbook-xsl-distro-dir
- is your directory with DocBook XSL Stylesheets,<output_type>
- type of output result you need to get (fo
> print,html
> html). To find out what each parameter is suitable for, you can use either DocBook XSL reference or/and (recommended!) the book DocBook XSL: The Complete Guide by Bob Stayton (available online).If you are ready to dig into the depths of a customization - you need to get really complex result for your output. In that case you need: