We use BC [mostly] for building release notes with full diffs.
When I build a diff report, using over-under, the added code and the deleted code is all red, making it confusing to easily read the diffs. Most of our changes are minor, making the over-under report, the one of choice.
What I would like, is to have the code that is in the first file that is not in the second file (or visa-versa?) to show as gray and strike-through. I have played with the style-sheet, but can't seem to get it to work.
Also, if I do change the style sheet, do I have to send it along with the diff report for other to see the strike-through? Is there a way to embed the style-sheet (easily) so that the resulting file has it all?
Thanks,
Paul
When I build a diff report, using over-under, the added code and the deleted code is all red, making it confusing to easily read the diffs. Most of our changes are minor, making the over-under report, the one of choice.
What I would like, is to have the code that is in the first file that is not in the second file (or visa-versa?) to show as gray and strike-through. I have played with the style-sheet, but can't seem to get it to work.
Also, if I do change the style sheet, do I have to send it along with the diff report for other to see the strike-through? Is there a way to embed the style-sheet (easily) so that the resulting file has it all?
Thanks,
Paul
Comment