Change History for TextExporter 4
TextExporter 4 can export all the stories of an InDesign document into a single file.
Supported output file formats:
- Rich Text Format (RTF)
- InDesign Tagged Text
We still have TextExporter 3 available. TextExporter 3 and TextExporter 4 are functionally equivalent.
TextExporter 3 supports InDesign CS3 – CC 2018. TextExporter 4 supports CC 2014 – CC 2018. If you have difficulties with TextExporter 4, you can try TextExporter 3 instead.
You can try out a fully functional demo of TextExporter 4 for a period of about 20 days. After that, you need to purchase an activation code.
Our activation system is not like others. Make sure to read https://www.rorohiko.com/licensing before purchasing.
Upgrading from TextExporter 3.x/InDesign before 2018
If you are upgrading from TextExporter 3.x: please note that you do not need APID ToolAssistant.
Many of our other plug-ins need APID ToolAssistant installed, but not TextExporter 4.
TextExporter 4 is now under the ‘Window – Extensions’ menu, not under the API menu.
Do not blindly add APID ToolAssistant to your plug-ins folder if all you want is TextExporter. It will make things very confusing.
Instead, use the TextExporter 4 installer, and after installing go to Window – Extensions – TextExporter…
Open the InDesign document you wish to export text from.
Select the ‘Window – Extensions – TextExporter…’ menu item.
A “Text Export Options” dialog should come up. Select the text gathering method you want (see the text gathering section below for more details).
Select the page range you want to export text from.
Click ‘Export’ or ‘Export As…’ to start the export.
With ‘Export As…’, a file-save dialog will appear, so you can select the location of the exported text. Choose a destination folder and a filename and click ‘OK’.
With ‘Export’, the exported text will be saved next to the InDesign document being exported.
Occasionally, certain documents will cause InDesign to crash, most commonly due to slight document corruptions that don’t surface during normal use. The following FAQ entry has some more info on how to work around these issues.