I hesitate to call this a bug, but it definitely reveals a serious limitation in Mellel's search engine. (Details for those who are interested in PS.) The solution is actually quite simple: 1) Before you export, make a global search in Word for Small Caps and then replace everything with 'found text'. But after the document is imported into Mellel, it ALWAYS takes another value, which is RGB 251, 0,7. docx format, then you can't use the color trick because Mellel changes the color value after import. Therefore I tried to change the color value of red in Word before I exported a file as docx to match the said value. The standard value for the color red is RGB 255, 0, 0 in Mellel. browse through all the occurrences of a word or a phrase in the document. If you want, I can send you such a FindSet. If you have to do this often, you create two Find Actions and run them together simultaneously in a FindSet. This means arrows precede and follow all found text in Small Caps.Ģ) After import you enter the "Small Caps" attribute from the Character pane (Character -> Attributes -> Case) into the Find and Replace boxes.ģ) Then search for "→Anything←" (without the quotes) and replace it with the 'Found Expression'.Ĥ) And finally you search for: → or ← and replace it with an empty Replace box to delete the arrows. It is shown in the following figure: The panel might be displayed when importing RTF and Word documents, depending on your selected import method. (Details for those who are interested in PS.)ġ) Before you export, make a global search in Word for Small Caps and then replace everything with "→found text←". The Font Matching panel enables conversion of original fonts into the best possible alternative supported by Mellel. docx format, then you can't use the color trick because Mellel changes the color value after import. You can then search for the color in Mellel and change everything to Small Caps and back to black. docx, because with those formats you can simply assign a color to all Small Caps in the Word document. You can try to train contributors to use the special suprascript letters in Unicode to indicate 'second edition' and the like, but I have not found a similar way to deal with small caps. I understand where the problem originates, which is in the styles, exactly what is so attractive in Mellel: when you import you impose the styles you have defined for the kind of publication, but small caps and suprascripts are lost, while italics, fats and others remain, because they are defined as separate fonts. When you are importing, as I so often do, it is very time-consuming, and easy to make mistakes, when you have to go over the whole text and manually insert and correct. Small caps are rendered as normal letters and suprascript numbers as ordinary figures resting on the base-line. The problem is the import of small caps and suprascript numbers. lickUp Docs is more sophisticated than Google Docs with the ability to. I had hoped that the new direct import of docx would solve it, but no. Some users feel Mellel is more tailored for professional writers than Word for. There is a problem that has been souring my life with Mellel for many years.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |