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; } } }

Preview 2 documents from one DCR

g_sal

TS6.5, Win2003

We have a requirement that all our generated pages be in English and French. We've identified numerous ways of coupling two documents and are in the process of evaluating each alternative.

One scheme thought of was having one DCT that would contain English and French fields. A workflow would then output not one but two documents in English and French. Building a workflow to do this seems feasible enough.

A problem arises when trying to preview the document from this multilingual DCR. Is there any means of opening two windows to preview an English and French document with one click of the preview button?

I'm assuming it can be done this way:
1. FormAPI triggers OnPreview event
2. Callserver runs script that generates second preview file
3. Something launches another browser window displaying second preview document

Would someone care to provide insight as to whether this is feasible?

Thanks

Edited by g_sal on 08/03/05 12:30 PM (server time).

Find more posts tagged with

Comments

Adam Stoller

I'd consider replacing the OOTB preview menu / links with custom menu / links that [presumably] process the same DCR with two different PTs to generate two different output files and then opens each output file up in a new window.

You *might* be able to do this with the OOTB stuff if you have one PT generate two files (iw_ostream or basic perl I/O) - but I'm not sure you can get two windows to open automatically from that (like if you were to somehow embed javascript code in the PT or perhaps perl code to somehow open a window with a given URl in it?)

I think the first approach is generally cleaner and will probably be a lot easier to figure out.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

I've seen people handle previewing multipage docs (i.e. those that use iw_ostream to create child pages) by checking in the tpl to see whether they are in preview mode or really generating (i.e. check the value of iwpt_get_ofile to see if it's a zz_preview file or not). If they are previewing they create a big framework that puts the content of the various page inside independent tables in one big doc.

You could do something similar. In preview mode, add an onLoad handler to your body that would pop open a second window to show the other language version. There's a lot of variables that go into deciding what the best thing to do in your case is. For instance, on generation is you idea that you would pass a parameter to iwpt_compile.ipl to determine which language version you are generating, or were you planning on generating both at the same time with iw_ostream.

Anyway, that should at least get you thinking about some possibilitites.

g_sal

Thanks for the responses guys.

I'd say that the implementation of this bilingual solution is too cumbersome. We'll have to look at other alternatives. Paired DCR's linked by an extended attribute for instance.