FCKeditor 之遲來的正義

有在努力用 FCKeditor 的朋友
應該知道就算是現在 stable 版的 2.4.3
如果你要把 FCKeditor 當 Word 用的話…
仍然有許多 bug ._.
例如表格（Table）排版設定等等問題

剛剛到 FCKeditor 網站上晃晃
看到了 2.5 Beta 讓我眼睛為之一亮！
更神奇的是…
以前到現在都不支援的 Opera 也支援了！


















目前 FCKeditor 支援的 browser 有：

• Internet Explorer, 5.5+
• Firefox, 1.5+
• Safari, 3.0+
• Opera, 9.50+
• Netscape, 7.1+
• Camino, 1.0+
  

2.5 Beta 修改紀錄功能真是大躍進！

• [#624] [#634] [#1300] [#1301] Official compatibility support with Opera 9.50 and Safari 3 (WebKit based browsers actually). These browsers are still in Beta, but we are confident that we'll have amazing results as soon as they get stable. We are continuously collaborating with Opera Software and Apple to bring a wonderful FCKeditor experience over their browser platforms.
• [#494] Introduced the new Style System. We are not anymore relaying on browser features to apply and remove styles, which guarantees that the editor will behave in the same way in all browsers. It is an incredibly flexible system, which aims to fit all developer's needs, from Flash content or HTML4 to XHTML 1.0 Strict or XHTML 1.1:
  
  • All basic formatting features, like Bold and Italic, can be precisely controlled by using the configuration file (CoreStyles setting). It means that now, the Bold button, for example, can produce < b >, < strong >, < span >, < span > or anything the developer prefers.
  • Again with the CoreStyles setting, each block format, font, size, and even the color pickers can precisely reflect end developer's needs.
  • Because of the above changes, font sizes are much more flexible. Any kind of font unit can be used, including a mix of units.
  • All styles, including toolbar bottom styles, are precisely controlled when being applied to the document. FCKeditor uses an element table derived from the W3C XHTML DTDs to precisely create the elements, guarantee standards compliant code.
  • No more tags... well... actually, the system is so flexible that it is up to you to use them or not.
  • It is possible to configure FCKeditor to produce a truly semantic aware and XHTML 1.1 compliant code. Check out sample14.html.
  • It's also possible to precisely control which inline elements must be removed with the "Remove All" button, by using the "RemoveFormatTags" setting.
  • [#1231] [#160] Paragraph indentation and justification now uses style attributes and don't create unnecessary elements, and <> is not anymore used for it. Now, even CSS classes can be used to indent or align text.
  • All paragraph formatting features work well when EnterMode=br.
  • [#172] All paragraph formatting features work well when list items too.
• [#100] A new configuration directive "FCKConfig.EditorAreaStyles" has been implemented to allow setting editing area styles from JavaScript.
• [#1060] Compatibility checks with Firefox 3.0 Alpha.