<html>
    <head>
      <base href="https://bugs.documentfoundation.org/">
    </head>
    <body><span class="vcard"><a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> <span class="fn">Mike Kaganski</span></a>
</span> changed
          <a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - TXT file encoding is lost when saving"
   href="https://bugs.documentfoundation.org/show_bug.cgi?id=120574">bug 120574</a>
          <br>
             <table border="1" cellspacing="0" cellpadding="8">
          <tr>
            <th>What</th>
            <th>Removed</th>
            <th>Added</th>
          </tr>

         <tr>
           <td style="text-align:right;">Keywords</td>
           <td>
                
           </td>
           <td>difficultyMedium, easyHack, skillCpp
           </td>
         </tr></table>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - TXT file encoding is lost when saving"
   href="https://bugs.documentfoundation.org/show_bug.cgi?id=120574#c4">Comment # 4</a>
              on <a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - TXT file encoding is lost when saving"
   href="https://bugs.documentfoundation.org/show_bug.cgi?id=120574">bug 120574</a>
              from <span class="vcard"><a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> <span class="fn">Mike Kaganski</span></a>
</span></b>
        <pre>The filter should store the settings in medium attached to the document. The
proper place to store this is likely AsciiReader::Read
(sw/source/filter/ascii/parasc.cxx), which has m_pMedium set in SwReader::Read,
and allows to call its GetItemSet()->Put() to modify the data based on parser
data.

Using this data likely should happen in SwASCWriter::SetupFilterOptions (which
should be implemented, and which is called from Writer::Write, where the medium
is available).

The easy hack implies that a unit test is also implemented, that tests that the
detected non-default settings (e.g., UTF-16BE with BOM with CR line endings,
etc.) are retained on save-and-reload. The unit test should be in
sw/qa/extras/txtexport/txtexport.cxx, and should include reading the exported
file (similar to what TxtExportTest::readExportedFile does), testing BOM and
data bytes.</pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>