This is Bugzilla
View Bug Activity | Format For Printing | XML | Clone This Bug
line breaks in all text based file export formats no longer display correctly in windows notepad compatible format. this is a recent breakage, text needs to include a \n newline char and a \r carraige return char to be displayed correctly by Notepad. This is an inherent flaw in Notepad, but it used to work. Replicated this on windows98 and 2000 Build_Version = 0.7.14_04-Jun-2001 Build_Options = LicensedTrademarks:Off Debug:Off BiDi:Off Pspell:Off Scripting:Off Build_Target = /cygdrive/c/Pritchett/Source/AbiWord/abi/src/WIN32_1.1.8_i386_OBJ/obj Build_CompileTime = 17:30:29 Build_CompileDate = Jun 4 2001
Actually linebreaks are written in the standard of the operating system. On Windows text files have CR + LF but if you write a text file on a Mac or Unix they'll have just CR or just LF. Also there are two kinds of linebreaks in Abiword but in text files they both come out the same (enter vs. shift-enter). There may have been a bug with this in an older build. The code in CVS is definitely fine.
im not sure if i was clear about what i meant if you take any abiword document that has been saved in any text based markup such as .abw, .xhtml, .rtf etc and try and view it in windows notepad it will not be displayed properly, there will be no linebreaks.
Regarding above comment, this is normal, and abi-word has always been this way AFAIK. The only line-breaks in the "source code" of the document will be at new sections and paragraphs. If you want to read the source more clearly, choose the Word Wrap option in notepad. Closing bug and marking as INVALID.
reopening will provide evidence as soon as i can
the proof. sent mail to the list with attached files open them in notepad to see that abiword used to compensate for notepad but the more recent 4th June nightly build does not. http://www.abisource.com/mailinglists/abiword-dev/01/June/0700.html
This is not a bug. RTF is meant to be viewed by a RTF viewer, ABW with AbiWord, etc... We won't be fixing this.
Created an attachment (id=73) [edit] an abiword 0.7.11 document not affected by bug
Created an attachment (id=74) [edit] an abiword 4th June windows nightly build document which suffers from this bug.
RTF should have CR/LF pair AFAIK.
in response to Dom comment: Notpad sucks. This was not previously a problem and someone has BROKEN previous functionality for no particular reason (although i would assume its accidental). I understand perfectly if you choose not to fix it, but some one else might.
If this bug is to be open (which I insist that it shouldn't) I'm recategorizing it.
Revised summary to be more clear.
This is not an RFE because it used to work. Im only asking for previous functionality to be fixed. you have to try and understand that this is an incredibly annoying bug for windows users and the default text editor on windows is Notepad. Dont boast about abiword producing clear readable html export on the webpage if you dont want it to be opened by windows users in notepad (explorer will do that when you view source). tweaked the summary accordingly changing from submitted to OPEN
Created an attachment (id=84) [edit] Doc. Source post 7.14 in MS Notepad
Created an attachment (id=85) [edit] Doc Source 7.14 in MS Notepad
NOTE: The document source looks fine in WordPad. I would suggest using that in the interim. Or use some other freeware notepad. MS notepad stinks!
.abw, .xhtml, .rtf have not defined EOL char, and EOL does not serve to specifically define the content. As for .abw and .html, everywhere we output \n as EOL For .rtf we output \n aswell since file revision 1.1. closing WONTFIX.
Verified. MS Notepad Stinks.