Forum Moderators: open
Tools > Web Settings > Language >
Server message language: English
Default page encoding: US/Western European
Does that correct the problem?
P.S. You may want to check the option of ignore the keyboard when deciding on the encoding of new pages.
[edited by: pageoneresults at 7:08 pm (utc) on Dec. 10, 2003]
Hmm, fontplague writes extremely bloated HTML code (as you already found out).
No it doesn't! Inexperienced users of FrontPage write extremely bloated code, it has nothing to do with the program. DW and any other WYSIWYG editor will do the same if the user is not proficient in the WYSIWYG interface.
I take offense to the fact that anytime FP comes up in a topic, someone has to chime in with negative comments about the program.
I shall repeat, it is not the program itself. It is how the program is used.
However if the tag is there and you type anything, the keyboard must match the content="fr-ca" or else the <span lang="en-us">anything</span> appears. (if your keyboard is in en-us, same for en-ca)
So it's not always the user (as you think)
FP2002 XP Service Pack 1 [support.microsoft.com]
There is a known bug with this issue and the Service Pack should correct it. Even though you may not be using the XP OS, this patch still applies to FP2002.
Span Lang Tag Inserted if Keyboard and Language Do Not MatchIf you set the page language to a language different from the keyboard language, any text that you type on the page is encapsulated with the following tag:
<span lang="keyboard language code">
SP-1 changes this behavior so that this tag is used only when the keyboard and page language use different code pages.
Inexperienced users of FrontPage write extremely bloated code, it has nothing to do with the program.
The whole point of FP and other WYSIWYG editors is to do the coding for you. If it takes years of study just to be able to use the program desinged for ease of use, then something is wrong with the program. I have better things to do with my time than leaning how to jump through hoops so FP doesn't write too much bloat.
I use TopStyle Pro 3.0 and used to use Homesite 4.5.2, and guess what? Not a single extra tag unless I put it there.
HTML and CSS are not exactly hard to learn to code. And since you need to know how to code in them even if you use FP, at least for anything beyond the trivial, you might as well avoid the interference and use a tool which supports good coding.
Don't get me wrong--FP has its place: it allows amaetures to through togeather a almost half-way decient site by someone without much skill. (If you want to talk about bloat, ever take a look at the pages MS Word generates?) I just think for serious work there are better tools to be had. I can't comment on DW, since I don't think I've used it for more than a total of 10 min.
To address the original post of this thread: If you're just starting out, don't worry about it; if you're up to the point where you're worrying about bloat, it's time to get a better tool.
The whole point of FP and other WYSIWYG editors is to do the coding for you. If it takes years of study just to be able to use the program desinged for ease of use, then something is wrong with the program. I have better things to do with my time than leaning how to jump through hoops so FP doesn't write too much bloat.
It doesn't take "years of study" to use FrontPage, and you don't have to "jump through hoops" to avoid code bloat.
It doesn't take "years of study" to use FrontPage, and you don't have to "jump through hoops" to avoid code bloat.I was exagerating to make a point. The Talmud says that a father should teach his son to ride a horse. One might think that the modern day equivlent is driving a car, but it's not. A horse has a will of its own which the rider must overcome; a car doesn't. While learning to rule over natual tendencies may be a valuble lesson for life, if you need to do that with a program you're wasting your time and energy.
Kirby-
...or just write the code yourself in html mode.Using FP to hand code? If you want to hand code you should use a tool which aids in hand coding, not just supports it.
It's improtant to use the right tool for the job, not just a tool which can be made to work. FP has some powerful features, but they come at a cost. Which is more important: getting the job done with ease or quality? How you answer that question should determin which tool you use. I'm not saying you can't write good code with FP; I'm saying you should use the right tool for the job. For high qulity code FP is't it.
For high qaulity code FP is't it.
I tend to differ with that statement. I've been using FP since 1996. I use both the WYSIWYG and HTML interfaces. Both are very powerful if you use them correctly and if you understand basic HTML.
The HTML editor in FP has all the bells and whistles that most other text editors have. You set up your preferences for editing and viola, you have what you want.
Cosmin, were you able to get rid of the <span> tags using the patch available?