Skip to main content
Known Participant
May 5, 2011
Question

Conditional build tag invalid?

  • May 5, 2011
  • 1 reply
  • 1538 views

Hello everyone!

I'm using RoboHelp 9 and I had to add a new conditional build tag to my documentation yesterday.

It's not the first time I had to do this since switching to RoboHelp 9 and it never was problematic.

However, when I try to create a document now, RoboHelp tells me that this new build tag is invalid.

I googled and searched but I cannot even find this error message anywhere on the net.

Does anybody know what might cause this error and how I can fix it?

Thank you very much in advance!

Louisa

This topic has been closed for replies.

1 reply

RoboColum_n_
Legend
May 5, 2011

Hi Louisa,

Can you tell us the name of the CBT you are trying to create? Is the error being generated when you create the CBT, applying it to some content or building a CBT expression? Also are there any other CBTs in this project? Is the problem only in one project? Sorry for all the questions but we haven't got a lot to go on.


  The RoboColum(n)   @robocolumn   Colum McAndrew
Louisa_deAuthor
Known Participant
May 5, 2011

Hi!

No, questions are good! Thank you for them!

I don't think I can tell you the name due to confidentiality issues.  But I can tell you it's capitalized, consists of 37 characters, 5 of them being _ and it's by far not the only (nor the longest) cbt in the document. It's one of over 100.

I have only tried entering the cbt in this project because I only need it in this project.

Does that help?

Otherwise just ask.

Thank you so much!

Louisa

RoboColum_n_
Legend
May 5, 2011

Hi!

Thanks for your answer!

We've developed a workaround for the 255 character problem. All in all the cbt take up more than 2500 characters in that project and that has never been a problem. This is the first cbt that proves to be problematic, but I don't know why. To me it doesn't look any different than the other 108 or so cbt.

I cannnot abbreviate the cbt because I don't name them, they are given to me and I only implement them. There's then a complex mechanism which automatically generates a list of the cbt needed for each project because selecting them manually would be very accident-prone.

However, what I'm gonna try now is delete a different cbt and see if that solves the problem. Then it would probably be down to the number of characters and I'd discovered the limits of our workaround.

If anyone has any ideas in the meantime, please let me know!

Thank you very much!

Louisa

P.S.: Deleting a different cbt has not worked, it's still this cbt that creates the problem.


Maybe you should think of getting the person who gives you the CBT to rethink how they create them. That would surely also help with making them less confidential and just think of the fun you could have formulating a code for them

As for manually selecting the CBTs, you don't have to. You can create multiple versions of your output type single source layout and change the CBT expression once for each one. I blogged about this here if you fancy a read.

You could also try creating the problematic CBT in a new project. That would tell you if the problem was the CBT itself.


  The RoboColum(n)   @robocolumn   Colum McAndrew