Try downloading the latest version from our web site – we’ve been tweaking some bugs away and added some new features – with a little luck things should work better…

http://www.rorohiko.com/textexporter

Cheers,

Kris

I need a solution for InCopy because the customer don’t use InDesign.

Cheers,

Aaricia

We have an updated version of the TextExporter in the works – please e-mail us at support@rorohiko.com, and we’ll send you a beta version to try. With a little luck that should work better…

The latest beta of StoryTweaker should work as-is with CS4; if you find it does not, could you be so kind to send us a bug report on support@rorohiko.com? We cannot fix bugs we don’t know about! Thanks so much!
Cheers,

Kris

I was wondering: who would be interested in a copy of TextExporter for InCopy? We have a pre-release of APIDToolAssistant and TextExporter available (Mac/Win/CS2/CS3), which seems to work well enough. If there is enough interest, we could productize this version.

The InCopy-capable prerelease can be downloaded from

http://www.rorohiko.com/downloads/TextExporter.2.0.2.pre.zip

(for more info and installation info etc… check the ‘normal’ TextExporter page referred to earlier on this web page)

Any feedback would be greatly appreciated – send it to pluginsupport@rorohiko.com

Cheers,

Kris

StoryTweaker is all about round-tripping text out of an InDesign document into an XML format, and later on flowing it back in with text edits (e.g. to allow a translator to translate the content, or to allow text corrections) without loss of formatting and text placement.

There is a very clear delineation of responsibilities: the ‘tweaker’ can only influence text content.

No layout changes can be made, no new text styles can be created,… – that responsibility remains with the designer.

The idea is that some person or persons (using the free StoryTweaker editor app) can edit the text content (and nothing but the text content) whereas the designer (using InDesign) can edit the layout as well as the content. There is/will be also support for multiple ‘versions’ (in different languages) of a single document – i.e. a single document can be concurrently tweaked by multiple translators, resulting in multiple translated versions of the same document.

Currently, we’re still in the alpha phase of the project – i.e. the program is not feature-complete, and the feature list is still growing and shrinking – ‘pulsating’ if you will – as we go.

In this phase we’re looking for people who have time to play with the tool, muck around, think of things we’ve missed, etc… and who don’t mind a lot of ‘rough edges’ – the software works, but it is rough, and it will be subject to change.

If you’re interested playing with an alpha version, contact joris at rorohiko.com (change the ‘at’ into an @). The latest alpha version we have for download has expired, and we’re about to release a new alpha some time next week.

Tentatively, we’re currently looking at going to beta towards the end of the year.

Cheers,

Kris

This year we bought ALL our authors the InCopy software, we brought them in in droves to our workplace and set up a projector and provided them with a laptop for the day.

I taught the people I work with, that never used InCopy before, how it worked. Then they showed all our authors how to use the software and send it back.

Out of 30 authors there were about 5 who didn’t fully understand the concept. But in general the whole InCopy and editing it as you see in the book was a huge success and greatly received by our authors. There were 2 authors that I personally had to visit their workplace to retrieve the files and I think 1 author that lost their work because they were working from a server that automatically sync’d the files from the laptop to the server and it’s a bit heavy to get into detail as to why that happened, but I know why though and it wasn’t InCopy’s fault at all.

InCopy is the way forward.

For our magazine that is bi-monthly we receive word files. The word files are edited and the basic styles are added to the word file using a word template, they are then proofread, copyedited and then sent to me. The styles are the exact same name in Word as it is in InDesign.

Using Tips from Anne-Marie and David, I import the Word file into a blank InDesign file and then export that text as RTF. Which clears out gunk styles, which was a fantastic tip by the way.

I import that RTF into the magazine and Map the styles.

I then run the Preservelocalformatting.jsx script, that I found through this site, to preserve all the bold, italic, superscript etc. Then I select all the text in the story and hit the Override button, all my character styles are preserved.

The only extra thing I have to do with the word file is convert the footnotes to endnotes, because I work with columns and InDesign can’t span columns yet (come on CS4).

So working with Word files is not so bad, once you have a system in place.

Exporting the files back to Word, that’s a whole other ball game, and I find the script that comes with InDesign names them all weird names, why not name it with the first few letters of the paragraph or something?

But generally I just open a word file up, then select the story and copy and paste it into word. Then I select the next story and copy and paste and so on. Meh, I get paid by the hour