#1980: Change default <b> and <i> to <strong> and <em>
----------------------------+-----------------------------------------------
Reporter: fredck | Owner:
Type: Task | Status: new
Priority: Normal | Milestone: FCKeditor 2.6
Component: Core : Styles | Version:
Resolution: | Keywords: Discussion
----------------------------+-----------------------------------------------
Comment (by alfonsoml):
I think that this isn't just an issue of one tag over the other. This is
almost a religious issue for some people, and the fact is that from a
semantic point of view <strong> isn't the same than <b>, and <strike>
isn't the same than <del>. But if you want to see how far people can argue
about that differences, take a look at this thread:
http://lists.w3.org/Archives/Public/public-html/2008Feb/0062.html
From my point of view the solution would be to offer some "profiles", just
a set of configuration settings that makes the editor behave in one way or
another according to each developer taste.
So one profile would be something like "html3", where no styles are used,
useful to work with outdated systems that don't understand css, but are
parte of the workflow (some pdf converters, partially flash did have also
some limitations, but I think that currently is much better).
Another one would be "html4", (i'm trying to figure out the different
profiles just to express my point of view), this would use for example
inline-styles, <b> and <i> (after all the user is probably just wanting to
make the text bold, not to give them any semantic meaning), everything
that is possible with html4.
Another is "pure xhtml1.1" now everything that is disallowed in xhtml1.1
is removed. Presentational attributes from the elements (border, style..)
aren't allowed, and the developer must configure the classes that he wants
to use. Instead of the <b> and <i> the <strong> and <em> buttons are
present, but those buttons must not be the same ones (the pictures), they
must reflect that they are used to mark a section as <strong> or <em>. The
underline, strike, color, background color buttons aren't available. Don't
even mention font-size or font-family...
With this mode you would end up with a WYSIWYM editor, and the people
cared about the purity of the content can use that mode and leave the rest
of the humanity keep using something that works for them. Setting up and
using such configuration is much more difficult (you need to define the
classes that you want to use beforehand so if you want to leave end users
working with that mode they will find that they are too restricted and
might have to face their anger about such a bad editor that doesn't even
have a color chooser).
So my vote would be to create such profiles (that's it: a different
fckconfig.js file for each one) and leave as the default one one that
resembles the current configuration, but maybe adjusting it a little (I'm
thinking about the option to clean content from Word to preserve the
formating instead of removing headers and generating font tags).
I would even remove the <u> and <strike> buttons from the default toolbar.
--
Ticket URL: <http://dev.fckeditor.net/ticket/1980#comment:2>
FCKeditor <http://www.fckeditor.net>
The text editor for Internet
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
FCKeditor-Trac mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fckeditor-trac
