Lack of reliable IDML import is a Show-Stopper

Previous topic - Next topic

ScribasTester

Based on a recommendation, I tried Scribus in the latest available Windows version (v1.7.3).

The very first thing I wanted to test was whether Scribus could become a replacement for InDesign.

So I tried to open an existing *.indd file.
The answer: it can't.

Fine, so I exported the document from InDesign as an *.idml file instead.

Scribus does import this ZIP-based format, but the result was disappointing. At first glance it was obvious that the fonts were not imported correctly, the font sizes were wrong, and none of the images were visible.

After spending several hours trying to figure out what was going on, I finally found the font mapping table—only to discover that not all of my installed Windows fonts were even recognized.

Sorry to say this, but at the current stage of development I would expect at least the installed fonts and font sizes to be imported correctly. Without that, it's very difficult to seriously evaluate Scribus as a possible successor to InDesign.

I'm not posting this because I'm looking for workarounds or complicated conversion workflows. I'm posting it to save other people from spending hours on the same ultimately pointless tests. Anyone searching for an affordable alternative to Adobe's increasingly expensive InDesign will probably start by asking one simple question: "Can I continue working with my existing documents?"
Right now, my answer would have to be "no".

MrB

Scribus will open your fonts, but maybe it doesn't know where you installed them - it scans a few default places. You can add extra font paths in preferences.
If you can provide a sample IDML file we can work to improve the import.