Hi Faruk,
Ha ha, this is turning into a "my CMS is bigger than your CMS"
discussion.
Anyway sounds good. I'm guessing though that it's based on working in a
Windows environment only?
With regards to "standards" I did look into processing the xml format
newer Word documents use but since clients had a variety of Word
versions and platforms on which they were running it this was not an
option. Certainly it is something I must note down to investigate
further.
Nick
My CMS does both - WYSIWYG interface, but also allows people to just
upload their Word documents. Takes care of lists, tables, images,
formatting... everything we don't offer in the WYSIWYG editor gets
stripped out. After uploading, the content is in the exact same shape
and
form as it would've been when entered into the WYSIWYG editor.
:)
I actually went a step further there. I didn't find a browser based
wysiwyg editor that performed satisfactorily across platforms and
browsers so I decided to get the clients to save Word to (filtered)
html and then clean that up server side. That way they did not have to
get the hang of anything new except the workflow.
However, there were instances where Word would fail to translate, eg a
list to an html ordered list, so while dabbling I had one client use
Markdown dingus ( http://daringfireball.net/projects/markdown/dingus )
to quickly do bits and pieces. That was successful enough that as
mentioned in another post I integrated it into my cms and it is even
used where users are unaware of it's presence.
Ultimately there is no one solution since clients and circumstances
differ and I'm often surprised when I read so much certainty about
what
clients want. Personally I'm often surprised by just how much clients
are willing to learn if it means they end up with a more appropriate
solution to their needs.
*********************************************************
The CMS discussion list for http://webstandardsgroup.org/
*********************************************************
