MadCap Software Forums

I have checked the help back and forth, and it seems the hyphenation settings are not language-dependent. For the time being I have resorted to turning hyphenation off in all used text styles, and it has made the translators a bit happier, though the ragged edges are really too ragged to my taste ...

You're entirely correct, RossF. We've been building one, piece by piece and I have even suggested to the translation agency to sell it back to SDL

The other part is the quality of the XML generated by LIngo. I am still waiting for more information from their terrific support team, but some tagging is not strict enough to Trados's taste and the resulting translated files cannot be integrated back in to Lingo. Moreover, some segments seem to be ...

Update : Trados, even SLD Studio 2011 with the MadCap Translation module and the TagEditor still does not see some translatable texts.
Examples are :
. CSS (cross-references, for instance)
. fltar
. flpgl

So if you have any string of characters that need to be translated in these files, they have ...

We have one Flare project per target language and using different CSS makes perfect sense, so thank you for the wealth of information I've just received browsing through this topic.
I was wondering if there was a way to tell Flare "this project is in Swedish" and have, say, the hyphenation follow ...

You are translating into all these European languages, and a couple of Chinese variants too. Do you not have a need for an English translation for your documentation?

We need the documentation in all official languages used in the countries in which our products are sold, so the translation into ...

I have also stumbled in that situation. What caused it is Lingo getting tagging mixed-up and thinking a tag is number 12 of the file when in the source it's number 5.
A workaround is the following:
- delete all tags in target segment
- right-click on segment and re-import tags from source
- place ...

Trados can be set to identify this markup so translators can "see" the strings and translate them. Be aware that if you're subcontracting the translation, you'll have to explain carefully what values are correct and why, otherwise the destinations may be incorrect.
Lingo does not suggest .fltar ...

More on this. After a bunch of issues in the xliff tagging generated by Lingo, we've decided to go a shorter route and translate the Flare projects directly in SDL Studio 2011. So the workflow becomes the following:
Flare French -> Flare English -> Flare Simplified Chinese -> Flare Traditional ...

Tip: request from your translator or translation agency they use SLD studio 2011 with the plug-in for Flare projects.
Also, specify clearly which files you want them to translate, and which files you don't want them to translate. We've just done that and all in all it works much much better (from my ...

Do not upgrade to V7 too early: I have found out the painful way that bundles prepared with V6 and bundles prepared with V7 are incompatible. I upgraded between the initial translation request and the complements and now I have a very invalid DB for two languages.
It seems the only solution is to re ...

I have found a case where setting a Stylesheet at project level is a life-saver.

Word documents are regularly migrated to XML documentation, currently in Flare. The import wizard automatically creates a Stylesheet, based on the styles used in the Word document. It also creates Master pages, which ...

First of all, did you try with Lingo 7? Does it behave the same way?

Second, MadCap tags are usually a mess in Trados and some other translation tools don't even recognize them. I've received translations where translators typed all cross-references because they couldn't see the tags and thought ...

For the sake of completeness, the main issue there was the chair-keyboard interface, the fallible element, the human, me.
One needs to export the translations from Lingo into a new Flare project. And there is a big menu entry to do just that under File \ Export.

So now you know, and so do I.

Doh.

In my experience, translation agencies are usually receptive. The passive resistance comes more from the local representatives of the company itself than from the translators. It's not a criticism, it's just the way things are.

I completely agree with you, "Rock solid" is a good description of how ...

I know this looks like a Very Bad Idea, and to my view it is, but it might just be my job to make it work.

Bit of background: We're translating our user documentation from French into a bunch of European languages. Our local representatives in, respectively China and Taiwan, are asking for the ...

The translators of our translation agency work with Trados. When they ship us a translated bundle, they also send the translation memory.

Open the Lingo project, load the translation memory and the bundle, and watch out for the following pitfalls:
- the keywords tags are not in front of the word ...

And for the sake of completeness, I must add that none of the translated topics display any target language strings.
All I see is my source content, and the flag indicating the topic is meant to be in the target language.

Could something have gone wrong during the import of the translation? I can ...

Turning to you, Lingo wizards. I would like to tap in your experience as I am in what seems a surprising situation.
(The names for the project and various files are made up, just focus on the extensions.)
I have received the first package translated from a Flare project. Unzip projet ok, load it ...

Unfortunately, there is nothing in Lingo's documentation, so the translation manager and I rolled up our sleeves and ran a couple of tries before working on serious matter.

For the record, and because I bumped into this message when importing my very first translation, this message is displayed when the structure of the folders/files is different in the bundle that is being merged compared to the structure of these files in the Lingo project.

The solution is to either ...