For my project just using the condition variable for profiling is not enough I need to use multiple profiling variables.
I've been trying to add these additional profiling parameters to the processing but it's truning out to be more complicated than I'd hoped, I've had to change the rng file, the stylesheets, and even the daps script but I've still not got it working.
Is there a simpler way to add new profiling variables to the ones initially provided by DAPS?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
All but revisionflag can be used with arbitrary strings, so they are not bound to a certain usecase. Therefore the list above should be sufficient for almost all usecases (if not, your docs will become difficult to maintain anyway ;-D).
With the SUSE documentation, we use arch in its intended sense (to differentiate between architectures), but os to distinguish between different product flavors.
For detailed information on how to use profiling with DAPS, refer to the DAPS documentation:
For my project just using the condition variable for profiling is not enough I need to use multiple profiling variables.
I've been trying to add these additional profiling parameters to the processing but it's truning out to be more complicated than I'd hoped, I've had to change the rng file, the stylesheets, and even the daps script but I've still not got it working.
Is there a simpler way to add new profiling variables to the ones initially provided by DAPS?
DAPS supports all profiling variables that upstream DocBook supports. These are
arch, DC-file:PROFARCHaudience, DC-file:PROFAUDIENCEcondition, DC-file:PROFCONDITIONconformance, DC-file:PROFCONFORMANCElang, DC-file:PROFLANGos, DC-file:PROFOSoutputformat, DC-file:PROFOUTPUTFORMATrevision, DC-file:PROFREVISIONrevisionflag="added|changed|deleted|off, DC-file:PROFREVISIONFLAGrole, DC-file:PROFROLEsecurity, DC-file:PROFSECURITYstatus, DC-file:PROFSTATUSuserlevel, DC-file:PROFUSERLEVELvendor, DC-file:PROFVENDORwordsize, DC-file:PROFWORDSIZEAll but
revisionflagcan be used with arbitrary strings, so they are not bound to a certain usecase. Therefore the list above should be sufficient for almost all usecases (if not, your docs will become difficult to maintain anyway ;-D).With the SUSE documentation, we use
archin its intended sense (to differentiate between architectures), butosto distinguish between different product flavors.For detailed information on how to use profiling with DAPS, refer to the DAPS documentation:
NOTE: To profile for more than one value for a single profiling attribute, you need to separate the values in the DC-file by semicolon: