Hi,
I've tryied more times both with Contributor 3.00/Contributor 5.00 and Flare 8.1.2.
What happens:
- In Flare 8.1.2 I prepare the package and I send to the editor
- In Contributor
- the Editor opens the package, adds a comment, deletes a word and inserts a new word
- the Editor save the package and send it to the sender (me)
- In Flare 8.1.2 I:
- open the original project,
- in Review, I clic on Import Review Package then on Topic Reviews
- in Topic Review I see Annotation=1, Changes=0
- I double clic the topic, in fact I see the comment but no change at all
If I or the editor we reopen the package with Contributor we see all the changes but no more tracked... so means we see together the deleted words plus the inserted words.
Help! What we have lost somewhere??
Reviews done with Contributor are not visible in the package
Re: Reviews done with Contributor are not visible in the package
MadCap Support investigated on it and they discovered a double <html></html> tag in each topic.. so we go to remove all of them in order to have the tracking works.
Curious to know that this is a former Robohelp 7 imported project. This is not the first Robohelp project we import, but maybe is the first imported Robohelp project on which we track changes.
In fact we noticed that importing the RH7 project, in some topic I've a long list of HTML tags in this way:
<html>
<html>
<html>
<html>
<html>
<html>
</html>
</html>
</html>
</html>
</html>
</html>
Does anyone of you experinced such behaviour in Robohelp imported projects?
Curious to know that this is a former Robohelp 7 imported project. This is not the first Robohelp project we import, but maybe is the first imported Robohelp project on which we track changes.
In fact we noticed that importing the RH7 project, in some topic I've a long list of HTML tags in this way:
<html>
<html>
<html>
<html>
<html>
<html>
</html>
</html>
</html>
</html>
</html>
</html>
Does anyone of you experinced such behaviour in Robohelp imported projects?
Re: Reviews done with Contributor are not visible in the package
We've imported a lot of projects from Robohelp without encountering this behaviour. Having said that, there are a bunch of other quirks we found, so it's possible there was some oddity in your project which caused this.