You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Wednesday, July 14th 2004, 10:55pm

HP forum sight konqueror problem with return key

Im not 100% certain what the problem is but when I send information to HP's forum the new lines are not sent through konqueror and they are with netscape. I'd have to experiment but Im guessing its because netscape sends the new line and return character sequence that windows apps send and maybe konqueror only sends the return character.
Is there an option to send the return character with the newline character?

2

Wednesday, July 14th 2004, 11:21pm

Re: HP forum sight konqueror problem with return key

Quoted

Original von Jeff Sadowski

Im not 100% certain what the problem is but when I send information to HP's forum the new lines are not sent through konqueror and they are with netscape. I'd have to experiment but Im guessing its because netscape sends the new line and return character sequence that windows apps send and maybe konqueror only sends the return character.
Is there an option to send the return character with the newline character?


I can confirm that there's a difference in line endings between Konqueror ("\n") and Mozilla ("\r\n"), both on Linux. I've seen this in the diff functionality of the KDE wiki before we patched it to ignore such differences...

I don't know if there's a switch to change Konqi's behaviour.
Neither do I know what the RFCs have to say about this
so I'm not sure if this is a bug.

If you think it is you may want to file a bug report at http://bugs.kde.org/ , maybe after some further research?

3

Sunday, July 18th 2004, 6:41am

Re: HP forum sight konqueror problem with return key

Quoted

Original von cmbofh

... you may want to file a bug report at http://bugs.kde.org/ , maybe after some further research?

Please don't open a bug report, it'll hopefully be fixed in the next KDE version: http://bugs.kde.org/show_bug.cgi?id=83098