This content has been marked as final. Show 9 replies
Hi Avi - I would definitely consider build tags. You can apply to entire topics or to content within a topic. Much easier to maintain than two projects.
Would build-tags solve all of the listed issues?
How about topic names?
Can I maintain two sets of topic names?
( an example for a topic name: "Installing <keyword>")
Hi Avi. As lmarden says, build tags would work but not on topic names. If you maintain two topics and apply a build tag to each you can include/exclude the one you want before you compile.
It should be able to handle all - even topic titles. I do that myself. For such a relatively small project, it shouldn't be too difficult to test this - Copy the entire project directory to a new hard drive location, open the copy, and test a few topics with build tags, compile and see the results. The only thing I have a question about is search keywords - I would test to see if a word with a build tag on it is picked up in a search in a compiled chm that was built to exclude components with that build tag. It should. I just haven't tried this on my projects so I don't know for sure.
If you have added a build tag to a word and EXCLUDED the tag from the compiled CHM it will not be found by a search as it will not exist inside the CHM file. Of course if the build tag was INCLUDED it would. Hope this helps.
Until today, my only experience with build-tags is at the topic level.
(assigning an entire topic to a tag, that is.)
Currently, I am building tags for text and screenshots within a single topic and see how it is working for me.
Next, I will have to find a solution for tagging the topic names that appears on the TOC.
Thanks for the tip :-)
I have just read your previous reply.
So, you say that I must duplicate each topic in order to maintain a tag-related topic name?