MadCap Software Forums

I think I've narrowed it down. I created a test project and when my global.css stylesheet is not applied to the topic, I don't encounter these problems. BUT when the global.css stylesheet is applied, I do have the problems.

How do I determine what is causing this problem in the stylesheet though?

Slight update. I've tried the following troubleshooting steps:

- Rebooting the PC
- Ran the "Clean Project" option within Flare
- Manually deleted the Analyzer and Outputs folders
- Inserted a new topic and attempted to insert a table (to make sure it was affecting both new and existing topics ...

The new projects were created using Flare 6.1. The old projects were created using Flare 4.0.

The problem is in new and existing topics. But the problem is recent (within the last month?), because when I was setting up the projects (converting from FrameMaker), I never encounted this problem.

I ...

One other thing - this is only occuring in our new projects. If I open one of the older legacy projects (that uses different topic stylesheets and table stylesheets), it's not a problem.

When attempting to insert the table, the topic has focus and the cursor is within the topic.

I've tried:
- Rebooting the PC
- Running CCleaner to fix any potential registry issues
- Uninstalled Flare/Reinstalled Flare

Nothing's helped.

If I select > Table menu > Insert > Table, Table is grayed out and inaccessible. If I place the cursor within an existing table and try to access the Table Properties dialog, I get the following exception error: Any ideas?

I have also noticed problem # 3 since upgrading to Flare 6.x. I didn't experience this problem in any of the previous releases.

You might try the following:
- From the Translate menu, select Pick TM to open the Current Translation Memory Provider dialog.
- From the Selected Translation Memory drop-down menu, select your TM database. Once the TM is selected in the dialog, you can either click the Import TMX button directly ...

Jennifer - thanks for posting!

Do you have any recommendations for MadCap Lingo users who are working with translation vendors?

We've been using Flare for several years for our CHM and DotNet Help projects, but we just bought a copy of Lingo and we're planning to use it for our next translation ...

Hi chenyu, have you submitted a bug to MadCap technical support for this issue?

We also translate to Chinese and output to PDF, but I'm still in the process of porting our FrameMaker documentation to Flare, so we haven't actually distributed any of the Flare-generated PDFs yet.

Thanks for the recommendation! Unfortunately, I think this method only works for DotNet help, HTML Help and Webhelp outputs. Bummer! That would have been perfect!

Thanks for the response! I tried manually typing in "Global.css" from the list of files to be excluded, but it didn't work. It may have been in conflict, based on the order of precedence for these fields.

We actually decided to not import the translated content into the English project, so this is ...

No problem! Glad I could help!

Yeah, it sounds like it could be a bug.

Maybe post a screenshot of your import settings, your conditional tag settings for the Import Conditions and the Accept Imported Documents dialog when the Auto-Exclude checkbox is checked and unchecked?

Just to verify - your content is conditionally tagged ...

Did you specify any file types for the Include Files or Exclude Files fields? (I'm assuming so, but just wanted to check.)

Also, check out this Flare topic for a list of global importing rules. It's for Flare 6, but might help to determine which of the fields takes precedence.
http://webhelp ...

We've decided to simply output the translations from their own project, rather than import them into the English project for PDF creation. We do have the page numbering limitation, but we can live with that. The translation vendor will manually combine the individual PDFs as part of their formatting ...

We've decided to simply output the translations from their own project, rather than import them into the English project for PDF creation. We do have the page numbering limitation, but we can live with that. The translation vendor will manually combine the individual PDFs as part of their formatting ...

Oops. Forgot about page numbering. I could manually change the page numbers in the PDF, but I don't think that's a feasible solution. Back to the drawing board.

Good point. I'll test it out and see what the output looks like.

If I use global project linking to import translated content into our English project (to generate a multi-language PDF), what is the best way to handle translated graphics?

In our QSGs, we have several graphics that include translated text and several that do not. For the graphics that do not ...

For our stylesheets, I have set up a “Global.css” that is stored in the global English project. In the global translation projects, I store both a copy of the Global.css that is used in the English global project and a “Global_xx.css” for the translated language (to include the translated ...

Typically, our translated projects are a mirror of the English projects (folder structure, file names, etc.). Our printed quick start guides are a single document that contains the English text and all translations in a single PDF file. If we use global project linking to import the translated QSG ...

For my English project, I’m currently using the folder structure that Nita Beck recommended (GlobalImages, GlobalResources, GlobalTopics, Images, Resources, Topics). This has worked well for differentiating the global vs. the local content.

As a general rule, if I set up global project linking ...

Hi all! I'm in the process of setting up global project linking for our English projects and translated projects and I'm stumped on how to best set up these projects for both our internal documentation team and the translation vendors. Any help is appreciated!

Our printed quick start guides are a ...

That worked perfectly! Thanks for the advice!!