RE: FrameMaker files and CHM
Dear Framers, I figured out what my problem was here. I had failed to set the Page break priority in WWP's Paragraph Styles, Option tab. I thought that placing the TopicAlias marker in a FM pgf tag that starts a new page and setting the Table of Contents in WWP would tell WWP to start the topic on a new page. Thanks to everyone who responded to my question. I truly appreciate your help. -k -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gross, Karen Sent: Tuesday, April 10, 2007 4:47 PM To: Bill Swallow Cc: [EMAIL PROTECTED] Subject: RE: FrameMaker files and CHM Sorry, the software to which I was referring is the application for which we're providing context-sensitive help. I haven't found any documentation stating anything about needing to break up the FM files per topic. Our software developer claims it's necessary, and our tests on the machine control prove him to be correct. I suspect the problem is with our control's software. At the very least, I'm missing something that will make it all work. We're using a custom .h file that holds our topic IDs and the control screen IDs (Map IDs). Example: #define IDH_ScreenName 123. The text is the same as what we put in the TopicAlias marker. The screen ID is the number assigned to the screen by the software developers. -Original Message- From: Bill Swallow [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 10, 2007 4:40 PM To: Gross, Karen Cc: [EMAIL PROTECTED] Subject: Re: FrameMaker files and CHM Which software are you talking about? WWP? You most certainly don't have to have one topic per FM file. That defeats the whole point of single-sourcing with FM and the point of using WWP in the first place. Can you provide details? On 4/10/07, Gross, Karen [EMAIL PROTECTED] wrote: I've assigned my markers, one per heading that starts a new page, and mapped the headings in WWP. Our software, which resides on a machine control, seems to require that we break up the FM file into smaller files, one topic per file. That doesn't sit right with me. It seemed to me that I could have more than one topic, each assigned to separate headings, that reside in one FM file. -- Bill Swallow HATT List Owner WWP-Users List Owner Senior Member STC, TechValley Chapter STC Single-Sourcing SIG Manager http://techcommdood.blogspot.com avid homebrewer and proud beer snob I see your OOO message and raise you a clue. ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/grossk%40hurco.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info. ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
FrameMaker files and CHM
Dear Framers, I figured out what my problem was here. I had failed to set the Page break priority in WWP's Paragraph Styles, Option tab. I thought that placing the TopicAlias marker in a FM pgf tag that starts a new page and setting the Table of Contents in WWP would tell WWP to start the topic on a new page. Thanks to everyone who responded to my question. I truly appreciate your help. -k -Original Message- From: framers-bounces+grossk=hurco@lists.frameusers.com [mailto:framers-bounces+grossk=hurco.com at lists.frameusers.com] On Behalf Of Gross, Karen Sent: Tuesday, April 10, 2007 4:47 PM To: Bill Swallow Cc: framers at lists.frameusers.com Subject: RE: FrameMaker files and CHM Sorry, the software to which I was referring is the application for which we're providing context-sensitive help. I haven't found any documentation stating anything about needing to break up the FM files per topic. Our software developer claims it's necessary, and our tests on the machine control prove him to be correct. I suspect the problem is with our control's software. At the very least, I'm missing something that will make it all work. We're using a custom .h file that holds our topic IDs and the control screen IDs (Map IDs). Example: #define IDH_ScreenName 123. The text is the same as what we put in the TopicAlias marker. The screen ID is the number assigned to the screen by the software developers. -Original Message- From: Bill Swallow [mailto:techcommd...@gmail.com] Sent: Tuesday, April 10, 2007 4:40 PM To: Gross, Karen Cc: framers at lists.frameusers.com Subject: Re: FrameMaker files and CHM Which software are you talking about? WWP? You most certainly don't have to have one topic per FM file. That defeats the whole point of single-sourcing with FM and the point of using WWP in the first place. Can you provide details? On 4/10/07, Gross, Karen wrote: > I've assigned my markers, one per heading that starts a new page, and > mapped the headings in WWP. Our software, which resides on a machine > control, seems to require that we break up the FM file into smaller > files, one topic per file. That doesn't sit right with me. It seemed to > me that I could have more than one topic, each assigned to separate > headings, that reside in one FM file. -- Bill Swallow HATT List Owner WWP-Users List Owner Senior Member STC, TechValley Chapter STC Single-Sourcing SIG Manager http://techcommdood.blogspot.com avid homebrewer and proud beer snob "I see your OOO message and raise you a clue." ___ You are currently subscribed to Framers as grossk at hurco.com. Send list messages to framers at lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscribe at lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/grossk%40hurco.com Send administrative questions to listadmin at frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
Re: FrameMaker files and CHM
Karen, WWP will generate a separate HTM file per heading (that is defined for starting a new topic). The TopicAlias marker provides the name of the HTM file. Only the generated HTM files should interest your developer - it should not matter to him/her whether the FrameMaker source is in a single file or in multiple files. David -- David Schor Senior Technical Writer RADLAN, a Marvell Company Tel: (+972) 3 7662823 Cellular: (+972) 54 4788253 E-mail: [EMAIL PROTECTED] Web: www.marvell.com On 4/10/07, Gross, Karen [EMAIL PROTECTED] wrote: Sorry, the software to which I was referring is the application for which we're providing context-sensitive help. I haven't found any documentation stating anything about needing to break up the FM files per topic. Our software developer claims it's necessary, and our tests on the machine control prove him to be correct. I suspect the problem is with our control's software. At the very least, I'm missing something that will make it all work. We're using a custom .h file that holds our topic IDs and the control screen IDs (Map IDs). Example: #define IDH_ScreenName 123. The text is the same as what we put in the TopicAlias marker. The screen ID is the number assigned to the screen by the software developers. ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
Re: FrameMaker files and CHM
Sorry, the software to which I was referring is the application for which we're providing context-sensitive help. That has about as much to do with your source content as the temperature in your office or the color of your socks. I haven't found any documentation stating anything about needing to break up the FM files per topic. Our software developer claims it's necessary, and our tests on the machine control prove him to be correct. I suspect the problem is with our control's software. At the very least, I'm missing something that will make it all work. Are they using the HTML Help API? Or another API for context-sensitivity? We're using a custom .h file that holds our topic IDs and the control screen IDs (Map IDs). Example: #define IDH_ScreenName 123. The text is the same as what we put in the TopicAlias marker. The screen ID is the number assigned to the screen by the software developers. That's all you need. Just make sure your TopicAlias markers are in the tight place (I put them in the middle of the headings) and make sure you are splitting on those heading levels in WWP. We produce c-s CHMs all the time from FM source using WWP and keep much of the content in a chapter format, so there are many help topics per FM file. -- Bill Swallow HATT List Owner WWP-Users List Owner Senior Member STC, TechValley Chapter STC Single-Sourcing SIG Manager http://techcommdood.blogspot.com avid homebrewer and proud beer snob I see your OOO message and raise you a clue. ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
Re: FrameMaker files and CHM
WWP will generate a separate HTM file per heading (that is defined for starting a new topic). The TopicAlias marker provides the name of the HTM file. TopicAlias markers set the c-s topic alias string for the topic, not the filename. Only the generated HTM files should interest your developer - it should not matter to him/her whether the FrameMaker source is in a single file or in multiple files. Agreed. Your know-it-all developer is waxing ignorant. ;-) -- Bill Swallow HATT List Owner WWP-Users List Owner Senior Member STC, TechValley Chapter STC Single-Sourcing SIG Manager http://techcommdood.blogspot.com avid homebrewer and proud beer snob I see your OOO message and raise you a clue. ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
FrameMaker files and CHM
Karen, WWP will generate a separate HTM file per heading (that is defined for starting a new topic). The TopicAlias marker provides the name of the HTM file. Only the generated HTM files should interest your developer - it should not matter to him/her whether the FrameMaker source is in a single file or in multiple files. David -- David Schor Senior Technical Writer RADLAN, a Marvell Company Tel: (+972) 3 7662823 Cellular: (+972) 54 4788253 E-mail: dschor at marvell.com Web: www.marvell.com On 4/10/07, Gross, Karen wrote: > Sorry, the software to which I was referring is the application for > which we're providing context-sensitive help. > > I haven't found any documentation stating anything about needing to > break up the FM files per topic. Our software developer claims it's > necessary, and our tests on the machine control prove him to be correct. > I suspect the problem is with our control's software. At the very least, > I'm missing something that will make it all work. > > We're using a custom .h file that holds our topic IDs and the control > screen IDs (Map IDs). Example: #define IDH_ScreenName 123. The text is > the same as what we put in the TopicAlias marker. The screen ID is the > number assigned to the screen by the software developers. >
FrameMaker files and CHM
> Sorry, the software to which I was referring is the application for > which we're providing context-sensitive help. That has about as much to do with your source content as the temperature in your office or the color of your socks. > I haven't found any documentation stating anything about needing to > break up the FM files per topic. Our software developer claims it's > necessary, and our tests on the machine control prove him to be correct. > I suspect the problem is with our control's software. At the very least, > I'm missing something that will make it all work. Are they using the HTML Help API? Or another API for context-sensitivity? > We're using a custom .h file that holds our topic IDs and the control > screen IDs (Map IDs). Example: #define IDH_ScreenName 123. The text is > the same as what we put in the TopicAlias marker. The screen ID is the > number assigned to the screen by the software developers. That's all you need. Just make sure your TopicAlias markers are in the tight place (I put them in the middle of the headings) and make sure you are splitting on those heading levels in WWP. We produce c-s CHMs all the time from FM source using WWP and keep much of the content in a chapter format, so there are many help topics per FM file. -- Bill Swallow HATT List Owner WWP-Users List Owner Senior Member STC, TechValley Chapter STC Single-Sourcing SIG Manager http://techcommdood.blogspot.com avid homebrewer and proud beer snob "I see your OOO message and raise you a clue."
FrameMaker files and CHM
> WWP will generate a separate HTM file per heading (that is defined for > starting a new topic). The TopicAlias marker provides the name of the > HTM file. TopicAlias markers set the c-s topic alias string for the topic, not the filename. > Only the generated HTM files should interest your developer - it > should not matter to him/her whether the FrameMaker source is in a > single file or in multiple files. Agreed. Your know-it-all developer is waxing ignorant. ;-) -- Bill Swallow HATT List Owner WWP-Users List Owner Senior Member STC, TechValley Chapter STC Single-Sourcing SIG Manager http://techcommdood.blogspot.com avid homebrewer and proud beer snob "I see your OOO message and raise you a clue."
FrameMaker files and CHM
Dear Framers, Is it a requirement to assign one TopicAlias marker per FrameMaker file in order to generate a context-sensitive CHM file using WebWorks ePublisher Pro? I understand that the marker needs to be placed in a pgf tag that starts a new page, but I thought I could have more than one marker per file. I'm using FM 7.2b144 and WWeP v9.2. Regards, Karen J. Gross Sr. Technical Writer Hurco Companies, Inc. 317-298-2637 ext. 2102 ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
RE: FrameMaker files and CHM
You can have as many as you want. It depends on your software. How many buttons do you have that point to different topics. If you have 10 help buttons that point to ten aliases, then you can have 10 topics. You need your software engineer to generate a resource.h file for you. That will tell you how many aliases the software has. Then you can create topic markers for all of the aliases and place them whereever you want. Go to the WebWorks help and search on context-sensitive help. You can also join the webworks help group on yahoo. -Gillian From: [EMAIL PROTECTED] on behalf of Gross, Karen Sent: Tue 4/10/2007 12:33 PM To: framers@lists.frameusers.com Subject: FrameMaker files and CHM Dear Framers, have Is it a requirement to assign one TopicAlias marker per FrameMaker file in order to generate a context-sensitive CHM file using WebWorks ePublisher Pro? I understand that the marker needs to be placed in a pgf tag that starts a new page, but I thought I could have more than one marker per file. I'm using FM 7.2b144 and WWeP v9.2. Regards, Karen J. Gross Sr. Technical Writer Hurco Companies, Inc. 317-298-2637 ext. 2102 ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/gflato%40nanometrics.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info. ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
Re: FrameMaker files and CHM
Is it a requirement to assign one TopicAlias marker per FrameMaker file in order to generate a context-sensitive CHM file using WebWorks ePublisher Pro? I understand that the marker needs to be placed in a pgf tag that starts a new page, but I thought I could have more than one marker per file. You can have one TopicAlias marker per TOPIC. Usually topics are broken down by heading levels, provided you're splitting on those headings in WWP. -- Bill Swallow HATT List Owner WWP-Users List Owner Senior Member STC, TechValley Chapter STC Single-Sourcing SIG Manager http://techcommdood.blogspot.com avid homebrewer and proud beer snob I see your OOO message and raise you a clue. ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
RE: FrameMaker files and CHM
I've assigned my markers, one per heading that starts a new page, and mapped the headings in WWP. Our software, which resides on a machine control, seems to require that we break up the FM file into smaller files, one topic per file. That doesn't sit right with me. It seemed to me that I could have more than one topic, each assigned to separate headings, that reside in one FM file. -Original Message- From: Bill Swallow [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 10, 2007 4:32 PM To: Gross, Karen Cc: framers@lists.frameusers.com Subject: Re: FrameMaker files and CHM Is it a requirement to assign one TopicAlias marker per FrameMaker file in order to generate a context-sensitive CHM file using WebWorks ePublisher Pro? I understand that the marker needs to be placed in a pgf tag that starts a new page, but I thought I could have more than one marker per file. You can have one TopicAlias marker per TOPIC. Usually topics are broken down by heading levels, provided you're splitting on those headings in WWP. -- Bill Swallow HATT List Owner WWP-Users List Owner Senior Member STC, TechValley Chapter STC Single-Sourcing SIG Manager http://techcommdood.blogspot.com avid homebrewer and proud beer snob I see your OOO message and raise you a clue. ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
Re: FrameMaker files and CHM
Which software are you talking about? WWP? You most certainly don't have to have one topic per FM file. That defeats the whole point of single-sourcing with FM and the point of using WWP in the first place. Can you provide details? On 4/10/07, Gross, Karen [EMAIL PROTECTED] wrote: I've assigned my markers, one per heading that starts a new page, and mapped the headings in WWP. Our software, which resides on a machine control, seems to require that we break up the FM file into smaller files, one topic per file. That doesn't sit right with me. It seemed to me that I could have more than one topic, each assigned to separate headings, that reside in one FM file. -- Bill Swallow HATT List Owner WWP-Users List Owner Senior Member STC, TechValley Chapter STC Single-Sourcing SIG Manager http://techcommdood.blogspot.com avid homebrewer and proud beer snob I see your OOO message and raise you a clue. ___ You are currently subscribed to Framers as [EMAIL PROTECTED] Send list messages to [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] or visit http://lists.frameusers.com/mailman/options/framers/archive%40mail-archive.com Send administrative questions to [EMAIL PROTECTED] Visit http://www.frameusers.com/ for more resources and info.
FrameMaker files and CHM
Dear Framers, Is it a requirement to assign one TopicAlias marker per FrameMaker file in order to generate a context-sensitive CHM file using WebWorks ePublisher Pro? I understand that the marker needs to be placed in a pgf tag that starts a new page, but I thought I could have more than one marker per file. I'm using FM 7.2b144 and WWeP v9.2. Regards, Karen J. Gross Sr. Technical Writer Hurco Companies, Inc. 317-298-2637 ext. 2102
FrameMaker files and CHM
You can have as many as you want. It depends on your software. How many buttons do you have that point to different topics. If you have 10 help buttons that point to ten aliases, then you can have 10 topics. You need your software engineer to generate a resource.h file for you. That will tell you how many aliases the software has. Then you can create topic markers for all of the aliases and place them whereever you want. Go to the WebWorks help and search on context-sensitive help. You can also join the webworks help group on yahoo. -Gillian From: framers-bounces+gflato=nanometrics@lists.frameusers.com on behalf of Gross, Karen Sent: Tue 4/10/2007 12:33 PM To: framers at lists.frameusers.com Subject: FrameMaker files and CHM Dear Framers, have Is it a requirement to assign one TopicAlias marker per FrameMaker file in order to generate a context-sensitive CHM file using WebWorks ePublisher Pro? I understand that the marker needs to be placed in a pgf tag that starts a new page, but I thought I could have more than one marker per file. I'm using FM 7.2b144 and WWeP v9.2. Regards, Karen J. Gross Sr. Technical Writer Hurco Companies, Inc. 317-298-2637 ext. 2102 ___ You are currently subscribed to Framers as gflato at nanometrics.com. Send list messages to framers at lists.frameusers.com. To unsubscribe send a blank email to framers-unsubscribe at lists.frameusers.com or visit http://lists.frameusers.com/mailman/options/framers/gflato%40nanometrics.com Send administrative questions to listadmin at frameusers.com. Visit http://www.frameusers.com/ for more resources and info.
FrameMaker files and CHM
> Is it a requirement to assign one TopicAlias marker per FrameMaker file > in order to generate a context-sensitive CHM file using WebWorks > ePublisher Pro? I understand that the marker needs to be placed in a pgf > tag that starts a new page, but I thought I could have more than one > marker per file. You can have one TopicAlias marker per TOPIC. Usually topics are broken down by heading levels, provided you're splitting on those headings in WWP. -- Bill Swallow HATT List Owner WWP-Users List Owner Senior Member STC, TechValley Chapter STC Single-Sourcing SIG Manager http://techcommdood.blogspot.com avid homebrewer and proud beer snob "I see your OOO message and raise you a clue."
FrameMaker files and CHM
I've assigned my markers, one per heading that starts a new page, and mapped the headings in WWP. Our software, which resides on a machine control, seems to require that we break up the FM file into smaller files, one topic per file. That doesn't sit right with me. It seemed to me that I could have more than one topic, each assigned to separate headings, that reside in one FM file. -Original Message- From: Bill Swallow [mailto:techcommd...@gmail.com] Sent: Tuesday, April 10, 2007 4:32 PM To: Gross, Karen Cc: framers at lists.frameusers.com Subject: Re: FrameMaker files and CHM > Is it a requirement to assign one TopicAlias marker per FrameMaker file > in order to generate a context-sensitive CHM file using WebWorks > ePublisher Pro? I understand that the marker needs to be placed in a pgf > tag that starts a new page, but I thought I could have more than one > marker per file. You can have one TopicAlias marker per TOPIC. Usually topics are broken down by heading levels, provided you're splitting on those headings in WWP. -- Bill Swallow HATT List Owner WWP-Users List Owner Senior Member STC, TechValley Chapter STC Single-Sourcing SIG Manager http://techcommdood.blogspot.com avid homebrewer and proud beer snob "I see your OOO message and raise you a clue."
FrameMaker files and CHM
Which software are you talking about? WWP? You most certainly don't have to have one topic per FM file. That defeats the whole point of single-sourcing with FM and the point of using WWP in the first place. Can you provide details? On 4/10/07, Gross, Karen wrote: > I've assigned my markers, one per heading that starts a new page, and > mapped the headings in WWP. Our software, which resides on a machine > control, seems to require that we break up the FM file into smaller > files, one topic per file. That doesn't sit right with me. It seemed to > me that I could have more than one topic, each assigned to separate > headings, that reside in one FM file. -- Bill Swallow HATT List Owner WWP-Users List Owner Senior Member STC, TechValley Chapter STC Single-Sourcing SIG Manager http://techcommdood.blogspot.com avid homebrewer and proud beer snob "I see your OOO message and raise you a clue."
FrameMaker files and CHM
Sorry, the software to which I was referring is the application for which we're providing context-sensitive help. I haven't found any documentation stating anything about needing to break up the FM files per topic. Our software developer claims it's necessary, and our tests on the machine control prove him to be correct. I suspect the problem is with our control's software. At the very least, I'm missing something that will make it all work. We're using a custom .h file that holds our topic IDs and the control screen IDs (Map IDs). Example: #define IDH_ScreenName 123. The text is the same as what we put in the TopicAlias marker. The screen ID is the number assigned to the screen by the software developers. -Original Message- From: Bill Swallow [mailto:techcommd...@gmail.com] Sent: Tuesday, April 10, 2007 4:40 PM To: Gross, Karen Cc: framers at lists.frameusers.com Subject: Re: FrameMaker files and CHM Which software are you talking about? WWP? You most certainly don't have to have one topic per FM file. That defeats the whole point of single-sourcing with FM and the point of using WWP in the first place. Can you provide details? On 4/10/07, Gross, Karen wrote: > I've assigned my markers, one per heading that starts a new page, and > mapped the headings in WWP. Our software, which resides on a machine > control, seems to require that we break up the FM file into smaller > files, one topic per file. That doesn't sit right with me. It seemed to > me that I could have more than one topic, each assigned to separate > headings, that reside in one FM file. -- Bill Swallow HATT List Owner WWP-Users List Owner Senior Member STC, TechValley Chapter STC Single-Sourcing SIG Manager http://techcommdood.blogspot.com avid homebrewer and proud beer snob "I see your OOO message and raise you a clue."
