Bug 816319
Summary: | Single condition at a time | ||
---|---|---|---|
Product: | [Community] Publican | Reporter: | eric |
Component: | publican | Assignee: | Ruediger Landmann <rlandman> |
Status: | CLOSED NOTABUG | QA Contact: | Ruediger Landmann <rlandman+disabled> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 2.8 | CC: | jfearn, mmcallis, rlandman+disabled, rlandman |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-08-17 05:04:59 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
eric
2012-04-25 19:22:58 UTC
(Not a bug in our packaging of Publican, moving upstream) Hi -- this is actually how DocBook conditions are supposed to work, and I agree it's a little counter-intuitive. They "profile" the output by removing any element that has a condition set on it, when that condition is different from the one specified for the document. To specify content to appear only in certain, specific versions of a document, set those multiple conditions as a comma-separated list in the "condition" attribute on that element. When any one of those conditions is met, Publican includes that element in the build. There's an example of how to do this in the Publican User Guide. If that doesn't help, maybe reply back here with an example of where it's going wrong for you. Cheers Rudi :) |