MadCap Software Forums

Thanks, Dave, for taking the time to check for any differences, much appreciated.

I'm still trying to find out why it doesn't work in my project though.

I have this in the head of my MasterPage:


<script src="../Scripts/common.js" />
<script src="../Scripts/css.js" />
<script src="../Scripts ...

Yes, I think this is done via the CSS. I'm trying to do something similar right now and stumbled over this: https://www.madcapsoftware.com/blog/201 ... e-outputs/

It's not yet working on my end, but maybe it helps you

Cool feature, thanks for including it here!

We just tested this and the rows do not sort when clicking on the column title. The column title DID change and appears like a link now, but clicking on it doesn't change the order of rows in the table - neither in the preview nor in the output.

Output ...

In our WebHelp output, we have a ref table with about 30 rows. It is updated with every feature release and very important to our customers. Additionally, we have a concept topic that is closely related to the ref table but does not contain the table yet, just an xref to it.

We are considering to ...

We're using the 'mark as new' setting for new topics in our TOC and are starting to wonder if there is a similar thing below the topic level. What we would like to do is to

a) highlight new content on the page and/or
b) allow users to search for topics that contain new content.

I can imagine ...

Thanks, Uwe. We are actually still considering Excel as well, precisely because it is easy to set up, handle and to import/export. But exchanging a centrally maintained excel file across departments to build and maintain terminology does strike me as somewhat anachronistic, especially considering ...

Is anyone using Lingo for translations while managing the terminology (and related workflows) in a separate database? We might have to do that and are wondering which terminology databases work well, i.e. offering the possibility to export tbx basic format to import into Lingo. Any recommendations?

Just as a quick update: I did end up changing the file name back to what it used to be, retracing my steps, taking the safe & sane way out of the mess I had created for myself. But I'd really like to know how shared/global files can be renamed properly. There must be a clever way that doesn't ...

I should know better, but I seem to have outmanoeuvred myself by renaming one of my global table style sheets. *dramatic drummroll* :roll:

The css file is referenced in the local master page of my child project. When I renamed the stylesheet file in my global project, I did select the option to ...

Just in case somebody should run into similar issues, allow me to summarize what happened next (after I contacted the awesome guys and girls at MadCap support):

The correct way to use master pages in combination with google fonts and default stylesheets is as follows:

1. Set master style sheet for ...

When I do that and view the output on a machine where open sans is _not_ installed, the output has a serif-font and looks worse than ever before.

Thanks, Dave, I think I'm beginning to understand how this works in Flare.

Here is how this is set up in our project(s):

1. There are 2 stylesheets in the global project, 1 to play around with and the other called "styles.css" which we consider the default stylesheet for all topics. Additionally ...

We have done that. We installed Open Sans on the machine where Flare is installed, as a consequence Flare listed the font as the available (installed) fonts when we edited the styles.css file, we selected Open Sans in the primary style sheet, then built the output and - voilá - it works like a ...

I kinda knew that. What I do not know is where to do this in Flare. I tried putting it in the master page but this doesn't seem to be the right way.

If I may chime in here... I have a related n00b question... :oops:

I have just installed Open Sans on my VM and Flare immediately listed it among the intalled fonts. So I selected it and built my targets and all is well.

But... this means, users of our WebHelp will only see Open Sans if they also ...

I have a similar problem and still do not quite understand when the drop-down text icon is enabled and when it isn't. We have a lot of drop-down texts within drop down-texts and I managed to insert them in the past, each <li> item of an <ol> being a drop-down text, but every once in a while when ...

Update:

I've also contacted MadCap support and they confirmed that the usual procedure is to first complete the master language version (DE in our case, EN for most of you out there, I guess) and then start localization. With each project update in Lingo the image files are overwritten, so in this ...

Hi there,

where & when in your localization process do you replace the screenshots?

We keep our screenshots in one folder for each product version, like so:

- content/resources/images/current_product_version/...
- content/resources/images/future_product_version/...

and the images in these ...

Hi Jennifer,

thanks so much for the long and informative reply, it is great to be able to benefit from your vast experience! Additionally, I have received a response from the MadCap support wizards, stating pretty much the same thing.

Concepts: I have found Concept.liconceptmap when MadCap ...

Having had a long, hard look at my first output from Lingo, I realized that quite a few things have not been translated, e.g.

- topic file names (*.htm, we generate WebHelp output)
- RelationshipTables
- concept links

I dare say that our U.S. customers will not be impressed if we ask them to open ...

Well, DUUUHHHH!!! me

Typical. As a German saying goes: "I couldn't see the forest because of all the trees!"

Thanks Nita, much appreciated

Having followed the global project linking and folder renaming advice in this thread: http://forums.madcapsoftware.com/viewtopic.php?f=13&t=15985, I have now manouevered myself into a nice little problem.

My project setup is like this:

#1) Global DE project (DE = German), w/ style sheets ...

Thanks Ramon, thanks Jennifer, much appreciated.

I still wonder why 1 global project for each language is advisable. My setup currently looks like this:

1. GlobalProject - containing nothing but the style sheet right now (but one never knows...projects tend to grow :wink:)
2. DE-Project ...

I hope it's okay to bring up this old thread, but it deals with just the decisions I'm about to make with our project, so I thought it might be useful to answer here instead of opening a new thread.

My question is: what's the easiest project setup and workflow if there are only 2 languages ...

Just to show that I'm not idling about and waiting for responses here, I have found this blogpost:

https://kaiweber.wordpress.com/2011/11/21/5-steps-from-legacy-documentation-to-topics/

which linked to this blogpost:

http://kaiweber.wordpress.com/2011/08/15/top-tactics-to-structure-legacy ...