Hi
I have made various bits of text superscript in Scrivener. If I export to rtf and view in TextEdit, the superscript is fine. But I need to submit my final version using Word, and if I export to .doc, .docx or rtf and open in Word 2008 all the superscript has been turned into standard text.
How can I move my superscript formatting into Word?
Thanks.
How did you make it superscript? Did you use Text > Font > Superscript? Because that worked fine for me when I just tested exporting some superscript text to Word via RTF.
Best,
Keith
No. I didn’t do it that way.
I think I’m using the system Typography tool. Not sure how I found it, but you can get it by going CMD-t to show fonts, and then using the gear wheel to show Typography.
That way you do get lovely looking superscript, but…
The “Typography” section of the font panel uses font glyph variants, and Word uses a different version of many fonts, which is most likely why you are seeing the discrepancy. Doing it that way is just using a font variant rather than true superscript - if you do it the way I said, superscripts will go across fine.
All the best,
Keith
Thanks for the info, Keith.
Unfortunately, I’m in the final editing stages and I’ve already done all the superscript using the Typography panel. Is there any way I can do a find chage into normal superscript?
Thanks.
I found a workaround that at least enabled me to spot the superscripts before manually changing them in Word.
First, I compiled a new version of the manuscript from Scrivener as an rtf. I changed the extension on this file to .txt. I then opened this .txt file in Text Wrangler (not TextEdit) and was able to spot all the superscripts by searching the .txt for “AppleTypeServices”, which is part of the mark-up that precedes every superscript run of text.
Then it was simply a matter of taking the time to find those same spots in the Word version of my manuscript and making the changes.
It would be great if the new version of Scrivener could handle this kind of superscript properly, and convert it for exports to .doc and .docx.
Glad you found a solution - I racked my brain and hadn’t got around to thinking of a good workaround before you found your own. I’m afraid it’s unlikely Scrivener will have improvements in this regard, as it’s not really a Scrivener problem but just an inherent difference between the typographical systems and fonts (over which I have no control anyway, as Scrivener is just built on the OS X text engine). Scrivener already handles superscript in the regular way.
All the best,
Keith
At some point in the future, the problem may be solved at the Word end. There are reports that at least one OpenType feature – ligatures – is enabled in the beta version of Windows Word 2010. Perhaps they will also add support for OpenType superiors, small caps etc. And that might filter through to the next version of Word for Mac.
Hi Keith
I’m sure that few Scrivener users are writing books about physics (which is what I’ve just done) and so few have the same need for superscript (or, to be more precise, ordinals) that I have, and I’m sure you’re pulled in a million directions when it comes to development, but it seems to me that the Typography panel is an easy way to make superscript for the user (all it takes is one click of a button) – and it’s superscript that looks much nicer than that ugly stuff you get from the Font menu.
The other advantage of this form of superscript is that (in my admittedly limited testing) it just works if you go into anything else that uses the OS X font engine (for example, TextEdit), and if you’re compiling to Word, all your code need do is replace
\AppleTypeServices\AppleTypeServicesF655361 2\AppleTypeServiceswith a Word friendly superscript 2 (at least, that’s the case in the true type font I was using).
Anyway, thanks for Scrivener. This book is the first time I’ve used it, and I’ve really enjoyed it.
Best regards
Jeff
That’s certainly not a bad idea, but it’s not that simple because I use Apple’s RTF exporter so have to hack into it (as I do for other features), and Apple don’t but curly brackets around the “AppleTypeServices”, making it very difficult to isolate them for replacement (and the ending “\AppleTypeServices” may not be present if the superscript is at the end of the document. This complicates the logic that would be required to replace these control words without potentially messing up the surrounding text. Searching for “\AppleTypeServices\AppleTypeServicesF655361” is easy enough, but what if other typographical features are turned on also? For instance, with “slashed zero”, this could become “\AppleTypeServices\AppleTypeServicesF917508\AppleTypeServicesF655361”.
Of course, Scrivener could just replace “\AppleTypeServicesF655361” with “\super”, but this presents another problem - what about users who export as RTF for opening in a program other than Word, for instance one that uses the OS X text system? They will find their superscript messed up, then, as it may be superscript but the font size will be larger.
All the best,
Keith