![]() ![]() ![]() I had to monkey around to find something that works (barely)ġ. That is even more important when you are taking information from Word to Mellel! Make sure you export/save as RTF from Word if you are going to take that document back to Mellel.Here is an update for anyone interested in this issue: To ensure that you are getting the most accurate round–tripping when working with Word, make sure you are dealing in RTF. The reason this is frustrating is that every new version of OS X introduces new Word import abilities, so what may work one way on a machine running Mavericks will not give you the same results as if you did it on a machine running Snow Leopard.) So, whatever level of Word support you have in Text Edit for whichever version of OS X you are running, that is the same level of Word import support you will get in Mellel. (Similarly, Mellel’s Word import ability is handled by the OS. Because “Word Format” and “RTF” as export options generate the exact same file, it really is disingenuous for Mellel to have a “Word Format” export I believe it is only there to “make things easier”, when it obscures some issues. I believe it is this deception that Mellel is engaging in that is causing your problem with Mellel. When you open this file in Word, Word thinks it is a DOC file, but realizes that it is RTF when it first reads it, so it then converts it to a native Word format. What Mellel does when you choose “Word Format” is create a RTF document with a DOC file extension. Microsoft publishes the RTF file specification, and it is updated with every version of Word because RTF is supposed to maintain 100% feature parity with Microsoft’s own DOC(X) formats. ![]() The RLE control character does basically the same thing, but is geared more towards smaller spans of ‘embedded’ text.Īs far as the Word export problem: Mellel does not actually export Word format-either a binary DOC format, or the XML–based DOCX format-at all. The RLO control character tells the Unicode Bidirectional Algorithm (the thing that determines which characters are RTL, and which are LTR, and what to do with numbers, punctuation, &c.) to disregard the rules it knows, and force it to treat what follows as RTL text. You must manually insert them using either a Unicode hex–entry keyboard, or possibly the character palette. You cannot find them in Mellel’s interface. I apologize, there was a typo in my previous post. I hope that there is on Mellel a way to fix the direction to be trasferable to all platforms. There it is opened with the Left inclination. Then I Save As the file in Word format (once again) then sent it to the PC side. I add to the road the following step: I open toe Word file on my desktop with NeoOffice, the last paid version, check that everything is OK since the step of Mellel, and rearrange what is needed, and Neo Office on Mac has the ability to handle R2L files. Since Hebrew files created by Mellel and exported to Word format, when coming to PC and opened by Word PC in Hebrew, the results are catastrophic. I have to add one more point to what you wrote to the Redlers. What are these two characters, and where can I find them in the Mellel interface, if at all. You wrote: ".You could try the RLE (Right–to–Left Override) control character at U+202E, or the RLE (Right–to–Left Embedding) control character at U+202B." ![]()
0 Comments
Leave a Reply. |