However, texts like this should be seen as code.įor example, if you want to italicize a specific word in your text, you select it and then click on the corresponding button. Without programs such as Word, you would enter a tag in your text (e.g. 'word'), which the device then interprets and implements. In our example, the device would be the printer.
Kompozer text box pdf#
However, converting the Word document into a PDF file or displaying the document in a browser can also be seen as an output e.g. The question of whether an HTML editor is a WYSIWYG editor or not plays an important role.
But before going into detail, it makes sense to briefly look at the history of these editors. One of the first word processing programs was WordStar, which was released in 1978 and still has a prominent user today in author George R.R. WordStar originally ran on the operating system CP/M and only had a few functions. In the first version, writers still had to work with tags for the typesetting. But the general opinion is that the program was the first WYSIWYG editor. It was possible to use italics or bold formatting in a text and see the results on the monitor straightaway. The problem at the time was that the computer graphics weren’t very advanced: the computer systems couldn’t display an exact reproduction of what the text would look like when printed or published.
Kompozer text box full#
The entire thing is chock full of all the things one expects from a WYSIWYG editor, and as such for someone like Rukbat or myself to even want to bother to try and help you, we'd have to throw that entire mess of code away and start over from scratch - it would be faster than to try and do anything with the decade and a half out of date methodology and nonsensical code that editor saddled you with.With the possibilities of PC and Mac systems increasing, text could be displayed better on the monitor. Nope, he guessed EXACTLY what you are referring to - as the link to your page confirmed. Anyone telling you otherwise is packing you so full of sand you could change your name to Sahara. The code doesn't even make sense having multiple HEAD, multiple TITLE, massive tables with even more massive STYLE attributes for christmas only knows what - it's a laundry list of how not to build a website - and ENTIRELY what one can expect from Kompozer.Įditors like Kompozer, Frontpage, the preview pane in Dreamweaver, etc, etc, are NOT how you build a website - they amount to nothing more than nube predation and broken methodologies.
Hence your 11k of markup to deploy 336 bytes of actual content and two inputs. Since you have tables for no good reason, presentation inlined in the markup, nothing remotely resembling semantics, and the whole other host of things that basically throw accessibility out the window. The entire thing is chock full of all the things one expects from a WYSIWYG editor, and as such for someone like Rukbat or myself to even want to bother to try and help you, we'd have to throw that entire mess of code away and start over from scratch - it would be faster than to try and do anything with the decade and a half out of date methodology and nonsensical code that editor saddled you with. Click to expand.Nope, he guessed EXACTLY what you are referring to - as the link to your page confirmed.
0 kommentar(er)
