![]() ![]() The only true WYSIWYG is to open the file with a browser, preferably at least 3 - Firefox, Chromium, and IE. Unless you know the underlying HTML, it will be difficult or impossible to fix, and it is much easier to learn to write good code then fix bad code )Ģ. Those errors will eventually cause a problem, and you will need to then dive into the code and fix them. It is detailed (yes, you can skip the installation section for example) and includes screenshots.ĭid a validation check and, apparently, the Serif program I purchased made about 500 errors in the process. If / when you are interested, there are many on line tutorialsīluefish and the link I gave you on gedit both have the html tags built into the menu, ie they are graphical. If you attach your html file as a text file I we can take a peek to see what, if any, problems it has. I will warn you, it is often easier to copy - paste your text then it is to find the error. ![]() The second step, and here is where WYSIWYG editors are a pain, view the code with gedit or bluefish and find and fix the errors the editor injected. Learning the syntax of html and css pays off in spades.Īt any rate, - The first step is to try to run your page through a html validating service : Just because your page passes a html validator does not mean it renders properly in all browsers (unfortunately browsers are often quirky to say the least when rendering html pages). Nothing like viewing the page in a few browsers ) ![]() You then view your pages with a browser, such as firefox and midoiri. Of the three, bluefish may be the best if you are migrating from a WYSIWYG editor. Once you learn the underlying code, try to migrate to tools such as bluefish, gedit, or honestly I use vim. The code they generate is sloppy and in the long run, IMO, it is better to learn to use other tools. There is a reason why "the experts" recommended you not use these programs, lol There is nothing wrong with using WYSIWYG programs when first starting, or a small number of "simple" pages, however. A folder called "kompozer" will be created.ģ) You're done!! To run kompozer simply go to that "kompozer" folder and run the shell script called "kompozer" by right-click on it or whatever. If you have a ~/downloads folder that will do, but perhaps you may want to extract elsewhere, an external usb disk being also possible. I solved it in this way:ġ) Download the compressed tar.gz file of kompozer for linux from their site ().Ģ) Extract to a place you find apropriate. Regarding your problem to run Kompozer: I'm running current LUbuntu and I have no problems with kompozer08b3, but I myself ran into a similar problem some releases ago (by the times of Hardy Heron). They're well seen both in win2 & linux, be it with ie, ff, epiphany, chrome. Well, as a non-expert person, I'd say that Kompozer worked fine for me to create and maintain some (three really) simple web pages I maintain since some years now. Web authoring experts usually say that every single WYSIWYG-like program for creating web pages is crap, and that html hand editing form scratch is the only way, despite the authors of such programs claiming that generated code will be W3C compliant ![]() Will Kompozer build a site that is workable by various browsers? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |