If for some reason you want to take articles from PageStream and put them into a QuarkXPress document, this script will assist in that process. Although it could be adapted to go through a document's chapters iteratively and export every article and the contents of every text frame, as it stands the process is manual.
Even with UTF-8 selected as the encoding many, possibly all, non-ASCII characters will be converted to PageStream's Unicode tag format. Any character so encoded will be converted into UTF-8.
PageStream style tags are converted into Quark tag notation. On import, if the tag does not exist then an entry is created for it (just like in PageStream). In cases where PageStream has numerous style tags piled up at the beginning of a paragraph, only the last one is retained. This will nearly always be the correct way to handle it — and if it isn't you're better off recreating the formatting in Quark.
Some directly formatted text is converted — in particular applied bold, italic and underline.
Some tags need no conversion. For example, both PageStream and Quark use <\n> to represent a new line. After considering style tags and other handled or equivalent tags, the remaining tags are stripped from the file.
That really depends on how the original document was formatted. You will probably get much better results if no character styles are used. Bold, italic, etc. will work just fine if PageStream exports them correctly (there is, or at least has been, a bug in this regard: no guarantees are made).
No attempt is made to handle directly formatted line height, character width, word spacing, etc. The article will display differently in Quark anyway (even the same font will give different results, and that's before considering differences in hyphenation) so tweaks wouldn't make much sense anyway. If the text is all formatted directly rather than using paragraph styles you're probably just better off with a plain text export/import, no text codes involved at all.
In principle, tabs could be converted and I wrote code to do so. Regrettably, the implementation is problematic and the effort to make it work was too much to be worth it.
If you actually manage to embed an object in a text frame it will not survive an export. This is a limitation of PageStream, but even if it weren't the script wouldn't support it.
Because it isn't worth the effort. And comparing the default tags present at the beginning of an exported article shows that tags don't always match the documentation and there are undocumented tags.
Although nothing compares to PageStream for entering text or handling chapters, PageStream has its share of missing features and bugs. For example, its implementation of OpenType features is incomplete and partially incorrect. These and other issues are a fact of life with PageStream so there are some documents that cannot be reasonably constructed in it. This script facilitates moving some or all of a project from PageStream to Quark.
Basically because, even though Quark sucks, Adobe sucks worse. They both have modern font support, but surprisingly poor handling of chapters. Neither appear to acknowledge bugs or shortcomings, but at least Quark is still selling their software rather than renting it on a monthly basis.