This would definitely be a plus. Associated with this I'd like to suggest an additional feature: if InqScribe currently uses .txt files within the .inqscr package, and if the idea suggested here would mean allowing .rtf or something similar as an alternative saving option within that package, it would also be very useful to have external access to the .rtf file. That is, I'd like to be able to markup the underlying text files using other programs as well, without having to export and create a copy of the transcription text. Case in point: I use the database DevonThink Pro Office to markup my transcriptions, and I'd rather have those markups on the original files than on a copy of them, because I often go back to re-do portions of the transcription. A single text (.rtf) file would prevent a lot of complications that are possible with the current workflow.
Josh
This would definitely be a plus. Associated with this I'd like to suggest an additional feature: if InqScribe currently uses .txt files within the .inqscr package, and if the idea suggested here would mean allowing .rtf or something similar as an alternative saving option within that package, it would also be very useful to have external access to the .rtf file. That is, I'd like to be able to markup the underlying text files using other programs as well, without having to export and create a copy of the transcription text. Case in point: I use the database DevonThink Pro Office to markup my transcriptions, and I'd rather have those markups on the original files than on a copy of them, because I often go back to re-do portions of the transcription. A single text (.rtf) file would prevent a lot of complications that are possible with the current workflow.