Dear Byomokesh,
There are many aspects to "quality":
- typographical
- pagination (whether the lines adhere to a fixed grid, the "register")
- the achievable technical quality of the generated PDF
- whether it complies with, e.g. PDF/X-3
- whether it's accessible (linear reading order, proper
caption/heading etc. markup works better with Antenna House than with
InDesign)
- aptness for certain content requirements
- e.g., it is not possible to have more than one index with InDesign
- aptness to design / workflow requiremtens
- whether ad-hoc placement, shape etc. of frames and other objects is
interactively controllable
- whether you have to check that visual appearance and XML structure
align (no problem with FO, difficult with InDesign)
- the quality of the XML data after author corrections have been carried out
- InDesign: see above (example: is you split a paragraph that has
been 'tagged' as <p> into two in Indesign, without further quality
insurance measurements the output will look like
<p>First para.
Second para.</p>
That is to say, InDesign primarily regards XML characters such as
newline as structuring elements, not the XML structure.
You can script this mapping when importing XML, but you cannot
enforce automatically that the reverse mapping will be applied upon
export. The XML tags (yes, it's appropriate to use the T-word here) are
carried along in the internal InDesign document format, as a kind of
contextual metadata, in a piggyback fashion on top of the layout
information. In our experience, it's sometimes better to let the
typesetters create a conventional, non-XML document, export it as XHTML
(with some scripting beforehand, in order to mark up characters such as
tab, or to mark up ad-hoc boldface formatting as a named character
style) and then use XSLT2 to create the target XML data.
Clearly, FO is better off in this regard as there is no import/export
procedure, it's just batch-processing according to rules. The drawback
of batch processing is the lack of interactivity and the relatively
cumbersome means of fine-tuning page layout individually.
So, as others said before, it depends on your workflow, layout,
accessibility and other requirements. It's impossible to give a general
answer because quality is such a contextual, relative property.
Gerrit
On 17.03.2010 06:22, byomokesh wrote:
Hi,
What is the difference between XSL:FO create PDF and InDesign creation PDF.
Which is good Quality?
I want to know only Quality wise.
Thank
Byomokesh
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--
Gerrit Imsieke
Geschäftsführer / Managing Director
le-tex publishing services GmbH
Weissenfelser Str. 84, 04229 Leipzig, Germany
Phone +49 341 355356 110, Fax +49 341 355356 510
gerrit(_dot_)imsieke(_at_)le-tex(_dot_)de, http://www.le-tex.de
Registergericht / Commercial Register: Amtsgericht Leipzig
Registernummer / Registration Number: HRB 24930
Geschäftsführer: Gerrit Imsieke, Svea Jelonek,
Thomas Schmidt, Dr. Reinhard Vöckler
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--