Flare 12 inc. latest update.
When requiring output in Word, is it possible to add a Page Number where there would normally be a Hyperlink?
For example, a Topic in my .chm will have a Hyperlink such as: "See also: Global: Embosser Setup...".
What I would like to see in my Word file is: "See also: Global Embosser Setup... (on page 144)".
Which begs another question. Is there no system based Help for Flare 12, or is it entirely on-line these days?
Page Numbers instead of Hyperlinks
-
Techno
- Sr. Propeller Head
- Posts: 193
- Joined: Fri Dec 09, 2005 9:23 pm
- Location: NORTHAMPTON, England, UK
- Contact:
Page Numbers instead of Hyperlinks
George Bell
Techno-Vision Systems Ltd., U.K.
Techno-Vision Systems Ltd., U.K.
-
Techno
- Sr. Propeller Head
- Posts: 193
- Joined: Fri Dec 09, 2005 9:23 pm
- Location: NORTHAMPTON, England, UK
- Contact:
Re: Page Numbers instead of Hyperlinks
After further research, I finally found a Madcap page which shows exactly what I wish to achieve in the first image at http://help.madcapsoftware.com/flare12/ ... rences.htm.
However even after downloading Madcap's 290 page Navigation Links Guide, and studied Chapter 4, Cross-References, I'm only a little wiser. (I hasten to add that English is my first language!!)
Is there no simple, "Dummies" type guide which gives clear step by step instructions on creating the example given at the above link?
However even after downloading Madcap's 290 page Navigation Links Guide, and studied Chapter 4, Cross-References, I'm only a little wiser. (I hasten to add that English is my first language!!)
Is there no simple, "Dummies" type guide which gives clear step by step instructions on creating the example given at the above link?
George Bell
Techno-Vision Systems Ltd., U.K.
Techno-Vision Systems Ltd., U.K.
-
Nita Beck
- Senior Propellus Maximus
- Posts: 3672
- Joined: Thu Feb 02, 2006 9:57 am
- Location: Pittsford, NY
Re: Page Numbers instead of Hyperlinks
Local Help in Flare 12 is not available by default, but it's easy to turn on. Go to File > Options > General and select the Use Local Help check box. Then, if there is no internet connectivity, the local Help will be presented.
About the format of your cross-reference in print output. You'll need to work in the medium you use for your Word output. That might be the built-in "print" medium, or it could be a custom medium. (For example, I use a custom medium called "WordPDF" for my Word and PDF outputs.)
In any case, in that medium, add something like the following:
The {pageref} will be replaced with "on page n" where n is the number, of course.
Also, please be aware that in Word output, I'm pretty sure that the only part of the xref that will be a live link is the page number. The text will not be. This is not the case for PDF output, in which both the text and the page number will be links.
I hope this is enough to point you in the right direction.
EDIT: Let me clarify one thing. I'm talking about cross-references, not hyperlinks. You can format the cross-references to look exactly like a standard hyperlink in online output, but then have it look like a standard print-based cross-reference (as in, with the page number) in print output. Perhaps I wasn't clear at the start...)
About the format of your cross-reference in print output. You'll need to work in the medium you use for your Word output. That might be the built-in "print" medium, or it could be a custom medium. (For example, I use a custom medium called "WordPDF" for my Word and PDF outputs.)
In any case, in that medium, add something like the following:
Code: Select all
MadCap|xref
{
mc-format: '{paratext} ({pageref})';
}Also, please be aware that in Word output, I'm pretty sure that the only part of the xref that will be a live link is the page number. The text will not be. This is not the case for PDF output, in which both the text and the page number will be links.
I hope this is enough to point you in the right direction.
EDIT: Let me clarify one thing. I'm talking about cross-references, not hyperlinks. You can format the cross-references to look exactly like a standard hyperlink in online output, but then have it look like a standard print-based cross-reference (as in, with the page number) in print output. Perhaps I wasn't clear at the start...)
Nita

RETIRED, but still fond of all the Flare friends I've made. See you around now and then!
RETIRED, but still fond of all the Flare friends I've made. See you around now and then!
-
GeorgeBell
- Sr. Propeller Head
- Posts: 114
- Joined: Thu Nov 22, 2012 3:27 am
Re: Page Numbers instead of Hyperlinks + Word compile failur
Bless you, Nita! You have helped me find a nasty bug.
I have checked the box you advised, but what I really want is local system Help by default. Short of killing wireless and disconnecting the network connection, can this be done?
The "bug" relates to the check box option 2 up from the Help one, "Import/Export Word files without MS Office". For some time, I have not been able to compile Word files on my laptop Windows 10 system with Office 2016. We run Source Control (with git server), and all worked fine on the office based Windows 7 with office 2010.
Needless to say, the error (copied here) is as user-friendly and informative as I don't know what
10086, "Build failed: Export to doc failed. Conversion to doc can be done manually on the XML file located at file:///C:/Users/George2.TVS.000/Documents/dbthelp/Output/George2/Temporary/Docs for Proofing/The_Menus_(All)/DBT_The_Menus__Windows_.xml. Open the document in Word and specify the desired file type under the Save As menu. Note: No images have been embedded and no fields have been updated. , The_Menus_(All), Compiler, C:\Users\George2.TVS.000\Documents\dbthelp\Project\Targets\Docs for Proofing\The_Menus_(All).fltar, "
It would not have been so bad if the XML file had actually been saved, but it had not!!!
Well, having spotted this Import/Export box was checked, I unchecked it, and all my Word files are now compiling OK.
Back to cross-references. Where I have a complete mental block, is exactly what to do, where and in what, such that Build to a .chm will show "See [Hyperlink] to the Topic", and but Build to Word will show "See [Topic Title] on page #".
Conditional Text is perhaps one option, but with literally hundreds of these to deal with, I'm hoping to find a simpler, quick to apply, option.
Many thanks for your help so far, especially the unexpected help.
I have checked the box you advised, but what I really want is local system Help by default. Short of killing wireless and disconnecting the network connection, can this be done?
The "bug" relates to the check box option 2 up from the Help one, "Import/Export Word files without MS Office". For some time, I have not been able to compile Word files on my laptop Windows 10 system with Office 2016. We run Source Control (with git server), and all worked fine on the office based Windows 7 with office 2010.
Needless to say, the error (copied here) is as user-friendly and informative as I don't know what
10086, "Build failed: Export to doc failed. Conversion to doc can be done manually on the XML file located at file:///C:/Users/George2.TVS.000/Documents/dbthelp/Output/George2/Temporary/Docs for Proofing/The_Menus_(All)/DBT_The_Menus__Windows_.xml. Open the document in Word and specify the desired file type under the Save As menu. Note: No images have been embedded and no fields have been updated. , The_Menus_(All), Compiler, C:\Users\George2.TVS.000\Documents\dbthelp\Project\Targets\Docs for Proofing\The_Menus_(All).fltar, "
It would not have been so bad if the XML file had actually been saved, but it had not!!!
Well, having spotted this Import/Export box was checked, I unchecked it, and all my Word files are now compiling OK.
Back to cross-references. Where I have a complete mental block, is exactly what to do, where and in what, such that Build to a .chm will show "See [Hyperlink] to the Topic", and but Build to Word will show "See [Topic Title] on page #".
Conditional Text is perhaps one option, but with literally hundreds of these to deal with, I'm hoping to find a simpler, quick to apply, option.
Many thanks for your help so far, especially the unexpected help.