Results 1 to 4 of 4

Thread: Editor saving oddity

  1. #1

    Default Editor saving oddity

    If editing a txt file in the editor, one simply clicks "save", then odd formatting is introduced. By clicking the "save" option-part of the button, then "save as", said formatting doesn't appear. It's as if the editor thinks and saves as though it's an rtf file, but keeps the file type as txt.

    If it crashes (or does the "you're closing BW but haven't saved this file yet") while the editor is open to a txt file, the same odd formatting appears, as below.


    {\rtf1\ansi\deff0{\fonttbl{\f0\fnil\fcharset0 Arial;}}
    {\colortbl ;\red0\green0\blue0;}
    {\*\generator Msftedit 5.41.15.1507;}\viewkind4\uc1\pard\cf1\lang1033\fs2 0

    and every line gets a "\par" tacked on at the end.

    This is problematic if one is writing or editing a txt file that is being integrated into BW, since the VDC doesn't recognize any of it.
    Last edited by Ben Spackman; 01-30-2009 at 04:02 PM. Reason: Clarity
    Ben

  2. #2
    Join Date
    Apr 2004
    Posts
    2,095

    Default

    Could it be the case that the editor is only capable of saving something in RTF format? I guess I've never experienced this because I've never used a simple text file in the Editor, it was always something I continued to use in the Editor.
    Michael Hanel
    PhD candidate Classics Univ. of Cincinnati
    MDiv Concordia Seminary
    MA Classics Washington University
    Unofficial BibleWorks Blog
    LibraryThing!

  3. #3

    Default

    The Editor help file doesn't say anything about file types.

    I just ran a test, by creating a file in the Editor with some random text, saving it as RTF, and then renaming the file as a txt and opening it with Wordpad.

    The formatting that appears is RTF formatting, which becomes visible when you open it as a txt.

    So although the file type is txt, the editor appears to always add RTF formatting by default, regardless of filetype. The only way around is a few (what should be) redundant clicks of "save as" then "txt".
    Ben

  4. #4
    Join Date
    Apr 2004
    Posts
    2,095

    Default

    Quote Originally Posted by Ben Spackman View Post
    The Editor help file doesn't say anything about file types.

    I just ran a test, by creating a file in the Editor with some random text, saving it as RTF, and then renaming the file as a txt and opening it with Wordpad.

    The formatting that appears is RTF formatting, which becomes visible when you open it as a txt.

    So although the file type is txt, the editor appears to always add RTF formatting by default, regardless of filetype. The only way around is a few (what should be) redundant clicks of "save as" then "txt".
    Hmm. Ok, so if you open a .txt file and hit save, it automatically converts it to .rtf style, but if you open a .txt file and explicitly do save as .txt then it will work correctly. I was thinking you meant it could only do .rtf. Then maybe there's a possibility of it getting fixed if the Editor can be trained to recognize what kind of file is open.
    Michael Hanel
    PhD candidate Classics Univ. of Cincinnati
    MDiv Concordia Seminary
    MA Classics Washington University
    Unofficial BibleWorks Blog
    LibraryThing!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •