<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - : Word file import field conversion" href="https://bugs.documentfoundation.org/show_bug.cgi?id=61618#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - : Word file import field conversion" href="https://bugs.documentfoundation.org/show_bug.cgi?id=61618">bug 61618</a> from <a class="email" href="mailto:phil.krylov@gmail.com" title="Phil Krylov <phil.krylov@gmail.com>"> Phil Krylov</a> <pre>Actually there are two separate problems here. One issue is that the EQ fields have no corresponding functionality in LO (except specific usages for Ruby/Combined characters). Another issue is that the information in unsupported field is lost while roundtripping the formats. The behaviour I am actually observing is: 1) When a EQ field can be parsed as a Combined Characters field or as Ruby styles applied to its content, it is carefully imported as such. 2) When a EQ field contains \o and optionally \ad switch (only) but cannot be parsed as a proper Combined Characters field, it is replaced by an Input field and the arguments are kept within that input field, formatting is lost. 3) When a EQ field contains \o and another backslash-escaped switch (\s \al \ac \ar) it is lost on import. I think, a proper solution (before LO includes any functional replacement for EQ \o) could be: 1) Store EQ fields which cannot be parsed properly, in the same format as field types which are not handled at all: between fieldmarks of type ODF_UNHANDLED. This way they can be seen in the UI, can be processed programmatically and can survive saving back to Word formats. This part requires a patch I am going to post soon. 2) When these EQs stop being lost, one only has to install TexMaths extension and write a small macro converting \o() structures to LaTeX invocations using nested \makebox to achieve overlapping.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>