<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - EDITING - Add Reveal Codes feature like there is in WordPerfect." href="https://bugs.documentfoundation.org/show_bug.cgi?id=34002#c18">Comment # 18</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - EDITING - Add Reveal Codes feature like there is in WordPerfect." href="https://bugs.documentfoundation.org/show_bug.cgi?id=34002">bug 34002</a> from <a class="email" href="mailto:j.e.labarre@gmail.com" title="James E. LaBarre <j.e.labarre@gmail.com>"> James E. LaBarre</a> <pre>I would just like to put a comment/clarification here, although I suspect there will be others who understand the technical factors far better than me. My understanding of the WordPerfect file format, and/or the way the application handled managing a document being edited, is that the file is a "streaming data" format (if that is the correct term). A code/format gets activated, and is in effect until it is deactivated. Formatting codes could be nested as well. The idea of the "reveal codes" function was/is to show those embedded formatting codes within the stream. Seems to me the WP formatting concept is basically like a "markup language", and from what I remember of using WP, they looked very much like HTML and XML. And since the OpenDocument format is also a streaming data format, it would seem to logically lend itself to a reveal codes editor. This is, of course, presuming that WP was in fact using a stream of data for their document format, and not using some long-since-lost hack to make it look that way.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>