nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

SourceDiff fails for long data lines in DCRs

System

I have just joined a year-old project that had not added pretty_print_dcrs=true to the [teamsite_templating] section of iw.cfg (which should probably be the default to avoid the condition described below). Business users now find themselves needing to compare hundreds of DCRs in workareas to the corresponding versions in STAGING. Since VisualDiff does not work for DCRs they have to use SourceDiff. But SourceDiff does not work properly for DCRs with very long lines of data - the lines get truncated at some point and VisualDiff does not report differences that occur after the truncation. Since by default most of a DCR is written on a single line, SourceDiff is pretty much useless. Corporate policy prevents users from mapping drives to the Interwoven virtual file system so tools such as BeyondCompare cannot be used.

Is there some way to add linefeeds to the DCR data before VisualDiff sees them, or some other solution?

Find more posts tagged with

Comments

Adam Stoller

Top-o-my-head suggestion: Create custom menu item for doing comparisons, have custom menu item prompt for the versions of the files, then create temporary files by processing the DCRs with something like XML::Twig to get the "pretty" format, then perform the diff. If you need to make changes during the diff it gets more complicated, but I believe if you write out the DCR in "pretty" format and then save it (having not set the configuration to use "pretty" format) - that the saved DCR will once again store it without the newlines.

I realize the above is mostly theoretical / hypothetical - but hopefully it's a pointer in the right direction (though it sounds like you should probably enable the "pretty_print" option for them so that over-time they'll be able to get rid of the custom menu item.

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

I know how I could set up a CMI to iwcat old versions (actually it would probably always be WORKAREA and STAGING) and add linefeeds, but I'm not sure I could pass them to the visual comparator unless I write them to somewhere in the workarea (and ensure they are marked private or otherwise not deployed), and it seems like they shouldn't be in the workarea. What are my options for where to write them?

On enabling pretty_print, yes I have done that, but the problem with that is that it doesn't add the linefeeds until you save the DCR through the UI, and then the comparison is totally different because of all the new linefeeds.

Frederik

Hi! (question on the side - new on Teamsite, trying to learn)

Can somebody explain me the specific effect of the pretty_print_dcrs option? I looked for this info in the TS 5.5.1 manuals, but didn't find. I have access to a TS 5.5.2 on solaris dev server, but a (superficial) test with some long lines in a textarea didn't show any differences. Maybe I didn't test the right way? (edit in UI, viewing dcr file in notepad through the iwmount shared drive to windows)

TIA !

Jeremy

Hi,

You're right. I checked the Admin guide and the Templating guide for 5.5.1 and did not see it. But I also checked the 5.5.2 Templating Guide and found it on page 36.

Controlling Printing of Data Content Records
Data content records are normally written so that all content appears on a single line. You have the
option to print so that each new XML element in a data content record start on a new line, indented.
To enable this type of printing, include the following line in the /etc/iw.cfg file.
[teamsite_templating]
pretty_print_dcrs=true

Not sure if this will be availble in 5.5.1 if its not in the manual, but then who knows!!

Hope that helps.

Jeremy

Edited by Jeremy on 08/27/03 02:01 AM (server time).

Frederik

hi Jeremy!

thanks for that... I'm stuck with 5.5.1 manuals :-(

wow... DCR on one long line, sounds like horror Smiley Wink

Anyway, the dev server i have access to, had the pretty_print_dcrs=true. I just imagined it would cut long lines within XML elements somehow, to allow even easier SourceDiff. But that would probably be illegal in XML (as opposed to HTML).

Last question: was pretty_print_dcrs available in TS 5.0? I'm asking coz i know our prod server is still on 5.0

Jeremy

Hi Frederik,

I am not sure if pretty_print_dcrs would be available in 5.0. If its not in the manuals for 5.5.1, but works then maybe you should try it on your 5.0 box to see.
If it doesn't work I don't think having that entry in your iw.cfg would mess anything up...but as I say, i don't think it would! Not 100% sure!

Maybe someone else would know about that.

Jeremy

Frederik

I was previously wondering:

Last question: was pretty_print_dcrs available in TS 5.0?

And after downloading the 5.5.2 docs from support, I found that this setting is mentioned as an enhancement to TST 5.5.2
in TeamSite Templating, Release Notes, Release 5.5.2. Page 5.