A HTML editor definitely should not reformat the user's source code! - Why not as an option, but FOR SURE NOT as a unavoidable option!
The reformatting would not be so bad if it did it in a more organised way. At the moment it just seems to word wrap the whole document. It would be better if it added extra cr-lfs after certain tags, e.g. </p>, </head>, </div>, </table> etc
It would also be nice to have some reformatting options. The most important one to me would be line length. The formatter cuts the line off halfway across my page.
There must be an option to turn off autoformat.
this one cannot have a high enough priority. I want my indentation and my line structure left alone! it makes it so much easier when I am looking at the html or css text (I use the source view almost exclusively).
and I do NOT like the CSS text file you build at all. There is no structure! I have to sit and reformat it constantly.
Should be highest priority!!
I’m afraid KompoZer will always reformat your markup. If you want to know why, read Daniel Glazman’s explanation: http://www.glazman.org/weblog/dotclear/index.php?post/2005/03/29/964-why-does-nvu-change-my-markup
In other words: that’ß not a bug, that’s a feature. :-(
I have to admit I *hate* the way KompoZer reformats the HTML code. I rely on HTML Tidy to reformat it better if I have to edit an HTML file in a text editor.
So at the moment I’m trying to implement Tidy in KompoZer so the HTML code will be serialized nicely, with a bunch of options to control the indentation, line lengths, and so on. This might not be ready for KompoZer 0.8, but I’m doing my best to have this feature working as soon as possible.
-Kazé, KompoZer lead dev
I think KompoZer is aimed more at the beginners who just want to make a basic website without knowing HTML. So why wouldn't it clean up a beginner's markup just in case s/he made a mistake?
The Kompozer should have the option to change or not the original code. I'm using to let beginners to change the text out of the Dreamweaver template code. But it changes de template too and the dw loses itself.
I would like to add my voice to the chorus on this one. The way Kompozer changes my source code is a great source of frustration because I often like to log in to my web server using SSH to make quick edits using a text editor like NANO.
OR, it would be even better if the user could configure HOW Kompozer reformats the source code. It would be great if I could teach Kompozer my particular preferences for tabbing and spacing.
For example, since some people like to have each HTML tag on a separate line, while others like to have an opening tag at the beginning of a time and the closing tag at the end, it would be great if we could tell Kompozer when to create a new line and when not to.
I am now cool on this one. With Hancoder and tidy I can make the code look tidy and understandable and edit it with ease - just don't use the built in source viewer.
What it looks like when complete and uploaded is not important to me as long as it works for both people and robots, which it does.
What fabiwan is planning to do is good and I support that.
I am so very not cool with this. It is a stopper for me. I may change the way I do formatting for different content types. If I use an external editor, and try to edit the page in WYSIWYG mode, it rearranges things, and the external editor has not prevented it. Thus, the handcoder plug-in is NOT a fix for this issue. I do not like to see my styles migrated to the top of the source, when I want it clear that they might be being used only in a local instance. I don't care if it violates XML standards. This is the Web, and the way people like to use html still counts. I am currently using Selida, which hasn't had an update since 2002. I wish the CSS editor were stand-alone, since it is the best one out there, but Komposer has this deal-breaker. Perhaps a decade or more ago, I quit using FrontPage because it made changes to my source I thought it shouldn't. I won't stand for it. Maybe I'll break down and pay for one, one day. I would feel differently about it insisting to put in <BR> in places I had edited, if I imported a web-page, and it left the rest alone. Yes, I realize html runs faster without the whitespace, but my editing does not. A whitespace removal tool before uploading would solve that. It has an option not to reformat text, but it does not work.
Marked as duplicated of bug 1607834
Log in to post a comment.