Global Project Linking: Importing Translated CSS files

[techwriter31]

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 auto-text for notes, tips, figure numbers, table numbers, etc.). In each language’s stylesheet, I am referencing the Global.css as an import.

If I use global project linking to import translated content into our English project (to generate a multi-language PDF), I believe I would use conditional tags to include the Global_xx.css file and exclude the Global.css file (it currently has no conditional tags applied), so that I don’t overwrite the “Global.css” file that is being imported from the global English project. While this currently works, I don’t think I want to conditionalize the Global_xx.css file for these specific outputs because this file will also be used for all other translated content that is directly generated from the translated Flare projects.

Should I hardcode the "Global_xx.css" file name when specifying which files to import into the English project and not use conditional tags on these files?

Any suggestions?

[NorthEast]

You can exclude your stylesheet file from the import; e.g. in the import editor, type Global.css in the Exclude files box.

Mind, there shouldn't be any problem in using conditions as you have done though; having an extra condition in the translated projects will do no harm, assuming the condition is just used for the import and nothing else inside those projects.

[techwriter31]

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 longer an issue for us.