MadCap Software Forums

Laurent, Lisas solution is a good one, but in regards to the having one project for all languages, keep in mind the following: While your team handles as in your example French and German, make sur to have also processes in place when you handle it when more "exotic" (Japanese for example)...

Damadeo, this is an interesting challenge. The way we have managed it here at my work is very simple, and this might work for you. Besides minimizing the use of screen shots alltogether we also made it mandatory that there are no translatable items in any of our screenshots, therefore, we use the sa...

The issue has been solved in conjunction with Lingo Support. Here is the explanation in case someone else runs into this. The project in question was originally created with Lingo 8 with a number of languages. Going forward only 2 languages were consistently updated and the others remained in the st...

I have a rather large lingo project, and I did run into the following problem. The translation was done via the XLIFF option with an external tool and I did get the translation back from the vendor. However, when I attempt to merge the bundle it will not allow me to do so for Spanish. The other lang...

Jim,

now I understand. No, at this time there is no way for this and I am doing the same manual renaming.

Jim,

the project is not compiled in Lingo, just exported from it after the translation has been completed. For the compiling of the final product aka the output you have to use Flare. In Flare you can define as you see fit.

Excellent. Hope it works out correctly.

Vanessa, thats probably the only way of doing it. Just one recommendation on my part in order to do a manual replace without compromising the TM quality. Instead of just attempting to replace FR with fr-FR I would recommend to copy the whole language segment identifier <tuv xml:lang="FR"> ...

Kai, I have to agree with Rob here. I am actually using Lingo exactly for this purpose. The problem with the default file type definition is the fact that the definition requires customization, since almost no-one uses the default. In my case I get documentation from writers around the World and tem...

Chris,

the link contains a nice little comparison that should help somewhat: http://erikej.blogspot.com/2011/01/comp ... 4-and.html

Philip,

at this time this is not possible.

Patrick, here are the answers: First of all, I updated the workflow a bit since some of the fixes from SDL came in with the latest patch. Ist now back down to 18 steps. For the Intro: I only translated the actual Flare files, until the bug was fixed. I am back to translating the .XLF files again. As...

Patrick,

I will relpy tomorrow in more Detail. Lots of Meetings...

Renee, your translator is using an EOL Version of the SDLX tool for the Translation. The language codes for Latin American Spanish have been deprecated a while back. Here is a suggestion: 1. Have the vendor provide you with the TMX file of the Translation Memory. You can then go ahead and use Notepa...

Following you will find a high-level description of the workflow in use for the localization of documentation written in Flare and being prepared for L10N with Lingo but translated with SDL Studio. I though it might be useful for you. THE WORKFLOW WAS UPDATED ON MARCH 31 TO REFLECT SDL FIXES. I am u...

Here is the Workaround instituted to solve the issue with the perfect matches and context matches. While I still process the update through Lingo, once I have the Project updated in Lingo, I am not using the exported lingo package. Instead I am exporting the list of changed files from Lingo and crea...

As promised here is a description of the bug: We are implementing a large scale L10N environment for Flare projects using MadCap Lingo in conjunction with SDL Studio 2014 SP2 latest patch. We do not use the translation memorx and termbase features of Lingo, because it does not meet my requirements. ...

Magdalene,

I am actually in the process of trying out a Workaround. Also, I plan on later to explain the whole bug in more Detail.

Just as an FYI, I found out that perfect and context matches do not work in SDL STudio, when it comes from a Lingo update with the xliff Option. I forwarded the bug to SDL, and let you know, when I find out more.