🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: adobe.indesign.sdk
Article #47

Re: IDML to INDD conversion

#47
From: toan.nguyen
Date: Wed, 30 Jan 2013 09:52
9 lines
1543 bytes
On Thursday, March 11, 2010 4:34:47 AM UTC+7, Radha wrote:
> I want to conver the IDML xml archive to Binary INDD file.
> 
> Yes ofcourse IDML file can be opened directly on Indesign. But I would
> like to know is there a way to convert the IDML to INDD.
> 
> Thanks...

save as to INDD
Technical Details
Message-ID: <d6d8d4bf-bfa2-4e11-8638-6637c2440e01@googlegroups.com>
Path: arc1-ca.pugleaf.net!6ni25139pbd.1!nntp.google.com!f6no3279375pbd.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
References: <3d7604a5-3ca6-4a1e-8628-425dc291ffce@g7g2000yqe.googlegroups.com>

Show Full Headers
Complete Article Headers
X-Google-Thread: f63e9,952a2bdd453758c8
X-Google-NewGroupId: yes
X-Google-Attributes: gid79d0882076,domainid0,public,usenet
X-Google-Language: ENGLISH,ASCII-7-bit
X-Received: by 10.66.76.201 with SMTP id m9mr417587paw.33.1359539524627;
        Wed, 30 Jan 2013 01:52:04 -0800 (PST)
X-Received: by 10.50.34.167 with SMTP id a7mr611175igj.5.1359539524254; Wed,
 30 Jan 2013 01:52:04 -0800 (PST)
Path: arc1-ca.pugleaf.net!6ni25139pbd.1!nntp.google.com!f6no3279375pbd.1!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: adobe.indesign.sdk
Date: Wed, 30 Jan 2013 01:52:03 -0800 (PST)
In-Reply-To: <3d7604a5-3ca6-4a1e-8628-425dc291ffce@g7g2000yqe.googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=113.161.80.48;
 posting-account=pLTGyAoAAABRLPE1Bg6hkGj-FvJacamN
NNTP-Posting-Host: 113.161.80.48
References: <3d7604a5-3ca6-4a1e-8628-425dc291ffce@g7g2000yqe.googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <d6d8d4bf-bfa2-4e11-8638-6637c2440e01@googlegroups.com>
Subject: Re: IDML to INDD conversion
From: toan.nguyen@audiencemedia.com
Injection-Date: Wed, 30 Jan 2013 09:52:04 +0000
Content-Type: text/plain; charset=ISO-8859-1