Hello,
Until 2 days ago, my colleague and I were happily using Flare 2016 r2 with Git via Bit Bucket.
Then, we upgraded to Flare 2017. I could no longer do anything in Flare other than open the project file. Clicking a folder would cause the program to stop responding. I was on the phone with ...
Search found 9 matches
- Thu Jan 12, 2017 7:39 pm
- Forum: Source Control
- Topic: Git (Bit Bucket) and Flare Don't Like Each Other Anymore
- Replies: 1
- Views: 2211
- Wed Oct 19, 2016 8:13 pm
- Forum: Single-Sourcing
- Topic: Base auto-numbering on TOC outline level
- Replies: 3
- Views: 2745
Re: Base auto-numbering on TOC outline level
It is complex. Our products are highly configurable, so customers can get any number of "pieces" (for lack of a better term). In the Help, it's pretty easy to move things around. But in PDF, it's much harder, of course.
Thanks!
~Robyn
Thanks!
~Robyn
- Wed Oct 19, 2016 8:10 pm
- Forum: Styles, Stylesheets and XML
- Topic: Fonts are sans-serif when I've specified serif
- Replies: 6
- Views: 4614
Re: Fonts are sans-serif when I've specified serif
Glossary terms aren't on any page in the web media. There's nothing to conditionalize.
Likewise, the MiniTOC proxy entries can't be conditionalized either.
The whole point of the stylesheet is to format the same content differently in different outputs. It makes no sense that I would have to ...
Likewise, the MiniTOC proxy entries can't be conditionalized either.
The whole point of the stylesheet is to format the same content differently in different outputs. It makes no sense that I would have to ...
- Tue Oct 18, 2016 9:55 am
- Forum: Single-Sourcing
- Topic: Base auto-numbering on TOC outline level
- Replies: 3
- Views: 2745
Base auto-numbering on TOC outline level
Hello,
I'm full of questions today. I'm working with Flare 12.
Flare can format a TOC based on the outline TOC. Thus, even if some of my topics have H1s, if they are located under another topic with an H1, the TOC displays it at the H2 level.
I want to format the first heading in a chapter with ...
I'm full of questions today. I'm working with Flare 12.
Flare can format a TOC based on the outline TOC. Thus, even if some of my topics have H1s, if they are located under another topic with an H1, the TOC displays it at the H2 level.
I want to format the first heading in a chapter with ...
- Tue Oct 18, 2016 8:41 am
- Forum: Styles, Stylesheets and XML
- Topic: Fonts are sans-serif when I've specified serif
- Replies: 6
- Views: 4614
Fonts are sans-serif when I've specified serif
Hello,
I'm working in Flare 12, creating styles for the print medium (PDF output).
Some fonts are appearing in sans-serif even though the style sheet specifies serif. Specifically, the mini TOCs at the beginning of each "chapter" and the Glossary definitions are sans-serif instead of serif.
For ...
I'm working in Flare 12, creating styles for the print medium (PDF output).
Some fonts are appearing in sans-serif even though the style sheet specifies serif. Specifically, the mini TOCs at the beginning of each "chapter" and the Glossary definitions are sans-serif instead of serif.
For ...
- Mon Oct 17, 2016 6:58 pm
- Forum: Single-Sourcing
- Topic: Context-Sensitive Cross-References: page number issue
- Replies: 2
- Views: 2374
Re: Context-Sensitive Cross-References: page number issue
I thought I was doing that, but apparently, I wasn't.You just need to adjust the xref format for each medium that you use.
Thank you for your help!
~Robyn
- Mon Oct 17, 2016 1:35 pm
- Forum: Single-Sourcing
- Topic: Context-Sensitive Cross-References: page number issue
- Replies: 2
- Views: 2374
Context-Sensitive Cross-References: page number issue
Working in Flare 12.
I have created a cross-reference format, MadCap.xref.TopicTitle. The definition is:
{b}{h1}{/b} {pageref}
According to their documentation, Flare should automatically remove the pageref when HTML output is generated. Indeed, it does so for their default style MadCap.xref. But ...
I have created a cross-reference format, MadCap.xref.TopicTitle. The definition is:
{b}{h1}{/b} {pageref}
According to their documentation, Flare should automatically remove the pageref when HTML output is generated. Indeed, it does so for their default style MadCap.xref. But ...
- Thu Sep 15, 2016 11:33 am
- Forum: Flare's General Discussion
- Topic: Salesforce - Flare only or Flare with CMS
- Replies: 12
- Views: 7989
Re: Salesforce - Flare only or Flare with CMS
Salesforce no longer uses Flare. They used to use Flare for their developer documentation. For about the last year, they've used a custom, in-house DITA tool based on oXygen. We're a SF partner too, and I was able to talk to a few of their documentation and training managers.
- Sun May 29, 2016 1:29 pm
- Forum: Simon's Career Network
- Topic: Contractor Needed for Short-Term Flare Conversion
- Replies: 1
- Views: 4418
Contractor Needed for Short-Term Flare Conversion
Our company, Vlocity, is migrating from Salesforce Knowledge to MadCap Flare. We have approximately 155 articles to import and format as topics. Each article takes anywhere from 20 minutes to 1 hour to import and format (I did a few to figure it out). We'd like to get everything converted ASAP (of ...