Can you apply condition tags to individual alias entries?

[Landy]

Hi,

As the subject states:
In Flare 7.2, are you able to apply condition tags to individual entries in the *.flali file?
From the Flare help it doesn't appear that you can.

Thanks

[i-tietz]

No.
But if you have different targets, you can have another alias file for each target. Yes: That means, that if you add an unconditioned alias, you will have to insert it into each one of the alias files.

[Landy]

Thanks, I thought as much.
It would be good if you could single source down to that level, but having 2 alias files (one for each target) is an acceptable solution, and what we will be going with.

[i-tietz]

You might want to place an enhancement request and ask MC to change the handling of the alias files to the way they handle glossary files ...
Assembling the final version of the alias file would make it easier for you (and for us, too )

[Landy]

OK, I have logged a case with MadCap for this. It is case 32145 if you are interested.
Let's see how we go and if we get some enhancements in this area.
Cheers,

[Landy]

Hi i-tietz

I assumed by your reference to alias files being treated more like glossary files that you were referring to the fact that the glossary has more functionality within the Webhelp target than the alias file does.
That is, in the Webhelp target you get a Glossary tab where you can define a few options. All you can do for aliases in the Webhelp target is select which one you want to use (in the Advanced tab).

Is that what you were getting at?
Let me know and I will update MadCap support on this feature request.

Thanks,

[i-tietz]

You can have more than one glossary file and in the target, and you pick those you want to include in the output. Flare assembles them to make one glossary.
But you can only pick one alias file ... it would be more handy to have several alias files, too. And then assemble them for the output, too. That would make handling conditional output easier.